Method and apparatus for wireless communication at first user equipment (UE)

Abstract

Methods and apparatus for wireless communication at a first user equipment (UE) are described. The method comprises: identifying a schedule associated with direct communication of the first UE with a second UE, the schedule comprising a wakeup period reserved for transmitting or receiving one-way communication; determining a wake-up period for a discontinuous reception configuration associated with transmitting or receiving the unidirectional communication, where the discontinuous reception configuration is for at least one discontinuous reception period controlled by a set of timers associated with the first UE, and where the set of timers is associated with the first UE; the wake-up period of the discontinuous reception configuration is based at least in part on a traffic load associated with the first UE and a sidelink traffic load between the first UE and one or more UEs including the second UE; and communicating with the second UE according to the discontinuous reception configuration.

Description

[0001] This application is a divisional application of a Chinese patent application with an application date of August 18, 2020 and an application number of 202080057925.3.

[0002] Cross-reference

[0003] This patent application claims the benefit of U.S. Provisional Patent Application No. 62 / 891,183, filed on August 23, 2019, by Wu et al. and titled "Methods of Scheduling With Inactivity in Sidelink Unicast", and U.S. Patent Application No. 16 / 995,505, filed on August 17, 2020, by Wu et al. and titled "Methods of Scheduling With Inactivity in Sidelink Unicast"; each of which is assigned to the assignee of this application. Technical Field

[0004] The following generally relates to wireless communication, and more specifically, to methods of scheduling with inactivity in sidelink unicast. Background Art

[0005] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasts, etc. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi-access systems include fourth-generation (4G) systems, such as Long-Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth-generation (5G) systems, which may be referred to as New Radio (NR) systems. These systems may employ techniques such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multi-access communication system may include multiple base stations or network access nodes, each of which simultaneously supports communication of multiple communication devices, which may also be referred to as user equipment (UE).

[0006] Some wireless communication systems can support an access link and a sidelink. The access link is a communication link between a UE and a base station. In some examples, the access link can be referred to as the Uu interface. Specifically, the Uu interface can refer to the air interface for downlink transmission, uplink transmission, or both. The sidelink is a communication link between similar devices. For example, the sidelink can support communication between multiple UEs (e.g., in examples such as vehicle-to-everything (V2X) systems, vehicle-to-vehicle (V2V) systems, device-to-device (D2D) systems, etc.). In some examples, the sidelink can support unicast messaging, multicast messaging, broadcast messaging, or a combination thereof. In these systems, efficient energy-saving techniques may be required. Summary of the Invention

[0007] The described techniques relate to improved methods, systems, devices, and apparatuses that support a method for scheduling in an inactive situation in sidelink unicast. Techniques for device-to-device communication between devices (e.g., user equipment (UE)) are proposed that ensure reliable communication and energy saving. A UE and additional UEs in a group of UEs can communicate directly (e.g., via the sidelink). Scheduling associated with the UE can include a wake-up period reserved for directed communication between the UE and the additional UEs. For example, the scheduling can include a wake-up period reserved for unidirectional communication from the UE to the additional UE (or from the additional UE to the UE), or a wake-up period reserved for bidirectional communication between the UE and the additional UEs. The UE can identify the scheduling and manage the wake-up period reserved for directed communication between the UE and the additional UEs.

[0008] For example, the UE can manage the wake-up period reserved for directed communication (e.g., manage one or more of the wake-up periods reserved for unidirectional communication or for bidirectional communication). In some cases, the UE can manage one or more of the wake-up periods based on traffic information associated with the UE (e.g., traffic load, inactivity). In some examples, the UE can send a request message to the additional UE based on traffic information associated with the UE. In some cases, the UE can receive a response message from the additional UE and manage one or more of the wake-up periods based on the response message. The response message can include an acknowledgement (e.g., an acceptance message) or a negative acknowledgement (e.g., a rejection message) and the associated reason for the response.

[0009] A method for wireless communication at a first UE in a group of UEs is described. The method can include identifying a scheduling associated with the first UE and a second UE in a group of UEs that directly communicates with the first UE, where the scheduling includes a wake-up period reserved for directed communication between the first UE and the second UE (e.g., a wake-up period reserved for unidirectional communication from the first UE to the second UE, or a wake-up period reserved for bidirectional communication between the first UE and the second UE, or a combination thereof); managing the wake-up period reserved for directed communication based on traffic information associated with the first UE; and communicating with the second UE according to the management.

[0010] A first apparatus in a group of apparatuses for wireless communication is described. The first apparatus can include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions can be executed by the processor to cause the first apparatus to identify a scheduling associated with the first apparatus and a second apparatus in a group of apparatuses that directly communicates with the first apparatus, where the scheduling includes a wake-up period reserved for directed communication between the first apparatus and the second apparatus (e.g., a wake-up period reserved for unidirectional communication from the first apparatus to the second apparatus, or a wake-up period reserved for bidirectional communication between the first apparatus and the second apparatus, or a combination thereof); managing the wake-up period reserved for directed communication based on traffic information associated with the first apparatus; and communicating with the second apparatus according to the management.

[0011] A first apparatus in a group of apparatuses for wireless communication is described. The first apparatus can include components for performing the following operations: identifying a scheduling associated with the first apparatus and a second apparatus in a group of apparatuses that directly communicates with the first apparatus, where the scheduling includes a wake-up period reserved for directed communication between the first apparatus and the second apparatus (e.g., a wake-up period reserved for unidirectional communication from the first apparatus to the second apparatus, or a wake-up period reserved for bidirectional communication between the first apparatus and the second apparatus, or a combination thereof); managing the wake-up period reserved for directed communication based on traffic information associated with the first apparatus; and communicating with the second apparatus according to the management.

[0012] A non-transitory computer-readable medium storing code for wireless communication at a first UE in a group of UEs is described. The code can include instructions executable by a processor to identify a scheduling associated with the first UE and a second UE in a group of UEs that directly communicates with the first UE, where the scheduling includes a wake-up period reserved for directed communication between the first UE and the second UE (e.g., a wake-up period reserved for unidirectional communication from the first UE to the second UE, or a wake-up period reserved for bidirectional communication between the first UE and the second UE, or a combination thereof); managing the wake-up period reserved for directed communication based on traffic information associated with the first UE; and communicating with the second UE according to the management.

[0013] A method for wireless communication at a first user equipment (UE) is described. The method includes: identifying a schedule associated with direct communication between the first UE and a second UE, the schedule including a wake-up period reserved for sending or receiving one-way communication; determining a wake-up period of a discontinuous reception configuration associated with sending or receiving the one-way communication, wherein the discontinuous reception configuration is for at least one discontinuous reception cycle controlled by a set of timers associated with the first UE, and wherein the wake-up period of the discontinuous reception configuration is at least partially based on a traffic load associated with the first UE and a sidelink traffic load between the first UE and one or more UEs including the second UE; and communicating with the second UE according to the discontinuous reception configuration.

[0014] A method for wireless communication at a first user equipment (UE) is described. The method includes: identifying a schedule associated with direct communication between the first UE and a second UE, the schedule including a wake-up period reserved for sending or receiving one-way communication; determining a wake-up period of a discontinuous reception configuration associated with sending or receiving the one-way communication, at least partially based on traffic information associated with the first UE or the second UE, wherein the discontinuous reception configuration is for at least one discontinuous reception cycle controlled by a set of timers associated with the first UE, and wherein the wake-up period of the discontinuous reception configuration is at least partially based on a traffic load associated with the first UE and a sidelink traffic load between the first UE and one or more UEs including the second UE; and communicating with the second UE according to the discontinuous reception configuration.

[0015] A first apparatus for wireless communication is described. The first apparatus includes: one or more processors, and at least one memory coupled to the one or more processors, the one or more processors being configured to: identify a schedule associated with direct communication between the first apparatus and a second apparatus, the schedule including a wake-up period reserved for sending or receiving one-way communication; determine a wake-up period of a discontinuous reception configuration associated with sending or receiving the one-way communication, wherein the discontinuous reception configuration is for at least one discontinuous reception cycle controlled by a set of timers associated with the first apparatus, and wherein the wake-up period of the discontinuous reception configuration is at least partially based on a traffic load associated with the first apparatus and a sidelink traffic load between the first apparatus and one or more apparatuses including the second apparatus; and communicate with the second apparatus according to the discontinuous reception configuration.

[0016] Describes a first device for wireless communication. The first device includes: one or more processors, and at least one memory coupled to the one or more processors, the one or more processors being configured to: identify a schedule associated with direct communication between the first device and a second device, the schedule including wake-up periods reserved for sending or receiving unidirectional communication; determine, at least in part based on traffic information associated with the first device or the second device, a wake-up period of a discontinuous reception configuration associated with sending or receiving the unidirectional communication, wherein the discontinuous reception configuration is for at least one discontinuous reception period controlled by a set of timers associated with the first device, and wherein the wake-up period of the discontinuous reception configuration is at least in part based on the traffic load associated with the first device and the sidelink traffic load between the first device and one or more devices including the second device; and communicate with the second device according to the discontinuous reception configuration.

[0017] Some examples of the methods, devices, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for sending a request message to a second UE based on traffic information associated with a first UE, receiving a response message from the second UE based on the request message, and wherein managing the wake-up period reserved for directed communication may be based on the response message.

[0018] In some examples of the methods, devices, and non-transitory computer-readable media described herein, one or more of the request message or the response message may be a PC5 radio resource control message.

[0019] In some examples of the methods, devices, and non-transitory computer-readable media described herein, one or more of the request message or the response message may be a media access control - control element message.

[0020] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the request message includes an indication of the number of periods associated with modifying the wake-up period reserved for directed communication.

[0021] Some examples of the methods, devices, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for determining that the traffic load associated with a first UE meets a threshold based on traffic information, wherein managing the wake-up period reserved for directed communication may be based on the traffic load meeting the threshold, and based on this determination, including a cause indication in the request message, the cause indication indicating that the traffic load associated with the first UE meets the threshold, wherein sending the request message to the second UE includes sending a request message carrying the cause indication to the second UE.

[0022] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, determining that the traffic associated with a first UE meets a threshold may include operations, features, components, or instructions for comparing the traffic associated with the first UE with the predicted traffic associated with the first UE, and wherein managing the wake-up period reserved for directed communication may be based on the comparison.

[0023] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for including, in a request message based on traffic information, an indication to remove the wake-up period reserved for directed communication (e.g., the wake-up period reserved for one-way communication), wherein communication with a second UE may be based on the indication.

[0024] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for including, in a request message based on traffic information, an indication to modify the wake-up period reserved for directed communication (e.g., the wake-up period reserved for one-way communication), wherein communication with a second UE may be based on the indication.

[0025] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for dispatching a bit value to a field in a request message, wherein the bit value corresponds to the duration of the wake-up period reserved for directed communication (e.g., the duration of the wake-up period reserved for one-way communication).

[0026] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for including, in a request message based on traffic information, an indication to remove or modify the wake-up period reserved for directed communication (e.g., the wake-up period reserved for two-way communication), wherein communication with a second UE may be based on the indication.

[0027] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for allocating a bit value to a field in a request message, wherein the bit value corresponds to the duration of the wake-up period reserved for directed communication (e.g., the duration of the wake-up period reserved for two-way communication).

[0028] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for including, in a request message based on traffic information, an indication to specifically allocate the wake-up period reserved for directed communication (e.g., the wake-up period reserved for two-way communication) to a second UE, wherein communication with the second UE may be based on the indication.

[0029] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the wake-up periods reserved for directed communication may include wake-up periods reserved for one-way communication from a first UE to a second UE or wake-up periods reserved for two-way communication between a first UE and a second UE. The wake-up periods reserved for two-way communication may be shared between the first UE and the second UE, while the wake-up periods reserved for one-way communication may not be shared between the first UE and the second UE.

[0030] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for receiving, from a second UE, an indication that a wake-up period reserved for directed communication (e.g., a wake-up period reserved for two-way communication) is dedicated to the first UE, wherein communication with the second UE may be based on the indication.

[0031] A method for wireless communication at a first UE in a group of UEs is described. The method may include identifying a schedule associated with the first UE and a second UE in the group of UEs that directly communicates with the first UE, wherein the schedule includes a wake-up period reserved for directed communication between the first UE and the second UE (e.g., a wake-up period reserved for one-way communication from the first UE to the second UE or from the second UE to the first UE, or a wake-up period reserved for two-way communication between the first UE and the second UE, or a combination thereof); managing the wake-up period reserved for directed communication based on traffic information associated with the first UE or the second UE; and communicating with the second UE according to the management.

[0032] A first apparatus in a group of apparatuses for wireless communication is described. The first apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the first processor to cause the first apparatus to identify a schedule associated with the first apparatus and a second apparatus in the group of apparatuses that directly communicates with the first apparatus, wherein the schedule includes a wake-up period reserved for directed communication between the first apparatus and the second apparatus (e.g., a wake-up period reserved for one-way communication from the first apparatus to the second apparatus or from the second apparatus to the first apparatus, or a wake-up period reserved for two-way communication between the first apparatus and the second apparatus, or a combination thereof); managing the wake-up period reserved for directed communication based on traffic information associated with the first apparatus or the second apparatus; and communicating with the second apparatus according to the management.

[0033] Describes a first device in a set of devices for wireless communication. The first device may include components for performing the following operations: identifying a schedule associated with the first device and a second device in a set of devices that communicates directly with the first device, where the schedule includes a wake-up period reserved for directed communication between the first device and the second device (e.g., a wake-up period reserved for unidirectional communication from the first device to the second device or from the second device to the first device, or a wake-up period reserved for bidirectional communication between the first device and the second device, or a combination thereof); managing the wake-up period reserved for directed communication based on traffic information associated with the first device or the second device; and communicating with the second device according to the management.

[0034] Describes a non-transitory computer-readable medium storing code for wireless communication at a first UE in a set of UEs. The code may include instructions executable by a processor to identify a schedule associated with the first UE and a second UE in a set of UEs that communicates directly with the first UE, where the schedule includes a wake-up period reserved for directed communication between the first UE and the second UE (e.g., a wake-up period reserved for unidirectional communication from the first UE to the second UE or from the second UE to the first UE, or a wake-up period reserved for bidirectional communication between the first UE and the second UE, or a combination thereof); managing the wake-up period reserved for directed communication based on traffic information associated with the first UE or the second UE; and communicating with the second UE according to the management.

[0035] Some examples of the methods, devices, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for receiving a request message from the second UE, the request message including traffic information associated with the second UE, sending a response message to the second UE based on the request message and traffic information associated with the first UE, and where managing the wake-up period reserved for directed communication may be based on the request message and traffic information associated with the first UE.

