Patent Description:
Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for configuring discontinuous reception (DRX) on sidelink communication channels.

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, or other similar types of services. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources with those users (e.g., bandwidth, transmit power, or other resources). Multiple-access technologies can rely on any of code division, time division, frequency division orthogonal frequency division, single-carrier frequency division, or time division synchronous code division, to name a few. These and other multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level.

Although wireless communication systems have made great technological advancements over many years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers, undermining various established wireless channel measuring and reporting mechanisms, which are used to manage and optimize the use of finite wireless channel resources. Consequently, there exists a need for further improvements in wireless communications systems to overcome various challenges.

<NPL>), provides a discussion on physical layer design considering sidelink DRX operation.

SUMMARY The invention is defined by the independent claims. Advantageous embodiments of the invention are given in the sub-claims.

The following description and the appended figures set forth certain features for purposes of illustration.

The appended figures depict certain features of the various aspects described herein and are not to be considered limiting of the scope of this disclosure.

Aspects of the present disclosure provide apparatuses and methods for configuring discontinuous reception (DRX) on sidelink communication channels.

Sidelink communications, also referred to as device-to-device (D2D) communication, enable myriad enhanced capabilities in wireless devices. For example, sidelink communications may enable a network to send data to a target wireless device that is not connected to the network via a relay wireless device that is connected to the network. As another example, sidelink communications may enable various safety features, such as vehicle-to-device communications that allow an approaching vehicle to notify a pedestrian with a wireless device of its imminent arrival. Many other use cases exist.

An issue with all wireless communications, including sidelink communications, for battery operated wireless devices (e.g., smartphones, smart wearables, and others) is that "listening" for such communications requires power. As such, wireless devices often implement discontinuous reception (DRX) modes in order to power down receiving equipment and save power. While power efficiency is improved, the ability to leverage advanced capabilities, such as those enabled by sidelink communications, is impacted.

Aspects described herein resolve this technical problem by coordinating sidelink DRX configurations between user equipments so that the user equipments are active at the same time-and thus need not be active as often. In other words, by aligning DRX active periods between user equipments, the user equipments ensure the ability to utilize sidelink communication capabilities while still saving power.

As described in more detail below, coordination of sidelink configurations may be accomplished with various designs. For example, a network may coordinate sidelink DRX configurations for multiple user equipments (e.g., in a relay-target relationship). As another example, a relay user equipment may coordinate sidelink configurations for itself and a target user equipment. As yet another example, a target user equipment may coordinate sidelink configurations for itself and a relay user equipment. In yet another example, a network may configure a relay user equipment's sidelink DRX cycle, and that relay user equipment may in-turn configure a target user equipment's DRX cycle.

Generally, the apparatuses and methods described herein improve network performance by, for example, extending reach and reducing data latency, and improve user equipment performance by enabling additional data sending and receiving opportunities while improving battery power. The additional data may be used to enable improved functions and capabilities at the user equipments.

<FIG> depicts an example of a wireless communications system <NUM>, in which aspects described herein may be implemented.

Generally, wireless communications system <NUM> includes base stations (BSs) <NUM>, user equipments (UEs) <NUM>, an Evolved Packet Core (EPC) <NUM>, and core network <NUM> (e.g., a <NUM> Core (5GC)), which interoperate to provide wireless communications services.

Base stations <NUM> may provide an access point to the EPC <NUM> and/or core network <NUM> for a UE <NUM>, and may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, delivery of warning messages, among other functions. Base stations may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, or a transceiver function, or a transmit reception point (TRP) in various contexts.

Base stations <NUM> wirelessly communicate with LTEs <NUM> via communications links <NUM>. Each of base stations <NUM> may provide communication coverage for a respective geographic coverage area <NUM>, which may overlap in some cases. For example, small cell <NUM>' (e.g., a low-power base station) may have a coverage area <NUM>' that overlaps the coverage area <NUM> of one or more macrocells (e.g., high-power base stations).

The communication links <NUM> between base stations <NUM> and UEs <NUM> may include uplink (UL) (also referred to as reverse link) transmissions from a UE <NUM> to a base station <NUM> and/or downlink (DL) (also referred to as forward link) transmissions from a base station <NUM> to a UE <NUM>. The communication links <NUM> may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity in various aspects.

Examples of UEs <NUM> include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or other similar devices. Some of UEs <NUM> may be internet of things (IoT) devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, or other IoT devices), always on (AON) devices, or edge processing devices. UEs <NUM> may also be referred to more generally as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, or a client.

Wireless communication network <NUM> includes sidelink DRX configuration component <NUM>, which may be used to coordinate sidelink DRX configurations between base stations <NUM> and UEs <NUM>. Wireless network <NUM> further includes sidelink DRX configuration component <NUM>, which may be used by UEs <NUM> to coordinate sidelink DRX configurations, such as between two UEs <NUM> (e.g., a sidelink connection <NUM>) and base stations <NUM>.

<FIG> depicts aspects of a base station (BS) <NUM> and a user equipment (UE) <NUM>.

Generally, BS <NUM> includes various processors (e.g., <NUM>, <NUM>, <NUM>, and <NUM>), antennas 234a-t, transceivers 232a-t, and other aspects, which are involved in transmission of data (e.g., source data <NUM>) and reception of data (e.g., data sink <NUM>). For example, BS <NUM> may send and receive data between itself and UE <NUM>. BS <NUM> includes controller / processor <NUM>, which sidelink DRX configuration component <NUM>. Sidelink DRX configuration component <NUM> may be configured to implement base station Sidelink DRX configuration <NUM> of <FIG>.

Generally, UE <NUM> includes various processors (e.g., <NUM>, <NUM>, <NUM>, and <NUM>), antennas 252a-r, transceivers 254a-r, and other aspects, involved in transmission of data (e.g., source data <NUM>) and reception of data (e.g., data sink <NUM>). UE <NUM> includes controller / processor <NUM>, which comprises Sidelink DRX configuration component <NUM>. Sidelink DRX configuration component <NUM> may be configured to implement user equipment distributed antenna panel component <NUM> of <FIG>.

<FIG> depict aspects of data structures for a wireless communication network, such as wireless communication network <NUM> of <FIG>. In particular, <FIG> is a diagram <NUM> illustrating an example of a first subframe within a <NUM> (e.g., <NUM> NR) frame structure, <FIG> is a diagram <NUM> illustrating an example of DL channels within a <NUM> subframe, <FIG> is a diagram <NUM> illustrating an example of a second subframe within a <NUM> frame structure, and <FIG> is a diagram <NUM> illustrating an example of UL channels within a <NUM> subframe.

Further discussions regarding <FIG>, <FIG>, and <FIG>-3D are provided later in this disclosure.

<FIG> depicts an examples of scenarios in which it may be beneficial to configure discontinuous reception (DRX) on a sidelink communication channel.

