HARQ-ACK based PDSCH transmission scheduled by multiple DL allocations

Abstract

A user equipment (UE) may generate a first HARQ-ACK information bit based on the first PDSCH and a second HARQ-ACK information bit based on the second PDSCH. The UE may determine a first slot for an expected PUCCH transmission with the first HARQ-ACK information bit. If the UE is configured to withhold HARQ-ACK for the first PDSCH and if the first slot is not available for the expected PUCCH transmission, the UE may determine an available, first-most second slot. The UE may also determine a third slot for an expected PUCCH transmission with the second HARQ-ACK information bit assigned to the second PDSCH. The resources assigned to the transmission of the first HARQ-ACK information bit are used to verify the order of the first and second HARQ-ACK transmissions, regardless of whether the first slot is not available and the second-most slot is used for the transmission of the first HARQ-ACK information bit.

Description

[Technical Field]

[0001] [Priority Claim] This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 311,816, filed February 18, 2022 [Reference No. AE2049-Z], U.S. Provisional Patent Application No. 63 / 314,932, filed February 28, 2022 [Reference No. AE2202-Z], U.S. Provisional Patent Application No. 63 / 315,366, filed March 1, 2022 [Reference No. AE2224-Z], and U.S. Provisional Patent Application No. 63 / 333,462, filed April 21, 2022 [Reference No. AE3184-Z], which are incorporated by reference herein in their entireties.

[0002] Embodiments relate to wireless communications. Some embodiments relate to wireless networks, including fifth-generation (5G) networks, including 3GPP (Third Generation Partnership Project) and 5G New Radio (NR) (or 5G-NR) networks. Some embodiments relate to sixth-generation (6G) networks. [Background technology]

[0003] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated, integrated communications platforms. The proliferation of different types of devices communicating with various network devices is driving increased use of 3GPP 5G NR systems. The proliferation of mobile devices (user equipment or UE) in modern society continues to drive demand for a variety of networked devices in many different environments. 5G NR wireless systems are emerging and are expected to deliver even higher speeds, connectivity, and usability, while also increasing throughput, coverage, and robustness and reducing latency and operational and capital expenditures. 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] One issue in 5G NR networks is the ordering of HARQ-ACK-based PDSCH transmissions scheduled by multiple DL allocations, which is particularly problematic for PDSCHs configured for downlink semi-persistent scheduling (SPS) when the UE is configured to withhold HARQ-ACK for the PDSCH. [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 2] 1 illustrates a functional block diagram of a wireless communication device according to some embodiments.

[0008] [Figure 3] 1 illustrates multi-TTI scheduling for PDSCH according to some embodiments.

[0009] [Figure 4] 1 illustrates an out-of-order (OOO) check based on the first indicated PUCCH repetition, according to some embodiments.

[0010] [Figure 5] 10 illustrates an OOO check based on the first indicated PUCCH iteration, according to some embodiments.

[0011] [Figure 6] 1 illustrates an OOO check based on all available PUCCH repetitions, according to some embodiments.

[0012] [Figure 7] 1 illustrates an OOO check based on the indicated PUCCH according to some embodiments.

[0013] [Figure 8] 1 illustrates an OOO check based on the indicated PUCCH according to some embodiments.

[0014] [Figure 9] 10 illustrates encoding of HARQ-ACK and CSI on PUSCH in the case of lacking a DL grant for PUSCH, according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0015] 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.

[0016] In some embodiments, user equipment (UE) configured for operation in a 5G NR network may decode a first PDSCH and a second PDSCH and may generate a first HARQ-ACK information bit based on the first PDSCH and a second HARQ-ACK information bit based on the second PDSCH. If the UE is configured to withhold HARQ-ACK for the first PDSCH, the UE may determine a first slot for an expected PUCCH transmission having the first HARQ-ACK information bit. If the first slot is not available for an expected PUCCH transmission of the first HARQ-ACK information bit, the UE may determine a first-most available second slot for a PUCCH transmission including the first HARQ-ACK information bit. The UE may also determine a third slot for an expected PUCCH transmission having the second HARQ-ACK information bit assigned to the second PDSCH. The UE may also verify that, for the scheduled cell, if the second PDSCH starts after the first PDSCH, the resources allocated by the second feedback timing for the transmission of the second HARQ-ACK information bit do not end before the start of the resources allocated for the transmission of the first HARQ-ACK information bit. In these embodiments, the resources allocated for the transmission of the first HARQ-ACK information bit are always used to verify the order of the first and second HARQ-ACK transmissions, even if the first slot is unavailable and the second, earliest slot is used for the transmission of the first HARQ-ACK information bit. These embodiments, as well as others, are described in more detail below.

[0017] In some embodiments, when a UE is scheduled by a gNB for transmission of multiple PUSCHs on its respective serving cell and the multiple PUSCHs overlap with a PUCCH carrying uplink control information (UCI) in a slot, the UE may select the PUSCH that overlaps with the PUCCH carrying UCI as a candidate PUSCH for UCI multiplexing in the slot. In these embodiments, when at least one of the multiple PUSCHs is scheduled by a DCI format including a downlink assignment index (DAI) field, for HARQ-ACK multiplexing, the UE may be configured to exclude one or more of the candidate PUSCHs for HARQ-ACK multiplexing that are scheduled by a DCI format including a DAI field equal to 4 or equal to 0 if a PUCCH carrying HARQ-ACK information bits has not been determined for the slot. In these embodiments, the UE may select one or more of the remaining candidate PUSCHs that are not excluded for HARQ-ACK multiplexing. These embodiments, as well as others, are described in more detail below.

[0018] FIG. 1A illustrates a network architecture according to some embodiments. Network 140A is shown to include user equipment (UE) 101 and UE 102. UE 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. UE 101 and 102 may be collectively referred to herein as UE 101, and UE 101 may be used to perform one or more of the techniques disclosed herein.

[0019] 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.

[0020] 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 in which multiple carrier signals operating at different frequencies may be used to carry communications for a single UE, thus increasing the bandwidth available to a single device. In some embodiments, carrier aggregation may be used when one or more component carriers operate in unlicensed frequencies.

[0021] 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 the 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and beyond frequencies, and Spectrum Access System (SAS) in the 3.55-3.7 GHz and beyond frequencies).

[0022] 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.), particularly to 3GPP NR (New Radio), by allocating OFDM carrier data bit vectors to corresponding symbol resources.

[0023] 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 include 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 the 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.

[0024] In some embodiments, either of the UEs 101 and 102 may comprise an enhanced MTC (eMTC) UE or a further enhanced MTC (FeMTC) UE.

[0025] UEs 101 and 102 may be configured to connect to, e.g., be communicatively coupled to, a radio access network (RAN) 110. 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. 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 depicted as air interfaces enabling the communicative coupling and may conform to a cellular communication protocol 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 fifth generation (5G) protocol, a new radio (NR) protocol, etc.

[0026] In one aspect, the UEs 101 and 102 may further exchange communication data directly via a 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).

[0027] UE 102 is shown as being configured to access access point (AP) 106 via connection 107. Connection 107 may include, for example, a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, according to which AP 106 may include a Wireless Fidelity (WiFi) router. In this example, 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).

[0028] 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.

[0029] Either of the RAN nodes 111 and 112 may terminate air interface protocols and may be the first point of contact for the UEs 101 and 102. In some embodiments, either of the 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 one example, either of the nodes 111 and / or 112 may be a new generation NodeB (gNB), an evolved NodeB (eNB), or another type of RAN node.

[0030] 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.

[0031] 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 similar in function 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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).

[0036] 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.

[0037] 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, the gNB may be a master node (MN) in the 5G architecture, and the NG-eNB may be a secondary node (SN).

[0038] 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 can include, for example, operator services, Internet access, or third-party services. The AMF 132 can be used to manage access control and mobility and can also include a network slice selection function. The SMF 136 can be configured to set up and manage various sessions according to network policies. The UPF 134 can be deployed in one or more configurations according to the desired service type. The PCF 148 can 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 can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0039] 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 embodiments 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 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, e.g., an IMS operated by a different network operator.

[0040] 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.

[0041] 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 (between the UDM 146 and the SMF 136, not shown), N12 (between the UPF 134 and the DN 152, not shown), N13 (between the UPF 134 and the DN 152, not shown), N14 (between the UPF 134 and the DN 152, not shown), N15 (between the UPF 134 and the DN 152, not shown), N16 (between the UPF 134 and the DN 152, not shown), N17 (between the SMF 136 and the PCF 148, not shown), N18 (between the UDM 146 and the AMF 132, not shown), N19 (between two UPFs 134, not shown), N20 (between the UDM 146 and the SMF 136, not shown), N21 (between the UPF 134 and the DN 1 1B shows 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.

[0042] 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 i or as service-based interfaces.

[0043] 1C , the 5G system architecture 140C may 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.

[0044] 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.

[0045] 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), provides 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 targeted to meet very different, and sometimes conflicting, performance dimensions and services. These diverse, multi-dimensional requirements are driven by different services and applications. Generally, 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, providing high-speed, rich content and services.

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

[0047] 2 illustrates a functional block diagram of a wireless communication device 200, according to some embodiments. The wireless communication device 200 may be suitable for use as a UE or gNB configured for operation in a 5G NR network.

[0048] 2 illustrates a functional block diagram of a communications device (STA) that may be suitable for use as an AP STA, a non-AP STA, or other user device, according to some embodiments. Communications device 200 may also be suitable for use as a handheld device, a mobile device, a cellular phone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computing device, a femtocell, a High Data Rate (HDR) subscriber device, an access point, an access terminal, or other Personal Communication System (PCS) device.

[0049] Communications device 200 may include communications circuitry 202 and a transceiver 210 that transmits and receives signals to other communications devices using one or more antennas 201. Communications circuitry 202 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. Communications device 200 may also include processing circuitry 206 and memory 208 configured to perform operations described herein. In some embodiments, communications circuitry 202 and processing circuitry 206 may be configured to perform operations detailed in the figures, drawings, and flows above.

[0050] According to some embodiments, the communications circuitry 202 may be configured to contend for the wireless medium and to construct frames or packets for communication over the wireless medium. The communications circuitry 202 may be configured to transmit and receive signals. The communications circuitry 202 may also include circuitry for modulation / demodulation, upconversion / downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry 206 of the communications device 200 may include one or more processors. In other embodiments, two or more antennas 201 may be coupled to the communications circuitry 202 configured to transmit and receive signals. The memory 208 may store information for configuring the processing circuitry 206, to construct and transmit message frames, and to perform various operations described herein. The memory 208 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, memory 208 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.

[0051] In some embodiments, communication device 200 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.

