WO2022155308A1

WO2022155308A1 - New radio (nr) sidelink communication

Info

Publication number: WO2022155308A1
Application number: PCT/US2022/012279
Authority: WO
Inventors: Sergey PANTELEEV; Alexey Khoryaev; Mikhail Shilov; Kilian Roth; Artyom LOMAYEV
Original assignee: Intel Corporation
Priority date: 2021-01-15
Filing date: 2022-01-13
Publication date: 2022-07-21

Abstract

Various embodiments herein provide techniques related to sidelink communication in fifth generation (5G) (or "new radio (NR)) cellular networks. Some embodiments may relate to techniques for low-power sidelink communication in 5G networks. Some embodiments may relate to techniques for sidelink discontinuous reception (DRX). Other embodiments may be described and/or claimed.

Description

NEW RADIO (NR) SIDELINK COMMUNICATION

CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority to U.S. Provisional Patent Application No. 63/138,200, which was filed January 15, 2021; and U.S. Provisional Patent Application No. 63/138,096, which was filed January 15, 2021.

FIELD

Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to new radio (NR) sidelink communication.

BACKGROUND

Various embodiments generally may relate to the field of wireless communications.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings.

Figure 1 illustrates an example of channel busy ratio (CBR) hysteresis, in accordance with various embodiments.

Figure 2 illustrates an example technique related to low power NR sidelink communication, in accordance with various embodiments.

Figure 3 illustrates an example technique related to NR sidelink discontinuous reception (DRX), in accordance with various embodiments.

Figure 4 schematically illustrates a wireless network in accordance with various embodiments.

Figure 5 schematically illustrates components of a wireless network in accordance with various embodiments.

Figure 6 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

BACKGROUND

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A/B” mean (A), (B), or (A and B).

Low Power NR Sidelink Communication

Energy efficiency and low power consumption may be considered to be main attributes of modern wireless communication system design. Various power saving mechanisms / features may be integrated directly into radio-interface protocols. Embodiments described herein include new mechanisms that may be applied to the NR sidelink air-interface.

The NR vehicle-to-anything (V2X) sidelink communication protocol is generally used for inter-vehicle communication and provides reliable and low latency communication capabilities for mission critical services. However, the designed legacy release-16 (Rel. 16) NR V2X airinterface may not be optimized in terms of power consumption, and thus new mechanisms to provide substantial power saving may be desirable. Specifically, for legacy Rel. 16 NR sidelink, it may be assumed that the receiver is always on and monitoring all system resources for control channel defined in the system configuration. This always-on status may result in a substantial amount of processing being used at the receiver side to support sidelink communication.

Embodiments and disclosures herein may relate to power-saving mechanisms, and may also include techniques to address problems in handling certain power saving aspects of the physical layer. The implementation of power saving in accordance with embodiments herein may have an impact on the physical layer implementation of the release-17 (Rel. 17) NR V2X design. Additionally, reduced power consumption may be allow battery-constrained devices to more effectively participate in NR sidelink communication.

Resource selection type may differ for transmissions of the same transport block (TB) or initial periodic transmission

After a user equipment (UE) receives a packet for sidelink transmission it may do immediate sensing once resource selection is triggered.

- Depending on latency and UE power consumption considerations it may: o Randomly select resource(s) for initial transmission of a TB and all subsequent retransmissions including reserved resources o Randomly select resource(s) for initial transmission of a TB and initial resource reservations, while utilizing aggregated sensing data for subsequent retransmissions o Select resource(s) for initial transmission of a TB, initial reservations indicated in sidelink control information (SCI) transmission and subsequent re-transmissions based on available sensing data o Select resource(s) for the first transmission and retransmissions of a TB within semi-persistent process (periodic traffic) based on partial sensing or random resource selection. Afterwards, the UE is expected to perform partial sensing and thus can reselect resources based on partial sensing knowledge of other transmissions for subsequent transmissions within semi-persistent process (of the same periodic traffic).

In general, all of the above options may be considered to be valid options. Selection of a specific option may depend on conditions such as latency budget, CBR, activated power saving mode/features and resource configuration, etc.

Partial sensing intervals based on known information

To enable the sidelink communication between different UEs, UEs may be informed when other UEs with whom they want to communicate are in active state (i.e. if another UE is able to monitor for and/or receive a physical sidelink control channel (PSCCH)). Given that an allocation of a partial sensing window may depend packet the arrival time at the UE transmitter as well as on whether semi-persistent or dynamic resource reservations are applied by the UE for sidelink communication (which may not be known to other UEs), the system wide mechanisms to acquire instances of time intervals with On-Duration may need to be enabled.

The alignment of system wide partial sensing starting time can be pre-configured by either a common time-offset with respect to system frame number (SFN)/direct frame number (DFN) slot 0 so that all UEs are receiving at the same time or in a UE specific manner when the start time of On-Duration (e.g., the time-offset with respect to SFN/DFN slot 0) is defined as a function of a destination UE identifier (ID) (e.g., a layer 1 (LI) or layer 2 (L2) ID) or some higher layer ID (e.g. an identifier related to a specific service/application etc.).

As an alternative to system-wide configuration of the partial sensing time, there may be a pre-configuration of a sensing time offset associated with a specific UE group or UE pair. This alignment may be different depending on the sidelink cast type (unicast, groupcast and broadcast) as well as what information is available.

• In case of unicast or groupcast, it may be assumed that, after discovery, the initial connect! on/associati on among all members is established using broadcast communication on system wide partial sensing intervals. Afterwards, UEs may negotiate parameters of the minimal partial sensing time intervals where all group members are active. This may define the minimal “on” duration as well as position. A redefinition of these regions may also be done during the communication. The related sidelink RRC or medium access control (MAC) control element (CE) signaling may need to be specified to configure the partial sensing parameters that may be used to derive an actual reception time interval.

Within network coverage, the partial sensing parameters may be configured by the network, or default pre-configured values can be used. For out-of-network-coverage scenarios, the system wide partial sensing parameters may be pre-configured. The configuration of system wide partial sensing parameters are mainly needed in order to support autonomous initiation of sidelink association / connection among UEs.

Congestion control/Open Loop Power Control (OLPC) based in periodic measurements and other measurement enhancements

Periodic CBR measurements windows may be pre-configured to the UE with a certain period and duration that may be dependent on the particular power saving or sensing state of the UE.

UE may also perform measurements when it wakes up for transmission or partial sensing, and switch the power saving mode based on CBR. For example, in some embodiments: o UE may measure CBR at each configured measurement window and, for example, average the N latest measured CBR values

■ CBR < CBRRANDOM THR - State with random resource selection (No sensing)

• The UE may use random resource selection for power saving if the measured CBR is below pre-configured CBRRANDOM THR value

■ CBRRANDOM THR < CBR < CBRPARTIAL SENSING THR - State with partial sensing for resource selection (Partial sensing)

• The UE may use partial sensing for power saving if the measured CBR is below pre-configured CBRRANDOM THR value

■ CBRPARTIAL _SENSING_THR < CBR - State with full sensing for resource selection (Full sensing) The UE may be expected to perform a full sensing procedure for resource selection

If the length of the CBR measurements would decrease, it may be the case that the transmitter switches frequently between different intervals. To mitigate this effect, a hysteresis effect can be introduced. This hysteresis effect may, for example, be implemented in a higher threshold to transition to another state. An Example 100 of this is shown in Figure 1. In this case there are 3 possible CBR ranges, 110, 115, and 120. We assume that due to the measurements in the last time interval the system is currently in the range 115. For the current CBR measurement to transition to another state, the resulting measurement may be required to be outside the interval given by the CBR range 115. It will be noted that, in order to accommodate a small amount of noise in the measurement, this range 115 may be larger than the CBR range that is associated with the current system state, described above.

Congestion control/OLPC for random resource selection

In Rel. 16, NR congestion control may be based on CBR measurements defined in a 100 millisecond (ms) window preceding the actual sidelink transmission. For UEs running partial sensing in case of semi-persistent transmission, it may be possible to perform CBR measurements across multiple partial sensing windows corresponding to different periodicities for transmission (which may be configured in the system) as well as measurements conducted in a partial sensing window right before or during a resource reselection procedure related to the actual sidelink transmission. For dynamic resource reservations, multiple partial sensing window(s) may not be available right before the sidelink transmission of a transport block (TB), and thus previous CBR measurements and measurements performed within the ongoing partial sensing time interval may potentially be used and thus aggregated from time intervals corresponding to previous transmissions of a TB.

In some embodiments, the CBR measurement interval sl-TimeWindowSizeCBR may only take one of the two values. These value may be 100 ms or 100 slots, and therefore it might be necessary to introduce additional values for CBR time windows applicable for UEs operating in partial sensing mode. Depending on the values of the partial sensing window, CBR measurements may be performed across multiple partial sensing intervals.

Another embodiment may introduce periodic CBR measurement instances. These instances may either take the form of configured periods with a CBR measurement window at a configured time, or through a requirement to perform a CBR measurement with a configured window size at least once during a predefined time period. An alternative approach for congestion control that may be suitable for random resource selection is to put constraints on the maximum amount of resources or CR value in a predefined time interval.

Congestion control/OLPC based on other metrics than CBR

In Rel. 16 NR SL congestion control and OLPC may be based on CBR measurements. For some cases in future releases the available measurement period may be less than the one assumed for the design of the CBR measurements in Rel. 16 NR sidelink. For a short time period, other parameters may be more suitable to base the power control on. This parameters may include, for example, the number of physical sidelink control channel (PSCCH), physical sidelink shared channel (PSSCH), or physical sidelink feedback channel (PSFCHO) resources that are occupied. Alternatively, the parameters may include the number of PSCCH resources where the demodulation reference signal (DMRS) reference signal received power (RSRP) exceeds a certain value.

Another option may include guessing the congestion control and power control of other devices currently transmitting. For example, from the used modulation and coding scheme (MCS), the current CBR state may be inferred (depend on the configuration). This may enable the devices to mimic the congestion control state of the transmission it receives. This technique may be appropriate for situations where the device does know that the other device transmitting is using full sensing or the maximum measurement accuracy.

It is also possible that devices that performed the CBR measurements as required for Rel. 16 NR sidelink indicate their CBR index inside the sidelink control information (SCI). To also enable Rel. 16 devices, this information may be placed inside the SCI in a way to not prevent devices only implementing Rel. 16 NR V2X from receiving the PSCCH and the related PSSCH. For partial sensing or random resource selection, the devices may then select this CBR index signaling from the UE that is physically closest. The related selection criteria may be the location, the PSCCH RSRP, or the PSSCH RSRP.

In case there is not enough time to perform accurate measurements, a default CBR index may be configured separately for partial sensing and random resource selection. This default value may also be different dependent on priority or cast type.

The above solutions may be primarily applicable if the required CBR measurements cannot be performed. This means that, after the hybrid automatic repeat request (HARQ) feedback is received, or other packets are to be transmitted and enough data is present to accurately estimate the CBR, this value may be taken for further retransmissions or following transmissions of other TBs. It may also be noted that the measured CBR be be required to be considered valid by the device for a (pre)-configured amount of time. This (pre)-configured amount of time may be dependent factors such as priority, sensing type, traffic periodicity, or cast type.

Soft prioritization of resource selection to facilitate bandwidth/time adaptation for power saving

If bandwidth adaptation for the sake of power saving is enabled, it may desirable to have a mechanism that prioritizes selection of sidelink resources for transmission from the set of anchor time/frequency resources used by UEs operating in power saving mode with reduced bandwidth/subset of time resources. The motivation behind such an operation may be performance in a low/medium congestion scenario. In this case, a UE (for example, a UE without power saving enabled) forming a candidate resource set may be expected to further check whether there are anchor resources prioritized for selection, and then select those resources for transmission. Such behavior (prioritization of candidate resources) may be triggered only if CBR measurement across system bandwidth or within anchor resources is below a predefined CBR threshold value. For example, one or more of the following aspects may be used:

Anchor time/frequency resources for power saving operation may be configured and used by UEs operating in power saving mode (e.g. set of sub-channels, slots within sidelink resource pool, etc.)

Anchor time/frequency resources (e.g. set of sub-channels, slots within sidelink resource pool, etc.) for power saving operation may be used for transmission / reception by UEs with an activated power saving feature

- UEs with a deactivated power saving feature may measure CBR, and if the measured CBR is below CBRRESOURCE_ADAPT THR , then the UE may prioritize selection of resources for transmission that intersect with or belong to anchor resources. If the amount of anchor resources in a candidate resource set is not enough, the UE mayuse other resources. o CBR measurement may be done either based on all resources within resources or considering only anchor resources.

- Different anchor resources may be configured in different geo-zones enabling soft time/frequency/spatial reuse in sidelink providing power saving and improved performance at low/medium loading.

UE partial sensing windows

Partial sensing is one mechanism that may be used for UE power saving. For NR sidelink communication, embodiments may include a partial sensing window size is determined based on the following parameters: 1) Type of sidelink transmission: semi-persistent (resource selection is done and reserved for periodic transmission (including retransmissions) of multiple TBs) or dynamic resource reservation (i.e. resource selection is done for each TB transmission)

