Method for scheduling inactive conditions in sidelink unicast

Abstract

Methods, systems, and devices for wireless communications are described. A method may include identifying, by a first user equipment (UE), a schedule associated with a first UE and a second UE in a group of UEs that communicate directly with the first UE. The schedule may include a wake-up period reserved for directional communication between the first UE and the second UE. The first UE may manage the wake-up period reserved for directional communication based on traffic information associated with the first UE, and may communicate with the second UE based on the management. The wake-up period reserved for directional communication may include a wake-up period reserved for unidirectional communication or a wake-up period reserved for bidirectional communication.

Description

[0001] Cross-references

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

[0003] The following relates generally to wireless communications and, more particularly, to methods for scheduling in an inactive situation in sidelink unicast. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems, such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems, which may be referred to as new radio (NR) systems. These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include multiple base stations or network access nodes, each of which simultaneously supports communication with multiple communication devices, which may also be referred to as user equipment (UE).

[0005] Some wireless communication systems may support access links and sidelinks. The access link is a communication link between a UE and a base station. In some examples, the access link may be referred to as a Uu interface. Specifically, the Uu interface may refer to an air interface for downlink transmission, uplink transmission, or both. A sidelink is a communication link between similar devices. For example, a sidelink may 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, a sidelink may support unicast messaging, groupcast messaging, multicast messaging, broadcast messaging, or a combination thereof. In these systems, efficient energy-saving techniques may be required. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatuses that support methods for scheduling in inactive situations in sidelink unicast. Technologies for device-to-device communication between devices (e.g., user equipment (UE)) are proposed, which ensure reliable communication and energy saving. A UE and an additional UE in a group of UEs can communicate directly (e.g., via a sidelink). A schedule associated with a UE may include a wake-up period reserved for directional communication between the UE and the additional UE. For example, the schedule may 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 UE. The UE can identify the schedule and manage the wake-up period reserved for directional communication between the UE and the additional UE.

[0007] For example, the UE may manage wake-up periods reserved for directional communications (e.g., managing one or more of wake-up periods reserved for unidirectional communications or wake-up periods reserved for bidirectional communications). In some cases, the UE may 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 may send a request message to an additional UE based on traffic information associated with the UE. In some cases, the UE may 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 may include an acknowledgement (e.g., an acceptance message) or a negative acknowledgement (e.g., a rejection message) and an associated reason for the response.

[0008] 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 a group of UEs that communicate directly with the first UE, wherein the schedule includes a wake-up period reserved for directional 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 directional communication based on service information associated with the first UE; and communicating with the second UE according to the management.

[0009] A first device in a group of devices for wireless communication is described. The first device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the first device to identify a schedule associated with the first device and a second device in a group of devices that communicate directly with the first device, wherein the schedule includes a wake-up period reserved for directional 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 a wake-up period reserved for bidirectional communication between the first device and the second device, or a combination thereof); manage the wake-up period reserved for directional communication based on business information associated with the first device; and communicate with the second device according to the management.

[0010] A first device in a group of devices for wireless communication is described. 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 group of devices that communicate directly with the first device, wherein the schedule includes a wake-up period reserved for directional 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 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 directional communication based on traffic information associated with the first device; and communicating with the second device in accordance with the management.

[0011] A non-transitory computer-readable medium storing code for wireless communication at a first UE in a group of UEs is described. The code may include instructions executable by a processor to identify a schedule associated with the first UE and a second UE in a group of UEs that communicate directly with the first UE, wherein the schedule includes a wake-up period reserved for directional 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); manage the wake-up period reserved for directional communication based on service information associated with the first UE; and communicate with the second UE according to the management.

[0012] Some examples of the methods, apparatus, 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 service information associated with the first UE, and receiving a response message based on the request message from the second UE, and wherein managing the wake-up period reserved for directional communication may be based on the response message.

[0013] In some examples of the methods, apparatus, 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.

[0014] In some examples of the methods, apparatus, 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.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the request message includes an indication of a number of cycles associated with modifying the wake-up period reserved for the directional communication.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for determining, based on the service information, that a traffic load associated with the first UE meets a threshold, wherein managing the wake-up period reserved for directional communication may be based on the traffic load meeting the threshold, and based on the 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 the request message carrying the cause indication to the second UE.

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

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for including in a request message an indication of removing a wake-up period reserved for directional communications (e.g., a wake-up period reserved for unidirectional communications) based on business information, wherein communication with the second UE may be based on the indication.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for including in a request message an indication of modifying a wake-up period reserved for directional communication (e.g., modifying a wake-up period reserved for unidirectional communication) based on business information, wherein communication with the second UE may be based on the indication.

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

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for including in a request message an indication of removing or modifying a wake-up period reserved for directional communication (e.g., removing or modifying a wake-up period reserved for bidirectional communication) based on business information, wherein communication with the second UE may be based on the indication.

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

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

[0024] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the wake-up period reserved for directional communication may include a wake-up period reserved for unidirectional communication from a first UE to a second UE or a wake-up period reserved for bidirectional communication between the first UE and the second UE. The wake-up period reserved for bidirectional communication may be shared between the first UE and the second UE, while the wake-up period reserved for unidirectional communication may not be shared between the first UE and the second UE.

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

[0026] 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 a group of UEs that communicate directly with the first UE, wherein the schedule includes a wake-up period reserved for directional 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 directional communication based on service information associated with the first UE or the second UE; and communicating with the second UE according to the management.

[0027] A first device in a group of devices for wireless communication is described. The first device 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 device to identify a schedule associated with the first device and a second device in a group of devices that communicate directly with the first device, wherein the schedule includes a wake-up period reserved for directional 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); manage the wake-up period reserved for directional communication based on business information associated with the first device or the second device; and communicate with the second device according to the management.

[0028] A first device in a group of devices for wireless communication is described. 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 group of devices that communicate directly with the first device, wherein the schedule includes a wake-up period reserved for directional 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 directional communication based on service information associated with the first device or the second device; and communicating with the second device according to the management.

[0029] A non-transitory computer-readable medium storing code for wireless communication at a first UE in a group of UEs is described. The code may include instructions executable by a processor to identify a schedule associated with the first UE and a second UE in a group of UEs that communicate directly with the first UE, wherein the schedule includes a wake-up period reserved for directional 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); manage the wake-up period reserved for directional communication based on service information associated with the first UE or the second UE; and communicate with the second UE according to the management.

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

[0031] In some examples of the methods, apparatus, 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 Medium Access Control - Control Element message.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the request message includes an indication of a number of cycles associated with modifying the wake-up period reserved for the directional communication.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, based on service information associated with the second UE, the request message carries a cause indication indicating that the service load associated with the second UE satisfies a threshold, and wherein management of the wake-up period reserved for directional communication can be based on inactivity associated with directional communication between the second UE and the first UE (e.g., inactivity associated with unidirectional communication from the second UE to the first UE).

[0034] Some examples of the methods, apparatus, 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 directional communication (e.g., a wake-up period reserved for unidirectional communication), releasing one or more resources associated with the wake-up period reserved for directional communication (e.g., a wake-up period reserved for unidirectional communication) based on the request message and service information, including in a response message a confirmation associated with the release of one or more resources associated with the wake-up period reserved for directional communication (e.g., a wake-up period reserved for unidirectional communication), and wherein communication with the second UE may be based on one or more of: the response message and the release of one or more resources associated with the wake-up period reserved for unidirectional communication.

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

[0036] Some examples of the methods, apparatus, 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 a request message, wherein the one or more bit values ​​correspond to a duration of a wake-up period reserved for directional communications (e.g., a duration of a wake-up period reserved for unidirectional communications).

[0037] Some examples of the methods, apparatus, 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 directional communication (e.g., a wake-up period reserved for two-way communication), including in a response message a confirmation associated with releasing one or more resources associated with the wake-up period reserved for directional communication (e.g., a wake-up period for two-way communication), and wherein communication with the second UE may be based on the response message.

[0038] Some examples of the methods, apparatus, 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 a duration of a wake-up period reserved for directional communication (e.g., a wake-up period reserved for bidirectional communication).

[0039] Some examples of the methods, apparatus, 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 directional communication (e.g., a wake-up period reserved for two-way communication) is exclusively allocated to the first UE, including in a response message a confirmation associated with the wake-up period reserved for directional communication (e.g., a wake-up period reserved for two-way communication) being exclusively allocated to the first UE, and wherein communication with the second UE may be based on the response message.

[0040] 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 in accordance with managing the wake-up period reserved for directional communication.

[0041] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the wake-up period reserved for directional communication may include a wake-up period reserved for unidirectional communication from a first UE to a second UE or a wake-up period reserved for bidirectional communication between the first UE and the second UE, wherein the wake-up period reserved for bidirectional communication may be shared between the first UE and the second UE, and wherein the wake-up period reserved for unidirectional communication may not be shared between the first UE and the second UE.

