Type-2 HARQ Codebook Decision in the Presence of PDCCH Repetitions

Abstract

A system and method for codebook determination is provided herein. In some embodiments, a method for constructing a codebook performed by a wireless device includes: defining a first PDCCH opportunity of a plurality of PDCCH opportunities associated with a physical downlink control channel (PDCCH); identifying the first PDCCH opportunity for each detected downlink control information (DCI); and constructing a codebook based on the first PDCCH opportunities of all detected PDCCHs with a counter field in the corresponding DCI. In this manner, construction of a type-2 hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook in the presence of PDCCH repetition is possible with minimal specification changes.

Description

[Technical field]

[0001] [Related Applications] This application claims the benefit of Provisional Patent Application No. 63 / 138,117, filed January 15, 2021, and Provisional Patent Application No. 63 / 138,721, filed January 18, 2021, the disclosures of which are hereby incorporated by reference in their entireties.

[0002] This disclosure relates to codebook determination. [Background technology]

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

[0004] Data scheduling in NR is typically done on a slot basis, an example of which is shown in FIG. 1 with a 14-symbol slot, where the first two symbols contain the Physical Downlink Control Channel (PDCCH) and the rest contain the Physical Shared Data Channel, which is either the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH).

[0005] In NR, various subcarrier spacing values ​​are supported. The supported subcarrier spacing values ​​(also called various numerologies) are Δf = (15 × 2 μ) kHz, and μ∈0,1,2,3,4. Δf=15 kHz is the basic subcarrier spacing. The slot time length for various subcarrier spacings is given by 1 / 2μ [ms].

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

[0007] Downlink transmissions can be either dynamically scheduled, with the gNB sending a DL assignment to the UE via downlink control information (DCI) on the physical downlink control channel (PDCCH) for each PDSCH transmission, or semi-persistently scheduled (SPS), with one or more DL SPSs semi-statically configured, each of which can be activated or deactivated by a DCI.

[0008] In NR, three DCI formats are defined for scheduling PDSCH, namely 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 the UE is not fully connected to the network, while DCI format 1_1 and DCI format 1_2 can be used to schedule multiple-input-multiple-output (MIMO) transmissions with two transport blocks (TBs). These DCI formats are called DL DCI formats.

[0009] The 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 REG is equal to one RB during one OFDM symbol. L is called the CCE aggregation level.

[0010] The set of PDCCH candidates is defined in terms of a PDCCH search space (SS) set. The 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 portion (BWP) for monitoring PDCCH candidates.

[0011] Each SS set is associated with a CORESET, which is a set of N RB CORESET N resource blocks in the time domain symb CORESET ∈{1,2,3} consecutive OFDM symbols. In NR Release 15, a UE can be configured with up to 3 CORESETs per bandwidth portion.

[0012] For each SS set, the UE is configured with the following parameters: ·k s PDCCH monitoring period of slots, and s PDCCH monitoring offset for slots PDCCH monitoring pattern in a slot, indicating the first symbol of the CORESET in the slot for PDCCH monitoring · k indicates the number of slots in which the search space set exists s T below slot s The length of time Number of PDCCH candidates M for each CCE aggregation level L s (L)

[0013] The UE determines the PDCCH monitoring occasions on the active DL BWP from the PDCCH monitoring period, the PDCCH monitoring offset, and the PDCCH monitoring pattern in the slot. For each search space set s, the UE determines whether the PDCCH monitoring occasions are (n f N slot frame,μ +n s,f μ -o s ) mod k s = 0 for frame n f In slot n s,f μ It is determined that it exists within N slot frame,μ is the number of slots per radio frame. The UE s,f μ Starting from T s Monitor PDCCH candidates for search space set s for the next k consecutive slots. s -T s do not monitor PDCCH candidates for search space set s for consecutive slots.

[0014] The UE detects a PDCCH at each PDCCH monitoring opportunity, and when a PDCCH is detected, the UE decodes a corresponding PDSCH based on the decoded control information in the PDCCH.

[0015] In Release 16, a new PDCCH monitoring capability is defined to better support multiple PDCCH monitoring occasions in a slot, at least in terms of the maximum number of non-overlapping CCEs for channel estimation. The new restrictions are discussed based on the concept of PDCCH monitoring span. In short, the definition of PDCCH monitoring span provides a set of rules for the UE and gNB to have the same understanding of the PDCCH monitoring span pattern in a slot based on the CORESET / search space configuration and UE capability signaling related to PDCCH monitoring. The UE signals a set of candidate values ​​containing parameters related to the span gap X (minimum gap in OFDM symbols between two consecutive spans) and the span length Y in OFDM symbols. Then, together with the CORESET / search space configuration, a monitoring span pattern can be derived. The span pattern, which can accommodate multiple spans in a slot, is repeated across multiple slots.

[0016] <NR HARQ ACK / NACKフィードバック> When a PDCCH is detected by a UE, the decoding status of its scheduled PDSCH is sent back to the gNB in ​​the form of a Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) on the Physical Uplink Control Channel (PUCCH) resources. If the PUCCH overlaps with a PUSCH transmission by the same UE, the HARQ ACK feedback can also be carried on the PUSCH.

[0017] Similarly, when a DL SPS deactivation DCI or a DCI for a secondary cell (SCell) dormancy is received by the UE, the UE sends a HARQ ACK to acknowledge receipt of the DCI.

[0018] When the UE detects a DCI format scheduling a PDSCH reception ending in slot n or detects a DCI indicating 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 the PDSCH to HARQ timing indicator field if present in the DCI format or provided by the dl-DataToUL-ACK. k is also referred to as K1. For DCI format 1-0, k may be one of {1, 2, 3, 4, 5, 6, 7, 8}. For DCI format 1-1 and DCI format 1_2, k may be one of a set of values ​​configured in the dl-DataToUL-ACK. The set of values ​​may be in the range of {0, 1, ..., 15}. Up to eight values ​​may be configured in the set.

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

[0020] In NR, up to four PUCCH resource sets can be configured for a UE. The PUCCH resource set with pucch-ResourceSetId=0 can have up to 32 PUCCH resources, while for PUCCH resource sets with pucch-ResourceSetId=1-3, each set can have up to 8 PUCCH resources. The UE determines the PUCCH resource set in a slot based on the number of consolidated uplink control information (UCI) bits to be transmitted in the slot. The UCI bits consist of HARQ ACK / NACK, scheduling request (SR), and channel state information (CSI) bits.

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

[0022] In the case of CA and / or TDD, if more than one DL DCI format is received, the PUCCH resource determination is based on the PRI field in the last of the DL DCI formats received and detected by the UE, where the multiple received DCIs have values ​​of the PDSCH-to-HARQ_feedback timing indicator field that indicate the same slot for PUCCH transmission. For PUCCH resource determination, the detected DCI formats are first indexed in ascending order across multiple serving cell indices for the same PDCCH monitoring occasion, and then indexed in ascending order across multiple PDCCH monitoring occasion indices.

[0023] <NR タイプ2HARQ-ACKコードブック> NR Release 15 supports two types of HARQ codebooks for multiplexing of HARQ Ack for multiple serving cells in case of Carrier Aggregation (CA) or multiple DL slots in case of TDD: semi-static codebook (Type 1) and dynamic codebook (Type 2). UEs can be configured to use either one of the codebooks for HARQ Ack / Nack feedback.

[0024] The 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 does not change dynamically. Therefore, the feedback overhead may be large.

[0025] Unlike the HARQ codebook of type 1, the size of the HARQ codebook of type 2 changes dynamically based on the actual number of PDSCH receptions, SPS PDSCH releases, or SCell dormancies associated with the same PUCCH resource for HARQ Ack feedback. For this purpose, a counter DAI (downlink assignment indicator) field is defined within the DCI, and in the cases of DCI format 1_1 and DCI format 1_2, a total DAI field is also defined (when more than one serving cell is configured).

[0026] The value of the counter DAI field within the DCI format represents the cumulative number of {serving cell, PDCCH monitoring occasion} pairs in PDSCH receptions, SPS PDSCH releases, or SCell dormancies associated with the DCI format up to the current serving cell and the current PDCCH monitoring occasion, first in ascending order of the serving cell index c and then in ascending order of the PDCCH monitoring occasion index m, where 0 ≤ m < M and M is the total number of PDCCH monitoring occasions.

[0027] When a total DAI exists within the DCI format, its value represents the total number of {serving cell, PDCCH monitoring occasion} pairs in PDSCH receptions, SPS PDSCH releases, or SCell dormancies associated with the DCI format up to the current PDCCH monitoring occasion m, and is updated from PDCCH monitoring occasion to PDCCH monitoring occasion.