[0052] In some embodiments, communications device 200 may include one or more antennas 201. Antenna 201 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 the different channel characteristics that may result between each of the antennas and the antenna of the transmitting device.

[0053] In some embodiments, communications device 200 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.

[0054] Although communications device 200 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 200 may refer to one or more processes operating on one or more processing elements.

[0055] In NR, PDSCH transmission based on hybrid automatic retransmission request (HARQ) is adopted. Generally, a physical downlink control channel (PDCCH) with downlink control information (DCI) may schedule a physical downlink shared channel (PDSCH). Then, HARQ acknowledgment (HARQ-ACK) information may be transmitted in a PUCCH indicated by the PDCCH.

[0056] PDSCH repetition is supported in NR, i.e., N PDSCHs can be indicated to carry the same TB. For PDSCH repetition type A, the N PDSCH repetitions are in N consecutive slots. For PDSCH repetition type B, the N PDSCH repetitions occupy N consecutive PDSCHs. A PDSCH repetition is dropped if it overlaps with an UL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. Furthermore, if a PDSCH repetition collides with an UL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for PDSCG repetition type A, the PDSCH repetition is extended so that the PDSCH repetition can be postponed to the next slot.

[0057] PUCCH repetitions are also supported in NR. Assuming N repetitions are configured for the PUCCH, the UE shall transmit N PUCCH repetitions. It is clarified that if a PUCCH repetition collides with an SSB symbol or a symbol indicated as DL by the tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the PUCCH repetition for N>1 (including the first PUCCH repetition) is postponed to the next available slot.

[0058] In NR, it is also supported to reserve the PUCCH carrying HARQ-ACK when PUCCH repetition is not configured. Specifically, if the PUCCH indicated by the DL assignment collides with an SSB symbol or an UL symbol indicated by the tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the PUCCH may be postponed to the next available slot.

[0059] For systems operating at carrier frequencies above 52.6 GHz, the subcarrier spacing is increased and the slot length is reduced. A DCI may schedule PDSCH transmissions with one or multiple TBs. Figure 3 shows an example of multi-PDSCH scheduling. In this example, four PDSCHs (PDSCH#0-3) with different transport blocks (TBs) are scheduled by a single DCI.

[0060] Out-of-order transmission of two PDSCHs and associated PUCCHs for HARQ-ACK transmission is not supported in NR. In a given scheduled cell, a UE is not expected to receive a first PDSCH in slot i, whose corresponding HARQ-ACK is assigned to be transmitted in slot j, and a second PDSCH that starts later than the first PDSCH and whose corresponding HARQ-ACK is assigned to be transmitted in a slot before slot j. In this IDF, we propose a detailed design of OOO handing that considers single-PDSCH or multi-PDSCH scheduling, PUCCH with or without repetition, and PUCCH reservation.

[0061] OOO check for PUCCH repetitions

[0062] If PUCCH repetitions are configured for the UE, the OOO check of the PDSCH and associated PUCCH for the serving cell may consider the influence of the indicated slot and / or available slot for PUCCH repetition. The slot with the first indicated PUCCH repetition is determined by the last PDSCH scheduled by the DCI and the PDSCH-to-HARQ_feedback timing indicator field (K1) in the DCI. If the first indicated PUCCH repetition does not collide with an SSB symbol or DL ​​symbol indicated by the tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the first indicated PUCCH repetition becomes the first available PUCCH repetition. Otherwise, the first available PUCCH repetition is delayed to the next available slot.

[0063] In one embodiment, the OOO check of the PDSCH and associated PUCCH for the serving cell may be defined based on the PDSCH and the indicated first PUCCH repetition for the PDSCH. For a given scheduled cell, the UE is not expected to receive a first PDSCH in slot i whose corresponding first indicated PUCCH repetition for HARQ-ACK is assigned to be transmitted in slot j, and a second PDSCH that starts later than the first PDSCH and whose corresponding first indicated PUCCH repetition for HARQ-ACK is assigned to be transmitted in a slot prior to slot j.

[0064] Figure 4 shows an example of an OOO check for two PDSCHs and associated PUCCHs with repetitions. In this example, the first indicated PUCCH repetition 201 for PDSCH1 collides with a DL symbol and is therefore delayed to the next available slot 202. The first indicated PUCCH repetition for PDSCH2 becomes the first available PUCCH repetition 203. Note that in Figure 4, the two available PUCCH repetitions for PDSCH1 precede the two available PUCCH repetitions of PDSCH2. The OOO check is performed on PDSCH1, PDSCH2, the first indicated PUCCH repetition 201 for PDSCH1, and the first indicated PUCCH repetition 203 for PDSCH2. Therefore, this is valid scheduling for the case of Figure 4.

[0065] 5 shows another example of an OOO check of two PDSCHs and associated PUCCHs with repetitions. In this example, the first indicated PUCCH repetition 301 for PDSCH1 collides with a DL symbol and is therefore delayed to the next available slot 302. The first indicated PUCCH repetition for PDSCH2 becomes the first available PUCCH repetition 303. Note that in FIG. 5, the two available PUCCH repetitions for PDSCH1 are later than the two available PUCCH repetitions of PDSCH2. The OOO check is performed on PDSCH1, PDSCH2, the first indicated PUCCH repetition 301 for PDSCH1, and the first indicated PUCCH repetition 303 for PDSCH2. Consequently, this is the effective scheduling of FIG. 5.

[0066] In these embodiments, the UE may be configured to decode the first PDSCH 511 (FIG. 5) and the second PDSCH 513 received from the gNB. In these embodiments, at least the first PDSCH 511 is configured for downlink semi-persistent scheduling (SPS). The UE may also generate a first HARQ-ACK information bit based on the first PDSCH 511 and a second HARQ-ACK information bit based on the second PDSCH 513. In these embodiments, if the UE is configured to defer HARQ-ACK for the first PDSCH 511 (i.e., sps-HARQ-Deferral is provided to the UE for the first PDSCH 511), the UE may determine the first slot 501 for the expected PUCCH transmission with the first HARQ-ACK information bit, assigned to the first PDSCH 511, based on the first feedback timing K1 provided by the gNB. In some embodiments, if the first slot 501 is unavailable for an expected PUCCH transmission of the first HARQ-ACK information bit (e.g., due to a collision with a downlink symbol), the UE may determine an earliest second slot 502 available for a PUCCH transmission including the first HARQ-ACK information bit. In these embodiments, the earliest second slot 502 may be the earliest slot available for a PUCCH transmission after the first slot 501. In some embodiments, the UE may also determine a third slot 503 for an expected PUCCH transmission with the second HARQ-ACK information bit, allocated to the second PDSCH 513, based on a second feedback timing k1 provided by the gNB. The UE may also verify that for the scheduled cell, if the second PDSCH 513 starts after the first PDSCH 511, the resources allocated by the second feedback timing k1 for the transmission of the second HARQ-ACK information bit do not end before the start of the resources allocated by the first feedback timing k1 for the transmission of the first HARQ-ACK information bit.

[0067] In these embodiments, in a given scheduled cell, the UE is not expected to receive the first PDSCH 511 and the second PDSCH 513, which starts after the first PDSCH 511 and whose corresponding HARQ-ACK is assigned to be transmitted on a resource that ends before the start of a different resource for the HARQ-ACK assigned to be transmitted for the first PDSCH 511. In these embodiments, the resource assigned by the first feedback timing K1 for the transmission of the first HARQ-ACK information bit is always used to verify the order of the first and second HARQ-ACK transmissions, even if the first slot is unavailable and the second, earliest slot is used for the transmission of the first HARQ-ACK information bit.

[0068] In some embodiments, if the order of PUCCH transmissions is invalid (i.e., out-of-order transmissions), the UE behavior may be unspecified. In some embodiments, if the order of PUCCH transmissions is invalid, the UE may drop one or both of the PUCCH transmissions, although the scope of embodiments is not limited in this respect.

[0069] In some embodiments, the resources allocated to the transmission of the second HARQ-ACK information bit are determined based on the second feedback timing k1 and are within the third slot 503. In these embodiments, the resources allocated to the transmission of the first HARQ-ACK information bit are determined based on the first feedback timing K1 and are within the first slot 501.

[0070] In some embodiments, when the UE is configured to defer HARQ-ACK for the first PDSCH 511, if the first slot 501 is available for the expected PUCCH transmission of the first HARQ-ACK information bit, the UE may encode the first HARQ-ACK information bit for the PUCCH transmission by the UE in the first slot 501. In these embodiments, if the first slot 501 is not available for the expected PUCCH transmission of the first HARQ-ACK information bit, the UE may encode the first HARQ-ACK information bit for the PUCCH transmission by the UE in the earliest second slot 502. In these embodiments, when the UE is configured with sps-HARQ-Deferral, the UE defer transmission of the first HARQ-ACK information bit if the first slot is not available.

[0071] In some embodiments, when the UE is not configured to withhold HARQ-ACK for the SPS PDSCH, if the first slot 501 is available for an expected PUCCH transmission of the first HARQ-ACK information bit, the UE may encode the first HARQ-ACK information bit for a PUCCH transmission by the UE in the first slot 501. In these embodiments, if the first slot 501 is not available for an expected PUCCH transmission of the first HARQ-ACK information bit, the UE may drop the PUCCH transmission of the first HARQ-ACK information bit.

[0072] In some embodiments, when the UE is configured to withhold HARQ-ACK for the first PDSCH 511, if the first slot 501 is not available for an expected PUCCH transmission of the first HARQ-ACK information bit, the UE may encode the first HARQ-ACK information bit for a PUCCH transmission by the UE in the earliest second slot 502. In these embodiments, the UE may encode the second HARQ-ACK information bit for a PUCCH transmission by the UE in the third slot 503.

[0073] In some embodiments, if the first second slot 502 is the same slot as the third slot 503, the UE may encode the first HARQ-ACK information bit and the second HARQ-ACK information bit for the PUCCH transmission in the first second slot 502.

[0074] In some embodiments, when the UE is configured to withhold HARQ-ACK for the first PDSCH 511, the UE may determine that the first slot 501 is unavailable if the PUCCH resource for the expected PUCCH transmission overlaps with symbols indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigDedicated and / or overlaps with a synchronization signal / PBCH block (SSB), although the scope of the embodiments is not limited in this respect.

[0075] In one embodiment, the OOO check of the PDSCH and associated PUCCH for the serving cell may be defined based on the PDSCH and the first available PUCCH repetition for the PDSCH. For a given scheduled cell, the UE is not expected to receive a first PDSCH in slot i, whose corresponding first available PUCCH repetition for HARQ-ACK is assigned to be transmitted in slot j, and a second PDSCH that starts later than the first PDSCH and whose corresponding first available PUCCH repetition for HARQ-ACK is assigned to be transmitted in a slot prior to slot j.

[0076] The embodiment shown in Figure 4 can be reused to illustrate an example embodiment. The OOO check is performed with PDSCH1, PDSCH2, the first available PUCCH repetition 202 for PDSCH1, and the first available PUCCH repetition 203 for PDSCH2. This is therefore a valid scheduling for the case of Figure 4.

[0077] The embodiment shown in Figure 5 can be reused to show another example of an embodiment. The OOO check is still performed with PDSCH1, PDSCH2, the first available PUCCH repetition 302 for PDSCH1, and the first available PUCCH repetition 303 for PDSCH2. Consequently, this is not a valid scheduling of Figure 5.

[0078] In one embodiment, the OOO check of the PDSCH and associated PUCCH for the serving cell may be defined based on the PDSCH and all available PUCCH repetitions for the PDSCH. For a given scheduled cell, the UE is not expected to receive a first PDSCH in slot i, whose corresponding available PUCCH repetition for HARQ-ACK is assigned to be transmitted in slot j, and a second PDSCH that starts later than the first PDSCH and whose corresponding available PUCCH repetition for HARQ-ACK is assigned to be transmitted in a slot prior to slot j.

[0079] The embodiment shown in Figure 5 can be reused to illustrate an example embodiment. The OOO check is performed with PDSCH1, PDSCH2, two available PUCCH repetitions for PDSCH1 (302, 304), and two available PUCCH repetitions for PDSCH2 (303, 305). Consequently, this is the effective scheduling of Figure 5.

[0080] Figure 6 shows another example of an out-of-band check of two PDSCHs and all associated available PUCCH repetitions for each PDSCH. In this example, the second PUCCH repetition 401 for PDSCH1 collides with a DL symbol and is therefore delayed to the next available slot 402. Note that in Figure 6, the second available PUCCH repetition 402 for PDSCH1 comes after the two available PUCCH repetitions (403, 404) for PDSCH2. The out-of-band check is performed on PDSCH1, PDSCH2, the two available PUCCH repetitions (400, 402) for PDSCH1, and the two available PUCCH repetitions (403, 404) for PDSCH2. Consequently, this is not a valid scheduling for Figure 6.

[0081] In one embodiment, the OOO check of the PDSCH and associated PUCCH for the serving cell may be defined based on the PDSCH, the first indicated PUCCH repetition, and all available PUCCH repetitions for the PDSCH. For a given scheduled cell, the UE is not expected to receive a first PDSCH in slot i, whose corresponding PUCCH repetition for HARQ-ACK (including the first indicated PUCCH repetition and any available PUCCH repetitions) is assigned to be transmitted in slot j, and a second PDSCH that starts after the first PDSCH and whose corresponding PUCCH repetition for HARQ-ACK (including the first indicated PUCCH repetition and any available PUCCH repetitions) is assigned to be transmitted in a slot prior to slot j.

[0082] The embodiment shown in Figure 5 can be reused to illustrate an example embodiment. The OOO check is performed with PDSCH1, PDSCH2, the first indicated PUCCH repetition 301 for PDSCH1, the two available PUCCH repetitions (302, 304) for PDSCH1, the first indicated PUCCH repetition 303 for PDSCH2, and the two available PUCCH repetitions (303, 305) for PDSCH2. Consequently, this is not a valid scheduling of Figure 5.

[0083] The embodiment shown in Figure 6 can be reused to show another example of an embodiment. The OOO check is performed with PDSCH1, PDSCH2, the first indicated PUCCH repetition 400 for PDSCH1, the two available PUCCH repetitions for PDSCH1 (400, 402), the first indicated PUCCH repetition 403 for PDSCH2, and the two available PUCCH repetitions for PDSCH2 (403, 404). Consequently, this is not a valid scheduling of Figure 6.

[0084] In one embodiment, an OOO check of the PDSCH and associated PUCCH for the serving cell may be defined based on the PDSCH, the first indicated PUCCH repetition, and the last available PUCCH repetition for the PDSCH. For a given scheduled cell, the UE is not expected to receive a first PDSCH in slot i, whose corresponding PUCCH repetition for HARQ-ACK (including the first indicated PUCCH repetition and the last available PUCCH repetition) is assigned to be transmitted in slot j, and a second PDSCH that starts after the first PDSCH and whose corresponding PUCCH repetition for HARQ-ACK (including the first indicated PUCCH repetition and the last available PUCCH repetition) is assigned to be transmitted in a slot prior to slot j. This embodiment can achieve the same OOO check result as the previous embodiment.

[0085] The embodiment shown in Figure 5 can be reused to illustrate an example embodiment. The OOO check is performed with PDSCH1, PDSCH2, the first indicated PUCCH repetition 301 for PDSCH1, the last available PUCCH repetition 304 for PDSCH1, the first indicated PUCCH repetition 303 for PDSCH2, and the last available PUCCH repetition 305 for PDSCH2. Consequently, this is not a valid scheduling for Figure 5.

[0086] The embodiment shown in Figure 6 can be reused to show another example of an embodiment. The OOO check is performed with PDSCH1, PDSCH2, the first indicated PUCCH repetition 400 for PDSCH1, the last available PUCCH repetition 402 for PDSCH1, the first indicated PUCCH repetition 403 for PDSCH2, and the last available PUCCH repetition 404 for PDSCH2. Consequently, this is not a valid scheduling of Figure 6.

[0087] OOO check when PUCCH is pending

[0088] If PUCCH reservation is configured for the UE, the OOO check of the PDSCH and associated PUCCH for the serving cell may consider the impact of the indicated PUCCH slot and / or available slots reserved for PUCCH transmission, if applicable. The slot with the indicated PUCCH is determined by the last PDSCH scheduled by the DCI and the PDSCH-to-HARQ_feedback timing indicator field (K1) in the DCI. If the indicated PUCCH collides with an SSB symbol or DL ​​symbol indicated by the tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the indicated PUCCH is delayed to the next available slot. PUCCH reservation may apply to the PUCCH for the SPS PDSCH-only case, or to any PUCCH, or only to the PUCCH for a PDSCH dynamically scheduled by the DCI.

[0089] In one embodiment, an OOO check of the PDSCH and associated PUCCH for the serving cell may be defined based on the PDSCH and the indicated PUCCH for the PDSCH. For a given scheduled cell, the UE is not expected to receive a first PDSCH in slot i whose corresponding indicated PUCCH for HARQ-ACK is assigned to be transmitted in slot j, and a second PDSCH that starts later than the first PDSCH and whose corresponding indicated PUCCH for HARQ-ACK is assigned to be transmitted in a slot prior to slot j.

[0090] Figure 7 shows an example of an OOO check of two PDSCHs and associated PUCCHs. In this example, the indicated PUCCH 501 for PDSCH1 collides with a DL symbol and is therefore delayed to the next available slot, i.e., reserved PUCCH 502. The indicated PUCCH for PDSCH2 becomes the available PUCCH 503. The OOO check is performed by PDSCH1, PDSCH2, the indicated PUCCH 501 for PDSCH1, and the indicated PUCCH 503 for PDSCH2. Therefore, this is valid scheduling for the case of Figure 7.

[0091] 8 shows another example of an OOO check of two PDSCHs and associated PUCCHs. In this example, the indicated PUCCH 601 for PDSCH1 611 collides with a DL symbol and is therefore delayed to the next available slot, i.e., the reserved PUCCH 602. The indicated PUCCH for PDSCH2 613 becomes the available PUCCH 603. The OOO check is performed on PDSCH1, PDSCH2, the indicated PUCCH 601 for PDSCH1, and the indicated PUCCH 603 for PDSCH2. Consequently, this is the effective scheduling of FIG. 8.

[0092] In one embodiment, the OOO check of the PDSCH and associated PUCCH for the serving cell may be defined based on the PDSCH and available PUCCH for the PDSCH. The available PUCCH may be an indicated PUCCH or a reserved PUCCH. For a given scheduled cell, the UE is not expected to receive a first PDSCH in slot i whose corresponding available PUCCH for HARQ-ACK transmission is assigned to be transmitted in slot j, and a second PDSCH that starts later than the first PDSCH and whose corresponding available PUCCH for HARQ-ACK is assigned to be transmitted in a slot prior to slot j.

[0093] The embodiment shown in Figure 7 can be reused to illustrate an example embodiment. The OOO check is performed by PDSCH1, PDSCH2, available PUCCH 502 for PDSCH1, and available PUCCH 503 for PDSCH2. Therefore, this is a valid scheduling for the case of Figure 7.

[0094] The embodiment shown in Figure 8 can be reused to show another example embodiment. The OOO check is performed by PDSCH1, PDSCH2, available PUCCH 602 for PDSCH1, and available PUCCH 603 for PDSCH2. Consequently, this is not a valid scheduling in Figure 8.

[0095] In one embodiment, the OOO check of the PDSCH and associated PUCCH for the serving cell may be defined based on the PDSCH, the indicated PUCCH for the PDSCH, and, if applicable, the reserved PUCCH. For a given scheduled cell, the UE is not expected to receive a first PDSCH in slot i, whose corresponding PUCCH for HARQ-ACK transmission (including the indicated PUCCH and, if applicable, the reserved PUCCH) is assigned to be transmitted in slot j, and a second PDSCH that starts after the first PDSCH and whose corresponding PUCCH for HARQ-ACK (including the indicated PUCCH and, if applicable, the reserved PUCCH) is assigned to be transmitted in a slot earlier than slot j.

[0096] The embodiment shown in Figure 8 can be reused to illustrate an example embodiment. The OOO check is performed by PDSCH1, PDSCH2, indicated PUCCH 601 for PDSCH1, reserved PUCCH 602 for PDSCH1, and indicated PUCCH 603 for PDSCH2. Consequently, this is not a valid scheduling of Figure 5. The above embodiment is as follows: PDCCH and PDSCH with and without repetition, PDCCH and PDSCH including multi-PDSCH scheduling PDCCH and PUSCH with and without repetition, and if PUSCH is counted based on available slots or physical slots, PDCCH and PUSCH including multi-PUSCH scheduling Note that this also applies to OOO handling for

[0097] In NR Rel-15, when a physical uplink control channel (PUCCH) in a single-slot transmission overlaps with a PUSCH in a single-slot transmission, the UE multiplexes uplink control information (UCI) on the PUSCH and drops the PUCCH if the timeline requirements specified in Section 9.2.5 of TS38.213 are met (Example 9). Furthermore, when a single-slot PUCCH overlaps with a multi-slot PUSCH repetition in a slot, the UE multiplexes UCI on the PUSCH in the overlapped slot and drops the PUCCH if the timeline requirements specified in Section 9.2.5 of TS38.213 are met for the overlapped slot.

[0098] In Rel-16, in the case of lacking DL grant and containing one PUSCH but no overlapping PUCCH with hybrid automatic repeat request acknowledgment (HARQ-ACK) within one PUCCH slot for both single carrier and UL carrier aggregation (CA) scenarios, if the uplink-total downlink assignment index (UL-TDAI) is not equal to 4 for Type-2 codebook or 1 for Type-1 codebook, the UE multiplexes the HARQ-ACK into the PUSCH according to the UL-TDAI.

[0099] In one example of HARQ-ACK on PUSCH in the case of lacking DL grant (Example 10), the UE lacks DL grant and correspondingly does not know the time domain allocation for PUCCH transmission. In the case where the UL-TDAI indicated in the UL grant for PUSCH scheduling is not equal to 4 in the case of Type 2 codebook or 1 in the case of Type 1 codebook, the UE multiplexes HARQ-ACK on PUSCH.

[0100] Furthermore, in the case of lacking a DL grant and including multiple overlapping PUSCHs within one PUCCH slot but not including overlapping PUCCHs with HARQ-ACK, it is up to the UE implementation how to handle the case where UL-TDAI n is not equal to 4 for Type-2 codebook or 1 for Type-1 codebook. Note that for PUSCH repetitions that do not include overlapping PUCCHs with HARQ-ACK within one PUCCH slot, if UL-TDAI n is not equal to 4 for Type-2 codebook or 1 for Type-1 codebook, a specific mechanism may need to be defined for HARQ-ACK multiplexing on PUSCH repetitions.

[0101] The embodiments disclosed herein provide a system and method for HARQ-ACK multiplexing on PUSCH repetitions in the absence of a DL grant. A system and method for HARQ-ACK and CSI multiplexing on PUSCH in the absence of a DL grant is also disclosed.

[0102] HARQ-ACK multiplexing on PUSCH repetitions in the absence of DL grant

[0103] As mentioned above, in Rel-16, in the case of lacking DL grant and including one PUSCH but no overlapping PUCCH with Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) within one PUCCH slot for both single carrier and UL Carrier Aggregation (CA) scenarios, if the Uplink Total Downlink Allocation Index (UL-TDAI) is not equal to 4 for Type-2 codebook or 1 for Type-1 codebook, the UE multiplexes the HARQ-ACK into the PUSCH according to the UL-TDAI.

