WO2024182986A1 - Procédures de rétroaction pour agrégation d'équipement utilisateur - Google Patents

Procédures de rétroaction pour agrégation d'équipement utilisateur Download PDF

Info

Publication number
WO2024182986A1
WO2024182986A1 PCT/CN2023/079979 CN2023079979W WO2024182986A1 WO 2024182986 A1 WO2024182986 A1 WO 2024182986A1 CN 2023079979 W CN2023079979 W CN 2023079979W WO 2024182986 A1 WO2024182986 A1 WO 2024182986A1
Authority
WO
WIPO (PCT)
Prior art keywords
feedback
downlink transmission
aggregated downlink
status
resource
Prior art date
Application number
PCT/CN2023/079979
Other languages
English (en)
Inventor
Hui Guo
Shuanshuan Wu
Tien Viet NGUYEN
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2023/079979 priority Critical patent/WO2024182986A1/fr
Publication of WO2024182986A1 publication Critical patent/WO2024182986A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated

Definitions

  • the following relates to wireless communications, including feedback procedures for user equipment aggregation.
  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) .
  • Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems.
  • 4G systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems
  • 5G systems which may be referred to as New Radio (NR) systems.
  • a wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .
  • UE user equipment
  • the described techniques relate to improved methods, systems, devices, and apparatuses that support feedback procedures for user equipment (UE) aggregation.
  • the described techniques provide for improved feedback reporting techniques for aggregated wireless communications.
  • a network entity may transmit a grant to a first UE and a second UE that are associated with each other.
  • the grant may schedule or allocate an aggregated downlink transmission to the first UE and the second UE.
  • the network entity may configure the grant to carry or otherwise convey an indication of a feedback mode for the aggregated downlink transmission as well as identifying a set of feedback resources.
  • the first UE (and second UE) may monitor for the aggregated downlink transmission according to the grant to attempt to receive and decode the aggregated downlink transmission.
  • the first UE may identify the feedback status for the aggregated downlink transmission, e.g., an acknowledgement (ACK) feedback status when the transmission is successfully received and decoded or a negative-acknowledgement (NACK) feedback status when the transmission is unable to be successfully received and decoded.
  • the first UE and the second UE may each select feedback resources from the set of feedback resources to use for transmitting a feedback message indicating the feedback status.
  • the set of feedback resources may be divided into separate resources for each of the first UE and the second UE.
  • the set of feedback resources may be divided into separate resources for ACK feedback status (es) and for NACK feedback status (es) . Accordingly, the network entity may monitor the resources in the set of feedback resources and retransmit the aggregated downlink transmission based on the indicated feedback status (es) .
  • FIG. 1 illustrates an example of a wireless communications system that supports feedback procedures for user equipment (UE) aggregation in accordance with one or more aspects of the present disclosure.
  • UE user equipment
  • FIG. 2 illustrates an example of a wireless communications system that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • FIG. 3 illustrates an example of a method that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • FIG. 4 illustrates an example of a process that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • FIGs. 5 and 6 illustrate block diagrams of devices that support feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • FIG. 7 illustrates a block diagram of a communications manager that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • FIG. 8 illustrates a diagram of a system including a device that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • FIGs. 9 and 10 illustrate block diagrams of devices that support feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • FIG. 11 illustrates a block diagram of a communications manager that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • FIG. 12 illustrates a diagram of a system including a device that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • FIGs. 13 through 17 illustrate flowcharts showing methods that support feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • Wireless networks may rely on feedback reporting to confirm successful reception and decoding of a message or to trigger a retransmission of the message.
  • the feedback reporting may include the transmitting device scheduling the message transmission to the receiving device using a grant that identifies the resources the receiving device is to receive the message on as well as the feedback resources to provide the feedback reporting.
  • Feedback reporting for multicast or broadcast transmissions may rely on a similar technique, even when the transmitting device is unaware of which, if any, receiving devices are attempting to receive the message.
  • aggregated message transmissions may be employed where the message is transmitted in an aggregated manner to multiple user equipment (UE) that are associated with each other.
  • UE user equipment
  • a vehicle may include its own wireless device (e.g., a vehicle UE (VUE) ) as well as the wireless devices (e.g., UE (s) ) of the passengers inside the vehicle.
  • VUE vehicle UE
  • UE UE
  • the message may be transmitted to the associated UE, which may, in some examples, rely on relaying operations to exchange the message.
  • Feedback reporting for the message may be problematic because the transmission may be considered successful when at least one of the UEs is able to successfully receive and decode the message.
  • the described techniques relate to improved methods, systems, devices, and apparatuses that support feedback procedures for UE aggregation.
  • the described techniques provide for improved feedback reporting techniques for aggregated wireless communications.
  • a network entity may transmit a grant to a first UE and a second UE that are associated with each other.
  • the grant may schedule or allocate an aggregated downlink transmission to the first UE and the second UE.
  • the network entity may configure the grant to carry or otherwise convey an indication of a feedback mode for the aggregated downlink transmission as well as identifying a set of feedback resources.
  • the first UE (and second UE) may monitor for the aggregated downlink transmission according to the grant to attempt to receive and decode the aggregated downlink transmission.
  • the first UE may identify the feedback status for the aggregated downlink transmission, e.g., an acknowledgement (ACK) feedback status when the transmission is successfully received and decoded or a negative-acknowledgement (NACK) feedback status when the transmission is unable to be successfully received and decoded.
  • the first UE and the second UE may each select feedback resources from the set of feedback resources to use for transmitting a feedback message indicating the feedback status.
  • the set of feedback resources may be divided into separate resources for each of the first UE and the second UE.
  • the set of feedback resources may be divided into separate resources for ACK feedback status (es) and for NACK feedback status (es) . Accordingly, the network entity may monitor the resources in the set of feedback resources and retransmit the aggregated downlink transmission based on the indicated feedback status (es) .
  • aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to feedback procedures for UE aggregation.
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • the wireless communications system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130.
  • the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-A Pro
  • NR New Radio
  • the network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities.
  • a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature.
  • network entities 105 and UEs 115 may wirelessly communicate via one or more communication links 125 (e.g., a radio frequency (RF) access link) .
  • a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish one or more communication links 125.
  • the coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .
  • RATs radio access technologies
  • the UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times.
  • the UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1.
  • the UEs 115 described herein may be capable of supporting communications with various types of devices, such as other UEs 115 or network entities 105, as shown in FIG. 1.
  • a node of the wireless communications system 100 which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein) , a UE 115 (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein.
  • a node may be a UE 115.
  • a node may be a network entity 105.
  • a first node may be configured to communicate with a second node or a third node.
  • the first node may be a UE 115
  • the second node may be a network entity 105
  • the third node may be a UE 115.
  • the first node may be a UE 115
  • the second node may be a network entity 105
  • the third node may be a network entity 105.
  • the first, second, and third nodes may be different relative to these examples.
  • reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node.
  • disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.
  • network entities 105 may communicate with the core network 130, or with one another, or both.
  • network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) .
  • network entities 105 may communicate with one another via a backhaul communication link 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via a core network 130) .
  • network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof.
  • the backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) , one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof.
  • a UE 115 may communicate with the core network 130 via a communication link 155.
  • One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) .
  • a base station 140 e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or a giga-NodeB (either of which may be
  • a network entity 105 may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140) .
  • a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (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) ) .
  • IAB integrated access backhaul
  • O-RAN open RAN
  • vRAN virtualized RAN
  • C-RAN cloud RAN
  • a network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) 180 system, or any combination thereof.
  • An RU 170 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 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) .
  • one or more network entities 105 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) ) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • the split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combinations thereof
  • a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack.
  • the CU 160 may host upper protocol layer (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) .
  • the CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or 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.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access control (MAC) layer
  • a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack.
  • the DU 165 may support one or multiple different cells (e.g., via one or more RUs 170) .
  • a functional split between a CU 160 and a DU 165, or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) .
  • a CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
  • CU-CP CU control plane
  • CU-UP CU user plane
  • a CU 160 may be connected to one or more DUs 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) .
  • a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that are in communication via such communication links.
  • infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130) .
  • IAB network one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other.
  • One or more IAB nodes 104 may be referred to as a donor entity or an IAB donor.
  • One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140) .
  • the one or more donor network entities 105 may be in communication with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120) .
  • IAB nodes 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by DUs 165 of a coupled IAB donor.
  • IAB-MT IAB mobile termination
  • An IAB-MT may include an independent set of antennas for relay of communications with UEs 115, or may share the same antennas (e.g., of an RU 170) of an IAB node 104 used for access via the DU 165 of the IAB node 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) .
  • the IAB nodes 104 may include DUs 165 that support communication links with additional entities (e.g., IAB nodes 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) .
  • one or more components of the disaggregated RAN architecture e.g., one or more IAB nodes 104 or components of IAB nodes 104) may be configured to operate according to the techniques described herein.
  • an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor) , IAB nodes 104, and one or more UEs 115.
  • the IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130) . That is, an IAB donor may refer to a RAN node with a wired or wireless connection to core network 130.
  • the IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170) , in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link) .
  • IAB donor and IAB nodes 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol) .
  • the CU 160 may communicate with the core network via an interface, which may be an example of a portion of backhaul link, and may communicate with other CUs 160 (e.g., a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of a portion of a backhaul link.
  • An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities) .
  • a DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with the IAB node 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through one or more other IAB nodes 104) .
  • an IAB node 104 may also be referred to as a parent node or a child node to other IAB nodes 104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of IAB nodes 104 may provide a Uu interface for a child IAB node 104 to receive signaling from a parent IAB node 104, and the DU interface (e.g., DUs 165) may provide a Uu interface for a parent IAB node 104 to signal to a child IAB node 104 or UE 115.
  • the DU interface e.g., DUs 165
  • IAB node 104 may be referred to as a parent node that supports communications for a child IAB node, or referred to as a child IAB node associated with an IAB donor, or both.
  • the IAB donor may include a CU 160 with a wired or wireless connection (e.g., a backhaul communication link 120) to the core network 130 and may act as parent node to IAB nodes 104.
  • the DU 165 of IAB donor may relay transmissions to UEs 115 through IAB nodes 104, or may directly signal transmissions to a UE 115, or both.
  • the CU 160 of IAB donor may signal communication link establishment via an F1 interface to IAB nodes 104, and the IAB nodes 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through the DUs 165. That is, data may be relayed to and from IAB nodes 104 via signaling via an NR Uu interface to MT of the IAB node 104. Communications with IAB node 104 may be scheduled by a DU 165 of IAB donor and communications with IAB node 104 may be scheduled by DU 165 of IAB node 104.
  • one or more components of the disaggregated RAN architecture may be configured to support feedback procedures for UE aggregation as described herein.
  • some operations described as being performed by a UE 115 or a network entity 105 may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 180) .
  • a UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples.
  • a UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer.
  • PDA personal digital assistant
  • a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.
  • WLL wireless local loop
  • IoT Internet of Things
  • IoE Internet of Everything
  • MTC machine type communications
  • the UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as relays as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • devices such as other UEs 115 that may sometimes act as relays as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • the UEs 115 and the network entities 105 may wirelessly communicate with one another via one or more communication links 125 (e.g., an access link) using resources associated with one or more carriers.
  • the term “carrier” may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication links 125.
  • a carrier used for a communication link 125 may include a portion of a RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR) .
  • BWP bandwidth part
  • Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling.
  • the wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation.
  • a UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration.
  • Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.
  • Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105.
  • the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105 may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105) .
  • a network entity 105 e.g., a base station 140, a CU 160, a DU 165, a RU 170
  • a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers.
  • a carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN) ) and may be identified according to a channel raster for discovery by the UEs 115.
  • E-UTRA evolved universal mobile telecommunication system terrestrial radio access
  • a carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different radio access technology) .
  • the communication links 125 shown in the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions.
  • Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
  • a carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100.
  • the carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) .
  • Devices of the wireless communications system 100 e.g., the network entities 105, the UEs 115, or both
  • the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths.
  • each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
  • Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) .
  • MCM multi-carrier modulation
  • OFDM orthogonal frequency division multiplexing
  • DFT-S-OFDM discrete Fourier transform spread OFDM
  • a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related.
  • the quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication.
  • a wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.
  • One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing ( ⁇ f) and a cyclic prefix.
  • a carrier may be divided into one or more BWPs having the same or different numerologies.
  • a UE 115 may be configured with multiple BWPs.
  • a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
  • Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) .
  • Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .
  • SFN system frame number
  • Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration.
  • a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots.
  • each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing.
  • Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) .
  • a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f ) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
  • a subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) .
  • TTI duration e.g., a quantity of symbol periods in a TTI
  • the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
  • Physical channels may be multiplexed for communication using a carrier according to various techniques.
  • a physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.
  • a control region e.g., a control resource set (CORESET)
  • CORESET control resource set
  • One or more control regions may be configured for a set of the UEs 115.
  • one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner.
  • An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size.
  • Search space sets may include common search space sets configured for sending control information to multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.
  • a network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof.
  • the term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) , or others) .
  • a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates.
  • Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105.
  • a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.
  • a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell.
  • a small cell may be associated with a lower-powered network entity 105 (e.g., a lower-powered base station 140) , as compared with a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells.
  • Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) .
  • a network entity 105 may support one or multiple cells and may also support communications via the one or more cells using one or multiple component carriers.
  • a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB) ) that may provide access for different types of devices.
  • protocol types e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB)
  • NB-IoT narrowband IoT
  • eMBB enhanced mobile broadband
  • a network entity 105 may be movable and therefore provide communication coverage for a moving coverage area 110.
  • different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105.
  • the overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105.
  • the wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.
  • the wireless communications system 100 may support synchronous or asynchronous operation.
  • network entities 105 e.g., base stations 140
  • network entities 105 may have different frame timings, and transmissions from different network entities 105 may, in some examples, not be aligned in time.
  • the techniques described herein may be used for either synchronous or asynchronous operations.
  • Some UEs 115 may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) .
  • M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention.
  • M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program.
  • Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
  • Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently) .
  • half-duplex communications may be performed at a reduced peak rate.
  • Other power conservation techniques for the UEs 115 include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications) , or a combination of these techniques.
  • some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
  • a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
  • the wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof.
  • the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) .
  • the UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions.
  • Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data.
  • Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications.
  • the terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
  • a UE 115 may be configured to support communicating directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., in accordance with a peer-to-peer (P2P) , D2D, or sidelink protocol) .
  • D2D device-to-device
  • P2P peer-to-peer
  • one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105.
  • one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105.
  • groups of the UEs 115 communicating via D2D communications may support a one-to-many (1: M) system in which each UE 115 transmits to each of the other UEs 115 in the group.
  • a network entity 105 may facilitate the scheduling of resources for D2D communications.
  • D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.
  • a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115) .
  • vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these.
  • V2X vehicle-to-everything
  • V2V vehicle-to-vehicle
  • a vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system.
  • vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to-network (V2N) communications, or with both.
  • roadside infrastructure such as roadside units
  • network nodes e.g., network entities 105, base stations 140, RUs 170
  • V2N vehicle-to-network
  • the core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions.
  • the core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one 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) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management function
  • S-GW serving gateway
  • PDN Packet Data Network gateway
  • UPF user plane function
  • the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130.
  • NAS non-access stratum
  • User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions.
  • the user plane entity may be connected to IP services 150 for one or more network operators.
  • the IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
  • IMS IP Multimedia Subsystem
  • the wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) .
  • the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length.
  • UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
  • HF high frequency
  • VHF very high frequency
  • the wireless communications system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) , also known as the millimeter band.
  • SHF super high frequency
  • EHF extremely high frequency
  • the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170) , and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas.
  • mmW millimeter wave
  • such techniques may facilitate using antenna arrays within a device.
  • EHF transmissions may be subject to even greater attenuation and shorter range than SHF or UHF transmissions.
  • the techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.
  • the wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands.
  • the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) radio access technology, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • LAA License Assisted Access
  • LTE-U LTE-Unlicensed
  • NR NR technology
  • an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance.
  • operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA) .
  • Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
  • a network entity 105 e.g., a base station 140, an RU 170
  • a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming.
  • the antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming.
  • one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower.
  • antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations.
  • a network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115.
  • a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations.
  • an antenna panel may support RF beamforming for a signal transmitted via an antenna port.
  • the network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers.
  • Such techniques may be referred to as spatial multiplexing.
  • the multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas.
  • Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords) .
  • Different spatial layers may be associated with different antenna ports used for channel measurement and reporting.
  • MIMO techniques include single-user MIMO (SU-MIMO) , for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) , for which multiple spatial layers are transmitted to multiple devices.
  • SU-MIMO single-user MIMO
  • Beamforming which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device.
  • Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference.
  • the adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device.
  • the adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
  • a network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations.
  • a network entity 105 e.g., a base station 140, an RU 170
  • Some signals e.g., synchronization signals, reference signals, beam selection signals, or other control signals
  • the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission.
  • Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.
  • a transmitting device such as a network entity 105
  • a receiving device such as a UE 115
  • Some signals may be transmitted by transmitting device (e.g., a transmitting network entity 105, a transmitting UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as a receiving network entity 105 or a receiving UE 115) .
  • a single beam direction e.g., a direction associated with the receiving device, such as a receiving network entity 105 or a receiving UE 115
  • the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions.
  • a UE 115 may receive one or more of the signals transmitted by the network entity 105 along different directions and may report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.
  • transmissions by a device may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115) .
  • the UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands.
  • the network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS) ) , which may be precoded or unprecoded.
  • a reference signal e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS)
  • the UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook) .
  • PMI precoding matrix indicator
  • codebook-based feedback e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook
  • these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170)
  • a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device) .
  • a receiving device may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a receiving device (e.g., a network entity 105) , such as synchronization signals, reference signals, beam selection signals, or other control signals.
  • a receiving device e.g., a network entity 105
  • signals such as synchronization signals, reference signals, beam selection signals, or other control signals.
  • a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions.
  • a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal) .
  • the single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions) .
  • receive configuration directions e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions
  • the wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack.
  • communications at the bearer or PDCP layer may be IP-based.
  • An RLC layer may perform packet segmentation and reassembly to communicate via logical channels.
  • a MAC layer may perform priority handling and multiplexing of logical channels into transport channels.
  • the MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency.
  • an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data.
  • a PHY layer may map transport channels to physical channels.
  • the UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully.
  • Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., a communication link 125, a D2D communication link 135) .
  • HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) .
  • FEC forward error correction
  • ARQ automatic repeat request
  • HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions) .
  • a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
  • a UE 115 may receive a grant scheduling an aggregated downlink transmission to the first UE and a second UE (e.g., a different, but associated other UE 115) that is associated with the first UE, the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources.
  • the UE 115 may monitor for the aggregated downlink transmission based at least in part on the grant.
  • the UE 115 may select, based at least in part on the feedback mode, a feedback resource from the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission based on a result of the monitoring.
  • a network entity 105 may transmit a grant scheduling an aggregated downlink transmission to a first UE (e.g., a UE 115) and a second UE (e.g., a different, but associated other UE 115) , the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources.
  • the network entity 105 may transmit the aggregated downlink transmission to the first UE and the second UE according to the grant.
  • the network entity 105 may monitor the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission.
  • FIG. 2 illustrates an example of a wireless communications system 200 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • Wireless communications system 200 may implement aspects of wireless communications system 100.
  • Wireless communications system 200 may include a UE 205, a UE 210, and/or a network entity 215, which may be examples of the corresponding devices described herein.
  • Wireless communications system 200 may support UE aggregation where multiple UEs are coordinated in their communications with the network.
  • UE aggregation is in automobiles.
  • a vehicle may have a UE (the V-UE) that is used for traditional wireless communications (e.g., via a Uu interface) as well as for sidelink communications (e.g., via a PC5 interface) .
  • the vehicle may also have one or more UEs carried by occupants inside. These UEs may be considered aggregated in that they coordinate with each other as well as with the network to improve wireless communications.
  • the V-UE antenna may be mounted on the rooftop of the vehicle, which has reduced pathloss (e.g., compared to the UE inside the vehicle) and better channel quality.
  • the V-UE is generally not power- limited (e.g., connected to the vehicle power) .
  • the V-UE may help the passenger’s UE carried inside the vehicle to improve wireless communications.
  • the V-UE may suffer from performance degradation in some instances (e.g., high heat) , which may mean the UE inside the vehicle helps the V-UE improve communications with the network.
  • the received signal may be forwarded from one UE (a relay UE) to another (a remote UE) .
  • inter-UE forwarding e.g., relaying
  • Such inter-UE forwarding may include layer one (L1) forwarding where the aggregated downlink signal is simply amplified and relayed, layer two (L2) forwarding where the aggregated downlink signal is partially decoded and relayed, and/or layer three (L3) forwarding where the aggregated downlink signal is fully decoded, processed, and regenerated for relaying to the other UE.
  • one example of such relaying operations may include multicast aggregation with L2 relay where the network (e.g., the network entity 215) multicasts a transport block (TB) to both UEs (e.g., the V-UE and passenger UE (s) ) .
  • the network e.g., the network entity 215
  • UEs e.g., the V-UE and passenger UE (s)
  • This approach may, when compared to traditional downlink relaying operations, include the radio resources and UE processing latency being conserved, conservation of the downlink transmission resources, and more.
  • the V-UE e.g., the relay node in this example, such as the UE 205
  • an associated (e.g., aggregated) UE e.g., the remote UE, such as the UE 210) if the UE is unable to successfully receive and decode the TB.
  • Another example of such relaying operations may include multicast aggregation with log-likelihood ratio (LLR) sharing where L2 relaying, but without decoding, is performed.
  • the network entity 215 may multicast the TB to both UEs (e.g., to the aggregated or otherwise associated UEs) .
  • the relay UE e.g., the UE 205
  • the remote UE may send the LLR information to the remote UE (e.g., the UE 210, in this example) instead of relaying the TB.
  • the remote UE may perform chase combing or incremental combing in the decoding phase using the LLR information.
  • Yet another option of such relaying operations may include may include multicast aggregation with in-phase/quadrature (I/Q) sample sharing (e.g., L1 relaying with signal compression) .
  • the network entity 215 may multicast the TB to both UE (e.g., the UE 205 and the UE 210) .
  • the relaying UE may send the I/Q samples to the remote UE and the remote UE may perform maximum ratio combining (MRC) combining.
  • MRC maximum ratio combining
  • the UEs may share the same radio network temporary identifier (RNTI) to receive the aggregated downlink transmission.
  • RNTI radio network temporary identifier
  • This may be either a dedicated RNTI for UE aggregation, or the remote UE shares its RNTI with relaying UE to support aggregated downlink communications.
  • the downlink aggregated communications may be considered successful when at least one of the UEs is able to successfully receive and decode the transmission.
  • the remote UE may be able to successfully receive and decode the transmission, resulting in no retransmission and no relaying being needed.
  • the remote UE may not be able to successfully receive and decode the transmission, but the relay UE may be able to. This may result in no retransmission being needed, but relaying operations being performed between the UEs.
  • neither the relaying UE nor the remote UE may be able to successfully receive and decode the aggregated downlink transmission. In this situation, retransmission of the aggregated downlink transmission may be needed.
  • wireless communications system 200 may relay on hybrid automatic repeat/request (HARQ) techniques.
  • the HARQ techniques may include the grant scheduling a downlink transmission to a UE indicating the HARQ resources to be used for HARQ feedback, as well as the timeline for such HARQ feedback.
  • HARQ techniques may include the UE sending HARQ feedback to the network using the indicated resources that indicates the results of its attempt to receive and decode the transmission.
  • the UE may send an ACK feedback status indication when the UE is able to successfully receive and decode the transmission or send a NACK feedback status indication when the UE is unable to successfully receive and decode the transmission.
  • the network receiving an ACK indication may not retransmit the signal, where the network receiving a NACK (or no HARQ feedback at all) may retransmit the signal to the UE.
  • HARQ techniques are generally not defined for aggregated downlink transmissions.
  • One approach may be that for UE aggregation the UEs may coordinate their HARQ feedback transmission based on the results of both UEs decoding outcomes (e.g., they exchange their decoding outcome before sending HARQ feedback) .
  • HARQ feedback timelines are rather short in some situations (e.g., intra-slot HARQ feedback) , which may mean that relaying operations between aggregated UEs may not be able to be performed within the HARQ timeline. That is, there may not be sufficient time for the aggregated UEs to coordinate the results of their decoding outcomes before the HARQ feedback is to be sent.
  • aspects of the techniques described herein provide various mechanisms to support HARQ feedback for downlink UE aggregation.
  • the described techniques improve gains associated with downlink UE aggregation. This may include both (or all) UEs having a HARQ resource for their respective HARQ feedback transmission. This may enable the network entity 215 to determine retransmission needs based on the received HARQ feedback from each UE, which may avoid unnecessary retransmissions. In some examples, this may include the UEs receiving an aggregated downlink transmission (e.g., aggregated physical downlink shared channel (PDSCH) transmission) not coordinating their HARQ feedback (e.g., in view of the HARQ feedback timeline) .
  • aggregated downlink transmission e.g., aggregated physical downlink shared channel (PDSCH) transmission
  • PDSCH physical downlink shared channel
  • the UE 205 (a first UE, in this example) and the UE 210 (a second UE, in this example) may be associated, such as UE participating in an aggregated downlink transmission. More than two UE may be associated with each other for an aggregated downlink transmission.
  • aggregated downlink communications include the vehicle-based example, the techniques described herein are not limited to the vehicle-based example.
  • UE participating in aggregated downlink transmissions may be aggregated based on other examples, such as within a factory setting, a traditional UE carried by a user as well as corresponding wireless devices (e.g., smartwatches, tablets, IoT devices, or any other smart devices, and more) of the user.
  • the UE 205 and the UE 210 may coordinate with each other to support aggregated downlink communications.
  • the UE 205 and the UE 210 may exchange various message (s) carrying or otherwise conveying information associated with respective UE capabilities, processing times, relaying operations, and more.
  • the UE 205 and the UE 210 may measure or otherwise monitor the conditions of the wireless channel between each UE in order to determine whether relaying operations are supported, as well to determine allocation and/or configuration parameters to be used for such relaying operations.
  • the UE 205 and the UE 210 may exchange supported HARQ processing and response timing information, such as information identifying the time that it takes each UE to receive and successfully decode an aggregated downlink transmission, the time it takes to determine the HARQ feedback status (e.g., ACK or NACK) for the aggregated downlink transmission, and then to prepare the HARQ feedback message indicating the HARQ feedback status.
  • the UE 205 and the UE 210 may communicate with each other via a cellular interface (e.g., a Uu interface) and/or a sidelink interface (e.g., a PC5 interface) .
  • the UE 205 and/or the UE 210 may communicate with the network entity 215 via a cellular interface (e.g., a Uu interface) and/or a sidelink interface (e.g., a PC5 interface) .
  • the network entity 215 may transmit or otherwise provide (and the UE 205 and the UE 210 may receive or otherwise obtain) a grant 220.
  • the grant 220 may schedule an aggregated downlink transmission 225 (e.g., an aggregated PDSCH transmission) to the UE 205 (e.g., the first UE, in this example) and to the UE 210 (e.g., the second UE, in this example) .
  • the grant 220 may carry or otherwise convey information identifying the resources (e.g., time, frequency, spatial, and/or code resources) to be used for the aggregated downlink transmission 225 as well as various parameters to be used for the aggregated downlink transmission 225 (e.g., coding scheme, beam information, and more) .
  • the grant 220 may indicate a feedback mode associated with the aggregated downlink transmission 225.
  • the grant 220 may indicate a set of feedback resources to be used for transmitting a feedback message (e.g., HARQ feedback) indicating the feedback status (e.g., ACK or NACK) of the aggregated downlink transmission 225.
  • the feedback mode may carry or otherwise convey an indication of how the resources in the set of resources to be used for the feedback message are to be used (e.g., how the feedback resources in the set are to be used) .
  • the grant 220 may be a dynamic grant identifying dynamically allocated resources for the aggregated downlink transmission 225.
  • the grant 220 may be a semi- persistent grant activating (pre) configured resources for the aggregated downlink transmission 225.
  • the grant 220 may be transmitted or otherwise conveyed in a downlink control information (DCI) and/or in a medium access control-control element (MAC-CE) .
  • the grant 220 may be transmitted or otherwise conveyed in an uplink control information (UCI) .
  • the grant 220 may be transmitted or otherwise conveyed in a physical downlink control channel (PDCCH) .
  • the grant 220 may be transmitted or otherwise conveyed in a physical sidelink control channel (PSCCH) and/or physical sidelink shared channel (PSSCH) .
  • DCI downlink control information
  • MAC-CE medium access control-control element
  • UCI uplink control information
  • PDCCH physical downlink control channel
  • PSSCH physical sidelink shared channel
  • the network entity 215 may transmit or otherwise provide (and the UE 205 and the UE 210 may monitor for to receive or otherwise obtain) the aggregated downlink transmission 225 according to the grant 220.
  • the aggregated downlink transmission 225 may be transmitted using the resources identified in the grant 220 as well as according to the parameters indicated in the grant 220.
  • the UE 205 and the UE 210 may each monitor for the aggregated downlink transmission 225 based on the grant 220.
  • the UE 205 and the UE 210 may monitor the frequency, spatial and/or code resources indicated in the grant 220 according to the time resources (e.g., when) indicated grant 220.
  • the UE 205 and the UE 210 may identify or otherwise determine a feedback status for the aggregated downlink transmission 225 based on the monitoring.
  • An ACK feedback status may be determined for the aggregated downlink transmission 225 if the UE 205 and/or the UE 210 are able to successfully receive and decode the aggregated downlink transmission 225.
  • a NACK feedback status may be determined for the aggregated downlink transmission 225 if the UE 205 and/or the UE 210 are unable to successfully receive and decode the aggregated downlink transmission 225.
  • the feedback status for the aggregated downlink transmission 225 determined by the UE 205 may be the same as, or different from the feedback status for the aggregated downlink transmission 225 determined by the UE 210.
  • Determination of the HARQ feedback status for the aggregated downlink transmission 225 may be performed autonomously by each of the UE 205 and the UE 210. This may include the UE 205 and the UE 210 identifying or otherwise determining their respective feedback status based on the results of monitoring for the aggregated downlink transmission 225. In this aspect, both the relay UE and the remote UE may determine their ACK/NACK based on their own decoding outcome.
  • Determination of the HARQ feedback status for the aggregated downlink transmission 225 may be based on whether one UE can deliver (e.g., relay) the decoded packet to the other UE “on time” (e.g., within a feedback delay reporting threshold) .
  • the UE 205 (the first UE, which is the relay UE in this example) and the UE 210 (the second UE, which is the remote UE in this example) may each determine their respective feedback status autonomously, as discussed above.
  • the relay UE may additionally determine its feedback status based on whether it can deliver the decoded packet (e.g., packet (s) carrying the TB conveyed in the aggregated downlink transmission 225) to the remote UE (the UE 210 in this example) within the feedback delay reporting threshold.
  • the UE 205 may determine that the feedback status for the aggregated downlink transmission 225 is an ACK feedback status (e.g., the UE 205 has successfully received and decoded the aggregated downlink transmission 225) .
  • This may include the UE 205 identifying or otherwise determining a delay time associated with relaying the aggregated downlink transmission 225 to the UE 210, or vice versa.
  • the delay time may generally define the time it would take the UE 205 to prepare and transmit the aggregated downlink transmission 225 to the UE 210.
  • the previously discussed information exchanged between the UE 205 and the UE 210 may identify, for each of the UE 205 and the UE 210, the delay time associated with relaying the aggregated downlink transmission 225 to the other UE.
  • the delay time may be based on the UE 205 comparing the delay time to the feedback delay reporting threshold to determine its feedback status, even when it has successfully received and decoded the aggregated downlink transmission 225. This may include the UE 205 assessing whether it can transmit the decoded packet to the UE 210 such that the packet arrives “on time” (e.g., the delay time satisfies the feedback reporting threshold) by the UE 210 (e.g., before the HARQ reporting timeline expires) .
  • the UE 205 may transmit a NACK feedback status in the HARQ feedback message 230 to the network entity 215. This may include the UE 205 transmitting its HARQ feedback message 230 indicating a NACK feedback status even if the UE 205 was able to successfully receive and decode the aggregated downlink transmission 225 (e.g., has an ACK feedback status) . This may trigger retransmission of the aggregated downlink transmission 225 by the UE 210.
  • the delay time may be based on a feedback reporting timer associated with the aggregated downlink transmission 225. This may include a timer (e.g., in x milliseconds and/or in N symbols and/or N slots) being defined for the aggregated downlink transmission 225 such that the network entity 215 does not wait too long for the HARQ feedback messages before triggering a retransmission.
  • the delay time may be based on the UE 205 determining whether it is able to relay the packet to the UE 210 before expiration of the timer (e.g., the delay time satisfies the feedback delay reporting threshold if so) .
  • the delay time may be based on message (s) exchanged between the UE 205 and the UE 210, such as discussed above. This may include the UE 205 and/or the UE 210 exchanging message (s) indicating a delay budget.
  • the delay budget may indicate an amount of time that the reporting UE has between when it expects to determine its feedback status for the aggregated downlink transmission 225 and transmit the associated HARQ feedback message.
  • the UE 205 determining that it can relay the packet to the UE 210 within the delay budget may indicate that the delay time satisfies the feedback delay reporting threshold.
  • the delay time may be based on the HARQ reporting timeline indicated in the grant 220 (e.g., explicitly indicated in the grant 220) .
  • the grant 220 may indicate the HARQ reporting timeline for the aggregated downlink transmission 225.
  • the grant 220 may indicate a timer value and/or packet delay budget.
  • the HARQ reporting timeline may define the feedback delay reporting threshold.
  • the UE 205 may compare the time it would take to forward the packet to the UE 210 to determine whether the delay time satisfies the feedback delay reporting threshold. If the UE 205 determines it is able to relay the packet to the UE 210 within the HARQ reporting timeline, this may indicate that the delay time satisfies the feedback reporting threshold.
  • the UE 205 may determine its feedback status based on the results of its own decoding attempts for the aggregated downlink transmission 225 as well as based on whether it can relay the aggregated downlink transmission 225 to the UE 210 “on time. ”
  • the UE 205 may transmit the HARQ feedback message 230 to the UE 210 indicating a NACK feedback status. This may trigger retransmission of the aggregated downlink transmission 225 by the network entity 215.
  • the UE 205 may refrain from relaying the aggregated downlink transmission 225 to the UE 210 when the delay time fails to satisfy the feedback delay reporting threshold.
  • the relaying may be performed via a cellular interface, a sidelink interface, a Wi-Fi interface, and/or a proprietary interface.
  • the grant 220 may carry or otherwise convey an indication (e.g., using bit(s) , field (s) , flag (s) , information element (s) (IE) (s) , and the like) of whether relaying operations are to be performed (e.g., the PDSCH feedback mode may be indicated when the sidelink relaying is to be performed) .
  • This may include the grant 220 indicating an “ACK only” feedback mode where if either the UE 205 or the UE 210 are able to successfully receive and decode the aggregated downlink transmission 225 (e.g., transmits an ACK feedback status) , then the aggregated downlink transmission 225 is considered successful and no retransmission is triggered.
  • the UE 205 and/or the UE 210 may identify or otherwise select a feedback resource from the set of feedback resources available to use for transmitting its HARQ feedback message.
  • the UE 205 may select a first feedback resource from the set of feedback resources to use to transmit its HARQ feedback message 230 and the UE 210 may select a second feedback resource from the set of resources to use to transmit its HARQ feedback message 235.
  • the UE 205 may transmit its HARQ feedback message 230 using the first feedback resource and the UE 210 may transmit its HARQ feedback message 235 using the second feedback resource.
  • the HARQ feedback message 230 and/or the HARQ feedback message 235 may be transmitted based on the associated feedback status.
  • This may include a NACK-only feedback mode where the HARQ feedback message (s) is (are) transmitted when the feedback status is NACK for the aggregated downlink transmission 225. This may include the UE 205 and/or the UE 210 refraining from transmitting their respective HARQ feedback message (s) when the feedback status is ACK for the aggregated downlink transmission 225. This may include an ACK-only feedback mode where the UE 205 and/or the UE 210 transmit feedback messages when the feedback status for the aggregated downlink transmission 225 is ACK. This may include an ACK/NACK feedback mode where the HARQ feedback messages are transmitted for both ACK and NACK feedback statuses for the aggregated downlink transmission 225. This may include the mode discussed above where the UE 205 transmits an indication of its feedback status, where its feedback status is based on whether it can relay the aggregated downlink transmission 225 to the UE 210 “on time. ”
  • the feedback mode may identify aspects of selection of the feedback resource from the set of feedback resources identified in the grant 220 by the UE 205 and/or the UE 210.
  • the feedback mode may identify how the feedback resources in the set of feedback resources are divided or otherwise allocated to support HARQ feedback operations by the UE 205 and the UE 210 for the aggregated downlink transmission 225.
  • One example may include at least two HARQ feedback resources in the set of feedback resources being configured for the aggregated downlink transmission 225 on a per-UE basis. This may include a first set of feedback resources being configured for the UE 205 and a second set of feedback resources for the UE 210. Each UE may transmit their HARQ feedback message on their respective HARQ feedback resources. For example, the UE 205 may transmit the HARQ feedback message 230 on the first feedback resource from the set of feedback resources and the UE 210 may transmit the HARQ feedback message 235 on the second feedback resource from the set of feedback resources.
  • the first feedback resource and the second feedback resource may be in the same slot or in different slots.
  • This example may include separate HARQ feedback resources for the two UEs.
  • the UE 210 may configure different feedback resources for the UE 205 and the UE 210.
  • the two HARQ feedback resources may be in the same slot (e.g., the HARQ feedback timeline indicated in the grant 220 for the two UEs is the same.
  • the two HARQ feedback resources can be in different slots (e.g., separate HARQ feedback timelines for the two UEs may be configured, such as in the grant 220) .
  • the network entity 215 may indicate the timeline to the two UEs (e.g., the timeline indication in DCI may indicates two timing values, one for each UE) .
  • the two different resources can be different resources in the time domain, the frequency domain, and/or the code domain.
  • the network entity 215 may determine the feedback to be NACK if no ACK is received, otherwise the network entity 215 may determine the feedback to be ACK.
  • the UE 210 may retransmit the TB or CBG (e.g., the aggregated downlink transmission 225) if a NACK feedback status is determined.
  • Each UE may separately send its HARQ feedback message based on their own decoding outcome. This may include the UE 205 and the UE 210 not needing to coordinate the HARQ feedback content.
  • the network entity 215 may decide whether a retransmission is required once it receives the HARQ feedback messages from both the UE 205 and the UE 210.
  • a timer e.g., in x ms or in N slots
  • Another example may include at least two HARQ feedback resources in the set of feedback resources being configured for the aggregated downlink transmission 225 on a per-feedback status basis. This may include a first set of feedback resources being configured for an ACK feedback status and a second set of feedback resources for a NACK feedback status. Each UE may transmit their HARQ feedback message on the HARQ feedback resources corresponding to their HARQ feedback status. The UE 205 and/or the UE 210 may transmit their HARQ feedback message 230 and HARQ feedback message 235, respectively, on a first feedback resource from the set of feedback resources when their feedback status for the aggregated downlink transmission 225 is ACK.
  • the UE 205 and/or the UE 210 may transmit their HARQ feedback message 230 and HARQ feedback message 235, respectively, on a second feedback resource from the set of feedback resources when their feedback status for the aggregated downlink transmission 225 is NACK.
  • the first feedback resource and the second feedback resource may be in the same slot or in different slots.
  • separate HARQ feedback resources for ACK and NACK may be configured.
  • the network entity 215 may configures different feedback resources for ACK and NACK.
  • the two HARQ feedback resources may be in the same slot (e.g., so HARQ feedback timeline for the two UEs is the same) .
  • the two different HARQ feedback resources can be different resources in the frequency domain and/or in the code domain.
  • the network entity 215 may determines the feedback status to be NACK if no ACK is received, otherwise the network entity 215 may determines the feedback status to be ACK upon receiving an ACK indication.
  • the network entity 215 may retransmit the TB or CBG (e.g., the aggregated downlink transmission 225) if a NACK feedback status is determined.
  • CBG e.g., the aggregated downlink transmission 225
  • the UE 205 and the UE 210 may separately send their feedback based on their own decoding outcome (e.g., based on their feedback status) .
  • their decoding outcome e.g., based on their feedback status
  • they may send the same HARQ feedback in the same resource (using a subframe number (SFN) manner) .
  • SFN subframe number
  • a timer e.g., in x ms or in N slots
  • Another example may include a common feedback resource being configured in the grant 220 according to the indicated feedback mode.
  • the UE 205 and the UE 210 may select the common feedback resource to transmit their HARQ feedback message 230 and HARQ feedback message 235, respectively, based on the feedback status.
  • the feedback mode may be an ACK-only feedback mode where the UE 205 and/or the UE 210 only transmit the HARQ feedback message if the feedback status of the aggregated downlink transmission 225 is ACK.
  • the single HARQ feedback resource may be configured.
  • the network entity 215 may configure the same HARQ feedback resource for the two UEs (e.g., for the UE 205 and the UE 210) .
  • the HARQ feedback transmission may be ACK-only, resulting in each UE transmitting an ACK feedback status if its decoding is successful. Otherwise, the UE does not transmit its HARQ feedback.
  • the network entity 215 may determine the feedback status to be ACK if an ACK feedback status is received. Otherwise, the network entity 215 may determine the feedback to be NACK.
  • the network entity 215 may retransmit the TB or CBG if NACK is determined.
  • the UE 205 and the UE 210 may separately send its feedback based on their own decoding outcome.
  • the UE 205 and the UE 210 may not send a NACK indication, meaning that they will send HARQ feedback only if decoding is successful.
  • both UEs decode the aggregated downlink transmission 225 successfully, they may send the same ACK feedback in the same resource (e.g., in a SFN manner) .
  • a timer e.g., in x ms or in N slots
  • This example may not be applicable to CBG based HARQ feedback.
  • the UE 205 and/or the UE 210 may select the appropriate feedback resource from the set of feedback resources according to the feedback mode and based, at least to some degree, on their respective feedback statuses for the aggregated downlink transmission 225.
  • FIG. 3 illustrates an example of a method 300 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • Method 300 may implement aspects of wireless communications system 100 or wireless communications system 200. Aspects of method 300 may be implemented at or implemented by a network entity 305, a UE 310, or a UE 315, which may be examples of the corresponding devices described herein. In some aspects, the network entity 305 and the UE 310 may be associated with each other, such as participating in aggregated downlink transmissions from the network entity 305.
  • the network entity 305 may allocate a set of feedback resources for the aggregated downlink transmission to the UE 310 and the UE 315.
  • the set of feedback resources may include time resources, frequency resources, spatial resources, and/or code resources to be used for transmitting a feedback message (e.g., a HARQ feedback message) indicating a feedback status for the aggregated downlink transmission.
  • the set of feedback resources may be allocated according to a feedback mode. This may include a first set of feedback resources and a second set of feedback resources being allocated to the HARQ feedback messages.
  • the first set of feedback resources and the second set of feedback resources may be allocated on a per-UE basis, on a per-HARQ feedback status basis, or as common resources to be shared by both the UE 310 and the UE 315.
  • the per-UE basis resources may include the first set of feedback resources being allocated to the UE 310 (a first UE, which may be a relay UE) and the second set of feedback resources being allocated to the UE 315 (a second UE, which may be a remote UE) .
  • the per-HARQ feedback status basis may include the first set of feedback resource may be allocated to ACK feedback status reporting and the second feedback resource may be allocated to NACK feedback status reporting, or vice versa.
  • the common feedback resource basis may include common or shared feedback resources being configured for the HARQ feedback reporting mechanisms, where the HARQ feedback reporting mode is an ACK-only feedback mode.
  • the network entity 305 may transmit or otherwise provide (and the UE 310 and the UE 315 may receive or otherwise obtain) a grant scheduling an aggregated downlink transmission to the UE 310 and the UE 315.
  • the grant may be a DCI grant indicating a feedback mode and identifying the set of feedback resources.
  • the network entity 305 may transmit or otherwise provide the aggregated downlink transmission to the UE 310 and the UE 315 according to the grant. This may include transmitting the aggregated downlink transmission using a common or shared RNTI associated with the UE 310 and the UE 315. This may include transmitting the aggregated downlink transmission using the resource (s) and/or parameter (s) indicated in the grant.
  • the UE 310 may determine its feedback status for the aggregated downlink transmission. This may include an ACK feedback status if the UE 310 is able to monitor for, receive, and successfully decode the aggregated downlink transmission. This may include a NACK feedback status if the UE 310 is unable to monitor for, receive, and successfully decode the aggregated downlink transmission.
  • the feedback status for the aggregated downlink transmission may be determined based on whether the UE 310 is able to relay the aggregated downlink transmission to the UE 315 within a feedback delay reporting threshold, in some examples.
  • the UE 315 may determine its feedback status for the aggregated downlink transmission. This may include an ACK feedback status if the UE 315 is able to monitor for, receive, and successfully decode the aggregated downlink transmission. This may include a NACK feedback status if the UE 315 is unable to monitor for, receive, and successfully decode the aggregated downlink transmission.
  • the UE 310 may identify or otherwise select a feedback resource from the set of feedback resources available to the UE 310 to use for transmitting a feedback message indicating the feedback associated with the aggregated downlink transmission. This may include the UE 310 selecting a first feedback resource from the set of feedback resources based at least in part on the feedback mode. This may include the UE 310 selecting a common resource from the set of feedback resources. The first or common feedback resource may be selected based at least in part on the feedback status for the aggregated downlink transmission.
  • the UE 315 may identify or otherwise select a feedback resource from the set of feedback resources available to the UE 315 to use for transmitting a feedback message indicating the feedback associated with the aggregated downlink transmission. This may include the UE 315 selecting a second feedback resource from the set of feedback resources based at least in part on the feedback mode. This may include the UE 315 selecting a common resource from the set of feedback resources. The second or common feedback resource may be selected based at least in part on the feedback status for the aggregated downlink transmission.
  • the UE 310 may transmit or otherwise provide (and the network entity 305 may receive or otherwise obtain) a feedback message (e.g., a HARQ feedback message) indicating the feedback status for the aggregated downlink transmission.
  • the UE 310 may transmit the feedback message using the first feedback resource and according to the HARQ parameter (s) indicated in the grant.
  • the UE 315 may transmit or otherwise provide (and the network entity 305 may receive or otherwise obtain) a feedback message (e.g., a HARQ feedback message) indicating the feedback status for the aggregated downlink transmission.
  • the UE 315 may transmit the feedback message using the second feedback resource and according to the HARQ parameter (s) indicated in the grant.
  • FIG. 4 illustrates an example of a process 400 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • Process 400 may implement aspects of wireless communications system 100, wireless communications system 200, or method 300. Aspects of process 400 may be implemented at or implemented by a first UE, which may be an example of the corresponding device described herein.
  • the first UE may receive a grant scheduling an aggregated downlink transmission to the first UE and to a second UE.
  • the second UE in this example may be associated with the first UE, such as by participating in the aggregated downlink transmission from a network entity.
  • the grant may identify resources and parameters to be used for the aggregated downlink transmission.
  • the grant may identify a feedback mode associated with the aggregated downlink transmission.
  • the grant may identify a set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status for the aggregated downlink transmission.
  • the feedback mode may identify how the feedback resources are allocated (e.g., on a per-UE basis, on a per-feedback status basis, or on a common resource basis) to the first UE and the second UE.
  • the first UE may decode the aggregated downlink transmission.
  • the first UE may monitor for the aggregated downlink transmission according to the resources indicated in the grant.
  • the first UE may successfully receive and decode the aggregated downlink transmission, which may be associated with an ACK feedback status for the aggregated downlink transmission.
  • the first UE may identify or otherwise determine a delay time associated with relaying the aggregated downlink transmission to the second UE. This may include the first UE and the second UE exchanging message (s) prior to the aggregated downlink transmission.
  • the exchanged message (s) may identify, for the second UE, a delay budget associated with HARQ feedback reporting.
  • the first UE may determine whether the delay time associated with relaying the aggregated downlink transmission to the second UE satisfies a feedback delay reporting threshold. This may include the first UE receiving an indication of the HARQ delay timing in the grant. This may include the first UE comparing the delay budget of the second UE (e.g., the delay time) to the feedback delay reporting threshold.
  • the first UE may relay the aggregated downlink transmission (e.g., TB or CBG associated with the aggregated downlink transmission) to the second UE.
  • the first UE may optionally transmit an ACK feedback status to the network entity based on the delay time satisfying the threshold and the first UE relaying the aggregated downlink transmission to the second UE.
  • the first UE may not (e.g., may refrain) relay the aggregated downlink transmission to the second UE. This may include the first UE determining that, since the aggregated downlink transmission cannot be relayed to the second UE within the delay budget, relaying the aggregated downlink transmission to the second UE is not supported within the applicable HARQ feedback reporting timeline.
  • the first UE may transmit a HARQ feedback message to the network entity to trigger retransmission of the aggregated downlink transmission. This may include, even though the first UE was able to successfully receive and decode the aggregated downlink transmission, the NACK feedback status indication may be provided in the feedback message to the network entity.
  • FIG. 5 illustrates a block diagram 500 of a device 505 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • the device 505 may be an example of aspects of a UE 115 as described herein.
  • the device 505 may include a receiver 510, a transmitter 515, and a communications manager 520.
  • the device 505 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to feedback procedures for UE aggregation) . Information may be passed on to other components of the device 505.
  • the receiver 510 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 515 may provide a means for transmitting signals generated by other components of the device 505.
  • the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to feedback procedures for UE aggregation) .
  • the transmitter 515 may be co-located with a receiver 510 in a transceiver module.
  • the transmitter 515 may utilize a single antenna or a set of multiple antennas.
  • the communications manager 520, the receiver 510, the transmitter 515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of feedback procedures for UE aggregation as described herein.
  • the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
  • the communications manager 520, the receiver 510, the transmitter 515, 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) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, 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.
  • DSP digital signal processor
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory) .
  • the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure) .
  • code e.g., as communications management software or firmware
  • the functions of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a
  • the communications manager 520 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both.
  • the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 520 may support wireless communication at a first UE in accordance with examples as disclosed herein.
  • the communications manager 520 may be configured as or otherwise support a means for receiving a grant scheduling an aggregated downlink transmission to the first UE and a second UE that is associated with the first UE, the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources.
  • the communications manager 520 may be configured as or otherwise support a means for monitoring for the aggregated downlink transmission based on the grant.
  • the communications manager 520 may be configured as or otherwise support a means for selecting, based on the feedback mode, a feedback resource from the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission based on a result of the monitoring.
  • the device 505 may support techniques for improved HARQ feedback reporting for aggregated downlink transmissions to multiple UE where the available HARQ resources are allocated according to a feedback mode.
  • the feedback mode may define, for the aggregated UE, how the HARQ feedback resources are allocated as well as when the HARQ feedback reporting is to be performed.
  • FIG. 6 illustrates a block diagram 600 of a device 605 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • the device 605 may be an example of aspects of a device 505 or a UE 115 as described herein.
  • the device 605 may include a receiver 610, a transmitter 615, and a communications manager 620.
  • the device 605 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to feedback procedures for UE aggregation) . Information may be passed on to other components of the device 605.
  • the receiver 610 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 615 may provide a means for transmitting signals generated by other components of the device 605.
  • the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to feedback procedures for UE aggregation) .
  • the transmitter 615 may be co-located with a receiver 610 in a transceiver module.
  • the transmitter 615 may utilize a single antenna or a set of multiple antennas.
  • the device 605, or various components thereof may be an example of means for performing various aspects of feedback procedures for UE aggregation as described herein.
  • the communications manager 620 may include a grant manager 625, an aggregated communications manager 630, an HARQ resource manager 635, or any combination thereof.
  • the communications manager 620 may be an example of aspects of a communications manager 520 as described herein.
  • the communications manager 620, or various components thereof may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both.
  • the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 620 may support wireless communication at a first UE in accordance with examples as disclosed herein.
  • the grant manager 625 may be configured as or otherwise support a means for receiving a grant scheduling an aggregated downlink transmission to the first UE and a second UE that is associated with the first UE, the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources.
  • the aggregated communications manager 630 may be configured as or otherwise support a means for monitoring for the aggregated downlink transmission based on the grant.
  • the HARQ resource manager 635 may be configured as or otherwise support a means for selecting, based on the feedback mode, a feedback resource from the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission based on a result of the monitoring.
  • FIG. 7 illustrates a block diagram 700 of a communications manager 720 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • the communications manager 720 may be an example of aspects of a communications manager 520, a communications manager 620, or both, as described herein.
  • the communications manager 720, or various components thereof, may be an example of means for performing various aspects of feedback procedures for UE aggregation as described herein.
  • the communications manager 720 may include a grant manager 725, an aggregated communications manager 730, an HARQ resource manager 735, an HARQ feedback manager 740, a resource selection manager 745, an HARQ status manager 750, or any combination thereof.
  • Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the communications manager 720 may support wireless communication at a first UE in accordance with examples as disclosed herein.
  • the grant manager 725 may be configured as or otherwise support a means for receiving a grant scheduling an aggregated downlink transmission to the first UE and a second UE that is associated with the first UE, the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources.
  • the aggregated communications manager 730 may be configured as or otherwise support a means for monitoring for the aggregated downlink transmission based on the grant.
  • the HARQ resource manager 735 may be configured as or otherwise support a means for selecting, based on the feedback mode, a feedback resource from the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission based on a result of the monitoring.
  • the HARQ feedback manager 740 may be configured as or otherwise support a means for transmitting, based on the feedback status, the feedback message using the feedback resource. In some examples, the HARQ feedback manager 740 may be configured as or otherwise support a means for refraining from transmitting, based on the result of the monitoring including an acknowledgment feedback status, the feedback message using the feedback resource.
  • the resource selection manager 745 may be configured as or otherwise support a means for identifying, based on the grant and the feedback mode, a first feedback resource associated with the first UE and a second feedback resource associated with the second UE from the set of feedback resources. In some examples, the resource selection manager 745 may be configured as or otherwise support a means for selecting the first feedback resource associated with the first UE as the feedback resource to transmit the feedback message. In some examples, the first feedback resource and the second feedback resource are allocated in a same slot or in different slots.
  • the resource selection manager 745 may be configured as or otherwise support a means for identifying, based on the grant and the feedback mode, a first feedback resource associated with an ACK feedback status for the aggregated downlink transmission and a second feedback resource associated with a NACK feedback status for the aggregated downlink transmission. In some examples, the resource selection manager 745 may be configured as or otherwise support a means for selecting the first feedback resource or the second feedback resource based on the feedback status of the aggregated downlink transmission, where the feedback status includes the ACK feedback status or the NACK feedback status. In some examples, the first feedback resource and the second feedback resource are allocated in a same slot.
  • the resource selection manager 745 may be configured as or otherwise support a means for identifying, based on the grant and the feedback mode, a common feedback resource associated with the aggregated downlink transmission. In some examples, the resource selection manager 745 may be configured as or otherwise support a means for selecting the common feedback resource to transmit the feedback message based on the feedback status of the aggregated downlink transmission including an acknowledgment feedback status. In some examples, the feedback mode includes an ACK feedback status only feedback mode.
  • the HARQ status manager 750 may be configured as or otherwise support a means for decoding the aggregated downlink transmission to obtain an ACK feedback status for the aggregated downlink transmission. In some examples, the HARQ status manager 750 may be configured as or otherwise support a means for determining a delay time associated with relaying the aggregated downlink transmission to the second UE. In some examples, the HARQ status manager 750 may be configured as or otherwise support a means for relaying the aggregated downlink transmission to the second UE based on the delay time satisfying a feedback delay reporting threshold. In some examples, a comparison of the delay time to the feedback delay reporting threshold, a feedback reporting timer associated with the aggregated downlink transmission, a message exchange with the second UE indicating the delay time, a delay timing indication carried in the grant, or any combination thereof.
  • the HARQ status manager 750 may be configured as or otherwise support a means for decoding the aggregated downlink transmission to obtain an ACK feedback status for the aggregated downlink transmission. In some examples, the HARQ status manager 750 may be configured as or otherwise support a means for determining that a delay time associated with relaying the aggregated downlink transmission to the second UE fails to satisfying a feedback delay reporting threshold. In some examples, the HARQ status manager 750 may be configured as or otherwise support a means for transmitting, based on the delay time failing to satisfy the feedback delay reporting threshold, the feedback message indicating a negative-acknowledgment feedback status associated with the aggregated downlink transmission.
  • the HARQ status manager 750 may be configured as or otherwise support a means for refraining from relaying the aggregated downlink transmission to the second UE based on the delay time failing to satisfy the feedback delay reporting threshold.
  • FIG. 8 illustrates a diagram of a system 800 including a device 805 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • the device 805 may be an example of or include the components of a device 505, a device 605, or a UE 115 as described herein.
  • the device 805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof.
  • the device 805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 820, an input/output (I/O) controller 810, a transceiver 815, an antenna 825, a memory 830, code 835, and a processor 840. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845) .
  • a bus 845 e.g., a bus 845
  • the I/O controller 810 may manage input and output signals for the device 805.
  • the I/O controller 810 may also manage peripherals not integrated into the device 805.
  • the I/O controller 810 may represent a physical connection or port to an external peripheral.
  • the I/O controller 810 may utilize an operating system such as or another known operating system.
  • the I/O controller 810 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
  • the I/O controller 810 may be implemented as part of a processor, such as the processor 840.
  • a user may interact with the device 805 via the I/O controller 810 or via hardware components controlled by the I/O controller 810.
  • the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 815 may communicate bi-directionally, via the one or more antennas 825, wired, or wireless links as described herein.
  • the transceiver 815 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 815 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 825 for transmission, and to demodulate packets received from the one or more antennas 825.
  • the transceiver 815 may be an example of a transmitter 515, a transmitter 615, a receiver 510, a receiver 610, or any combination thereof or component thereof, as described herein.
  • the memory 830 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 830 may store computer-readable, computer-executable code 835 including instructions that, when executed by the processor 840, cause the device 805 to perform various functions described herein.
  • the code 835 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code 835 may not be directly executable by the processor 840 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 830 may contain, 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.
  • BIOS basic I/O system
  • the processor 840 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) .
  • the processor 840 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 840.
  • the processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting feedback procedures for UE aggregation) .
  • the device 805 or a component of the device 805 may include a processor 840 and memory 830 coupled with or to the processor 840, the processor 840 and memory 830 configured to perform various functions described herein.
  • the communications manager 820 may support wireless communication at a first UE in accordance with examples as disclosed herein.
  • the communications manager 820 may be configured as or otherwise support a means for receiving a grant scheduling an aggregated downlink transmission to the first UE and a second UE that is associated with the first UE, the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources.
  • the communications manager 820 may be configured as or otherwise support a means for monitoring for the aggregated downlink transmission based on the grant.
  • the communications manager 820 may be configured as or otherwise support a means for selecting, based on the feedback mode, a feedback resource from the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission based on a result of the monitoring.
  • the device 805 may support techniques for improved HARQ feedback reporting for aggregated downlink transmissions to multiple UE where the available HARQ resources are allocated according to a feedback mode.
  • the feedback mode may define, for the aggregated UE, how the HARQ feedback resources are allocated as well as when the HARQ feedback reporting is to be performed.
  • the communications manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 815, the one or more antennas 825, or any combination thereof.
  • the communications manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 820 may be supported by or performed by the processor 840, the memory 830, the code 835, or any combination thereof.
  • the code 835 may include instructions executable by the processor 840 to cause the device 805 to perform various aspects of feedback procedures for UE aggregation as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.
  • FIG. 9 illustrates a block diagram 900 of a device 905 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • the device 905 may be an example of aspects of a network entity 105 as described herein.
  • the device 905 may include a receiver 910, a transmitter 915, and a communications manager 920.
  • the device 905 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 910 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • Information may be passed on to other components of the device 905.
  • the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 915 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 905.
  • the transmitter 915 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • the transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include or be coupled with a modem.
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of feedback procedures for UE aggregation as described herein.
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, 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.
  • a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory) .
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure) .
  • code e.g., as communications management software or firmware
  • the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a
  • the communications manager 920 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both.
  • the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 920 may support wireless communication at a network entity in accordance with examples as disclosed herein.
  • the communications manager 920 may be configured as or otherwise support a means for transmitting a grant scheduling an aggregated downlink transmission to a first UE and a second UE, the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources.
  • the communications manager 920 may be configured as or otherwise support a means for transmitting the aggregated downlink transmission to the first UE and the second UE according to the grant.
  • the communications manager 920 may be configured as or otherwise support a means for monitoring the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission.
  • the device 905 may support techniques for improved HARQ feedback reporting for aggregated downlink transmissions to multiple UE where the available HARQ resources are allocated according to a feedback mode.
  • the feedback mode may define, for the aggregated UE, how the HARQ feedback resources are allocated as well as when the HARQ feedback reporting is to be performed.
  • FIG. 10 illustrates a block diagram 1000 of a device 1005 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • the device 1005 may be an example of aspects of a device 905 or a network entity 105 as described herein.
  • the device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020.
  • the device 1005 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1010 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • Information may be passed on to other components of the device 1005.
  • the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1015 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1005.
  • the transmitter 1015 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include or be coupled with a modem.
  • the device 1005, or various components thereof, may be an example of means for performing various aspects of feedback procedures for UE aggregation as described herein.
  • the communications manager 1020 may include a grant manager 1025, an aggregated communications manager 1030, an HARQ manager 1035, or any combination thereof.
  • the communications manager 1020 may be an example of aspects of a communications manager 920 as described herein.
  • the communications manager 1020, or various components thereof may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both.
  • the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 1020 may support wireless communication at a network entity in accordance with examples as disclosed herein.
  • the grant manager 1025 may be configured as or otherwise support a means for transmitting a grant scheduling an aggregated downlink transmission to a first UE and a second UE, the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources.
  • the aggregated communications manager 1030 may be configured as or otherwise support a means for transmitting the aggregated downlink transmission to the first UE and the second UE according to the grant.
  • the HARQ manager 1035 may be configured as or otherwise support a means for monitoring the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission.
  • FIG. 11 illustrates a block diagram 1100 of a communications manager 1120 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • the communications manager 1120 may be an example of aspects of a communications manager 920, a communications manager 1020, or both, as described herein.
  • the communications manager 1120, or various components thereof, may be an example of means for performing various aspects of feedback procedures for UE aggregation as described herein.
  • the communications manager 1120 may include a grant manager 1125, an aggregated communications manager 1130, an HARQ manager 1135, an HARQ resource manager 1140, a retransmission manager 1145, a relay manager 1150, a delay manager 1155, or any combination thereof.
  • Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) which may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105) , or any combination thereof.
  • the communications manager 1120 may support wireless communication at a network entity in accordance with examples as disclosed herein.
  • the grant manager 1125 may be configured as or otherwise support a means for transmitting a grant scheduling an aggregated downlink transmission to a first UE and a second UE, the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources.
  • the aggregated communications manager 1130 may be configured as or otherwise support a means for transmitting the aggregated downlink transmission to the first UE and the second UE according to the grant.
  • the HARQ manager 1135 may be configured as or otherwise support a means for monitoring the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission.
  • the HARQ resource manager 1140 may be configured as or otherwise support a means for allocating a first feedback resource in the set of feedback resources to the first UE to use to transmit the feedback message and a second feedback resource in the set of feedback resources to the second UE to use to transmit the feedback message. In some examples, the HARQ resource manager 1140 may be configured as or otherwise support a means for allocating a first feedback resource in the set of feedback resources to an ACK feedback status associated with the aggregated downlink transmission and a second feedback resource in the set of feedback resources to a NACK feedback status associated with the aggregated downlink transmission. In some examples, the HARQ resource manager 1140 may be configured as or otherwise support a means for allocating a common feedback resource in the set of feedback resources to the first UE and the second UE to use to transmit the feedback message.
  • the retransmission manager 1145 may be configured as or otherwise support a means for determining, based on the feedback message not being received, that the feedback status associated with the aggregated downlink transmission includes a NACK feedback status. In some examples, the retransmission manager 1145 may be configured as or otherwise support a means for retransmitting the aggregated downlink transmission to the first UE and the second UE based on the NACK feedback status.
  • the relay manager 1150 may be configured as or otherwise support a means for providing a relay indication in the grant, the relay indication associated with relaying operations between the first UE and the second UE for the aggregated downlink transmission.
  • the delay manager 1155 may be configured as or otherwise support a means for providing a feedback reporting timer, a delay timing indication, or a combination thereof, in the grant.
  • FIG. 12 illustrates a diagram of a system 1200 including a device 1205 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • the device 1205 may be an example of or include the components of a device 905, a device 1005, or a network entity 105 as described herein.
  • the device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof.
  • the device 1205 may include components that support outputting and obtaining communications, such as a communications manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, code 1230, and a processor 1235. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1240) .
  • buses e
  • the transceiver 1210 may support bi-directional communications via wired links, wireless links, or both as described herein.
  • the transceiver 1210 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the device 1205 may include one or more antennas 1215, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently) .
  • the transceiver 1210 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1215, by a wired transmitter) , to receive modulated signals (e.g., from one or more antennas 1215, from a wired receiver) , and to demodulate signals.
  • the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1215 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1215 that are configured to support various transmitting or outputting operations, or a combination thereof.
  • the transceiver 1210 may include or be configured for coupling with one or more processors or memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof.
  • the transceiver 1210, or the transceiver 1210 and the one or more antennas 1215, or the transceiver 1210 and the one or more antennas 1215 and one or more processors or memory components may be included in a chip or chip assembly that is installed in the device 1205.
  • the transceiver may be operable to support communications via one or more communications links (e.g., a communication link 125, a backhaul communication link 120, a midhaul communication link 162, a fronthaul communication link 168) .
  • one or more communications links e.g., a communication link 125, a backhaul communication link 120, a midhaul communication link 162, a fronthaul communication link 168 .
  • the memory 1225 may include RAM and ROM.
  • the memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by the processor 1235, cause the device 1205 to perform various functions described herein.
  • the code 1230 may be stored in a non-transitory computer- readable medium such as system memory or another type of memory. In some cases, the code 1230 may not be directly executable by the processor 1235 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 1225 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • the processor 1235 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, a discrete hardware component, or any combination thereof) .
  • the processor 1235 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1235.
  • the processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1225) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting feedback procedures for UE aggregation) .
  • the device 1205 or a component of the device 1205 may include a processor 1235 and memory 1225 coupled with the processor 1235, the processor 1235 and memory 1225 configured to perform various functions described herein.
  • the processor 1235 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1230) to perform the functions of the device 1205.
  • the processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1205 (such as within the memory 1225) .
  • the processor 1235 may be a component of a processing system.
  • a processing system may generally refer to a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs (which may be passed to other systems or components of, for example, the device 1205) .
  • a processing system of the device 1205 may refer to a system including the various other components or subcomponents of the device 1205, such as the processor 1235, or the transceiver 1210, or the communications manager 1220, or other components or combinations of components of the device 1205.
  • the processing system of the device 1205 may interface with other components of the device 1205, and may process information received from other components (such as inputs or signals) or output information to other components.
  • a chip or modem of the device 1205 may include a processing system and one or more interfaces to output information, or to obtain information, or both.
  • the one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or a same interface configured to output information and to obtain information, among other implementations.
  • the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, such that the device 1205 may transmit information output from the chip or modem.
  • the one or more interfaces may refer to an interface between the processing system of the chip or modem and a receiver, such that the device 1205 may obtain information or signal inputs, and the information may be passed to the processing system.
  • a first interface also may obtain information or signal inputs
  • a second interface also may output information or signal outputs.
  • a bus 1240 may support communications of (e.g., within) a protocol layer of a protocol stack.
  • a bus 1240 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack) , which may include communications performed within a component of the device 1205, or between different components of the device 1205 that may be co-located or located in different locations (e.g., where the device 1205 may refer to a system in which one or more of the communications manager 1220, the transceiver 1210, the memory 1225, the code 1230, and the processor 1235 may be located in one of the different components or divided between different components) .
  • the communications manager 1220 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links) .
  • the communications manager 1220 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • the communications manager 1220 may manage communications with other network entities 105, and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other network entities 105.
  • the communications manager 1220 may support an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between network entities 105.
  • the communications manager 1220 may support wireless communication at a network entity in accordance with examples as disclosed herein.
  • the communications manager 1220 may be configured as or otherwise support a means for transmitting a grant scheduling an aggregated downlink transmission to a first UE and a second UE, the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources.
  • the communications manager 1220 may be configured as or otherwise support a means for transmitting the aggregated downlink transmission to the first UE and the second UE according to the grant.
  • the communications manager 1220 may be configured as or otherwise support a means for monitoring the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission.
  • the device 1205 may support techniques for improved HARQ feedback reporting for aggregated downlink transmissions to multiple UE where the available HARQ resources are allocated according to a feedback mode.
  • the feedback mode may define, for the aggregated UE, how the HARQ feedback resources are allocated as well as when the HARQ feedback reporting is to be performed.
  • the communications manager 1220 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1210, the one or more antennas 1215 (e.g., where applicable) , or any combination thereof.
  • the communications manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1220 may be supported by or performed by the transceiver 1210, the processor 1235, the memory 1225, the code 1230, or any combination thereof.
  • the code 1230 may include instructions executable by the processor 1235 to cause the device 1205 to perform various aspects of feedback procedures for UE aggregation as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.
  • FIG. 13 illustrates a flowchart showing a method 1300 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1300 may be implemented by a UE or its components as described herein.
  • the operations of the method 1300 may be performed by a UE 115 as described with reference to FIGs. 1 through 8.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving a grant scheduling an aggregated downlink transmission to the first UE and a second UE that is associated with the first UE, the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources.
  • the operations of 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by a grant manager 725 as described with reference to FIG. 7.
  • the method may include monitoring for the aggregated downlink transmission based on the grant.
  • the operations of 1310 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by an aggregated communications manager 730 as described with reference to FIG. 7.
  • the method may include selecting, based on the feedback mode, a feedback resource from the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission based on a result of the monitoring.
  • the operations of 1315 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed by an HARQ resource manager 735 as described with reference to FIG. 7.
  • FIG. 14 illustrates a flowchart showing a method 1400 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1400 may be implemented by a UE or its components as described herein.
  • the operations of the method 1400 may be performed by a UE 115 as described with reference to FIGs. 1 through 8.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving a grant scheduling an aggregated downlink transmission to the first UE and a second UE that is associated with the first UE, the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources.
  • the operations of 1405 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by a grant manager 725 as described with reference to FIG. 7.
  • the method may include monitoring for the aggregated downlink transmission based on the grant.
  • the operations of 1410 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by an aggregated communications manager 730 as described with reference to FIG. 7.
  • the method may include selecting, based on the feedback mode, a feedback resource from the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission based on a result of the monitoring.
  • the operations of 1415 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by an HARQ resource manager 735 as described with reference to FIG. 7.
  • the method may include transmitting, based on the feedback status, the feedback message using the feedback resource.
  • the operations of 1420 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed by an HARQ feedback manager 740 as described with reference to FIG. 7.
  • FIG. 15 illustrates a flowchart showing a method 1500 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1500 may be implemented by a UE or its components as described herein.
  • the operations of the method 1500 may be performed by a UE 115 as described with reference to FIGs. 1 through 8.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving a grant scheduling an aggregated downlink transmission to the first UE and a second UE that is associated with the first UE, the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources.
  • the operations of 1505 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed by a grant manager 725 as described with reference to FIG. 7.
  • the method may include monitoring for the aggregated downlink transmission based on the grant.
  • the operations of 1510 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by an aggregated communications manager 730 as described with reference to FIG. 7.
  • the method may include selecting, based on the feedback mode, a feedback resource from the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission based on a result of the monitoring.
  • the operations of 1515 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed by an HARQ resource manager 735 as described with reference to FIG. 7.
  • the method may include refraining from transmitting, based on the result of the monitoring including an acknowledgment feedback status, the feedback message using the feedback resource.
  • the operations of 1520 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed by an HARQ feedback manager 740 as described with reference to FIG. 7.
  • FIG. 16 illustrates a flowchart showing a method 1600 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1600 may be implemented by a network entity or its components as described herein.
  • the operations of the method 1600 may be performed by a network entity as described with reference to FIGs. 1 through 4 and 9 through 12.
  • a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.
  • the method may include transmitting a grant scheduling an aggregated downlink transmission to a first UE and a second UE, the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources.
  • the operations of 1605 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed by a grant manager 1125 as described with reference to FIG. 11.
  • the method may include transmitting the aggregated downlink transmission to the first UE and the second UE according to the grant.
  • the operations of 1610 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by an aggregated communications manager 1130 as described with reference to FIG. 11.
  • the method may include monitoring the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission.
  • the operations of 1615 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed by an HARQ manager 1135 as described with reference to FIG. 11.
  • FIG. 17 illustrates a flowchart showing a method 1700 that supports feedback procedures for UE aggregation in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1700 may be implemented by a network entity or its components as described herein.
  • the operations of the method 1700 may be performed by a network entity as described with reference to FIGs. 1 through 4 and 9 through 12.
  • a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.
  • the method may include allocating a first feedback resource in the set of feedback resources to the first UE to use to transmit the feedback message and a second feedback resource in the set of feedback resources to the second UE to use to transmit the feedback message.
  • the operations of 1705 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by an HARQ resource manager 1140 as described with reference to FIG. 11.
  • the method may include transmitting a grant scheduling an aggregated downlink transmission to a first UE and a second UE, the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources.
  • the operations of 1710 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a grant manager 1125 as described with reference to FIG. 11.
  • the method may include transmitting the aggregated downlink transmission to the first UE and the second UE according to the grant.
  • the operations of 1715 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by an aggregated communications manager 1130 as described with reference to FIG. 11.
  • the method may include monitoring the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission.
  • the operations of 1720 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed by an HARQ manager 1135 as described with reference to FIG. 11.
  • a method for wireless communication at a first UE comprising: receiving a grant scheduling an aggregated downlink transmission to the first UE and a second UE that is associated with the first UE, the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources; monitoring for the aggregated downlink transmission based at least in part on the grant; and selecting, based at least in part on the feedback mode, a feedback resource from the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission based on a result of the monitoring.
  • Aspect 2 The method of aspect 1, further comprising: transmitting, based at least in part on the feedback status, the feedback message using the feedback resource.
  • Aspect 3 The method of any of aspects 1 through 2, further comprising: refraining from transmitting, based at least in part on the result of the monitoring comprising an acknowledgment feedback status, the feedback message using the feedback resource.
  • Aspect 4 The method of any of aspects 1 through 3, further comprising: identifying, based at least in part on the grant and the feedback mode, a first feedback resource associated with the first UE and a second feedback resource associated with the second UE from the set of feedback resources; and selecting the first feedback resource associated with the first UE as the feedback resource to transmit the feedback message.
  • Aspect 5 The method of aspect 4, wherein the first feedback resource and the second feedback resource are allocated in a same slot or in different slots.
  • Aspect 6 The method of any of aspects 1 through 5, further comprising: identifying, based at least in part on the grant and the feedback mode, a first feedback resource associated with an acknowledgement feedback status for the aggregated downlink transmission and a second feedback resource associated with a negative-acknowledgement feedback status for the aggregated downlink transmission; and selecting the first feedback resource or the second feedback resource based at least in part on the feedback status of the aggregated downlink transmission, wherein the feedback status comprises the acknowledgement feedback status or the negative-acknowledgement feedback status.
  • Aspect 7 The method of aspect 6, wherein the first feedback resource and the second feedback resource are allocated in a same slot.
  • Aspect 8 The method of any of aspects 1 through 7, further comprising: identifying, based at least in part on the grant and the feedback mode, a common feedback resource associated with the aggregated downlink transmission; and selecting the common feedback resource to transmit the feedback message based at least in part on the feedback status of the aggregated downlink transmission comprising an acknowledgment feedback status.
  • Aspect 9 The method of any of aspects 1 through 8, wherein the feedback mode comprises an acknowledgement feedback status only feedback mode.
  • Aspect 10 The method of any of aspects 1 through 9, further comprising: decoding the aggregated downlink transmission to obtain an acknowledgement feedback status for the aggregated downlink transmission; determining a delay time associated with relaying the aggregated downlink transmission to the second UE; and relaying the aggregated downlink transmission to the second UE based at least in part on the delay time satisfying a feedback delay reporting threshold.
  • Aspect 11 The method of aspect 10, wherein the relaying is based on at least one of a comparison of the delay time to the feedback delay reporting threshold, a feedback reporting timer associated with the aggregated downlink transmission, a message exchange with the second UE indicating the delay time, a delay timing indication carried in the grant, or any combination thereof.
  • Aspect 12 The method of any of aspects 1 through 11, further comprising: decoding the aggregated downlink transmission to obtain an acknowledgement feedback status for the aggregated downlink transmission; determining that a delay time associated with relaying the aggregated downlink transmission to the second UE fails to satisfying a feedback delay reporting threshold; and transmitting, based at least in part on the delay time failing to satisfy the feedback delay reporting threshold, the feedback message indicating a negative-acknowledgment feedback status associated with the aggregated downlink transmission.
  • Aspect 13 The method of aspect 12, further comprising: refraining from relaying the aggregated downlink transmission to the second UE based at least in part on the delay time failing to satisfy the feedback delay reporting threshold.
  • a method for wireless communication at a network entity comprising: transmitting a grant scheduling an aggregated downlink transmission to a first UE and a second UE, the grant indicating a feedback mode associated with the aggregated downlink transmission and identifying a set of feedback resources; transmitting the aggregated downlink transmission to the first UE and the second UE according to the grant; and monitoring the set of feedback resources available to the first UE and the second UE to use for transmitting a feedback message indicating a feedback status associated with the aggregated downlink transmission.
  • Aspect 15 The method of aspect 14, further comprising: allocating a first feedback resource in the set of feedback resources to the first UE to use to transmit the feedback message and a second feedback resource in the set of feedback resources to the second UE to use to transmit the feedback message.
  • Aspect 16 The method of any of aspects 14 through 15, further comprising: allocating a first feedback resource in the set of feedback resources to an acknowledgement feedback status associated with the aggregated downlink transmission and a second feedback resource in the set of feedback resources to a negative-acknowledgement feedback status associated with the aggregated downlink transmission.
  • Aspect 17 The method of any of aspects 14 through 16, further comprising: allocating a common feedback resource in the set of feedback resources to the first UE and the second UE to use to transmit the feedback message.
  • Aspect 18 The method of any of aspects 14 through 17, further comprising: determining, based at least in part on the feedback message not being received, that the feedback status associated with the aggregated downlink transmission comprises a negative-acknowledgement feedback status; and retransmitting the aggregated downlink transmission to the first UE and the second UE based at least in part on the negative-acknowledgement feedback status.
  • Aspect 19 The method of any of aspects 14 through 18, further comprising: providing a relay indication in the grant, the relay indication associated with relaying operations between the first UE and the second UE for the aggregated downlink transmission.
  • Aspect 20 The method of any of aspects 14 through 19, further comprising: providing a feedback reporting timer, a delay timing indication, or a combination thereof, in the grant.
  • Aspect 21 An apparatus for wireless communication at a first UE, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 1 through 13.
  • Aspect 22 An apparatus for wireless communication at a first UE, comprising at least one means for performing a method of any of aspects 1 through 13.
  • Aspect 23 A non-transitory computer-readable medium storing code for wireless communication at a first UE, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 13.
  • Aspect 24 An apparatus for wireless communication at a network entity, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 14 through 20.
  • Aspect 25 An apparatus for wireless communication at a network entity, comprising at least one means for performing a method of any of aspects 14 through 20.
  • Aspect 26 A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform a method of any of aspects 14 through 20.
  • LTE, LTE-A, LTE-A Pro, or NR may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks.
  • the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
  • UMB Ultra Mobile Broadband
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Institute of Electrical and Electronics Engineers
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • 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.
  • 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 using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of 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 location to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • 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.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.
  • determining encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des procédés, des systèmes et des dispositifs destinés aux communications sans fil. Un équipement utilisateur (UE) peut recevoir une autorisation ordonnançant une transmission de liaison descendante agrégée vers le premier équipement utilisateur et un second équipement utilisateur qui est associé au premier équipement utilisateur, l'autorisation indiquant un mode de rétroaction associé à la transmission de liaison descendante agrégée et identifiant un ensemble de ressources de rétroaction. L'équipement utilisateur peut surveiller la transmission de liaison descendante agrégée sur la base, au moins en partie, de l'autorisation. L'équipement utilisateur peut sélectionner, sur la base, au moins en partie, du mode de rétroaction, une ressource de rétroaction parmi l'ensemble de ressources de rétroaction disponibles pour le premier équipement utilisateur et le second équipement utilisateur à utiliser pour transmettre un message de rétroaction indiquant un état de rétroaction associé à la transmission de liaison descendante agrégée sur la base d'un résultat de la surveillance.
