WO2026123747A1

WO2026123747A1 - Transmission/reception window and harq feedback

Info

Publication number: WO2026123747A1
Application number: PCT/CN2025/114184
Authority: WO
Inventors: Hongmei Liu; Zhi YAN; Ruixiang MA
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2025-08-12
Filing date: 2025-08-12
Publication date: 2026-06-18
Anticipated expiration: 2028-02-12

Abstract

Various aspects of the present disclosure relate to transmission/reception window and HARQ feedback. In an aspect, a UE receives, from a network entity, information associated with at least one on-duration window, wherein the at least one on-duration window is associated with at least one of the following: downlink transmission, downlink reception, uplink transmission, or uplink reception. The UE performs communication with the network entity based on the at least one on-duration window.

Description

TRANSMISSION/RECEPTION WINDOW AND HARQ FEEDBACK

TECHNICAL FIELD

The present disclosure relates to wireless communications, and more specifically to user equipments (UEs) , base stations, processors, and methods for transmission/reception window and hybrid automatic repeat request (HARQ) feedback.

BACKGROUND

A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. Each network communication devices, such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) . Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .

In 5G new radio (NR) systems or other generation systems, windows may be designed in some scenarios to support transmissions/receptions in the windows. Enhancements on transmission/reception windows are needed. In addition, enhancements on HARQ feedback are still needed.

SUMMARY

The present disclosure relates to methods, apparatuses, and systems that support transmission/reception window and HARQ feedback.

In a first aspect of the solution, a UE receives, from a network entity, information associated with at least one on-duration window, wherein the at least one on-duration window is associated with at least one of the following: downlink transmission, downlink reception, uplink transmission, or uplink reception. The UE performs communication with the network entity based on the at least one on-duration window.

In some implementations of the method and apparatuses described herein, the at least one on-duration window is associated with a geographical area.

In some implementations of the method and apparatuses described herein, the at least one on-duration window corresponds to a plurality of different on-duration windows.

In some implementations of the method and apparatuses described herein, the information associated with at least one on-duration window comprises an indication of a reference on-duration window and at least one time domain offset between the at least one on-duration window and the reference on-duration window.

In some implementations of the method and apparatuses described herein, the information associated with at least one on-duration window comprises at least one of the following: an indication of an on-duration window for downlink transmission; an indication of an on-duration window for downlink reception; an indication of an on-duration window for uplink transmission; or an indication of an on-duration window for uplink reception.

In some implementations of the method and apparatuses described herein, the information associated with at least one on-duration window comprises an indication of a reference on-duration window and an indication of whether a starting position of an on-duration for downlink reception is before or after a starting position of an on-duration window for uplink transmission.

Some implementations of the method and apparatuses described herein may further include: determining the at least one on-duration window based on a reference on-duration window and at least one of the following: a timing advance value, or a cell specific offset.

In some implementations of the method and apparatuses described herein, the information associated with the at least one on-duration window is valid within a timer or before reception of information associated with at least one updated on-duration window.

In some implementations of the method and apparatuses described herein, at least one default on-duration window is valid after an expiry of the timer.

In some implementations of the method and apparatuses described herein, the at least one updated on-duration window is valid after the reception of the information associated with at least one updated on-duration window.

In some implementations of the method and apparatuses described herein, a time domain resource for a channel or reference signal is out of an on-duration window associated with the channel or reference signal. Some implementations of the method and apparatuses described herein may further include: determining whether to transmit or receive the channel or reference signal on the time domain resource or not based on a priority of the channel or reference signal.

In some implementations of the method and apparatuses described herein, the priority of the channel or reference signal is configured or predefined.

In some implementations of the method and apparatuses described herein, a priority of a synchronization signal block (SSB) is higher than a priority of an uplink transmission.

In some implementations of the method and apparatuses described herein, a priority of at least one channel or reference signal related to a random access procedure is higher than a priority of a downlink transmission.

In some implementations of the method and apparatuses described herein, the priority of the channel or reference signal is applicable for this channel or reference signal.

In some implementations of the method and apparatuses described herein, the priority of the channel or reference signal is applicable for at least one subsequent channel or reference signal associated with the channel or reference signal.

In some implementations of the method and apparatuses described herein, the channel or reference signal is a physical random access channel (PRACH) , and the at least one subsequent channel or reference signal comprises at least one of the following: a message 2 (Msg2) , a message 3 (Msg3) , a message 4 (Msg4) or a HARQ feedback for Msg4.

In some implementations of the method and apparatuses described herein, the channel or reference signal is a physical downlink shared channel (PDSCH) , and the at least one subsequent channel or reference signal comprises a hybrid automatic repeat request (HARQ) feedback associated with the PDSCH.

In some implementations of the method and apparatuses described herein, the channel or reference signal is a physical uplink shared channel (PUSCH) , and the at least one subsequent channel or reference signal comprises a HARQ feedback associated with the PUSCH.

In some implementations of the method and apparatuses described herein, the channel or reference signal and the at least one subsequent channel or reference signal are associated with a same configured grant (CG) configuration.

In some implementations of the method and apparatuses described herein, the channel or reference signal and at least subsequent channel or reference signal are associated with a same semi-persistent scheduling (SPS) configuration.

Some implementations of the method and apparatuses described herein may further include: receiving, from the network entity, an indication of the priority of the channel or reference signal. The indication of the priority of the channel or reference signal is carried in one of the following: downlink control information (DCI) associated with the channel or reference signal; a medium access control (MAC) control element (CE) associated with the channel or reference signal; or a radio resource control (RRC) configuration associated with the channel or reference signal.

Some implementations of the method and apparatuses described herein may further include: determining the priority of the channel or reference signal based on a resource for the channel or reference signal in at least one of the following: a time domain, a frequency domain or a code domain.

In a second aspect of the solution, a UE receives, from a network entity, a first indication indicating whether a hybrid automatic repeat request (HARQ) feedback for a first transmission is enabled or not; and transmits to the network entity or receives from the network entity the HARQ feedback for the first transmission, wherein the HARQ feedback for the first transmission is enabled.

In some implementations of the method and apparatuses described herein, the first transmission is in a physical uplink shared channel (PUSCH) or a physical downlink shared channel (PDSCH) .

In some implementations of the method and apparatuses described herein, the first indication is carried in one of the following: downlink control information (DCI) associated with the first transmission; a medium access control (MAC) control element (CE) associated with the first transmission; or a radio resource control (RRC) configuration associated with the first transmission.

In some implementations of the method and apparatuses described herein, the first indication is carried in a specific bit field for enabling or disabling HRAQ feedback.

In some implementations of the method and apparatuses described herein, the first indication is indicated by re-interpretation of a modulation and coding scheme (MCS) field.

In some implementations of the method and apparatuses described herein, the first indication is valid for the single transmission.

In some implementations of the method and apparatuses described herein, the first indication is valid for a set of transmissions comprising the first transmission and at least one subsequent transmission associated with a same configured grant (CG) configuration.

In some implementations of the method and apparatuses described herein, the first indication is valid for a set of transmissions comprising the first transmission and at least one subsequent transmission associated with a same semi-persistent scheduling (SPS) configuration.

In some implementations of the method and apparatuses described herein, the first indication is valid for at least one transmission comprising the first transmission, wherein the at least one transmission is associated with a same HARQ process number, wherein the at least one transmission is within an indicated duration or comprises an indicated number of transmissions.

In some implementations of the method and apparatuses described herein, the HARQ feedback for the first transmission is disabled. Some implementations of the method and apparatuses described herein may further include: omitting transmitting or receiving the HARQ feedback for the first transmission.

In some implementations of the method and apparatuses described herein, the HARQ feedback for the first transmission is enabled. Some implementations of the method and apparatuses described herein may further include: determining a first feedback window for transmitting or receiving the HARQ feedback for the first transmission.