[0104] Furthermore, in the case of lacking a DL grant and including multiple overlapping PUSCHs within one PUCCH slot but not including overlapping PUCCHs with HARQ-ACK, it is up to the UE implementation how to handle the case where UL-TDAI n is not equal to 4 for Type-2 codebook or 1 for Type-1 codebook. Note that for PUSCH repetitions that do not include overlapping PUCCHs with HARQ-ACK within one PUCCH slot, if UL-TDAI n is not equal to 4 for Type-2 codebook or 1 for Type-1 codebook, a specific mechanism may need to be defined for HARQ-ACK multiplexing on PUSCH repetitions.

[0105] An embodiment of HARQ-ACK multiplexing on PUSCH repetitions in the case of lacking DL grant is provided below.

[0106] In one embodiment, if UL-TDAI n is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook by including more than one PUSCH repetition and not including overlapping PUCCHs with HARQ-ACK within one PUCCH slot, the UE multiplexes the HARQ-ACK according to the UL-TDAI into the first PUSCH repetition in the PUCCH slot. Note that this may apply to PUSCH repetition Type A and PUSCH with transport block processing over multiple slots (TBoMS).

[0107] In an example (Example 11) of HARQ-ACK on a PUSCH repetition in the case where a DL grant for PUSCH repetition type A is lacking, the PUCCH is scheduled on CC#1 with a subcarrier spacing (SCS) of 15 kHz, and the PUSCH repetition is scheduled on CC#0 with an SCS of 60 kHz. Furthermore, the UE lacks a DL grant and, correspondingly, does not know the time-domain allocation for PUCCH transmission. If the UL-TDAI indicated in the UL grant for the PUSCH repetition is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE multiplexes HARQ-ACK on the first PUSCH repetition (Repetition #0) in the PUCCH slot.

[0108] In another embodiment, when a PUCCH slot contains more than one PUSCH repetition but does not contain an overlapping PUCCH with HARQ-ACK, if UL-TDAI n is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE multiplexes the HARQ-ACK onto all PUSCH repetitions in the PUCCH slot according to the UL-TDAI (Option 2). Alternatively, the UE multiplexes the HARQ-ACK onto all PUSCH repetitions according to the UL-TDAI (Option 3). Note that this can be applied to PUSCH repetition type A and PUSCH with TBoMS.

[0109] In one example (Example 12) of HARQ-ACK on PUSCH repetitions in the case of lacking a DL grant for PUSCH repetition type A, PUCCH is scheduled on CC#1 with a subcarrier spacing (SCS) of 15 kHz, and PUSCH repetitions are scheduled on CC#0 with an SCS of 60 kHz. Furthermore, the UE lacks a DL grant and, correspondingly, does not know the time-domain allocation for PUCCH transmission. If the UL-TDAI indicated in the UL grant for the PUSCH repetition is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE multiplexes HARQ-ACK on all PUSCH repetitions (repetitions #0, #1, #2, and #3) in the PUCCH slot.

[0110] In another embodiment, for PUSCH repetition type B, which includes more than one PUSCH repetition but does not include an overlapping PUCCH with HARQ-ACK within one PUCCH slot, if UL-TDAI n is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE multiplexes the HARQ-ACK according to the UL-TDAI into the first actual PUSCH repetition in the PUCCH slot.

[0111] In one example (Example 13) of HARQ-ACK on a PUSCH repetition in the case of lacking a DL grant for PUSCH repetition type B, the PUCCH is scheduled on CC#1 with a subcarrier spacing (SCS) of 15 kHz, and the PUSCH repetition is scheduled on CC#0 with an SCS of 30 kHz. Furthermore, the UE lacks a DL grant and, correspondingly, does not know the time-domain allocation for PUCCH transmission. In the case where the UL-TDAI indicated in the UL grant for the PUSCH repetition is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE multiplexes HARQ-ACK on the first actual PUSCH repetition (actual repetition #0) in the PUCCH slot.

[0112] In another embodiment, for PUSCH repetition type B, which includes more than one PUSCH repetition but does not include an overlapping PUCCH with HARQ-ACK within one PUCCH slot, if UL-TDAI n is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE multiplexes the HARQ-ACK onto all actual PUSCH repetitions in the PUCCH slot according to the UL-TDAI (Option 2). Alternatively, the UE multiplexes the HARQ-ACK onto all PUSCH repetitions according to the UL-TDAI (Option 3).

[0113] In one example (Example 14) of HARQ-ACK on PUSCH repetitions in the case of lacking a DL grant for PUSCH repetition type B, the PUCCH is scheduled on CC#1 with a subcarrier spacing (SCS) of 15 kHz, and the PUSCH repetition is scheduled on CC#0 with an SCS of 30 kHz. Furthermore, the UE lacks a DL grant and, correspondingly, does not know the time-domain allocation for PUCCH transmission. If the UL-TDAI indicated in the UL grant for the PUSCH repetition is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE multiplexes HARQ-ACK on all actual PUSCH repetitions (repetitions #0, #1, and #2) in the PUCCH slot.

[0114] In another embodiment, if all PUSCH repetitions do not contain overlapping PUCCHs with HARQ-ACKs, and if the UL-TDAI is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE multiplexes the HARQ-ACK onto the first PUSCH repetition according to the UL-TDAI (option 1), or the UE multiplexes the HARQ-ACK onto the first PUSCH repetition in each PUCCH slot according to the UL-TDAI (option 2), or the UE multiplexes the HARQ-ACK onto all PUSCH repetitions according to the UL-TDAI (option 3). Otherwise, the UE multiplexes the HARQ-ACK onto PUSCH repetitions that overlap with PUCCHs with HARQ-ACKs according to the UL-TDAI (option 4).

[0115] In an example (Example 15) of HARQ-ACK on a PUSCH repetition in the case where a DL grant is lacking for PUSCH repetition type A, the PUCCH is scheduled on CC#1 with a subcarrier spacing (SCS) of 15 kHz, and the PUSCH repetition is scheduled on CC#0 with an SCS of 30 kHz. Furthermore, the UE lacks a DL grant for PUCCH1 and, correspondingly, does not know the time-domain allocation for PUCCH transmission. In the case where the UL-TDAI indicated in the UL grant for the PUSCH repetition is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, and the UE does not detect any PUCCH that overlaps with any PUSCH repetition, the UE multiplexes HARQ-ACK on the first PUSCH repetition (Repetition#0) in the first PUCCS slot.

[0116] In one example (Example 16) of HARQ-ACK on PUSCH repetitions in the case where there is no DL grant for PUSCH repetition type A, in the case where the UL-TDAI indicated in the UL grant for the PUSCH repetition is not equal to 4 in the case of a Type 2 codebook or not equal to 1 in the case of a Type 1 codebook, and the UE does not detect a PUCCH that overlaps with any PUSCH repetition in a PUCCH slot (the first PUCCS slot including PUSCH repetitions #0 and #1), while the UE detects a PUCCH that overlaps with a PUSCH repetition in another PUCCH slot (PUCCH2 that overlaps with PUSCH repetition #2), the UE does not multiplex HARQ-ACK on PUSCH repetitions #0, #1, and #3, but instead multiplexes HARQ-ACK on PUSCH repetition #2 according to the UL DAI.

[0117] In another embodiment, for a PUSCH transmission including repetitions, if UL-TDAI n is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE multiplexes the HARQ-ACK onto all PUSCH repetitions according to the UL-TDAI. If the PUSCH repetition does not overlap with any PUCCH with HARQ-ACK, the UE multiplexes the N-bit NACK onto the PUSCH repetition according to the UL-DAI. If the PUSCH repetition overlaps with a PUCCH with HARQ-ACK, the UE multiplexes the M-bit HARQ-ACK onto the PUSCH repetition according to the UL-DAI to receive the PDSCH associated with the PUCCH. For example, for a Type-2 HARQ-ACK codebook, M=N+4*i and UL-DAI=N. As another example, for a Type-1 HARQ-ACK codebook, N=M, which is the size of the Type-1 HARQ-ACK codebook when n=1.

[0118] In an example (Example 17) of HARQ-ACK on PUSCH repetitions in the case where a DL grant for PUSCH repetition type A is lacking, PUCCH is scheduled on CC#1 with a subcarrier spacing (SCS) of 15 kHz, and PUSCH repetitions are scheduled on CC#0 with an SCS of 30 kHz. Furthermore, the UE lacks a DL grant for PUCCH1 and, correspondingly, does not know the time-domain allocation for PUCCH transmission. In the case where the UL-TDAI indicated in the UL grant for PUSCH repetitions is not equal to 4 for a Type 2 codebook or 1 for a Type 1 codebook, e.g., n=2 for a Type 2 HARQ-ACK codebook, the UE does not detect PUCCHs overlapping with PUSCH repetitions #0, #1, and #3, while the UE detects PUCCH2 overlapping with PUSCH repetition #2, and the UE receives five PDSCHs associated with PUCCH2. The UE multiplexes a 2-bit NACK into PUSCH repetitions #0, #1, and #3, and the UE multiplexes a 6-bit HARQ-ACK into PUSCH repetition #2.

[0119] Multiplexing of HARQ-ACK and CSI on PUSCH in the absence of DL grant

[0120] As mentioned above, in Rel-16, in the case of lacking DL grant and including one PUSCH but no overlapping PUCCH with Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) within one PUCCH slot for both single carrier and UL Carrier Aggregation (CA) scenarios, if the Uplink Total Downlink Allocation Index (UL-TDAI) is not equal to 4 for Type-2 codebook or 1 for Type-1 codebook, the UE multiplexes the HARQ-ACK into the PUSCH according to the UL-TDAI.

