CN116602019A - New air interface (NR) side link communication - Google Patents
New air interface (NR) side link communication Download PDFInfo
- Publication number
- CN116602019A CN116602019A CN202280008234.3A CN202280008234A CN116602019A CN 116602019 A CN116602019 A CN 116602019A CN 202280008234 A CN202280008234 A CN 202280008234A CN 116602019 A CN116602019 A CN 116602019A
- Authority
- CN
- China
- Prior art keywords
- electronic device
- side link
- factor
- transmission
- resources
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000004891 communication Methods 0.000 title abstract description 71
- 238000000034 method Methods 0.000 claims abstract description 139
- 230000001413 cellular effect Effects 0.000 claims abstract description 8
- 230000005540 biological transmission Effects 0.000 claims description 104
- 238000005259 measurement Methods 0.000 claims description 56
- 230000000737 periodic effect Effects 0.000 claims description 16
- 230000000694 effects Effects 0.000 claims description 14
- 230000004913 activation Effects 0.000 claims description 4
- 230000011664 signaling Effects 0.000 description 30
- 238000012545 processing Methods 0.000 description 29
- 230000006870 function Effects 0.000 description 27
- 238000007726 management method Methods 0.000 description 20
- 230000008569 process Effects 0.000 description 17
- 230000007246 mechanism Effects 0.000 description 13
- 238000013461 design Methods 0.000 description 7
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 6
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 6
- 230000006399 behavior Effects 0.000 description 6
- 238000013135 deep learning Methods 0.000 description 6
- 230000007704 transition Effects 0.000 description 6
- 230000008859 change Effects 0.000 description 5
- 230000001960 triggered effect Effects 0.000 description 5
- 230000006978 adaptation Effects 0.000 description 4
- 238000013475 authorization Methods 0.000 description 4
- 238000001514 detection method Methods 0.000 description 4
- 238000013507 mapping Methods 0.000 description 4
- 230000002093 peripheral effect Effects 0.000 description 4
- 238000001228 spectrum Methods 0.000 description 4
- 101150071746 Pbsn gene Proteins 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 3
- 238000004220 aggregation Methods 0.000 description 3
- 230000006855 networking Effects 0.000 description 3
- 238000012913 prioritisation Methods 0.000 description 3
- 206010062519 Poor quality sleep Diseases 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 239000000969 carrier Substances 0.000 description 2
- 230000010267 cellular communication Effects 0.000 description 2
- 239000003795 chemical substances by application Substances 0.000 description 2
- 230000001427 coherent effect Effects 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000009977 dual effect Effects 0.000 description 2
- 238000001914 filtration Methods 0.000 description 2
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000010187 selection method Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- MJSPPDCIDJQLRE-YUMQZZPRSA-N S-methionyl-L-thiocitrulline Chemical compound CSCC[C@@H](C(S/C(\N)=N/CCC[C@@H](C(O)=O)N)=O)N MJSPPDCIDJQLRE-YUMQZZPRSA-N 0.000 description 1
- 102100040255 Tubulin-specific chaperone C Human genes 0.000 description 1
- 230000003213 activating effect Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000004873 anchoring Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000003139 buffering effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 239000013256 coordination polymer Substances 0.000 description 1
- 230000001351 cycling effect Effects 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000009849 deactivation Effects 0.000 description 1
- 230000007423 decrease Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007274 generation of a signal involved in cell-cell signaling Effects 0.000 description 1
- 230000001976 improved effect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000003278 mimic effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008450 motivation Effects 0.000 description 1
- 230000010287 polarization Effects 0.000 description 1
- 238000004705 quadratic configuration interaction calculation Methods 0.000 description 1
- 230000004622 sleep time Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000008093 supporting effect Effects 0.000 description 1
- 108010093459 tubulin-specific chaperone C Proteins 0.000 description 1
- 230000005641 tunneling Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
- 230000002618 waking effect Effects 0.000 description 1
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
Various embodiments herein provide techniques related to side link communications in fifth generation (5G) (or "new air interface (NR)") cellular networks. Some embodiments may relate to techniques for low power side link communications in 5G networks. Some embodiments may relate to techniques for side link Discontinuous Reception (DRX). Other embodiments may be described and/or claimed.
Description
Cross Reference to Related Applications
The present application claims priority from the following applications: U.S. provisional patent application Ser. No.63/138,200, filed on 1/15 of 2021; and U.S. provisional patent application No.63/138,096 filed on 1 month 15 of 2021.
Technical Field
Various embodiments may relate generally to the field of wireless communications. For example, some embodiments may relate to new air interface (NR) side link communications.
Background
Various embodiments may relate generally to the field of wireless communications.
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. The embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings.
Fig. 1 illustrates an example of Channel Busy Rate (CBR) hysteresis in accordance with various embodiments.
Fig. 2 illustrates an example technique related to low power NR side link communication according to various embodiments.
Fig. 3 illustrates an example technique related to NR side link Discontinuous Reception (DRX) in accordance with various embodiments.
Fig. 4 schematically illustrates a wireless network in accordance with various embodiments.
Fig. 5 schematically illustrates components of a wireless network in accordance with various embodiments.
Fig. 6 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some example embodiments.
Background
Various embodiments may relate generally to the field of wireless communications.
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 the various embodiments. However, it will be apparent to one skilled in the art having the benefit of this 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 this document, the phrases "A or B" and "A/B" mean (A), (B) or (A and B).
Low power NR side link communication
Energy efficiency and low power consumption may be considered as the primary attributes of modern wireless communication system designs. Various power saving mechanisms/functions may be integrated directly into the radio interface protocol. The embodiments described herein include new mechanisms that can be applied to the NR side link air interface.
NR vehicle-to-everything (V2X) side link communication protocols are commonly used for inter-vehicle communication and provide reliable and low latency communication capabilities for mission critical services. However, the legacy 16 th edition (rel.16) NR V2X air interface designed may not be optimized in terms of power consumption, and thus new mechanisms for providing significant power savings may be desired. In particular, for a legacy rel.16nr side link, the receiver can be assumed to be always on and monitor the control channels defined in the system configuration for all system resources. This always-on state may result in a significant amount of processing on the receiver side to support side-link communications.
Embodiments and disclosure herein may relate to power saving mechanisms and may also include techniques for solving problems in handling certain power saving aspects of the physical layer. The implementation of power savings according to embodiments herein may have an impact on the physical layer implementation of the 17 th edition (rel.17) NR V2X design. Further, the reduced power consumption may allow the battery-constrained device to more efficiently participate in NR side chain communications.
The resource selection type may be different for the transmission of the same Transport Block (TB) or for the initial period transmission
After the User Equipment (UE) receives the packet for the side link transmission, it can listen immediately once the resource selection is triggered.
From latency and UE power consumption considerations, it may:
randomly selecting resources (including reserved resources) for initial transmission and all subsequent retransmissions of a TB
Randomly selecting resources for initial transmission and initial resource reservation of TB while subsequent retransmissions with aggregated listening data
Selecting resources for initial transmission of TB, initial reservation indicated in side link control information (SCI) transmission, and subsequent retransmission based on available listening data
Based on partial interception or random resource selection, resources are selected for the first transmission and retransmission of a TB within a semi-persistent procedure (periodic traffic). Thereafter, the UE is expected to perform partial interception and thus may reselect resources for subsequent transmissions within the semi-permanent process (of the same periodic traffic) based on the partial interception knowledge of other transmissions.
In general, all the above options can be considered valid options. The selection of a particular option may depend on conditions such as latency budget, CBR, active power saving mode/feature and resource configuration.
Partial listening interval based on known information
To enable side link communications between different UEs, the UEs may be notified when other UEs with which they want to communicate are active (i.e., if another UE is able to monitor and/or receive a physical side link control channel (PSCCH)). It is contemplated that the allocation of a partial listening window may depend On the packet arrival time at the UE transmitter and whether the UE applies semi-persistent or dynamic resource reservation to side link communications (which may not be known to other UEs), a system-wide (system-wide) mechanism may need to be enabled to acquire instances of time intervals with On-Duration.
The alignment of the full system part listening start time may be preconfigured with a common time offset relative to the System Frame Number (SFN)/Direct Frame Number (DFN) slot 0 such that all UEs receive simultaneously or in a UE specific manner when the start time of On-Duration (e.g., time offset relative to SFN/DFN slot 0) is defined according to the destination UE Identifier (ID) (e.g., layer 1 (L1) or layer 2 (L2) ID) or some higher layer ID (e.g., identifier related to a specific service/application, etc.).
As an alternative to a system-wide configuration of partial listening times, there may be a pre-configuration of listening time offsets associated with a particular group of UEs or UE pair.
This alignment may be different depending on the type of side link propagation (unicast, multicast and broadcast) and what information is available.
● In the case of unicast or multicast, it may be assumed that after discovery, the initial connections/associations between all members are established using broadcast communications at system-wide partial listening intervals. The UE may then negotiate parameters for the minimum partial listening interval where all group members are active. This may define a minimum "on" duration and position. Redefinition of these areas may also be done during communication. It may be necessary to specify associated side chain RRC or Medium Access Control (MAC) Control Element (CE) signaling to configure the partial listening parameters that may be used to derive the actual reception time interval.
Within the network coverage, part of the listening parameters may be configured by the network or default pre-configured values may be used. For scenarios outside of network coverage, the system-wide partial interception parameters may be preconfigured. The system-wide partial interception parameters need to be configured mainly to support autonomous initiation of side link association/connection between UEs.
Congestion control/Open Loop Power Control (OLPC) enhanced based on periodic measurements and other measurements
The UE may be preconfigured with a periodic CBR measurement window having a certain period and duration, which may depend on the specific power saving or listening state of the UE.
The UE may also perform measurements when it wakes up for transmission or partial interception and switch power save modes based on CBR. For example, in some embodiments:
the UE may measure CBR at each configured measurement window and average, for example, the N most recently measured CBR values
■CBR<CBR RANDOM_THR State with random resource selection (no interception)
● If the measured CBR is lower than the pre-configured CBR RANDOM_THR Value, the UE may use random resource selection for power saving
■CBR RANDOM_THR <CBR<CBR PARTIAL_SENSING_THR State with partial interception for resource selection (partial interception)
● If the measured CBR is lower than the pre-configured CBR RANDOM_THR The UE can use partial listening for power saving
■CBR PARTIAL_SENSING_THR <CBR-state with full snoop for resource selection (full snoop)
● The UE may be expected to perform a full listening procedure for resource selection
If the length of the CBR measurement is to be reduced, it may be the case that the transmitter switches frequently between different intervals. To mitigate this effect, a hysteresis effect may be introduced. Such hysteresis effects may be implemented, for example, with a higher threshold for transitioning to another state. An example 100 of this is shown in fig. 1. In this case, there are three possible CBR ranges, 110, 115, and 120. We assume that the system is currently in range 115 due to the measurement in the last time interval. For current CBR measurements to be used to transition to another state, the resulting measurement may be required to be outside the interval given by CBR range 115. It is noted that this range 115 may be larger than the CBR range associated with the current system state in order to accommodate a small amount of noise in the measurement, as 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 prior to the actual side link transmission. For a UE running partial listening in the case of semi-permanent transmission, the following may be possible: CBR measurements are performed across a plurality of partial listening windows corresponding to different transmission periods (which may be configured in the system), and measurements made in the partial listening windows are performed immediately before or during a resource reselection procedure associated with actual side link transmissions. For dynamic resource reservation, multiple partial listening windows may not be available immediately prior to the side chain transmission of a Transport Block (TB), and thus previous CBR measurements and measurements performed during the ongoing partial listening time interval may potentially be used and thus aggregated from the time interval corresponding to the previous transmission of the TB.
In some embodiments, the CBR measurement interval sl-timewindowsizebsr may take only one of two values. These values may be 100ms or 100 slots and thus may require the introduction of additional values for CBR time windows suitable for UEs operating in the partial listening mode. CBR measurements may be performed across multiple partial listening intervals according to the value of the partial listening window.
Another embodiment may incorporate periodic CBR measurement instances. These examples may take the form of a configuration period with a CBR measurement window at a configuration time, or by requiring CBR measurements with a configuration window size to be performed at least once during a predefined period of time.
An alternative method for congestion control, which may be suitable for random resource selection, is to impose a constraint on the maximum amount of resources or CR value in a predefined time interval.
Congestion control/OLPC based on metrics other than CBR
In rel.16, NR SL congestion control and OLPC may be based on CBR measurements. For some cases in future versions, the available measurement period may be less than what is assumed for the design of CBR measurements in the rel.16nr side link. For short periods of time, other parameters may be more suitable as a basis for power control. These parameters may include, for example, the number of occupied physical side link control channel (PSCCH), physical side link shared channel (PSSCH), or physical side link feedback channel (PSFCHO) resources. Alternatively, the parameters may include the number of PSCCH resources for which a demodulation reference signal (DMRS) Reference Signal Received Power (RSRP) exceeds a particular value.
Another option may include guessing congestion control and power control of other devices currently transmitting. For example, from the Modulation Coding Scheme (MCS) used, the current CBR state (depending on the configuration) may be inferred. This may enable a device to mimic the congestion control state of the transmissions it receives. This technique may be appropriate for situations where the device does know that the transmitting other device is using full interception or maximum measurement accuracy.
It is also possible that devices that perform CBR measurements as required by rel.16nr side links indicate their CBR index within side chain control information (SCI). To also enable rel.16 devices, this information may be placed within the SCI in a manner that does not prevent devices implementing only rel.16nr V2X from receiving the PSCCH and associated PSSCH. For partial interception or random resource selection, the device may then select the CBR index signaling from the physically closest UE. The relevant selection criteria may be location, PSCCH RSRP or PSSCH RSRP.
In the event that there is insufficient time to perform accurate measurements, the default CBR index may be configured separately for partial interception and random resource selection. The default value may also be different depending on the priority or the propagation type.
The above solution may be mainly applied when the required CBR measurement cannot be performed. This means that after receiving hybrid automatic repeat request (HARQ) feedback, or other packets are to be sent and there is enough data to accurately estimate CBR, this value can be employed for further retransmissions or subsequent transmissions of other TBs. It may also be noted that the device is required to treat the measured CBR as valid for a (pre) configured amount of time. The amount of time of this (pre) configuration may depend on factors such as priority, interception type, traffic cycle or propagation type.
Soft prioritization of resource selection to facilitate bandwidth/time adaptation for power savings
If bandwidth adaptation is enabled for power saving, it may be desirable to have a mechanism to prioritize the selection of side link resources for transmission from the anchor time/frequency resource set used by a UE operating in a power saving mode with a reduced subset of bandwidth/time resources. The motivation behind such operation may be performance in low/medium congestion situations. In this case, the UE forming the candidate set of resources (e.g., a non-power-save-enabled UE) may be expected to further check whether there are preferred anchor resources and then select those resources for transmission. Such behavior (prioritization of candidate resources) may be triggered only when CBR measurements across system bandwidth or within anchor resources are below a predefined CBR threshold. For example, one or more of the following aspects may be used:
UEs operating in power save mode may configure and use anchor time/frequency resources (e.g., subchannel sets, time slots within side-chain resource pools, etc.) for power save operation
An anchor time/frequency resource (e.g. a set of sub-channels, time slots within a side-chain resource pool, etc.) for power saving operation may be used for transmission/reception of UEs with active power saving features-UEs with inactive power saving features may measure CBR and if the measured CBR is lower than CBR RESOURCE_ADAPT_THR The UE may prefer resources that intersect or belong to the anchor resource for transmission. The UE may use other resources if the amount of anchor resources in the candidate set of resources is insufficient.
CBR measurements may be done based on all resources within a resource or only considering anchor resources.
Different anchor resources may be configured in different geographical areas to achieve soft time/frequency/spatial reuse in the side links, providing power savings and improved performance under low/medium loads.
UE partial listening window
Partial interception is one mechanism that may be used for UE power saving. For NR side link communication, embodiments may include: determining a partial listening window size based on:
1) Type of side link transmission: semi-persistent (completing resource selection and reserving periodic transmissions (including retransmissions) for multiple TBs) or dynamic resource reservation (i.e., completing resource selection for each TB transmission)
2) SCI signaling window duration, e.g., n=32 logical slots
3) Resource selection window size
4) Whether or not it is the first TB transmission of a given resource selection procedure
The duration and start/end positions of the partial listening window have the following dependence on the type of side link transmission:
1) Dynamic reservation
a. Option 1. Partial listening window start time is based on time instance/slot triggered by resource reselection (same or next slot)
b. Option 2. The partial listening window start time is advanced in time by N logical slots (e.g., n=32 and associated with SCI signaling window size) triggered by the resource reselection. The UE may be used if it has periodic traffic with predictable resource reselection times, but the resource pool configuration disables semi-persistent reservation/transmission.
c. For a given dynamic reservation, the partial listening window duration may end at the time slot of the last retransmission of a given TB
d. For a given dynamic reservation, the partial listening window duration may end at the time slot when an ACK signal is received on the PSFCH, or at a subsequent time slot due to PSFCH processing delay
2) Semi-permanent reservation
a. The partial listening window start time (time slot) may be based on the set of configuration periods in the system, the resource reselection trigger, whether it is the first TB (resource reselection) or the subsequent TB of a given semi-persistent resource reservation procedure
i. In the case of the first TB, it starts (triggers) at the time instance/slot of the resource reselection trigger or at a subsequent slot
in the case of a subsequent TB transmission, it starts in advance of the value of the resource reselection trigger time instance/slot max (SCI signalling window size, resource selection window size)
b. The partial listening window duration may depend on the time instance/slot of the last retransmission of a given TB or the time instance of the ACK received for a given TB
Side link Discontinuous Reception (DRX)
In the legacy rel.16nr sidelink design, it may be assumed that the receiver is always on and monitors all system resources defined in the system configuration. This always on state may mean that a large amount of processing is used at the receiving side. Side link DRX may be a solution to save a lot of power. According to various embodiments herein, implementation of side link DRX may affect physical layer implementation of the rel.17nrv2x design. Embodiments may provide reduced power consumption, which may be beneficial for battery-limited devices to participate in NR side link communications. Additionally or alternatively, embodiments may align DRX and partial listening operations for power saving and ensure a proper tradeoff between reliability of transmission and UE power consumption depending on the type of communication and services running on the UE side.
In general, side link DRX may be defined by a DRX cycle, which may include a predefined active time (which may be referred to as a "duration" and may be the time at which the UE monitors side link PSCCH transmissions). The DRX cycle may also include a configurable potential inactivity time associated with transitioning to the inactivity time interval. The inactivity time interval may be when the UE may turn off the RX chain in order to save power and thus not monitor SL transmissions until the next on duration interval. In areas with potential inactivity times, the identification of when a UE should transition to a sleep state may depend on factors such as side link physical layer activity. Due to the different behavior of the side link physical layer, different solutions depending on the communication requirements may be required, as described with reference to the following embodiments.
The power saving mechanism to be defined at the side link physical layer may be or include a resource selection technique based on partial interception. The partial listening operation may allow the UE to monitor the PSCCH/PSSCH and perform listening only in a subset of slots processed to select side link resources for upcoming transmissions.
From the physical layer perspective, for a side-link DRX design that needs to be consistent with random or partial listening mechanisms for resource selection, there may be one or more of the following potential impacts and/or challenges:
1) Supporting side link communication between UEs operating in partial listening mode for side link communication
2) Efficient support of sidelink unicast/multicast/broadcast communications with low UE power consumption
3) Details of UE partial listening behavior for dynamic and semi-persistent resource reservation
a. Triggering of On-Duration time interval for activating side link DRX mechanism
4) Side link HARQ support-maximum number of side link retransmissions, and minimum time between retransmissions or feedback
5) Conditions/triggers for transition to or from On-Duration time interval
6) The dependence of On-Duration time interval On the following parameters: partial listening window duration and time allocation, UE resource selection window duration and time allocation, SCI signaling window duration and time allocation, packet delay budget and HARQ operation, and priority of destination ID (L1/L2) or source ID (L1/L2), side link transmission
7) Side link measurement interval (e.g., CBR measurement)
8) Consideration of non-side-chain subframes
SL DRX cycle trigger condition and length of "On-Duration" time interval
The range of "On-Duration" time intervals may be controlled by a timer, which may be initialized by different values and/or activated by different triggers.
The trigger condition and start time instance of the SL DRX "On-Duration" time interval may be a function of the following parameters: the configured set of periods available for side link transmission, resource reselection trigger time instances, switch time from sleep state (shallow or deep), partial snoop trigger, current time instance (slot), SFN/DFN slot 0, UE destination ID, and/or type of side link communication (e.g., side link transmission with semi-permanent or dynamic resource reservation).
The following embodiments may include examples of how an On-Duration timer may be initialized for different trigger conditions (wake-up trigger sets).
Side link part interception trigger
In the case of only partial snoop operations, the On-Duration timer may be initialized by a Duration that may be a function of one or more of:
1) Resource selection window size (determined by UE) (e.g., for semi-persistent reservation)
2) Configured partial listening window size
3) Packet delay budget
4) SCI signaling window duration
5) T2min values defined by the relevant 3GPP specifications
6) Values configured by side link RRC/MAC CE signaling during UE negotiation
7) One or more of the above components plus a switch/transition time from a sleep state (e.g., a light sleep state or a deep sleep state)
Side link part interception and resource reselection triggering
In the case where the partial listening process is followed by a resource selection process, the On-Duration timer may be initialized by or based On one or more of the following:
1) Total partial listening window duration and resource selection window duration
2) Configured partial listening window size
3) Resource selection window duration only
4) Packet delay budget for processed packets
5) SCI signaling window duration
6) Specification defined T2min values
7) Values configured by side link RRC/MAC CE signaling during UE negotiation
Resource reselection or preemption (pre-emption) check trigger
In the case of a resource reselection procedure or preemption check, the On-Duration timer may be initialized according to one or more of the following parameters:
1) Resource selection window size (determined by UE) (e.g., for semi-persistent reservation) or remaining resource selection window
2) Configured partial listening window size or minimum partial listening window
3) Packet delay budget or residual packet delay budget
4) SCI signaling window duration
5) Specification defined T2min values
6) Values configured by side link RRC/MAC CE signaling during UE negotiation
7) Or one or more of the above components plus a function of the switching time from a sleep state (e.g., light sleep state or deep sleep state)
Side link measurement triggers (e.g., CBR)
In some embodiments, if the UE is expected to perform CBR measurements that are not aligned with part of the listening window, it may activate a separate On-Duration time interval.
PSFCH reception trigger
For example, if the UE wants to transmit with random resource selection and HARQ feedback request enabled, it may need to turn On the reception process and activate the On-Duration interval.
The specific values used to initialize the On-Duration timer may be determined according to one or more of the following configuration settings (function parameters):
1) The set of periods configured for side link transmission,
2) The resource reselection triggers a time instance (e.g., symbol/slot/subframe/frame index),
3) Partial snoop 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) Types of side link communication (e.g., side link transmission with semi-persistent or dynamic resource reservation)
8) Power saving/consumption state
9) Preconfigured On-Duration timer settings
Side link DRX cycle configuration dependency
Depending on whether the traffic is periodic or aperiodic, different solutions related to side link DRX may be required. Specifically:
● Periodic traffic: in this case, the transmission may have a period in time. The period may mean that the DRX cycle may be adapted to the set of configured period values. The start time of the active time may be required to ensure that the required listening and measurement procedures can be performed before the side link transmission. A minimum activity duration may be required to ensure that all potential retransmissions can be handled without the UE transitioning to an inactive state. The Packet Delay Budget (PDB) may be known prior to waking up, so the minimum DRX on duration may be planned accordingly.
● Aperiodic traffic: for aperiodic traffic, the packet arrival time at the higher layer may not be predictable. However, in some cases, the delay budget for all potential traffic may be available. Because the device can know how long it will wake up (e.g., if a packet arrives at a higher layer), it can plan the SL DRX cycle accordingly. This may also mean that if a device can continuously expect high priority traffic with very short PDBs, it may not be suitable to transition to an inactive state at all. For other types of potential PDBs, a lighter sleep time may be sufficient. These times may also depend on the configured resource reservation scheme. These schemes may be different depending on the PDB, priority, or other parameters of the communication.
The overall side link DRX UE behavior for the side links may be considered as multiple side link DRX cycles running in parallel (e.g., a full system side link DRX cycle, a side link DRX cycle for dynamic or semi-persistent resource reservation based on partial listening resource selection, a side link DRX cycle for random resource selection, and/or different side link DRX cycles for different unicast/multicast connections). Alternatively, the functionality of multiple DRX cycles may be integrated into a single side link DRX cycle design. Another possible option may be to decouple the partial snoop operation from the side link DRX cycle operation. In this case, the side link DRX behavior may depend only on traffic.
SL DRX implementation of inactivity timer
In some embodiments, the side chain HARQ ACK may serve as a trigger for the inactivity timer. The side link HARQ NACK may be used to reset the inactivity timer.
An inactivity timer may be required to address different events related to the DL DRX inactivity timer. The inactivity timer or the event it solves may depend on or be related to one or more of the following conditions:
● Priority broadcast: since some devices may only be interested in higher priority messages for broadcasting, the inactivity timer may be configured not to reset if a lower priority broadcast message is received. In some embodiments, the inactivity timer may be configured to not consider broadcast transmissions at all.
● Propagation type: the inactivity timer may be configured to consider only certain propagation type transmissions.
● Power saving state/battery state: the configuration of the inactivity timer may also vary depending on the battery state of the device. In some embodiments, the priority of the transmission for resetting the timer may increase as the battery state decreases.
● Communication context: in the case of unicast or multicast messages, these messages may trigger a response to a request. Thus, the device may not be allowed to go to sleep until the response is sent and received correctly.
Long and short SL DRX cycles
During DRX associated with the UU interface, the configuration may be split between long DRX and short DRX. Short DRX can be used for small time scale variations. An example of such a time scale may be decoding a Physical Downlink Control Channel (PDCCH) only every 3 rd slot. In embodiments where side link DRX is used, such small scale variations may not be possible, as the actual allocation of resources may not be known. Thus, the above considerations can be applied generally to "long" side link DRX. However, for unicast and multicast with side link DRX, a short side link DRX cycle may also be introduced. In this case, only a subset of the available time slots may be used within the On-Duration. However, such cycling may result in restrictions on resource selection.
Fig. 2 depicts an example technique 200 related to low power NR side link communication according to various embodiments. The technique 200 may be performed by one or more processors of an electronic device, such as a User Equipment (UE) in an NR cellular network.
Technique 200 may include: at 205, the UE identifies a first one or more resources to be used for an initial NR side chain transmission based on a first factor related to random resource selection or partial interception by other devices within the vicinity of the UE. Technique 200 may also include: at 210, the ue reserves the identified first one or more resources for initial NR side chain transmission based on a first factor. Technique 200 may also include: at 215, the ue sends an initial NR side chain transmission on the identified first one or more resources. In some embodiments, one or more processors may facilitate the transmission of an initial NR side link transmission at 215. Facilitating the sending may include: the data related to the transmission is provided to one or more other processors or systems of the UE (e.g., radio Frequency (RF) circuitry or antenna circuitry of the UE) for transmission.
It should be understood that this technique is intended as one example technique according to embodiments herein, and that 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.
Fig. 3 illustrates an example technique 300 related to NR side link 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: at 305, parameters of a Discontinuous Reception (DRX) procedure to be used by the UE for NR side link data are identified, wherein the parameters include an active time region where the UE is to monitor NR side link data and an inactive time region where the UE is not to monitor NR side link data. The technique 300 may further include: at 310, a DRX procedure is performed for NR side link data.
It should be understood that this technique is intended as one example technique according to embodiments herein, and that 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.
System and implementation
Fig. 4-6 illustrate various systems, devices, and components that may implement aspects of the disclosed embodiments.
Fig. 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 thereto, and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems, and the like.
The network 400 may include a UE 402, and the UE 402 may include any mobile or non-mobile computing device designed to communicate with a RAN 404 via an over-the-air connection. UE 402 may be communicatively coupled with RAN 404 over a Uu interface. The UE 402 may be, but is not limited to, a smart phone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment device, in-vehicle entertainment device, instrument cluster, head mounted display device, in-vehicle diagnostic device, dashboard mobile device, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networking appliance, machine type communication device, M2M or D2D device, ioT device, etc.
In some embodiments, the network 400 may include multiple UEs directly coupled to each other via a side link interface. The UE may be an M2M/D2D device that communicates using a physical side link channel (e.g., without limitation, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.).
In some embodiments, the UE 402 may additionally communicate with the AP 406 via an over-the-air connection. The AP 406 may manage WLAN connections that may be used to offload some/all network traffic from the RAN 404. The connection between the UE 402 and the AP 406 may conform to any IEEE 802.11 protocol, where the AP 406 may be wireless fidelity And a router. In some embodiments, the UE 402, RAN 404, and AP 406 may utilize cellular-WLAN aggregation (e.g., LWA/LWIP). cellular-WLAN aggregation may involve UE 402 being configured by RAN 404 to utilize both cellular radio resources and WLAN resources.
RAN 404 may include one or more access nodes, such as AN 408.AN 408 may terminate the air interface protocol for UE 402 by providing access stratum protocols, including RRC, PDCP, RLC, MAC and L1 protocols. In this way, the AN 408 may enable a data/voice connection between the CN 420 and the UE 402. In some embodiments, AN 408 may be implemented in a separate device or as one or more software entities running on a server computer as part of, for example, a virtual network (which may be referred to as a CRAN or virtual baseband unit pool). AN 408 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, nodeB, RSU, TRxP, TRP, etc. AN 408 may be a macrocell base station or a low power base station for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth than a macrocell.
In embodiments where the RAN 404 includes multiple ANs, they may be coupled to each other 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 interface (which may be separated into control/user plane interfaces in some embodiments) may allow the AN to communicate information related to handoff, data/context transfer, mobility, load management, interference coordination, etc.
The ANs of the RAN 404 may each manage one or more cells, groups of cells, component carriers, etc. to provide the air interface for network access to the UE 402. The UE 402 may be simultaneously connected with multiple cells provided by the same or different ANs of the RAN 404. For example, the UE 402 and the RAN 404 may use carrier aggregation to allow the UE 402 to connect with multiple component carriers, each component carrier corresponding to a Pcell or Scell. In a dual connectivity scenario, the first AN may be a primary node providing AN MCG and the second AN may be a secondary node providing AN SCG. The first/second AN may be any combination of eNB, gNB, ng-enbs, etc.
RAN 404 may provide the air interface over licensed spectrum or unlicensed spectrum. To operate in unlicensed spectrum, a node may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCell/Scell. Prior to accessing the unlicensed spectrum, the node may perform medium/carrier sense operations based on, for example, a Listen Before Talk (LBT) protocol.
In a V2X scenario, the UE 402 or AN 408 may be or act as AN RSU, which may refer to any traffic infrastructure entity for V2X communications. The RSU may be implemented in or by a suitable AN or a fixed (or relatively fixed) UE. An RSU implemented in or by: for a UE, it may be referred to as a "UE-type RSU"; for enbs, it may be referred to as "eNB-type RSUs"; for gNB, it may be referred to as "gNB-type RSU"; etc. In one example, the RSU is a computing device coupled with radio frequency circuitry located at the roadside that provides connection support to the passing vehicle UE. The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications/software for listening to and controlling the traffic of traveling vehicles and pedestrians. The RSU may provide very low latency communications required for high speed events (e.g., collision avoidance, traffic alerts, etc.). Additionally or alternatively, the RSU may provide other cellular/WLAN communication services. The components of the RSU may be enclosed in a weather-proof enclosure suitable for outdoor installation, and may include a network interface controller for providing a wired connection (e.g., ethernet) to a traffic signal controller or backhaul network.
In some embodiments, the RAN 404 may be an LTE RAN 410 with an eNB (e.g., eNB 412). The LTE RAN 410 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; a CP-OFDM waveform for DL and an SC-FDMA waveform for UL; turbo codes for data and TBCCs 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 operate on the sub-6GHz band.
In some embodiments, RAN 404 may be NG-RAN 414 with a gNB (e.g., gNB 416) or a NG-eNB (e.g., NG-eNB 418). The gNB 416 may connect with 5G enabled UEs using a 5G NR interface. The gNB 416 may connect with the 5G core through a NG interface, which may include an N2 interface or an N3 interface. The NG-eNB 418 may also connect with the 5G core over the NG interface, but may connect with the UE via the LTE air interface. The gNB 416 and the ng-eNB 418 may be connected to each other via an Xn interface.
In some embodiments, the NG interface may be split into two parts: a NG user plane (NG-U) interface that carries traffic data (e.g., an N3 interface) between nodes of NG-RAN 414 and UPF 448; and a NG control plane (NG-C) interface, which is a signaling interface (e.g., an N2 interface) between the node of NG-RAN 414 and AMF 444.
NG-RAN 414 may provide a 5G-NR air interface having the following characteristics: a variable SCS; CP-OFDM for DL, CP-OFDM for UL, and DFT-s-OFDM; polarization codes for control, repetition codes, simplex codes, and Reed-Muller codes, and LDPC codes for data. Similar to the LTE air interface, the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS. The 5G-NR air interface may not use CRS but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signals for time tracking. The 5G-NR air interface may operate on an FR1 band including a sub-6GHz band or an FR2 band including a frequency band from 24.25GHz to 52.6 GHz. The 5G-NR air interface may comprise an SSB, which is an area of the downlink resource grid comprising PSS/SSS/PBCH.
In some embodiments, the 5G-NR air interface may utilize BWP for various purposes. For example, BWP may be used for dynamic adaptation of SCS. For example, the UE 402 may be configured with multiple BWP, where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 402, the SCS of the transmission also changes. Another example of use of BWP relates to power saving. In particular, the UE 402 may be configured with multiple BWPs having different amounts of frequency resources (e.g., PRBs) to support data transmission in different traffic load scenarios. BWP containing a smaller number of PRBs may 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. BWP containing a larger number of PRBs may be used for scenarios with higher traffic load.
The RAN 404 is communicatively coupled to a CN 420, the CN 420 including network elements for providing various functions to support data and telecommunications services for clients/subscribers (e.g., users of the UE 402). The components of CN 420 may be implemented in one physical node or in a separate physical node. In some embodiments, NFV may be used to virtualize any or all of the functionality provided by the network elements of CN 420 onto physical computing/storage resources in servers, switches, etc. The logical instantiation of the CN 420 may be referred to as a network slice, while the logical instantiation of a portion of the CN 420 may be referred to as a network sub-slice.
In some embodiments, CN 420 may be LTE CN 422 (which may also be referred to as EPC). LTE CN 422 may include MME 424, SGW 426, SGSN 428, HSS 430, PGW 432, and PCRF 434, which are coupled to each other through interfaces (or "reference points") as shown. The function of the elements of LTE CN 422 may be briefly described as follows.
MME 424 may implement mobility management functions to track the current location of UE 402 to facilitate paging, bearer activation/deactivation, handover, gateway selection, authentication, and the like.
SGW 426 may terminate the S1 interface towards the RAN and route data packets between the RAN and LTE CN 422. The SGW 426 may be a local mobility anchor for inter-RAN node handover and may also provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful interception, billing and some policy enforcement.
The SGSN 428 may track the location of the UE 402 and perform security functions and access control. Furthermore, SGSN 428 may perform EPC inter-node signaling for mobility between different RAT networks; MME 424 specified PDN and S-GW selection; MME selection for handover; etc. The S3 reference point between MME 424 and SGSN 428 may enable user and bearer information exchange for inter-3 GPP network mobility in the idle/active state.
HSS 430 may include a database for network users (including subscription related information) to support the handling of communication sessions by network entities. HSS 430 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, and the like. The S6a reference point between HSS 430 and MME 424 may enable the transfer of subscription and authentication data for authenticating/authorizing a user to access LTE CN 420.
PGW 432 may terminate the SGi interface towards a Data Network (DN) 436 that may include an application/content server 438. PGW 432 may route data packets between LTE CN 422 and data network 436. PGW 432 may be coupled to SGW 426 via an S5 reference point to facilitate user plane tunneling and tunnel management. PGW 432 may also include nodes (e.g., PCEFs) for policy enforcement and charging data collection. Further, the SGi reference point between PGW 432 and data network 436 may be an operator external public, private PDN, or an operator internal packet data network (e.g., for provisioning IMS services). PGW 432 may be coupled with PCRF 434 via a Gx reference point.
PCRF 434 is a policy and charging control element of LTE CN 422. PCRF 434 may be communicatively coupled to application/content server 438 to determine appropriate QoS and charging parameters for the service flows. PCRF 432 may assign the associated rules to the PCEF with the appropriate TFTs and QCIs (via Gx reference points).
In some embodiments, CN 420 may be 5gc 440. The 5gc 440 may include AUSF 442, AMF 444, SMF 446, UPF 448, NSSF 450, NEF 452, NRF 454, PCF 456, UDM 458, and AF 460, which are coupled to each other through interfaces (or "reference points") as shown. The function of the elements of the 5gc 440 may be briefly described as follows.
AUSF 442 may store data for authentication of UE 402 and process authentication related functions. AUSF 442 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5gc 440 through a reference point as shown, the AUSF 442 may also present an interface based on the Nausf service.
AMF 444 may allow other functions of 5gc 440 to communicate with UE 402 and RAN 404 and subscribe to notifications about mobility events for UE 402. The AMF 444 may be responsible for registration management (e.g., for registering the 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 for transmission of SMS messages between UE 402 and SMSF. The AMF 444 may interact with the AUSF 442 and the UE 402 to perform various security anchoring and context management functions. Furthermore, the AMF 444 may be an end point of the 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 the termination point of NAS (N1) signaling and perform NAS ciphering and integrity protection. The AMF 444 may also support NAS signaling with the UE 402 over the N3IWF interface.
The SMF 446 may be responsible for SM (e.g., session establishment, tunnel management between UPF 448 and AN 408); UE IP address allocation and management (including optional authorization); selection and control of the UP function; configuring the traffic steering at the UPF 448 to route the traffic to the correct destination; terminating the interface towards the policy control function; control policy enforcement, charging, and a portion of QoS; lawful interception (for SM events and interfaces to LI systems); terminating the SM portion of the NAS message; downlink data notification; initiate AN specific SM information sent to AN 408 over N2 via AMF 444; and determining the SSC mode of the session. SM may refer to the management of PDU sessions, and PDU sessions or "sessions" may refer to PDU connectivity services that provide or enable the exchange of PDUs between UE 402 and data network 436.
The UPF 448 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 436, and a branching point to support multi-homing PDU sessions. The UPF 448 may also perform packet routing and forwarding, perform packet inspection, implement policy rules user plane parts, lawful interception packets (UP collection), perform traffic usage reporting, perform QoS processing for the 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. The UPF 448 may include an uplink classifier to support routing traffic flows to a data network.
NSSF 450 may select a set of network slice instances to serve UE 402. NSSF 450 may also determine allowed NSSAIs and mappings to subscribed S-NSSAIs (if needed). NSSF 450 may also determine a set of AMFs or a list of candidate AMFs to use for serving UE 402 based on a suitable configuration and possibly by querying NRF 454. The selection of a set of network slice instances for the UE 402 may be triggered by the AMF 444 registered by the UE 402 by interacting with the NSSF 450, which may result in a change in AMF. NSSF 450 may interact with AMF 444 via an N22 reference point; and may communicate with another NSSF in the visited network via an N31 reference point (not shown). In addition, NSSF 450 may expose an interface based on the Nnssf service.
NEF 452 may securely open services and capabilities provided by 3GPP network functions for third parties, internal openness/reopening, AF (e.g., AF 460), edge computing or fog computing systems, and the like. In such embodiments, NEF 452 may authenticate, authorize or restrict AF. NEF 452 may also convert information exchanged with AF 460 and with internal network functions. For example, NEF 452 may translate between AF service identifiers and internal 5GC information. The NEF 452 may also receive information from other NFs based on their ability to open. This information may be stored as structured data at NEF 452 or at data store NF using a standardized interface. The stored information may then be re-opened by NEF 452 to other NFs and AFs, or for other purposes (e.g., analysis). Furthermore, NEF 452 may expose an interface based on Nnef services.
NRF 454 may support a service discovery function, receive NF discovery requests from NF instances, and provide information of the discovered NF instances to the NF instances. NRF 454 also maintains information of available NF instances and services supported by them. As used herein, the terms "instantiation," "instantiation," and the like may refer to the creation of an instance, while "instance" may refer to a specific occurrence of an object, which may occur, for example, during program code execution. Further, NRF 454 may expose an interface based on Nnrf services.
PCF 456 may provide policy rules to control plane functions to implement them and may also support a unified policy framework to manage network behavior. PCF 456 may also implement a front end to access subscription information related to policy decisions in the UDR of UDM 458. In addition to communicating with functions through reference points as shown, PCF 456 also presents an interface based on the Npcf service.
The UDM 458 may process subscription related information to support the processing of communication sessions by network entities and may store subscription data for the UE 402. For example, subscription data may be communicated via an N8 reference point between the UDM 458 and the AMF 444. UDM 458 may include two parts: application front-end and UDR. The UDR may store subscription data and policy data for UDM 458 and PCF 456, and/or structured data for open and application data for NEF 452 (including PFD for application detection, application request information for multiple UEs 402). The Nudr service-based interface may be exposed by UDR 221 to allow UDM 458, PCF 456, and NEF 452 to access a particular set of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of related data changes in UDR. The UDM may include a UDM-FE that is responsible for handling credentials, location management, subscription management, etc. 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 processing, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, the UDM 458 may also expose Nudm service-based interfaces.
AF 460 may provide application impact on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.
In some embodiments, the 5gc 440 may enable edge computation by selecting an operator/third party service to be geographically close to the point where the UE 402 attaches to the network. This may reduce latency and load on the network. To provide edge computing implementations, the 5gc 440 may select the UPF 448 in close proximity to the UE 402 and perform traffic steering from the UPF 448 to the data network 436 via the N6 interface. This may be based on the UE subscription data, the UE location, and the information provided by AF 460. In this way, AF 460 may affect UPF (re) selection and traffic routing. Based on the operator deployment, the network operator may allow the AF 460 to interact directly with the relevant NF when the AF 460 is considered a trusted entity. In addition, AF 460 may expose an interface based on Naf services.
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, the application/content server 438.
Fig. 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 504. The UE 502 and the AN 504 may be similar to, and substantially interchangeable with, similarly named components described elsewhere herein.
The UE 502 may be communicatively coupled with the AN 504 via a connection 506. Connection 506 is shown as implementing a communicatively coupled air interface and may conform to a cellular communication protocol, such as the LTE protocol or the 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. Host platform 508 may include application processing circuitry 512, and application processing circuitry 512 may be coupled with protocol processing circuitry 514 of modem platform 510. Application processing circuitry 512 may run various applications for outgoing/incoming application data for UE 502. The application processing circuitry 512 may also implement one or more layer operations to send and receive application data to and from the data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.
Protocol processing circuitry 514 may implement one or more layers of operations to facilitate sending or receiving data over connection 506. Layer operations implemented by the protocol processing circuit 514 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
Modem platform 510 may also include digital baseband circuitry 516, digital baseband circuitry 516 may implement one or more layer operations that are "lower" layer operations in the network protocol stack performed by protocol processing circuitry 514. These operations may include, for example, PHY operations, including one or more of the following: HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/demapping, 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 space coding), reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.
Modem platform 510 may also include transmit circuitry 518, receive circuitry 520, RF circuitry 522, and RF front end (RFFE) 524, which may include or be connected to one or more antenna panels 526. Briefly, the transmit circuit 518 may include digital-to-analog converters, mixers, intermediate Frequency (IF) components, and the like; the receive circuitry 520 may include analog-to-digital converters, mixers, IF components, etc.; RF circuitry 522 may include low noise amplifiers, power tracking components, and the like; RFFE 524 may include filters (e.g., surface/bulk acoustic wave filters), switches, antenna tuners, beam forming components (e.g., phased array antenna components), and so forth. The selection and arrangement of the components of the transmit circuit 518, receive circuit 520, RF circuit 522, RFFE 524, and antenna panel 526 (commonly referred to as "transmit/receive components") may be specific to the specifics of the particular implementation, such as whether the communication is TDM or FDM, frequency at mmWave or sub-6GHz, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be provided in the same or different chips/modules, etc.
In some embodiments, protocol processing circuitry 514 may include one or more instances of control circuitry (not shown) for providing control functions for the transmit/receive components.
UE reception may be established by and via antenna panel 526, RFFE 524, RF circuitry 522, receive circuitry 520, digital baseband circuitry 516, and protocol processing circuitry 514. In some embodiments, the antenna panel 526 may receive transmissions from the AN 504 via receive beamformed signals received by multiple antennas/antenna elements of one or more antenna panels 526.
UE transmissions may be established by and through protocol processing circuitry 514, digital baseband circuitry 516, transmit circuitry 518, RF circuitry 522, RFFE 524, and antenna panel 526. In some embodiments, the transmit component of the UE 504 may apply spatial filtering to the data to be transmitted to form a transmit beam that is transmitted by the antenna elements of the antenna panel 526.
Similar to the UE 502, the an 504 may include a host platform 528 coupled with a modem platform 530. Host platform 528 may include application processing circuitry 532 coupled with protocol processing circuitry 534 of modem platform 530. The modem platform may also include digital baseband circuitry 536, transmit circuitry 538, receive circuitry 540, RF circuitry 542, RFFE circuitry 544, and antenna panel 546. The components of the AN 504 may be similar to, and substantially interchangeable with, similarly 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 logic functions including, for example, RNC functions (e.g., radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling).
Fig. 6 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some example embodiments. In particular, FIG. 6 shows a graphical representation of a hardware resource 600, the hardware resource 600 comprising 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 that utilize node virtualization (e.g., NFV), the hypervisor 602 can be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 600.
The processor 610 may include, for example, a processor 612 and a processor 614. The processor 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 (e.g., baseband processor), an ASIC, an FPGA, a Radio Frequency Integrated Circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
Memory/storage 620 may include main memory, disk storage, or any suitable combination thereof. Memory/storage 620 may include, but is not limited to, any type of volatile, nonvolatile, 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 memory, and the like.
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 the network 608. For example, the communication resources 630 may include wired communication components (e.g., for use via USB, for exampleEthernet, etc.), cellular communication component, NFC component,(or->) Assembly, & gtof>Components and other communication components.
The instructions 650 may include software, programs, applications, applets, apps, or other executable code for causing at least any of the processors 610 to perform any one or more of the methods discussed herein. The instructions 650 may reside, completely or partially, within at least one of the processor 610 (e.g., within a cache memory of the processor), the memory/storage 620, or any suitable combination thereof. Further, any portion of instructions 650 may be transferred from any combination of peripherals 604 or databases 606 to hardware resource 600. Thus, the memory of the processor 610, the memory/storage 620, the peripherals 604 and the database 606 are examples of computer readable and machine readable media.
For one or more embodiments, at least one component set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, procedures, and/or methods set forth in the following examples section. For example, the baseband circuitry described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more examples set forth below. As another example, circuitry associated with a UE, base station, network element, etc., 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 in the examples section below.
Example
Example 1 may include an NR SL resource selection scheme, wherein an initial transmission including a resource reservation is based on random resource selection and a subsequent transmission is based on full listening.
Example 2 may include an NR SL resource selection scheme, wherein an initial transmission including a resource reservation is based on partial interception and a subsequent transmission is based on full interception.
Example 3 may include an NR SL resource selection scheme, wherein an initial transmission including a resource reservation is based on random resource selection and a subsequent transmission is based on partial interception.
Example 4 may include the resource selection scheme of examples 1, 2, or 3, or some other example herein, wherein the initial transmission is also for semi-persistent resource reservation.
Example 5 may include the resource selection scheme of example 1, 2, or 3, or some other example herein, wherein the use of different schemes is indicated in the control information.
Example 6 may include the resource selection schemes of examples 1, 2, 3, or some other example herein, wherein the selection of the different schemes depends on:
a. power delay budget
b. Power saving mode activation
c. Device characteristic configuration
d. Any combination of the above
Example 7 may include a partial resource listening process in which the activity time of each device is known by other devices to enable communication
The process of a.7 wherein full system partial snoop cycle alignment is achieved
The procedure in i.7a utilizes common configuration as offset in terms of SFN/DFN and duration
ii.7a, wherein the device specific activity duration is defined based on the UEID or a higher layer ID, possibly depending on the service or application
The procedure in 7a uses signalling over the Uu interface when within network coverage
b.7, wherein only certain groups of devices are aligned over their partial listening cycles
c.7a or 7b, wherein the alignment is different depending on the propagation type (unicast, multicast or broadcast)
d.7a or 7b, wherein the alignment for unicast multicast is signaled
The procedure in iv.7d uses the SL interface for signalling
The procedure in v.7d uses Uu interface for signaling
The process in vi.7d signals a change in alignment during active communication over SL.
Example 8 may include congestion control and open loop power control based on periodic CBR measurements
The method of a.8, wherein the measurement window is (pre) configured
b.8, wherein the measurement window is configured via a network
c.8, wherein the measurement only needs to be performed when no current measurement is available at the end of the required window
d.8, wherein 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, wherein the resulting CBR measurements are also dependent on previous measurements taking into account
a. Measuring window length
b. The time elapsed since the last measurement.
Example 10 may include a congestion control mechanism for a device based on the following selection or partial interception using random resources:
a. CBR measurement taking into account non-consecutive amount of time slots
b. CBR measurement for past transmissions of semi-permanent transmissions
c. CBR measurement based on reduced window size
d. Combination of CBR measurements in the past.
Example 11 may include a congestion control mechanism for devices that is not based on CBR measurements, but rather based on the following selection or partial interception with random resources:
a. allocation of control channels for other devices within a pre-transmission window
b. Allocation of feedback channels for other devices within a pre-transmission window
c.PSCCH DMRS RSRP
d. Deriving CBR index from transmissions of nearby devices
e. CBR index using indication in control information (SCI) of physically close devices
f. Default CBR index (pre) configured according to propagation type and interception type
g. Switching between the above-described cases and CBR measurements based on their availability.
Example 12 may include a soft prioritization scheme for resource selection to facilitate bandwidth/time adaptation for power saving.
Example 13 may include a UE partial listening window depending on:
a. types of side-link transmission, e.g. semi-persistent or dynamic resource reservation
SCI resource signaling window duration
c. Resource selection window size
d. Whether it is the first transmission of the resource selection procedure.
Example 14 may include that the duration and start/end position of the partial listening window depend on the following UE partial listening procedure:
a. dynamic reservation in which
Time instance with partial listening window start time based on resource reselection trigger
viii partial listening window start time advance of future predictable resource reselection triggers
Part of the listening window ends at time slot x. part of the last retransmission of a given TB ends when an ACK or no NACK is received (in case of NACK feedback only)
b. Semi-permanent reservation in which
Part of the listening window start time is based on a set of configured periodicity and resource reselection triggers, and
1. for the case where it is the first transmission of a semi-persistent resource reservation, it begins with a resource reselection trigger
2. For the case where it is not the first transmission, it starts before a known resource reselection trigger (known by the period)
The partial listening window duration depends on the time of the last possible retransmission of a given TB, or the time of ACK received, or the time of NACK not received (for NACK-only feedback).
Example 15 is a method, comprising:
receiving, by the UE, a signal comprising an indication of a packet for side chain transmission;
determining, by the UE, resources for initial transmission of the transport block based on the latency and power consumption of the UE;
determining, by the UE, a transport block; and
the transport block is transmitted by the UE using the determined resources.
Example 16 may include the method of example 15 or any other example herein, wherein determining the resource further comprises: resources are randomly selected.
Example 17 may include the method of example 15 or any other example herein, wherein determining the resource further comprises: the aggregate snoop data is used to randomly select resources for subsequent transmission.
Example 18 may include the method of example 15 or any other example herein, wherein determining the resource further comprises: resources that use the snoop data to determine the initial resource reservation are determined.
AD4697
Example 1 may include a SL DRX procedure to enable device power saving.
Example 2 may include the SL DRX procedure of example 1 or some other example herein, wherein the SL DRX cycle includes an active region and a potentially inactive region.
Example 3 may include the SL DRX procedure of example 1 or some other example herein, wherein the SL DRX active region and the inactive region depend on requirements for physical layer communication requirements.
Example 4 may include the SL DRX procedure of example 1 or some other example herein, wherein the active time of each device is known by other devices to enable communication
e.4, wherein a system-wide SL DRX cycle alignment is achieved
The procedure in i.4a utilizes common configuration as offset in terms of SFN/DFN and duration
The procedure in 4a, wherein the device specific activity duration is defined based on the UEID or a higher layer ID, possibly depending on the service or application
The procedure in 4a uses signalling over the Uu interface when within network coverage
f.4, wherein only certain groups of devices are aligned in their SL DRX cycle
The procedure in g.4a or 4b, wherein the alignment is different according to the propagation type (unicast, multicast or broadcast)
The procedure in h.4a or 4b, wherein signaling the procedure in aligned i.4d for unicast multicast uses the SL interface for signaling
The procedure in ii.4d uses Uu interface for signaling
The procedure in 4d signals a change in alignment during active communication over SL
Example 5 may include the SL DRX procedure of example 1 or some other example herein, wherein the trigger to transition to the active state is based on
a. SL communication period for periodic traffic
b. Resource reselection trigger time instance
c. Preemptive check time instance
d. Partial interception trigger
e. Time instances based on other alignment procedures
f.UE destination or Source ID
g. Type of side link communication
h. Required SL measurement trigger
HARQ reception trigger
j. Any combination of the above
Example 6 may include the trigger of example 5 or some other example herein, wherein the resulting length of activity duration after the partial snoop trigger is based on
a. Resource selection window size
b. Configured partial listening window size
c. Packet delay budget
SCI signaling window duration
e. T2min values defined in the specification
f. Values configured by side link RRC/MAC CE signaling during UE negotiation
g. Values of (pre) configuration in resource pool configuration
h. Any combination of the above, including the device knowing the time to switch between active and inactive states, and vice versa
Example 7 may include the trigger of example 5 or some other example herein, wherein the resulting length of activity duration after the partial listening and resource reselection trigger is based on
a. Total partial listening window duration and resource selection window duration
b. Configured partial listening window size
c. Resource selection window duration
d. Packet delay budget
SCI signaling window duration
f. T2min values defined in the specification
g. Values configured by side link RRC/MAC CE signaling during UE negotiation
h. Values of (pre) configuration in resource pool configuration
i. Any combination of the above, including the device knowing the time to switch between active and inactive states, and vice versa
Example 8 may include the trigger of example 5 or some other example herein, wherein the resulting length of activity duration after the resource reselection or preemption check trigger is based on
a. Total partial listening window duration and resource selection window duration
b. Configured partial listening window size
c. Resource selection window duration
d. Packet delay budget
SCI signaling window duration
f. T2min values defined in the specification
g. Values configured by side link RRC/MAC CE signaling during UE negotiation
h. Values of (pre) configuration in resource pool configuration
i. Any combination of the above, including the device knowing the time to switch between active and inactive states, and vice versa
Example 9 may include the trigger of example 5 or some other example herein, wherein the resulting length of activity duration after HARQ reception of the trigger is based on
a. Configured periodic set for side link transmission
b. Resource reselection trigger time instances (e.g., symbol/slot/subframe/frame index)
c. Partial snoop trigger time instance (e.g., symbol/slot/subframe/frame index)
d. Partial snoop trigger time instance (e.g., symbol/slot/subframe/frame index)
e. Current time instance (e.g., symbol/slot/subframe/frame index)
SFN/DFN slot time instance
Ue destination/source ID
h. Types of side link communication (e.g., side link transmission with semi-persistent or dynamic resource reservation)
i. Power saving/consumption state
j. Preconfigured On-Duration time settings
k. Any combination of the above, including the device knowing the time to switch between active and inactive states, and vice versa
Example 10 may include the SL DRX procedure of example 1 or some other example herein, wherein the configuration of the cycle is dependent on expected periodic or aperiodic traffic
The procedure in l.10, wherein the location and duration of the active time ensures all requirements of the periodic communication in terms of power delay budget, measurement, listening procedure and (preemptive) occupancy check and potential HARQ feedback
m.10 where the location and duration of the active time in case of aperiodic traffic ensures that all potential requirements of the communication are met
Example 11 may include the SL DRX procedure of example 1 or some other example herein, wherein the SL DRX for different communication instances of the SL in the same device is treated as a standalone SL DRX procedure
Example 12 may include the SL DRX procedure of example 1 or some other example herein, wherein the SL DRX for different communication instances of the SL in the same device are combined to form a single SL DRX procedure
Example 13 may include the SL DRX procedure of example 1 or some other example herein, wherein the implementation of the inactivity timer is based on
SL HARQ ACK triggering inactivity timer
b.SL HARQ NACK reset inactivity timer
c. Priority of last received transmission
d. Propagation type
e. Power saving state
f. Battery state
g. Combinations of the above
Example 14 may include a SL DRX procedure, where the short SL DRX cycle is configured for unicast and multicast only.
Example 15 may include a method comprising:
determining a Side Link (SL) Discontinuous Reception (DRX) configuration of a User Equipment (UE) for communication on a side link channel; and
based on the DRX configuration, communication with the UE is on a side-link channel.
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 methods of examples 15-16 or some other examples herein, wherein the DRX configuration is determined from a common configuration (e.g., as an offset in terms of SFN/DFN and duration).
Example 18 may include the methods of examples 15-17 or some other examples herein, wherein the DRX configuration is determined based on an ID associated with the UE (e.g., a UE ID or a higher layer ID (e.g., an ID associated with a service or application)).
Example 19 may include the methods of examples 15-18 or some other example herein, further comprising: an indication of a DRX configuration is received (e.g., over a Uu interface).
Example 20 may include the methods of examples 15-19 or some other examples 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 air interface (NR) cellular network, where the method comprises: identifying, by the UE, a first one or more resources to be used for initial NR side link transmission based on a first factor related to random resource selection or partial interception by other devices within the vicinity of the UE; the UE reserving the identified first one or more resources for initial NR side link transmission based on a first factor; the UE transmits or facilitates transmitting an initial NR side link 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: the UE performs open loop power control (OPLC) based on periodic Channel Busy Rate (CBR) measurements.
Example 23 may include the method of example 21 or some other example herein, further comprising: the UE performs semi-persistent resource reservation based on a first factor.
Example 24 may include the method of example 21 or some other example herein, wherein the UE is aware of activity times of other devices prior to performing the partial listening.
Example 25 may include the method of any one of examples 21-24 or some other example herein, further comprising: the UE identifying a second one or more resources to be used for subsequent NR side link transmissions based on a second factor related to full or partial interception by other devices within the vicinity of the UE; the UE reserving the identified second one or more resources of the subsequent NR sidelink transmission based on a second factor; the UE transmits or facilitates transmission of subsequent NR side chain transmissions 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 interception.
Example 27 may include the method of example 25 or some other example herein, wherein the first factor is partial interception and the second factor is full interception.
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 interception.
Example 29 may include the method of example 25 or some other example herein, wherein the first factor or the second factor is 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 the second factor is 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 air interface (NR) wireless network, where the method comprises: the UE identifying parameters to be used by the UE for a Discontinuous Reception (DRX) procedure of NR side link data, wherein the parameters include an active time region in which the UE is to monitor NR side link data and an inactive time region in which the UE is not to monitor NR side link data; the UE performs a DRX procedure for NR side link data.
Example 32 may include the method of example 31 or some other example herein, wherein the length of the active region or the length of the inactive region is based on requirements of the NR network associated with the physical layer transmission.
Example 33 may include the method of example 31 or some other example herein, wherein a length of the active time region 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 the indication of the length of the active time region or the length of the inactive time region 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 to be sent by the UE.
Example 37 may include the method of example 36, wherein the type is one of unicast, multicast, or broadcast.
Example 38 may include the method of any of examples 31-33 or some other example herein, wherein the UE changes from the inactive time region to the active time region based on a partial listening trigger.
Example 39 may include the method of any of examples 31-33 or some other example herein, wherein the UE changes from the inactive time region to the active time region based on a resource reselection 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 time region to the active time region based on a hybrid automatic repeat request (HARQ) reception trigger.
Example 41 may include an apparatus comprising means for performing one or more elements of the methods described in or associated with 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 that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the methods described in or associated with any one 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 the methods described in or associated with 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 associated with any of examples 1-40, or portions 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 one or more processors, cause the one or more processors to perform the methods, techniques, or processes described in or related to any one of examples 1-40 or portions thereof.
Example 46 may include signals as described in or associated with any of examples 1-40 or portions thereof.
Example 47 may include a datagram, packet, frame, segment, protocol Data Unit (PDU), or message as described in or associated with any one of examples 1-40, or portions thereof, or otherwise described in this disclosure.
Example 48 may include a signal encoded with data as described in or associated with any of examples 1-40 or portions thereof, or otherwise described in this disclosure.
Example 49 may include a signal encoded with a datagram, packet, frame, segment, protocol Data Unit (PDU), or message as described in or associated with any one of examples 1-40, or portions thereof, or otherwise described in this disclosure.
Example 50 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors causes the one or more processors to perform the method, technique, or process as described in or related to any one 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 causes the processing element to perform a method, technique, or process as described in or related to any one 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 communications as shown and described herein.
Example 55 may include a device to provide wireless communication as shown and described herein.
Any of the above 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 the 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.
Terminology
For purposes of this document, the following terms and definitions apply to the examples and embodiments discussed herein.
The term "circuitry" as used herein refers to, is part of, or includes, the following hardware components configured to provide the described functionality: such as electronic circuitry, logic circuitry, 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 (hcld), a structured ASIC, or a programmable SoC), a Digital Signal Processor (DSP), etc. 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 one or more hardware elements in combination with program code (or a combination of circuitry and program code used in an electrical or electronic system) for performing the functions of the program code. In these embodiments, a combination of hardware elements and program code may be referred to as a particular type of circuit.
The term "processor circuit" as used herein refers to a circuit, part of or comprising, capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing and/or transmitting digital data. The processing circuitry may include one or more processing cores for executing instructions and one or more memory structures for storing 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 tri-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions (e.g., program code, software modules, and/or functional processes). The processing circuitry may include further 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 with "processor circuitry" and may be referred to as "processor circuitry".
The term "interface circuit" 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 circuit" may refer to one or more hardware interfaces, such as a bus, an I/O interface, a peripheral component interface, a network interface card, and the like.
The term "user equipment" or "UE" as used herein refers to a device having radio communication capabilities and may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered as synonyms for the following terms and may be referred to as they: a client, mobile station, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" may include any type of wireless/wired device or any computing device that contains a wireless communication interface.
The term "network element" as used herein refers to a physical or virtualized device and/or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered as synonym for and/or referred to as the following terms: a networked computer, networking hardware, network device, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, etc.
The term "computer system" as used herein refers to any type of interconnected electronic device, computer device, or component thereof. Furthermore, the terms "computer system" and/or "system" may refer to various components of a computer that are communicatively coupled to each other. Furthermore, the terms "computer system" and/or "system" may refer to a plurality of computer devices and/or a plurality of computing systems communicatively coupled to each other and configured to share computing and/or networking resources.
The terms "appliance," "computer appliance," and the like as used herein refer to a computer device or computer system having program code (e.g., software or firmware) specifically designed to provide a particular 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 is otherwise dedicated to providing specific computing resources.
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 a computer device, a mechanical device, a memory space, a processor/CPU time, a processor/CPU usage, a processor and accelerator load, a hardware time or usage, power, input/output operations, ports or network sockets, channel/link allocations, throughput, memory usage, storage, networks, databases and applications, workload units, and the like. "hardware resources" may refer to computing, storage, and/or network resources provided by physical hardware elements. "virtualized resources" may refer to computing, storage, and/or network resources provided by the virtualization infrastructure to applications, devices, systems, etc. The term "network resource" or "communication resource" may refer to a resource that is accessible to a computer device/system via a communication network. The term "system resource" may refer to any kind of shared entity that provides a service and may include computing resources and/or network resources. System resources may be considered as a set of coherent functions, network data objects, or services that are accessible through a server, where the 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, whether tangible or intangible, used to communicate data or data streams. The term "channel" may be synonymous with and/or equivalent to the following terms: "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and/or any other similar term that refers to a path or medium through which data is transferred. Furthermore, the term "link" as used herein refers to a connection between two devices via a RAT for transmitting and receiving information.
The terms "instantiation", "instantiation" and the like as used herein refer to the creation of an instance. "instance" also refers to a specific occurrence of an object, which may occur, for example, during execution of program code.
The terms "coupled," "communicatively coupled," and their derivatives are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with 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 elements that are considered to be coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in communication with each other, including by wired or other interconnection connections, by wireless communication channels or links, and so forth.
The term "cell" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of a cell, or a data element containing content.
The term "SMTC" refers to an SSB-based measurement timing configuration configured by SSB-measurementtiming configuration.
The term "SSB" refers to an SS/PBCH block.
The term "primary cell" refers to an MCG cell operating on a primary frequency in which a UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.
The term "primary SCG cell" refers to an SCG cell in which a UE performs random access when performing a synchronization reconfiguration procedure, for DC operation.
The term "secondary cell", for a UE configured with CA, refers to a cell that provides additional radio resources over a special cell.
The term "secondary cell group" refers to a subset of serving cells including PSCell and zero or more secondary cells for a UE configured with DC.
The term "serving cell" refers to a primary cell for a UE in rrc_connected that is not configured with CA/DC, and only one serving cell includes the primary cell.
The term "serving cell" or "plurality of serving cells" refers to a set of cells including a special cell and all secondary cells for a UE in rrc_connected configured with CA/DC.
The term "special cell" refers to the PCell of an MCG or the PSCell of an SCG for DC operation; otherwise, the term "special cell" refers to a Pcell.
Claims (20)
1. An electronic device for a User Equipment (UE) of a new air interface (NR) cellular network, wherein the electronic device comprises:
one or more processors; and
one or more non-transitory computer-readable media comprising instructions that, when executed by the one or more processors, cause the electronic device to:
identifying a first one or more resources to be used for initial NR side chain transmission based on a first factor related to random resource selection or partial interception by other devices within the vicinity of the UE;
reserving the identified first one or more resources for the initial NR side link transmission based on the first factor; and
facilitating transmission of the initial NR side link transmission on the identified first one or more resources.
2. The electronic device of claim 1, wherein the instructions further cause the electronic device to:
open loop power control (OPLC) is performed based on periodic Channel Busy Rate (CBR) measurements.
3. The electronic device of claim 1, wherein the instructions further cause the electronic device to:
Semi-persistent resource reservation is performed by the UE based on the first factor.
4. The electronic device of claim 1, wherein the UE is aware of an activity time of the other device prior to performing partial listening.
5. The electronic device of any of claims 1-4, wherein the instructions further cause the electronic device to:
identifying a second one or more resources to be used for subsequent NR side chain transmissions based on a second factor related to full or partial interception by the other device within proximity of the UE;
reserving the identified second one or more resources of the subsequent NR side link transmission based on the second factor; and
facilitating transmission of the subsequent NR side chain 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 interception.
7. The electronic device of claim 5, wherein the first factor is partial interception and the second factor is full interception.
8. The electronic device of claim 5, wherein the first factor is random resource selection and the second factor is partial interception.
9. The electronic device of claim 5, wherein the first factor or the second factor is based on control information received by the UE.
10. The electronic device of claim 5, wherein the first factor or the second factor is 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 a User Equipment (UE) of a new air interface (NR) cellular network, wherein the electronic device comprises:
one or more processors; and
one or more non-transitory computer-readable media comprising instructions that, when executed by the one or more processors, cause the electronic device to:
identifying parameters to be used by the UE for a Discontinuous Reception (DRX) procedure of NR side link data, wherein the parameters include an active time region where the UE is to monitor the NR side link data and an inactive time region where the UE is not to monitor the NR side link data; and
the DRX procedure is performed for the NR side link data.
12. The electronic device of claim 11, wherein a length of the active region or a length of the inactive region is based on requirements of the NR network related to physical layer transmission.
13. The electronic device of claim 11, wherein other UEs in the NR network are aware of the length of the active time zone.
14. The electronic device of any of claims 11-13, wherein the indication of the length of the active time region or the length of the inactive time region is identified based on a transmission received from an NR NodeB (gNB) of the network.
15. The electronic device of claim 14, wherein the indication relates 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 to be transmitted by the UE.
17. The electronic device of claim 16, wherein the type is one of unicast, multicast, or broadcast.
18. The electronic device of any of claims 11-13, wherein the UE changes from the inactive time region to the active time region based on a partial listening trigger.
19. The electronic device of any of claims 11-13, wherein the UE changes from the inactive time region to the active time region based on a resource reselection trigger.
20. The electronic device of any of claims 11-13, wherein the UE changes from the inactive time region to the active time region based on a hybrid automatic repeat request (HARQ) reception trigger.
Applications Claiming Priority (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US202163138096P | 2021-01-15 | 2021-01-15 | |
| US63/138,200 | 2021-01-15 | ||
| US63/138,096 | 2021-01-15 | ||
| PCT/US2022/012279 WO2022155308A1 (en) | 2021-01-15 | 2022-01-13 | New radio (nr) sidelink communication |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116602019A true CN116602019A (en) | 2023-08-15 |
Family
ID=87594231
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202280008234.3A Pending CN116602019A (en) | 2021-01-15 | 2022-01-13 | New air interface (NR) side link communication |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116602019A (en) |
-
2022
- 2022-01-13 CN CN202280008234.3A patent/CN116602019A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11871436B2 (en) | Apparatus for UE measurement delay and granularity for new radio positioning measurement | |
| CN113473635A (en) | Two-cell scheduling for NR operation | |
| US20240129929A1 (en) | Techniques for cancelation of one or more uplink transmissions from a user equipment | |
| WO2022155108A1 (en) | Enhanced inter-slot frequency hopping for uplink coverage in 5g systems | |
| EP4278814A1 (en) | New radio multicast and broadcast service mac layer and group scheduling | |
| WO2022155125A1 (en) | Cot sharing procedure for unlicensed band communications | |
| WO2022011527A1 (en) | Srs configuration and transmission in multi-dci multi-trp and carrier aggregation | |
| CN113285790A (en) | Method for feeding back resource allocation | |
| CN113543337A (en) | Handling MsgB scheduled uplink transmission collisions with dynamic SFI | |
| US11979894B2 (en) | Soft resource availability indication for integrated access and backhaul (IAB) operation in paired spectrum | |
| CN115694700A (en) | Apparatus for use in a wireless communication system | |
| WO2022155595A1 (en) | Enhanced active time power saving for user equipment devices | |
| WO2022240969A1 (en) | Methods and apparatus for power headroom reporting for multiple transmission reception point (multi-trp) transmissions | |
| WO2022154962A1 (en) | Mitigation of time-domain overlaps involving transport block over multiple slots transmissions | |
| CN116648900A (en) | Support for lifecycle management for edge-enabled servers and edge configuration servers | |
| CN113541902A (en) | Apparatus for use in user equipment | |
| CN116602019A (en) | New air interface (NR) side link communication | |
| WO2022155308A1 (en) | New radio (nr) sidelink communication | |
| US11751228B2 (en) | Methods and apparatuses for uplink spatial relation info switch | |
| US20240237035A1 (en) | Apparatus for ue measurement delay and granularity for new radio positioning measurement | |
| EP4207666A1 (en) | Configuration of pdcch monitoring occasions for multi-slot pdcch monitoring capability | |
| US20240073930A1 (en) | Sidelink transmission resources for inter-ue coordination feedback | |
| US20240214147A1 (en) | Group-based channel state information reference signal (csi-rs) transmission | |
| US20230164670A1 (en) | Reduced complexity channel coding for reduced capability new radio user equipment | |
| CN116601898A (en) | Enhanced inter-slot frequency hopping for uplink coverage in 5G systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |