Reliable HARQ-ACK transmission in unlicensed spectrum

By using a selective one-time HARQ feedback method, WTRU generates a HARQ codebook based on TB priority and selects the transmission power, which solves the problems of high-priority HARQ-ACK transmission reliability and resource utilization in URLLC services in unlicensed spectrum, and improves the reliability and latency performance of URLLC services.

CN118944820AActive Publication Date: 2024-11-12INTERDIGITAL PATENT HOLDINGS INC
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
CN202411351216.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2020-08-04
Filing Date
2021-02-11
Publication Date
2024-11-12
Estimated Expiration
2041-02-11

AI Technical Summary

Technical Problem

In unlicensed spectrum, the wireless transmit/receive unit (WTRU) of Ultra Reliable Low Latency Communication (URLLC) services faces high transmission power requirements and interference issues for reliable transmission of high-priority HARQ-ACK under the Hybrid Automatic Repeat Request (HARQ) mechanism. Existing HARQ-ACK codebooks fail to effectively consider priorities, resulting in transmissions that are unsuitable for resource utilization.

Method used

The selective one-time HARQ feedback method is adopted. The WTRU determines the HARQ codebook according to the priority of TB, generates and transmits the HARQ codebook including ACK or NACK bits, and selects the transmission power based on priority to ensure reliable transmission of high-priority HARQ-ACK.

Benefits of technology

It improves the transmission reliability of high-priority HARQ-ACK, reduces interference and power scaling, optimizes resource utilization, and enhances the reliability and latency performance of URLLC services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118944820A_ABST
    Figure CN118944820A_ABST
Patent Text Reader

Abstract

The invention describes reliable HARQ-ACK transmission in unlicensed spectrum, and specifically describes a method and apparatus for selective one-time hybrid automatic repeat request (HARQ) feedback at a priority level. For example, a wireless transmit / receive unit (WTRU) may determine a priority associated with each transport block (TB). Each TB may correspond to a respective HARQ process associated with a downlink transmission from a base station (BS). The WTRU may receive, from the BS, a request for the one-time HARQ feedback with an indication of a priority selected for the one-time HARQ feedback. The WTRU may generate a HARQ codebook for transmission of the one-time feedback. The HARQ codebook may include one or more information bits corresponding to one or more TBs determined based on the indicated priority. The WTRU may determine a transmission power based on a number of the one or more information bits, and transmit the one-time feedback including the generated HARQ codebook at the transmission power.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of Chinese patent application No. 202180019024.X entitled “Reliable HARQ-ACK Transmission in Unlicensed Spectrum” filed on February 11, 2021. The contents of the parent application are incorporated herein by reference.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Application No. 62 / 975,535, filed on February 12, 2020, and U.S. Provisional Application No. 63 / 060,960, filed on August 4, 2020, the contents of which are hereby incorporated by reference into this document. Background Art

[0004] A wireless transmit / receive unit (WTRU) supporting ultra-reliable low-latency communication (URLLC) services may operate in 5G NR (NR-U) in an unlicensed spectrum. Such WTRUs may benefit from using all hybrid automatic repeat request (HARQ) mechanisms (e.g., type 2 codebooks or type 3 codebooks) introduced for URLLC and NR-U operations. However, under such HARQ mechanisms, when the HARQ-ACK payload exceeds several bits, high transmission power may be required to ensure reliable transmission of high priority HARQ-acknowledgements (ACKs). In addition, reporting HARQ-ACK information for all HARQ processes may result in interference, power scaling, and / or loss of reliability of the URLLC A HARQ-ACK codebook. Therefore, methods and apparatus for reliable HARQ-ACK transmission are needed. Summary of the invention

[0005] Methods and apparatus for selective one-time hybrid automatic repeat request (HARQ) feedback by priority level are described herein. For example, a wireless transmit / receive unit (WTRU) may determine a priority associated with each transport block (TB). Each TB may correspond to a corresponding HARQ process associated with a downlink transmission from a base station (BS). The priority associated with each TB may be determined based on the priority of a corresponding previous physical downlink shared channel (PDSCH) transmission, a downlink transmission type (e.g., dynamic or semi-persistent scheduling), or a dynamic indication received from the BS (e.g., downlink control information (DCI) or a medium access control (MAC) control element (MAC CE)). The WTRU may receive from the BS a request for one-time HARQ feedback with an indication of a priority selected for one-time HARQ feedback. The WTRU may generate a HARQ codebook for transmitting one-time HARQ feedback. The HARQ codebook may include one or more information bits (e.g., acknowledgment (ACK) bits and / or negative acknowledgment (NACK) bits) corresponding to one or more TBs determined based on the indicated priority. The WTRU may determine a transmit power based on the number of one or more information bits and then transmit a one-time HARQ feedback including the generated HARQ codebook at the transmit power. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] A more detailed understanding may be obtained from the following description given by way of example in conjunction with the accompanying drawings, in which like reference numerals indicate similar elements, and in which:

[0007] Figure 1A is a system diagram illustrating an exemplary communication system in which one or more disclosed embodiments may be implemented;

[0008] Figure 1B is a diagram showing that according to the embodiment, Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) for use within the communication system shown;

[0009] Figure 1C is a diagram showing that according to the embodiment, Figure 1A A system diagram of an exemplary radio access network (RAN) and an exemplary core network (CN) used within the illustrated communication system;

[0010] Figure 1D is a diagram showing that according to the embodiment, Figure 1A A system diagram of another exemplary RAN and another exemplary CN used within the communication system shown;

[0011] Figure 2is a diagram illustrating an example selective one-shot hybrid automatic repeat request (HARQ) feedback procedure using a HARQ codebook based on priority levels;

[0012] Figure 3 is a diagram illustrating another example selective one-shot HARQ feedback procedure;

[0013] Figure 4A is a diagram illustrating exemplary indexed HARQ feedback; and

[0014] Figure 4B is a diagram illustrating exemplary compression of indexed HARQ feedback. DETAILED DESCRIPTION

[0015] Figure 1A 1 is a diagram illustrating an exemplary communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources (including wireless bandwidth). For example, the communication system 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word discrete Fourier transform spread OFDM (ZT-UW-DFT-S-OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0016] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, but it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a station (STA)) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0017] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device that is configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a NodeB, an evolved NodeB (eNB), a Home NodeB, a Home evolved NodeB, a next generation NodeB such as a gNodeB (gNB), a new radio (NR) NodeB, a site controller, an access point (AP), a wireless router, and the like. Although the base stations 114a, 114b are each depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0018] The base station 114a may be part of the RAN 104, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrums. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0019] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0020] More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 116. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High Speed ​​Uplink (UL) Packet Access (HSUPA).

[0021] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro).

[0022] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using NR.

[0023] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for example using dual connectivity (DC) principles. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0024] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA20001X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0025] Figure 1AThe base station 114b in the may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or a femtocell. As Figure 1A As shown, the base station 114 b may have a direct connection to the Internet 110. Thus, the base station 114 b may not need to access the Internet 110 via the CN 106.

[0026] The RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, delay requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the accompanying drawings, the CN 106 may be configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. Figure 1A Although not shown in the figure, it will be appreciated that the RAN 104 and / or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may utilize NR radio technology, the CN 106 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0027] The CN 106 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.

[0028] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0029] Figure 1B is a system diagram illustrating an exemplary WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be appreciated that the WTRU 102 may include any subcombination of the foregoing elements while remaining consistent with an embodiment.

[0030] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0031] The transmit / receive element 122 may be configured to transmit or receive signals to or from a base station (e.g., base station 114a) via an air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be a transmitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It should be understood that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0032] Although the transmit / receive element 122 is Figure 1B 1 as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0033] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. For example, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0034] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit) and may receive user input data therefrom. The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0035] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0036] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0037] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, FM radio unit, digital music player, media player, video game player module, Internet browser, virtual reality and / or augmented reality (VR / AR) device, activity tracker, etc. The peripheral device 138 may include one or more sensors. The sensor may be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geographic location sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor, etc.

[0038] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and DL (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via hardware (e.g., choke) or via signal processing performed by a processor (e.g., a separate processor (not shown) or via the processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or DL ​​(e.g., for reception)) may be concurrent and / or simultaneous.

[0039] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0040] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

[0041] Each of the evolved Node Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.

[0042] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. Although the foregoing elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0043] The MME 162 may be connected to each of the evolved Node-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0044] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-evolved Node-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.

[0045] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0046] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0047] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments, such terminals may (eg, temporarily or permanently) use a wired communications interface with a communications network.

[0048] In a representative embodiment, the other network 112 may be a WLAN.

[0049] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for a BSS and one or more stations (STA) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that brings traffic into and / or out of the BSS. Traffic originating from outside the BSS and leading to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be sent to the AP to be delivered to the corresponding destination. For example, traffic between STAs in the BSS may be sent by the AP, wherein the source STA may send traffic to the AP, and the AP may deliver the traffic to the destination STA. Traffic between STAs in the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be sent between the source and destination STAs (e.g., directly between them) using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad-hoc" communication mode.