[0042] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for sending an indication to a second UE associated with allocating a wake-up period reserved for directional communication (e.g., a wake-up period reserved for bidirectional communication) exclusively to the second UE, and wherein communication with the second UE may be based on the indication. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 An example of a wireless communication system supporting methods for scheduling in an inactive case in sidelink unicast according to aspects of the present disclosure is shown.

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

[0045] Figure 3 An example of a wireless system supporting methods for scheduling in an inactive case in sidelink unicast according to aspects of the present disclosure is shown.

[0046] Figure 4 An example of a timing diagram of a method to support scheduling in the inactivity case in sidelink unicast according to aspects of the present disclosure is shown.

[0047] Figure 5 An example of a process flow of a method for supporting scheduling in an inactive case in sidelink unicast according to aspects of the present disclosure is shown.

[0048] Figure 6 and Figure 7 A block diagram of an apparatus supporting a method for scheduling in an inactive case in sidelink unicast according to aspects of the present disclosure is shown.

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

[0050] Fig. 9 A schematic diagram of a system including devices supporting a method for scheduling in an inactive case in sidelink unicast according to aspects of the present disclosure is shown.

[0051] Figures 10 to 13 A flow chart of a method for supporting scheduling in the absence of activity in sidelink unicast according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0052] A wireless communication system may support access links and sidelinks for communication between wireless devices. An access link may refer to a communication link between a user equipment (UE) and a base station. For example, an access link may support uplink signaling, downlink signaling, a connection process, and the like. A sidelink may refer to any communication link between similar wireless devices (e.g., a communication link between UEs, or a backhaul communication link between base stations). It should be noted that, although the various examples provided herein are discussed with respect to UE sidelink devices, such sidelink connection technology may be used for any type of wireless device that uses sidelink connection communication. For example, a sidelink may support device-to-device (D2D) communication, vehicle-to-everything (V2X) and / or vehicle-to-vehicle (V2V) communication, message relay, discovery signaling, beacon signaling, or any combination of these signals or other signals, which are sent from one UE to one or more other UEs through the air. Sidelink communication may support communication within a group of UEs. For example, the sidelink communication may include communication between the UE and other UEs within a coverage area including the group of UEs (e.g., a coverage area provided by a base station, a coverage area outside the coverage area provided by a base station, or a combination thereof). One or more UEs in the group of UEs may initiate sidelink communication with other UEs in the group of UEs.

[0053] For example, a UE communicating with one or more additional UEs in the group of UEs (e.g., in a D2D system, among other examples) may send information to or receive information from another UE. In order 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 may reserve resources (e.g., time slots or time periods) for sending or receiving information. In some examples, the reservation may be semi-persistent, and the UE may reserve resources based on a prediction of future communication needs by the UE or another UE in the group of UEs communicating with the UE. However, demand predictions may not always be accurate, and the UE may inadvertently reserve (e.g., distributed NR sidelink reservations) more resources than required in a unicast link. In these examples, a UE that is aware of its own inactivity regarding an established unicast link (e.g., a schedule that has been negotiated between the UE and another UE in the group of UEs) may notify another UE associated with the link (e.g., a peer UE) to adjust the reservation.

[0054] As described herein, energy-saving techniques for sidelink communications can be used to achieve reduced power consumption and extended battery life while ensuring reliable and efficient communication in the group of UEs. Energy-saving techniques can be implemented in part by one or more UEs in the group of UEs. In some examples, the 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 a directional scheduling (e.g., unidirectional scheduling or bidirectional scheduling) associated with communication between the UE and another UE. In some examples, managing scheduling can include releasing another UE from a prior communication obligation (e.g., terminating a unicast link associated with a unidirectional communication from the UE to another UE or from another UE to the UE, and releasing associated resources).

[0055] Aspects of the examples described herein can bring several advantages to communications associated with various communication technologies. For example, in the sub-6 GHz range, if a UE is aware of its own inactivity (e.g., no additional transmissions from the UE) with respect to an established unicast link (e.g., a scheduling that has been 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 the link to schedule transmissions between other peer UEs. For example, in millimeter wave (mmW) communications, a peer UE can similarly reuse previously allocated resources as described above, but can also benefit from being able to receive transmissions in another beam direction.

[0056] In some examples, a UE in a group of UEs may identify a schedule associated with the UE and another UE in the group of UEs (e.g., a peer UE). The schedule may 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 may send a request message to the peer UE based on business information associated with the UE. In one example, the request message may include an indication of the number of cycles associated with modifying one or more of the wake-up periods. In some examples, the request message may include a cause indication associated with the request message (e.g., inactivity, business load exceeds business expectations). The UE may receive a response message from the peer UE and may 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 may include a confirmation (e.g., acceptance) or a negative confirmation (e.g., rejection) and an associated cause (e.g., business information associated with the peer UE, such as scheduled communication from the peer UE to the UE).

[0057] According to an example of aspects described herein, a UE may manage wake-up periods (e.g., one or more of wake-up periods for unidirectional communication or bidirectional communication) based on traffic information associated with the UE (e.g., traffic load, inactivity) and a response message from a peer UE. In some examples, the UE may terminate a unicast link associated with unidirectional communication from the UE to the peer UE, and remove the wake-up period for the unidirectional 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 the unidirectional communication. In other exemplary aspects, the UE may adjust the duration of the wake-up period reserved for directional communication (e.g., bidirectional communication) between the UE and the peer UE, or remove the wake-up period (e.g., release resources associated with the wake-up period). On the other hand, the UE may allocate the wake-up period exclusively to the UE or the peer UE (e.g., allocate the wake-up period reserved for bidirectional communication between the UE and the peer UE exclusively to the wake-up period reserved for unidirectional communication associated with the UE or the peer UE). Through one or any combination of the described techniques, a UE may implement various power saving enhancement schemes, thereby improving battery life and reducing unnecessary power consumption at the UE while providing efficient and reliable communication on the sidelink.

[0058] Aspects of the present disclosure are initially described in the context of wireless communication systems. Aspects of the present disclosure are further illustrated and described by apparatus diagrams, system diagrams, and flow charts that relate to methods for scheduling in the case of inactivity in sidelink unicast.

[0059] Figure 1An example of a wireless communication system 100 supporting a method for scheduling in an inactive case in a sidelink unicast according to 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 communications, ultra-reliable (e.g., mission-critical) communications, low-latency communications, communications with low-cost and low-complexity devices, or any combination thereof.

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

[0061] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary, mobile, or both at different times. The UEs 115 may be devices of different forms or with different capabilities. Figure 1 Some exemplary UEs 115 are shown in FIG. 1. 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), such as Figure 1 shown.

[0062] The base stations 105 may communicate with each other, or with the core network 130, or both. For example, the base stations 105 may 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 may communicate with each other directly (e.g., directly between the 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 may be or include one or more wireless links. The one or more base stations 105 described herein may include or may be referred to by a person of ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next generation NodeB or a gigabit NodeB (any of which may be referred to as a gNB), a home NodeB, a home eNodeB or other suitable terms.

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

[0064] The UE 115 and the base station 105 can communicate with each other wirelessly 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 of a radio spectrum band (e.g., a bandwidth portion (BWP)) that operates according to a physical layer channel 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 operations, 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. Depending on 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.

[0065] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be positioned according to a channel grid for ease of discovery by UE 115. A carrier may operate in a standalone mode, where initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, where connections are anchored using different carriers (e.g., the same or different radio access technologies).

[0066] 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 communications (e.g., in FDD mode), or may be configured to carry downlink and uplink communications (e.g., in TDD mode). A carrier may be associated with a specific 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). A device 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 communications on a specific carrier bandwidth, or may be configured to support communications on one bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 and / or a UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0067] The signal waveform transmitted through the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may be composed of a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, wherein the symbol period and the subcarrier spacing are anti-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 received by UE 115 and the higher the order of the modulation scheme, the higher the data rate of 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 communications with UE 115.

[0068] The time interval of the base station 105 or the UE 115 can be expressed as a multiple of the basic time unit. For example, the basic time unit can refer to T s =1 / (Δf max ·N f ) seconds sampling period, where Δf max It can represent the maximum supported subcarrier spacing, and N fThe maximum supported discrete Fourier transform (DFT) size can be represented. The time intervals of communication resources can be organized according to radio frames, each radio frame having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023). Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some cases, the frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into multiple time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include multiple symbol periods (e.g., depending on the length of the cyclic prefix before each symbol period). In some wireless communication systems 100, the time slots may be further divided into multiple micro time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0069] A subframe, 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 a short TTI (sTTI)).

