Feedback reporting for multiple feedback opportunities

Abstract

Methods, systems, and devices for wireless communication are described. In some examples, a first user equipment (UE) may send a sidelink message from a first layer of a protocol stack at the first UE and via a sidelink shared channel to one or more second UEs, the sidelink message corresponding to a plurality of feedback monitoring occasions for first feedback associated with the sidelink message. The sidelink message may be associated with a broadcast type of a plurality of broadcast types, including unicast, multicast associated with feedback based on negative acknowledgement only, and multicast associated with feedback based on negative acknowledgement and positive acknowledgement. The first UE may send a single feedback report to a second layer of the protocol stack that is higher than the first layer based on the broadcast type and based on receiving or absence of one or more feedback messages via the feedback monitoring opportunities, the single feedback report indicating second feedback for the plurality of feedback monitoring opportunities.

Description

Technical Field

[0001] This disclosure relates to wireless communications, including feedback reporting for multiple feedback timings. Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing 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-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0003] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting feedback reporting for multiple feedback timings. Typically, the techniques described herein allow a user equipment (UE) to determine whether or when to send feedback to a higher layer at that UE for multiple feedback timings associated with a feedback channel (e.g., a Physical Sidelink Feedback Channel (PSFCH)), and information to indicate or include in that feedback. For example, a first UE may send a sidelink message (e.g., a PSSCH message) from a first layer of its protocol stack (such as the physical (PHY) layer) and via a sidelink shared channel (e.g., a Physical Sidelink Shared Channel (PSSCH)) to one (e.g., unicast) or multiple (e.g., multicast) second UEs. In such cases, the sidelink message may correspond to multiple feedback timings (e.g., feedback monitoring timings) in which the first UE can monitor a first feedback associated with the sidelink message. Additionally, the sidelink message may be associated with a broadcast type among a variety of broadcast types, including at least unicast, multicast associated with feedback based on negative acknowledgment only (NACK only), and multicast associated with feedback based on both negative acknowledgment (NACK) and positive acknowledgment (ACK). The first UE may receive or identify the absence of the first feedback associated with the sidelink message based on the monitoring via one or more of the plurality of feedback times.

[0004] Therefore, the first UE may send a feedback report (e.g., a single feedback report) to a second layer (such as a Media Access Control (MAC) layer) higher than the first layer of the protocol stack, indicating a second feedback for the plurality of feedback monitoring moments. The second feedback, the timing of its transmission, or both may be based on the broadcast type of the sidelink message and on the receipt or absence of one or more feedback messages via the plurality of feedback moments (e.g., whether the first feedback was received or identified as absent during the one or more feedback moments in the plurality of feedback moments). For example, the second feedback (e.g., and the timing of its transmission) may be based on a rule associated with the broadcast type, wherein the rule indicates one or more conditions under which the first UE may send the second feedback. In such cases, the rule may further be based on whether the first feedback associated with the sidelink message during at least one of the plurality of feedback monitoring moments includes one or more ACK messages, one or more NACK messages, or both, or whether it includes the absence of the one or more ACK messages, the one or more NACK messages, or both.

[0005] A method for wireless communication by a UE is described. The method may include: transmitting a sidelink message from a first layer of a protocol stack at a first UE and via a sidelink shared channel to one or more second UEs, the sidelink message corresponding to a set of multiple feedback monitoring opportunities for a first feedback associated with the sidelink message, wherein the sidelink message belongs to a first broadcast type in a set of multiple broadcast types; and reporting a single feedback report to a second layer above the first layer of the protocol stack based on the first broadcast type and based on the receipt or absence of one or more feedback messages via the set of multiple feedback monitoring opportunities, the single feedback report indicating a second feedback for the set of multiple feedback monitoring opportunities.

[0006] A first UE for wireless communication is described. The first UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors are individually or jointly operable to execute the code so that the first UE: transmits a sidelink message from a first layer of a protocol stack at the first UE and via a sidelink shared channel to one or more second UEs, the sidelink message corresponding to a set of multiple feedback monitoring opportunities for a first feedback associated with the sidelink message, wherein the sidelink message belongs to a first broadcast type in a set of multiple broadcast types; and reports a single feedback report to a second layer above the first layer of the protocol stack based on the first broadcast type and based on the receipt or absence of one or more feedback messages via the set of multiple feedback monitoring opportunities, the single feedback report indicating a second feedback for the set of feedback monitoring opportunities.

[0007] Another first UE for wireless communication is described. The first UE may include: components for transmitting a sidelink message from a first layer of a protocol stack at the first UE and via a sidelink shared channel to one or more second UEs, the sidelink message corresponding to a set of multiple feedback monitoring opportunities for a first feedback associated with the sidelink message, wherein the sidelink message belongs to a first broadcast type in a set of multiple broadcast types; and components for reporting a single feedback report to a second layer above the first layer of the protocol stack based on the first broadcast type and based on the receipt or absence of one or more feedback messages via the set of multiple feedback monitoring opportunities, the single feedback report indicating a second feedback for the set of feedback monitoring opportunities.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: transmit a sidelink message from a first layer of a protocol stack at a first UE and via a sidelink shared channel to one or more second UEs, the sidelink message corresponding to a set of multiple feedback monitoring opportunities for a first feedback associated with the sidelink message, wherein the sidelink message belongs to a first broadcast type in a set of multiple broadcast types; and report a single feedback report to a second layer above the first layer of the protocol stack based on the first broadcast type and based on the receipt or absence of one or more feedback messages via the set of multiple feedback monitoring opportunities, the single feedback report indicating a second feedback for the set of multiple feedback monitoring opportunities.

[0009] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first broadcast type may be unicast, and the methods, apparatus, and nontransitory computer-readable media may include further operations, features, components, or instructions for performing the following: receiving a positive acknowledgment message during monitoring at least a first feedback monitoring moment in the set of multiple feedback monitoring moments, wherein reporting the single feedback report includes: reporting a positive acknowledgment based on receiving the positive acknowledgment message after monitoring the set of multiple feedback monitoring moments, wherein the second feedback includes the positive acknowledgment.

[0010] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first broadcast type may be unicast, and the methods, apparatus, and nontransitory computer-readable media may include further operations, features, components, or instructions for performing the following: monitoring the set of multiple feedback monitoring moments for a positive acknowledgment message, wherein reporting the single feedback report includes: after monitoring the set of multiple feedback monitoring moments, reporting a negative acknowledgment based on the absence of the positive acknowledgment message during the monitoring period of the set of multiple feedback monitoring moments, wherein the second feedback includes the negative acknowledgment.

[0011] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first broadcast type may be unicast, and the methods, apparatus, and nontransitory computer-readable media may include further operations, features, components, or instructions for performing the following: receiving a negative acknowledgment message during monitoring at least a first feedback monitoring moment in the set of multiple feedback monitoring moments, wherein reporting the single feedback report includes: reporting a negative acknowledgment based on receiving the negative acknowledgment message after monitoring the set of multiple feedback monitoring moments, wherein the second feedback includes the negative acknowledgment.

[0012] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first broadcast type may be unicast, and the methods, apparatus, and nontransitory computer-readable media may include further operations, features, components, or instructions for performing the following: monitoring the set of multiple feedback monitoring moments for a negative acknowledgment message, wherein reporting the single feedback report includes: after monitoring the set of multiple feedback monitoring moments, reporting a positive acknowledgment based on the absence of the negative acknowledgment message during the monitoring period of the set of multiple feedback monitoring moments, wherein the second feedback includes the positive acknowledgment.

[0013] The methods described herein, some examples of UEs and nontransitory computer-readable media may further include operations, features, components or instructions for performing the following: receiving one or more feedback messages during monitoring of the set of multiple feedback monitoring moments, wherein reporting the single feedback report includes: reporting a positive confirmation or a negative confirmation based on the one or more feedback messages after monitoring the set of multiple feedback monitoring moments, wherein the second feedback includes the positive confirmation or the negative confirmation.

[0014] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first broadcast type may be unicast, and the methods, apparatus, and nontransitory computer-readable media may include further operations, features, components, or instructions for performing the following: receiving a first feedback message during monitoring of a first feedback monitoring moment in the set of multiple feedback monitoring moments, wherein reporting the single feedback report includes: reporting an indication of the first feedback message after the first feedback monitoring moment, based on the first feedback message received during the monitoring period of the first feedback monitoring moment, wherein the second feedback includes the indication.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first feedback message may be an affirmative acknowledgment feedback message, and the indication of the first feedback message includes affirmative acknowledgment.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first broadcast type may be unicast, and the methods, apparatus, and nontransitory computer-readable media may include further operations, features, components, or instructions for performing the following: monitoring the set of multiple feedback monitoring moments for a positive acknowledgment message, wherein reporting the single feedback report includes: after monitoring the set of multiple feedback monitoring moments, reporting a negative acknowledgment based on the absence of the positive acknowledgment message during the monitoring period of the set of multiple feedback monitoring moments, wherein the second feedback includes the negative acknowledgment.

[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first broadcast type may be multicast associated with feedback based solely on negative acknowledgments, and the methods, apparatus, and nontransitory computer-readable media may include further operations, features, components, or instructions for performing the following: monitoring the set of multiple feedback monitoring moments for a negative acknowledgment message, wherein reporting the single feedback report includes: after monitoring the set of multiple feedback monitoring moments, reporting a positive acknowledgment based on the absence of the negative acknowledgment message during the monitoring period of the set of multiple feedback monitoring moments, wherein the second feedback includes the positive acknowledgment.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first broadcast type may be multicast associated with feedback based solely on negative acknowledgment, and the methods, apparatus, and nontransitory computer-readable media may include further operations, features, components, or instructions for receiving a negative acknowledgment message during monitoring of a first feedback monitoring moment in the set of multiple feedback monitoring moments, wherein reporting the single feedback report includes reporting a negative acknowledgment based on receiving the negative acknowledgment message during monitoring of the set of multiple feedback monitoring moments, wherein the second feedback includes the negative acknowledgment.

[0019] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, the negative confirmation may be reported after the set of multiple feedback monitoring events.

[0020] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, the negative confirmation may be reported after the first feedback monitoring opportunity.

[0021] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first broadcast type may be multicast, and the methods, apparatus, and nontransitory computer-readable media may include further operations, features, components, or instructions for performing the following: receiving a positive acknowledgment message associated with each of the one or more second UEs during monitoring of the set of multiple feedback monitoring times, wherein reporting the single feedback report includes: reporting a positive acknowledgment based on receiving the positive acknowledgment message associated with each of the one or more second UEs during monitoring of the set of multiple feedback monitoring times, wherein the second feedback includes the positive acknowledgment.

[0022] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the affirmative confirmation may be reported after the set of multiple feedback monitoring events.

[0023] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the affirmative acknowledgment may be reported after receiving the last affirmative acknowledgment message in the affirmative acknowledgment messages associated with each of the one or more second UEs.

[0024] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first broadcast type may be multicast associated with feedback based on positive and negative acknowledgments, and the methods, apparatus, and nontransitory computer-readable media may include further operations, features, components, or instructions for receiving a negative acknowledgment message during monitoring of a first feedback monitoring moment in the set of multiple feedback monitoring moments, wherein reporting the single feedback report includes reporting a negative acknowledgment based on receiving the negative acknowledgment message during monitoring of the set of multiple feedback monitoring moments, wherein the second feedback includes the negative acknowledgment.

[0025] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, the negative confirmation may be reported after the set of multiple feedback monitoring events.

[0026] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, the negative confirmation may be reported after the first feedback monitoring opportunity.

[0027] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first broadcast type may be multicast associated with feedback based on positive and negative acknowledgments, and the methods, apparatus, and nontransitory computer-readable media may include further operations, features, components, or instructions for performing the following: monitoring the set of multiple feedback monitoring moments for a negative acknowledgment message, wherein reporting the single feedback report includes: after monitoring the set of multiple feedback monitoring moments, reporting a negative acknowledgment based on the absence of the positive acknowledgment message from at least one of the one or more second UEs during the monitoring period of the set of multiple feedback monitoring moments, wherein the second feedback includes the negative acknowledgment. Attached Figure Description

[0028] Figure 1 An example of a wireless communication system supporting feedback reporting for multiple feedback timings, according to one or more aspects of this disclosure, is shown.

[0029] Figure 2 An example of a wireless communication system supporting feedback reporting for multiple feedback timings, according to one or more aspects of this disclosure, is shown.

[0030] Figure 3 An example of a process flow supporting feedback reporting for multiple feedback timings, according to one or more aspects of this disclosure, is shown.

[0031] Figure 4 and Figure 5 A block diagram of an apparatus supporting feedback reporting for multiple feedback times, according to one or more aspects of this disclosure, is shown.

[0032] Figure 6 A block diagram is shown of a communication manager that supports feedback reporting for multiple feedback times, according to one or more aspects of this disclosure.

[0033] Figure 7 A diagram is shown of a system including a device that supports feedback reporting for multiple feedback moments, according to one or more aspects of this disclosure.

[0034] Figure 8 A flowchart illustrating a method for reporting feedback at multiple feedback points, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0035] In some wireless communication systems, a first User Equipment (UE) may send sidelink messages, referred to as PSSCH transmissions, to one (e.g., unicast) or multiple (e.g., multicast) second UEs via a Physical Sidelink Shared Channel (PSSCH) through a first layer of the protocol stack at the first UE. Additionally, one or more second UEs may send a first feedback to the first UE regarding the PSSCH transmission via a Physical Sidelink Feedback Channel (PSFCH), such as an acknowledgment (ACK), a negative acknowledgment (NACK), or neither. In such cases, the first UE may send an indication of the first feedback associated with the PSSCH transmission to a second layer of the protocol stack above the first layer; this may be referred to as second feedback.