[0050] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP may transmit a beacon on a fixed channel (such as a primary channel). The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a dynamically set width. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0051] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0052] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz and / or 80MHz channels can be formed by combining continuous 20MHz channels. A 160MHz channel can be formed by combining 8 continuous 20MHz channels, or by combining two discontinuous 80MHz channels (this can be referred to as 80+80 configuration). For the 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be transmitted by transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration can be reversed, and the combined data can be sent to the medium access control (MAC).

[0053] 802.11af and 802.11ah support operating modes below 1GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter type control / machine type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) specific bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0054] WLAN systems that can support multiple channels and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA (which supports the minimum bandwidth operating mode) from among all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (supporting only a 1MHz operating mode) is transmitting to the AP, all available frequency bands may be considered busy even if most of the available frequency bands remain idle.

[0055] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. Depending on the country code, the total bandwidth available for 802.11ah is 6MHz to 26MHz.

[0056] Figure 1D1 is a system diagram showing the RAN 104 and the CN 106 in accordance with an embodiment. As noted above, the RAN 104 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0057] The RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, gNB 180a may transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In an embodiment, gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0058] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable parameter sets. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., containing different numbers of OFDM symbols and / or continuously varying absolute time lengths).

[0059] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRU 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the evolved Node-B 160a, 160b, 160c. For example, the WTRU 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more evolved Node-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the evolved Node-B 160a, 160b, 160c may act as a mobility anchor for the WTRU 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRU 102a, 102b, 102c.

[0060] Each of the gNBs 180a, 180b, 180c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support of network slicing, interworking between DC, NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0061] Figure 1D The CN 106 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although the foregoing elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0062] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of non-access stratum (NAS) signaling, mobility management, etc. The AMF 182a, 182b may use network slicing in order to customize CN support for the WTRU 102a, 102b, 102c based on the type of services utilized by the WTRU 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, etc. The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.

[0063] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 106 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 106 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0064] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, etc.

[0065] The CN 106 may facilitate communications with other networks. For example, the CN 106 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to the DNs 185a, 185b via the UPFs 184a, 184b via the N3 interfaces to the UPFs 184a, 184b and the N6 interfaces between the UPFs 184a, 184b and the local DNs 185a, 185b.

[0066] Given that Figures 1A to 1D as well as Figures 1A to 1D In accordance with the corresponding description of the present invention, one or more or all of the functions described herein with reference to one or more of the following may be performed by one or more simulation devices (not shown): WTRU 102a-102d, base station 114a-114b, evolved Node B 160a-160c, MME 162, SGW 164, PGW 166, gNB 180a-180c, AMF 182a-182b, UPF 184a-184b, SMF 183a-183b, DN 185a-185b and / or any other device described herein. The simulation device may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0067] The simulation device may be designed to implement one or more tests of other devices in a laboratory environment and / or in an operator network environment. For example, one or more simulation devices may perform one or more or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. One or more simulation devices may perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device may be directly coupled to another device for testing purposes and / or perform testing using over-the-air wireless communications.

[0068] One or more simulation devices can perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test scenario in a test laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test equipment. Direct RF coupling and / or wireless communication via RF circuits (e.g., which can include one or more antennas) can be used by the simulation device to transmit and / or receive data.

[0069] To better support operations with different types of services such as URLLC and eMBB, there may be mechanisms to ensure that certain transmissions can be received at higher levels of latency and reliability. For example, depending on the priority level assigned to the HARQ-ACK, the HARQ-ACK may be transmitted according to one of two possible physical uplink control channel (PUCCH) configurations. For example, this may enable a high priority HARQ-ACK to be transmitted at a higher power level than a low priority HARQ-ACK.

[0070] Separately, when operating in NR unlicensed spectrum (NR-U), there may be mechanisms to better enable HARQ-ACK transmissions. A first mechanism, referred to as an "enhanced type 2 codebook," may enable the scheduler to request transmission of HARQ-ACK information for certain PDSCH transmissions identified by a physical downlink shared channel (PDSCH) group. A second mechanism, referred to as a "type 3 codebook" or "one-time feedback," may enable the scheduler to request HARQ-ACK information for all HARQ processes and serving cells.

[0071] In some scenarios, a WTRU supporting ultra-reliable low-latency communication (URLLC) services may operate in an unlicensed spectrum (e.g., NR-U). Such WTRUs may benefit from using all HARQ-ACK enhancements introduced for URLLC and NR-U operations. However, if the HARQ-ACK payload exceeds a few bits, ensuring reliable transmission of high-priority HARQ-ACKs may require excessively high transmission power levels. For example, when the WTRU reports HARQ-ACK information using a type 3 codebook (e.g., one-time feedback), the WTUR transmits HARQ-ACK information for all HARQ processes and cells. This may result in excessive interference and / or power scaling, in which case the type 3 codebook report may not be used effectively. In some cases, the enhanced type 2 codebook mechanism may not take into account the priority of the HARQ-ACK. This may result, for example, in the WTRU grouping high-priority HARQ-ACKs in resources that are not suitable for this purpose.

[0072] Figure 2 An example selective one-shot HARQ feedback procedure 200 based on priority level using a HARQ codebook is shown, which may be used in conjunction with any other embodiments described herein. Figure 2 As shown, the BS may transmit a plurality (e.g., 16) of TBs 205, 215, 225 to a WTRU associated with the BS. Each of the TBs (e.g., TB1 205, TB2 215, and TB3 225) may be associated with a HARQ process for HARQ feedback. Each HARQ process may be associated with each HARQ process ID (PID) (e.g., HARQ PID1, HARQ PID2, and HARQ PID3). Each HARQ process or HARQ PID may be associated with a corresponding priority. Figure 2As shown, the BS may indicate to the WTRU, for example, using downlink control information (DCI), that TB1 / HARQ PID1 205 and TB2 / HARQ PID2 215 are associated with priority 0 (i.e., low priority). The BS may also indicate to the WTRU, for example, using DCI, that TB3 / HARQ PID3 225 is associated with priority 1 (i.e., high priority). After receiving a plurality of TBs (e.g., TB1-3 205, 215, 225) from the BS, the WTRU may transmit HARQ feedback 210, 220 associated with the corresponding HARQ PIDs (i.e., HARQ PID1 and HARQ PID2). In one example, the WTRU may determine the priority associated with the HARQ process based on the RRC configuration or dynamic downlink indication (such as DCI and MAC-CE). In the event that the WTRU misses the RRC configuration or the dynamic downlink indication, the WTRU may use different methods to determine the priority associated with the HARQ process. Examples of different approaches may include, but are not limited to, using the priority of the most recent PDSCH transmission with the received HARQ PID, the downlink (DL) transmission type (such as dynamic assignment or semi-persistent scheduling), and / or the associated scheduling control resource set (CORESET) or search space.

[0073] The WTRU may be unable to transmit HARQ feedback 230 for TB3 / PID3 due to a Listen Before Talk (LBT) failure or may discard the feedback due to a conflict with a higher priority transmission. Alternatively or alternatively, the BS may be unable to receive the HARQ feedback 230 for any reason. The WTRU may receive a request 235 for a one-time HARQ feedback with an indication of a priority level (e.g., priority 1) from the BS. The request 235 for the one-time HARQ feedback may be included in, for example, a scheduled DCI or a non-scheduled DCI with an indication of the priority level. Specifically, a flag indicating the one-time HARQ feedback and another flag indicating the priority level may be transmitted to the WTRU in a scheduled DCI or a non-scheduled DCI.

[0074] After receiving the request 235 for a one-time HARQ feedback request with an indication of a priority level (e.g., priority 1), the WTRU may generate a HARQ codebook based on the indicated priority. Figure 210. The HARQ codebook generated by the WTRU may include one or more ACK or NACK bits associated with TB3 / PID3 and TB10 / PID10. The codebook size may be determined based on the number of HARQ processes associated with the indicated priority (i.e., the HARQ processes in the priority subset). In one example, the HARQ codebook may include ACK or NACK bits for HARQ processes (in the priority subset), where the priority associated with the HARQ process is equal to or higher than the indicated priority from the BS. In another example, when a semi-static codebook size is used or configured, in addition to the ACK or NACK bits for the HARQ processes in the priority subset, the HARQ codebook may also include one or more NACK bits for the HARQ processes in the non-priority subset. In this case, the priority (or multiple priorities) associated with the HARQ processes in the non-priority subset is lower than the indicated priority. Once the HARQ codebook is generated based on the indicated priority, the WTRU may transmit selective one-shot HARQ feedback 240 including the generated codebook to the BS.