[0070] According to various techniques, physical channels can be multiplexed on a carrier. For example, a physical control channel and a physical data channel can be multiplexed on a downlink carrier using a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. The control region (e.g., a control resource set (CORESET)) of a physical control channel can be defined by multiple symbol periods and can be extended across a system bandwidth of a carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, a UE 115 can monitor or search for control information in a control region according to one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate can refer to multiple 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 can include a common search space set configured for sending control information to multiple UEs 115 and a UE-specific search space set for sending control information to a specific UE 115.

[0071] Each base station 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or various combinations thereof). The term "cell" may refer to a logical communication entity used to communicate with the base station 105 (e.g., via a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), etc.) used to distinguish adjacent cells. In some examples, a cell may also refer to a geographic coverage area 110 or a portion of a geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. 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 the base station 105. For example, a cell may be or include a building, a subset of a building, an external space between or overlapping geographic coverage areas 110, and the like.

[0072] A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to a UE 115 that supports a macro cell and has subscribed to a network provider's service. Compared to a macro cell, a small cell may be associated with a low-power base station 105, and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 that has subscribed to a network provider's service, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed user group (CSG), a UE 115 associated with a user in a home or office, etc.). A 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 that may provide access to different types of devices (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB) or other).

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

[0074] Some UEs 115, such as MTC devices or IoT devices, may be low-cost or low-complexity devices and may provide automatic communication between machines, such as via machine-to-machine (M2M) communication. M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a base station 105 without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate 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 may be designed to collect information or implement automatic behavior of machines or other devices. Application examples of MTC devices include smart meters, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

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

[0076] 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. UE115 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.

[0077] In some cases, UE 115 can also communicate directly with other UE 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 geographic coverage area 110 of the base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of the base station 105 or unable 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, wherein each UE 115 transmits to each 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.

[0078] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these communications. The vehicles can send information related to traffic conditions, signal scheduling, weather, safety, emergency situations, 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.

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

[0080] Some network devices, such as base stations 105, may include subcomponents, such as access network entities 140, which may be examples of access node controllers (ANCs). Each access network entity 140 may communicate with UE 115 through multiple other access network transport entities 145, which may be referred to as radio heads, smart radio heads, or transmit / receive points (TRPs). Each access network transport 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 merged into a single network device (e.g., base station 105).

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

[0082] The wireless communication system 100 can also operate in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as the millimeter wave band). In some examples, the wireless communication system 100 can support mmW communications between the UE 115 and the base station 105, and the EHF antennas of the corresponding devices can be smaller and closer than the UHF antennas. In some cases, this can facilitate the use of antenna arrays within the UE 115. However, compared with ultra-high frequency (SHF) transmissions or UHF transmissions, the propagation of EHF transmissions may be subject to greater atmospheric attenuation and shorter distances. The technology disclosed herein can be adopted in transmissions using one or more different frequency regions, and the designated use of frequency bands on these frequency regions may vary from country to country or regulatory agency.

[0083] The wireless communication system 100 can utilize licensed and unlicensed radio spectrum bands. For example, the wireless communication system 100 can adopt license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed radio spectrum band, devices such as base stations 105 and UEs 115 can use carrier sensing for conflict detection and conflict avoidance. In some cases, operations in unlicensed bands can be based on carrier aggregation configurations and component carriers operating in licensed bands (e.g., LAA). Operations in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, D2D transmissions, and the like.

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

[0085] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station 105, a UE 115) to shape or steer 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 may be achieved by combining signals transmitted via antenna elements of an antenna array so that some signals propagating at a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustment of signals transmitted via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals transmitted via antenna elements associated with the device. Adjustments associated with each antenna element may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).

[0086] 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 based on IP. The radio link control (RLC) layer can perform packet segmentation and reorganization to communicate on the logical channel. The media access control (MAC) layer can perform priority processing and multiplex the logical channel into a transport channel. The MAC layer can also use error detection technology, error correction technology, or both to support retransmission of 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 UE115 and the base station 105 or the core network 130 supporting the radio bearer of the user plane data. At the physical layer, the transport channel can be mapped to the physical channel.

[0087] UE 115 and 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 through 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 poor 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, wherein the device can provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In other cases, the device can provide HARQ feedback in a subsequent time slot or according to other time intervals.

[0088] 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., to save energy and extend 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) communications and a "DRX period" during which the UE 115 can turn off the radio component. 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 inactive timer." If the scheduling message is successfully received, the UE 115 may be ready to receive data, and the DRX inactive timer may be reset. When the DRX inactive timer expires without receiving a scheduling message, the UE 115 may suppress further monitoring of the remainder of the DRX cycle (e.g., the UE 115 may turn off the radio component). Additionally or alternatively, UE 115 may enter a short DRX cycle and may start a "DRX short cycle timer". When the DRX short cycle timer expires, UE 115 may enter a long DRX cycle (e.g., shut down the radio component for a relatively long period of time). However, in some wireless communication systems, the use of such timers may be inefficient. For example, an 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 be able to receive sidelink communications.

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

[0090] In some examples, other UEs 115 in the group UE 115 may be referred to as "member" UEs 115. The member UEs 115 may communicate with the group UE 115 using sidelink communications. The member UEs 115 may identify the group leader UE 115 (e.g., based on a notification from an upper layer, based on information from an AS layer to determine the group leader UE 115, or both). The member UEs 115 may provide service information (e.g., group member ID, transmission schedule of the member UEs 115, etc.) to the group leader UE 115 and / or the upper layer. In some examples, the member UEs 115 may continuously monitor sidelink communications from the group UE 115. The member UEs 115 may receive a DRX configuration from the group leader UE 115 (e.g., based on a notification 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 indicating that each member UE 115 of the group of UEs 115 may communicate during wake-up periods and turn off radio components during DRX periods of the DRX cycle. The DRX configuration may be for a single DRX cycle or multiple DRX cycles.

[0091] One or more of the UEs 115 may include a UE communication manager 101 that may identify a schedule associated with the UE 115 and another UE 115 in a group of UEs 115 that communicate 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 directional communication between the UE 115 and the other UE 115 (e.g., a wake-up period reserved for unidirectional communication from the UE 115 to the other UE 115, or a wake-up period reserved for bidirectional communication between the UE 115 and the other UE 115, or a combination thereof). The UE communication manager 101 may manage the wake-up period reserved for directional communication (e.g., one or more of the wake-up period reserved for unidirectional communication or the wake-up period reserved for bidirectional communication based on traffic information associated with the UE 115), and communicate with the other UE 115 according to the management.

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

[0093] Figure 2 An example of a wireless communication system 200 supporting D2D scheduling according to aspects of the present disclosure is shown. In some examples, the wireless communication system 200 can implement aspects of the wireless communication system 100 and can include a group of UEs 115 (e.g., UE 115-a, UE 115-b, and UE 115-c) and a base station 105-a, which can be referenced to Figure 1 An example of a UE 115 and a base station 105 is described. In some cases, the group of UEs 115 may communicate with each other (e.g., in a V2X system, a D2D system, etc.), and scheduling operations (e.g., associated with D2D communications) may be employed to save energy and ensure reliable communications.

[0094] In accordance with some aspects, the group of UEs 115 may communicate with each other (or with another group of UEs 115) via sidelink communications 205 (e.g., using a P2P or D2D protocol). For example, UE 115-a may monitor a resource pool for sidelink communications 205 and / or indications of sidelink communications 205 (e.g., resource reservations, control channel transmissions, etc., for example) from UE 115-b and UE 115-c. Additionally or alternatively, user equipment 115-a may have data to send to UE 115-b and / or UE 115-c and may send the data using sidelink communications 205.

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

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

[0097] A technique for direct communication (e.g., D2D communication) between UEs 115 is proposed, which can ensure reliable communication, efficient use of resources and energy saving. In one example, UE 115-a can identify a schedule associated with UE 115-b in a group of UEs 115 that are in direct communication with UE 115-a and UE 115-a. The schedule can 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 unidirectional communication from UE 115-a to UE 115-b, or a wake-up period reserved for bidirectional 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 period reserved for unidirectional communication or the wake-up period reserved for bidirectional communication) based on business information associated with UE 115-a, and communicate with UE 115-b according to the management.

[0098] According to an example of aspects described herein, UE 115 may utilize update message 210 to manage wake-up periods reserved for directional communications (e.g., wake-up periods reserved for one-way communications or two-way communications). Update message 210 may include a request message or a response message. For example, UE 115-a may send a request message to UE 115-b based on business information associated with UE 115-a, and may receive a response message based on the request message from UE 115-b. In some examples, UE 115-a may manage wake-up periods reserved for directional communications (e.g., one or more of the wake-up periods reserved for one-way communications or two-way communications) based on the response message.