2) SCI signaling window duration e.g. N = 32 logical slots

3) Resource selection window size

4) Whether it is the first TB transmission of a given resource selection process or not Duration and start/end position of partial sensing window have following dependency from the type of sidelink transmission:

1) Dynamic reservation a. Option 1. Partial sensing window start time is based on time instance/slot of resource reselection trigger (either the same or next slot) b. Option 2. Partial sensing window start time is ahead in time of resource reselection trigger on N logical slots (e.g. N = 32 and is associated with SCI signaling window size). It may be used if the UE has periodic traffic with predictable resource reselection time but semi-persistent reservations/transmissions are disabled by resource pool configuration. c. For a given dynamic reservation, partial sensing window duration may end at the slot of the last retransmission of a given TB d. For a given dynamic reservation, partial sensing window duration may end at the slot where the ACK signal is received on PSFCH or the subsequent slot due to PSFCH processing delay

2) Semi-persistent reservation a. Partial sensing window start time (slot) may be based on the set of configured periodicities in the system and resource reselection trigger and whether the it the first TB(resource reselection) or subsequent TBs of a given semi-persistent resource reservation process i. In case of the first TB it starts(triggered)at time instance/slot of resource reselection trigger or at subsequent slot ii. In case of the subsequent TBs transmission it starts ahead of resource reselection trigger time instance / slot by the value of max(SCI signaling window size, resource selection window size) b. Partial sensing window duration may depend on the time instance/slot of the last retransmission of a given TB or time instance when ACK is received for a given TB Sidelink Discontinuous Reception (DRX)

