Sidelink communication using fixed frame period

Abstract

Methods, systems, and devices for wireless communication are described. A first user equipment (UE) may be configured with timing of a frame structure for sidelink communications via a shared channel. The timing of the frame structure may correspond to a fixed frame period (FFP), and the first UE may initiate sidelink communication at a boundary of the FFP. The first UE may also support techniques for determining whether to initiate a channel access procedure to occupy a shared channel during the first FFP. In one example, the first UE may determine whether to initiate the channel access procedure to occupy the shared channel during the first FFP based on monitoring the shared channel during a second FFP for sidelink transmissions from a second UE. In another example, the first UE may receive an indication of whether to initiate the channel access procedure during the first FFP.

Description

Technical Field

[0001] The following relates to wireless communications, including sidelink communications using a fixed frame period. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques 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 communication system may include one or more network entities, each of which supports wireless communications of communication devices, which may be referred to as user equipment (UE). Some wireless communication systems may support sidelink communications between UEs in a shared radio frequency spectrum. A shared radio frequency spectrum may be a spectrum that is unlicensed, licensed to multiple operators, or licensed to a single operator with opportunistic access by other devices (e.g., a licensed radio frequency spectrum, an unlicensed radio frequency spectrum, or a combination of licensed and unlicensed radio frequency spectrum). Improved techniques for facilitating sidelink communications in a shared radio frequency spectrum may be desirable. Summary of the invention

[0004] The described technology relates to improved methods, systems, devices and apparatuses for supporting sidelink communications using a fixed frame period. A first user equipment (UE) may be configured with timing of a frame structure for sidelink communications via a shared channel. The timing of the frame structure may correspond to a fixed frame period (FFP), and the first UE may initiate sidelink communications at the boundary of the FFP. The first UE may also support technology for determining whether to initiate a channel access procedure to occupy a shared channel during a first FFP. In one example, the first UE may determine whether to initiate a channel access procedure to occupy a shared channel during a first FFP based on monitoring the shared channel during a second FFP for sidelink transmissions from a second UE. In another example, the first UE may receive an indication of whether to initiate a channel access procedure during the first FFP.

[0005] A method for wireless communication at a first user equipment (UE) is described. The method may include: identifying sidelink data to be sent in a first frame period of a set of multiple frame periods having a fixed frame duration established for communication by the first UE via a shared channel; determining whether to initiate a channel access procedure to occupy the shared channel in the first frame period; and sending the sidelink data based on the determination.

[0006] An apparatus for wireless communication at a first UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: identify sidelink data to be sent in a first frame period of a set of multiple frame periods having a fixed frame duration established for communication by the first UE via a shared channel; determine whether to initiate a channel access procedure to occupy the shared channel in the first frame period; and send the sidelink data based on the determination.

[0007] Another apparatus for wireless communication at a first UE is described. The apparatus may include: means for identifying sidelink data to be sent in a first frame period of a set of multiple frame periods having a fixed frame duration established for communication by the first UE via a shared channel; means for determining whether to initiate a channel access procedure to occupy the shared channel in the first frame period; and means for sending the sidelink data based on the determination.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a first UE is described. The code may include instructions executable by a processor to: identify sidelink data to be sent in a first frame period of a set of multiple frame periods having a fixed frame duration established for communication by the first UE via a shared channel; determine whether to initiate a channel access procedure to occupy the shared channel in the first frame period; and send the sidelink data based on the determination.

[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for monitoring a shared channel during a second frame period in the group of multiple frame periods for sidelink transmissions from a second UE, wherein determining whether to initiate a channel access procedure to occupy the shared channel during a first frame period may be based on the monitoring.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining whether to initiate a channel access procedure to occupy a shared channel during a first frame period may include operations, features, components, or instructions for the following actions: detecting a side link transmission from a second UE based on the monitoring; determining a shared channel occupancy time including a second frame period initiated by the second UE based on detecting the side link transmission; and avoiding initiating a channel access procedure to occupy a shared channel during the first frame period based on determining a shared channel occupancy time initiated by the second UE.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication in the sidelink transmission that the sidelink transmission may be from a second UE, wherein detecting the sidelink transmission from the second UE may be based on receiving the indication.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining whether to initiate a channel access procedure to occupy a shared channel during a first frame period may include operations, features, components, or instructions for the following actions: determining to initiate a channel access procedure to occupy a shared channel during the first frame period based on a failure to detect a sidelink transmission from a second UE.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of configuration of a second frame period from a network entity, a second UE, or a third UE and identifying a starting boundary of the second frame period based on receiving the indication of configuration of the second frame period, wherein monitoring sidelink transmissions from the second UE may be based on identifying the starting boundary of the second frame period.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the sidelink transmission from the second UE includes a data transmission or a shared information transmission.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving an indication in downlink control information from a network entity of whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupancy time initiated by a second UE.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving an indication in a multicast transmission from a second UE whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupancy time initiated by a third UE.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the multicast transmission includes a bitmap, and a bit or time indicator for the first UE in the bitmap indicates whether the first UE can initiate a channel access procedure to occupy a shared channel during a first frame period or share a channel occupancy time initiated by a third UE.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the multicast transmission includes a field that includes an identifier of the first UE and an indication of whether the first UE can initiate a channel access procedure to occupy a shared channel during a first frame period or share a channel occupancy time initiated by a third UE.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving an indication in a unicast transmission from a second UE whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupancy time initiated by the second UE.

[0020] A method for wireless communication at a wireless device is described. The method may include: identifying respective traffic patterns associated with a plurality of UEs; determining, based on the respective traffic patterns of the plurality of UEs, whether each of the plurality of UEs is to initiate a channel access procedure to occupy a shared channel during a first frame period in a set of a plurality of frame periods having a fixed frame duration established for communication with the plurality of UEs; and sending, based on the determination, to each UE an indication of whether to initiate a channel access procedure to occupy the shared channel during the first frame period.

[0021] An apparatus for wireless communication at a wireless device is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: identify respective traffic patterns associated with a plurality of UEs; determine, based on the respective traffic patterns associated with the plurality of UEs, whether each of the plurality of UEs is to initiate a channel access procedure to occupy a shared channel during a first frame period in a set of a plurality of frame periods having a fixed frame duration established for communication with the plurality of UEs; and send, based on the determination, to each UE an indication of whether to initiate a channel access procedure to occupy the shared channel during the first frame period.

[0022] Another apparatus for wireless communication at a wireless device is described. The apparatus may include: means for identifying respective traffic patterns associated with a plurality of UEs; means for determining, based on the respective traffic patterns associated with the plurality of UEs, whether each of the plurality of UEs is to initiate a channel access procedure to occupy a shared channel during a first frame period in a set of a plurality of frame periods having a fixed frame duration established for communication with the plurality of UEs; and means for sending, based on the determination, to each UE an indication of whether to initiate a channel access procedure to occupy the shared channel during the first frame period.

[0023] A non-transitory computer-readable medium storing code for wireless communication at a wireless device is described. The code may include instructions executable by a processor to: identify respective traffic patterns associated with a plurality of UEs; determine, based on the respective traffic patterns associated with the plurality of UEs, whether each of the plurality of UEs is to initiate a channel access procedure to occupy a shared channel during a first frame period in a set of a plurality of frame periods having a fixed frame duration established for communication with the plurality of UEs; and send, based on the determination, to each UE an indication of whether to initiate a channel access procedure to occupy the shared channel during the first frame period.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an indication of whether to initiate a channel access procedure to occupy a shared channel during a first frame period may include operations, features, components, or instructions for the following actions: sending an indication in downlink control information of whether to initiate a channel access procedure to occupy a shared channel during the first frame period or to share a channel occupancy time initiated by another UE.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an indication of whether to initiate a channel access procedure to occupy a shared channel during a first frame period may include operations, features, components, or instructions for the following actions: sending an indication of whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupancy time initiated by another UE in a multicast transmission.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the multicast transmission includes a bitmap, and each bit in the bitmap indicates whether the corresponding UE can initiate a channel access procedure to occupy a shared channel during a first frame period or share a channel occupation time initiated by another UE.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the multicast transmission includes a bitmap, and a time indicator in the bitmap indicates whether the corresponding UE can initiate a channel access procedure to occupy a shared channel during each frame period of one or more frame periods including a first frame period or share a channel occupancy time initiated by other UEs.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the multicast transmission includes a field that includes an identifier for each UE and an indication of whether each UE can initiate a channel access procedure to occupy a shared channel during a first frame period or share channel occupancy time with another UE.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an indication of whether to initiate a channel access procedure to occupy a shared channel during a first frame period may include operations, features, components, or instructions for the following actions: sending an indication to each UE in a unicast transmission of whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupancy time initiated by another UE.

[0030] A method for wireless communication at a first UE is described. The method may include: identifying, at the first UE, a configuration of timing of a frame structure for sidelink communication via a shared channel, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration; and communicating during one or more frame periods in the set of multiple frame periods of the frame structure according to the configuration.

[0031] An apparatus for wireless communication at a first UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: identify, at the first UE, a configuration of timing of a frame structure for sidelink communication via a shared channel, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration; and communicate during one or more frame periods of the set of multiple frame periods of the frame structure according to the configuration.

[0032] Another apparatus for wireless communication at a first UE is described. The apparatus may include: means for identifying, at the first UE, a configuration of timing of a frame structure for sidelink communication via a shared channel, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration; and means for communicating during one or more frame periods in the set of multiple frame periods of the frame structure according to the configuration.

[0033] A non-transitory computer-readable medium storing code for wireless communication at a first UE is described. The code may include instructions that can be executed by a processor to: identify, at the first UE, a configuration of timing of a frame structure for sidelink communication via a shared channel, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration; and communicate during one or more frame periods in the set of multiple frame periods of the frame structure according to the configuration.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying the configuration of the timing of the frame structure may include operations, features, components, or instructions for the following actions: receiving an indication of the configuration of the timing of the frame structure from a network entity or a second UE.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the configuration of the timing of the frame structure may be preconfigured at the first UE.

[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for identifying the configuration of the timing of the frame structure based on a traffic pattern at the first UE.

[0037] A method for wireless communication at a wireless device is described. The method may include: identifying a timing of a frame structure for sidelink communication via a shared channel at a first UE based on a traffic pattern associated with the first UE, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration; and sending an indication of the configuration of the timing of the frame structure to the first UE.

[0038] An apparatus for wireless communication at a wireless device is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: identify a timing of a frame structure for sidelink communication via a shared channel at a first UE based on a traffic pattern associated with the first UE, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration; and send an indication of the configuration of the timing of the frame structure to the first UE.

[0039] Another apparatus for wireless communication at a wireless device is described. The apparatus may include: means for identifying timing of a frame structure for sidelink communication via a shared channel at a first UE based on a traffic pattern associated with the first UE, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration; and means for sending an indication of the configuration of the timing of the frame structure to the first UE.

[0040] A non-transitory computer-readable medium storing code for wireless communication at a wireless device is described. The code may include instructions executable by a processor to: identify timing of a frame structure for sidelink communication via a shared channel at a first UE based on a traffic pattern associated with the first UE, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration; and send an indication of the configuration of the timing of the frame structure to the first UE.

[0041] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the wireless device includes a network entity, and the methods, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for the following actions: determining a service mode associated with a first UE based on sidelink communications scheduled by the network entity at the first UE.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the wireless device includes a second UE, and the methods, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for the following actions: receiving an indication of a service mode at the first UE from a network entity or from the first UE.

[0043] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the wireless device includes a second UE, and the second UE includes an anchor UE that may be preconfigured, configured via signaling from a network entity, or selected by one or more UEs including the first UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 An example of a wireless communication system supporting sidelink communication using a fixed frame period according to one or more aspects of the present disclosure is illustrated.

[0045] Figure 2 An example of a fixed frame period (FFP) according to one or more aspects of the present disclosure is illustrated.

[0046] Figure 3 An example of an FFP structure for sidelink communications in a shared spectrum according to one or more aspects of the present disclosure is illustrated.

[0047] Figure 4 An example of a wireless communication system supporting sidelink communication using a fixed frame period according to one or more aspects of the present disclosure is illustrated.

[0048] Figure 5 An example of channel occupancy time (COT) sharing according to one or more aspects of the present disclosure is illustrated.

[0049] Figure 6An example of initialization of a channel access procedure in accordance with one or more aspects of the present disclosure is illustrated.

[0050] Figure 7 An example of a multicast transmission indicating whether each UE of a plurality of user equipments (UEs) is to initiate a channel access procedure to occupy a shared channel in FFP according to one or more aspects of the present disclosure is illustrated.

[0051] Figure 8 An example of a process flow for supporting sidelink communications using a fixed frame period in accordance with one or more aspects of the present disclosure is illustrated.

[0052] Fig. 9 and Fig.10 A block diagram of a device supporting sidelink communications using a fixed frame period is shown in accordance with one or more aspects of the present disclosure.

[0053] Fig.11 A block diagram of a communication manager supporting sidelink communications using a fixed frame period is shown in accordance with one or more aspects of the present disclosure.

[0054] Fig.12 A diagram of a system including a device supporting sidelink communications using a fixed frame period is shown in accordance with one or more aspects of the present disclosure.

[0055] Fig.13 and Fig.14 A block diagram of a device supporting sidelink communications using a fixed frame period is shown in accordance with one or more aspects of the present disclosure.

[0056] Fig.15 A block diagram of a communication manager supporting sidelink communications using a fixed frame period is shown in accordance with one or more aspects of the present disclosure.

[0057] Fig.16 A diagram of a system including a device supporting sidelink communications using a fixed frame period is shown in accordance with one or more aspects of the present disclosure.

[0058] Figures 17 to 20 A flow chart illustrating a method of supporting sidelink communications using a fixed frame period according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0059] Some wireless communication systems may support sidelink communications between user equipment (UE) in a shared spectrum (e.g., a shared radio frequency spectrum). In such systems, UEs communicating on the sidelink may support a load-based equipment (LBE) mode or an FBE mode. In the LBE mode, the UE may contend for access to a shared channel at any time to send sidelink data on the shared channel. In the FBE mode, the UE may contend for access to a shared channel at a fixed time to send sidelink data on the shared channel. For example, in the FBE mode, the UE may be configured with a fixed frame period (FFP), and the UE may contend for access to the shared channel at the boundary of the FFP to send sidelink data in the FFP. However, in some cases, the technique for configuring the timing of the frame structure for sidelink communication on the shared channel may be undefined. In addition, in the FBE system, the technique for contending for access to the shared channel at the boundary of the FFP at the UE may be flawed.

[0060] As described herein, a wireless communication system may support efficient techniques for facilitating sidelink communications in a shared spectrum (e.g., in an FBE system). A first UE may be configured with timing of a frame structure for sidelink communications via a shared channel. The timing of the frame structure may correspond to an FFP, and the first UE may initiate sidelink communications at a boundary of the FFP. The first UE may also support techniques for determining whether to initiate a channel access procedure to occupy a shared channel during a first FFP. In one example, the first UE may determine whether to initiate a channel access procedure to occupy a shared channel during a first FFP based on monitoring the shared channel during a second FFP for sidelink transmissions from a second UE. In another example, the first UE may receive an indication of whether to initiate a channel access procedure during the first FFP.

[0061] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to sidelink communications using a fixed frame period.

[0062] Figure 1 An example of a wireless communication system 100 supporting sidelink communications using a fixed frame period according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0063] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0064] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices that take different form factors or have different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

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

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