In some implementations of the method and apparatuses described herein, a plurality of transmissions are within a time period and are associated with a same HARQ process number, wherein HARQ feedbacks for the plurality of transmissions are enabled, wherein the plurality of transmissions comprises the first transmission. Some implementations of the method and apparatuses described herein may further include: determining a plurality of feedback windows for transmitting or receiving the HARQ feedbacks for the plurality of transmissions.

In some implementations of the method and apparatuses described herein, the plurality of feedback windows are evenly distributed within a next time period after the time period.

In some implementations of the method and apparatuses described herein, the size of each of the plurality of feedback windows is determined based on the size of the time period and a number of the plurality of transmissions.

In some implementations of the method and apparatuses described herein, a number of the plurality of transmissions is preconfigured.

Some implementations of the method and apparatuses described herein may further include: receiving, from the network entity, an indication indicative that the plurality of feedback windows are evenly distributed.

In some implementations of the method and apparatuses described herein, a starting point of the first feedback window is associated with a time point of the first transmission and a size of the time period.

In some implementations of the method and apparatuses described herein, an ending point of the first feedback window is determined based on a starting point of a second feedback window for transmitting or receiving a HARQ feedback for a next transmission after the first transmission among the plurality of transmissions.

Some implementations of the method and apparatuses described herein may further include: determining a virtual HARQ process number for the first transmission based on the same HARQ process number and an index of the first feedback window within the plurality of feedback windows.

In some implementations of the method and apparatuses described herein, a starting point of the time period is predefined.

In some implementations of the method and apparatuses described herein, the size of the time period is configured.

In some implementations of the method and apparatuses described herein, the size of the time period is determined based on at least one of the following: system information, a cell specific offset; a timing advance value, or a minimum round trip time.

In a third aspect of the solution, a network entity transmits, to a user equipment (UE) , information associated with at least one on-duration window, wherein the at least one on-duration window is associated with at least one of the following: downlink transmission, downlink reception, uplink transmission, or uplink reception; and performs communication with the UE based on the at least one on-duration window.

In some implementations of the method and apparatuses described herein, the information associated with the at least one on-duration window is valid within a timer or before transmission of information associated with at least one updated on-duration window.

In some implementations of the method and apparatuses described herein, the at least one updated on-duration window is valid after the transmission of the information associated with at least one updated on-duration window.

In some implementations of the method and apparatuses described herein, a time domain resource for a channel or reference signal is out of an on-duration window associated with the channel or reference signal. Some implementations of the method and apparatuses described herein may further include: determining whether to receive or transmit the channel or reference signal on the time domain resource or not based on a priority of the channel or reference signal.

Some implementations of the method and apparatuses described herein may further include: transmitting to the UE, an indication of the priority of the channel or reference signal. The indication of the priority of the channel or reference signal is carried in one of the following: downlink control information (DCI) associated with the channel or reference signal; a medium access control (MAC) control element (CE) associated with the channel or reference signal; or a radio resource control (RRC) configuration associated with the channel or reference signal.

In a fourth aspect of the solution, a network entity transmits, to a user equipment (UE) , a first indication indicating whether a hybrid automatic repeat request (HARQ) feedback for a first transmission is enabled or not; and receives from the UE or transmit to the UE the HARQ feedback for the first transmission, wherein the HARQ feedback for the first transmission is enabled.

In some implementations of the method and apparatuses described herein, the HARQ feedback for the first transmission is disabled. Some implementations of the method and apparatuses described herein may further include: omitting receiving or transmitting the HARQ feedback for the first transmission.

In some implementations of the method and apparatuses described herein, the HARQ feedback for the first transmission is enabled. Some implementations of the method and apparatuses described herein may further include: determining a first feedback window for receiving or transmitting the HARQ feedback for the first transmission.

In some implementations of the method and apparatuses described herein, a plurality of transmissions are within a time period and are associated with a same HARQ process number, wherein HARQ feedbacks for the plurality of transmissions are enabled, wherein the plurality of transmissions comprises the first transmission. Some implementations of the method and apparatuses described herein may further include: determining a plurality of feedback windows for receiving or transmitting the HARQ feedbacks for the plurality of transmissions.

Some implementations of the method and apparatuses described herein may further include: transmitting to the UE, an indication indicative that the plurality of feedback windows are evenly distributed.

In some implementations of the method and apparatuses described herein, an ending point of the first feedback window is determined based on a starting point of a second feedback window for receiving or transmitting a HARQ feedback for a next transmission after the first transmission among the plurality of transmissions.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an example of a wireless communications system that supports transmission/reception window and HARQ feedback in accordance with aspects of the present disclosure.

FIG. 1B illustrates an example diagram of on-durations and off-durations for different geographical areas.

FIGS. 1C and 1D illustrate example diagrams of time domain offsets among uplink and downlink transmissions and receptions in different cases.

FIG. 2 illustrates an example of a signalling procedure of transmission/reception window in accordance with aspects of the present disclosure.

FIGS. 3A and 3B illustrate example diagrams of on-duration windows for uplink and downlink transmissions and receptions.

FIG. 4 illustrates an example of a signalling procedure of HARQ feedback in accordance with aspects of the present disclosure.

FIG. 5 illustrates an example diagram of monitoring windows for HARQ feedback in accordance with aspects of the present disclosure.

FIG. 6 illustrates an example of a device that supports transmission/reception window and HARQ feedback in accordance with aspects of the present disclosure.

FIG. 7 illustrates an example of a processor that supports transmission/reception window and HARQ feedback in accordance with aspects of the present disclosure.

FIGS. 8 and 9 illustrate flowcharts of methods that support transmission/reception window in accordance with aspects of the present disclosure.

FIGS. 10 and 11 illustrate flowcharts of methods that support HARQ feedback in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

Principles of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein may be implemented in various manners other than the ones described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

References in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It shall be understood that although the terms “first” and “second” or the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” , when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof.

As used herein, the term “communication network” refers to a network following any suitable communication standards, such as, 5G new radio (NR) , long term evolution (LTE) , LTE-advanced (LTE-A) , wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , narrow band internet of things (NB-IoT) , and so on. Further, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will also be future type communication technologies and systems in which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned systems.

As used herein, the term “network device” generally refers to a node in a communication network via which a terminal device can access the communication network and receive services therefrom. The network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , a radio access network (RAN) node, an evolved NodeB (eNodeB or eNB) , a NR NB (also referred to as a gNB) , a remote radio unit (RRU) , a radio header (RH) , an infrastructure device for a V2X (vehicle-to-everything) communication, a transmission and reception point (TRP) , a reception point (RP) , a remote radio head (RRH) , a relay, an integrated access and backhaul (IAB) node, a low power node such as a femto BS, a pico BS, and so forth, depending on the applied terminology and technology.

As used herein, the term “terminal device” generally refers to any end device that may be capable of wireless communications. By way of example rather than a limitation, a terminal device may also be referred to as a communication device, a user equipment (UE) , an end user device, a subscriber station (SS) , an unmanned aerial vehicle (UAV) , a portable subscriber station, a mobile station (MS) , or an access terminal (AT) . The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable terminal device, a personal digital assistant (PDA) , a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback appliance, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , a USB dongle, a smart device, wireless customer-premises equipment (CPE) , an internet of things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device (for example, a remote surgery device) , an industrial device (for example, a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. In the following description, the terms: “terminal device, ” “communication device, ” “terminal, ” “user equipment” and “UE, ” may be used interchangeably.

Aspects of the present disclosure are described in the context of a wireless communications system. FIG. 1A illustrates an example of a wireless communications system 100 that supports transmission/reception window and HARQ feedback accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 102 (also referred to as network equipment (NE) ) , one or more UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.

The one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN) , a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. A network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112. For example, a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies. In some implementations, a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an internet-of-things (IoT) device, an internet-of-everything (IoE) device, or machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In some other implementations, a UE 104 may be mobile in the wireless communications system 100.

The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1A. A UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in FIG. 1A. Additionally, or alternatively, a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.

A UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

A network entity 102 may support communications with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) . In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102) . In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) . In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) . An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .

In some implementations, a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open radio access network (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) . For example, a network entity 102 may include one or more of a CU, a DU, a radio unit (RU) , a RAN intelligent controller (RIC) (e.g., a near-real time RIC (Near-RT RIC) , a non-real time RIC (Non-RT RIC) ) , a service management and orchestration (SMO) system, or any combination thereof.

An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) . In some implementations, one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .

Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU. For example, a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., radio resource control (RRC) , service data adaption protocol (SDAP) , packet data convergence protocol (PDCP) ) . The CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.

Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or multiple different cells (e.g., via one or more RUs) . In some implementations, a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .

A CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u) , and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface) . In some implementations, a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.

The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a packet data network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.

The core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) . The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .

In the wireless communications system 100, the network entities 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) . In some implementations, the network entities 102 and the UEs 104 may support different resource structures. For example, the network entities 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) . The network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.

One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames) . Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) . In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to symbols.

In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) . In some implementations, the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) . In some implementations, FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) . For example, FR1 may be associated with a first numerology (e.g., μ=0) , which includes 15 kHz subcarrier spacing; a second numerology (e.g., μ=1) , which includes 30 kHz subcarrier spacing; and a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) . For example, FR2 may be associated with a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., μ=3) , which includes 120 kHz subcarrier spacing.

A non-terrestrial network (NTN) network refers to a network, or a segment of networks using radio frequency (RF) resources on board a satellite or a HAPS, providing 4G/5G access using LTE/NR protocols. The satellite in NTN may be a geostationary earth orbiting (GEO) satellite with a fixed location to the Earth, or a low earth orbiting (LEO) satellite orbiting around the Earth, or a HAPS including Unmanned Aerial Vehicle (UAV) or balloon. In NTN network, due to limitation of transmission/reception power at satellite side, beam hopping for NTN UEs is considered. From UE perspective, only a duration (e.g. 20ms) is available for communication. Due to beam hopping, there are on-durations and off-durations for each geographical area. The on-duration can be a time domain window, and the time resource out of the window can be considered to be off-duration. FIG. 1B illustrates an example diagram of on-durations and off-durations for different geographical areas. As used herein, the terms “on-duration” and “active duration” may be used interchangeably. As used herein, the terms “off-duration” and “non-active duration” may be used interchangeably.

However, there is large propagation delay between RAN node and terminal devices in NTN network. For regenerative satellites at LEO-600km, LEO-1200km and GEO, the two-way propagation delays between RAN node and terminal devices are about 12.89ms, 20.89ms, 270.73ms, respectively. For transparent satellite at LEO-600km, LEO-1200km and GEO, the two-way propagation delays between RAN node and terminal devices are about 25.77ms, 41.77ms, 541.46ms, respectively. If there is a UL transmission from UE, and UE expects DL response from BS side, then the duration from UL transmission to DL reception at UE side will be at least 12.89ms, 20.89ms, 270.73ms, respectively.

Due to the large propagation delay between RAN node and terminal devices in NTN network, there will be large time domain offsets among downlink (DL) transmission (Tx) , DL reception (Rx) , uplink (UL) Tx and UL Rx. DL Rx at UE side is always after DL Tx at BS side, and the difference is one-way propagation delay. UL Rx at BS side is always after UL Tx at UE side, and the different is one-way propagation delay

Regarding the time domain difference between DL Rx at UE side and UL Tx at UE side, it depends on the timing advance (TA) configuration. If UL Tx is before DL Rx by two-way propagation delay, then UL Rx at BS side and DL Tx at BS side are aligned; otherwise, there will be an offset.

For different channels, there are difference requirements regarding the offset between DL Tx and UL Rx at BS side or between UL Tx and DL Rx at UE side.

In the first case, there may be a DL response from BS side after an UL transmission from UE. This case may be applicable at least to UE oriented channels or reference signals (RS) , e,g., PRACH transmission and RAR monitoring, beam failure recovery request transmission and corresponding PDCCH monitoring, PUSCH and expected feedback in PDCCH. In this case, it is expected that there will be UL Tx first, and then DL Rx second at UE side. At BS side, there will be UL Rx first, then after processing, there will be DL Tx at BS side, and then after propagation delay, there will be DL Rx at UE side. FIG. 1C illustrates an example diagram of time domain offsets among uplink and downlink transmissions and receptions in different cases. As shown in FIG. 1C, a PUSCH transmission is transmitted at UE at T0 and received at BS at T1. A round trip time (RTT) is 24 ms, and an offset between the UL Tx at UE side and the UL Rx at BS side is 12 ms. After a processing time (e.g., 4 ms) , a PDCCH transmission (e.g., carrying HARQ feedback of the PUSCH transmission) is transmitted at BS at T2, and received at UE at T3. An offset between the DL Tx at BS side and the DL Rx at UE side is 12 ms. In this case, the UL Tx is before DL Rx at UE side by a large offset, and the UL Rx and DL Tx at BS side may be quite close.

In the second case, there may be an UL response from UE side after a DL transmission from BS. This case may be applicable at least to PDSCH transmission and corresponding HARQ feedback. In this case, it is expected that there will be DL Tx first, and then UL Rx second at BS side. At UE side, there will be DL Rx first, then after processing, there will be UL Tx at UE side, and then after propagation delay, there will be UL Rx at BS side. FIG. 1D illustrates an example diagram of time domain offsets among uplink and downlink transmissions and receptions in different cases. As shown in FIG. 1D, a PDSCH transmission is transmitted at BS at T0 and received at UE at T1. A RTT is 24 ms, and an offset between the DL Tx at BS side and the DL Rx at UE side is 12 ms. After a processing time (e.g., 4 ms) , a PUCCH transmission (e.g., carrying HARQ feedback of the PDSCH transmission) is transmitted at UE at T2, and received at BS at T3. An offset between the UL Tx at UE side and the UL Rx at BS side is 12 ms. In this case, the DL Tx is before UL Rx at BS side by a large offset, and the UL Tx is after DL Rx at UE side by a small processing offset.

If the active duration for a geographical area is concentrated in 20ms with a periodicity of 160ms or 320ms, DL feedback of an UL transmission or UL feedback of a DL transmission may fall into the non-active duration or may be delayed to the next active duration, which may result in data loss or increased delay. Solutions related to lost or delayed response due to the beam hopping are needed.

In addition, the collision of HARQ process IDs might increase due to large propagation delay in NTN. At most 32 HARQ processes are supported in 5GR. For NR NTN, to address the collision of HARQ process IDs due to large propagation delay in NR NTN, HARQ disabling in DCI per HARQ process ID is proposed. In 5GR, HARQ process is configured per HARQ process ID. From network scheduling perspective, if a HARQ process ID is disabled, all PDSCH/PUSCH associated with the disabled HARQ process ID is HARQ disabled. And the BS may associate data which doesn’ t require feedback to PUSCH with the disabled HARQ process ID. However, in some scenarios, there might be a need to use a same HARQ process ID for both PDSCH/PUSCH with disabled HARQ process ID and PDSCH/PUSCH without disabled HARQ process ID, especially when considering the scenario of a large RTT (e.g., 270 ms) .

Since there is no limitation on backward compatibility in 6G, new schemes can be designed to avoid the collision of HARQ process IDs in 6G NTN. The max RTT for transparent satellite for LEO-1200km is about 42ms. If there are 64 HARQ process IDs (increased from 32 HARQ process IDs supported in 5G NR) , the HARQ collision issue may be solved. However, 6 bits are required for HARQ process indication, which increases the signaling overhead. Meanwhile, for GEO, the max RTT is 270ms for regenerative payload, which may not be covered by increasing HARQ process numbers only. Thus, further enhancements are needed to avoid the collision of HARQ process IDs.