[0075] Figure 3Another example selective one-time HARQ feedback procedure 300 is shown, which may be used in conjunction with any other embodiment described herein. At step 305, the WTRU may receive a configuration including the number of HARQ processes associated with a downlink transmission from the BS via radio resource control (RRC) signaling or a dynamic indication such as a DCI or MAC-CE. At step 310, the WTRU may determine a priority associated with each TB. Each TB may correspond to a respective HARQ process associated with a downlink transmission. In the case where the WTRU is configured with RRC signaling or receives a dynamic indication such as a DCI or MAC-CE, the WTRU may determine the priority based on the RRC configuration, the DCI, or the MAC-CE. In the case where the WTRU is not configured with RRC signaling or misses a dynamic indication such as a DCI or MAC-CE, the WTRU may determine the priority based on the priority of the previous PDSCH transmission, the downlink transmission type, the associated scheduling CORSET or search space, etc. When the WTRU determines the priority of the TB based on the priority of the previous PDSCH transmission, the WTRU may select the previous PDSCH transmission for the same HARQ process associated with the TB. For example, assuming that TB3 is associated with HARQ process 3 and TB10 is associated with HARQ process 10, if the WTRU determines the priority of TB3 and TB10 based on previous PDSCH transmissions, the WTRU uses different previous PDSCH transmissions associated with HARQ process 3 and HARQ process 10, respectively, to determine the priority of TB3 and TB10.

[0076] After determining the priority associated with the HARQ process or HARQ PID, at step 315, the WTRU may receive from the BS a request for a one-time HARQ feedback with an indication of a priority selected for the one-time HARQ feedback. The WTRU may receive a request for a one-time HARQ feedback when the WTRU is unable to transmit the HARQ feedback due to a LBT failure, or the BS does not receive the HARQ feedback for a certain duration. At step 320, the WTRU may generate a HARQ codebook for transmitting the one-time feedback based on the received indicated priority. The generated HARQ codebook may include one or more information bits corresponding to one or more TBs or HARQ processes determined based on the indicated priority. These TBs or HARQ processes determined based on the indicated priority may form a priority subset. For example, TBs or HARQ processes with certain priorities equal to or higher than the indicated priority may be included in the priority subset. The one or more information bits may include an acknowledgement (ACK) bit or a negative acknowledgement (NACK) bit. The generated HARQ codebook may include one or more ACK or NACK bits for TBs or HARQ processes in the priority subset, wherein each priority associated with the TBs or HARQ processes in the priority subset is higher than or equal to the indicated priority. If the HARQ codebook size is semi-statically determined or configured, the HARQ codebook may also include one or more NACK bits for the non-priority subset, wherein each priority associated with the TBs or HARQ processes in the non-priority subset is lower than the indicated priority.

[0077] At step 325, the WTRU may determine a transmission power for the one-time HARQ feedback. The transmission power may be determined, for example, based on the number of information bits in the generated codebook, or based on the number of information bits of the highest priority in the generated codebook, or based on the number of information bits of each priority subset in the generated codebook. At step 330, the WTRU may transmit the one-time HARQ feedback including the HARQ codebook generated based on the indicated priority to the BS at the determined transmission power.

[0078] In one embodiment, the WTRU may transmit a one-time HARQ-ACK feedback for a subset of HARQ processes associated with a priority level and / or serving cell to improve the reliability of the transmission. Such a subset may be referred to as a "priority subset" herein. The report may be referred to as "selective one-time HARQ feedback".

[0079] Given their relaxed latency timelines, it may also be beneficial to bundle HARQ feedback for lower priority transmissions while keeping unbundled (e.g., normal) HARQ feedback for prioritized transmissions. This may reduce the number of times HARQ feedback collides with other higher priority uplink control information (UCI) or physical uplink shared channel (PUSCH) transmissions. Additionally, this may reduce the number of discarded HARQ feedback while leaving room for the network to request HARQ feedback from the WTRU for transmissions with more relaxed latency. This may also be a useful tool for the network to request feedback on discarded low priority HARQ-ACK transmissions (e.g., due to collision with higher priority transmissions) without having to retransmit the associated TBs again, because the BS (e.g., gNB) is aware that some HARQ-ACK feedback was missed due to, for example, intra-WTRU or inter-WTRU prioritization.

[0080] In some cases, there may be an explicit indication for HARQ feedback. If a HARQ process is indicated by L1, MAC or RRC signaling, the HARQ process may be included in or associated with the priority subset. Alternatively or alternatively, the HARQ process may be included in or associated with the priority subset indicated by the DCI that triggered the one-time HARQ feedback transmission. The indication to include / associate a given HARQ process in a priority set may include one or more of RRC signaling or dynamic signaling.

[0081] For example, the WTRU may be configured via RRC signaling to include a subset of HARQ processes as part of the one-time HARQ feedback, or possibly as part of the priority subset (if dynamically indicated). The RRC may also configure a mapping between HARQ process IDs and PDSCH group indices, or more generally, a set of HARQ processes for which feedback may be reported together after receiving an associated one-time HARQ feedback request, for example. The RRC may configure the WTRU as to whether selective one-time feedback is applicable. The RRC may configure the WTRU with one or more priority levels that may be applicable to the one-time HARQ feedback.

[0082] In an example of dynamically triggering a one-time HARQ feedback, the WTRU may receive downlink control information (DCI) or a medium access control (MAC) control element (CE) indicating which HARQ process IDs are part of a priority subset. For example, the WTRU may receive a bitmap of HARQ process IDs, where a 1 or 0 indicates whether the HARQ process ID is included in part of a priority subset. The WTRU may then include HARQ feedback only for the indicated HARQ processes that are part of a priority subset, such as after triggering the one-time HARQ feedback. In another example, the WTRU may receive a DCI or MAC CE indicating a set of priority levels or PDSCH group indices. After receiving a one-time HARQ feedback request indicating certain priority levels or PDSCH groups, the WTRU may include the HARQ processes associated with those priority levels or PDSCH groups as part of a "priority subset" for which the WTRU will provide HARQ feedback together, such as after triggering the one-time HARQ feedback.

[0083] The dynamic signaling may indicate a PDSCH group index or a set of HARQ processes configured by the RRC. Upon receiving such a group index, the WTRU may consider mapping the HARQ process ID to the group index as part of a priority subset. The WTRU may associate the HARQ process with the group index according to the mapping configured by the RRC, or by maintaining the group index assigned to each scheduled PDSCH. In one example, the dynamic signaling may indicate a state index associated with one or more DL semi-persistent scheduling (SPS) or configured granted resources (e.g., a state for SPS (de)activation). Upon receiving such a state index, the WTRU may consider the HARQ process ID (PID) associated with the state as part of the priority subset.

[0084] Dynamic signaling may override a previously configured priority subset via RRC. For example, the WTRU may be configured with a default priority subset by RRC, which the WTRU uses by default after triggering or receiving a one-time HARQ feedback request. If the dynamic signaling indicates a different priority subset, the WTRU may override or temporarily suspend the default subset.

[0085] In some embodiments, the one-time HARQ feedback may be dynamically determined by receiving a subsequent schedule for the same HARQ PID or the same HARQ PID group. In one example, the WTRU may trigger a one-time HARQ feedback and provide HARQ feedback for all HARQ process IDs mapped to the same PDSCH group index configured by RRC after receiving a retransmission of a HARQ PID belonging to the same PDSCH group index. In one example, the WTRU may trigger a one-time feedback after receiving all HARQ process IDs for which the new data indicator (NDI) was not toggled after receiving a retransmission of a DL TB associated with the same PDSCH group index (e.g., for which the TB is pending in the HARQ buffer).

[0086] In some embodiments, there may be HARQ processes associated with certain serving cells. In one example, the WTRU may receive a one-time HARQ feedback request for a set of HARQ processes associated with a subset of serving cells. The WTRU may receive a cross-carrier request for HARQ feedback. For example, the WTRU may receive a one-time HARQ feedback request with a carrier index or control format indicator (CFI) field that indicates a carrier different from the carrier on which the request was received. Upon receiving such a request, the WTRU may include a HARQ PID associated with the requested cell (e.g., a portion of a priority subset).

[0087] In another example, the WTRU may exclude HARQ PIDs associated with serving cells other than the serving cell on which the one-time HARQ feedback request was received from the priority subset. For example, the WTRU may be configured or may determine a mapping between each serving cell and a subset of HARQ processes; the WTRU may then exclude HARQ processes mapped to serving cells other than the serving cell on which the one-time HARQ feedback request was received.

[0088] In another example, the WTRU may determine the priority of a cell based on the associated service, data radio bearer (DRB), or logical channel. For example, the WTRU may receive a one-time HARQ feedback request for a priority level, and the WTRU may then include the HARQ PID associated with the priority level for the same cell. In one example, the WTRU may determine the priority of a cell based on the configured LCH to cell restrictions and / or the LCH to priority level mapping configured by RRC.

[0089] In some embodiments, there may be HARQ processes or HARQ PIDs associated with certain HARQ-ACK priority levels. The WTRU may keep track of which HARQ processes (or HARQ PIDs) are associated with a certain priority level or codebook. A HARQ process may be included in a priority subset based on at least one aspect of the transmission using the HARQ process or associated with the HARQ process.