[0121] The UE may be expected to transmit both HARQ-ACK and CSI in a PUCCH slot. In some scenarios, the HARQ-ACK PUCCH resources overlap with the CSI PUCCH resources, and the UE multiplexes the HARQ-ACK and CSI in one resulting PUCCH, and then the UE multiplexes the resulting PUCCH onto the PUSCH. In some scenarios, the HARQ-ACK PUCCH resources do not overlap with the CSI PUCCH resources, and the UE multiplexes the HARQ-ACK PUCCH and the CSI PUCCH onto the PUSCH, respectively. The PUSCH selected for HARQ-ACK and the PUSCH selected for CSI may be the same or different PUSCHs according to the PUSCH selection rules specified in Rel-15 / 16.

[0122] In the case where a DL grant for HARQ-ACK is missing, the UE behavior of CSI transmission is unclear. Figure 9 shows an example. The HARQ-ACK PUCCH overlaps with PUSCH1 and PUSCH2, the CSI PUCCH overlaps with PUSCH2, and the HARQ-ACK PUCCH does not overlap with the CSI PUCCH in Case 1. On the other hand, the HARQ-ACK PUCCH overlaps with the CSI PUCCH in Case 2. If the UE misdetects the DL grant for HARQ-ACK, it is unclear how the UE transmits CSI. For example, if UL-TDAI n for both PUSCH1 and PUSCH2 is not equal to 4 for a type-2 codebook or 1 for a type-1 codebook, but the UE fails to detect the HARQ-ACK PUCCH, the UE does not know whether to multiplex CSI in PUSCH1 or PUSCH2 or drop the CSI.

[0123] In one embodiment, for a PUSCH that does not include an overlapping PUCCH with HARQ-ACK but has a PUCCH with CSI within one PUCCH slot, if UL-TDAI n is not equal to 4 for a Type 2 codebook or 1 for a Type 1 codebook, according to a predefined rule, the UE multiplexes the HARQ-ACK into one or more PUSCHs according to the UL-TDAI, and the UE multiplexes the CSI with HARQ-ACK in the same PUSCH. In these examples (Examples 18 and 19), if PUSCH1 is selected to multiplex the HARQ-ACK, the CSI is also multiplexed with the HARQ-ACK in PUSCH1, regardless of whether the CSI PUCCH overlaps with PUSCH1.

[0124] In another embodiment, for a PUSCH that does not include an overlapping PUCCH with HARQ-ACK but has a PUCCH with CSI within one PUCCH slot, if UL-TDAI n is not equal to 4 for a Type 2 codebook or 1 for a Type 1 codebook, the UE multiplexes the HARQ-ACK into one or more PUSCHs according to the UL-TDAI, and the UE drops the CSI according to a predefined rule. In these examples (Examples 18 and 19), CSI is dropped for all cases.

[0125] In another embodiment, for a PUSCH that does not include an overlapping PUCCH with HARQ-ACK but has a PUCCH with CSI within one PUCCH slot, if UL-TDAI n is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE multiplexes the HARQ-ACK into one or more PUSCHs according to the UL-TDAI according to a predefined rule, and if the CSI PUCCH resource overlaps with the PUSCH for HARQ-ACK multiplexing, the UE multiplexes the CSI with HARQ-ACK in the same PUSCH.

[0126] In one option, if the CSI PUCCH resources do not overlap with the PUSCH for HARQ-ACK multiplexing, the UE selects the PUSCH (if any) for CSI according to Rel-15 / 16 rules.

[0127] 9 illustrates HARQ-ACK and CSI on PUSCH in the case where there is no DL grant for PUSCH, according to some embodiments. In FIG. 9 (Example 18), for Case 1, the UE multiplexes HARQ-ACK on PUSCH1, and the UE multiplexes CSI on PUSCH2. For Case 2, the UE multiplexes HARQ-ACK and CSI on PUSCH1. In Example 19, for Case 3, the UE multiplexes HARQ-ACK on PUSCH1, and the UE transmits CSI PUCCH. For Case 4, the UE multiplexes HARQ-ACK on PUSCH1, and the UE multiplexes CSI on PUSCH2.

[0128] In another option, if the CSI PUCCH resource does not overlap with the PUSCH for HARQ-ACK multiplexing, the UE drops the CSI. For Cases 1, 3, and 4, the UE multiplexes the HARQ-ACK on PUSCH1 and drops the CSI. For Case 2, the UE multiplexes the HARQ-ACK and CSI on PUSCH1.

[0129] In another embodiment, for a PUSCH that does not include an overlapping PUCCH with HARQ-ACK but has a PUCCH with CSI within one PUCCH slot, if UL-TDAI n is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE multiplexes the HARQ-ACK into one or more PUSCHs according to the UL-TDAI according to a predefined rule, and the UE multiplexes CSI in the PUSCH according to Rel-15 / 16 rules.

[0130] In another embodiment, for a PUSCH that does not include an overlapping PUCCH with HARQ-ACK but has a PUCCH with CSI within one PUCCH slot, if UL-TDAI n is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, according to a predefined rule, the UE multiplexes the HARQ-ACK into one or more PUSCHs according to the UL-TDAI, and the UE selects a PUSCH for CSI according to the Rel-15 / 16 and UL-TDAI value.

[0131] In one option, if the PUSCH for the CSI selected according to the Rel-15 / 16 rules is a PUSCH with UL-DAI n equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE multiplexes the CSI in the PUSCH; otherwise, the UE multiplexes the HARQ-ACK and CSI in the same PUSCH for the HARQ-ACK, or the UE drops the CSI.

[0132] In another option, if the PUSCH for CSI selected according to the Rel-15 / 16 rules is a PUSCH with UL-DAI n not equal to 4 for a Type-2 codebook or not equal to 1 for a Type-1 codebook, the UE multiplexes the CSI in the PUSCH; otherwise, the UE multiplexes the HARQ-ACK and CSI in the same PUSCH for the HARQ-ACK, or the UE drops the CSI.

[0133] In another option, the PUSCH for the CSI is selected from PUSCHs with UL-TDAI n not equal to 4 for the Type-2 codebook or 1 for the Type-1 codebook (if any), and then the Rel-15 / 16 PUSCH selection rules are applied. If there is no PUSCH that overlaps with the CSI PUCCH with UL-TDAI n not equal to 4 for the Type-2 codebook or 1 for the Type-1 codebook, the UE multiplexes the HARQ-ACK and CSI in the same PUSCH for the HARQ-ACK. Alternatively, if there is no PUSCH that overlaps with the CSI PUCCH with UL-TDAI n not equal to 4 for the Type-2 codebook or 1 for the Type-1 codebook, the UE drops the CSI.

[0134] In the above embodiment, if the UE is configured with multiple PUCCH resources in a slot to transmit CSI in the PUCCH slot, the UE determines CSI multiplexing for each CSI PUCCH resource individually. Alternatively, the UE jointly determines CSI multiplexing for all CSI PUCCH resources. Alternatively, the UE determines CSI multiplexing for only one CSI PUCCH resource and drops the other CSI reports.

[0135] For example, for a PUSCH that does not include an overlapping PUCCH with HARQ-ACK but has one CSI PUCCH within one PUCCH slot, the UE determines CSI multiplexing according to one of the above embodiments. For a PUSCH that does not include an overlapping PUCCH with HARQ-ACK but has more than one CSI PUCCH within one PUCCH slot, if UL-TDAI n is not equal to 4 for a type-2 codebook or 1 for a type-1 codebook, the UE multiplexes the HARQ-ACK into one or more PUSCHs according to the UL-TDAI, and drops all CSI, according to a predefined rule. Alternatively, if more than one CSI PUCCH overlaps with a PUSCH with UL-TDAI n that is not equal to 4 for a type-2 codebook or 1 for a type-1 codebook, all CSI are multiplexed in the same PUSCH.

[0136] HARQ-ACK multiplexing over PUSCH in the absence of DL grant

[0137] As mentioned above, in the case of lacking a DL grant and including more than one PUSCH but no overlapping PUCCH with HARQ-ACK within one PUCCH slot for both single carrier and UL Carrier Aggregation (CA) scenarios, a specific mechanism needs to be defined for HARQ-ACK multiplexing on PUSCH when the Uplink Total Downlink Allocation Index (UL-TDAI) is not equal to 4 for Type 2 codebook or 1 for Type 1 codebook.

[0138] In the case of different SCSs of the PUCCH cell and other cells, the slot length may be different for different cells. For example, if the SCS of the PUCCH cell is 30 kHz, while the SCS of another cell with a PUSCH is 15 kHz, the PUSCH may overlap with two PUCCH slots. Furthermore, a PUCCH slot may be a slot or a subslot. In the case of PUCCH resources consisting of subslots, the PUCCH slot length may be shorter than that of the PUSCH slot. For example, if the SCS of all cells is 15 kHz, the PUCCH consists of two-symbol subslots, and the PUSCH may overlap with up to seven subslots. If one PUCCH slot overlaps with more than one PUSCH and at least one of the PUSCHs crosses the PUCCH slot, the UE behavior of HARQ-ACK multiplexing on the PUSCH in the case of a lack of DL grant becomes unclear.