In particular, <FIG> depicts an example scenario <NUM> in which a base station <NUM> (such as base station <NUM> in <FIG> and <FIG>) is trying to send data to a target user equipment 404B, which is out of coverage of base station <NUM>. That is, in this example, no Uu interface exists between base station <NUM> and target UE 404B. Further in this example, the data being sent by base station <NUM> is a paging message; however, in other examples, base station <NUM> may be attempting to send other sort of data to target user equipment 404B.

In order to resolve the coverage problem, base station <NUM> can send a data relay request to relay user equipment 404A, which in this example includes a paging message intended for target user equipment 404B. In this case, base station <NUM> is able to send the paging relay request because it is in-coverage (e.g., via a Uu interface) to relay user equipment 404A.

Relay user equipment 404A then forwards the paging message to target user equipment 404B via an alternative communication channel. In this example, the alternative communication channel is a sidelink communication channel via a PC5 interface.

<FIG> depicts an alternative scenario <NUM> in which target user equipment 404B is still within coverage of base station <NUM>, but the connection is weak (e.g., due to a degraded channel state). For example, target user equipment 404B may be on the edge of base station <NUM>'s coverage area, or target user equipment 404B may be in conditions that negatively affect its connection to base station <NUM>, such as within a building where the signals from base station <NUM> are heavily attenuated. Alternatively, target user equipment 404B may be idle or inactive over the Uu interface with base station <NUM>.

Accordingly, the same relaying approach as described with respect to <FIG> may be used to resolve the situation of <FIG>. In this particular scenario, the message relayed by relay user equipment 404A may add transmit diversity by repetition, and thereby improve the reliability of the network.

<FIG> depicts various timelines to illustrate aspects of configuring sidelink DRX cycles to overlap between multiple user equipments.

In particular, timeline <NUM> shows a general network timeline in which repeating blocks of time are dedicated to control messaging and to data messaging in a wireless communication network, such as network <NUM> of <FIG>.

Timelines <NUM> and <NUM> depict various periods of an inactive state or an active state on a sidelink communication channel for a relay user equipment and a target user equipment, respectively. As depicted, different user equipments may have different DRX cycles (e.g., different times of active or inactive states during a common on DRX period). DRX cycles are generally periodic, and a UE may have multiple DRX cycles configured. In cases where a UE has no specific sidelink DRX configuration, it may monitor the entirety of each common on period.

In the depicted example, the network configures common on and common off periods in which all user equipments will either be inactive on the sidelink, or may be active. During common on periods, user equipment may monitor discovery/paging messages or data transmission. During common off periods, user equipments may stop monitoring any messages or data on the sidelink communication channel, but may have communication with the network on, for example, a Uu interface. The common sidelink DRX cycle configuration may be, in some cases, configured by the network in a system information broadcast (SIB).

Timeline <NUM> depicts a data transmission timeline in which different types of data may be transmitted from the relay user equipment to the target user equipment. In particular, during time <NUM> and time <NUM>, both the relay user equipment and target user equipment are active and therefore may communicate to each other via a sidelink communication channel (e.g., as described with respect to <FIG>).

It is clear from <FIG> that aligning sidelink DRX active times of the relay user equipment and the target user equipment beneficially facilitates the relay user equipment being able to relay data to the target user equipment, such as the paging message at time <NUM> and the data message (e.g., comprising data packets) at time <NUM>. This may allow for a network to get data to the target user equipment even when it is in an idle or inactive state with respect to its connection to the network (e.g., over a Uu interface). However, it is not always the case that the relay user equipment and target relay equipment will have aligned active time periods depending on their own DRX configurations. Accordingly, configuring the relay user equipment and the target user equipment to have overlapping active periods is beneficial.

Configuring user equipments to have coordinate sidelink DRX active periods may be done in various manners. For example, a network may coordinate the configuration of the relay and target user equipments' sidelink DRX cycles to ensure alignment during at least some portion of the common on periods. As another example, a relay user equipment may coordinate the configuration of the relay and target user equipments' sidelink DRX cycles to ensure alignment during at least some portion of the common on periods. As yet another example, a target user equipment may coordinate the configuration of the relay and target user equipments' sidelink DRX cycles to ensure alignment during at least some portion of the common on periods. In further examples, some combination of user equipments and the network (e.g., a hybrid approach) may be used to coordinate the configuration of the relay and target user equipments' sidelink DRX cycles to ensure alignment during at least some portion of the common on periods. Accordingly, various methods for aligning sidelink DRX active times (e.g., by way of sidelink DRX configurations) are discussed in more detail with respect to <FIG>.

<FIG> depicts an example data flow <NUM> between user equipments for coordinating sidelink DRX configurations between user equipments.

The flow <NUM> begins at step <NUM> where a user equipment <NUM> (e.g., user equipment <NUM> of <FIG> and <FIG>) sends base station (e.g., base station <NUM> of <FIG> and <FIG>) sidelink DRX preference information. The sidelink DRX preference information may include various aspects. In one example, the sidelink DRX preference information comprises a plurality of sidelink DRX configuration options. In some cases, the plurality of sidelink DRX configurations options are in an ordered list by preference of the user equipment to which they apply (e.g., the target and/or relay user equipments).

Notably, step <NUM> is optional, and in the absence of any preference information from the user equipments, base station <NUM> may generate the configuration for the user equipments.

Flow <NUM> then proceeds to step <NUM> where base station <NUM> sends a sidelink DRX configuration to relay user equipment and target user equipment <NUM>. In some cases, the sidelink DRX configuration may include multiple sidelink DRX configurations for multiple different user equipments.

In some cases, the sidelink DRX configuration at step <NUM> may be sent by using layer <NUM> signaling, such as an RRCReconfiguration message sent via radio resource control (RRC) signaling. In other cases, the sidelink DRX configuration may be sent using layer <NUM> or layer <NUM> signaling, such as via downlink control information (DCI) or a medium access control control element (MAC-CE), which is described in more detail with respect to <FIG>.

Target and relay user equipments <NUM> may their sidelink DRX cycle based on the sidelink DRX configuration received at step <NUM>.

Flow <NUM> then proceeds to step <NUM> with one or both of the target and relay user equipments <NUM> sending an indication that the sidelink DRX configuration is complete to base station <NUM>. The indication may take many forms. In one example, the indication includes an RRCReconfigurationComplete message.

The sidelink DRX configurations for the relay and target user equipments may ensure that both user equipments are active during at least a portion of the common on DRX periods, as discussed with respect to <FIG>, so that the relay and target user equipments may communicate directly on the sidelink communication channel.

Thus, <FIG> depicts an example of network coordination of sidelink DRX configurations for user equipments, such as the target and relay user equipments <NUM>. In this example, base station <NUM> may have a direct connection to both the target and relay user equipments (e.g., via a Uu interface) in order to facilitate the direct configuration of each user equipment. Note that while <FIG> discusses two user equipments (relay and target), in other cases, the network may configure sidelink DRX cycles for any number of user equipments in any number of target / relay relationships with each other.