In view of the above, embodiments of the present disclosure provide schemes related to transmission/reception window and HARQ feedback. In a first aspect, a UE receives information associated with at least one on-duration window from the base station and performs communication with the base station based on the at least one on-duration window. The at least one on-duration window may be associated with at least one of downlink transmission, downlink reception, uplink transmission, or uplink reception. In a second aspect, a UE receives, from a base station, an indication indicating whether a HARQ feedback for a transmission is enabled or not. If HARQ feedback for the first transmission is enabled, the UE transmits the HARQ feedback for the transmission to the base station (if the transmission is a downlink transmission) or receives the HARQ feedback for the transmission from the base station (if the transmission is a downlink transmission) .

Embodiments of the present disclosure related to the two aspects can be combined. Although some embodiments of the first aspect are contextualized for beam hopping, it should be understood that embodiments of the present disclosure may also be applied to other scenarios with on-durations and off-durations. Although some embodiments of the present disclosure are contextualized for NTN, it should be understood that embodiments of the present disclosure may also be applied to TN. Although some embodiments of the present disclosure are contextualized for 6G, it should be understood that embodiments of the present disclosure may also be applied to other generations, e.g., 4G, 5G or future generations after 6G.

FIG. 2 illustrates an example of a signalling procedure 200 of transmission/reception window in accordance with aspects of the present disclosure. For the purpose of discussion, the procedure 200 will be described with reference to FIG. 1A, and the procedure 200 may involve a UE 104 and a network entity 102 as shown in FIG. 1A. The network entity may be implemented as a base station. It is to be understood that the steps and the order of the steps in FIG. 2 are merely for illustration, and not for limitation. It is to be understood that procedure 200 may further include additional blocks not shown and/or omit some shown blocks, and the scope of the present disclosure is not limited in this regard.

As shown in FIG. 2, the base station 102 transmits (202) information 204 associated with at least one on-duration window to the UE 104. The at least one on-duration window is associated with at least one of downlink transmission, downlink reception, uplink transmission, or uplink reception. The UE 104 receives (206) the information 204 associated with at least one on-duration window from the base station 102. The UE 104 and the base station 102 perform (208) communication with each other based on the at least one on-duration window.

In some embodiments, the at least one on-duration window may be associated with a geographical area. Communication between the base station 102 and UEs located within the geographical area may be performed based on the at least one on-duration window associated with the geographical area.

In some embodiments, the at least one on-duration window may correspond to a plurality of different on-duration windows. For example, the at least one on-duration window may include at least one of an on-duration window for downlink transmission, an on-duration window for downlink reception, an on-duration window for uplink transmission, or an on-duration window for uplink reception. In an example, the base station 102 may perform downlink transmission based on the on-duration window for downlink transmission, and the UE 104 may perform downlink reception based on the on-duration window for downlink reception. In another example, the UE 104 may perform uplink transmission based on the on-duration window for uplink transmission, and the base station 102 may perform uplink reception based on the on-duration window for uplink reception. In some cases, an on-duration window for downlink transmission may be the same as an on-duration window for uplink reception.

In some embodiments, the information 204 associated with at least one on-duration window may include an indication of a reference on-duration window and at least one time domain offset between the at least one on-duration window and the reference on-duration window. The term “reference on-duration window” may be used interchangeably with other suitable terms, e.g., “base on-duration window” , etc. For example, there may be an on-duration configuration for a geographical area and a respective offset for each of DL Tx, DL Rx, UL Tx, UL Rx. The offset can be zero for some of the DL/UL Tx/Rx. If the offset for DL Tx is zero, the on-duration window for DL Tx is aligned with the reference on-duration window configured in the on-duration configuration. The offset can be explicitly configured with respect to a subcarrier spacing (SCS) as a number of slots/symbols. Alternatively, the offset can be explicitly configured in unit of ms. The at least one on-duration window may be configured via a high layer signaling such as RRC and/or MAC CE.

As described with reference to FIGS. 1C and 1D, there may be offsets among DL Tx, DL Rx, UL Tx, UL Rx. The offset between DL Tx and DL Rx and the offset between UL Tx and UL Rx is related to the propagation delay. The offset between DL Tx and UL Rx at BS side may be different for different channels. The offset between UL Tx and DL Rx at UE side may be different for different channels. Thus, the on-duration windows for DL Tx, DL Rx, UL Tx, UL Rx may be different. FIG. 3A illustrates an example diagram of on-duration windows for DL Tx, DL Rx, UL Tx, UL Rx for the first case where UL Tx is before DL Rx at UE side. FIG. 3B illustrates an example diagram of on-duration windows for DL Tx, DL Rx, UL Tx, UL Rx for the second case where UL Tx is after DL Rx at UE side. The on-duration windows for DL Tx, DL Rx, UL Tx, UL Rx may be configured in various manners.

In some embodiments, the information 204 associated with at least one on-duration window may include at least one of the following: an indication of an on-duration window for downlink transmission; an indication of an on-duration window for downlink reception; an indication of an on-duration window for uplink transmission; or an indication of an on-duration window for uplink reception. In other words, the respective on-duration window for each type (DL Tx, DL Rx, UL Tx, UL Rx) may be separately configured. The respective on-duration window for each type may be configured in unit of ms or in unit of slot/symbol with respect to a SCS.

In some embodiments, the information 204 associated with at least one on-duration window may include an indication of a reference on-duration window and an indication of whether a starting position of an on-duration for downlink reception is before or after a starting position of an on-duration window for uplink transmission. The reference on-duration window may be one of an on-duration window for downlink transmission, an on-duration window for downlink reception, an on-duration window for uplink transmission, or an on-duration window for uplink reception. The case selection between the first case where UL Tx is before DL Rx at UE side and the second case where UL Tx is after DL Rx at UE side may be indicated. If UL Tx is before DL Rx at UE side, the time offset between UL Tx and DL Rx at UE side is large, e.g., considering the propagation delay. If UL Tx is after DL Rx at UE side, then the time offset between DL Rx and UL Tx at UE side is small, e.g., considering a processing time.

In some implementations, the UE may determine the at least one on-duration window based on the reference on-duration window and at least one of a timing advance (TA) value or a cell specific offset (e.g., k-offset) . The cell specific offset is used to determine offset between DL reception (e.g. PDCCH) and corresponding uplink transmission (e.g. scheduled PUSCH) . The cell specific offset is configured in system information. The cell specific offset can also be further updated by MAC CE signaling. For example, one of an on-duration window for downlink transmission, an on-duration window for downlink reception, an on-duration window for uplink transmission, or an on-duration window for uplink reception may be explicitly configured, and other on-duration windows may be determined based on the (instantaneous) TA applied by the UE, or the cell specific k-offset configured in system information or the UE-specific k-offset determined based on system information and MAC CE.

In some embodiments, the information 204 associated with the at least one on-duration window is valid within a timer. At least one default on-duration window is valid after an expiry of the timer. In other words, the at least one on-duration window may be associated with a timer. After expiry of the timer, a default offset or a default on-duration window for each of DL Tx, DL Rx, UL Tx, UL Rx may be applied.

Alternatively, the information 204 associated with the at least one on-duration window is valid within a timer or before reception of information associated with at least one updated on-duration window. The at least one updated on-duration window is valid after the reception of the information 204 associated with at least one updated on-duration window. In other words, a new indication of at least one on-duration window for DL Tx, DL Rx, UL Tx, UL Rx may override the previous indication of at least one on-duration window for DL Tx, DL Rx, UL Tx, UL Rx.

A classical size of on-duration may be 20ms considering the coverage ratio and active beam ratio for a satellite. In some cases, there may be continuous channels/RS, e.g., DL->UL->DL, or UL->DL->UL. For example, for the DL->UL->DL, the first DL may be a PDCCH scheduling a PUSCH, and the UL may be the scheduled PUSCH, and the second DL may be a feedback (A/N) corresponding to the scheduled PUSCH. In another example, for the UL-DL->UL, the first UL may be a PRACH transmission, and the DL is RAR, and the second UL is msg3. The last channel/RS in the continuous channels/RS might fall out of the 20ms duration. It may be beneficial to design some exceptions for the off-duration window. Some rules or indications for the priority of a channel/RS may be designed.