[0139] In one embodiment, for a PUCCH slot that does not contain a PUCCH with HARQ-ACK, if at least one PUSCH overlapping with the PUCCH slot has an UL-TDAI n that is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE determines candidate PUSCHs for HARQ-ACK multiplexing, where the candidate PUSCHs are all PUSCHs overlapping with the PUCCH slot or a subset of all PUSCHs overlapping with the PUCCH slot, for example, PUSCHs with an UL-TDAI n that is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook. The UE selects one PUSCH from the candidate PUSCHs and multiplexes the HARQ-ACK onto the PUSCH according to the UL-TDAI of the PUSCH. If the UE determines that more than one PUCCH with HARQ-ACK is multiplexed on the same PUSCH, the UE considers this an error case or the UE behavior is not specified. It should be noted that the PUSCH for HARQ-ACK multiplexing may be the first PUSCH or the last PUSCH of the candidate PUSCHs.

[0140] In some examples (Examples 20A and 20B) of a PUSCH spanning two subslots for a PUCCH with HARQ-ACK in the case where a DL grant is missing, assuming that the UE receives a DL grant for PUCCH2, the UE multiplexes PUCCH2 with PUSCH2 according to the existing UCI multiplexing procedure (Example 20A). The UE does not receive a DL grant for PUCCH1, but the UE receives a UL grant for PUSCH1 with UL TDAI=2. The UE expects a PUCCH with HARQ-ACK in subslot #0, but the UE misdetects the DL grant. In this case, the UE determines PUSCH1 as a candidate PUSCH for subslot #0 and multiplexes the HARQ-ACK of PUCCH1 in subslot #0 onto PUSCH1. In Example 20B, assuming that the UE receives a DL grant for PUCCH1, the UE multiplexes PUCCH1 with PUSCH1 according to the existing UCI multiplexing procedure. The UE does not receive a DL grant for PUCCH2, but it receives an UL grant for PUSCH2 with UL TDAI=2. Because PUSCH2 is in subslot #1, the UE expects a PUCCH with HARQ-ACK in subslot #1, but the UE misdetects the DL grant. In this case, the UE determines PUSCH1 and PUSCH2 as candidate PUSCHs for subslot 1. If the UE selects PUSCH1 for HARQ-ACK multiplexing, e.g., the first PUSCH that overlaps with subslot 1, but multiplexing two PUCCHs with HARQ-ACK into one PUSCH is not supported (at least, intra-UE multiplexing between different priorities is not configured), the UE considers this an error case.

[0141] In another embodiment, for a PUCCH slot that does not contain a PUCCH with HARQ-ACK, if at least one PUSCH overlapping with the PUCCH slot has UL-TDAI n not equal to 4 for a Type-2 codebook or not equal to 1 for a Type-1 codebook, the UE determines candidate PUSCHs for HARQ-ACK multiplexing, where the candidate PUSCHs are all PUSCHs overlapping with the PUCCH slot or a subset of all PUSCHs overlapping with the PUCCH slot, for example, PUSCHs with UL-TDAI n not equal to 4 for a Type-2 codebook or not equal to 1 for a Type-1 codebook. The UE selects one PUSCH from the candidate PUSCHs for HARQ-ACK multiplexing. Note that the PUSCH for HARQ-ACK multiplexing may be the first PUSCH or the last PUSCH among the candidate PUSCHs. If the UE determines that more than one PUCCH with HARQ-ACK is multiplexed on the same PUSCH, the UE multiplexes only the HARQ-ACK from one PUCCH onto the PUSCH according to the UL-TDAI for the PUSCH. For example, if the UE receives a DL grant for one PUCCH with HARQ-ACK, the UE multiplexes the PUCCH onto the PUSCH. As another example, if the UE does not receive any DL grant from any PUCCH with HARQ-ACK, the UE multiplexes one PUCCH onto the PUSCH, all with NACKs.

[0142] In an example (Example 21) of a PUSCH spanning two subslots for a PUCCH with HARQ-ACK in the case where a DL grant is lacking, assuming that the UE receives a DL grant for PUCCH1, the UE multiplexes the HARQ-ACK from PUCCH1 on PUSCH1 according to the existing UCI multiplexing procedure. The UE does not receive a DL grant for PUCCH2. The UE determines PUSCH1 and PUSCH2 as candidate PUSCHs for subslot 1, and the UE selects PUSCH1 for HARQ-ACK multiplexing, e.g., the first PUSCH that overlaps with subslot 1. On the other hand, the UE also determines PUSCH1 and PUSCH2 as candidate PUSCHs for subslot 2. However, because multiplexing two PUCCHs with HARQ-ACK into one PUSCH is not supported (at least when intra-UE multiplexing between different priorities is not configured), the UE does not multiplex PUCCH2 on either PUSCH.

[0143] In another embodiment, for a PUCCH slot that does not contain a PUCCH carrying HARQ-ACK, if at least one PUSCH overlapping with the PUCCH slot has a UL-TDAI n that is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE determines candidate PUSCHs for HARQ-ACK multiplexing, and the PUSCHs already determined for multiplexing HARQ-ACK feedback for the previous PUCCH slot are excluded from the candidate PUSCHs for the PUCCH slot.

[0144] For examples 20B and 21, PUSCH1 is already selected for multiplexing with PUCCH1, so PUSCH1 is excluded from the candidate PUSCHs for subslot 1. Therefore, the UE multiplexes the HARQ-ACK for subslot 1 onto PUSCH2.

[0145] In another embodiment, for a PUCCH slot that does not contain a PUCCH with HARQ-ACK, if at least one PUSCH restricted in the PUCCH slot has an UL-TDAI n that is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE determines candidate PUSCHs for HARQ-ACK multiplexing, the PUSCHs that are not restricted in the PUCCH slot are excluded from the candidate PUSCHs for the PUCCH slot, and the UE selects one PUSCH from the candidate PUSCHs and multiplexes the HARQ-ACK on the PUSCH according to the UL-TDAI; otherwise, the UE does not multiplex the HARQ-ACK on the PUSCH, or the UE behavior is not specified. It should be noted that the PUSCH for HARQ-ACK multiplexing may be the first PUSCH or the last PUSCH of the candidate PUSCHs.

[0146] For example 20B, for subslot 1, PUSCH2 with UL-TDAI=2 is restricted in subslot 1. Therefore, the UE may identify PUCCH in subslot 1, but the UE does not receive any DL grant for PUCCH2. The UE multiplexes PUCCH2 with PUSCH2. For example 21, there is no PUSCH restricted in subslot 1. The UE may not specify whether there is a PUCCH in subslot 1. The UE does not multiplex PUCCH with PUSCH for subslot 1.

[0147] In one embodiment, if the UE is configured with more than one priority, e.g., configured with LP and HP PUCCH resources, the UE determines whether it is missing a DL grant for a PUCCH with HARQ-ACK by checking the UL TDAI of the PUSCHs with the respective priorities.

[0148] In Example 21, the PUCCH slots HP PUSCH1 and LP PUSCH2 overlap with the PUCCH slot. Since the UE is configured with both LP and HP PUCCH resources, if both the LP and HP are configured with slots for PUCCH resources, the gNB may schedule the PUCCH with HARQ-ACK for the LP and the PUCCH with HARQ-ACK for the HP, respectively, in the same PUCCH slot. Although the UE does not receive any DL grant for the LP HARQ-ACK, the UE receives an UL grant for the LP PUSCH2 with UL TDAI=2; therefore, the UE identifies the missing PUCCH for the LP HARQ-ACK, and the UE selects the LP PUSCH2 for multiplexing the LP HARQ-ACK.

[0149] In the above embodiment, for a PUSCH that does not overlap with any PUCCH but where the HARQ-ACK is piggybacked onto the PUSCH according to the UL DAI, the UE generates an N-bit NACK according to the UL DAI value n.

[0150] In the above embodiments, different options may be applied for different HARQ-ACK codebook types. In the above embodiments, different options may be applied for different PUSCH repetition types, such as Type A or Type B repetition, PUSCH with transport block processing over multiple slots (TBoMS), and multi-PUSCH scheduling with a single DCI. In the case of multi-PUSCH scheduling with a single DCI, the PUSCH repetition discussed above is replaced with a PUSCH transmission. It should be noted that for the above embodiments, the UE is expected to meet the timeline for UCI multiplexing on PUSCH specified in Section 9.2.5 of TS38.213. Furthermore, the above embodiments may be applied to single carrier and CA scenarios.

[0151] In some embodiments, when a UE is scheduled by a gNB for transmission of multiple PUSCHs on its respective serving cell and the multiple PUSCHs overlap with a PUCCH carrying uplink control information (UCI) in a slot, the UE may select the PUSCH that overlaps with the PUCCH carrying UCI as a candidate PUSCH for UCI multiplexing in the slot. In these embodiments, when at least one of the multiple PUSCHs is scheduled by a DCI format that includes a downlink allocation index (DAI) field, for HARQ-ACK multiplexing, the UE may be configured to exclude one or more of the candidate PUSCHs for HARQ-ACK multiplexing that are scheduled by a DCI format that includes a DAI field equal to 4 or equal to 0 if a PUCCH carrying HARQ-ACK information bits has not been determined for the slot. In these embodiments, the UE may select one or more of the remaining candidate PUSCHs that have not been excluded for HARQ-ACK multiplexing.

[0152] In these embodiments, if the UE does not determine a PUCCH that carries the HARQ-ACK information bit for a slot, this may be because the UE misdetected the PDCCH that scheduled the PDSCH. Therefore, the HARQ-ACK information bit is not generated because the UE did not receive the scheduled PDSCH. In these embodiments, the UE understands that the HARQ-ACK is not multiplexed on the PUSCH with UL-DAI4 because the UE did not receive the corresponding PDSCH.

[0153] In these embodiments, for a slot, one of the remaining candidate PUSCHs is selected for HARQ-ACK multiplexing, even though the PUCCH carrying the HARQ-ACK information bits has not been determined. In these embodiments, the PUSCH data may be rate-matched around the UCI in the PUSCH. To avoid the impact of an incorrect UCI payload caused by a false detection of the PDCCH for the PDSCH associated with the HARQ-ACK, the UE may transmit dummy bits as HARQ-ACK information bits instead of the UCI part in the PUSCH and perform rate matching of the data part around the UCI part in the PUSCH. This may help ensure the correct data part in the PUSCH.

[0154] In some embodiments, if a PUCCH carrying a HARQ-ACK information bit for a slot has been determined, the UE may be configured to avoid excluding candidate PUSCHs scheduled by a DCI format including a DAI field equal to 4 or equal to 0.

[0155] In some embodiments, if the PUCCH carrying HARQ-ACK information bits for a slot has not been determined, to exclude one or more of the candidate PUSCHs for HARQ-ACK multiplexing that are scheduled by a DCI format including a DAI field equal to 4 or equal to 0, if the UE is configured with a dynamic pdsch-HARQ-ACK-Codebook, the UE may exclude any one or more of the candidate PUSCHs that are scheduled by a DCI format including a DAI field equal to 4. In these embodiments, if the UE is configured with a semi-static pdsch-HARQ-ACK-Codebook, the UE may also exclude any one or more of the candidate PUSCHs that are scheduled by a DCI format including a DAI field equal to 0.