[0099] From the exemplary perspective of UE 115-b, UE 115-b can also identify a schedule associated with UE 115-b and UE 115-a. The schedule can include a wake-up period reserved for directional communication between UE 115-b and UE 115-a (e.g., a wake-up period reserved for unidirectional communication from UE 115-b to UE 115-a or from UE 115-a to UE 115-b, or a wake-up period reserved for bidirectional communication between UE 115-b and UE 115-a, or a combination thereof). UE 115-b can be managed based on business information associated with UE 115-b or UE 115-a, and communicate with UE 115-a based on the management.

[0100] According to an example of aspects described herein, UE 115-b may receive an update message 210 (e.g., a request message) from UE 115-a and may send an update message 210 (e.g., a response message) to UE 115-a based on the request message and service information associated with UE 115-b. In some examples, UE 115-b may manage wake-up periods reserved for directional communications (e.g., one or more of wake-up periods reserved for one-way communications or wake-up periods reserved for two-way communications) based on the request message and service information associated with UE 115-b.

[0101] Figure 3 An example of a wireless system 300 that supports methods for scheduling in the case of inactivity in sidelink unicast according to aspects of the present disclosure is shown. In some examples, the wireless system 300 may implement the method described herein with reference to Figure 1 and Figure 2 The wireless system 300 may include UE 115 (eg, UE 115-d to 115-i), which may be as described herein. Figure 1 and Figure 2 Examples of aspects of UE 115 and UE 115-a to UE 115-c are described.

[0102] Figure 3 An example is shown in which UE 115 is able to communicate directly with other UEs 115. In this example, UE 115-d can communicate directly (e.g., using a P2P or D2D protocol) with UE 115-e through UE 115-i. For example, UE 115-d can communicate directly with UE 115-e (e.g., as shown in solid lines), and can communicate directly with any of UEs 115-f through 115-i (e.g., as shown in dashed lines). Sidelink communication 305 and update message 310 can be as described herein. Figure 2 1 and 1 . Examples of aspects of sidelink communication 205 and update message 210 are described. Communication link 315 may include sidelink communication 305. In some examples, communication link 315 may include directional communication between a UE and another UE 115. For example, communication link 315 may include unidirectional communication from UE 115 to another UE 115 or bidirectional communication between 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).

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

[0104] In the mmW spectrum, communication conflicts may increase. For example, if another UE 115 is not in an RX state on a particular beam direction (e.g., an RX beam direction associated with the TX beam direction of UE 115), UE 115 (e.g., UE 115-d) may not be able to transmit to another UE 115 (e.g., any one of UE 115-e to UE 115-i). For example, for communications in the mmW spectrum, the complexity associated with scheduling multiple direct communications (e.g., D2D links) in different directions may be much higher than in other spectrums. For example, for communications in the mmW spectrum, if UE 115-d is communicating with UE 115-e and wants 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 scheduling between UE 115-d and UE 115-e and start transmitting to UE 115-f. In mmW communications, UE 115 - d may not be free to modify scheduling based on the availability of peer UEs 115 (eg, UE 115 - f ).

[0105] For example, for mmW spectrum, contention-based access may not be sufficient (e.g., for successful communication transmission) 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 may be better served (e.g., utilized) on a reserved basis so that UE scheduling (e.g., scheduling of UE 115) may be more deterministic.

[0106] For example, similar to the DRX cycle and DRX processing, beam unavailability in a beam direction (e.g., “beam direction unavailable”) may produce similar effects as DRX with respect to UE scheduling. 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., a wake-up period) for communication. In some examples, outside of the “onDuration” period associated with the unicast link, UE 115-d and UE 115-e may not necessarily be available for the unicast link. For example, outside of 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 used for communication (e.g., a unicast link) with other UEs 115 in the group of UEs (e.g., UE 115-f to UE 115-i) or another group of UEs.

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

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

[0109] According to examples of aspects of the present invention, based on traffic demand or traffic demand prediction, UE 115 can manage (e.g., modify, maintain, or remove) a reserved “onDuration” (e.g., a wake-up period) associated with communication (e.g., directional communication) between UE 115 and other UEs 115. In one example, based on traffic demand or traffic demand prediction, UE 115 can modify, maintain, or remove a reserved “onDuration” associated with communication between UE 115 and other UEs 115. For example, UE 115-d can modify, maintain, or remove a reserved “onDuration” associated with communication (e.g., directional communication) between UE 115-d and any one of UE 115-e to UE 115-i based on traffic demand or traffic demand prediction.

[0110] According to an example of aspects described herein, UE 115 may manage "onDuration" using update message 310. Update message 310 may include a request message or a response message. For example, UE 115-d may send a request message to UE 115-e based on service information associated with UE 115-d, and may receive a response message based on the request message from UE 115-e.

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

[0112] In some examples, UE 115-d may indicate in the request message that UE 115-d will serve other links (e.g., other communication links 315, sidelink communications 305) for more time than the assigned scheduled “onDuration” and that the “onDuration” on the directional link (e.g., the communication link 315 between UE 115-d and UE 115-e, sidelink communications 305) can no longer be guaranteed. In some examples, UE 115-d may indicate in the request message that UE 115-d is processing more traffic than UE 115-d expected or predicted. For example, UE 115-d may determine that the traffic load associated with UE 115-d meets a threshold (e.g., exceeds the expected traffic load).

[0113] Figure 4 An example of a timing diagram 405 and a timing diagram 410 are shown for supporting a method for scheduling in an inactive situation in a sidelink unicast according to aspects of the present disclosure. In some examples, the timing diagrams 405 and 410 may implement the method described herein with reference to Figure 1 , Figure 2 and Figure 3 Aspects of described systems 100, 200, and 300. Timing diagrams 405 and 410 illustrate examples of aspects of scheduled “onDuration” periods (e.g., wake-up periods) associated with bidirectional communications and unidirectional communications between UE A (e.g., UE 115-d) and additional UEs, UE B1, UE B2, and UE B3 (e.g., UE 115-e to UE 115-g).

[0114] Timing diagram 405 illustrates an example of a two-way communication schedule, where UE A may 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) may correspond to a wake-up period associated with two-way communication between UE A and UE B1, “onDuration” period 430 (e.g., B2) may correspond to a wake-up period associated with two-way communication between UE A and UE B2, and “onDuration” period 435 (e.g., B3) may correspond to a wake-up period associated with two-way communication between UE A and UE B3.

[0115] Timing diagram 410 shows an example of a one-way communication schedule, where, for a peer UE transmitting to another peer UE, separate "onDuration" periods may 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 may have a separate "onDuration" period for traffic in the direction from UE A to UE B1, and UE B1 may have a separate "onDuration" period for traffic in the direction from UE B1 to UE A. For example, an “onDuration” period 440 (e.g., B1 TX) may correspond to a wake-up period reserved for unidirectional communication from UE A to UE B1 (e.g., instead of from UE B1 to UE A), an “onDuration” period 445 (e.g., B2 RX) may correspond to a wake-up period reserved for unidirectional communication from UE B2 to UE A (e.g., instead of from UE A to UE B2), and an “onDuration” period 450 (e.g., B3 TX) may correspond to a wake-up period reserved for unidirectional communication from UE A to UE B3 (e.g., instead of from UE B3 to UE A).

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

[0117] As described herein with respect to the exemplary unidirectional scheduling in timing diagram 405, “ON” time slots (e.g., “onDuration” periods, wake-up periods) may be reserved for both directions from UE 115 to another UE 115 and from another UE 115 to UE 115 (e.g., “onDuration” period 425 (e.g., B1) may correspond to a wake-up period reserved for bidirectional communications 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 bidirectional scheduling for the “onDuration” period (e.g., “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 transmissions 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).

[0118] 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, for example, traffic associated with 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., deform) the "onDuration" period 425 from an "onDuration" period for two-way communication (e.g., communication from UE B1 to UE A and communication from UE B1 to UE A) to an "onDuration" period for one-way communication (e.g., from UE B1 to UE A). In some examples, since the traffic demand associated with the modified "onDuration" can be reduced (e.g., reduced to half, based only on one-way communication from UE B1 to UE A), UE A (e.g., and UE B1) may adjust the duration (e.g., time slot size) of the "onDuration" period.

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

[0120] 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 unidirectional scheduling for the “onDuration” period of “TX B” (e.g., “onDuration” period 440). 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), and UE A may request in the request message to delete the “onDuration” occurrence (e.g., “onDuration” period 440).

