DCI-triggered HARQ-ACK codebook retransmission

Abstract

A user equipment (UE) configured for hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook determination in a fifth generation (5G) new radio (NR) network may decode a downlink control information (DCI) format received from a generation NodeB (gNB). When the DCI format triggers a HARQ-ACK codebook retransmission, the UE may determine the HARQ-ACK codebook to be retransmitted based on a time offset indicated in the DCI format. To determine the HARQ-ACK codebook to be retransmitted, the UE may determine an uplink (UL) slot that included an initial transmission of the HARQ-ACK codebook based on subtracting a time offset from a DL slot that included the DCI. The UE may also encode a physical uplink control channel (PUCCH) to include the determined HARQ-ACK codebook to be retransmitted in the UL slot based on the slot offset.

Description

[Technical Field]

[0001] [Priority Claim] This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 251,534 [Reference No. AD9328-Z], filed October 1, 2021, and U.S. Provisional Patent Application No. 63 / 276,436 [Reference No. AE0155-Z], filed November 5, 2021, each of which is incorporated by reference herein in its entirety.

[0002] Embodiments relate to wireless communications. Some embodiments relate to wireless networks, including 5G networks, including 3GPP (Third Generation Partnership Project) and Fifth-Generation (5G) New Radio (NR) (or 5G-NR) networks. Some embodiments relate to Sixth-Generation (6G) networks. Some embodiments relate to Ultra-Reliable Low-Latency Communication (URLLC). [Background technology]

[0003] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated, integrated communications platforms. The use of 3GPP 5G NR systems is increasing with the proliferation of different types of devices communicating with various network devices. The penetration of mobile devices (user equipment or UE) in modern society continues to drive the demand for a variety of network-connected devices in many different environments. 5G NR wireless systems are emerging and are expected to deliver even higher speeds, connectivity, and availability, while also increasing throughput, coverage, and robustness and reducing latency and operational and capital costs. 5G-NR networks will continue to evolve based on 3GPP LTE-Advanced with additional potential new radio access technologies (RATs) to enrich people's lives with seamless wireless connectivity solutions that deliver high-speed, rich content and services. As current cellular network frequencies are saturated, higher frequencies, such as millimeter wave (mmWave) frequencies, may be beneficial due to their higher bandwidth.

[0004] Current 5G NR networks are concerned with enhancing NR technologies to support Ultra-Reliable Low-Latency Communications (URLLC) and the Industrial Internet-of-Things (IIoT), particularly enhancing Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) feedback from UEs. One issue is the retransmission of dropped or canceled HARQ-ACK feedback. [Brief explanation of the drawings]

[0005] [Figure 1A] 1 illustrates a network architecture according to some embodiments.

[0006] [Figure 1B]1 illustrates a non-roaming 5G system architecture according to some embodiments. [Figure 1C] 1 illustrates a non-roaming 5G system architecture according to some embodiments.

[0007] [Figure 2A] 1 is an example illustrating the deferral of both low-priority (LP) and high-priority (HP) Semi-Persistent Scheduled (SPS) HARQ-ACKs to different target slots, according to some embodiments.

[0008] [Figure 2B] 1 is an example illustrating the deferral of both a LP SPS HARQ-ACK and a HP SPS HARQ-ACK to the same target slot, where the deferred LP SPS HARQ-ACK and HP SPS HARQ-ACK are co-coded within the target slot, according to some embodiments.

[0009] [Figure 2C] 10 is an example showing the deferral of both an LP SPS HARQ-ACK and an HP SPS HARQ-ACK to the same target slot determined by the HP SPS HARQ-ACK, where the deferred LP SPS HARQ-ACK and HP SPS HARQ-ACK are coded separately within the target slot.

[0010] [Figure 3] 1 illustrates a Physical Uplink Control Channel (PUCCH) transmission triggered by a Downlink Control Information (DCI) format, according to some embodiments.

[0011] [Figure 4] 1 illustrates a functional block diagram of a wireless communication device according to some embodiments.

[0012] [Figure 5A] 1 illustrates a HARQ-ACK codebook retransmission according to some embodiments. [Figure 5B] 1 illustrates a HARQ-ACK codebook retransmission according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0013] The following description and drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice the embodiments. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in or substituted for those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0014] In some embodiments, a user equipment (UE) configured for hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook determination in a fifth-generation (5G) new radio (NR) network may decode a downlink control information (DCI) format received from a generation NodeB (gNB). When the DCI format triggers a HARQ-ACK codebook retransmission, the UE may determine the HARQ-ACK codebook to be retransmitted based on a time offset indicated in the DCI format. To determine the HARQ-ACK codebook to be retransmitted, the UE may determine an uplink (UL) slot that included an initial transmission of the HARQ-ACK codebook based on subtracting the time offset from the DL slot that included the DCI. The UE may also encode a physical uplink control channel (PUCCH) to include the determined HARQ-ACK codebook to be retransmitted in the UL slot based on the slot offset. These embodiments are described in more detail below.

[0015] Some embodiments are directed to a generation NodeB (gNB) configured for operation in a fifth-generation (5G) New Radio (NR) network. In these embodiments, for a user equipment (UE) configured for hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook determination, the gNB may determine a HARQ-ACK codebook to be retransmitted by the UE and encode a downlink control information (DCI) format for transmission to the UE that triggers the HARQ-ACK codebook retransmission. In these embodiments, the DCI format may be encoded to include a time offset used by the UE to determine the HARQ-ACK codebook to be retransmitted. The gNB may decode a physical uplink control channel (PUCCH) that includes the retransmitted HARQ-ACK codebook. These embodiments are described in more detail below.

[0016] 1A illustrates a network architecture according to some embodiments. Network 140A is shown to include user equipment (UE) 101 and UE 102. UEs 101 and 102 are shown as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a personal digital assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handset, a drone, or any other computing device that includes a wired and / or wireless communication interface. UEs 101 and 102 may be collectively referred to herein as UE 101, which may be used to perform one or more of the techniques disclosed herein.

[0017] Any of the wireless links described herein (e.g., used in network 140A or any other illustrated network) may operate according to any example wireless communication technology and / or standard.

[0018] LTE and LTE Advanced are standards for high-speed data wireless communications for UEs, such as mobile phones. In LTE Advanced and various wireless systems, carrier aggregation is a technique according to which multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thereby increasing the bandwidth available to a single device. In some embodiments, carrier aggregation may be used when one or more component carriers operate on unlicensed frequencies.

[0019] The embodiments described herein may be used in the context of any spectrum management scheme, including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and beyond, and Spectrum Access System (SAS) in 3.55-3.7 GHz and beyond).

[0020] The embodiments described herein can also be applied to different single carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, Filter Bank Based Multi-Carrier (FBMC), OFDMA, etc.) and in particular to 3GPP NR (New Radio) by allocating OFDM carrier data bit vectors to corresponding symbol resources.

[0021] In some embodiments, either of the UEs 101 and 102 may comprise an Internet of Things (IoT) UE or a cellular IoT (CIoT) UE, which may have a network access layer designed for low-power IoT applications utilizing temporary UE connections. In some embodiments, either of the UEs 101 and 102 may comprise a narrowband (NB) IoT UE (e.g., enhanced NB-IoT (eNB-IoT) UE and further enhanced (FeNB-IoT) UE). IoT UEs may utilize technologies such as public land mobile networks (PLMNs), proximity-based services (ProSe) or device-to-device (D2D) communications, sensor networks, or machine-to-machine (M2M) or machine-type communications (MTC) to exchange data with an MTC server or device over an IoT network. M2M or MTC exchanges of data may be machine-initiated exchanges of data. An IoT network includes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with temporary connections. The IoT UE may run background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0022] In some embodiments, either of the UEs 101 and 102 may include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0023] The UEs 101 and 102 may be configured to connect to, e.g., be communicatively coupled to, a radio access network (RAN) 110. The RAN 110 may be, e.g., an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which includes a physical communication interface or layer (discussed in more detail below); in this example, connections 103 and 104 are shown as air interfaces enabling the communicative coupling and may conform to cellular communication protocols such as a Global System for Mobile Communications (GSM) protocol, a Code Division Multiple Access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT Over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a 5th Generation (5G) protocol, a New Radio (NR) protocol, and the like.

[0024] In an aspect, the UEs 101 and 102 may further directly exchange communication data via the ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface that includes one or more logical channels, including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0025] The UE 102 is shown as being configured to access an access point (AP) 106 via a connection 107. The connection 107 may include a local wireless connection, such as any IEEE 802.11 protocol-compliant connection according to which the AP 106 may include a Wireless Fidelity (WiFi) router. In this example, the AP 106 is shown as being connected to the Internet without connecting to a core network of a wireless system (described in more detail below).