In legacy Rel. 16 NR sidelink designs, it may be assumed that the receiver is always on and monitoring all system resources defined in the system configuration. This always-on status may mean that a substantial amount of processing is used at the receiver. Sidelink DRX may be one solution to save a substantial amount of power. In accordance with various embodiments herein, the implementation of sidelink DRX may impact the physical layer implementation of the Rel. 17 NR V2X design. Embodiments may provide reduced power consumption, which may be beneficial for battery constraint devices to participate in NR sidelink communication. Additionally, or alternatively, embodiments may align DRX and partial sensing operation for the sake of power saving, and ensure proper tradeoff between reliability of transmissions and UE power consumption depending on communication types and services running at the UE side.

In general, the sidelink DRX may be defined by a DRX cycle that may include a predefined active time (which may be referred to as “On Duration” and which may be the time when the UE monitors sidelink PSCCH transmissions). The DRX cycle may also include a configurable potential inactivity time that relates to transition to an Inactivity time interval. The inactivity time interval may be when the UE may switch off the RX chain in order to save power, and thus does not monitor SL transmissions until the next On duration interval. In the region with a potential inactivity time, the identification of when the UE should transition into a sleep state may depend on factors such as sidelink physical layer activity. Due to the different behavior of the sidelink physical layer, different solutions dependent on the communication requirements may be needed as described with reference to embodiments below.

The power saving mechanism to be defined at the sidelink physical layer may be or include a partial sensing-based resource selection technique. A partial sensing operation may allow the UE to monitor PSCCH/PSSCH, and perform sensing only in a subset of slots that are processed for selection of sidelink resources for upcoming transmission.

From the physical layer perspective, one or more of the following potential implications and/or challenges may exist for sidelink DRX design that needs to be aligned with random or partial sensing mechanism for resource selection:

1) Support of sidelink communication between UEs operating in partial sensing mode for sidelink communication

2) Efficient support of sidelink unicast/groupcast/broadcast communication with low UE power consumption

3) Details of UE partial sensing behavior for dynamic and semi-persistent resource reservations a. Triggers to activate On-Duration time intervals of sidelink DRX mechanism 4) Sidelink HARQ support - max amount of sidelink retransmissions, and minimum time between retransmissions or feedback

5) Conditions/Triggers to transition to or from an On-Duration time interval

6) On-Duration time interval dependency on partial sensing window duration and allocation in time, UE resource selection window duration and allocation in time, SCI signaling window duration allocation in time, packet delay budget and HARQ operation, as well as destination ID (L1/L2) or source ID (L1/L2), priority of sidelink transmission

7) Sidelink measurements intervals (e.g. CBR measurements)

8) Consideration on non-sidelink subframes

SL DRX Cycle Triggering Conditions and LENGTH of “On-Duration” time interval

The extent of the “On-Duration” time interval may be controlled by timers which may be initialized by different values and/or activated by different triggers.

The triggering condition and start time instance of the SL DRX “On-Duration” time interval may be a function of the configured set of periodicities available for sidelink transmissions, resource reselection trigger time instance, switching time from the sleep state (light or deep), partial sensing trigger, current time instance (slot), SFN/DFN slot 0, UE destination ID, and/or type of sidelink communication (e.g. sidelink transmission w/ semi-persistent or dynamic resource reservation).

Embodiments below may include examples of how an On-Duration timer may be initialized for different triggering conditions (set of wake-up triggers).

Sidelink partial sensing trigger

In case of a partial sensing-only operation, the On-Duration timer may be initialized by the duration which may be a function of one or more of:

1) resource selection window size (determined by UE) (e.g. for semipersi stent reservations)

2) configured partial sensing window size

3) packet delay budget

4) SCI signaling window duration

5) T2min value defined by the relevant 3 GPP specifications

6) values configured through sidelink RRC/MAC CE signaling during UE negotiations

7) One or more of the above components plus switching/transition time from a sleep state (e.g., a light sleep state or a deep sleep state)

Sidelink partial sensing and resource re-selection trigger In the case of a partial sensing procedure followed by a resource selection procedure, the On-Duration timer can be initialized by or based on one or more of the following:

1) total partial sensing widow duration and resource selection window duration

2) configured partial sensing window size

3) resource selection window duration only

4) packet delay budget for processed packet

5) SCI signaling window duration

6) T2min value defined by spec

7) values configured through sidelink RRC/MAC CE signaling during UE negotiations

Resource re-selection or pre-emption check triggers

In the case of a resource re-selection procedure or preemption check, the On-Duration timer may be initialized in accordance with one or more of the following parameters:

1) resource selection window size (determined by UE) (e.g. for semipersistent reservations) or remaining resource selection window

2) configured partial sensing window size or min partial sensing window

3) packet delay budget or remaining packet delay budget

4) SCI signaling window duration

5) T2min value defined by spec

7) or a function of one or more of the above components plus switching time from a sleep state (e.g., a light sleep state or a deep sleep state)

Sidelink measurements trigger (e.g. CBR)

In some embodiments, if the UE is expected to perform CBR measurements that not aligned with partial sensing windows, then it may activate separate On-Duration time intervals.

PSFCH reception trigger

If the UE wants to transmit with, for example, random resource selection and HARQ feedback request enabled, then it may need to switch on receive processing and activate On- Duration interval.

The specific value to initialize the On-Duration timer may be determined as a function of one or more of the following configuration settings (function arguments):

1) configured set of periodicities available for sidelink transmissions,

2) resource reselection trigger time instance (e.g. symbol/slot/subframe/frame index), 3) partial sensing trigger time instance (e.g. symbol/slot/subframe/frame index)

4) current time instance (e.g. symbol/slot/subframe/frame index)

5) SFN/DFN slot 0 time instance

6) UE destination/ source ID

7) type of sidelink communication (e.g. sidelink transmission w/ semi-persistent or dynamic resource reservation)

8) power saving/consumption state

9) Pre-configured On-Duration timer settings

Sidelink DRX Cycle configuration dependencies

Different solutions related to sidelink DRX may be required dependent on whether traffic is periodic or aperiodic. Specifically:

• Periodic traffic: In this case the transmission may have certain periodicity in time. This periodicity may mean that the DRX cycle may be adapted to the set of the configured periodicity values. The start time of the active time may be required to ensure that the required sensing and measurement procedures may be performed prior to sidelink transmission. The minimum active duration may be required to to ensure that all potential retransmissions may be handled without the UE transitioning to the inactivity state The Packet Delay Budget (PDB) may be known prior to wake-up, so the minimal DRX on duration may be planned accordingly.