[0067] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next generation NodeB or a gigabit NodeB (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a home NodeB, a home eNodeB, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0068] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is 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 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (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 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

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

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

[0071] Where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support sidelink communications using a fixed frame period as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0072] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may 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 communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0073] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 shown.

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

[0075] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified based on a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0076] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry either downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in TDD mode).

[0077] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be capable of being configured to support communications using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0078] The signal waveform transmitted via the carrier may 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 using MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that (e.g., in the transmission duration) a relatively high number of resource elements and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity of the communication with the UE 115.

[0079] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0080] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

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

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

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

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

[0085] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not support concurrent transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other energy-saving techniques for UEs 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

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

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

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

[0089] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity for managing access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity for routing packets or interconnecting to an external network (e.g., a serving gateway (S-GW)), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. The IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0090] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range length is about one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0091] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to adopt license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entities 105 and UEs 115 can use carrier sensing for conflict detection and avoidance. In some examples, operations performed using unlicensed bands can be based on carrier aggregation configuration (e.g., LAA) in combination with component carriers operating using licensed bands. Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

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

[0093] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of the antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0094] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels to transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map a transport channel to a physical channel.

[0095] The wireless communication system 100 may utilize unshared (e.g., licensed) and shared (e.g., unlicensed, licensed to more than one operator, licensed to one or more operators in the case of opportunistic use) radio frequency spectrum bands. For example, the wireless communication system 100 may employ license assisted access (LAA), LTE-unlicensed (LTE-U) radio access technology, NR technology in unlicensed bands (NR-U, including sidelink U) such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in unlicensed radio frequency spectrum bands, devices such as network entities 105 and UEs 115 may employ carrier sensing for conflict detection and avoidance. For example, the network entity 105 and the UE 115 may employ a listen-before-talk (LBT) procedure to ensure that a frequency channel (e.g., an LBT subchannel or a band that can be accessed via an LBT procedure) is idle before sending data. In some examples, operation in an unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating in a licensed band. Operations in the unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0096] The LBT procedure may be an example of a channel access procedure. The channel access procedure may include monitoring a channel, determining whether the channel is idle based on the monitoring, and transmitting on the channel when the channel is idle. The device may determine that the channel is idle (e.g., available for use) after monitoring the channel and failing to detect a transmission on the channel or failing to detect a transmission on the channel with a signal strength that satisfies a threshold. Alternatively, the device may determine that the channel is not idle (e.g., not available for use) after monitoring the channel and detecting one or more transmissions on the channel or detecting one or more transmissions on the channel with a signal strength that satisfies a threshold. The UE 115 may initiate a channel access procedure by monitoring the channel for transmissions from another device (e.g., another UE 115 or a network entity 105). In some cases, initiating a channel access procedure may refer to executing a channel access procedure.

[0097] In some implementations, there may be different categories of LBT procedures, including Category 1 LBT (e.g., no LBT), Category 2 LBT (e.g., LBT without backoff period including one-time channel sensing for a fixed period), Category 3 LBT (e.g., LBT with a random (or other) backoff period and a fixed-size contention window), and Category 4 LBT (e.g., LBT with a random (or other) backoff period and a variable-size contention window). In some cases, a Category 2 LBT procedure may be referred to as a one-time LBT procedure, in which the UE 115 may perform channel sensing for a defined duration (e.g., 25 μs). Additionally, a Category 4 LBT procedure may be referred to as a fairness-based LBT procedure for performing channel sensing with backoff, in which the backoff may be used to prevent the UE 115 from accessing the channel immediately after detecting that the channel is idle.

[0098] The wireless communication system 100 may support sidelink communications between UEs 115 in a shared (e.g., unlicensed) spectrum. Sidelink communications may occur in a transmit or receive resource pool. The minimum resource allocation unit for sidelink communications may be a subchannel in the frequency domain, and the resource allocation in the time domain for sidelink communications may be a time slot. Some time slots may not be able to be used for sidelinks (e.g., a subset of all time slots of a carrier may be able to be used for sidelinks), and some time slots may contain feedback resources. In some aspects, the RRC configuration for sidelink communications may be preconfigured (e.g., preloaded on UE 115) or signaled to UE 115 (e.g., from network entity 105). In some examples, network entity 105 facilitates scheduling of resources for sidelink communications (e.g., in resource allocation mode 1). In other cases, sidelink communications are performed between UEs 115 without the participation of network entity 105 (e.g., in resource allocation mode 2).

[0099] In some aspects, a UE 115 communicating via a sidelink in a shared spectrum may support an LBE mode or an FBE mode. The UE 115 may receive system information (e.g., remaining minimum system information (RMSI)) from the network entity 105 indicating an FBE mode (e.g., a semi-static channel access mode) in which the UE 115 may operate. In the LBE mode, the UE 115 may contend for access to a shared channel at any time to send sidelink data on the shared channel. In the FBE mode, the UE 115 may contend for access to a shared channel at a fixed time to send sidelink data on the shared channel. For example, in the FBE mode, the UE may be configured with an FFP, and the UE may contend for access to the shared channel at a boundary of the FFP to send sidelink data in the FFP. The UE 115 may receive an indication of an FFP configuration for the UE 115 (e.g., in a system information block 1 (SIB1)). The FFP configuration may indicate an FFP (e.g., a periodicity of a radio frame) in which the UE 115 may communicate. In some examples, the FFP configuration may be signaled to UE 115 using UE-specific RRC signaling (eg, for a FBE secondary cell (SCell)).

[0100] The FFP may include idle periods and periods for sending data, and the FFP may be limited to values ​​of 1 ms, 2 ms, 2.5 ms, 4 ms, 5 ms, and 10 ms (e.g., including idle periods). The starting position of the FFP within every two radio frames may be from an even radio frame and may be given by i*P, where and P is a fixed frame period in ms. The idle period (e.g., in FFP) for a given subcarrier spacing (SCS) may be equal to Where the minimum idle period allowed is equal to max(5% of FFP, 100μs), Ts is the symbol duration of a given SCS, and when the FBE mode of operation is indicated, the physical random access channel (PRACH) resources are considered invalid if they overlap with the idle period of the FFP. Table 1 provides the minimum number of occupied symbols for idle mode in FFP of different SCSs.

[0101] Table 1: Minimum number of occupied symbols in idle periods in FFP of different SCS

[0102] SCS(kHz) Minimum number of occupied symbols for idle 15 2 30 3 60 6 120 12

[0103] Figure 2An example of an FFP 200 according to one or more aspects of the present disclosure is illustrated. The first FFP 205-a may include a channel occupation time (COT) corresponding to a period in the FFP 205-a during which the UE 115 may occupy a shared channel for sidelink communication, and the first FFP 205-a may include an idle period. In some examples, the UE 115 may perform a channel access procedure in the idle period of the first FFP 205-a to gain access to the COT of the second FFP 205-b. If the channel access procedure is successful, the UE 115 may send sidelink data during the COT of the second FFP 205-b. Otherwise, the UE 115 may avoid occupying the COT of the second FFP 205-b. In some cases, the UE 115 may be configured with one or more FBE channel access rules that may be consistent with any regulations for FBE operation. Table 2 below provides examples of these FBE channel access rules. In some examples, the Category 2 LBT for FBE may be different from the Category 2 LBT in LBE (25 μs or 16 μs). In such an example, UE 115 may perform a 9 μs measurement before transmitting, with at least 4 μs used for measurement.

[0104] Table 2: FBE channel access rules

[0105]

[0106]

[0107] Figure 3 An example of an FFP structure 300 for sidelink communications in a shared spectrum according to one or more aspects of the present disclosure is illustrated. A UE 115 may be configured to use multiple time slots for communications, and the UE 115 may be allowed to use a subset of these time slots for sidelink communications. The time slots configured for communications at the UE 115 may include time slots 310 that can be used for the sidelink and time slots 315 that cannot be used for the sidelink and may be referred to as physical time slots, and the time slots 310 that can be used for the sidelink may be referred to as logical time slots. Figure 3 In the example of , the length of the FFP can be configured as 4 physical time slots, and the FFP can be 2ms when the SCS is 30kHz. In some cases, there may be one or more ways to construct the FFP for sidelink communication in the shared spectrum (e.g., and the alignment of the FFP with the logical time slot). The FFP may follow the specified values ​​or a subset of these values.

[0108] In the first example 300-a, the sidelink traffic may not be aligned with the starting point of the FFP. For example, the first time slot that can be used for the sidelink in cycle 305-b may not be the first time slot in cycle 305-b. Therefore, UE 115 may not occupy the channel during cycle 305-b for sidelink communication. On the contrary, UE 115 may occupy the channel during cycle 305-a corresponding to the first FFP and cycle 305-c corresponding to the second FFP. In the second example 300-b, the resource configuration of the resource pool may be based on the FFP configuration. The resource configuration of the resource pool can ensure that the logical time slot is located at the starting point of the FFP (for example, the logical time slot is the first time slot in the FFP). For example, the first time slot in each of cycles 305-d, 305-e and 305-f can be a time slot 310 that can be used for the sidelink. Thus, UE 115 may occupy the channel during period 305 - d corresponding to the first FFP, period 305 - e corresponding to the second FFP, and period 305 - f corresponding to the third FFP.