[0026] The RAN 110 may include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) may be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next-generation NodeBs (gNBs), RAN nodes, etc., and may include terrestrial stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). In some embodiments, the communication nodes 111 and 112 may be transmit / receive points (TRPs). In cases where the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs may function within the communication cell of the NodeB. The RAN 110 may include one or more RAN nodes that provide a macrocell, e.g., a macro RAN node 111, and one or more RAN nodes that provide a femtocell or picocell (e.g., a cell with a smaller coverage area, lower user capacity, or higher bandwidth compared to a macrocell), e.g., a low-power (LP) RAN node 112.

[0027] Either of RAN nodes 111 and 112 may terminate air interface protocols and may be the first point of contact for UEs 101 and 102. In some embodiments, either of RAN nodes 111 and 112 may perform various logical functions for the RAN 110, including, but not limited to, radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and radio network controller (RNC) functions such as mobility management. In examples, either of nodes 111 and / or 112 may be a new generation NodeB (gNB), an evolved NodeB (eNB), or another type of RAN node.

[0028] The RAN 110 is shown as communicatively coupled to a core network (CN) 120 via an S1 interface 113. In an embodiment, the CN 120 may be an evolved packet core (EPC) network, a next-generation packet core (NPC) network, or some other type of CN (e.g., as shown with reference to FIGS. 1B-1C). In this aspect, the S1 interface 113 is divided into two parts: an S1-U interface 114 that carries traffic data between the RAN nodes 111 and 112 and a serving gateway (S-GW) 122, and an S1-mobility management entity (MME) interface 115 that is a signaling interface between the RAN nodes 111 and 112 and an MME 121.

[0029] In this aspect, the CN 120 includes an MME 121, an S-GW 122, a Packet Data Network (PDN) Gateway (P-GW) 123, and a Home Subscriber Server (HSS) 124. The MME 121 may be functionally similar to the control plane of a legacy Serving General Packet Radio Service (GPRS) Support Node (SGSN). The MME 121 may manage mobility aspects of access, such as gateway selection and tracking area list management. The HSS 124 may include a database for network users, including subscription-related information to support handling of communication sessions by network entities. The CN 120 may include one or several HSSs 124s, depending on the number of mobile subscribers, device capabilities, network organization, etc. For example, the HSS 124 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc.

[0030] The S-GW 122 terminates the S1 interface 113 towards the RAN 110 and may route data packets between the RAN 110 and the CN 120. Additionally, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and may provide an anchor for inter-3GPP mobility. Other roles of the S-GW 122 may include lawful interception, charging, and some policy enforcement.

[0031] The P-GW 123 may terminate the SGi interface toward the PDN. The P-GW 123 may route data packets between the EPC network 120 and external networks, such as a network including an application server 184 (alternatively referred to as an application function (AF)), via an Internet Protocol (IP) interface 125. The P-GW 123 may also communicate data to other external networks 131A, which may include the Internet, an IP Multimedia Subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element that provides applications that use IP bearer resources in conjunction with a core network (e.g., a UMTS packet service (PS) domain, an LTE PS data service, etc.). In this aspect, the P-GW 123 is shown as communicatively coupled to the application server 184 via the IP interface 125. The application server 184 may also be configured to support one or more communication services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.

[0032] The P-GW 123 may also be a policy enforcement and charging data collection node. The Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some embodiments, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with the UE's IP-CAN session: a Home PCRF (H-PCRF) in the HPLMN and a Visited PCRF (V-PCRF) in the Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0033] In some embodiments, the communication network 140A may be an IoT network or a 5G network, including a 5G New Radio Network that uses communications in licensed (5G NR) and unlicensed (5G NR-U) spectrum. One of the current enablers of IoT is Narrowband IoT (NB-IoT).

[0034] The NG system architecture may include a RAN 110 and a 5G network core (5GC) 120. The NG-RAN 110 may include multiple nodes, such as a gNB and an NG-eNB. The core network 120 (e.g., a 5G core network or 5GC) may include an access and mobility function (AMF) and / or a user plane function (UPF). The AMF and UPF may be communicatively coupled to the gNB and the NG-eNB via an NG interface. More specifically, in some embodiments, the gNB and the NG-eNB may be connected to the AMF by an NG-C interface and to the UPF by an NG-U interface. The gNB and the NG-eNB may be coupled to each other via an Xn interface.

[0035] In some embodiments, the NG system architecture may use reference points between various nodes such as those provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12). In some embodiments, each of the gNB and NG-eNB may be implemented as a base station, a mobile edge server, a small cell, a home eNB, etc. In some embodiments, in a 5G architecture, the gNB may be a master node (MN) and the NG-eNB may be a secondary node (SN).

[0036] FIG. 1B illustrates a non-roaming 5G system architecture according to some embodiments. Referring to FIG. 1B, a 5G system architecture 140B is illustrated in a reference point representation. More specifically, a UE 102 can communicate with a RAN 110 and one or more other 5G Core (5GC) network entities. The 5G system architecture 140B includes multiple network functions (NFs), such as an access and mobility management function (AMF) 132, a session management function (SMF) 136, a policy control function (PCF) 148, an application function (AF) 150, a user plane function (UPF) 134, a network slice selection function (NSSF) 142, an authentication server function (AUSF) 144, and a unified data management (UDM) / home subscriber server (HSS) 146. The UPF 134 can provide connectivity to a data network (DN) 152, which may include, for example, operator services, internet access, or third-party services. The AMF 132 may be used to manage access control and mobility and may also include a network slice selection function. The SMF 136 may be configured to set up and manage various sessions according to network policies. The UPF 134 may be deployed in one or more configurations according to the desired service type. The PCF 148 may be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to a PCRF in a 4G communication system). The UDM may be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0037] In some embodiments, the 5G system architecture 140B includes multiple IP multimedia core network subsystem entities, such as an IP Multimedia Subsystem (IMS) 168B and a Call Session Control Function (CSCF). More specifically, the IMS 168B includes a CSCF, which can function as a Proxy CSCF (P-CSCF) 162B, a Serving CSCF (S-CSCF) 164B, an Emergency CSCF (E-CSCF) (not shown in FIG. 1B), or an Interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first point of contact for the UE 102 within the IM Subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle session state in the network, and the E-CSCF can be configured to handle specific aspects of the emergency session, such as routing emergency requests to the correct emergency center or PSAP. The I-CSCF 166B may be configured to act as a contact point within a network operator's network for all IMS connections destined for that network operator's subscribers or roaming subscribers currently located within that network operator's service area. In some embodiments, the I-CSCF 166B may connect to another IP multimedia network 170E, for example, an IMS operated by a different network operator.

[0038] In some embodiments, UDM / HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS). AS 160B can be coupled to IMS 168B via S-CSCF 164B or I-CSCF 166B.

[0039] 1B shows the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), N11 1B , N11 (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the AMF 132 in the case of a non-roaming scenario, or between the PCF 148 and the visited network and the AMF 132 in the case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between the AMF 132 and the NSSF 142, not shown). Other reference point representations not shown in FIG. 1B may also be used.

[0040] 1C shows a 5G system architecture 140C and a service-based representation. In addition to the network entities shown in FIG. 1B, the system architecture 140C may also include a network publication function (NEF) 154 and a network repository function (NRF) 156. In some embodiments, the 5G system architecture may be service-based, and interactions between network functions may be represented by corresponding point-to-point reference points N or as service-based interfaces.

[0041] 1C , a service-based representation can be used to represent network functions in the control plane that allow other authorized network functions to access those services. In this regard, the 5G system architecture 140C can include the following service-based interfaces: Namf 158H (a service-based interface presented by the AMF 132), Nsmf 158I (a service-based interface presented by the SMF 136), Nnef 158B (a service-based interface presented by the NEF 154), Npcf 158D (a service-based interface presented by the PCF 148), Nudm 158E (a service-based interface presented by the UDM 146), Naf 158F (a service-based interface presented by the AF 150), Nnrf 158C (a service-based interface presented by the NRF 156), Nnssf 158A (a service-based interface presented by the NSSF 142), Nausf 158G (a service-based interface presented by the AUSF 144). Other service-based interfaces not shown in FIG. 1C (eg, Nudr, N5g-eir, and Nudsf) can also be used.

[0042] In some embodiments, any of the UEs or base stations described in connection with FIGS. 1A-1C may be configured to perform the functions described herein.

[0043] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated, integrated communications platforms. The next-generation wireless communications system, 5G, or New Radio (NR), will provide access to information and sharing of data anywhere, anytime by a variety of users and applications. NR is expected to be an integrated network / system aimed at satisfying vastly different and sometimes conflicting performance dimensions and services. These diverse multi-dimensional requirements are driven by different services and applications. Overall, NR will evolve based on 3GPP LTE-Advanced with additional potential new radio access technologies (RATs) to enrich people's lives with better, simpler, and seamless wireless connectivity solutions. NR will enable everything to be connected wirelessly, delivering high-speed, rich content and services.

[0044] Rel-15 NR systems are designed to operate on licensed spectrum. NR Unlicensed (NR-U), shorthand for NR-based access to unlicensed spectrum, is the technology that enables NR systems to operate on unlicensed spectrum.