[0036] In some examples of the methods, devices, and non-transitory computer-readable media described herein, one or more of the request message or the response message may be a PC5 radio resource control message or a media access control - control element message.

[0037] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the request message includes an indication of the number of periods associated with modifying the wake-up period reserved for directed communication.

[0038] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, based on traffic information associated with a second UE, a request message carries a cause indication that indicates that the traffic payload associated with the second UE meets a threshold, and wherein managing a wake-up period reserved for directed communication can be based on inactivity associated with the directed communication between the second UE and the first UE (e.g., inactivity associated with one-way communication from the second UE to the first UE).

[0039] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for identifying, in a request message, an indication to remove a wake-up period reserved for directed communication (e.g., a wake-up period reserved for one-way communication), releasing one or more resources associated with the wake-up period reserved for directed communication (e.g., a wake-up period reserved for one-way communication) based on the request message and the traffic information, including, in a response message, an acknowledgement associated with releasing the one or more resources associated with the wake-up period reserved for directed communication (e.g., a wake-up period reserved for one-way communication), and wherein communication with the second UE can be based on one or more of: the response message and the release of the one or more resources associated with the wake-up period reserved for one-way communication.

[0040] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for identifying, in a request message, an indication to modify a wake-up period reserved for directed communication (e.g., a wake-up period reserved for one-way communication), including, in a response message, an acknowledgement associated with adjusting the duration of the wake-up period reserved for directed communication (e.g., one or more of the wake-up periods reserved for one-way communication), and wherein communication with the second UE can be based on the response message.

[0041] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for identifying one or more bit values assigned to a field in the request message, wherein the one or more bit values correspond to the duration of the wake-up period reserved for directed communication (e.g., the duration of the wake-up period reserved for one-way communication).

[0042] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for identifying, in a request message, an indication to remove a wake-up period reserved for directed communication (e.g., a wake-up period reserved for two-way communication), including, in a response message, an acknowledgement associated with releasing one or more resources associated with the wake-up period reserved for directed communication (e.g., the wake-up period for two-way communication), and wherein communication with a second UE may be based on the response message.

[0043] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for identifying a bit value assigned to a field in a request message, wherein the bit value corresponds to the duration of a wake-up period reserved for directed communication (e.g., a wake-up period reserved for two-way communication).

[0044] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for identifying, in a request message, an indication that a wake-up period reserved for directed communication (e.g., a wake-up period reserved for two-way communication) is specifically allocated to a first UE, including, in a response message, an acknowledgement associated with the wake-up period reserved for directed communication (e.g., the wake-up period for two-way communication) being specifically allocated to the first UE, and wherein communication with a second UE may be based on the response message.

[0045] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for communicating with a third UE in the group of UEs according to managing a wake-up period reserved for directed communication.

[0046] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the wake-up period reserved for directed communication may include a wake-up period reserved for one-way communication from a first UE to a second UE or a wake-up period reserved for two-way communication between the first UE and the second UE, wherein the wake-up period reserved for two-way communication may be shared between the first UE and the second UE, and wherein the wake-up period reserved for one-way communication may not be shared between the first UE and the second UE.

[0047] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for sending to a second UE an indication associated with a wake-up period reserved for directed communication (e.g., a wake-up period reserved for two-way communication) being specifically allocated to the second UE, and wherein communication with the second UE may be based on the indication. Description of the Drawings

[0048] Figure 1 An example of a wireless communication system is shown that supports a method for scheduling in an inactive scenario in sidelink unicast according to various aspects of the present disclosure.

[0049] Figure 2 An example of a wireless system is shown that supports device - to - device (D2D) scheduling of a wireless communication system according to various aspects of the present disclosure.

[0050] Figure 3 An example of a wireless system is shown that supports a method for scheduling in an inactive scenario in sidelink unicast according to various aspects of the present disclosure.

[0051] Figure 4 An example of a timing diagram is shown that supports a method for scheduling in an inactive scenario in sidelink unicast according to various aspects of the present disclosure.

[0052] Figure 5 An example of a processing flow is shown that supports a method for scheduling in an inactive scenario in sidelink unicast according to various aspects of the present disclosure.

[0053] Figure 6 and Figure 7 A block diagram of a device is shown that supports a method for scheduling in an inactive scenario in sidelink unicast according to various aspects of the present disclosure.

[0054] Figure 8 A block diagram of a user equipment (UE) communication manager is shown that supports a method for scheduling in an inactive scenario in sidelink unicast according to various aspects of the present disclosure.

[0055] Figure 9 A schematic diagram of a system of a device is shown that includes a method for scheduling in an inactive scenario in sidelink unicast according to various aspects of the present disclosure.

[0056] Figures 10 to 13 A flowchart of a method is shown that supports scheduling in an inactive scenario in sidelink unicast according to aspects of the present disclosure. Detailed Description

[0057] A wireless communication system can support an access link and a sidelink for communication between wireless devices. The access link can refer to the communication link between a user equipment (UE) and a base station. For example, the access link can support uplink signaling, downlink signaling, connection procedures, etc. The sidelink can refer to any communication link between similar wireless devices (e.g., the communication link between UEs, or the backhaul communication link between base stations). It should be noted that although the various examples provided in this document are discussed for UE sidelink devices, this sidelink access technology can be used for any type of wireless device that uses sidelink access communication. For example, the sidelink can support device-to-device (D2D) communication, vehicle-to-everything (V2X) and / or vehicle-to-vehicle (V2V) communication, message relaying, discovery signaling, beacon signaling, or any combination of these signals or other signals that are sent from one UE to one or more other UEs over the air. Sidelink communication can support communication within a group of UEs. For example, sidelink communication can include communication between a UE and other UEs within the coverage area that includes the group of UEs (e.g., the coverage area provided by a base station, the coverage area outside the coverage area provided by a base station, or a combination thereof). One or more UEs in the group of UEs can initiate sidelink communication with other UEs in the group of UEs.

[0058] For example, a UE communicating with one or more additional UEs in the group of UEs (e.g., in a D2D system, in other examples) can send information to or receive information from another UE. To address scheduling issues that may be associated with communicating with multiple concurrent peers (e.g., peer UEs in the group of UEs), the UE can reserve resources (e.g., time slots or time periods) for sending or receiving information. In some examples, the reservation can be semi-persistent, and the UE can reserve resources based on a prediction of future communication needs by the UE or another UE in the group of UEs that communicates with the UE. However, the demand prediction may not always be accurate, and the UE may inadvertently reserve (e.g., distributed NR sidelink reservation) more resources than required in a unicast link. In these examples, a UE that realizes its own inactivity with respect to an established unicast link (e.g., a scheduling that has been negotiated between the UE and another UE in the group of UEs) can notify another UE (e.g., the peer UE) associated with the link to adjust the reservation.

[0059] As described herein, energy-saving techniques for sidelink communication can be used to achieve reduced power consumption and extended battery life while ensuring reliable and efficient communication among the group of UEs. The energy-saving techniques can be implemented, in part, by one or more UEs in the group of UEs. In some examples, a UE can utilize a signaling mechanism to manage unidirectional scheduling or bidirectional scheduling associated with communication between the UE and another UE. For example, the UE can modify or update the directional scheduling (e.g., unidirectional scheduling or bidirectional scheduling) associated with communication between the UE and another UE. In some examples, managing the scheduling can include releasing another UE from a prior communication obligation (e.g., terminating a unicast link associated with unidirectional communication from the UE to another UE or from another UE to the UE and releasing the associated resources).

[0060] Aspects of the examples described herein can bring several advantages to communication associated with various communication technologies. For example, in the sub-6 GHz range, if a UE realizes its own inactivity (e.g., no additional transmissions from the UE) with respect to an established unicast link (e.g., a schedule negotiated between the UE and a peer UE) and notifies the peer UE of the inactivity, the peer UE can use the resources previously allocated to that link to schedule transmissions between other peer UEs. For example, in millimeter wave (mmW) communication, the peer UE can similarly reuse the previously allocated resources as described above, but can also benefit from being able to receive transmissions in another beam direction.

[0061] In some examples, a UE in a group of UEs can identify a schedule associated with the UE and another UE (e.g., a peer UE) in the group of UEs. The schedule can include a wake-up period for directional communication between the UE and the peer UE (e.g., a wake-up period reserved for unidirectional communication from the UE to the peer UE, or a wake-up period reserved for bidirectional communication between the UE and the peer UE, or a combination thereof). The UE can send a request message to the peer UE based on traffic information associated with the UE. In one example, the request message can include an indication of the number of periods associated with modifying one or more of the wake-up periods. In some examples, the request message can include an indication of the reason associated with the request message (e.g., inactivity, traffic load exceeding traffic expectations). The UE can receive a response message from the peer UE and can manage the wake-up period (e.g., one or more of the wake-up periods for unidirectional communication or bidirectional communication) based on the response message. In some cases, the response message can include an acknowledgement (e.g., acceptance) or a negative acknowledgement (e.g., rejection) and an associated reason (e.g., traffic information associated with the peer UE, such as scheduled communication from the peer UE to the UE).

[0062] According to examples of aspects described herein, a UE may manage wake-up periods (e.g., one or more of the wake-up periods for one-way or two-way communication) based on service information associated with the UE (e.g., service load, inactivity) and a response message from a peer UE. In some examples, the UE may terminate a unicast link associated with one-way communication from the UE to the peer UE and remove the wake-up period for the one-way communication (e.g., release resources associated with the wake-up period). In another example, the UE may adjust the duration of the wake-up period for one-way communication. In other exemplary aspects, the UE may adjust the duration of the wake-up period reserved for directed communication (e.g., two-way communication) between the UE and the peer UE, or remove the wake-up period (e.g., release resources associated with the wake-up period). In another aspect, the UE may dedicate the wake-up period to the UE or the peer UE (e.g., dedicate the wake-up period reserved for two-way communication between the UE and the peer UE to the wake-up period reserved for one-way communication associated with the UE or the peer UE). Through one or any combination of the described techniques, the UE may implement various energy-saving enhancement schemes, thereby improving battery life and reducing unnecessary power consumption at the UE while providing efficient and reliable communication on the sidelink.

[0063] Aspects of the present disclosure are initially described in the context of a wireless communication system. Further aspects of the present disclosure are illustrated and described by means of apparatus diagrams, system diagrams, and flowcharts that relate to methods for scheduling in the case of inactivity in sidelink unicast.

[0064] Figure 1 An example of a wireless communication system 100 that supports a method for scheduling in the case of inactivity in sidelink unicast in accordance with aspects of the present disclosure is shown. The wireless communication system 100 may include a base station 105, a UE 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, or a New Radio (NR) network. In some cases, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, communication with low-cost and low-complexity devices, or any combination thereof.

[0065] Base stations 105 can be dispersed throughout a geographical area to form a wireless communication system 100 and can be devices of different forms or with different capabilities. The base stations 105 and the UEs 115 can communicate wirelessly via one or more communication links 125. Each base station 105 can provide a coverage area 110 over which the UEs 115 and the base station 105 can establish a communication link 125. The coverage area 110 can be an example of a geographical area over which the base station 105 and the UEs 115 support signal communication according to one or more radio access technologies.

[0066] The UEs 115 can be dispersed in the coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary, or mobile, or both at different times. The UEs 115 can be devices of different forms or with different capabilities. Figure 1 Some exemplary UEs 115 are shown. The UEs 115 described herein are capable of communicating with various types of devices, such as other UEs 115, base stations 105, and / or network devices (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network devices), as Figure 1 shown.

[0067] The base stations 105 can communicate with each other, or with the core network 130, or both. For example, the base stations 105 can be connected to the core network 130 via a backhaul link 120 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 can communicate with each other directly (e.g., directly between base stations 105) or indirectly (e.g., via the core network 130) or both via the backhaul link 120 (e.g., via X2, Xn, or other interfaces). In some examples, the backhaul link 120 can be or include one or more wireless links. One or more of the base stations 105 described herein can include or can be referred to by those of ordinary skill in the art as base transceiver stations, radio base stations, access points, radio transceivers, NodeB, eNodeB (eNB), next-generation NodeB, or gigabit NodeB (any of which can be referred to as gNB), home NodeB, home eNodeB, or other suitable terms.

[0068] The 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 the "device" may also be referred to as a unit, a station, a terminal, or a client, etc. The 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, the UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances, vehicles, meters, etc. As Figure 1 shown, the UE 115 described herein is capable of communicating with various types of devices, such as other UEs 115 that can sometimes act as relays, as well as base stations 105 and network devices, including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc.

[0069] The UE 115 and the base station 105 may communicate wirelessly with each other via one or more communication links 125 on one or more carriers. The term "carrier" may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion (e.g., a bandwidth part (BWP)) of a radio spectrum band that operates according to the physical layer channels of 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 operation, user data, or other signaling. The wireless communication system 100 may use carrier aggregation or multi-carrier operation to support communication with the UE 115. According to the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used with frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0070] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling for coordinating 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 radio frequency channel number (EARFCN)) and may be positioned according to a channel raster to facilitate discovery by the UE 115. A carrier may operate in an independent mode, where initial acquisition and connection may be performed by the UE 115 via the carrier; or a carrier may operate in a non-independent mode, where the connection is anchored using a different carrier (e.g., the same or a different radio access technology).

[0071] The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105, or a downlink transmission from the base station 105 to the UE 115. A carrier may carry downlink or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode). A carrier may be associated with a particular bandwidth of the radio spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth may be one of a plurality of predetermined bandwidths of a carrier 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). Devices of the wireless communication system 100 (e.g., the base station 105 or the UE 115 or both) may have a hardware configuration that supports communication on a particular carrier bandwidth, or may be configured to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include the base station 105 and / or the UE 115, and the base station 105 and / or the UE 115 support simultaneous communication via carriers associated with a plurality of carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0072] The signal waveform transmitted through a carrier may be composed of a plurality of subcarriers (e.g., using a multi-carrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system adopting an MCM technique, a resource element may be composed of a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and the subcarrier spacing are inversely correlated. 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). Therefore, the more resource elements the UE 115 receives and the higher the order of the modulation scheme, the higher the data rate of the UE 115 may be. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may further increase the data rate or data integrity of communicating with the UE 115.