• Aperiodic traffic: For aperiodic traffic, the packet arrival time at the higher layers may not be predictable. However, in some cases, the delay budget of all potential traffic may be available. Because the device may know how long it will take to wake-up (for example, if a packet arrives at the higher layers) so it may plan the SL DRX cycle accordingly. This may also mean that if the device can constantly expect high priority traffic with a very short PDB, it may not be suitable to transition to the inactivity state at all. For other types of potential PDB, a lighter sleep time may be enough. These times may also be dependent on the configured resource reservation schemes. These schemes may be different dependent on the PDB the priority or other parameter of the communication.

The overall sidelink DRX UE behavior for sidelink may be viewed as multiple sidelink DRX cycles running in parallel (e.g. a system-wide sidelink DRX cycle, a sidelink DRX cycle for partial sensing - based resource selection for dynamic or semi-persistent resource reservations, a sidelink DRX cycle for random resource selection, and/or different sidelink DRX cycles for different unicast/groupcast connections). Alternatively, the functionality of multiple DRX cycles may be integrated into a single sidelink DRX cycle design. Another possible option may be to decouple a partial sensing operation from sidelink DRX cycle operation. In this case, sidelink DRX behavior may only depend on the traffic.

SL DRX implementation of the inactivity timer

In some embodiments, sidelink HARQ ACK may act as a trigger for an inactivity timer. Sidelink HARQ NACK may act to reset the inactivity timer.

The inactivity timer may be required to address different events relative to the DL DRX inactivity timer. The inactivity timer, or the events that it addresses, may be dependent on or related to one or more of the following conditions:

• Priority broadcast: As some devices may only be interested in higher priority messages for broadcast, the inactivity timer may be configured to not reset if lower priority broadcast messages are received. In some embodiments, the inactivity timer may be configured to not consider broadcast transmission at all.

• Cast type: The inactivity timer may be configured to only consider transmissions of certain cast types.

• Power saving state / battery state: The configuration of the inactivity timer may also change dependent on the battery state of the devices. In some embodiments, as the battery state decreases, the priority of the transmission to reset the timer may increase.

• Communication context: In scenarios where unicast or groupcast messages are transmitted, such messages may trigger a response for a request. As a result, the device may not be allowed to go to sleep before this response is transmitted and correctly received.

Long and Short SL DRX cycles

In aDRX procedure related to the UU interface, the configuration may be split between a long and a short DRX. The short DRX may be used for variations on a small-time scale. An example of such a time scale may be decoding the physical downlink control channel (PDCCH) only every 3^rd slot. In embodiments where sidelink DRX is used, such small scale variations may not be possible because actual allocation of resources may be unknown. Thus, the above considerations may begenerally applied to “long” sidelink DRX. However, for unicast and groupcast with sidelink DRX, it may be possible to also introduce a short sidelink DRX cycle. In this case, only a subset of the available slots may be used inside the On-Duration. However, such a cycle may result in a restriction on resource selection. Figure 2 depicts an example technique 200 related to low power NR sidelink communication, in accordance with various embodiments. The technique 200 may be performed by one or more processors of an electronic device such as a user equipment (UE) in a NR cellular network.

The technique 200 may include identifying, at 205 by the UE based on a first factor related to random resource selection or partial sensing of other devices within a vicinity of the UE, first one or more resources to be used for an initial NR sidelink transmission. The technique 200 may further include reserving, at 210 by the UE based on the first factor, the identified first one or more resources for the initial NR sidelink transmission. The technique 200 may further include transmitting, at 215 by the UE, the initial NR sidelink transmission on the identified first one or more resources. In some embodiments, the one or more processors may facilitate transmission at 215 of the initial NR sidelink transmission. Facilitation of the transmission may include providing data related to the transmission to one or more other processors or systems of the UE such as radio frequency (RF) circuitry or antenna circuitry of the UE for transmission.

It will be understood that this technique is intended as one example technique in accordance with embodiments herein, and other embodiments may vary. For example, other embodiments may have more or fewer elements, elements performed in another order than depicted, elements performed concurrently, etc.

Figure 3 illustrates an example technique 300 related to NR sidelink discontinuous reception (DRX), in accordance with various embodiments. The technique 300 may be performed by one or more processors of an electronic device such as a user equipment (UE) in a 5G cellular network.

The technique 300 may include identifying, at 305, parameters of a discontinuous reception (DRX) procedure that is to be used by the UE for NR sidelink data, wherein the parameters include an active region of time in which the UE is to monitor for the NR sidelink data and an inactive region of time in which the UE is to not monitor for the NR sidelink data. The technique 300 may further include performing, at 310, the DRX procedure for NR sidelink data.

SYSTEMS AND IMPLEMENTATIONS Figures 4-6 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

Figure 4 illustrates a network 400 in accordance with various embodiments. The network 400 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3 GPP systems, or the like.

The network 400 may include a UE 402, which may include any mobile or non-mobile computing device designed to communicate with a RAN 404 via an over-the-air connection. The UE 402 may be communicatively coupled with the RAN 404 by a Uu interface. The UE 402 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.

In some embodiments, the network 400 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

In some embodiments, the UE 402 may additionally communicate with an AP 406 via an over-the-air connection. The AP 406 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 404. The connection between the UE 402 and the AP 406 may be consistent with any IEEE 802.11 protocol, wherein the AP 406 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 402, RAN 404, and AP 406 may utilize cellular-WLAN aggregation (for example, LWA/LWIP). Cellular-WLAN aggregation may involve the UE 402 being configured by the RAN 404 to utilize both cellular radio resources and WLAN resources.

The RAN 404 may include one or more access nodes, for example, AN 408. AN 408 may terminate air-interface protocols for the UE 402 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 408 may enable data/voice connectivity between CN 420 and the UE 402. In some embodiments, the AN 408 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 408 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 408 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

In embodiments in which the RAN 404 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 404 is an LTE RAN) or an Xn interface (if the RAN 404 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.

The ANs of the RAN 404 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 402 with an air interface for network access. The UE 402 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 404. For example, the UE 402 and RAN 404 may use carrier aggregation to allow the UE 402 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.

The RAN 404 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.

In V2X scenarios the UE 402 or AN 408 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

In some embodiments, the RAN 404 may be an LTE RAN 410 with eNBs, for example, eNB 412. The LTE RAN 410 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub-6 GHz bands.

In some embodiments, the RAN 404 may be an NG-RAN 414 with gNBs, for example, gNB 416, or ng-eNBs, for example, ng-eNB 418. The gNB 416 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 416 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 418 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 416 and the ng-eNB 418 may connect with each other over an Xn interface.

In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 414 and a UPF 448 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN414 and an AMF 444 (e.g., N2 interface).

The NG-RAN 414 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.

In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 402 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 402, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 402 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 402 and in some cases at the gNB 416. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

The RAN 404 is communicatively coupled to CN 420 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 402). The components of the CN 420 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 420 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 420 may be referred to as a network slice, and a logical instantiation of a portion of the CN 420 may be referred to as a network sub-slice.