[0028] Figure 3 shows an example in which a UE is configured with two serving cells and three PDCCH monitoring opportunities. The corresponding counter DAI and total DAI values for each scheduled DCI are shown. The counter DAI is updated after each scheduled DCI, while the total DAI is updated only for each monitoring opportunity. Since only 2 bits are allocated to either the counter DAI or the total DAI in a DCI, the actual DAI value wraps around by an operation modulo 4. If the number of consecutively undetected DCIs is less than 4, the UE can determine the actual number of transmitted DCIs even if some DCIs go undetected.

[0029] For the HARQ-ACK information transmitted on the PUCCH in slot n, the UE determines the HARQ-ACK information bits associated with dynamically scheduled PDSCH, SPS PDSCH release, or SCell suspension

Number

Number

[0030] <PDCCH Repetition> In NR Release 16, PDSCH transmission with multiple panels or transmission reception points (TRPs) is incorporated, and in order to increase the reliability of the PDSCH, transport blocks can be repeated over multiple TRPs.

[0031] In NR Release 17, it was proposed to improve the reliability of the PDCCH for multiple TRPs by repeating the PDCCH over different TRPs. Figure 5 shows an example where a PDCCH, both carrying the same DCI, is repeated at different times on two TRPs. The DCI can be a DL DCI or a UL DCI.

[0032] The PDCCH is 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. To perform PDCCH detection, the UE may detect the PDCCH individually in each PDCCH candidate or jointly by soft combining of the two linked PDCCH candidates.

[0033] What is needed is an improved system and method for codebook determination. Summary of the Invention

[0034] A system and method for codebook determination is provided herein. In some embodiments, a method for constructing a codebook performed by a wireless device includes: defining a first PDCCH opportunity of a plurality of PDCCH opportunities associated with a physical downlink control channel (PDCCH); identifying the first PDCCH opportunity for each detected downlink control information (DCI); and constructing a codebook based on the first PDCCH opportunity of all detected PDCCHs with a counter field in the corresponding DCI. In this way, construction of a type-2 hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook in the presence of PDCCH repetition is possible with minimal specification changes.

[0035] Certain aspects of the present disclosure and embodiments thereof may provide solutions to the above or other problems. A method is proposed for constructing a codebook in the presence of PDCCH repetition. The method includes one or more of: defining a first PDCCH opportunity of a plurality of PDCCH opportunities associated with a PDCCH; identifying the first PDCCH opportunity at a UE for each detected DCI; and constructing a codebook based on the first PDCCH opportunities of all detected PDCCHs with a counter field in the corresponding DCI. In some embodiments, the codebook includes a type 2 HARQ-ACK codebook. In some embodiments, the counter field includes a counter DAI field. [Brief description of the drawings]

[0036] The accompanying drawing figures, which are incorporated in and constitute a part of this specification, illustrate several aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.

[0037] [Figure 1] 1 shows how data scheduling in New Radio (NR) is done on a slot basis, typically with a slot of 14 symbols, where the first two symbols accommodate the Physical Downlink Control Channel (PDCCH) and the remaining accommodate the Physical Shared Data Channel, which can be either the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH); [Diagram 2] Shows the basic NR physical time-frequency resource grid, with only one resource block (RB) shown in a 14-symbol slot; [Diagram 3] An example is shown where a user equipment (UE) is configured with two serving cells and three PDCCH monitoring opportunities; [Figure 4] An example is shown in Fig. 3 when one TB is enabled for both cells; [Diagram 5]Both show an example where a PDCCH carrying the same Downlink Control Information (DCI) is repeated at different times on two Transmit / Receive Points (TRPs); [Figure 6] 1 illustrates an example of a cellular communication system in which embodiments of the present disclosure may be implemented. [Figure 7] 1 illustrates an example in which three DCIs are transmitted in two serving cells and two PDCCH monitoring occasions in accordance with some embodiments of the present disclosure; [Figure 8] 1 illustrates an example in which a Type 2 HARQ codebook is constructed based on a first PDCCH opportunity determined in accordance with some embodiments of the present disclosure; [Figure 9] 1 illustrates the resulting HARQ-ACK information bits assuming only a single codeword is configured in two serving cells according to some embodiments of the present disclosure; [Figure 10] 1 illustrates an example in which three DCIs are transmitted in two serving cells and two PDCCH monitoring occasions in accordance with some embodiments of the present disclosure; [Figure 11] 1 illustrates an example in which a Type 2 HARQ codebook is constructed based on the last PDCCH opportunity determined in accordance with some embodiments of the present disclosure; [Figure 12] 1 illustrates the resulting HARQ-ACK information bits assuming only a single codeword is configured in two serving cells according to some embodiments of the present disclosure; [Figure 13A] 1 illustrates a method for constructing a codebook executed by a wireless device according to some embodiments of the present disclosure; [Figure 13B] 1 illustrates a method for constructing a codebook executed by a wireless device according to some embodiments of the present disclosure; [Figure 14A] 1 illustrates a method for constructing a codebook executed by a base station according to some embodiments of the present disclosure; [Figure 14B]1 illustrates a method for constructing a codebook executed by a base station according to some embodiments of the present disclosure; [Figure 15] 1 is a schematic block diagram of an exemplary embodiment of a radio access node according to certain other embodiments of the present disclosure; [Figure 16] 1 is a schematic block diagram of an exemplary embodiment of a radio access node according to certain other embodiments of the present disclosure; [Figure 17] 1 is a schematic block diagram of an exemplary embodiment of a radio access node according to certain other embodiments of the present disclosure; [Figure 18] 1 is a schematic block diagram of a UE according to some embodiments of the present disclosure; [Figure 19] 1 is a schematic block diagram of a UE according to some embodiments of the present disclosure; [Figure 20] 1 illustrates an exemplary embodiment of a communication system in which embodiments of the present disclosure may be implemented; [Figure 21] 17 illustrates an example embodiment of the host computer, base station, and UE of FIG. 16 according to some embodiments of the present disclosure; [Figure 22] 21 is a flow chart illustrating an exemplary embodiment of a method implemented in a communication system such as that of FIG. 20; [Diagram 23] 21 is a flow chart illustrating an exemplary embodiment of a method implemented in a communication system such as that of FIG. 20; [Figure 24] 21 is a flow chart illustrating an exemplary embodiment of a method implemented in a communication system such as that of FIG. 20; [Diagram 25] 21 is a flow chart illustrating an exemplary embodiment of a method implemented in a communication system such as that of FIG. 20. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0038] The embodiments described below represent information that will enable those skilled in the art to practice the embodiments and illustrate the best modes of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the present disclosure and recognize applications of those concepts not specifically addressed herein. It should be understood that those concepts and applications fall within the scope of the present disclosure.

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

[0040] Radio Access Node: As used herein, a "radio access node," "radio network node," or "radio access network node" is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and / or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a 3rd Generation Partnership Project (3GPP) fifth generation (5G) NR network, or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high power or macro base station, a low power base station (e.g., a micro base station, a pico base station, or a Home eNB), a relay node, a network node implementing a portion of the functionality of a base station (e.g., a network node implementing a gNB central unit (gNB-CU) or a network node implementing a gNB distributed unit (gNB-DU)), or a network node implementing a portion of the functionality of any other type of radio access node.

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

[0042] Communications Device: As used herein, a "communications device" is any type of device that has access to an access network. Some examples of communications devices include, but are not limited to, a mobile phone, a smartphone, a sensor device, a meter, a vehicle, a home appliance, a medical appliance, a media player, a camera, or any type of consumer electronic device, such as, but not limited to, a television, a radio, a lighting device, a tablet computer, a laptop, or a personal computer (PC). A communications device may be a portable, handheld, computer-embedded, or vehicle-mounted mobile device that is enabled to communicate voice and / or data via wireless or wired connections.

[0043] [Wireless Communication Device]: Another type of communication device is a wireless communication device, which may be any type of wireless device that has access to (is served by) a wireless network (e.g., a cellular network). Some examples of wireless communication devices include, but are not limited to, user equipment devices (UE) in 3GPP networks, machine type communication (MTC) devices, and Internet of Things (IoT) devices. Such wireless communication devices may be or be integrated into mobile phones, smartphones, sensor devices, meters, vehicles, home appliances, medical appliances, media players, cameras, or any type of consumer electronics, such as, but not limited to, televisions, radios, lighting devices, tablet computers, laptops, or PCs. Wireless communication devices may be portable, handheld, computer-embedded, or vehicle-mounted mobile devices that are enabled to communicate voice and / or data over a wireless connection.

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