In some embodiments, if a time domain resource for a channel or reference signal is out of an on-duration window associated with the channel or reference signal, the UE 104 may determine whether to transmit or receive the channel or reference signal on the time domain resource or not based on a priority of the channel or reference signal.

In some implementations, the priority of the channel or reference signal may be predefined. In some examples, a priority of a synchronization signal block (SSB) is higher than a priority of an uplink transmission or other downlink reception. Alternatively or additionally, a priority of at least one channel or reference signal related to a random access procedure is higher than a priority of a downlink transmission or other uplink channel or uplink reference signal. For example, SSB and msg 1/2/3/4 may have a higher priority than the on-duration/off-duration. When overlapped with an off-duration, transmission and reception of SSB or msg 1/2/3/4 will be performed. In a more specific example, if SSB for a first geographical area is overlapped with PDSCH for a second geographical area, SSB for the first geographical area is transmitted, and the overlapped PDSCH for the second geographical area may be dropped. If the network supports a FDD scheme, then the satellite may treat DL/UL separately. If the network supports a TDD scheme, the network may determine the high priority channel/RS when there is time domain overlap between DL and UL. For example, SSB has a higher priority than PRACH and all following msg 1/2/3/4. The on-duration/off-duration may have a higher priority than periodic RS and other dynamic scheduling. In other words, periodic RS and other dynamic scheduling may only transmitted when overlapped with an on-duration.

In some implementations, the priority of the channel or reference signal may be configured. For example, the priority of the channel or reference signal may be determined based on an explicit indication of the priority value.

In some examples, the priority of the channel or reference signal is applicable for this channel or reference signal. In other words, if a priority value is indicated for a channel/RS, this priority value may be used for this channel/RS. In some examples, the priority of the channel or reference signal may be valid within a duration. For example, if a priority value is indicated for a channel/RS, this priority value may be used for this channel/RS for a duration starting from the priority configuration or from the first transmission/reception of the channel or RS.

In some examples, the priority of the channel or reference signal is applicable for at least one subsequent channel or reference signal associated with the channel or reference signal. In other words, if the priority value is indicated for a first channel, and this priority value may be applied to the following second RS/channel associated the first channel/RS.

In one example, the channel or reference signal is a PRACH, and the at least one subsequent channel or reference signal may include at least one of the following: a Msg2, a Msg3, a Msg4 or a HARQ feedback for Msg4. For example, if the priority value is indicated for PRACH, this priority value may be applicable until msg5 is transmitted.

In another example, the channel or reference signal is a PUSCH, and the at least one subsequent channel or reference signal may include a HARQ feedback associated with the PUSCH. For example, if the priority value is indicated for a PUSCH, this priority value may be applicable to the next PDCCH monitoring occasion until a PDCCH with same HARQ process ID is received. As used herein, the terms “HARQ process ID” and “HARQ process number” may be used interchangeably.

In another example, the channel or reference signal is a PDSCH, and the at least one subsequent channel or reference signal may include a HARQ feedback associated with the PDSCH. For example, if the priority value is indicated for a PDSCH, this priority value may be applicable to the next PUCCH transmission occasion for transmitting A/N for the PDSCH.

In another example, the channel or reference signal and the at least one subsequent channel or reference signal are associated with a same configured grant (CG) configuration. In another example, the channel or reference signal and at least subsequent channel or reference signal are associated with a same semi-persistent scheduling (SPS) configuration.

In some examples, the UE 104 may receive, from the base station 102, an indication of the priority of the channel or reference signal. The indication of the priority of the channel or reference signal may be carried in a DCI or a MAC CE or a RRC configuration associated with the channel or reference signal. In other words, the priority value may be explicitly configured or indicated. For example, the priority value may be indicated in 1 bit, indicating whether the corresponding channel/RS is restricted by the on-duration or not. Alternatively, the priority value may be indicated in more than one bit with more states indicating different priority levels.

In some examples, the UE 104 may determine the priority of the channel or reference signal based on a resource for the channel or reference signal in at least one of the following: a time domain, a frequency domain or a code domain. In other words, the priority value may be implicitly determined based on a specific time/frequency/code domain resource. For example, different time/frequency/code domain resources may be associated with different priority values.

With some embodiments of the present disclosure, the on-duration windows for DL Tx, DL Rx, UL Tx, UL Rx may be different, thus avoiding lost or delayed responses and improving communication performance.

FIG. 4 illustrates an example of a signalling procedure 400 of HARQ feedback in accordance with aspects of the present disclosure. For the purpose of discussion, the procedure 400 will be described with reference to FIG. 1A, and the procedure 400 may involve a UE 104 and a network entity 102 as shown in FIG. 1A. The network entity may be implemented as a base station. It is to be understood that the steps and the order of the steps in FIG. 4 are merely for illustration, and not for limitation. It is to be understood that procedure 400 may further include additional blocks not shown and/or omit some shown blocks, and the scope of the present disclosure is not limited in this regard. It should be understood that the procedure 400 may be performed independently from or in combination with the procedure 200 in FIG. 2.

As shown in FIG. 4, the base station 102 transmits (402) , to the UE 104, a first indication 404 indicating whether a HARQ feedback for a first transmission is enabled or not. The UE 104 receives (406) the first indication 404 from the base station 102. If the HARQ feedback for the first transmission is enabled, the HARQ feedback 408 for the first transmission is transmitted. For example, if the first transmission is an uplink transmission (e.g., a PUSCH transmission) and the HARQ feedback for the first transmission is enabled, the UE 104 receives the HARQ feedback 408 for the first transmission from the base station 102. In another example, if the first transmission is a downlink transmission (e.g., a PDSCH transmission) and the HARQ feedback for the first transmission is enabled, the UE 104 transmits the HARQ feedback 408 for the first transmission to the base station 102.

In some embodiments, if the HARQ feedback for the first transmission is disabled, the UE 104 may omit transmitting or receiving the HARQ feedback for the first transmission.

In some embodiments, the first indication 404 may be carried in a DCI or a MAC CE or a RRC configuration associated with the first transmission. In this way, the HARQ enabling/disabling may be configured per transmission. For example, whether a HARQ feedback is enabled or disabled may be configured/indicated for each PUSCH transmission or each PDSCH transmission. That is, HARQ enabling/disabling per PDSCH/PUSCH is supported.

In some embodiments, the first indication 404 may be carried in a specific bit field for enabling or disabling HRAQ feedback. For example, a new bit in DCI/MAC CE/RRC configuration may be indicative of whether the scheduled PDSCH or PUSCH is HARQ disabled or not.

In some embodiments, the first indication 404 may be indicated by re-interpretation of existing fields, e.g. a modulation and coding scheme (MCS) field. For example, some codepoints of the MAC field may be used to implicitly indicate the HARQ enabling/disabling. The actual MCS may be a subset of the total MCS table. For example, there are 5 bits for MCS indication, and codepoints 29, 30, 31 may be used to indicate HARQ disabling, and the corresponding MCS may be based on index#0, index#6, index#12, which may be associated with QPSK, 16QAM, 64QAM respectively.

In some embodiments, the first indication 404 is valid for the single transmission. For example, an indication of HARQ enabling/disabling is carried in a DCI scheduling a PDSCH or PUSCH, and the HARQ enabling/disabling indication is applicable to the scheduled PDSCH or PUSCH only.

In some embodiments, the first indication 404 is valid for a set of transmissions comprising the first transmission and at least one subsequent transmission associated with a same configured grant (CG) configuration. For example, an indication of HARQ enabling/disabling is carried in a DCI or MAC CE activating a CG configuration or is carried in RRC configuration of the CG configuration, and the HARQ enabling/disabling indication is applicable to all the corresponding CG-based PUSCH transmissions.

In some embodiments, the first indication 404 is valid for a set of transmissions comprising the first transmission and at least one subsequent transmission associated with a same semi-persistent scheduling (SPS) configuration. For example, an indication of HARQ enabling/disabling is carried in a DCI or MAC CE activating a SPS configuration or is carried in RRC configuration of the SPS configuration, and the HARQ enabling/disabling indication is applicable to all the corresponding SPS-based PDSCH transmissions.