[0121] According to examples of various aspects of the present invention, UE A (e.g., UE 115-d) may request to delete "onDuration" occurrences associated with "fast changes" or "slow changes" (e.g., "onDuration" period 440). In one example, UE A may signal inactivity with reference to the original negotiated schedule between UE A and UE B1 (e.g., UE 115-e). UE A may signal the duration of inactivity relative to the original negotiated schedule. In the example of "fast changes", UE A may include in the request message a request to delete or modify a single cycle T or multiple cycles T starting from or after the current cycle T. The "onDuration" period 440 (e.g., B1 Tx) after which UE A and UE B1 may resume communication according to the original negotiated schedule. In another example of "fast changes", UE A may include in the request message a request to delete or modify the "onDuration" period 440 of all cycles T starting from or after the current cycle T (e.g., the release of the unicast link between UE A and UE B1). In the “slowly changing” example, UE A may migrate or renegotiate the deletion or modification of the “onDuration” period 440 over multiple periods T (e.g., over a separate signal or request message sent from UE A to UE B1). According to examples of aspects described herein, UE A may no longer have traffic or communications associated with communications from UE A to UE B1 and from UE B1 to UE A. In these examples, UE A may include in the request message a request to release the unicast link between UE A and UE B1, which may release all “onDuration” time slots or periods of “TX A / B” (e.g., “onDuration” period 440) and “RX A / B” (not shown).

[0122] Figure 5 An example of a process flow 500 of a method for supporting scheduling in an inactive case in a sidelink unicast according to aspects of the present disclosure is shown. The process flow 500 may illustrate an exemplary scheduling scheme (e.g., D2D scheduling) between UEs 115 of a wireless system. For example, UE 115-j and UE 115-k may perform a scheduling process for an "onDuration" period (e.g., a wake-up period) associated with a one-way communication or a two-way communication.

[0123] UE 115-j and UE 115-k may be reference Figures 1 to 4Examples of corresponding wireless devices described. For example, UE 115-j and UE 115-k can communicate directly with each other (e.g., D2D communication). In some cases, either UE 115-j and UE 115-k can initiate the exemplary scheduling process (e.g., send a request message or a response message). The following alternative examples may be implemented, in which 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.

[0124] 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 directional 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 directional 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 business information associated with UE 115-j. According to an example 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 the 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., the reason for the change). For example, the cause indication may include inactivity associated with directional communications (e.g., one or more of unidirectional communications or bidirectional communications), or a traffic load associated with UE 115-j that meets a threshold (e.g., a traffic load that exceeds an expected traffic load).

[0125] In one example, the request message may include an impact period (e.g., a number of cycles T associated with the change). For example, the impact period may include a number of cycles associated with modifying a wake-up period reserved for directional communication (e.g., a wake-up period reserved for unidirectional communication or one or more of 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 a duration (e.g., an adjusted duration) of a wake-up period reserved for directional 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 a bit value to a field 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.

[0126] At 520, UE 115-k may send a response message to UE 115-j. UE 115-k may send a request message based on business information associated with UE 115-k or UE 115-j. According to an example of aspects described herein, UE 115-k may send a response message via UE signaling described herein. 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 one example, where the response message is a PC5-RRC message, the response message may include a response code (e.g., acceptance, rejection). For example, if accepted, the response message may include a confirmation associated with the request message (e.g., acceptance). In another example, the response message may include a negative confirmation associated with the request message (e.g., rejection).

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

[0128] At 525, UE 115-j may manage the wake-up period reserved for directional communication (e.g., one or more of the wake-up period reserved for unidirectional communication or the wake-up period reserved for bidirectional communication) based on the service information associated with UE 115-j or the response message. At 530, UE 115-k may manage the wake-up period reserved for directional communication (e.g., one or more of the wake-up period reserved for unidirectional communication or the wake-up period reserved for bidirectional communication) based on the service 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 aspects of the present invention, in which the described UE signaling includes the use of MAC CE messages, the example of aspects 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, the processing flow 500 may include aggregation of MAC-CE messages with the transmitted data.

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

[0130] The receiver 610 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 methods for scheduling in the case of inactivity in sidelink unicast). The information may be passed to other components of the device 605. The receiver 610 may be a reference Fig. 9 Examples of aspects of the transceiver 920 are described. The receiver 610 may use a single antenna or a collection of antennas.

[0131] The UE communication manager 615 may identify a schedule associated with the device 605 and an additional device in a group of devices that communicate directly with the device 605, wherein the schedule includes a wake-up period reserved for directional 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 may manage the wake-up period reserved for directional communication (e.g., one or more of the wake-up period reserved for unidirectional communication or the wake-up period reserved for bidirectional communication) based on the service information associated with the device 605, and communicate with the additional device according to the management.

[0132] The UE communication manager 615 may 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, wherein the schedule includes a wake-up period reserved for directional 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 directional communication (e.g., one or more of the wake-up period reserved for unidirectional communication or the wake-up period reserved for bidirectional communication) based on traffic information associated with the device 605 or the additional device; and communicate with the additional device according to the management. The UE communication manager 615 may be an example of aspects of the UE communication manager 910 described herein.

[0133] The UE communication manager 615 or its subcomponents may 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 subcomponents may 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 the present disclosure.

[0134] The UE communication manager 615 or its subcomponents may be physically located in different locations, including being distributed so that part of the functionality is implemented by one or more physical components in different physical locations. In some examples, according to various aspects of the present disclosure, the UE communication manager 615 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of the present disclosure, the UE communication manager 615 or its subcomponents 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.

[0135] Transmitter 620 can transmit signals generated by other components of device 605. In some examples, transmitter 620 can be collocated with receiver 610 in a transceiver module. For example, transmitter 620 can be a reference Fig. 9 Examples of aspects of the transceiver 920 are described. The transmitter 620 may utilize a single antenna or a collection of antennas.

[0136] Figure 7 A block diagram 700 of a device 705 supporting a method for scheduling in a sidelink unicast inactive case according to aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or 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).

[0137] 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 methods for scheduling in the case of inactivity in sidelink unicast). The information may be passed to other components of the device 705. The receiver 710 may be a reference Fig. 9 Examples of aspects of the transceiver 920 are described. The receiver 710 may use a single antenna or a collection of antennas.

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

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

[0140] Management component 725 can manage wake-up periods reserved for directional communication (e.g., one or more of wake-up periods reserved for one-way communication or wake-up periods reserved for two-way communication) based on traffic information associated with device 705. In some examples, management component 725 can manage wake-up periods reserved for directional communication based on traffic information associated with an additional device or device 705. Communication component 730 can communicate with an additional device in accordance with the management. In some examples, communication component 730 can communicate with a device in accordance with the management.

[0141] Transmitter 735 can transmit signals generated by other components of device 705. In some examples, transmitter 735 can be collocated with receiver 710 in a transceiver module. For example, transmitter 735 can be a reference Fig. 9 Examples of aspects of the transceiver 920 are described. The transmitter 735 may utilize a single antenna or a collection of antennas.

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

[0143] The scheduling component 810 can identify a schedule associated with a device and an additional device in a group of devices that communicate directly with the device, wherein the schedule includes a wake-up period reserved for directional communication between the device and the additional device (e.g., a wake-up period reserved for unidirectional communication from the device to the additional device, or a wake-up period reserved for bidirectional communication between the device and the additional device, or a combination thereof). In some examples, the scheduling component 810 can identify a schedule associated with an additional device and a device in the group of devices that communicate directly with the additional device, wherein the schedule includes a wake-up period reserved for directional 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 can determine, based on the business information, inactivity associated with the wake-up period reserved for directional communication (e.g., one or more of unidirectional communication or bidirectional communication).

[0144] The management component 815 can manage the wake-up periods reserved for directional communication (e.g., one or more of the wake-up periods reserved for one-way communication or the wake-up periods reserved for two-way communication based on the traffic information associated with the device). In some examples, the management component 815 can manage the wake-up periods reserved for directional communication (e.g., one or more of the wake-up periods reserved for one-way communication or the wake-up periods reserved for two-way communication) based on the traffic information associated with the additional device or devices. In some examples, the management component 815 can manage the wake-up periods reserved for directional communication based on the response message. In some examples, the management component 815 can manage the wake-up periods reserved for directional communication based on inactivity.

[0145] In some examples, the management component 815 can manage the wake-up period reserved for directional communication (e.g., one or more of the wake-up period reserved for one-way communication or the wake-up period reserved for two-way communication) based on the traffic load meeting the threshold. In some examples, the management component 815 can manage the wake-up period reserved for directional communication based on the comparison. In some examples, the management component 815 can release one or more resources associated with the wake-up period reserved for one-way communication based on the response message. In some examples, the management component 815 can adjust the duration of the wake-up period reserved for one-way communication 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 directional communication (e.g., two-way communication) based on the response message.

[0146] In some examples, the management component 815 can adjust the duration of the wake-up period reserved for directional communication (e.g., two-way communication) based on the response message. In some examples, the management component 815 can allocate the wake-up period reserved for directional communication (e.g., two-way communication) exclusively to the 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 unidirectional communication from the device to the additional device based on the termination. In some examples, the management component 815 can allocate the wake-up period reserved for directional communication (e.g., two-way communication) exclusively to the additional device based on the indication received from the device.