[0045] Transmit / Receive Point (TRP): In some embodiments, a TRP can be either a network node, a radio head, a spatial relation, or a transmission configuration indicator (TCI) state. A TRP can be represented by a spatial relation or a TCI state in some embodiments. In some embodiments, a TRP may use multiple TCI states. In some embodiments, a TRP may be part of a gNB that transmits and receives radio signals to and from a UE according to physical layer characteristics and parameters specific to that element. In some embodiments, in multiple transmit / receive point (multi-TRP) operation, a serving cell can schedule a UE from two TRPs, providing better PDSCH coverage, reliability, and / or data rate. 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, the UE is scheduled with the same DCI for both TRPs, and in multi-DCI mode, the UE is scheduled with independent DCI from each TRP.

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

[0047] It is important to note that although reference may be made to the term "cell" in this description, particularly with respect to 5G NR concepts, beams may be used instead of cells, and therefore the concepts described herein are equally applicable to both cells and beams.

[0048] FIG. 6 illustrates an example of a cellular communication system 600 in which embodiments of the present disclosure may be implemented. In the embodiment described herein, the cellular communication system 600 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC). In this example, the RAN includes base stations 602-1 and 602-2, which in 5GS include NR base stations (gNBs) and optionally Next Generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to 5GC) that control corresponding (macro) cells 604-1 and 604-2. The base stations 602-1 and 602-2 are generally referred to herein collectively as the base stations 602 and individually as the base station 602. Similarly, the (macro) cells 604-1 and 604-2 are generally referred to herein collectively as the (macro) cells 604 and individually as the (macro) cells 604. The RAN may also include a number of low power nodes 606-1 to 606-4 that control corresponding small cells 608-1 to 608-4. The low power nodes 606-1 to 606-4 may be small base stations (such as pico or femto base stations) or remote radio heads (RRHs), etc. Notably, although not shown, one or more of the small cells 608-1 to 608-4 may alternatively be provided by the base station 602. The low power nodes 606-1 to 606-4 are generally collectively referred to herein as a number of low power nodes 606, and individually referred to as a low power node 606. Similarly, the small cells 608-1 to 608-4 are generally collectively referred to herein as a number of small cells 608, and individually referred to as a small cell 608. The cellular communication system 600 also includes a core network 610, referred to as 5GC in a 5G system (5GS). The base station 602 (and optionally the low power node 606 ) is connected to a core network 610 .

[0049] Base station 602 and low power node 606 provide service to wireless communication devices 612-1 through 612-5 in corresponding cells 604 and 608. Wireless communication devices 612-1 through 612-5 are generally referred to herein collectively as wireless communication devices 612 and individually as a wireless communication device 612. In the following description, wireless communication devices 612 are often UEs, although this disclosure is not limited thereto.

[0050] Currently, certain problems exist. The problem is how to construct a type-2 hybrid automatic repeat request (HARQ) acknowledgement (ACK) codebook in the presence of physical downlink control channel (PDCCH) repetition. For example, assume an example where PDCCH#1, which schedules a PDSCH, is repeated in PDCCH monitoring occasions m=0 and m=1, and there is another PDSCH scheduled by the PDCCH in PDCCH monitoring occasion m=0, and PDCCH#1 is detected only in PDCCH monitoring occasion m=1. If the existing procedure for constructing a type-2 HARQ ACK codebook is applied (i.e., HARQ ACK bits are arranged in ascending order of serving cell index first 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 will result in an inaccurate number of HARQ ACK bits and also an inaccurate mapping between PDSCH and HARQ ACK bits. An improved system and method for codebook determination is needed.

[0051] A system and method for codebook determination is provided herein. In some embodiments, a method for constructing a codebook performed by a wireless device includes one or more of: defining a first PDCCH opportunity of a plurality of PDCCH opportunities associated with a PDCCH; identifying a first PDCCH opportunity for each detected DCI; and constructing a codebook based on the first PDCCH opportunities of all detected PDCCHs with a counter field in the corresponding DCI. In this way, construction of a type-2 HARQ ACK codebook in the presence of PDCCH repetition is possible with minimal specification changes.

[0052] In an embodiment, the counter DAI in a DCI is incremented only in the first PDCCH opportunity in case of PDCCH repetition. If the PDCCH is repeated in two PDCCH monitoring opportunities, the first PDCCH opportunity is defined as the one among the PDCCH monitoring opportunities that occurs earlier in time. Only the first PDCCH opportunity is considered for incrementing the counter DAI and the total DAI in the subsequent DCI.

[0053] The PDCCH monitoring occasions described in this disclosure can be either within one slot or within one monitoring span. Different PDCCH monitoring occasions may be within different slots / monitoring spans or may be within the same slot / monitoring span.

[0054] FIG. 7 shows an example in which three DCIs are transmitted in two serving cells and two PDCCH monitoring opportunities. Those DCIs are used to schedule three PDSCHs from PDSCH#1 to #3. The HARQ Ack associated with those PDSCHs is assumed to be transmitted in the same PUCCH or PUSCH within the uplink slot. DCI#1 is carried in PDCCH#1 and repeated in both PDCCH monitoring opportunities m = 0 and m = 1. In this case, the first PDCCH opportunity of PDCCH#1 is the one within PDCCH monitoring opportunity m = 0, and the second PDCCH opportunity of PDCCH#1 is within PDCCH monitoring opportunity m = 1. The counter DAI and the total DAI in DCI#1 are incremented at the first PDCCH opportunity within PDCCH monitoring opportunity m = 0. At the second opportunity within PDCCH monitoring opportunity m = 1, since the same DCI#1 is transmitted, the counter DAI and the total DAI are not changed. For DCI#3, its counter DAI and total DAI are incremented without considering the repetition of PDCCH#1, that is, the second opportunity of PDCCH#1 within PDCCH monitoring opportunity m = 1 is not counted.

[0055] <Type 2 HARQ Codebook Construction in the Presence of PDCCH Repetition> In an embodiment, the counter DAI in the DCI is incremented only at the first PDCCH opportunity in the case of PDCCH repetition. When the PDCCH is repeated in two PDCCH monitoring opportunities, the first PDCCH opportunity is defined as the one among the PDCCH monitoring opportunities that occur earlier in time. Only the first PDCCH opportunity is considered for incrementing the counter DAI and the total DAI in subsequent DCIs.

[0056] If a PDCCH is repeated within the same PDCCH monitoring opportunity in different PDCCH candidates of the same or different CORESET or in different SS sets, the first PDCCH opportunity may be defined as one of the following: Linked PDCCH candidates with lower (or higher) PDCCH candidate index A linked PDCCH candidate in a CORESET with a lower (or higher) CORESET ID, or Linked PDCCH candidates in the SS set with a lower (or higher) SS Set ID

[0057] At the UE side, for each detected DCI, the first associated PDCCH opportunity is determined, and the existing Type-2 HARQ codebook procedure is applied by considering only the first determined PDCCH opportunity.

[0058] Using the example shown in Figure 7, assume that DCI#1 is detected in the second PDCCH opportunity in PDCCH monitoring opportunity m=1, but not the first opportunity in PDCCH monitoring opportunity m=0. DCI#2 and DCI#3 are both detected. Based on the linking of PDCCH candidates for PDCCH repetitions, the UE can determine that the first PDCCH opportunity for DCI#1 is in PDCCH monitoring opportunity m=0. For DCI#2 and #3, since no repetitions are performed, the corresponding first opportunity is the one detected. Then, the type-2 HARQ codebook is constructed based on the first PDCCH opportunity determined as shown in Figure 8.

[0059] Assuming that only a single codeword is configured in the two serving cells, the total number of ACK = 3 HARQ-ACK information bits

number

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

[0061] ---Start of proposed changes in Section 9.1.3.1 of 38.213 v16.4.0--- 9.1.3.1 Type 2 HARQ-ACK codebook in the physical uplink control channel ---Text without changes is omitted---

Table 1

Table 2

Table 3

[0062] <Alternative embodiment for Type 2 HARQ codebook construction in the presence of PDCCH repetitions> In an alternative embodiment, the counter DAI within the DCI is incremented only at the last PDCCH opportunity in the case of PDCCH repetitions. When PDCCH is repeated at two PDCCH monitoring opportunities, the last PDCCH opportunity is defined as the one among the PDCCH monitoring opportunities that occur latest in time. Only the last PDCCH opportunity is considered for incrementing the counter DAI and the total DAI.