In some embodiments, the CN 420 may be an LTE CN 422, which may also be referred to as an EPC. The LTE CN 422 may include MME 424, SGW 426, SGSN 428, HSS 430, PGW 432, and PCRF 434 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 422 may be briefly introduced as follows.

The MME 424 may implement mobility management functions to track a current location of the UE 402 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.

The SGW 426 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 422. The SGW 426 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

The SGSN 428 may track a location of the UE 402 and perform security functions and access control. In addition, the SGSN 428 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 424; MME selection for handovers; etc. The S3 reference point between the MME 424 and the SGSN 428 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active states.

The HSS 430 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 430 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 430 and the MME 424 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 420. The PGW 432 may terminate an SGi interface toward a data network (DN) 436 that may include an application/content server 438. The PGW 432 may route data packets between the LTE CN 422 and the data network 436. The PGW 432 may be coupled with the SGW 426 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 432 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 432 and the data network 4 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 432 may be coupled with a PCRF 434 via a Gx reference point.

The PCRF 434 is the policy and charging control element of the LTE CN 422. The PCRF 434 may be communicatively coupled to the app/content server 438 to determine appropriate QoS and charging parameters for service flows. The PCRF 432 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

In some embodiments, the CN 420 may be a 5GC 440. The 5GC 440 may include an AUSF 442, AMF 444, SMF 446, UPF 448, NSSF 450, NEF 452, NRF 454, PCF 456, UDM 458, and AF 460 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 440 may be briefly introduced as follows.

The AUSF 442 may store data for authentication of UE 402 and handle authentication- related functionality. The AUSF 442 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 440 over reference points as shown, the AUSF 442 may exhibit an Nausf service-based interface.

The AMF 444 may allow other functions of the 5GC 440 to communicate with the UE 402 and the RAN 404 and to subscribe to notifications about mobility events with respect to the UE 402. The AMF 444 may be responsible for registration management (for example, for registering UE 402), connection management, reachability management, mobility management, lawful interception of AMF -related events, and access authentication and authorization. The AMF 444 may provide transport for SM messages between the UE 402 and the SMF 446, and act as a transparent proxy for routing SM messages. AMF 444 may also provide transport for SMS messages between UE 402 and an SMSF. AMF 444 may interact with the AUSF 442 and the UE 402 to perform various security anchor and context management functions. Furthermore, AMF 444 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 404 and the AMF 444; and the AMF 444 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection. AMF 444 may also support NAS signaling with the UE 402 over an N3 IWF interface.

The SMF 446 may be responsible for SM (for example, session establishment, tunnel management between UPF 448 and AN 408); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 448 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 444 over N2 to AN 408; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 402 and the data network 436.

The UPF 448 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 436, and a branching point to support multi-homed PDU session. The UPF 448 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF- to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 448 may include an uplink classifier to support routing traffic flows to a data network.

The NSSF 450 may select a set of network slice instances serving the UE 402. The NSSF 450 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 450 may also determine the AMF set to be used to serve the UE 402, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 454. The selection of a set of network slice instances for the UE 402 may be triggered by the AMF 444 with which the UE 402 is registered by interacting with the NSSF 450, which may lead to a change of AMF. The NSSF 450 may interact with the AMF 444 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 450 may exhibit an Nnssf service-based interface.

The NEF 452 may securely expose services and capabilities provided by 3 GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 460), edge computing or fog computing systems, etc. In such embodiments, the NEF 452 may authenticate, authorize, or throttle the AFs. NEF 452 may also translate information exchanged with the AF 460 and information exchanged with internal network functions. For example, the NEF 452 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 452 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 452 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 452 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 452 may exhibit an Nnef service-based interface.

The NRF 454 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 454 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 454 may exhibit the Nnrf service-based interface.

The PCF 456 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 456 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 458. In addition to communicating with functions over reference points as shown, the PCF 456 exhibit an Npcf service-based interface.

The UDM 458 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 402. For example, subscription data may be communicated via an N8 reference point between the UDM 458 and the AMF 444. The UDM 458 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 458 and the PCF 456, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 402) for the NEF 452. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 458, PCF 456, and NEF 452 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM- FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 458 may exhibit the Nudm service-based interface.

The AF 460 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

In some embodiments, the 5GC 440 may enable edge computing by selecting operator/3^rd party services to be geographically close to a point that the UE 402 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 440 may select a UPF 448 close to the UE 402 and execute traffic steering from the UPF 448 to data network 436 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 460. In this way, the AF 460 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 460 is considered to be a trusted entity, the network operator may permit AF 460 to interact directly with relevant NFs. Additionally, the AF 460 may exhibit an Naf service-based interface.

The data network 436 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 438.

Figure 5 schematically illustrates a wireless network 500 in accordance with various embodiments. The wireless network 500 may include a UE 502 in wireless communication with an AN 504. The UE 502 and AN 504 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.

The UE 502 may be communicatively coupled with the AN 504 via connection 506. The connection 506 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR. protocol operating at mmWave or sub-6GHz frequencies.

The UE 502 may include a host platform 508 coupled with a modem platform 510. The host platform 508 may include application processing circuitry 512, which may be coupled with protocol processing circuitry 514 of the modem platform 510. The application processing circuitry 512 may run various applications for the UE 502 that source/sink application data. The application processing circuitry 512 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations

The protocol processing circuitry 514 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 506. The layer operations implemented by the protocol processing circuitry 514 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

The modem platform 510 may further include digital baseband circuitry 516 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 514 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

The modem platform 510 may further include transmit circuitry 518, receive circuitry 520, RF circuitry 522, and RF front end (RFFE) 524, which may include or connect to one or more antenna panels 526. Briefly, the transmit circuitry 518 may include a digital -to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 520 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 522 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 524 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 518, receive circuitry 520, RF circuitry 522, RFFE 524, and antenna panels 526 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.

In some embodiments, the protocol processing circuitry 514 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.

A UE reception may be established by and via the antenna panels 526, RFFE 524, RF circuitry 522, receive circuitry 520, digital baseband circuitry 516, and protocol processing circuitry 514. In some embodiments, the antenna panels 526 may receive a transmission from the AN 504 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 526.

A UE transmission may be established by and via the protocol processing circuitry 514, digital baseband circuitry 516, transmit circuitry 518, RF circuitry 522, RFFE 524, and antenna panels 526. In some embodiments, the transmit components of the UE 504 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 526.

Similar to the UE 502, the AN 504 may include a host platform 528 coupled with a modem platform 530. The host platform 528 may include application processing circuitry 532 coupled with protocol processing circuitry 534 of the modem platform 530. The modem platform may further include digital baseband circuitry 536, transmit circuitry 538, receive circuitry 540, RF circuitry 542, RFFE circuitry 544, and antenna panels 546. The components of the AN 504 may be similar to and substantially interchangeable with like-named components of the UE 502. In addition to performing data transmission/reception as described above, the components of the AN 508 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