[0036] In some examples, PSSCH transmission may be associated with multiple feedback monitoring moments related to PSFCH, which may be referred to as PSFCH moments. Therefore, one or more second UEs may transmit feedback on PSSCH transmissions at one or more of the multiple PSFCH moments. However, due to the multiple PSFCH moments, the first UE may not be able to determine when to transmit a second feedback to the second layer for those multiple PSFCH moments and what to indicate in that second feedback.

[0037] Therefore, the techniques described herein enable a first UE to determine when to send a second feedback to a second layer for multiple PSFCH timings and what is indicated in that second feedback (e.g., ACK or NACK). For example, the first UE may send a PSSCH message to one or more second UEs via a first layer and via PSSCH. In such cases, the PSSCH message may correspond to multiple PSFCH timings, during which the first UE may monitor the first feedback associated with the PSSCH message. Additionally, the PSSCH message may be associated with a broadcast type among multiple broadcast types, including at least unicast, multicast associated with feedback based on NACK only, and multicast associated with feedback based on both NACK and ACK. Thus, the UE may monitor the first feedback during at least one PSFCH timing.

[0038] Additionally, the first UE may send a single feedback report to the second layer, indicating a second feedback associated with multiple PSFCH timings. The second feedback and its transmission time may be based on the broadcast type of the PSSCH message and on the receipt or absence of one or more feedback messages (e.g., including the first feedback sent for the PSSCH) via multiple PSFCH timings (e.g., via at least one PSFCH timing). For example, the second feedback (e.g., and its transmission time) may be based on a rule associated with the broadcast type, where the rule indicates one or more conditions under which the first UE may send the second feedback. In such cases, the rule may be further based on whether the first feedback associated with the PSSCH message during at least one PSFCH timing includes one or more ACK messages, one or more NACK messages, or both, or whether it includes the absence of one or more ACK messages, one or more NACK messages, or both.

[0039] The aspects of this disclosure are first described in the context of a wireless communication system. Then, the aspects of this disclosure are described in the context of a process flow. The aspects of this disclosure are further illustrated, and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to feedback reporting for multiple feedback opportunities.

[0040] Figure 1An example of a wireless communication system 100 supporting feedback reporting for multiple feedback timings according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0041] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, among other designations. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0042] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0043] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0044] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0045] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that 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 base station 140).

[0046] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across 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)). For example, network entity 105 may include one or more of the following: 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, a non-real-time RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0047] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can 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 each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0048] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0049] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support feedback reporting for multiple feedback timings as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0050] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0051] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0052] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a physical layer structure defined for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to utilize multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0053] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0054] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0055] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0056] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0057] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region of the physical control channel (e.g., a control resource set (CORESET)) can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0058] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with network entity 105 (e.g., using a carrier) and may be associated with an identifier used to distinguish neighboring cells (e.g., a Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other cell identifier). In some examples, a cell may also refer to...

[0059] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, 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. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0060] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices 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 geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0061] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private 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 business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0062] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0063] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may signal information related to traffic conditions, signaling, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0064] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0065] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the region from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range is 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 these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer waves in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0066] Wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be combined with component carriers operating with licensed frequency bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0067] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly such as an antenna tower. In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0068] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0069] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reassembly for transmission via logical channels. The MAC layer can perform priority handling and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer can map transport channels to physical channels.

[0070] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0071] The wireless communication system 100 may support techniques for a first UE 115 to determine when to send a second feedback to a second layer for multiple PSFCH timings and what is indicated in the second feedback (e.g., ACK or NACK). For example, the first UE 115 may send a PSSCH message to one or more second UEs 115 via a first layer and via PSSCH. In such a case, the PSSCH message may correspond to multiple PSFCH timings, during which the first UE 115 may monitor a first feedback associated with the PSSCH message. Additionally, the PSSCH message may be associated with a broadcast type among multiple broadcast types, including unicast, multicast associated with feedback based on NACK only, and multicast associated with feedback based on both NACK and ACK. Therefore, the UE 115 may monitor the first feedback during at least one PSFCH timing.

[0072] Additionally, the first UE 115 may send a single feedback report to the second layer, indicating a second feedback associated with multiple PSFCH timings. The second feedback, and the timing of its transmission, may be based on the broadcast type of the PSSCH message and on the receipt or absence of one or more feedback messages via multiple PSFCH timings (e.g., via at least one PSFCH timing). For example, the second feedback (and its transmission timing) may be based on a rule associated with the broadcast type, wherein the rule indicates one or more conditions under which the first UE may transmit the second feedback. In such cases, the rule may be further based on whether the first feedback associated with the PSSCH message during at least one PSFCH timing includes one or more ACK messages, one or more NACK messages, or both, or whether it includes the absence of one or more ACK messages, one or more NACK messages, or both.

[0073] Figure 2 An example of a wireless communication system 200 supporting feedback reporting for multiple feedback timings according to one or more aspects of this disclosure is shown. In some cases, the wireless communication system 200 may implement or be implemented by aspects of the wireless communication system 100. For example, the wireless communication system 200 may include one or more UEs 115 (e.g., UE115-a, UE 115-b, and UE 115-c) and one or more network entities 105, which may be examples of corresponding devices as described herein.

[0074] In some wireless communication systems (such as wireless communication system 200), a first UE 115 (such as UE 115-a) may send a sidelink message via PSSCH to one (e.g., unicast) or multiple (e.g., multicast) second UE 115s (such as UE 115-b, UE 115-c, or both). This sidelink message may be referred to as PSSCH message 210 (e.g., it may be associated with PSCCH message 205). In such cases, PSSCH message 210 may be sent via the first layer of the protocol stack at UE 115. For example, as referenced... Figure 1 As described, the protocol stack at UE 115-a may include RRC layer 220, PDPC layer 225, RLC layer 230, MAC layer 235, and PHY layer 240. Therefore, UE 115-a can send PSSCH message 210 via PHY layer 240.

[0075] Additionally, UE 115-b, UE 115-c, or both may send a first feedback to UE 115-a regarding PSSCH message 210 during a feedback timing associated with PSSCH. In such a case, UE 115-a may send a report 245 indicating the first feedback associated with PSSCH message 210 to a second layer above the first layer of the protocol stack (such as MAC layer 235). That is, report 245 may indicate feedback information (e.g., HARQ-ACK information, second feedback), such as ACK or NACK, based on the first feedback to PSSCH message 210.

[0076] For example, a first rule (e.g., for unicast) may instruct that, for each PSFCH timing 215, UE 115-a will report feedback information to MAC layer 235, which indicates the same value (e.g., ACK or NACK) as the feedback information associated with the corresponding PSFCH timing 215 (e.g., the value of the HARQ-ACK information determined by UE 115-a from PSFCH timing 215). Additionally, the first rule may be associated with a first control message format (e.g., SCI format 2-A) based on the PSCCH message 205 corresponding to the corresponding PSFCH timing 215 and instruct unicast based on the PSCCH message 205 (e.g., a broadcast type indicator field value indicating "10") or associated with a second control message format (e.g., SCI format 2-C) based on the PSCCH message 205.

[0077] For example, UE 115-a may send a unicast PSSCH message 210 to UE 115-b, wherein the unicast PSSCH message 210 is associated with a PSCCH message 205, which is further associated with a first control message format or a second control message format, and wherein the unicast PSCCH message 205 corresponds to PSFCH timing 215. In some examples, as depicted in Table 1, UE 115-b may send a feedback message indicating an ACK to UE 115-a during PSFCH timing 215-a. Therefore, UE 115-a may report the ACK associated with PSFCH timing 215-a to MAC layer 235. UE 115-a may clear the feedback buffer (e.g., a HARQ buffer) based on reporting the ACK to MAC layer 235. Table 1: Unicast PSSCH message 210, Scenario 1

[0078] In another example, as depicted in Table 2, UE 115-b may send a first feedback message indicating NACK to UE 115-a during PSFCH timing 215-a. Therefore, UE 115-a may report the NACK associated with PSFCH timing 215-a to MAC layer 235 and may retransmit the unicast PSSCH message 210 (e.g., trigger a new transmission) based on reporting the NACK to MAC layer 235. Additionally, UE 115-b may send a second feedback message indicating ACK to UE 115-a during PSFCH timing 215-b. Therefore, UE 115-a may report the ACK associated with PSFCH timing 215-b to MAC layer 235. Table 2: Unicast PSSCH message 210, Scenario 2

[0079] Additionally or alternatively, a second rule (e.g., for multicast associated with feedback based on NACK only) may instruct that, for each PSFCH timing 215, if UE 115-a determines that there is no feedback associated with the corresponding PSFCH timing 215 (e.g., no NACK) (e.g., no PSFCH reception for the corresponding PSFCH timing 215), then UE 115-a will report an ACK to MAC layer 235. Otherwise, UE 115-a may report a NACK to MAC layer 235. Additionally, the second rule may be associated with a first control message format (e.g., SCI format 2-A) based on the PSCCH message 205 corresponding to the corresponding PSFCH timing 215 and indicating multicast type 1 based on the PSCCH message 205 (e.g., a broadcast type indicator field value indicating "11") or associated with a third control message format (e.g., SCI format 2-B) based on the PSCCH message 205. Multicast type 1 may be multicast associated with feedback based on NACK only.

[0080] For example, UE 115-a may send a multicast type 1 PSSCH message 210 to UE 115-b and UE 115-c, wherein the multicast type 1 PSSCH message 210 is associated with a PSCCH message 205, which is further associated with a first control message format or a third control message format, and wherein the multicast type 1 PSCCH message 205 corresponds to PSFCH timing 215. In some examples, as depicted in Table 3, UE 115-b and UE 115-c may avoid sending feedback messages to UE 115-a during PSFCH timing 215-a associated with the first transmission of PSSCH message 210. In other words, one or more feedback messages (e.g., indications of feedback information) may not exist in PSFCH timing 215-a. Therefore, UE 115-a may report an ACK associated with PSFCH timing 215-a to MAC layer 235. Table 3: Multicast Type 1 PSSCH Message 210, Scenario 1

