Feedback monitoring for multiple feedback occasions
Patent Information
- Authority / Receiving Office
- EP · EP
- Patent Type
- Applications
- Current Assignee / Owner
- QUALCOMM INC
- Filing Date
- 2023-07-24
- Publication Date
- 2026-06-03
AI Technical Summary
In wireless communications, user equipment (UE) faces challenges in determining when to terminate monitoring of multiple candidate feedback occasions for sidelink messages, leading to inefficient resource utilization and increased power consumption.
The UE implements a method to determine when to terminate monitoring of candidate feedback occasions based on the cast type associated with the sidelink message and a set of rules, which consider the presence or absence of acknowledgment messages.
This approach allows the UE to efficiently manage feedback monitoring, reducing unnecessary resource allocation and power consumption while ensuring timely feedback processing.
Smart Images

Figure CN2023108843_30012025_PF_FP_ABST
Abstract
Description
FEEDBACK MONITORING FOR MULTIPLE FEEDBACK OCCASIONS
[0001] FIELD OF TECHNOLOGY
[0002] The present disclosure relates to wireless communications, including feedback monitoring for multiple feedback occasions.BACKGROUND
[0003] Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) . Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. 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 spread orthogonal frequency division multiplexing (DFT-S-OFDM) . A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .SUMMARY
[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support feedback monitoring for multiple feedback occasions. Generally, the techniques described herein enable a user equipment (UE) , in sidelink communications, to determine when (e.g., if at all) to terminate monitoring of multiple candidate feedback occasions associated with a sidelink message. For example, a first UE may transmit, via a sidelink shared channel (e.g., a physical sidelink shared channel (PSSCH) ) , a sidelink message to one or more second UEs. The sidelink message may be associated with a given cast type from multiple cast types, including at least unicast and groupcast. The sidelink message may correspond to multiple feedback monitoring occasions, or candidate feedback occasions (e.g., candidate physical sidelink feedback channel (PSFCH) occasions) , for feedback associated with the sidelink message. As such, the first UE may monitor, after transmitting the sidelink message, one or more feedback monitoring occasions of the multiple feedback monitoring occasions for the feedback, which may be transmitted by one or more second UEs, for the sidelink message. The one or more feedback monitoring occasions monitored by the first UE may be based on the cast type associated with the first sidelink message. For example, the one or more feedback monitoring occasions may be based on a rule associated with the cast type, where the rule indicates one or more conditions under which the first UE may terminate the monitoring of subsequent feedback monitoring occasions. In such cases, the rule may be based on whether the feedback associated with the sidelink message comprises one or more positive acknowledgment messages, one or more negative acknowledgment message, or both, or comprises an absence of the one or more positive acknowledgment messages, an absence of the one or more negative acknowledgment message, or both, during at least one of the multiple feedback monitoring occasions.
[0005] A method for wireless communications by a first UE is described. The method may include transmitting, via a sidelink shared channel, a sidelink message to one or more second UEs, the sidelink message corresponding to a set of multiple feedback monitoring occasions for feedback associated with the sidelink message, where the sidelink message is of a first cast type of a set of multiple cast types and monitoring, after transmitting the sidelink message, one or more feedback monitoring occasions of the set of multiple feedback monitoring occasions for the feedback associated with the sidelink message from the one or more second UEs, where the one or more feedback monitoring occasions are based on the first cast type.
[0006] A first UE for wireless communications is described. The first UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively operable to execute the code to cause the first UE to transmit, via a sidelink shared channel, a sidelink message to one or more second UEs, the sidelink message corresponding to a set of multiple feedback monitoring occasions for feedback associated with the sidelink message, where the sidelink message is of a first cast type of a set of multiple cast types and monitor, after transmitting the sidelink message, one or more feedback monitoring occasions of the set of multiple feedback monitoring occasions for the feedback associated with the sidelink message from the one or more second UEs, where the one or more feedback monitoring occasions are based on the first cast type.
[0007] Another first UE for wireless communications is described. The first UE may include means for transmitting, via a sidelink shared channel, a sidelink message to one or more second UEs, the sidelink message corresponding to a set of multiple feedback monitoring occasions for feedback associated with the sidelink message, where the sidelink message is of a first cast type of a set of multiple cast types and means for monitoring, after transmitting the sidelink message, one or more feedback monitoring occasions of the set of multiple feedback monitoring occasions for the feedback associated with the sidelink message from the one or more second UEs, where the one or more feedback monitoring occasions are based on the first cast type.
[0008] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by a processor to transmit, via a sidelink shared channel, a sidelink message to one or more second UEs, the sidelink message corresponding to a set of multiple feedback monitoring occasions for feedback associated with the sidelink message, where the sidelink message is of a first cast type of a set of multiple cast types and monitor, after transmitting the sidelink message, one or more feedback monitoring occasions of the set of multiple feedback monitoring occasions for the feedback associated with the sidelink message from the one or more second UEs, where the one or more feedback monitoring occasions are based on the first cast type.
[0009] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, monitoring the one or more feedback monitoring occasions may include operations, features, means, or instructions for monitoring each feedback monitoring occasion of the set of multiple feedback monitoring occasions, where the first cast type may be unicast or groupcast.
[0010] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the first cast type may be unicast and the method, apparatuses, and non-transitory computer-readable medium may include further operations, features, means, or instructions for receiving the feedback associated with the sidelink message during monitoring of the first feedback monitoring occasion based on the monitoring and terminating the monitoring of each subsequent feedback monitoring occasion of the set of multiple feedback monitoring occasions based on receiving the feedback associated with the sidelink message during the monitoring of the first feedback monitoring occasion.
[0011] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, monitoring the one or more feedback monitoring occasions may include operations, features, means, or instructions for monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message and monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based on absence of the feedback associated with the sidelink message during monitoring of the first feedback monitoring occasion.
[0012] In some examples of the method, first user UEs, and non-transitory computer-readable medium described herein, the first cast type may be unicast and the method, apparatuses, and non-transitory computer-readable medium may include further operations, features, means, or instructions for receiving a positive acknowledgment message during monitoring of the first feedback monitoring occasion, where the feedback associated with the sidelink message includes the positive acknowledgment message and terminating the monitoring of each subsequent feedback monitoring occasion of the set of multiple feedback monitoring occasions based on receiving the positive acknowledgment message during the monitoring of the first feedback monitoring occasion.
[0013] In some examples of the method, first UEs, and non-transitory computer-readable medium described herein, monitoring the one or more feedback monitoring occasions may include operations, features, means, or instructions for monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message and monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based on absence of a positive acknowledgment message during monitoring of the first feedback monitoring occasion, where the feedback associated with the sidelink message includes the positive acknowledgment message.
[0014] In some examples of the method, first UEs, and non-transitory computer-readable medium described herein, the first cast type may be groupcast associated with negative acknowledgment-only based feedback and the method, apparatuses, and non-transitory computer-readable medium may include further operations, features, means, or instructions for receiving a negative acknowledgment message during monitoring of the first feedback monitoring occasion based on the monitoring, where the feedback associated with the sidelink message includes the negative acknowledgment message and terminating the monitoring of each subsequent feedback monitoring occasions of the set of multiple feedback monitoring occasions based on receiving the negative acknowledgment message during the monitoring of the first feedback monitoring occasion.
[0015] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, monitoring the one or more feedback monitoring occasions may include operations, features, means, or instructions for monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message and monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based on absence of a negative acknowledgment message during monitoring of the first feedback monitoring occasion, where the feedback associated with the sidelink message includes the negative acknowledgment message.
[0016] In some examples of the method, first UEs, and non-transitory computer-readable medium described herein, the first cast type may be groupcast associated with positive acknowledgment and negative acknowledgment based feedback and the method, apparatuses, and non-transitory computer-readable medium may include further operations, features, means, or instructions for receiving, from at least one of the one or more second UEs, a negative acknowledgment message during monitoring of the first feedback monitoring occasion based on the monitoring, where the feedback associated with the sidelink message includes the negative acknowledgment message and terminating the monitoring of each subsequent feedback monitoring occasions of the set of multiple feedback monitoring occasions based on receiving the negative acknowledgment message from the at least one of the one or more second UEs during the monitoring of the first feedback monitoring occasion.
[0017] In some examples of the method, first UEs, and non-transitory computer-readable medium described herein, monitoring the one or more feedback monitoring occasions may include operations, features, means, or instructions for monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message and monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based on absence of a negative acknowledgment message from at least one of the one or more second UEs during monitoring of the first feedback monitoring occasion, where the feedback associated with the sidelink message includes the negative acknowledgment message.
[0018] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the first cast type may be groupcast associated with positive acknowledgment and negative acknowledgment based feedback and the method, apparatuses, and non-transitory computer-readable medium may include further operations, features, means, or instructions for receiving, from each of the one or more second UEs, the feedback associated with the sidelink message during monitoring of the first feedback monitoring occasion based on the monitoring and terminating the monitoring of each subsequent feedback monitoring occasions of the set of multiple feedback monitoring occasions based on receiving the feedback associated with the sidelink message from each of the one or more second UEs during the monitoring of the first feedback monitoring occasion.
[0019] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, monitoring the one or more feedback monitoring occasions may include operations, features, means, or instructions for monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message and monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based on absence of the feedback associated with the sidelink message from each of the one or more second UEs during monitoring of the first feedback monitoring occasion.
[0020] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the first cast type may be groupcast associated with positive acknowledgment and negative acknowledgment based feedback and the method, apparatuses, and non-transitory computer-readable medium may include further operations, features, means, or instructions for receiving, from each of the one or more second UEs, a positive acknowledgment message during monitoring of the first feedback monitoring occasion based on the monitoring, where the feedback associated with the sidelink message includes the positive acknowledgment message and terminating the monitoring of each subsequent feedback monitoring occasions of the set of multiple feedback monitoring occasions based on receiving the positive acknowledgment message from each of the one or more second UEs during the monitoring of the first feedback monitoring occasion.
[0021] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, monitoring the one or more feedback monitoring occasions may include operations, features, means, or instructions for monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message and monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based on absence of a positive acknowledgment message from each of the one or more second UEs during monitoring of the first feedback monitoring occasion, where the feedback associated with the sidelink message includes the positive acknowledgment message.
[0022] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the sidelink shared channel, a second sidelink message to one or more third UEs, the second sidelink message corresponding to a second set of multiple feedback monitoring occasions for second feedback associated with the second sidelink message, where the second sidelink message may be of a second cast type of the set of multiple cast types, and where the second set of multiple feedback monitoring occasions overlap with the set of multiple feedback monitoring occasions.
[0023] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the one or more feedback monitoring occasions includes an overlapping feedback monitoring occasion associated with the set of multiple feedback monitoring occasions and the second set of multiple feedback monitoring occasions and the method, apparatuses, and non-transitory computer-readable medium may include further operations, features, means, or instructions for receiving, during monitoring of the overlapping feedback monitoring occasion, the feedback associated with the sidelink message from each of the one or more second UEs and the second feedback associated with the second sidelink message from each of the one or more third UEs and terminating the monitoring of each subsequent feedback monitoring occasions of the set of multiple feedback monitoring occasions and the second set of multiple feedback monitoring occasions based on receiving, during the monitoring of the overlapping feedback monitoring occasion, the feedback associated with the sidelink message from each of the one or more second UEs and the second feedback associated with the second sidelink message from each of the one or more third UEs.
[0024] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, monitoring the one or more feedback monitoring occasions may include operations, features, means, or instructions for monitoring a first overlapping feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message and for the second feedback associated with the second sidelink message, where the first overlapping feedback monitoring occasion may be associated with the set of multiple feedback monitoring occasions and the second set of multiple feedback monitoring occasions and monitoring a second overlapping feedback monitoring occasion of the one or more feedback monitoring occasions based on absence of, during the monitoring of the first overlapping feedback monitoring occasion, the feedback associated with the sidelink message from each of the one or more second UEs and the second feedback associated with the second sidelink message from each of the one or more third UEs, where the second overlapping feedback monitoring occasion may be associated with the set of multiple feedback monitoring occasions and the second set of multiple feedback monitoring occasions.
[0025] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the one or more feedback monitoring occasions may be based on a rule associated with reception of the feedback associated with the sidelink message via at least one of the one or more feedback monitoring occasions.
[0026] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the rule may be based on the first cast type and whether the feedback associated with the sidelink message includes one or more positive acknowledgment messages, one or more negative acknowledgment message, or both, or includes an absence of the one or more positive acknowledgment messages, an absence of the one or more negative acknowledgment message, or both, during at least one of the set of multiple feedback monitoring occasions.BRIEF DESCRIPTION OF THE DRAWINGS
[0027] FIG. 1 shows an example of a wireless communications system that supports feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure.
[0028] FIG. 2 shows an example of a wireless communications system that supports feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure.
[0029] FIG. 3 shows examples of a wireless communications system that supports feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure.
[0030] FIG. 4 shows examples of a wireless communications system that supports feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure.
[0031] FIG. 5 shows an example of a process flow that supports feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure.
[0032] FIGs. 6 and 7 show block diagrams of devices that support feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure.
[0033] FIG. 8 shows a block diagram of a communications manager that supports feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure.
[0034] FIG. 9 shows a diagram of a system including a device that supports feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure.
[0035] FIGs. 10 and 11 show flowcharts illustrating methods that support feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION
[0036] In some wireless communications systems, a first user equipment (UE) may transmit, to one (e.g., unicast) or more (e.g., groupcast) second UEs, a sidelink message via a physical sidelink shared channel (PSSCH) , which may be referred to as a PSSCH transmission or PSSCH message. In some cases, one or more of the second UEs may transmit, to the first UE, feedback, such as a positive acknowledgment (ACK) or a negative acknowledgment (NACK) , for the PSSCH transmission. In some examples, the PSSCH transmission may be associated with multiple candidate feedback occasions for feedback via a feedback channel, such as a physical sidelink feedback channel (PSFCH) , and such candidate feedback occasions may be referred to as candidate PSFCH occasions. As such, the one or more second UEs may transmit the feedback for the PSSCH transmission in one or more of the multiple candidate PSFCH occasions. However, the first UE may be unaware of which of the multiple candidate PSFCH occasions are to be used by the one or more second UEs for transmitting feedback via the PSFCH. As such, the first UE may monitor all of multiple candidate PSFCH occasions the first UE regardless of whether feedback has been received in any of the candidate PSFCH occasions.
[0037] Accordingly, techniques described herein may enable the first UE to select which of multiple PSFCH occasions to monitor or to determine when (e.g., if at all) to terminate monitoring of the multiple candidate PSFCH occasions associated with the PSSCH transmission for the feedback from one or more second UEs. That is, the first UE may transmit a PSSCH transmission to the one or more second UEs, where the PSSCH transmission corresponds to multiple candidate PSFCH occasions. Additionally, the PSSCH transmission may be associated with a cast type of multiple cast types, including at least unicast, a first groupcast mode associated with NACK-only based feedback, and a second groupcast mode associated with ACK and NACK based feedback. After transmitting the PSSCH transmission, the first UE may monitor one or more candidate PSFCH occasions of the multiple PSFCH occasions for the feedback associated with the PSSCH transmission. In such cases, the one or more candidate PSFCH occasions monitored by the first UE may be based on the cast type and a rule associated with the cast type. That is, each cast type may be associated with one or more rules that each indicate conditions in which the first UE may terminate monitoring of subsequent candidate PSFCH occasions. The conditions may be based on whether the feedback associated with the PSSCH transmission includes one or more NACKs, one or more NACKS, or both, or whether one or more NACKs, one or more NACKS, or both, are absent from the feedback associated with the PSSCH transmission.
[0038] Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are then described in the context of a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to feedback monitoring for multiple feedback occasions.
[0039] FIG. 1 shows an example of a wireless communications system 100 that supports feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-APro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
[0040] The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via one or more communication links 125 (e.g., a radio frequency (RF) access link) . For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .
[0041] The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices, such as other UEs 115 or network entities 105, as shown in FIG. 1.
[0042] As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein) , a UE 115 (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.
[0043] In some examples, network entities 105 may communicate with the core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) . In some examples, network entities 105 may communicate with one another via a backhaul communication link 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via a core network 130) . In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) , one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.
[0044] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) . In some examples, a network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140) .
[0045] In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) . For example, a network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) 180 system, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) . In some examples, one or more network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
[0046] The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or more RUs 170) . In some cases, a functional split between a CU 160 and a DU 165, or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) . A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to one or more DUs 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) . In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that are in communication via such communication links.
[0047] In wireless communications systems (e.g., wireless communications system 100) , infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130) . In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as a donor entity or an IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140) . The one or more donor network entities 105 (e.g., IAB donors) may be in communication with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120) . IAB nodes 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by DUs 165 of a coupled IAB donor. An IAB-MT may include an independent set of antennas for relay of communications with UEs 115, or may share the same antennas (e.g., of an RU 170) of an IAB node 104 used for access via the DU 165 of the IAB node 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) . In some examples, the IAB nodes 104 may include DUs 165 that support communication links with additional entities (e.g., IAB nodes 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) . In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of IAB nodes 104) may be configured to operate according to the techniques described herein.
[0048] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support feedback monitoring for multiple feedback occasions as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 180) .
[0049] A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.
[0050] The UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as relays as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
[0051] The UEs 115 and the network entities 105 may wirelessly communicate with one another via one or more communication links 125 (e.g., an access link) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication links 125. For example, a carrier used for a communication link 125 may include a portion of a RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR) . Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105) .
[0052] Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) . In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.
[0053] The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts=1 / (Δfmax·Nf) seconds, for which Δfmax may represent a supported subcarrier spacing, and Nf may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) . Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .
[0054] Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) . In some wireless communications systems 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
[0055] A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) . In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
[0056] Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET) ) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.
[0057] In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area 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, the overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.
[0058] Some UEs 115, such as MTC or IoT devices, may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) . M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
[0059] The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) . The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
[0060] In some examples, a UE 115 may be configured to support communicating directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., in accordance with a peer-to-peer (P2P) , D2D, or sidelink protocol) . In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to-many (1: M) system in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, a network entity 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.
[0061] In some systems, a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115) . In some examples, vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to-network (V2N) communications, or with both.
[0062] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
[0063] The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) . Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
[0064] The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) radio access technology, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA) . Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
[0065] A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. 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, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.
[0066] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
[0067] The UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., a communication link 125, a D2D communication link 135) . HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) . HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions) . In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
[0068] The wireless communications system 100 may support techniques to enable the first UE 115 to determine when (e.g., if at all) to terminate monitoring of the multiple candidate PSFCH occasions associated with the PSSCH transmission for the feedback from one or more second UEs. That is, the first UE 115 may transmit a PSSCH transmission to the one or more second UEs 115, where the PSSCH transmission corresponds to multiple candidate PSFCH occasions. Additionally, the PSSCH transmission may be associated with a cast type of multiple cast types. The multiple cast types may include unicast, groupcast, broadcast, etc., and in some examples groupcast may one of a first groupcast mode associated with NACK-only based feedback and a second groupcast mode associated with ACK and NACK based feedback. After transmitting the PSSCH transmission, the first UE 115 may monitor one or more candidate PSFCH occasions of the multiple PSFCH occasions for the feedback associated with the PSSCH transmission. In such cases, the one or more candidate PSFCH occasions monitored by the first UE 115 may be based on the cast type and a rule associated with the cast type. That is, each cast type may be associated with one or more rules that each indicate conditions in which the first UE 115 may terminate monitoring of, or continue to monitor, subsequent candidate PSFCH occasions. The conditions may be based on whether the feedback associated with the PSSCH transmission includes one or more ACKs, one or more NACKS, or both, or on whether one or more ACKs, one or more NACKS, or both, are absent from the feedback associated with the PSSCH transmission.
[0069] FIG. 2 shows an example of a wireless communications system 200 that supports feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure. In some cases, the wireless communications system 200 may implement or be implemented by aspects of the wireless communications system 100. For example, the wireless communications system 200 may include one or more UEs 115 (e.g., a UE 115-a and a UE 115-b) and one or more network entities 105, which may be examples of the corresponding devices as described herein.
[0070] In some wireless communications systems, such as the wireless communications system 200, a transmitting UE 115, such as the UE 115-a, may transmit, to one (e.g., unicast) or more (e.g., groupcast) second UEs, such as the UE 115-b, a sidelink message via a PSSCH, which may be referred to as a PSSCH message 215. In some examples, the PSSCH message 215 may be associated with a control message transmitted via a physical sidelink control channel (PSCCH) , which may be referred to as a PSCCH message 210.
[0071] In some examples, the PSSCH message 215 (or the PSCCH message 210) may be associated with (or may indicate) multiple candidate feedback occasions associated with a PSFCH, which may be referred to as a candidate PSFCH occasion 225. A candidate PSFCH occasion may be a set of available time and frequency resources over which the UE 115-b may transmit feedback for the PSSCH message 215. For example, the PSSCH message 215 may be associated with (e.g., correspond to) N candidate PSFCH occasions 225 (e.g., via pre-configuration) , where a value range of N may include at least {1, 2, 3, 4} . In some examples (e.g., N>1) , a first set of N candidate PSFCH occasions 225 for a first PSSCH message 215 (e.g., or a first PSCCH message 210) may be associated with different time resources, frequency resources, or both, than a second set of N candidate PSFCH occasions 225 for a second PSSCH message 215 (e.g., or a second PSCCH message 210) . In such cases, the first PSSCH message 215 and the second PSSCH message 215 may be associated with non-overlapping resources (e.g., in a time domain, a frequency domain, or both) . In other words, a first set of resources associated with the first PSSCH message 215 may not overlap with a second set of resources associated with the second PSSCH message 215.
[0072] As such, the UE 115-b may transmit one or more feedback messages, indicating an ACK or a NACK, for a PSSCH message 215 via a PSFCH associated with the N candidate PSFCH occasions 225. A feedback message transmitted via the PSFCH may be referred to as a PSFCH message 230. In such cases, the UE 115-b may transmit a PSFCH message 230 via one or more of the N candidate PSFCH occasions 225. In some examples, the UE 115-b (e.g., a PSSCH message 215 receiver or a PSCCH message 210 receiver) may attempt to transmit a PSFCH message 230 for the PSSCH message 215 (e.g., or the PSCCH message 210) on a candidate PSFCH occasion 225 of the N candidate PSFCH occasions 225 based on the UE 115-b failing to transmit the PSFCH message 230 on a previous candidate PSFCH occasion 225 of the N candidate PSFCH occasions 225 due to failure of a listen-before-talk (LBT) procedure (e.g., associated with the PSFCH message 230) . In some other examples, the UE 115-b may attempt to transmit the PSFCH message 230 for the PSSCH message 215 on a candidate PSFCH occasion 225 of the N candidate PSFCH occasions 225 based on the UE 115-b failing to transmit the PSFCH message 230 on a previous candidate PSFCH occasion 225 of the N candidate PSFCH occasions 225 due to failure of an LBT procedure or due to an uplink or sidelink prioritization (e.g., a sidelink message or an uplink message is transmitted instead of the PSFCH message 230 based on the sidelink message or the uplink message being associated with a higher priority than the PSFCH message 230) . In some other examples, the UE 115-b may select which of the N candidate PSFCH occasions 225 to transmit the PSFCH message 230 (e.g., UE 115-b behavior on transmitting the PSFCH message 230 due to failure of an LBT procedure may be up to UE 115-b implementation) .
[0073] However, the UE 115-a may be unaware of which of the N candidate PSFCH occasions 225 over which the UE 115-b may transmit the one or more PSFCH messages 230. As such, the UE 115-a may be unable to determine which of the N candidate PSFCH occasions 225 to monitor for the one or more PSFCH message 230. In other words, the UE 115-a may be unaware of whether to monitor for the one or more PSFCH message 230 on each of the N candidate PSFCH occasions 225 or to terminate monitoring for the one or more PSFCH messages 230 based on receiving feedback (e.g., HARQ-ACK information) on one or more of the N candidate PSFCH occasions 225.
[0074] Accordingly, techniques described herein may enable the UE 115-a to determine or select one or more candidate PSFCH occasions 225 to monitor for one or more PSFCH message 230 associated with a PSSCH message 215. That is, techniques described herein may enable the UE 115-a to determine if or when to terminate monitoring of candidate PSFCH occasions 225 based on the cast type associated with the PSSCH message 215 and a rule associated with the cast type. That is, the PSSCH message 215 may be a unicast transmission (e.g., to the UE 115-b, as depicted in FIG. 2) , a groupcast transmission associated with NACK-only based feedback (e.g., as depicted in FIG. 3) , or a groupcast transmission associated with ACK and NACK based feedback (e.g., as depicted in FIG. 4) . Additionally, each cast type may be associated with one or more rules that indicate conditions in which the UE 115-a may terminate monitoring of subsequent candidate PSFCH occasions 225. The conditions may be based on whether the one or more PSFCH messages 230 for the PSSCH message 215 includes one or more ACKs, one or more NACKS, or both, or whether the one or more ACKs, the one or more NACKS, or both, are absent from the one or more PSFCH messages 230 associated with the PSSCH message 215. A candidate PSFCH occasion 225 monitored by the UE 115-a may be referred to as a PSFCH monitoring occasion 220.
[0075] In some implementations, as depicted in FIG. 2, the UE 115-a may transmit a unicast PSSCH message 215 to the UE 115-b, where the unicast PSSCH message 215 is associated with multiple candidate PSFCH occasions 225. In some cases, a first rule associated with unicast PSSCH messages 210 may indicate for the UE 115-a to monitor for a PSFCH message 230 on each of the multiple candidate PSFCH occasions 225 associated with the unicast PSSCH message 215. For example, as depicted in example 205-a, the UE 115-a may transmit a unicast PSSCH message 215-a (e.g., associated with a PSCCH message 210-a) , where the unicast PSSCH message 215-a is associated with multiple candidate PSFCH occasions 225. As such, the UE 115-a may monitor each of the multiple candidate PSFCH occasions 225 for a PSFCH message 230. That is, the UE 115-a may monitor for the PSFCH message 230 during a PSFCH monitoring occasion 220-a, a PSFCH monitoring occasion 220-b, a PSFCH monitoring occasion 220-c, and a PSFCH monitoring occasion 220-d. (e.g., regardless of if the PSFCH message 230 is received during monitoring of the PSFCH monitoring occasions 220) .
[0076] Additionally, or alternatively, a second rule associated with unicast PSSCH messages 210 may indicate for the UE 115-a to monitor for a PSFCH message 230 on the multiple candidate PSFCH occasions 225 associated with the unicast PSSCH message 215 starting from a first candidate PSFCH occasion 225 until the PSFCH message 230 associated with the unicast PSSCH message 215 is received (e.g., regardless of whether the PSFCH message 230 indicates ACK or NACK) . For example, as depicted in example 205-b, the UE 115-a may transmit a unicast PSSCH message 215-b (e.g., associated with a PSCCH message 210-b) , where the unicast PSSCH message 215-b is associated with multiple candidate PSFCH occasions 225. As such, the UE 115-a may monitor the multiple candidate PSFCH occasions 225 until the UE 115-a receives a PSFCH message 230, such as a PSFCH message 230-a. That is, the UE 115-a may monitor a PSFCH monitoring occasion 220-e and a PSFCH monitoring occasion 220-f, and may receive the PSFCH message 230-a during monitoring of the PSFCH monitoring occasion 220-f. As such, the UE 115-a may refrain from monitoring a candidate PSFCH occasion 225-a and a candidate PSFCH occasion 225-b based on receiving the PSFCH message 230-a during monitoring of the PSFCH monitoring occasion 220-f.
[0077] Additionally, or alternatively, a third rule associated with unicast PSSCH messages 210 may indicate for the UE 115-a to monitor for a PSFCH message 230 on the multiple candidate PSFCH occasions 225 associated with the unicast PSSCH message 215 starting from a first candidate PSFCH occasion 225 until a PSFCH message 230 indicating ACK is received. For example, as depicted in example 205-c, the UE 115-a may transmit a unicast PSSCH message 215-c (e.g., associated with a PSCCH message 210-c) , where the unicast PSSCH message 215-c is associated with multiple candidate PSFCH occasions 225. As such, the UE 115-a may monitor the multiple candidate PSFCH occasions 225 until the UE 115-a receives a PSFCH message 230 indicating ACK. However, the UE 115-a may receive a PSFCH message 230-b indicating NACK during monitoring of the multiple candidate PSFCH occasions 225 and, as such, may monitor each of the multiple candidate PSFCH occasions 225. That is, the UE 115-a may monitor for a PSFCH message 230 indicating ACK during a PSFCH monitoring occasion 220-g and a PSFCH monitoring occasion 220-h, and may receive a PSFCH message 230-b indicating NACK during monitoring of the PSFCH monitoring occasion 220-h. However, the UE 115-a may monitor a PSFCH monitoring occasion 220-j and a PSFCH monitoring occasion 220-k based on the PSFCH message 230-b indicating NACK.
[0078] Alternatively, as depicted in example 205-d, the UE 115-a may transmit a unicast PSSCH message 215-d (e.g., associated with a PSCCH message 210-d) , where the unicast PSSCH message 215-d is associated with multiple candidate PSFCH occasions 225. As described previously (e.g., according to the third rule) , the UE 115-amay monitor the multiple candidate PSFCH occasions 225 until the UE 115-a receives a PSFCH message 230 indicating ACK, such as a PSFCH message 230-c. That is, the UE 115-a may monitor for the PSFCH message 230-c during a PSFCH monitoring occasion 220-m and a PSFCH monitoring occasion 220-n, and may receive the PSFCH message 230-c during monitoring of the PSFCH monitoring occasion 220-n. As such, the UE 115-a may refrain from monitoring a candidate PSFCH occasion 225-c and a candidate PSFCH occasion 225-d based on receiving the PSFCH message 230-c indicating ACK during monitoring of the PSFCH monitoring occasion 220-n.
[0079] Though described in the context of the example 205-a, the example 205-b, the example 205-c, and the example 205-d, this is not to be regarded as a limitation of the present disclosure. In this regard, the example 205-a, the example 205-b, the example 205-c, and the example 205-d are not an exhaustive list of examples 205 in which the UE 115-a may apply the first rule, the second rule, the third rule, or any combination thereof, associated with unicast PSSCH messages 215.
[0080] FIG. 3 shows an example of a wireless communications system 300 that supports feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure. In some cases, the wireless communications system 300 may implement or be implemented by aspects of the wireless communications system 100, the wireless communications system 200, or both. For example, the wireless communications system 300 may include one or more UEs 115 (e.g., a UE 115-c, a UE 115-d, a UE 115-e, and a UE 115-f) and one or more network entities 105, which may be examples of the corresponding devices as described herein.
[0081] As described previously, techniques described herein may enable a UE 115, such as the UE 115-c, to determine if or when to terminate monitoring of candidate PSFCH occasions 325 based on the cast type associated with a PSSCH message 315 and a rule associated with the cast type. A candidate PSFCH occasion 325 monitored by the UE 115-c may be referred to as a PSFCH monitoring occasion 320.
[0082] In some implementations, as depicted in FIG. 3, the UE 115-c may transmit a groupcast PSSCH message 315 to multiple UEs 115, including at least a UE 115-d, a UE 115-e, and a UE 115-f, where the groupcast PSSCH message 315 is associated with multiple candidate PSFCH occasions 325. Additionally, the groupcast PSSCH message 315 may be associated with a first type of groupcast transmissions in which a PSFCH message 330 may indicate NACK-only. In other words, a cast type of the groupcast PSSCH message 315 may be groupcast associated with NACK-only based feedback. In such cases, the UE 115-d, the UE 115-e, the UE 115-f, or any combination thereof, may transmit a PSFCH message 330 indicating NACK based on the respective UE 115 failing to receive or decode the groupcast PSSCH message 315 and may refrain from transmitting any PSFCH message 330 based on the respective UE 115 successfully receiving and decoding the groupcast PSSCH message 315.
[0083] In some cases, a first rule associated with groupcast PSSCH messages 310 may indicate for the UE 115-c to monitor for a PSFCH message 330 (e.g., indicating NACK) on each of the multiple candidate PSFCH occasions 325 associated with the groupcast PSSCH message 315. For example, as depicted in example 305-a, the UE 115-c may transmit a groupcast PSSCH message 315-a (e.g., associated with a PSCCH message 310-a) , where the groupcast PSSCH message 315-a is associated with multiple candidate PSFCH occasions 325. As such, the UE 115-c may monitor each of the multiple candidate PSFCH occasions 325 for a PSFCH message 330. That is, the UE 115-c may monitor for the PSFCH message 330 (e.g., indicating NACK) during a PSFCH monitoring occasion 320-a, a PSFCH monitoring occasion 320-b, a PSFCH monitoring occasion 320-c, and a PSFCH monitoring occasion 320-d (e.g., regardless of if the PSFCH message 330 is received during monitoring of the PSFCH monitoring occasions 320) .
[0084] Additionally, or alternatively, a second rule associated with groupcast PSSCH messages 310 may indicate for the UE 115-c to monitor for a PSFCH message 330 on the multiple candidate PSFCH occasions 325 associated with the groupcast PSSCH message 315 starting from a first candidate PSFCH occasion 325 until a PSFCH message 330 indicating NACK is received. In other words, the UE 115-c may terminate monitoring of PSFCH monitoring occasions 320 based on receiving a PSFCH message 330 indicating NACK from at least one of the UE 115-d, the UE 115-e, and the UE 115-f. For example, as depicted in example 305-b, the UE 115-c may transmit a groupcast PSSCH message 315-b (e.g., associated with a PSCCH message 310-b) , where the groupcast PSSCH message 315-b is associated with multiple candidate PSFCH occasions 325. As such, the UE 115-c may monitor the multiple candidate PSFCH occasions 325 until the UE 115-c receives a first PSFCH message 330 indicating NACK, such as a PSFCH message 330-a. That is, the UE 115-c may monitor for the PSFCH message 330-a during a PSFCH monitoring occasion 320-e and a PSFCH monitoring occasion 320-f, and may receive the PSFCH message 330-a during monitoring of the PSFCH monitoring occasion 320-f (e.g., transmitted by the UE 115-d) . As such, the UE 115-c may refrain from monitoring a candidate PSFCH occasion 325-a and a candidate PSFCH occasion 325-b based on receiving the PSFCH message 330-a indicating NACK during monitoring of the PSFCH monitoring occasion 320-f.
[0085] In some examples, another UE 115, such as the UE 115-e, the UE 115-f, or both, may transmit a PSFCH message 330 after the UE 115-c terminates monitoring of subsequent candidate PSFCH occasions 325. For example, the UE 115-e may transmit a PSFCH message 330-b indicating NACK during the candidate PSFCH occasion 325-a. In such cases. the UE 115-c may fail to receive the PSFCH message 330-b based on terminating monitoring of subsequent candidate PSFCH occasions 325 after the PSFCH monitoring occasion 320-f. However, the UE 115-c may have previously (e.g., already) determined to retransmit the groupcast PSSCH message 315-b based on receiving the PFSCH message 330-a indicating NACK. As such, the UE 115-c may reduce power consumption based on terminating monitoring of subsequent candidate PSFCH occasions 325 after the PSFCH monitoring occasion 320-f.
[0086] Though described in the context of the example 305-a and the example 305-b, this is not to be regarded as a limitation of the present disclosure. In this regard, the example 305-a and the example 305-b are not an exhaustive list of examples 305 in which the UE 115-c may apply the first rule, the second rule, or both, associated with groupcast PSSCH messages 315 further associated with NACK-only based feedback.
[0087] FIG. 4 shows an example of a wireless communications system 400 that supports feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure. In some cases, the wireless communications system 400 may implement or be implemented by aspects of the wireless communications system 100, the wireless communications system 200, the wireless communications system 300, or any combination thereof. For example, the wireless communications system 400 may include one or more UEs 115 (e.g., a UE 115-g, a UE 115-h, a UE 115-j, a UE 115-k, and a UE 115-m) and one or more network entities 105, which may be examples of the corresponding devices as described herein.
[0088] As described previously, techniques described herein may enable a UE 115, such as the UE 115-g, to determine when to terminate monitoring of candidate PSFCH occasions 425 based on the cast type associated with a PSSCH message 415 and a rule associated with the cast type. A candidate PSFCH occasion 425 monitored by the UE 115-g may be referred to as a PSFCH monitoring occasion 420.
[0089] In some implementations, as depicted in FIG. 4, the UE 115-g may transmit a groupcast PSSCH message 415 to multiple UEs 115, including at least a UE 115-h, a UE 115-j, a UE 115-k, and a UE 115-m where the groupcast PSSCH message 415 is associated with multiple candidate PSFCH occasions 425. Additionally, the groupcast PSSCH message 415 may be associated with a second type of groupcast transmissions in which a PSFCH message 430 may indicate ACK or NACK. In other words, a cast type of the groupcast PSSCH message 415 may be groupcast associated with ACK and NACK based feedback. In such cases, the UE 115-h, the UE 115-j, the UE 115-k, the UE 115-m, or any combination thereof, may transmit a PSFCH message 430 indicating NACK based on the respective UE 115 failing to receive or decode the groupcast PSSCH message 415 and may transmit a PSFCH message 430 indicating ACK based on the respective UE 115 successfully receiving and decoding the groupcast PSSCH message 415.
[0090] In some cases, a first rule associated with groupcast PSSCH messages 410 may indicate for the UE 115-g to monitor for a PSFCH message 430 (e.g., indicating ACK or NACK) on each of the multiple candidate PSFCH occasions 425 associated with the groupcast PSSCH message 415. For example, as depicted in example 405-a, the UE 115-g may transmit a groupcast PSSCH message 415-a (e.g., associated with a PSCCH message 410-a) , where the groupcast PSSCH message 415-a is associated with multiple candidate PSFCH occasions 425. As such, the UE 115-g may monitor each of the multiple candidate PSFCH occasions 425 for a PSFCH message 430. That is, the UE 115-g may monitor for the PSFCH message 430 during a PSFCH monitoring occasion 420-a, a PSFCH monitoring occasion 420-b, a PSFCH monitoring occasion 420-c, and a PSFCH monitoring occasion 420-d (e.g., regardless of if the PSFCH message 430 is received during monitoring of the PSFCH monitoring occasions 420) .
[0091] Additionally, or alternatively, a second rule associated with groupcast PSSCH messages 410 may indicate for the UE 115-g to monitor for a PSFCH message 430 on the multiple candidate PSFCH occasions 425 associated with the groupcast PSSCH message 415 starting from a first candidate PSFCH occasion 425 until a PSFCH message 430 indicating NACK is received (e.g., from at least one UE 115) . In other words, the UE 115-g may terminate monitoring of PSFCH monitoring occasions 420 based on receiving a PSFCH message 430 indicating NACK from at least one of the UE 115-h, the UE 115-j, the UE 115-k, and the UE 115-m. For example, as depicted in example 405-b, the UE 115-g may transmit a groupcast PSSCH message 415-b (e.g., associated with a PSCCH message 410-b) , where the groupcast PSSCH message 415-b is associated with multiple candidate PSFCH occasions 425. As such, the UE 115-g may monitor the multiple candidate PSFCH occasions 425 until the UE 115-g receives a first PSFCH message 430 indicating NACK, such as a PSFCH message 430-b. That is, the UE 115-g may monitor for the PSFCH message 430-b during a PSFCH monitoring occasion 420-e and a PSFCH monitoring occasion 420-f, and may receive the PSFCH message 430-b during monitoring of the PSFCH monitoring occasion 420-f. In some examples, the UE 115-j may transmit the PSFCH message 430-b. As such, the UE 115-g may refrain from monitoring a candidate PSFCH occasion 425-a and a candidate PSFCH occasion 425-b based on receiving the PSFCH message 430-b indicating NACK during monitoring of the PSFCH monitoring occasion 420-f.
[0092] In some examples, the UE 115-h may transmit a PSFCH message 430-a during monitoring of the PSFCH monitoring occasion 420-e, however, the PSFCH message 430-a may indicate ACK. As such, the UE 115-a may continue to monitor candidate PSFCH occasions 425 after the PSFCH monitoring occasion 420-e. Additionally, or alternatively, one or more other UEs 115, such as the UE 115-k, the UE 115-m, or both, may transmit a PSFCH message 430 after the UE 115-g terminates monitoring of subsequent candidate PSFCH occasions 425. For example, the UE 115-k may transmit a PSFCH message 430-c indicating ACK during the candidate PSFCH occasion 425-a and the UE 115-m may transmit a PSFCH message 430-d indicating NACK during the candidate PSFCH occasion 425-a. In such cases, the UE 115-g may fail to receive the PSFCH message 430-c and the PSFCH message 430-d based on terminating monitoring of subsequent candidate PSFCH occasions 425 after the PSFCH monitoring occasion 420-f. However, the UE 115-g may have previously (e.g., already) determined to retransmit the groupcast PSSCH message 415-b based on receiving the PFSCH message 430-b indicating NACK. As such, the UE 115-g may reduce power consumption based on terminating monitoring of subsequent candidate PSFCH occasions 425 after the PSFCH monitoring occasion 420-f.
[0093] Additionally, or alternatively, a third rule associated with groupcast PSSCH messages 410 may indicate for the UE 115-g to monitor for a PSFCH message 430 on the multiple candidate PSFCH occasions 425 associated with the groupcast PSSCH message 415 starting from a first candidate PSFCH occasion 425 until the PSFCH message 430 associated with the groupcast PSSCH message 415 is received from each of the UEs 115 associated with the groupcast PSSCH message 415 (e.g., regardless of whether the PSFCH message 430 indicates ACK or NACK) . For example, as depicted in example 405-c, the UE 115-g may transmit a groupcast PSSCH message 415-c (e.g., associated with a PSCCH message 410-c) , where the groupcast PSSCH message 415-c is associated with multiple candidate PSFCH occasions 425. As such, the UE 115-g may monitor the multiple candidate PSFCH occasions 425 until the UE 115-g receives a PSFCH message 430 from each of the UEs 115 (e.g., the UE 115-h, the UE 115-j, the UE 115-k, and the UE 115-m) . That is, the UE 115-g may monitor for the PSFCH message 430 from each UE 115 during a PSFCH monitoring occasion 420-g, a PSFCH monitoring occasion 420-h, and a PSFCH monitoring occasion 420-j, and may receive a PSFCH message 430-e from the UE 115-h during monitoring of the PSFCH monitoring occasion 420-g, a PSFCH message 430-f from the UE 115-j during monitoring of the PSFCH monitoring occasion 420-h, and a PSFCH message 430-g from the UE 115-k and a PSFCH message 430-h from the UE 115-m during monitoring of the PSFCH monitoring occasion 420-j. As such, the UE 115-g may refrain from monitoring a candidate PSFCH occasion 425-c based on receiving the PSFCH messages 430 from each of the UEs 115 (e.g., regardless of whether the PSFCH message 430 indicate ACK or NACK) .
[0094] Additionally, or alternatively, a fourth rule associated with groupcast PSSCH messages 410 may indicate for the UE 115-g to monitor for a PSFCH message 430 on the multiple candidate PSFCH occasions 425 associated with the groupcast PSSCH message 415 starting from a first candidate PSFCH occasion 425 until a PSFCH message 430 indicating ACK is received from each of the UEs 115 associated with the groupcast PSSCH message 415. For example, as depicted in example 405-d, the UE 115-g may transmit a groupcast PSSCH message 415-d (e.g., associated with a PSCCH message 410-d) , where the groupcast PSSCH message 415-d is associated with multiple candidate PSFCH occasions 425. As such, the UE 115-g may monitor the multiple candidate PSFCH occasions 425 until the UE 115-g receives a PSFCH message 430 indicating ACK from each of the UEs 115 (e.g., the UE 115-h, the UE 115-j, the UE 115-k, and the UE 115-m) . That is, the UE 115-g may monitor for the PSFCH message 430 indicating ACK from each UE 115 during a PSFCH monitoring occasion 420-k, a PSFCH monitoring occasion 420-m, a PSFCH monitoring occasion 420-n, and a PSFCH monitoring occasion 420-o. In such cases, the UE 115-g may receive a PSFCH message 430-j from the UE 115-h during monitoring of the PSFCH monitoring occasion 420-k, a PSFCH message 430-k from the UE 115-j during monitoring of the PSFCH monitoring occasion 420-m, and a PSFCH message 430-m from the UE 115-k and a PSFCH message 430-n from the UE 115-m during monitoring of the PSFCH monitoring occasion 420-n. However, the PSFCH message 430-k and the PSFCH message 430-n may indicate NACK. As such, the UE 115-g may monitoring the PSFCH monitoring occasion 420-o (e.g., despite receiving a PSFCH message 430 from each of the UEs 115 due to the PSFCH message 430-k and the PSFCH message 430-n indicating NACK) .
[0095] Alternatively, as depicted in example 405-e, the UE 115-g may transmit a groupcast PSSCH message 415-e (e.g., associated with a PSCCH message 410-e) , where the groupcast PSSCH message 415-e is associated with multiple candidate PSFCH occasions 425. As described previously (e.g., according to the fourth rule) , the UE 115-g may monitor the multiple candidate PSFCH occasions 425 until the UE 115-g receives a PSFCH message 430 indicating ACK from each of the UEs 115 (e.g., the UE 115-h, the UE 115-j, the UE 115-k, and the UE 115-m) . That is, the UE 115-g may monitor for the PSFCH message 430 indicating ACK from each UE 115 during a PSFCH monitoring occasion 420-p, a PSFCH monitoring occasion 420-q, and a PSFCH monitoring occasion 420-r. That is, the UE 115-g may receive a PSFCH message 430-o from the UE 115-h during monitoring of the PSFCH monitoring occasion 420-p, a PSFCH message 430-p from the UE 115-j during monitoring of the PSFCH monitoring occasion 420-q, and a PSFCH message 430-q from the UE 115-k and a PSFCH message 430-r from the UE 115-m during monitoring of the PSFCH monitoring occasion 420-r, where each of the PSFCH messages 430 indicate ACK. As such, the UE 115-g may refrain from monitoring a candidate PSFCH occasion 425-d based on receiving the PSFCH messages 430 indicating ACK from each of the UEs 115 prior to the candidate PSFCH occasion 425-d.
[0096] In some examples, the UE 115-g may transmit a first PSSCH message 415 associated with a first cast type corresponding to a first set of candidate PSFCH occasions 425 and a second PSSCH message 415 associated with a second cast type (e.g., different than the first cast type) corresponding to a second set of candidate PSFCH occasions 425, where the first set of candidate PSFCH occasions 425 overlaps with the second set of candidate PSFCH occasions 425 (e.g., in a time domain, a frequency domain, or both) . In other words, the first set of candidate PSFCH occasions 425 and the second set of candidate PSFCH occasions 425 may collectively be referred to as an set of overlapping candidate PSFCH occasions 425. For example, the UE 115-g may transmit a groupcast PSSCH message 415 (e.g., associated with the first type of groupcast transmission or the second type of groupcast transmission) to the UE 115-h, the UE 115-j, the UE 115-k, and the UE 115-m and may transmit a unicast PSSCH message 415 to another UE 115. Additionally, the groupcast PSSCH message 415 and the unicast PSSCH message 415 may both correspond to a set of overlapping candidate PSFCH occasions 425.
[0097] In such cases, a first rule associated with transmission of multiple PSSCH messages 415 of mixed cast types (e.g., with different cast types) , may indicate for the UE 115-g to monitor for a PSFCH message 430 on the set of overlapping candidate PSFCH occasions 425 (e.g., associated with the first PSSCH message 415 and the second PSSCH message 415) starting from a first candidate PSFCH occasion 425 until a PSFCH message 430 is received from each of the UEs 115 associated with each PSSCH message 415 (e.g., each of the different cast types) . In other words, the UE 115-g may monitor for a PSFCH message 430 on the set of overlapping candidate PSFCH occasions 425 associated with the groupcast PSSCH message 415 and the unicast PSSCH message 415 starting from a first overlapping candidate PSFCH occasion 425 of the set of overlapping candidate PSFCH occasions 425 until a PSFCH message 430 is received from each of the UEs 115 associated with the groupcast PSSCH message 415 and the other UE 115 associated with the unicast PSSCH message 415 (e.g., regardless of whether the PSFCH messages indicate ACK or NACK) .
[0098] Though described in the context of the example 405-a, the example 405-b, the example 405-c, and the example 405-d, this is not to be regarded as a limitation of the present disclosure. In this regard, the example 405-a, the example 405-b, the example 405-c, and the example 405-d are not an exhaustive list of examples 405 in which the UE 115-g may apply the first rule, the second rule, the third rule, the fourth rule, or any combination thereof, associated with groupcast PSSCH messages 415 further associated with ACK and NACK based feedback.
[0099] FIG. 5 shows an example of a process flow 500 that supports feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure. In some cases, the process flow 500 may implement or be implemented by aspects of the wireless communications system 100, the wireless communications system 200, the wireless communications system 300, the wireless communications system 400, or any combination thereof. For example, the process flow 500 may include one or more UEs 115 (e.g., a UE 115-n, a UE 115-o, and a UE 115-p) and one or more network entities 105, which may be examples of the corresponding devices as described herein.
[0100] At 505, the UE 115-n may transmit, via a sidelink shared channel (e.g., PSSCH) a first sidelink message (e.g., PSSCH transmission) to one or more other UEs 115, such as the UE 115-o. The first sidelink message may correspond to a first set of feedback monitoring occasions (e.g., PSFCH monitoring occasions, candidate PSFCH occasions) for first feedback (e.g., ACK or NACK) associated with the first sidelink message. In such cases, the first sidelink message may be of a first cast type of a multiple cast types, where the multiple cast types includes at least unicast, a groupcast type 1, and a groupcast type 2. The groupcast type 1 may be groupcast associated with NACK-only based feedback and the groupcast type 2 may be groupcast associated with ACK and NACK based feedback.
[0101] In some examples, at 510, the UE 115-n may transmit, via the sidelink shared channel, a second sidelink message to one or more additional UEs 115 (e.g., different than the one or more other UEs 115) , such as the UE 115-p. The second sidelink message may correspond to a second set of feedback monitoring occasions for second feedback associated with the second sidelink message. In such cases, the second sidelink message may be of a second cast type (e.g., different than the first cast type) of the multiple cast types. Additionally, the second set of feedback monitoring occasions may overlap with the first set of feedback monitoring occasions. As such, the first set of feedback monitoring occasions and the second set of feedback monitoring occasions may be collectively referred to as a set of overlapping feedback monitoring occasions.
[0102] At 515, the UE 115-n may monitor, after transmitting the first sidelink message, one or more feedback monitoring occasions of the first set of feedback monitoring occasions for the first feedback associated with the first sidelink message from the one or more other UEs 115 (e.g., the UE 115-o) . In such cases, the one or more feedback monitoring occasions may be based on the first cast type. Additionally, the one or more feedback monitoring occasions may be based on a rule associated with reception of first feedback associated with the first sidelink message via at least one of the one or more feedback monitoring occasions. In such cases, the rule may be based on the first cast type and whether the first feedback associated with the first sidelink message includes one or more ACKs, one or more NACKS, or both, or whether the first feedback includes an absence of the one or more ACKs, the one or more NACKs, or both.
[0103] In some examples, to monitor the one or more feedback monitoring occasions, the UE 115-n may monitor each feedback monitoring occasion of the first set of monitoring occasions (e.g., regardless of which of the multiple cast types is the first cast type) .
[0104] In some other examples, the first cast type may be unicast and, at 520, the UE 115-n may receive the first feedback associated with the first sidelink message during monitoring of a first feedback monitoring occasions of the first set of feedback monitoring occasions. As such, the UE 115-n, at 530, may terminate the monitoring of each subsequent feedback monitoring occasion of the first set of feedback monitoring occasions based on receiving the first feedback associated with the first sidelink message during the monitoring of the first feedback monitoring occasion. Conversely, the UE 115-n may fail to receive the first feedback associated with the first sidelink message during monitoring of the first feedback monitoring occasions of the first set of feedback monitoring occasions. As such, the UE 115-n may monitor a second feedback monitoring occasion of the first set of feedback monitoring occasions based on an absence of the first feedback associated with the first sidelink message during monitoring of the first feedback monitoring occasions.
[0105] In some other examples, the first cast type may be unicast and, at 520, the UE 115-n may receive an ACK message (e.g., positive acknowledgment message) associated with the first sidelink message during monitoring of the first feedback monitoring occasions of the first set of feedback monitoring occasions (e.g., the first feedback includes the ACK message) . As such, the UE 115-n, at 530, may terminate the monitoring of each subsequent feedback monitoring occasion of the first set of feedback monitoring occasions based on receiving the ACK message associated with the first sidelink message during the monitoring of the first feedback monitoring occasion. Conversely, the UE 115-n may fail to receive the ACK message associated with the first sidelink message during monitoring of the first feedback monitoring occasions of the first set of feedback monitoring occasions. As such, the UE 115-n may monitor the second feedback monitoring occasion of the first set of feedback monitoring occasions based on an absence of the ACK message associated with the first sidelink message during monitoring of the first feedback monitoring occasions.
[0106] In some other example, the first cast type may be groupcast type 1 and, at 520, the UE 115-n may receive a NACK message (e.g., negative acknowledgment message) associated with the first sidelink message during monitoring of the first feedback monitoring occasions of the first set of feedback monitoring occasions (e.g., the first feedback includes the NACK message) . As such, the UE 115-n, at 530, may terminate the monitoring of each subsequent feedback monitoring occasion of the first set of feedback monitoring occasions based on receiving the NACK message associated with the first sidelink message during the monitoring of the first feedback monitoring occasion. Conversely, the UE 115-n may fail to receive the NACK message associated with the first sidelink message during monitoring of the first feedback monitoring occasions of the first set of feedback monitoring occasions. As such, the UE 115-n may monitor the second feedback monitoring occasion of the first set of feedback monitoring occasions based on an absence of the NACK message associated with the first sidelink message during monitoring of the first feedback monitoring occasions.
[0107] In some other examples, the first cast type may be groupcast type 2 and, at 520, the UE 115-n may receive a NACK message associated with the first sidelink message during monitoring of the first feedback monitoring occasions of the first set of feedback monitoring occasions (e.g., the first feedback includes the NACK message) . As such, the UE 115-n, at 530, may terminate the monitoring of each subsequent feedback monitoring occasion of the first set of feedback monitoring occasions based on receiving the NACK message associated with the first sidelink message during the monitoring of the first feedback monitoring occasion. Conversely, the UE 115-n may fail to receive the NACK message associated with the first sidelink message during monitoring of the first feedback monitoring occasions of the first set of feedback monitoring occasions. As such, the UE 115-n may monitor the second feedback monitoring occasion of the first set of feedback monitoring occasions based on an absence of the NACK message associated with the first sidelink message during monitoring of the first feedback monitoring occasions.
[0108] In some other examples, the first cast type may be groupcast type 2 and, at 520, the UE 115-n may receive, from each of the one or more other UEs 115, the first feedback associated with the first sidelink message during monitoring of a first feedback monitoring occasions of the first set of feedback monitoring occasions. As such, the UE 115-n, at 530, may terminate the monitoring of each subsequent feedback monitoring occasion of the first set of feedback monitoring occasions based on receiving, from each of the one or more other UEs 115, the first feedback associated with the first sidelink message during the monitoring of the first feedback monitoring occasion. Conversely, the UE 115-n may fail to receive the first feedback associated with the first sidelink message during monitoring of the first feedback monitoring occasions from each of the one or more other UEs 115. As such, the UE 115-n may monitor a second feedback monitoring occasion of the first set of feedback monitoring occasions based on an absence of the first feedback associated with the first sidelink message from each of the one or more other UEs 115 during monitoring of the first feedback monitoring occasions.
[0109] In some other examples, the first cast type may be groupcast type 2 and, at 520, the UE 115-n may receive, from each of the one or more other UEs 115, an ACK message associated with the first sidelink message during monitoring of the first feedback monitoring occasions of the first set of feedback monitoring occasions (e.g., the first feedback includes the ACK messages) . As such, the UE 115-n, at 530, may terminate the monitoring of each subsequent feedback monitoring occasion of the first set of feedback monitoring occasions based on receiving the ACK messages associated with the first sidelink message from each of the one or more other UEs 115 during the monitoring of the first feedback monitoring occasion. Conversely, the UE 115-n may fail to receive the ACK messages associated with the first sidelink message from each of the one or more other UEs 115 during monitoring of the first feedback monitoring occasions. As such, the UE 115-n may monitor the second feedback monitoring occasion of the first set of feedback monitoring occasions based on an absence of the ACK message associated with the first sidelink message from each of the one or more other UEs 115 during monitoring of the first feedback monitoring occasions.
[0110] In some other examples, the UE 115-n may receive, at 520 and at 525, during a first overlapping feedback monitoring occasions of the set of overlapping feedback monitoring occasions, the first feedback associated with the first sidelink message from each of the other or more other UEs 115 and the second feedback associated with the second sidelink message from each of the one or more additional UEs 115. As such, the UE 115-n, at 530, may terminate the monitoring of each subsequent feedback monitoring occasions of the first set of feedback monitoring occasions and the second set of feedback monitoring occasions based on receiving, during the monitoring of the first overlapping feedback monitoring occasion, the first feedback associated with the first sidelink message from each of the other or more other UEs 115 and the second feedback associated with the second sidelink message from each of the one or more additional UEs 115. Conversely, the UE 115-n may fail to receive the first feedback associated with the first sidelink message from each of the other or more other UEs 115 and the second feedback associated with the second sidelink message from each of the one or more additional UEs 115 during the first overlapping feedback monitoring occasions. As such, the UE 115-n may monitor a second overlapping feedback monitoring occasion of the set of overlapping feedback monitoring occasions based on an absence of the first feedback associated with the first sidelink message from each of the other or more other UEs 115 and the second feedback associated with the second sidelink message from each of the one or more additional UEs 115 during the first overlapping feedback monitoring occasions.
[0111] FIG. 6 shows a block diagram 600 of a device 605 that supports feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure. The device 605 may be an example of aspects of a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. The device 605, or one or more components of the device 605 (e.g., the receiver 610, the transmitter 615, and the communications manager 620) , may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
[0112] The receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to feedback monitoring for multiple feedback occasions) . Information may be passed on to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.
[0113] The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to feedback monitoring for multiple feedback occasions) . In some examples, the transmitter 615 may be co-located with a receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a set of multiple antennas.
[0114] The communications manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof may be examples of means for performing various aspects of feedback monitoring for multiple feedback occasions as described herein. For example, the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be capable of performing one or more of the functions described herein.
[0115] In some examples, the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include at least one of a processor, a digital signal processor (DSP) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .
[0116] Additionally, or alternatively, the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functions of the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .
[0117] In some examples, the communications manager 620 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.
[0118] The communications manager 620 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 620 is capable of, configured to, or operable to support a means for transmitting, via a sidelink shared channel, a sidelink message to one or more second UEs, the sidelink message corresponding to a set of multiple feedback monitoring occasions for feedback associated with the sidelink message, where the sidelink message is of a first cast type of a set of multiple cast types. The communications manager 620 is capable of, configured to, or operable to support a means for monitoring, after transmitting the sidelink message, one or more feedback monitoring occasions of the set of multiple feedback monitoring occasions for the feedback associated with the sidelink message from the one or more second UEs, where the one or more feedback monitoring occasions are based on the first cast type.
[0119] By including or configuring the communications manager 620 in accordance with examples as described herein, the device 605 (e.g., at least one processor controlling or otherwise coupled with the receiver 610, the transmitter 615, the communications manager 620, or a combination thereof) may support techniques for feedback monitoring for multiple PSFCH occasions, which may result in reduced processing, reduced power consumption, and more efficient utilization of communication resources, among other advantages.
[0120] FIG. 7 shows a block diagram 700 of a device 705 that supports feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure. The device 705 may be an example of aspects of a device 605 or a UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communications manager 720. The device 705, or one of more components of the device 705 (e.g., the receiver 710, the transmitter 715, and the communications manager 720) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
[0121] The receiver 710 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to feedback monitoring for multiple feedback occasions) . Information may be passed on to other components of the device 705. The receiver 710 may utilize a single antenna or a set of multiple antennas.
[0122] The transmitter 715 may provide a means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to feedback monitoring for multiple feedback occasions) . In some examples, the transmitter 715 may be co-located with a receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a set of multiple antennas.
[0123] The device 705, or various components thereof, may be an example of means for performing various aspects of feedback monitoring for multiple feedback occasions as described herein. For example, the communications manager 720 may include a messaging component 725, a monitoring component 730, or any combination thereof. The communications manager 720 may be an example of aspects of a communications manager 620 as described herein. In some examples, the communications manager 720, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 710, the transmitter 715, or both. For example, the communications manager 720 may receive information from the receiver 710, send information to the transmitter 715, or be integrated in combination with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.
[0124] The communications manager 720 may support wireless communications in accordance with examples as disclosed herein. The messaging component 725 is capable of, configured to, or operable to support a means for transmitting, via a sidelink shared channel, a sidelink message to one or more second UEs, the sidelink message corresponding to a set of multiple feedback monitoring occasions for feedback associated with the sidelink message, where the sidelink message is of a first cast type of a set of multiple cast types. The monitoring component 730 is capable of, configured to, or operable to support a means for monitoring, after transmitting the sidelink message, one or more feedback monitoring occasions of the set of multiple feedback monitoring occasions for the feedback associated with the sidelink message from the one or more second UEs, where the one or more feedback monitoring occasions are based on the first cast type.
[0125] In some cases, the messaging component 725 and the monitoring component 730 may each be or be at least a part of at least one processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor) . The at least one processor may be coupled with 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 messaging component 725 and the monitoring component 730 discussed herein. A transceiver processor may be collocated with and / or communicate with (e.g., direct the operations of) a transceiver of the device. A radio processor may be collocated with and / or communicate with (e.g., direct the operations of) a radio (e.g., an NR radio, an LTE radio, a Wi-Fi radio) of the device. A transmitter processor may be collocated with and / or communicate with (e.g., direct the operations of) a transmitter of the device. A receiver processor may be collocated with and / or communicate with (e.g., direct the operations of) a receiver of the device.
[0126] FIG. 8 shows a block diagram 800 of a communications manager 820 that supports feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure. The communications manager 820 may be an example of aspects of a communications manager 620, a communications manager 720, or both, as described herein. The communications manager 820, or various components thereof, may be an example of means for performing various aspects of feedback monitoring for multiple feedback occasions as described herein. For example, the communications manager 820 may include a messaging component 825, a monitoring component 830, a feedback component 835, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories) , may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
[0127] The communications manager 820 may support wireless communications in accordance with examples as disclosed herein. The messaging component 825 is capable of, configured to, or operable to support a means for transmitting, via a sidelink shared channel, a sidelink message to one or more second UEs, the sidelink message corresponding to a set of multiple feedback monitoring occasions for feedback associated with the sidelink message, where the sidelink message is of a first cast type of a set of multiple cast types. The monitoring component 830 is capable of, configured to, or operable to support a means for monitoring, after transmitting the sidelink message, one or more feedback monitoring occasions of the set of multiple feedback monitoring occasions for the feedback associated with the sidelink message from the one or more second UEs, where the one or more feedback monitoring occasions are based on the first cast type.
[0128] In some examples, to support monitoring the one or more feedback monitoring occasions, the monitoring component 830 is capable of, configured to, or operable to support a means for monitoring each feedback monitoring occasion of the set of multiple feedback monitoring occasions, where the first cast type is unicast or groupcast.
[0129] In some examples, the first cast type is unicast, and the feedback component 835 is capable of, configured to, or operable to support a means for receiving the feedback associated with the sidelink message during monitoring of the first feedback monitoring occasion based on the monitoring. In some examples, the first cast type is unicast, and the monitoring component 830 is capable of, configured to, or operable to support a means for terminating the monitoring of each subsequent feedback monitoring occasion of the set of multiple feedback monitoring occasions based on receiving the feedback associated with the sidelink message during the monitoring of the first feedback monitoring occasion.
[0130] In some examples, to support monitoring the one or more feedback monitoring occasions, the monitoring component 830 is capable of, configured to, or operable to support a means for monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message. In some examples, to support monitoring the one or more feedback monitoring occasions, the monitoring component 830 is capable of, configured to, or operable to support a means for monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based on absence of the feedback associated with the sidelink message during monitoring of the first feedback monitoring occasion.
[0131] In some examples, the first cast type is unicast, and the feedback component 835 is capable of, configured to, or operable to support a means for receiving a positive acknowledgment message during monitoring of the first feedback monitoring occasion, where the feedback associated with the sidelink message includes the positive acknowledgment message. In some examples, the first cast type is unicast, and the monitoring component 830 is capable of, configured to, or operable to support a means for terminating the monitoring of each subsequent feedback monitoring occasion of the set of multiple feedback monitoring occasions based on receiving the positive acknowledgment message during the monitoring of the first feedback monitoring occasion.
[0132] In some examples, to support monitoring the one or more feedback monitoring occasions, the monitoring component 830 is capable of, configured to, or operable to support a means for monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message. In some examples, to support monitoring the one or more feedback monitoring occasions, the monitoring component 830 is capable of, configured to, or operable to support a means for monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based on absence of a positive acknowledgment message during monitoring of the first feedback monitoring occasion, where the feedback associated with the sidelink message includes the positive acknowledgment message.
[0133] In some examples, the first cast type is groupcast associated with negative acknowledgment-only based feedback, and the feedback component 835 is capable of, configured to, or operable to support a means for receiving a negative acknowledgment message during monitoring of the first feedback monitoring occasion based on the monitoring, where the feedback associated with the sidelink message includes the negative acknowledgment message. In some examples, the first cast type is groupcast associated with negative acknowledgment-only based feedback, and the monitoring component 830 is capable of, configured to, or operable to support a means for terminating the monitoring of each subsequent feedback monitoring occasions of the set of multiple feedback monitoring occasions based on receiving the negative acknowledgment message during the monitoring of the first feedback monitoring occasion.
[0134] In some examples, to support monitoring the one or more feedback monitoring occasions, the monitoring component 830 is capable of, configured to, or operable to support a means for monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message. In some examples, to support monitoring the one or more feedback monitoring occasions, the monitoring component 830 is capable of, configured to, or operable to support a means for monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based on absence of a negative acknowledgment message during monitoring of the first feedback monitoring occasion, where the feedback associated with the sidelink message includes the negative acknowledgment message.
[0135] In some examples, the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and the feedback component 835 is capable of, configured to, or operable to support a means for receiving, from at least one of the one or more second UEs, a negative acknowledgment message during monitoring of the first feedback monitoring occasion based on the monitoring, where the feedback associated with the sidelink message includes the negative acknowledgment message. In some examples, the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and the monitoring component 830 is capable of, configured to, or operable to support a means for terminating the monitoring of each subsequent feedback monitoring occasions of the set of multiple feedback monitoring occasions based on receiving the negative acknowledgment message from the at least one of the one or more second UEs during the monitoring of the first feedback monitoring occasion.
[0136] In some examples, to support monitoring the one or more feedback monitoring occasions, the monitoring component 830 is capable of, configured to, or operable to support a means for monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message. In some examples, to support monitoring the one or more feedback monitoring occasions, the monitoring component 830 is capable of, configured to, or operable to support a means for monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based on absence of a negative acknowledgment message from at least one of the one or more second UEs during monitoring of the first feedback monitoring occasion, where the feedback associated with the sidelink message includes the negative acknowledgment message.
[0137] In some examples, the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and the feedback component 835 is capable of, configured to, or operable to support a means for receiving, from each of the one or more second UEs, the feedback associated with the sidelink message during monitoring of the first feedback monitoring occasion based on the monitoring. In some examples, the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and the monitoring component 830 is capable of, configured to, or operable to support a means for terminating the monitoring of each subsequent feedback monitoring occasions of the set of multiple feedback monitoring occasions based on receiving the feedback associated with the sidelink message from each of the one or more second UEs during the monitoring of the first feedback monitoring occasion.
[0138] In some examples, to support monitoring the one or more feedback monitoring occasions, the monitoring component 830 is capable of, configured to, or operable to support a means for monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message. In some examples, to support monitoring the one or more feedback monitoring occasions, the monitoring component 830 is capable of, configured to, or operable to support a means for monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based on absence of the feedback associated with the sidelink message from each of the one or more second UEs during monitoring of the first feedback monitoring occasion.
[0139] In some examples, the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and the feedback component 835 is capable of, configured to, or operable to support a means for receiving, from each of the one or more second UEs, a positive acknowledgment message during monitoring of the first feedback monitoring occasion based on the monitoring, where the feedback associated with the sidelink message includes the positive acknowledgment message. In some examples, the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and the monitoring component 830 is capable of, configured to, or operable to support a means for terminating the monitoring of each subsequent feedback monitoring occasions of the set of multiple feedback monitoring occasions based on receiving the positive acknowledgment message from each of the one or more second UEs during the monitoring of the first feedback monitoring occasion.
[0140] In some examples, to support monitoring the one or more feedback monitoring occasions, the monitoring component 830 is capable of, configured to, or operable to support a means for monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message. In some examples, to support monitoring the one or more feedback monitoring occasions, the monitoring component 830 is capable of, configured to, or operable to support a means for monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based on absence of a positive acknowledgment message from each of the one or more second UEs during monitoring of the first feedback monitoring occasion, where the feedback associated with the sidelink message includes the positive acknowledgment message.
[0141] In some examples, the messaging component 825 is capable of, configured to, or operable to support a means for transmitting, via the sidelink shared channel, a second sidelink message to one or more third UEs, the second sidelink message corresponding to a second set of multiple feedback monitoring occasions for second feedback associated with the second sidelink message, where the second sidelink message is of a second cast type of the set of multiple cast types, and where the second set of multiple feedback monitoring occasions overlap with the set of multiple feedback monitoring occasions.
[0142] In some examples, the one or more feedback monitoring occasions includes an overlapping feedback monitoring occasion associated with the set of multiple feedback monitoring occasions and the second set of multiple feedback monitoring occasions, and the feedback component 835 is capable of, configured to, or operable to support a means for receiving, during monitoring of the overlapping feedback monitoring occasion, the feedback associated with the sidelink message from each of the one or more second UEs and the second feedback associated with the second sidelink message from each of the one or more third UEs. In some examples, the one or more feedback monitoring occasions includes an overlapping feedback monitoring occasion associated with the set of multiple feedback monitoring occasions and the second set of multiple feedback monitoring occasions, and the monitoring component 830 is capable of, configured to, or operable to support a means for terminating the monitoring of each subsequent feedback monitoring occasions of the set of multiple feedback monitoring occasions and the second set of multiple feedback monitoring occasions based on receiving, during the monitoring of the overlapping feedback monitoring occasion, the feedback associated with the sidelink message from each of the one or more second UEs and the second feedback associated with the second sidelink message from each of the one or more third UEs.
[0143] In some examples, to support monitoring the one or more feedback monitoring occasions, the monitoring component 830 is capable of, configured to, or operable to support a means for monitoring a first overlapping feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message and for the second feedback associated with the second sidelink message, where the first overlapping feedback monitoring occasion is associated with the set of multiple feedback monitoring occasions and the second set of multiple feedback monitoring occasions. In some examples, to support monitoring the one or more feedback monitoring occasions, the monitoring component 830 is capable of, configured to, or operable to support a means for monitoring a second overlapping feedback monitoring occasion of the one or more feedback monitoring occasions based on absence of, during the monitoring of the first overlapping feedback monitoring occasion, the feedback associated with the sidelink message from each of the one or more second UEs and the second feedback associated with the second sidelink message from each of the one or more third UEs, where the second overlapping feedback monitoring occasion is associated with the set of multiple feedback monitoring occasions and the second set of multiple feedback monitoring occasions.
[0144] In some examples, the one or more feedback monitoring occasions are based on a rule associated with reception of the feedback associated with the sidelink message via at least one of the one or more feedback monitoring occasions.
[0145] In some examples, the rule is based on the first cast type and whether the feedback associated with the sidelink message includes one or more positive acknowledgment messages, one or more negative acknowledgment message, or both, or includes an absence of the one or more positive acknowledgment messages, an absence of the one or more negative acknowledgment message, or both, during at least one of the set of multiple feedback monitoring occasions.
[0146] In some cases, the messaging component 825, the monitoring component 830, and the feedback component 835 may each be or be at least a part of at least one processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor) . The at least one processor may be coupled with 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 messaging component 825, the monitoring component 830, and the feedback component 835 discussed herein.
[0147] FIG. 9 shows a diagram of a system 900 including a device 905 that supports feedback monitoring for multiple feedback occasions in accordance with one or more aspects of the present disclosure. The device 905 may be an example of or include the components of a device 605, a device 705, or a UE 115 as described herein. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, at least one memory 930, code 935, and at least one processor 940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 945) .
[0148] The I / O controller 910 may manage input and output signals for the device 905. The I / O controller 910 may also manage peripherals not integrated into the device 905. In some cases, the I / O controller 910 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 910 may utilize an operating system such as or another known operating system. Additionally, or alternatively, the I / O controller 910 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I / O controller 910 may be implemented as part of one or more processors, such as the at least one processor 940. In some cases, a user may interact with the device 905 via the I / O controller 910 or via hardware components controlled by the I / O controller 910.
[0149] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 915 may communicate bi-directionally, via the one or more antennas 925, wired, or wireless links as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 915 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 925 for transmission, and to demodulate packets received from the one or more antennas 925. The transceiver 915, or the transceiver 915 and one or more antennas 925, may be an example of a transmitter 615, a transmitter 715, a receiver 610, a receiver 710, or any combination thereof or component thereof, as described herein.
[0150] The at least one memory 930 may include random access memory (RAM) and read-only memory (ROM) . The at least one memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by the at least one processor 940, cause the device 905 to perform various functions described herein. The code 935 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 935 may not be directly executable by the at least one processor 940 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 930 may contain, among other things, a basic I / O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
[0151] The at least one processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some cases, the at least one processor 940 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 940. The at least one processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks supporting feedback monitoring for multiple feedback occasions) . For example, the device 905 or a component of the device 905 may include at least one processor 940 and at least one memory 930 coupled with or to the at least one processor 940, the at least one processor 940 and at least one memory 930 configured to perform various functions described herein. In some examples, the at least one processor 940 may include multiple processors and the at least one memory 930 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
[0152] The communications manager 920 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 920 is capable of, configured to, or operable to support a means for transmitting, via a sidelink shared channel, a sidelink message to one or more second UEs, the sidelink message corresponding to a set of multiple feedback monitoring occasions for feedback associated with the sidelink message, where the sidelink message is of a first cast type of a set of multiple cast types. The communications manager 920 is capable of, configured to, or operable to support a means for monitoring, after transmitting the sidelink message, one or more feedback monitoring occasions of the set of multiple feedback monitoring occasions for the feedback associated with the sidelink message from the one or more second UEs, where the one or more feedback monitoring occasions are based on the first cast type.
[0153] By including or configuring the communications manager 920 in accordance with examples as described herein, the device 905 may support techniques for feedback monitoring for multiple PSFCH occasions, which may result in improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, and improved utilization of processing capability, among other advantages.
[0154] In some examples, the communications manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 915, the one or more antennas 925, or any combination thereof. Although the communications manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 920 may be supported by or performed by the at least one processor 940, the at least one memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions executable by the at least one processor 940 to cause the device 905 to perform various aspects of feedback monitoring for multiple feedback occasions as described herein, or the at least one processor 940 and the at least one memory 930 may be otherwise configured to, individually or collectively, perform or support such operations.
[0155] FIG. 10 shows a flowchart illustrating a method 1000 that supports feedback monitoring for multiple feedback occasions in accordance with aspects of the present disclosure. The operations of the method 1000 may be implemented by a UE or its components as described herein. For example, the operations of the method 1000 may be performed by a UE 115 as described with reference to FIGs. 1 through 9. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
[0156] At 1005, the method may include transmitting, via a sidelink shared channel, a sidelink message to one or more second UEs, the sidelink message corresponding to a set of multiple feedback monitoring occasions for feedback associated with the sidelink message, where the sidelink message is of a first cast type of a set of multiple cast types. The operations of block 1005 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1005 may be performed by a messaging component 825 as described with reference to FIG. 8.
[0157] At 1010, the method may include monitoring, after transmitting the sidelink message, one or more feedback monitoring occasions of the set of multiple feedback monitoring occasions for the feedback associated with the sidelink message from the one or more second UEs, where the one or more feedback monitoring occasions are based on the first cast type. The operations of block 1010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1010 may be performed by a monitoring component 830 as described with reference to FIG. 8.
[0158] FIG. 11 shows a flowchart illustrating a method 1100 that supports feedback monitoring for multiple feedback occasions in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by a UE or its components as described herein. For example, the operations of the method 1100 may be performed by a UE 115 as described with reference to FIGs. 1 through 9. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
[0159] At 1105, the method may include transmitting, via a sidelink shared channel, a sidelink message to one or more second UEs, the sidelink message corresponding to a set of multiple feedback monitoring occasions for feedback associated with the sidelink message, where the sidelink message is of a first cast type of a set of multiple cast types. The operations of block 1105 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1105 may be performed by a messaging component 825 as described with reference to FIG. 8.
[0160] At 1110, the method may include monitoring, after transmitting the sidelink message, one or more feedback monitoring occasions of the set of multiple feedback monitoring occasions for the feedback associated with the sidelink message from the one or more second UEs, where the one or more feedback monitoring occasions are based on the first cast type. The operations of block 1110 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1110 may be performed by a monitoring component 830 as described with reference to FIG. 8.
[0161] At 1115, the method may include transmitting, via the sidelink shared channel, a second sidelink message to one or more third UEs, the second sidelink message corresponding to a second set of multiple feedback monitoring occasions for second feedback associated with the second sidelink message, where the second sidelink message is of a second cast type of the set of multiple cast types, and where the second set of multiple feedback monitoring occasions overlap with the set of multiple feedback monitoring occasions. The operations of block 1115 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1115 may be performed by a messaging component 825 as described with reference to FIG. 8.
[0162] The following provides an overview of aspects of the present disclosure:
[0163] Aspect 1: A method for wireless communications at a first UE, comprising: transmitting, 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 feedback associated with the sidelink message, wherein the sidelink message is of a first cast type of a plurality of cast types; and monitoring, after transmitting the sidelink message, one or more feedback monitoring occasions of the plurality of feedback monitoring occasions for the feedback associated with the sidelink message from the one or more second UEs, wherein the one or more feedback monitoring occasions are based at least in part on the first cast type.
[0164] Aspect 2: The method of aspect 1, wherein monitoring the one or more feedback monitoring occasions comprises: monitoring each feedback monitoring occasion of the plurality of feedback monitoring occasions, wherein the first cast type is unicast or groupcast.
[0165] Aspect 3: The method of aspect 1, wherein the first cast type is unicast, and wherein the one or more feedback monitoring occasions comprises a first feedback monitoring occasion, the method further comprising: receiving the feedback associated with the sidelink message during monitoring of the first feedback monitoring occasion based at least in part on the monitoring; and terminating the monitoring of each subsequent feedback monitoring occasion of the plurality of feedback monitoring occasions based at least in part on receiving the feedback associated with the sidelink message during the monitoring of the first feedback monitoring occasion.
[0166] Aspect 4: The method of aspect 1, wherein the first cast type is unicast, and wherein monitoring the one or more feedback monitoring occasions comprises: monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message; and monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of the feedback associated with the sidelink message during monitoring of the first feedback monitoring occasion.
[0167] Aspect 5: The method of aspect 1, wherein the first cast type is unicast, and wherein the one or more feedback monitoring occasions comprises a first feedback monitoring occasion, the method further comprising: receiving a positive acknowledgment message during monitoring of the first feedback monitoring occasion, wherein the feedback associated with the sidelink message comprises the positive acknowledgment message; and terminating the monitoring of each subsequent feedback monitoring occasion of the plurality of feedback monitoring occasions based at least in part on receiving the positive acknowledgment message during the monitoring of the first feedback monitoring occasion.
[0168] Aspect 6: The method of aspect 1, wherein the first cast type is unicast, and wherein monitoring the one or more feedback monitoring occasions comprises: monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message; and monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of a positive acknowledgment message during monitoring of the first feedback monitoring occasion, wherein the feedback associated with the sidelink message comprises the positive acknowledgment message.
[0169] Aspect 7: The method of aspect 1, wherein the first cast type is groupcast associated with negative acknowledgment-only based feedback, and wherein the one or more feedback monitoring occasions comprises a first feedback monitoring occasion, the method further comprising: receiving a negative acknowledgment message during monitoring of the first feedback monitoring occasion based at least in part on the monitoring, wherein the feedback associated with the sidelink message comprises the negative acknowledgment message; and terminating the monitoring of each subsequent feedback monitoring occasions of the plurality of feedback monitoring occasions based at least in part on receiving the negative acknowledgment message during the monitoring of the first feedback monitoring occasion.
[0170] Aspect 8: The method of aspect 1, wherein the first cast type is groupcast associated with negative acknowledgment-only based feedback, and wherein monitoring the one or more feedback monitoring occasions comprises: monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message; and monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of a negative acknowledgment message during monitoring of the first feedback monitoring occasion, wherein the feedback associated with the sidelink message comprises the negative acknowledgment message.
[0171] Aspect 9: The method of aspect 1, wherein the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and wherein the one or more feedback monitoring occasions comprises a first feedback monitoring occasion, the method further comprising: receiving, from at least one of the one or more second UEs, a negative acknowledgment message during monitoring of the first feedback monitoring occasion based at least in part on the monitoring, wherein the feedback associated with the sidelink message comprises the negative acknowledgment message; and terminating the monitoring of each subsequent feedback monitoring occasions of the plurality of feedback monitoring occasions based at least in part on receiving the negative acknowledgment message from the at least one of the one or more second UEs during the monitoring of the first feedback monitoring occasion.
[0172] Aspect 10: The method of aspect 1, wherein the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and wherein monitoring the one or more feedback monitoring occasions comprises: monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message; and monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of a negative acknowledgment message from at least one of the one or more second UEs during monitoring of the first feedback monitoring occasion, wherein the feedback associated with the sidelink message comprises the negative acknowledgment message.
[0173] Aspect 11: The method of aspect 1, wherein the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and wherein the one or more feedback monitoring occasions comprises a first feedback monitoring occasion, the method further comprising: receiving, from each of the one or more second UEs, the feedback associated with the sidelink message during monitoring of the first feedback monitoring occasion based at least in part on the monitoring; and terminating the monitoring of each subsequent feedback monitoring occasions of the plurality of feedback monitoring occasions based at least in part on receiving the feedback associated with the sidelink message from each of the one or more second UEs during the monitoring of the first feedback monitoring occasion.
[0174] Aspect 12: The method of aspect 1, wherein the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and wherein monitoring the one or more feedback monitoring occasions comprises: monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message; and monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of the feedback associated with the sidelink message from each of the one or more second UEs during monitoring of the first feedback monitoring occasion.
[0175] Aspect 13: The method of aspect 1, wherein the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and wherein the one or more feedback monitoring occasions comprises a first feedback monitoring occasion, the method further comprising: receiving, from each of the one or more second UEs, a positive acknowledgment message during monitoring of the first feedback monitoring occasion based at least in part on the monitoring, wherein the feedback associated with the sidelink message comprises the positive acknowledgment message; and terminating the monitoring of each subsequent feedback monitoring occasions of the plurality of feedback monitoring occasions based at least in part on receiving the positive acknowledgment message from each of the one or more second UEs during the monitoring of the first feedback monitoring occasion.
[0176] Aspect 14: The method of aspect 1, wherein the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and wherein monitoring the one or more feedback monitoring occasions comprises: monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message; and monitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of a positive acknowledgment message from each of the one or more second UEs during monitoring of the first feedback monitoring occasion, wherein the feedback associated with the sidelink message comprises the positive acknowledgment message.
[0177] Aspect 15: The method of aspect 1, further comprising: transmitting, via the sidelink shared channel, a second sidelink message to one or more third UEs, the second sidelink message corresponding to a second plurality of feedback monitoring occasions for second feedback associated with the second sidelink message, wherein the second sidelink message is of a second cast type of the plurality of cast types, and wherein the second plurality of feedback monitoring occasions overlap with the plurality of feedback monitoring occasions.
[0178] Aspect 16: The method of aspect 15, wherein the one or more feedback monitoring occasions comprises an overlapping feedback monitoring occasion associated with the plurality of feedback monitoring occasions and the second plurality of feedback monitoring occasions, the method further comprising: receiving, during monitoring of the overlapping feedback monitoring occasion, the feedback associated with the sidelink message from each of the one or more second UEs and the second feedback associated with the second sidelink message from each of the one or more third UEs; and terminating the monitoring of each subsequent feedback monitoring occasions of the plurality of feedback monitoring occasions and the second plurality of feedback monitoring occasions based at least in part on receiving, during the monitoring of the overlapping feedback monitoring occasion, the feedback associated with the sidelink message from each of the one or more second UEs and the second feedback associated with the second sidelink message from each of the one or more third UEs.
[0179] Aspect 17: The method of aspect 16, wherein monitoring the one or more feedback monitoring occasions comprises: monitoring a first overlapping feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message and for the second feedback associated with the second sidelink message, wherein the first overlapping feedback monitoring occasion is associated with the plurality of feedback monitoring occasions and the second plurality of feedback monitoring occasions; and monitoring a second overlapping feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of, during the monitoring of the first overlapping feedback monitoring occasion, the feedback associated with the sidelink message from each of the one or more second UEs and the second feedback associated with the second sidelink message from each of the one or more third UEs, wherein the second overlapping feedback monitoring occasion is associated with the plurality of feedback monitoring occasions and the second plurality of feedback monitoring occasions.
[0180] Aspect 18: The method of any of aspects 1 through 17, wherein the one or more feedback monitoring occasions are based at least in part on a rule associated with reception of the feedback associated with the sidelink message via at least one of the one or more feedback monitoring occasions.
[0181] Aspect 19: The method of aspect 18, wherein the rule is based at least in part on the first cast type and whether the feedback associated with the sidelink message comprises one or more positive acknowledgment messages, one or more negative acknowledgment message, or both, or comprises an absence of the one or more positive acknowledgment messages, an absence of the one or more negative acknowledgment message, or both, during at least one of the plurality of feedback monitoring occasions.
[0182] Aspect 20: A first UE for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the first UE to perform a method of any of aspects 1 through 19.
[0183] Aspect 21: A first UE for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 19.
[0184] Aspect 22: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 19.
[0185] It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.
[0186] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
[0187] Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0188] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) . Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.
[0189] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
[0190] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.
[0191] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ”
[0192] As used herein, including in the claims, the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a, ” “at least one, ” “one or more, ” “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs 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 “acomponent” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components, ” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ”
[0193] The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.
[0194] In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label.
[0195] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration, ” and not “preferred” or “advantageous over other examples. ” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.
[0196] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
Claims
1.A first user equipment (UE) , comprising:one or more memories storing processor-executable code; andone or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the first UE to:transmit, 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 feedback associated with the sidelink message, wherein the sidelink message is of a first cast type of a plurality of cast types; andmonitor, after transmitting the sidelink message, one or more feedback monitoring occasions of the plurality of feedback monitoring occasions for the feedback associated with the sidelink message from the one or more second UEs, wherein the one or more feedback monitoring occasions are based at least in part on the first cast type.2.The first UE of claim 1, wherein, to monitor the one or more feedback monitoring occasions, the one or more processors are individually or collectively operable to execute the code to cause the first UE to:monitor each feedback monitoring occasion of the plurality of feedback monitoring occasions, wherein the first cast type is unicast or groupcast.3.The first UE of claim 1, wherein the first cast type is unicast, and wherein the one or more feedback monitoring occasions comprises a first feedback monitoring occasion, and the one or more processors are individually or collectively further operable to execute the code to cause the first UE to:receive the feedback associated with the sidelink message during monitoring of the first feedback monitoring occasion based at least in part on the monitoring; andterminate the monitoring of each subsequent feedback monitoring occasion of the plurality of feedback monitoring occasions based at least in part on receiving the feedback associated with the sidelink message during the monitoring of the first feedback monitoring occasion.4.The first UE of claim 1, wherein the first cast type is unicast, and wherein, to monitor the one or more feedback monitoring occasions, the one or more processors are individually or collectively operable to execute the code to cause the first UE to:monitor a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message; andmonitor a second feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of the feedback associated with the sidelink message during monitoring of the first feedback monitoring occasion.5.The first UE of claim 1, wherein the first cast type is unicast, and wherein the one or more feedback monitoring occasions comprises a first feedback monitoring occasion, and the one or more processors are individually or collectively further operable to execute the code to cause the first UE to:receive a positive acknowledgment message during monitoring of the first feedback monitoring occasion based at least in part on the monitoring, wherein the feedback associated with the sidelink message comprises the positive acknowledgment message; andterminate the monitoring of each subsequent feedback monitoring occasion of the plurality of feedback monitoring occasions based at least in part on receiving the positive acknowledgment message during the monitoring of the first feedback monitoring occasion.6.The first UE of claim 1, wherein the first cast type is unicast, and wherein, to monitor the one or more feedback monitoring occasions, the one or more processors are individually or collectively operable to execute the code to cause the first UE to:monitor a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message; andmonitor a second feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of a positive acknowledgment message during monitoring of the first feedback monitoring occasion, wherein the feedback associated with the sidelink message comprises the positive acknowledgment message.7.The first UE of claim 1, wherein the first cast type is groupcast associated with negative acknowledgment-only based feedback, and wherein the one or more feedback monitoring occasions comprises a first feedback monitoring occasion, and the one or more processors are individually or collectively further operable to execute the code to cause the first UE to:receive a negative acknowledgment message during monitoring of the first feedback monitoring occasion based at least in part on the monitoring, wherein the feedback associated with the sidelink message comprises the negative acknowledgment message; andterminate the monitoring of each subsequent feedback monitoring occasions of the plurality of feedback monitoring occasions based at least in part on receiving the negative acknowledgment message during the monitoring of the first feedback monitoring occasion.8.The first UE of claim 1, wherein the first cast type is groupcast associated with negative acknowledgment-only based feedback, and wherein, to monitor the one or more feedback monitoring occasions, the one or more processors are individually or collectively operable to execute the code to cause the first UE to:monitor a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message; andmonitor a second feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of a negative acknowledgment message during monitoring of the first feedback monitoring occasion, wherein the feedback associated with the sidelink message comprises the negative acknowledgment message.9.The first UE of claim 1, wherein the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and wherein the one or more feedback monitoring occasions comprises a first feedback monitoring occasion, and the one or more processors are individually or collectively further operable to execute the code to cause the first UE to:receive, from at least one of the one or more second UEs, a negative acknowledgment message during monitoring of the first feedback monitoring occasion based at least in part on the monitoring, wherein the feedback associated with the sidelink message comprises the negative acknowledgment message; andterminate the monitoring of each subsequent feedback monitoring occasions of the plurality of feedback monitoring occasions based at least in part on receiving the negative acknowledgment message from the at least one of the one or more second UEs during the monitoring of the first feedback monitoring occasion.10.The first UE of claim 1, wherein the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and wherein, to monitor the one or more feedback monitoring occasions, the one or more processors are individually or collectively operable to execute the code to cause the first UE to:monitor a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message; andmonitor a second feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of a negative acknowledgment message from at least one of the one or more second UEs during monitoring of the first feedback monitoring occasion, wherein the feedback associated with the sidelink message comprises the negative acknowledgment message.11.The first UE of claim 1, wherein the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and wherein the one or more feedback monitoring occasions comprises a first feedback monitoring occasion, and the one or more processors are individually or collectively further operable to execute the code to cause the first UE to:receive, from each of the one or more second UEs, the feedback associated with the sidelink message during monitoring of the first feedback monitoring occasion based at least in part on the monitoring; andterminate the monitoring of each subsequent feedback monitoring occasions of the plurality of feedback monitoring occasions based at least in part on receiving the feedback associated with the sidelink message from each of the one or more second UEs during the monitoring of the first feedback monitoring occasion.12.The first UE of claim 1, wherein the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and wherein, to monitor the one or more feedback monitoring occasions, the one or more processors are individually or collectively operable to execute the code to cause the first UE to:monitor a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message; andmonitor a second feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of the feedback associated with the sidelink message from each of the one or more second UEs during monitoring of the first feedback monitoring occasion.13.The first UE of claim 1, wherein the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and wherein the one or more feedback monitoring occasions comprises a first feedback monitoring occasion, and the one or more processors are individually or collectively further operable to execute the code to cause the first UE to:receive, from each of the one or more second UEs, a positive acknowledgment message during monitoring of the first feedback monitoring occasion based at least in part on the monitoring, wherein the feedback associated with the sidelink message comprises the positive acknowledgment message; andterminate the monitoring of each subsequent feedback monitoring occasions of the plurality of feedback monitoring occasions based at least in part on receiving the positive acknowledgment message from each of the one or more second UEs during the monitoring of the first feedback monitoring occasion.14.The first UE of claim 1, wherein the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and wherein, to monitor the one or more feedback monitoring occasions, the one or more processors are individually or collectively operable to execute the code to cause the first UE to:monitor a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message; andmonitor a second feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of a positive acknowledgment message from each of the one or more second UEs during monitoring of the first feedback monitoring occasion, wherein the feedback associated with the sidelink message comprises the positive acknowledgment message.15.The first UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the first UE to:transmit, via the sidelink shared channel, a second sidelink message to one or more third UEs, the second sidelink message corresponding to a second plurality of feedback monitoring occasions for second feedback associated with the second sidelink message, wherein the second sidelink message is of a second cast type of the plurality of cast types, and wherein the second plurality of feedback monitoring occasions overlap with the plurality of feedback monitoring occasions.16.The first UE of claim 15, wherein the one or more feedback monitoring occasions comprises an overlapping feedback monitoring occasion associated with the plurality of feedback monitoring occasions and the second plurality of feedback monitoring occasions, and the one or more processors are individually or collectively further operable to execute the code to cause the first UE to:receive, during monitoring of the overlapping feedback monitoring occasion, the feedback associated with the sidelink message from each of the one or more second UEs and the second feedback associated with the second sidelink message from each of the one or more third UEs; andterminate the monitoring of each subsequent feedback monitoring occasions of the plurality of feedback monitoring occasions and the second plurality of feedback monitoring occasions based at least in part on receiving, during the monitoring of the overlapping feedback monitoring occasion, the feedback associated with the sidelink message from each of the one or more second UEs and the second feedback associated with the second sidelink message from each of the one or more third UEs.17.The first UE of claim 16, wherein, to monitor the one or more feedback monitoring occasions, the one or more processors are individually or collectively operable to execute the code to cause the first UE to:monitor a first overlapping feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message and for the second feedback associated with the second sidelink message, wherein the first overlapping feedback monitoring occasion is associated with the plurality of feedback monitoring occasions and the second plurality of feedback monitoring occasions; andmonitor a second overlapping feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of, during the monitoring of the first overlapping feedback monitoring occasion, the feedback associated with the sidelink message from each of the one or more second UEs and the second feedback associated with the second sidelink message from each of the one or more third UEs, wherein the second overlapping feedback monitoring occasion is associated with the plurality of feedback monitoring occasions and the second plurality of feedback monitoring occasions.18.The first UE of claim 1, wherein the one or more feedback monitoring occasions are based at least in part on a rule associated with reception of the feedback associated with the sidelink message via at least one of the one or more feedback monitoring occasions.19.The first UE of claim 18, wherein the rule is based at least in part on the first cast type and whether the feedback associated with the sidelink message comprises one or more positive acknowledgment messages, one or more negative acknowledgment message, or both, or comprises an absence of the one or more positive acknowledgment messages, an absence of the one or more negative acknowledgment message, or both, during at least one of the plurality of feedback monitoring occasions.20.A method for wireless communications at a first user equipment (UE) , comprising:transmitting, 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 feedback associated with the sidelink message, wherein the sidelink message is of a first cast type of a plurality of cast types; andmonitoring, after transmitting the sidelink message, one or more feedback monitoring occasions of the plurality of feedback monitoring occasions for the feedback associated with the sidelink message from the one or more second UEs, wherein the one or more feedback monitoring occasions are based at least in part on the first cast type.21.The method of claim 20, wherein monitoring the one or more feedback monitoring occasions comprises:monitoring each feedback monitoring occasion of the plurality of feedback monitoring occasions, wherein the first cast type is unicast or groupcast.22.The method of claim 20, wherein the first cast type is unicast, and wherein the one or more feedback monitoring occasions comprises a first feedback monitoring occasion, the method further comprising:receiving the feedback associated with the sidelink message during monitoring of the first feedback monitoring occasion based at least in part on the monitoring; andterminating the monitoring of each subsequent feedback monitoring occasion of the plurality of feedback monitoring occasions based at least in part on receiving the feedback associated with the sidelink message during the monitoring of the first feedback monitoring occasion.23.The method of claim 20, wherein the first cast type is unicast, and wherein monitoring the one or more feedback monitoring occasions comprises:monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message; andmonitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of the feedback associated with the sidelink message during monitoring of the first feedback monitoring occasion.24.The method of claim 20, wherein the first cast type is unicast, and wherein the one or more feedback monitoring occasions comprises a first feedback monitoring occasion, the method further comprising:receiving a positive acknowledgment message during monitoring of the first feedback monitoring occasion, wherein the feedback associated with the sidelink message comprises the positive acknowledgment message; andterminating the monitoring of each subsequent feedback monitoring occasion of the plurality of feedback monitoring occasions based at least in part on receiving the positive acknowledgment message during the monitoring of the first feedback monitoring occasion.25.The method of claim 20, wherein the first cast type is unicast, and wherein monitoring the one or more feedback monitoring occasions comprises:monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message; andmonitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of a positive acknowledgment message during monitoring of the first feedback monitoring occasion, wherein the feedback associated with the sidelink message comprises the positive acknowledgment message.26.The method of claim 20, wherein the first cast type is groupcast associated with negative acknowledgment-only based feedback, and wherein the one or more feedback monitoring occasions comprises a first feedback monitoring occasion, the method further comprising:receiving a negative acknowledgment message during monitoring of the first feedback monitoring occasion based at least in part on the monitoring, wherein the feedback associated with the sidelink message comprises the negative acknowledgment message; andterminating the monitoring of each subsequent feedback monitoring occasions of the plurality of feedback monitoring occasions based at least in part on receiving the negative acknowledgment message during the monitoring of the first feedback monitoring occasion.27.The method of claim 20, wherein the first cast type is groupcast associated with negative acknowledgment-only based feedback, and wherein monitoring the one or more feedback monitoring occasions comprises:monitoring a first feedback monitoring occasion of the one or more feedback monitoring occasions for the feedback associated with the sidelink message; andmonitoring a second feedback monitoring occasion of the one or more feedback monitoring occasions based at least in part on absence of a negative acknowledgment message during monitoring of the first feedback monitoring occasion, wherein the feedback associated with the sidelink message comprises the negative acknowledgment message.28.The method of claim 20, wherein the first cast type is groupcast associated with positive acknowledgment and negative acknowledgment based feedback, and wherein the one or more feedback monitoring occasions comprises a first feedback monitoring occasion, the method further comprising:receiving, from at least one of the one or more second UEs, a negative acknowledgment message during monitoring of the first feedback monitoring occasion based at least in part on the monitoring, wherein the feedback associated with the sidelink message comprises the negative acknowledgment message; andterminating the monitoring of each subsequent feedback monitoring occasions of the plurality of feedback monitoring occasions based at least in part on receiving the negative acknowledgment message from the at least one of the one or more second UEs during the monitoring of the first feedback monitoring occasion.29.A first user equipment (UE) for wireless communications, comprising:means for transmitting, 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 feedback associated with the sidelink message, wherein the sidelink message is of a first cast type of a plurality of cast types; andmeans for monitoring, after transmitting the sidelink message, one or more feedback monitoring occasions of the plurality of feedback monitoring occasions for the feedback associated with the sidelink message from the one or more second UEs, wherein the one or more feedback monitoring occasions are based at least in part on the first cast type.30.A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to:transmit, 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 feedback associated with the sidelink message, wherein the sidelink message is of a first cast type of a plurality of cast types; andmonitor, after transmitting the sidelink message, one or more feedback monitoring occasions of the plurality of feedback monitoring occasions for the feedback associated with the sidelink message from the one or more second UEs, wherein the one or more feedback monitoring occasions are based at least in part on the first cast type.