[0090] In one example, one aspect of the transmission may be a priority level associated with the HARQ-ACK. For example, upon receiving a one-time HARQ feedback request for a certain priority subset, the WTRU may provide a one-time HARQ feedback for one or more HARQ processes associated with the priority level. The WTRU may track the priority levels associated with the scheduled PDSCH to determine which HARQ processes match the indicated priority level.

[0091] In one example, one aspect of the transmission may be a PDSCH group or codebook index. For example, upon receiving a one-time HARQ feedback request together with a PDSCH group-based dynamic feedback request for a PDSCH group, or in the same time slot as the dynamic feedback request, the WTRU may exclude one or more HARQ processes or HARQ PIDs that are not associated with the indicated PDSCH group index from the priority subset. In a different example, the WTRU may exclude one or more HARQ processes or HARQ PIDs from the priority subset if a one-time HARQ feedback for those HARQ processes has been provided in the same time slot in response to the PDSCH group-based dynamic feedback request. In another example, the WTRU may exclude one or more HARQ processes or HARQ PIDs from the priority subset if the new field indicator (NFI) value of the HARQ process for its corresponding indicated PDSCH group has been switched. In a different example, the WTRU may exclude one or more HARQ processes or HARQ PIDs that are not associated with a HARQ feedback codebook index or type (associated with a one-time HARQ feedback request), where the codebook type may be determined based on dynamic signaling, priority level, and / or whether the associated PUCCH resources occupy an entire time slot or a sub-time slot.

[0092] In one example, an aspect of the transmission may be a PDSCH to HARQ-ACK (K1) value, such as whether K1 is a numeric value.

[0093] In one example, one aspect of the transmission may be a control resource set (CORESET) for indicating the DCI of the transmission. For example, if the properties of the PDCCH resources (e.g., CORESET, RNTI, search space) that schedule the associated PDSCH are associated with a given priority level or priority subset and / or meet the reliability suitability criteria configured by the RRC, the WTRU may associate the HARQ process or HARQ PID with a priority level or include it in a priority subset. In another example, the WTRU may be configured to have multiple transmit and receive points (TRPs) within a serving cell, whereby each TRP may be associated with a PDCCH, a subset of PDCCH resources, or a subset of coresets. The WTRU may receive a one-time HARQ feedback request from one TRP. The WTRU may include a HARQ process (or HARQ PID) associated with a TRP from which the WTRU receives a one-time HARQ feedback request portion of a priority subset. In a different example, the WTRU may include an associated HARQ process (or HARQ PID) that is different from a TRP from which the WTRU receives a one-time HARQ feedback request portion of a priority subset after receiving the indication.

[0094] In one example, one aspect of the transmission may be whether the HARQ process has been successfully decoded and HARQ feedback has been provided. For example, if the WTRU has provided HARQ feedback for the associated TB and the TB was successfully decoded, the WTRU may exclude the HARQ PID from the priority subset. In a different example, the WTRU may include the HARQ process in the priority subset only if the associated TB has not been successfully decoded.

[0095] In one example, one aspect of the transmission may be an NDI, where the WTRU may include a HARQ process (or HARQ PID) in the priority subset if the NDI for that HARQ process has not toggled and there are pending TBs in the associated HARQ buffer.

[0096] In one example, an aspect of the transmission may be a PDSCH resource type. For example, the WTRU may include a HARQ PID for semi-persistent scheduling (SPS), or may exclude dynamic assignments from the priority subset. In a different example, the WTRU may include a HARQ process in a priority subset if the associated PDSCH resource meets a certain reliability criterion.

[0097] In one example, an aspect of the transmission may be a cell or bandwidth part (BWP). For example, if the corresponding PDSCH of certain HARQ processes (or HARQ PIDs) is scheduled on a different BWP and / or cell than the BWP and / or cell where the one-time HARQ feedback request was received, the WTRU may exclude one or more of these HARQ processes from the priority subset. In another example, the one-time HARQ feedback request may indicate a certain cell or BWP; the WTRU may only include the HARQ process IDs associated with the indicated cell and / or BWP in the priority subset.

[0098] In one example, one aspect of the transmission may be that the WTRU includes one or more HARQ processes (or HARQ PIDs) associated with the same processing timeline, a pipeline and / or a processing chain in a priority subset to match the processing pipeline, processing capability and / or scheduling timeline indicated or determined by the DCI.

[0099] In one example, one aspect of the transmission may be whether HARQ feedback is disabled. In some systems, HARQ feedback may be disabled for some HARQ processes or HARQ PIDs by the network, such as by RRC or dynamic signaling. The WTRU may assume that the HARQ PIDs for which HARQ feedback is disabled are excluded from the priority set. In a different example, the WTRU may include in the priority set only the HARQ processes or HARQ PIDs for which HARQ feedback has been disabled after receiving a one-time HARQ feedback request.

[0100] As described above, the downlink transmissions considered for HARQ feedback may include, but are not limited to, at least one of the following: the last PDSCH transmission before the one-time HARQ feedback is triggered; the PDSCH in the last downlink portion of the radio frame configuration in TDD; the PDSCH in the last scheduled channel occupancy time (COT); the PDSCH scheduled within the time window before evaluating a priority subset (e.g., a subset of HARQ processes for which the WTRU feeds back HARQ-ACK); the PDSCH scheduled within the time window before receiving a DCI requesting a one-time HARQ feedback, and / or more generally, triggering the one-time HARQ feedback; downlink TBs for which the time since the initial transmission has not exceeded a certain time threshold, which may be predefined or semi-statically configured by the RRC; the PDSCH for which the WTRU has sufficient time to process the TB and determine the HARQ-ACK value; and / or any previously scheduled PDSCH for which a TB is stored in the HARQ process buffer.

[0101] When determining which processes to include in the HARQ feedback for a given priority level, the time may be based on the time of receiving the DCI for the one-time HARQ feedback, or the earliest possible time of transmitting the feedback (e.g., either in some cases where LBT is not used, or if the WTRU processing makes such a transmission possible). Additionally, the time of the initial HARQ transmission and / or the last transmission (e.g., DCI reception or actual transmission) of a given process may be considered.

[0102] In some embodiments, there may be HARQ feedback for DL ​​semi-persistent (SPS) transmissions. In one example, the WTRU may be configured to use selective one-time HARQ feedback to send HARQ-ACK feedback for semi-persistent (SPS) downlink transmissions and / or confirmation of SPS release. For example, the WTRU may be configured with multiple selective one-time HARQ feedbacks, each with a given priority. The WTRU may then use the configuration parameters of the DL SPS to determine the priority of the DL SPS. In one example, the semi-static configuration of the DL SPS may include a priority parameter that can be mapped to the selective one-time HARQ feedback, or the configuration may map the configuration directly to the selective one-time HARQ feedback. In another example, the WTRU may dynamically determine the selective one-time HARQ feedback based on, for example, the HARQ PID used for DL ​​transmission. For example, the WTRU may be configured with DL SPS resources for which a formula that depends on the transmission time is used to calculate the HARQ PID associated with the PDSCH transmission. The WTRU may also be configured with selective one-time HARQ feedback based on the HARQ PID, such as selective one-time HARQ feedback for a subset of the HARQ PIDs. After determining the HARQ process (or HARQ PID) for a given PDSCH transmission, the WTRU may use the corresponding selective one-time feedback to confirm the HARQ process.

[0103] In another example, the WTRU may determine the selective one-time HARQ feedback to associate / transmit the confirmation of the SPS release using the DCI indicating the SPS release. Such DCI may reuse some of the existing bit fields to indicate the associated selective one-time HARQ feedback. In one example, the time domain resource allocation field (TDRA) may be reused to indicate the associated selective one-time HARQ feedback. For example, the WTRU may be configured with a mapping between the TDRA code point in the DCI and the selective one-time feedback. Such mapping may be semi-statically configured using RRC configuration or alternatively fixed in the specification.

[0104] In one example, after receiving a DCI releasing an SPS configuration, the WTRU may be triggered to transmit a selective one-time HARQ feedback associated with an ACK / NACK for the SPS release. The WTRU may use the indicated PUCCH resource indication and HARQ-ACK feedback timing in the DCI. The WTRU may then transmit all ACK / NACK bits of the previously transmitted PDSCH associated with the indicated selective one-time HARQ feedback. If the indicated PUCCH resource overlaps with the PUSCH, the WTRU may be configured to piggyback the selective one-time HARQ feedback on the PUSCH. The WTRU may be configured to piggyback the selective one-time HARQ only if the PUSCH grant satisfies one or more of the following: the priority associated with the PUSCH grant is equal to or higher than the priority associated with the selective one-time feedback; and / or the time difference between the indicated end symbol of the PUCCH and the end symbol of the PUSCH is lower than a configured threshold.

[0105] In some embodiments, there may be a maximum number of processes for selective one-shot HARQ feedback. Specifically, there may be a maximum number of HARQ processes (or HARQ PIDs) that can be included in a priority subset.