<FIG> depicts another example data flow <NUM> between user equipments for coordinating sidelink DRX configurations between user equipments.

The flow <NUM> begins at step <NUM> where target user equipment 704A sends sidelink DRX preference information to relay user equipment 704B. Relay user equipment 704B may receive the sidelink DRX preference information by various manner. In the depicted example, relay user equipment 704B may receive the sidelink DRX preference information via a PC5 sidelink connection with target user equipment 704A.

Flow <NUM> then proceeds to step <NUM> where relay user equipment 704B sends to base station <NUM> (e.g., base station <NUM> of <FIG> and <FIG>) sidelink DRX preference information from one or both of target user equipment 704A and relay user equipment 704B. In some cases, relay user equipment 704B may send joint or combined sidelink DRX preference information (e.g., related to both target and relay user equipments), such as by merging its and target user equipment 704A's sidelink DRX preference information into one message. In other cases, relay user equipment 704B may send separate messages for each of target user equipment 704A and relay user equipment 704B's sidelink DRX preference information.

As with step <NUM>, step <NUM> is optional, and in the absence of any preference information from the user equipments, base station <NUM> may generate the configuration for the user equipments independently. In the depicted example, relay user equipment 704B and base station <NUM> are connected via a Uu interface, but other data connection types are possible.

Flow <NUM> then proceeds to step <NUM> where base station <NUM> sends a sidelink DRX configuration to relay user equipment 704B. In one example, the sidelink DRX configuration includes individual sidelink DRX configurations for each of relay user equipment 704B and target user equipment 704A (e.g., multiple user equipments).

As above, the sidelink DRX configuration at step <NUM> may be sent by using layer <NUM> signaling, such as an RRCReconfiguration message sent via RRC signaling. In other cases, the sidelink DRX configuration may be sent using layer <NUM> or layer <NUM> signaling, such as via DCI or MAC-CE, which is described in more detail with respect to <FIG>.

Relay user equipment 704B may configure its sidelink DRX cycle based on the sidelink DRX configuration received at step <NUM>.

Flow <NUM> then proceeds to step <NUM> with relay user equipment 704B sending a sidelink DRX configuration to target user equipment 704A. User equipment 704B may send the sidelink DRX configuration to target user equipment 704A by various means. In the depicted example, user equipment 704B sends the sidelink DRX configuration to target user equipment 704A by way of a PC5 sidelink connection. In one example, the sidelink DRX configuration may be sent in an RRCReconfigurationSidelink message, which is configured to forward the sidelink DRX configuration to target user equipment 704A.

Flow <NUM> then proceeds to step <NUM> with target user equipment 704A sending an indication to relay user equipment 704B that the sidelink reconfiguration is complete. In one example, the indication may include an RRCReconfigurationSidelinkComplete message, which tells relay user equipment 704B that target user equipment 704A has applied the sidelink DRX configuration.

Flow <NUM> then proceeds to step <NUM> with relay user equipment 704B sending an indication that the sidelink DRX configuration is complete to base station <NUM>. The indication that the sidelink DRX configuration is complete may take many forms. In one example, the indication includes an RRCReconfigurationComplete message, which indicates to base station <NUM> that the sidelink DRX configuration is applied successfully.

Thus, <FIG> depicts another example of a network-coordinated configuration of sidelink DRX cycles for user equipments, such as the target user equipment 704A and relay user equipment 704B in this example. However, unlike the example of <FIG>, in this example base station <NUM> coordinates the sidelink DRX configuration of multiple user equipments via relay user equipment 704B. Note that while <FIG> discusses two user equipments (relay and target), in other cases, the network may coordinate sidelink DRX configurations for any number of user equipments in any number of target / relay relationships with each other.

<FIG> depict another example data flow <NUM> between user equipments and a base station for coordinating sidelink DRX configurations between user equipments.

The flow <NUM> begins at step <NUM> where a target user equipment 804A sends sidelink DRX preference information to relay user equipment 804B. The sidelink DRX preference information may include various aspects. In one example, the sidelink DRX preference information comprises a plurality of sidelink DRX configuration options. In some cases, the plurality of sidelink DRX configurations options are in an ordered list by preference of the user equipment to which they apply (e.g., the target and/or relay user equipments).

In the absence of any preference information from target user equipment, relay user equipment 804B may generate the configuration for the user equipments.

Flow <NUM> then proceeds to step <NUM> where relay user equipment 804B sends a sidelink DRX configuration to target user equipment 804A.

In some cases, the sidelink DRX configuration at step <NUM> may be sent by using layer <NUM> signaling, such as an RRCReconfiguration message sent via radio resource control (RRC) signaling. In other cases, the sidelink DRX configuration may be sent using, for example, downlink control information (DCI) or a medium access control control element (MAC-CE), which is described in more detail with respect to <FIG>10C.

Target user equipment 804A configures its sidelink DRX cycle based on the sidelink DRX configuration received at step <NUM>.

Flow <NUM> then proceeds to step <NUM> with target user equipments 804A sending an indication that the sidelink DRX configuration is complete to relay user equipment 804B. The indication may take many forms. In one example, the indication includes an RRCReconfigurationSidelinkComplete message.

As above, the sidelink DRX configuration for the target user equipment 804A may ensure it and relay user equipment 804B are active during at least a portion of the common on DRX periods, as discussed with respect to <FIG>, so that target user equipment 804A and relay user equipment 804B may communicate directly on the sidelink communication channel.

Flow <NUM> then proceeds to step <NUM> with relay user equipment 804B sending sidelink DRX configuration information to base station <NUM>. The sidelink DRX configuration information may, for example, include the sidelink DRX configurations for both target user equipment 804A and relay user equipment 804B.

Note that no step is shown for relay user equipment 804B configuring its own sidelink DRX cycle in <FIG>. This is because relay user equipment 804B may determine the sidelink configuration (sent to target user equipment 804A in step <NUM>) based on its own existing configuration, so that no reconfiguration is necessary for relay user equipment 804B. However, in other cases, relay user equipment 804B may reconfigure its own DRX configuration based on, for example, the sidelink DRX preference information received from target user equipment 804A (if any is received) at step <NUM>.

For example, when the network changes (e.g., a new user equipment joins or leaves, or if the common DRX cycle changes), relay user equipment 804B may reconfigure target user equipment 804A's sidelink DRX configuration (e.g., its DRX cycle, as depicted in <FIG>) without any sidelink DRX preference information from target user equipment 804A.

However, target user equipment 804A may not accept relay user equipment 804B's sidelink DRX configuration due to conflicts. For example, target user equipment 804A may already be configured for other data traffic on the sidelink and may need another configuration from relay user equipment 804B. If target user equipment 804A does not accept relay user equipment 804B's specific sidelink DRX configuration, it sends sidelink DRX preference information back to relay user equipment 804B after receiving the initial sidelink configuration from relay user equipment 804B at step <NUM>. For example, target user equipment 804A may send a list of its sidelink DRX preference with different priorities to relay user equipment 804B, and thereafter relay user equipment 804B can adjust target user equipment 804A's sidelink DRX configuration based on the highest priority option in the list of preferences that is also suitable for relay user equipment 804B.

