Data transmission availability in S-SSB opportunity

Abstract

Methods, systems, and devices for wireless communication are described. A first user equipment (UE) may receive a first message indicating one or more opportunities associated with a sidelink synchronization signal block (S-SSB) transmission between at least the first UE and a second UE. The first UE may send a second message to the network entity, the second message including an indication of a coverage default state associated with whether the one or more opportunities are available for sidelink data transmission. The first UE may communicate one or more reference signals between at least the first UE and the second UE based on sending the second message to the network entity. In some examples, the first UE may drop sidelink data transmissions based on a priority value associated with the sidelink data transmissions being lower than a priority value associated with an overlapping S-SSB.

Description

TECHNICAL FIELD

[0001] The following relates to wireless communications, including data transmission availability in sidelink synchronization signal block (S-SSB) occasions. BACKGROUND

[0002] 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 can 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 can be referred to as New Radio (NR) systems. These systems can 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).

[0003] A wireless multiple-access communications system can include one or more base stations, each simultaneously supporting communication for multiple communication devices, which can be otherwise known as user equipment (UE). In some examples, a UE can engage in sidelink communication with one or more other UEs. SUMMARY

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support data transmission availability in S-SSB occasions. For example, the described techniques allow a first UE to receive a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE. The first UE can transmit, to a network entity, a second message including an indication to override a default state associated with whether the one or more occasions are available for sidelink data transmissions between at least the first UE and the second UE. The first UE can communicate, based on transmitting the second message to the network entity, one or more reference signals between at least the first UE and the second UE. In some examples, the first UE can drop a sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with a S-SSB associated with an upcoming occasion, and the first UE can transmit a negative acknowledgement message based on dropping the sidelink data transmission. In some cases, a priority value of the negative acknowledgement message can be a same value as a priority value of the sidelink data transmission.

[0005] A method for wireless communication at a first UE is described. The method can include receiving a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE, transmitting, to a network entity, a second message including an indication overriding a default state associated with whether the one or more occasions are available for sidelink data transmissions between the first UE and the second UE, and communicating one or more reference signals between at least the first UE and the second UE based on transmitting the second message to the network entity.

[0006] An apparatus for wireless communication at a first UE is described. The apparatus can include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions can be executable by the processor to cause the apparatus to receive a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE, transmit, to a network entity, a second message including an indication overriding a default state associated with whether the one or more occasions are available for sidelink data transmissions between the first UE and the second UE, and communicate one or more reference signals between at least the first UE and the second UE based on transmitting the second message to the network entity.

[0007] Another apparatus for wireless communication at a first UE is described. The apparatus can include means for receiving a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE, means for transmitting, to a network entity, a second message including an indication overriding a default state associated with whether the one or more occasions are available for sidelink data transmissions between the first UE and the second UE, and means for communicating one or more reference signals between at least the first UE and the second UE based on transmitting the second message to the network entity.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a first UE is described. The code can include instructions executable by a processor to receive a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE, transmit, to a network entity, a second message including an indication overriding a default state associated with whether the one or more occasions are available for sidelink data transmissions between the first UE and the second UE, and communicate one or more reference signals between at least the first UE and the second UE based on transmitting the second message to the network entity.

[0009] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the second message indicates that a default state is overridden for a next occasion of the one or more occasions.

[0010] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the second message indicates that a default state is overridden for an occasion within a current S-SSB period.

[0011] Some examples of the method, apparatuses, and non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for transmitting, to the network entity, a fourth message that includes an indication to return to the default state for occasions within a current S-SSB period.

[0012] Some examples of the method, apparatuses, and non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for transmitting, to the network entity, a third message prior to transmitting the first message, the third message indicating one or more Layer 2 ID values associated with the first UE.

[0013] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the default state indicates that the one or more occasions can be available for sidelink data transmissions between the first UE and the second UE.

[0014] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the default state indicates that the one or more occasions can not be available for sidelink data transmissions between the first UE and the second UE.

[0015] Some examples of the method, apparatuses, and non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for transmitting, to the second UE, a sidelink data message during a next occasion of the one or more occasions based on the default state being overridden.

[0016] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, communicating the one or more reference signals can include operations, features, means, or instructions for communicating the one or more reference signals during an occasion subsequent to the next occasion of the one or more occasions.

[0017] Some examples of the method, apparatuses, and non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for transmitting, to the network entity, a fourth message that includes an indication to return to the default state for occasions within a current S-SSB period, where communicating the one or more reference signals can be based on transmitting the fourth message.

[0018] In some examples of the method, apparatus, and non-transitory computer-readable medium described herein, the default state can be based on a success rate associated with a listen-before-talk procedure at the first UE for the S-SSB transmission.

[0019] In some examples of the method, apparatus, and non-transitory computer-readable medium described herein, the indication to override the default state includes one or more bits within a second message, the second message including an uplink control message.

[0020] In some examples of the method, apparatus, and non-transitory computer-readable medium described herein, transmitting the second message can include operations, features, means, or instructions for transmitting the uplink control message during a time window configured by the network entity, where the one or more bits include one or more additional bits included in the second message based on transmitting the uplink control message during the time window.

[0021] In some examples of the method, apparatus, and non-transitory computer-readable medium described herein, the second message includes a dedicated control message associated with transmitting the indication to override the default state.

[0022] Some examples of the method, apparatus, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving, from a second UE, a message including an indication to override the default state, where transmitting the second message to the network entity can be based on receiving the message including the indication to override the default state from the second UE.

[0023] Some examples of the method, apparatus, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for determining that an upcoming occasion of one or more occasions associated with the S-SSB transmission overlaps with an occasion for a sidelink data transmission; dropping the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with the S-SSB transmission associated with the upcoming occasion; and transmitting a negative acknowledgement message based on dropping the sidelink data transmission, where a priority value associated with the negative acknowledgement message can be a same value as the priority value associated with the sidelink data transmission.

[0024] A method for wireless communication at a network entity is described. The method can include transmitting, to a first UE, a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE, receiving a second message including an indication to override a default status associated with whether the one or more occasions are available for sidelink data transmissions between the first UE and the second UE, and scheduling one or more sidelink data transmissions between at least the first UE and the second UE for one or more resources selected based on the default status being overridden.

[0025] An apparatus for wireless communication at a network entity is described. The apparatus can include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions can be executable by the processor to cause the apparatus to transmit, to a first UE, a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE, receive a second message including an indication to override a default status associated with whether the one or more occasions are available for sidelink data transmissions between the first UE and the second UE, and schedule one or more sidelink data transmissions between at least the first UE and the second UE for one or more resources selected based on the default status being overridden.

[0026] Another apparatus for wireless communication at a network entity is described. The apparatus can include means for transmitting, to a first UE, a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE, means for receiving a second message including an indication to override a default status associated with whether the one or more occasions are available for sidelink data transmissions between the first UE and the second UE, and means for scheduling one or more sidelink data transmissions between at least the first UE and the second UE for one or more resources selected based on the default status being overridden.

[0027] A non-transitory computer-readable medium storing code for wireless communications at a network entity is described. The code can include instructions executable by a processor to transmit, to a first UE, a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE, receive a second message including an indication to override a default status associated with whether the one or more occasions are available for sidelink data transmissions between the first UE and the second UE, and schedule one or more sidelink data transmissions between at least the first UE and the second UE for one or more resources selected based on the default status being overridden.

[0028] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving, from the second UE, a third message indicating one or more layer 2 ID values associated with the second UE, where receiving the second message can be based on receiving the third message from the second UE.

[0029] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving, from the first UE, a sidelink buffer status report indicating one or more destination ID values, and determining that a destination ID value of the one or more destination ID values can be associated with the second UE, where scheduling the one or more sidelink data transmissions can be based on the determination.

[0030] In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the second message indicates that the default status is overridden for a next occasion of the one or more occasions.

[0031] In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the second message indicates that the default status is overridden for an occasion within a current S-SSB period.

[0032] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving a fourth message including an indication to return to the default status for an occasion within a current S-SSB period.

[0033] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the default status indicates that the one or more occasions are not available for sidelink data transmissions between the first UE and the second UE, and scheduling the one or more sidelink data transmissions can include operations, features, means, or instructions for scheduling, based on the default status being overridden, a sidelink data transmission between the first UE and the second UE during an occasion of the one or more occasions based on receiving the second message.

[0034] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the default status indicates that the one or more occasions are not available for sidelink data transmissions between the first UE and the second UE, and scheduling the one or more sidelink data transmissions can include operations, features, means, or instructions for scheduling, based on the default status being overridden, a sidelink data transmission between the first UE and the second UE during an occasion of the one or more occasions based on receiving the second message.

[0035] In some examples of the method, apparatuses, and non-transitory computer- readable medium described herein, the indication to override the default status includes one or more bits within the second message, the second message including an uplink control message.

[0036] A method for wireless communication at a first UE is described. The method can include receiving a message indicating one or more occasions associated with S-SSB transmissions between the first UE and a second UE, where an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with an occasion for a sidelink data transmission, dropping the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion, and transmitting a negative acknowledgement message based on dropping the sidelink data transmission, where a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission.

[0037] An apparatus for wireless communication at a first UE is described. The apparatus can include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions can be executable by the processor to cause the apparatus to receive a message indicating one or more occasions associated with S-SSB transmissions between the first UE and a second UE, where an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with a time occasion for a sidelink data transmission, drop the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion, and transmit a negative acknowledgement message based on dropping the sidelink data transmission, where a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission.

[0038] Another apparatus for wireless communication at a first UE is described. The apparatus can include means for receiving a message indicating one or more occasions associated with S-SSB transmissions between the first UE and a second UE, where an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with a time occasion for a sidelink data transmission, means for dropping the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion, and means for transmitting a negative acknowledgement message based on dropping the sidelink data transmission, where a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission.

[0039] A non-transitory computer-readable medium storing code for wireless communication at a first UE is described. The code can include instructions executable by a processor to receive a message indicating one or more occasions associated with S-SSB transmissions between the first UE and a second UE, where an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with a time occasion for a sidelink data transmission, drop the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion, and transmit a negative acknowledgement message based on dropping the sidelink data transmission, where a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission.

[0040] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for transmitting one or more reference signals to the second UE based on dropping the sidelink data transmission.

[0041] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for transmitting, to a network entity, a message including an indication of a default state of coverage, the default state being associated with whether one or more occasions are available for sidelink data transmissions between the first UE and the second UE.

[0042] A method for wireless communication at a network entity is described. The method can include transmitting a message indicating one or more occasions associated with S-SSB transmissions between a first UE and a second UE, where an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with an occasion for sidelink data transmissions, and receiving, from the first UE, a negative acknowledgement message indicating that the first UE dropped the sidelink data transmissions based on a priority value associated with the sidelink data transmissions being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion, where a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmissions.

[0043] An apparatus for wireless communication at a network entity is described. The apparatus can include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions can be executable by the processor to cause the apparatus to transmit a message indicating one or more occasions associated with S-SSB transmissions between a first UE and a second UE, where an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with an occasion for sidelink data transmissions, and receive, from the first UE, a negative acknowledgement message indicating that the first UE dropped the sidelink data transmissions based on a priority value associated with the sidelink data transmissions being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion, where a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmissions.

[0044] Another apparatus for wireless communication at a network entity is described. The apparatus can include means for transmitting a message indicating one or more occasions associated with S-SSB transmissions between a first UE and a second UE, where an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with an occasion for sidelink data transmissions, and means for receiving, from the first UE, a negative acknowledgement message indicating that the first UE dropped the sidelink data transmissions based on a priority value associated with the sidelink data transmissions being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion, where a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmissions.

[0045] A non-transitory computer-readable medium storing code for wireless communications at a network entity is described. The code can include instructions executable by a processor to transmit a message indicating one or more occasions associated with S-SSB transmissions between a first UE and a second UE, where an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with an occasion for a sidelink data transmission, and receive a negative acknowledgement message from the first UE indicating that the first UE dropped the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion, where a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission.

[0046] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving, from the first UE, a message including an indication of a default state associated with whether one or more occasions are available for sidelink data transmissions between the first UE and the second UE. BRIEF DESCRIPTION OF DRAWINGS

[0047] Figure 1 An example of a wireless communications system that supports data transmission availability in S-SSB occasions is shown, in accordance with one or more aspects of the present disclosure.

[0048] Figure 2 An example of a wireless communications system that supports data transmission availability in S-SSB occasions is shown, in accordance with one or more aspects of the present disclosure.

[0049] Figure 3A And Figure 3B An example of a signaling diagram that supports data transmission availability in S-SSB occasions is shown, in accordance with one or more aspects of the present disclosure.

[0050] Figure 4 An example of a signaling diagram that supports data transmission availability in S-SSB occasions is shown, in accordance with one or more aspects of the present disclosure.

[0051] Figure 5 An example of a wireless communications system that supports data transmission availability in S-SSB occasions is shown, in accordance with one or more aspects of the present disclosure.

[0052] Figure 6 An example of a process flow that supports data transmission availability in S-SSB occasions is shown, in accordance with one or more aspects of the present disclosure.

[0053] Figure 7An example of a process flow that supports data transmission availability in S-SSB occasions is shown.

[0054] Figure 8 And Figure 9 A block diagram of a device that supports data transmission availability in S-SSB occasions is shown, in accordance with one or more aspects of the present disclosure.

[0055] Figure 10 A block diagram of a communications manager that supports data transmission availability in S-SSB occasions is shown.

[0056] Figure 11 A diagram of a system including a device that supports data transmission availability in S-SSB occasions is shown.

[0057] Figure 12 And Figure 13 A block diagram of a device that supports data transmission availability in S-SSB occasions is shown, in accordance with one or more aspects of the present disclosure.

[0058] Figure 14 A block diagram of a communications manager that supports data transmission availability in S-SSB occasions is shown.

[0059] Figure 15 A diagram of a system including a device that supports data transmission availability in S-SSB occasions is shown.

[0060] Figures 16 to 20 A flow diagram illustrating a method that supports data transmission availability in S-SSB occasions is shown, in accordance with one or more aspects of the present disclosure. DETAILED DESCRIPTION

[0061] The first UE can perform sidelink communications with the second UE. In some examples, to align on beams for performing the sidelink communications, the first UE and the second UE can communicate one or more reference signals. In some cases, S-SSB transmissions can be configured by a network entity, which can include configuring occasions for the first UE to transmit (e.g., broadcast) one or more reference signals (e.g., S-SSB reference signals) to the second UE and, in some cases, as part of a broadcast, to other UEs. For example, the network entity can configure (e.g., via a radio resource control (RRC) message) one or more occasions (e.g., including time resources, frequency resources, or both) associated with S-SSB transmissions (e.g., unicast or multicast S-SSB transmissions) between at least the first UE and the second UE. The S-SSB occasions can refer to resources or sets of resources (e.g., time and frequency resources) via which S-SSB transmissions can potentially occur.