[0073] The time interval of the base station 105 or the UE 115 may be expressed as a multiple of a basic time unit. For example, the basic time unit may refer to the sampling period of seconds, where may represent the maximum supported subcarrier spacing, and may represent the maximum supported Discrete Fourier Transform (DFT) size. The time intervals of communication resources may be organized according to radio frames, each radio frame 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). Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some cases, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a plurality of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a plurality of symbol periods (e.g., depending on the length of the cyclic prefix before each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini-slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., number of) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0074] A subframe, time slot, mini-slot, or 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 Transmission Time Interval (TTI). In some cases, 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 a burst of short TTIs (sTTIs)).

[0075] According to various techniques, physical channels may be multiplexed on a carrier. For example, a physical control channel and a physical data channel may be multiplexed on a downlink carrier using Time Division Multiplexing (TDM) techniques, Frequency Division Multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. The control region of a physical control channel (e.g., a Control Resource Set (CORESET)) may be defined by a plurality of symbol periods and may span the system bandwidth of the carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESET) may be configured for a set of UEs 115. For example, a UE 115 may monitor or search for control information in a control region 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 a plurality of control channel resources (e.g., Control Channel Elements (CCEs)) associated with coded information of a control information format having a given payload size. The search space set may include a common search space set configured to send control information to a plurality of UEs 115 and a UE-specific search space set for sending control information to a specific UE 115.

[0076] Each base station 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells or various combinations thereof). The term "cell" may refer to a logical communication entity used to communicate with base station 105 (e.g., via a carrier), and may be associated with an identifier (e.g., physical cell identifier (PCID), virtual cell identifier (VCID), etc.) used to distinguish adjacent cells. In some examples, a cell may also refer to a geographical coverage area 110 or a portion (e.g., a sector) of the geographical coverage area 110 on which the logical communication entity operates. The scope of such a cell may range from a smaller area (e.g., a structure, a subset of a structure) to a larger area, depending on various factors such as the capabilities of base station 105. For example, a cell may be or include a building, a subset of a building, an external space between or overlapping with geographical coverage area 110, etc.

[0077] Macro cells typically cover a relatively large geographical area (e.g., with a radius of several kilometers) and may allow UEs 115 subscribed to the network provider's services supported by the macro cell to access unrestrictedly. Compared with macro cells, small cells may be associated with low-power base stations 105, and small cells may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 subscribed to the network provider's services, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed user group (CSG), UEs 115 associated with users in a home or office, etc.). Base station 105 may support one or more cells and may also support communication on one or more cells using one or more component carriers. In some examples, a carrier may support multiple cells and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of devices.

[0078] In some examples, base station 105 may be mobile and may thus provide communication coverage for a mobile geographical coverage area 110. In some examples, different geographical coverage areas 110 associated with different technologies may overlap, but different geographical coverage areas 110 may be supported by the same base station 105. In other examples, different base stations 105 may support overlapping geographical coverage areas 110 associated with different technologies. For example, wireless communication system 100 may include a heterogeneous network in which different types of base stations 105 provide coverage for various geographical coverage areas 110 using the same or different radio access technologies.

[0079] Some UEs 115, such as MTC devices or IoT devices, can be low-cost or low-complexity devices and can provide automatic communication between machines (such as, via machine-to-machine (M2M) communication). M2M communication or MTC can refer to a data communication technology that allows devices to communicate with each other or with the base station 105 without human intervention. In some examples, M2M communication or MTC can include communication from devices integrated with sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 can be designed to collect information or implement automatic behavior of machines or other devices. Example applications of MTC devices include smart meters, inventory monitoring, water level monitoring, device monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security awareness, physical access control, and transaction-based commercial charging.

[0080] Some UEs 115 can be configured to operate in power-saving modes, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but not both simultaneously). In some examples, half-duplex communication can be performed at a reduced peak rate. Other energy-saving techniques for UEs 115 include entering a power-saving deep sleep mode when not participating in active communication, operating on limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UEs 115 can be configured to operate using a narrowband protocol type associated with a predefined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of the carrier, or outside the carrier.

[0081] 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) or mission-critical communication. The UE 115 can be designed to support ultra-reliable, low-latency, or critical functions (e.g., mission-critical functions). Ultra-reliable communication can include private communication or group communication and can be supported by one or more mission-critical services, such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions can include determining the priority of services, and mission-critical services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency can be used interchangeably herein.

[0082] In some cases, UE 115 can also communicate directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 using D2D communication can be within the geographical coverage area 110 of the base station 105. Other UEs 115 in such a group may be outside the geographical coverage area 110 of the base station 105 or may not be able to receive transmissions from the base station 105. In some cases, multiple groups of UEs 115 communicating via D2D communication can utilize a one-to-many (1:M) system, where each UE 115 transmits to every other UE 115 in the group. In some examples, the base station 105 facilitates resource scheduling for D2D communication. In other cases, D2D communication is performed between UEs 115 without the participation of the base station 105.

[0083] 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, vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these communications. Vehicles can send information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information related to the V2X system. In some cases, vehicles in a 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., base station 105), or communicate with both.

[0084] The core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which can 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 external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a user plane function (UPF)). The control plane entity can manage non-access stratum (NAS) functions, such as the mobility, authentication, and bearer management of UEs 115 served by the base station 105 associated with the core network 130. User IP packets can be transmitted through the user plane entity, which can provide IP address allocation and other functions. The user plane entity can be connected to the network operator's IP service 150. The operator's IP service 150 can include access to the Internet, an intranet(s), an IP multimedia subsystem (IMS), or packet-switched streaming services.

[0085] Some network devices, such as base station 105, may include subcomponents, such as access network entity 140, which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with UE 115 via a plurality of other access network transmission entities 145, which may be referred to as radio heads, intelligent radio heads, or transmit / receive points (TRPs). Each access network transmission entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs), or consolidated into a single network device (e.g., base station 105).

[0086] Wireless communication system 100 may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or the decimeter band because the wavelength range is from approximately 1 decimeter to 1 meter in length. UHF waves may be blocked or redirected by buildings and environmental features, but the waves can penetrate structures sufficiently to enable a macro cell to serve a UE 115 located indoors. Compared to transmissions at smaller frequencies and longer wavelengths using the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 megahertz, UHF wave transmissions may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers).

[0087] Wireless communication system 100 may also operate in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as the millimeter band). In some examples, wireless communication system 100 may support mmW communication between UE 115 and base station 105, and the EHF antennas of the corresponding devices may be smaller and more closely spaced than UHF antennas. In some cases, this may facilitate the use of antenna arrays within UE 115. However, compared to super high frequency (SHF) transmissions or UHF transmissions, EHF transmissions may experience greater atmospheric attenuation and shorter distances. The techniques disclosed herein may be employed in transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may vary by country or regulatory body.

[0088] The wireless communication system 100 can utilize licensed and unlicensed radio spectrum bands. For example, the wireless communication system 100 can employ Licensed-Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technologies, or NR technologies in unlicensed bands such as the 5 GHz Industrial, Scientific, and Medical (ISM) band. When operating in an unlicensed radio spectrum band, devices such as the base station 105 and the UE 115 can employ carrier sensing for collision detection and avoidance. In some cases, operation in the unlicensed band can be based on a carrier aggregation configuration and a component carrier operating in a licensed band (e.g., LAA). Operations in the unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, D2D transmissions, etc.

[0089] The base station 105 or the UE 115 can be equipped with multiple antennas, which can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the base station 105 or the UE 115 can be located within one or more antenna arrays or antenna panels, which can support MIMO operation, or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays can be co-located at an antenna assembly, such as at an antenna tower. In some cases, the antennas or antenna arrays associated with the base station 105 can be located at different geographical locations. The base station 105 can have an antenna array having multiple rows and columns of antenna ports, which the base station 105 can use to support beamforming for communication with the UE 115. Similarly, the UE 115 can have one or more antenna arrays, which can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel can support radio frequency beamforming of signals transmitted via the antenna ports.

[0090] Beamforming, which can also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., the base station 105, the UE 115) to shape or manipulate an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals transmitted via the antenna elements of an antenna array such that some signals propagating in a particular orientation relative to the antenna array experience constructive interference while other signals experience destructive interference. The adjustment of the signals transmitted via the antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals transmitted via the antenna elements associated with the device. The adjustment associated with each antenna element can 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).

[0091] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, the communication of the bearer layer or the Packet Data Convergence Protocol (PDCP) layer can be IP-based. The Radio Link Control (RLC) layer can perform packet segmentation and reassembly for communication over logical channels. The Medium Access Control (MAC) layer can perform priority handling and multiplex logical channels into transport channels. The MAC layer can also use error detection techniques, error correction techniques, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer can provide the establishment, configuration, and maintenance of the RRC connection between the UE 115 and the base station 105 or the core network 130 that supports the radio bearers for user plane data. At the physical layer, the transport channels can be mapped to physical channels.

[0092] The UE 115 and the base station 105 can support retransmission of data to increase the likelihood that the data is successfully received. Hybrid Automatic Repeat reQuest (HARQ) feedback is a technique that increases the likelihood that data is correctly received over the communication link 125. HARQ can include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat reQuest (ARQ)). Under adverse radio conditions (e.g., low signal-to-noise ratio conditions), HARQ can improve the throughput of the MAC layer. In some cases, a device can support simultaneous slot HARQ feedback, where the device can provide HARQ feedback for data received in previous symbols in a particular slot during that slot. In other cases, the device can provide HARQ feedback in a subsequent slot or according to other time intervals.

[0093] In some cases, the UE 115 may continuously monitor the communication link 125 (e.g., a wireless link) to obtain an indication that the UE 115 can receive data or perform data transmission. In other cases (e.g., for energy conservation and extended battery life), the UE 115 may be configured to have a discontinuous reception (DRX) cycle. The DRX cycle includes an "onDuration" (i.e., a wake-up period) during which the UE 115 can monitor (e.g., from the base station 105 and / or from another UE 115) communication and a "DRX period" during which the UE 115 can turn off the radio components. In some cases, the DRX cycle and / or continuous reception may be controlled by an internal timer. For example, when monitoring a scheduling message, the UE 115 may start a "DRX inactivity timer". If the scheduling message is successfully received, the UE 115 may be ready to receive data and the DRX inactivity timer may be reset. When the DRX inactivity timer expires without receiving a scheduling message, the UE 115 may suppress further monitoring of the remaining part of the DRX cycle (e.g., the UE 115 may turn off the radio components). Additionally or alternatively, the UE 115 may enter a short DRX cycle and may start a "DRX short cycle timer". When the DRX short cycle timer expires, the UE 115 may enter a long DRX cycle (e.g., turn off the radio components for a relatively long period). However, in some wireless communication systems, the use of such timers may be inefficient. For example, the inactivity timer may increase the likelihood that a UE in a group of UEs (e.g., communicating via the sidelink communication link 135) may not receive sidelink communication.

[0094] Accordingly, when communicating in a group of UEs, the wireless communication system 100 may support various energy conservation techniques. As an example, the UE 115 may be the group leader of the group of UEs (e.g., a UE 115 configured by an upper layer as the group leader, a UE 115 performing the group leader function for the group of UEs, or a combination thereof). The UE 115 may receive traffic information of other UEs 115 (e.g., from an upper layer, from other UEs 115, or both). The UE 115 may combine the received traffic information and determine the DRX configuration for the group of UEs. For example, the UE 115 may determine a DRX schedule indicating one or more DRX cycles for the group of UEs 115. In some cases, in addition to other operations, the UE 115 may broadcast the DRX configuration to the group of UEs 115, provide an acknowledgment message and / or an adjustment message to another UE 115 in response to a request included in the traffic information of another UE 115. The group leader UE 115 may enable the group of UEs 115 to reduce power consumption (e.g., compared to continuous monitoring) while maintaining reliable communication.

[0095] In some examples, other UEs 115 in the group of UEs 115 may be referred to as "member" UEs 115. Member UEs 115 may communicate with the group of UEs 115 using sidelink communication. Member UEs 115 may identify the group leader UE 115 (e.g., based on a notification from an upper layer, based on information from the AS layer to determine the group leader UE 115, or both). Member UEs 115 may provide traffic information (e.g., group member ID, transmission scheduling of member UEs 115, etc.) to the group leader UE 115 and / or the upper layer. In some examples, member UEs 115 may continuously monitor sidelink communication from the group of UEs 115. Member UEs 115 may receive DRX configuration from the group leader UE 115 (e.g., based on an announcement or multicast transmission from the group leader UE 115), and implement the DRX configuration to save energy. For example, the DRX configuration may include a DRX schedule that indicates that each member UE 115 of the group of UEs 115 may communicate during a wake-up period and turn off radio components during the DRX period of the DRX cycle. The DRX configuration may be used for a single DRX cycle or multiple DRX cycles.

[0096] One or more of the UEs 115 may include a UE communication manager 101, which may identify a schedule associated with the UE 115 and another UE 115 in a group of UEs 115 that communicates directly with the UE 115. The UE communication manager 101 may be an example of aspects of the UE communication manager 615 described herein. The schedule may include a wake-up period reserved for directed communication between the UE 115 and another UE 115 (e.g., a wake-up period reserved for unidirectional communication from the UE 115 to another UE 115, or a wake-up period reserved for bidirectional communication between the UE 115 and another UE 115, or a combination thereof). The UE communication manager 101 may manage the wake-up period reserved for directed communication (e.g., one or more of the wake-up periods reserved for unidirectional communication or bidirectional communication based on traffic information associated with the UE 115), and communicate with another UE 115 according to the management.

[0097] From an exemplary perspective of another UE 115, the UE communication manager 101 may also identify a schedule associated with the other UE 115 and the UE 115. The schedule may include a wake-up period reserved for directed communication between the other UE 115 and the UE 115 (e.g., a wake-up period reserved for unidirectional communication from the other UE 115 to the UE 115 or from the UE 115 to the other UE 115, or a wake-up period reserved for bidirectional communication between the other UE 115 and the UE 115, or a combination thereof). The UE communication manager 101 may manage the wake-up period reserved for directed communication (e.g., one or more of the wake-up periods reserved for unidirectional communication or the wake-up periods reserved for bidirectional communication) based on traffic information associated with the other UE 115 or the UE 115, and communicate with the UE 115 according to such management.

[0098] Figure 2 FIG. 4 shows an example of a wireless communication system 200 that supports D2D scheduling in accordance with aspects of the present disclosure. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100 and may include a set of UEs 115 (e.g., UEs 115-a, 115-b, and 115-c) and a base station 105-a, which may be examples of the UE 115 and the base station 105, respectively, as referenced Figure 1 described. In some cases, the set of UEs 115 may communicate with each other (e.g., in a V2X system, a D2D system, etc.) and may employ scheduling operations (e.g., associated with D2D communication) to conserve energy and ensure reliable communication.