In some embodiments, the first indication 404 is valid for at least one transmission comprising the first transmission. The at least one transmission is associated with a same HARQ process number. The at least one transmission may be within an indicated duration. In other words, a timer may be associated with the HARQ enabling/disabling indication. The HARQ enabling/disabling indication may be applicable to PDSCH/PUSCH with the same HARQ process ID within the duration of the timer. The timer may be indicated or configured in a DCI or a MAC CE or a RRC configuration.

In some embodiments, the first indication 404 is valid for at least one transmission comprising the first transmission. The at least one transmission is associated with a same HARQ process number. The at least one transmission may include an indicated number of transmissions. In other words, the HARQ enabling/disabling indication may be applicable to the indicated number of PDSCH/PUSCH transmissions with the same HARQ process ID. The number may be indicated or configured in a DCI or a MAC CE or a RRC configuration. In a more specific example, for a scheduled PUSCH, a specific bit field in DCI indicates that HARQ is disabled for the scheduled PUSCH, the HARQ process ID is 3, and the number configured by RRC configuration is 4. Then, there will be 4 PUSCH with HARQ process ID 3 with HARQ disabled.

In some embodiments, PDSCH/PUSCH transmissions may be transmitted with repetition to enhance reliability. Repetitions may be transmitted for coverage enhancement, and schemes, such as repetition number indication in DCI, TBoMS or joint DMRS processing for multiple slots, may be applied.

In some embodiments, if the HARQ feedback for the first transmission is enabled, the UE 104 may determine a first feedback window for transmitting or receiving the HARQ feedback for the first transmission. In some embodiments, if a plurality of transmissions including the first transmission are within a time period and are associated with a same HARQ process number, and HARQ feedbacks for the plurality of transmissions are enabled, the UE 104 may determine a plurality of feedback windows for transmitting or receiving the HARQ feedbacks for the plurality of transmissions. In some embodiments, a starting point of the time period may be predefined. In some embodiments, the size of the time period may be configured. Alternatively, the size of the time period may be determined based on at least one of the following: system information, a cell specific offset; a timing advance value, or a minimum RTT. In some examples, the time period may be a periodic window associated with a minimum RTT. For example, if there are multiple HARQ enabled PUSCH transmissions reusing the same HARQ process ID within a minimum RTT, respective monitoring windows may be determined for monitoring feedbacks of these PUSCH transmissions.

In some implementations, the plurality of feedback windows may be evenly distributed within a next time period after the time period. The size of each of the plurality of feedback windows may be determined based on the size of the time period and a number of the plurality of transmissions. In some examples, a number of the plurality of transmissions may be preconfigured. In some examples, the UE 104 may receive, from the base station 102, an indication indicative that the plurality of feedback windows are evenly distributed, and the UE 104 may determine the plurality of feedback windows based on the indication. For example, if there are multiple HARQ enabled PUSCH transmissions reusing the same HARQ process ID, time resources may be divided for different HARQ enabled PUSCH associated with the same HARQ process ID, and the division may be based on an even distribution of a periodic window. The division may be based on the number of HARQ enabled PUSCH transmissions sharing same HARQ process ID.

In some implementations, a starting point of the first feedback window may be associated with a time point of the first transmission and a size of the time period. For example, For a PUSCH#1 transmission at T1, the feedback on corresponding PDCCH is at least minimum RTT (e.g. RTT1) after the PUSCH#1 transmission (T1) , i.e., no earlier than T1+RTT1. An ending point of the first feedback window may be determined based on a starting point of a second feedback window for transmitting or receiving a HARQ feedback for a next transmission after the first transmission among the plurality of transmissions. For example, if there are multiple HARQ enabled PUSCH transmissions reusing the same HARQ process ID, time resources may be divided based on the scheduling of the next PUSCH transmission with the same HARQ process ID. In other words, if a second HARQ enabled PUSCH with a same HARQ process ID is scheduled, the PDCCH monitoring window for the first PUSCH ends when the PDCCH monitoring window for the second PUSCH starts. In some examples, the UE 104 may receive, from the base station 102, an indication indicative that that the first feedback window is associated with the next transmission, and the UE 104 may determine the plurality of feedback windows based on the indication.

In some implementations, the UE 104 may determine a virtual HARQ process number for the first transmission based on the same HARQ process number and an index of the first feedback window within the plurality of feedback windows. For example, if there are multiple HARQ enabled PUSCH transmissions reusing the same HARQ process ID K, for a M-th PUSCH transmission among the multiple PUSCH transmissions, the actual process HARQ process ID is K+N* (M-1) , wherein N is a predefined value, e.g., the maximum number of HARQ process IDs, which may be a predefined value or may be indicated in DCI (e.g. if there are 4 bits in DCI for HARQ process ID indication, then N=16) .

FIG. 5 illustrates an example diagram of monitoring windows for HARQ feedback in accordance with aspects of the present disclosure. As shown in FIG. 5, a PUSCH#1 transmission with HARQ process ID=3 and HARQ enabled is transmitted at T1. The monitoring window for the feedback on corresponding PDCCH starts at minimum RTT (e.g. RTT1) after the PUSCH#1 transmission (T1) , e.g., at T1+RTT1. The minimum RTT may be based on the satellite attitude which is broadcasted in system information or based on k-offset broadcasted. Alternatively, the minimum RTT may be the same as the time difference between PRACH transmission and RAR monitoring.

For PUSCH transmissions with HARQ disabled, no monitoring window for the feedback is needed. A PUSCH#3 transmission with HARQ process ID=3 and HARQ enabled is transmitted at T2, which is the second HARQ enabled PUSCH with same HARQ process ID after PUSCH#1 transmission. In the example shown in FIG. 5, the PDCCH monitoring window for the PUSCH#1 ends when the PDCCH monitoring window for the PUSCH#3 starts, e.g., at T2+RTT1. Thus, the PDCCH monitoring window for the PUSCH#1 may be from T1+RTT1 to T2+RTT1.

If there is another HARQ enabled PUSCH with same HARQ process ID K, it may be considered that the actual HARQ process ID is K+N* (M-1) , where N is a predefined value, e.g. 32 or the maximum number of HARQ process ID which may be indicated in DCI, and where M is the times of occurrence of PUSCH with same process ID. For example, for PUSCH#1, M=1, K=3, and the actual HARQ process ID is 3; for PUSCH#3, M=2, K=3, and the actual HARQ process ID is 35 (assuming N=32) .

The HARQ enabled PUSCH#3 transmission with same HARQ process ID is scheduled in T2 which is between T1 and T1+RTT1 (i.e., after the PUSCH#1 transmission and before the start of PDCCH monitoring window for the PUSCH#1) , and will be considered to be a new scheduling and is not to be combined with the PUSCH#1 transmission at T1.