[0081] In another example, as depicted in Table 4, at least one of UE 115-b and UE 115-c may send a first feedback message indicating NACK to UE 115-a during PSFCH timing 215-a. Therefore, UE 115-a may report the NACK associated with PSFCH timing 215-a to MAC layer 235 and may retransmit multicast type 1 PSSCH message 210. Additionally, UE 115-b and UE 115-c may avoid sending feedback messages to UE 115-a during a second transmission of PSFCH message 215-b associated with PSSCH message 210. In other words, one or more feedback messages (e.g., feedback indication information) may not be present during PSFCH timing 215-b. Therefore, UE 115-a may report the ACK associated with PSFCH timing 215-b to MAC layer 235. Table 4: Multicast Type 1 PSSCH Message 210, Scenario 2

[0082] Additionally or alternatively, a third rule (e.g., for multicast associated with ACK and NACK-based feedback) may instruct UE 115-a to report a NACK to MAC layer 235 for each PSFCH timing 215 until UE 115-a receives an ACK corresponding to each UE 115 associated with PSSCH message 210. In other words, UE 115-a may, based on each identifier of UE 115 (e.g., UE 115-b and UE 115-c) that UE 115-a expects to receive the corresponding PSSCH message 210, [e.g., ...]. The UE 115-a determines an ACK value to report an ACK based on at least one of the multiple PSFCH timings 215 in the corresponding feedback resource (e.g., PSFCH resource). Otherwise, the UE 115-a may report a NACK to the MAC layer 235. Additionally, a third rule may be based on the PSCCH message 205 corresponding to the corresponding PSFCH timing 215, associated with a first control message format (e.g., SCI format 2-A), and based on the PSCCH message 205 indicating multicast type 2 (e.g., a broadcast type indicator field value indicating "01"). Multicast type 2 may be a multicast associated with feedback based on ACK and NACK.

[0083] For example, UE 115-a may send a multicast type 2 PSSCH message 210 to UE 115-b, UE 115-c, and the additional UE 115, wherein the multicast type 2 PSSCH message 210 is associated with a PSCCH message 205 further associated with a first control message format, and wherein the multicast type 2 PSCCH message 205 corresponds to PSFCH timing 215. In some examples, as depicted in Table 5, during PSFCH timing 215-a, UE 115-b may send an ACK, and UE 115-c and the additional UE 115 may send a NACK. Therefore, UE 115-a may report the NACK associated with PSFCH timing 215-a to MAC layer 235 and may retransmit the multicast type 2 PSSCH message 210. Additionally, during the PSFCH timing 215-b associated with the second transmission of PSSCH message 210, UE 115-b may avoid sending feedback information (e.g., based on an already sent ACK), UE 115-c may send an ACK, and the feedback transmission by the additional UE 115 may fail (e.g., UE 115-a fails to decode the feedback transmission). Therefore, UE 115-a may report the NACK associated with PSFCH timing 215-b to MAC layer 235 and may retransmit multicast type 2 PSSCH message 210. Additionally, during the PSFCH timing 215-c associated with the third transmission of PSSCH message 210, UE 115-b and UE 115-c may avoid sending feedback information (e.g., based on an already sent ACK), and the additional UE 115 may send an ACK. Therefore, UE 115-a may report the ACK associated with PSFCH timing 215-c to MAC layer 235. Table 5: Multicast Type 2 PSSCH Message 210, Scenario 1

[0084] In some examples, PSSCH message 210 may be associated with multiple feedback opportunities related to PSFCH, which may be referred to as PSFCH opportunities 215 (e.g., PSFCH reception opportunity, PSFCH monitoring opportunity, candidate PSFCH opportunity). PSFCH opportunity 215 may be a set of available time and frequency resources on which UE 115-b, UE 115-c, or both may send feedback information (e.g., one or more feedback messages) for PSSCH message 210. For example, PSSCH message 210 may (e.g., via pre-configuration) be associated with (e.g., corresponding to) NThere are PSFCH timings 215, such as PSFCH timing 215-a, PSFCH timing 215-b, PSFCH timing 215-c, and PSFCH timing 215-d, among which N The value range can include at least {1, 2, 3, 4}. In some examples (e.g., N >1), used for the first PSSCH message 210 (e.g., or the first PSCCH message 205) N The first set of PSFCH timings 215 can be used with the second PSSCH message 210 (e.g., or the second PSCCH message 205). N The second set of PSSCH events 215 is associated with different time resources, frequency resources, or both. In such cases, the first PSSCH message 210 and the second PSSCH message 210 may (e.g., in the time domain, frequency domain, or both) be associated with non-overlapping resources. In other words, the first set of resources associated with the first PSSCH message 210 may not overlap with the second set of resources associated with the second PSSCH message 210.