Thus, <FIG> depicts an example of user equipment coordination of sidelink DRX configurations for user equipments-specifically where the relay user equipment coordinates for itself and at least one target user equipment. Note that while <FIG> discusses two user equipments (relay and target), in other cases, a user equipment such as relay user equipment 804B may coordinate sidelink DRX configurations for any number of target user equipments in any number of target / relay relationships with each other.

<FIG> depicts another example data flow <NUM> between user equipments and a base station for coordinating sidelink DRX configurations between user equipments.

The flow <NUM> begins at step <NUM> where a relay user equipment 804A sends sidelink DRX preference information to target user equipment 804A. The sidelink DRX preference information may include various aspects. In one example, the sidelink DRX preference information comprises a plurality of sidelink DRX configuration options. In some cases, the plurality of sidelink DRX configurations options are in an ordered list by preference of the user equipment to which they apply (e.g., to relay user equipment 904B in this example).

As in examples above, step <NUM> is optional, and in the absence of any preference information from relay user equipment, target user equipment 804A may generate the configuration for the user equipments.

Flow <NUM> then proceeds to step <NUM> where relay target equipment 804A sends a sidelink DRX configuration to relay user equipment 804B.

Relay user equipment 904B may configure its sidelink DRX cycle based on the sidelink DRX configuration received at step <NUM>.

Flow <NUM> then proceeds to step <NUM> with relay user equipments 904A sending an indication that the sidelink DRX configuration is complete to target user equipment 804A. The indication may take many forms. In one example, the indication includes an RRCReconfigurationSidelinkComplete message.

As above, the sidelink DRX configuration for the relay user equipment 904B may ensure it and target user equipment 804A are active during at least a portion of the common on DRX periods, as discussed with respect to <FIG>, so that target user equipment 804A and relay user equipment 804B may communicate directly on the sidelink communication channel.

Flow <NUM> then proceeds to step <NUM> with relay user equipment 904B sending sidelink DRX configuration information to base station <NUM>. The sidelink DRX configuration information may, for example, include the sidelink DRX configurations for both target user equipment 904A and relay user equipment 904B.

Note that no step is shown for target user equipment 904A configuring its own sidelink DRX cycle in <FIG>. This is because target user equipment 904A may determine the sidelink configuration (sent to relay user equipment 904B in step <NUM>) based on its own existing configuration, so that no reconfiguration is necessary for target user equipment 904A. However, in other cases, target user equipment 904A may reconfigure its own DRX configuration based on, for example, the sidelink DRX preference information received from relay user equipment 904B (if any is received) at step <NUM>.

Relay user equipment 904B may not accept target user equipment 904A's sidelink DRX configuration due to conflicts. For example, relay user equipment 904A may already be configured for other data traffic on the sidelink (e.g., to another target user equipment) and may need another configuration from target user equipment 904A. If relay user equipment 904B does not accept target user equipment 904B's specific sidelink DRX configuration, it may instead send sidelink DRX preference information back to target user equipment 904A after receiving the initial sidelink configuration from target user equipment 904A at step <NUM>. For example, relay user equipment 904B may send a list of its sidelink DRX preference with different priorities to target user equipment 904A, and thereafter target user equipment 904A can adjust relay user equipment 904B's sidelink DRX configuration based on the highest priority option in the list of preferences that is also suitable for target user equipment 904A.

In one example, target user equipment 904A may select a user-equipment-specific sidelink DRX configuration (e.g., a sidelink DRX cycle) autonomously based on an identifier associated with the user equipment, such as a sidelink synchronization identity (SSID) or Layer-<NUM> ID. The network (e.g., base station <NUM>) may determine the number of user equipment-specific slots N, during a common on period, and then user equipments can derive their user equipment-specific on slots based on their own identifier. In one example, a user equipment, such as target user equipment 904A, can use the following expression: <MAT>.

Thus, a user equipment can use this equation to get its default sidelink configuration if no sidelink DRX configuration is received from the network.

Thus, <FIG> depicts another example of user equipment coordination of sidelink DRX configurations for user equipments-specifically where the target user equipment coordinates for itself and at least one relay user equipment. Note that while <FIG> discusses two user equipments (relay and target), in other cases, a user equipment such as target user equipment 904A may coordinate sidelink DRX configurations for any number of relay user equipments in any number of target / relay relationships with each other.

<FIG> depict various examples of coordinating sidelink DRX configurations where either the network (e.g., a base station) or a user equipment coordinates the sidelink DRX configurations. However, in other examples, the network and user equipments may both participate in the sidelink DRX configuration.

For example, the network may configure a relay user equipment as depicted and described with respect to <FIG> and <FIG>, but then the relay user equipment may configure the target user equipment as depicted and described with respect to <FIG>. Other examples are possible.

<FIG> depicts various manners for sending sidelink DRX configurations.

As described above, sidelink DRX configuration information may be sent via layer <NUM> signaling, such as RRC signaling, or layer <NUM> or layer <NUM> signaling, such as DCI and MAC-CE signaling. A benefit of layer <NUM> and layer <NUM> signaling is its lower latency, meaning that configurations may be performed more quickly.

In some examples, layer <NUM> and layer <NUM> signaling can be used to signal preconfigured sidelink DRX configurations. In other examples, layer <NUM> and layer <NUM> signaling can be used for more dynamic sidelink DRX alignment over the sidelink between relay and target user equipments.

<FIG> depicts an example of a system information block (SIB) type <NUM> for indicating preconfigured sidelink DRX configurations.

In some cases, a network may preconfigure a plurality of sidelink DRX configurations, and inform user equipments of the available options through system information block (SIB) signaling. In one example, the network (e.g., a base station) broadcasts the preconfigured DRX configuration options on a Uu interface using a SIB <NUM> message, as depicted in <FIG>, where the "commDRXConfig" field is used to define the preconfigured option.

In such a scenario, all user equipments connected to the network receive the same preconfigured options via the SIB <NUM> message, wherein the commDRXConfig is a set of possible sidelink DRX configurations, each of which is associated with an index. Each user equipment may then use one of the SL DRX configurations in the preconfigured set.

After broadcasting preconfigured DRX configurations using the SIB <NUM> block as in <FIG>, the network may then indicate to each user equipment (such as the target and relay user equipments in <FIG>) which option to select via a user equipment-specific message, such as the SIB19 block in <FIG>.

For example, the "DRXInfoList" field in <FIG> may include a list of numbers, where each number indicates one option from the set of SL DRX preconfigured options, and each number is associated with a user equipment identifier. Upon receiving the SIB <NUM> block, a user equipment finds its user equipment identifier in the list, and determines its preconfigured sidelink DRX configuration option.

<FIG> depicts another method in which a network can inform a user equipment of a sidelink DRX configuration.