[0063] FIG. 10 shows an example in which three DCIs are 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 and is repeated in both PDCCH monitoring occasions m=0 and m=1. In this case, the last PDCCH opportunity of PDCCH#1 is that in PDCCH monitoring opportunity m=1, and the first PDCCH opportunity of PDCCH#1 is in PDCCH monitoring opportunity m=0. The counter DAI and total DAI in DCI#1 are incremented in the last PDCCH opportunity in PDCCH monitoring opportunity m=1. In the first opportunity in PDCCH monitoring opportunity m=0, the same DCI#1 is transmitted, so the counter DAI and total DAI are not changed. For DCI#2, its counter DAI and total DAI are incremented without considering the repetition of PDCCH#1, ie the first opportunity of PDCCH#1 within the PDCCH monitoring opportunity m=0 is not counted.

[0064] At the UE side, for each detected DCI, the associated last PDCCH opportunity is determined, and the existing Type-2 HARQ codebook procedure is applied by considering only the determined last PDCCH opportunity.

[0065] Using the example shown in Figure 10, assume that DCI#1 is detected in the first PDCCH opportunity in PDCCH monitoring opportunity m=0, but not the last opportunity in PDCCH monitoring opportunity m=1. DCI#2 and DCI#3 are both detected. Based on the linking of PDCCH candidates for PDCCH repetitions, the UE can determine that the last PDCCH opportunity for DCI#1 is in PDCCH monitoring opportunity m=1. For DCI#2 and #3, since no repetitions are performed, the corresponding last opportunities are the ones detected. Then, the type-2 HARQ codebook is constructed based on the last PDCCH opportunity determined as shown in Figure 11.

[0066] Assuming that only a single codeword is configured in the two serving cells, the total number of ACK = 3 HARQ-ACK information bits

number

[0067] The following modifications in the existing pseudocode for Type-2 HARQ-Ack codebook (highlighted in bold) may describe this embodiment:

[0068] ---Begin proposed change in section 9.1.3.1 of 38.213v16.4.0--- 9.1.3.1 Type 2 HARQ-ACK Codebook on the Physical Uplink Control Channel ---Unchanged text omitted--- [Table 4] [Table 5] [Table 6]

[0069] 13A illustrates a method for constructing a codebook performed by a wireless device, the method including one or more of: defining a first PDCCH opportunity of a plurality of PDCCH opportunities associated with a PDCCH (Step 1300A), identifying a first PDCCH opportunity for each detected DCI (Step 1302A), and constructing a codebook based on the first PDCCH opportunities of all detected PDCCHs with a counter field in the corresponding DCI (Step 1304A).

[0070] 13B illustrates a method for constructing a codebook performed by a wireless device, the method including receiving PDCCHs associated with a first set and a second set of DCI formats (step 1300B), determining, for each of the at least one PDCCH, a first PDCCH monitoring opportunity of a plurality of PDCCH monitoring opportunities (step 1302B), constructing a HARQ-ACK codebook by ordering HARQ-ACK information associated with each PDCCH according to an associated PDCCH monitoring opportunity index, where, for each of the at least one PDCCH, the associated PDCCH monitoring opportunity is the first PDCCH monitoring opportunity (step 1304B), and transmitting HARQ-ACK information in the codebook to a base station (step 1306B).

[0071] 14A illustrates a method for constructing a codebook performed by a base station, the method including one or more of: defining a first PDCCH opportunity of a plurality of PDCCH opportunities associated with a PDCCH (step 1400A), identifying a first PDCCH opportunity for each DCI (step 1402A), and incrementing a counter based on the first PDCCH opportunity for all PDCCHs with a counter field in the corresponding DCI (step 1404A).

[0072] 14B illustrates a method for constructing a codebook performed by a base station, the method including determining a first PDCCH monitoring opportunity of a plurality of PDCCH monitoring opportunities (step 1400B), incrementing a counter at the first PDCCH monitoring opportunity and pointing a value of the counter in a counter field in a DCI (step 1402B), transmitting the DCI on a PDCCH in a plurality of PDCCH candidates to a wireless device (step 1404B), and receiving HARQ-ACK information associated with the PDCCH from the wireless device (step 1406B).

[0073] FIG. 15 is a schematic block diagram of a radio access node 1500 according to some other embodiments of the present disclosure. Optional features are represented by dashed boxes. The radio access node 1500 may be, for example, a base station 602 or 606, or a network node implementing all or part of the functionality of the base station 602 or gNB described herein. As shown, the radio access node 1500 includes a control system 1502 including one or more processors 1504 (e.g., a central processing unit (CPU), an application specific integrated circuit (ASIC), and / or a field programmable gate array (FPGA)), a memory 1506, and a network interface 1508. The one or more processors 1504 are also referred to herein as processing circuits. In addition, the radio access node 1500 may include one or more radio units 1510 each including one or more transmitters 1512 and one or more receivers 1514, which are coupled to one or more antennas 1516. The radio unit 1510 may be referred to as, or may be part of, a radio interface circuit. In some embodiments, the radio unit 1510 is external to the control system 1502 and is connected to the control system 1502, for example, via a wired connection (e.g., an optical cable). However, in some embodiments, the radio unit 1510 and potentially the antenna 1516 are integrated with the control system 1502. The one or more processors 1504 operate to provide one or more functions of the radio access node 1500 as described herein. In some embodiments, the functions are implemented in software that is stored, for example, in the memory 1506 and executed by the one or more processors 1504.

[0074] 16 is a schematic block diagram illustrating a virtualized embodiment of a radio access node 1500 according to some embodiments of the present disclosure. The discussion is equally applicable to other types of network nodes. Furthermore, other types of network nodes may have similar virtualized architectures. Again, optional features are represented by dashed boxes.

[0075] As used herein, a "virtualized" radio access node is an implementation of the radio access node 1500 in which at least a portion of the functionality of the radio access node 1500 is implemented as a virtual component (e.g., via a virtual machine running on a physical processing node in a network). As shown, in this example, the radio access node 1500 may include a control system 1502 and / or one or more radio units 1510 as described above. The control system 1502 may be connected to the radio units 1510, for example, via an optical cable. The radio access node 1500 includes one or more processing nodes 1600 coupled to or included as part of a network 1602. If present, the control system 1502 or the radio units are connected to the processing nodes 1600 via the network 1602. Each processing node 1600 includes one or more processors 1604 (e.g., CPUs, ASICs, and / or FPGAs), memory 1606, and a network interface 1608.

[0076] In this example, the radio access node 1500 functions 1610 described herein may be implemented in one or more processing nodes 1600 or distributed across one or more processing nodes 1600, control system 1502, and / or radio unit 1510 in any desired manner. In some specific embodiments, some or all of the radio access node 1500 functions 1610 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment hosted by the processing node 1600. As will be appreciated by those skilled in the art, additional signaling or communication between the processing node 1600 and the control system 1502 may be used to perform at least some of the desired functions 1610. Notably, some embodiments may not include a control system 1502, in which case the radio unit 1510 communicates directly with the processing node 1600 via an appropriate network interface.

[0077] In some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform functionality of the radio access node 1500 or a node (e.g., processing node 1600) implementing one or more of the functions 1610 of the radio access node 1500 in a virtual environment in accordance with any of the embodiments described herein. In some embodiments, a carrier is provided that includes the computer program product as described above. 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 a memory).

[0078] 17 is a schematic block diagram of a radio access node 1500 according to some other embodiments of the present disclosure. The radio access node 1500 includes one or more modules 1700, each of which is implemented in software. The modules 1700 provide the functionality of the radio access node 1500 described herein. This discussion is equally applicable to the processing nodes of FIG. 16, and the modules 1700 may be implemented in one of the processing nodes 1600, distributed across multiple processing nodes 1600, and / or distributed across the processing nodes 1600 and the control system 1502.

[0079] 18 is a schematic block diagram of a wireless communication device 1800 according to some other embodiments of the present disclosure. As shown, the wireless communication device 1800 includes one or more processors 1802 (e.g., a CPU, an ASIC, and / or an FPGA, etc.), a memory 1804, and one or more transceivers 1806 each including one or more transmitters 1808 and one or more receivers 1810 coupled to one or more antennas 1812. The transceiver 1806 includes radio front-end circuitry connected to the antenna 1812 configured to condition signals exchanged between the antenna 1812 and the processor 1802, as would be understood by one of ordinary skill in the art. The processor 1802 is also referred to herein as a processing circuit. The transceiver 1806 is also referred to herein as a radio circuit. In some embodiments, the above-described functionality of the wireless communication device 1800 may be implemented, fully or partially, in software stored, for example, in the memory 1804 and executed by the processor 1802. It should be noted that wireless communication device 1800 may include additional components not shown in FIG. 18 , such as, for example, one or more user interface components (e.g., a display, buttons, a touch screen, a microphone, and / or a speaker, and / or any other components for enabling input of information into and / or output of information from wireless communication device 1800) and a power source (e.g., a battery and associated power circuitry).