[0109] The UE 115 in the wireless communication system 100 may use the reference Figure 3 Any of the described FFP structures may be used for sidelink communications in a shared spectrum. However, in some cases, techniques for configuring the timing of a frame structure for sidelink communications on a shared channel may be undefined. In addition, in an FBE system, techniques for contending for access to a shared channel at a boundary of an FFP at a UE 115 may be flawed. For example, a UE 115 may be able to initiate a channel access procedure to occupy a shared channel during an FFP or COT, or a UE 115 may be able to share a COT with other devices. However, the behavior of the UE 115 or the specific options that the UE 115 uses for channel access may be undefined. As described herein, the wireless communication system 100 may support efficient techniques for facilitating sidelink communications in a shared spectrum (e.g., in an FBE system).

[0110] Figure 4 An example of a wireless communication system 400 supporting sidelink communication using a fixed frame period according to one or more aspects of the present disclosure is illustrated. The wireless communication system 400 includes a wireless device 405, which may be a reference Figures 1 to 3 The wireless communication system 400 also includes UE 115-a, UE 115-b, and UE 115-c, which may be reference UEs 105 and 115-c. Figures 1 to 3 An example of a depicted UE 115. The wireless communication system 400 may implement aspects of the wireless communication system 100. For example, the wireless communication system 400 may support efficient techniques for facilitating sidelink communications in a shared spectrum (eg, in a FBE system).

[0111] Before communicating with UE 115-c in a shared channel (e.g., in a shared or unlicensed spectrum), UE 115-a may identify an FFP configuration for sidelink communication in the shared channel. The FFP configuration may refer to a configuration of the timing of a frame structure for sidelink communication in a shared channel, wherein the frame structure includes a plurality of frame periods (e.g., a plurality of FFPs) with a fixed frame duration. The FFP configuration may indicate the periodicity of a radio frame (e.g., the length of the FFP), and UE 115-a may contend for access to the shared channel at the boundaries of these FFPs. In an example, UE 115-a (UE0) may be configured to communicate during FFP 420, and UE 115-b (UE1) may be configured to communicate during FFP 425. The lengths of FFP 420 and FFP 425 (e.g., the periodicity of the radio frames configured for UE 115-a and UE 115-b) may be the same or different.

[0112] In some aspects, the wireless device 405 may send an indication of the FFP configuration 410 for sidelink communications in the shared channel to the UE 115-a.

[0113] If the wireless device 405 is a network entity 105, the network entity 105 may send the FFP configuration 410 to the UE 115-a in the RRC configuration. For example, the network entity 105 may configure the FFP configuration 410 to the UE 115-a using RRC signaling (e.g., for resource allocation mode 1 for sidelink communication). Because the network entity 105 may identify the sidelink traffic at the UE 115-a (e.g., for transmission by the UE 115-a), and the network entity 105 may identify the periodic traffic of the sidelink transmission from the UE 115-a, the network entity may be able to provide the UE 115-a with an appropriate FFP configuration 410. That is, the network entity may determine the FFP configuration 410 for the UE 115-a based on the sidelink traffic at the UE 115-a (e.g., to maximize throughput). In an example, the FFP configuration 410 may be based on the amount of sidelink traffic at the UE 115-a, the average length of the bursts of the sidelink transmission from the UE 115-a, etc.

[0114] If the wireless device 405 is a UE 115, the UE 115 may send an FFP configuration 410 to the UE 115-a in a PC-5RRC configuration. The UE 115 may be connected to the UE 115-a via a PC-5 interface, on which the UE 115 may send and the UE 115-a may receive the PC-5RRC configuration. The UE 115 that provides the FFP configuration 410 to the UE 115-a may be referred to as an anchor UE 115 and may provide control information to multiple UEs 115 (e.g., out-of-coverage UEs 115). For example, the anchor UE 115 may provide the FFP configuration to multiple UEs 115 (e.g., including UE 115-a). In some examples, the anchor UE 115 of the multiple UEs 115 may be preconfigured (e.g., a programmable logic controller (PLC)). In other examples, the anchor UE 115 of the multiple UEs 115 may be RRC configured. In yet other examples, the anchor UE 115 may be selected by multiple UEs 115 (eg, multiple users may form a group and may select a central node as the anchor UE 115).

[0115] In some cases, the anchor UE 115 may support efficient techniques for determining an appropriate FFP configuration 410 to provide to the UE 115-a. For example, the anchor UE 115 may receive an indication of ongoing traffic from a plurality of UEs 115 connected to the anchor UE 115 (e.g., an indication of a traffic pattern at each of the plurality of UEs 115), and the anchor UE 115 may determine the FFP configuration for each UE based on the traffic pattern at the UE 115 (e.g., and traffic patterns at other UEs 115). Additionally or alternatively, the anchor UE 115 may receive information (e.g., related to the traffic pattern at each of the plurality of UEs 115) from the network entity 105, and the anchor UE 115 may determine the FFP configuration for each UE 115 based on the information received from the network entity 105 (e.g., for resource allocation mode 1 for sidelink communication).

[0116] In other aspects, the FFP configuration may be pre-configured at the UE 115-a, or the UE 115-a may self-configure the FFP configuration (eg, each UE 115 may configure its own FFP based on its own traffic).

[0117] Once UE 115-a is able to identify the appropriate FFP configuration, UE 115-a may communicate with other UEs 115 (e.g., UE 115-c) according to the FFP configuration. For example, UE 115-a may perform a channel access procedure to obtain access to a COT (e.g., within an FFP or across one or more FFPs), and UE 115-a may send sidelink data 415 to UE 115-c in the COT. In addition, UE 115-a may support efficient techniques for contending for access to a shared channel at the boundaries of the FFP indicated by the FFP configuration. If UE 115-a does not have sidelink data 415 to send at the beginning of the FFP, UE 115-a may not initiate a channel access procedure (e.g., initiate an FFP or COT) to obtain access to a shared channel during the FFP. Otherwise, if UE 115-a has sidelink data 415 to send at the start of FFP and UE 115-a is able to share the COT with another UE 115, UE 115-a may use the techniques described herein to determine whether to initiate a channel access procedure to occupy a shared channel during FFP or to share the COT with another UE 115.

[0118] In some aspects, UE 115-a may be configured to prioritize COT sharing. COT sharing may be given a higher priority than initializing a channel access procedure. For example, if COT sharing is available, UE 115-a may share the COT instead of initiating a channel access procedure. UE 115-a may identify sidelink data 415 to be sent in a shared channel in a first FFP, and UE 115-a may monitor the shared channel in a second FFP for sidelink transmissions from UE 115-b. If UE 115-a detects a sidelink transmission from UE 115-b, UE 115-a may share the COT with UE 115-b. Otherwise, UE 115-a may initiate a channel access procedure to obtain access to the first FFP to send sidelink data 415 (e.g., to UE 115-c).

[0119] The first FFP may be an example of an FFP (e.g., FFP 420-a or FFP 420-b) configured for sidelink communication in a shared channel at UE 115-a. The second FFP may be an example of an FFP (e.g., FFP 420-a or FFP 420-b) configured for sidelink communication in a shared channel at UE 115-a or an FFP (e.g., FFP 425-a, FFP 425-b, or FFP 425-c) configured for sidelink communication in a shared channel at UE 115-b. In one example, if the first FFP corresponds to FFP 420-a, the second FFP may correspond to FFP 425-a, and UE 115-a may monitor the sidelink transmission from UE 115-b in FFP 425-a. In another example, if the first FFP corresponds to FFP 420-b, the second FFP may correspond to FFP 420-a, and UE 115-a may monitor sidelink transmissions from UE 115-b in FFP 420-a (e.g., in an idle period of FFP 420-a).

[0120] In some examples, UE 115-a may monitor a shared channel in a second FFP for sidelink traffic from UE 115-b (e.g., UE 115-a may monitor the FFP of UE 115-b). If UE 115-a detects sidelink traffic, UE 115-a may share the COT with UE 115-b. Otherwise, UE 115-a may initiate a channel access procedure to occupy a shared channel in a first FFP (e.g., the FFP of UE 115-a). Because UE 115-a may monitor a second FFP (e.g., the FFP of UE 115-b), it may be appropriate for UE 115-a to identify the FFP configuration (e.g., duration and starting point) of UE 115-b. In some cases, during an initial connection between UE 115-a and UE 115-b, UE 115-a and UE 115-b may exchange FFP configuration information with each other. In other cases, the wireless device 405 may indicate the FFP configuration of the UE 115-b to the UE 115-a. The UE 115-a may then use the FFP configuration of the UE 115-b to monitor the sidelink traffic from the UE 115-b in the second FFP.

[0121] In addition, UE 115-a determines that the UE 115 from which the sidelink traffic is detected may be appropriate. For example, after detecting the sidelink traffic, UE 115-a determines whether UE 115-b has sent the sidelink traffic in its own FFP or whether UE 115-b shares the COT with another UE 115. Using the techniques described herein, UE 115-b may add a bit to sidelink control information (SCI) (e.g., SCI-2) to indicate whether the sidelink traffic from UE 115-b is sent in its own FFP. UE 115-b may send the SCI to reserve resources to send the sidelink traffic, and UE 115-a may receive the SCI. If UE 115-a detects sidelink traffic from UE 115-b, and UE 115-a determines from the SCI that the sidelink traffic is sent in the FFP of UE 115-b, UE 115-a may share the COT with UE 115-b. Otherwise, if UE 115-a detects sidelink traffic from UE 115-b, but UE 115-a determines from the SCI that UE 115-b is sharing the COT, UE 115-a may avoid sharing the COT (e.g., because UE 115-a may not detect the sidelink traffic from UE 115 that initiated the COT).

[0122] In some examples, UE 115-a may monitor the shared channel in the second FFP for COT sharing information from UE 115-b (e.g., and other UEs 115). If UE 115-a detects COT sharing information, UE 115-a may share the COT with UE 115-b. Otherwise, UE 115-a may initiate a channel access procedure to occupy the shared channel in the first FFP (e.g., the FFP of UE 115-a).

[0123] Figure 5Examples of COT sharing 500 according to one or more aspects of the present disclosure are illustrated. In a first example 500-a, a UE 115-b may perform an LBT procedure 510 to gain access to a shared channel in a COT 505-a, and the LBT procedure 510 may be successful. Therefore, the UE 115-b may send a sidelink service 520 in the COT 505-a. The UE 115-a may detect the sidelink service 520 in the COT 505-a, and may determine to share the COT 505-a with the UE 115-b based on detecting the sidelink service 520. Therefore, the UE 115-a may send a sidelink transmission 525 in the COT 505-a. In a second example 500-b, the UE 115-b may perform an LBT procedure 510 to gain access to a shared channel in the COT 505-b, and the LBT procedure 510 may be successful. Thus, UE 115-b may send sidelink traffic 520 in COT 505-b. UE 115-b may also send COT sharing information 515 in COT 505-b. UE 115-a may detect COT sharing information 515 in COT 505-b and may determine to share COT 505-b with UE 115-b based on detecting COT sharing information 515. Thus, UE 115 may send sidelink transmission 525 in COT 505-b.

[0124] Figure 6 An example of initialization of a channel access procedure 600 according to one or more aspects of the present disclosure is illustrated. UE 115-b may execute LBT procedure 610 to obtain access to a shared channel in COT 605-a, but LBT procedure 610 may fail. Because LBT procedure 610 may fail, UE 115-a may fail to detect a sidelink transmission (e.g., sidelink traffic or COT sharing information) from UE 115-b. Therefore, UE 115-a may not be able to share the COT with UE 115-b. Alternatively, UE 115-a may execute LBT procedure 615 to obtain access to a shared channel in COT 605-b, and LBT procedure 615 may succeed. UE 115 may then send a sidelink transmission 620 in COT 605-b.

[0125] In some aspects, the wireless device 405 (e.g., the network entity 105 or the anchor side link node) may dynamically control whether the UE 115-a may initiate a channel access procedure to occupy a shared channel in the FFP (e.g., starting at the boundary of the FFP). Because the wireless device 405 may be able to identify the traffic patterns of the connected nodes (including the UE 115-a), the wireless device 405 may dynamically indicate which UEs 115 may initiate a channel access procedure to occupy a shared channel in the FFP based on the combined traffic patterns (e.g., at the UE 115) to maximize resource utilization and reduce conflicts (e.g., as much as possible).