[0099] According to some aspects, the set of UEs 115 may communicate with each other (or with another set of UEs 115) via sidelink communication 205 (e.g., using a P2P or D2D protocol). For example, UE 115-a may monitor a resource pool of sidelink communication 205 from UEs 115-b and 115-c and / or an indication of sidelink communication 205 (e.g., examples such as resource reservation, control channel transmission, etc.). Additionally or alternatively, the user equipment 115-a may have data to send to UEs 115-b and / or 115-c and may use sidelink communication 205 to send the data.

[0100] In some examples, in addition to the access link for communicating with base station 105-a, the group of UEs 115 may also utilize sidelink (e.g., sidelink communication 205). For example, one or more of the UEs 115 may be within the coverage area of base station 105-a (e.g., coverage area 110). In these examples, the UEs 115 may communicate with base station 105-a via the Uu interface (e.g., base station 105-a may send downlink communication 215 to one or more of the UEs 115). In some other examples, the group of UEs 115 may not be within the coverage area and / or may not use the access link to communicate with base station 105-a.

[0101] In some cases, communication between UEs 115 (or between a group of UEs 115 and another group of UEs 115) via sidelink communication 205 can be decentralized (e.g., P2P, D2D, direct, as opposed to via base station 105-a), and the UEs 115 can use predictions of future communication needs of the UEs 115 to implement a reservation scheme to schedule signal transmission between a UE 115 and other UEs 115 in the group of UEs 115. However, the demand prediction may not always be accurate, and the UEs 115 may inadvertently reserve more resources in the unicast link than required. Such inadvertent or unnecessary resource reservation may result in waste of communication resources, transmission delay due to reduced resource availability, and unnecessary power consumption due to the activity of the UEs 115 during the wake-up periods associated with the reservation.

[0102] Techniques are proposed for direct communication between UEs 115 (e.g., D2D communication), which can ensure reliable communication, efficient use of resources, and energy conservation. In one example, UE 115-a can identify a schedule associated with UE 115-b in the group of UEs 115 that is in direct communication with UE 115-a. The schedule may include a wake-up period reserved for directional communication between UE 115-a and UE 115-b (e.g., a wake-up period reserved for one-way communication from UE 115-a to UE 115-b, or a wake-up period reserved for two-way communication between UE 115-a and UE 115-b, or a combination thereof). UE 115-a can manage the wake-up period reserved for directional communication (e.g., one or more of the wake-up periods reserved for one-way communication or two-way communication) based on the traffic information associated with UE 115-a, and communicate with UE 115-b according to such management.

[0103] According to examples of aspects described herein, the UE 115 may utilize an update message 210 to manage wake-up periods reserved for directed communication (e.g., wake-up periods reserved for unidirectional or bidirectional communication). The update message 210 may include a request message or a response message. For example, the UE 115-a may send a request message to the UE 115-b based on traffic information associated with the UE 115-a and may receive a response message based on the request message from the UE 115-b. In some examples, the UE 115-a may manage the wake-up periods reserved for directed communication (e.g., one or more of the wake-up periods reserved for unidirectional or bidirectional communication) based on the response message.

[0104] From an exemplary perspective of the UE 115-b, the UE 115-b may also identify a schedule associated with the UE 115-b and the UE 115-a. The schedule may include wake-up periods reserved for directed communication between the UE 115-b and the UE 115-a (e.g., wake-up periods reserved for unidirectional communication from the UE 115-b to the UE 115-a or from the UE 115-a to the UE 115-b, or wake-up periods reserved for bidirectional communication between the UE 115-b and the UE 115-a, or a combination thereof). The UE 115-b may manage based on traffic information associated with the UE 115-b or the UE 115-a and communicate with the UE 115-a according to the management.

[0105] According to examples of aspects described herein, the UE 115-b may receive an update message 210 (e.g., a request message) from the UE 115-a and may send an update message 210 (e.g., a response message) to the UE 115-a based on the request message and traffic information associated with the UE 115-b. In some examples, the UE 115-b may manage the wake-up periods reserved for directed communication (e.g., one or more of the wake-up periods reserved for unidirectional communication or wake-up periods reserved for bidirectional communication) based on the request message and traffic information associated with the UE 115-b.

[0106] Figure 3 An example of a wireless system 300 that supports a method for scheduling in an inactive case in sidelink unicast according to aspects of the present disclosure is shown. In some examples, the wireless system 300 may implement aspects of the system 100 and the system 200 as described herein with reference to Figure 1 and Figure 2 described. The wireless system 300 may include UEs 115 (e.g., UEs 115-d to 115-i), which may be examples of aspects of the UE 115 and the UEs 115-a to 115-c as described herein with reference to Figure 1 and Figure 2 described.

[0107] Figure 3 shows an example in which UE 115 can communicate directly with other UEs 115. In this example, UE 115-d can communicate directly (e.g., using P2P or D2D protocols) with UEs 115-e to 115-i. For example, UE 115-d can communicate directly with UE 115-e (e.g., as shown by the solid line), and can communicate directly with any one of UEs 115-f to 115-i (e.g., as shown by the dashed line). Sidelink communication 305 and update message 310 can be examples of aspects of sidelink communication 205 and update message 210 as described herein with reference to Figure 2 described. Communication link 315 can include sidelink communication 305. In some examples, communication link 315 can include directed communication between a UE and another UE 115. For example, communication link 315 can include unidirectional communication from a UE 115 to another UE 115 or bidirectional communication between a UE 115 and another UE 115 (e.g., unidirectional communication from UE 115-d to UE 115-e or bidirectional communication between UE 115-d and UE 115-e).

[0108] In some wireless systems, direct communication (e.g., P2P, D2D) between UEs 115 can be decentralized (e.g., lacking centralized control of MAC scheduling for example by base station 105 or 105-a). For example, in direct communication, conflicts associated with half-duplex communication can be resolved in the scheduling. For example, half-duplex communication can utilize unidirectional communication via transmission or reception (but not simultaneous transmission and reception), and if another UE 115 is not in the receive (RX) state, UE 115 (e.g., UE 115-d) may not be able to send to another UE 115 (e.g., any one of UEs 115-e to 115-i).

[0109] In the mmW spectrum, communication collisions may increase. For example, if another UE 115 is not in the RX state in a particular beam direction (e.g., the RX beam direction associated with the TX beam direction of UE 115), UE 115 (e.g., UE115-d) may not be able to send to another UE 115 (e.g., any one of UE 115-e to UE 115-i). For example, for communication in the mmW spectrum, the complexity associated with scheduling multiple direct communications (e.g., D2D links) in different directions may be much higher compared to other spectrums. For example, for communication in the mmW spectrum, if UE 115-d is communicating with UE 115-e and wishes to communicate with another UE 115 (e.g., UE 115-f), due to beam management, UE 115-d may not be able to simply resume the existing schedule between UE 115-d and UE 115-e and start sending to UE 115-f. In mmW communication, UE115-d may not be able to freely modify the schedule based on the availability of the peer UE 115 (e.g., UE 115-f).

[0110] For example, for the mmW spectrum, contention-based access may be insufficient (e.g., for successful communication transmissions) because sensing in contention-based access may be limited in direction. Additionally, due to beam scanning, the cost of sending or receiving "random access" control signals (e.g., random access signaling) may be high. Thus, for example, communication resources can be better met (e.g., utilized) on a reservation basis, such that UE scheduling (e.g., the scheduling of UE 115) can be more deterministic.

[0111] For example, similar to DRX cycles and DRX handling, beam unavailability in a beam direction (e.g., "beam direction unavailable") may have a similar effect on UE scheduling as DRX. In some examples, peer UEs 115 on a unicast link (e.g., UE 115-d and UE 115-e communicating via sidelink communication 305) may negotiate a corresponding "onDuration" period (e.g., wake-up period) for communication. In some examples, outside the "onDuration" period associated with a unicast link, UE 115-d and UE 115-e may not have to be available for the unicast link. For example, outside the "onDuration" period associated with the unicast link between UE 115-d and UE 115-e, UE 115-d and UE 115-e may be available for communication (e.g., unicast links) with other UEs 115 in the group (e.g., UE 115-f to UE 115-i) or another group of UEs.

[0112] According to examples in various aspects of this document, the UE 115 can determine the length of the "onDuration" (e.g., wake-up period) based on the amount of resources required for the UE 115's services (e.g., time slots, cycles). In some examples, the UE 115 can determine the length of the "onDuration" based on the service requirements associated with communication with other devices (e.g., other UEs 115 in a UE group or other UE groups). For example, the UE 115-d can determine the length of the "onDuration" based on the amount of resources required for the services between the UE 115-d and any one of the UEs 115-e to 115-i. In some examples, the "onDuration" can include a duty cycle.

[0113] In some examples, based on a prediction of the service requirements associated with the UE 115 (e.g., services between the UE 115 and other UEs 115 in the UE group or another UE group), the UE 115 can reserve the "onDuration" (e.g., wake-up period, resources associated with the wake-up period) for communication with another UE 115. However, the predicted service requirements may be inaccurate. For example, the UE 115 may overestimate or underestimate the service requirements (e.g., overestimate or underestimate the amount of resources the UE 115 may use for communication).

[0114] According to examples in various aspects of this document, based on service requirements or a prediction of service requirements, the UE 115 can manage (e.g., modify, maintain, or remove) the reserved "onDuration" (e.g., wake-up period) associated with communication (e.g., directed communication) between the UE 115 and other UEs 115. In one example, based on service requirements or a prediction of service requirements, the UE 115 can modify, maintain, or remove the reserved "onDuration" associated with communication between the UE 115 and other UEs 115. For example, the UE 115-d can modify, maintain, or remove the reserved "onDuration" associated with communication (e.g., directed communication) between the UE 115-d and any one of the UEs 115-e to 115-i based on service requirements or a prediction of service requirements.

[0115] According to examples of the aspects described in this document, the UE 115 can use the update message 310 to manage the "onDuration". The update message 310 can include a request message or a response message. For example, the UE 115-d can send a request message to the UE 115-e based on the service information associated with the UE 115-d and can receive a response message based on the request message from the UE 115-e.

[0116] In one example, the UE 115 may provide or include a cause (e.g., a reason indication) in a request message. For example, the UE 115-d may indicate in a request message the absence of traffic (e.g., inactivity) associated with the communication link 315 (e.g., sidelink communication 305) between the UE 115-d and the UE 115-e. In some examples, the UE 115-d may indicate in a request message the inactivity associated with the directed communication between the UE 115-d and the UE 115-e based on the traffic information associated with the UE 115-d. For example, the UE 115-d may indicate in a request message the inactivity associated with the unidirectional communication from the UE 115-d to the UE 115-e based on the traffic information associated with the UE 115-d. In some examples, the UE 115-d may indicate in a request message the inactivity associated with the bidirectional communication between the UE 115-d and the UE 115-e based on the traffic information associated with the UE 115-d.

[0117] In some examples, the UE 115-d may indicate in a request message that the UE 115-d will service other links (e.g., other communication links 315, sidelink communication 305) for more time than the allocated scheduled "onDuration", and can no longer guarantee the "onDuration" on the directed link (e.g., the communication link 315 between the UE 115-d and the UE 115-e, sidelink communication 305). In some examples, the UE 115-d may indicate in a request message that the UE 115-d is handling more traffic than the UE 115-d expected or predicted. For example, the UE 115-d may determine that the traffic load associated with the UE 115-d meets a threshold (e.g., exceeds the expected traffic load).

[0118] Figure 4 Examples of a timing diagram 405 and a timing diagram 410 illustrating a method for supporting scheduling in the case of inactivity in sidelink unicast according to aspects of the present disclosure are shown. In some examples, the timing diagrams 405 and 410 may implement aspects of the systems 100, 200, and 300 described herein with reference to Figure 1 , Figure 2 and Figure 3 The timing diagram 405 and the timing diagram 410 illustrate examples of aspects of the "onDuration" period (e.g., wake-up period) of scheduling associated with bidirectional and unidirectional communications between a UE A (e.g., the UE 115-d) and additional UEs, UE B1, UE B2, and UE B3 (e.g., the UEs 115-e to 115-g).

[0119] Timing diagram 405 shows an example of two-way communication scheduling, where UE A can share the same traffic "onDuration" period with UE B1, UE B2, and UE B3 in either direction (e.g., from UE A to UE B1, or from UE B1 to UE A). For example, "onDuration" 425 (e.g., B1) can correspond to the wake-up period associated with two-way communication between UE A and UE B1, "onDuration" period 430 (e.g., B2) can correspond to the wake-up period associated with two-way communication between UE A and UE B2, and "onDuration" period 435 (e.g., B3) can correspond to the wake-up period associated with two-way communication between UE A and UE B3.

[0120] Timing diagram 410 shows an example of one-way communication scheduling, where, for a peer UE transmitting to another peer UE, separate "onDuration" periods can be reserved for traffic in different directions. For example, for UE A and UE B1 (e.g., any one of UE B1, UE B2, or UE B3), UE A can have a separate "onDuration" period for traffic in the direction from UE A to UE B1, and UE B1 can have a separate "onDuration" period for traffic in the direction from UE B1 to UE A. For example, "onDuration" period 440 (e.g., B1 TX) can correspond to the wake-up period reserved for one-way communication from UE A to UE B1 (e.g., rather than from UE B1 to UE A), "onDuration" period 445 (e.g., B2 RX) can correspond to the wake-up period reserved for one-way communication from UE B2 to UE A (e.g., rather than from UE A to UE B2), and "onDuration" period 450 (e.g., B3 TX) can correspond to the wake-up period reserved for one-way communication from UE A to UE B3 (e.g., rather than from UE B3 to UE A).

[0121] Examples according to aspects described herein, such as the wireless communication systems 100, 200, and 300 described herein (e.g., UE 115 communicating directly with each other), can use two-way scheduling, one-way scheduling, or a combination thereof in one or more hybrid manners. In some examples, the wireless communication systems 100, 200, and 300 can combine directional scheduling (e.g., two-way scheduling and one-way scheduling) in sub-6 GHz and mmW communications. Examples of using signaling messages to adjust aspects of communication scheduling based on inactivity are referred to herein Figure 4 , UE A (e.g., which can correspond to Figure 3UE 115-d), as well as additional UEs, UE B1, UE B2, and UE B3 (e.g., which may correspond to Figure 3 UEs 115-e through 115-g). According to examples of various aspects herein, UE A may perform a scheduling update for directed communication (e.g., one-way communication and two-way communication).