In particular, <FIG> may represent a downlink control information (DCI) element or a medium access control control element (MAC-CE). In either case, the network may use a number (e.g., an octal number) to indicate one option from the set of sidelink DRX preconfigured options.

For example, where <FIG> represents DCI, each DCI element (e.g., C<NUM>. C<NUM>) is dedicated to one user equipment.

Similarly, where <FIG> represents a MAC-CE, each MAC-CE element (e.g., C<NUM>. C<NUM>) is dedicated to one user equipment.

<FIG> depicts an example method <NUM> for configuring discontinuous reception on a sidelink communication channel at a user equipment.

Method <NUM> begins at step <NUM> with receiving, at a first user equipment from a network, a sidelink discontinuous reception (DRX) configuration.

The sidelink DRX configuration may configure various aspects of a sidelink communication channel. For example, the sidelink DRX configuration may cause the first user equipment and the second user equipment to become active during a common portion of a common sidelink DRX cycle, such as depicted and described in <FIG>.

The first user equipment may receive the sidelink DRX configuration in various manners. For example, the first user equipment may receive the sidelink DRX configuration via layer <NUM> signaling, such as radio resource control (RRC) signaling from the network, or via layer <NUM> and layer <NUM> signaling, such as downlink control information (DCI) signaling from the network or medium access control control element (MAC-CE) signaling from the network. In some cases, the first user equipment receives the sidelink DRX configuration from the network via a Uu interface.

Method <NUM> then proceeds to step <NUM> with configuring a sidelink DRX cycle at the first user equipment based on the sidelink DRX configuration.

Method <NUM> then proceeds to step <NUM> with receiving, at the first user equipment from the network, data for a second user equipment.

The data for the second user equipment may be many sorts of data. For example, the data for the second user equipment may be a paging message. As another example, the data for the second user equipment may be a data packet or other type of message.

Method <NUM> then proceeds to step <NUM> with sending, from the first user equipment to the second user equipment on a sidelink in accordance with the sidelink DRX cycle, the data for the second user equipment.

The first user equipment may send the data to the second user equipment in various ways. In one example, the first user equipment sends the data to the second user equipment via a PC5 interface on the sidelink.

In some cases, method <NUM> may be performed along with additional steps not depicted in <FIG>.

In some cases, method <NUM> may include sending, from the first user equipment to the second user equipment, the sidelink DRX configuration.

In some cases, method <NUM> may include sending, from the first user equipment to the network, a sidelink DRX configuration preference for the first user equipment.

In some cases, method <NUM> may include: receiving, at the first user equipment from the second user equipment, a sidelink DRX configuration preference for the second user equipment; and sending, from the first user equipment to the network, the sidelink DRX configuration preference for the second user equipment.

In some cases, method <NUM> may include: sending, from the first user equipment to the second user equipment on the sidelink, a second sidelink DRX configuration, wherein, the second sidelink DRX configuration is configured to configure a DRX cycle at the second user equipment.

In some cases, method <NUM> may include: receiving, at the first user equipment from the second user equipment, a sidelink DRX configuration preference; and sending, from the first user equipment to the second user equipment on the sidelink, a third sidelink DRX configuration, wherein the third sidelink DRX configuration is based on the sidelink DRX configuration preference from the second user equipment.

In some cases, a user equipment (e.g., UE <NUM> in the wireless communication network <NUM> of <FIG>), or a portion thereof, may perform, or be configured, operable, or adapted to perform, operations of method <NUM>. In some cases, operations of method <NUM> may be implemented as software components (e.g., sidelink DRX configuration component <NUM> of <FIG>) that are executed and run on one or more processors (e.g., controller/processor <NUM> of <FIG>). Signals involved in the operations may be transmitted or received by the UE by one or more antennas (e.g., antennas <NUM> of <FIG>), or via a bus interface of one or more processors (e.g., the controller/processor <NUM>) obtaining and/or outputting the signals.

<FIG> depicts one example of a method consistent with the disclosure herein, but other examples are possible, which may include additional or alternative steps, or which omit certain steps. The various examples discussed with respect to <FIG> are illustrative and not meant to limit the scope of method <NUM>.

<FIG> depicts another example method <NUM> for configuring discontinuous reception on a sidelink communication channel at a user equipment.

Method <NUM> begins at step <NUM> with configuring a sidelink discontinuous reception (DRX) cycle at the first user equipment.

Method <NUM> then proceeds to step <NUM> with sending, from the first user equipment to a second user equipment, a sidelink DRX configuration.

The sidelink DRX configuration may configure various aspects of a sidelink communication channel. For example, the sidelink DRX configuration may cause the second user equipment and the first user equipment to become active during a common portion of a common sidelink DRX cycle, such as depicted and described in <FIG>.

Method <NUM> then proceeds to step <NUM> with receiving, at the first user equipment from the network, data for the second user equipment.

In some cases, method <NUM> includes receiving, at the first user equipment from the second user equipment, a message indicating that the second user equipment has configured its sidelink DRX cycle according to the sidelink DRX configuration.

In some cases, method <NUM> includes: receiving, at the first user equipment from the second user equipment, a sidelink DRX configuration preference for the second user equipment; and generating the sidelink DRX configuration based on the sidelink DRX configuration preference from the second user equipment.

In some cases, method <NUM> includes: receiving, at the first user equipment from the second user equipment, a sidelink DRX configuration preference for the second user equipment; and sending, from the first user equipment to the second user equipment, a second sidelink DRX configuration based on the sidelink DRX configuration preference from the second user equipment.

The sidelink DRX configuration preference may include various information. In one example, the sidelink DRX configuration preference comprises a plurality of sidelink DRX configuration options in an ordered list by preference of the second user equipment. In another example, the sidelink DRX configuration preference may include a single preferred DRX configuration option of the second user equipment. Other examples are possible.

In some cases, method <NUM> includes: sending, from the first user equipment to the network, sidelink DRX configuration information comprising the sidelink DRX configuration for the first user equipment and a sidelink DRX configuration for the second user equipment.

Method <NUM> begins at step <NUM> with receiving, at a first user equipment from a second user equipment, a sidelink discontinuous reception (DRX) configuration.

Method <NUM> then proceeds to step <NUM> with configuring a DRX cycle at the first user equipment based on the sidelink DRX configuration received from the second user equipment.

In some cases, method <NUM> includes sending, from the first user equipment to the second user equipment, a message indicating that the first user equipment has configured its sidelink DRX cycle according to the sidelink DRX configuration.

In some cases, method <NUM> includes sending, from the first user equipment to the second user equipment, a sidelink DRX configuration preference for the first user equipment.

The sidelink DRX configuration preference may include various information. In one example, the sidelink DRX configuration preference comprises a plurality of sidelink DRX configuration options in an ordered list by preference of the first user equipment. In another example, the sidelink DRX configuration preference may include a single preferred DRX configuration option of the first user equipment. Other examples are possible.

In some cases, the sidelink DRX configuration received at the first user equipment from the second user equipment is based on the sidelink DRX configuration preference from the first user equipment.