[0106] The WTRU may construct a dynamic or semi-static HARQ feedback codebook for a one-time HARQ feedback request using a subset of priorities. For a dynamic codebook, the WTRU may determine the maximum number of HARQ processes (or HARQ PIDs) to be included in the priority set based on the total downlink assignment index (DAI) value. For example, if the total DAI is signaled in part of the one-time HARQ feedback request for a given priority set, the WTRU may determine the number of HARQ processes in the evaluation period based on the {cDAI, tDAI} values ​​previously scheduled for each PDSCH.

[0107] The WTRU may determine the maximum number of HARQ processes (or HARQ PIDs) that may be included in the priority subset semi-statically, such as based on the number of HARQ processes configured for each serving cell. In one example, the WTRU may be configured with 3 serving cells and each cell may be configured with 16 HARQ processes. Assuming that one of the cells is not applicable for priority level x or codebook index x, the WTRU may assume that the maximum number of HARQ processes in the codebook constructed for one-time HARQ feedback for priority level x is 32. Assuming that all cells support any priority level, the WTRU may assume that the maximum number of HARQ processes is 48. In another example, the WTRU may be configured by the RRC such that only 8 of the 16 HARQ processes in the cell may be included in the priority set; in such a configuration, the WTRU may assume that the maximum number of HARQ processes per cell in the codebook constructed for one-time HARQ feedback is 8. The WTRU may further derive the number of HARQ processes for which feedback is disabled based on the determined maximum number of HARQ processes (or HARQ PIDs) that may be included in the priority subset.

[0108] In one example, the WTRU may be configured via RRC with a maximum number of HARQ processes that may be included in a priority subset; however, in some cases, the WTRU may have determined a larger number of HARQ processes that meet the priority subset inclusion criteria. Under such configuration, the WTRU may sort the HARQ processes in the priority subset in order of priority, time since initial transmission, time since K1, highest LCH priority, and / or HARQ PID index.

[0109] In some embodiments, selective one-shot HARQ feedback and setting power may be encoded. The WTRU may be scheduled with DL transmissions of different priorities. The WTRU may use the priority of the DL transmission to determine the associated priority level of the feedback. The WTRU may be configured to report feedback for all TBs (e.g., HARQ processes and / or serving cells) of a specific priority (e.g., all TBs forming a priority subset).

[0110] In some cases, multiple groups of HARQ processes (or HARQ PIDs) and serving cells may be configured (e.g., semi-statically configured) for transmissions of specific priorities and may form semi-static priority subsets. The WTRU may be requested to provide feedback for all HARQ processes (or HARQ PIDs) and serving cells associated with one or more priority subsets. In another case, the HARQ processes (or HARQ PIDs) and / or serving cells may be used for transmissions at any one of a plurality of priority levels. In this case, the HARQ processes (or HARQ PIDs) and serving cells that constitute the priority subsets may be changed dynamically.

[0111] The WTRU may receive a one-time HARQ feedback request associated with one or more priority levels (e.g., priority subsets) from the network. For the case where the priority subsets are semi-statically configured, the size of the codebook used to report the HARQ feedback may be explicit to both the WTRU reporting the feedback and the BS (e.g., gNB) detecting / decoding the feedback. For the case where the priority subsets are dynamically determined by the WTRU based on scheduling information for each specific DL transmission, if the WTRU erroneously detects one or more scheduling DCIs, the WTRU and the BS (e.g., gNB) may interpret the codebook size and the location of a specific HARQ-ACK value within the codebook differently.

[0112] In some embodiments, there may be a downlink assignment index (DAI) per priority subset, where the priority subset specific DAI (e.g., a counter or total DAI) may be indicated to the WTRU in each scheduling instance. Based on the priority subset specific DAI, the WTRU may be able to determine whether one or more DCIs were misdetected for that priority subset, and more importantly, how many DCIs were misdetected and at what positions within the HARQ feedback codebook. The one-time feedback request may also indicate to the WTRU the expected size of the codebook (e.g., the final total DAI).

[0113] In some embodiments, the reported HARQ process (or HARQ PID) may be indicated to the WTRU, where the WTRU may provide an index for each HARQ-ACK feedback or a group of HARQ-ACK feedback reports. For example, after receiving a request for a transmission priority subset for a one-time HARQ feedback, the WTRU may construct a codebook based on feedback for all HARQ processes and serving cells for which scheduling of that priority level is received. The WTRU may include in the first set of bits the index of the HARQ process and serving cell that indicates the subsequent set of bits applicable to provide the HARQ-ACK value. The WTRU may include feedback for all HARQ processes and serving cells with a priority equal to or higher than the requested for DL ​​transmissions.

[0114] In another example, the index may apply to a subsequent set of HARQ-ACK bits. For example, the index may point to a set of HARQ processes and / or serving cells, and the subsequent bits may provide the HARQ-ACK status of the set of HARQ processes and / or serving cells. In such an example, the WTRU may report feedback for all HARQ process groups and / or serving cells such that all HARQ processes and / or serving cells with the desired priority level are reported.

[0115] If some HARQ processes and / or serving cells are not actually used for DL ​​transmission, the WTRU may include a NACK for such HARQ processes / serving cells. In this example, some HARQ processes and / or serving cells may not actually be used for DL ​​transmission of the requested priority level, but may have been used for transmission of a lower (or higher) priority level. In this case, the WTRU may report a HARQ-ACK for those processes or report a NACK for those processes.

[0116] In some instances, there may be a feedback request indicating a HARQ process group. It may also be possible to explicitly request in a one-time HARQ feedback request a group of HARQ processes for which the WTRU provided feedback in a one-time HARQ feedback. For example, a WTRU may be configured with M groups of HARQ processes and serving cells. The WTRU may receive a one-time HARQ feedback request that explicitly requests feedback for one or more groups of HARQ processes in the M groups of HARQ processes (e.g., regardless of the priority level of each transmission within each fixed group).

[0117] After requesting feedback of HARQ-ACK for one or more groups of HARQ processes in the preconfigured M groups of HARQ processes, the WTRU may construct a codebook of appropriate size (e.g., the sum of all elements of the requested group). The WTRU may also attach HARQ-ACK feedback for HARQ processes of a specific priority subset for which the HARQ processes are not included in the request. For example, the WTRU may be requested to report feedback for the first group of all HARQ processes covering the first serving cell. The WTRU may also schedule with high priority DL transmission on the HARQ process of the second cell. The WTRU may report all feedback states of the HARQ processes of the requested group (e.g., of the first cell) and may attach the HARQ-ACK for the high priority HARQ process transmitted on the second cell to the codebook. The feedback transmitted by the WTRU may include a bit string indicating that high priority HARQ-ACK feedback is attached. The feedback transmitted by the WTRU may also include an index identifying each or the group of attached high priority HARQ-ACK feedback.

[0118] In one case, the one-time HARQ feedback request may provide a set of HARQ processes for which the WTRU may report HARQ-ACK feedback. In addition, the one-time HARQ feedback request may include a priority level (or priority subset) for which the WTRU should provide the required feedback (possibly by appending to a codebook). The WTRU may report feedback for all HARQ processes for the requested priority level and / or possibly higher priority levels.

[0119] Figure 4A An exemplary indexed HARQ feedback 400 is shown, which may be used in conjunction with any other embodiment described herein. Figure 4A As shown, an exemplary HARQ feedback 400 for multiple HARQ processes may include HARQ process index types 405, 420, 435, HARQ process index fields (HPIFs) 410, 425, 440, and HARQ-ACK bit strings 415, 430. Each of the HARQ process index types 405, 420, 435 may include a bit indicating 0 or 1. Bit 0 in the HARQ process index types 405, 420, 435 may indicate that the HARQ process ID associated with the subsequent HARQ-ACK bit string may be determined based on the previous HARQ index value and / or HPIF. Bit 1 in the HARQ process index types 405, 420, 435 may indicate that the HARQ process ID associated with the subsequent HARQ-ACK bit string is not explicitly indicated and (i.e., the HPIF is not included), and the HARQ process ID associated with the subsequent HARQ-ACK bit string may be determined as a value immediately following the previous HARQ process ID within the codebook. Each of the HPIFs 410, 425 may include an index value of a HARQ process associated with the HARQ-ACK bit string 415, 430, respectively. The reserved HPIF value may be used to indicate the end of the codebook. For example, the HPIF 440 may include 0000 as an index value to indicate that it is the end of the codebook. If the previous HARQ process index type is 1, the HPIFs 410, 425 may not exist. In one example, if the WTRU needs to report HARQ-ACK feedback for the 3rd, 7th, and 10th HARQ processes, the WTRU may include the index value and HPIF associated with the 3rd, 7th, and 10th HARQ processes in the HARQ-ACK feedback. In this case, the previous HARQ process index type of the HPIF associated with the 3rd, 7th, and 10th HARQ processes is 0.