PCT/CN2023/079979 2023-03-07 2023-03-07 Procédures de rétroaction pour agrégation d'équipement utilisateur WO2024182986A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/079979 WO2024182986A1 (fr) 2023-03-07 2023-03-07 Procédures de rétroaction pour agrégation d'équipement utilisateur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/079979 WO2024182986A1 (fr) 2023-03-07 2023-03-07 Procédures de rétroaction pour agrégation d'équipement utilisateur

Publications (1)

Publication Number Publication Date
WO2024182986A1 true WO2024182986A1 (fr) 2024-09-12

Family

ID=92674043

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/079979 WO2024182986A1 (fr) 2023-03-07 2023-03-07 Procédures de rétroaction pour agrégation d'équipement utilisateur

Country Status (1)

Country Link
WO (1) WO2024182986A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200205175A1 (en) * 2018-07-06 2020-06-25 Qualcomm Incorporated Feedback for multi-point communications
US20200266932A1 (en) * 2019-02-14 2020-08-20 Qualcomm Incorporated Acknowledgment feedback techniques in wireless communications
US20210219331A1 (en) * 2020-01-15 2021-07-15 Qualcomm Incorporated Feedback transmissions based on uplink grants
US20220330311A1 (en) * 2021-04-05 2022-10-13 Qualcomm Incorporated Grant-based feedback bit determination for feedback occasions

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200205175A1 (en) * 2018-07-06 2020-06-25 Qualcomm Incorporated Feedback for multi-point communications
US20200266932A1 (en) * 2019-02-14 2020-08-20 Qualcomm Incorporated Acknowledgment feedback techniques in wireless communications
US20210219331A1 (en) * 2020-01-15 2021-07-15 Qualcomm Incorporated Feedback transmissions based on uplink grants
US20220330311A1 (en) * 2021-04-05 2022-10-13 Qualcomm Incorporated Grant-based feedback bit determination for feedback occasions