Figure 6 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 6 shows a diagrammatic representation of hardware resources 600 including one or more processors (or processor cores) 610, one or more memory/storage devices 620, and one or more communication resources 630, each of which may be communicatively coupled via a bus 640 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 602 may be executed to provide an execution environment for one or more network slices/ sub-slices to utilize the hardware resources 600.

The processors 610 may include, for example, a processor 612 and a processor 614. The processors 610 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

The memory/storage devices 620 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 620 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

The communication resources 630 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 604 or one or more databases 606 or other network elements via a network 608. For example, the communication resources 630 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components. Instructions 650 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 610 to perform any one or more of the methodologies discussed herein. The instructions 650 may reside, completely or partially, within at least one of the processors 610 (e.g., within the processor’s cache memory), the memory/storage devices 620, or any suitable combination thereof. Furthermore, any portion of the instructions 650 may be transferred to the hardware resources 600 from any combination of the peripheral devices 604 or the databases 606. Accordingly, the memory of processors 610, the memory/storage devices 620, the peripheral devices 604, and the databases 606 are examples of computer-readable and machine-readable media.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

EXAMPLES

Example 1 may include the NR SL resource selection scheme where the initial transmission including resource reservation is based on random resource selection and subsequent transmission are based on full sensing.

Example 2 may include A NR SL resource selection scheme where the initial transmission including resource reservation is based on partial sensing selection and subsequent transmission are based on full sensing.

Example 3 may include the NR SL resource selection scheme where the initial transmission including resource reservation is based on random resource selection and subsequent transmission are based on partial sensing.

Example 4 may include the resource selection scheme in examples 1, 2 or 3 or some other example herein, where the initial transmission is also used for semi persistent resource reservation.

Example 5 may include the resource selection schemes in examples 1, 2 or 3 or some other example herein, where the usage of a different scheme is indicated in the control information. Example 6 may include the resource selection schemes in examples 1,2,3 or some other example herein where the selection of the different schemes depend on: a. Power delay budget b. Power saving mode activation c. Device feature configuration d. Any combination of the above

Example 7 may include partial resource sensing procedure where the active time of each device is known by other devices to enable communication a. The procedure in 7 where a system wide partial sensing cycle alignment is achieved i. The procedure in 7a. utilizing a common configuration as an offset in terms of SFN/DFN and a duration ii. The procedure in 7a. where a device specific active duration is defined based on UE ID or a higher layer ID possibly dependent on the service or application iii. The procedure in 7a. using signaling over the Uu interface while in coverage of a network b. The procedure in 7 where only certain device groups are aligned in terms of their partial sensing cycle c. The procedure in 7a. or 7b. where the alignment is different dependent on the cast type (unicast, groupcast or broadcast) d. The procedure in 7a. or 7b. where the alignment in for unicast groupcast is signaled iv. The procedure in 7d. utilizing the SL interface for the signaling v. The procedure in 7d. utilizing the Uu interface for the signaling vi. The procedure in 7d. signaling changes for the alignment during active communication on the SL.

Example 8 may include the congestion control and open loop power control based on periodic CBR measurements a. The method in 8 where the measurement window is (pre)-configured b. The method in 8 where the measurement window is configured via the network c. The method in 8 where the measurement only needs to be performed in no current measurement is available at the end of the required window d. The method in 8 where the measurements from multiple instances are combined according to their length. Example 9 may include congestion control and open loop power control based on CBR measurements where the resulting CBR measurement depends also on preceding measurements considering a. The measurement window length b. The time that passed since the last measurement.

Example 10 may include congestion control mechanism for devices utilizing random resource selection or partial sensing based on: a. CBR measurements that consider a nonconsecutive amount of slots b. CBR measurements on past transmission for semi persistent transmissions c. CBR measurements based on the reduced window size d. Combination of CBR measurements in the past.

Example 11 may include congestion control mechanism for devices utilizing random resource selection or partial sensing not based on CBR measurements but on: a. Allocations of the control channel of other devices in a window before the transmission b. Allocation of the feedback channel of other devices in a window before the transmission c. PSCCH DMRS RSRP d. Deriving the CBR index from transmission of close by devices e. Using the CBR index indicated in the control information (SCI) of physical close devices f. A default CBR index (pre)-configured dependent on the cast type and sensing type g. The switching between the above-mentioned cases and CBR measurements based on availability of those.

Example 12 may include soft prioritization scheme for the resource selection to facilitate bandwidth/time adaptation for power saving.

Example 13 may include UE partial sensing window that is dependent on: a. Type of sidelink transmission like semi-persistent or dynamic resource reservation b. SCI resource signaling window duration c. Resource selection window size d. Whether it is the first transmission of a resource selection process.

Example 14 may include UE partial sensing process with the duration and start/end position of the partial sensing window being dependent on: a. Dynamic reservation with vii. Partial sensing window start time being based on the time instance of the resource reselection trigger viii. Partial sensing window start time is ahead of a predictable resource reselection trigger in the future ix. Partial sensing window ends at the slot of the last retransmission of a given TB x. Partial sensing window ends when ACK or no NACK (in cast of NACK only feedback) is received b. Semi-persistent reservation with xi. Partial sensing window start time is based on the set of configured periodicities and the resource reselection trigger and

1. For the case that it is the first transmission of the semi persistent resource reservation it starts at the resource reselection trigger

2. For the case that it is not the first transmission it starts ahead of the known resource reselection trigger (known by the periodicity) xii. Partial sensing window duration depends on the time of the last possible retransmission of a given TB or the time ACK is received or the time no NACK is received for NACK only feedback.

Example 15 is a method comprising: receiving, by a UE, a signal that includes an indication of a packet for side link transmission; determining, by the UE, based upon latency and power consumption of the UE, resources for initial transmission of a transmission block; determining, by the UE, the transmission block; and transmitting, by the UE, the transmission block using the determined resources.

Example 16 may include the method of example 15, or of any other example herein, wherein determining resources further includes randomly selecting resources.

Example 17 may include the method of example 15, or of any other example herein, wherein determining resources further includes randomly selecting resources using aggregated sensing data for subsequent transmissions.

Example 18 may include the method of example 15, or of any other example herein, wherein determining resources further includes determining resources where sensing data is used to determine initial resource reservations. AD4697

Example 1 may include SL DRX procedure to enable Devices power saving.

Example 2 may include the SL DRX procedure in example 1 or some other example herein, where the SL DRX cycle includes an active and a potential inactive region.

Example 3 may include the SL DRX procedure in example 1 or some other example herein, where the SL DRX active and inactive region depend on the requirements on the physical layer communication requirements.

Example 4 may include the SL DRX procedure in example 1 or some other example herein, where the active time of each device is known by other devices to enable communication e. The procedure in 4 where a system wide SL DRX cycle alignment is achieved i. The procedure in 4a. utilizing a common configuration as an offset in terms of SFN/DFN and a duration ii. The procedure in 4a. where a device specific active duration is defined based on UE ID or a higher layer ID possibly dependent on the service or application iii. The procedure in 4a. using signaling over the Uu interface while in coverage of a network f. The procedure in 4 where only certain device groups are aligned in terms of their SL DRX cycle g. The procedure in 4a. or 4b. where the alignment is different dependent on the cast type (unicast, groupcast or broadcast) h. The procedure in 4a. or 4b. where the alignment in for unicast groupcast is signaled i. The procedure in 4d. utilizing the SL interface for the signaling ii. The procedure in 4d. utilizing the Uu interface for the signaling iii. The procedure in 4d. signaling changes for the alignment during active communication on the SL