[0120] Figure 4BAn exemplary comparison 450 of indexed one-shot HARQ feedback is shown, which may be used in conjunction with any other embodiment described herein. To reduce feedback overhead, the WTRU may not report an index for each HARQ-ACK feedback it reports. Figure 4B As shown, the exemplary codebook may include HARQ feedback 465, 475, 490 for the 3rd, 4th, and 10th HARQ processes. In this example, if the HARQ-ACK feedback is not a direct subsequent HARQ-ACK feedback of the previous HARQ-ACK feedback, the WTRU may only report the index of the HARQ-ACK feedback it reports. For example, if the WTRU needs to report HARQ-ACK feedback for the 3rd, 4th, and 10th HARQ processes, the HARQ-ACK feedback may include the index 460 for the 3rd HARQ process (i.e., 0011), does not include the index for the 4th HARQ process (e.g., considering that there are no other HARQ processes that can be fed back between the two HARQ processes) and includes the index 485 for the 10th HARQ process (i.e., 0110). As described above, bit 1 in the HARQ process index type 470 may indicate that neither the index value or the HPIF associated with the 4th HARQ process is present in the codebook. The index may also be absolute (e.g., indicating an absolute HARQ PID) or relative (e.g., indicating a HARQ PID relative to the HARQ PID of the immediately preceding HARQ-ACK value). For each HARQ-ACK feedback, the WTRU may report a first bit indicating the index type (e.g., HARQ process index type 455, 470, 480, 495), followed by a bit string indicating the index (e.g., HPIF 460, 485, 497), and finally the actual HARQ-ACK value (e.g., HARQ-ACK bit string 465, 475, 490). For example, in the case where HARQ-ACK feedback for the 3rd, 4th, and 10th HARQ processes is to be transmitted, the WTRU may construct the following: Figure 4B The codebook shown.

[0121] The bit indicating the index type may also indicate whether an index is provided for HARQ-ACK feedback. In addition, the index may be used to indicate that no additional HARQ-ACK feedback exists in the codebook. The index may also provide the identity of a subsequent set of HARQ-ACK feedback, so that no index or index type bit is required for each HARQ process.

[0122] In some embodiments, there may be CBG level feedback. The WTRU may be configured with different types of feedback for different priority levels. For example, feedback for a high priority HARQ process may use TB level feedback, and feedback for a lower priority HARQ process may use CBG level feedback. In this case, the WTRU may use repeated feedback for the HARQ process using TB level feedback. This ensures that all feedback for all HARQ processes uses the same amount of payload. In the case of using repetition for high priority feedback, the reliability of such feedback may be improved.

[0123] In some embodiments, there may be a power setting. The WTRU may report a one-time HARQ feedback using a predetermined and possibly configurable codebook size. The WTRU may have fewer bits for feedback than provided by a predetermined codebook size. Therefore, the WTRU may fill the codebook (e.g., with NACK values ​​or bits) in locations mapped to HARQ processes for which the WTRU does not need to provide feedback. For example, this may occur in the following situation: the WTRU provides indexes to multiple HARQ processes, but the WTRU does not have feedback for all the HARQ processes pointed to by the indexes. When determining the power setting for transmitting feedback, the WTRU may only consider the payload size as the number of bits used for actual feedback, without considering the padding bits.

[0124] The power setting may be determined based on the number of HARQ-ACK bits for a particular priority subset. For example, the power setting may be determined based on the number of HARQ-ACK bits used to feedback for the highest priority transmission. In another example, the power setting may be determined based on the number of HARQ-ACK bits used to feedback for the highest priority transmission and the total codebook size or total number of information bits. In another example, the power setting may be determined based on the number of HARQ-ACK bits used to feedback for the requested or predetermined determined or configurable priority transmission and possibly any other higher priority transmission.

[0125] In another example, the power setting may be determined based on the number of HARQ processes in the requested priority subset, regardless of whether there is actual feedback for all such HARQ processes.

[0126] In another example, the power setting may be determined by the last received DAI (eg, total DAI).Such a value may be obtained from the most recently scheduled DL transmission, or may be obtained from a one-time HARQ feedback request.

[0127] The PUCCH resource configuration may be obtained from a PUCCH configuration corresponding to a priority associated with a HARQ-ACK included in the codebook, the resource configuration including at least a PUCCH resource, a sub-slot configuration, and a PUCCH power control parameter. Alternatively or alternatively, the WTRU may be configured with a separate PUCCH configuration for each configuration of selective one-time HARQ feedback, such as each priority level.

[0128] In some embodiments, there may be techniques for triggering selective one-shot HARQ feedback. The WTRU may be configured with multiple selective one-shot HARQ feedbacks, each of which may be associated with a given priority. In some cases, the WTRU may be configured to transmit selective one-shot HARQ feedback upon the occurrence of at least one event or combination of events.

[0129] One such event for transmitting selective one-time HARQ feedback may occur after receiving a DCI. For example, the WTRU may be configured to transmit selective one-time HARQ feedback after receiving a DCI that schedules one of the HARQ processes associated with a high priority transmission. Such DCI may carry an explicit indication to trigger the feedback, or alternatively, the mere receipt of such DCI may trigger the selective one-time HARQ feedback. In another example, the WTRU may receive a DCI that does not schedule a PDSCH (e.g., a non-scheduled DCI). For example, a DCI that triggers aperiodic CSI reporting may also be used to trigger one-time feedback.

[0130] One such event with respect to transmitting selective one-time HARQ feedback may occur after a failure to receive a HARQ retransmission. For example, the WTRU receives the first transmission of a HARQ PID within a priority subset (e.g., a subset of DL HARQ processes). The WTRU may then fail to decode the transmission correctly and report a NACK to the BS (e.g., gNB). The WTRU may autonomously transmit a one-time HARQ feedback after a timer expires. Such a timer may be semi-statically configured for the WTRU or fixed in the specification. The timer duration may depend on the priority of the downlink transmission. In another example, the WTRU may transmit a one-time HARQ feedback if the channel occupancy time (COT) expires without receiving a HARQ retransmission. The COT may be initiated by the BS (e.g., gNB) or the WTRU and shared with the BS (e.g., gNB). In another example, the WTRU may trigger autonomous one-time HARQ feedback after a certain number of retransmission failures for the same TB, whereby the number of failed transmission thresholds is predetermined or semi-statically configured.

[0131] One such event regarding transmission of selective one-shot HARQ feedback may occur after a failure to access a channel. For example, due to a Listen Before Talk (LBT) failure, the WTRU is unable to transmit HARQ-ACK feedback (e.g., one-shot HARQ feedback or HARQ codebook). The WTRU then autonomously transmits the selective one-shot HARQ feedback in the next available opportunity to access the channel.

[0132] One such event for transmitting selective one-time HARQ feedback may occur after a HARQ-ACK is a NACK for a HARQ PID within a priority subset (a subset of DL HARQ processes), and the WTRU autonomously transmits the one-time HARQ feedback. For example, the WTRU may be configured with multiple selective one-time HARQ feedbacks corresponding to a set of HARQ process subsets. If only one NACK for a HARQ process subset is determined, the WTRU may transmit a one-time HARQ feedback with priority. In another example, if the number of NACKs in the applicable priority subset is greater than a certain threshold, the WTRU may trigger autonomous one-time HARQ feedback.

[0133] One such event regarding transmission of selective one-shot HARQ feedback may occur after a preemption and / or failure to transmit HARQ-ACK feedback occurs. The WTRU may discard the HARQ-ACK transmission and transmit the selective one-shot HARQ feedback. For example, the WTRU may be configured with HARQ-ACK transmission resources that overlap with a higher priority uplink transmission. In another example, the WTRU HARQ-ACK transmission resources may overlap with a higher priority downlink transmission.

[0134] One such event with respect to transmission of selective one-shot HARQ feedback may occur after a decision is made regarding discarding a scheduled HARQ-ACK due to inter-WTRU or intra-WTRU prioritization. For example, the WTRU may trigger autonomous selective one-shot HARQ feedback after discarding a scheduled HARQ-ACK and / or after de-prioritizing HARQ-ACK transmissions for one or more HARQ processes in a priority subset.

[0135] One such event for transmitting selective one-shot HARQ feedback may occur after a failure to receive a DL signal / channel. For example, the WTRU may be configured to monitor a COT structure indication from the BS (e.g., gNB) in a set of monitoring time slots. After failing to receive a COT indication for N consecutive occasions, the WTRU may autonomously transmit selective one-shot HARQ feedback. This approach may be useful if a NACK to ACK error occurs and no DL traffic is scheduled for the WTRU.

[0136] One such event regarding transmission of selective one-shot HARQ feedback may occur after a timer expires. The WTRU may be configured with a timer that is updated based on a schedule of a subset of HARQ PIDs. For example, after receiving a downlink schedule with a HARQ PID from a subset of HARQ PIDs, the timer is reset. In another example, the WTRU may reset the timer each time after it receives a DCI schedule. The value of the timer may be semi-statically configured by the RRC. The WTRU may start the timer depending on the priority level and / or the value of the PDSCH group index indicating the PDSCH.