[0080] In some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform the functionality of the wireless communication device 1800 in accordance with any of the embodiments described herein. In some embodiments, a carrier is provided that includes the computer program product as described above. 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 a memory).

[0081] 19 is a schematic block diagram of a wireless communication device 1800 according to some other embodiments of the present disclosure. The wireless communication device 1800 includes one or more modules 1900, each of which is implemented in software. The modules 1900 provide the functionality of the wireless communication device 1800 described herein.

[0082] Referring to Fig. 20, according to one embodiment, a communication system includes a telecommunications network 2000, such as a 3GPP type cellular network, including an access network 2002, such as a RAN, and a core network 2004. The access network 2002 includes a number of base stations 2006A, 2006B, 2006C, such as Node B, eNB, gNG, or other types of wireless access points (AP), each of which defines a corresponding coverage area 2008A, 2008B, 2008C. Each base station 2006A, 2006B, 2006C is connectable to the core network 2004 over a wired or wireless connection 2010. A first UE 2012 located in the coverage area 2008C is configured to be wirelessly connected to or paged by the corresponding base station 2006C. A second UE 2014 within the coverage area 2008A can wirelessly connect to the corresponding base station 2006A. Although multiple UEs 2012, 2014 are shown in this example, the disclosed embodiments are equally applicable to situations where there is a single UE within the coverage area or a single UE connecting to the corresponding base station 2006.

[0083] The telecommunications network 2000 is itself connected to a host computer 2016, which may be embodied in standalone server hardware and / or software, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 2016 may be owned or controlled by a service provider, or may be operated by or for the service provider. The connections 2018 and 2020 between the telecommunications network 2000 and the host computer 2016 may extend directly from the core network 2004 to the host computer 2016, or may be connected via an optional intermediate network 2022. The intermediate network 2022 may be one or a combination of a public, private, or hosted network, and the intermediate network 2022 may be a backbone network or the Internet, if any, and in particular the intermediate network 2022 may include two or more sub-networks (not shown).

[0084] The communication system of FIG. 20 generally enables connectivity between connected UEs 2012, 2014 and a host computer 2016. The connectivity may be described as an over-the-top (OTT) connection 2024. The host computer 2016 and connected UEs 2012, 2014 are configured to communicate data and / or signaling via the OTT connection 2024 using the access network 2002, the core network 2004, any intermediate networks 2022, and possible further infrastructure (not shown) as intermediate steps. The OTT connection 2024 may be transparent in the sense that participating communication devices en route through the OTT connection 2024 are unaware of the routing of uplink and downlink communications. For example, the base station 2006 may not be informed or need to be informed of the past routing of incoming downlink communications with data originating from the host computer 2016 to be forwarded (e.g., handed over) to the connected UE 2012. Similarly, the base station 2006 does not need to be aware of the future routing of outgoing uplink communications originating from the UE 2012 to the host computer 2016 .

[0085] An exemplary implementation according to one embodiment of the UE, base station and host computer discussed in the previous paragraph will now be described with reference to FIG. 21. In the communication system 2100, the host computer 2102 comprises hardware 2104 including a communication interface 2106 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 2100. The host computer 2102 further comprises a processing circuit 2108 that may have storage and / or processing capabilities. Among other things, the processing circuit 2108 may include one or more programmable processors, ASICs, FPGAs or combinations thereof (not shown) adapted to execute instructions. The host computer 2102 further comprises software 2110 stored in or accessible by the host computer 2102 and executable by the processing circuit 2108. The software 2110 includes a host application 2112. The host application 2112 may be operable to provide services to a remote user, such as a UE 2114, connecting via an OTT connection 2116 that terminates at the UE 2114 and the host computer 2102. During the provision of services to the remote user, the host application 2112 may provide user data that is transmitted using the OTT connection 2116.

[0086] The communication system 2100 further includes a base station 2118 provided in the telecommunications system, the base station 2118 comprising hardware 2120 enabling communication with the host computer 2102 and the UE 2114. The hardware 2120 may include a communication interface 2122 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 2100, as well as a wireless interface 2124 for setting up and maintaining at least a wireless connection 2126 with a UE 2114 located within a coverage area (not shown in FIG. 21) served by the base station 2118. The communication interface 2122 may be configured to facilitate a connection 2128 to the host computer 2102. The connection 2128 may be direct or may pass through a core network (not shown in FIG. 21) of the telecommunications system and / or one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 2120 of the base station 2118 further includes processing circuitry 2130, which may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. The base station 2118 further includes software 2132 stored internally or accessible via an external connection.

[0087] The communication system 2100 further includes the UE 2114 already mentioned. The hardware 2134 of the UE 2114 may include a radio interface 2136 configured to set up and maintain a radio connection 2126 with a base station serving the coverage area in which the UE 2114 is currently located. The hardware 2134 of the UE 2114 further includes a processing circuit 2138 adapted to execute instructions, which may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown). The UE 2114 further includes software 2140 stored within or accessible by the UE 2114, the software 2140 being executable by the processing circuit 2138. The software 2140 includes a client application 2142. The client application 2142, with the support of the host computer 2102, may be operable to provide services via the UE 2114 to a human or non-human user. At the host computer 2102, an executing host application 2112 may communicate with an executing client application 2142 via an OTT connection 2116 that terminates at the UE 2114 and the host computer 2102. During the provision of a service to a user, the client application 2142 may receive request data from the host application 2112 and provide user data in response to the request data. The OTT connection 2116 may transport both the request data and the user data. The client application 2142 may interact with the user to generate the user data that it provides.

[0088] It should be noted that the host computer 2102, base station 2118, and UE 2114 shown in Fig. 21 may be similar to or identical to the host computer 2016, one of the base stations 2006A, 2006B, and 2006C, and one of the UEs 2012 and 2014 shown in Fig. 20, respectively. That is to say, the internal workings of these entities may be as shown in Fig. 21, and independently, the surrounding network topology may be that of Fig. 20.

[0089] 21, the OTT connection 2116 is depicted abstractly to illustrate communication between the host computer 2102 and the UE 2114 through the base station 2118 without explicit reference to any intermediate devices and the exact routing of messages through those devices. The routing may be determined by the network infrastructure, which may be configured to hide the routing from the UE 2114 or the service provider operating the host computer 2102, or both. While the OTT connection 2116 is active, the network infrastructure may further make decisions to dynamically change the routing (e.g., based on load balancing considerations or network reconfiguration).

[0090] The wireless connection 2126 between the UE 2114 and the base station 2118 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT services provided to the UE 2114 using the OTT connection 2116, of which the wireless connection 2126 forms the final segment. More precisely, the teachings of the embodiments may improve data rates, latency, power consumption, etc., thereby providing benefits such as reduced user latency, relaxed limitations on file sizes, better responsiveness, increased battery life, etc.

[0091] A measurement procedure may be provided to monitor data rates, latency, and other factors that are improved by one or more embodiments. There may also be optional network functionality to reconfigure the OTT connection 2116 between the host computer 2102 and the UE 2114 in response to measurement variations. The measurement procedure and / or the network functionality to reconfigure the OTT connection 2116 may be implemented in the software 2110 and hardware 2104 of the host computer 2102, or in the software 2140 and hardware 2134 of the UE 2114, or both. In some embodiments, sensors (not shown) may be deployed in or associated with the communication device through which the OTT connection 2116 passes, and these sensors may participate in the measurement procedure by providing values ​​of the monitored quantities exemplified above or other physical quantities from which the monitored quantities may be calculated or estimated by the software 2110, 2140. Reconfiguration of the OTT connection 2116 may include message formats, retransmission settings, preferred routing, etc., which may not affect the base station 2118 and may be unknown or imperceptible to the base station 2118. Such procedures and functionality may be known or practiced in the art. In one embodiment, the measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation time, latency, etc. by the host computer 2102. The measurements may be implemented by the software 2110 and 2140 sending messages, specifically empty or "dummy" messages, over the OTT connection 2116 while monitoring propagation times, errors, etc.