[0062] However, in some cases, one or more occasions associated with S-SSB transmissions configured to the first UE can introduce some inefficiency or scheduling uncertainty at the network entity and the first UE. For example, there can be uncertainty as to whether the one or more occasions associated with the S-SSB transmissions are to be added to a pool of resources for sidelink transmissions by the first UE. If the one or more occasions are not added to the pool of resources, the first UE will not utilize resources of the one or more occasions for sidelink data transmissions, which can result in less efficient use of the communication spectrum by the first UE. At the same time, if the one or more occasions are added to the pool of resources, there can be an overlap between the S-SSB transmissions and sidelink data transmissions scheduled by the network entity during the one or more occasions. Thus, techniques to resolve these overlaps can be desirable, which can enable the network entity to schedule sidelink messages (e.g., unicast or multicast sidelink messages) between at least the first UE and the second UE during the one or more occasions without overlapping with the S-SSB transmissions.

[0063] According to examples as described herein, the first UE 115 can transmit a message including an indication of an override of a default state associated with whether one or more occasions associated with S-SSB transmissions are available for sidelink data transmissions. For example, the default state can be defined (e.g., based on a success rate of a listen-before-talk (LBT) procedure at the first UE) that indicates whether one or more occasions associated with S-SSBs are available for sidelink data transmissions. For example, the default state can correspond to one or more occasions not being available for sidelink transmissions, and if the first UE is to transmit a sidelink data transmission on an upcoming occasion, the first UE can transmit a message including an indication of an override of the default state. Alternatively, the default state can correspond to sidelink data transmissions being allowed during one or more occasions, and if the first UE is to transmit a reference signal associated with an S-SSB on an upcoming occasion, the first UE can transmit a message including an indication of an override of the default state. In some cases, the default state can be overridden for only the next occasion or for all occasions within an S-SSB period until a message including a second indication is transmitted to revert to the default state.

[0064] Additionally or alternatively, the first UE can drop the sidelink data transmission if a priority value associated with the sidelink data transmission is lower than a priority value associated with the overlapping S-SSB transmission. In these examples, the first UE can transmit a negative acknowledgement (e.g., NACK) to the network entity, the negative acknowledgement having a priority value equal to the priority value of the dropped sidelink data transmission. Accordingly, the network entity can be aware of the dropped sidelink data transmission and perform scheduling (e.g., retransmission scheduling) accordingly.

[0065] Aspects of the disclosure are first described in the context of a wireless communications system. Additionally, aspects of the disclosure are illustrated in the context of signaling diagrams and process flows. Further aspects of the disclosure are illustrated and described in further detail by reference to apparatus diagrams, system diagrams, and flowcharts related to data transmission availability in S-SSB occasions.

[0066] Figure 1 An example of a wireless communications system 100 that supports data transmission availability in S-SSB occasions is shown in accordance with one or more aspects of the present disclosure. The wireless communications system 100 can 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 can be a Long Term Evolution (LTE) network, a LTE-Advanced (LTE-A) network, a LTE-A Pro network, a New Radio (NR) network, or a network operating according to some other wireless communication standard or radio technology including future-generation systems and radio technologies not expressly mentioned herein.

[0067] Network entities 105 can be dispersed throughout the geographic region of wireless communication system 100, and can be representative of a larger or smaller number of network entities 105. Network entities 105 can be configured to provide wireless access to the core network 130 for any number of UEs 115 within areas 110, which can be referred to as cells, or by other techniques. In some examples, each network entity 105 can be configured to provide wireless access to core network 130 for UEs 115 in relatively small geographic areas. In some examples, network entities 105 can be referred to as transmission and reception points (TRPs), access points (APs), base stations, radio base stations, network access nodes, or other network entities based on configuration and / or functionality. In some examples, network entities 105 can be a part of a larger group of network entities 105 that are configured to provide wireless access to core network 130. In some examples, network entities 105 can be configured to provide access to core network 130 using different technologies, such as global system for mobile communications (GSM), code division multiple access (CDMA), wideband CDMA (WCDMA), LTE, Bluetooth®, 5G, or other technologies. In some examples, network entities 105 can be configured to use different radio frequency spectrum for communication, such as licensed spectrum, unlicensed spectrum, or shared spectrum.

[0068] UEs 115 can be dispersed throughout the coverage areas 110 of wireless communication system 100, and each UE 115 can be stationary or mobile or both at different times. UEs 115 can be devices such as mobile phones, tablets, personal computers, wireless modems, base stations, or other types of devices that include a wireless transceiver. Figure 1 Some example UEs 115 are illustrated in FIG. 1. UEs 115 described herein can be able to support communication with various types of network entities, such as other UEs 115 or network entities 105, as shown in FIG. 1. Figure 1 As shown, UEs 115 can include one or more transceivers 120, one or more processors 140, memory 150, and / or one or more communication interfaces 160. In some examples, one or more of the components of UE 115 can be configured to communicate using one or more different RATs. For example, a transceiver 120 can be configured to communicate using a first RAT while a transceiver 120 is configured to communicate using a second RAT.

[0069] As described herein, a node of the wireless communications system 100 (which can be referred to as a network node or a wireless node) can be a network entity 105 (e.g., any of the network entities described herein), a UE 115 (e.g., any of the UEs described herein), a network controller, a device, an apparatus, 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 can be a UE 115. As another example, a node can be a network entity 105. As yet another example, a first node can be configured to communicate with a second node or a third node. In one aspect of this example, the first node can be a UE 115, the second node can be a network entity 105, and the third node can be a UE 115. In another aspect of this example, the first node can be a UE 115, the second node can be a network entity 105, and the third node can be a network entity 105. In other aspects of this example, the first node, the second node, and the third node can be different relative to these examples. Similarly, references to a UE 115, a network entity 105, a device, an apparatus, a computing system, etc. can include the disclosure of the UE 115, the network entity 105, the device, the apparatus, the computing system, etc. as a node. For example, a 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.

[0070] In some examples, the network entities 105 can be in communication with the core network 130 or with each other or both. For example, the network entities 105 can communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to an SI, N2, N3, or other interface protocol). In some examples, the network entities 105 can communicate with each other via backhaul communication links 120 (e.g., according to an X2, Xn, or other interface protocol) either directly (e.g., direct point-to-point between network entities 105) or indirectly (e.g., via core network 130). In some examples, the network entities 105 can communicate with each other via mid-cell communication links 162 (e.g., according to a mid-cell interface protocol) or front-haul communication links 168 (e.g., according to a front-haul interface protocol), or any combination thereof. The backhaul communication links 120, mid-cell communication links 162, or front-haul communication links 168 can be or include one or more wired links (e.g., electrical, fiber optic), one or more wireless links (e.g., radio, wireless optical), etc., or various combinations thereof. A UE 115 can communicate with the core network 130 via communication links 155.

[0071] One or more of the network entities 105 described herein can include or can be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an evolved NodeB (eNB), a Next Generation NodeB or a Gigabit NodeB (any of which can 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, the network entity 105 (e.g., base station 140) can be implemented in an aggregated (e.g., monolithic, self-standing) base station architecture that can be configured to utilize protocol stacks that are physically or logically integrated within a single network entity 105 (e.g., a single RAN node such as a base station 140).

[0072] In some examples, the network entity 105 can be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that can be configured to utilize protocol stacks that are physically or logically distributed between 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, the network entity 105 can 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. The RU 170 can also be referred to as a radio head, an intelligent 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 entity 105 in the disaggregated RAN architecture can be co-located, or one or more components of the network entity 105 can be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the disaggregated RAN architecture can be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0073] The functional split between the CU 160, the DU 165, and the RU 170 is flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at the CU 160, the DU 165, or the RU 170. For example, a functional split of a protocol stack can be employed between the CU 160 and the DU 165, such that the CU 160 can support one or more layers of the protocol stack, and the DU 165 can support one or more different layers of the protocol stack. In some examples, the CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., RRC, service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 can be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 can host lower protocol layers, such as layer 1 (LI) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, and can each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of a protocol stack can be employed between the DU 165 and the RU 170, such that the DU 165 can support one or more layers of the protocol stack, and the RU 170 can support one or more different layers of the protocol stack. The DU 165 can support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 can be within a protocol layer (e.g., some functions of a protocol layer can be performed by one of the CU 160, the DU 165, or the RU 170, while other functions of that protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170). The CU 160 can be further split in function into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU 160 can be connected to one or more DUs 165 via a backhaul communication link 162 (e.g., Fl, Fl-c, Fl-u), and the DU 165 can be connected to one or more RUs 170 via a front-haul communication link 168 (e.g., open front-haul (FH) interface). In some examples, the backhaul communication link 162 or the front-haul communication link 168 can be implemented in accordance with an interface (e.g., channel) between layers of a protocol stack supported by the respective network entities 105 that communicate via these communication links.

[0074] In some wireless communications systems (e.g., wireless communications system 100), infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections to provide an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) can be partially controlled by one another. One or more IAB nodes 104 can be referred to as a donor entity or IAB donor. One or more DUs 165 or one or more RUs 170 can be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) can communicate 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). An IAB node 104 can include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled DU 165 of an IAB donor. An IAB-MT can include a separate set of antennas for relaying communications with UEs 115 or can share the same antennas (e.g., of a RU 170) of the IAB node 104 for accessing via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, an IAB node 104 can include a DU 165 that supports a communication link with an additional entity (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of an access network. In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of an IAB node 104) can be configured to operate according to the techniques described herein.

[0075] In cases where the techniques described herein apply in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture can be configured to support data transmission availability in S-SSB occasions as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., base station 140) can additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0076] A UE 115 can include or can 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” can also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 can also include or can 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 can include or can 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 can be implemented in various objects such as appliances or vehicles, among other examples.

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

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

[0079] Signal waveforms transmitted over a carrier can be composed 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 can refer to a resource comprising a symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing can be inversely related. A number of bits carried by each resource element can 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 large number of resource elements (e.g., in a transmission duration) and a relatively high order of modulation scheme can correspond to a relatively high data rate. A wireless communications resource can refer to a combination of a RF spectrum resource, a time resource, and a spatial resource (e.g., spatial layers or beams), and the use of multiple spatial resources can increase the data rate or data

[0080] Time intervals for the network entity 105 or the UE 115 can be expressed in multiples of a basic time unit, which may, for example, refer to a sampling period of 1 second, where may represent supported subcarrier spacings, and may represent supported discrete fourier transform (DFT) sizes. Time intervals of a communications resource can be organized as radio frames, each

[0081] Each frame can comprise a plurality of consecutive numbered subframes or slots, and each subframe or slot can have the same duration. In some examples, a frame can be divided (e.g., in the time domain) into subframes, and each subframe can be further divided into a number of slots. Alternatively, each frame can include a variable number of slots, and the number of slots can depend on the subcarrier spacing. Each slot can include a number 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 can be further divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period can be associated with one or more (e.g., sampling periods. The duration of a symbol period can depend on the subcarrier spacing or the frequency band.

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

[0083] Physical channels can be multiplexed according to various techniques to communicate using a carrier. For example, physical control channels and physical data channels can be multiplexed using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques, among other techniques. A control region (e.g., a control resource set (CORESET)) of a physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth or a subset of the system bandwidth of a carrier. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more of the UEs 115 can monitor or search control regions for control information according to one or more search space sets, and each search space set can include one or more control channel candidates arranged in one or more aggregation levels in a cascaded manner. An aggregation level for a control channel candidate can refer to a quantity of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. A search space set can include common search space sets configured for transmission of control information to a plurality of UEs 115 and UE-specific search space sets configured for transmission of control information to a specific UE 115.

[0084] In some examples, network entities 105 (e.g., base stations 140, RUs 170) can be mobile and thus provide communication coverage for a moving coverage area 110. In some examples, different coverage areas 110 associated with different technologies can overlap, but different coverage areas 110 can be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies can be supported by different network entities 105. Wireless communications system 100 can include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0085] The wireless communications system 100 can be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 can be configured to support ultra-reliable low-latency communications (URLLC). UEs 115 can be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communications can include private communication or group communication, and can be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions can include prioritization of services, and such services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency can be used interchangeably herein.

[0086] In some examples, UEs 115 can be configured to communicate directly with other UEs 115 via device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P) or D2D or sidelink protocol). In some examples, one or more UEs 115 in a group that is performing D2D communication can be within the coverage area 110 of a network entity 105 (e.g., base station 140, RU 170) that supports aspects of such D2D communication configured by the network entity 105 (e.g., scheduled). In some examples, one or more UEs 115 in such a group can be outside the coverage area 110 of a network entity 105 or can otherwise be unable to receive signals from or transmit signals to the network entity 105. In some examples, the group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, where each UE 115 transmits to every other UE 115 in the group. In some examples, a network entity 105 can facilitate scheduling of resources for D2D communication. In some other examples, D2D communication can be carried out between UEs 115 without involvement of a network entity 105.

[0087] In some systems, D2D communication link 135 can be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115). In some examples, vehicles can communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle can signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information related to V2X systems. In some examples, vehicles in a V2X system can 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 both.

[0088] The core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 can be an evolved packet core (EPC) or 5G core (5GC), which can 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 can manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UEs 115 served by network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets can be transferred through the user plane entity, which can provide IP address allocation as well as other functions. The user plane entity can be connected to the IP services 150 of the one or more network operators. The IP services 150 can include access to the Internet, Intranet, an IP multimedia subsystem (IMS), or a packet-switched streaming service.

[0089] The wireless communications system 100 can operate using one or more frequency bands, 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, since the wavelengths range from approximately one decimeter to one meter in length. UHF waves can be blocked or redirected by buildings and environmental features, but the waves can penetrate structures sufficiently for a macro cell to provide service to UEs 115 located indoors. The use of UHF frequencies, however, may

[0090] The wireless communications system 100 can utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 can employ LTE License Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed frequency spectrum band such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in unlicensed frequency spectrum bands, access points 105 and UEs 115 such as network entities 105 and UE 115 can employ carrier sensing for collision detection and avoidance. In some examples, operations in unlicensed frequency spectrum bands can be based on a carrier aggregation configuration in combination with operations in a licensed frequency spectrum band (e.g., LAA). Operations in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

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

[0092] Beamforming, which can also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer the beam over the space. Beamforming can be achieved by combining the signals that are transmitted or received by antennas of an array of antennas. The signals transmitted or received by each antenna of the array of antennas can include a respective amplitude, phase, and / or polarization. By adjusting the amplitudes, phases, and / or polarizations of the signals transmitted or received by each of the antennas of the array of antennas, the shape and direction of the beam can be steered or shaped.