If there is a further PUSCH scheduled between T1+RTT1 and T2+RTT1 (i.e., within the PDCCH monitoring window for the PUSCH#1) , and if the A/N indicated in the PDCCH is for retransmission, this PUSCH transmission may be considered to be associated with PUSCH#1.

If there is a further PUSCH scheduled within the PDCCH monitoring window for the PUSCH#3, and if the A/N indicated in the PDCCH is for retransmission, this PUSCH transmission may be considered to be associated with PUSCH#3.

Alternatively, the number of HARQ enabled PUSCH sharing same HARQ process ID may be pre-configured. There will be division of time resources for different HARQ enabled PUSCH associated with the same HARQ process ID. The division may be evenly distribution of a periodic window. The periodic window starts from a predefined time position or starts from the first PUSCH associated with the HARQ process ID. The division may be based on the number of HARQ enabled PUSCH sharing same HARQ process ID. The window size may be pre-defined, e.g. same as the min-RTT in the corresponding network, e.g. 260ms for GEO.

For example, assume the number of HARQ enabled PUSCH sharing same HARQ process ID is four, and the size of the periodic window is minimum RTT (e.g., RTT1) . PUSCH#1, PUSCH#2, PUSCH#3 and PUSCH#4 sharing same HARQ process ID and with HARQ enabled are transmitted within a window from T0 to T0+RTT1. The respective feedback monitoring windows may be T0+RTT1 to T0+1.25×RTT1, T0+1.25×RTT1 to T0+1.5×RTT1, T0+1.5×RTT1 to T0+1.75×RTT1, and T0+1.75×RTT1 to T0+2×RTT1, respectively.

Whether the division is evenly distribution or based on reception of DCI scheduling PUSCH with the same HARQ process ID may be pre-defined or configured. With some embodiments of the present disclosure, a scheme is designed for avoiding collision of HARQ process IDs. This is in particular beneficial for scenarios with a large propagation delay.

FIG. 6 illustrates an example of a device 600 that supports transmission/reception window and HARQ feedback in accordance with aspects of the present disclosure. The device 600 may be an example of a UE 104 or a base station 102 as described herein. The device 600 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 600 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 602, a memory 604, a transceiver 606, and, optionally, an I/O controller 608. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 602, the memory 604, the transceiver 606, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 602, the memory 604, the transceiver 606, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

In some implementations, the processor 602, the memory 604, the transceiver 606, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 602 and the memory 604 coupled with the processor 602 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 602, instructions stored in the memory 604) .

For example, the processor 602 may support wireless communication at the device 600 in accordance with examples as disclosed herein. The processor 602 may be configured to operable to support a means for receiving, from a network entity, information associated with at least one on-duration window, wherein the at least one on-duration window is associated with at least one of the following: downlink transmission, downlink reception, uplink transmission, or uplink reception; and a means for performing communication with the network entity based on the at least one on-duration window.

In another example, the processor 602 may support wireless communication at the device 600 in accordance with examples as disclosed herein. The processor 602 may be configured to operable to support a means for transmitting, to a user equipment (UE) , information associated with at least one on-duration window, wherein the at least one on-duration window is associated with at least one of the following: downlink transmission, downlink reception, uplink transmission, or uplink reception; and a means for performing communication with the UE based on the at least one on-duration window.

In another example, the processor 602 may support wireless communication at the device 600 in accordance with examples as disclosed herein. The processor 602 may be configured to operable to support a means for receiving, from a network entity, a first indication indicating whether a hybrid automatic repeat request (HARQ) feedback for a first transmission is enabled or not; and a means for transmitting to the network entity or receiving from the network entity the HARQ feedback for the first transmission, wherein the HARQ feedback for the first transmission is enabled.

In another example, the processor 602 may support wireless communication at the device 600 in accordance with examples as disclosed herein. The processor 602 may be configured to operable to support a means for transmitting, to a user equipment (UE) , a first indication indicating whether a hybrid automatic repeat request (HARQ) feedback for a first transmission is enabled or not; and a means for receiving, from the UE or transmitting to the UE the HARQ feedback for the first transmission, wherein the HARQ feedback for the first transmission is enabled.

The processor 602 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some implementations, the processor 602 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 602. The processor 602 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 604) to cause the device 600 to perform various functions of the present disclosure.

The memory 604 may include random access memory (RAM) and read-only memory (ROM) . The memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 602 cause the device 600 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 602 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 604 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The I/O controller 608 may manage input and output signals for the device 600. The I/O controller 608 may also manage peripherals not integrated into the device M02. In some implementations, the I/O controller 608 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 608 may utilize an operating system such as or another known operating system. In some implementations, the I/O controller 608 may be implemented as part of a processor, such as the processor 606. In some implementations, a user may interact with the device 600 via the I/O controller 608 or via hardware components controlled by the I/O controller 608.

In some implementations, the device 600 may include a single antenna 610. However, in some other implementations, the device 600 may have more than one antenna 610 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 606 may communicate bi-directionally, via the one or more antennas 610, wired, or wireless links as described herein. For example, the transceiver 606 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 606 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 610 for transmission, and to demodulate packets received from the one or more antennas 610. The transceiver 606 may include one or more transmit chains, one or more receive chains, or a combination thereof.

A transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) . The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmit chain may also include one or more antennas 610 for transmitting the amplified signal into the air or wireless medium.

A receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receive chain may include one or more antennas 610 for receive the signal over the air or wireless medium. The receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal. The receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

FIG. 7 illustrates an example of a processor 700 that supports transmission/reception window and HARQ feedback in accordance with aspects of the present disclosure. The processor 700 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 700 may include a controller 702 configured to perform various operations in accordance with examples as described herein. The processor 700 may optionally include at least one memory 704, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 700 may optionally include one or more arithmetic-logic units (ALUs) 706. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 700 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 700) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .

The controller 702 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 700 to cause the processor 700 to support various operations of a base station in accordance with examples as described herein. For example, the controller 702 may operate as a control unit of the processor 700, generating control signals that manage the operation of various components of the processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

The controller 702 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 704 and determine subsequent instruction (s) to be executed to cause the processor 700 to support various operations in accordance with examples as described herein. The controller 702 may be configured to track memory address of instructions associated with the memory 704. The controller 702 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 702 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 700 to cause the processor 700 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 702 may be configured to manage flow of data within the processor 700. The controller 702 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 700.