Similar Documents

Publication Publication Date Title
US11546038B2 (en) Beam sweeping patterns for single frequency network broadcast channel
US20230164819A1 (en) Uplink control information multiplexing rule for simultaneous uplink control channel and uplink shared channel transmission
WO2024035455A1 (fr) Construction de livre de codes de rétroaction pour une commutation de porteuse de canal de commande
WO2023239449A1 (fr) Planification de liaison montante semi-autonome
US20220330311A1 (en) Grant-based feedback bit determination for feedback occasions
US11778629B2 (en) Techniques for determining resource assignments for decode and forward relaying via downlink control information
WO2023009343A1 (fr) Architecture pour accès et raccordement intégrés avec liaison latérale
WO2024182986A1 (fr) Procédures de rétroaction pour agrégation d'équipement utilisateur
WO2024178705A1 (fr) Temps d'application de faisceau pour états d'indicateur de configuration de transmission unifiée
US11937213B2 (en) Optimizations for sidelink user equipment for integrated access and backhaul network
US11477760B2 (en) Frequency diversity techniques for single frequency networks
WO2023206459A1 (fr) Multiplexage de liaison montante pour opérations multiples de point de transmission / réception
US20240031063A1 (en) Transport block size determination for sidelink slot aggregation
US11991715B2 (en) Techniques to support user equipment based relaying for coverage enhancement
US20240114518A1 (en) System information transmission with coverage recovery
US20240155622A1 (en) Discontinuous reception enhancement with multiple sidelink feedback channel opportunities
US20230345454A1 (en) Techniques for sending a collision indication via a physical sidelink feedback channel
US20240195463A1 (en) Space time coding for sidelink transmissions
US20240306139A1 (en) Transmission of deferred feedback via uplink shared channel
US20240107535A1 (en) User equipment processing capability for wireless communications with rate splitting
WO2024045001A1 (fr) Techniques d'attribution de ressources de fréquence dans un canal d'accès aléatoire
WO2024092596A1 (fr) Indication implicite de répétition de prach
US20240340109A1 (en) Conditional hybrid automatic repeat request retransmission across carriers
WO2024065642A1 (fr) Multiplexage d'informations de commande de liaison montante sur des canaux de multiplexage par répartition en fréquence
US20240129070A1 (en) Configurable mini-slot retransmissions in sidelink communications