[0093] The network entity 105 or UE 115 can use beam sweeping techniques as part of a beamforming operation. For example, a network entity 105 (e.g., a base station 140, a RU 170) can use multiple antennas or antenna arrays (e.g., antenna panels) for beamforming operations for directional communications with a UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) can be transmitted by a network entity 105 or a UE 115 multiple times in different directions. For example, a network entity 105 or UE 115 can transmit the same or different signals along different beam directions according to different beamforming weight sets associated with different directions. Transmissions in different beam directions can be used, for example, to identify (e.g., by a transmitting device such as a network entity 105 or a Tx UE 115 or by a receiving device such as a UE 115 or a Rx UE 115) a beam direction for subsequent transmission or reception by a network entity 105 or UE 115.

[0094] Some signals, such as data signals associated with a particular receiving device, can be transmitted along a single beam direction (e.g., a direction associated with the receiving device, such as a receiving network entity 105 or a receiving UE 115) by a transmitting device (e.g., a transmitting network entity 105 or a transmitting UE 115). In some examples, the beam direction associated with transmissions along a single beam direction can be determined based on a signal that was transmitted in one or more beam directions (e.g., a beam selection signal). For example, a UE 115 can receive one or more of the signals transmitted by the network entity 105 in different directions, and can report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality, or other acceptable signal quality.

[0095] In some examples, transmissions by a device (e.g., by a network entity 105 or a UE 115) can be performed using multiple beam directions, and the device can use a combination of digital precoding or beamforming to generate a combined beam for transmissions (e.g., from a network entity 105 to a UE 115). The UE 115 can report feedback that indicates precoding weights for one or more beam directions, and the feedback can correspond to a set of beams that are configured across a system bandwidth or one or more sub-bands. The network entity 105 can transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)) that can or can not be precoded. The UE 115 can provide feedback for beam selection, which can be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted by a network entity 105 (e.g., a base station 140, a RU 170) in one or more directions, a UE 115 can use similar techniques for transmitting signals multiple times in different directions (e.g., for identifying a beam direction for subsequent transmission or reception by a UE 115), or for transmitting a signal in a single direction (e.g., for transmitting data to a receiving device).

[0096] A receiving device (e.g., a UE 115) can perform reception operations according to multiple receive configurations (e.g., directional listening) when receiving various signals from a receiving device (e.g., network entity 105), such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device can perform reception according to multiple receive directions by using different antenna subarrays for reception, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which can be referred to as“listening” according to different receive configurations or receive directions. In some examples, a receiving device can use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration can be aligned in a beam direction determined based on listening in different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening in multiple beam directions).

[0097] The UEs 115 and network entities 105 can support retransmission of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique used to increase the likelihood that data is received correctly over a communication link (e.g., communication link 125, D2D communication link 135). HARQ can 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 can improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions). In some examples, a device can support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In some other examples, the device can provide HARQ feedback in a subsequent slot or according to some other time interval.

[0098] In some examples, a first UE 115 (e.g., a transmitting or Tx UE) can perform sidelink communications with a second UE 115 (e.g., a receiving or Rx UE). The network entity 105 can indicate or configure a grant to the first UE 115 for performing a sidelink data transmission (e.g., a physical sidelink shared channel (PSSCH) transmission). For example, the network entity 105 can configure a grant (e.g., a configured grant, such as a Type 1 configured grant or a Type 2 configured grant) to the UE 115, and the network entity can activate the grant by transmitting a downlink control information (DCI) message (e.g., a DCI 3-0 message for a Type 2 configured grant) or an RRC message (e.g., for a Type 1 configured grant) to the first UE 115. Additionally or alternatively, the network entity 105 can transmit a DCI message (e.g., a DCI 3-0 message) indicating a grant (e.g., a dynamic grant) to the first UE 115, and the DCI message can provide an allocation (e.g., an occasion, time resources, frequency resources) for the first UE 115 to perform a sidelink data transmission. In some cases, the DCI message (e.g., in the case of a dynamic grant) can indicate whether the allocation is for a retransmission of a previous sidelink data transmission (e.g., a dropped transmission in some cases). In some examples, the first UE 115 can select a modulation and coding scheme (MCS) for a sidelink transmission, but the UE 115 can be configured with a restriction for the MCS by the network entity 105.

[0099] In some cases, the first UE 115 can not be able to transmit the sidelink data transmission. For example, due to prioritization, the first UE 115 can drop the sidelink data transmission if the overlapping transmission has a higher priority value. In some examples, if the first UE 115 does not transmit the sidelink data transmission in any of the resources provided by the DCI message (e.g., for a dynamic grant) or in any of the resources provided in a period that provides uplink control resources (e.g., for a physical uplink control channel (PUCCH) transmission) to the first UE 115 for reporting HARQ information, the first UE 115 can generate and transmit a NACK to the network entity 105 (e.g., in the uplink control resources). In some examples, the NACK can have the same priority value as the priority value of the dropped sidelink data transmission.

[0100] In some cases, the first UE 115 can also not be able to transmit the sidelink control transmission (e.g., a physical sidelink control channel (PSCCH) transmission). In some examples, if the UE 115 does not transmit the sidelink control transmission (e.g., a PSCCH with sidelink control information (SCI) with format 1-A) in any of the resources provided for a grant that provides uplink control resources to the first UE 115 for reporting HARQ-ACK information (e.g., a period for a configured grant, or indicated in a DCI message for a dynamic grant), the first UE 115 can generate and transmit an ACK to the network entity (e.g., in the uplink control resources). In some examples, the ACK can have the same priority value as the maximum priority value among the possible priority values of the grant.

[0101] In some examples, the first UE 115 can transmit a sidelink buffer status report (SL-BSR) to the network entity 105 (e.g., via a MAC control element (MAC-CE) message). The SL-BSR can include information about sidelink data to be transmitted out by the first UE 115, which can allow the network entity 105 to schedule sidelink data transmissions. In some examples, the SL-BSR can include one or more control elements, each of which can include a destination index field, a logical channel group (LCG) identification (ID) value (e.g., or identity value), a buffer size value, or any combination thereof, and each of which can correspond to a target group of the report. The destination index can be associated with a destination (e.g., a second UE 115) of the sidelink data and can be set to a corresponding index of a sidelink destination ID of the same destination (e.g., the second UE 115) reported to the network entity 105 in a sidelink information element (e.g., SL-TxResourceReqList, SL-TxResourceReqListDisc, SL-TxResourceReqListCommRelay). In some cases, the destination index of multiple destinations can be indexed in ascending order starting from 0 based on the occurrence of the sidelink destination ID in the information element or as presented in a control message (e.g., a sidelinkUEInformationNR message).

[0102] In some examples, the network entity 105 can configure, to the first UE 115, an occasion associated with S-SSB transmissions for the first UE 115 to transmit one or more reference signals to the second UE 115. For example, the network entity can configure (e.g., via an RRC message) one or more occasions (e.g., including time resources, frequency resources, or both) associated with S-SSB transmissions (e.g., broadcasts) between at least the first UE 115 and the second UE 115. In some examples, the one or more occasions can be in addition to other S-SSB occasions previously configured or indicated to the first UE 115. However, in some cases, the one or more additional occasions can introduce some inefficiency or scheduling uncertainty at the network entity 105 and the first UE 115. For example, if the one or more occasions are not added to a resource pool of the first UE 115 associated with sidelink data transmissions, the first UE 115 can not use resources with the one or more occasions for sidelink data transmissions, which can result in less efficient use of the communication spectrum by the first UE 115. However, if the one or more occasions are added to the resource pool, there can be an overlap (e.g., in time, in frequency, or both) between the S-SSB transmissions and sidelink data transmissions (e.g., PSSCH messages) that can be scheduled by the network entity 105 during the one or more occasions. Thus, techniques for performing scheduling while resolving or avoiding these overlaps can be desirable.

[0103] According to examples as described herein, the first UE 115 can transmit a message including an indication to override a default state associated with whether one or more occasions associated with S-SSB transmissions are available for sidelink data transmissions. For example, a default state can be defined (e.g., based on a success rate of LBT procedures at the first UE 115) that indicates whether the one or more occasions associated with S-SSB are available for sidelink data transmissions. For example, the default state can correspond to the one or more occasions not being used for sidelink transmissions, and if the first UE 115 is to transmit a sidelink data transmission on an upcoming occasion, the first UE 115 can transmit a message including an indication to override the default state. Alternatively, the default state can correspond to sidelink data transmissions being allowed during the one or more occasions, and if the first UE 115 is to transmit a S-SSB 220 on an upcoming occasion, the first UE 115 can transmit a message including an indication to override the default state. In some cases, the default state can be overridden for only the next occasion or for all occasions within a S-SSB period until a message including a second indication is transmitted to revert to the default state.

[0104] Additionally or alternatively, the first UE 115 can be configured to drop the sidelink data transmission if a priority value associated with the sidelink data transmission is lower than a priority value associated with the overlapping S-SSB transmission. In these examples, the first UE 115 can transmit a NACK to the network entity 105, the priority value of the NACK being equal to the priority value of the dropped sidelink data transmission. Thus, the network entity can be aware of the dropped sidelink data transmission and perform scheduling accordingly.

[0105] Figure 2 An example of a wireless communications system 200 that supports data transmission availability in S-SSB occasions is shown in accordance with one or more aspects of the present disclosure. The wireless communications system 200 can be an example of the wireless communications system 100, or incorporate aspects of the wireless communications system 100. For example, the wireless communications system 200 illustrates communications between a UE 115-a, a UE 115-b, and a network entity 105-a, which can be examples of the corresponding components described herein. Figure 1 Similarly, the UE 115-a, the UE 115-b, and the network entity 105-a can perform communications via a communication link 205-a and a communication link 205-b, which can be examples of the communication links 125 as described herein. Figure 1

[0106] ​In some examples, the network entity 105-a can transmit one or more messages 210 (e.g., RRC messages) to configure the UE 115-a with a set of (e.g., one or more) S-SSB occasions associated with the transmission of S-SSBs 220 by the UE 115-a to the UE 115-b. In some examples, the S-SSB occasions can be in addition to other S-SSB occasions previously (e.g., preconfigured or indicated by the network entity 105-a) to the UE 115-a. However, in some cases, the S-SSB occasions can introduce some inefficiency or scheduling uncertainty at the network entity 105-a and the UE 115-a. For example, if the S-SSB occasions are not included (e.g., added by the network entity 105-a) in a resource pool for sidelink data transmissions by the UE 115-a, the UE 115-a can experience a relatively inefficient use of the communication spectrum because the resources associated with the S-SSB occasions will not be used for sidelink data transmissions by the UE 115-a. However, if the S-SSB occasions are included in the resource pool for sidelink data transmissions by the UE 115-a, the network entity 105-a can schedule sidelink data messages 225 (e.g., PSSCH messages) during these occasions, which can result in an overlap between the transmission of S-SSBs 220 (e.g., the transmission or broadcast of one or more reference signals) and the sidelink data messages 225. Thus, techniques for resolving or avoiding these overlaps can be desirable.

[0107] According to examples as described herein, the UE 115-a can transmit a message including an indication 215-a associated with an override of a default state to the network entity 105. The indication 215-a can inform the network entity 105 of an override of a default state associated with whether S-SSB occasions are available for sidelink data transmissions by the UE 115-a scheduled by the network entity 105-a. For example, the default state can correspond to S-SSB occasions being available for sidelink data transmissions. Thus, if the UE 115-a has data (e.g., in a buffer) available for a sidelink data message 225, the UE 115-a can transmit the sidelink data message during one of the S-SSB occasions. Meanwhile, if the UE 115-a is to transmit an S-SSB 220, the UE 115-a can transmit the message including the indication 215 to prevent the network entity 105-a from scheduling an overlapping sidelink data message 225 during one or more upcoming ones of the S-SSB occasions. In some other examples, the default state can correspond to S-SSB occasions being unavailable for sidelink data transmissions. Thus, if the UE 115-a has data (e.g., in a buffer) available for a sidelink data message 225, the UE 115-a can transmit the message including the indication 215.

[0108] In some examples, the default state can be configured (e.g., or preconfigured) to the UE 115-a, the network entity 105-a, or both. In some cases, the default state can be defined and configured to all UEs 115 that communicate with the network entity 105-a. Additionally or alternatively, the default state can be defined on a per-UE basis, and in some examples, the default state can be defined by the UE 115-a. For example, the UE 115-a can determine the default state and indicate the default state to the network entity 105-a in a message (e.g., an RRC message). Further, in some cases, the default state can not be explicitly defined at the UE 115-a or the network entity 105-a, and the UE 115-a can simply indicate an interpretation of the indication 215 (e.g., and future indications 215) sent to the network entity 105-a. For example, the UE 115-a can indicate (e.g., in an RRC message) whether the indication 215 corresponds to S-SSB occasions being enabled for sidelink data transmissions or S-SSB occasions being disabled for sidelink data transmissions without explicitly defining the default state.

[0109] In some examples, the default state can be based on one or more conditions at the UE 115-a, such as a success rate of LBT procedures at the UE 115-a. For example, the UE 115-a can perform an LBT procedure prior to performing an S-SSB 220 transmission. The UE 115-a can listen (e.g., sense) for transmissions made by other devices prior to broadcasting the S-SSB 220, and can perform the broadcast if the UE 115-a determines that there are no transmissions made by other devices (e.g., or that the measured signal strength is below a threshold). In some examples, if the success rate of LBT procedures at the UE 115-a (e.g., the ratio of LBT procedures that result in the UE 115-a making a transmission) is high, the default state can correspond to S-SSB occasions being available for sidelink data transmissions. Alternatively, if the success rate of LBT procedures at the UE 115-a is low (which can correspond to a relatively busy transmission environment), the default state can correspond to S-SSB occasions being unavailable for sidelink data transmissions.

[0110] In some examples, the indication 215 can indicate to override the default state for a single upcoming S-SSB occasion (e.g., or to enable or disable S-SSB occasions for sidelink data transmission). For example, the indication 215 can apply to (e.g., correspond to) the next S-SSB occasion in the S-SSB occasions, or to (e.g., correspond to) a particular S-SSB occasion in the S-SSB occasions indicated in the message (e.g., the message containing the indication 215). In some other examples, the indication 215 can apply to all upcoming occasions in the S-SSB occasions until the UE 115-a transmits a second message containing a second indication 215, in which case the default state is resumed (e.g., S-SSB occasions are disabled or enabled for sidelink data transmission, which corresponds to the state prior to transmitting the first indication 215). In some cases, the indication 215 can expire based on the expiration of the current S-SSB period, and the default state can resume based on the start of a new S-SSB period, regardless of whether the network entity 105-a has received a second indication 215 from the UE 115-a. Reference is made herein to Figure 3A and Figure 3B These examples are described in more detail.