[0085] Therefore, UE 115-b, UE 115-c, or both can be used at multiple PSFCH times 215 (e.g., N A first feedback message for PSSCH message 210 may be sent (e.g., or avoided) during one or more PSSCH opportunities (215 of the multiple PSSCH opportunities). That is, UE 115-b and UE 115-c may send one or more feedback messages for PSSCH message 210 via PSSCHs associated with the multiple PSSCH opportunities 215, the feedback messages indicating ACK (e.g., ACK message) or NACK (e.g., NACK message). In some cases, UE 115-a may generate feedback information for each of the multiple PSSCH opportunities 215 and report this feedback information to MAC layer 235. In other words, each of the multiple PSSCH opportunities 215 may be associated with a report 245. In such cases, UE 115-a can generate feedback information for each PSFCH timing 215 based on the format of the PSCCH message 205 associated with the corresponding PSFCH timing 215 (e.g., the side link control information (SCI) format).

[0086] However, UE 115-b and UE 115-c may follow one or more additional rules for reporting feedback information in one or more PSFCH timings 215, and UE 115-a may not know which of these additional rules UE 115-b and UE 115-c follow. For example, in some cases, UE 115-b, UE 115-c, or both (e.g., PSSCH message 210 receiver or PSCCH message 205 receiver) may attempt to send feedback information for PSSCH message 210 (e.g., or PSCCH message 205) on PSFCH timing 215 among multiple PSFCH timings 215 because UE 115-b, UE 115-c, or both failed to send feedback information on a previous candidate PSFCH timing 215 among multiple PSFCH timings 215 due to (e.g., a failure of the Listen-After-Speak (LBT) procedure associated with a feedback message including feedback information). In some other examples, UE 115-b, UE 115-c, or both may attempt to send feedback information for PSSCH message 210 on PSSCH time slot 215 among multiple PSSCH time slots 215, based on the failure of the LBT procedure or the uplink or sidelink priority ordering (e.g., sending sidelink or uplink messages based on associating them with a higher priority than feedback information). In some other examples, UE 115-b, UE 115-c, or both may select which PSSCH time slot among multiple PSSCH time slots 215 to send feedback information (e.g., the behavior of UE 115 sending feedback information due to the failure of the LBT procedure may depend on the implementation of UE 115). Therefore, since there are multiple PSFCH timings 215 and UE 115-a does not know how UE 115-b and UE 115-c send feedback, UE 115-a may not be able to determine when to send feedback information to MAC layer 235 for multiple PSFCH timings 215 and what to indicate in that feedback information.

[0087] For example, in the case where UE 115-a sends a unicast PSSCH message 210 to UE 115-b and UE 115-b successfully receives the unicast PSSCH message 210, UE 115-b may send an ACK on the first PSFCH timing 215 where the LBT process is successful (LBT passes) or on each PSFCH timing 215 where the LBT process is successful. Therefore, in some cases, due to unnecessary reporting 245 (e.g., reporting 245 for each PSFCH timing 215), UE 115-a reporting an ACK for each PSFCH timing 215 to the MAC layer 235 may lead to inefficient resource utilization and power consumption. Conversely, for a unicast PSSCH message 210 in which UE 115-a sends a unicast PSSCH message 210 to UE 115-b and UE 115-b fails to receive or decode the unicast PSSCH message 210, UE 115-b may send a NACK on the first PSFCH timing 215 in which the LBT process succeeds or on every PSFCH timing 215 in which the LBT process succeeds. Therefore, in some cases, UE 115-a reporting a NACK to the MAC layer 235 for every PSFCH timing 215 may lead to inefficient resource utilization and power consumption due to unnecessary retransmissions triggered by reporting a NACK for each PSFCH timing 215.

[0088] In another example, for a multicast type 1 PSSCH message 210, UE 115-a may send multicast type 1 PSSCH message 210 to UE 115-b and UE 115-c. Additionally, UE 115-b may successfully receive multicast type 2 PSSCH message 210 and may avoid sending feedback information during the first PSFCH timing 215. Conversely, UE 115-c may fail to receive multicast type 2 PSSCH message 210 and may attempt to send NACK during the first PSFCH timing 215; however, the NACK transmission may fail due to LBT procedure failure (e.g., LBT failure). Therefore, UE 115-a may report ACK to MAC layer 235 based on the failure to include feedback information during the first PSFCH timing 215, and UE 115-a may clear the feedback buffer before UE 115-c successfully receives multicast type 2 message 210.

[0089] In another example, for a multicast type 2 PSSCH message 210, UE 115-a may send the multicast type 2 PSSCH message 210 to UE 115-b and UE 115-c. Additionally, UE 115-b may successfully receive the multicast type 2 PSSCH message 210 and send an ACK during the first PSFCH timing 215. Similarly, UE 115-c may successfully receive the multicast type 2 PSSCH message 210 and may attempt to send an ACK during the first PSFCH timing 215; however, due to a failure of the LBT process (e.g., LBT failure), the transmission of the ACK may fail. Therefore, UE 115-a may report a NACK to MAC layer 235 based on the failure of the first PSFCH timing 215 to include feedback information from UE 115-c. Consequently, UE 115-a may retransmit the multicast type 2 PSSCH message 210, which may result in inefficient resource utilization and power consumption due to unnecessary retransmission triggered by reporting a NACK to MAC layer 235.

[0090] Therefore, the techniques described herein enable UE 115-a to determine when to send a single report 245 to MAC layer 235 (or other higher layers in the protocol stack) for multiple PSFCH timings 215 and what to indicate in the single report 245 (e.g., ACK or NACK).

[0091] For example, UE 115-a may send a unicast PSSCH message 210 corresponding to multiple PSSCH times 215 to UE 115-b, and UE 115-b may send feedback for the unicast PSSCH message 210 in one or more of the multiple PSSCH times 215. In some examples, UE 115-a may include in a single report 245 the same value (e.g., ACK or NACK) as the value of the feedback information associated with the multiple PSSCH times 215 (e.g., the value of the HARQ-ACK information determined by UE 115-a from the multiple PSSCH times 215). In some cases, according to a first unicast implementation, UE 115-a may generate an ACK to be included in a single report 245 based on receiving at least one ACK in the multiple PSSCH times 215 and may report the ACK after the multiple PSSCH times 215. Otherwise, UE 115-a may send a NACK. For example, as depicted in Table 6, UE 115-a can identify the absence of feedback information during the monitoring period of PSFCH timing 215-a, and thus avoid sending report 245 to MAC layer 235. However, UE 115-a can receive ACK during the monitoring period of PSFCH timing 215-b, and thus can send report 245 indicating ACK to MAC layer 235 after multiple PSFCH timings 215-d. Conversely, as depicted in Table 7, UE 115-a can identify the absence of feedback information during the monitoring period of PSFCH timing 215-a, and thus avoid sending report 245 to MAC layer 235. However, UE 115-a can receive NACK during the monitoring period of PSFCH timing 215-b, and thus can send report 245 indicating NACK to MAC layer 235 after multiple PSFCH timings 215-d.

[0092] In the second unicast implementation, UE 115-a may generate a NACK to be included in a single report 245 based on receiving at least one NACK during multiple PSFCH timings 215. Otherwise, UE 115-a may send an ACK. For example, as depicted in Table 6, UE 115-a may identify the absence of feedback information during the monitoring period of PSFCH timing 215-a, and thus avoid sending report 245 to MAC layer 235. However, UE 115-a may receive an ACK during the monitoring period of PSFCH timing 215-b, and thus may send report 245 indicating an ACK to MAC layer 235 after multiple PSFCH timings 215-d. Conversely, as depicted in Table 7, UE 115-a may identify the absence of feedback information during the monitoring period of PSFCH timing 215-a, and thus avoid sending report 245 to MAC layer 235. However, UE 115-a may receive NACK during the monitoring of PSFCH timing 215-b, and therefore may send a report 245 to MAC layer 235 after multiple PSFCH timings 215-d, the report 245 indicating NACK.

[0093] In the third unicast implementation, UE 115-a can generate an ACK or NACK to be included in a single report 245 based on a logical OR operation, which is based on feedback information received at multiple PSFCH times. For example, as depicted in Table 6, UE 115-a can identify the absence of feedback information during the monitoring period of PSFCH time 215-a and can receive an ACK during the monitoring period of PSFCH time 215-b. Therefore, after multiple PSFCH times 215, UE 115-a can determine, based on a logical OR operation, to send a report 245 indicating an ACK to the MAC layer 235. Conversely, as depicted in Table 7, UE 115-a can identify the absence of feedback information during the monitoring period of PSFCH time 215-a and can receive a NACK during the monitoring period of PSFCH time 215-b. Therefore, after multiple PSFCH times 215, UE 115-a can send a report 245 indicating a NACK to the MAC layer 235 based on a logical OR operation.

[0094] Additionally or alternatively, according to the fourth unicast implementation, UE 115-a may include in a single report 245 the same value (e.g., ACK or NACK) as the feedback information of the first PSFCH reception time among multiple PSFCH times 215, and may report this same value after the first PSFCH reception time. That is, the first PSFCH reception time may be the earliest PSFCH time 215 in which feedback information associated with the unicast PSSCH message 210 is received (e.g., PSFCH time 215-b in Tables 6 and 7). For example, as depicted in Table 6, UE 115-a may identify the absence of feedback information during the monitoring of PSFCH time 215-a, and thus avoid sending report 245 to MAC layer 235. However, UE 115-a may receive ACK during the monitoring of PSFCH time 215-b, and thus may send report 245 indicating ACK to MAC layer 235 after PSFCH time 215-b. Conversely, as depicted in Table 7, UE 115-a can identify the absence of feedback information during the monitoring of PSFCH timing 215-a, and thus avoid sending report 245 to MAC layer 235. However, UE 115-a can receive NACK during the monitoring of PSFCH timing 215-b, and thus can send report 245 to MAC layer 235 after PSFCH timing 215-b, with report 245 indicating NACK.

[0095] Additionally or alternatively, according to the fifth unicast implementation, UE 115-a may include an ACK in a single report 245 based on receiving an ACK during the first PSFCH reception period among multiple PSFCH periods 215, and may report the ACK after the first PSFCH reception period. Conversely, UE 115-a may include a NACK in a single report 245 based on the absence of an ACK during multiple PSFCH periods 215, and may report the NACK after the last PSFCH period 215 among multiple PSFCH periods 215 (e.g., PSFCH period 215-d in Tables 6 and 7). For example, as depicted in Table 6, UE 115-a may identify the absence of feedback information during the monitoring period of PSFCH period 215-a, and thus avoid sending report 245 to MAC layer 235. However, UE 115-a may receive an ACK during the monitoring period of PSFCH period 215-b, and thus may send report 245 indicating an ACK to MAC layer 235 after PSFCH period 215-b. Conversely, as depicted in Table 7, UE 115-a may identify the absence of feedback information during the monitoring of each of PSFCH timings 215-a, 215-b, 215-c, and 215-d, and thus may send a report 245 to MAC layer 235 after multiple PSFCH timings 215-d, the report 245 indicating NACK.

[0096] In the context of Tables 6 and 7, PSFCH timing 215-a can be associated with LBT failure, and PSFCH timings 215-b, 215-c, and 215-d can be associated with LBT success. In other words, UE 115-b may be unable to send feedback during PSFCH timing 215-a due to LBT failure. Table 6: Unicast PSSCH Message 210 Feedback Report, Scenario 1 Table 7: Unicast PSSCH Message 210 Feedback Report, Scenario 2

[0097] In another example, UE 115-a may send multicast type 1 PSSCH messages 210 corresponding to multiple PSFCH times 215 to UE 115-b and UE 115-c, and UE 115-b, UE 115-c or both may send feedback on the multicast type 1 PSSCH messages 210 in one or more of the multiple PSFCH times 215.

[0098] In some cases, according to the first multicast type 1 implementation, UE 115-a may generate an ACK to be included in a single report 245 based on the absence of a NACK during multiple PSFCH timings 215 (e.g., based on the absence of PSFCH reception for multiple PSFCH timings 215). For example, as depicted in Table 8, UE 115-b and UE 115-c may avoid sending NACKs during multiple PSFCH timings 215, and therefore UE 115-a may send a report 245 indicating an ACK to MAC layer 235 after multiple PSFCH timings 215. Table 8: Multicast Type 1 PSSCH Message 210 Feedback Report, Scenario 1

[0099] Additionally or alternatively, UE 115-a may generate a NACK to be included in a single report 245 based on receiving at least one NACK during multiple PSFCH timings. In some cases, according to the second multicast type 1 implementation, UE 115-a may generate a NACK to be included in a single report after multiple PSFCH timings 215 (e.g., after the last PSFCH timing 215 of the multiple PSFCH timings 215). For example, as depicted in Table 9, UE 115-b may avoid sending a NACK during multiple PSFCH timings 215, and UE 115-c may send a NACK during PFSCH timing 215-c. Therefore, UE 115-a may send a report 245 indicating a NACK to MAC layer 235 after multiple PSFCH timings 215.

[0100] In some other cases, according to the third multicast type 1 implementation, UE 115-a may generate a NACK to be included in a single report after the first PSFCH timing 215 among multiple PSFCH timings 215, where the first PSFCH timing 215 is the first PSFCH reception timing (e.g., first PSFCH timing 215) in which a NACK associated with a multicast type 1 PSSCH message 210 is received. For example, as depicted in Table 9, UE 115-b may avoid sending a NACK during multiple PSFCH timings 215, and UE 115-c may send a NACK during PFSCH timing 215-c. Therefore, UE 115-a may send a report 245 indicating a NACK to MAC layer 235 after PSFCH timing 215-c. Table 9: Multicast Type 1 PSSCH Message 210 Feedback Report, Scenario 2

[0101] In another example, UE 115-a may send multicast type 2 PSSCH messages 210 corresponding to multiple PSFCH times 215 to UE 115-b and UE 115-c, and UE 115-b, UE 115-c or both may send feedback on multicast type 2 PSSCH messages 210 in one or more of the multiple PSFCH times 215.

[0102] For example, UE 115-a may be based on each of UE 115-b and UE 115-c during multiple PSFCH timings 215 (e.g., each identity of UE 115). UE 115-a receives at least one ACK to generate an ACK to be included in a single report 245. In some cases, depending on the first multicast type 2 implementation, UE 115-a may generate an ACK to be included in a single report after multiple PSFCH timings 215 (e.g., after the last PSFCH timing 215 of multiple PSFCH timings 215). For example, as depicted in Table 10, UE 115-b may send an ACK during PSFCH timing 215-a, and UE 115-c may send an ACK during PSFCH timing 215-c. Therefore, UE 115-a may send a report 245 indicating an ACK to MAC layer 235 after multiple PSFCH timings.

[0103] In some other cases, according to the second multicast type 2 implementation, UE 115-a may generate an ACK to be included in a single report after the latest PSFCH timing 215 among multiple PSFCH timings 215, where the latest PSFCH timing 215 is the last PSFCH reception timing (e.g., the last PSFCH timing 215) from which the last UE 115 (e.g., UE 115-b and UE 115-c) receives the ACK associated with the multicast type 2 PSSCH message 210. For example, as depicted in Table 10, UE 115-b may send an ACK during PSFCH timing 215-a, however, UE 115-c may not send an ACK until PSFCH timing 215-c. Therefore, UE 115-a may send a report 245 indicating an ACK to MAC layer 235 after PSFCH timing 215-c. Table 10: Multicast Type 2 PSSCH Message 210 Feedback Report, Scenario 1

[0104] Additionally or alternatively, UE 115-a may generate a NACK to be included in a single report 245 based on receiving at least one NACK from at least one UE 115 (e.g., UE 115-b and UE 115-c, which are expected to receive multicast type 2 PSSCH messages 210) during multiple PSFCH timings. In some cases, according to a third multicast type 2 implementation, UE 115-a may generate a NACK to be included in a single report after multiple PSFCH timings 215 (e.g., after the last PSFCH timing 215 among multiple PSFCH timings 215) based on receiving at least one NACK from at least one UE 115 during multiple PSFCH timings 215. For example, as depicted in Table 11, UE 115-b may send an ACK during PSFCH timing 215-a, however, UE 115-c may send a NACK during PSFCH timing 215-c. Therefore, UE 115-a may send a report 245 indicating a NACK to the MAC layer 235 after multiple PSFCH timings 215 based on receiving a NACK from UE 115-c. Conversely, as depicted in Table 12, UE 115-b may send an ACK during PSFCH timing 215-a; however, (e.g., due to LBT failure) UE 115-c may not be able to send a NACK during each of the multiple PSFCH timings 215. Therefore, UE 115-a may suppress sending a report 245 to the MAC layer 235 after multiple PSFCH timings 215 based on failing to receive a NACK during multiple PSFCH timings 215.

[0105] In some other cases, according to the fourth multicast type 2 implementation, UE 115-a may generate a NACK to be included in a single report after a first PSFCH timing 215 among the multiple PSFCH timings 215, based on receiving at least one NACK from at least one UE 115 during multiple PSFCH timings 215, wherein the first PSFCH timing 215 is the first PSFCH reception timing (e.g., first PSFCH timing 215) in which a NACK associated with a multicast type 2 PSSCH message 210 is received from at least one UE 115. For example, as depicted in Table 11, UE 115-b may send an ACK during PSFCH timing 215-a, however, UE 115-c may send a NACK during PSFCH timing 215-c. Therefore, UE 115-a may send a report 245 indicating a NACK to MAC layer 235 after receiving a NACK from UE 115-c. Conversely, as depicted in Table 12, UE 115-b may send an ACK during PSFCH timing 215-a; however, (e.g., due to LBT failure) UE 115-c may not be able to send a NACK during each of the multiple PSFCH timings 215. Therefore, UE 115-a may suppress the transmission of report 245 to MAC layer 235 after multiple PSFCH timings 215 based on the failure to receive a NACK during multiple PSFCH timings 215.

[0106] In some other cases, according to the fifth multicast type 2 implementation, UE 115-a may generate a NACK to be included in a single report 245 based on the absence of an ACK from at least one UE 115 (e.g., UE 115-b and UE 115-c, which are expected to receive multicast type 2 PSSCH messages 210) during multiple PSFCH times 215, and may report the NACK after the last PSFCH time 215 of the multiple PSFCH times 215. For example, as depicted in Table 11, UE 115-b may send an ACK during PSFCH time 215-a, however, UE 115-c may send a NACK during PSFCH time 215-c. Therefore, UE 115-a may send a report 245 indicating a NACK to the MAC layer 235 after multiple PSFCH times 215 based on the failure to receive an ACK from UE 115-c (e.g., receiving a NACK from UE 115-c). Similarly, as depicted in Table 12, UE 115-b may send an ACK during PSFCH timing 215-a; however, (e.g., due to LBT failure) UE 115-c may not be able to send a NACK during each of the multiple PSFCH timings 215. Therefore, UE 115-a may send a report 245 indicating a NACK to MAC layer 235 after multiple PSFCH timings 215 based on the failure to receive an ACK from UE 115-c. Table 11: Multicast Type 2 PSSCH Message 210 Feedback Report, Scenario 2 Table 12: Multicast Type 2 PSSCH Message 210 Feedback Report, Scenario 3

[0107] Although described in the context of sidelink communication between UE 115-a, UE 115-b, and UE 115-c, this should not be construed as limiting the scope of this disclosure. In this respect, UE 115-a may communicate with any number of UE 115s, including a single UE 115 or multiple UE 115s. Additionally, although described in the context of multiple implementations for each broadcast type (e.g., unicast, multicast type 1, and multicast type 2), these implementations should not be considered exclusive, and any combination of implementations may be considered in relation to the techniques described herein.

[0108] Figure 3An example of a process flow 300 supporting feedback reporting for multiple feedback timings according to one or more aspects of this disclosure is shown. In some cases, process flow 300 may be implemented by or by aspects of wireless communication system 100, wireless communication system 200, or both. For example, process flow 300 may include one or more UEs 115 (e.g., UE 115-d, UE 115-e, and UE 115-f) and one or more network entities 105, which may be examples of corresponding devices as described herein.

[0109] At 305, UE 115-d may send sidelink messages (e.g., PSSCH messages) from the first layer of the protocol stack at UE 115-d (e.g., the PHY layer) and via a sidelink shared channel (e.g., PSSCH) to UE 115-e, UE 115-f, or both. The sidelink message may correspond to multiple feedback monitoring opportunities (e.g., PSFCH monitoring opportunity, PSFCH opportunity, PSFCH reception opportunity) for a first feedback associated with that sidelink message. Additionally, the sidelink message may belong to a first broadcast type among multiple broadcast types, including at least unicast, multicast associated with feedback based on NACK only (which may be referred to as multicast type 1), and multicast associated with feedback based on both NACK and ACK (which may be referred to as multicast type 2).

[0110] In some cases, at 310, UE 115-d can monitor a first feedback associated with a sidelink message (e.g., via one or more feedback messages), where the first feedback may include ACK (e.g., ACK message) or NACK (e.g., NACK message).

[0111] In some examples, the first broadcast type may be unicast, and UE 115-d may receive an ACK from UE 115-e at 315 during the monitoring of at least the first feedback timing among multiple feedback timings. Therefore, at 320, UE 115-d may report an ACK to a layer higher than layer one in the protocol stack (e.g., the MAC layer) based on receiving an ACK from UE 115-e after monitoring multiple feedback monitoring timings. Conversely, there may be no ACK among the multiple feedback timings, allowing UE 115-d to report a NACK to the layer two after monitoring multiple feedback monitoring timings based on the absence of an ACK during those multiple feedback monitoring timings.

[0112] In some other examples, the first broadcast type may be unicast, and UE 115-d may receive a NACK from UE 115-e at 315 during the monitoring period of at least the first feedback timing among multiple feedback timings. Therefore, at 320, UE 115-d may report a NACK to Layer 2 based on receiving a NACK from UE 115-e after monitoring multiple feedback monitoring timings. Conversely, there may be no NACK among the multiple feedback timings, allowing UE 115-d to report an ACK to Layer 2 after monitoring multiple feedback monitoring timings based on the absence of a NACK during the multiple feedback monitoring timings.

[0113] In some other examples, the first broadcast type may be unicast, and UE 115-d may receive ACK or NACK from UE 115-e during the monitoring period of at least the first feedback timing among multiple feedback timings at 315. Therefore, at 320, UE 115-d may report ACK or NACK to the second layer based on receiving ACK or NACK from UE 115-e (e.g., based on a logical OR operation) after monitoring multiple feedback monitoring timings.

[0114] In some other examples, the first broadcast type may be unicast, and UE 115-d may receive ACK or NACK from UE 115-e during the monitoring of the first feedback timing among multiple feedback timings at 315. Therefore, at 320, UE 115-d may report ACK or NACK to Layer 2 based on receiving ACK or NACK from UE 115-e respectively after the first feedback monitoring timing. In some examples, ACK may not be present in the multiple feedback timings, such that UE 115-d may report NACK to Layer 2 after monitoring multiple feedback monitoring timings based on the absence of ACK during the multiple feedback monitoring timings. Conversely, in some examples, NACK may not be present in the multiple feedback timings, such that UE 115-d may report ACK to Layer 2 after monitoring multiple feedback monitoring timings based on the absence of NACK during the multiple feedback monitoring timings.

[0115] In some other examples, the first broadcast type may be multicast (e.g., type 1 or type 2), and UE 115-d may receive a NACK from UE 115-e at 315 during the monitoring of at least the first feedback timing among multiple feedback timings. Therefore, at 320, UE 115-d may report a NACK to Layer 2 based on receiving a NACK from UE 115-e. In some examples, UE 115-d may report a NACK after monitoring multiple feedback monitoring timings. In some other examples, UE 115-d may report a NACK after the first feedback monitoring timing.

[0116] In some other examples, the first broadcast type may be multicast (e.g., type 1 or type 2), and UE 115-d may receive ACKs from each of UE 115-e and UE 115-f at 315 during the monitoring period of at least the first feedback timing among multiple feedback timings. Therefore, at 320, UE 115-d may report an ACK to Layer 2 based on receiving an ACK from each of UE 115-e and UE 115-f. In some examples, UE 115-d may report an ACK after monitoring multiple feedback monitoring timings. In some other examples, UE 115-d may report an ACK after the first feedback monitoring timing.

[0117] In some other examples, the first broadcast type may be multicast type 2, and UE 115-d may receive a NACK from at least one of UE 115-e and UE 115-f during the monitoring period of at least the first feedback timing among multiple feedback timings at 315. Therefore, at 320, UE 115-d may report a NACK to Layer 2 based on receiving a NACK from at least one of UE 115-e and UE 115-f. In some examples, UE 115-d may report a NACK after monitoring multiple feedback monitoring timings. In some other examples, UE 115-d may report a NACK after the first feedback monitoring timing. Conversely, there may be no NACK among the multiple feedback timings; however, UE 115-d may report a NACK to Layer 2 after monitoring multiple feedback monitoring timings based on the absence of an ACK during the multiple feedback monitoring timings.

[0118] Although described in the context of sidelink communication between UE 115-d, UE 115-e, and UE 115-f, this should not be construed as limiting this disclosure. In this respect, UE 115-d may communicate with any number of UE 115s, including a single UE 115 or multiple UE 115s.

[0119] Figure 4 A block diagram 400 illustrates a device 405 supporting feedback reporting for multiple feedback timings according to one or more aspects of this disclosure. Device 405 may be an example of aspects of UE 115 as described herein. Device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. Device 405, or one or more components of device 405 (e.g., receiver 410, transmitter 415, and communication manager 420), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0120] Receiver 410 may provide components 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 associated with feedback reports for multiple feedback timings). The information may be transmitted to other components of device 405. Receiver 410 may utilize a single antenna or a collection of multiple antennas.

[0121] Transmitter 415 may provide components for transmitting signals generated by other components of device 405. For example, transmitter 415 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with feedback reports for multiple feedback timings), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 415 may be co-located with receiver 410 in a transceiver module. Transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0122] The communication manager 420, receiver 410, transmitter 415, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of feedback reporting for multiple feedback timings as described herein. For example, the communication manager 420, receiver 410, transmitter 415, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0123] In some examples, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., executing instructions stored in at least one memory individually or collectively by one or more processors).

[0124] Additionally or alternatively, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0125] In some examples, the communication manager 420 may be configured to use or otherwise cooperate with the receiver 410, transmitter 415, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 420 may receive information from the receiver 410, transmit information to the transmitter 415, or be integrated in combination with the receiver 410, transmitter 415, or both to acquire information, output information, or perform various other operations as described herein.

[0126] Communication manager 420 may support wireless communication according to examples disclosed herein. For example, communication manager 420 may be capable of, configured to, or operable to support components for transmitting a sidelink message from a first layer of the protocol stack at a first UE to one or more second UEs via a sidelink shared channel, the sidelink message corresponding to a set of multiple feedback monitoring opportunities for a first feedback associated with the sidelink message, wherein the sidelink message belongs to a first broadcast type in a set of multiple broadcast types. Communication manager 420 may be capable of, configured to, or operable to support components for transmitting a single feedback report to a second layer above the first layer of the protocol stack based on the first broadcast type and based on the receipt or absence of one or more feedback messages via the set of multiple feedback monitoring opportunities, the single feedback report indicating a second feedback for the set of multiple feedback monitoring opportunities.

[0127] By including or configuring a communication manager 420 according to an example as described herein, device 405 (e.g., controlling receiver 410, transmitter 415, communication manager 420 or a combination thereof or at least one processor otherwise coupled thereto) can support techniques for feedback reporting for multiple PSFCH timings, which can result in reduced processing, lower power consumption and more efficient utilization of communication resources, among other benefits.

[0128] Figure 5A block diagram 500 of a device 505 supporting feedback reporting for multiple feedback timings according to one or more aspects of this disclosure is shown. Device 505 may be an example of aspects of device 405 or UE 115 as described herein. Device 505 may include receiver 510, transmitter 515, and communication manager 520. Device 505, or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0129] Receiver 510 may provide components 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 associated with feedback reports for multiple feedback timings). The information may be transmitted to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0130] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with feedback reports for multiple feedback timings), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0131] Device 505 or its various components may be examples of parts for performing various aspects of feedback reporting for multiple feedback timings as described herein. For example, communication manager 520 may include message sending and receiving component 525, reporting component 530, or any combination thereof. Communication manager 520 may be examples of aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to use or otherwise cooperate with receiver 510, transmitter 515, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated with receiver 510, transmitter 515, or a combination thereof to acquire information, output information, or perform various other operations as described herein.

[0132] Communication manager 520 may support wireless communication according to examples disclosed herein. Message receiving component 525 is capable of, configured to, or operable to support components for transmitting sidelink messages from a first layer of the protocol stack at a first UE to one or more second UEs via a sidelink shared channel, the sidelink message corresponding to a set of multiple feedback monitoring opportunities for a first feedback associated with the sidelink message, wherein the sidelink message belongs to a first broadcast type in a set of multiple broadcast types. Reporting component 530 is capable of, configured to, or operable to support components for transmitting a single feedback report to a second layer above the first layer of the protocol stack based on the first broadcast type and based on the receipt or absence of one or more feedback messages via the set of multiple feedback monitoring opportunities, the single feedback report indicating a second feedback for the set of multiple feedback monitoring opportunities.

[0133] In some cases, the message receiving component 525 and the reporting component 530 may each be at least one processor (e.g., a transceiver processor, a radio processor, a transmitter processor, or a receiver processor) or at least part of at least one processor. The at least one processor may be coupled to at least one memory and execute instructions stored in the at least one memory that enable the at least one processor to perform or facilitate the features of the message receiving component 525 and the reporting component 530 discussed herein. The transceiver processor may co-locate with and / or communicate with (e.g., instruct its operation) the transceiver of the device. The radio processor may co-locate with and / or communicate with (e.g., instruct its operation) the radio components of the device (e.g., NR radio components, LTE radio components, Wi-Fi radio components). The transmitter processor may co-locate with and / or communicate with (e.g., instruct its operation) the transmitter of the device. The receiver processor may co-locate with and / or communicate with (e.g., instruct its operation) the receiver of the device.