[0122] As described herein with respect to the exemplary one-way scheduling in timing diagram 405, an "ON" time slot (e.g., an "onDuration" period, a wake-up period) may be reserved for both directions from UE 115 to another UE 115 and from another UE 115 to UE 115 (e.g., the "onDuration" period 425 (e.g., B1) may correspond to a wake-up period reserved for two-way communication from UE B1 to UE A and from UE B1 to UE A). In one example, UE A (e.g., UE 115-d) may send a request message to UE B1 (e.g., UE 115-e) to adjust the two-way scheduling for the "onDuration" period (e.g., the "onDuration" period 425) associated with UE A and UE B1. For example, UE A may no longer have traffic (e.g., no longer have traffic associated with the communication link between UE A and UE B1, e.g., inactivity associated with the transmission from UE A to UE B1), and UE A may request in the request message to delete the "onDuration" occurrence (e.g., the "onDuration" period 425).

[0123] UE B1 may send a response message to UE A to accept or reject the request. In one example, UE B1 may still have traffic associated with the communication link between UE A and UE B1, e.g., traffic associated with the transmission from UE B1 to UE A. Based on the response message, UE A (e.g., and UE B1) may maintain the "onDuration" period 425. For example, UE A and UE B1 may modify (e.g., transform) the "onDuration" period 425 from the "onDuration" period for two-way communication (e.g., communication from UE B1 to UE A and communication from UE B1 to UE A) to the "onDuration" period for one-way communication (e.g., from UE B1 to UE A). In some examples, since the traffic requirements associated with the modified "onDuration" may be reduced (e.g., reduced by half, based only on the one-way communication from UE B1 to UE A), UE A (e.g., and UE B1) may adjust the duration (e.g., the time slot size) of the "onDuration" period.

[0124] In some examples, if UE B1 no longer has traffic (e.g., no longer has traffic associated with a modified "onDuration" period of one-way communication from UE B1 to UE A), then UE B1 can send a request message to UE A to delete the "onDuration" period. Aspects of the request message can be as described herein for the "one-way" case of releasing a time slot (e.g., deleting the "onDuration" period associated with one-way communication). Further, as described herein for the exemplary one-way scheduling in timing diagram 410, an "on" time slot (e.g., an "onDuration" period, a wake-up period) can be reserved for the direction from UE 115 to another UE 115, rather than from another UE 115 to UE 115 (e.g., the "onDuration" period 440 (e.g., B1 TX) can correspond to a wake-up period reserved for one-way communication from UE B1 to UE A, rather than a wake-up period reserved for one-way communication from UE A to UE B1).

[0125] In one example, UE A (e.g., UE 115-d) can send a request message to UE B1 (e.g., UE 115-e) to adjust the one-way scheduling for the "onDuration" period of "TX B" (e.g., the "onDuration" period 440). For example, UE A may no longer have traffic (e.g., no longer has traffic associated with the communication link between UE A and UE B1), and UE A can request in the request message to delete the "onDuration" occurrence (e.g., the "onDuration" period 440).

[0126] According to examples in various aspects of this document, UE A (e.g., UE 115-d) may request deletion of an "onDuration" occurrence (e.g., "onDuration" period 440) associated with "fast change" or "slow change". In one example, UE A may signal inactivity with reference to an original negotiated schedule between UE A and UE B1 (e.g., UE 115-e). UE A may signal the inactivity duration relative to the original negotiated schedule. In an example of "fast change", UE A may include in a request message a request to delete or modify the "onDuration" period 440 (e.g., B1 Tx) for a single period T or multiple periods T starting from or after the current period T, after which UE A and UE B1 may resume communication according to the originally negotiated schedule. In another example of "fast change", UE A may include in a request message a request to delete or modify the "onDuration" period 440 for all periods T starting from or after the current period T (e.g., release of a unicast link between UE A and UE B1). In an example of "slow change", UE A may migrate or renegotiate the deletion or modification of the "onDuration" period 440 over multiple periods T (e.g., on a separate signal or request message sent from UE A to UE B1). According to examples of aspects described in this document, UE A may no longer have traffic or communication associated with communication from UE A to UE B1 and from UE B1 to UE A. In these examples, UE A may include in a request message a request to release the unicast link between UE A and UE B1, which may disassociate all "onDuration" time slots or periods of "TX A / B" (e.g., "onDuration" period 440) from "RX A / B" (not shown).

[0127] Figure 5 FIG. 500 shows an example of a process flow of a method that supports scheduling in the case of inactivity in sidelink unicast according to various aspects of the present disclosure. The process flow 500 may show an exemplary scheduling scheme (e.g., D2D scheduling) between UEs 115 of a wireless system. For example, UEs 115-j and 115-k may perform a scheduling process for an "onDuration" period (e.g., a wake-up period) associated with unidirectional or bidirectional communication.

[0128] UEs 115-j and 115-k may be reference Figures 1 to 4Examples of corresponding wireless devices are described. For example, UE 115-j and UE 115-k may communicate directly with each other (e.g., D2D communication). In some cases, either UE 115-j or UE 115-k may initiate an exemplary scheduling process (e.g., send a request message or a response message). The following alternative examples may be implemented, where some steps are performed in a different order than described or not performed at all. In some cases, the steps may include additional features not mentioned below, or further steps may be added.

[0129] At 505, UE 115-j may identify a schedule associated with UE 115-j and UE 115-k. The schedule may include a wake-up period reserved for directed communication between UE 115-j and UE 115-k (e.g., a wake-up period reserved for unidirectional communication from UE 115-j to UE 115-k, or a wake-up period reserved for bidirectional communication between UE 115-j and UE 115-k, or a combination thereof). At 510, UE 115-k may identify a schedule associated with UE 115-k and UE 115-j. The schedule may include a wake-up period reserved for directed communication between UE 115-k and UE 115-j (e.g., a wake-up period reserved for unidirectional communication from UE 115-k to UE 115-j or from UE 115-j to UE 115-k, or a wake-up period reserved for bidirectional communication between UE 115-k and UE 115-j, or a combination thereof). At 515, UE 115-j may send a request message to UE 115-k. UE 115-j may send the request message based on traffic information associated with UE 115-j. According to examples of aspects described herein, UE 115-j sends the request message via UE signaling. For example, UE signaling may include a PC5-RRC message (e.g., option 1) or a MAC control element (MAC CE) message (e.g., option 2). In an example where the request message is a PC5-RRC message, the request message may include a cause indication determined by UE 115-j (e.g., a reason for change). For example, the cause indication may include inactivity associated with directed communication (e.g., one or more of unidirectional or bidirectional communication), or a traffic load at UE 115-j that meets a threshold (e.g., a traffic load that exceeds an expected traffic load).

[0130] In one example, the request message may include an impact period (e.g., the number of cycles T associated with the change). For example, the impact period may include the number of cycles associated with modifying the wake-up period reserved for directed communication (e.g., one or more of the wake-up periods reserved for unidirectional communication or the wake-up periods reserved for bidirectional communication). In some examples, the request message may include a suggested size for the new wake-up period. For example, the size may include the duration (e.g., the adjusted duration) of the wake-up period reserved for directed communication (e.g., one or more of the wake-up periods reserved for unidirectional communication or bidirectional communication). In some examples, UE 115-j may assign bit values to fields in the request message. In one example, where the bit value may correspond to the duration of the wake-up period reserved for unidirectional communication, UE 115-j may assign a zero bit value. In another example, where the bit value may correspond to the duration of the wake-up period reserved for bidirectional communication, UE 115-j may assign a non-zero value.

[0131] At 520, UE 115-k may send a response message to UE 115-j. UE 115-k may send the request message based on traffic information associated with UE 115-k or UE 115-j. According to examples of aspects described herein, UE 115-k may send the response message via UE signaling described herein. For example, the UE signaling may include a PC5-RRC message (e.g., option 1) or a MAC control element (MAC CE) message (e.g., option 2). In one example, where the response message is a PC5-RRC message, the response message may include a response code (e.g., accept, reject). For example, if accepted, the response message may include an acknowledgement (e.g., accept) associated with the request message. In another example, the response message may include a negative acknowledgement (e.g., reject) associated with the request message.

[0132] In one example, in the case where the response message includes a negative acknowledgment, the response message may include the reason for the negative acknowledgment (e.g., a cause indication for the negative acknowledgment). For example, based on the inactivity determined by UE 115-j in connection with the transmission from UE 115-j to UE 115-k, UE 115-j may send a request message to UE 115-k to modify the wake-up period reserved for the directed communication (e.g., two-way communication between UE 115-j and UE 115-k) between UE 115-j and UE 115-k. In one example, where UE 115-k may still have traffic associated with the transmission from UE 115-j to UE 115-k, UE 115-k may send a response message including a negative acknowledgment. In some examples, the response message may include an additional action. For example, the response message may include an indication of an idle time slot, e.g., indicating that there is no activity in the reverse direction (e.g., from UE 115-k to UE 115-j). In some examples, the signaling may be extended to increase the size (e.g., duration, number of time slots) of the wake-up period reserved for the directed communication (e.g., one or more of the wake-up periods reserved for unidirectional communication or for two-way communication).

[0133] At 525, UE 115-j may manage the wake-up period reserved for the directed communication (e.g., one or more of the wake-up periods reserved for unidirectional communication or for two-way communication) based on the traffic information associated with UE 115-j or the response message. At 530, UE 115-k may manage the wake-up period reserved for the directed communication (e.g., one or more of the wake-up periods reserved for unidirectional communication or for two-way communication) based on the traffic information associated with UE 115-k or UE 115-j or based on the request message. At 535, UE 115-j and UE 115-k may communicate with each other according to the management. According to an example of an aspect herein, where the described UE signaling includes using a MAC CE message, an example of an aspect of process flow 500 may be similar. However, the overall message size (e.g., UE signaling, request message, response message) may be limited. In some examples, process flow 500 may include the aggregation of the MAC-CE message and the data being transmitted.

[0134] Figure 6 Block diagram 600 of a device 605 showing a method for supporting scheduling in the case of inactivity in sidelink unicast according to aspects of the present disclosure is shown. Device 605 may be an example of aspects of UE 115 as described herein. Device 605 may include a receiver 610, a UE communication manager 615, and a transmitter 620. Device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0135] The receiver 610 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to methods for scheduling in the sidelink unicast non-active case). The information can be passed to other components of the device 605. The receiver 610 can be an example of an aspect of the transceiver 920 described in the reference Figure 9 The receiver 610 can use a single antenna or an antenna array.

[0136] The UE communication manager 615 can identify a schedule associated with the device 605 and an additional device in a group of devices that communicate directly with the device 605, where the schedule includes a wake-up period reserved for directed communication between the device 605 and the additional device (e.g., a wake-up period reserved for unidirectional communication from the device 605 to the additional device, or a wake-up period reserved for bidirectional communication between the device 605 and the additional device, or a combination thereof). The UE communication manager 615 can manage the wake-up period reserved for directed communication (e.g., one or more of the wake-up periods reserved for unidirectional communication or bidirectional communication) based on traffic information associated with the device 605, and communicate with the additional device according to this management.

[0137] The UE communication manager 615 can also identify a schedule associated with the device 605 and an additional device in the group of devices that communicate directly with the device 605, where the schedule includes a wake-up period reserved for directed communication between the device 605 and the additional device (e.g., a wake-up period reserved for unidirectional communication from the device 605 to the additional device or from the additional device to the device 605, or a wake-up period reserved for bidirectional communication between the device 605 and the additional device, or a combination thereof); manage the wake-up period reserved for directed communication (e.g., one or more of the wake-up periods reserved for unidirectional communication or bidirectional communication) based on traffic information associated with the device 605 or the additional device; and communicate with the additional device according to this management. The UE communication manager 615 can be an example of aspects of the UE communication manager 910 described herein.

[0138] The UE communication manager 615 or its sub-components can be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the UE communication manager 615 or its sub-components can be performed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0139] The UE communication manager 615 or its sub-components may be physically located in different positions, including being distributed such that some functions are implemented by one or more physical components at different physical locations. In some examples, in accordance with various aspects of the present disclosure, the UE communication manager 615 or its sub-components may be separate and distinct components. In some examples, in accordance with various aspects of the present disclosure, the UE communication manager 615 or its sub-components may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in the present disclosure, or a combination thereof.

[0140] The transmitter 620 may transmit signals generated by other components of the device 605. In some examples, the transmitter 620 may be collocated with the receiver 610 in a transceiver module. For example, the transmitter 620 may be an example of aspects of the transceiver 920 described in Figure 9 reference. The transmitter 620 may utilize a single antenna or an antenna array.

[0141] Figure 7 FIG. 700 is a block diagram of a device 705 that illustrates a method for supporting scheduling in an inactive scenario in sidelink unicast in accordance with various aspects of the present disclosure. The device 705 may be an example of aspects of the device 605 or the UE 115 described herein. The device 705 may include a receiver 710, a UE communication manager 715, and a transmitter 735. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0142] The receiver 710 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to a method for scheduling in an inactive scenario in sidelink unicast). The information may be passed to other components of the device 705. The receiver 710 may be an example of aspects of the transceiver 920 described in Figure 9 reference. The receiver 710 may use a single antenna or an antenna array.

[0143] The UE communication manager 715 may be an example of aspects of the UE communication manager 615 described herein. The UE communication manager 715 may include a scheduling component 720, a management component 725, and a communication component 730. The UE communication manager 715 may be an example of aspects of the UE communication manager 910 described herein.

[0144] The scheduling component 720 may identify a schedule associated with the device 705 and additional devices in a group of devices that communicate directly with the device 705, where the schedule includes wake-up periods reserved for directed communication between the device 705 and the additional devices (e.g., a wake-up period reserved for unidirectional communication from the device 705 to the additional devices, or a wake-up period reserved for bidirectional communication between the device 705 and the additional devices, or a combination thereof). In some examples, the scheduling component 720 may identify a schedule associated with the additional devices and the device 705 in the group of devices that communicate directly with the additional devices, where the schedule includes wake-up periods reserved for directed communication between the device 705 and the additional devices (e.g., a wake-up period reserved for unidirectional communication from the additional devices to the device 705 or from the device 705 to the additional devices, or a wake-up period reserved for bidirectional communication between the additional devices and the device 705, or a combination thereof).

[0145] The management component 725 may manage the wake-up periods reserved for directed communication (e.g., one or more of the wake-up periods reserved for unidirectional communication or the wake-up periods reserved for bidirectional communication) based on the traffic information associated with the device 705. In some examples, the management component 725 may manage the wake-up periods reserved for directed communication based on the traffic information associated with the additional devices or the device 705. The communication component 730 may communicate with the additional devices according to this management. In some examples, the communication component 730 may communicate with the device according to this management.

[0146] The transmitter 735 may transmit signals generated by other components of the device 705. In some examples, the transmitter 735 may be collocated with the receiver 710 in the transceiver module. For example, the transmitter 735 may be an example of an aspect of the transceiver 920 described in Figure 9 reference. The transmitter 735 may utilize a single antenna or an antenna array.

[0147] Figure 8 FIG. 800 is a block diagram of a UE communication manager 805 that illustrates a method for supporting scheduling in an inactive scenario in sidelink unicast according to aspects of the present disclosure. The UE communication manager 805 may be an example of an aspect of the UE communication manager 615, the UE communication manager 715, or the UE communication manager 910 described herein. The UE communication manager 805 may include a scheduling component 810, a management component 815, a communication component 820, a messaging component 825, a traffic component 830, a bit value component 835, an acknowledgment component 840, and a termination component 845. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0148] The scheduling component 810 may identify a schedule associated with a device and additional devices in a group of devices that communicate directly with the device, where the schedule includes a wake-up period reserved for directed communication between the device and the additional devices (e.g., a wake-up period reserved for unidirectional communication from the device to the additional devices, or a wake-up period reserved for bidirectional communication between the device and the additional devices, or a combination thereof). In some examples, the scheduling component 810 may identify a schedule associated with an additional device and a device in the group of devices that communicate directly with the additional device, where the schedule includes a wake-up period reserved for directed communication (e.g., a wake-up period reserved for unidirectional communication from the additional device to the device or from the device to the additional device, or a wake-up period reserved for bidirectional communication between the additional device and the device, or a combination thereof). In some examples, the scheduling component 810 may determine inactivity associated with a wake-up period reserved for directed communication (e.g., one or more of unidirectional communication or bidirectional communication) based on traffic information.

[0149] The management component 815 may manage a wake-up period reserved for directed communication (e.g., one or more of a wake-up period reserved for unidirectional communication or a wake-up period reserved for bidirectional communication based on traffic information associated with the device). In some examples, the management component 815 may manage a wake-up period reserved for directed communication (e.g., one or more of a wake-up period reserved for unidirectional communication or a wake-up period reserved for bidirectional communication) based on traffic information associated with the additional device or the device. In some examples, the management component 815 may manage a wake-up period reserved for directed communication based on a response message. In some examples, the management component 815 may manage a wake-up period reserved for directed communication based on inactivity.

[0150] In some examples, the management component 815 may manage a wake-up period reserved for directed communication (e.g., one or more of a wake-up period reserved for unidirectional communication or a wake-up period reserved for bidirectional communication) based on a traffic load meeting a threshold. In some examples, the management component 815 may manage a wake-up period reserved for directed communication based on a comparison. In some examples, the management component 815 may release one or more resources associated with a wake-up period reserved for unidirectional communication based on a response message. In some examples, the management component 815 may adjust the duration of a wake-up period reserved for unidirectional communication based on a response message. In some examples, the management component 815 may release one or more resources associated with a wake-up period reserved for directed communication (e.g., bidirectional communication) based on a response message.

[0151] In some examples, the management component 815 can adjust the duration of the wake-up period reserved for directed communication (e.g., two-way communication) based on the response message. In some examples, the management component 815 can specifically allocate the wake-up period reserved for directed communication (e.g., two-way communication) to an additional device based on the response message. In some examples, the management component 815 can release one or more resources associated with the wake-up period reserved for one-way communication from the slave device to the additional device based on termination. In some examples, the management component 815 can specifically allocate the wake-up period reserved for directed communication (e.g., two-way communication) to an additional device based on an indication received from the slave device.

[0152] In some examples, the management component 815 can manage the wake-up period reserved for directed communication (e.g., one or more of the wake-up periods reserved for one-way communication or two-way communication) based on the request message and the traffic information associated with the additional device. In some examples, the management component 815 can manage the wake-up period reserved for directed communication based on the inactivity associated with the directed communication between the device and the additional device (e.g., one or more of the following: the inactivity associated with one-way communication from the slave device to the additional device, the inactivity associated with one-way communication from the additional device to the device, or the inactivity associated with two-way communication). In some examples, the management component 815 can manage the wake-up period reserved for directed communication based on the inactivity associated with the directed communication (e.g., the inactivity associated with one-way communication from the slave device to the additional device).

[0153] In some examples, the management component 815 can release one or more resources associated with the wake-up period reserved for directed communication (e.g., one-way communication) based on the request message and the traffic information. In some examples, the management component 815 can adjust the duration of one or more of the wake-up periods reserved for directed communication (e.g., one-way communication from the additional device to the device or the wake-up period reserved for one-way communication from the slave device to the additional device) based on the request message and the traffic information. In some examples, the management component 815 can release one or more resources associated with the wake-up period reserved for directed communication (e.g., two-way communication) based on the request message and the traffic information. In some examples, the management component 815 can adjust the duration of the wake-up period reserved for directed communication (e.g., two-way communication) based on the response message and the traffic information.

[0154] In some examples, the management component 815 may specifically allocate the wake-up periods reserved for directed communication (e.g., two-way communication) to additional devices based on the request message and service information. In some examples, the management component 815 may release one or more resources associated with the wake-up periods reserved for directed communication (e.g., one-way communication from an additional device to a device) based on termination. In some examples, the management component 815 may specifically allocate the wake-up periods reserved for directed communication (e.g., two-way communication) to a device based on the service information associated with the additional device or the device.

[0155] The communication component 820 may communicate with the additional device according to this management. In some examples, the communication component 820 may communicate with the additional device based on releasing one or more resources associated with the wake-up periods reserved for one-way communication. In some cases, the wake-up periods reserved for directed communication (e.g., two-way communication) are shared between the device and the additional device. In some cases, the wake-up periods reserved for directed communication (e.g., one-way communication) are not shared between the device and the additional device.

[0156] In some examples, the communication component 820 may communicate with the additional UE based on termination. In some examples, the communication component 820 may communicate with the additional device based on an indication to modify the wake-up periods reserved for directed communication (e.g., one-way communication). In some cases, the communication component 820 may communicate with the additional device based on adjusting the duration of the wake-up periods reserved for directed communication (e.g., one-way communication). In some examples, the communication component 820 may communicate with the additional device based on an indication to remove the wake-up periods reserved for directed communication (e.g., two-way communication). In some cases, the communication component 820 may communicate with the additional device based on releasing one or more resources associated with the wake-up periods reserved for directed communication (e.g., two-way communication). In some examples, the communication component 820 may communicate with the additional device based on an indication to adjust the wake-up periods reserved for directed communication (e.g., two-way communication). In some cases, the communication component 820 may communicate with the additional device based on adjusting the duration of the wake-up periods reserved for directed communication (e.g., two-way communication).

[0157] In some examples, communication component 820 may communicate with an additional device based on an indication that a wake-up period reserved for directed communication (e.g., two-way communication) is specifically allocated to the additional device. In some cases, communication component 820 may communicate with an additional device based on a wake-up period reserved for directed communication (e.g., two-way communication) being specifically allocated to the additional device. In some examples, communication component 820 may communicate with an additional device based on an indication that a wake-up period reserved for directed communication (e.g., two-way communication) is specifically allocated to a device. In some cases, communication component 820 may communicate with an additional device based on a wake-up period reserved for directed communication (e.g., two-way communication) being specifically allocated to a device. In some examples, communication component 820 may communicate with an additional device based on an acknowledgement. In some examples, communication component 820 may communicate with an additional device based on one or more of a negative acknowledgement or an indication of the reason for the negative acknowledgement.

[0158] In some examples, communication component 820 may communicate with a device according to this management. In some examples, communication component 820 may communicate with a third device in the group of devices based on managing a wake-up period reserved for directed communication (e.g., a wake-up period reserved for one-way communication or one or more of the wake-up periods reserved for two-way communication). In some examples, communication component 820 may communicate with a device based on one or more of releasing one or more resources associated with a wake-up period reserved for directed communication (e.g., one-way communication) and a response message. In some cases, a wake-up period reserved for directed communication (e.g., two-way communication) is shared between an additional device and a device.

[0159] In some examples, communication component 820 may communicate with an additional device based on an indication that a wake-up period reserved for directed communication (e.g., two-way communication) is specifically allocated to the additional device. In some cases, communication component 820 may communicate with a device based on the indication or based on a wake-up period reserved for directed communication (e.g., two-way communication) being specifically allocated to the additional device. In some examples, communication component 820 may communicate with an additional device based on an indication that adjusts the duration of a wake-up period reserved for directed communication (e.g., one-way communication). In some cases, communication component 820 may communicate with a device based on one or more of adjusting the duration of a wake-up period reserved for directed communication (e.g., one or more of the wake-up periods reserved for one-way communication) and a response message. In some examples, communication component 820 may communicate with a device based on one or more of releasing one or more resources associated with a wake-up period reserved for directed communication (e.g., two-way communication) and a response message.

[0160] In some examples, the communication component 820 may communicate with a device based on one or more of the duration of a wake-up period reserved for directed communication (e.g., two-way communication) and a response message. In some examples, the communication component 820 may communicate with a device based on specifically allocating the wake-up period reserved for directed communication (e.g., two-way communication) to an additional device and a response message. In some examples, the communication component 820 may communicate with a device based on specifically allocating the wake-up period reserved for directed communication (e.g., two-way communication) to the device. In some examples, the communication component 820 may communicate with a device based on an acknowledgement. In some examples, the communication component 820 may communicate with a device based on one or more of a negative acknowledgement or an indication of the reason for the negative acknowledgement.

[0161] The messaging component 825 may send a request message to an additional device based on service information associated with the device. In some examples, the messaging component 825 may receive a response message from the additional device based on the request message. In some examples, the messaging component 825 may be based on determining that a reason indication is included in the request message, the reason indication indicating inactivity. In some examples, the messaging component 825 may be based on determining that a reason indication is included in the request message, the reason indication indicating that the service payload associated with the device meets a threshold. In some examples, the messaging component 825 may include an indication of removing the wake-up period reserved for directed communication (e.g., one-way communication) in the request message based on the service information.

[0162] In some examples, the messaging component 825 may include an indication of modifying the wake-up period reserved for directed communication (e.g., one-way communication) in the request message based on the service information. In some examples, the messaging component 825 may include an indication of removing the wake-up period reserved for directed communication (e.g., two-way communication) in the request message based on the service information. In some examples, the messaging component 825 may include an indication of modifying the wake-up period reserved for directed communication (e.g., two-way communication) in the request message based on the service information. In some examples, the messaging component 825 may include an indication of specifically allocating the wake-up period reserved for directed communication (e.g., two-way communication) to an additional device in the request message based on the service information. In some examples, the messaging component 825 may receive an indication of specifically allocating the wake-up period reserved for directed communication (e.g., two-way communication) to the device from the additional device.

[0163] In some cases, one or more of the request message or the response message are PC5 radio resource control messages. In some cases, one or more of the request message or the response message are media access control-control element messages. In some cases, the request message includes an indication of the number of periods associated with a wake-up period reserved for sidelink communication. In some cases, the cause indication includes traffic information associated with an additional device or the amount of available resources associated with the additional device for allocation to a device for sidelink communication (e.g., two-way communication).

[0164] In some examples, the messaging component 825 may receive a request message from a device, the request message including traffic information associated with the device. In some examples, the messaging component 825 may send a response message to the device based on the request message and traffic information associated with an additional device. In some examples, the messaging component 825 may identify, in the request message, an indication to remove a wake-up period reserved for sidelink communication (e.g., one-way communication). In some examples, the messaging component 825 may include, in the response message, an acknowledgement associated with releasing one or more resources associated with a wake-up period reserved for sidelink communication (e.g., one-way communication). In some examples, the messaging component 825 may identify, in the request message, an indication to modify a wake-up period reserved for sidelink communication (e.g., one-way communication).

[0165] In some examples, the messaging component 825 may include, in the response message, an acknowledgement associated with adjusting the duration of one or more of the wake-up periods reserved for sidelink communication (e.g., one-way communication). In some examples, the messaging component 825 may identify, in the request message, an indication to remove a wake-up period reserved for sidelink communication (e.g., two-way communication). In some examples, the messaging component 825 may identify, in the request message, an indication to modify a wake-up period reserved for sidelink communication (e.g., two-way communication). In some examples, the messaging component 825 may identify, in the request message, an indication to specifically allocate a wake-up period reserved for sidelink communication (e.g., two-way communication) to an additional device. In some examples, the messaging component 825 may send an indication associated with specifically allocating a wake-up period reserved for sidelink communication (e.g., two-way communication) to a device.

[0166] In some cases, one or more of the request message or the response message is a PC5 radio resource control message. In some cases, one or more of the request message or the response message is a media access control-control element message. In some cases, the request message includes an indication of the number of cycles associated with a wake-up period reserved for sidelink communication. In some cases, the request message carries a cause indication indicating the reason for inactivity associated with sidelink communication (e.g., one-way or two-way communication from the device to an additional device), and at least traffic information associated with the device. In some cases, based on the traffic information associated with the device, the request message carries a cause indication that indicates that the traffic load associated with the device meets a threshold. In some cases, the cause indication includes traffic information associated with the additional device or the amount of available resources associated with the additional device for sidelink communication (e.g., two-way communication) allocated to the device.

[0167] The traffic component 830 may determine that the traffic load associated with the device meets a threshold based on the traffic information. In some examples, the traffic component 830 may compare the traffic load associated with the device with the predicted traffic load associated with the device. The bit value component 835 may dispatch a bit value to a field in the request message, where the bit value corresponds to the duration of a wake-up period reserved for sidelink communication (e.g., one-way communication). In some examples, the bit value component 835 may dispatch a bit value to a field in the request message, where the bit value corresponds to the duration of a wake-up period reserved for sidelink communication (e.g., two-way communication). In some examples, the bit value component 835 may identify the bit value dispatched to a field in the request message, where the bit value corresponds to the duration of a wake-up period reserved for sidelink communication (e.g., two-way communication). The confirmation component 840 may identify an acknowledgement associated with the request message in the response message. In some examples, the confirmation component 840 may identify a negative acknowledgement and a cause indication of the negative acknowledgement associated with the request message in the response message.

[0168] In some examples, the confirmation component 840 may include in the response message an acknowledgement associated with releasing one or more resources associated with a wake-up period for sidelink communication (e.g., two-way communication). In some examples, the confirmation component 840 may include in the response message an acknowledgement associated with adjusting the duration of a wake-up period reserved for sidelink communication (e.g., two-way communication). In some examples, the confirmation component 840 may include in the response message an acknowledgement associated with specifically allocating a wake-up period reserved for sidelink communication (e.g., two-way communication) to an additional device.

[0169] In some examples, based on the service information, the confirmation component 840 may include, in the response message, a confirmation associated with the request message. In some examples, based on the service information, the confirmation component 840 may include, in the response message, a negative confirmation associated with the request message and an indication of the reason for the negative confirmation. The termination component 845 may terminate a unicast link associated with the directed communication (e.g., one-way communication) based on the service information. In some examples, the termination component 845 may terminate a unicast link associated with the directed communication (e.g., one-way communication) based on the service information.

[0170] Figure 9 FIG. shows a schematic diagram of a system 900 including a device 905 that supports a method for scheduling in the case of inactivity in sidelink unicast according to aspects of the present disclosure. The device 905 may be an example of the device 605, the device 705, or the UE 115 described herein or include components thereof. The device 905 may include components for two-way voice and data communication, including components for sending and receiving communications, including a UE communication manager 910, an I / O controller 915, a transceiver 920, an antenna 925, a memory 930, and a processor 940. These components may communicate electronically via one or more buses (e.g., bus 945).

[0171] The UE communication manager 910 may identify a schedule associated with the device 905 and an additional device in a group of devices that communicate directly with the device 905, where the schedule includes a wake-up period reserved for directed communication between the device 905 and the additional device (e.g., a wake-up period reserved for one-way communication from the device 905 to the additional device, or a wake-up period reserved for two-way communication between the device 905 and the additional device, or a combination thereof); manage the wake-up period reserved for directed communication based on the service information associated with the device 905; and communicate with the additional device according to the management.

[0172] The UE communication manager 910 may also identify a schedule associated with the device 905 and a device in a group of devices that communicate directly with the additional device, where the schedule includes a wake-up period reserved for directed communication between the device 905 and the device (e.g., a wake-up period reserved for one-way communication from the device 905 to the device or from the additional device to the device 905, or a wake-up period reserved for two-way communication between the device 905 and the device, or a combination thereof); manage the wake-up period reserved for directed communication based on the service information associated with the device 905 or the device; and communicate with the device according to the management.

[0173] The I / O controller 915 may manage the input and output signals of the device 905. The I / O controller 915 may also manage peripheral devices not integrated into the device 905. In some cases, the I / O controller 915 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 915 may use an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In other cases, the I / O controller 915 may represent, or interact with, a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 915 may be implemented as part of a processor. In some cases, a user may interact with the device 905 via the I / O controller 915 or via hardware components controlled by the I / O controller 915.

[0174] As described above, the transceiver 920 may communicate bidirectionally via one or more antennas, wired or wireless links. For example, the transceiver 920 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 920 may also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, and to demodulate packets received from the antenna. In some cases, the device 905 may include a single antenna 925. However, in some cases, the device 905 may have more than one antenna 925 capable of simultaneously transmitting or receiving multiple wireless transmissions.

[0175] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935, including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, the memory 930 may contain, for example, BIOS, which may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0176] The processor 940 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic component, discrete hardware component, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks supporting a method for scheduling in an inactive situation in sidelink unicast).

[0177] Code 935 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communication. Code 935 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, code 935 may not be directly executable by the processor 940, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0178] Figure 10 FIG. 1000 is a flow diagram illustrating a method 1000 for supporting scheduling in an inactive scenario in sidelink unicast according to aspects of the present disclosure. As described herein, the operations of method 1000 may be implemented by a UE 115 or components thereof. For example, the operations of method 1000 may be performed by a UE communication manager as referenced Figures 6 to 9 described. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0179] At 1005, a first UE may identify a schedule associated with the first UE and a second UE in a group of UEs that communicate directly with the first UE, where the schedule includes a wake-up period reserved for directed communication between the first UE and the second UE (e.g., a wake-up period reserved for unidirectional communication from the first UE to the second UE, or a wake-up period reserved for bidirectional communication between the first UE and the second UE, or a combination thereof). The operation of 1005 may be performed according to the methods described herein. In some examples, aspects of the operation of 1005 may be performed by a scheduling component as referenced Figures 6 to 9 described.

[0180] At 1010, the first UE may manage the wake-up period reserved for directed communication based on traffic information associated with the first UE. The operation of 1010 may be performed according to the methods described herein. In some examples, aspects of the operation of 1010 may be performed by a management component as referenced Figures 6 to 9 described.

[0181] At 1015, the first UE may communicate with the second UE according to the management. The operation of 1015 may be performed according to the methods described herein. In some examples, aspects of the operation of 1015 may be performed by a communication component as referenced Figures 6 to 9 described.

[0182] Figure 11FIG. 1100 is a flow diagram illustrating a method 1100 for supporting scheduling in an inactive scenario in sidelink unicast according to aspects of the present disclosure. As described herein, the operations of method 1100 may be implemented by a UE 115 or its components. For example, the operations of method 1100 may be performed by a UE communication manager described with reference to Figures 6 to 9 In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0183] At 1105, a first UE may identify a scheduling associated with the first UE and a second UE in a set of UEs that communicate directly with the first UE, where the scheduling includes a wake-up period reserved for directed communication between the first UE and the second UE (e.g., a wake-up period reserved for unidirectional communication from the first UE to the second UE, or a wake-up period reserved for bidirectional communication between the first UE and the second UE, or a combination thereof). The operation of 1105 may be performed according to the methods described herein. In some examples, aspects of the operation of 1105 may be performed by a scheduling component described with reference to Figures 6 to 9 described.

[0184] At 1110, the first UE may send a request message to the second UE based on traffic information associated with the first UE. The operation of 1110 may be performed according to the methods described herein. In some examples, aspects of the operation of 1110 may be performed by a messaging component described with reference to Figures 6 to 9 described.

[0185] At 1115, the first UE may receive a response message from the second UE based on the request message. The operation of 1115 may be performed according to the methods described herein. In some examples, aspects of the operation of 1115 may be performed by a messaging component described with reference to Figures 6 to 9 described.

[0186] At 1120, the first UE may manage the wake-up period reserved for directed communication (e.g., one or more of a wake-up period reserved for unidirectional communication or a wake-up period reserved for bidirectional communication) based on traffic information associated with the first UE and the response message. The operation of 1120 may be performed according to the methods described herein. In some examples, aspects of the operation of 1120 may be performed by a management component described with reference to Figures 6 to 9 described.

[0187] At 1125, the first UE may communicate with the second UE according to the management. The operation of 1125 may be performed according to the methods described herein. In some examples, aspects of the operation of 1125 may be performed by a communication component described with reference to Figures 6 to 9 described.

[0188] Figure 12 FIG. 1200 is a flowchart illustrating a method 1200 for supporting scheduling in an inactive scenario in sidelink unicast according to aspects of the present disclosure. As described herein, the operations of method 1200 may be implemented by UE 115 or its components. For example, the operations of method 1200 may be performed by a UE communication manager as referenced Figures 6 to 9 described. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0189] At 1205, a first UE may identify a scheduling associated with the first UE and a second UE in a set of UEs that communicate directly with the first UE, where the scheduling includes a wake-up period reserved for directed communication between the first UE and the second UE (e.g., a wake-up period reserved for unidirectional communication from the first UE to the second UE or from the second UE to the first UE, or a wake-up period reserved for bidirectional communication between the first UE and the second UE, or a combination thereof). The operation of 1205 may be performed according to the methods described herein. In some examples, aspects of the operation of 1205 may be performed by a scheduling component as referenced Figures 6 to 9 described.

[0190] At 1210, the first UE may manage the wake-up period reserved for directed communication (e.g., one or more of a wake-up period reserved for unidirectional communication or a wake-up period reserved for bidirectional communication) based on traffic information associated with the first UE or the second UE. The operation of 1210 may be performed according to the methods described herein. In some examples, aspects of the operation of 1210 may be performed by a management component as referenced Figures 6 to 9 described.

[0191] At 1215, the first UE may communicate with the second UE according to the management. The operation of 1215 may be performed according to the methods described herein. In some examples, aspects of the operation of 1215 may be performed by a communication component as referenced Figures 6 to 9 described.

[0192] Figure 13 FIG. 1300 is a flowchart illustrating a method 1300 for supporting scheduling in an inactive scenario in sidelink unicast according to aspects of the present disclosure. As described herein, the operations of method 1300 may be implemented by UE 115 or its components. For example, the operations of method 1300 may be performed by a UE communication manager as referenced Figures 6 to 9Performed by the described UE communication manager. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0193] At 1305, the first UE may identify a schedule associated with the first UE and a second UE among a set of UEs directly communicating with the first UE, where the schedule includes a wake-up period reserved for directed communication between the first UE and the second UE (e.g., a wake-up period reserved for unidirectional communication from the first UE to the second UE or from the second UE to the first UE, or a wake-up period reserved for bidirectional communication between the first UE and the second UE, or a combination thereof). The operation of 1305 may be performed according to the methods described herein. In some examples, aspects of the operation of 1305 may be performed by a scheduling component referenced Figures 6 to 9 as described.

[0194] At 1310, the first UE may receive a request message from the second UE, the request message including traffic information associated with the second UE. The operation of 1310 may be performed according to the methods described herein. In some examples, aspects of the operation of 1310 may be performed by a messaging component referenced Figures 6 to 9 as described.

[0195] At 1315, the first UE may send a response message to the second UE based on the request message and traffic information associated with the first UE. The operation of 1315 may be performed according to the methods described herein. In some examples, aspects of the operation of 1315 may be performed by a messaging component referenced Figures 6 to 9 as described.

[0196] At 1320, the first UE may manage the wake-up period reserved for directed communication (e.g., one or more of the wake-up periods reserved for unidirectional communication or bidirectional communication) based on the request message and traffic information associated with the first UE or the second UE. The operation of 1320 may be performed according to the methods described herein. In some examples, aspects of the operation of 1320 may be performed by a management component referenced Figures 6 to 9 as described.

[0197] At 1325, the first UE may communicate with the second UE according to the management. The operation of 1325 may be performed according to the methods described herein. In some examples, aspects of the operation of 1325 may be performed by a communication component referenced Figures 6 to 9 as described.

[0198] Note that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Further, aspects of two or more methods may be combined.

[0199] The techniques described herein can be used in various wireless communication systems such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-Carrier Frequency Division Multiple Access (SC-FDMA), and other systems. CDMA systems may implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers the IS-2000, IS-95, and IS-856 standards. The IS-2000 release is often referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is often referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems may implement radio technologies such as Global System for Mobile Communications (GSM).

[0200] OFDMA systems may implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE, LTE-A, and LTE-A Pro are UMTS releases that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-A Pro, NR, and GSM are described in documents from an organization named the "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named the "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein can be used in the systems and radio technologies mentioned herein and other systems and radio technologies. Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for purposes of example and the LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein can be applied outside of LTE, LTE-A, LTE-A Pro, or NR applications.

[0201] Macro cells typically cover a relatively large geographical area (e.g., with a radius of several kilometers) and can allow unrestricted access to UEs that have subscribed to the services of a network provider. Compared with macro cells, small cells can be associated with low-power base stations, and small cells can operate in the same or different (e.g., licensed, unlicensed, etc.) frequency bands as macro cells. According to various examples, small cells can include pico cells, femto cells, and micro cells. For example, a pico cell can cover a small geographical area and can allow unrestricted access to UEs that have subscribed to the services of a network provider. A femto cell can also cover a small geographical area (e.g., a home) and can provide restricted access by UEs associated with that femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in the home, etc.). The eNB for a macro cell can be referred to as a macro eNB. The eNB for a small cell can be referred to as a small cell eNB, pico eNB, femto eNB, or home eNB. An eNB can support one or more (e.g., two, three, four, etc.) cells and can also support communication using one or more component carriers.

[0202] The wireless communication systems described herein can support synchronous operation or asynchronous operation. For synchronous operation, base stations can have similar frame timings, and transmissions from different base stations can be approximately aligned in time. For asynchronous operation, base stations may have different frame timings, and transmissions from different base stations may not be aligned in time. The techniques described herein can be used for synchronous operation or asynchronous operation.

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

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

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

[0206] Computer-readable media includes non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium can be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer or a general purpose or special purpose processor. Additionally, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0207] As used herein, including in the claims, the term "or" as used in a list of items (e.g., a list of items prefaced by a phrase such as "at least one" or "one or more") means an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Further, as used herein, the phrase "based on" should not be construed as referring to a closed set of conditions. For example, an exemplary step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on."

[0208] In the drawings, similar components or features may have the same reference numeral. Further, various components of the same type may be distinguished by following the reference numeral with a dash and a second numeral that differentiates among similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, regardless of the second or further reference numerals.

[0209] The description set forth herein, in connection with the drawings, describes exemplary configurations and does not represent all examples that may be implemented or that are within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration" and does not mean "preferred" or "better than other examples." To provide an understanding of the described technology, the detailed description includes specific details. However, the technology may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0210] The present description is provided to enable a person skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a first user equipment (UE), comprising: identifying a scheduling associated with direct communication between the first UE and a second UE, the scheduling including a wake-up period reserved for sending or receiving a one-way communication; determining a wake-up period of a discontinuous reception configuration associated with sending or receiving the one-way communication, wherein the discontinuous reception configuration is for at least one discontinuous reception period controlled by a set of timers associated with the first UE, and wherein the wake-up period of the discontinuous reception configuration is at least partially based on a traffic load associated with the first UE and a sidelink traffic load between the first UE and one or more UEs including the second UE; and communicating with the second UE according to the discontinuous reception configuration.

2. The method according to claim 1, further comprising: sending a request message to the second UE at least partially based on traffic information associated with the first UE; and receiving a response message from the second UE at least partially based on the request message, wherein the discontinuous reception configuration associated with sending or receiving the one-way communication is at least partially based on the response message.

3. The method according to claim 2, wherein one or more of the request message or the response message is a PC5 radio resource control message or a media access control - control element message.

4. The method according to claim 2, wherein the request message includes an indication of a number of periods associated with modifying the wake-up period reserved for sending or receiving the one-way communication.

5. The method according to claim 2, further comprising: determining that the traffic load associated with the first UE meets a threshold at least partially based on the traffic information, wherein the discontinuous reception configuration associated with sending or receiving the one-way communication is at least partially based on the traffic load meeting the threshold; and including a cause indication in the request message at least partially based on the determination, the cause indication indicating that the traffic load associated with the first UE meets the threshold, wherein sending the request message to the second UE includes: sending the request message carrying the cause indication to the second UE.