[0111] In some cases, UE 115-b can transmit a message containing an indication 215-b associated with an override default state to UE 115-a, and UE 115-a can forward the indication 215-b by transmitting a message containing the indication 215-a to network entity 105-a. For example, UE 115-b can be unable to communicate with network entity 105-a, or network entity 105-a can not be aware of which UE 115 UE 115-a is performing sidelink communications with, as a sidelink destination ID (e.g., within a SL-BSR) indicated by UE 115-a can be relative in nature and not identify UE 115-b without additional information. In some cases, UE 115-b can determine to transmit the indication 215-b based similarly to UE 115-a. For example, if the default state corresponds to S-SSB occasions being available for sidelink data transmissions, then if UE 115-b is to transmit (e.g., or receive) a reference signal associated with S-SSB 220, UE 115-b can transmit a message including the indication 215-b to prevent network entity 105-a from scheduling an overlapping sidelink data transmission during one or more upcoming ones of the S-SSB occasions. Meanwhile, if the default state corresponds to S-SSB occasions being unavailable for sidelink data transmissions, then if UE 115-b has data (e.g., in a buffer) available for a sidelink data message 225 (e.g., or if UE 115-b is waiting to receive a sidelink data message 225 from UE 115-a), UE 115-b can transmit a message including the indication 215-b. Alternatively, UE 115-b can transmit a message containing the indication 215-b directly to network entity 105-a, as described herein with reference to FIG. 2. Figure 5 are described in more detail.

[0112] Figure 3A An example of a signaling diagram 300-a that supports data transmission availability in S-SSB occasions is shown in accordance with one or more aspects of the present disclosure. The signaling diagram 300-a can depict S-SSB occasions 305 (e.g., S-SSB occasion 305-a, S-SSB occasion 305-b, S-SSB occasion 305-c, S-SSB occasion 305-d, and S-SSB occasion 305-e) that can be associated with occasions (e.g., one or more resources) during which a UE 115 can transmit (e.g., broadcast) an S-SSB (e.g., one or more S-SSB reference signals), as described herein with reference to FIG. 2. Figure 1 and Figure 2described. Additionally, signaling diagram 300-a illustrates example communications between UE 115 and network entity 105 of indications 310 (e.g., indication 310-a, indication 310-b, indication 310-c, and indication 310-d), which can be examples of indications 215 associated with whether S-SSB occasions 305 are enabled or disabled for sidelink data transmissions (e.g., by indicating an override to a default state), as described herein with reference to Figure 2 described.

[0113] In some examples, S-SSB occasions 305 can be associated with a default state, as described herein with reference to Figure 1 and Figure 2 For example, the default state can correspond to S-SSB occasions 305 being available for sidelink data transmissions. Thus, if UE 115 is to transmit an S-SSB (e.g., one or more S-SSB reference signals), UE 115 can transmit a message including indication 310 to prevent network entity 105 from scheduling an overlapping sidelink data message during one or more upcoming S-SSB occasions 305. In some other examples, the default state can correspond to S-SSB occasions 305 being unavailable for sidelink data transmissions. Thus, if UE 115 has data available for sidelink data transmissions (e.g., in a sidelink data buffer), UE 115 can transmit a message including indication 310.

[0114] In some examples, indication 310 can indicate an override of the default state for a single upcoming S-SSB occasion 305 (e.g., or, for example, in cases where a default state is not explicitly defined, enable or disable S-SSB occasions 305 for sidelink data transmissions). For example, as illustrated in Figure 3A indication 310-a can indicate an override of the default state for next S-SSB occasion 305-b. Similarly, UE 115 can transmit indication 310-b to network entity 105 indicating an override of the default state for S-SSB occasion 305-c, indication 310-c indicating an override of the default state for S-SSB occasion 305-d, and indication 310-d indicating an override of the default state for S-SSB occasion 305-e. UE 115 can not transmit an indication after S-SSB occasion 305-e and before next S-SSB occasion 305-f, and thus the default state can apply to S-SSB occasion 305-f again.

[0115] Figure 3BAn example of a signaling diagram 300-b that supports data transmission availability in S-SSB occasions is shown in accordance with one or more aspects of the present disclosure. The signaling diagram 300-b can implement aspects of the signaling diagram 300-a. For example, the signaling diagram 300-b can depict S-SSB occasions 305 (e.g., S-SSB occasion 305-g, S-SSB occasion 305-h, S-SSB occasion 305-i, S-SSB occasion 305-j, S-SSB occasion 305-k, and S-SSB occasion 305-l) that can be examples of S-SSB occasions as described with reference to Figures 1 to 3A FIG. 2. Moreover, the signaling diagram 300-b illustrates example communications, indications 310 (e.g., indication 310-e and indication 310-f) between the UE 115 and the network entity 105 that can be examples of the indication 215 or indication 310 associated with whether S-SSB occasions 305 are enabled or disabled for sidelink data transmission as described with reference to Figure 2 and Figure 3A

[0116] In some examples, the indication 310 can indicate that the default state is overridden for all upcoming S-SSB occasions 305 (e.g., or for example, where a default state is not explicitly defined, S-SSB occasions 305 are enabled or disabled for sidelink data transmission) until the UE 115 (e.g., or in some cases, another UE 115 in communication with the UE 115) sends a second indication 310 to the network entity 105. For example, the default state can apply to S-SSB occasion 305-g. The UE 115 can then send the indication 310-e, which can override the default state for subsequent S-SSB occasions 305. For example, the default state can be overridden for S-SSB occasion 305-h, S-SSB occasion 305-i, S-SSB occasion 305-j, and S-SSB occasion 305-k. The UE 115 can then send another indication 310-f, which can restore the default state for subsequent S-SSB occasions 305, such as S-SSB occasion 305-l.

[0117] In some cases, the indication 310 can expire based on the expiration of the current S-SSB period 315. For example, the first S-SSB period 315-a can end before the start of S-SSB occasion 305-l and after S-SSB occasion 305-k. Thus, even if the UE 115 does not send the indication 310-f to the network entity 105, the default state can be restored for subsequent S-SSB occasions 305 within the second S-SSB period 315-b (e.g., starting with S-SSB occasion 305-l).

[0118] Figure 4 ​An example of a signaling diagram 400 that supports data transmission availability in S-SSB occasions is shown in accordance with one or more aspects of the present disclosure. The signaling diagram 400 can illustrate communications between a UE 115 and a network entity 105, which can be as described herein with reference to FIGs. 1-2. The UE 115 can transmit an indication to the network entity 105 indicating to override a default state for one or more S-SSB occasions (e.g., or to enable or disable S-SSB occasions for sidelink data transmission, for example, in cases where a default state is not explicitly defined), as described herein with reference to FIGs. 1-2. The network entity 105 can configure one or more control message occasions 410 to the UE 115 via an RRC message (e.g., within one or more information elements, such as PUCCH-Config). The UE 115 can transmit a dedicated control message (e.g., generated for transmitting the indication) to the network entity 105 during a control message occasion 410-a including the indication associated with the default state override, as described herein with reference to FIGs. 1-2. Figures 1 to 3B Examples of corresponding components are described.

[0119] In some examples, the UE 115 can transmit an indication indicating to override a default state for one or more S-SSB occasions (e.g., or to enable or disable S-SSB occasions for sidelink data transmission, for example, in cases where a default state is not explicitly defined), as described herein with reference to FIGs. 1-2. In some cases, the UE 115 can transmit the indication to the network entity 105 within a control message (e.g., PUCCH), and the one or more control message occasions 410 can be configured to the UE 115 via an RRC message (e.g., within one or more information elements, such as PUCCH-Config). For example, the UE 115 can transmit a dedicated control message (e.g., generated for transmitting the indication) to the network entity 105 during a control message occasion 410-a including the indication associated with the default state override. Figures 1 to 3B

[0120] Additionally or alternatively, the UE 115 can include the indication as one or more additional bits within a control message carrying other control information (e.g., multiplexed or piggybacked to the control message). In some examples, the network entity 105 can transmit a downlink message 405 (e.g., a control message, an RRC message containing one or more information elements) that can configure the UE 115 with one or more windows 415 for transmitting control messages (e.g., including one or more time resources, frequency resources, or both). In some cases, control messages transmitted during control message occasions 410 within the configured window 415 can be larger (e.g., have a larger payload size) than control messages transmitted outside of the configured window 415, as the configured window 415 can allocate more resources for transmitting additional information. Accordingly, the UE 115 can be configured to transmit the indication as one or more additional bits within a control message transmitted during the configured window 415. For example, the UE 115 can include the indication as one or more additional bits included (e.g., multiplexed, piggybacked) in a control message including other control information and transmitted during a control message occasion 410-b within the configured window 415-a.

[0121] Figure 5 ​An example of a wireless communications system 500 that supports data transmission availability in S-SSB occasions is shown in accordance with one or more aspects of the present disclosure. The wireless communications system 500 can be an example of, or incorporate aspects of, the wireless communications system 100 and the wireless communications system 200. For example, the wireless communications system 500 illustrates communications between a UE 115-c, a UE 115-d, and a network entity 105-b, which can be examples of the UEs 115 and network entities 105 described herein with reference to the Figures 1 to 4 described examples of corresponding components. Similarly, the UE 115-c, the UE 115-d, and the network entity 105-n can perform communications via a communication link 505-a, a communication link 505-b, and a communication link 505-c, which can be examples of the communication links 125 or the communication links 205 as described herein with reference to Figure 1 and Figure 2 described.

[0122] In some examples, the UE 115-c and the UE 115-d can transmit a message to the network entity 105-b containing an indication 515 associated with a default state covering one or more S-SSB occasions, as described herein with reference to Figures 2 to 4 However, in some cases, the network entity 105-b can not be aware of which UEs 115 the UE 115-a is performing sidelink communications with. For example, the UE 115-a can transmit a SL-BSR 520, which can include one or more sidelink destination IDs. However, the network entity 105-b can not be able to determine which UEs 115 the sidelink destination IDs correspond to. Thus, if the UE 115-d transmits a message to the network entity 105-b including the indication 515, the network entity 105-b can not be able to associate the indication 515 with sidelink communications for the UE 115-c. This can result in scheduling uncertainty, as the network entity 105-b can not be able to properly enable or disable the conveyance of sidelink data messages 530 during S-SSB occasions if indicated by the UE 115-d.

[0123] According to examples as described herein, UE 115-c and UE 115-d can be configured to transmit one or more respective layer 2 IDs 510 to network entity 105-b. For example, UE 115-c can transmit a message (e.g., an RRC message) to network entity 105-b indicating one or more layer 2 IDs 510-a associated with UE 115-c, and UE 115-d can transmit a message (e.g., an RRC message) to network entity 105-b indicating one or more layer 2 IDs 510-b associated with UE 115-d. In some cases, the one or more layer 2 IDs 510 can be associated with different broadcast types, different sessions, or both. In some examples, the message indicating the layer 2 IDs 510 can be transmitted during a communication establishment procedure, such as when UE 115-c and UE 115-d initiate a sidelink procedure.

[0124] Accordingly, network entity 105-b can receive the SL-SBR 520 from UE 115-c, and network entity 105-b can identify (e.g., determine) UEs 115 in communication with UE 115-c based on the destination IDs (e.g., associated with UE 115-d, and in some cases, other UEs 115) provided in the SL-SBR 520 and any reported layer 2 IDs 510. For example, network entity 105-b can determine that UE 115-d is in sidelink communication with UE 115-c based on the destination ID provided by UE 115-c in the SL-SBR 520 and the one or more layer 2 IDs 510-b provided by UE 115-d. In some examples, network entity 105-b can generate a mapping between the received layer 2 IDs 510 and UEs 115 based on the received layer 2 IDs 510. Further, network entity 105-b can identify that UE 115-d has transmitted the indication 515, and network entity 105-b can associate the indication 515 with scheduling for UE 115-c based on the mapping and the SL-SBR 520. Accordingly, network entity 105-b can perform scheduling of sidelink data messages 530 by UE 115-c while preventing overlap with S-SSB transmissions, for example, by enabling or disabling transmission of sidelink data messages 530 during S-SSB occasions based on the indication 515 received from UE 115-d (e.g., regarding default state override as described herein).

[0125] Figure 6An example of a process flow 600 that supports data transmission availability in S-SSB occasions is shown in accordance with one or more aspects of the present disclosure. The process flow 600 can illustrate communications between a network entity 105-c, a UE 115-e, and a UE 115-f, which can be as described herein with reference to FIGs. 1-2. In some examples, the steps depicted in the process flow 600 can be performed in a different order. Additionally, some steps can be added or omitted from the process flow 600. Figures 1 to 5 The described examples of corresponding devices. In some examples, the steps depicted in the process flow 600 can be performed in a different order. Additionally, some steps can be added or omitted from the process flow 600.

[0126] At 605, the UE 115-f can transmit a message (e.g., an RRC message) to the network entity 105-c indicating one or more Layer 2 IDs associated with the UE 115-f. Similarly, at 610, the UE 115-e can transmit a message (e.g., an RRC message) to the network entity 105-c indicating one or more Layer 2 IDs 510-a associated with the UE 115-e. In some examples, the Layer 2 IDs can enable the network entity 105-c to map the Layer 2 IDs to respective UEs 115.

[0127] At 615, the network entity 105-c can transmit a message (e.g., an RRC message) to configure the UE 115-e with one or more S-SSB occasions associated with S-SSBs transmitted (e.g., broadcasted) by the UE 115-e. In some examples, the one or more S-SSB occasions can be in addition to other S-SSB occasions previously (e.g., by the network entity 105-c) configured or indicated to the UE 115-e.

[0128] At 620, the UE 115-e can transmit a message including an indication associated with a default state override. The indication can inform the network entity 105-c of an override to a default state associated with whether one or more S-SSB occasions are available for sidelink data transmission scheduled by the network entity 105-c associated with the UE 115-e. For example, the default state can correspond to the one or more S-SSB occasions being available for sidelink data transmission. Thus, if the UE 115-e is to transmit an S-SSB (e.g., one or more S-SSB reference signals), the UE 115-e can transmit the message including the indication to prevent the network entity 105-c from scheduling an overlapping sidelink data message during one or more upcoming occasions of the S-SSB occasions. In some other examples, the default state can correspond to the S-SSB occasions being unavailable for sidelink data transmission. Thus, if the UE 115-e has data (e.g., in a sidelink data buffer) available for a sidelink data message, the UE 115-e can transmit the message including the indication.

[0129] At 625, UE 115-f can transmit a message including the indication. For example, network entity 105-c can identify that UE 115-e and UE 115-f are in sidelink communication based on the receiver layer 2 ID and the SL-BSR transmitted by UE 115-e. Accordingly, network entity 105-c can perform scheduling of sidelink data transmissions for UE 115-e based on the indication transmitted by UE 115-f.