[0134] Figure 6 A block diagram 600 illustrates a communication manager 620 supporting feedback reporting for multiple feedback moments according to one or more aspects of this disclosure. The communication manager 620 may be an example of aspects of the communication manager 420, communication manager 520, or both as described herein. The communication manager 620 or its various components may be examples of parts for performing various aspects of feedback reporting for multiple feedback moments as described herein. For example, the communication manager 620 may include a message sending and receiving component 625, a reporting component 630, a feedback component 635, a monitoring component 640, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0135] The communication manager 620 may support wireless communication according to examples disclosed herein. The message sending and receiving component 625 is capable of, configured to, or operable to support components for sending sidelink messages from a first layer of the protocol stack at a first UE to one or more second UEs via a sidelink shared channel, the sidelink message corresponding to a set of multiple feedback monitoring opportunities for a first feedback associated with the sidelink message, wherein the sidelink message belongs to a first broadcast type in a set of multiple broadcast types. The reporting component 630 is capable of, configured to, or operable to support components for sending a single feedback report to a second layer above the first layer of the protocol stack based on the first broadcast type and based on the receipt or absence of one or more feedback messages via the set of multiple feedback monitoring opportunities, the single feedback report indicating a second feedback for the set of multiple feedback monitoring opportunities.

[0136] In some examples, the first broadcast type is unicast, and the feedback component 635 is capable of, configured to, or operable to support components for receiving a positive acknowledgment message during monitoring at least a first feedback monitoring moment in a set of multiple feedback monitoring moments, wherein reporting a single feedback report includes... In some examples, the first broadcast type is unicast, and the reporting component 630 is capable of, configured to, or operable to support components for reporting a positive acknowledgment based on receiving a positive acknowledgment message after monitoring a set of multiple feedback monitoring moments, wherein the second feedback includes the positive acknowledgment.

[0137] In some examples, the first broadcast type is unicast, and the monitoring component 640 is capable of, configured to, or operable to support components for monitoring a set of multiple feedback monitoring moments to obtain a positive acknowledgment message, wherein reporting a single feedback report includes... In some examples, the first broadcast type is unicast, and the reporting component 630 is capable of, configured to, or operable to support components for reporting a negative acknowledgment based on the absence of a positive acknowledgment message during the monitoring of the multiple sets of feedback monitoring moments after monitoring the set of multiple feedback monitoring moments, wherein the second feedback includes the negative acknowledgment.

[0138] In some examples, the first broadcast type is unicast, and the feedback component 635 is capable of, configured to, or operable to support components for receiving a negative acknowledgment message during monitoring at least a first feedback monitoring moment in a set of multiple feedback monitoring moments, wherein reporting a single feedback report includes... In some examples, the first broadcast type is unicast, and the reporting component 630 is capable of, configured to, or operable to support components for reporting a negative acknowledgment based on the received negative acknowledgment message after monitoring a set of multiple feedback monitoring moments, wherein the second feedback includes the negative acknowledgment.

[0139] In some examples, the first broadcast type is unicast, and the monitoring component 640 is capable of, configured to, or operable to support components for monitoring a set of multiple feedback monitoring moments to obtain negative acknowledgment messages, wherein reporting a single feedback report includes... In some examples, the first broadcast type is unicast, and the reporting component 630 is capable of, configured to, or operable to support components for reporting positive acknowledgment after monitoring a set of multiple feedback monitoring moments, based on the absence of a negative acknowledgment message during the monitoring of the set of multiple feedback monitoring moments, wherein the second feedback includes the positive acknowledgment.

[0140] In some examples, the one or more feedback messages are received during monitoring of a set of multiple feedback monitoring moments, wherein a single feedback report is reported. In some examples, after monitoring a set of multiple feedback monitoring moments, a positive confirmation or a negative confirmation is reported based on one or more feedback messages, wherein a second feedback includes the positive confirmation or the negative confirmation.

[0141] In some examples, the first broadcast type is unicast, and the feedback component 635 is capable of, configured to, or operable to support components for receiving a first feedback message during monitoring of a first feedback monitoring moment in a set of multiple feedback monitoring moments, wherein reporting a single feedback report includes... In some examples, the first broadcast type is unicast, and the reporting component 630 is capable of, configured to, or operable to support components for reporting an indication of the first feedback message received during monitoring of the first feedback monitoring moment, after the first feedback monitoring moment, wherein second feedback includes the indication.

[0142] In some examples, the first feedback message is a positive confirmation message. In some examples, the indication of the first feedback message includes positive confirmation.

[0143] In some examples, the first broadcast type is unicast, and the monitoring component 640 is capable of, configured to, or operable to support components for monitoring a set of multiple feedback monitoring moments to obtain a positive acknowledgment message, wherein reporting a single feedback report includes... In some examples, the first broadcast type is unicast, and the reporting component 630 is capable of, configured to, or operable to support components for reporting a negative acknowledgment based on the absence of a positive acknowledgment message during the monitoring of the multiple sets of feedback monitoring moments after monitoring the set of multiple feedback monitoring moments, wherein the second feedback includes the negative acknowledgment.

[0144] In some examples, the first broadcast type is a multicast associated with feedback based on negative acknowledgment only, and the monitoring component 640 is capable of, configured to, or operable to support components for monitoring a set of multiple feedback monitoring moments to obtain negative acknowledgment messages, wherein reporting a single feedback report includes... In some examples, the first broadcast type is a multicast associated with feedback based on negative acknowledgment only, and the reporting component 630 is capable of, configured to, or operable to support components for reporting positive acknowledgments after monitoring a set of multiple feedback monitoring moments, based on the absence of negative acknowledgment messages during the monitoring period of the multiple sets of feedback monitoring moments, wherein the second feedback includes the positive acknowledgment.

[0145] In some examples, the first broadcast type is a multicast associated with feedback based on negative acknowledgment only, and the feedback component 635 is capable of, configured to, or operable to support components for receiving a negative acknowledgment message during monitoring of a first feedback monitoring moment in a set of multiple feedback monitoring moments, wherein reporting a single feedback report includes... In some examples, the first broadcast type is a multicast associated with feedback based on negative acknowledgment only, and the reporting component 630 is capable of, configured to, or operable to support components for reporting negative acknowledgments based on receiving a negative acknowledgment message during monitoring of a set of multiple feedback monitoring moments, wherein the second feedback includes the negative acknowledgment.

[0146] In some examples, negative confirmation is reported after a set of multiple feedback monitoring events have been monitored.

[0147] In some examples, negative confirmations are reported after the initial feedback monitoring period.

[0148] In some examples, the first broadcast type is multicast, and the feedback component 635 is capable of, configured to, or operable to support components for receiving a positive acknowledgment message associated with each of one or more second UEs during monitoring of a set of multiple feedback monitoring moments, wherein reporting a single feedback report includes... In some examples, the first broadcast type is multicast, and the reporting component 630 is capable of, configured to, or operable to support components for reporting a positive acknowledgment based on receiving a positive acknowledgment message associated with each of one or more second UEs during monitoring of a set of multiple feedback monitoring moments, wherein the second feedback includes the positive acknowledgment.

[0149] In some examples, the confirmation is reported after a set of multiple feedback monitoring events have been monitored.

[0150] In some examples, a positive acknowledgment is reported after the last positive acknowledgment message in the positive acknowledgment messages associated with each of the one or more second UEs.

[0151] In some examples, the first broadcast type is a multicast associated with feedback based on positive and negative acknowledgments, and the feedback component 635 is capable of, configured to, or operable to support components for receiving a negative acknowledgment message during monitoring of a first feedback monitoring moment in a set of multiple feedback monitoring moments, wherein reporting a single feedback report includes... In some examples, the first broadcast type is a multicast associated with feedback based on positive and negative acknowledgments, and the reporting component 630 is capable of, configured to, or operable to support components for reporting a negative acknowledgment based on receiving a negative acknowledgment message during monitoring of a set of multiple feedback monitoring moments, wherein the second feedback includes the negative acknowledgment.

[0152] In some examples, negative confirmation is reported after a set of multiple feedback monitoring events have been monitored.

[0153] In some examples, negative confirmations are reported after the initial feedback monitoring period.

[0154] In some examples, the first broadcast type is a multicast associated with feedback based on positive and negative acknowledgments, and the monitoring component 640 is capable, configured, or operable to support components for monitoring a set of multiple feedback monitoring moments to obtain negative acknowledgment messages, wherein reporting a single feedback report includes... In some examples, the first broadcast type is a multicast associated with feedback based on positive and negative acknowledgments, and the reporting component 630 is capable, configured, or operable to support components for reporting negative acknowledgments after monitoring a set of multiple feedback monitoring moments, based on the absence of a positive acknowledgment message from at least one of one or more second UEs during the monitoring period of the set of multiple feedback monitoring moments, wherein the second feedback includes the negative acknowledgment.

[0155] In some cases, the message receiving component 625, the reporting component 630, the feedback component 635, and the monitoring component 640 may each be at least one processor (e.g., a transceiver processor, a radio processor, a transmitter processor, or a receiver processor) or at least part of at least one processor. The at least one processor may be coupled to at least one memory and execute instructions stored in the at least one memory that enable the at least one processor to perform or facilitate the features of the message receiving component 625, the reporting component 630, the feedback component 635, and the monitoring component 640 discussed herein.

[0156] Figure 7A diagram of a system 700 including a device 705 supporting feedback reporting for multiple feedback timings, according to one or more aspects of this disclosure, is shown. Device 705 may be an example of device 405, device 505, or UE 115 as described herein, or a component including such devices. Device 705 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 720, an input / output (I / O) controller 710, a transceiver 715, an antenna 725, at least one memory 730, code 735, and at least one processor 740. These components may communicate electronically via one or more buses (e.g., bus 745) or be otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically).

[0157] I / O controller 710 manages the input and output signals of device 705. I / O controller 710 can also manage peripheral devices not integrated into device 705. In some cases, I / O controller 710 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 710 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 710 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 710 may be implemented as part of one or more processors, such as at least one processor 740. In some cases, a user may interact with the device 705 via the I / O controller 710 or via hardware components controlled by the I / O controller 710.

[0158] In some cases, device 705 may include a single antenna 725. However, in other cases, device 705 may have more than one antenna 725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 715 may communicate bidirectionally via one or more antennas 725, wired or wireless links, as described herein. For example, transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 715 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 725 for transmission; and demodulating packets received from one or more antennas 725. Transceiver 715, or transceiver 715 and one or more antennas 725, may be an example of transmitter 415, transmitter 515, receiver 410, receiver 510, or any combination thereof or components thereof as described herein.

[0159] At least one memory 730 may include random access memory (RAM) and read-only memory (ROM). At least one memory 730 may store computer-readable, computer-executable code 735, including instructions that, when executed by at least one processor 740, cause device 705 to perform the various functions described herein. Code 735 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 735 may not be directly executable by at least one processor 740, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 730 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0160] At least one processor 740 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 740 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 740. At least one processor 740 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 730) to cause device 705 to perform various functions (e.g., various functions or tasks supporting feedback reporting for multiple feedback times). For example, device 705 or components of device 705 may include at least one processor 740 and at least one memory 730 coupled to or coupled to at least one processor 740, at least one processor 740 and at least one memory 730 being configured to perform the various functions described herein. In some examples, at least one processor 740 may include multiple processors, and at least one memory 730 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein.