[0045] As mentioned above, one issue with enhancing NR technology to support Ultra-Reliable Low-Latency Communications (URLLC) and the Industrial Internet of Things (IIoT) is the retransmission of dropped or canceled HARQ feedback. NR's achievable latency and reliability performance is key to supporting use cases with more stringent requirements. Dropping of SPS HARQ-ACK in the TDD case can be due to PUCCH collision with at least one DL or flexible symbol. Areas for possible solutions include: SPS HARQ skipping for "skipped" SPS PDSCH PUCCH repetition enhancement (at least for HARQ-ACK), e.g., sub-slot based, etc. Retransmission of canceled HARQ SPS HARQ payload size reduction and / or skipping for "non-skipped" SPS PDSCH Type 1 HARQ codebook based on sub-slot PUCCH structure PUCCH carrier switching for HARQ feedback

[0046] One of the problems to be solved is the retransmission of dropped or cancelled HARQ feedback that may occur due to: · Unable to map UCI to HARQ-ACK on available uplink symbols due to collision with quasi-static or dynamic DL, SSB, CORESET#0 symbols. Overlap with a UL channel with higher priority when the multiplexing option is not enabled. Cancellation by the gNB using a UL cancellation indication or other mechanism.

[0047] Another issue concerns SPS HARQ-ACK deferral. Currently, this mechanism does not handle the case of PUCCH repetition across slots or sub-slots. This mechanism does not handle the case of SPS deferral due to intra-UE multiplexing between different priorities. The embodiments disclosed herein provide: · Handling of PUCCH repetitions when SPS HARQ-ACK deferral is enabled. · Handling of SPS HARQ-ACK deferral when the UE is configured / instructed to perform intra-UE multiplexing between different priorities. Handling of missed DCI scheduling PDSCH in case of one-shot dropped PUCCH retransmission. · SPS HARQ-ACK postponed

[0048] Repetition handling: In 3GPP RAN Working Group 1 (WG1), there is already agreement on how to determine the deferral conditions from the initial slot / subslot to intermediate slots / subslots, and how to determine the target slot / subslot. Such determinations are made under the assumption of a single PUCCH transmission over a single slot / subslot. However, further clarification is needed regarding UE behavior when PUCCH is operated with slot or subslot repetition. Several issues exist:

[0049] Question 1: Whether to consider only the initial PUCCH repetitions, or all PUCCH repetitions, or a subset of PUCCH repetitions to check the deferral condition.

[0050] Since the deferral is checked taking into account all multiplexing results, the initial PUCCH repetitions are likely to be easier to handle. Alternatively, at least one iteration from the number of iterations may be checked for validity, i.e., the deferral process is stopped if at least one iteration can be mapped to a candidate slot / subslot. In another example, the number of iterations to be checked for validity may be configured by higher layers from 1 to the (maximum) number of PUCCH repetitions. Furthermore, the number of iterations to be checked for validity may be defined relative to the total number of iterations for which the PUCCH was originally scheduled or configured; for example, the number of iterations to be checked for validity may be determined as a floor (f*R), where "f" is a configured or specified factor and "R" is the total number of PUCCH repetitions. It should be noted that requiring the UE to map all PUCCH repetitions may often result in excessive deferrals and drops.

[0051] In one example, if a UE is configured with slot-based or subslot-based PUCCH repetitions and is indicated with more than one PUCCH repetition, and the corresponding SPS HARQ-ACK carried by the repetition is enabled with deferral, only the conditions for mapping the initial PUCCH repetition from multiple PUCCH repetitions may be checked for deferral.

[0052] In another example, if a UE is configured with slot-based or subslot-based PUCCH repetitions and is indicated with more than one PUCCH repetition, and the corresponding SPS HARQ-ACK carried by the repetition is enabled for deferral, the conditions for mapping of all PUCCH transmissions from multiple PUCCH transmissions may be checked for deferral, i.e., only when all PUCCH repetitions can be mapped to valid UL slots / subslots, no further deferral is performed.

[0053] In yet another example, if a UE is configured with slot-based or subslot-based PUCCH repetitions and is indicated with more than one PUCCH repetition, and the corresponding SPS HARQ-ACK carried by that repetition is enabled with deferral, the condition for the mapping of each PUCCH transmission from multiple PUCCH transmissions may be checked for deferral. If at least X PUCCH repetitions can be mapped to valid UL slots / subslots, deferral is not performed, where X may be fixed to 1 or may be configurable from 1 to the number of PUCCH repetitions.

[0054] Problem 2: Behavior when postponed repeat PUCCH cannot be mapped to some repetitions. When the postponement is stopped by fulfilling a condition, some PUCCH repetitions still cannot be mapped. They are assumed to be dropped according to the R15 / 16 procedure.

[0055] Problem 3: According to the current specification, when a PUCCH consists of PUCCH repetitions, overlap of such PUCCHs of different types is either not expected or is resolved by dropping the one that starts later or has a lower priority. If SPS HARQ-ACK deferral is enabled, this rule may further complicate the procedure, since the same starting slot / subslot for different UCI types may not be avoided by scheduling due to the allowed deferral.

[0056] In one example, if the SPS HARQ-ACK is configured with deferral enabled, the UE:

number

[0057] When one of the UCIs includes an SPS HARQ-ACK with deferral enabled, the UE may expect that either the first PUCCH or the second PUCCH starts in the same slot and includes a UCI type with the same priority. In this case, one of the following dropping rules may be applied: If there are UCIs of different types with the same priority, the UCI including the SPS HARQ-ACK is dropped and the other UCI is transmitted; or, if there are UCIs of different types with the same priority, the UCI including the SPS HARQ-ACK is retained and the other UCI is dropped.

[0058] Interaction with intra-UE multiplexing / prioritization with different priorities: In 3GPP RAN Working Group 1 (WG1), it has already been agreed that a UE can be indicated for intra-UE multiplexing with different priorities. This indication can be higher layer signaling, e.g., RRC signaling, or dynamic signaling, e.g., by DCI. When intra-UE multiplexing with different priorities is indicated for overlapping UL channels with different priorities, the UE can multiplex UCI with priority i onto PUCCH or PUSCH with priority j. In general, intra-UE multiplexing / prioritization between different priorities involves two steps. Step 1 resolves overlapping UL channels with the same priority, and step 2 resolves overlapping UL channels with different priorities. The result of step 2 can be multiplexing of different priorities or cancellation of lower priorities. For example, if in step 2 an LP (low priority with priority index 0) PUCCH is overlapped with an HP (high priority with priority index 1) PUCCH and intra-UE multiplexing with different priorities is indicated, the UE transmits an HP PUCCH carrying both the LP HARQ-ACK and the HP HARQ-ACK. In another example, if in step 2 an LP PUCCH, an HP PUCCH, and an HP PUSCH are overlapped and intra-UE multiplexing with different priorities is indicated, the UE transmits an HP PUSCH carrying both the LP HARQ-ACK and the HP HARQ-ACK.

[0059] For an SPS with priority i configured in spsHARQdeferral (i.e., when SPS HARQ-ACK deferral is activated for the SPS configuration), the UE decides whether to defer the SPS HARQ-ACK from the first slot to the second slot according to at least one of the following rules:

[0060] The decision to defer SPS or not is made after step 2 of intra-UE multiplexing / prioritization (if applicable).

[0061] Alternative 1: For an SPS HARQ-ACK with priority i, after resolving overlapping PUCCH / PUSCH (if applicable) with different priorities, and if the UE would transmit the SPS HARQ-ACK using an invalid PUCCH SPS-PUCCH-AN-List-r16 or n1PUCCH-AN, the SPS HARQ-ACK with priority i is postponed.

[0062] In one example, if the HARQ-ACKs to be postponed include both LP HARQ-ACKs and HP HARQ-ACKs, the target slot (second slot) is determined separately for the LP HARQ-ACKs and HP HARQ-ACKs after performing intra-UE multiplexing / prioritization within the target slot.

[0063] 2A provides an example. In FIG. 2A, both the LP SPS HARQ-ACK and the HP SPS HARQ-ACK in slot n are postponed, but the target slots for the postponed LP SPS HARQ-ACK and the HP SPS HARQ-ACK are different. If the UE transmits the first LP SPS HARQ-ACK and the first HP SPS HARQ-ACK using the HP PUCCH resource in slot n and the HP PUCCH resource is invalid, the UE determines to postpone both the first LP SPS HARQ-ACK and the HP SPS HARQ-ACK. To find the target slot, if the UL channel of the LP result for the first LP SPS HARQ-ACK and the second LP HARQ-ACK or the LP UL-SCH (if applicable) is an LP PUCCH resource that does not overlap with the UL channel of the HP result for the first HP SPS HARQ-ACK and the second HP HARQ-ACK or the HP UL-SCH (if applicable) in slot n+1, the UE checks the validity of the UL channel of the LP result and the UL channel of the HP result, respectively, and decides whether to further postpone the LP SPS HARQ-ACK and the HP SPS HARQ-ACK, respectively. For example, if the UL channel of the HP result is valid while the UL channel of the LP result (LP SPS PUCCH resource) is invalid, then slot n+1 is the target slot for the first HP SPS HARQ-ACK, while slot n+1 is not the target slot for the first LP SPS HARQ-ACK. The UE needs to find a later slot as the target slot for the first LP SPS HARQ-ACK and the second LP SPS HARQ-ACK (if applicable). Note that the LP HARQ-ACK and the HP HARQ-ACK are coded separately, at least when the number of bits is greater than 2.