[0130] At 630, UE 115-e and UE 115-f can communicate one or more S-SSB reference signals (e.g., one or more reference signals associated with S-SSB broadcast) in accordance with the scheduling by network entity 105-c. For example, UE 115-e can broadcast one or more S-SSB reference signals, and UE 115-f can measure the one or more S-SSB reference signals. Additionally or alternatively, UE 115-f can broadcast one or more S-SSB reference signals, and UE 115-e can receive the one or more S-SSB reference signals.

[0131] Accordingly, by transmitting the indication associated with the override default state, UE 115-e and UE 115-f can communicate sidelink data messages and S-SSB reference signals non- overlappingly during S-SSB occasions.

[0132] Figure 7 An example of a process flow 700 that supports data transmission availability in S-SSB occasions is shown in accordance with one or more aspects of the present disclosure. Process flow 700 can illustrate communications between a network entity 105-d and a UE 115-g, which can be examples of the corresponding devices as described herein with reference to FIGs. 1-6. In some examples, the steps depicted in process flow 700 can be performed in a different order. Additionally, some steps can be added or omitted from process flow 700. Figures 1 to 6

[0133] At 705, network entity 105-d can transmit a message (e.g., an RRC message) to configure UE 115-g with one or more S-SSB occasions associated with transmission (e.g., broadcast) of S-SSBs by UE 115-g. In some examples, the one or more S-SSB occasions can be in addition to other S-SSB occasions previously configured or indicated to UE 115-g (e.g., by network entity 105-d).

[0134] ​At 710, the network entity 105-d can transmit a message that allocates one or more resources to the UE 115-g for a sidelink data message (e.g., PSSCH) with another UE 115. In some examples, the one or more resources for the sidelink data message can overlap with a time occasion of the one or more S-SSB occasions.

[0135] At 715, the UE 115-g can determine that the sidelink data message overlaps with an S-SSB to be transmitted on a time occasion of the one or more S-SSB occasions, and the UE 115-g can discard the sidelink data message. In some examples, the UE 115-g can discard the sidelink data message based on a priority value of the sidelink data message being lower than a priority value associated with the S-SSB to be transmitted within the overlapping occasion.

[0136] At 720, the UE 115-g can transmit a negative acknowledgement (e.g., NACK) within a control message (e.g., PUCCH) associated with the sidelink data message (e.g., a PUCCH for signaling a HARQ-ACK associated with the sidelink data message). In some examples, the negative acknowledgement (e.g., or the PUCCH carrying the negative acknowledgement) can have a same priority value as a priority value of the discarded sidelink data message.

[0137] Thus, the UE 115-g can utilize an S-SSB occasion to transmit a sidelink data message, and the UE 115-g can be configured with a procedure for notifying the network entity 105-d in case of an overlap between the sidelink data message and the S-SSB. Thus, the network entity 105-d can perform rescheduling of the discarded sidelink data message and can configure the UE 115-g with an additional grant for the sidelink data message.

[0138] Figure 8 A block diagram 800 of a device 805 that supports data transmission availability in S-SSB occasions is shown in accordance with one or more aspects of the present disclosure. The device 805 can be an example of aspects of a UE 115 as described herein. The device 805 can include a receiver 810, a transmitter 815, and a communications manager 820. The device 805 can also include a processor. Each of these components can be in communication with one another (e.g., via one or more buses).

[0139] The receiver 810 can provide 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 data transmission availability in S-SSB occasions). Information can be passed on to other components of the device 805. The receiver 810 can utilize a single antenna or a set of multiple antennas.

[0140] The transmitter 815 can provide a means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 can 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 data transmission availability in S-SSB occasions). In some examples, the transmitter 815 can be collocated with the receiver 810 in a transceiver module. The transmitter 815 can utilize a single antenna or a set of multiple antennas.

[0141] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof or various components thereof can be examples of means for performing various aspects of data transmission availability in S-SSB occasions as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof can support a method for performing one or more of the functions described herein.

[0142] In some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof can be implemented in hardware (e.g., in communication management circuitry). The hardware can include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a microcode controller, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in this disclosure. In some examples, a processor and memory coupled with the processor can be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory).

[0143] Additionally or alternatively, in some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof can be implemented in code (e.g., as communication management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof can be executed 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.

[0144] In some examples, the communication manager 820 can be configured to use or otherwise employ the receiver 810, the transmitter 815, or both, to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting). For example, the communication manager 820 can receive information from the receiver 810, transmit information to the transmitter 815, or be integrated in combination with or otherwise

[0145] The communication manager 820 can support wireless communication at a first UE in accordance with examples as disclosed herein. For example, the communication manager 820 can be, be configured to, or be operable to support a means for receiving a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE. The communication manager 820 can be, be configured to, or be operable to support a means for transmitting, to a network entity, a second message including an indication to override a default state associated with whether the one or more occasions are available for sidelink data transmissions between at least the first UE and the second UE. The communication manager 820 can be, be configured to, or be operable to support a means for communicating one or more reference signals between at least the first UE and the second UE based on transmitting the second message to the network entity.

[0146] Additionally or alternatively, the communication manager 820 can support wireless communication at a first UE in accordance with examples as disclosed herein. For example, the communication manager 820 can be, be configured to, or be operable to support a means for receiving a message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE, where an upcoming occasion of the one or more occasions associated with the S-SSB transmissions overlaps with an occasion for a sidelink data transmission. The communication manager 820 can be, be configured to, or be operable to support a means for dropping the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion. The communication manager 820 can be, be configured to, or be operable to support a means for transmitting a negative acknowledgement message based on dropping the sidelink data transmission, where a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission.

[0147] By including or configuring the communication manager 820 in accordance with examples as described herein, the device 805 (e.g., a processor controlling the receiver 810, the transmitter 815, the communication manager 820, or a combination or otherwise of them, or otherwise coupled with them) can support techniques for performing sidelink data transmissions while avoiding overlap with S-SSB transmissions in a larger communication spectrum, thereby more efficiently utilizing communication resources.

[0148] Figure 9 A block diagram 900 of a device 905 that supports data transmission availability in S-SSB occasions is shown, in accordance with one or more aspects of the present disclosure. The device 905 can be an example of aspects of a device 805 or a UE 115 as described herein. The device 905 can include a receiver 910, a transmitter 915, and a communications manager 920. The device 905 can also include a processor. Each of these components can be in communication with one another (e.g., via one or more buses).

[0149] The receiver 910 can provide 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 data transmission availability in S-SSB occasions). Information can be passed on to other components of the device 905. The receiver 910 can utilize a single antenna or a set of multiple antennas.

[0150] The transmitter 915 can provide means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 can transmit information associated with various information channels (e.g., control channels, data channels, information channels related to data transmission availability in S-SSB occasions), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 915 can be collocated with the receiver 910 in a transceiver module. The transmitter 915 can utilize a single antenna or a set of multiple antennas.

[0151] The device 905 or its various components can be an example of means for performing various aspects of data transmission availability in S-SSB occasions as described herein. For example, the communications manager 920 can include a S-SSB occasion manager 925, an overlap component 930, a S-SSB component 935, a sidelink data component 940, a feedback component 945, or any combination thereof. The communications manager 920 can be an example of aspects of the communications manager 820 as described herein. In some examples, the communications manager 920 or various components thereof can be configured to receive, obtain, monitor, output, transmit, or the like using or in conjunction with the receiver 910, the transmitter 915, or both. For example, the communications manager 920 can receive information from the receiver 910, transmit information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0152] The communications manager 920 can support wireless communication at a first UE in accordance with examples as disclosed herein. The S-SSB occasion manager 925 can support, be configured as, or can operate as a means for receiving a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE. The override component 930 can support, be configured as, or can operate as a means for transmitting, to a network entity, a second message including an indication of an override default state associated with whether the one or more occasions are available for sidelink data transmissions between at least the first UE and the second UE. The S-SSB component 935 can support, be configured as, or can operate as a means for communicating one or more reference signals between at least the first UE and the second UE based on transmitting the second message to the network entity.

[0153] Additionally or alternatively, the communications manager 920 can support wireless communication at a first UE in accordance with examples as disclosed herein. The S-SSB component 935 can support, be configured as, or can operate as a means for receiving a message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE, where an upcoming occasion of the one or more occasions associated with the S-SSB transmissions overlaps with an occasion for a sidelink data transmission. The sidelink data component 940 can support, be configured as, or can operate as a means for dropping the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion. The feedback component 945 can support, be configured as, or can operate as a means for transmitting a negative acknowledgement message based on dropping the sidelink data transmission, where a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission.

[0154] Figure 10 A block diagram 1000 of a communications manager 1020 that supports data transmission availability in S-SSB occasions is shown in accordance with one or more aspects of the present disclosure. The communications manager 1020 can be an example of aspects of a communications manager 820, a communications manager 920, or both, as described herein. The communications manager 1020, or various components thereof, can be an example of means for performing various aspects of data transmission availability in S-SSB occasions as described herein. For example, the communications manager 1020 can include a S-SSB occasion manager 1025, an override component 1030, a S-SSB component 1035, a sidelink data component 1040, a feedback component 1045, an ID component 1050, an overlap component 1055, or any combination thereof. Each of these components can communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0155] The communications manager 1020 can support wireless communication at a first UE in accordance with examples as disclosed herein. The S-SSB occasion manager 1025 can enable, be configured as, or be operable to support means for receiving a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE. The override component 1030 can enable, be configured as, or be operable to support means for transmitting, to a network entity, a second message including an indication of an override default state, the default state being associated with whether the one or more occasions are available for sidelink data transmissions between at least the first UE and the second UE. The S-SSB component 1035 can enable, be configured as, or be operable to support means for communicating one or more reference signals between at least the first UE and the second UE based on transmitting the second message to the network entity.

[0156] In some examples, the second message indicates the override default state for a next occasion of the one or more occasions. In some examples, the second message indicates the override default state for an occasion within a current S-SSB period.

[0157] In some examples, the override component 1030 can enable, be configured as, or be operable to support means for transmitting, to the network entity, a fourth message including an indication to return to the default state for an occasion within a current S-SSB period.

[0158] In some examples, the ID component 1050 can enable, be configured as, or be operable to support means for transmitting, to the network entity, a third message indicating one or more Layer 2 ID values associated with the first UE prior to receiving the first message.

[0159] In some examples, the default state indicates that the one or more occasions are available for sidelink data transmissions between at least the first UE and the second UE. In some examples, the default state indicates that the one or more occasions are not available for sidelink data transmissions between at least the first UE and the second UE.

[0160] In some examples, the sidelink data component 1040 can enable, be configured as, or be operable to support means for transmitting a sidelink data message to the second UE during a next occasion of the one or more occasions based on the default state being overridden.

[0161] In some examples, to support communicating the one or more reference signals, the S-SSB component 1035 can enable, be configured as, or be operable to support means for communicating the one or more reference signals during an occasion subsequent to the next occasion of the one or more occasions.

[0162] In some examples, the overriding component 1030 can be, configured as, or can operate a means for supporting transmission of a fourth message to the network entity, the fourth message including an indication to return to a default state for occasions within a current S-SSB period, where communicating the one or more reference signals is based on transmitting the fourth message.

[0163] In some examples, the default state is based on a success rate associated with a listen-before-talk procedure at the first UE for S-SSB transmissions. In some examples, the indication to override the default state includes one or more bits within a second message, the second message including an uplink control message.

[0164] In some examples, to support transmission of the second message, the overriding component 1030 can be, configured as, or can operate a means for transmitting the uplink control message during a time window configured by the network entity, where the one or more bits include one or more additional bits included in the second message based on transmitting the uplink control message during the time window. In some examples, the second message includes a dedicated control message associated with transmitting the indication to override the default state.

[0165] In some examples, the overriding component 1030 can be, configured as, or can operate a means for receiving a message from the second UE including an indication to override the default state, where transmitting the second message to the network entity is based on receiving the message from the second UE including the indication to override the default state.

[0166] In some examples, the overlapping component 1055 can be, configured as, or can operate a means for determining that an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with an occasion for sidelink data transmissions. In some examples, the sidelink data component 1040 can be, configured as, or can operate a means for dropping the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with the S-SSB transmission associated with the upcoming occasion. In some examples, the feedback component 1045 can be, configured as, or can operate a means for transmitting a negative acknowledgement message based on dropping the sidelink data transmission, where a priority value associated with the negative acknowledgement message is a same value as the priority value associated with the sidelink data transmission.

[0167] Additionally or alternatively, the communication manager 1020 can support wireless communication at a first UE in accordance with examples as disclosed herein. In some examples, the S-SSB component 1035 can enable, be configured as, or be operable to support means for receiving a message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE, where an upcoming occasion of the one or more occasions associated with the S-SSB transmissions overlaps with a time occasion for a sidelink data transmission. The sidelink data component 1040 can enable, be configured as, or be operable to support means for dropping the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion. The feedback component 1045 can enable, be configured as, or be operable to support means for transmitting a negative acknowledgement message based on dropping the sidelink data transmission, where a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission.

[0168] In some examples, the S-SSB component 1035 can enable, be configured as, or be operable to support means for transmitting one or more reference signals to the second UE based on dropping the sidelink data transmission.

[0169] In some examples, the coverage component 1030 can enable, be configured as, or be operable to support means for transmitting a message to a network entity, the message including an indication of a default state of coverage, the default state being associated with whether the one or more occasions are available for sidelink data transmissions between at least the first UE and a second UE.

[0170] Figure 11 A diagram illustrates a system 1100 including a device 1105 that supports data transmission availability in S-SSB occasions in accordance with one or more aspects of the present disclosure. The device 1105 can be an example of or include the components of a device 805, a device 905, or a UE 115 as described herein. The device 1105 can communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). The device 1105 can include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, a memory 1130, code 1135, and a processor 1140. These components can be in electronic communication or otherwise

[0171] I / O controller 1110 manages the input and output signals of device 1105. I / O controller 1110 can also manage peripheral devices not integrated into device 1105. In some cases, I / O controller 1110 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1110 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 1110 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1110 may be implemented as part of a processor (such as processor 1140). In some cases, a user may interact with device 1105 via the I / O controller 1110 or via hardware components controlled by the I / O controller 1110.

[0172] In some cases, device 1105 may include a single antenna 1125. However, in other cases, device 1105 may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1115 may communicate bidirectionally via one or more antennas 1125, a wired or wireless link as described herein. For example, transceiver 1115 may represent a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. Transceiver 1115 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1125 for transmission; and demodulating packets received from one or more antennas 1125. Transceiver 1115, or transceiver 1115 and one or more antennas 1125, may be an example of transmitter 815, transmitter 915, receiver 810, receiver 910, or any combination thereof or components thereof, as described herein.

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