[0161] The communication manager 720 may support wireless communication according to examples disclosed herein. For example, the communication manager 720 may be capable of, configured to, or operable to support components for transmitting a sidelink message from a first layer of the protocol stack at a first UE to one or more second UEs via a sidelink shared channel, the sidelink message corresponding to a set of multiple feedback monitoring opportunities for a first feedback associated with the sidelink message, wherein the sidelink message belongs to a first broadcast type in a set of multiple broadcast types. The communication manager 720 may be capable of, configured to, or operable to support components for transmitting a single feedback report to a second layer above the first layer of the protocol stack based on the first broadcast type and based on the receipt or absence of one or more feedback messages via the set of multiple feedback monitoring opportunities, the single feedback report indicating a second feedback for the set of multiple feedback monitoring opportunities.

[0162] By including or configuring a communication manager 720 according to an example as described herein, device 705 can support techniques for feedback reporting for multiple PSFCH timings, which can lead to improved communication reliability, reduced latency, improved user experience associated with reduced processing, reduced power consumption, more efficient use of communication resources, improved coordination between devices, longer battery life, and improved utilization of processing power, among other benefits.

[0163] In some examples, the communication manager 720 may be configured to use or otherwise coordinate with the transceiver 715, one or more antennas 725, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported by or performed by at least one processor 740, at least one memory 730, code 735, or any combination thereof. For example, code 735 may include instructions that may be executed by at least one processor 740 to cause the device 705 to perform various aspects of feedback reporting for multiple feedback timings as described herein, or at least one processor 740 and at least one memory 730 may be otherwise configured to perform or support such operations individually or jointly.

[0164] Figure 8 A flowchart illustrating a method 800 for supporting feedback reporting at multiple feedback points according to various aspects of this disclosure is shown. Operation of method 800 can be implemented by a UE or its components as described herein. For example, operation of method 800 can be achieved by, as referenced... Figures 1 to 7 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0165] At 805, the method may include: transmitting a sidelink message from a first layer of the protocol stack at a first UE and via a sidelink shared channel to one or more second UEs, the sidelink message corresponding to a set of multiple feedback monitoring opportunities for a first feedback associated with the sidelink message, wherein the sidelink message belongs to a first broadcast type in a set of multiple broadcast types. Operation of block 805 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 805 may be provided by reference to [reference]. Figure 6 The message receiving and sending component 625 described herein shall be used to perform this action.

[0166] At 810, the method may include: reporting a single feedback report to a second layer above the first layer of the protocol stack based on a first broadcast type and based on the receipt or absence of one or more feedback messages via a set of multiple feedback monitoring moments, the single feedback report indicating a second feedback for the set of multiple feedback monitoring moments. The operation of block 810 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 810 may be provided by reference to [reference needed]. Figure 6 The described reporting component 630 is executed.

[0167] The following provides an overview of the various aspects of this disclosure:

[0168] Aspect 1: A method for wireless communication at a first UE, the method comprising: transmitting a sidelink message from a first layer of a protocol stack at the first UE and via a sidelink shared channel to one or more second UEs, the sidelink message corresponding to a plurality of feedback monitoring opportunities for a first feedback associated with the sidelink message, wherein the sidelink message belongs to a first broadcast type among a plurality of broadcast types; and reporting a single feedback report to a second layer above the first layer of the protocol stack, at least in part based on the first broadcast type and at least in part based on the receipt or absence of one or more feedback messages via the plurality of feedback monitoring opportunities, the single feedback report indicating a second feedback for the plurality of feedback monitoring opportunities.

[0169] Aspect 2: According to the method of aspect 1, wherein the first broadcast type is unicast, the method further includes: receiving a positive acknowledgment message during the monitoring of at least a first feedback monitoring moment among the plurality of feedback monitoring moments, wherein reporting the single feedback report includes: reporting a positive acknowledgment at least in part based on receiving the positive acknowledgment message after monitoring the plurality of feedback monitoring moments, wherein the second feedback includes the positive acknowledgment.

[0170] Aspect 3: According to the method of aspect 1, wherein the first broadcast type is unicast, the method further includes: monitoring the plurality of feedback monitoring opportunities for positive acknowledgment messages, wherein reporting the single feedback report includes: after monitoring the plurality of feedback monitoring opportunities, reporting a negative acknowledgment at least in part based on the absence of the positive acknowledgment message during the monitoring period of the plurality of feedback monitoring opportunities, wherein the second feedback includes the negative acknowledgment.

[0171] Aspect 4: According to the method of aspect 1, wherein the first broadcast type is unicast, the method further includes: receiving a negative acknowledgment message during the monitoring of at least a first feedback monitoring moment among the plurality of feedback monitoring moments, wherein reporting the single feedback report includes: reporting a negative acknowledgment at least in part based on receiving the negative acknowledgment message after monitoring the plurality of feedback monitoring moments, wherein the second feedback includes the negative acknowledgment.

[0172] Aspect 5: According to the method of aspect 1, wherein the first broadcast type is unicast, the method further includes: monitoring the plurality of feedback monitoring moments for negative acknowledgment messages, wherein reporting the single feedback report includes: after monitoring the plurality of feedback monitoring moments, reporting an affirmative acknowledgment at least in part based on the absence of the negative acknowledgment message during the monitoring of the plurality of feedback monitoring moments, wherein the second feedback includes the affirmative acknowledgment.

[0173] Aspect 6: The method according to Aspect 1, wherein the first broadcast type is unicast, the method comprising: receiving the one or more feedback messages during the monitoring of the plurality of feedback monitoring moments, wherein reporting the single feedback report comprises: reporting a positive confirmation or a negative confirmation at least in part based on the one or more feedback messages after monitoring the plurality of feedback monitoring moments, wherein the second feedback includes the positive confirmation or the negative confirmation.

[0174] Aspect 7: The method according to aspect 1, wherein the first broadcast type is unicast, the method further comprising: receiving a first feedback message during the monitoring period of a first feedback monitoring moment among the plurality of feedback monitoring moments, wherein reporting the single feedback report comprises: reporting an indication of the first feedback message after the first feedback monitoring moment, at least in part based on the receipt of the first feedback message during the monitoring period of the first feedback monitoring moment, wherein the second feedback includes the indication.

[0175] Aspect 8: According to the method of aspect 7, wherein the first feedback message is a positive confirmation feedback message, and the indication to the first feedback message includes positive confirmation.

[0176] Aspect 9: According to the method of aspect 1, wherein the first broadcast type is unicast, the method further includes: monitoring the plurality of feedback monitoring moments for a positive acknowledgment message, wherein reporting the single feedback report includes: after monitoring the plurality of feedback monitoring moments, reporting a negative acknowledgment at least in part based on the absence of the positive acknowledgment message during the monitoring period of the plurality of feedback monitoring moments, wherein the second feedback includes the negative acknowledgment.

[0177] Aspect 10: The method according to aspect 1, wherein the first broadcast type is a multicast associated with feedback based on only negative acknowledgment, the method further comprising: monitoring the plurality of feedback monitoring moments for negative acknowledgment messages, wherein reporting the single feedback report comprises: reporting a positive acknowledgment after monitoring the plurality of feedback monitoring moments, at least in part based on the absence of the negative acknowledgment message during the monitoring of the plurality of feedback monitoring moments, wherein the second feedback includes the positive acknowledgment.

[0178] Aspect 11: The method according to aspect 1, wherein the first broadcast type is a multicast associated with feedback based on negative acknowledgment only, the method further comprising: receiving a negative acknowledgment message during the monitoring of a first feedback monitoring moment among the plurality of feedback monitoring moments, wherein reporting the single feedback report comprises: reporting a negative acknowledgment at least in part based on receiving the negative acknowledgment message during the monitoring of the plurality of feedback monitoring moments, wherein the second feedback includes the negative acknowledgment.

[0179] Aspect 12: According to the method of aspect 11, the negative confirmation is reported after monitoring the plurality of feedback monitoring opportunities.

[0180] Aspect 13: According to the method of aspect 11, the negative confirmation is reported after the first feedback monitoring timing.

[0181] Aspect 14: The method according to Aspect 1, wherein the first broadcast type is multicast, the method further comprising: receiving a positive acknowledgment message associated with each of the one or more second UEs during the monitoring of the plurality of feedback monitoring moments, wherein reporting the single feedback report comprises: reporting the positive acknowledgment based at least in part on receiving the positive acknowledgment message associated with each of the one or more second UEs during the monitoring of the plurality of feedback monitoring moments, wherein the second feedback includes the positive acknowledgment.

[0182] Aspect 15: According to the method of aspect 14, the affirmative confirmation is reported after monitoring the plurality of feedback monitoring moments.

[0183] Aspect 16: According to the method of aspect 14, the affirmative acknowledgment is reported after receiving the last affirmative acknowledgment message in the affirmative acknowledgment messages associated with each of the one or more second UEs.

[0184] Aspect 17: The method according to aspect 1, wherein the first broadcast type is multicast associated with feedback based on positive and negative acknowledgments, the method further comprising: receiving a negative acknowledgment message during the monitoring of a first feedback monitoring moment among the plurality of feedback monitoring moments, wherein reporting the single feedback report comprises: reporting a negative acknowledgment at least in part based on receiving the negative acknowledgment message during the monitoring of the plurality of feedback monitoring moments, wherein the second feedback includes the negative acknowledgment.

[0185] Aspect 18: According to the method of aspect 17, the negative confirmation is reported after monitoring the plurality of feedback monitoring moments.

[0186] Aspect 19: According to the method of aspect 17, the negative confirmation is reported after the first feedback monitoring timing.

[0187] Aspect 20: The method according to aspect 1, wherein the first broadcast type is a multicast associated with feedback based on positive acknowledgment and negative acknowledgment, the method further comprising: monitoring the plurality of feedback monitoring moments for negative acknowledgment messages, wherein reporting the single feedback report comprises: after monitoring the plurality of feedback monitoring moments, reporting a negative acknowledgment based at least in part on the absence of a positive acknowledgment message from at least one of the one or more second UEs during the monitoring of the plurality of feedback monitoring moments, wherein the second feedback includes the negative acknowledgment.

[0188] Aspect 21: A first UE for wireless communication, the first UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the first UE performs a method according to any one of aspects 1 to 20.

[0189] Aspect 22: A first UE for wireless communication, the first UE comprising at least one component for performing the method according to any one of aspects 1 to 20.

[0190] Aspect 23: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the method according to any one of aspects 1 to 20.

[0191] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0192] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0193] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0194] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a 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 working in conjunction with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

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

[0196] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0197] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0198] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0199] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

[0200] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0201] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0202] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first user equipment (UE), the first user equipment (UE) comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and capable of operating, alone or in combination, to execute the code to cause the first UE to: transmit, from a first layer of a protocol stack at the first UE and via a sidelink shared channel, a sidelink message to one or more second UEs, the sidelink message corresponding to a plurality of feedback monitoring occasions for first feedback associated with the sidelink message, wherein the sidelink message is of a first cast type among a plurality of cast types; and report, to a second layer of the protocol stack higher than the first layer, a single feedback report based at least in part on the first cast type and based at least in part on receiving or an absence of one or more feedback messages via the plurality of feedback monitoring occasions, the single feedback report indicating second feedback for the plurality of feedback monitoring occasions.

2. The first UE of claim 1, wherein the first cast type is unicast, and the one or more processors capable of operating, alone or in combination, to further execute the code to cause the first UE to: receive a positive acknowledgement message during monitoring of at least a first feedback monitoring occasion of the plurality of feedback monitoring occasions, wherein reporting the single feedback report comprises: reporting a positive acknowledgement based at least in part on receiving the positive acknowledgement message after monitoring the plurality of feedback monitoring occasions, wherein the second feedback comprises the positive acknowledgement.