[0147] In some examples, the management component 815 can manage the wake-up period reserved for directional communication (e.g., one or more of the wake-up period reserved for unidirectional communication or the wake-up period reserved for bidirectional communication) based on the request message and the business information associated with the additional device. In some examples, the management component 815 can manage the wake-up period reserved for directional communication based on inactivity associated with directional communication between the device and the additional device (e.g., one or more of the following: inactivity associated with unidirectional communication from the device to the additional device, inactivity associated with unidirectional communication from the additional device to the device, or inactivity associated with bidirectional communication. In some examples, the management component 815 can manage the wake-up period reserved for directional communication based on inactivity associated with directional communication (e.g., inactivity associated with unidirectional communication from the device to the additional device).

[0148] In some examples, the management component 815 may release one or more resources associated with a wake-up period reserved for directional communication (e.g., one-way communication) based on the request message and the business information. In some examples, the management component 815 may adjust the duration of one or more of the wake-up periods reserved for directional communication (e.g., one-way communication from an attached device to a device or a wake-up period reserved for one-way communication from a device to an attached device) based on the request message and the business information. In some examples, the management component 815 may release one or more resources associated with a wake-up period reserved for directional communication (e.g., two-way communication) based on the request message and the business information. In some examples, the management component 815 may adjust the duration of the wake-up period reserved for directional communication (e.g., two-way communication) based on the response message and the business information.

[0149] In some examples, the management component 815 can allocate a wake-up period reserved for directional communication (e.g., two-way communication) exclusively to the attached device based on the request message and the service information. In some examples, the management component 815 can release one or more resources associated with the wake-up period reserved for directional communication between the attached device and the device (e.g., one-way communication from the attached device to the device) based on the termination. In some examples, the management component 815 can allocate a wake-up period reserved for directional communication (e.g., two-way communication) exclusively to the device based on the service information associated with the attached device or the device.

[0150] The communication component 820 can communicate with the additional device according to the management. In some examples, the communication component 820 can communicate with the additional device based on releasing one or more resources associated with the wake-up period reserved for one-way communication. In some cases, the wake-up period reserved for directional communication (e.g., two-way communication) is shared between the device and the additional device. In some cases, the wake-up period reserved for directional communication (e.g., one-way communication) is not shared between the device and the additional device.

[0151] 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 of a wake-up period reserved for directional communication (e.g., one-way communication). In some cases, the communication component 820 may communicate with the additional device based on the duration of the wake-up period reserved for directional communication (e.g., one-way communication). In some examples, the communication component 820 may communicate with the additional device based on the indication of removing the wake-up period reserved for directional 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 period reserved for directional communication (e.g., two-way communication). In some examples, the communication component 820 may communicate with the additional device based on an indication of a wake-up period reserved for directional communication (e.g., two-way communication). In some cases, the communication component 820 may communicate with the additional device based on the duration of the wake-up period reserved for directional communication (e.g., two-way communication).

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

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

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

[0155] In some examples, the communication component 820 can communicate with the device based on adjusting the duration of the wake-up period reserved for directional communication (e.g., two-way communication) and one or more of the response message. In some examples, the communication component 820 can communicate with the device based on the wake-up period reserved for directional communication (e.g., two-way communication) is specifically allocated to the additional device and the response message. In some examples, the communication component 820 can communicate with the device based on the wake-up period reserved for directional communication (e.g., two-way communication) is specifically allocated to the device. In some examples, the communication component 820 can communicate with the device based on confirmation. In some examples, the communication component 820 can communicate with the device based on one or more of the negative confirmation or the reason indication of the negative confirmation.

[0156] The messaging component 825 may send a request message to the additional device based on the business information associated with the device. In some examples, the messaging component 825 may receive a response message based on the request message from the additional device. In some examples, the messaging component 825 may include a cause indication in the request message based on determining that the cause indication indicates inactivity. In some examples, the messaging component 825 may include a cause indication in the request message based on determining that the business load associated with the device meets a threshold. In some examples, the messaging component 825 may include an indication in the request message to remove a wake-up period reserved for directional communication (e.g., one-way communication) based on the business information.

[0157] In some examples, the messaging component 825 may include in the request message an indication to modify the wake-up period reserved for directional communication (e.g., one-way communication) based on the business information. In some examples, the messaging component 825 may include in the request message an indication to remove the wake-up period reserved for directional communication (e.g., two-way communication) based on the business information. In some examples, the messaging component 825 may include in the request message an indication to modify the wake-up period reserved for directional communication (e.g., two-way communication) based on the business information. In some examples, the messaging component 825 may include in the request message an indication to allocate the wake-up period reserved for directional communication (e.g., two-way communication) specifically to the attached device based on the business information. In some examples, the messaging component 825 may receive from the attached device an indication that the wake-up period reserved for directional communication (e.g., two-way communication) is allocated specifically to the device.

[0158] 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 the wake-up period reserved for modified directional communication. In some cases, the cause indication includes traffic information associated with the additional device or the number of available resources associated with the additional device for allocation to the device for directional communication (e.g., two-way communication).

[0159] In some examples, the messaging component 825 may receive a request message from the device, the request message including business 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 the business information associated with the additional device. In some examples, the messaging component 825 may identify in the request message an indication of removing a wake-up period reserved for directional communication (e.g., one-way communication). In some examples, the messaging component 825 may include in the response message a confirmation associated with releasing one or more resources, the one or more resources being associated with the wake-up period reserved for directional communication (e.g., one-way communication). In some examples, the messaging component 825 may identify in the request message an indication of modifying the wake-up period reserved for directional communication (e.g., one-way communication).

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

[0161] 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 the wake-up period reserved for modified directional communication. In some cases, the request message carries an indication of a cause of inactivity associated with directional communication (e.g., one or more of a one-way communication or a two-way communication from the device to the attached device), and at least service information associated with the device. In some cases, based on the service information associated with the device, the request message carries a cause indication that the service load associated with the device meets a threshold. In some cases, the cause indication includes service information associated with the attached device or the number of available resources associated with the attached device for directional communication (e.g., two-way communication) allocated to the device.

[0162] The business component 830 can determine that the business load associated with the device meets the threshold based on the business information. In some examples, the business component 830 can compare the business load associated with the device with the predicted business load associated with the device. The bit value component 835 can 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 directional communication (e.g., one-way communication). In some examples, the bit value component 835 can 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 directional communication (e.g., two-way communication). In some examples, the bit value component 835 can identify the bit value assigned to the field in the request message, wherein the bit value corresponds to the duration of the wake-up period reserved for directional communication (e.g., two-way communication). The confirmation component 840 can identify the confirmation associated with the request message in the response message. In some examples, the confirmation component 840 can identify the negative confirmation associated with the request message and the reason indication of the negative confirmation in the response message.

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

[0164] In some examples, based on the business information, the confirmation component 840 can include a confirmation associated with the request message in the response message. In some examples, based on the business information, the confirmation component 840 can include a negative confirmation associated with the request message and a cause indication of the negative confirmation in the response message. The termination component 845 can terminate a unicast link associated with a directional communication (e.g., a one-way communication) based on the business information. In some examples, the termination component 845 can terminate a unicast link associated with a directional communication (e.g., a one-way communication) based on the business information.

[0165] Fig. 9 A schematic diagram of a system 900 including a device 905 supporting a method for scheduling in an inactive case in a sidelink unicast according to various aspects of the present disclosure is shown. The device 905 may be an example of or include components of the device 605, device 705, or UE 115 described herein. The device 905 may include components for two-way voice and data communications, 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).

[0166] The UE communication manager 910 can identify a schedule associated with the device 905 and an additional device in a group of devices that communicate directly with the device 905, wherein the schedule includes a wake-up period reserved for directional communication between the device 905 and the additional device (for example, a wake-up period reserved for unidirectional communication from the device 905 to the additional device, or a wake-up period reserved for bidirectional communication between the device 905 and the additional device, or a combination thereof); manage the wake-up period reserved for directional communication based on business information associated with the device 905; and communicate with the additional device based on the management.

[0167] 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 an additional device, wherein the schedule includes a wake-up period reserved for directional communication between the device 905 and the additional device (for example, a wake-up period reserved for unidirectional communication from the device 905 to the device or from the additional device to the device 905, or a wake-up period reserved for bidirectional communication between the device 905 and the device, or a combination thereof); manage the wake-up period reserved for directional communication based on business information associated with the device 905 or the device; and communicate with the device according to the management.

[0168] I / O controller 915 can manage input signals and output signals of device 905. I / O controller 915 can also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 915 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 915 can use an operating system, such as MS- Or another known operating system. In other cases, I / O controller 915 can represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 915 can be implemented as part of a processor. In some cases, a user can interact with device 905 via I / O controller 915 or via hardware components controlled by I / O controller 915.

[0169] As described above, the transceiver 920 can communicate bidirectionally via one or more antennas, wired or wireless links. For example, the transceiver 920 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 920 can also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, and demodulate the 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, which can send or receive multiple wireless transmissions at the same time.