[0126] In some examples, wireless device 405 may be network entity 105, and network entity 105 may indicate to UE 115-a whether to initiate a channel access procedure to occupy a shared channel in FFP (e.g., for resource allocation mode 1). Network entity 105 may add a bit field (e.g., a channel access field) to downlink control information (DCI) (e.g., DCI 3_0 or DCI 3_1) to notify sidelink devices including UE 115-a whether to initiate a channel access procedure in their own FFP for sidelink transmission. Table 3 shows an example of an indication that may be included in a DCI to indicate whether to initiate a channel access procedure.

[0127] Table 3: Indication included in DCI to indicate whether to initiate a channel access procedure

[0128] Maps to indexed bit fields Resources associated with sidelink transmission 0 Share COT with other UEs 1 Launch its own FFP

[0129] In other examples, the wireless device 405 may be the anchor UE 115, and the anchor UE 115 may indicate to the UE 115-a whether to initiate a channel access procedure to occupy a shared channel in the FFP.

[0130] In one aspect, anchor UE 115 may send a unicast transmission (e.g., in SCI-2) to UE 115-a to indicate whether UE 115-a is to initiate a channel access procedure to occupy a shared channel in an FFP. In some cases, the unicast transmission may include a single bit indicating whether UE 115-a is to initiate a channel access procedure to occupy a shared channel in a next upcoming FFP. The next upcoming FFP may refer to an FFP immediately after the time at which the unicast transmission is received at UE 115-a (e.g., an FFP that is subsequent to and adjacent to the FFP in which the unicast transmission is received). In other cases, the unicast transmission may include a time indicator indicating an FFP for which UE 115-a may initiate a channel access procedure to occupy a shared channel. For example, time indicator 1 may indicate that UE 115-a may initiate a channel access procedure to occupy a shared channel in the next upcoming FFP, time indicator 2 may indicate that UE 115 may initiate a channel access procedure to occupy a shared channel in the FFP immediately following the next upcoming FFP, and so on.

[0131] In another aspect, the anchor UE 115 may send a multicast transmission to the plurality of UEs 115 to indicate whether each UE 115 of the plurality of UEs 115 (eg, including UE 115-a) is to initiate a channel access procedure to occupy a shared channel in the FFP.

[0132] Figure 7 An example of a multicast transmission 700 indicating whether each UE 115 of a plurality of UEs 115 is to initiate a channel access procedure to occupy a shared channel in FFP in accordance with one or more aspects of the present disclosure is illustrated.

[0133] In the first example 700-a, the anchor UE 115 may add a bitmap to the SCI (e.g., SCI-2) to indicate which UE 115 is to initiate a channel access procedure in the FFP. The addition of the bitmap may be applicable to static deployments (e.g., where the number of UEs 115 connected to the anchor UE 115 is static). In some cases, each field in the bitmap may correspond to a UE 115 and may include a bit indicating whether the UE 115 is to initiate a channel access procedure to occupy a shared channel in the next upcoming FFP. The next upcoming FFP may refer to the FFP immediately after the time at which the bitmap is received (e.g., the FFP that is subsequent to and adjacent to the FFP in which the bitmap is received). In other cases, each field in the bitmap may correspond to a UE 115 and may include a time indicator indicating the FFP for which the UE 115 may initiate a channel access procedure to occupy a shared channel.

[0134] In a second example 700-b, the anchor UE 115 may add a field to the SCI (e.g., SCI-2) for each UE 115 of the plurality of UEs indicating whether the UE 115 is to initiate a channel access procedure in an FFP. The field for the UE 115 may include a user identifier (ID) identifying the UE 115 (e.g., a groupcast member ID) and a bit or a timing indicator for the UE 115. As described, the bit may indicate whether the UE 115 is to initiate a channel access procedure to occupy a shared channel in a next upcoming FFP, and the timing indicator may indicate an FFP for which the UE 115 may initiate a channel access procedure to occupy a shared channel.

[0135] Figure 8 An example of a process flow 800 for supporting sidelink communications using a fixed frame period according to one or more aspects of the present disclosure is illustrated. The process flow 800 includes a wireless device 805, which may be a reference Figures 1 to 7 The process flow 800 also includes UE 115-d and UE 115-e, which may be reference UEs 115-d and 115-e. Figures 1 to 7 An example of a UE 115 is described. The process flow 800 can implement aspects of the wireless communication system 100. For example, the process flow 800 can support efficient techniques for facilitating sidelink communications in a shared spectrum (eg, in a FBE system).

[0136] In the following description of process flow 800, the signaling exchanged between wireless device 805, UE 115-d, and UE 115-e may be exchanged in a different order than the example shown, or the operations performed by wireless device 805, UE 115-d, and UE 115-e may be performed in a different order or at a different time. Some operations may also be omitted from process flow 800, and other operations may be added to process flow 800.

[0137] UE 115-d may identify a configuration of timing of a frame structure for sidelink communications via a shared channel. The configuration of timing of a frame structure for sidelink communications via a shared channel may be referred to as an FFP configuration. A frame structure may include multiple frame periods (e.g., FFPs) having a fixed duration.

[0138] In some examples, at 810, the wireless device 805 may send and the UE 115-d may receive an indication of the configuration of the timing of the frame structure. The wireless device 805 may identify the timing of the frame structure for the sidelink communication via the shared channel at the UE 115-d based on the traffic pattern at the UE 115-d. If the wireless device 805 is a network entity 105, the network entity 105 may determine the traffic pattern at the UE 115-d based on the sidelink communication scheduled by the network entity 105 at the UE 115-d. If the wireless device 805 is an anchor UE 115, the anchor UE 115 may receive an indication of the traffic pattern at the UE 115-d from the network entity 105 or from the UE 115-d. In some other examples, the configuration of the timing of the frame structure may be preconfigured at the UE 115-d. In yet other examples, the UE 115-d may identify the configuration of the timing of the frame structure based on the traffic pattern at the UE 115-d.

[0139] At 815, the UE 115-d may identify sidelink data to be sent in a first frame period (e.g., a first FFP) of a plurality of frame periods having a fixed frame duration. The plurality of frame periods may be established for the UE 115-d to communicate via a shared channel (e.g., established in an FFP configuration). At 820, the UE 115-d may determine whether to initiate a channel access procedure to occupy the shared channel in the first frame period.

[0140] In one aspect, UE 115-d may monitor a shared channel for sidelink transmissions from another UE 115 during a second frame period (e.g., a second FFP) in the plurality of frame periods, and UE 115-d may determine based on the monitoring whether to initiate a channel access procedure to occupy the shared channel during the first frame period. The sidelink transmission from the other UE 115 may be a data transmission (e.g., a sidelink service) or a shared information transmission. In some cases, UE 115-d may receive an indication of the configuration of the second frame period, and UE 115-d may identify the starting boundary of the second frame period based on receiving the indication of the configuration of the second frame period. In this way, UE 115-d may be able to monitor the sidelink transmission from the other UE 115 based on identifying the starting boundary of the second frame period.

[0141] If UE 115-d detects a sidelink transmission, UE 115-d may determine to share the COT initiated by the other UE 115 including the second frame period, and UE 115-d may refrain from initiating a channel access procedure to occupy the shared channel during the first frame period. In some cases, the sidelink transmission may include an indication that the sidelink transmission is from the other UE 115. If UE 115-d fails to detect the sidelink transmission, UE 115-d may determine to initiate a channel access procedure to occupy the shared channel during the first frame period.

[0142] On the other hand, at 825, the wireless device 805 may send and the UE 115-d may receive an indication of whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupancy time initiated by another UE 115. The wireless device 805 may identify a traffic mode of the UE 115-d, and the wireless device 805 may determine whether the UE 115-d is to initiate a channel access procedure to occupy a shared channel during a first frame period based on the traffic mode of the UE 115-d. If the wireless device 805 is a network entity 105, the network entity 105 may identify the traffic mode of the UE 115-d based on a sidelink communication scheduled by the network entity 105 at the UE 115-d. If the wireless device is a UE 115, the UE 115 may receive an indication of the traffic mode at the UE 115-d from the UE 115-d or from the network entity 105.

[0143] In addition, if the wireless device 805 is the network entity 105, the network entity 105 may send and the UE 115-d may receive a DCI indicating whether to initiate a channel access procedure. If the wireless device 805 is the UE 115, the UE 115 may send and the UE 115-d may receive a multicast transmission or a unicast transmission indicating whether to initiate a channel access procedure. In some examples, the multicast transmission may include a bitmap, and a bit or time indicator for the UE 115-d in the bitmap may indicate whether the UE 115-d is to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a COT initiated by another UE 115. In some examples, the multicast transmission may include a field having an identifier of the UE 115-d and an indication of whether the UE 115-d is to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a COT initiated by another UE 115.

[0144] At 830, UE 115-d may send side link data to UE 115-e based on determining whether to initiate a channel access procedure to occupy the shared channel in the first frame period. For example, if UE 115-e determines to initiate a channel access procedure to occupy the shared channel in the first frame period, UE 115-e may send side link data in the first frame period if the channel access procedure is successful. If the channel access procedure is unsuccessful, UE 115-d may compete for access to the shared channel at a later time, and UE 115-d may send side link data in a subsequent or future frame period. Alternatively, if UE 115-e determines to share a COT initiated by another UE 115, UE 115-e may send side link data in a COT shared with another UE 115.

[0145] Fig. 9 A block diagram 900 of a device 905 supporting sidelink communications using a fixed frame period according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of a UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0146] The receiver 910 may 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 associated with sidelink communications using a fixed frame period). The information may be communicated to other components of the device 905. The receiver 910 may utilize a single antenna or a collection of multiple antennas.

[0147] The transmitter 915 may provide means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels associated with sidelink communications using a fixed frame period). In some examples, the transmitter 915 may be co-located with the receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0148] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of sidelink communications using a fixed frame period as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

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

[0150] Additionally or alternatively, in some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure).

[0151] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated in conjunction with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0152] The communication manager 920 may support wireless communication at the first UE according to the examples disclosed herein. For example, the communication manager 920 may be configured as or otherwise support a component for identifying the side link data to be sent in a first frame period of a set of multiple frame periods having a fixed frame duration established for communication by the first UE via a shared channel. The communication manager 920 may be configured as or otherwise support a component for determining whether to initiate a channel access procedure to occupy the shared channel in the first frame period. The communication manager 920 may be configured as or otherwise support a component for sending the side link data based on the determination.

[0153] Additionally or alternatively, the communication manager 920 may support wireless communications at a wireless device according to examples as disclosed herein. For example, the communication manager 920 may be configured as or otherwise support a component for identifying a respective business mode associated with a plurality of UEs. The communication manager 920 may be configured as or otherwise support a component for determining, based on the respective business modes associated with the plurality of UEs, whether each of the plurality of UEs is to initiate a channel access procedure to occupy a shared channel during a first frame period in a set of a plurality of frame periods having a fixed frame duration established for communicating with the plurality of UEs. The communication manager 920 may be configured as or otherwise support a component for sending, based on the determination, to each UE an indication of whether to initiate a channel access procedure to occupy a shared channel during the first frame period.

[0154] Additionally or alternatively, the communication manager 920 may support wireless communication at the first UE according to the examples disclosed herein. For example, the communication manager 920 may be configured as or otherwise support a means for identifying, at the first UE, a configuration of a timing of a frame structure for sidelink communication via a shared channel, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration. The communication manager 920 may be configured as or otherwise support a means for communicating during one or more frame periods of the set of multiple frame periods of the frame structure according to the configuration.

[0155] Additionally or alternatively, the communication manager 920 may support wireless communications at the wireless device according to examples as disclosed herein. For example, the communication manager 920 may be configured as or otherwise support means for identifying a timing of a frame structure for sidelink communications via a shared channel at the first UE based on a traffic pattern associated with the first UE, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration. The communication manager 920 may be configured as or otherwise support means for sending an indication of the configuration of the timing of the frame structure to the first UE.

[0156] By including or configuring the communication manager 920 according to the examples as described herein, the device 905 (e.g., a processor controlling or otherwise coupled to the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof) can support techniques for reduced processing and reduced power consumption. Specifically, because the device 905 can prioritize COT sharing or can be configured as to whether to initiate a channel access procedure or share the COT, the device 905 can more efficiently contend for access to a shared channel and can avoid unnecessary execution of channel access procedures. Therefore, less time and processing resources can be wasted at the device 905 on the channel access procedure, and the device 905 can achieve reduced processing and reduced power consumption.