3. The first UE of claim 1, wherein the first cast type is unicast, and the one or more processors capable of operating, alone or in combination, to further execute the code to cause the first UE to: monitor the plurality of feedback monitoring occasions for a positive acknowledgement message, wherein reporting the single feedback report comprises: reporting a negative acknowledgement based at least in part on an absence of the positive acknowledgement message during monitoring of the plurality of feedback monitoring occasions after monitoring the plurality of feedback monitoring occasions, wherein the second feedback comprises the negative acknowledgement.

4. The first UE of claim 1, wherein the first cast type is unicast, and the one or more processors capable of operating, alone or in combination, to further execute the code to cause the first UE to: receive a negative acknowledgement message during monitoring of at least a first feedback monitoring occasion of the plurality of feedback monitoring occasions, wherein reporting the single feedback report comprises: reporting a negative acknowledgement based at least in part on receiving the negative acknowledgement message after monitoring the plurality of feedback monitoring occasions, wherein the second feedback comprises the negative acknowledgement.

5. The first UE of claim 1, wherein the first cast type is unicast, and the one or more processors capable of operating, alone or in combination, to further execute the code to cause the first UE to: monitor the plurality of feedback monitoring occasions for a negative acknowledgement message, wherein reporting the single feedback report comprises: reporting a positive acknowledgement after monitoring the plurality of feedback monitoring occasions based at least in part on an absence of the negative acknowledgement message during monitoring of the plurality of feedback monitoring occasions, wherein the second feedback comprises the positive acknowledgement.

6. The first UE of claim 1, wherein the first cast type is unicast, and the one or more processors, separately or collectively, are further operable to execute the code to cause the first UE to: receive the one or more feedback messages during monitoring of the plurality of feedback monitoring occasions, wherein reporting the single feedback report comprises: reporting a positive acknowledgement or a negative acknowledgement after monitoring the plurality of feedback monitoring occasions based at least in part on the one or more feedback messages, wherein the second feedback comprises the positive acknowledgement or the negative acknowledgement.

7. The first UE of claim 1, wherein the first cast type is unicast, and the one or more processors, separately or collectively, are further operable to execute the code to cause the first UE to: receive a first feedback message during monitoring of a first feedback monitoring occasion of the plurality of feedback monitoring occasions, wherein reporting the single feedback report comprises: reporting an indication of the first feedback message after the first feedback monitoring occasion based at least in part on receiving the first feedback message during the monitoring of the first feedback monitoring occasion, wherein the second feedback comprises the indication.

8. The first UE of claim 7, wherein the first feedback message is a positive acknowledgement feedback message, and the indication of the first feedback message comprises a positive acknowledgement.

9. The first UE of claim 1, wherein the first cast type is unicast, and the one or more processors, separately or collectively, are further operable to execute the code to cause the first UE to: monitor the plurality of feedback monitoring occasions for a positive acknowledgement message, wherein reporting the single feedback report comprises: reporting a negative acknowledgement after monitoring the plurality of feedback monitoring occasions based at least in part on an absence of the positive acknowledgement message during monitoring of the plurality of feedback monitoring occasions, wherein the second feedback comprises the negative acknowledgement.

10. The first UE of claim 1, wherein the first cast type is a groupcast associated with negative acknowledgement only based feedback, and the one or more processors, separately or collectively, are further operable to execute the code to cause the first UE to: monitor the plurality of feedback monitoring occasions for a negative acknowledgement message, wherein reporting the single feedback report comprises: reporting a positive acknowledgement after monitoring the plurality of feedback monitoring occasions based at least in part on an absence of the negative acknowledgement message during monitoring of the plurality of feedback monitoring occasions, wherein the second feedback comprises the positive acknowledgement.

11. The first UE of claim 1, wherein the first broadcast type is groupcast associated with negative-acknowledgement-only based feedback, and the one or more processors, separately or collectively, are further operable to execute the code to cause the first UE to: receive a negative-acknowledgement message during monitoring of a first feedback monitoring occasion of the plurality of feedback monitoring occasions, wherein reporting the single feedback report comprises: report a negative-acknowledgement based at least in part on receiving the negative- acknowledgement message during monitoring of the plurality of feedback monitoring occasions, wherein the second feedback comprises the negative-acknowledgement.

12. The first UE of claim 11, wherein the negative-acknowledgement is reported after monitoring the plurality of feedback monitoring occasions.

13. The first UE of claim 11, wherein the negative-acknowledgement is reported after the first feedback monitoring occasion.

14. The first UE of claim 1, wherein the first broadcast type is groupcast, and the one or more processors, separately or collectively, are further operable to execute the code to cause the first UE to: receive a positive-acknowledgement message associated with each second UE of the one or more second UEs during monitoring of the plurality of feedback monitoring occasions, wherein reporting the single feedback report comprises: report a positive-acknowledgement based at least in part on receiving the positive- acknowledgement message associated with each second UE of the one or more second UEs during monitoring of the plurality of feedback monitoring occasions, wherein the second feedback comprises the positive-acknowledgement.

15. The first UE of claim 14, wherein the positive-acknowledgement is reported after monitoring the plurality of feedback monitoring occasions.

16. The first UE of claim 14, wherein the positive-acknowledgement is reported after receiving a last positive-acknowledgement message of the positive-acknowledgement messages associated with each second UE of the one or more second UEs.

17. The first UE of claim 1, wherein the first broadcast type is groupcast associated with positive-acknowledgement and negative-acknowledgement based feedback, and the one or more processors, separately or collectively, are further operable to execute the code to cause the first UE to: receive a negative-acknowledgement message during monitoring of a first feedback monitoring occasion of the plurality of feedback monitoring occasions, wherein reporting the single feedback report comprises: report a negative-acknowledgement based at least in part on receiving the negative- acknowledgement message during monitoring of the plurality of feedback monitoring occasions, wherein the second feedback comprises the negative-acknowledgement.

18. The first UE of claim 17, wherein the negative-acknowledgement is reported after monitoring the plurality of feedback monitoring occasions.

19. The first UE of claim 17, wherein the negative-acknowledgement is reported after the first feedback monitoring occasion.

20. The first UE of claim 1, wherein the first broadcast type is a groupcast associated with positive-acknowledgement and negative-acknowledgement based feedback, and the one or more processors, individually or collectively, are further operable to execute the code to cause the first UE to: monitor the plurality of feedback monitoring occasions for a negative-acknowledgement message, wherein reporting the single feedback report comprises: reporting, after monitoring the plurality of feedback monitoring occasions, a negative- acknowledgement based at least in part on an absence of a positive-acknowledgement message from at least one of the one or more second UEs during monitoring of the plurality of feedback monitoring occasions, wherein the second feedback comprises the negative-acknowledgement.

21. A method for wireless communication at a first user equipment (UE), comprising: transmitting, from a first layer of a protocol stack at the first UE and via a sidelink shared channel, a sidelink message to one or more second UEs, the sidelink message corresponding to a plurality of feedback monitoring occasions for first feedback associated with the sidelink message, wherein the sidelink message belongs to a first broadcast type of a plurality of broadcast types; and reporting, to a second layer of the protocol stack higher than the first layer, a single feedback report based at least in part on the first broadcast type and based at least in part on receiving or an absence of one or more feedback messages via the plurality of feedback monitoring occasions, the single feedback report indicating second feedback for the plurality of feedback monitoring occasions.

22. The method of claim 21, wherein the first broadcast type is unicast, the method further comprising: receiving a positive-acknowledgement message during monitoring of at least a first feedback monitoring occasion of the plurality of feedback monitoring occasions, wherein reporting the single feedback report comprises: reporting, after monitoring the plurality of feedback monitoring occasions, a positive- acknowledgement based at least in part on receiving the positive-acknowledgement message, wherein the second feedback comprises the positive-acknowledgement.

23. The method of claim 21, wherein the first broadcast type is unicast, the method further comprising: monitoring the plurality of feedback monitoring occasions for a positive-acknowledgement message, wherein reporting the single feedback report comprises: reporting, after monitoring the plurality of feedback monitoring occasions, a negative- acknowledgement based at least in part on an absence of the positive-acknowledgement message during monitoring of the plurality of feedback monitoring occasions, wherein the second feedback comprises the negative-acknowledgement.

24. The method of claim 21, wherein the first broadcast type is unicast, the method further comprising: receiving a negative-acknowledgement message during monitoring of at least a first feedback monitoring occasion of the plurality of feedback monitoring occasions, wherein reporting the single feedback report comprises: reporting, after monitoring the plurality of feedback monitoring occasions, a negative- acknowledgement based at least in part on receiving the negative-acknowledgement message, wherein the second feedback comprises the negative-acknowledgement.

25. The method of claim 21, wherein the first broadcast type is unicast, the method further comprising: monitor the plurality of feedback monitoring occasions for a negative acknowledgement message, wherein reporting the single feedback report comprises: reporting a positive acknowledgement after monitoring the plurality of feedback monitoring occasions based at least in part on an absence of the negative acknowledgement message during monitoring of the plurality of feedback monitoring occasions, wherein the second feedback comprises the positive acknowledgement.

26. The method of claim 21, wherein the first cast type is unicast, the method comprising: receiving the one or more feedback messages during monitoring of the plurality of feedback monitoring occasions, wherein reporting the single feedback report comprises: reporting a positive acknowledgement or a negative acknowledgement after monitoring the plurality of feedback monitoring occasions based at least in part on the one or more feedback messages, wherein the second feedback comprises the positive acknowledgement or the negative acknowledgement.

27. The method of claim 21, wherein the first cast type is unicast, the method further comprising: receiving a first feedback message during monitoring of a first feedback monitoring occasion of the plurality of feedback monitoring occasions, wherein reporting the single feedback report comprises: reporting an indication of the first feedback message after the first feedback monitoring occasion based at least in part on receiving the first feedback message during the monitoring of the first feedback monitoring occasion, wherein the second feedback comprises the indication.

28. The method of claim 21, wherein the first cast type is unicast, the method further comprising: monitoring the plurality of feedback monitoring occasions for a positive acknowledgement message, wherein reporting the single feedback report comprises: reporting a negative acknowledgement after monitoring the plurality of feedback monitoring occasions based at least in part on an absence of the positive acknowledgement message during monitoring of the plurality of feedback monitoring occasions, wherein the second feedback comprises the negative acknowledgement.

29. A first user equipment (UE) for wireless communication, the first user equipment (UE) comprising: means for transmitting, from a first layer of a protocol stack at the first UE and via a sidelink shared channel to one or more second UEs, a sidelink message, the sidelink message corresponding to a plurality of feedback monitoring occasions for first feedback associated with the sidelink message, wherein the sidelink message belongs to a first cast type of a plurality of cast types; and means for reporting, to a second layer of the protocol stack higher than the first layer, a single feedback report based at least in part on the first cast type and based at least in part on receiving or an absence of one or more feedback messages via the plurality of feedback monitoring occasions, the single feedback report indicating second feedback for the plurality of feedback monitoring occasions.

30. A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to: transmit, from a first layer of a protocol stack at a first user equipment (UE) and via a sidelink shared channel, a sidelink message to one or more second UEs, the sidelink message corresponding to a plurality of feedback monitoring occasions for first feedback associated with the sidelink message, wherein the sidelink message belongs to a first cast type of a plurality of cast types; and report, to a second layer of the protocol stack higher than the first layer, a single feedback report based at least in part on the first cast type and based at least in part on receiving or an absence of one or more feedback messages via the plurality of feedback monitoring occasions, the single feedback report indicating second feedback for the plurality of feedback monitoring occasions.

Images