[0170] 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 a BIOS, etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0171] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the 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., memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks of a method for scheduling in an inactive situation in a sidelink unicast).

[0172] The code 935 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 935 may be stored in a non-transitory computer-readable medium, such as a system memory or other type of memory. In some cases, the code 935 may not be directly executable by the processor 940, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein.

[0173] Fig.10 A flow chart illustrating a method 1000 for supporting scheduling in a sidelink unicast inactive condition according to aspects of the present disclosure is shown. As described herein, the operations of the method 1000 may be implemented by the UE 115 or a component thereof. For example, the operations of the method 1000 may be implemented by reference to Figures 6 to 9 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 various aspects of the functions described below.

[0174] At 1005, the first UE may identify a schedule associated with the first UE and a second UE in a group of UEs in direct communication with the first UE, wherein the schedule includes a wake-up period reserved for directional 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 operations of 1005 may be performed according to the methods described herein. In some examples, aspects of the operations of 1005 may be performed by reference to Figures 6 to 9 Describes the scheduling component to execute.

[0175] At 1010, the first UE may manage a wake-up period reserved for directional communication based on traffic information associated with the first UE. The operations of 1010 may be performed according to the methods described herein. In some examples, aspects of the operations of 1010 may be described with reference to Figures 6 to 9 Described management components to perform.

[0176] At 1015, the first UE may communicate with the second UE according to the management. The operations of 1015 may be performed according to the methods described herein. In some examples, aspects of the operations of 1015 may be described with reference to Figures 6 to 9 The communication components described are performed.

[0177] Fig.11A flow chart illustrating a method 1100 for supporting scheduling in a sidelink unicast inactive condition according to aspects of the present disclosure is shown. As described herein, the operations of the method 1100 may be implemented by the UE 115 or a component thereof. For example, the operations of the method 1100 may be implemented by reference to Figures 6 to 9 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 various aspects of the functions described below.

[0178] At 1105, the first UE may identify a schedule associated with the first UE and a second UE in a group of UEs in direct communication with the first UE, wherein the schedule includes a wake-up period reserved for directional 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 operations of 1105 may be performed according to the methods described herein. In some examples, aspects of the operations of 1105 may be performed by reference to Figures 6 to 9 Describes the scheduling component to execute.

[0179] At 1110, the first UE may send a request message to the second UE based on the service information associated with the first UE. The operations of 1110 may be performed according to the methods described herein. In some examples, aspects of the operations of 1110 may be described in detail with reference to Figures 6 to 9 The message passing components described are implemented.

[0180] At 1115, the first UE may receive a response message based on the request message from the second UE. The operations of 1115 may be performed according to the methods described herein. In some examples, aspects of the operations of 1115 may be described with reference to Figures 6 to 9 The message passing components described are implemented.

[0181] At 1120, the first UE may manage a wake-up period reserved for directional 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 the traffic information associated with the first UE and the response message. The operations of 1120 may be performed according to the methods described herein. In some examples, aspects of the operations of 1120 may be described with reference to Figures 6 to 9 Described management components to perform.

[0182] At 1125, the first UE may communicate with the second UE in accordance with the management. The operations of 1125 may be performed in accordance with the methods described herein. In some examples, aspects of the operations of 1125 may be described with reference to Figures 6 to 9 The communication components described are performed.

[0183] Fig.12 A flow chart illustrating a method 1200 for supporting scheduling in a sidelink unicast inactive condition according to aspects of the present disclosure is shown. As described herein, the operations of the method 1200 may be implemented by the UE 115 or a component thereof. For example, the operations of the method 1200 may be implemented by reference to Figures 6 to 9 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 various aspects of the functions described below.

[0184] At 1205, the first UE may identify a schedule associated with the first UE and a second UE in a group of UEs in direct communication with the first UE, wherein the schedule includes a wake-up period reserved for directional 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 operations of 1205 may be performed according to the methods described herein. In some examples, aspects of the operations of 1205 may be performed by reference to Figures 6 to 9 Describes the scheduling component to execute.

[0185] At 1210, the first UE may manage a wake-up period reserved for directional 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 operations of 1210 may be performed according to the methods described herein. In some examples, aspects of the operations of 1210 may be described with reference to Figures 6 to 9 Described management components to perform.

[0186] At 1215, the first UE may communicate with the second UE in accordance with the management. The operations of 1215 may be performed in accordance with the methods described herein. In some examples, aspects of the operations of 1215 may be described in detail with reference to Figures 6 to 9 The communication components described are performed.

[0187] Fig.13 A flow chart illustrating a method 1300 for supporting scheduling in a sidelink unicast inactive condition according to aspects of the present disclosure is shown. As described herein, the operations of the method 1300 may be implemented by the UE 115 or a component thereof. For example, the operations of the method 1300 may be implemented by reference to Figures 6 to 9In 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 various aspects of the functions described below.

[0188] At 1305, the first UE may identify a schedule associated with the first UE and a second UE in a group of UEs in direct communication with the first UE, wherein the schedule includes a wake-up period reserved for directional 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 operations of 1305 may be performed according to the methods described herein. In some examples, aspects of the operations of 1305 may be performed by reference to Figures 6 to 9 Describes the scheduling component to execute.

[0189] At 1310, the first UE may receive a request message from the second UE, the request message including service information associated with the second UE. The operations of 1310 may be performed according to the methods described herein. In some examples, aspects of the operations of 1310 may be described with reference to Figures 6 to 9 The message passing components described are implemented.

[0190] At 1315, the first UE may send a response message to the second UE based on the request message and the service information associated with the first UE. The operation of 1315 may be performed according to the methods described herein. In some examples, various aspects of the operation of 1315 may be described by reference to Figures 6 to 9 The message passing components described are implemented.

[0191] At 1320, the first UE may manage a wake-up period reserved for directional 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 the request message and traffic information associated with the first UE or the second UE. The operations of 1320 may be performed according to the methods described herein. In some examples, aspects of the operations of 1320 may be described with reference to Figures 6 to 9 Described management components to perform.

[0192] At 1325, the first UE may communicate with the second UE in accordance with the management. The operations of 1325 may be performed in accordance with the methods described herein. In some examples, aspects of the operations of 1325 may be described with reference to Figures 6 to 9 The communication components described are performed.

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

[0194] The technology 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 can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95 and IS-856 standards. IS-2000 versions are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Speed ​​Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems can implement radio technologies such as Global System for Mobile Communications (GSM).

[0195] OFDMA systems can 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 Universal Mobile Telecommunications System (UMTS). LTE, LTE-A, and LTE-A Pro are versions of UMTS 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 "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The technology described herein can be used for the systems and radio technologies mentioned herein as well as other systems and radio technologies. Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may be applicable beyond LTE, LTE-A, LTE-A Pro, or NR applications.

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

[0197] The wireless communication systems described herein may support synchronous operation or asynchronous operation. For synchronous operation, the base stations may have similar frame timing, and transmissions from different base stations may be approximately consistent in time. For asynchronous operation, the base stations may have different frame timing, and transmissions from different base stations may be inconsistent in time. The techniques described herein may be used for synchronous operation or asynchronous operation.

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

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

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

[0201] Computer-readable media include non-transitory computer storage media and communication media, and communication media include any medium that is convenient for transmitting a computer program from one place to another. Non-transitory storage media can be any available medium that a general or special-purpose computer can access. As an example and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, disk storage or other magnetic storage device, 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 can be accessed by a general or special-purpose computer or a general or special-purpose processor. In addition, any connection is properly referred to as a computer-readable medium. For example, if the software is sent from a website, a server or other remote source using a coaxial cable, a fiber optic cable, a twisted pair, a digital subscriber line (DSL) or wireless technology (such as infrared, radio and microwave), then the coaxial cable, the fiber optic cable, the twisted pair, the DSL or wireless technology (such as infrared, radio and microwave) are all included in the definition of the medium. Disk and disc, as used herein, includes 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.

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

[0203] In the drawings, similar components or features may have the same reference number. Further, various components of the same type may be distinguished by following the reference number with a dash and a second reference that distinguishes between the similar components. If only the first reference number is used in the specification, the description applies to any one of the similar components having the same first reference number, regardless of the second or other subsequent reference numbers.

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

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

Claims

1. A method for wireless communication at a first UE in a group of user equipments (UEs), comprising: identifying a schedule associated with direct communication between the first UE and a second UE, wherein the schedule includes a wake-up period reserved for sending or receiving a one-way communication, wherein sending the one-way communication is configured separately from receiving the one-way communication; determining, based at least in part on traffic information associated with the first UE, a discontinuous reception configuration associated with sending or receiving the unidirectional 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 in the discontinuous reception configuration is based at least in part on a traffic load associated with the first UE and a predicted traffic load between the first UE and one or more other UEs including the second UE; and Communicate 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 based at least in part on the service information associated with the first UE; as well as A response message based at least in part on the request message is received from the second UE, wherein the wake-up period in a discontinuous reception configuration associated with sending or receiving the unidirectional communication is based at least in part 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 Medium Access Control-Control Element message.

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