[0156] In some embodiments, the UCI may include HARQ-ACK information bits and channel state information (CSI). In these embodiments, due to the multiplexing of CSI, the UE may avoid excluding candidate PUSCHs that are scheduled by a DCI format that includes a DAI field equal to 4 or 0. In some embodiments, the PUCCH carrying the CSI may be a different PUCCH from the PUCCH carrying the HARQ-ACK information bits, although the scope of this embodiment is not limited in this respect. In these embodiments, the PUCCH carrying the CSI and the PUCCH carrying the HARQ-ACK information bits may both be transmitted in the same slot.

[0157] In some embodiments, if more than one of the candidate PUSCHs is scheduled by a dynamic grant (DG) (DG PUSCH), the UE may select one of the DG PUSCHs with the smallest serving cell index. In these embodiments, if more than one of the DG PUSCHs has the smallest serving cell index, the UE may select one of the DG PUSCHs that is earliest in the slot.

[0158] In some embodiments, if none of the candidate PUSCHs are scheduled by a dynamic grant and at least one of the candidate PUSCHs is scheduled by a configured grant (CG) (CG PUSCH), the UE may select one of the CG PUSCHs with the smallest serving cell index. In these embodiments, more than one of the CG PUSCHs may have the smallest serving cell index. In these embodiments, the UE may select one of the CG PUSCHs that is earlier in the slot. In some of these embodiments, the UE may first check whether there is a scheduled CG PUSCH or a DG PUSCH. If there is a scheduled DG PUSCH, the UE selects the DG PUSCH. If more than one DG PUSCH is scheduled, the UE selects the DG PUSCH with the smallest serving cell index. If there is no scheduled DG PUSCH and multiple CG PUSCHs, the UE selects the CG PUSCH with the smallest serving cell index. If there is more than one PUSCH with the smallest serving cell index, the UE selects the earliest PUSCH in the slot.

[0159] example 1. Example 1: Wireless communication system and method for out-of-order handling on a PDSCH and associated PUCCS for HARQ-ACK transmission. 2. The method of Example 1, wherein if PUCCH repetition is configured for the UE, the OOO check of the PDSCH and associated PUCCH for the serving cell refers to the indicated slot and / or available slot for PUCCH repetition. 3. The method of Example 2, wherein the OOO check is defined based on the PDSCH and the indicated first PUCCH repetition for the PDSCH. 4. The method of Example 2, wherein the OOO check is defined based on the PDSCH and the first available PUCCH repetition for the PDSCH. 5. The method of Example 2, wherein the OOO check is defined based on the PDSCH and all available PUCCH repetitions for the PDSCH. 6. The method of example 2, wherein the OOO check is defined based on the PDSCH and the first indicated PUCCH repetition for the PDSCH and all available PUCCH repetitions. 7. The method of example 2, wherein the OOO check is defined based on the PDSCH and the first indicated PUCCH repetition and the last available PUCCH repetition for the PDSCH. 8. The method described in Example 1, where PUCCH reservation is configured for the UE, the OOO check of the PDSCH and associated PUCCH for the serving cell references the indicated PUCCH slot and / or available slots reserved for PUCCH transmission, if applicable. 9. The method of Example 2 based on the PDSCH and the indicated PUCCH for the PDSCH. 10. The method of Example 2 based on PDSCH and available PUCCH for PDSCH. 11. The method of Example 2 based on the PDSCH and the indicated PUCCH for the PDSCH, and, if applicable, the reserved PUCCH.

[0160] Additional Examples 1. Example 1A: System and method for wireless communications for a fifth generation (5G) or new radio (NR) system: A UE determines, within one PUCCH slot, one or more Physical Uplink Shared Channel (PUSCH) repetitions that do not overlap with a Physical Uplink Control Channel (PUCCH) having a Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK); and the UE multiplexes HARQ-ACK feedback onto the determined one or more PUSCH repetitions. 2. The method of Example 1A, wherein if UL-TDAI n is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook due to including more than one PUSCH repetition and not including overlapping PUCCH with HARQ-ACK within one PUCCH slot, the UE multiplexes HARQ-ACK according to UL-TDAI into the first PUSCH repetition in the PUCCH slot. 3. The method of Example 1A, in which if UL-TDAI n is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook due to including more than one PUSCH repetition and not including overlapping PUCCHs with HARQ-ACK within one PUCCH slot, the UE multiplexes HARQ-ACK according to UL-TDAI into all PUSCH repetitions in the PUCCH slot. 4. The method of Example 1A, wherein if UL-TDAI n is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook due to including more than one PUSCH repetition and not including overlapping PUCCHs with HARQ-ACK within one PUCCH slot, the UE multiplexes HARQ-ACK into all PUSCH repetitions according to UL-TDAI. 5. The method of Example 1A, wherein the PUSCH repetition is for PUSCH with PUSCH repetition type A and TBoMS. 6. For PUSCH repetition type B, which includes more than one PUSCH repetition but does not include an overlapping PUCCH with HARQ-ACK within one PUCCH slot, if UL-TDAI n is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE multiplexes the HARQ-ACK into the first actual PUSCH repetition in the PUCCH slot according to the UL-TDAI. The method of Example 1A. 7. For PUSCH repetition type B, which includes more than one PUSCH repetition but does not include overlapping PUCCH with HARQ-ACK within one PUCCH slot, if UL-TDAI n is not equal to 4 for a Type 2 codebook or 1 for a Type 1 codebook, the UE multiplexes HARQ-ACK into all actual PUSCH repetitions in the PUCCH slot according to the UL-TDAI. The method according to Example 1A. 8. For PUSCH repetition type B, which includes more than one PUSCH repetition but does not include overlapping PUCCH with HARQ-ACK within one PUCCH slot, if UL-TDAI n is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE multiplexes HARQ-ACK into all actual PUSCH repetitions according to UL-TDAI. The method according to Example 1A. 9. If all PUSCH repetitions do not contain overlapping PUCCHs with HARQ-ACK, and if the UL-TDAI is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE multiplexes the HARQ-ACK onto the first PUSCH repetition according to the UL-TDAI (option 1), or the UE multiplexes the HARQ-ACK onto the first PUSCH repetition in each PUCCH slot according to the UL-TDAI (option 2), or the UE multiplexes the HARQ-ACK onto all PUSCH repetitions according to the UL-TDAI (option 3), the method of Example 1A. Otherwise, the UE multiplexes the HARQ-ACK onto PUSCH repetitions that overlap with PUCCHs with HARQ-ACK according to the UL-TDAI (option 4). 10. For a PUSCH transmission with repetitions, if UL-TDAI n is not equal to 4 for a Type-2 codebook or 1 for a Type-1 codebook, the UE multiplexes HARQ-ACK into all PUSCH repetitions according to UL-TDAI. If the PUSCH repetition does not overlap with any PUCCH with HARQ-ACK, the UE multiplexes N-bit NACK into the PUSCH repetition according to UL-DAI. 11. The method of Example 1A, wherein for a PUSCH that does not overlap with any PUCCH but where a HARQ-ACK is piggybacked onto the PUSCH according to the UL DAI, the UE generates an N-bit NACK according to the UL DAI value n. 12. The method of Example 1A, wherein the timeline for UCI multiplexing on PUSCH is met. 13. The method described in Example 1A, wherein the above embodiment can be applied to single carrier and carrier aggregation (CA) scenarios. 14. For a PUSCH that does not include an overlapping PUCCH with HARQ-ACK but has a PUCCH with CSI within one PUCCH slot, if UL-TDAI n is not equal to 4 for a type-2 codebook or is not equal to 1 for a type-1 codebook, according to a predefined rule, the UE multiplexes the HARQ-ACK into one or more PUSCHs according to the UL-TDAI, and the UE multiplexes the CSI with HARQ-ACK in the same PUSCH. The method according to Example 1A. 15. For a PUSCH that does not include an overlapping PUCCH with HARQ-ACK but has a PUCCH with CSI within one PUCCH slot, if UL-TDAI n is not equal to 4 in the case of a type 2 codebook or is not equal to 1 in the case of a type 1 codebook, according to a predefined rule, the UE multiplexes the HARQ-ACK into one or more PUSCHs according to the UL-TDAI, and the UE drops the CSI. The method according to Example 1A. 16. For a PUSCH that does not include an overlapping PUCCH with HARQ-ACK but has a PUCCH with CSI within one PUCCH slot, if UL-TDAI n is not equal to 4 in the case of a type-2 codebook or is not equal to 1 in the case of a type-1 codebook, the UE multiplexes the HARQ-ACK into one or more PUSCHs according to the UL-TDAI according to a predefined rule, and if the CSI PUCCH resource overlaps with the PUSCH for HARQ-ACK multiplexing, the UE multiplexes the CSI with HARQ-ACK in the same PUSCH. The method according to Example 1A. 17. For a PUSCH that does not include an overlapping PUCCH with HARQ-ACK but has a PUCCH with CSI within one PUCCH slot, if UL-TDAI n is not equal to 4 for a Type 2 codebook or 1 for a Type 1 codebook, the UE multiplexes the HARQ-ACK into one or more PUSCHs according to the UL-TDAI according to a predefined rule, and the UE multiplexes CSI in the PUSCH according to Rel-15 / 16 rules. The method according to Example 1A. 18. For a PUSCH that does not include an overlapping PUCCH with HARQ-ACK but has a PUCCH with CSI within one PUCCH slot, if UL-TDAI n is not equal to 4 for a type-2 codebook or is not equal to 1 for a type-1 codebook, according to a predefined rule, the UE multiplexes the HARQ-ACK into one or more PUSCHs according to the UL-TDAI, and the UE selects a PUSCH for CSI according to the Rel-15 / 16 and UL-TDAI value. The method according to Example 1A.

[0161] 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. The Abstract 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.

Claims