[0137] In some embodiments, there may be techniques for resource selection for selective one-shot HARQ feedback. The WTRU may determine the resources on which the feedback will be transmitted based on the content of the feedback and the priority of the feedback. For example, the WTRU may have a set of feedback resources and some feedback resources may be associated with specific priority levels. The WTRU may only use such feedback resources if the feedback includes feedback for transmissions only for, or at least for, the associated priority level.

[0138] The WTRU may be configured with different feedback resource types. For example, the WTRU may be configured with PUCCH resources, cell group (CG) resources, scheduling request (SR) resources, random access resources (e.g., for 2-step or 4-step RA). The WTRU may determine the resource types that it can use for UCI feedback (e.g., HARQ-ACK feedback) based on the priority level of the feedback being transmitted. For example, for feedback of the highest priority subset, the WTRU may use any feedback resource type and may therefore select the first available feedback resource. In another example, for feedback of different priority subsets, the WTRU may only select PUCCH or CG resource types and may determine the appropriate feedback resource timing based on the timing of the last DL transmission of the feedback report reporting feedback.

[0139] The WTRU may use dynamically scheduled PUSCH resources to transmit UCI (e.g., HARQ-ACK feedback). The selection of such PUSCH resources may be determined based on whether the WTRU is scheduled to feedback UCI in the same time slot. In another example, the selection of such PUSCH resources may be determined based on the priority of the HARQ-ACK feedback and based on the timing of the PUSCH resources. For example, the WTRU may have a HARQ-ACK codebook consisting of high priority feedback. The WTRU may be scheduled with a PUSCH that occurs before the timing of the next upcoming available feedback resource. The WTRU may autonomously transmit UCI on the scheduled PUSCH. Such a decision to autonomously multiplex UCI into the PUSCH may depend on the priority level of the UCI. This may also depend on the timing of the PUSCH transmission. For example, this may be feasible (e.g., only feasible) for the first PUSCH with a certain channel occupancy time (COT).

[0140] The WTRU may provide an indication to the BS (e.g., gNB) that the UCI is included in the PUSCH. In another example, the DCI scheduling the PUSCH may also trigger a HARQ-ACK feedback report, which may include an expected priority subset.

[0141] The WTRU may determine the appropriate power setting parameters (eg, β offset) for the UCI based on the priority of the UCI and the priority of the PUSCH transmission.

[0142] The WTRU may determine to autonomously transmit UCI based on whether there is any pending high priority UCI for a transmission scheduled with a non-numerical K1 value. For example, the WTRU may always include UCI for high priority data in the first available PUSCH resource when the associated DL transmission is scheduled with a non-numerical K1. In such an example, the WTRU may accumulate HARQ-ACK feedback for all high priority transmissions scheduled with a non-numerical K1 and may transmit the UCI for this set at the first available feedback resource or PUSCH resource.

[0143] In some embodiments, there may be overlapping selective one-time HARQ feedbacks. In one example, the WTRU may be configured to prioritize between selective one-time HARQ feedbacks and / or between selective one-time HARQ feedbacks and other HARQ-ACK codebooks (e.g., dynamic HARQ-ACK codebooks or semi-static HARQ-ACK codebooks) in the case of overlapping uplink resources. In one case, the WTRU may be configured to prioritize only one HARQ feedback using a priority associated with the HARQ feedback. The priority associated with the selective one-time HARQ feedback may be determined based on one or more methods disclosed herein (such as those presented above). In another case, the WTRU may be configured to prioritize the last triggered one-time HARQ feedback. For example, the WTRU may receive a request to transmit a first selective one-time HARQ feedback in time slot n, and subsequently receive another request for a second selective one-time HARQ feedback. The WTRU may prioritize the triggered second selective one-time HARQ feedback.

[0144] In another example, the WTRU may be configured to multiplex multiple selective one-shot HARQ codebooks in one HARQ codebook. The WTRU may sort the scheduled selective one-shot HARQ feedback in increasing order and determine the number of HARQ feedbacks to be multiplexed based on one or more of the following: the last indicated PUCCH resource (e.g., the WTRU may determine how many HARQ codebooks to multiplex based on the payload of the last indicated PUCCH resource); and / or, in the case of multiplexing UCI on PUSCH, the resources available for HARQ-ACK UCI within PUSCH (e.g., the beta factor indicated for HARQ transmission within PUSCH).

[0145] In one embodiment, there may be a PDSCH grouping with multiple HARQ-ACK priorities. In some cases, the WTRU may be configured with a dynamic HARQ-ACK codebook for each priority (e.g., where the size of the HARQ-ACK codebook may change dynamically for each priority). One example of a dynamic HARQ-ACK codebook for each priority may be based on a PDSCH grouping specified in an NR unlicensed. Another example may be based on a dynamic HARQ-ACK codebook specified in an NR. As described herein, there may be a method of supporting a dynamic HARQ-ACK codebook for each priority using an existing PDSCH grouping implementation.

[0146] In some embodiments, there may be a mapping between the PDSCH group and the service / priority type. In one example, the WTRU may be configured to semi-statically associate one or more PDSCH groups with a service / priority type. For example, the WTRU may use RRC signaling to receive a mapping between a PDSCH group index (e.g., a g parameter used in NR-U) and a service / priority type. In other examples, a dynamic indication of a service / priority type may be used to dynamically indicate the association between a PDSCH group and a service / priority type. For example, the WTRU may be configured to support multiple (e.g., two) types of services / priorities and multiple (e.g., two) PDSCH groups. After determining the service type of the scheduled PDSCH, the WTRU may use the PDSCH group indication used in the PDSCH scheduling and associate the service type with the PDSCH group index. This situation may enable the reduction of the overhead of URLLC type services scheduled in a DCI format. For example, if a compact DCI is used, the WTRU may not receive an indication of which PDSCH group the scheduled PDSCH is associated with. The WTRU may use a service / priority indication and then associate the feedback with the configured PDSCH group of the URLLC.

[0147] In the case where there is a dynamic mapping between PDSCH groups and service / priority types, the WTRU may be configured to reset / refresh the HARQ-ACK bits of the PDSCH group when the WTRU receives a downlink assignment with the same PDSCH group index but with a different priority / service type. For example, in the first COT, the WTRU may schedule with a PDSCH of priority 1 (e.g., eMBB type traffic) associated with PDSCH group 1. In subsequent COTs, the WTRU may schedule with a PDSCH of priority 2 (e.g., URLLC type traffic) associated with PDSCH group 1. The WTRU may then refresh, for example, the HARQ-ACK codebook 1 associated with PDSCH group 1 and use the codebook for traffic with priority 2. This solution may be useful if the high priority service scheduled by the DCI format does not have a new feedback indicator (NFI). For example, a compact DCI may be used to schedule URLLC type services. In order to keep the DCI size small, such DCI may not support the NFI bit field. The WTRU may be configured to receive NFI only in a subset of the DCI format. After receiving a DCI with the same PDSCH group index and NFI bit field, the WTRU may follow the NFI indication from the network. In other cases, the WTRU may be configured to autonomously switch the NDI / reset / refresh the HARQ-ACK codebook for a PDSCH group associated with a given priority / service type (e.g., URLLC) after the timer expires and no PDSCH scheduling is received for the PDSCH group. The timer value may be RRC configured or fixed in the specification.

[0148] In some embodiments, there may be a triggering event for transmitting the HARQ-ACK codebook for the PDSCH group. The WTRU may be configured to autonomously transmit a dynamic HARQ-ACK codebook for each priority level based on a triggering event described for one-time HARQ feedback. In addition, the WTRU may be configured to autonomously transmit the HARQ-ACK codebook for the PDSCH group when the WTRU determines that the service / priority type associated with the PDSCH group has changed. For example, the WTRU may be scheduled with a PDSCH belonging to PDSCH group 1, and the PDSCH is associated with priority 2 (e.g., an eMBB type of service). In a subsequent transmission, the WTRU receives a PDSCH belonging to PDSCH group 1, and the PDSCH is associated with priority 1 (e.g., a URLLC type of service). The WTRU may then transmit the HARQ-ACK codebook associated with the previously constructed PDSCH group 1 and reset / refresh the HARQ-ACK codebook.

[0149] In some embodiments, there may be multiple (e.g., two) joint transmissions of HARQ-ACK codebooks for different PDSCH groups. In some instances, the WTRU may determine whether to jointly transmit two HARQ-ACK codebooks for two different PDSCH groups based on a PUCCH resource indication (PRI). For example, in the case where the WTRU is scheduled using compact DCI, there may be no bit field indicating the joint transmission of the HARQ codebook. In one example, the WTRU may be configured to transmit two HARQ-ACK codebooks based on the payload of the indicated PRI. In another example, the WTRU may be semi-statically configured with a subset of PUCCH resources for the joint HARQ-ACK codebook. If the PRI indicates a resource from the subset, the WTRU may transmit two HARQ-ACK codebooks. In another example, if PUSCH is used to transmit HARQ feedback (e.g., piggybacking UCI on PUSCH), the WTRU may determine whether to jointly transmit two HARQ-ACK codebooks. In one example, the WTRU may first determine whether to piggyback UCI on the PUSCH, and then use the parameters for piggybacking indicated by the BS (e.g., gNB) to determine whether to jointly transmit two HARQ-ACK codebooks. For example, if a β factor greater than a threshold is indicated to the WTRU, the WTRU may transmit two HARQ-ACK codebooks.