5. The method according to claim 2, further comprising: Determining, based at least in part on the traffic information, that a traffic load associated with the first UE satisfies a threshold, wherein the wake-up period in a discontinuous reception configuration associated with sending or receiving the unidirectional communication is based at least in part on the traffic load satisfying the threshold; and Based at least in part on the determination that a traffic load associated with the first UE satisfies a threshold, including a cause indication in the request message, the cause indication indicating that the traffic load associated with the first UE satisfies the threshold, wherein sending the request message to the second UE comprises: Sending the request message carrying the cause indication to the second UE.

6. The method according to claim 5, wherein: Determining that the traffic load associated with the first UE satisfies the threshold includes: The traffic load associated with the first UE is compared to a predicted traffic load associated with the first UE, wherein managing the awake period reserved for the unidirectional communication is based at least in part on the comparison.

7. The method according to claim 2, further comprising: Based at least in part on the traffic information, an indication is included in the request message to remove the wake-up period reserved for the unidirectional communication, wherein the communication with the second UE is based at least in part on the indication.

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

9. The method according to claim 2, further comprising: Based at least in part on the traffic information, an indication is included 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 UE is based at least in part on the indication.

10. The method according to claim 2, further comprising: A bit value is 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 unidirectional communication.

11. The method according to claim 2, further comprising: Based at least in part on the traffic information, the request message includes an indication that the wake-up period reserved for sending or receiving the unidirectional communication is exclusively allocated to the second UE, wherein the communication with the second UE is based at least in part on the indication.

12. The method according to claim 1, further comprising: An indication is received from the second UE to allocate the wake-up period reserved for sending or receiving the one-way communication exclusively to the first UE, wherein the communication with the second UE is based at least in part on the indication.

13. The method according to claim 1, wherein: Based on the traffic load decreasing, the duration of the wake-up period in the discontinuous reception configuration is decreased, and based on the traffic load increasing, the duration of the wake-up period in the discontinuous reception configuration is increased.

14. A method for wireless communication at a first UE in a group of user equipments (UEs), comprising: identifying a schedule associated with direct communication between the first UE and a second UE, wherein the schedule includes a wake-up period reserved for sending or receiving a one-way communication, wherein sending the one-way communication is configured separately from receiving the one-way communication; determining, based at least in part on traffic information associated with the first UE or the second UE, a discontinuous reception configuration associated with sending or receiving the unidirectional 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 in the discontinuous reception configuration is based at least in part on a traffic load associated with the first UE and a predicted traffic load between the first UE and one or more other UEs including the second UE; and Communicate with the second UE according to the discontinuous reception configuration.

15. The method according to claim 14, further comprising: receiving a request message from the second UE, the request message including the service information associated with the second UE; as well as Sending a response message to the second UE based at least in part on the request message and the service information associated with the first UE or the second UE, wherein the wake-up period in the discontinuous reception configuration associated with sending or receiving the unidirectional communication is based at least in part on the request message and the service information associated with the first UE.

16. The method according to claim 15, wherein: One or more of the request message or the response message is a PC5 Radio Resource Control message or a Medium Access Control-Control Element message.

17. The method according to claim 15, wherein: The request message includes an indication of a number of cycles associated with modifying the wake-up period reserved for sending or receiving the unidirectional communication.

18. The method according to claim 15, wherein: The request message carries a cause indication based at least in part on the service information associated with the second UE, the cause indication indicating that the service load associated with the second UE meets a threshold, and wherein the wake-up period in the discontinuous reception configuration associated with sending or receiving the unidirectional communication is based at least in part on inactivity associated with the unidirectional communication between the second UE and the first UE.

19. The method according to claim 14, further comprising: Communicating with a third UE in the group of UEs according to a discontinuous reception configuration associated with sending or receiving the unidirectional communication.

20. The method of claim 15, further comprising: identifying in the request message an indication to remove the wake-up period reserved for sending or receiving the one-way communication; as well as releasing one or more resources associated with the wake-up period reserved for sending or receiving the unidirectional communication based at least in part on the request message and the traffic information; as well as A confirmation is included in the response message, and the confirmation is associated with the release of 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 partially based on one or more of the following: the response message and the release of the one or more resources associated with the wake-up period reserved for sending or receiving the one-way communication.

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

22. The method of claim 15, further comprising: identifying in the request message an indication to modify the wake-up period reserved for sending or receiving the one-way communication; as well as An acknowledgement associated with adjusting a duration of the wake-up period reserved for sending or receiving the unidirectional communication is included in the response message, wherein the communication with the second UE is based at least in part on the response message.

23. The method of claim 15, further comprising: One or more bit values ​​assigned to a field in the request message are identified, wherein the one or more bit values ​​correspond to a duration of the wake-up period reserved for sending or receiving the unidirectional communication.

24. The method of claim 15, further comprising: identifying in the request message an indication to remove or modify the wake-up period reserved for sending or receiving the one-way communication; as well as An acknowledgement is included in the response message, the acknowledgement being associated with releasing one or more resources associated with the wake-up period for sending or receiving the unidirectional communication, wherein the communication with the second UE is based at least in part on the response message.

25. The method of claim 15, further comprising: identifying in the request message an indication that the wake-up period reserved for sending or receiving the unidirectional communication is to be allocated exclusively to the first UE; as well as A confirmation is included in the response message, the confirmation being associated with allocating the wake-up period reserved for sending or receiving the unidirectional communication exclusively to the first UE, wherein the communication with the second UE is based at least in part on the response message.

26. The method of claim 14, further comprising: An indication is sent to the second UE associated with allocating the wake-up period reserved for sending or receiving the unidirectional communication exclusively to the second UE, wherein the communication with the second UE is based at least in part on the indication.

27. The method of claim 14, wherein: Based on the traffic load decreasing, the duration of the wake-up period in the discontinuous reception configuration is decreased, and based on the traffic load increasing, the duration of the wake-up period in the discontinuous reception configuration is increased.

28. A first device in a group of devices for wireless communication, comprising: means for identifying a schedule associated with direct communication between the first device and a second device, wherein the schedule includes a wake-up period reserved for sending or receiving one-way communications, wherein sending the one-way communications is configured separately from receiving the one-way communications; means for determining a discontinuous reception configuration associated with sending or receiving the unidirectional communication based at least in part on traffic information associated with the first apparatus, 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 in the discontinuous reception configuration is based at least in part on a traffic load associated with the first apparatus and a predicted traffic load between the first apparatus and one or more other apparatuses including the second apparatus; and Means for communicating with the second device according to the discontinuous reception configuration.

29. A first device in a group of devices for wireless communication, comprising: means for identifying a schedule associated with the first device and the second device, wherein the schedule includes a wake-up period reserved for sending or receiving one-way communications, wherein sending the one-way communications is configured separately from receiving the one-way communications; means for determining a discontinuous reception configuration associated with sending or receiving the unidirectional communication based at least in part on traffic information associated with the first apparatus or the second apparatus, 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 in the discontinuous reception configuration is based at least in part on a traffic load associated with the first apparatus and a predicted traffic load between the apparatus and one or more other apparatuses including the second apparatus; and Means for communicating with the second device according to the discontinuous reception configuration.

30. A computer-readable storage medium having stored thereon instructions for wirelessly communicating at a first UE in a group of user equipments (UEs), which when executed cause one or more processors to: identifying a schedule associated with direct communication between the first UE and a second UE, wherein: The schedule includes a wake-up period reserved for sending or receiving a one-way communication, wherein sending the one-way communication is configured separately from receiving the one-way communication; determining, based at least in part on traffic information associated with the first UE, a discontinuous reception configuration associated with sending or receiving the unidirectional 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 in the discontinuous reception configuration is based at least in part on a traffic load associated with the first UE and a predicted traffic load between the first UE and one or more other UEs including the second UE; and Communicate with the second UE according to the discontinuous reception configuration.

31. A computer readable storage medium having stored thereon instructions for wirelessly communicating at a first UE in a group of user equipments (UEs), which when executed cause one or more processors to: identifying a schedule associated with direct communication between the first UE and the second UE, wherein: The schedule includes a wake-up period reserved for sending or receiving a one-way communication, wherein sending the one-way communication is configured separately from receiving the one-way communication; determining, based at least in part on traffic information associated with the first UE or the second UE, a discontinuous reception configuration associated with sending or receiving the unidirectional 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 in the discontinuous reception configuration is based at least in part on a traffic load associated with the first UE and a predicted traffic load between the first UE and one or more other UEs including the second UE; and Communicate with the second UE according to the discontinuous reception configuration.

Images