[0092] FIG. 22 is a flow chart 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 as described with reference to FIG. 20 and FIG. 21. To simplify the disclosure, only reference to the diagram of FIG. 22 will be included in this section. In step 2200, the host computer provides user data. In sub-step 2202 of step 2200 (which may be optional), the host computer provides the user data by executing a host application. In step 2204, the host computer initiates a transmission to the UE carrying the user data. In step 2206 (which may be optional), the base station transmits the user data carried in the host computer initiated transmission to the UE according to the teachings of the embodiments described throughout this disclosure. In step 2208 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0093] FIG. 23 is a flow chart 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 as described with reference to FIG. 20 and FIG. 21. To simplify the disclosure, only reference to the diagram of FIG. 23 will be included in this section. In step 2300 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 2302, the host computer initiates a transmission to the UE carrying the user data. The transmission may go through the base station according to the teachings of the embodiments described throughout this disclosure. In step 2304 (which may be optional), the UE receives the user data carried in the transmission.

[0094] FIG. 24 is a flow chart 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 as described with reference to FIG. 20 and FIG. 21. To simplify the disclosure, only reference to the diagram of FIG. 24 will be included in this section. In step 2400 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2402, the UE provides user data. In sub-step 2404 (which may be optional) of step 2400, the UE provides the user data by executing a client application. In sub-step 2406 (which may be optional) of step 2402, the UE executes a client application that provides the user data in reaction to receiving the input data provided by the host computer. During the provision of the user data, the executed client application may further take into account user input received from a user. Regardless of the specific manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in sub-step 2408 (which may be optional). In step 2410 of the method, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

[0095] FIG. 25 is a flow chart 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 as described with reference to FIG. 20 and FIG. 21. To simplify the disclosure, only reference to the diagram of FIG. 25 will be included in this section. In step 2500 (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 2502 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 2504 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0096] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. The functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, and other digital hardware, which may include digital signal processors (DSPs) and special purpose digital logic. 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, and the like. The program code stored in memory includes program instructions for implementing one or more telecommunications and / or data communication protocols, and instructions for performing one or more of the techniques described herein. In some embodiments, the processing circuitry may be used to cause the respective functional units to perform functions corresponding to the respective functional units in accordance with one or more embodiments of the present disclosure.

[0097] Although the processes in the figures may indicate a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such orders are exemplary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, overlap certain operations, etc.).

[0098] <Embodiment> Group A Embodiments Embodiment 1: A method for constructing a codebook, performed by a wireless device, the method including one or more of: defining a first PDCCH opportunity of a plurality of PDCCH opportunities associated with a PDCCH (1300); identifying the first PDCCH opportunity for each detected DCI (1302); and constructing a codebook based on the first PDCCH opportunities of all detected PDCCHs with a counter field in a corresponding DCI (1304).

[0099]

[0023] Embodiment 2: The method of embodiment 1, wherein the codebook includes a Type 2 HARQ-ACK codebook.

[0100] Embodiment 3: The method of any one of embodiments 1 to 2, wherein the counter field includes a counter Downlink Allocation Indicator (DAI) field.

[0101] Embodiment 4: The method of any one of embodiments 1 to 2, wherein the wireless device includes a user equipment (UE).

[0102] Embodiment 5: The method of any one of embodiments 1 to 4, further comprising receiving, from the network node, a plurality of search space sets and PDCCH repetitions in a subset of the search space sets.

[0103] Embodiment 6: The method of any one of embodiments 1 to 5, further comprising monitoring the first PDCCH and the second PDCCH, and decoding a corresponding PDSCH if detected.

[0104] Embodiment 7: The method of any one of embodiments 1 to 6, further comprising: determining a first PDCCH opportunity for the first PDCCH if it is detected.

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

[0106] Embodiment 9: A method according to any one of embodiments 1 to 8, wherein receiving the PDCCH repetitions in the plurality of search space sets and subsets of the search space sets includes receiving a plurality of linked PDCCH candidates in the same or different plurality of search space sets in which the PDCCH may be repeated.

[0107] Embodiment 10: The method of any one of embodiments 1 to 9, wherein the first PDCCH monitoring opportunity corresponds to a linked PDCCH candidate that occurs first in time.

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

[0109] Embodiment 12: A method according to any one of embodiments 1 to 11, wherein the value of the counter field in the DCI carried in a PDCCH that is repeated in multiple PDCCH opportunities is determined based on the first PDCCH opportunity in the case of PDCCH repetition.

[0110] Embodiment 13: A method according to any one of embodiments 1 to 12, wherein constructing a type 2 HARQ-ACK codebook based on the first PDCCH opportunity includes allocating a HARQ ACK bit to the first PDSCH scheduled by the first PDCCH transmitted in the first PDCCH opportunity.

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

[0112] Group B Embodiments Embodiment 15: A method for updating a counter, performed by a base station, the method comprising one or more of: defining a first PDCCH opportunity of a plurality of PDCCH opportunities associated with a DCI (1400); identifying the first PDCCH opportunity (1402); and incrementing the counter at the first PDCCH opportunity and pointing to a value of the counter in a counter field in the DCI (1404).

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

[0114] Embodiment 17: The method of any of embodiments 15 or 16, wherein the counter field includes a counter downlink assignment indicator (DAI) field.

[0115] Embodiment 18: The method of any one of embodiments 15 to 17, wherein the base station includes a gNB.

[0116]

[0046] Embodiment 19: The method of any one of embodiments 15 to 18, further comprising: configuring the wireless device with a plurality of search space sets and PDCCH repetitions in a subset of the search space sets.

[0117] Embodiment 20: The method of any one of embodiments 15 to 19, further comprising: scheduling the first PDSCH on a first PDCCH that is repeated on multiple PDCCH opportunities, and the second PDSCH on a second PDCCH without repetition.

[0118] Embodiment 21: The method of any one of embodiments 15 to 20, further comprising: determining a first PDCCH opportunity for the first PDCCH.

[0119] Embodiment 22: The method of embodiment 1, wherein incrementing the counter includes adding one to the counter.

[0120] Embodiment 23: A method according to any one of embodiments 15 to 22, wherein configuring the wireless device with the plurality of search space sets and PDCCH repetitions in a subset of the search space sets includes configuring the wireless device with a plurality of linked PDCCH candidates in the same or different search space sets in which the PDCCH may be repeated.

[0121]

[0046] Embodiment 24: The method of any one of embodiments 15 to 23, wherein the first PDCCH opportunity corresponds to a linked PDCCH candidate that occurs first in time.

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

[0123] Embodiment 26: A method according to any one of embodiments 15 to 25, wherein the value of the counter field in the DCI carried in a PDCCH that is repeated in multiple PDCCH opportunities is determined based on the first PDCCH opportunity in the case of PDCCH repetition.

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

[0125] Group C Embodiments Embodiment 29: A wireless device for constructing a codebook, comprising: a processing circuit configured to perform any of the steps of any of the embodiments of Group A; and a power supply circuit configured to supply power to the wireless device.

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

[0127] Embodiment 31: A user equipment (UE) for building a codebook, comprising: an antenna configured to transmit and receive wireless signals; a radio front-end circuit connected to the antenna and a processing circuit and configured to condition signals communicated between the antenna and the processing circuit; the processing circuit configured to perform any of the steps of any of the embodiments of Group A; an input interface connected to the processing circuit and configured to enable input of information to the UE to be processed by the processing circuit; an output interface connected to the processing circuit and configured to output information processed by the processing circuit from the UE; and a battery connected to the processing circuit and configured to supply power to the UE.

[0128] Embodiment 32: A communications system including a host computer, the host computer comprising a processing circuit configured to provide user data and a communications interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), the cellular network including a base station, the base station comprising a radio interface and a processing circuit, the processing circuit of the base station configured to perform any of the steps of any of the embodiments of Group B.

[0129] Embodiment 33: The communication system of any of the preceding embodiments, further comprising the base station.

[0130] Embodiment 34: The communication system of the two preceding embodiments, further comprising the UE, the UE configured to communicate with the base station.

[0131] Embodiment 35: A communication system according to any of the three preceding embodiments, wherein the processing circuitry of the host computer is configured to provide the user data by executing a host application, and the UE comprises processing circuitry configured to execute a client application associated with the host application.

[0132] Embodiment 36: A method implemented in a communications system including a host computer, a base station and a user equipment (UE), comprising: providing user data at the host computer; and initiating a transmission at the host computer conveying the user data to the UE via a cellular network including the base station, wherein the base station performs any of the steps of any of the Group B embodiments.