[0150] In some instances, the WTRU may determine whether to jointly transmit two HARQ-ACK codebooks based on the HARQ-ACK feedback timing indication of the scheduled PDSCH group and / or the HARQ-ACK transmission time of the previous PDSCH group. For example, the WTRU may receive a first DL assignment and a first HARQ-ACK codebook transmission timing associated with PDSCH group 1 in t1. In subsequent DL transmissions, the DL PDSCH is associated with PDSCH group 2 and HARQ-ACK feedback timing t2. In one example, the WTRU may determine whether to jointly transmit two HARQ-ACK codebooks based on the time difference between t1 and t2 (e.g., t2-t1). For example, if t2-t1 is higher than a configured threshold, the WTRU may jointly transmit two HARQ-ACK codebooks. In another example, if t2-t1 is lower than a configured threshold, the WTRU may transmit two HARQ-ACK codebooks.

[0151] Although features and elements are described above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as built-in hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with software may be used to implement a radio frequency transceiver used in a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

1. A wireless transmit / receive unit (WTRU), the WTRU include: A processor configured to: receiving configuration information for providing hybrid automatic repeat request (HARQ) feedback, wherein the configuration information indicates one or more HARQ feedback groups, and wherein each HARQ feedback group includes one or more HARQ processes for each of one or more serving cells, and wherein the configuration of each HARQ feedback group includes an index value; receiving downlink control information (DCI) indicating that the WTRU is to transmit a one-time HARQ feedback transmission, wherein the transmission comprises one or more HARQ feedback bits corresponding to a first group of the one or more HARQ feedback groups, wherein the DCI comprises an indication of the index of the one or more HARQ feedback groups, wherein the DCI does not schedule a physical downlink shared channel (PDSCH) transmission; determining one or more HARQ processes of one or more serving cells associated with the indicated one or more HARQ feedback groups; determining one or more HARQ feedback bits for each included HARQ process of the indicated one or more HARQ feedback groups; and The one-time HARQ feedback transmission is sent including the one or more HARQ feedback bits corresponding to the indicated one or more HARQ feedback groups.

2. The WTRU of claim 1 , wherein the configuration information is received in a radio resource control (RRC) message.

3. The WTRU of claim 1 , wherein the DCI includes the indication of an index associated with the first group.

4. The WTRU of claim 1 , wherein the processor is further configured to construct a dynamic or semi-static HARQ feedback codebook associated with the one-time HARQ feedback.

5. The WTRU of claim 1 , wherein the processor is further configured to determine a number of serving cells and a number of HARQ processes associated with each serving cell.

6. The WTRU of claim 1, wherein the processor is further configured to determine that the DCI is a non-scheduled DCI.

7. The WTRU of claim 1 , wherein the processor is configured to: receiving, via radio resource control (RRC) signaling, a configuration comprising a number of HARQ processes associated with a downlink transmission from a base station; generating a HARQ codebook to perform the one-time HARQ feedback transmission, wherein the HARQ codebook includes one or more information bits corresponding to one or more transport blocks (TBs) determined based on the indicated priority; determining a transmission power for the one-time HARQ feedback based on the number of the one or more information bits; and The one-time HARQ feedback including the HARQ codebook generated based on the indicated priority is sent to the base station at the transmission power.

8. The WTRU of claim 1 , wherein the processor is configured to: determining a priority associated with each transport block (TB), in, Each of the TBs corresponds to a respective HARQ process associated with a downlink transmission from a base station (BS); generating a HARQ codebook to perform the one-time HARQ feedback transmission, wherein the HARQ codebook includes one or more information bits corresponding to one or more transport blocks (TBs) determined based on the indicated priority, wherein the HARQ codebook includes one or more acknowledgement (ACK) or negative acknowledgement (NACK) bits for a first subset of the TBs, wherein each priority associated with the first subset of the TBs is greater than or equal to the indicated priority; as well as Wherein, under the condition that the size of the HARQ codebook is semi-static, the HARQ codebook further includes one or more NACK bits for a second subset of TBs, wherein each priority associated with the second subset of TBs is less than the indicated priority.

9. The WTRU of claim 8, wherein the priority associated with each TB is determined based on a priority of a corresponding previous physical downlink shared channel (PDSCH) transmission, a downlink transmission type, or a dynamic indication received from the BS; in, The corresponding previous PDSCH transmission is associated with a HARQ process corresponding to each TB; The downlink transmission type includes dynamic scheduling or semi-persistent scheduling (SPS); and The dynamic indication is included in downlink control information (DCI) or medium access control (MAC) control element (CE).

10. The WTRU of claim 1 , wherein the processor is configured to transmit a dynamic HARQ-ACK codebook for each priority level of a physical downlink shared channel group based on a triggering event associated with the one-time HARQ feedback transmission.

11. A method performed by a wireless transmit / receive unit (WTRU), the method include: receiving configuration information for providing hybrid automatic repeat request (HARQ) feedback, wherein the configuration information indicates one or more HARQ feedback groups, and wherein each HARQ feedback group includes one or more HARQ processes for each of one or more serving cells, and wherein the configuration of each HARQ feedback group includes an index value; receiving downlink control information (DCI) indicating that the WTRU is to transmit a one-time HARQ feedback transmission, wherein the transmission comprises one or more HARQ feedback bits corresponding to a first group of the one or more HARQ feedback groups, wherein the DCI comprises an indication of the index of the one or more HARQ feedback groups, wherein the DCI does not schedule a physical downlink shared channel (PDSCH) transmission; determining one or more HARQ processes of one or more serving cells associated with the indicated one or more HARQ feedback groups; determining one or more HARQ feedback bits for each included HARQ process of the indicated one or more HARQ feedback groups; and The one-time HARQ feedback transmission is sent including the one or more HARQ feedback bits corresponding to the indicated one or more HARQ feedback groups.

12. The method according to claim 11, in, The configuration information is received in a Radio Resource Control (RRC) message.

13. The method according to claim 11, in, The DCI includes an indication of an index associated with the first group.

14. The method according to claim 11, further comprising: include: A dynamic or semi-static HARQ feedback codebook associated with the one-time HARQ feedback is constructed.

15. The method according to claim 11, in, The method further includes determining a number of serving cells and a number of HARQ processes associated with each serving cell.

16. The method according to claim 11, further comprising: include: It is determined that the DCI is a non-scheduled DCI.

17. The method according to claim 11, further comprising: include: receiving, via radio resource control (RRC) signaling, a configuration comprising a number of HARQ processes associated with a downlink transmission from a base station; generating a HARQ codebook to perform the one-time HARQ feedback transmission, wherein the HARQ codebook includes one or more information bits corresponding to one or more transport blocks (TBs) determined based on the indicated priority; determining a transmission power for the one-time HARQ feedback based on the number of the one or more information bits; and The one-time HARQ feedback including the HARQ codebook generated based on the indicated priority is sent to the base station at the transmission power.

18. The method according to claim 11, further comprising: include: determining a priority associated with each transport block (TB), wherein each TB corresponds to a respective HARQ process associated with a downlink transmission from a base station (BS); generating a HARQ codebook to perform the one-time HARQ feedback transmission, wherein the HARQ codebook includes one or more information bits corresponding to one or more transport blocks (TBs) determined based on the indicated priority, wherein the HARQ codebook includes one or more acknowledgement (ACK) or negative acknowledgement (NACK) bits for a first subset of the TBs, wherein each priority associated with the first subset of the TBs is greater than or equal to the indicated priority; and Wherein, under the condition that the size of the HARQ codebook is semi-static, the HARQ codebook further includes one or more NACK bits for a second subset of TBs, wherein each priority associated with the second subset of TBs is less than the indicated priority.

19. The method according to claim 18, in, The priority associated with each TB is determined based on a priority of a corresponding previous physical downlink shared channel (PDSCH) transmission, a downlink transmission type, or a dynamic indication received from the BS; wherein the corresponding previous PDSCH transmission is associated with a HARQ process corresponding to each TB; The downlink transmission type includes dynamic scheduling or semi-persistent scheduling (SPS); and The dynamic indication is included in downlink control information (DCI) or medium access control (MAC) control element (CE).

20. The method according to claim 11, further comprising: include: Based on a triggering event associated with the one-time HARQ feedback transmission, a dynamic HARQ-ACK codebook for each priority level of a physical downlink shared channel group is transmitted.

Citation Information

Patent Citations

  • Uplink control information transmissions / receptions in wireless networks

    CN105144805A

  • Radio communication apparatus

    EP3484079A1

  • Uplink control information transmissions / receptions in wireless networks

    EP3493606A1

  • Control Element Trigger

    US20190253197A1

  • Simultaneous HARQ-ACK feedback and uplink transmission without dynamic grant

    US20190327755A1