[0174] The processor 1140 can 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 processor 1140 can be configured to operate a memory array. In some other cases, a memory controller can be integrated into the processor 1140. The processor 1140 can be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting data transmission availability in S-SSB occasions). For example, the device 1105 or a component of the device 1105 can include the processor 1140 and the memory 1130 coupled with or to the processor 1140, the processor 1140 and the memory 1130 being configured to perform various functions described herein.

[0175] According to examples as disclosed herein, the communication manager 1120 can support wireless communication at a first UE. For example, the communication manager 1120 can be, be configured as, or be operable as, a means for receiving a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE. The communication manager 1120 can be, be configured as, or be operable as, a means for transmitting, to a network entity, a second message including an indication to override a default state associated with whether the one or more occasions are available for sidelink data transmissions between at least the first UE and the second UE. The communication manager 1120 can be, be configured as, or be operable as, a means for communicating one or more reference signals between at least the first UE and the second UE based on transmitting the second message to the network entity.

[0176] Additionally, or alternatively, the communication manager 1120 can support wireless communication at a first UE in accordance with examples as disclosed herein. For example, the communication manager 1120 can enable, be configured to, or be operable to support means for receiving a message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE, where an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with a time occasion for a sidelink data transmission. The communication manager 1120 can enable, be configured to, or be operable to support means for dropping the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion. The communication manager 1120 can enable, be configured to, or be operable to support means for transmitting a negative acknowledgement message based on dropping the sidelink data transmission, where a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission.

[0177] By including or configuring the communication manager 1120 in accordance with examples as described herein, the device 1105 can support techniques for performing sidelink data transmissions in larger communication spectrums while avoiding overlap with S-SSB transmissions, thereby more efficiently utilizing communication resources and reducing latency due to avoiding retransmissions.

[0178] In some examples, the communication manager 1120 can be configured to use or otherwise employ the transceiver 1115, the one or more antennas 1125, or any combination thereof, to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 can be supported by, or performed by, the processor 1140, the memory 1130, the code 1135, or any combination thereof. For example, the code 1135 can include instructions executable by the processor 1140 to cause the device 1105 to perform various aspects of data transmission availability in S-SSB occasions as described herein, or the processor 1140 and the memory 1130 can be otherwise configured to perform or support such operations.

[0179] Figure 12 A block diagram 1200 of a device 1205 that supports data transmission availability in S-SSB occasions is shown in accordance with one or more aspects of the present disclosure. The device 1205 can be an example of aspects of a network entity 105 as described herein. The device 1205 can include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 can also include a processor. Each of these components can be in communication with one another (e.g., via one or more buses).

[0180] Receiver 1210 can provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information can pass to other components of the device 1205. In some examples, receiver 1210 can support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, receiver 1210 can support obtaining information by receiving signals via one or more wired (e.g., electrical, optical), wireless interfaces, or any combination thereof.

[0181] Transmitter 1215 can provide means for outputting (e.g., transmitting, providing, transferring, communicating) information generated by other components of the device 1205. For example, transmitter 1215 can output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1215 can support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, transmitter 1215 can support outputting information by transmitting signals via one or more wired (e.g., electrical, optical), wireless interfaces, or any combination thereof. In some examples, transmitter 1215 and receiver 1210 can be collocated in a transceiver, which can include or be coupled with a modem.

[0182] Communication manager 1220, receiver 1210, transmitter 1215, or various combinations thereof or various components thereof can be examples of means for performing various aspects of data transmission availability in S-SSB occasions as described herein. For example, communication manager 1220, receiver 1210, transmitter 1215, or various combinations or components thereof can support a method for performing one or more of the functions described herein.

[0183] In some examples, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof can be implemented in hardware (e.g., in communications management circuitry). The hardware can include a processor, a DSP, a CPU, an ASIC, an FPGA, or other programmable logic device, a microcode, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in this disclosure. In some examples, a processor and memory coupled with the processor can be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in memory).

[0184] Additionally or alternatively, in some examples, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof can be implemented in code (e.g., as communication management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof can be executed 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.

[0185] In some examples, the communication manager 1220 can be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1210, the transmitter 1215, or both. For example, the communication manager 1220 can receive information from the receiver 1210, transmit information to the transmitter 1215, or be integrated in combination with the receiver 1210, the transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0186] The communications manager 1220 can support wireless communication at a network entity in accordance with examples as disclosed herein. For example, the communications manager 1220 can enable, be configured as, or be operable to support means for transmitting, to a first UE, a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE. The communications manager 1220 can enable, be configured as, or be operable to support means for receiving a second message including an indication overriding a default status associated with whether the one or more occasions are available for sidelink data transmissions between at least the first UE and the second UE. The communications manager 1220 can enable, be configured as, or be operable to support means for scheduling one or more sidelink data transmissions between at least the first UE and the second UE for one or more resources selected based at least in part on the default status being overridden.

[0187] Additionally or alternatively, the communications manager 1220 can support wireless communication at a network entity in accordance with examples as disclosed herein. For example, the communications manager 1220 can enable, be configured as, or be operable to support means for transmitting a message indicating one or more occasions associated with S-SSB transmissions between at least a first UE and a second UE, where an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with an occasion for sidelink data transmissions. The communications manager 1220 can enable, be configured as, or be operable to support means for receiving, from the first UE, a negative acknowledgement message indicating that the first UE dropped the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion, where the priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission.

[0188] By including or configuring the communications manager 1220 in accordance with examples as described herein, the device 1205 (e.g., a processor of the device 1205 controlling the receiver 1210, the transmitter 1215, the communications manager 1220, or a combination of them or otherwise coupled to them) can support a technique for scheduling sidelink data transmissions while avoiding overlap with S-SSB transmissions, thereby more efficiently utilizing communication resources.

[0189] Figure 13 A block diagram 1300 of a device 1305 that supports data transmission availability in S-SSB occasions is shown, in accordance with one or more aspects of the present disclosure. The device 1305 can be an example of aspects of a device 1205 or a network entity 105 as described herein. The device 1305 can include a receiver 1310, a transmitter 1315, and a communications manager 1320. The device 1305 can also include a processor. Each of these components can be in communication with one another (e.g., via one or more buses).

[0190] Receiver 1310 can provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information can pass to other components of the device 1305. In some examples, the receiver 1310 can support obtaining information by receiving signals through one or more antennas. Additionally or alternatively, the receiver 1310 can support obtaining information by receiving signals through one or more wired (e.g., electrical, optical), wireless interfaces, or any combination thereof.

[0191] Transmitter 1315 can provide means for outputting (e.g., sending, providing, transmitting) information generated by other components of the device 1305. For example, the transmitter 1315 can output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1315 can support outputting information by transmitting signals through one or more antennas. Additionally or alternatively, the transmitter 1315 can support outputting information by transmitting signals through one or more wired (e.g., electrical, optical), wireless interfaces, or any combination thereof. In some examples, the transmitter 1315 and the receiver 1310 can be collocated in a transceiver, which can include or be coupled to a modem.

[0192] Device 1305 or its various components can be an example of means for performing various aspects of data transmission availability in S-SSB occasions as described herein. For example, the communications manager 1320 can include a S-SSB occasion component 1325, a coverage manager 1330, a sidelink data manager 1335, a feedback manager 1340, or any combination thereof. The communications manager 1320 can be an example of aspects of the communications manager 1220 as described herein. In some examples, the communications manager 1320 or its various components can be configured to use or otherwise employ the receiver 1310, the transmitter 1315, or both, to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting). For example, the communications manager 1320 can receive information from the receiver 1310, transmit information to the transmitter 1315, or be integrated in combination with the receiver 1310, the transmitter 1315, or both, to obtain information, output information, or perform various other operations as described herein.

[0193] According to examples as disclosed herein, the communications manager 1320 can support wireless communication at a network entity. The S-SSB occasion component 1325 can enable, be configured as, or be operable to support means for transmitting a first message to a first UE indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE. The coverage manager 1330 can enable, be configured as, or be operable to support means for receiving a second message including an indication of a coverage default state associated with whether the one or more occasions are available for sidelink data transmissions between at least the first UE and the second UE. The sidelink data manager 1335 can enable, be configured as, or be operable to support means for scheduling one or more sidelink data transmissions between at least the first UE and the second UE for one or more resources selected based at least in part on the default state being overridden.

[0194] Additionally or alternatively, according to examples as disclosed herein, the communications manager 1320 can support wireless communication at a network entity. The S-SSB occasion component 1325 can enable, be configured as, or be operable to support means for transmitting a message indicating one or more occasions associated with S-SSB transmissions between at least a first UE and a second UE, where an upcoming occasion of the one or more occasions associated with the S-SSB transmissions overlaps with an occasion for a sidelink data transmission. The feedback manager 1340 can enable, be configured as, or be operable to support means for receiving a negative acknowledgement message from the first UE indicating that the first UE dropped the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion, where a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission.

[0195] Figure 14A block diagram 1400 illustrating the communication manager 1420 that supports data transmission availability in S-SSB occasions in accordance with one or more aspects of the present disclosure is shown. The communication manager 1420 can be an example of aspects of a communication manager 1220, a communication manager 1320, or both, as described herein. The communication manager 1420, or various components thereof, can be an example of means for performing various aspects of data transmission availability in S-SSB occasions as described herein. For example, the communication manager 1420 can include a S-SSB occasion component 1425, an override manager 1430, a sidelink data manager 1435, a feedback manager 1440, an ID manager 1445, or any combination thereof. Each of these components can communicate, directly or indirectly, with one another (e.g., via one or more buses), which can include communication among protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0196] The communication manager 1420 can support wireless communication at a network entity in accordance with examples as disclosed herein. The S-SSB occasion component 1425 can enable, be configured as, or be operable to support means for transmitting a first message to a first UE, the first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE. The override manager 1430 can enable, be configured as, or be operable to support means for receiving a second message, the second message including an indication of an override default state, the default state being associated with whether the one or more occasions are available for sidelink data transmissions between at least the first UE and the second UE. The sidelink data manager 1435 can enable, be configured as, or be operable to support means for scheduling one or more sidelink data transmissions between at least the first UE and the second UE for one or more resources selected based at least in part on the default state being overridden.

[0197] In some examples, the ID manager 1445 can enable, be configured as, or be operable to support means for receiving a third message from the second UE, the third message indicating one or more Layer 2 ID values associated with the second UE, where receiving the second message is based on receiving the third message from the second UE.

[0198] In some examples, the ID manager 1445 is capable of, configured for, or operable with a means for receiving, from the first UE, a sidelink buffer status report indicating one or more destination ID values. In some examples, the ID manager 1445 is capable of, configured for, or operable with a means for determining that a destination identity value of the one or more destination ID values is associated with the second UE, where scheduling the one or more sidelink data transmissions is based on the determination.

[0199] In some examples, the second message indicates that a default status is overridden for a next occasion of the one or more occasions.

[0200] In some examples, the second message indicates that a default status is overridden for occasions within a current S-SSB period.

[0201] In some examples, the override manager 1430 is capable of, configured for, or operable with a means for receiving a fourth message including an indication to return to a default status for occasions within a current S-SSB period.

[0202] In some examples, the default status indicates that the one or more occasions are unavailable for sidelink data transmissions between the first UE and the second UE, and to support scheduling the one or more sidelink data transmissions, the sidelink data manager 1435 is capable of, configured for, or operable with a means for scheduling, based on the default status being overridden, sidelink data transmissions between at least the first UE and the second UE during an occasion of the one or more occasions based on receiving the second message.

[0203] In some examples, the default status indicates that the one or more occasions are available for sidelink data transmissions between the first UE and the second UE, and to support scheduling the one or more sidelink data transmissions, the sidelink data manager 1435 is capable of, configured for, or operable with a means for scheduling, based on receiving the second message, sidelink data transmissions between at least the first UE and the second UE for resources different from a next occasion of the one or more occasions.

[0204] In some examples, the indication to override the default status includes one or more bits within the second message, the second message including an uplink control message.

[0205] Additionally or alternatively, the communication manager 1420 can support wireless communication at a network entity in accordance with examples as disclosed herein. In some examples, the S-SSB occasion component 1425 can enable, be configured as, or be operable to support a means for transmitting a message indicating one or more occasions associated with S-SSB transmissions between at least a first UE and a second UE, where an upcoming occasion of the one or more occasions associated with the S-SSB transmissions overlaps with an occasion for sidelink data transmissions. The feedback manager 1440 can enable, be configured as, or be operable to support a means for receiving a negative acknowledgement message from the first UE indicating that the first UE dropped the sidelink data transmissions based on a priority value associated with the sidelink data transmissions being lower than a priority value associated with the synchronization signal block transmissions associated with the upcoming occasion, where the priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmissions.

[0206] In some examples, the coverage manager 1430 can enable, be configured as, or be operable to support a means for receiving a message from the first UE including an indication of a coverage default state, the default state being associated with whether the one or more occasions are available for sidelink data transmissions between at least the first UE and the second UE.

[0207] Figure 15 A diagram illustrates a system 1500 including a device 1505 that supports data transmission availability in S-SSB occasions in accordance with one or more aspects of the present disclosure. The device 1505 can be an example of or include the components of device 1205, device 1305, or a network entity 105 as described herein. The device 1505 can communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, the communication can include communications through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1505 can include components for supporting output and receiving communications, such as a communication manager 1520, a transceiver 1510, an antenna 1515, a memory 1525, code 1530, and a processor 1535. These components can be in electronic communication or otherwise

[0208] The transceiver 1510 can support bi-directional communication over a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1510 can include a wired transceiver and can communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1510 can include a wireless transceiver and can communicate bidirectionally with another wireless transceiver. In some examples, the device 1505 can include one or more antennas 1515, which can be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1510 can also include a modem to modulate signals, provide modulated signals to be transmitted (e.g., by the one or more antennas 1515, by a wired transmitter), receive signals (e.g., from the one or more antennas 1515, from a wired receiver), and demodulate signals. In some implementations, the transceiver 1510 can include one or more interfaces, such as one or more interfaces coupled with one or more antennas 1515 configured to support various receive or obtain operations, or one or more interfaces coupled with one or more antennas 1515 configured to support various transmit or output operations, or a combination thereof. In some implementations, the transceiver 1510 can include or be coupled with one or more processors or memory components capable of operating to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1510, or the transceiver 1510 and one or more antennas 1515, or the transceiver 1510 and one or more antennas 1515 and one or more processors or memory components (e.g., the processor 1535 or the memory 1525, or both), can be included in a chip or chip assembly mounted in the device 1505. In some examples, the transceiver can be operable to support communication via one or more communication links (e.g., the communication links 125, the backhaul communication links 120, the midhaul communication links 162, the fronthaul communication links 168).