[0157] Fig.10 A block diagram 1000 of a device 1005 supporting sidelink communications using a fixed frame period according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or UE 115 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0158] The receiver 1010 may 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 associated with sidelink communications using a fixed frame period). The information may be communicated to other components of the device 1005. The receiver 1010 may utilize a single antenna or a collection of multiple antennas.

[0159] The transmitter 1015 may provide means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels associated with sidelink communications using a fixed frame period). In some examples, the transmitter 1015 may be co-located with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0160] Device 1005 or its various components may be examples of components for performing various aspects of sidelink communications using a fixed frame period as described herein. For example, communication manager 1020 may include sidelink data manager 1025, channel access manager 1030, service manager 1035, frame manager 1040, or any combination thereof. Communication manager 1020 may be an example of various aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or integrate with receiver 1010, transmitter 1015, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0161] The communication manager 1020 may support wireless communication at the first UE according to the examples disclosed herein. The sidelink data manager 1025 may be configured as or otherwise support a component for identifying sidelink data to be sent in a first frame period of a set of multiple frame periods having a fixed frame duration established for communication by the first UE via a shared channel. The channel access manager 1030 may be configured as or otherwise support a component for determining whether to initiate a channel access procedure to occupy the shared channel in the first frame period. The sidelink data manager 1025 may be configured as or otherwise support a component for sending the sidelink data based on the determination.

[0162] Additionally or alternatively, the communication manager 1020 may support wireless communication at a wireless device according to examples as disclosed herein. The communication manager 1035 may be configured as or otherwise support a component for identifying a respective business mode associated with a plurality of UEs. The channel access manager 1030 may be configured as or otherwise support a component for determining, based on the respective business modes associated with the plurality of UEs, whether each of the plurality of UEs is to initiate a channel access procedure to occupy a shared channel during a first frame period in a group of a plurality of frame periods having a fixed frame duration established for communicating with the group of the plurality of UEs. The channel access manager 1030 may be configured as or otherwise support a component for sending, based on the determination, to each UE an indication of whether to initiate a channel access procedure to occupy a shared channel during the first frame period.

[0163] Additionally or alternatively, the communication manager 1020 may support wireless communications at the first UE according to examples as disclosed herein. The frame manager 1040 may be configured as or otherwise support a means for identifying, at the first UE, a configuration of a timing of a frame structure for sidelink communications via a shared channel, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration. The sidelink data manager 1025 may be configured as or otherwise support a means for communicating during one or more frame periods of the set of multiple frame periods of the frame structure according to the configuration.

[0164] Additionally or alternatively, the communication manager 1020 may support wireless communications at a wireless device according to examples as disclosed herein. The frame manager 1040 may be configured as or otherwise support means for identifying a timing of a frame structure for sidelink communications via a shared channel at the first UE based on a traffic pattern associated with the first UE, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration. The communication manager 1040 may be configured as or otherwise support means for sending an indication of the configuration of the timing of the frame structure to the first UE.

[0165] Fig.11 A block diagram 1100 of a communication manager 1120 supporting sidelink communications using a fixed frame period according to one or more aspects of the present disclosure is shown. The communication manager 1120 may be an example of a communication manager 920, a communication manager 1020, or aspects of both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of sidelink communications using a fixed frame period as described herein. For example, the communication manager 1120 may include a sidelink data manager 1125, a channel access manager 1130, a traffic manager 1135, a frame manager 1140, a COT sharing manager 1145, a channel access initiator 1150, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0166] The communication manager 1120 may support wireless communication at the first UE according to the examples disclosed herein. The sidelink data manager 1125 may be configured as or otherwise support a component for identifying the sidelink data to be sent in a first frame period in a set of multiple frame periods having a fixed frame duration established for communication by the first UE via a shared channel. The channel access manager 1130 may be configured as or otherwise support a component for determining whether to initiate a channel access procedure to occupy a shared channel in the first frame period. In some examples, the sidelink data manager 1125 may be configured as or otherwise support a component for sending the sidelink data based on the determination.

[0167] In some examples, the COT sharing manager 1145 may be configured as or otherwise support a component for monitoring a shared channel during a second frame period in the group of multiple frame periods for sidelink transmissions from a second UE, wherein a determination of whether to initiate a channel access procedure to occupy the shared channel during the first frame period is based on the monitoring.

[0168] In some examples, to support determining whether to initiate a channel access procedure to occupy a shared channel during a first frame period, the COT sharing manager 1145 may be configured as or otherwise support a component for detecting a sidelink transmission from a second UE based on the monitoring. In some examples, to support determining whether to initiate a channel access procedure to occupy a shared channel during a first frame period, the COT sharing manager 1145 may be configured as or otherwise support a component for determining, based on detecting the sidelink transmission, that sharing of a channel occupancy time including a second frame period initiated by the second UE. In some examples, to support determining whether to initiate a channel access procedure to occupy a shared channel during a first frame period, the channel access initiator 1150 may be configured as or otherwise support a component for suppressing initiation of a channel access procedure to occupy a shared channel during the first frame period based on determining that sharing of a channel occupancy time initiated by the second UE.

[0169] In some examples, the COT sharing manager 1145 may be configured as or otherwise support means for receiving an indication in the sidelink transmission that the sidelink transmission is from a second UE, wherein detecting the sidelink transmission from the second UE is based on receiving the indication.

[0170] In some examples, to support determining whether to initiate a channel access procedure to occupy a shared channel during a first frame period, channel access initiator 1150 may be configured as or otherwise support a component for determining to initiate a channel access procedure to occupy a shared channel during a first frame period based on a failure to detect a sidelink transmission from a second UE.

[0171] In some examples, frame manager 1140 may be configured as or otherwise support means for receiving an indication of configuration of a second frame period from a network entity, a second UE, or a third UE. In some examples, frame manager 1140 may be configured as or otherwise support means for identifying a starting boundary of the second frame period based on receiving an indication of configuration of the second frame period, wherein monitoring sidelink transmissions from the second UE is based on identifying the starting boundary of the second frame period.

[0172] In some examples, the sidelink transmission from the second UE includes data transmission or shared information transmission.

[0173] In some examples, channel access manager 1130 may be configured as or otherwise support a component for receiving an indication in downlink control information from a network entity whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupancy time initiated by a second UE.

[0174] In some examples, channel access manager 1130 may be configured as or otherwise support a component for receiving an indication in a multicast transmission from a second UE whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupancy time initiated by a third UE.

[0175] In some examples, the multicast transmission includes a bitmap, and a bit or time indicator for the first UE in the bitmap indicates whether the first UE is to initiate a channel access procedure to occupy a shared channel during a first frame period or share a channel occupation time initiated by a third UE.

[0176] In some examples, the multicast transmission includes a field including an identifier of the first UE and an indication of whether the first UE is to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupation time initiated by a third UE.

[0177] In some examples, channel access manager 1130 may be configured as or otherwise support means for receiving an indication in a unicast transmission from a second UE whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupancy time initiated by the second UE.

[0178] Additionally or alternatively, the communication manager 1120 may support wireless communication at a wireless device according to examples as disclosed herein. The communication manager 1135 may be configured as or otherwise support a component for identifying a corresponding business mode associated with a plurality of UEs. In some examples, the channel access manager 1130 may be configured as or otherwise support a component for determining, based on the corresponding business modes associated with the plurality of UEs, whether each of the plurality of UEs is to initiate a channel access procedure to occupy a shared channel during a first frame period in a set of a plurality of frame periods having a fixed frame duration established for communicating with the plurality of UEs. In some examples, the channel access manager 1130 may be configured as or otherwise support a component for sending an indication to each UE of whether to initiate a channel access procedure to occupy a shared channel during the first frame period based on the determination.

[0179] In some examples, to support sending an indication of whether to initiate a channel access procedure to occupy a shared channel during a first frame period, the channel access manager 1130 may be configured as or otherwise support a component for sending an indication in downlink control information of whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupancy time initiated by another UE.

[0180] In some examples, to support sending an indication of whether to initiate a channel access procedure to occupy a shared channel during a first frame period, the channel access manager 1130 may be configured as or otherwise support a component for sending an indication in a multicast transmission of whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupancy time initiated by another UE.

[0181] In some examples, the multicast transmission includes a bitmap, and each bit in the bitmap indicates whether the corresponding UE is to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupation time initiated by another UE.

[0182] In some examples, the multicast transmission includes a bitmap, and a time indicator in the bitmap indicates whether the corresponding UE is to initiate a channel access procedure to occupy a shared channel during each of one or more frame periods including a first frame period or to share a channel occupancy time initiated by other UEs.

[0183] In some examples, the multicast transmission includes a field including an identifier for each UE and an indication to each UE whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share channel occupancy time with another UE.

[0184] In some examples, to support sending an indication of whether to initiate a channel access procedure to occupy a shared channel during a first frame period, the channel access manager 1130 may be configured as or otherwise support a component for sending an indication to each UE in a unicast transmission as to whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupancy time initiated by another UE.

[0185] Additionally or alternatively, the communication manager 1120 may support wireless communications at the first UE according to examples as disclosed herein. The frame manager 1140 may be configured as or otherwise support a means for identifying, at the first UE, a configuration of a timing of a frame structure for sidelink communications via a shared channel, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration. In some examples, the sidelink data manager 1125 may be configured as or otherwise support a means for communicating during one or more frame periods of the set of multiple frame periods of the frame structure according to the configuration.

[0186] In some examples, to support identifying the configuration of the timing of the frame structure, frame manager 1140 may be configured as or otherwise support means for receiving an indication of the configuration of the timing of the frame structure from a network entity or a second UE.

[0187] In some examples, the configuration of the timing of the frame structure is preconfigured at the first UE.

[0188] In some examples, frame manager 1140 may be configured as or otherwise support means for identifying the configuration of the timing of the frame structure based on a traffic pattern at the first UE.

[0189] Additionally or alternatively, the communication manager 1120 may support wireless communications at the wireless device according to examples as disclosed herein. In some examples, the frame manager 1140 may be configured as or otherwise support means for identifying a timing of a frame structure for sidelink communications via a shared channel at the first UE based on a traffic pattern associated with the first UE, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration. In some examples, the frame manager 1140 may be configured as or otherwise support means for sending an indication of the configuration of the timing of the frame structure to the first UE.

[0190] In some examples, the wireless device includes a network entity, and the traffic manager 1135 may be configured as or otherwise support means for determining a traffic mode associated with the first UE based on sidelink communications scheduled by the network entity at the first UE.

[0191] In some examples, the wireless device includes a second UE, and the traffic manager 1135 may be configured as or otherwise support means for receiving an indication of a traffic pattern at the first UE from a network entity or from the first UE.

[0192] In some examples, the wireless device includes a second UE, and the second UE includes an anchor UE that is preconfigured, configured via signaling from a network entity, or selected by one or more UEs including the first UE.

[0193] Fig.12A diagram of a system 1200 including a device 1205 supporting sidelink communications using a fixed frame period according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a UE 115 as described herein or include a component of these devices. The device 1205 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1205 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1220, an input / output (I / O) controller 1210, a transceiver 1215, an antenna 1225, a memory 1230, a code 1235, and a processor 1240. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1245).

[0194] I / O controller 1210 can manage input and output signals for device 1205. I / O controller 1210 can also manage peripheral devices that are not integrated into device 1205. In some cases, I / O controller 1210 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1210 can utilize an operating system such as or another known operating system. Additionally or alternatively, I / O controller 1210 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1210 may be implemented as part of a processor (such as processor 1240). In some cases, a user may interact with device 1205 via I / O controller 1210 or via hardware components controlled by I / O controller 1210.

[0195] In some cases, the device 1205 may include a single antenna 1225. However, in some other cases, the device 1205 may have more than one antenna 1225, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. As described herein, the transceiver 1215 may communicate bidirectionally via one or more antennas 1225, a wired or wireless link. For example, the transceiver 1215 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1215 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 1225 for transmission, and demodulating packets received from one or more antennas 1225. The transceiver 1215 or the transceiver 1215 and the one or more antennas 1225 may be examples of the transmitter 915, the transmitter 1015, the receiver 910, the receiver 1010, or any combination thereof or any component thereof as described herein.

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