[0133] Embodiment 37: The method of any preceding embodiment, further comprising, at the base station, transmitting the user data.

[0134] Embodiment 38: The method of the two preceding embodiments, wherein the user data is provided by executing a host application on the host computer, and the method further includes executing, on the UE, a client application associated with the host application.

[0135] Embodiment 39: A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and a processing circuit configured to perform the methods of the three preceding embodiments.

[0136] Embodiment 40: A communications system including a host computer, the host computer comprising a processing circuit configured to provide user data and a communications interface configured to transfer the user data to a cellular network for transmission to a user equipment (UE), the UE comprising a wireless interface and a processing circuit, the components of the UE being configured to perform any of the steps of any of the embodiments of Group A.

[0137] Embodiment 41: The communication system of any of the preceding embodiments, wherein the cellular network further includes a base station configured to communicate with the UE.

[0138] Embodiment 42: A communication system according to the two preceding embodiments, wherein the processing circuitry of the host computer is configured to provide the user data by executing a host application, and the processing circuitry of the UE is configured to execute a client application associated with the host application.

[0139] Embodiment 43: A method implemented in a communications system including a host computer, a base station and a user equipment (UE), comprising: providing user data at the host computer; and initiating a transmission at the host computer conveying the user data to the UE via a cellular network including the base station, wherein the UE performs any of the steps of any of the embodiments of Group A.

[0140] Embodiment 44: The method of any preceding embodiment, further comprising: receiving, at the UE, the user data from the base station.

[0141] Embodiment 45: A communications system including a host computer having a communications interface configured to accept user data derived from a transmission signal from a user equipment (UE) to a base station, the UE having a radio interface and processing circuitry, the processing circuitry of the UE being configured to perform any of the steps of any of the embodiments of Group A.

[0142] Embodiment 46: The communication system of any of the preceding embodiments, further comprising the UE.

[0143] Embodiment 47: A communication system according to the two preceding embodiments, further comprising the base station, the base station comprising a radio interface configured to communicate with the UE, and a communication interface configured to transfer the user data carried by a transmission from the UE to the base station to the host computer.

[0144] Embodiment 48: A communication system according to any of the three preceding embodiments, wherein the processing circuitry of the host computer is configured to execute a host application, and the processing circuitry of the UE is configured to provide the user data by executing a client application associated with the host application.

[0145] Embodiment 49: A communication system according to any of the four preceding embodiments, wherein the processing circuitry of the host computer is configured to provide request data by executing a host application, and the processing circuitry of the UE is configured to provide the user data in response to the request data by executing a client application associated with the host application.

[0146] Embodiment 50: A method implemented in a communications system including a host computer, a base station and a user equipment (UE), comprising receiving, at the host computer, user data transmitted from the UE to the base station, wherein the UE performs any of the steps of any of the embodiments of Group A.

[0147] Embodiment 51: The method of any preceding embodiment, further comprising, at the UE, providing the user data to the base station.

[0148] Embodiment 52: The method of the two preceding embodiments, further comprising: providing the user data to be transmitted by executing a client application in the UE; and executing a host application in the host computer that is associated with the client application.

[0149] Embodiment 53: The method of any of the three preceding embodiments, further comprising: executing, in the UE, a client application; and receiving, in the UE, input data to the client application provided by executing, in the host computer, 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.

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

[0151] Embodiment 55: The communication system of any of the preceding embodiments, further comprising the base station.

[0152] Embodiment 56: The communication system of the two preceding embodiments, further comprising the UE, the UE configured to communicate with the base station.

[0153] Embodiment 57: A communication system according to any of the three preceding embodiments, wherein the processing circuitry of the host computer is configured to execute a host application, and the UE is configured to provide the user data to be received by the host computer by executing a client application associated with the host application.

[0154] Embodiment 58: A method implemented in a communications system including a host computer, a base station and a user equipment (UE), comprising receiving, at the host computer, user data from the base station originating from a transmission signal received by the base station from the UE, the UE performing any of the steps of any of the embodiments of Group A.

[0155] Embodiment 59: The method of any preceding embodiment, further comprising: receiving, at the base station, the user data from the UE.

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

[0157] Some embodiments of the present disclosure could be implemented using one or more of the following suggestions.

[0158] Proposal 1: Confirm the working assumptions for the non-SFN scheme and PDCCH reliability improvement with Option 2+Case 1, i.e., support Option 3 (two SS sets are associated with the corresponding CORESET).

[0159] Proposal 2: When PDCCH repetition is enabled for a UE, by default two PDCCH candidates are linked. It is for future study (FFS) whether it can be configured to link more than two.

[0160] Proposal 3: If a PDCCH consists of two linked PDCCH candidates, then two blind decodes per PDCCH pair are counted towards the BD limit for the UE.

[0161] Proposal 4: Support option 2 and use either the linked PDCCH candidate in the CORESET with the smallest controlResourceSetId or the SS set with the smallest searchSpaceId in the linked SS set.

[0162] Proposal 5: Define the PDCCH symbol that occurs last in time in a pair of linked PDCCH candidates as the last symbol regardless of which PDCCH candidate the UE actually detects.

[0163] Proposal 6: Increment the DAI counter DAI only at the first PDCCH transmission in a linked pair of PDCCH candidates (ie, the first PDCCH opportunity).

[0164] Proposal 7: The existing procedure for constructing the Type 2 HARQ-ACK codebook is applied only for the first PDCCH opportunity in the case of PDCCH repetition, regardless of whether the PDCCH is actually detected in the first or / and second PDCCH opportunity.

[0165] Proposal 8: If a CORESET is not configured as unavailable for PDSCH and a PDSCH scheduled by a PDCCH pair overlaps with resources in the CORESET that contains that PDCCH, perform PDSCH rate matching around the set of linked PDCCH candidates and corresponding DM-RSs.

[0166] Proposal 9: Multi-TRP based PDCCH extension to also support DCI format 2-2 / 2-3.

[0167] Proposal 10: Use one of the two activated TCI states as the default TCI state. Whether to standardize or indicate in the MAC CE which TCI state to activate is for future study.

[0168] Proposal 11: Consider finalizing PDCCH extension with intra-slot PDCCH repetition first.

[0169] Proposal 12: For codebook / non-codebook based multi-TRP PUSCH, support two separate SRI fields in the DCI, with the first SRI field pointing to the SRI corresponding to the first TRP and the second SRI field pointing to the SRI corresponding to the second TRP.

[0170] Proposal 13: For codebook-based multi-TRP PUSCH, two separate TPMI fields are supported in the 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, and the number of layers indicated in the first TPMI field and the second TPMI field are the same.

[0171] Proposal 14: Support option 3 of adding a second TPC field to DCI formats 0_1 / 0_2 for per-TRP closed-loop power control for PUSCH.

[0172] Proposal 15: Dynamic switching between PUSCH transmission for a single TRP and multi-TRP, i.e., each PUSCH transmission is intended for reception on one TRP or on two TRPs, should be supported.

[0173] Proposal 16: Support two SRI / TPMI fields for PUSCH repetition for m-TRP.

[0174] Proposal 17: To dynamically indicate PUSCH transmission for a single TRP or multiple TRPs, each SRI / TPMI field carries a codepoint that indicates whether the SRI / TPMI field is disabled or not.

[0175] Proposal 18: Support option 1 for CG PUSCH transmission for multiple TRPs.

[0176] Proposal 19: For PUSCH repetition type B, reuse the same RV mapping method as PUSCH repetition type A.

[0177] Proposal 20: Consider allowing back-to-back scheduling of PUSCH repetitions via multiple DCIs across multiple TRPs in NR Release 17.

[0178] Proposal 21: To improve the reliability of A-CSI, support A-CSI multiplexing on at least two PUSCH opportunities for different TRPs in NR Release 17.

[0179] Proposal 22: Do not support intra-slot beam hopping (method 2) in NR Release 17.

[0180] Proposal 23: Support multi-TRP intra-slot repetition (method 3) in NR Release 17.

[0181] Proposal 24: Support both short and long PUCCH formats for intra-slot repetition.

[0182] Proposal 25: For per-TRP closed loop power control for PUCCH, in NR Release 17, support either option 3 (two TPC fields in DCI1_1 / 1_2) or option 4 (one codepoint in the TPC field indicating two TPC values).