[0209] Memory 1525 can include RAM and ROM. The memory 1525 can store computer- readable, computer-executable code 1530 including instructions that, when executed by the processor 1535, cause the device 1505 to perform various functions described herein. The code 1530 can be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1530 can not be directly executable by the processor 1535 but can cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory 1525 can include, among other things, a BIOS which can control basic hardware or software operation such as the interaction with peripheral components or devices.

[0210] The processor 1535 can include an intelligent hardware device, (e.g., a general- purpose processor, a DSP, a ASIC, a CPU, a FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1535 can be configured to operate a memory array using a memory controller. In some other cases, a memory controller can be integrated into the processor 1535. The processor 1535 can be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1525) to cause the device 1505 to perform various functions (e.g., functions or tasks for supporting data transmission availability in S-SSB occasions). For example, the device 1505 or a component of the device 1505 can include the processor 1535 and the memory 1525 coupled with the processor 1535, which are configured to perform various functions described herein. The processor 1535 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host (e.g., by executing code 1530) functions for performing functions of the device 1505. The processor 1535 can be any one or more suitable processors that can execute scripts or instructions of one or more software programs stored in the device 1505, such as within the memory 1525. In some implementations, the processor 1535 can be a component of a processing system. A processing system can generally refer to a system or series of machines or components that receive inputs and process those inputs to produce a set of outputs (which can be passed to other systems or components of the device 1505, for example). For example, a processing system of the device 1505 can refer to a system that includes various other components or subcomponents of the device 1505, such as the processor 1535 or the transceiver 1510 or the communications manager 1520, or a combination of other components or components of the device 1505. The processing system of the device 1505 can interface with other components of the device 1505 and can process information received from other components (such as inputs or signals) or output information to other components. For example, a chip or modem of the device 1505 can include a processing system and one or more interfaces for outputting information or for obtaining information, or both. The one or more interfaces can be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and to obtain information, among other implementations. In some implementations, the one or more interfaces can refer to an interface between the processing system of the chip or modem and a transmitter such that the device 1505 can transmit information output from the chip or modem.Additionally or alternatively, in some implementations, the one or more interfaces can refer to an interface between a processing system of a chip or modem and a receiver that enables the device 1505 to obtain information or signal input and the information can be passed to the processing system. One of ordinary skill in the art would readily recognize that the first interface can also obtain information or signal input and the second interface can also output information or signal output.

[0211] In some examples, the bus 1540 can support communication of protocol layers (e.g., within which protocol layers) of a protocol stack. In some examples, the bus 1540 can support communication associated with logical channels of a protocol stack (e.g., between protocol layers of the protocol stack), which can include communication performed within a component of the device 1505, or between different components of the device 1505 that can be co-located or located in different locations (e.g., where the device 1505 can refer to a system in which one or more of the communication manager 1520, the transceiver 1510, the memory 1525, the code 1530, and the processor 1535 can be located in one component or partitioned between different components).

[0212] In some examples, the communication manager 1520 can manage aspects of the communication (e.g., via one or more wired or wireless backhaul links) with a core network 130. For example, the communication manager 1520 can manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 1520 can manage communications with other network entities 105, and can include a controller or scheduler for coordinating communications with UEs 115 in cooperation with other network entities 105. In some examples, the communication manager 1520 can support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0213] According to examples as disclosed herein, the communication manager 1520 can support wireless communications at a network entity. For example, the communication manager 1520 can be capable of, configured to, or operable to support means for transmitting a first message to a first UE, the first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE. The communication manager 1520 can be capable of, configured to, or operable to support means for receiving a second message including an indication overriding a default status, the default status associated with whether the one or more occasions are available for sidelink data transmissions between at least the first UE and the second UE. The communication manager 1520 can be capable of, configured to, or operable to support means for scheduling one or more sidelink data transmissions between at least the first UE and the second UE for one or more resources selected based at least in part on the default status being overridden.

[0214] Additionally or alternatively, the communication manager 1520 can support wireless communication at a network entity in accordance with examples as disclosed herein. For example, the communication manager 1520 can enable, be configured to, or be operable to support means for transmitting a message indicating one or more occasions associated with S-SSB transmissions between at least a first UE and a second UE, where an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with a time occasion for a sidelink data transmission. The communication manager 1520 can enable, be configured to, or be operable to support means for receiving a negative acknowledgement message from the first UE indicating that the first UE dropped the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion, where the priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission.

[0215] By including or configuring the communication manager 1520 in accordance with examples as described herein, the device 1505 can support techniques for scheduling sidelink data transmissions while avoiding overlap with S-SSB transmissions, thereby more efficiently utilizing communication resources and reducing latency.

[0216] In some examples, the communication manager 1520 can be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1510, the one or more antennas 1515 (e.g., when applicable), or any combination thereof. Although the communication manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1520 can be supported by or performed in connection with the transceiver 1510, the processor 1535, the memory 1525, the code 1530, or any combination thereof. For example, the code 1530 can include instructions executable by the processor 1535 to cause the device 1505 to perform various aspects of data transmission availability in S-SSB occasions as described herein, or the processor 1535 and the memory 1525 can be otherwise configured to support or perform such operations.

[0217] Figure 16 A flow diagram illustrating a method 1600 that supports data transmission availability in S-SSB occasions in accordance with aspects of the present disclosure is shown. The operations of method 1600 can be implemented by a UE or its components as described herein. For example, the operations of method 1600 can be performed by a UE 115 as described with reference to FIG. 1A through 1D, 2, 3, 5A, 5B, 6, 7, 8, or 9 through 12. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE can perform aspects of the described functions using special-purpose hardware. Figures 1 to 11

[0218] ​At 1605, the method can include receiving a first message indicating one or more occasions associated with S-SSB transmissions between at least a first UE and a second UE. The operations of block 1605 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1605 can be performed by a S-SSB occasion manager 1025 as described with reference to Figure 10 FIG. 12.

[0219] At 1610, the method can include transmitting, to the network entity, a second message including an indication to override a default state associated with whether the one or more occasions are available for sidelink data transmissions between at least the first UE and the second UE. The operations of block 1610 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1610 can be performed by an override component 1030 as described with reference to Figure 10 FIG. 13.

[0220] At 1615, the method can include communicating one or more reference signals between at least the first UE and the second UE based on transmitting the second message to the network entity. The operations of block 1615 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1615 can be performed by a S-SSB component 1035 as described with reference to Figure 10 FIG. 14.

[0221] Figure 17 A flow diagram illustrating an example method 1700 that supports data transmission availability in S-SSB occasions is shown. The operations of method 1700 can be implemented by a UE or its components as described herein. For example, the operations of method 1700 can be performed by a UE 115 as described with reference to Figures 1 to 11 FIG. 15. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE can perform aspects of the described functions using special-purpose hardware.

[0222] At 1705, the method can include transmitting, to a network entity, a third message indicating one or more Layer 2 ID values associated with the first UE. The operations of block 1705 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1705 can be performed by an ID component 1050 as described with reference to Figure 10 FIG. 16.

[0223] At 1710, the method can include receiving a first message indicating one or more occasions associated with S-SSB transmissions between at least a first UE and a second UE. The operations of block 1710 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1710 can be performed by a S-SSB occasion manager 1025 as described with reference toFigure 10 The S-SSB occasion manager 1025 described can perform the operations.

[0224] At 1715, the method can include transmitting, to the network entity, a second message including an indication of an override default state, the default state being associated with whether one or more occasions are available for sidelink data transmissions between at least the first UE and the second UE. The operations of block 1715 can be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1715 can be performed by an override component 1030 as described with reference to Figure 10

[0225] At 1720, the method can include communicating one or more reference signals between at least the first UE and the second UE based on transmitting the second message to the network entity. The operations of block 1720 can be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1720 can be performed by an S-SSB component 1035 as described with reference to Figure 10

[0226] Figure 18 A flow diagram illustrating a method 1800 that supports data transmission availability in S-SSB occasions in accordance with aspects of the present disclosure is shown. The operations of method 1800 can be implemented by a network entity or its components as described herein. For example, the operations of method 1800 can be performed by a network entity as described with reference to Figures 1 to 7 and Figures 12 to 15 In some examples, a network entity can execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity can perform aspects of the described functions using special-purpose hardware.

[0227] At 1805, the method can include transmitting, to a first UE, a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE. The operations of block 1805 can be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1805 can be performed by an S-SSB occasion component 1425 as described with reference to Figure 14

[0228] At 1810, the method can include receiving a second message including an indication of an override default state, the default state being associated with whether one or more occasions are available for sidelink data transmissions between at least the first UE and the second UE. The operations of block 1810 can be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1810 can be performed by an override manager 1430 as described with reference to Figure 14

[0229] ​​​​At 1815, the method can include scheduling one or more sidelink data transmissions between at least the first UE and the second UE for one or more resources selected based at least in part on being overridden based on the default state. The operations of block 1815 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1815 can be performed by a sidelink data manager 1435 as described with reference to Figure 14

[0230] Figure 19 A flow diagram illustrating an example method 1900 that supports data transmission availability in S-SSB occasions in accordance with aspects of the present disclosure is shown. The operations of method 1900 can be implemented by a UE or its components as described herein. For example, the operations of method 1900 can be performed by a UE 115 as described with reference to Figures 1 to 11 FIGS. 11 and 12. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE can perform aspects of the described functions using special-purpose hardware.

[0231] At 1905, the method can include receiving a message indicating one or more occasions associated with S-SSB transmissions between at least a first UE and a second UE, where an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with an occasion for a sidelink data transmission. The operations of block 1905 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1905 can be performed by a S-SSB component 1035 as described with reference to Figure 10 FIGS. 11 and 12. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE can perform aspects of the described functions using special-purpose hardware.

[0232] At 1910, the method can include dropping the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion. The operations of block 1910 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1910 can be performed by a sidelink data component 1040 as described with reference to Figure 10 FIGS. 11 and 12. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE can perform aspects of the described functions using special-purpose hardware.

[0233] At 1915, the method can include transmitting a negative acknowledgement message based on dropping the sidelink data transmission, where a priority value of the negative acknowledgement message is a same value as a priority value of the sidelink data transmission. The operations of block 1915 can be performed according to the examples as disclosed herein. In some examples, aspects of the operations of 1915 can be performed by a feedback component 1045 as described with reference to Figure 10 FIGS. 11 and 12. In some examples, a UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE can perform aspects of the described functions using special-purpose hardware.

[0234] Figure 20 ​A flow diagram illustrating a method 2000 that supports data transmission availability in S-SSB occasions in accordance with aspects of the present disclosure is shown. The operations of method 2000 can be implemented by a network entity or its components as described herein. For example, the operations of method 2000 can be performed by a network entity as described with reference to Figs. 1A-1B and 2A-2B. In some examples, a network entity can execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity can perform aspects of the described functions using special-purpose hardware. Figures 1 to 7 Also Figures 12 to 15 Additionally or alternatively, the network entity can perform aspects of the described functions using special-purpose hardware.

[0235] At 2005, the method can include transmitting a message indicating one or more occasions associated with S-SSB transmissions between at least a first UE and a second UE, where an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with an occasion for sidelink data transmissions. The operations of block 2005 can be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2005 can be performed by a S-SSB occasion component 1425 as described with reference to Figs. 1A-1B and 2A-2B. Figure 14

[0236] At 2010, the method can include receiving a negative acknowledgement message from the first UE indicating that the first UE dropped the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with the synchronization signal block transmission associated with the upcoming occasion, where the priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission. The operations of block 2010 can be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2010 can be performed by a feedback manager 1440 as described with reference to Figs. 1A-1B and 2A-2B. Figure 14

[0237] The following provides an overview of aspects of the present disclosure:

[0238] Aspect 1 : A method for wireless communication at a first UE, the method comprising: receiving a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE; transmitting, to a network entity, a second message including an indication to override a default state associated with whether the one or more occasions can be used for sidelink data transmissions between the first UE and the second UE; and communicating one or more reference signals between at least the first UE and the second UE based at least in part on transmitting the second message to the network entity.

[0239] ​​Aspect 2: The method of Aspect 1, wherein the second message indicates that the default status is overridden for a next occasion of the one or more occasions.

[0240] Aspect 3: The method of Aspect 1, wherein the second message indicates that the default status is overridden for an occasion within a current S-SSB period.

[0241] Aspect 4: The method of Aspect 3, further comprising: transmitting, to the network entity, a fourth message including an indication to return to the default status for occasions within the current S-SSB period.

[0242] Aspect 5: The method of any one of Aspects 1-4, further comprising: transmitting, to the network entity, a third message indicating one or more Layer 2 ID values associated with the first UE prior to transmitting the first message.

[0243] Aspect 6: The method of any one of Aspects 1-5, wherein the default status indicates that the one or more occasions can be used for sidelink data transmissions between the first UE and the second UE.

[0244] Aspect 7: The method of any one of Aspects 1-5, wherein the default status indicates that the one or more occasions cannot be used for sidelink data transmissions between the first UE and the second UE.

[0245] Aspect 8: The method of Aspect 7, further comprising: transmitting, to the second UE, a sidelink data message during a next occasion of the one or more occasions based at least in part on the default status being overridden.

[0246] Aspect 9: The method of Aspect 8, wherein communicating the one or more reference signals further comprises: communicating the one or more reference signals during an occasion subsequent to the next occasion of the one or more occasions.

[0247] Aspect 10: The method of any one of Aspects 7-9, further comprising: transmitting, to the network entity, a fourth message including an indication to return to the default status for occasions within a current S-SSB period, wherein communicating the one or more reference signals is based at least in part on transmitting the fourth message.

[0248] Aspect 11: The method of any one of Aspects 1-10, wherein the default status is based at least in part on a success rate associated with a listen-before-talk procedure at the first UE for S-SSB transmissions.

[0249] Aspect 12: The method of any one of aspects 1 through 11, wherein the indication that the default status is overridden comprises one or more bits within the second message, the second message comprising an uplink control message.

[0250] Aspect 13: The method of aspect 12, wherein transmitting the second message further comprises: transmitting the uplink control message during a time window configured by the network entity, wherein the one or more bits comprise one or more additional bits included in the second message based at least in part on transmitting the uplink control message during the time window.

[0251] Aspect 14: The method of any one of aspects 12 through 13, wherein the second message comprises a dedicated control message associated with transmitting the indication that the default status is overridden.

[0252] Aspect 15: The method of any one of aspects 1 through 14, the method further comprising: receiving, from the second UE, a message comprising the indication that the default status is overridden, wherein transmitting the second message to the network entity is based at least in part on receiving, from the second UE, the message comprising the indication that the default status is overridden.

[0253] Aspect 16: The method of any one of aspects 1 through 15, the method further comprising: determining that an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with an occasion for a sidelink data transmission; dropping the sidelink data transmission based at least in part on a priority value associated with the sidelink data transmission being lower than a priority value associated with an S-SSB transmission associated with the upcoming occasion; and transmitting a negative acknowledgement message based at least in part on dropping the sidelink data transmission, wherein a priority value associated with the negative acknowledgement message is a same value as the priority value associated with the sidelink data transmission.