6. The method according to claim 2, further comprising: including an indication of removing the wake-up period reserved for sending or receiving the one-way communication in the request message at least partially based on the traffic information, wherein communication with the second UE is at least partially based on the indication.

7. The method according to claim 1, wherein the wake-up period reserved for sending or receiving the one-way communication includes a sidelink unicast from the first UE to the second UE, and wherein the wake-up period reserved for the one-way communication is not shared between the first UE and the second UE.

8. The method according to claim 2, further comprising: Include, at least in part based on the service information, an indication in the request message to modify the wake-up period reserved for sending or receiving the one-way communication, wherein communication with the second UE is at least in part based on the indication.

9. The method according to claim 2, further comprises: Assigning a bit value to a field in the request message, wherein the bit value corresponds to the duration of the wake-up period reserved for sending or receiving the one-way communication.

10. The method according to claim 2, further comprises: Include, at least in part based on the service information, an indication in the request message to remove or modify the wake-up period reserved for the one-way communication, wherein communication with the second UE is at least in part based on the indication.

11. The method according to claim 2, further comprises: Assigning a bit value to a field in the request message, wherein the bit value corresponds to the duration of the wake-up period reserved for sending or receiving the one-way communication.

12. The method according to claim 2, further comprises: Include, at least in part based on the service information, an indication in the request message to specifically allocate the wake-up period reserved for sending or receiving the one-way communication to the second UE, wherein communication with the second UE is at least in part based on the indication.

13. The method according to claim 1, further comprises: Receiving from the second UE an indication to specifically allocate the wake-up period reserved for sending or receiving the one-way communication to the first UE, wherein communication with the second UE is at least in part based on the indication.

14. The method according to claim 1, further comprises: Sending a first message to the second UE, the first message including an indication of the duration of the wake-up period reserved for the one-way communication; and In response to the first message, receiving from the second UE a second message indicating acceptance or rejection of the wake-up period, wherein communication with the second UE according to the discontinuous reception configuration is at least in part based on the second message.

15. A method for wireless communication at a first user equipment (UE), comprises: Identifying a schedule associated with direct communication between the first UE and the second UE, the schedule including a wake-up period reserved for sending or receiving one-way communication; Determining, at least in part based on service information associated with the first UE or the second UE, a wake-up period of a discontinuous reception configuration associated with sending or receiving the one-way communication, wherein the discontinuous reception configuration is for at least one discontinuous reception period controlled by a set of timers associated with the first UE, and wherein the wake-up period of the discontinuous reception configuration is at least in part based on the service load associated with the first UE and the sidelink service load between the first UE and one or more UEs including the second UE; and Communicating with the second UE according to the discontinuous reception configuration.

16. The method according to claim 15, further comprises: Receive a request message from the second UE, the request message including service information associated with the second UE; and Send a response message to the second UE at least in part based on the request message and the service information associated with the first UE, wherein the discontinuous reception configuration associated with sending or receiving the one-way communication is at least in part based on the request message and the service information associated with the first UE.

17. The method according to claim 16, wherein, One or more of the request message or the response message is a PC5 radio resource control message or a media access control - control element message.

18. The method according to claim 16, wherein, The request message includes an indication of the number of periods associated with modifying the wake-up period reserved for sending or receiving the one-way communication.

19. The method according to claim 16, wherein, At least in part based on the service information associated with the second UE, the request message carries a cause indication that indicates that a first service payload associated with the second UE meets a threshold, and wherein the discontinuous reception configuration associated with sending or receiving the one-way communication is at least in part based on the inactivity associated with the one-way communication between the second UE and the first UE.

20. The method according to claim 15, further comprising: Communicate with a third UE according to the discontinuous reception configuration associated with sending or receiving the one-way communication.

21. The method according to claim 16, further comprising: Identify an indication in the request message to remove the wake-up period reserved for sending or receiving the one-way communication; and Release one or more resources associated with the wake-up period reserved for sending or receiving the one-way communication at least in part based on the request message and the service information; and Include in the response message an acknowledgment associated with releasing the one or more resources associated with the wake-up period reserved for sending or receiving the one-way communication, wherein the communication with the second UE is at least in part based on one or more of: the response message and releasing the one or more resources associated with the wake-up period reserved for sending or receiving the one-way communication.

22. The method according to claim 15, wherein, The wake-up period reserved for sending or receiving the one-way communication includes a sidelink unicast from the first UE to the second UE, and wherein the wake-up period reserved for the one-way communication is not shared between the first UE and the second UE.

23. The method according to claim 16, further comprising: Identify an indication in the request message to modify the wake-up period reserved for sending or receiving the one-way communication; and Include in the response message an acknowledgment associated with adjusting the duration of the wake-up period reserved for sending or receiving the one-way communication, wherein the communication with the second UE is at least in part based on the response message.

24. The method according to claim 16, further comprising: Identify one or more bit values assigned to a field in the request message, wherein the one or more bit values correspond to a duration of the wake-up period reserved for sending or receiving the one-way communication.

25. The method according to claim 16, further comprising: Identify an indication in the request message to remove or modify the wake-up period reserved for sending or receiving the one-way communication; and Include in the response message an acknowledgment associated with releasing one or more resources associated with the wake-up period used for sending or receiving the one-way communication, wherein communication with the second UE is at least partially based on the response message.

26. The method according to claim 16, further comprising: Identify a bit value assigned to a field in the request message, wherein the bit value corresponds to a duration of the wake-up period reserved for sending or receiving the one-way communication.

27. The method according to claim 16, further comprising: Identify an indication in the request message that specifically allocates the wake-up period reserved for sending or receiving the one-way communication to the first UE; and Include in the response message an acknowledgment associated with specifically allocating the wake-up period reserved for sending or receiving the one-way communication to the first UE, wherein communication with the second UE is at least partially based on the response message.

28. The method according to claim 15, further comprising: Send to the second UE an indication associated with specifically allocating the wake-up period reserved for sending or receiving the one-way communication to the second UE, wherein communication with the second UE is at least partially based on the indication.

29. A first apparatus for wireless communication, comprising: One or more processors, and At least one memory coupled to the one or more processors, the one or more processors being configured to: Identify a schedule associated with direct communication between the first apparatus and a second apparatus, the schedule including a wake-up period reserved for sending or receiving one-way communication; Determine a wake-up period of a discontinuous reception configuration associated with sending or receiving the one-way communication, wherein the discontinuous reception configuration is for at least one discontinuous reception period controlled by a set of timers associated with the first apparatus, and wherein the wake-up period of the discontinuous reception configuration is at least partially based on a traffic load associated with the first apparatus and a sidelink traffic load between the first apparatus and one or more apparatuses including the second apparatus; and Communicate with the second apparatus according to the discontinuous reception configuration.

30. The first apparatus according to claim 29, wherein The one or more processors are configured to cause the first apparatus to: Send a request message to the second apparatus at least partially based on traffic information associated with the first apparatus; and Receive from the second apparatus a response message at least partially based on the request message, wherein the wake-up period reserved for sending or receiving the one-way communication is at least partially based on the response message.

31. The first device according to claim 30, wherein, one or more of the request message or the response message is a PC5 radio resource control message or a media access control - control element message.

32. The first device according to claim 30, wherein, the request message includes an indication of the number of periods associated with the wake - up period reserved for sending or receiving the one - way communication.

33. The first device according to claim 30, wherein, the one or more processors are configured to cause the first device to: determine, at least in part based on the traffic information, that the traffic load associated with the first device meets a threshold, wherein the wake - up period reserved for sending or receiving the one - way communication is at least in part based on the traffic load meeting the threshold; and include, at least in part based on the traffic load associated with the first device meeting the threshold, a cause indication in the request message, the cause indication indicating that the traffic load associated with the first device meets the threshold, wherein, to send the request message, the one or more processors are configured to cause the first device to: send the request message carrying the cause indication to the second device.

34. The first device according to claim 30, wherein, the one or more processors are configured to cause the first device to: include, at least in part based on the traffic information, an indication in the request message to remove the wake - up period reserved for sending or receiving the one - way communication, wherein the communication with the second device is at least in part based on the indication.

35. The first device according to claim 29, wherein, the wake - up period reserved for sending or receiving the one - way communication includes a sidelink unicast from the first device to the second device, and wherein the wake - up period reserved for the one - way communication is not shared between the first device and the second device.

36. The first device according to claim 30, wherein, the one or more processors are configured to cause the first device to: include, at least in part based on the traffic information, an indication in the request message to modify the wake - up period reserved for sending or receiving the one - way communication, wherein the communication with the second device is at least in part based on the indication.

37. The first device according to claim 30, wherein, the one or more processors are configured to cause the first device to: assign a bit value to a field in the request message, wherein the bit value corresponds to the duration of the wake - up period reserved for sending or receiving the one - way communication.

38. The first device according to claim 30, wherein, the one or more processors are configured to cause the first device to: include, at least in part based on the traffic information, an indication in the request message to remove or modify the wake - up period reserved for the one - way communication, wherein the communication with the second device is at least in part based on the indication.

39. The first device according to claim 30, wherein, The one or more processors are configured to cause the first device to: Dispatch a bit value to a field in the request message, where the bit value corresponds to a duration of the wake-up period reserved for sending or receiving the one-way communication.

40. The first device according to claim 30, wherein, The one or more processors are configured to cause the first device to: Include, in the request message, an indication that specifically allocates the wake-up period reserved for sending or receiving the one-way communication to the second device, at least partially based on the traffic information, wherein communication with the second device is at least partially based on the indication.

41. The first device according to claim 29, wherein, The one or more processors are configured to cause the first device to: Receive, from the second device, an indication that specifically allocates the wake-up period reserved for sending or receiving the one-way communication to the first device, wherein communication with the second device is at least partially based on the indication.

42. The first device according to claim 29, wherein, The one or more processors are configured to cause the first device to: Send a first message to the second device, the first message including an indication of the duration of the wake-up period reserved for the one-way communication; and In response to the first message, receive a second message from the second device indicating acceptance or rejection of the wake-up period, wherein communication with the second device according to the discontinuous reception configuration is at least partially based on the second message.

43. A first device for wireless communication, comprising: One or more processors, and At least one memory coupled to the one or more processors, the one or more processors being configured to: Identify a schedule associated with direct communication between the first device and a second device, the schedule including a wake-up period reserved for sending or receiving one-way communication; Determine, at least partially based on traffic information associated with the first device or the second device, a wake-up period of a discontinuous reception configuration associated with sending or receiving the one-way communication, wherein the discontinuous reception configuration is for at least one discontinuous reception period controlled by a set of timers associated with the first device, and wherein the wake-up period of the discontinuous reception configuration is at least partially based on a traffic load associated with the first device and a sidelink traffic load between the first device and one or more devices including the second device; and Communicate with the second device according to the discontinuous reception configuration.

44. The first device according to claim 43, wherein, The one or more processors are configured to cause the first device to: Receive a request message from the second device, the request message including traffic information associated with the second device; and Send a response message to the second device at least partially based on the request message and the service information associated with the first device, wherein the wake-up period reserved for sending or receiving the one-way communication is at least partially based on the request message and the service information associated with the first device.

45. The first device according to claim 44, wherein, One or more of the request message or the response message is a PC5 radio resource control message or a media access control-control element message.

46. The first device according to claim 44, wherein, The request message includes an indication of the number of periods associated with modifying the wake-up period reserved for sending or receiving the one-way communication.

47. The first device according to claim 44, wherein, At least partially based on the service information associated with the second device, the request message carries a cause indication indicating that a first service payload associated with the second device meets a threshold, and wherein the wake-up period reserved for sending or receiving the one-way communication is at least partially based on inactivity associated with the one-way communication between the second device and the first device.

48. The first device according to claim 43, wherein, The one or more processors are configured to cause the first device to: Communicate with a third device according to a discontinuous reception configuration associated with sending or receiving the one-way communication.

49. The first device according to claim 44, wherein, The one or more processors are configured to cause the first device to: Identify an indication to remove the wake-up period reserved for sending or receiving the one-way communication in the request message; Release one or more resources associated with the wake-up period reserved for sending or receiving the one-way communication at least partially based on the request message and the service information; and Include an acknowledgment associated with releasing the one or more resources associated with the wake-up period reserved for sending or receiving the one-way communication in the response message, wherein communication with the second device is at least partially based on one or more of: releasing the one or more resources associated with the wake-up period reserved for sending or receiving the one-way communication and the response message.

50. The first device according to claim 43, wherein, The wake-up period reserved for sending or receiving the one-way communication includes a sidelink unicast from the first device to the second device, and wherein the wake-up period reserved for the one-way communication is not shared between the first device and the second device.

51. The first device according to claim 44, wherein, The one or more processors are configured to cause the first device to: Identify an indication to modify the wake-up period reserved for sending or receiving the one-way communication in the request message; and Include, in the response message, an acknowledgement associated with a duration of the wake-up period reserved for transmitting or receiving the one-way communication, wherein communication with the second device is at least partially based on the response message.

52. The first device according to claim 44, wherein, the one or more processors are configured to cause the first device to: Identify one or more bit values assigned to a field in the request message, wherein the one or more bit values correspond to a duration of the wake-up period reserved for transmitting or receiving the one-way communication.

53. The first device according to claim 44, wherein, the one or more processors are configured to cause the first device to: Identify, in the request message, an indication to remove or modify the wake-up period reserved for transmitting or receiving the one-way communication; and Include, in the response message, an acknowledgement associated with releasing one or more resources associated with the wake-up period for transmitting or receiving the one-way communication, wherein communication with the second device is at least partially based on the response message.

54. The first device according to claim 44, wherein, the one or more processors are configured to cause the first device to: Identify a bit value assigned to a field in the request message, wherein the bit value corresponds to a duration of the wake-up period reserved for transmitting or receiving the one-way communication.

55. The first device according to claim 44, wherein, the one or more processors are configured to cause the first device to: Identify, in the request message, an indication that the wake-up period reserved for transmitting or receiving the one-way communication is specifically allocated to the first device; and Include, in the response message, an acknowledgement associated with specifically allocating the wake-up period reserved for transmitting or receiving the one-way communication to the first device, wherein communication with the second device is at least partially based on the response message.

56. The first device according to claim 43, wherein, the one or more processors are configured to cause the first device to: Send an indication associated with specifically allocating the wake-up period reserved for transmitting or receiving the one-way communication to the second device, wherein communication with the second device is at least partially based on the indication.

Images