[0197] Processor 1240 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1240 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1240. Processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1230) to cause device 1205 to perform various functions (e.g., functions or tasks that support side link communications using a fixed frame period). For example, device 1205 or a component of device 1205 may include processor 1240 and memory 1230 coupled to or coupled to processor 1240, and processor 1240 and memory 1230 are configured to perform various functions described herein.

[0198] The communication manager 1220 may support wireless communication at the first UE according to the examples disclosed herein. For example, the communication manager 1220 may be configured as or otherwise support a component for identifying the side link data to be sent in a first frame period of a set of multiple frame periods having a fixed frame duration established for communication by the first UE via a shared channel. The communication manager 1220 may be configured as or otherwise support a component for determining whether to initiate a channel access procedure to occupy the shared channel in the first frame period. The communication manager 1220 may be configured as or otherwise support a component for sending the side link data based on the determination.

[0199] Additionally or alternatively, the communication manager 1220 may support wireless communications at a wireless device according to examples as disclosed herein. For example, the communication manager 1220 may be configured as or otherwise support a component for identifying a respective business mode associated with a plurality of UEs. The communication manager 1220 may be configured as or otherwise support a component for determining, based on the respective business modes associated with the plurality of UEs, whether each of the plurality of UEs is to initiate a channel access procedure to occupy a shared channel during a first frame period in a set of a plurality of frame periods having a fixed frame duration established for communicating with the plurality of UEs. The communication manager 1220 may be configured as or otherwise support a component for sending, based on the determination, to each UE an indication of whether to initiate a channel access procedure to occupy a shared channel during the first frame period.

[0200] Additionally or alternatively, the communication manager 1220 may support wireless communication at the first UE according to the examples disclosed herein. For example, the communication manager 1220 may be configured as or otherwise support a means for identifying, at the first UE, a configuration of a timing of a frame structure for sidelink communication via a shared channel, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration. The communication manager 1220 may be configured as or otherwise support a means for communicating during one or more frame periods of the set of multiple frame periods of the frame structure according to the configuration.

[0201] Additionally or alternatively, the communication manager 1220 may support wireless communications at the wireless device according to examples as disclosed herein. For example, the communication manager 1220 may be configured as or otherwise support means for identifying a timing of a frame structure for sidelink communications via a shared channel at the first UE based on a traffic pattern associated with the first UE, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration. The communication manager 1220 may be configured as or otherwise support means for sending an indication of the configuration of the timing of the frame structure to the first UE.

[0202] By including or configuring the communication manager 1220 according to the examples described herein, the device 1205 can support techniques for reducing processing and reducing power consumption. Specifically, because the device 1205 can prioritize COT sharing or can be configured to whether to initiate a channel access procedure or share the COT, the device 1205 can more efficiently compete for access to the shared channel and can avoid unnecessary execution of channel access procedures. Therefore, less time and processing resources can be wasted at the device 905 on the channel access procedure, and the device 1205 can achieve reduced processing and reduced power consumption.

[0203] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1215, one or more antennas 1225, or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the processor 1240, the memory 1230, the code 1235, or any combination thereof. For example, the code 1235 may include instructions that are executable by the processor 1240 to cause the device 1205 to perform various aspects of sidelink communications using a fixed frame period as described herein, or the processor 1240 and the memory 1230 may be otherwise configured to perform or support such operations.

[0204] Fig.13 A block diagram 1300 of a device 1305 supporting sidelink communications using a fixed frame period according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of aspects of the network entity 105 as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0205] Receiver 1310 may 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 may be communicated to other components of device 1305. In some examples, receiver 1310 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1310 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0206] The transmitter 1315 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1305. For example, the transmitter 1315 may 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 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1315 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1315 and the receiver 1310 may be co-located in a transceiver, which may include or be coupled to a modem.

[0207] The communication manager 1320, the receiver 1310, the transmitter 1315, or various combinations thereof or various components thereof may be examples of means for performing various aspects of sidelink communications using a fixed frame period as described herein. For example, the communication manager 1320, the receiver 1310, the transmitter 1315, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

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

[0209] Additionally or alternatively, in some examples, the communication manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure).

[0210] In some examples, communication manager 1320 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1310, transmitter 1315, or both. For example, communication manager 1320 may receive information from receiver 1310, transmit information to transmitter 1315, or be integrated in conjunction with receiver 1310, transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.

[0211] The communication manager 1320 may support wireless communication at a wireless device according to examples as disclosed herein. For example, the communication manager 1320 may be configured as or otherwise support a component for identifying a respective business mode associated with a plurality of UEs. The communication manager 1320 may be configured as or otherwise support a component for determining, based on the respective business modes associated with the plurality of UEs, whether each of the plurality of UEs is to initiate a channel access procedure to occupy a shared channel during a first frame period in a set of a plurality of frame periods having a fixed frame duration established for communication with the plurality of UEs. The communication manager 1320 may be configured as or otherwise support a component for sending, based on the determination, to each UE an indication of whether to initiate a channel access procedure to occupy a shared channel during the first frame period.

[0212] Additionally or alternatively, the communication manager 1320 may support wireless communications at the wireless device according to examples as disclosed herein. For example, the communication manager 1320 may be configured as or otherwise support means for identifying a timing of a frame structure for sidelink communications via a shared channel at the first UE based on a traffic pattern associated with the first UE, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration. The communication manager 1320 may be configured as or otherwise support means for sending an indication of the configuration of the timing of the frame structure to the first UE.

[0213] By including or configuring the communication manager 1320 according to the examples described herein, the device 1305 (e.g., a processor that controls or otherwise couples with the receiver 1310, the transmitter 1315, the communication manager 1320, or a combination thereof) can support techniques for more efficiently utilizing communication resources. Specifically, because the device 1305 can signal the FFP configuration to the UE and can configure the UE whether to initiate a channel access procedure or share the COT, the device 1305 can improve resource utilization at the UE. Therefore, the device 1305 can have access to more resources for communicating with the UE or other UEs, and the device 1305 can achieve more efficient utilization of communication resources.

[0214] Fig.14 A block diagram 1400 of a device 1405 supporting sidelink communications using a fixed frame period according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of aspects of the device 1305 or the network entity 105 as described herein. The device 1405 may include a receiver 1410, a transmitter 1415, and a communication manager 1420. The device 1405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0215] Receiver 1410 may 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 may be communicated to other components of device 1405. In some examples, receiver 1410 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1410 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0216] The transmitter 1415 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1405. For example, the transmitter 1415 may 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 1415 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1415 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1415 and the receiver 1410 may be co-located in a transceiver, which may include a modem or be coupled to the modem.

[0217] Device 1405 or its various components may be examples of components for performing various aspects of sidelink communications using a fixed frame period as described herein. For example, communication manager 1420 may include service manager 1425, channel access manager 1430, frame manager 1435, or any combination thereof. Communication manager 1420 may be an example of various aspects of communication manager 1320 as described herein. In some examples, communication manager 1420 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1410, transmitter 1415, or both. For example, communication manager 1420 may receive information from receiver 1410, transmit information to transmitter 1415, or integrate with receiver 1410, transmitter 1415, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0218] The communication manager 1420 may support wireless communication at a wireless device according to the examples disclosed herein. The communication manager 1425 may be configured as or otherwise support a component for identifying a respective business mode associated with a plurality of UEs. The channel access manager 1430 may be configured as or otherwise support a component for determining, based on the respective business modes associated with the plurality of UEs, whether each of the plurality of UEs is to initiate a channel access procedure to occupy a shared channel during a first frame period in a set of a plurality of frame periods having a fixed frame duration established for communication with the plurality of UEs. The channel access manager 1430 may be configured as or otherwise support a component for sending, based on the determination, to each UE an indication of whether to initiate a channel access procedure to occupy a shared channel during the first frame period.

[0219] Additionally or alternatively, the communication manager 1420 may support wireless communications at the wireless device according to examples as disclosed herein. The frame manager 1435 may be configured as or otherwise support means for identifying a timing of a frame structure for sidelink communications via a shared channel at the first UE based on a traffic pattern at the first UE, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration. The communication manager 1435 may be configured as or otherwise support means for sending an indication of the configuration of the timing of the frame structure to the first UE.

[0220] Fig.15A block diagram 1500 of a communication manager 1520 supporting sidelink communication using a fixed frame period according to one or more aspects of the present disclosure is shown. The communication manager 1520 may be an example of a communication manager 1320, a communication manager 1420, or aspects of both as described herein. The communication manager 1520 or its various components may be examples of components for performing various aspects of sidelink communication using a fixed frame period as described herein. For example, the communication manager 1520 may include a service manager 1525, a channel access manager 1530, a frame manager 1535, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0221] The communication manager 1520 may support wireless communication at a wireless device according to examples as disclosed herein. The communication manager 1525 may be configured as or otherwise support a component for identifying a corresponding business mode associated with a plurality of UEs. The channel access manager 1530 may be configured as or otherwise support a component for determining, based on the corresponding business modes associated with the plurality of UEs, whether each of the plurality of UEs is to initiate a channel access procedure to occupy a shared channel during a first frame period in a set of a plurality of frame periods having a fixed frame duration established for communication with the plurality of UEs. In some examples, the channel access manager 1530 may be configured as or otherwise support a component for sending an indication to each UE of whether to initiate a channel access procedure to occupy a shared channel during the first frame period based on the determination.

[0222] In some examples, to support sending an indication of whether to initiate a channel access procedure to occupy a shared channel during a first frame period, the channel access manager 1530 may be configured as or otherwise support a component for sending an indication in downlink control information of whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupancy time initiated by another UE.

[0223] In some examples, to support sending an indication of whether to initiate a channel access procedure to occupy a shared channel during a first frame period, the channel access manager 1530 may be configured as or otherwise support a component for sending an indication in a multicast transmission of whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupancy time initiated by another UE.

[0224] In some examples, the multicast transmission includes a bitmap, and each bit in the bitmap indicates whether the corresponding UE is to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupation time initiated by another UE.

[0225] In some examples, the multicast transmission includes a bitmap, and a time indicator in the bitmap indicates whether the corresponding UE is to initiate a channel access procedure to occupy a shared channel during each frame period of one or more frame periods including a first frame period or to share a channel occupancy time initiated by other UEs.

[0226] In some examples, the multicast transmission includes a field including an identifier for each UE and an indication to each UE whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share channel occupancy time with another UE.

[0227] In some examples, to support sending an indication of whether to initiate a channel access procedure to occupy a shared channel during a first frame period, the channel access manager 1530 may be configured as or otherwise support a component for sending an indication to each UE in a unicast transmission as to whether to initiate a channel access procedure to occupy a shared channel during a first frame period or to share a channel occupancy time initiated by another UE.

[0228] Additionally or alternatively, the communication manager 1520 may support wireless communications at the wireless device according to examples as disclosed herein. The frame manager 1535 may be configured as or otherwise support means for identifying a timing of a frame structure for sidelink communications via a shared channel at the first UE based on a traffic pattern associated with the first UE, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration. In some examples, the frame manager 1535 may be configured as or otherwise support means for sending an indication of the configuration of the timing of the frame structure to the first UE.

[0229] In some examples, the wireless device includes a network entity, and the traffic manager 1525 may be configured as or otherwise support means for determining a traffic mode at the first UE based on sidelink communications scheduled by the network entity at the first UE.

[0230] In some examples, the wireless device includes a second UE, and the traffic manager 1525 may be configured as or otherwise support means for receiving an indication of a traffic pattern at the first UE from a network entity or from the first UE.

[0231] In some examples, the wireless device includes a second UE, and the second UE includes an anchor UE that is preconfigured, configured via signaling from a network entity, or selected by one or more UEs including the first UE.

[0232] Fig.16 A diagram of a system 1600 including a device 1605 supporting sidelink communications using a fixed frame period according to one or more aspects of the present disclosure is shown. The device 1605 may be an example of a device 1305, a device 1405, or a network entity 105 as described herein, or include components thereof. The device 1605 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1605 may include components that support output and acquisition of communications, such as a communication manager 1620, a transceiver 1610, an antenna 1615, a memory 1625, a code 1630, and a processor 1635. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1640).