<FIG> depicts another example method <NUM> for configuring discontinuous reception on a sidelink communication channel at a network.

Method <NUM> begins at step <NUM> with sending, from a network to a first user equipment, a sidelink discontinuous reception (DRX) configuration.

The network may send the sidelink DRX configuration in various ways. In one example, the network sends the sidelink DRX configuration via a Uu interface.

The sidelink DRX configuration may include various information. In one example, the sidelink DRX configuration includes a sidelink DRX configuration for the first user equipment and a sidelink DRX configuration for a second user equipment.

Method <NUM> then proceeds to step <NUM> with receiving, at the network from the first user equipment, an indication that the sidelink DRX reconfiguration is complete.

The network may receive the indication that the sidelink DRX reconfiguration is complete in various ways. In one example, the network receives the indication that the sidelink DRX reconfiguration is complete via a Uu interface.

The indication that the sidelink DRX reconfiguration is complete may include various information. In one example, the indication that the sidelink DRX reconfiguration is complete includes an indication that the sidelink DRX configuration is complete for one or more of the first user equipment and a second user equipment. In some cases, the indication that the sidelink DRX reconfiguration is complete comprises a radio resource control (RRC) reconfiguration complete message.

In some cases, method <NUM> includes receiving a sidelink DRX configuration preference from the first user equipment.

The sidelink DRX configuration preference may include various information. In one example, the sidelink DRX configuration preference comprises a plurality of sidelink DRX configuration options in an ordered list by preference of one or more of the first user equipment and/or the second user equipment. In another example, the sidelink DRX configuration preference may include a single preferred DRX configuration option of one or more of the first user equipment and the second user equipment. Other examples are possible.

In some cases, a base station (e.g., such as base station <NUM> in the wireless communication network <NUM> of <FIG>), or a portion thereof, may perform, or be configured, operable, or adapted to perform, operations of method <NUM>. In some cases, operations of method <NUM> may be implemented as software components (e.g., sidelink DRX configuration component <NUM> of <FIG>) that are executed and run on one or more processors (e.g., controller/processor <NUM> of <FIG>). Signals involved in the operations may be transmitted or received by the base station by one or more antennas (e.g., antennas <NUM> of <FIG>), or via a bus interface of one or more processors (e.g., the controller/processor <NUM>) obtaining and/or outputting the signals.

<FIG> depicts an example method <NUM> for receiving a sidelink discontinuous reception (DRX) configuration at a network.

Method <NUM> begins at step <NUM> with receiving at a network from a user equipment, sidelink discontinuous reception (DRX) configuration information.

The sidelink DRX configuration information may include various information. In one example, the sidelink DRX configuration information includes a sidelink DRX configuration for a first user equipment and a sidelink DRX configuration for a second user equipment.

The sidelink DRX configuration for the first user equipment and/or second user equipment may configure various aspects of a sidelink communication channel. For example, the sidelink DRX configuration may cause the first user equipment and the second user equipment to become active during a common portion of a common sidelink DRX cycle, such as depicted and described in <FIG>.

The network may receive the sidelink DRX configuration information in various manners. In one example, then network receives the sidelink DRX configuration information via a Uu interface.

<FIG> depicts an example communications device <NUM> that includes various components operable, configured, or adapted to perform operations for the techniques disclosed herein, such as the operations depicted and described with respect to <FIG>. In some examples, communication device <NUM> may be a UE <NUM> as described, for example with respect to <FIG> and <FIG>.

Communications device <NUM> includes a processing system <NUM> coupled to a transceiver <NUM> (e.g., a transmitter and/or a receiver). Transceiver <NUM> is configured to transmit (or send) and receive signals for the communications device <NUM> via an antenna <NUM>, such as the various signals as described herein. Processing system <NUM> may be configured to perform processing functions for communications device <NUM>, including processing signals received and/or to be transmitted by communications device <NUM>.

Processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium/memory <NUM> via a bus <NUM>. In certain aspects, computer-readable medium/memory <NUM> is configured to store instructions (e.g., computer-executable code) that when executed by processor <NUM>, cause processor <NUM> to perform the operations illustrated in <FIG>, or other operations for performing the various techniques discussed herein for sidelink DRX configuration.

In the depicted example, computer-readable medium/memory <NUM> stores code <NUM> for sending and receiving sidelink DRX preference information, code <NUM> for sending and receiving sidelink DRX configurations, code <NUM> for sending and receiving DRX configuration confirmations, code <NUM> for configuring sidelink DRX, and code <NUM> for sending and receiving data.

In the depicted example, processor <NUM> has circuitry configured to implement the code stored in the computer-readable medium/memory <NUM>, including circuitry <NUM> for sending and receiving sidelink DRX preference information, circuitry <NUM> for sending and receiving sidelink DRX configurations, circuitry <NUM> for sending and receiving DRX configuration confirmations, circuitry <NUM> for configuring sidelink DRX, and circuitry <NUM> for sending and receiving data.

Various components of communications device <NUM> may provide means for performing the methods described herein, including with respect to <FIG>.

In some examples, means for transmitting or sending (or means for outputting for transmission) may include the transceivers <NUM> and/or antenna(s) <NUM> of the UE <NUM> illustrated in <FIG> and/or transceiver <NUM> and antenna <NUM> of the communication device <NUM> in <FIG>.

In some examples, means for receiving (or means for obtaining) may include the transceivers <NUM> and/or antenna(s) <NUM> of the UE <NUM> illustrated in <FIG> and/or transceiver <NUM> and antenna <NUM> of the communication device <NUM> in <FIG>.

In some examples, means for configuring sidelink DRX, means for determining sidelink DRX preferences, means for generating configuration confirmations, and means for processing received data may include a processing system, which may include one or more processors, such as the receive processor <NUM>, the transmit processor <NUM>, the TX MIMO processor <NUM>, and/or the controller/processor <NUM>, including sidelink DRX configuration component <NUM>, of the UE <NUM> illustrated in <FIG> and/or the processing system <NUM> of the communication device <NUM> in <FIG>.

Notably, <FIG> is just use example, and many other examples and configurations of communication device <NUM> are possible.

<FIG> depicts aspects of another example communications device <NUM> that includes various components operable, configured, or adapted to perform operations for the techniques disclosed herein, such as the operations depicted and described with respect to <FIG> and <NUM>-<NUM>. In some examples, communication device <NUM> may be a base station <NUM> as described, for example with respect to <FIG> and <FIG>.

Processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium/memory <NUM> via a bus <NUM>. In certain aspects, computer-readable medium/memory <NUM> is configured to store instructions (e.g., computer-executable code) that when executed by processor <NUM>, cause processor <NUM> to perform the operations illustrated in <FIG> and <NUM>-<NUM>, or other operations for performing the various techniques discussed herein for sidelink DRX configuration.