[0064] In another example, when the HARQ-ACKs to be postponed include both LP HARQ-ACKs and HP HARQ-ACKs, the target slot (second slot) is determined jointly for the LP HARQ-ACKs and HP HARQ-ACKs after performing intra-UE multiplexing / prioritization within the target slot. The postponed LP HARQ-ACKs are coded together with the HP HARQ-ACKs in the target slot. Figure 2B provides an example. In Figure 2B, both the LP SPS HARQ-ACK and the HP SPS HARQ-ACK in slot n are postponed to the same target slot, and the postponed LP SPS HARQ-ACK and the HP SPS HARQ-ACK are coded together in the target slot.

[0065] Alternatively, the UE determines a target slot for the deferred HP HARQ-ACK and applies the target slot to the LP HARQ-ACK, but performs separate coding for the deferred LP HARQ-ACK and the HP HARQ-ACK. In this case, if the UE cannot transmit the deferred LP HARQ-ACK in the target slot, the UE drops the deferred LP HARQ-ACK. Figure 2C provides an example. In Figure 2C, both the LP SPS HARQ-ACK and the HP SPS HARQ-ACK in slot n are deferred to the same target slot determined by the HP. The deferred LP SPS HARQ-ACK and the HP SPS HARQ-ACK are coded separately within the target slot.

[0066] Alternative 2: For an SPS HARQ-ACK with priority i, after resolving overlapping PUCCH / PUSCH (if applicable) with different priorities, and if the UE would transmit the SPS HARQ-ACK using a PUCCH SPS-PUCCH-AN-List-r16 configured for priority i or n1PUCCH-AN configured for priority i that is not valid, the SPS HARQ-ACK with priority i is postponed.

[0067] In this case, if there is a LP SPS HARQ-ACK and a HP SPS HARQ-ACK in the first slot, after resolving the overlapping PUCCH / PUSCH with different priorities, the UE will transmit the SPS HARQ-ACK using the HP PUCCH SPS-PUCCH-AN-List-r16 or n1PUCCH-AN, and the PUCCH resource is invalid, so the HP SPS HARQ-ACK is postponed while the LP SPS HARQ-ACK is dropped. Compared with Alternative 1, the transmission probability of the LP HARQ-ACK is reduced, but the implementation is simpler.

[0068] Whether to postpone an SPS is decided after step 1 of intra-UE multiplexing and / or prioritization, regardless of whether there is a subsequent step 2. For an SPS HARQ-ACK with priority i, after resolving overlapping PUCCH / PUSCH with the same priority (step 1), and if the UE would transmit the SPS HARQ-ACK using an inactive PUCCH SPS-PUCCH-AN-List-r16 with priority i or an n1PUCCH-AN with priority i, the SPS HARQ-ACK with priority i is postponed.

[0069] The postponement of SPS HARQ-ACKs with different priorities is postponed separately. If there are overlapping UL channels with different priorities in a slot and the UL channel resulting from step 2 is a valid UL channel, the UE transmits the resulting UL channel with the multiplexed SPS HARQ-ACK regardless of whether it is determined to postpone the SPS HARQ-ACK to another slot. Alternatively, if it is not determined to postpone the SPS HARQ-ACK to another slot, the UE transmits the resulting UL channel with the multiplexed SPS HARQ-ACK.

[0070] In the above embodiments, if a PUCCH resource overlaps with a symbol indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigDedicated, or indicated for an SS / PBCH block by ssb-PositionsInBurst, or indicated for CORESET#0, the PUCCH resource is invalid.

[0071] In the above embodiment, if the time difference between the target slot and the initial slot is greater than the maximum deferral time, the deferred SPS HARQ-ACK is dropped.

[0072] HARQ-ACK retransmission

[0073] 3 illustrates a Physical Uplink Control Channel (PUCCH) transmission triggered by a Downlink Control Information (DCI) format, according to some embodiments. One-shot triggering of HARQ-ACK retransmission assumes that the DCI indicates which PUCCH in which slot / subslot needs to be retransmitted (e.g., due to dynamic dropping or failed reception at the gNB), as shown in FIG. 3. In the case of a one-shot trigger, the PUCCH that needs to be retransmitted will be indicated. The simplest option to indicate the CB for retransmission is to provide a time offset into the past from the DCI reception that triggers the retransmission. There may be issues with the payload:

[0074] Problem 1: Due to the incorrect detection of DCI that schedules PDSCH and the corresponding HARQ-ACK, a dropped (or transmitted) PUCCH may not be reliably constructed. When this PUCCH is requested to be retransmitted, the payload of the retransmitted PUCCH may not be known. To solve this, one or more of the following solutions may be applied:

[0075] In one example, for type 2 CB, an additional total DAI or continuity counter DAI may be used to derive the CB size of the PUCCH in the slot / sub-slot indicated for retransmission.

[0076] In another example, for Type 2 CB, the DCI with a retransmission of the HARQ-ACK codebook may indicate an additional time offset from the PUCCH resource into the past for the new HARQ-ACK, in which case the UE is assumed to continue CB construction from the indicated PUCCH resource in the past to the PUCCH resource in the future. In other words, the UE assumes that the previous or original PUCCH resource will be used for the retransmission, and it continues counting HARQ-ACK bits using a counter DAI that includes the DAI from the DCI requesting the PUCCH retransmission and the total DAI. In an example, the time offset may be indicated in terms of the number of slots corresponding to the subcarrier spacing (SCS) of the active UL BWP to which the PUCCH is mapped. Furthermore, to distinguish between multiple PUCCH resources within a potentially affected slot, a reference to one of multiple possible PUCCHs may be provided to the UE via a combination of a slot offset referencing the previous slot and a PUCCH resource indication (PRI) for the indicated slot. In this case, the UE may not expect the same HARQ process ID for the CC to be indicated in the new DCI and associated with the HARQ codebook payload in the retransmitted PUCCH.

[0077] In one example, the UE may not be expected to be requested to retransmit a PUCCH of a first priority by a DCI indication including a second priority, i.e., triggering of PUCCH retransmission by DCI of a different priority is not supported.

[0078] In an example, for the same codebook type, in the case of a type-1 codebook, the codebook size may still be an issue. For a type-1 codebook, there is one special case where the UE transmits only a 1-bit HARQ-ACK or only a HARQ-ACK for the SPS PDSCH when the UE does not receive any DCI or receives only one DCI with DCI1_0 with a specific DAI value. For other cases, the UE generates a type-1 codebook (usually with a much larger size). One way to avoid such ambiguity is to always generate a type-1 codebook for dropped PUCCHs (even when the UE has only an SPS PDSCH HARQ-ACK to transmit or receives only one DCI with DCI1_0 with a specific DAI value).

[0079] Problem 2: A potentially rare event can occur when a gNB requests a PUCCH / CB retransmission that the UE initially missed completely, i.e., the UE did not receive any DCI scheduling HARQ-ACK feedback in the requested PUCCH. To handle it, either all information about the CB type and its size needs to be provided in the trigger DCI, or the UE can assume some default parameters or drop this requested PUCCH transmission.