1. 1. A user equipment (UE) apparatus configured for operation in a fifth generation (5G) new radio (NR) network, the apparatus comprising: a processing circuit; and a memory, the processing circuit comprising: Decoding a first physical downlink shared channel (PDSCH) and a second PDSCH received from a next generation Node B (gNB), where at least the first PDSCH is configured for downlink semi-persistent scheduling (SPS); generating a first hybrid automatic repeat request acknowledgement (HARQ-ACK) information bit based on the first PDSCH and a second HARQ-ACK information bit based on the second PDSCH; The device is configured to: If the UE is configured to reserve a HARQ-ACK for the first PDSCH, the processing circuitry: and configured to determine a first slot for an expected physical uplink control channel (PUCCH) transmission having the first HARQ-ACK information bit assigned to the first PDSCH based on a first feedback timing provided by the gNB; If the first slot is not available for the expected PUCCH transmission of the first HARQ-ACK information bit, the processing circuitry further determines an earliest second slot available for a PUCCH transmission including the first HARQ-ACK information bit, the earliest second slot being the earliest slot available for the PUCCH transmission after the first slot; and determining a third slot for expected PUCCH transmission having the second HARQ-ACK information bit assigned to the second PDSCH based on a second feedback timing provided by the gNB; and verifying that, for the scheduled cell, if the second PDSCH starts later than the first PDSCH, resources allocated by the second feedback timing for transmission of the second HARQ-ACK information bit do not end before a start of resources allocated by the first feedback timing for transmission of the first HARQ-ACK information bit. The device is configured to: The memory is configured to store the first HARQ-ACK information bit. Device.

2. the resource allocated for transmission of the second HARQ-ACK information bit is determined based on the second feedback timing and is within the third slot; The resource allocated for transmission of the first HARQ-ACK information bit is determined based on the first feedback timing and is within the first slot.

2. The apparatus of claim 1.

3. If the UE is configured to reserve a HARQ-ACK for the first PDSCH, the processing circuitry: encoding the first HARQ-ACK information bit for the PUCCH transmission by the UE in the first slot if the first slot is available for the expected PUCCH transmission of the first HARQ-ACK information bit; and encoding a first HARQ-ACK information bit for the PUCCH transmission by the UE in the first-most second slot if the first slot is not available for the anticipated PUCCH transmission of the first HARQ-ACK information bit. The apparatus of claim 2 , configured to:

4. If the UE is not configured to reserve HARQ-ACK for SPS PDSCH, the processing circuitry: encoding the first HARQ-ACK information bit for the PUCCH transmission by the UE in the first slot if the first slot is available for the expected PUCCH transmission of the first HARQ-ACK information bit; and Dropping the PUCCH transmission of the first HARQ-ACK information bit if the first slot is not available for the expected PUCCH transmission of the first HARQ-ACK information bit. The apparatus of claim 3 configured to:

5. If the UE is configured to reserve a HARQ-ACK for the first PDSCH, the processing circuitry: encoding a first HARQ-ACK information bit for the PUCCH transmission by the UE in the first-most second slot if the first slot is not available for the anticipated PUCCH transmission of the first HARQ-ACK information bit; and encoding the second HARQ-ACK information bit for the PUCCH transmission by the UE in the third slot; The apparatus of claim 4 configured to:

6. 6. The apparatus of claim 5, wherein the first-most second slot is the same slot as the third slot, and the processing circuitry is configured to encode the first HARQ-ACK information bit and the second HARQ-ACK information bit for the PUCCH transmission in the first-most second slot.

7. If the UE is configured to withhold a HARQ-ACK for the first PDSCH, the processing circuitry determines whether a PUCCH resource for the anticipated PUCCH transmission is: overlaps with symbols indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigDedicated; and / or Overlapped with synchronization signal / PBCH block (SSB) The apparatus according to claim 1 , further configured to determine that the first slot is unavailable if

8. When the UE is scheduled by the gNB for transmission of multiple PUSCHs on respective serving cells, and the multiple PUSCHs overlap with a PUCCH carrying uplink control information (UCI) in a slot, the processing circuitry: configured to select a PUSCH that overlaps with the PUCCH carrying the UCI as a candidate PUSCH for UCI multiplexing in the slot; When at least one of the plurality of PUSCHs is scheduled by a DCI format that includes a downlink allocation index (DAI) field, for HARQ-ACK multiplexing, the processing circuitry: excluding one or more of the candidate PUSCHs for HARQ-ACK multiplexing scheduled by a DCI format including a DAI field equal to 4 or equal to 0 if a PUCCH carrying a HARQ-ACK information bit has not been determined for the slot; and Selecting one or more of the candidate PUSCHs that are not excluded for HARQ-ACK multiplexing. The apparatus of claim 1 configured to:

9. 1. A non-transitory computer-readable storage medium storing instructions executed by a processing circuit of a user equipment (UE) configured for operation in a fifth generation (5G) new radio (NR) network, the processing circuit comprising: Decoding a first physical downlink shared channel (PDSCH) and a second PDSCH received from a next generation Node B (gNB), where at least the first PDSCH is configured for downlink semi-persistent scheduling (SPS); generating a first hybrid automatic repeat request acknowledgement (HARQ-ACK) information bit based on the first PDSCH and a second HARQ-ACK information bit based on the second PDSCH; The device is configured to: If the UE is configured to reserve a HARQ-ACK for the first PDSCH, the processing circuitry: and configured to determine a first slot for an expected physical uplink control channel (PUCCH) transmission having the first HARQ-ACK information bit assigned to the first PDSCH based on a first feedback timing provided by the gNB; If the first slot is not available for the expected PUCCH transmission of the first HARQ-ACK information bit, the processing circuitry further determines an earliest second slot available for a PUCCH transmission including the first HARQ-ACK information bit, the earliest second slot being the earliest slot available for the PUCCH transmission after the first slot; and determining a third slot for expected PUCCH transmission having the second HARQ-ACK information bit assigned to the second PDSCH based on a second feedback timing provided by the gNB; and verifying that, for the scheduled cell, if the second PDSCH starts later than the first PDSCH, resources allocated by the second feedback timing for transmission of the second HARQ-ACK information bit do not end before a start of resources allocated by the first feedback timing for transmission of the first HARQ-ACK information bit. It is configured to A non-transitory computer-readable storage medium.

10. the resource allocated for transmission of the second HARQ-ACK information bit is determined based on the second feedback timing and is within the third slot; The resource allocated for transmission of the first HARQ-ACK information bit is determined based on the first feedback timing and is within the first slot.

10. The non-transitory computer-readable storage medium of claim 9.

11. If the UE is configured to reserve a HARQ-ACK for the first PDSCH, the processing circuitry: encoding the first HARQ-ACK information bit for the PUCCH transmission by the UE in the first slot if the first slot is available for the expected PUCCH transmission of the first HARQ-ACK information bit; and encoding a first HARQ-ACK information bit for the PUCCH transmission by the UE in the first-most second slot if the first slot is not available for the anticipated PUCCH transmission of the first HARQ-ACK information bit.

11. The non-transitory computer-readable storage medium of claim 10 configured to:

12. If the UE is not configured to reserve HARQ-ACK for SPS PDSCH, the processing circuitry: encoding the first HARQ-ACK information bit for the PUCCH transmission by the UE in the first slot if the first slot is available for the expected PUCCH transmission of the first HARQ-ACK information bit; and Dropping the PUCCH transmission of the first HARQ-ACK information bit if the first slot is not available for the expected PUCCH transmission of the first HARQ-ACK information bit.

12. The non-transitory computer-readable storage medium of claim 11 configured to:

13. If the UE is configured to reserve a HARQ-ACK for the first PDSCH, the processing circuitry: encoding a first HARQ-ACK information bit for the PUCCH transmission by the UE in the first-most second slot if the first slot is not available for the anticipated PUCCH transmission of the first HARQ-ACK information bit; and encoding the second HARQ-ACK information bit for the PUCCH transmission by the UE in the third slot; 13. The non-transitory computer-readable storage medium of claim 12, configured to:

14. 14. The non-transitory computer-readable storage medium of claim 13, wherein the first-most second slot is the same slot as the third slot, and the processing circuitry is configured to encode the first HARQ-ACK information bit and the second HARQ-ACK information bit for the PUCCH transmission in the first-most second slot.

15. 1. A user equipment (UE) apparatus configured for operation in a fifth generation (5G) new radio (NR) network, the apparatus comprising: a processing circuit; and a memory; When the UE is scheduled by a next generation Node B (gNB) for transmission of multiple physical uplink shared channels (PUSCHs) on respective serving cells, and the multiple PUSCHs overlap with a physical uplink control channel (PUCCH) carrying uplink control information (UCI) in a slot, the processing circuitry: configured to select a PUSCH that overlaps with the PUCCH carrying the UCI as a candidate PUSCH for UCI multiplexing in the slot; When at least one of the plurality of PUSCHs is scheduled by a downlink control information (DCI) format that includes a downlink allocation index (DAI) field, for hybrid automatic repeat request-acknowledgement (HARQ-ACK) multiplexing, the processing circuitry: excluding one or more of the candidate PUSCHs for HARQ-ACK multiplexing scheduled by a DCI format including a DAI field equal to 4 or equal to 0 if a PUCCH carrying a HARQ-ACK information bit has not been determined for the slot; and Selecting one or more of the candidate PUSCHs that are not excluded for HARQ-ACK multiplexing. The apparatus is configured to:

16. 16. The apparatus of claim 15, wherein the processing circuitry is configured to avoid excluding a candidate PUSCH scheduled by a DCI format including a DAI field equal to 4 or equal to 0 when a PUCCH carrying a HARQ-ACK information bit has been determined for the slot.

17. For the slot, if a PUCCH carrying a HARQ-ACK information bit has not been determined, to exclude the one or more of the candidate PUSCHs for the HARQ-ACK multiplexing scheduled by a DCI format including a DAI field equal to 4 or equal to 0, the processing circuitry further comprises: If the UE is configured with a dynamic pdsch-HARQ-ACK-Codebook, excluding any one or more of the candidate PUSCHs that are scheduled by a DCI format including a DAI field equal to 4; If the UE is configured with a semi-static pdsch-HARQ-ACK-Codebook, exclude any one or more of the candidate PUSCHs that are scheduled by a DCI format that includes a DAI field equal to 0.

17. The apparatus of claim 16, configured to:

18. The UCI comprises HARQ-ACK information bits and channel state information (CSI); For the multiplexing of the CSI, the processing circuit is configured to avoid excluding a candidate PUSCH that is scheduled by a DCI format that includes a DAI field equal to 4 or 0.

20. The apparatus of claim 17.

19. If more than one of the candidate PUSCHs is scheduled by a dynamic grant (DG) (DG PUSCH), the processing circuit is configured to select one of the DG PUSCHs having a smallest serving cell index; If more than one of the DG PUSCHs has the smallest serving cell index, the processing circuit selects one of the DG PUSCHs that is front-most in the slot.

20. The apparatus of claim 18.

20. When none of the candidate PUSCHs is scheduled by a dynamic grant and at least one of the candidate PUSCHs is scheduled by a configuration grant (CG) (CG PUSCH), the processing circuit is configured to select one of the CG PUSCHs having a smallest serving cell index; If more than one of the CG PUSCHs has the smallest serving cell index, the processing circuit selects one of the CG PUSCHs that is frontmost in the slot.

20. The apparatus of claim 19.

Images