[0183] At least some of the following abbreviations may be used in this disclosure. In the event of a conflict among the abbreviations, the way it is used above shall prevail. If listed multiple times below, the first listing shall prevail over any subsequent listings. 3GPP Third Generation Partnership Project ·5G fifth generation 5GC Fifth generation core 5GS Fifth Generation System ACK Acknowledgement AF application function AMF Access and Mobility Functions AN Access network AP Access point ASIC Application Specific Integrated Circuit -AUSF authentication server function ·BWP Bandwidth Part ·CCE Control Channel Element ·CG Composition Grant · CORESET Control resource set ·CP-OFDM Cyclic Prefix Orthogonal Frequency Division Multiplexing CPU Central Processing Unit ·CSI Channel State Information ·CSI-RS Channel State Information Reference Signal ·CSS Common Search Space ·DAI Downlink Allocation Index DCI Downlink Control Information ·DFT Discrete Fourier Transform DL Downlink DMRS demodulation reference signal ·DN Data Network DSP Digital Signal Processor eNB Enhanced or evolved Node B ·FPGA Field Programmable Gate Array ·gNB New wireless base station ·gNB-DU New Wireless Base Station Distributed Unit -HARQ Hybrid Automatic Repeat Request ·HSS Home Subscriber Server ·IoT Internet of Things IP Internet Protocol ·LTE Long Term Evolution MME Mobility Management Entity MTC Machine Type Communication ·NACK Negative Acknowledgement NEF network exposure function NF network function ·NR New Radio · NRF Network Function Repository Function -NSSF network slice selection function OFDM Orthogonal Frequency Division Multiplexing OTT (Over the Top) PC Personal computer ·PCF policy control function PDCCH Physical Downlink Control Channel PDSCH Physical Downlink Shared Channel ·P-GW Packet Data Network Gateway PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel ·QCL Quasi-Collocated QoS Quality of Service RAM Random Access Memory RAN Radio Access Network RB Resource Block RE Resource Element ·REG Resource Element Group ROM Read-only memory RRH Remote Radio Head RS Reference Signal RTT Round Trip Time SCEF Service Capability Exposure Function -SMF session management function ·SPS Semi-Persistent Schedule · SR Scheduling Request ·SRS Sounding Reference Signal ·SS Search Space ·SSB sync signal block TCI Transmit Configuration Indicator ·UDM Unified Data Management UE User Equipment UPF user plane function USS UE specific search space

[0184] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure, and all such improvements and modifications are deemed to be within the scope of the concepts disclosed herein.

Claims

1. 1. A method performed by a wireless device served by a base station for constructing a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) codebook including at least one of a set of Physical Downlink Shared Channel (PDSCH) repetitions scheduled by a first set of Downlink Control Information (DCI) formats and HARQ-ACK information associated with a second set of DCI formats without scheduling of PDSCH repetitions, the HARQ-ACK information being to be transmitted by the wireless device in a same uplink slot, each of the DCI formats being carried by a Physical Downlink Control Channel (PDCCH), and at least one PDCCH being repeated in a plurality of PDCCH candidates in a plurality of PDCCH monitoring occasions each having an index, the method comprising: receiving a PDCCH associated with the first and second sets of DCI formats (1300B); determining, for each of the at least one PDCCH, a first PDCCH monitoring opportunity of the plurality of PDCCH monitoring opportunities, the first PDCCH monitoring opportunity occurring first in time (1302B); constructing the HARQ-ACK codebook by ordering the HARQ-ACK information associated with each PDCCH according to an index of the associated PDCCH monitoring opportunity (1304B), where for each of the at least one PDCCH, the associated PDCCH monitoring opportunity is the first PDCCH monitoring opportunity; transmitting the HARQ-ACK information to the base station in the codebook (1306B); The method includes:

2. 2. The method of claim 1, wherein the multiple PDCCH monitoring occasions are within the same time slot or the same PDCCH monitoring span.

3. 2. The method of claim 1, wherein the HARQ-ACK codebook comprises a type-2 HARQ-ACK codebook.

4. 4. The method of claim 1, wherein each of the first and second sets of DCI formats includes a counter downlink allocation index (DAI) field that contains a cumulative number of DCI formats that exist up to the associated PDCCH monitoring occasion, and for a DCI associated to a PDCCH that is repeated in multiple PDCCH monitoring occasions, the associated PDCCH monitoring occasion corresponds to the first PDCCH monitoring occasion.

5. The method of any one of claims 1 to 4, wherein the wireless device comprises a user equipment (UE).

6. The method according to any one of claims 1 to 5, further comprising:

23. A method comprising: receiving, from a network node, a configuration of a plurality of search space sets and PDCCH repetitions in a subset of the search space sets.

7. 7. The method of claim 6, wherein the configuring of PDCCH repetitions comprises configuring a plurality of linked PDCCH candidates in the subset of the search space set.

8. The method of any one of claims 1 to 7, wherein the wireless device operates in a New Radio (NR) network.

9. 1. A method for updating a counter in a downlink control information (DCI) format carried by a physical downlink control channel (PDCCH) performed by a base station serving a wireless device, the PDCCH being repeated in a plurality of PDCCH candidates in a plurality of PDCCH monitoring occasions, the method comprising: determining a first PDCCH monitoring opportunity of the plurality of PDCCH monitoring opportunities, the first PDCCH monitoring opportunity occurring in time (1400B); incrementing the counter at the first PDCCH monitoring occasion and indicating a value of the counter in a counter field in the DCI format (1402B); transmitting, on the PDCCH in the plurality of PDCCH candidates, a DCI in the DCI format to the wireless device (1404B); receiving HARQ-ACK information associated with the PDCCH from the wireless device (1406B); The method includes:

10. 10. The method of claim 9, wherein the DCI schedules one or more of a physical downlink shared channel (PDSCH), an indication of release of a semi-persistently scheduled (SPS) PDSCH, and an indication of Scell ​​dormancy.

11. 11. The method of claim 9, wherein the counter field includes a counter Downlink Allocation Index (DAI) field that contains a cumulative number of DCI formats that exist up to the PDCCH monitoring occasion associated with the DCI, and for a DCI associated with a PDCCH that is repeated in multiple PDCCH monitoring occasions, the associated PDCCH monitoring occasion is the first PDCCH monitoring occasion.

12. The method according to any one of claims 9 to 11, wherein the base station includes a gNB.

13. The method according to any one of claims 9 to 12, further comprising: configuring the wireless device with a plurality of search space sets and PDCCH repetitions in a subset of the search space sets.

14. The method of any one of claims 9 to 13, wherein incrementing the counter comprises adding one to the counter.

15. 14. The method of claim 13, wherein configuring the wireless device with the plurality of search space sets and PDCCH repetitions in a subset of the search space sets comprises: configuring the wireless device with multiple linked PDCCH candidates in the same or different search space sets in which a PDCCH may be repeated.

16. A wireless device (1800), One or more transmitters (1808); One or more receivers (1810); a processing circuit (1802) associated with the one or more transmitters (1808) and the one or more receivers (1810), the processing circuit (1802) providing to the wireless device (1800): receiving at least one physical downlink control channel (PDCCH) each repeated in a plurality of PDCCH monitoring occasions; receiving one or more PDCCHs each transmitted at a monitoring occasion; determining a first PDCCH monitoring opportunity of the plurality of PDCCH monitoring opportunities associated with each of the at least one PDCCH, the first PDCCH monitoring opportunity being a PDCCH monitoring opportunity that occurs first in time; constructing a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) codebook by ordering HARQ-ACK information associated with each PDCCH according to an index of the associated PDCCH monitoring opportunity, where for each of the at least one PDCCH, the associated PDCCH monitoring opportunity is the first PDCCH monitoring opportunity; A wireless device (1800) configured to cause

17. A wireless device (1800) according to claim 16, said wireless device (1800) being further adapted to perform the method according to any one of claims 2 to 8.

18. A radio access node (1500), One or more transmitters (1512); One or more receivers (1514); and a processing circuit (1504) associated with the one or more transmitters (1512) and the one or more receivers (1514), the processing circuit (1504) providing to the radio access node (1500): determining a first PDCCH monitoring opportunity, the first PDCCH monitoring opportunity occurring first in time, of a plurality of PDCCH monitoring opportunities associated with a physical downlink control channel (PDCCH); incrementing a Downlink Assignment Index (DAI) counter at the first PDCCH monitoring occasion and indicating a value of the counter in a Counter DAI field in Downlink Control Information (DCI) carried on the PDCCH; A radio access node (1500) configured to:

19. A radio access node (1500) according to claim 18, said radio access node (1500) being further adapted to perform the method according to any one of claims 10 to 15.

Images