[0080] In one example, if the DCI indicates a retransmission of a PUCCH in a slot / subslot that (from the UE's perspective) has not previously been indicated to the UE by any other DCI (i.e., the UE does not recognize any PUCCH in the slot / subslot requested for retransmission), the UE transmits a specific / default payload on the PUCCH. For example, the UE transmits a 1-bit Type 1 CB with a NACK payload. Alternatively, the UE transmits a Type 1 or Type 2 CB with all NACKs.

[0081] In one example, if the DCI indicates a retransmission of a PUCCH in a slot / subslot that (from the UE's perspective) has not been previously indicated to the UE by any other DCI (i.e., the UE does not see any PUCCH in the slot / subslot requested for retransmission), the UE shall assume a null codebook for the retransmitted PUCCH and transmit a new HARQ-ACK only if the DCI schedules a PDSCH. The gNB shall take this information into account, e.g., perform hypothesis testing. If detected, it may understand whether the PUCCH has been dropped or whether the DCI was not received.

[0082] 4 shows a functional block diagram of a wireless communication device, according to some embodiments. The wireless communication device 400 may be suitable for use as a UE or gNB configured for operation in a 5G NR network. The communication device 400 may also be suitable for use as a handheld device, mobile device, cellular phone, smartphone, tablet, netbook, wireless terminal, laptop computer, wearable computing device, femtocell, High Data Rate (HDR) subscriber device, access point, access terminal, or other Personal Communication System (PCS) device.

[0083] The communications device 400 may include communications circuitry 402 and a transceiver 410 that transmits and receives signals to and from other communications devices using one or more antennas 401. The communications circuitry 402 may include circuitry capable of operating physical layer (PHY) communications and / or medium access control (MAC) communications that control access to a wireless medium, and / or any other communications layer that transmits and receives signals. The communications device 400 may also include processing circuitry 406 and memory 408 arranged to perform operations described herein. In some embodiments, the communications circuitry 402 and the processing circuitry 406 may be configured to perform operations detailed in the figures, drawings, and flows above.

[0084] According to some embodiments, the communications circuitry 402 may be configured to contend for the wireless medium and configure frames or packets for communication over the wireless medium. The communications circuitry 402 may be configured to transmit and receive signals. The communications circuitry 402 may also include circuitry for modulation / demodulation, up-conversion / down-conversion, filtering, amplification, etc. In some embodiments, the processing circuitry 406 of the communications device 400 may include one or more processors. In other embodiments, two or more antennas 401 may be coupled to the communications circuitry 402 arranged to transmit and receive signals. The memory 408 may store information for configuring the processing circuitry 406, perform operations for constructing and transmitting message frames, and perform various operations described herein. The memory 408 may include any type of memory, including non-transitory memory, that stores information in a form readable by a machine (e.g., a computer). For example, the memory 408 may include computer-readable storage devices, read-only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, and other storage devices and media.

[0085] In some embodiments, communication device 400 may be part of a portable wireless communication device such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capabilities, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computing device, or another device that may receive and / or transmit information wirelessly.

[0086] In some embodiments, the communications device 400 may include one or more antennas 401. The antennas 401 may include one or more directional or omnidirectional antennas, including, for example, a dipole antenna, a monopole antenna, a patch antenna, a loop antenna, a microstrip antenna, or other types of antennas suitable for transmitting RF signals. In some embodiments, a single antenna with multiple apertures may be used instead of two or more antennas. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated due to spatial diversity and different channel characteristics that may result between each of the antennas and the antenna of the transmitting device.

[0087] In some embodiments, communications device 400 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, a speaker, and other mobile device elements. The display may be an LCD screen, including a touch screen.

[0088] Although communications device 400 is shown as having several separate functional elements, two or more of those functional elements may be combined and implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and / or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio frequency integrated circuits (RFICs), and various combinations of hardware and logic circuits that perform at least the functions described herein. In some embodiments, the functional elements of communications device 400 may refer to one or more processes operating on one or more processing elements.

[0089] 5A and 5B illustrate HARQ-ACK codebook retransmission, according to some embodiments. In both 5A and 5B, the UE receives DCI on the PDCCH in DL slot 502 (DL slot n) that triggers a HARQ-ACK codebook retransmission in the same UL slot 506 (UL slot n+2) (i.e., k=2).

[0090] In Figure 5A, the time offset is 0, so the HARQ-ACK codebook to be retransmitted was originally in UL slot n. In Figure 5A, the retransmitted HARQ-ACK codebook is associated with candidate DL slots and valid PDSCH locations within candidate DL slots 512 and 514. In the example of Figure 5A, the HARQ-ACK codebook payload will be 3 bits corresponding to the three valid PDSCH locations shown.

[0091] In Figure 5B, the time offset is 1, so the HARQ-ACK codebook to be retransmitted was originally transmitted in UL slot n-1. In Figure 5B, the retransmitted HARQ-ACK codebook is associated with candidate DL slots and valid PDSCH locations within candidate DL slots 514 and 516. In the example of Figure 5B, the HARQ-ACK codebook payload will be 7 bits, corresponding to the 7 valid PDSCH locations shown.

[0092] In these embodiments, for Type 1 HARQ-ACK codebooks, the HARQ-ACK codebook payload is based on the candidate DL slots and the valid PDSCH locations in each candidate DL slot (i.e., the sum of the number of valid PDSCHs in all candidate DL slots).

[0093] In some embodiments, for slots of PUCCH transmission on the primary cell, in the case of Type 1 or Type 2 HARQ-ACK codebooks, a UE that transmitted or was to transmit a PUCCH or PUSCH with the first HARQ-ACK codebook in slot m may not schedule PDSCH reception and may be indicated by a DCI format with a CRC scrambled by the C-RNTI or MCS-C-RNTI received in a PDCCH ending in slot n to transmit a PUCCH with the first HARQ-ACK codebook in slot n+k, where slot n+k is after slot m. The UE determines k and resources for PUCCH transmission.

[0094] In these embodiments, m represents the slot of the original transmission of the codebook, n represents the ending slot of the PUCCH in which the DCI was received (i.e., the slot that triggers the retransmission of the codebook), k represents the slot offset (i.e., the number of slots after the slot in which the codebook will be retransmitted), and l represents the time offset indicated in the DCI format.

[0095] In some embodiments, if the pdsch-HARQ-ACK-retx or pdsch-HARQ-ACK-retxDCI-1-2 field value in DCI format 1_1 or 1_2, respectively, is '1', the UE determines slot m as m=nl, where l is determined by a one-to-one mapping between the value of the MCS field in DCI format 1_1 or 1_2 and values ​​from −7 to 24 in ascending order. If DCI format 1_1 or 1_2 includes a priority indicator field with a value, the priority value of the first HARQ-ACK information in the first HARQ-ACK codebook is the same as the value of the priority indicator field; otherwise, the priority value of the first HARQ-ACK information is 0.

[0096] In some embodiments, the PDSCH-Config IE may be used to configure UE-specific PDSCH parameters. In these embodiments, when pdsch-HARQ-ACK-RetxDCI-1-2 is configured, DCI format 1_2 may request the UE to perform HARQ-ACK retransmissions on PUCCH resources. In some embodiments, an RRC configuration information element may be used to configure cell group-specific L1 parameters. In some embodiments, when pdsch-HARQ-ACK-Retx and pdsch-HARQ-ACK-RetxSecondaryPUCCHgroup are configured, DCI format 1_1 may request the UE to perform HARQ-ACK retransmissions on PUCCH resources in the primary PUCCH group and the secondary PUCCH group, respectively.

[0097] In some embodiments, a user equipment (UE) configured for operation in a fifth-generation (5G) new radio (NR) network may be configured for hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook determination. In these embodiments, the UE may decode a downlink control information (DCI) format received from a generation NodeB (gNB). When the DCI format triggers a HARQ-ACK codebook retransmission, the UE may determine the HARQ-ACK codebook to be retransmitted based on a time offset indicated in the DCI format. The UE may also encode a physical uplink control channel (PUCCH) to include the determined HARQ-ACK codebook to be retransmitted. These embodiments are described in more detail below.

[0098] In some embodiments, the DCI format may be received in a physical downlink control channel (PDCCH) terminating in a downlink (DL) slot (i.e., slot n) 502 (see FIGS. 5A and 5B). In these embodiments, to determine the HARQ-ACK codebook to be retransmitted, the UE may determine the uplink (UL) slot (i.e., slot m) 504 that included the initial transmission of the HARQ-ACK codebook based on subtracting a time offset (l) from the DL slot (i.e., slot n) 502 (i.e., the UE determines slot m as m = nl). In these embodiments, the UE may determine which HARQ-ACK codebook to retransmit from multiple initially transmitted HARQ-ACK codebooks based on the time offset indicated in the DCI format. In some embodiments, the time offset (l) may be determined based on the value of a Modulation and Coding Scheme (MCS) field in the DCI format, although the scope of the embodiments is not limited in this respect.

[0099] In some embodiments, the UL slot (i.e., slot m) 504 containing the initial transmission of the HARQ-ACK codebook is the first UL slot. In these embodiments, the UE may also be configured to determine the second UL slot (i.e., slot n+k) 506 for retransmission of the HARQ-ACK codebook based on a slot offset (i.e., k) relative to the DL slot (i.e., slot n) 502 (i.e., the UE determines the slot for retransmission of the HARQ-ACK codebook as slot n+k).

[0100] In the example shown in Figure 5A, the time offset (l) has a value of 0, so the HARQ-ACK codebook transmitted in slot UL slot n-0 (i.e., UL slot n) will be retransmitted in UL slot 506. In the example shown in Figure 5B, the time offset (l) has a value of 1, so the HARQ-ACK codebook transmitted in slot UL slot n-1 will be retransmitted in UL slot 506.

[0101] In some embodiments, the DCI format may be a DCI format for scheduling Physical Downlink Shared Channel (PDSCH) HARQ-ACK retransmissions, comprising one of DCI format 1_1 and DCI format 1_2.

[0102] In some embodiments, the DCI format includes a PDSCH HARQ-ACK transmission indicator (pdsch-HARQ-ACK-retx). In these embodiments, when the UE is configured by Radio-Resource Control (RRC) signaling, the PDSCH HARQ-ACK transmission indicator requests the UE to perform HARQ-ACK retransmissions on PUCCH resources. In some embodiments, the RRC signaling may comprise a PDSCH configuration information element (PDSCH-Config IE) to configure the UE with specific PDSCH parameters.

[0103] In some embodiments, when the DCI format further includes a priority indicator field having a value, the value indicates the priority of the HARQ-ACK information in an initial transmission of the HARQ-ACK codebook, and the value indicates the priority of the HARQ-ACK information for a retransmission of the HARQ-ACK codebook triggered by the DCI format.

[0104] In some embodiments, when the DCI format does not include a priority indicator field, the priority of the HARQ-ACK information for retransmission of the HARQ-ACK codebook is 0. In these embodiments, a bit field with one bit to represent priority may be configured to be present or absent in the DCI. When this bit field is configured, "0" is for lower priority (LP) and "1" is for higher priority (HP). When this bit field is not configured (i.e., when the DCI format includes a priority indicator field with no value), lower priority is assumed, which corresponds to "0". Thus, the gNB may trigger a retransmission of the LP HARQ-ACK only when the field is not configured. In other words, when the gNB uses a DCI format without this bit field, the gNB may trigger only PUCCH slot m carrying the LP HARQ-ACK, and the LP HARQ-ACK is retransmitted. On the other hand, the gNB cannot use a DCI format without this bit field to trigger PUCCH slot m carrying the HP HARQ-ACK.

[0105] In some embodiments, the UE may also be configured to generate a HARQ-ACK codebook based on valid PDSCH locations in one or more candidate DL slots. The UE may also be configured to transmit an initial PUCCH carrying an initial transmission of the HARQ-ACK codebook in a first UL slot (i.e., slot m) 504 and a second PUCCH carrying a retransmission of the HARQ-ACK codebook in a second UL slot (i.e., slot n+k) 506.

[0106] In the example shown in FIG. 5A, the HARQ-ACK codebook to be retransmitted is generated based on valid PDSCH locations DL slot n-2 514 and DL slot n-1 512. In this example, there are three valid PDSCH locations DL slot n-2 514 and DL slot n-1 512, and therefore the HARQ-ACK payload may be 3 bits. In the example shown in FIG. 5B, the HARQ-ACK codebook to be retransmitted is generated based on valid PDSCH locations DL slot n-3 516 and DL slot n-2 514. In these examples, there are seven valid PDSCH locations DL slot n-3 516 and DL slot n-2 514, and therefore the payload may be 7 bits. To generate the HARQ-ACK codebook, the UE may decode the PDSCH received at the valid locations, although the scope of embodiments is not limited in this respect.

[0107] In some embodiments, the HARQ-ACK codebook may be generated based on one of Type 1 and Type 2 HARQ-ACK codebook determination. In these embodiments, for Type 1 HARQ-ACK codebook determination, the HARQ-ACK codebook may be a semi-static fixed-size codebook. In these embodiments, for Type 2 HARQ-ACK codebook determination, the HARQ-ACK codebook may be a dynamic codebook. In some embodiments, the HARQ-ACK codebook may be generated for downlink transmissions scheduled on semi-persistent scheduling (SPS) resources, although the scope of the embodiments is not limited in this respect.

[0108] In some embodiments, the UE may include processing circuitry that may comprise a baseband processor, and in these embodiments, the PDCCH may be received by the UE using two or more antennas. The UE may also include a memory configured to store a HARQ-ACK codebook determined to be retransmitted.

[0109] Some embodiments are directed to a non-transitory computer-readable storage medium storing instructions for execution by a processing circuit of a user equipment (UE) configured for hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook determination operation in a fifth-generation (5G) new radio (NR) network. In these embodiments, the processing circuit may be configured to decode a downlink control information (DCI) format received from a next-generation NodeB (gNB). When the DCI format triggers a HARQ-ACK codebook retransmission, the processing circuit may be configured to determine a HARQ-ACK codebook to be retransmitted based on a time offset indicated in the DCI format and encode a physical uplink control channel (PUCCH) to include the determined HARQ-ACK codebook to be retransmitted.

[0110] Some embodiments are directed to a generation NodeB (gNB) configured for operation in a fifth-generation (5G) New Radio (NR) network. In these embodiments, for a user equipment (UE) configured for hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook determination, the gNB may encode a downlink control information (DCI) format for transmission to the UE that determines the HARQ-ACK codebook to be retransmitted by the UE and triggers the HARQ-ACK codebook retransmission. In these embodiments, the DCI format may be encoded to include a time offset used by the UE to determine the HARQ-ACK codebook to be retransmitted. The gNB may decode a physical uplink control channel (PUCCH) that includes the retransmitted HARQ-ACK codebook.

[0111] In some embodiments, the DCI format may be transmitted in a physical downlink control channel (PDCCH) that ends in a downlink (DL) slot (i.e., slot n) 502. In these embodiments, the time offset (l) may be based on the difference between the DL slot (i.e., slot n) 502 and the uplink (UL) slot (i.e., slot m) 504 that contained the initial reception of the HARQ-ACK codebook (i.e., the UE determines slot m as m = nl), and therefore the gNB determines l as = n m.

[0112] In some embodiments, the gNB may encode the DCI to include a slot offset (i.e., k) relative to the DL slot (i.e., slot n) 502 to enable the UE to determine the second UL slot (i.e., slot n+k) 506 for HARQ-ACK codebook retransmission based on the slot offset (i.e., k) relative to the DL slot (i.e., slot n) 502 (i.e., the UE determines the slot for HARQ-ACK codebook retransmission as slot n+k).

[0113] example

[0114] Example 1: A system and method for enhanced UE HARQ feedback for NR, comprising: a procedure in which a gNB configures SPS HARQ-ACK postponement and PUCCH repetition over slots and subslots; a procedure in which a UE performs SPS HARQ-ACK postponement taking into account PUCCH repetition; a procedure in which a gNB configures and requests PUCCH retransmission from a previous slot or subslot; and a procedure in which a UE sends PUCCH retransmission.

[0115] Example 2: The method of Example 1, wherein the number of iterations to be checked for validity may be configured by higher layers from 1 to the (maximum) number of PUCCH iterations. Furthermore, the number of iterations to be checked for validity may be defined relative to the total number of iterations for which the PUCCH was originally scheduled or configured, e.g., the number of iterations to be checked for validity may be determined as a floor (f*R), where "f" is a configured or specified factor and "R" is the total number of PUCCH iterations.

[0116] Example 3: The method described in Example 1, in which if a UE is configured with slot-based or subslot-based PUCCH repetitions and is indicated with more than one PUCCH repetition, and the corresponding SPS HARQ-ACK carried by the repetition is enabled for deferral, only the conditions for mapping the initial PUCCH repetition from multiple PUCCH repetitions may be checked for deferral.

[0117] Example 4: The method of Example 1, in which if a UE is configured with slot-based or subslot-based PUCCH repetition and is indicated with more than one PUCCH repetition, and the corresponding SPS HARQ-ACK carried by the repetition is enabled for deferral, the conditions for mapping of all PUCCH transmissions from multiple PUCCH transmissions may be checked for deferral, i.e., only when all PUCCH repetitions can be mapped to valid UL slots / subslots, no further deferral is performed.

[0118] Example 5: The method of Example 1, in which if a UE is configured with slot-based or subslot-based PUCCH repetition and is indicated with more than one PUCCH repetition, and the corresponding SPS HARQ-ACK carried by the repetition is enabled for deferral, a condition for mapping of each PUCCH transmission from multiple PUCCH transmissions may be checked for deferral. If at least X PUCCH repetitions can be mapped to valid UL slots / subslots, deferral is not performed, where X may be fixed to 1 or may be configurable from 1 to the number of PUCCH repetitions.

[0119] Example 6: When SPS HARQ-ACK is configured with deferral enabled, the UE:

number

[0120] Example 7: The method of Example 6, in which the UE may expect that either the first PUCCH or the second PUCCH starts in the same slot and includes a UCI type with the same priority when one of the UCIs includes SPS HARQ-ACJ with deferral enabled. In this case, one of the following dropping rules may be applied:

[0121] If there are UCIs of different types with the same priority, the UCI containing the SPS HARQ-ACK is dropped and the other UCI is transmitted.

[0122] Alternatively, if there are different types of UCIs with the same priority, the UCI containing the SPS HARQ-ACK is kept and the other UCIs are dropped.

[0123] Example 8: When a PUCCH is triggered for retransmission by a DCI, in the case of a type 2 CB, an additional total DAI or consecutive counter DAI may be used to derive the CB size of the PUCCH in the slot / subslot indicated for retransmission, as described in Example 1.

[0124] Example 9: When a PUCCH is triggered for retransmission by a DCI, in the case of a type 2 CB, the DCI with a retransmission of the HARQ-ACK codebook may indicate an additional time offset from the PUCCH resource to the past for the new HARQ-ACK, in which case the UE is assumed to continue CB construction from the indicated PUCCH resource in the past to the PUCCH resource in the future, as described in Example 1.

[0125] Example 10: The method described in Example 9, in which the UE assumes that the previous or original PUCCH resource will be used for retransmission, and it continues to count HARQ-ACK bits using a counter DAI including the DAI from the DCI requesting PUCCH retransmission and the total DAI.

[0126] Example 11: The method of example 9, wherein the time offset may be indicated in terms of a number of slots corresponding to a subcarrier spacing (SCS) of the active UL BWP to which the PUCCH is mapped.

[0127] Example 12: The method of Example 9, wherein a reference to one of multiple possible PUCCHs may be provided to the UE via a combination of a slot offset referencing the previous slot and a PUCCH resource indication (PRI) for the indicated slot, so as to distinguish between multiple PUCCH resources within the slot that may be affected.

[0128] Example 13: The method of Example 9, in which the UE may not expect the same HARQ process ID for the CC to be indicated in the new DCI and associated with the HARQ codebook payload in the retransmitted PUCCH.

[0129] Example 14: When a PUCCH is triggered for retransmission by a DCI, the UE may not be expected to be requested to retransmit a PUCCH of a first priority by a DCI indication including a second priority, i.e., triggering of PUCCH retransmission by a DCI of a different priority is not supported. The method described in Example 9.

[0130] Example 15: The method of Example 9, where, for the same codebook type, codebook size may still be an issue in the case of a type-1 codebook when a PUCCH is triggered for retransmission by a DCI. For a type-1 codebook, there is one special case where the UE transmits only a 1-bit HARQ-ACK or only a HARQ-ACK for an SPS PDSCH when the UE does not receive any DCI or receives only one DCI with DCI1_0 having a specific DAI value. For other cases, the UE generates a type-1 codebook (usually with a much larger size). One way to avoid such ambiguity is to always generate a type-1 codebook for dropped PUCCHs (even when the UE has only an SPS PDSCH HARQ-ACK to transmit or receives only one DCI with DCI1_0 having a specific DAI value).

[0131] Example 16: For an SPS with priority i configured in spsHARQdeferral (i.e., when SPS HARQ-ACK deferral is activated for the SPS configuration), the UE determines whether to defer the SPS HARQ-ACK from the first slot to the second slot. The method of Example 1.

[0132] Example 17: The method according to example 15, in which, for an SPS HARQ-ACK with priority i, after resolving overlapping PUCCH / PUSCH (if applicable) with different priorities, and if the UE would transmit the SPS HARQ-ACK using an invalid PUCCH SPS-PUCCH-AN-List-r16 or n1PUCCH-AN, the SPS HARQ-ACK with priority i is postponed.

[0133] Example 18: For an SPS HARQ-ACK with priority i, after resolving overlapping PUCCH / PUSCH (if applicable) with different priorities, and if the UE would transmit the SPS HARQ-ACK using an inactive PUCCH SPS-PUCCH-AN-List-r16 configured for priority i or an n1PUCCH-AN configured for priority i, the SPS HARQ-ACK with priority i is postponed. The method according to example 15.

[0134] Example 19: For an SPS HARQ-ACK with priority i, after resolving overlapping PUCCH / PUSCH with the same priority (step 1), and if the UE is going to transmit the SPS HARQ-ACK using an invalid PUCCH SPS-PUCCH-AN-List-r16 with priority i or n1 PUCCH-AN with priority i, the SPS HARQ-ACK with priority i is postponed. The method according to example 15.

[0135] The Abstract is provided to comply with Title 37 of the Code of Federal Regulations. Section 1.72(b) requires an abstract that will allow the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. The following claims are therefore hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. [Item 1] 1. An apparatus for user equipment (UE) configured for operation in a fifth-generation (5G) new radio (NR) network, comprising: processing circuitry; and memory, wherein the UE is configured for hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook determination; wherein the processing circuitry decodes a downlink control information (DCI) format received from a generation NodeB (gNB), and when the DCI format triggers a HARQ-ACK codebook retransmission, the processing circuitry: determining a HARQ-ACK codebook to be retransmitted based on the time offset indicated in the DCI format; and Encoding a physical uplink control channel (PUCCH) to include the HARQ-ACK codebook determined to be retransmitted. It is configured as follows: wherein the memory is configured to store the HARQ-ACK codebook determined to be retransmitted. Device. [Item 2] the DCI format is received on a Physical Downlink Control Channel (PDCCH) that ends in a downlink (DL) slot; To determine the HARQ-ACK codebook to be retransmitted, the processing circuitry is configured to determine an uplink (UL) slot that includes an initial transmission of the HARQ-ACK codebook based on subtracting the time offset from the DL slot. Item 1. The device according to item 1. [Item 3] the UL slot containing the initial transmission of the HARQ-ACK codebook is a first UL slot; the processing circuitry is further configured to determine a second UL slot for the retransmission of the HARQ-ACK codebook based on a slot offset relative to the DL slot. Item 2. The device according to item 2. [Item 4] Item 4. The apparatus of item 3, wherein the DCI format is a DCI format for scheduling a Physical Downlink Shared Channel (PDSCH) HARQ-ACK retransmission and comprises one of DCI format 1_1 and DCI format 1_2. [Item 5] The DCI format is PDSCH Includes a HARQ-ACK transmission indicator (pdsch-HARQ-ACK-retx), When the UE is configured by radio resource control (RRC) signaling, the PDSCH The HARQ-ACK transmission indicator requests the UE to perform a HARQ-ACK retransmission on a PUCCH resource. Item 4. The device according to item 4. [Item 6] 6. The apparatus of claim 5, wherein when the DCI format further includes a priority indicator field having a value, the value indicates a priority of HARQ-ACK information in the initial transmission of the HARQ-ACK codebook, and the value indicates a priority of HARQ-ACK information for the retransmission of the HARQ-ACK codebook triggered by the DCI format. [Item 7] 7. The apparatus of claim 6, wherein when the DCI format does not include a priority indicator field, the priority of the HARQ-ACK information for the retransmission of the HARQ-ACK codebook is 0. [Item 8] The processing circuitry determining the HARQ-ACK codebook for the initial transmission based on PDSCH reception in one or more candidate DL slots; transmitting an initial PUCCH carrying the initial transmission of the HARQ-ACK codebook in the first UL slot; and transmit a second PUCCH carrying the retransmission of the HARQ-ACK codebook in the second UL slot. Item 5. The apparatus of item 4, wherein the UE is configured to: [Item 9] the HARQ-ACK codebook is generated based on one of a Type 1 and a Type 2 HARQ-ACK codebook decision; In the case of the Type 1 HARQ-ACK codebook determination, the HARQ-ACK codebook is a quasi-static fixed-size codebook; In the case of the type 2 HARQ-ACK codebook determination, the HARQ-ACK codebook is a dynamic codebook. Item 9. The device according to item 8. [Item 10] 10. The apparatus of any of items 1 to 9, wherein the processing circuitry comprises a baseband processor, and the PDCCH is received by the UE using two or more antennas. [Item 11] 1. A non-transitory computer-readable storage medium storing instructions for execution by a processing circuit of a user equipment (UE) configured for a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook determination operation in a fifth-generation (5G) new radio (NR) network, wherein the processing circuit decodes a downlink control information (DCI) format received from a fifth-generation NodeB (gNB); When the DCI format triggers a HARQ-ACK codebook retransmission, the processing circuitry determining a HARQ-ACK codebook to be retransmitted based on the time offset indicated in the DCI format; and Encoding a physical uplink control channel (PUCCH) to include the HARQ-ACK codebook determined to be retransmitted. A non-transitory computer-readable storage medium configured to: [Item 12] the DCI format is received on a Physical Downlink Control Channel (PDCCH) that ends in a downlink (DL) slot; To determine the HARQ-ACK codebook to be retransmitted, the processing circuitry is configured to determine an uplink (UL) slot that includes an initial transmission of the HARQ-ACK codebook based on subtracting the time offset from the DL slot. Item 12. The non-transitory computer-readable storage medium of item 11. [Item 13] the UL slot containing the initial transmission of the HARQ-ACK codebook is a first UL slot; the processing circuitry is further configured to determine a second UL slot for the retransmission of the HARQ-ACK codebook based on a slot offset relative to the DL slot. Item 13. The non-transitory computer-readable storage medium of item 12. [Item 14] Item 14. The non-transitory computer-readable storage medium of item 13, wherein the DCI format is a DCI format for scheduling Physical Downlink Shared Channel (PDSCH) HARQ-ACK retransmissions and comprises one of DCI format 1_1 and DCI format 1_2. [Item 15] The DCI format is PDSCH Includes a HARQ-ACK transmission indicator (pdsch-HARQ-ACK-retx), When the UE is configured by radio resource control (RRC) signaling, the PDSCH The HARQ-ACK transmission indicator requests the UE to perform a HARQ-ACK retransmission on a PUCCH resource. Item 15. The non-transitory computer-readable storage medium of item 14. [Item 16] Item 16. The non-transitory computer-readable storage medium of item 15, wherein when the DCI format further includes a priority indicator field having a value, the value indicates a priority of HARQ-ACK information in the initial transmission of the HARQ-ACK codebook, and the value indicates a priority of HARQ-ACK information for the retransmission of the HARQ-ACK codebook triggered by the DCI format. [Item 17] Item 17. The non-transitory computer-readable storage medium of item 16, wherein when the DCI format does not include a priority indicator field, the priority of the HARQ-ACK information for the retransmission of the HARQ-ACK codebook is 0. [Item 18] 1. An apparatus for a fifth generation (5G) NodeB (gNB) configured for operation in a fifth generation (5G) new radio (NR) network, comprising: processing circuitry; and memory; For a user equipment (UE) configured for hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook determination, the processing circuitry: determining a HARQ-ACK codebook to be retransmitted by the UE; encoding a downlink control information (DCI) format for transmission to the UE, the DCI format triggering a HARQ-ACK codebook retransmission, the DCI format encoded to include a time offset used by the UE to determine the HARQ-ACK codebook to be retransmitted; Decoding a physical uplink control channel (PUCCH) including the retransmitted HARQ-ACK codebook; wherein the memory is configured to store the DCI format. Device. [Item 19] the DCI format is transmitted in a Physical Downlink Control Channel (PDCCH) that ends in a downlink (DL) slot; the time offset is based on the difference between the DL slot and the uplink (UL) slot that contained the initial reception of the HARQ-ACK codebook. Item 19. The device according to item 18. [Item 20] 20. The apparatus of claim 19, wherein the processing circuitry is further configured to encode the DCI to include a slot offset relative to the DL slot to enable the UE to determine a second UL slot for the retransmission of the HARQ-ACK codebook based on the slot offset relative to the DL slot.

Claims

1. 1. An apparatus for a user equipment (UE) configured for operation in a fifth-generation (5G) new radio (NR) network, comprising: a processing circuit; and a memory, wherein the UE is configured for hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook determination; the HARQ-ACK codebook includes two or more HARQ-ACKs; the memory is configured to store the HARQ-ACK codebook; wherein the processing circuitry decodes a downlink control information (DCI) format received from a generation NodeB (gNB), and when the DCI format triggers a HARQ-ACK codebook retransmission, the processing circuitry: Determining a HARQ-ACK codebook to be retransmitted based on the time offset indicated in the DCI format; and encoding a physical uplink control channel (PUCCH) to include the HARQ-ACK codebook to be retransmitted; It is configured as follows: The processing circuitry further comprises: If the HARQ-ACKs to be postponed include both low priority (LP) HARQ-ACKs and high priority (HP) HARQ-ACKs, determine target slots for including the HARQ-ACKs to be postponed in a HARQ-ACK codebook separately for the LP HARQ-ACKs and the HP HARQ-ACKs; It is configured as follows: Device.

2. the DCI format is received on a Physical Downlink Control Channel (PDCCH) that ends in a downlink (DL) slot; To determine the HARQ-ACK codebook to be retransmitted, the processing circuitry is configured to determine an uplink (UL) slot containing an initial transmission of the HARQ-ACK codebook to be retransmitted based on subtracting the time offset from the DL slot.

10. The apparatus of claim 1.

3. the UL slot containing the initial transmission of the HARQ-ACK codebook to be retransmitted is a first UL slot; the processing circuitry is further configured to determine a second UL slot for the retransmission of the HARQ-ACK codebook to be retransmitted based on a slot offset relative to the DL slot.

3. The apparatus of claim 2.

4. 4. The apparatus of claim 3, wherein the DCI format is a DCI format for scheduling a Physical Downlink Shared Channel (PDSCH) HARQ-ACK retransmission and comprises one of DCI format 1_1 and DCI format 1_2.

5. The DCI format includes a PDSCH HARQ-ACK transmission indicator (pdsch-HARQ-ACK-retx); When the UE is configured by Radio Resource Control (RRC) signaling, the PDSCH HARQ-ACK transmission indicator requests the UE to perform HARQ-ACK retransmission on PUCCH resources.

5. The apparatus of claim 4.

6. 6. The apparatus of claim 5, wherein when the DCI format further includes a priority indicator field having a value, the value indicates a priority of HARQ-ACK information in the initial transmission of the HARQ-ACK codebook to be retransmitted, and the value indicates a priority of HARQ-ACK information for the retransmission of the HARQ-ACK codebook to be retransmitted triggered by the DCI format.

7. 7. The apparatus of claim 6, wherein when the DCI format does not include a priority indicator field, the priority of the HARQ-ACK information for the retransmission of the HARQ-ACK codebook to be retransmitted is 0.

8. The processing circuitry determining the to-be-retransmitted HARQ-ACK codebook for the initial transmission based on PDSCH reception in one or more candidate DL slots; transmitting an initial PUCCH carrying the initial transmission of the HARQ-ACK codebook to be retransmitted in the first UL slot; and transmitting a second PUCCH carrying the retransmission of the HARQ-ACK codebook to be retransmitted in the second UL slot; The apparatus of claim 4 , further comprising:

9. the HARQ-ACK codebook to be retransmitted is generated based on one of a Type 1 and a Type 2 HARQ-ACK codebook decision; In the case of the Type 1 HARQ-ACK codebook determination, the HARQ-ACK codebook to be retransmitted is a semi-static codebook; In the case of the Type 2 HARQ-ACK codebook determination, the HARQ-ACK codebook to be retransmitted is a dynamic codebook.

9. The apparatus of claim 8.

10. 10. The apparatus of claim 1, wherein the processing circuitry comprises a baseband processor, and wherein a PDCCH is received by the UE using two or more antennas.

11. 1. A computer program for execution by a processing circuit of a user equipment (UE) configured for a Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) codebook determination operation in a fifth generation (5G) New Radio (NR) network, comprising: the HARQ-ACK codebook includes two or more HARQ-ACKs; wherein the processing circuitry decodes a downlink control information (DCI) format received from a generation NodeB (gNB); When the DCI format triggers a HARQ-ACK codebook retransmission, the computer program causes the processing circuit to: determining a HARQ-ACK codebook to be retransmitted based on the time offset indicated in the DCI format; and encoding a physical uplink control channel (PUCCH) to include the HARQ-ACK codebook to be retransmitted; Execute The computer program further causes the processing circuitry to: If the HARQ-ACKs to be postponed include both low priority (LP) HARQ-ACKs and high priority (HP) HARQ-ACKs, a procedure for separately determining target slots for including the HARQ-ACKs to be postponed in the HARQ-ACK codebook for the LP HARQ-ACKs and the HP HARQ-ACKs. A computer program for executing

12. the DCI format is received on a Physical Downlink Control Channel (PDCCH) that ends in a downlink (DL) slot; To determine the HARQ-ACK codebook to be retransmitted, the computer program causes the processing circuit to perform a procedure of determining an uplink (UL) slot containing an initial transmission of the HARQ-ACK codebook to be retransmitted based on subtracting the time offset from the DL slot.

12. A computer program according to claim 11.

13. the UL slot containing the initial transmission of the HARQ-ACK codebook to be retransmitted is a first UL slot; The computer program further causes the processing circuit to determine a second UL slot for the retransmission of the HARQ-ACK codebook to be retransmitted based on a slot offset relative to the DL slot.

13. A computer program according to claim 12.

14. 14. The computer program product of claim 13, wherein the DCI format is a DCI format for scheduling a Physical Downlink Shared Channel (PDSCH) HARQ-ACK retransmission and comprises one of DCI format 1_1 and DCI format 1_2.

15. The DCI format includes a PDSCH HARQ-ACK transmission indicator (pdsch-HARQ-ACK-retx); When the UE is configured by Radio Resource Control (RRC) signaling, the PDSCH HARQ-ACK transmission indicator requests the UE to perform HARQ-ACK retransmission on PUCCH resources.

15. A computer program according to claim 14.

16. 16. The computer program product of claim 15, wherein when the DCI format further includes a priority indicator field having a value, the value indicates a priority of HARQ-ACK information in the initial transmission of the HARQ-ACK codebook to be retransmitted, and the value indicates a priority of HARQ-ACK information for the retransmission of the HARQ-ACK codebook to be retransmitted triggered by the DCI format.

17. 17. The computer program product of claim 16, wherein when the DCI format does not include a priority indicator field, the priority of the HARQ-ACK information for the retransmission of the HARQ-ACK codebook to be retransmitted is 0.

18. A computer readable storage medium storing a computer program according to any one of claims 11 to 17.

Images