Example 5 may include the SL DRX procedure in example 1 or some other example herein, where the trigger to transition to the active state is based on a. The SL communication periodicities for periodic traffic b. The resource reselection trigger time instance c. Pre-emption check time instance d. Partial sensing trigger e. Time instance based on other alignment procedures f. The UE destination or source ID g. The type of sidelink communication h. Required SL measurement trigger i. HARQ reception trigger j . Any combination of the above

Example 6 may include the trigger in example 5 or some other example herein, where the resulting active duration length after a partial sensing trigger is based on a. The resource selection window size b. Configured partial sensing window size c. The packet delay budget d. SCI signaling window duration e. T2min value defined in the specification f. Values configure through sidelink RRC/MAC CE signaling during UE negotiation g. Value (pre)configured in the resource pool configuration h. Any combination of the above including the by the device know time to switch between the active and inactive state as well as vice versa

Example 7 may include the trigger in example 5 or some other example herein, where the resulting active duration length after a partial sensing and resource re-selection trigger is based on a. The total partial sensing window duration and the resource selection window duration b. The configured partial sensing window size c. The resource selectin window duration d. The packet delay budget e. SCI signaling window duration f. T2min value defined in the specification g. Values configure through sidelink RRC/MAC CE signaling during UE negotiation h. Value (pre)configured in the resource pool configuration i. Any combination of the above including the by the device know time to switch between the active and inactive state as well as vice versa

Example 8 may include the trigger in example 5 or some other example herein, where the resulting active duration length after a resource re-selection or pre-emption check trigger a. The total partial sensing window duration and the resource selection window duration b. The configured partial sensing window size c. The resource selectin window duration d. The packet delay budget e. SCI signaling window duration f. T2min value defined in the specification g. Values configure through sidelink RRC/MAC CE signaling during UE negotiation h. Value (pre)configured in the resource pool configuration i. Any combination of the above including the by the device know time to switch between the active and inactive state as well as vice versa

Example 9 may include the trigger in example 5 or some other example herein, where the resulting active duration length after a HARQ reception trigger is based on a. The configured set of periodicities available for sidelink transmission b. Resource reselection trigger time instances (e.g. symbol/slot/subframe/frame index) c. Partial sensing trigger time instance (e.g. symbol/slot/subframe/frame index) d. Partial sensing trigger time instance (e.g. symbol/slot/subframe/frame index) e. Current time instance (e.g. symbol/slot/subframe/frame index) f. SFN/DFN slot time instance g. UE destination/ source ID h. Type of sidelink communication (e.g. sidelink transmission w/ semi -persistent or dynamic resource reservation) i. Power saving/consumption state j . Pre-configured On-Duration time setting k. Any combination of the above including the by the device know time to switch between the active and inactive state as well as vice versa

Example 10 may include the SL DRX procedure in example 1 or some other example herein, where configuration of the cycle is dependent if periodic or aperiodic traffic is expected l. The procedure in 10 where the location and duration of the active time is ensuring all requirements of the periodic communication in terms of power delay budget, measurements, sensing procedures and (pre)-emption checks as well as potential HARQ feedback m. The procedure in 10 where the location and duration of the active time in the case aperiodic traffic ensure that all potential requirements of the communication is met

Example 11 may include the SL DRX procedure in example 1 or some other example herein, where the SL DRX for different communication instances for the SL in the same device are treated as independent SL DRX procedures

Example 12 may include the SL DRX procedure in example 1 or some other example herein, where the SL DRX for different communication instances for the SL in the same devices are combined to form a single SL DRX procedure

Example 13 may include the SL DRX procedure in example 1 or some other example herein, where the implementation of the inactivity timer is based a. SL HARQ ACK triggering the inactivity timer b. SL HARQ NACK resetting the inactivity timer c. The priority of the last received transmission d. The cast types e. The power saving state f. The battery states g. A combination of the above

Example 14 may include the SL DRX procedure where short SL DRX cycles are only configured for unicast and groupcast.

Example 15 may include a method comprising: determining a slidelink (SL) discontinuous reception (DRX) configuration of a user equipment (UE) for communication on a sidelink channel; and communicating with the UE on the sidelink channel based on the DRX configuration.

Example 16 may include the method of example 15 or some other example herein, wherein the DRX configuration includes one or more active time periods and one or more inactive time periods.

Example 17 may include the method of example 15-16 or some other example herein, wherein the DRX configuration is determined according to a common configuration (e.g., as an offset in terms of SFN/DFN and a duration).

Example 18 may include the method of example 15-17 or some other example herein, wherein the DRX configuration is determined based on an ID associated with the UE (e.g., UE ID or a higher layer ID such as an ID associated with a service or application).

Example 19 may include the method of example 15-18 or some other example herein, further comprising receiving an indication of the DRX configuration (e.g., over a Uu interface). Example 20 may include the method of example 15-19 or some other example herein, wherein the method is performed by another UE or a portion thereof.

Example 21 includes a method to be performed by a user equipment (UE) in a new radio (NR) cellular network, wherein the method comprises: identifying, by the UE based on a first factor related to random resource selection or partial sensing of other devices within a vicinity of the UE, first one or more resources to be used for an initial NR sidelink transmission; reserving, by the UE based on the first factor, the identified first one or more resources for the initial NR sidelink transmission; and transmitting or facilitating transmission of, by the UE, the initial NR sidelink transmission on the identified first one or more resources.

Example 22 may include the method of example 21, or some other example herein, further comprising performing, by the UE, an open loop power control (OPLC) based on periodic channel busy ratio (CBR) measurements.

Example 23 may include the method of example 21, or some other example herein, further comprising performing, by the UE, semi-persistent resource reservation based on the first factor.

Example 24 may include the method of example 21, or some other example herein, wherein an active time of the other devices is known to the UE prior to performance of partial sensing.

Example 25 may include the method of any of examples 21-24, or some other example herein, further comprising: identifying, by the UE based on a second factor related to full sensing or partial sensing of the other devices within the vicinity of the UE, second one or more resources to be used for a subsequent NR sidelink transmission; reserving, by the UE based on the second factor, the identified second one or more resources of the subsequent NR sidelink transmission; and transmitting or facilitating transmission of, by the UE, the subsequent NR sidelink transmission on the identified second one or more resources.

Example 26 may include the method of example 25, or some other example herein, wherein the first factor is random resource selection and the second factor is full sensing.

Example 27 may include the method of example 25, or some other example herein, wherein the first factor is partial sensing and the second factor is full sensing.

Example 28 may include the method of example 25, or some other example herein, wherein the first factor is random resource selection and the second factor is partial sensing.