[0233] As described herein, the transceiver 1610 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, the transceiver 1610 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1610 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1605 may include one or more antennas 1615, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1610 may also include a modem for: modulating a signal, providing the modulated signal for transmission (e.g., via one or more antennas 1615, via a wired transmitter), receiving the modulated signal (e.g., from one or more antennas 1615, from a wired receiver), and demodulating the signal. Where applicable, transceiver 1610 or transceiver 1610 and one or more antennas 1615 or wired interfaces may be examples of transmitter 1315, transmitter 1415, receiver 1310, receiver 1410, or any combination thereof or any components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0234] Memory 1625 may include RAM and ROM. Memory 1625 may store computer-readable, computer-executable code 1630 including instructions that, when executed by processor 1635, cause device 1605 to perform various functions described herein. Code 1630 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1630 may not be directly executable by processor 1635, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, memory 1625 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0235] Processor 1635 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, processor 1635 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1635. Processor 1635 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1625) to cause device 1605 to perform various functions (e.g., functions or tasks that support side link communications using a fixed frame period). For example, device 1605 or a component of device 1605 may include processor 1635 and memory 1625 coupled to processor 1635, the processor 1635 and memory 1625 being configured to perform the various functions described herein. Processor 1635 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 functionality (e.g., by executing code 1630) to perform the functions of device 1605.

[0236] In some examples, bus 1640 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1640 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1605 or between different components of device 1605 that may be co-located or located in different locations (e.g., where device 1605 may refer to a system in which one or more of communication manager 1620, transceiver 1610, memory 1625, code 1630, and processor 1635 may be located in one of the different components or divided between the different components).

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

[0238] The communication manager 1620 may support wireless communication at a wireless device according to examples as disclosed herein. For example, the communication manager 1620 may be configured as or otherwise support a component for identifying a respective business mode associated with a plurality of UEs. The communication manager 1620 may be configured as or otherwise support a component for determining, based on the respective business modes associated with the plurality of UEs, whether each of the plurality of UEs is to initiate a channel access procedure to occupy a shared channel during a first frame period in a set of a plurality of frame periods having a fixed frame duration established for communication with the plurality of UEs. The communication manager 1620 may be configured as or otherwise support a component for sending, based on the determination, to each UE an indication of whether to initiate a channel access procedure to occupy a shared channel during the first frame period.

[0239] Additionally or alternatively, the communication manager 1620 may support wireless communications at the wireless device according to examples as disclosed herein. For example, the communication manager 1620 may be configured as or otherwise support means for identifying a timing of a frame structure for sidelink communications via a shared channel at the first UE based on a traffic pattern associated with the first UE, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration. The communication manager 1620 may be configured as or otherwise support means for sending an indication of the configuration of the timing of the frame structure to the first UE.

[0240] By including or configuring the communication manager 1620 according to the examples described herein, the device 1605 can support techniques for more efficient use of communication resources. Specifically, because the device 1605 can signal the FFP configuration to the UE and can configure the UE whether to initiate a channel access procedure or share the COT, the device 1605 can improve resource utilization at the UE. Therefore, the device 1605 can have access to more resources for communicating with the UE or other UEs, and the device 1605 can achieve more efficient use of communication resources.

[0241] In some examples, the communication manager 1620 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1610, one or more antennas 1615 (where applicable), or any combination thereof. Although the communication manager 1620 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1620 may be supported or performed by the processor 1635, the memory 1625, the code 1630, the transceiver 1610, or any combination thereof. For example, the code 1630 may include instructions that are executable by the processor 1635 to cause the device 1605 to perform various aspects of sidelink communications using a fixed frame period as described herein, or the processor 1635 and the memory 1625 may be otherwise configured to perform or support such operations.

[0242] Fig.17 1700 for supporting sidelink communications using a fixed frame period according to one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or a component thereof as described herein. Figures 1 to 12 The UE 115 may be used to perform the functions. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions.

[0243] At 1705, the method may include identifying sidelink data to be sent in a first frame period of a set of a plurality of frame periods having a fixed frame duration established for communication by the first UE via a shared channel. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.11 The described side link data manager 1125 is executed.

[0244] At 1710, the method may include determining whether to initiate a channel access procedure to occupy a shared channel within a first frame period. The operations of 1710 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.11 The described channel access manager 1130 is executed.

[0245] At 1715, the method may include sending the sidelink data based on the determination. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig.11 The described side link data manager 1125 is executed.

[0246] Fig.18A flow chart of a method 1800 for supporting sidelink communication using a fixed frame period according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a UE or a network entity or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a UE or a network entity or a component thereof as described herein. Figures 1 to 12 UE 115 as described or as referenced Figures 1 to 8 and Figures 13 to 16 In some examples, the UE or network entity may execute an instruction set to control the functional elements of the UE or network entity to perform the described functions. Additionally or alternatively, the UE or network entity may use dedicated hardware to perform various aspects of the described functions.

[0247] At 1805, the method may include identifying a traffic pattern at each UE in a group of multiple UEs. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.11 and Fig.15 The described business manager 1135 or business manager 1525 is executed.

[0248] At 1810, the method may include determining, based on a respective traffic pattern at each UE, whether each UE is to initiate a channel access procedure to occupy a shared channel during a first frame period in a set of a plurality of frame periods having a fixed frame duration established for communication with the set of a plurality of UEs. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.11 and Fig.15 The described channel access manager 1130 or channel access manager 1530 is executed.

[0249] At 1815, the method may include sending, based on the determination, to each UE an indication of whether to initiate a channel access procedure to occupy the shared channel during the first frame period. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Fig.11 and Fig.15 The described channel access manager 1130 or channel access manager 1530 is executed.

[0250] Fig.19 1 is a flow chart showing a method 1900 for supporting sidelink communication using a fixed frame period according to one or more aspects of the present disclosure. The operations of the method 1900 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a UE or a component thereof as described herein. Figures 1 to 12The UE 115 may be used to perform the functions. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions.

[0251] At 1905, the method may include identifying, at the first UE, a configuration of a timing of a frame structure for sidelink communication via a shared channel, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Fig.11 The frame manager 1140 is used to execute.

[0252] At 1910, the method may include communicating during one or more frame periods of the set of multiple frame periods of the frame structure according to the configuration. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference to Fig.11 The described side link data manager 1125 is executed.

[0253] Fig. 20 A flow chart of a method 2000 for supporting sidelink communication using a fixed frame period according to one or more aspects of the present disclosure is shown. The operations of the method 2000 may be implemented by a UE or a network entity or a component thereof as described herein. For example, the operations of the method 2000 may be implemented by a UE or a network entity or a component thereof as described herein. Figures 1 to 12 UE 115 as described or as referenced Figures 1 to 8 and Figures 13 to 16 In some examples, the UE or network entity may execute an instruction set to control the functional elements of the UE or network entity to perform the described functions. Additionally or alternatively, the UE or network entity may use dedicated hardware to perform various aspects of the described functions.

[0254] At 2005, the method may include identifying timing of a frame structure for sidelink communication via a shared channel at the first UE based on a traffic pattern at the first UE, wherein the frame structure includes a set of multiple frame periods with a fixed frame duration. The operations of 2005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed as described in reference to Fig.11 and Fig.15 The described frame manager 1140 or frame manager 1535 is performed.

[0255] At 2010, the method may include sending an indication of the configuration of the timing of the frame structure to the first UE. The operations of 2010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed as described in reference to Fig.11 and Fig.15 The described frame manager 1140 or frame manager 1535 is performed.

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

[0257] Aspect 1: A method for wireless communication at a first UE, the method comprising: identifying sidelink data to be sent in a first frame period of multiple frame periods having a fixed frame duration established for communication by the first UE via a shared channel; determining whether to initiate a channel access procedure to occupy the shared channel within the first frame period; and sending the sidelink data based at least in part on the determination.

[0258] Aspect 2: According to the method described in Aspect 1, the method also includes: monitoring the shared channel during a second frame period among the multiple frame periods for a side link transmission from a second UE, wherein determining whether to initiate the channel access procedure to occupy the shared channel during the first frame period is at least partially based on the monitoring.

[0259] Aspect 3: A method according to Aspect 2, wherein determining whether to initiate the channel access procedure to occupy the shared channel during the first frame period includes: detecting the sidelink transmission from the second UE based at least in part on the monitoring; determining the shared channel occupancy time including the second frame period initiated by the second UE based at least in part on detecting the sidelink transmission; and suppressing initiating the channel access procedure to occupy the shared channel during the first frame period based at least in part on determining the shared channel occupancy time initiated by the second UE.

[0260] Aspect 4: According to the method according to Aspect 3, the method also includes: receiving an indication in the sidelink transmission that the sidelink transmission is from the second UE, wherein detecting the sidelink transmission from the second UE is at least partially based on receiving the indication.

[0261] Aspect 5: A method according to any one of Aspects 2 to 4, wherein determining whether to initiate the channel access procedure to occupy the shared channel during the first frame period includes: determining to initiate the channel access procedure to occupy the shared channel during the first frame period based at least in part on a failure to detect the sidelink transmission from the second UE.

[0262] Aspect 6: According to the method described in any one of Aspects 2 to 5, the method also includes: receiving an indication of the configuration of the second frame period from a network entity, the second UE or a third UE; and identifying the starting boundary of the second frame period based at least in part on receiving the indication of the configuration of the second frame period, wherein monitoring the sidelink transmission from the second UE is based at least in part on identifying the starting boundary of the second frame period.

[0263] Aspect 7: The method according to any one of Aspects 2 to 6, wherein the sidelink transmission from the second UE includes data transmission or shared information transmission.

[0264] Aspect 8: According to the method described in any one of Aspects 1 to 7, the method further includes: receiving an indication in downlink control information from a network entity as to whether to initiate the channel access procedure to occupy the shared channel during the first frame period or to share the channel occupancy time initiated by the second UE.

[0265] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method further includes: receiving an indication in a multicast transmission from a second UE as to whether to initiate the channel access procedure to occupy the shared channel during the first frame period or to share the channel occupancy time initiated by a third UE.

[0266] Aspect 10: A method according to Aspect 9, wherein the multicast transmission includes a bitmap, and a bit or time indicator for the first UE in the bitmap indicates whether the first UE is to initiate the channel access procedure to occupy the shared channel during the first frame period or to share the channel occupancy time initiated by the third UE.

[0267] Aspect 11: A method according to any one of Aspects 9 to 10, wherein the multicast transmission includes a field, the field including an identifier of the first UE and an indication of whether the first UE is to initiate the channel access procedure to occupy the shared channel during the first frame period or to share the channel occupancy time initiated by the third UE.

[0268] Aspect 12: According to the method described in any one of Aspects 1 to 11, the method further includes: receiving, in a unicast transmission from a second UE, an indication of whether to initiate the channel access procedure to occupy the shared channel during the first frame period or to share the channel occupancy time initiated by the second UE.

[0269] Aspect 13: A method for performing wireless communications at a wireless device, the method comprising: identifying corresponding business patterns associated with multiple UEs; determining, at least in part based on the corresponding business patterns associated with the multiple UEs, whether each of the multiple UEs is to initiate a channel access procedure to occupy a shared channel during a first frame period of multiple frame periods having a fixed frame duration established for communicating with the multiple UEs; and sending an indication to each UE as to whether to initiate the channel access procedure to occupy the shared channel during the first frame period based at least in part on the determination.

[0270] Aspect 14: A method according to Aspect 13, wherein the wireless device includes a network entity, and wherein sending the indication of whether to initiate the channel access procedure to occupy the shared channel during the first frame period includes: sending an indication in downlink control information as to whether to initiate the channel access procedure to occupy the shared channel during the first frame period or to share the channel occupancy time initiated by another UE.

[0271] Aspect 15: A method according to any one of Aspects 13 to 14, wherein the wireless device includes a UE, and wherein sending the indication of whether to initiate the channel access procedure to occupy the shared channel during the first frame period includes: sending an indication in a multicast transmission of whether to initiate the channel access procedure to occupy the shared channel during the first frame period or to share the channel occupancy time initiated by another UE.

[0272] Aspect 16: The method according to aspect 15, wherein the multicast transmission includes a bitmap, and each bit in the bitmap indicates whether the corresponding UE is to initiate the channel access procedure to occupy the shared channel during the first frame period or share the channel occupation time initiated by another UE.

[0273] Aspect 17: A method according to any one of Aspects 15 to 16, wherein the multicast transmission includes a bitmap, and the time indicator in the bitmap indicates whether the corresponding UE is to initiate the channel access procedure to occupy the shared channel during each frame period of one or more frame periods including the first frame period or to share the channel occupancy time initiated by other UEs.

[0274] Aspect 18: A method according to any one of Aspects 15 to 17, wherein the multicast transmission includes a field, the field including an identifier of each UE and an indication of whether each UE is to initiate the channel access procedure to occupy the shared channel during the first frame period or to share the channel occupancy time with another UE.