In the depicted example, computer-readable medium/memory <NUM> stores code <NUM> for sending and receiving sidelink DRX preference information, code <NUM> for sending and receiving sidelink DRX configurations, code <NUM> for receiving DRX configuration confirmations, and code <NUM> for sending and receiving data.

In the depicted example, processor <NUM> has circuitry configured to implement the code stored in the computer-readable medium/memory <NUM>, including: circuitry <NUM> for receiving sidelink DRX preference information, circuitry <NUM> for sending and receiving sidelink DRX configurations, circuitry <NUM> for receiving DRX configuration confirmations, and circuitry <NUM> for sending and receiving data.

Various components of communications device <NUM> may provide means for performing the methods described herein, including with respect to <FIG> and <NUM>-<NUM>.

In some examples, means for transmitting or sending (or means for outputting for transmission) may include the transceivers <NUM> and/or antenna(s) <NUM> of the base station <NUM> illustrated in <FIG> and/or transceiver <NUM> and antenna <NUM> of the communication device <NUM> in <FIG>.

In some examples, means for receiving (or means for obtaining) may include the transceivers <NUM> and/or antenna(s) <NUM> of the base station <NUM> illustrated in <FIG> and/or transceiver <NUM> and antenna <NUM> of the communication device <NUM> in <FIG>.

In some examples, means for determining sidelink DRX preferences, means for determining sidelink DRX configurations, and means for processing received data may include a processing system, which may include one or more processors, such as the receive processor <NUM>, the transmit processor <NUM>, the TX MIMO processor <NUM>, and/or the controller/processor <NUM>, including sidelink DRX configuration <NUM>, of the base station <NUM> illustrated in <FIG> and/or the processing system <NUM> of the communication device <NUM> in <FIG>.

The techniques and methods described herein may be used for various wireless communications networks (or wireless wide area network (WWAN)) and radio access technologies (RATs). While aspects may be described herein using terminology commonly associated with <NUM>, <NUM>, and/or <NUM> (e.g., <NUM> new radio (NR)) wireless technologies, aspects of the present disclosure may likewise be applicable to other communication systems and standards not explicitly mentioned herein.

<NUM> wireless communication networks may support various advanced wireless communication services, such as enhanced mobile broadband (eMBB), millimeter wave (mmWave), machine type communications (MTC), and/or mission critical targeting ultra-reliable, low-latency communications (URLLC). These services, and others, may include latency and reliability requirements.

Returning to <FIG>, various aspects of the present disclosure may be performed within the example wireless communication network <NUM>.

A macro cell may generally cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having an association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG) and UEs for users in the home).

Base stations <NUM> configured for <NUM> LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC <NUM> through first backhaul links <NUM> (e.g., an S1 interface). Base stations <NUM> configured for <NUM> (e.g., <NUM> NR or Next Generation RAN (NG-RAN)) may interface with core network <NUM> through second backhaul links <NUM>. Base stations <NUM> may communicate directly or indirectly (e.g., through the EPC <NUM> or core network <NUM>) with each other over third backhaul links <NUM> (e.g., X2 interface). Third backhaul links <NUM> may generally be wired or wireless.

Small cell <NUM>' may operate in a licensed and/or an unlicensed frequency spectrum. Small cell <NUM>', employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.

Some base stations, such as gNB <NUM> may operate in a traditional sub-<NUM> spectrum, in millimeter wave (mmWave) frequencies, and/or near mmWave frequencies in communication with the UE <NUM>. When the gNB <NUM> operates in mmWave or near mmWave frequencies, the gNB <NUM> may be referred to as an mmWave base station.

The communication links <NUM> between base stations <NUM> and, for example, UEs <NUM>, may be through one or more carriers. For example, base stations <NUM> and UEs <NUM> may use spectrum up to Y MHz (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and other MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction.

Wireless communications system <NUM> further includes a Wi-Fi access point (AP) <NUM> in communication with Wi-Fi stations (STAs) <NUM> via communication links <NUM> in, for example, a <NUM> and/or <NUM> unlicensed frequency spectrum.

D2D communication may be through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE <NUM> standard, <NUM> (e.g., LTE), or <NUM> (e.g., NR), to name a few options.

EPC <NUM> may include a Mobility Management Entity (MME) <NUM>, other MMEs <NUM>, a Serving Gateway <NUM>, a Multimedia Broadcast Multicast Service (MBMS) Gateway <NUM>, a Broadcast Multicast Service Center (BM-SC) <NUM>, and a Packet Data Network (PDN) Gateway <NUM>. MME <NUM> may be in communication with a Home Subscriber Server (HSS) <NUM>. MME <NUM> is the control node that processes the signaling between the UEs <NUM> and the EPC <NUM>. Generally, MME <NUM> provides bearer and connection management.

Generally, user Internet protocol (IP) packets are transferred through Serving Gateway <NUM>, which itself is connected to PDN Gateway <NUM>. PDN Gateway <NUM> provides UE IP address allocation as well as other functions. PDN Gateway <NUM> and the BM-SC <NUM> are connected to the IP Services <NUM>, which may include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services.

BM-SC <NUM> may provide functions for MBMS user service provisioning and delivery. BM-SC <NUM> may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. MBMS Gateway <NUM> may be used to distribute MBMS traffic to the base stations <NUM> belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

Core network <NUM> may include an Access and Mobility Management Function (AMF) <NUM>, other AMFs <NUM>, a Session Management Function (SMF) <NUM>, and a User Plane Function (UPF) <NUM>. AMF <NUM> may be in communication with a Unified Data Management (UDM) <NUM>.

AMF <NUM> is generally the control node that processes the signaling between UEs <NUM> and core network <NUM>. Generally, AMF <NUM> provides QoS flow and session management.

All user Internet protocol (IP) packets are transferred through UPF <NUM>, which is connected to the IP Services <NUM>, and which provides UE IP address allocation as well as other functions for core network <NUM>. IP Services <NUM> may include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services.

Returning to <FIG>, various example components of BS <NUM> and UE <NUM> (e.g., the wireless communication network <NUM> of <FIG>) are depicted, which may be used to implement aspects of the present disclosure.

At BS <NUM>, a transmit processor <NUM> may receive data from a data source <NUM> and control information from a controller/processor <NUM>. The control information may be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid ARQ indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC PDCCH), and others. The data may be for the physical downlink shared channel (PDSCH), in some examples.

A medium access control (MAC)-control element (MAC-CE) is a MAC layer communication structure that may be used for control command exchange between wireless nodes. The MAC-CE may be carried in a shared channel such as a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), or a physical sidelink shared channel (PSSCH).

Processor <NUM> may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. Transmit processor <NUM> may also generate reference symbols, such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS).

Transmit (TX) multiple-input multiple-output (MIMO) processor <NUM> may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) in transceivers 232a-232t. Each modulator in transceivers 232a-232t may process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Downlink signals from the modulators in transceivers 232a-232t may be transmitted via the antennas 234a-234t, respectively.