The memory 704 may include one or more caches (e.g., memory local to or included in the processor 700 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 704 may reside within or on a processor chipset (e.g., local to the processor 700) . In some other implementations, the memory 704 may reside external to the processor chipset (e.g., remote to the processor 700) .

The memory 704 may store computer-readable, computer-executable code including instructions that, when executed by the processor 700, cause the processor 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 702 and/or the processor 700 may be configured to execute computer-readable instructions stored in the memory 704 to cause the processor 700 to perform various functions. For example, the processor 700 and/or the controller 702 may be coupled with or to the memory 704, and the processor 700, the controller 702, and the memory 704 may be configured to perform various functions described herein. In some examples, the processor 700 may include multiple processors and the memory 704 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

The one or more ALUs 706 may be configured to support various operations in accordance with examples as described herein. In some implementation, the one or more ALUs 706 may reside within or on a processor chipset (e.g., the processor 700) . In some other implementations, the one or more ALUs 706 may reside external to the processor chipset (e.g., the processor 700) . One or more ALUs 706 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 706 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 706 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 706 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 706 to handle conditional operations, comparisons, and bitwise operations.

For example, the processor 700 may support wireless communication in accordance with examples as disclosed herein. The processor 700 may be configured to or operable to support a means for receiving, from a network entity, information associated with at least one on-duration window, wherein the at least one on-duration window is associated with at least one of the following: downlink transmission, downlink reception, uplink transmission, or uplink reception; and a means for performing communication with the network entity based on the at least one on-duration window.

In another example, the processor 700 may support wireless communication in accordance with examples as disclosed herein. The processor 700 may be configured to or operable to support a means for transmitting, to a user equipment (UE) , information associated with at least one on-duration window, wherein the at least one on-duration window is associated with at least one of the following: downlink transmission, downlink reception, uplink transmission, or uplink reception; and a means for performing communication with the UE based on the at least one on-duration window.

In another example, the processor 700 may support wireless communication in accordance with examples as disclosed herein. The processor 700 may be configured to or operable to support a means for receiving, from a network entity, a first indication indicating whether a hybrid automatic repeat request (HARQ) feedback for a first transmission is enabled or not; and a means for transmitting to the network entity or receiving from the network entity the HARQ feedback for the first transmission, wherein the HARQ feedback for the first transmission is enabled.

In another example, the processor 700 may support wireless communication in accordance with examples as disclosed herein. The processor 700 may be configured to or operable to support a means for transmitting, to a user equipment (UE) , a first indication indicating whether a hybrid automatic repeat request (HARQ) feedback for a first transmission is enabled or not; and a means for receiving, from the UE or transmitting to the UE the HARQ feedback for the first transmission, wherein the HARQ feedback for the first transmission is enabled.

FIG. 8 illustrates a flowchart of a method 800 that supports transmission/reception window in accordance with aspects of the present disclosure. The operations of the method 800 may be implemented by a device or its components as described herein. For example, the operations of the method 800 may be performed by the UE 104 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 805, the method may include receiving, from a network entity, information associated with at least one on-duration window, wherein the at least one on-duration window is associated with at least one of the following: downlink transmission, downlink reception, uplink transmission, or uplink reception. The operations of 805 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 805 may be performed by a device as described with reference to FIG. 1A.

At 810, the method may include performing communication with the network entity based on the at least one on-duration window. The operations of 810 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 810 may be performed by a device as described with reference to FIG. 1A.

FIG. 9 illustrates a flowchart of a method 900 that supports transmission/reception window in accordance with aspects of the present disclosure. The operations of the method 900 may be implemented by a device or its components as described herein. For example, the operations of the method 900 may be performed by the base station 102 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 905, the method may include transmitting, to a user equipment (UE) , information associated with at least one on-duration window, wherein the at least one on-duration window is associated with at least one of the following: downlink transmission, downlink reception, uplink transmission, or uplink reception. The operations of 905 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 905 may be performed by a device as described with reference to FIG. 1A.

At 910, the method may include performing communication with the UE based on the at least one on-duration window. The operations of 910 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 910 may be performed by a device as described with reference to FIG. 1A.

FIG. 10 illustrates a flowchart of a method 1000 that supports HARQ feedback in accordance with aspects of the present disclosure. The operations of the method 1000 may be implemented by a device or its components as described herein. For example, the operations of the method 1000 may be performed by the UE 104 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 1005, the method may include receiving, from a network entity, a first indication indicating whether a hybrid automatic repeat request (HARQ) feedback for a first transmission is enabled or not. The operations of 1005 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1005 may be performed by a device as described with reference to FIG. 1A.

At 1010, the method may include transmitting to the network entity or receiving from the network entity the HARQ feedback for the first transmission, wherein the HARQ feedback for the first transmission is enabled. The operations of 1010 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1010 may be performed by a device as described with reference to FIG. 1A.

FIG. 11 illustrates a flowchart of a method 1100 that supports HARQ feedback in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by a device or its components as described herein. For example, the operations of the method 1100 may be performed by the base station 102 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 1105, the method may include transmitting, to a user equipment (UE) , a first indication indicating whether a hybrid automatic repeat request (HARQ) feedback for a first transmission is enabled or not. The operations of 1105 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1105 may be performed by a device as described with reference to FIG. 1A.

At 1110, the method may include receiving, from the UE or transmitting to the UE the HARQ feedback for the first transmission, wherein the HARQ feedback for the first transmission is enabled. The operations of 1110 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1110 may be performed by a device as described with reference to FIG. 1A.

It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

As used herein, including in the claims, an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

A user equipment (UE) , comprising:

a processor; and

a transceiver coupled to the processor,

wherein the processor is configured to:

receive, from a network entity via the transceiver, information associated with at least one on-duration window, wherein the at least one on-duration window is associated with at least one of the following: downlink transmission, downlink reception, uplink transmission, or uplink reception; and

perform communication with the network entity based on the at least one on-duration window.
The UE of claim 1, wherein the at least one on-duration window is associated with a geographical area.
The UE of claim 1, wherein the at least one on-duration window corresponds to a plurality of different on-duration windows.
The UE of claim 1, wherein the information associated with at least one on-duration window comprises an indication of a reference on-duration window and at least one time domain offset between the at least one on-duration window and the reference on-duration window.
The UE of claim 1, wherein the information associated with at least one on-duration window comprises at least one of the following:

an indication of an on-duration window for downlink transmission;

an indication of an on-duration window for downlink reception;

an indication of an on-duration window for uplink transmission; or

an indication of an on-duration window for uplink reception.
The UE of claim 1, wherein the information associated with at least one on-duration window comprises an indication of a reference on-duration window and an indication of whether a starting position of an on-duration for downlink reception is before or after a starting position of an on-duration window for uplink transmission.
The UE of claim 1, wherein the processor is further configured to:

determine the at least one on-duration window based on a reference on-duration window and at least one of the following:

a timing advance value, or

a cell specific offset.
The UE of claim 1, wherein the information associated with the at least one on-duration window is valid within a timer or before reception of information associated with at least one updated on-duration window.
The UE of claim 8, wherein at least one default on-duration window is valid after an expiry of the timer; or

wherein the at least one updated on-duration window is valid after the reception of the information associated with at least one updated on-duration window.
The UE of claim 1, wherein a time domain resource for a channel or reference signal is out of an on-duration window associated with the channel or reference signal, and the processor is further configured to:

determine whether to transmit or receive the channel or reference signal on the time domain resource or not based on a priority of the channel or reference signal.
The UE of claim 10, wherein the priority of the channel or reference signal is configured or predefined.
The UE of claim 10, wherein at least one of the following:

a priority of a synchronization signal block (SSB) is higher than a priority of an uplink transmission; or

a priority of at least one channel or reference signal related to a random access procedure is higher than a priority of a downlink transmission.
The UE of claim 10, wherein the priority of the channel or reference signal is applicable for this channel or reference signal; or

wherein the priority of the channel or reference signal is applicable for at least one subsequent channel or reference signal associated with the channel or reference signal.
The UE of claim 13, wherein one of the following:

the channel or reference signal is a physical random access channel (PRACH) , and the at least one subsequent channel or reference signal comprises at least one of the following: a message 2 (Msg2) , a message 3 (Msg3) , a message 4 (Msg4) or a HARQ feedback for Msg4;

the channel or reference signal is a physical downlink shared channel (PDSCH) , and the at least one subsequent channel or reference signal comprises a hybrid automatic repeat request (HARQ) feedback associated with the PDSCH;

the channel or reference signal is a physical uplink shared channel (PUSCH) , and the at least one subsequent channel or reference signal comprises a HARQ feedback associated with the PUSCH;

the channel or reference signal and the at least one subsequent channel or reference signal are associated with a same configured grant (CG) configuration; or

the channel or reference signal and at least subsequent channel or reference signal are associated with a same semi-persistent scheduling (SPS) configuration.
The UE of claim 10, wherein the processor is further configured to:

receive, from the network entity via the transceiver, an indication of the priority of the channel or reference signal, wherein the indication of the priority of the channel or reference signal is carried in one of the following:

downlink control information (DCI) associated with the channel or reference signal;

a medium access control (MAC) control element (CE) associated with the channel or reference signal; or

a radio resource control (RRC) configuration associated with the channel or reference signal.
The UE of claim 10, wherein the processor is further configured to:

determine the priority of the channel or reference signal based on a resource for the channel or reference signal in at least one of the following: a time domain, a frequency domain or a code domain.
A network entity, comprising:

a processor; and

a transceiver coupled to the processor,

wherein the processor is configured to:

transmit, to a user equipment (UE) via the transceiver, information associated with at least one on-duration window, wherein the at least one on-duration window is associated with at least one of the following: downlink transmission, downlink reception, uplink transmission, or uplink reception; and

perform communication with the UE based on the at least one on-duration window.
The network entity of claim 17, wherein a time domain resource for a channel or reference signal is out of an on-duration window associated with the channel or reference signal, and the processor is further configured to:

determine whether to receive or transmit the channel or reference signal on the time domain resource or not based on a priority of the channel or reference signal.
A processor for wireless communication, comprising:

at least one memory; and

a controller coupled with the at least one memory and configured to cause the controller to:

receive, from a network entity, information associated with at least one on-duration window, wherein the at least one on-duration window is associated with at least one of the following: downlink transmission, downlink reception, uplink transmission, or uplink reception; and

perform communication with the network entity based on the at least one on-duration window.
A method performed by a user equipment, the method comprising:

receiving, from a network entity, information associated with at least one on-duration window, wherein the at least one on-duration window is associated with at least one of the following: downlink transmission, downlink reception, uplink transmission, or uplink reception; and

performing communication with the network entity based on the at least one on-duration window.