TYPE 2 HARQ CODEBOOK DETERMINATION IN PRESENCE OF PDCCH REPETITIONS Related Applications [0001] This application claims the benefit of provisional patent application serial number 63/138,117, filed January 15, 2021 and provisional patent application serial number 63/138,721, filed January 18, 2021, the disclosures of which are hereby incorporated herein by reference in their entireties. Technical Field [0002] The present disclosure relates to codebook determination. Background [0003] NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in both downlink (i.e., from a network node, gNB, or base station, to a user equipment or UE) and uplink (i.e., from UE to gNB). DFT spread OFDM is also supported in the uplink. In the time domain, NR downlink and uplink are organized into equally sized subframes of 1ms each. A subframe is further divided into multiple slots of equal duration. The slot length depends on subcarrier spacing. For subcarrier spacing of ∆f = 15kHz, there is only one slot per subframe, and each slot consists of 14 OFDM symbols. [0004] Data scheduling in NR is typically in slot basis, an example is shown in Figure 1 with a 14-symbol slot, where the first two symbols contain Physical Downlink Control Channel (PDCCH) and the rest contains physical shared data channel, either Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH). [0005] Different subcarrier spacing values are supported in NR. The supported subcarrier spacing values (also referred to as different numerologies) are given by ∆f = (15 × 2 ^μ )kHz where μ ∈ 0,1,2,3,4. ∆f = 15kHz is the basic subcarrier spacing. The slot durations at different subcarrier spacings is given by [0006] In the frequency domain, a system bandwidth is divided into resource blocks (RBs), each corresponding to twelve contiguous subcarriers. The RBs are numbered starting with 0 from one end of the system bandwidth. The basic NR physical time- frequency resource grid is illustrated in Figure 2, where only one resource block (RB) within a 14-symbol slot is shown. One OFDM subcarrier during one OFDM symbol interval forms one resource element (RE). [0007] Downlink transmissions can be either dynamically scheduled in which the gNB transmits a DL assignment via Downlink Control Information (DCI) over PDCCH (Physical Downlink Control Channel) to a UE for each PDSCH transmission, or Semi- Persistent Scheduled (SPS) in which one or more DL SPS are semi-statically configured and each can be activated or deactivated by a DCI. [0008] There are three DCI formats defined for scheduling PDSCH in NR, i.e., DCI format 1_0, DCI format 1_1, and DCI format 1_2. DCI format 1-0 has a smaller size and can be used when a UE is not fully connected to the network while DCI format 1_1 and DCI format 1_2 can be used for scheduling MIMO (Multiple-Input-Multiple-Output) transmissions with up to 2 transport blocks (TBs). The DCI formats are referred to as DL DCI formats. [0009] A UE monitors a set of PDCCH candidates for potential PDCCHs. A PDCCH candidate consists of L ∈ [1,2,4,8,16] control-channel elements (CCEs) in a Control Resource Set (CORESET). A CCE consists of 6 resource-element groups (REGs) where a REG equals one RB during one OFDM symbol. L is referred to as the CCE aggregation level. [0010] The set of PDCCH candidates is defined in terms of PDCCH search space (SS) sets. A SS set can be a Common Search Space (CSS) set or a UE Specific Search Space (USS) set. A UE can be configured with up to 10 SS sets per bandwidth part (BWP) for monitoring PDCCH candidates. [0011] Each SS set is associated with a CORESET. A CORESET consists of resource blocks in the frequency domain and consecutive OFDM symbols in the time domain. In NR Rel-15, a UE can be configured with up to 3 CORESETs per bandwidth part. [0012] For each SS set, a UE is configured with the following parameters: • a PDCCH monitoring periodicity of k _s slots and a PDCCH monitoring offset of - _, slots • a PDCCH monitoring pattern within a slot, indicating first symbol(s) of the CORESET within a slot for PDCCH monitoring • a duration of T _s < k _s slots indicating a number of slots that the search space set exists • a number of PDCCH candidates per CCE aggregation level L [0013] A UE determines a PDCCH monitoring occasion on an active DL BWP from the PDCCH monitoring periodicity, the PDCCH monitoring offset, and the PDCCH monitoring pattern within a slot. For search space set s, the UE determines that a PDCCH monitoring occasion(s) exists in slot in frame n _f 0, where is the number of slots per radio frame. The UE monitors PDCCH candidates for search space set s for T _s consecutive slots, starting from slot and does not monitor PDCCH candidates for search space set s for the next k _s − T _s consecutive slots. [0014] A UE detects PDCCH in each PDCCH monitoring occasion. If a PDCCH is detected, the UE decodes the corresponding PDSCH based on the decoded control information in the PDCCH. [0015] In Rel-16, to better support multiple PDCCH monitoring occasions in a slot, new PDCCH monitoring capabilities are defined at least in terms of the maximum number of non-overlapping CCEs for channel estimation. The new limit is discussed based on the concept of PDCCH monitoring span. In short, the PDCCH monitoring span definition provides a set of rules for UE and gNB to have the same understanding on PDCCH monitoring span pattern in a slot based on CORESET/search space configuration and UE capability signaling related to PDCCH monitoring. The UE signals a candidate value set which contains parameters related to span gap X (minimum gap in OFDM symbols between two consecutive spans) and span length Y in OFDM symbols. Together with the CORESET/search space configuration, the monitoring span pattern can then be derived. The span pattern may contain multiple spans in a slot is repeated over multiple slots. [0016] NR HARQ ACK/NACK feedback [0017] When a PDCCH is detected by the UE, the decoding status of its scheduled PDSCH is sent back to the gNB in the form of Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) over a Physical Uplink Control Channel (PUCCH) resource. If the PUCCH overlaps with a PUSCH transmission by the same UE, HARQ ACK feedback can also be conveyed on PUSCH. [0018] Similarly, when a DL SPS deactivation DCI or a DCI for Secondary cell (SCell) dormancy is received by the UE, a HARQ ACK is sent by the UE to acknowledge the reception of the DCI. [0019] If the UE detects a DCI format scheduling a PDSCH reception ending in slot ⁿ or if the UE detects a DCI indicating a SPS PDSCH release or SCell dormancy through a PDCCH reception ending in slot ⁿ , the UE provides corresponding HARQ-ACK information in a PUCCH transmission in slot ^{n+ k} , where ^k is indicated by a PDSCH-to- HARQ-timing-indicator field in the DCI format, if present, or provided by dl-DataToUL- ACK. ^k is also referred to as K1. For DCI format 1-0, ^k can be one of {1, 2, 3, 4, 5, 6, 7, 8}. For DCI format 1-1 and DCI format 1_2, k can be one of a set of values configured in dl-DataToUL-ACK. The set of values can be in the range of {0,1, …,15}. Up to eight values can be configured in the set. [0020] In case of carrier aggregation (CA) with multiple carriers and/or TDD operation, multiple aggregated HARQ ACK/NACK bits may be sent in a single PUCCH resource. [0021] In NR, up to four PUCCH resource sets can be configured to a UE. A PUCCH resource set with pucch-ResourceSetId=0 can have up to 32 PUCCH resources while for PUCCH resource sets with pucch-ResourceSetId=1 to 3, each set can have up to 8 PUCCH resources. A UE determines the PUCCH resource set in a slot based on the number of aggregated UCI (Uplink Control Information) bits to be sent in the slot. The UCI bits consists of HARQ ACK/NACK, scheduling request (SR), and channel state information (CSI) bits. [0022] For a PUCCH transmission with HARQ-ACK information, a UE determines a PUCCH resource after determining a PUCCH resource set. The PUCCH resource determination is based on a 3-bit PUCCH resource indicator (PRI) field in a DL DCI format. [0023] If more than one DL DCI formats are received in the case of CA and/or TDD, the PUCCH resource determination is based on a PRI field in the last DCI among the multiple received DL DCIs that the UE detects. The multiple received DCIs have a value of a PDSCH-to-HARQ_feedback timing indicator field indicating a same slot for the PUCCH transmission. For PUCCH resource determination, the detected DCI formats are first indexed in an ascending order across serving cell indexes for a same PDCCH monitoring occasion and are then indexed in an ascending order across PDCCH monitoring occasion indexes. [0024] NR Type 2 HARQ -ACK Codebook [0025] NR Rel-15 supports two types of HARQ codebooks, i.e., semi-static (type 1) and dynamic (type 2) codebooks, for HARQ Ack multiplexing for multiple serving cells in case of carrier aggregation (CA) or multiple DL slots in case of TDD. A UE can be configured to use either one of the codebooks for HARQ Ack/Nack feedback. [0026] Type 1 HARQ codebook (CB) is determined based on a set of semi-statically configured parameters. The codebook size corresponds to the maximum number of HARQ Ack bits that may need to be fed back and it does not change dynamically. Therefore, the feedback overhead can be large. [0027] Unlike Type 1 HARQ codebook, the size of Type 2 HARQ codebook changes dynamically based on the actual number of PDSCH receptions or SPS PDSCH releases or SCell dormancy associated with a same PUCCH resource for HARQ Ack feedback. For this purpose, a counter DAI (Downlink Assignment Indicator) field in the DCIs and in case of DCI format 1-1 and DCI format 1_2, also a total DAI field (if more than one serving cell are configured) are defined. [0028] A value of the counter DAI field in DCI formats denotes the accumulative number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s), SPS PDSCH release, or SCell dormancy associated with the DCI formats that is present up to the current serving cell and current PDCCH monitoring occasion, first in ascending order of serving cell index c and then in ascending order of PDCCH monitoring occasion index m, where ^{0≤m < M} and M is total number of PDCCH monitoring occasions. [0029] The value of the total DAI, when present, in DCI formats denotes the total number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release or SCell dormancy associated with the DCI formats that is present, up to the current PDCCH monitoring occasion m and is updated from PDCCH monitoring occasion to PDCCH monitoring occasion. [0030] An example is shown Figure 3, where a UE is configured with two serving cells and three PDCCH monitoring occasions. The corresponding counter DAI and total DAI values in each scheduled DCI are shown. The counter DAI is updated after every scheduled DCI while total DAI is only updated every monitoring occasion. Since only two bits are allocated for either counter DAI or total DAI in DCI, the actual DAI values are wrapped round with a modulo 4 operation. A UE can figure out the actual number of DCIs transmitted even though some DCIs are undetected, if the undetected consecutive DCIs are smaller than four. [0031] For HARQ-ACK information transmitted in a PUCCH in slot ⁿ , the UE determines the HARQ-ACK information bits, associated with dynamic scheduled PDSCHs or SPS PDSCH release or SCell dormancy, in the order of first in ascending order of serving cell index and then in ascending order of PDCCH monitoring occasion index m . For the example shown in Figure 3 and if one TB is enabled for both cells, the (where O _ACK = 5) are shown in Figure 4. [0032] PDCCH repetition [0033] PDSCH transmission with multiple panels or transmission points (TRPs) has been introduced in NR Rel-16, in which a transport block may be repeated over multiple TRPs to increase PDSCH reliability. [0034] In NR Rel-17, it has been proposed to enhance PDCCH reliability with multiple TRPs by repeating a PDCCH over different TRPs. An example is shown in Figure 5, where a PDCCH is repeated over two TRPs at different times, both containing the same DCI. The DCI can be a DL DCI or a UL DCI. [0035] The PDCCH are repeated in two PDCCH candidates each associated with one of the two TRPs. The two PDCCH candidates are linked, i.e., the location of one PDCCH candidate can be obtained from the other PDCCH candidate. When performing PDCCH detection, a UE may detect PDCCH individually in each PDCCH candidate or jointly by soft combining of the two linked PDCCH candidates. [0036] Improved systems and methods for codebook determination are needed. Summary [0037] Systems and methods for codebook determination are provided herein. In some embodiments, a method performed by a wireless device for constructing a codebook includes: defining a first Physical Downlink Control Channel (PDCCH) occasion among multiple PDCCH occasions associated with a PDCCH; identifying the first PDCCH occasion for each detected Downlink Control Information (DCI); and constructing a codebook based on the first PDCCH occasion of all detected PDCCHs with a counter field in the corresponding DCIs. In this way, Type 2 Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) codebook construction is enabled in the presence of PDCCH repetitions with minimum specification changes. [0038] Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. A method is proposed to construct the codebook in the presence of PDCCH repetitions. The method comprises one or more of: defining a first PDCCH occasion among multiple PDCCH occasions associated with a PDCCH; identifying at the UE the first PDCCH occasion for each detected DCI; and constructing a codebook based on the first PDCCH occasion of all detected PDCCHs with a counter field in the corresponding DCIs. In some embodiments, the codebook comprises a Type 2 HARQ ACK codebook. In some embodiments, the counter field comprises a counter DAI field. Brief Description of the Drawings [0039] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure. [0040] Figure 1 illustrates data scheduling in New Radio (NR) is typically in slot basis, with a 14-symbol slot, where the first two symbols contain Physical Downlink Control Channel (PDCCH) and the rest contains physical shared data channel, either Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH); [0041] Figure 2 illustrates the basic NR physical time-frequency resource grid where only one resource block (RB) within a 14-symbol slot is shown; [0042] Figure 3 illustrates an example where a User Equipment (UE) is configured with two serving cells and three PDCCH monitoring occasions; [0043] Figure 4 illustrates the example of Figure 3 if one TB is enabled for both cells; [0044] Figure 5 illustrates an example where a PDCCH is repeated over two Transmission/Reception Points (TRPs) at different times, both containing the same Downlink Control Information (DCI); [0045] Figure 6 illustrates one example of a cellular communications system in which embodiments of the present disclosure may be implemented; [0046] Figure 7 illustrates an example where there are three DCIs transmitted in two serving cells and two PDCCH monitoring occasions, according to some embodiments of the present disclosure; [0047] Figure 8 illustrates an example where Type 2 HARQ codebook is constructed based on the determined first PDCCH occasions, according to some embodiments of the present disclosure; [0048] Figure 9 illustrates the resulting HARQ ACK information bits assuming that only a single codeword is configured in the two serving cells, according to some embodiments of the present disclosure; [0049] Figure 10 illustrates an example where there are three DCIs transmitted in two serving cells and two PDCCH monitoring occasions, according to some embodiments of the present disclosure; [0050] Figure 11 illustrates an example where the Type 2 HARQ codebook is constructed based on the determined last PDCCH occasions, according to some embodiments of the present disclosure; [0051] Figure 12 illustrates the resulting HARQ ACK information bits assuming that only a single codeword is configured in the two serving cells, according to some embodiments of the present disclosure; [0052] Figures 13A and 13B illustrate methods performed by a wireless device for constructing a codebook, according to some embodiments of the present disclosure; [0053] Figures 14A and 14B illustrate methods performed by a base station for constructing a codebook, according to some embodiments of the present disclosure; [0054] Figures 15 through 17 are schematic block diagrams of example embodiments of a radio access node, according to some embodiments of the present disclosure; [0055] Figures 18 and 19 are schematic block diagrams of a UE, according to some embodiments of the present disclosure; [0056] Figure 20 illustrates an example embodiment of a communication system in which embodiments of the present disclosure may be implemented; [0057] Figure 21 illustrates example embodiments of the host computer, base station, and UE of Figure 16, according to some embodiments of the present disclosure; and [0058] Figures 22 through 25 are flow charts that illustrate example embodiments of methods implemented in a communication system such as that of Figure 20. Detailed Description [0059] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode 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 disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure. [0060] Radio Node: As used herein, a “radio node” is either a radio access node or a wireless communication device. [0061] Radio Access Node: As used herein, a “radio access node” or “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 Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB Central Unit (gNB-CU) or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node. [0062] 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, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing a 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), a Unified Data Management (UDM), or the like. [0063] Communication Device: As used herein, a “communication device” is any type of device that has access to an access network. Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The communication device may be a portable, hand-held, computer-comprised, or vehicle- mounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection. [0064] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (IoT) device. Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC. The wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection. [0065] Network Node: As used herein, a “network node” is any node that is either part of the RAN or the core network of a cellular communications network/system. [0066] Transmission/Reception Point (TRP): In some embodiments, a TRP may be either a network node, a radio head, a spatial relation, or a Transmission Configuration Indicator (TCI) state. A TRP may be represented by a spatial relation or a TCI state in some embodiments. In some embodiments, a TRP may be using multiple TCI states. In some embodiments a TRP may be a part of the gNB transmitting and receiving radio signals to/from UE according to physical layer properties and parameters inherent to that element. In some embodiments, in Multiple Transmit/Receive Point (multi-TRP) operation, a serving cell can schedule UE from two TRPs, providing better PDSCH coverage, reliability and/or data rates. There are two different operation modes for multi-TRP: single- Downlink Control Information (DCI) and multi-DCI. For both modes, control of uplink and downlink operation is done by both physical layer and MAC. In single-DCI mode, UE is scheduled by the same DCI for both TRPs and in multi- DCI mode, UE is scheduled by independent DCIs from each TRP. [0067] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system. [0068] Note that, in the description herein, reference may be made to the term “cell”; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams. [0069] Figure 6 illustrates one example of a cellular communications system 600 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications 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 the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC), controlling corresponding (macro) cells 604-1 and 604-2. The base stations 602-1 and 602-2 are generally referred to herein collectively as base stations 602 and individually as base station 602. Likewise, the (macro) cells 604-1 and 604-2 are generally referred to herein collectively as (macro) cells 604 and individually as (macro) cell 604. The RAN may also include a number of low power nodes 606-1 through 606-4 controlling corresponding small cells 608-1 through 608-4. The low power nodes 606-1 through 606-4 can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like. Notably, while not illustrated, one or more of the small cells 608-1 through 608-4 may alternatively be provided by the base stations 602. The low power nodes 606-1 through 606-4 are generally referred to herein collectively as low power nodes 606 and individually as low power node 606. Likewise, the small cells 608-1 through 608-4 are generally referred to herein collectively as small cells 608 and individually as small cell 608. The cellular communications system 600 also includes a core network 610, which in the 5G System (5GS) is referred to as the 5GC. The base stations 602 (and optionally the low power nodes 606) are connected to the core network 610. [0070] The base stations 602 and the low power nodes 606 provide service to wireless communication devices 612-1 through 612-5 in the corresponding cells 604 and 608. The wireless communication devices 612-1 through 612-5 are generally referred to herein collectively as wireless communication devices 612 and individually as wireless communication device 612. In the following description, the wireless communication devices 612 are oftentimes UEs, but the present disclosure is not limited thereto. [0071] There currently exist certain challenges. In the presence of Physical Downlink Control Channel (PDCCH) repetition, how to construct Type 2 Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) codebook is an issue. For instance, consider an example where PDCCH #1 scheduling a PDSCH is repeated in PDCCH monitoring occasions m=0 and m=1, and there are other PDSCHs scheduled by PDCCHs in PDCCH monitoring occasion m=0, assume that PDCCH #1 is only detected in PDCCH monitoring occasion m=1. If the existing procedure for Type 2 HARQ ACK codebook construction is applied (i.e., the HARQ ACK bits are arranged first in ascending order of serving cell index and then in ascending order of PDCCH monitoring occasion index), the counter DAI and total DAI in DCI #1 in PDCCH monitoring occasion m=1 would result in an incorrect number of HARQ ACK bits and also incorrect mapping between the PDSCHs and the HARQ ACK bits. Improved systems and methods for codebook determination are needed. [0072] Systems and methods for codebook determination are provided herein. In some embodiments, a method performed by a wireless device for constructing a codebook includes: defining a first PDCCH occasion among multiple PDCCH occasions associated with a PDCCH; identifying the first PDCCH occasion for each detected DCI; and constructing a codebook based on the first PDCCH occasion of all detected PDCCHs with a counter field in the corresponding DCIs. In this way, Type 2 HARQ ACK codebook construction is enabled in the presence of PDCCH repetitions with minimum specification changes. [0073] In one embodiment, the counter DAI in a DCI is incremented only at the first PDCCH occasion in case of PDCCH repetition. If a PDCCH is repeated in two PDCCH monitoring occasions, the first PDCCH occasion is defined as the one in the PDCCH monitoring occasion that occurs early in time. Only the first PDCCH occasion is considered for incrementing counter DAI and total DAI in subsequent DCIs. [0074] The PDCCH monitoring occasions described in this invention disclosure can be either in a slot or a monitoring span. The different PDCCH monitoring occasions can be in different slots/monitoring spans or the same slot/monitoring span. [0075] An example is shown in Figure 7, where there are three DCIs transmitted in two serving cells and two PDCCH monitoring occasions. The DCIs are used to schedule three PDSCHs, PDSCHs #1 to #3. It is assumed that the HARQ-Acks associated with the PDSCHs are to be transmitted in a same PUCCH or PUSCH in an uplink slot. DCI#1 is carried in PDCCH #1, which is repeated in both PDCCH monitoring occasions m=0 and m=1. In this case, the first PDCCH occasion of PDCCH #1 is the one in PDCCH monitoring occasion m=0 and the second PDCCH occasion of PDCCH #1 is in PDCCH monitoring occasions m=1. The counter DAI and the total DAI in DCI #1 are incremented in the first PDCCH occasion in PDCCH monitoring occasions m=0. In the second occasion in PDCCH monitoring occasions m=1, the same DCI #1 is transmitted, thus the counter and total DAIs are unchanged. For DCI #3, its counter DAI and total DAI are incremented without considering the PDCCH #1 repetition, i.e., the second occasion of PDCCH #1 in PDCCH monitoring occasion m=1 is not counted. [0076] Type 2 HARQ codebook construction in presence of PDCCH repetitions [0077] In one embodiment, the counter DAI in a DCI is incremented only at the first PDCCH occasion in case of PDCCH repetition. If a PDCCH is repeated in two PDCCH monitoring occasions, the first PDCCH occasion is defined as the one in the PDCCH monitoring occasion that occurs early in time. Only the first PDCCH occasion is considered for incrementing counter DAI and total DAI in subsequent DCIs. [0078] If a PDCCH is repeated within a same PDCCH monitoring occasion in different PDCCH candidates of a same or different CORESETs or in a same or different SS sets, the first PDCCH occasion can be defined as one of • a linked PDCCH candidate with a lower (or higher) PDCCH candidate index, • a linked PDCCH candidate in a CORESET with a lower (or higher) CORESET ID, or • a linked PDCCH candidate in a SS set with a lower (or higher) SS set ID. [0079] In the UE side, for each detected DCI, the associated first PDCCH occasion is determined. The existing Type 2 HARQ codebook procedure is then applied by considering only the determined first PDCCH occasion. [0080] Using the example shown in Figure 7, let us assume DCI#1 is detected in the second PDCCH occasion in PDCCH monitoring occasions m=1 but not in the first occasion in PDCCH monitoring occasion m=0. Both DCI #2 and DCI #3 are detected. Based on the linkage of PDCCH candidates for PDCCH repetition, the UE can determine that the first PDCCH occasion for DCI#1 is in PDCCH monitoring occasions m=0. For DCIs #2 and #3, they are not repeated and thus the corresponding first occasions are the ones over which they are detected. The Type 2 HARQ codebook is then constructed based on the determined first PDCCH occasions as shown in Figure 8. [0081] Assuming that only a single codeword is configured in the two serving cells, the resulting HARQ ACK information bits for a total number of O _ACK = 3 HARQ-ACK information bits in a PUCCH, are shown in Figure 9. [0082] The embodiment may be described by changes (highlighted in bold) in the existing pseudo code for Type 2 HARQ-Ack codebook below. [0083] ---start of proposed changes in 38.213 v16.4.0 section 9.1.3.1--- [0084] 9.1.3.1 Type-2 HARQ-ACK codebook in physical uplink control channel [0085] ---unchanged text omitted --- [0086] If the UE transmits HARQ-ACK information in a PUCCH in slot 2 and for any PUCCH format, the UE determines the , for a total number of O _ACK HARQ-ACK information bits, according to the following pseudo-code: Set m = 0 – PDCCH with DCI format scheduling PDSCH reception, SPS PDSCH release or SCell dormancy indication monitoring occasion index: lower index corresponds to earlier PDCCH monitoring occasion Set j = 0 Set V _temp = 0 Set V _temp2 = 0 Set V _s = Ø Set to the number of serving cells configured by higher layers for the UE - if, for an active DL BWP of a serving cell, the UE is not provided coresetPoolIndex or is provided coresetPoolIndex with value 0 for one or more first CORESETs and is provided coresetPoolIndex with value 1 for one or more second CORESETs, and is provided ACKNackFeedbackMode = JointFeedback, the serving cell is counted two times where the first time corresponds to the first CORESETs and the second time corresponds to the second CORESETs - if the UE indicates type2-HARQ-ACK-Codebook, a serving cell is counted times where is the number of PDSCH receptions that can be scheduled for the serving cell by DCI formats in PDCCH receptions at a same PDCCH monitoring occasion based on the reported value of type2-HARQ-ACK-Codebook - if PDCCH repetition is configured, for each detected DCI the first PDCCH occasion is determined. The pseudo-code is applicable to PDCCHs in the first PDCCH occasions. Set M to the number of PDCCH monitoring occasion(s) while m < M Set c = 0 – serving cell index: lower indexes correspond to lower RRC indexes of corresponding cell while if PDCCH monitoring occasion m is before an active DL BWP change on serving cell c or an active UL BWP change on the PCell and an active DL BWP change is not triggered in PDCCH monitoring occasion m c = c + 1; else if there is a PDSCH on serving cell c associated with PDCCH in PDCCH monitoring occasion m, or there is a PDCCH indicating SPS PDSCH release or SCell dormancy on serving cell c, and if the PDCCH corresponds to a first PDCCH occasion in case of PDCCH repetition end if if harq-ACK-SpatialBundlingPUCCH is not provided and the UE is configured by maxNrofCodeWordsScheduledByDCI with reception of two transport blocks for at least one configured DL BWP of at least one serving cell, information bit corresponding to the first transport block of this cell information bit corresponding to the second transport block of this cell elseif harq-ACK-SpatialBundlingPUCCH is provided to the UE and m is a monitoring occasion for PDCCH with a DCI format that supports PDSCH reception with two transport blocks and the UE is configured by maxNrofCodeWordsScheduledByDCI with reception of two transport blocks in at least one configured DL BWP of a serving cell, = binary AND operation of the HARQ-ACK information bits corresponding to the first and second transport blocks of this cell else formation bit of this cell end if end if c = c + 1 end if end while m = m + 1 end while if UE does not set V _temp2 = V _temp end if if V _temp2 < V _temp j = j + 1 end if if harq-ACK-SpatialBundlingPUCCH is not provided to the UE and the UE is configured by maxNrofCodeWordsScheduledByDCI with reception of two transport blocks for at least one configured DL BWP of a serving cell, O ^ACK = 2 ⋅ (4 ⋅ j + V _temp2 ) else O ^ACK = 4 ⋅ j + V _temp2 end if ---unchanged text omitted --- ---end of proposed changes -------- [0087] Alternative embodiment for Type 2 HARQ codebook construction in presence of PDCCH repetitions [0088] In an alternative embodiment, the counter DAI in a DCI is incremented only at the last PDCCH occasion in case of PDCCH repetition. If a PDCCH is repeated in two PDCCH monitoring occasions, the last PDCCH occasion is defined as the one in the PDCCH monitoring occasion that occurs latest in time. Only the last PDCCH occasion is considered for incrementing counter DAI and total DAI. [0089] An example is shown in Figure 10, where there are three DCIs transmitted in two serving cells and two PDCCH monitoring occasions. The DCIs are used to schedule three PDSCHs, PDSCHs #1 to #3. DCI#1 is carried in PDCCH #1, which is repeated in both PDCCH monitoring occasions m=0 and m=1. In this case, the last PDCCH occasion of PDCCH #1 is the one in PDCCH monitoring occasion m=1 and the first PDCCH occasion of PDCCH #1 is in PDCCH monitoring occasions m=0. The counter DAI and the total DAI in DCI #1 are incremented in the last PDCCH occasion in PDCCH monitoring occasions m=1. In the first occasion in PDCCH monitoring occasions m=0, the same DCI #1 is transmitted, thus the counter and total DAIs are unchanged. For DCI #2, its counter DAI and total DAI are incremented without considering the PDCCH #1 repetition, i.e., the first occasion of PDCCH #1 in PDCCH monitoring occasion m=0 is not counted. [0090] In the UE side, for each detected DCI, the associated last PDCCH occasion is determined. The existing Type 2 HARQ codebook procedure is then applied by considering only the determined last PDCCH occasions. [0091] Using the example shown in Figure 10, let us assume DCI#1 is detected in the first PDCCH occasion in PDCCH monitoring occasions m=0 but not in the last occasion in PDCCH monitoring occasion m=1. Both DCI #2 and DCI #3 are also detected. Based on the linkage of PDCCH candidates for PDCCH repetition, the UE can determine that the last PDCCH occasion for DCI#1 is in PDCCH monitoring occasions m=1. For DCIs #2 and #3, they are not repeated and thus the corresponding last occasions are the ones over which they are detected. The Type 2 HARQ codebook is then constructed based on the determined last PDCCH occasions as shown in Figure 11. [0092] Assuming that only a single codeword is configured in the two serving cells, the resulting HARQ ACK information bits for a total number of O _ACK = 3 HARQ-ACK information bits in a PUCCH, are shown in Figure 12. [0093] The embodiment may be described by changes (highlighted in bold) in the existing pseudo code for Type 2 HARQ-Ack codebook below. [0094] ---start of proposed changes in 38.213 v16.4.0 section 9.1.3.1--- [0095] 9.1.3.1 Type-2 HARQ-ACK codebook in physical uplink control channel [0096] ---unchanged text omitted --- [0097] If the UE transmits HARQ-ACK information in a PUCCH in slot 2 and for any PUCCH format, the UE determines the , for a total number of O _ACK HARQ-ACK information bits, according to the following pseudo-code: Set m = 0 – PDCCH with DCI format scheduling PDSCH reception, SPS PDSCH release or SCell dormancy indication monitoring occasion index: lower index corresponds to earlier PDCCH monitoring occasion Set j = 0 Set V _temp = 0 Set V _temp2 = 0 Set V _s = ∅ Set to the number of serving cells configured by higher layers for the UE - if, for an active DL BWP of a serving cell, the UE is not provided coresetPoolIndex or is provided coresetPoolIndex with value 0 for one or more first CORESETs and is provided coresetPoolIndex with value 1 for one or more second CORESETs, and is provided ACKNackFeedbackMode = JointFeedback, the serving cell is counted two times where the first time corresponds to the first CORESETs and the second time corresponds to the second CORESETs - if the UE indicates type2-HARQ-ACK-Codebook, a serving cell is counted times where is the number of PDSCH receptions that can be scheduled for the serving cell by DCI formats in PDCCH receptions at a same PDCCH monitoring occasion based on the reported value of type2-HARQ-ACK-Codebook - if PDCCH repetition is configured, for each detected DCI the last PDCCH occasion is determined. The pseudo-code is applicable to PDCCHs in the last PDCCH occasions. Set M to the number of PDCCH monitoring occasion(s) while m < M Set c = 0 – serving cell index: lower indexes correspond to lower RRC indexes of corresponding cell while if PDCCH monitoring occasion m is before an active DL BWP change on serving cell c or an active UL BWP change on the PCell and an active DL BWP change is not triggered in PDCCH monitoring occasion m c = c + 1; else if there is a PDSCH on serving cell c associated with PDCCH in PDCCH monitoring occasion m, or there is a PDCCH indicating SPS PDSCH release or SCell dormancy on serving cell c, and if the PDCCH corresponds to a last PDCCH occasion in case of PDCCH repetition end if if harq-ACK-SpatialBundlingPUCCH is not provided and the UE is configured by maxNrofCodeWordsScheduledByDCI with reception of two transport blocks for at least one configured DL BWP of at least one serving cell, HARQ-ACK information bit corresponding to the first transport block of this cell = HARQ-ACK information bit corresponding to the second transport block of this cell elseif harq-ACK-SpatialBundlingPUCCH is provided to the UE and m is a monitoring occasion for PDCCH with a DCI format that supports PDSCH reception with two transport blocks and the UE is configured by maxNrofCodeWordsScheduledByDCI with reception of two transport blocks in at least one configured DL BWP of a serving cell, = binary AND operation of the HARQ-ACK information bits corresponding to the first and second transport blocks of this cell else formation bit of this cell end if end if c = c + 1 end if end while m = m + 1 end while if UE does not set and T _D = 2 V _temp2 = V _temp end if if V _temp2 < V _temp j = j + 1 end if if harq-ACK-SpatialBundlingPUCCH is not provided to the UE and the UE is configured by maxNrofCodeWordsScheduledByDCI with reception of two transport blocks for at least one configured DL BWP of a serving cell, O ^ACK = 2 ⋅ (4 ⋅ j + V _temp2 ) else O ^ACK = 4 ⋅ j + V _temp2 end if [0098] Figure 13A illustrates a method performed by a wireless device for constructing a codebook. The method includes one or more of: defining (step 1300A) a first PDCCH occasion among multiple PDCCH occasions associated with a PDCCH; identifying (step 1302A) the first PDCCH occasion for each detected DCI; and constructing (step 1304A) a codebook based on the first PDCCH occasion of all detected PDCCHs with a counter field in the corresponding DCIs. [0099] Figure 13B illustrates a method performed by a wireless device for constructing a codebook. The method includes: receiving PDCCHs associated with the first and second sets of DCI formats (step 1300B); determining a first PDCCH monitoring occasion among the multiple PDCCH monitoring occasions for each of the at least one PDCCH (step 1302B); constructing the HARQ-ACK codebook by ordering the HARQ-ACK information associated with each PDCCH according to the associated PDCCH monitoring occasion index, wherein for each of the at least one PDCCH the associated PDCCH monitoring occasion is the first PDCCH monitoring occasion (step 1304B); and transmitting, to the base station, the HARQ-ACK information in the codebook (step1306B). [0100] Figure 14A illustrates a method performed by a base station for constructing a codebook. The method includes one or more of: defining (step 1400A) a first PDCCH occasion among multiple PDCCH occasions associated with a PDCCH; identifying (step 1402A) the first PDCCH occasion for each DCI; and increment (step 1404A) a counter based on the first PDCCH occasion of all PDCCHs with a counter field in the corresponding DCIs. [0101] Figure 14B illustrates a method performed by a base station for constructing a codebook. The method includes: determining a first PDCCH monitoring occasion among the multiple PDCCH monitoring occasions (step 1400B); incrementing the counter at the first PDCCH monitoring occasion and indicating the counter value in a counter field in the DCI (step 1402B); transmitting, to the wireless device, the DCI in the PDCCH in the multiple PDCCH candidates (step 1404B); receiving, from the wireless device, HARQ-ACK information associated with the PDCCH (step 1406B). [0102] Figure 15 is a schematic block diagram of a radio access node 1500 according to some 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 that implements all or part of the functionality of the base station 602 or gNB described herein. As illustrated, the radio access node 1500 includes a control system 1502 that includes one or more processors 1504 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 1506, and a network interface 1508. The one or more processors 1504 are also referred to herein as processing circuitry. In addition, the radio access node 1500 may include one or more radio units 1510 that each includes one or more transmitters 1512 and one or more receivers 1514 coupled to one or more antennas 1516. The radio units 1510 may be referred to or be part of radio interface circuitry. In some embodiments, the radio unit(s) 1510 is external to the control system 1502 and connected to the control system 1502 via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s) 1510 and potentially the antenna(s) 1516 are integrated together with the control system 1502. The one or more processors 1504 operate to provide one or more functions of a radio access node 1500 as described herein. In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 1506 and executed by the one or more processors 1504. [0103] Figure 16 is a schematic block diagram that illustrates a virtualized embodiment of the radio access node 1500 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Further, other types of network nodes may have similar virtualized architectures. Again, optional features are represented by dashed boxes. [0104] 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(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the radio access node 1500 may include the control system 1502 and/or the one or more radio units 1510, as described above. The control system 1502 may be connected to the radio unit(s) 1510 via, for example, an optical cable or the like. The radio access node 1500 includes one or more processing nodes 1600 coupled to or included as part of a network(s) 1602. If present, the control system 1502 or the radio unit(s) are connected to the processing node(s) 1600 via the network 1602. Each processing node 1600 includes one or more processors 1604 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1606, and a network interface 1608. [0105] In this example, functions 1610 of the radio access node 1500 described herein are implemented at the one or more processing nodes 1600 or distributed across the one or more processing nodes 1600 and the control system 1502 and/or the radio unit(s) 1510 in any desired manner. In some particular embodiments, some or all of the functions 1610 of the radio access node 1500 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 1600. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 1600 and the control system 1502 is used in order to carry out at least some of the desired functions 1610. Notably, in some embodiments, the control system 1502 may not be included, in which case the radio unit(s) 1510 communicate directly with the processing node(s) 1600 via an appropriate network interface(s). [0106] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of radio access node 1500 or a node (e.g., a processing node 1600) implementing one or more of the functions 1610 of the radio access node 1500 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory). [0107] Figure 17 is a schematic block diagram of the 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 module(s) 1700 provide the functionality of the radio access node 1500 described herein. This discussion is equally applicable to the processing node 1600 of Figure 16 where the modules 1700 may be implemented at one of the processing nodes 1600 or distributed across multiple processing nodes 1600 and/or distributed across the processing node(s) 1600 and the control system 1502. [0108] Figure 18 is a schematic block diagram of a wireless communication device 1800 according to some embodiments of the present disclosure. As illustrated, the wireless communication device 1800 includes one or more processors 1802 (e.g., CPUs, ASICs, FPGAs, and/or the like), 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(s) 1806 includes radio-front end circuitry connected to the antenna(s) 1812 that is configured to condition signals communicated between the antenna(s) 1812 and the processor(s) 1802, as will be appreciated by on of ordinary skill in the art. The processors 1802 are also referred to herein as processing circuitry. The transceivers 1806 are also referred to herein as radio circuitry. In some embodiments, the functionality of the wireless communication device 1800 described above may be fully or partially implemented in software that is, e.g., stored in the memory 1804 and executed by the processor(s) 1802. Note that the wireless communication device 1800 may include additional components not illustrated in Figure 18 such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device 1800 and/or allowing output of information from the wireless communication device 1800), a power supply (e.g., a battery and associated power circuitry), etc. [0109] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the wireless communication device 1800 according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory). [0110] Figure 19 is a schematic block diagram of the 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 module(s) 1900 provide the functionality of the wireless communication device 1800 described herein. [0111] With reference to Figure 20, in accordance with an embodiment, a communication system includes a telecommunication network 2000, such as a 3GPP- type cellular network, which comprises an access network 2002, such as a RAN, and a core network 2004. The access network 2002 comprises a plurality of base stations 2006A, 2006B, 2006C, such as Node Bs, eNBs, gNBs, or other types of wireless Access Points (APs), each defining 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 coverage area 2008C is configured to wirelessly connect to, or be paged by, the corresponding base station 2006C. A second UE 2014 in coverage area 2008A is wirelessly connectable to the corresponding base station 2006A. While a plurality of UEs 2012, 2014 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 2006. [0112] The telecommunication network 2000 is itself connected to a host computer 2016, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 2016 may be under the ownership or control of a service provider or may be operated by the service provider or on behalf of the service provider. Connections 2018 and 2020 between the telecommunication network 2000 and the host computer 2016 may extend directly from the core network 2004 to the host computer 2016 or may go via an optional intermediate network 2022. The intermediate network 2022 may be one of, or a combination of more than one of, a public, private, or hosted network; the intermediate network 2022, if any, may be a backbone network or the Internet; in particular, the intermediate network 2022 may comprise two or more sub-networks (not shown). [0113] The communication system of Figure 20 as a whole enables connectivity between the connected UEs 2012, 2014 and the host computer 2016. The connectivity may be described as an Over-the-Top (OTT) connection 2024. The host computer 2016 and the 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 network 2022, and possible further infrastructure (not shown) as intermediaries. The OTT connection 2024 may be transparent in the sense that the participating communication devices through which the OTT connection 2024 passes are unaware of routing of uplink and downlink communications. For example, the base station 2006 may not or need not be informed about the past routing of an incoming downlink communication with data originating from the host computer 2016 to be forwarded (e.g., handed over) to a connected UE 2012. Similarly, the base station 2006 need not be aware of the future routing of an outgoing uplink communication originating from the UE 2012 towards the host computer 2016. [0114] Example implementations, in accordance with an embodiment, of the UE, base station, and host computer discussed in the preceding paragraphs will now be described with reference to Figure 21. In a communication system 2100, a host computer 2102 comprises hardware 2104 including a communication interface 2106 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 2100. The host computer 2102 further comprises processing circuitry 2108, which may have storage and/or processing capabilities. In particular, the processing circuitry 2108 may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The host computer 2102 further comprises software 2110, which is stored in or accessible by the host computer 2102 and executable by the processing circuitry 2108. The software 2110 includes a host application 2112. The host application 2112 may be operable to provide a service to a remote user, such as a UE 2114 connecting via an OTT connection 2116 terminating at the UE 2114 and the host computer 2102. In providing the service to the remote user, the host application 2112 may provide user data which is transmitted using the OTT connection 2116. [0115] The communication system 2100 further includes a base station 2118 provided in a telecommunication system and comprising hardware 2120 enabling it to communicate with the host computer 2102 and with the UE 2114. The hardware 2120 may include a communication interface 2122 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 2100, as well as a radio interface 2124 for setting up and maintaining at least a wireless connection 2126 with the UE 2114 located in a coverage area (not shown in Figure 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 it may pass through a core network (not shown in Figure 21) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware 2120 of the base station 2118 further includes processing circuitry 2130, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The base station 2118 further has software 2132 stored internally or accessible via an external connection. [0116] The communication system 2100 further includes the UE 2114 already referred to. The UE’s 2114 hardware 2134 may include a radio interface 2136 configured to set up and maintain a wireless connection 2126 with a base station serving a coverage area in which the UE 2114 is currently located. The hardware 2134 of the UE 2114 further includes processing circuitry 2138, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The UE 2114 further comprises software 2140, which is stored in or accessible by the UE 2114 and executable by the processing circuitry 2138. The software 2140 includes a client application 2142. The client application 2142 may be operable to provide a service to a human or non-human user via the UE 2114, with the support of the host computer 2102. In the host computer 2102, the executing host application 2112 may communicate with the executing client application 2142 via the OTT connection 2116 terminating at the UE 2114 and the host computer 2102. In providing the service to the 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 transfer 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. [0117] It is noted that the host computer 2102, the base station 2118, and the UE 2114 illustrated in Figure 21 may be similar or identical to the host computer 2016, one of the base stations 2006A, 2006B, 2006C, and one of the UEs 2012, 2014 of Figure 20, respectively. This is to say, the inner workings of these entities may be as shown in Figure 21 and independently, the surrounding network topology may be that of Figure 20. [0118] In Figure 21, the OTT connection 2116 has been drawn abstractly to illustrate the communication between the host computer 2102 and the UE 2114 via the base station 2118 without explicit reference to any intermediary devices and the precise routing of messages via these devices. The network infrastructure may determine the routing, which may be configured to hide from the UE 2114 or from the service provider operating the host computer 2102, or both. While the OTT connection 2116 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network). [0119] The wireless connection 2126 between the UE 2114 and the base station 2118 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 2114 using the OTT connection 2116, in which the wireless connection 2126 forms the last segment. More precisely, the teachings of these embodiments may improve the e.g., data rate, latency, power consumption, etc. and thereby provide benefits such as e.g., reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. [0120] A measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 2116 between the host computer 2102 and the UE 2114, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 2116 may be implemented in the software 2110 and the hardware 2104 of the host computer 2102 or in the software 2140 and the hardware 2134 of the UE 2114, or both. In some embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 2116 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which the software 2110, 2140 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 2116 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the base station 2118, and it may be unknown or imperceptible to the base station 2118. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer 2102’s measurements of throughput, propagation times, latency, and the like. The measurements may be implemented in that the software 2110 and 2140 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2116 while it monitors propagation times, errors, etc. [0121] Figure 22 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 20 and 21. For simplicity of the present disclosure, only drawing references to Figure 22 will be included in this section. In step 2200, the host computer provides user data. In sub-step 2202 (which may be optional) of step 2200, the host computer provides the user data by executing a host application. In step 2204, the host computer initiates a transmission carrying the user data to the UE. In step 2206 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2208 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer. [0122] Figure 23 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 20 and 21. For simplicity of the present disclosure, only drawing references to Figure 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 carrying the user data to the UE. The transmission may pass via the base station, in accordance with 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. [0123] Figure 24 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 20 and 21. For simplicity of the present disclosure, only drawing references to Figure 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 which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in sub-step 2408 (which may be optional), transmission of the user data to the host computer. In step 2410 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure. [0124] Figure 25 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 20 and 21. For simplicity of the present disclosure, only drawing references to Figure 25 will be included in this section. In step 2500 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. 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. [0125] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure. [0126] While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.). [0127] Embodiments [0128] Group A Embodiments [0129] Embodiment 1: A method performed by a wireless device for constructing a codebook, the method comprising one or more of: defining (1300) a first PDCCH occasion among multiple PDCCH occasions associated with a PDCCH; identifying (1302) the first PDCCH occasion for each detected DCI; and constructing (1304) a codebook based on the first PDCCH occasion of all detected PDCCHs with a counter field in the corresponding DCIs. [0130] Embodiment 2: The method of embodiment 1 wherein the codebook comprises a Type 2 HARQ ACK codebook. [0131] Embodiment 3: The method of any of embodiments 1 to 2 wherein the counter field comprises a counter Downlink Assignment Indicator, DAI, field. [0132] Embodiment 4: The method of any of embodiments 1 to 2 wherein the wireless device comprises a User Equipment, UE. [0133] Embodiment 5: The method of any of embodiments 1 to 4, further comprising: receiving, from a network node, multiple search space sets and PDCCH repetition in a subset of the search space sets. [0134] Embodiment 6: The method of any of embodiments 1 to 5, further comprising: monitoring the first and the second PDCCHs and if detected, decoding the corresponding PDSCH. [0135] Embodiment 7: The method of any of embodiments 1 to 6, further comprising: determining a first PDCCH occasion for the first PDCCH when it is detected. [0136] Embodiment 8: The method of any of embodiments 1 to 7, further comprising: constructing a Type 2 HARQ ACK codebook based on the first PDCCH occasion of the first PDCCH and/or the second PDCCH, and the decoding status of the first and the second PDSCH. [0137] Embodiment 9: The method of any of embodiments 1 to 8 wherein receiving the multiple search space sets and the PDCCH repetition in a subset of the search space sets comprises: receiving multiple linked PDCCH candidates in a same or different search space sets over which a PDCCH may be repeated. [0138] Embodiment 10: The method of any of embodiments 1 to 9 wherein the first PDCCH occasion corresponds to a linked PDCCH candidate that occurs first in time. [0139] Embodiment 11: The method of any of embodiments 1 to 10 wherein the first PDCCH occasion corresponds to one of: a. a linked PDCCH candidate with a lower (or higher) PDCCH candidate index; b. a linked PDCCH candidate in a CORESET with a lower (or higher) CORESET ID; and c. a linked PDCCH candidate in a SS set with a lower (or higher) SS set ID. [0140] Embodiment 12: The method of any of embodiments 1 to 11 wherein a value of the counter field in a DCI carried in a PDCCH repeated in multiple PDCCH occasions is determined based on the first PDCCH occasion in case of PDCCH repetition. [0141] Embodiment 13: The method of any of embodiments 1 to 12 wherein constructing a Type 2 HARQ ACK codebook based on the first PDCCH occasion comprises allocating a HARQ ACK bit(s) to the first PDSCH scheduled by the first PDCCH transmitted in the first PDCCH occasion. [0142] Embodiment 14: The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the base station. [0143] Group B Embodiments [0144] Embodiment 15: A method performed by a base station for updating a counter , the method comprising one or more of: defining (1400) a first PDCCH occasion among multiple PDCCH occasions associated with a DCI; identifying (1402) the first PDCCH occasion; and incrementing (1404) the counter at the first PDCCH occasion and indicating the counter value in a counter field in the DCI. [0145] Embodiment 16: The method of embodiment 1 wherein the PDCCH schedules a PDSCH, a SPS release, or a Scell dormancy. [0146] Embodiment 17: The method of any of embodiments 15 to 16 wherein the counter field comprises a counter Downlink Assignment Indicator, DAI, field. [0147] Embodiment 18: The method of any of embodiments 15 to 17 wherein the base station comprises a gNB. [0148] Embodiment 19: The method of any of embodiments 15 to 18, further comprising: configuring a wireless device with multiple search space sets and PDCCH repetition in a subset of the search space sets. [0149] Embodiment 20: The method of any of embodiments 15 to 19, further comprising: scheduling a first PDSCH with a first PDCCH which is repeated in multiple PDCCH occasions and a second PDSCH with a second PDCCH without repetition. [0150] Embodiment 21: The method of any of embodiments 15 to 20, further comprising: determining a first PDCCH occasion for the first PDCCH. [0151] Embodiment 22: The method of embodiment 1 where the incrementing the counter comprises adding one to the counter. [0152] Embodiment 23: The method of any of embodiments 15 to 22 wherein configuring the wireless device with the multiple search space sets and the PDCCH repetition in a subset of the search space sets comprises: configuring the wireless device with multiple linked PDCCH candidates in a same or different search space sets over which a PDCCH may be repeated. [0153] Embodiment 24: The method of any of embodiments 15 to 23 wherein the first PDCCH occasion corresponds to a linked PDCCH candidate that occurs first in time. [0154] Embodiment 25: The method of any of embodiments 15 to 24 wherein the first PDCCH occasion corresponds to one of: a. a linked PDCCH candidate with a lower (or higher) PDCCH candidate index; b. a linked PDCCH candidate in a CORESET with a lower (or higher) CORESET ID; and c. a linked PDCCH candidate in a SS set with a lower (or higher) SS set ID. [0155] Embodiment 26: The method of any of embodiments 15 to 25 wherein a value of the counter field in a DCI carried in a PDCCH repeated in multiple PDCCH occasions is determined based on the first PDCCH occasion in case of PDCCH repetition. [0156] Embodiment 28: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or a wireless device. [0157] Group C Embodiments [0158] Embodiment 29: A wireless device for constructing a codebook, the wireless device comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the wireless device. [0159] Embodiment 30: A base station for incrementing a counter, the base station comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the base station. [0160] Embodiment 31: A User Equipment, UE, for constructing a codebook, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE. [0161] Embodiment 32: A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a User Equipment, UE; wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. [0162] Embodiment 33: The communication system of the previous embodiment further including the base station. [0163] Embodiment 34: The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. [0164] Embodiment 35: The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application. [0165] Embodiment 36: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments. [0166] Embodiment 37: The method of the previous embodiment, further comprising, at the base station, transmitting the user data. [0167] Embodiment 38: The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application. [0168] Embodiment 39: A User Equipment, UE, configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform the method of the previous 3 embodiments. [0169] Embodiment 40: A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a User Equipment, UE; wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments. [0170] Embodiment 41: The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE. [0171] Embodiment 42: The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application. [0172] Embodiment 43: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments. [0173] Embodiment 44: The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station. [0174] Embodiment 45: A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station; wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments. [0175] Embodiment 46: The communication system of the previous embodiment, further including the UE. [0176] Embodiment 47: The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station. [0177] Embodiment 48: The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data. [0178] Embodiment 49: The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data. [0179] Embodiment 50: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. [0180] Embodiment 51: The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station. [0181] Embodiment 52: The method of the previous 2 embodiments, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application. [0182] Embodiment 53: The method of the previous 3 embodiments, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application; wherein the user data to be transmitted is provided by the client application in response to the input data. [0183] Embodiment 54: A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. [0184] Embodiment 55: The communication system of the previous embodiment further including the base station. [0185] Embodiment 56: The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. [0186] Embodiment 57: The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer. [0187] Embodiment 58: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. [0188] Embodiment 59: The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE. [0189] Embodiment 60: The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer. [0190] Some embodiments of the present disclosure could be implemented using one or more of the following proposals. [0191] Proposal 1 Confirm the working assumption for PDCCH reliability enhancements with non-SFN schemes and Option 2 + Case 1, i.e. support Alt3 (two SS sets associated with corresponding CORESETs). [0192] Proposal 2 When PDCCH repetition is enabled for the UE, the default is that two PDCCH candidates are linked. FFS whether more than two can be configured to be linked [0193] Proposal 3 Two blind decodes per PDCCH pair is counted towards BD limit for the UE when the PDCCH consists of two PDCCH candidates that are linked. [0194] Proposal 4 Support Alt.2 and use one of the linked PDCCH candidates in a CORESET having the lowest controlResourceSetId or a SS set with lowest searchSpaceId in the linked SS sets. [0195] Proposal 5 The PDCCH symbol occurring latest in time in a pair of linked PDCCH candidates is defined as the last symbol regardless of which PDCCH candidate(s) the UE actually have detected. [0196] Proposal 6 The DAI counter DAI is incremented only at the first time a PDCCH is transmitted (i.e., at the first PDCCH occasion) in a linked pair of PDCCH candidates. [0197] Proposal 7 The existing procedure for type 2 HARQ-ACK codebook construction is applied only for the first PDCCH occasion in case of PDCCH repetition regardless whether the PDCCH is actually detected in the first or/and the second PDCCH occasion. [0198] Proposal 8 In case the CORESET is not configured as unavailable for PDSCH and if a PDSCH scheduled by a pair of PDCCHs overlap with resources in the CORESETs containing the PDCCHs, PDSCH rate matching is done around the union of the linked PDCCH candidates and corresponding DM-RS [0199] Proposal 9 DCI Format 2-2/2-3 are also supported by multi-TRP based PDCCH enhancements. [0200] Proposal 10 One of the two activated TCI states is used as the default TCI state, FFS whether the one is specified or indicated in a MAC CE activating the TCI states. [0201] Proposal 11 Consider finalizing PDCCH enhancement with intra-slot PDCCH repetition first. [0202] Proposal 12 For codebook/non-codebook based multi-TRP PUSCH, support two separate SRI fields in DCI, where the first SRI field indicates the SRI(s) corresponding to the first TRP and the second SRI field indicates the SRI(s) corresponding to the second TRP. [0203] Proposal 13 For codebook based multi-TRP PUSCH, support two separate TPMI fields in DCI, where the first TPMI field indicates the TPMI corresponding to the first TRP and the second TPMI field indicates the TPMI corresponding to the second TRP. The number of layers indicated in the first TPMI field and the second TPMI field are the same. [0204] Proposal 14 For per TRP closed-loop power control for PUSCH, Option 3 is supported where a second TPC field is added in DCI formats 0_1 / 0_2. [0205] Proposal 15 Dynamic switching between PUSCH transmission to a single-TRP and multi-TRP should be supported, i.e. each PUSCH transmission is either targeting reception at one or at two TRPs. [0206] Proposal 16 Two SRI/TPMI fields are supported for PUSCH repetition towards m-TRP. [0207] Proposal 17 To dynamically indicate PUSCH transmission towards a single- TRP or multiple-TRPs, each SRI/TPMI field contains a codepoint that indicates whether the SRI/TPMI field is disabled or not. [0208] Proposal 18 For CG PUSCH transmission towards multiple TRPs, support Alt.1. [0209] Proposal 19 Reuse the same RV mapping method as in PUSCH repetition Type A for PUSCH repetition Type B [0210] Proposal 20 Consider allowing back-to-back scheduling of PUSCH repetitions via multiple DCIs over multiple TRPs in NR Rel-17. [0211] Proposal 21 To improve A-CSI reliability, support A-CSI multiplexing on at least two PUSCH occasions towards different TRPs in NR Rel-17. [0212] Proposal 22 Intra-slot beam hopping (Scheme 2) is not supported in NR Rel- 17. [0213] Proposal 23 Support Multi-TRP intra-slot repetition (Scheme 3) in NR Rel-17 [0214] Proposal 24 Both short and long PUCCH formats are supported for Intra-slot repetition [0215] Proposal 25 For per TRP closed-loop power control for PUCCH, support either Option 3 (two TPC fields in DCI 1_1/1_2) or Option 4 (one codepoint in TPC field indicating two TPC values) in NR Rel-17. [0216] At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s). • 3GPP Third Generation Partnership Project • 5G Fifth Generation • 5GC Fifth Generation Core • 5GS Fifth Generation System • ACK Acknowledgement • AF Application Function • AMF Access and Mobility Function • AN Access Network • AP Access Point • ASIC Application Specific Integrated Circuit • AUSF Authentication Server Function • BWP Bandwidth Part • CCE Control Channel Elements • CG Configured 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 Assignment 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 Radio Base Station • gNB-DU New Radio 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 Co-Located • 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 Scheduled • SR Scheduling Request • SRS Sounding Reference Signal • SS Search Space • SSB Synchronization Signal Block • TCI Transmission Configuration Indicator • UDM Unified Data Management • UE User Equipment • UPF User Plane Function • USS UE Specific Search Space [0217] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.