At UE <NUM>, antennas 252a-252r may receive the downlink signals from the BS <NUM> and may provide received signals to the demodulators (DEMODs) in transceivers 254a-254r, respectively. Each demodulator in transceivers 254a-254r may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM) to obtain received symbols.

MIMO detector <NUM> may obtain received symbols from all the demodulators in transceivers 254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. Receive processor <NUM> may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE <NUM> to a data sink <NUM>, and provide decoded control information to a controller/processor <NUM>.

On the uplink, at UE <NUM>, transmit processor <NUM> may receive and process data (e.g., for the physical uplink shared channel (PUSCH)) from a data source <NUM> and control information (e.g., for the physical uplink control channel (PUCCH) from the controller/processor <NUM>. Transmit processor <NUM> may also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS)). The symbols from the transmit processor <NUM> may be precoded by a TX MIMO processor <NUM> if applicable, further processed by the modulators in transceivers 254a-254r (e.g., for SC-FDM), and transmitted to BS <NUM>.

At BS <NUM>, the uplink signals from UE <NUM> may be received by antennas 234at, processed by the demodulators in transceivers 232a-232t, detected by a MIMO detector <NUM> if applicable, and further processed by a receive processor <NUM> to obtain decoded data and control information sent by UE <NUM>. Receive processor <NUM> may provide the decoded data to a data sink <NUM> and the decoded control information to the controller/processor <NUM>.

Memories <NUM> and <NUM> may store data and program codes for BS <NUM> and UE <NUM>, respectively.

Scheduler <NUM> may schedule UEs for data transmission on the downlink and/or uplink.

Antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of UE <NUM> and/or antennas <NUM>, processors <NUM>, <NUM>, <NUM>, and/or controller/processor <NUM> of BS <NUM> may be used to perform the various techniques and methods described herein.

For example, as shown in <FIG>, the controller/processor <NUM> of the BS <NUM> has a sidelink DRX configuration component <NUM> that may be configured to coordinate sidelink DRX configurations, according to aspects described herein. As shown in <FIG>, the controller/processor <NUM> of the UE <NUM> has a sidelink DRX configuration component <NUM> that may be configured to coordinate sidelink DRX configurations, according to aspects described herein. Although shown at the controller/processor, other components of UE <NUM> and BS <NUM> may be used to perform the operations described herein.

<NUM> may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. <NUM> may also support half-duplex operation using time division duplexing (TDD). OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth into multiple orthogonal subcarriers, which are also commonly referred to as tones and bins. Each subcarrier may be modulated with data. The minimum resource allocation, called a resource block (RB), may be <NUM> consecutive subcarriers in some examples. NR may support a base subcarrier spacing (SCS) of <NUM> and other SCS may be defined with respect to the base SCS (e.g., <NUM>, <NUM>, <NUM>, <NUM>, and others).

As above, <FIG> depict various example aspects of data structures for a wireless communication network, such as wireless communication network <NUM> of <FIG>.

In various aspects, the <NUM> frame structure may be frequency division duplex (FDD), in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for either DL or UL. <NUM> frame structures may also be time division duplex (TDD), in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by <FIG>, the <NUM> frame structure is assumed to be TDD, with subframe <NUM> being configured with slot format <NUM> (with mostly DL), where D is DL, U is UL, and X is flexible for use between DL/UL, and subframe <NUM> being configured with slot format <NUM> (with mostly UL). Note that the description below applies also to a <NUM> frame structure that is TDD.

In some examples, each slot may include <NUM> or <NUM> symbols, depending on the slot configuration.

For example, for slot configuration <NUM>, each slot may include <NUM> symbols, and for slot configuration <NUM>, each slot may include <NUM> symbols.

For slot configuration <NUM>, different numerologies (µ) <NUM> to <NUM> allow for <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> slots, respectively, per subframe. Accordingly, for slot configuration <NUM> and numerology µ, there are <NUM> symbols/slot and 2µ slots/subframe. The subcarrier spacing may be equal to <NUM>µ × <NUM>, where µ is the numerology <NUM> to <NUM>. As such, the numerology µ = <NUM> has a subcarrier spacing of <NUM> and the numerology µ = <NUM> has a subcarrier spacing of <NUM>. <FIG> provide an example of slot configuration <NUM> with <NUM> symbols per slot and numerology µ = <NUM> with <NUM> slots per subframe. The slot duration is <NUM>, the subcarrier spacing is <NUM>, and the symbol duration is approximately <NUM>.

As illustrated in <FIG>, some of the REs carry reference (pilot) signals (RS) for a UE (e.g., UE <NUM> of <FIG> and <FIG>).

The PSS is used by a UE (e.g., <NUM> of <FIG> and <FIG>) to determine subframe/symbol timing and a physical layer identity.

The preceding description provides examples of sidelink DRX configuration in communication systems. Changes may be made in the function and arrangement of elements discussed without departing from the disclosure. In addition, the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein.

The techniques described herein may be used for various wireless communication technologies, such as <NUM> (e.g., <NUM> NR), 3GPP Long Term Evolution (LTE), LTE-Advanced (LTE-A), 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), time division synchronous code division multiple access (TD-SCDMA), and other networks. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, and others. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. An OFDMA network may implement a radio technology such as NR (e.g. <NUM> RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE <NUM> (Wi-Fi), IEEE <NUM> (WiMAX), IEEE <NUM>, Flash-OFDMA, and others. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS).

The method steps and/or actions may be interchanged with one another. In other words, unless a specific order of steps or actions is specified, the order and/or use of specific steps and/or actions may be modified.

Reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more.

The means may include various hardware and/or software component(s) and/or module(s), including, but not limited to a circuit, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or a processor (e.g., a general purpose or specifically programmed processor).

The various illustrative logical blocks, modules and circuits described in connection with the present disclosure may be implemented or performed with a general purpose processor, a DSP, an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.

In the case of a user equipment (see <FIG>), a user interface (e.g., keypad, display, mouse, joystick, touchscreen, biometric sensor, proximity sensor, light emitting element, and others) may also be connected to the bus.

Combinations of the above can also be considered as examples of computer-readable media.

Claim 1:
A method of wireless communications, comprising:
receiving (<NUM>), at a first user equipment from a network, a sidelink discontinuous reception, DRX, configuration;
configuring a sidelink DRX cycle at the first user equipment based on the sidelink DRX configuration;
receiving (<NUM>), at the first user equipment from the network, data for a second user equipment;
sending (<NUM>), from the first user equipment to the second user equipment on a sidelink in accordance with the sidelink DRX cycle, the data for the second user equipment;
sending, from the first user equipment to the second user equipment on the sidelink, the first sidelink DRX configuration, wherein the first sidelink DRX configuration is configured to configure a DRX cycle at the second user equipment;
receiving (<NUM>), at the first user equipment from the second user equipment, a sidelink DRX configuration preference; and
sending (<NUM>), from the first user equipment to the second user equipment on the sidelink, a second sidelink DRX configuration based on the sidelink DRX configuration preference from the second user equipment.