[0254] Aspect 17: A method for wireless communications at a network entity, comprising: transmitting, to a first UE, a first message indicating one or more occasions associated with S-SSB transmissions between at least the first UE and a second UE; receiving a second message comprising an indication that a default status is overridden, the default status being associated with whether the one or more occasions can be used for sidelink data transmissions between the first UE and the second UE; and scheduling one or more sidelink data transmissions between at least the first UE and the second UE for one or more resources selected based at least in part on the default status being overridden.

[0255] Aspect 18: The method of aspect 17, further comprising: receiving, from the second UE, a third message indicating one or more Layer 2 ID values associated with the second UE, wherein receiving the second message is based at least in part on receiving the third message from the second UE.

[0256] Aspect 19: The method of aspect 18, further comprising: receiving, from the first UE, a sidelink buffer status report indicating one or more destination ID values; and determining that a destination ID value of the one or more destination ID values is associated with the second UE, wherein scheduling the one or more sidelink data transmissions is based at least in part on the determination.

[0257] Aspect 20: The method of any one of aspects 17 to 19, wherein the second message indicates that the default status is overridden for a next occasion of the one or more occasions.

[0258] Aspect 21: The method of any one of aspects 17 to 19, wherein the second message indicates that the default status is overridden for occasions within a current S-SSB period.

[0259] Aspect 22: The method of aspect 21, further comprising: receiving a fourth message including an indication to return to the default status for occasions within the current S-SSB period.

[0260] Aspect 23: The method of any one of aspects 17 to 22, wherein the default status indicates that the one or more occasions are unavailable for sidelink data transmissions between the first UE and the second UE, and wherein scheduling the one or more sidelink data transmissions comprises: based at least in part on the default status being overridden, based at least in part on receiving the second message, scheduling a sidelink data transmission between the first UE and the second UE during an occasion of the one or more occasions.

[0261] Aspect 24: The method of any one of aspects 17 to 22, wherein the default status indicates that the one or more occasions are available for sidelink data transmissions between the first UE and the second UE, and wherein scheduling the one or more sidelink data transmissions comprises: based at least in part on receiving the second message, scheduling a sidelink data transmission between the first UE and the second UE for resources different from a next occasion of the one or more occasions.

[0262] Aspect 25: The method of any of aspects 17 through 24, wherein the indication covering the default state comprises one or more bits within the second message, the second message comprising an uplink control message.

[0263] Aspect 26: A method for wireless communication at a first UE, comprising: receiving a message indicating one or more occasions associated with S-SSB transmissions between the first UE and a second UE, wherein an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with an occasion for a sidelink data transmission; dropping the sidelink data transmission based at least in part on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion; and transmitting a negative acknowledgement message based at least in part on dropping the sidelink data transmission, wherein a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission.

[0264] Aspect 27: The method of aspect 26, further comprising: transmitting one or more reference signals to the second UE based at least in part on dropping the sidelink data transmission.

[0265] Aspect 28: The method of any of aspects 26 through 27, further comprising: transmitting, to a network entity, a message comprising an indication covering a default state, the default state being associated with whether the one or more occasions can be used for a sidelink data transmission between the first UE and the second UE.

[0266] Aspect 29: A method for wireless communication at a network entity, comprising: transmitting a message indicating one or more occasions associated with S-SSB transmissions between a first UE and a second UE, wherein an upcoming occasion of the one or more occasions associated with S-SSB transmissions overlaps with an occasion for a sidelink data transmission; and receiving, from the first UE, a negative acknowledgement message indicating that the first UE dropped the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion, wherein a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission.

[0267] Aspect 30: The method of aspect 29, further comprising: receiving, from the first UE, a message comprising an indication covering a default state, the default state being associated with whether the one or more occasions can be used for a sidelink data transmission between the first UE and the second UE.

[0268] Aspect 31 : An apparatus for wireless communication at a first UE, the apparatus comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any of aspects 1-16.

[0269] Aspect 32 : An apparatus for wireless communication at a first UE, the apparatus comprising at least one means for performing the method of any of aspects 1-16.

[0270] Aspect 33 : A non-transitory computer-readable medium storing code for wireless communication at a first UE, the code comprising instructions executable by a processor to perform the method of any of aspects 1-16.

[0271] Aspect 34 : An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any of aspects 17-25.

[0272] Aspect 35 : An apparatus for wireless communication at a network entity, the apparatus comprising at least one means for performing the method of any of aspects 17-25.

[0273] Aspect 36 : A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method of any of aspects 17-25.

[0274] Aspect 37 : An apparatus for wireless communication at a first UE, the apparatus comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any of aspects 26-28.

[0275] Aspect 38 : An apparatus for wireless communication at a first UE, the apparatus comprising at least one means for performing the method of any of aspects 26-28.

[0276] Aspect 39 : A non-transitory computer-readable medium storing code for wireless communication at a first UE, the code comprising instructions executable by a processor to perform the method of any of aspects 26-28.

[0277] Aspect 40: An apparatus for wireless communication at a network entity, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any of aspects 29 through 30.

[0278] Aspect 41: An apparatus for wireless communication at a network entity, comprising at least one means for performing the method of any of aspects 29 through 30.

[0279] Aspect 42: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method of any of aspects 29 through 30.

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

[0281] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system can be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology can 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 can be applicable to various other wireless communication 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, and others.

[0282] Information and signals described herein can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that can be referenced throughout the description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0283] The various illustrative blocks and components described in connection with the disclosure herein can be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, but in the alternative, the processor can be any processor, controller, microcontroller, or state machine. A processor can 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).

[0284] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium and executed by the processor. 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 can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions can also be physically located at different locations, including being distributed such that portions of functions are implemented at different physical locations.

[0285] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium can be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can 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 can be used to carry or store desired program code means in the form of instructions or data structures and that can 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 where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0286] As used herein, including in the claims,“or” as used in a list of items prefaced by“at least one of’ indicates a disjunctive list such that, e.g., 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). Additionally, as used herein, the phrase“based on” is not meant to be limiting. For example, a step that is described as“based on condition A” can be based on both condition A and condition B, without departing from the scope of the present disclosure. In other words, as used herein the phrase“based on” should be interpreted in the same manner as the phrase“based at least in part on.”

[0287] The term“determining” encompasses a wide variety of actions and, therefore,“determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via 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 in a memory) and the like. Also, “determining” can include resolving, selecting, choosing, establishing and other such similar actions.

[0288] In the drawings, like reference numerals can be used to denote similar components throughout the several views. Further, components of the same type can be distinguished by following the reference numeral with a dashed line and a second label wherein the second label distinguishes among the group of similar components. If only the first reference numeral is used in the specification, the description is applicable to any one of the similar components having the same first reference numeral irrespective of the second reference label or second reference numerals.

[0289] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that can be implemented or that are within the scope of the claims. The term“example” as used herein means“serving as an example, instance, or illustration,” and not“preferred” or“superior” over other examples. The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0290] The description herein is presented to enable any person skilled in the art to practice the present disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other variations without departing from the scope of the disclosure. Thus, the present disclosure is not to be 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. An apparatus for wireless communication at a first user equipment (UE), the apparatus comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receive a first message indicating one or more occasions associated with sidelink synchronization signal block transmissions between at least the first UE and a second UE; transmit, to a network entity, a second message including an indication to override a default state associated with whether the one or more occasions can be used for sidelink data transmissions between at least the first UE and the second UE; and communicate one or more reference signals between at least the first UE and the second UE based at least in part on transmitting the second message to the network entity.

2. The apparatus of claim 1, wherein the second message indicates to override the default state for a next occasion of the one or more occasions.

3. The apparatus of claim 1, wherein the second message indicates to override the default state for an occasion within a current sidelink synchronization signal block period.

4. The apparatus of claim 3, wherein the instructions are further executable by the processor to cause the apparatus to: transmit, to the network entity, a fourth message including an indication to return to the default state for an occasion within the current sidelink synchronization signal block period.

5. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: transmit, to the network entity, a third message indicating one or more layer 2 identification values associated with the first UE prior to receiving the first message.

6. The apparatus of claim 1, wherein the default state indicates that the one or more occasions can be used for sidelink data transmissions between at least the first UE and the second UE.

7. The apparatus of claim 1, wherein the default state indicates that the one or more occasions cannot be used for sidelink data transmissions between at least the first UE and the second UE.

8. The apparatus of claim 7, wherein the instructions are further executable by the processor to cause the apparatus to: transmit, to the second UE, a sidelink data message during a next occasion of the one or more occasions based at least in part on the default state being overridden.

9. The apparatus of claim 8, wherein the instructions to communicate the one or more reference signals are further executable by the processor to cause the apparatus to: communicate the one or more reference signals during an occasion subsequent to the next occasion of the one or more occasions.

10. The apparatus of claim 7, wherein the instructions are further executable by the processor to cause the apparatus to: transmitting a fourth message to the network entity, the fourth message including an indication to return to the default state for occasions within a current sidelink synchronization signal block period, wherein communicating the one or more reference signals is based at least in part on transmitting the fourth message.

11. The apparatus of claim 1, wherein the default state is based at least in part on a success rate associated with a listen-before-talk procedure at the first UE for sidelink synchronization signal block transmissions.

12. The apparatus of claim 1, wherein the indication overriding the default state comprises one or more bits within the second message, the second message comprising an uplink control message.

13. The apparatus of claim 12, wherein to transmit the second message, the instructions are executable by the processor to cause the apparatus to: transmit the uplink control message during a time window configured by the network entity, wherein the one or more bits comprise one or more additional bits included in the second message based at least in part on transmitting the uplink control message during the time window.

14. The apparatus of claim 12, wherein the second message comprises a dedicated control message associated with transmitting the indication overriding the default state.

15. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receive, from the second UE, a message including the indication overriding the default state, wherein transmitting the second message to the network entity is based at least in part on receiving, from the second UE, the message including the indication overriding the default state.

16. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: determine that an upcoming occasion of the one or more occasions associated with sidelink synchronization signal block transmissions overlaps with an occasion for sidelink data transmissions; drop the sidelink data transmissions based at least in part on a priority value associated with the sidelink data transmissions being lower than a priority value associated with sidelink synchronization signal block transmissions associated with the upcoming occasion; and transmit a negative acknowledgement message based at least in part on dropping the sidelink data transmissions, wherein a priority value associated with the negative acknowledgement message is a same value as the priority value associated with the sidelink data transmissions.

17. An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: transmit a first message to a first user equipment (UE), the first message indicating one or more occasions associated with sidelink synchronization signal block transmissions between at least the first UE and a second UE; transmit a second message to the first UE, the second message indicating a default state for the one or more occasions associated with the sidelink synchronization signal block transmissions between at least the first UE and the second UE; and transmit a third message to the first UE, the third message indicating an override of the default state for the one or more occasions associated with the sidelink synchronization signal block transmissions between at least the first UE and the second UE. receiving a second message, the second message including an indication to override a default status, the default status associated with whether the one or more occasions can be used for sidelink data transmissions between at least the first UE and the second UE; and scheduling one or more sidelink data transmissions between at least the first UE and the second UE for one or more resources selected based at least in part on the default status being overridden.

18. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: receive, from the second UE, a third message indicating one or more layer 2 identification values associated with the second UE, wherein receiving the second message is based at least in part on receiving the third message from the second UE.

19. The apparatus of claim 18, wherein the instructions are further executable by the processor to cause the apparatus to: receive, from the first UE, a sidelink buffer status report indicating one or more destination identification values; and determine that a destination identification value of the one or more destination identification values is associated with the second UE, wherein scheduling the one or more sidelink data transmissions is based at least in part on the determination.

20. The apparatus of claim 17, wherein the second message indicates that the default status is overridden for a next occasion of the one or more occasions.

21. The apparatus of claim 17, wherein the second message indicates that the default status is overridden for occasions within a current sidelink synchronization signal block period.

22. The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to: receive a fourth message including an indication to return to the default status for occasions within the current sidelink synchronization signal block period.

23. The apparatus of claim 17, wherein the default status indicates that the one or more occasions cannot be used for sidelink data transmissions between the first UE and the second UE, and wherein to schedule the one or more sidelink data transmissions, the instructions are executable by the processor to cause the apparatus to: schedule, based at least in part on the default status being overridden, a sidelink data transmission between at least the first UE and the second UE during an occasion of the one or more occasions based at least in part on receiving the second message.

24. The apparatus of claim 17, wherein the default status indicates that the one or more occasions can be used for sidelink data transmissions between the first UE and the second UE, and wherein to schedule the one or more sidelink data transmissions, the instructions are executable by the processor to cause the apparatus to: schedule, based at least in part on receiving the second message, a sidelink data transmission between at least the first UE and the second UE for resources different from a next occasion of the one or more occasions.

25. The apparatus of claim 17, wherein the indication to override the default status comprises one or more bits within the second message, the second message comprising an uplink control message.

26. An apparatus for wireless communication at a first user equipment (UE), the apparatus comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receive a message indicating one or more occasions associated with sidelink synchronization signal block transmissions between at least the first UE and a second UE, wherein an upcoming occasion of the one or more occasions associated with sidelink synchronization signal block transmissions overlaps with an occasion for a sidelink data transmission; drop the sidelink data transmission based at least in part on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion; and transmit a negative acknowledgement message based at least in part on dropping the sidelink data transmission, wherein a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission.

27. The apparatus of claim 26, wherein the instructions are further executable by the processor to cause the apparatus to: transmit one or more reference signals to the second UE based at least in part on dropping the sidelink data transmission.

28. The apparatus of claim 26, wherein the instructions are further executable by the processor to cause the apparatus to: transmit, to a network entity, a message comprising an indication to override a default status associated with whether the one or more occasions can be used for a sidelink data transmission between at least the first UE and the second UE.

29. An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: transmit a message indicating one or more occasions associated with sidelink synchronization signal block transmissions between at least a first user equipment (UE) and a second UE, wherein an upcoming occasion of the one or more occasions associated with sidelink synchronization signal block transmissions overlaps with an occasion for a sidelink data transmission; and receive, from the first UE, a negative acknowledgement message indicating that the first UE dropped the sidelink data transmission based on a priority value associated with the sidelink data transmission being lower than a priority value associated with a synchronization signal block transmission associated with the upcoming occasion, wherein a priority value of the negative acknowledgement message is a same value as the priority value of the sidelink data transmission.

30. The apparatus of claim 29, wherein the instructions are further executable by the processor to cause the apparatus to: ​ receive, from the first UE, a message including an indication of a default state, the default state being associated with whether the one or more occasions can be used for sidelink data transmissions between at least the first UE and the second UE.

Images