Example 29 may include the method of example 25, or some other example herein, wherein the first factor or the second factor are based on control information received by the UE. Example 30 may include the method of example 25, or some other example herein, wherein the first factor or second factor are based on one or more of a power delay budget, a power saving mode activation, and a device feature configuration.

Example 31 may include a method to be performed by a user equipment (UE) in a new radio (NR) wireless network, wherein the method comprises: identifying, by the UE, parameters of a discontinuous reception (DRX) procedure that is to be used by the UE for NR sidelink data, wherein the parameters include an active region of time in which the UE is to monitor for the NR sidelink data and an inactive region of time in which the UE is to not monitor for the NR sidelink data; and performing, by the UE, the DRX procedure for NR sidelink data.

Example 32 may include the method of example 31, or some other example herein, wherein a length of the active region or a length of the inactive region are based on requirements of the NR network related to physical layer transmissions.

Example 33 may include the method of example 31, or some other example herein, wherein a length of the active region of time is known to other UEs in the NR network.

Example 34 may include the method of any of examples 31-33, or some other example herein, wherein an indication of a length of the active region of time or a length of the inactive region of time is identified based on a transmission received from a NR NodeB (gNB) of the network.

Example 35 may include the method of example 34, wherein the indication is related to a system frame number (SFN) or a direct frame number (DFN) and an offset value.

Example 36 may include the method of any of examples 31-33, or some other example herein, wherein a length of the active region or a length of the inactive region is based on a type of SL transmission that the UE is to transmit.

Example 37 may include the method of example 36, wherein the type is one of unicast, groupcast, or broadcast.

Example 38 may include the method of any of examples 31-33, or some other example herein, wherein the UE is to change from the inactive region of time to the active region of time based on a partial sensing trigger.

Example 39 may include the method of any of examples 31-33, or some other example herein, wherein the UE is to change from the inactive region of time to the active region of time based on a resource re-selection trigger.

Example 40 may include the method of any of examples 31-33, or some other example herein, wherein the UE is to change from the inactive region of time to the active region of time based on a hybrid automatic repeat request (HARQ) reception trigger. Example 41 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-40, or any other method or process described herein.

Example 42 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-40, or any other method or process described herein.

Example 43 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-40, or any other method or process described herein.

Example 44 may include a method, technique, or process as described in or related to any of examples 1-40, or portions or parts thereof.

Example 45 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-40, or portions thereof.

Example 46 may include a signal as described in or related to any of examples 1-40, or portions or parts thereof.

Example 47 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-40, or portions or parts thereof, or otherwise described in the present disclosure.

Example 48 may include a signal encoded with data as described in or related to any of examples 1-40, or portions or parts thereof, or otherwise described in the present disclosure.

Example 49 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-40, or portions or parts thereof, or otherwise described in the present disclosure.

Example 50 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-40, or portions thereof.

Example 51 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-40, or portions thereof.

Example 52 may include a signal in a wireless network as shown and described herein. Example 53 may include a method of communicating in a wireless network as shown and described herein.

Example 54 may include a system for providing wireless communication as shown and described herein.

Example 55 may include a device for providing wireless communication as shown and described herein.

Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computerexecutable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.

The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.

The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/ systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.

The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.

The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content.

The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration .

The term “SSB” refers to an SS/PBCH block.

The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.

The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.

The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.

The term “Serving Cell” refers to the primary cell for a UE in RRC CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.

The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC CONNECTED configured with CA/.

The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

Claims

1. An electronic device for use in a user equipment (UE) of a new radio (NR) cellular network, wherein the electronic device comprises: one or more processors; and one or more non-transitory computer-readable media comprising instructions that, upon execution of the instructions by the one or more processors, are to cause the electronic device to: identify, based on a first factor related to random resource selection or partial sensing of other devices within a vicinity of the UE, first one or more resources to be used for an initial NR sidelink transmission; reserve, based on the first factor, the identified first one or more resources for the initial NR sidelink transmission; and facilitate transmission of the initial NR sidelink transmission on the identified first one or more resources.

2. The electronic device of claim 1, wherein the instructions are further to cause the electronic device to perform an open loop power control (OPLC) based on periodic channel busy ratio (CBR) measurements.

3. The electronic device of claim 1, wherein the instructions are further to cause the electronic device to perform, by the UE, semi-persistent resource reservation based on the first factor.

4. The electronic device of claim 1, wherein an active time of the other devices is known to the UE prior to performance of partial sensing.

5. The electronic device of any of claims 1-4, wherein the instructions are further to cause the electronic device to: identify, based on a second factor related to full sensing or partial sensing of the other devices within the vicinity of the UE, second one or more resources to be used for a subsequent NR sidelink transmission, reserve, based on the second factor, the identified second one or more resources of the subsequent NR sidelink transmission; and facilitate transmission of the subsequent NR sidelink transmission on the identified second one or more resources.

6. The electronic device of claim 5, wherein the first factor is random resource selection and the second factor is full sensing.

7. The electronic device of claim 5, wherein the first factor is partial sensing and the second factor is full sensing.

8. The electronic device of claim 5, wherein the first factor is random resource selection and the second factor is partial sensing.

9. The electronic device of claim 5, wherein the first factor or the second factor are based on control information received by the UE.

10. The electronic device of claim 5, wherein the first factor or second factor are based on one or more of a power delay budget, a power saving mode activation, and a device feature configuration.

11. An electronic device for use in a user equipment (UE) of a new radio (NR) cellular network, wherein the electronic device comprises: one or more processors; and one or more non-transitory computer-readable media comprising instructions that, upon execution of the instructions by the one or more processors, are to cause the electronic device to: identify parameters of a discontinuous reception (DRX) procedure that is to be used by the UE for NR sidelink data, wherein the parameters include an active region of time in which the UE is to monitor for the NR sidelink data and an inactive region of time in which the UE is to not monitor for the NR sidelink data; and perform the DRX procedure for NR sidelink data.

12. The electronic device of claim 11, wherein a length of the active region or a length of the inactive region are based on requirements of the NR network related to physical layer transmissions.

13. The electronic device of claim 11, wherein a length of the active region of time is known to other UEs in the NR network.

14. The electronic device of any of claims 11-13, wherein an indication of a length of the active region of time or a length of the inactive region of time is identified based on a transmission received from a NR NodeB (gNB) of the network.

15. The electronic device of claim 14, wherein the indication is related to a system frame number (SFN) or a direct frame number (DFN) and an offset value.

16. The electronic device of any of claims 11-13, wherein a length of the active region or a length of the inactive region is based on a type of SL transmission that the UE is to transmit.

17. The electronic device of claim 16, wherein the type is one of unicast, groupcast, or broadcast.

18. The electronic device of any of claims 11-13, wherein the UE is to change from the inactive region of time to the active region of time based on a partial sensing trigger.

19. The electronic device of any of claims 11-13, wherein the UE is to change from the inactive region of time to the active region of time based on a resource re-selection trigger.

20. The electronic device of any of claims 11-13, wherein the UE is to change from the inactive region of time to the active region of time based on a hybrid automatic repeat request (HARQ) reception trigger.