[0275] Aspect 19: A method according to any one of Aspects 13 to 18, wherein the wireless device includes a UE, and wherein sending the indication of whether to initiate the channel access procedure to occupy the shared channel during the first frame period includes: sending an indication to each UE in a unicast transmission as to whether to initiate the channel access procedure to occupy the shared channel during the first frame period or to share the channel occupancy time initiated by another UE.

[0276] Aspect 20: A method for performing wireless communications at a first UE, the method comprising: identifying, at the first UE, a timing configuration of a frame structure for sidelink communication via a shared channel, wherein the frame structure comprises a plurality of frame periods having a fixed frame duration; and performing communications during one or more frame periods of the plurality of frame periods of the frame structure according to the configuration.

[0277] Aspect 21: The method according to aspect 20, wherein identifying the configuration of the timing of the frame structure includes: receiving an indication of the configuration of the timing of the frame structure from a network entity or a second UE.

[0278] Aspect 22: The method according to any one of aspects 20 to 21, wherein the configuration of the timing of the frame structure is pre-configured at the first UE.

[0279] Aspect 23: According to any one of aspects 20 to 22, the method also includes: identifying the configuration of the timing of the frame structure based at least in part on a traffic pattern at the first UE.

[0280] Aspect 24: A method for performing wireless communications at a wireless device, the method comprising: identifying the timing of a frame structure for sidelink communication via a shared channel at a first UE based at least in part on a traffic pattern associated with the first UE, wherein the frame structure comprises a plurality of frame periods having a fixed frame duration; and sending an indication of the configuration of the timing of the frame structure to the first UE.

[0281] Aspect 25: A method according to Aspect 24, wherein the wireless device includes a network entity, and the method further includes: determining the traffic mode at the first UE at least in part based on sidelink communications scheduled by the network entity at the first UE.

[0282] Aspect 26: A method according to any one of aspects 24 to 25, wherein the wireless device comprises a second UE, the method further comprising: receiving an indication of the traffic mode at the first UE from a network entity or from the first UE.

[0283] Aspect 27: A method according to any one of aspects 24 to 26, wherein the wireless device comprises a second UE, and the second UE comprises an anchor UE that is pre-configured, configured via signaling from a network entity, or selected by one or more UEs including the first UE.

[0284] Aspect 28: An apparatus for performing wireless communications at a first UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 12.

[0285] Aspect 29: An apparatus for wireless communication at a first UE, the apparatus comprising: at least one means for performing the method according to any one of aspects 1 to 12.

[0286] Aspect 30: 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 according to any one of aspects 1 to 12.

[0287] Aspect 31: An apparatus for performing wireless communications at a wireless device, the apparatus comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 13 to 19.

[0288] Aspect 32: An apparatus for wireless communication at a wireless device, the apparatus comprising at least one means for performing the method according to any one of aspects 13 to 19.

[0289] Aspect 33: A non-transitory computer-readable medium storing code for wireless communication at a wireless device, the code comprising instructions executable by a processor to perform the method according to any one of aspects 13 to 19.

[0290] Aspect 34: An apparatus for performing wireless communications at a first UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 20 to 23.

[0291] Aspect 35: An apparatus for wireless communication at a first UE, the apparatus comprising: at least one means for performing the method according to any one of aspects 20 to 23.

[0292] Aspect 36: A non-transitory computer-readable medium storing code for wireless communication at a first UE, the code comprising instructions executable by a processor to perform a method according to any one of aspects 20 to 23.

[0293] Aspect 37: An apparatus for performing wireless communications at a wireless device, the apparatus comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 24 to 27.

[0294] Aspect 38: An apparatus for wireless communication at a wireless device, the apparatus comprising at least one means for performing a method according to any one of aspects 24 to 27.

[0295] Aspect 39: A non-transitory computer-readable medium storing code for wireless communication at a wireless device, the code comprising instructions executable by a processor to perform the method according to any one of aspects 24 to 27.

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

[0297] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques may 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 other systems and radio technologies not explicitly mentioned herein.

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

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

[0300] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0301] Computer readable medium includes both non-transient computer storage medium and communication medium, and the communication medium includes any medium that promotes the transfer of computer program from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage or other magnetic storage device, or can be used for carrying or storing desired program code components and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.In addition, any connection is appropriately referred to as computer readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer readable medium. Disks and optical disks used herein include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, and magnetic disks can reproduce data magnetically and optical discs can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0302] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on 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."

[0303] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure), ascertaining, etc. Additionally, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, retrieving, selecting, choosing, establishing, and other such similar actions.

[0304] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label, or other subsequent reference labels.

[0305] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific embodiments include specific details to provide an understanding of the described technology. However, these technologies may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

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

Claims

1. An apparatus for wireless communication at a first user equipment (UE), the apparatus comprising: processor; and a memory coupled to the processor, wherein the memory includes instructions executable by the processor to cause the apparatus to: identifying sidelink data to be sent in a first frame period of a plurality of frame periods having a fixed frame duration established for communication by the first UE via a shared channel; determining whether to initiate a channel access procedure to occupy the shared channel within the first frame period; as well as The sidelink data is sent based at least in part on the determination.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: The shared channel is monitored during a second frame period of the plurality of frame periods for sidelink transmissions from a second UE, wherein determining whether to initiate the channel access procedure to occupy the shared channel during the first frame period is based at least in part on the monitoring.

3. The apparatus of claim 2, wherein the instructions to determine whether to initiate the channel access procedure to occupy the shared channel during the first frame period are executable by the processor to cause the apparatus to: detecting the sidelink transmission from the second UE based at least in part on the monitoring; Determining to share a channel occupancy time initiated by the second UE and including the second frame period based at least in part on detecting the sidelink transmission; as well as Refraining from initiating the channel access procedure to occupy the shared channel during the first frame period based at least in part on determining to share the channel occupancy time initiated by the second UE.

4. The apparatus of claim 3, wherein the instructions are further executable by the processor to cause the apparatus to: Receiving in the sidelink transmission an indication that the sidelink transmission is from the second UE, wherein detecting the sidelink transmission from the second UE is based at least in part on receiving the indication.

5. The apparatus of claim 2, wherein the instructions to determine whether to initiate the channel access procedure to occupy the shared channel during the first frame period are executable by the processor to cause the apparatus to: Determining to initiate the channel access procedure to occupy the shared channel during the first frame period is based at least in part on a failure to detect the sidelink transmission from the second UE.

6. The apparatus of claim 2, wherein the instructions are further executable by the processor to cause the apparatus to: receiving an indication of configuration of the second frame period from a network entity, the second UE, or a third UE; and A starting boundary of the second frame period is identified based at least in part on receiving the indication of the configuration of the second frame period, wherein monitoring the sidelink transmission from the second UE is based at least in part on identifying the starting boundary of the second frame period.

7. The apparatus of claim 2, wherein the sidelink transmission from the second UE comprises data transmission or shared information transmission.

8. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of whether to initiate the channel access procedure to occupy the shared channel during the first frame period or to share a channel occupation time initiated by a second UE is received in downlink control information from a network entity.

9. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of whether to initiate the channel access procedure to occupy the shared channel during the first frame period or to share a channel occupation time initiated by a third UE is received in a multicast transmission from the second UE.

10. The apparatus of claim 9, wherein the multicast transmission comprises a bitmap, and a bit or a time indicator for the first UE in the bitmap indicates whether the first UE is to initiate the channel access procedure to occupy the shared channel during the first frame period or to share the channel occupation time initiated by the third UE.

11. The apparatus of claim 9, wherein the multicast transmission includes a field including an identifier of the first UE and an indication of whether the first UE is to initiate the channel access procedure to occupy the shared channel during the first frame period or to share the channel occupancy time initiated by the third UE.

12. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of whether to initiate the channel access procedure to occupy the shared channel during the first frame period or to share the channel occupancy time initiated by the second UE is received in a unicast transmission from the second UE.

13. An apparatus for wireless communication at a wireless device, the apparatus comprising: processor; and a memory coupled to the processor, wherein the memory includes instructions executable by the processor to cause the apparatus to: identifying respective traffic patterns associated with a plurality of user equipments (UEs); determining, based at least in part on the respective traffic patterns associated with the plurality of UEs, whether each of the plurality of UEs is to initiate a channel access procedure to occupy a shared channel during a first frame period of a plurality of frame periods having a fixed frame duration established for communicating with the plurality of UEs; as well as An indication is sent to the each UE based at least in part on the determination as to whether to initiate the channel access procedure to occupy the shared channel during the first frame period.

14. The apparatus of claim 13, wherein the instructions to send the indication of whether to initiate the channel access procedure to occupy the shared channel during the first frame period are executable by the processor to cause the apparatus to: An indication of whether to initiate the channel access procedure to occupy the shared channel during the first frame period or to share a channel occupation time initiated by another UE is sent in downlink control information.

15. The apparatus of claim 13, wherein the instructions to send the indication of whether to initiate the channel access procedure to occupy the shared channel during the first frame period are executable by the processor to cause the apparatus to: An indication of whether to initiate the channel access procedure to occupy the shared channel during the first frame period or to share a channel occupation time initiated by another UE is sent in a multicast transmission.

16. The apparatus of claim 15, wherein the multicast transmission comprises a bitmap, and each bit in the bitmap indicates whether the corresponding UE is to initiate the channel access procedure to occupy the shared channel during the first frame period or to share a channel occupation time initiated by another UE.

17. An apparatus according to claim 15, wherein the multicast transmission includes a bitmap, and a time indicator in the bitmap indicates whether the corresponding UE is to initiate the channel access procedure to occupy the shared channel during each frame period of one or more frame periods including the first frame period or to share the channel occupancy time initiated by other UEs.

18. The apparatus of claim 15, wherein the multicast transmission includes a field including an identifier of each UE and an indication of whether each UE is to initiate the channel access procedure to occupy the shared channel during the first frame period or to share channel occupancy time with another UE.

19. The apparatus of claim 13, wherein the instructions to send the indication of whether to initiate the channel access procedure to occupy the shared channel during the first frame period are executable by the processor to cause the apparatus to: An indication is sent to each UE in a unicast transmission as to whether to initiate the channel access procedure to occupy the shared channel during the first frame period or to share a channel occupation time initiated by another UE.

20. An apparatus for wireless communication at a first user equipment (UE), the apparatus comprising: processor; and a memory coupled to the processor, wherein the memory includes instructions executable by the processor to cause the apparatus to: identifying, at the first UE, a configuration of timing of a frame structure for sidelink communications via a shared channel, wherein the frame structure comprises a plurality of frame periods having a fixed frame duration; as well as Communicating during one or more frame periods of the plurality of frame periods of the frame structure according to the configuration.

21. The apparatus of claim 20, wherein the instructions identifying the configuration of the timing of the frame structure are executable by the processor to cause the apparatus to: An indication of the configuration of the timing of the frame structure is received from a network entity or a second UE.

22. The apparatus of claim 20, wherein the configuration of the timing of the frame structure is preconfigured at the first UE.

23. The apparatus of claim 20, wherein the instructions are further executable by the processor to cause the apparatus to: The configuration of the timing of the frame structure is identified based at least in part on a traffic pattern at the first UE.

24. An apparatus for wireless communication at a wireless device, the apparatus comprising: processor; and a memory coupled to the processor, wherein the memory includes instructions executable by the processor to cause the apparatus to: identifying timing of a frame structure for sidelink communications via a shared channel at a first user equipment (UE) based at least in part on a traffic pattern associated with the first UE, wherein the frame structure includes a plurality of frame periods having a fixed frame duration; as well as An indication of the configuration of the timing of the frame structure is sent to the first UE.

25. The apparatus of claim 24, wherein the wireless device comprises a network entity, and the instructions are further executable by the processor to cause the apparatus to: The traffic pattern associated with the first UE is determined based at least in part on sidelink communications scheduled at the first UE by the network entity.

26. The apparatus of claim 24, wherein the wireless device comprises a second UE, and the instructions are further executable by the processor to cause the apparatus to: An indication of the traffic pattern at the first UE is received from a network entity or from the first UE.

27. The apparatus of claim 24, wherein the wireless device comprises a second UE, and the second UE comprises an anchor UE that is preconfigured, configured via signaling from a network entity, or selected by one or more UEs including the first UE.

Images