Aperiodic sidelink resource reservation request

Abstract

Techniques for wireless communication are disclosed. Aspects of the present disclosure relate to an aperiodic sidelink resource reservation request that requests a reservation of a set of time-frequency resources associated with a future time offset relative to a time reference, or alternatively a reservation of a set of time-frequency resources at a future absolute time.

Description

Background Technology

[0001] 1. Technical Field

[0002] All aspects of this disclosure relate to wireless technology.

[0003] 2. Related technical descriptions

[0004] Wireless communication systems have evolved through many generations, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data, wireless services with internet capabilities, and fourth-generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular systems and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog Advanced Mobile Phone Systems (AMPS), as well as digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), and others.

[0005] The fifth-generation (5G) wireless standard, known as New Radio (NR), delivers higher data transfer speeds, more connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance (NGC), the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on Positioning Reference Signals (RS-P), such as downlink, uplink, or sidelink Positioning Reference Signals (PRS)), and other technological enhancements compared to previous standards. These enhancements, along with the use of higher frequency bands, advancements in the PRS process and technology, and the high-density deployment of 5G, enable high-accuracy positioning based on 5G. Summary of the Invention

[0006] The following is a simplified summary of the invention relating to one or more aspects disclosed herein. Therefore, this summary should not be considered an exhaustive overview relating to all conceived aspects, nor should it be considered to identify key or decisive elements relating to all conceived aspects or to depict the scope associated with any particular aspect. Thus, the sole purpose of this summary is to present, in a simplified form, certain concepts relating to one or more aspects involving the mechanisms disclosed herein, prior to the detailed description presented below.

[0007] In one aspect, a method of operating a first user equipment (UE) includes: sending a first type of aperiodic sidelink resource reservation request to a second UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources associated with a future time relative to a time reference offset, and wherein the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and a second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options different from the first set of relative timing offset options; and communicating with the second UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0008] In one aspect, a method of operating a second user equipment (UE) includes: receiving from a first UE a first type of aperiodic sidelink resource reservation request, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources at a future time relative to a time reference offset, and wherein the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and a second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options different from the first set of relative timing offset options; and communicating with the first UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0009] In one aspect, a method of operating a first user equipment (UE) includes: sending an aperiodic sidelink resource reservation request to a second UE, the aperiodic sidelink resource reservation request requesting the reservation of a set of time-frequency resources at a future absolute time; and communicating with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request.

[0010] In one aspect, a method of operating a second user equipment (UE) includes: receiving an aperiodic sidelink resource reservation request from a first UE, the aperiodic sidelink resource reservation request requesting the reservation of a set of time-frequency resources at a future absolute time; and communicating with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request.

[0011] In one aspect, a first user equipment (UE) includes: one or more memories; and one or more processors communicatively coupled to the one or more memories, the one or more processors individually or in combination configured to: send a first type of aperiodic sidelink resource reservation request to a second UE, wherein the aperiodic sidelink resource reservation request requests reservations for a set of time-frequency resources associated with a future time relative to a time reference offset, and wherein the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and a second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options different from the first set of relative timing offset options; and communicate with the second UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0012] In one aspect, a second user equipment (UE) includes: one or more memories; and one or more processors communicatively coupled to the one or more memories, the one or more processors individually or in combination configured to: receive from a first UE a first type of aperiodic sidelink resource reservation request, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources at a future time relative to a time reference offset, and wherein the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and a second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options different from the first set of relative timing offset options; and communicate with the first UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0013] In one aspect, a user equipment (UE) includes: one or more memories; and one or more processors communicatively coupled to the one or more memories, the one or more processors individually or in combination configured to: send an aperiodic sidelink resource reservation request to a second UE, the aperiodic sidelink resource reservation request requesting reservation of a set of time-frequency resources at a future absolute time; and communicate with the second UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0014] In one aspect, a user equipment (UE) includes: one or more memories; and one or more processors communicatively coupled to the one or more memories, the one or more processors individually or in combination configured to: receive an aperiodic sidelink resource reservation request from a first UE, the aperiodic sidelink resource reservation request requesting reservation of a set of time-frequency resources at a future absolute time; and communicate with the first UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0015] In one aspect, a first user equipment (UE) includes: components for sending a first type of aperiodic sidelink resource reservation request to a second UE, wherein the aperiodic sidelink resource reservation request requests reservations for a set of time-frequency resources associated with a future time relative to a time reference offset, and wherein the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and a second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options different from the first set of relative timing offset options; and components for communicating with the second UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0016] In one aspect, a second user equipment (UE) includes: components for receiving from a first UE a first type of aperiodic sidelink resource reservation request, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources at a future time relative to a time reference offset, and wherein the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and a second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options different from the first set of relative timing offset options; and components for communicating with the first UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0017] In one aspect, a user equipment (UE) includes: components for sending an aperiodic sidelink resource reservation request to a second UE, the aperiodic sidelink resource reservation request requesting the reservation of a time-frequency resource set at a future absolute time; and components for communicating with the second UE on the time-frequency resource set according to the aperiodic sidelink resource reservation request.

[0018] In one aspect, a user equipment (UE) includes: components for receiving an aperiodic sidelink resource reservation request from a first UE, the aperiodic sidelink resource reservation request requesting the reservation of a set of time-frequency resources at a future absolute time; and components for communicating with the first UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0019] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a first user equipment (UE), cause the UE to: send a first type of aperiodic sidelink resource reservation request to a second UE, wherein the aperiodic sidelink resource reservation request requests reservations for a set of time-frequency resources associated with a future time relative to a time reference offset, and wherein the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and a second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options different from the first set of relative timing offset options; and communicate with the second UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0020] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a second user equipment (UE), cause the UE to: receive from a first UE a first type of aperiodic sidelink resource reservation request, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources at a future time relative to a time reference offset, and wherein the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and a second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options different from the first set of relative timing offset options; and communicate with the first UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0021] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: send an aperiodic sidelink resource reservation request to a second UE, the aperiodic sidelink resource reservation request requesting reservation of a set of time-frequency resources at a future absolute time; and, in accordance with the aperiodic sidelink resource reservation request, communicate with the second UE on the set of time-frequency resources.

[0022] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive an aperiodic sidelink resource reservation request from a first UE, the aperiodic sidelink resource reservation request requesting reservation of a set of time-frequency resources at a future absolute time; and, in accordance with the aperiodic sidelink resource reservation request, communicate with the first UE on the set of time-frequency resources.

[0023] Based on the accompanying drawings and detailed description, other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art. Attached Figure Description

[0024] The accompanying drawings are provided to help describe various aspects of this disclosure, and are provided for illustrative purposes only and not to limit the aspects.

[0025] Figure 1 Example wireless communication systems according to various aspects of this disclosure are illustrated.

[0026] Figure 2A , Figure 2B and Figure 2C Example wireless network architectures based on various aspects of this disclosure are illustrated.

[0027] Figure 3A , Figure 3B and Figure 3C It is a simplified block diagram of several examples of components that can be used in user equipment (UE), base stations and network entities and configured to support communications as taught herein.

[0028] Figure 4 This is a diagram illustrating an example frame structure according to various aspects of this disclosure.

[0029] Figure 5A and Figure 5B This is a diagram illustrating example sidelink time slot structures with and without feedback resources according to various aspects of this disclosure.

[0030] Figure 6 This is a diagram illustrating how a shared channel (SCH) can be established on a side link between two or more UEs according to various aspects of this disclosure.

[0031] Figure 7 This is an illustration of an example of a location resource pool configured within a sidelink resource pool for communication, according to various aspects of this disclosure.

[0032] Figure 8A An example call flow for pattern A discovery is illustrated according to various aspects of this disclosure, and Figure 8BAn example call flow for pattern B discovery is illustrated according to various aspects of this disclosure.

[0033] Figure 9A and Figure 9B Various scenarios of interest are illustrated according to aspects of this disclosure, including sidelink-only localization or combined Uu and sidelink localization.

[0034] Figure 10 Two resource allocation modes for transmission on a side link according to various aspects of this disclosure are illustrated.

[0035] Figure 11 The location preparation stage of the location estimation process according to various aspects of this disclosure is illustrated.

[0036] Figure 12 Examples of various aspects according to this disclosure are illustrated. Figure 11 The location estimation process is in the position execution phase.

[0037] Figure 13 Depicting aspects related to this disclosure Figures 11 to 12 The timing information associated with the corresponding stages described in the text.

[0038] Figure 14 An exemplary process of communication according to one aspect of this disclosure is illustrated.

[0039] Figure 15 An exemplary process of communication according to one aspect of this disclosure is illustrated.

[0040] Figure 16 An exemplary process of communication according to one aspect of this disclosure is illustrated.

[0041] Figure 17 An exemplary process of communication according to one aspect of this disclosure is illustrated.

[0042] Figure 18 Examples of various aspects according to this disclosure are shown respectively. Figures 14 to 17 Examples of specific implementations of any process in the process.

[0043] Figure 19 Examples of various aspects according to this disclosure are shown respectively. Figures 14 to 17 Examples of specific implementations of any process in the process.

[0044] Figure 20 Examples of various aspects according to this disclosure are shown respectively. Figures 14 to 17 Examples of specific implementations of any process in the process.

[0045] Figure 21 Examples of various aspects according to this disclosure are shown respectively. Figures 14 to 17 Examples of specific implementations of any process in the process. Detailed Implementation

[0046] Various aspects of this disclosure are provided in the following description and accompanying drawings of various examples provided for illustrative purposes. Alternative aspects may be devised without departing from the scope of this disclosure. Furthermore, well-known elements of this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure.

[0047] Various aspects typically involve non-periodic sidelink resource reservation requests. Scheduled locations are used when the location of a User Equipment (UE) is expected at a specific future time. For example, all vehicles on a road can be located simultaneously to provide indications of traffic congestion and assist vehicle communication. People, containers, transportation systems, etc., can also be located at certain common times. Scheduled location sessions are known in the Uu framework. However, the scheduling of sidelink resources for scheduled location estimation sessions is limited.

[0048] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. Aspects of this disclosure relate to aperiodic sidelink resource reservation requests that request reservations for a set of time-frequency resources associated with a future time relative to a time reference offset, or alternatively, reservations for a set of time-frequency resources at a future absolute time. Such aspects can provide various technical advantages, such as flexible support for scheduled location estimation for sidelink-based location estimation sessions (e.g., which can facilitate location tracking that meets various application requirements for V2X, inventory tracking systems, etc.).

[0049] The terms “exemplary” and / or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and / or “example” is not necessarily to be construed as superior to or better than other aspects. Similarly, the term “aspects of this disclosure” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed.

[0050] Those skilled in the art will understand that any of a variety of different techniques and methods can be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the following description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, and so on.

[0051] Furthermore, many aspects are described according to a sequence of actions to be performed by elements of, for example, a computing device. It will be appreciated that the various actions described herein can be performed by specific circuitry (e.g., an application-specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of both. Additionally, the sequence of actions described herein can be considered entirely embodied in any form of non-transitory computer-readable storage medium storing a corresponding set of computer instructions that, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of this disclosure can be embodied in a variety of different forms, all of which are contemplated within the scope of the claimed subject matter. Furthermore, for each aspect described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions."

[0052] As used herein, unless otherwise stated, the terms “User Equipment” (UE) and “Base Station” are not intended to be specific or otherwise limited to any particular Radio Access Technology (RAT). In general, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., mobile phone, router, tablet computer, laptop computer, consumer asset positioning device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.). A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term “UE” can be interchangeably referred to as “Access Terminal” or “AT,” “Client Equipment,” “Wireless Equipment,” “Subscriber Equipment,” “Subscriber Terminal,” “Subscriber Station,” “User Terminal” or “UT,” “Mobile Equipment,” “Mobile Terminal,” “Mobile Station,” or variations thereof. Overall, a UE can communicate with a core network via the RAN, and through the core network, a UE can connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through wired access networks, wireless local area network (WLAN) networks (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, etc.).

[0053] A base station may operate according to one of several RATs to communicate with the UE, depending on the network in which it is deployed, and may alternatively be referred to as an Access Point (AP), Network Node, Node B, Evolved Node B (eNB), Next Generation eNB (ng-eNB), New Radio (NR) Node B (also referred to as gNB or gNodeB), etc. The base station may primarily be used to support the UE's radio access, including supporting data, voice, and / or signaling connections for the supported UE. In some systems, the base station may only provide edge node signaling functions, while in others, it may provide additional control and / or network management functions. The communication link through which the UE can transmit signals to the base station is called an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the base station can transmit signals to the UE is called a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term “Traffic Channel (TCH)” may refer to the uplink / reverse traffic channel or the downlink / forward traffic channel.

[0054] The term "base station" can refer to a single physical transmit / receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, when the term "base station" refers to a single physical TRP, the physical TRP can be the antenna of a base station corresponding to a cell (or several cell sectors) of the base station. When the term "base station" refers to multiple co-located physical TRPs, the physical TRP can be the antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). When the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP can be a distributed antenna system (DAS) (a network of spatially separated antennas connected via a transmission medium to a common source) or a remote radio headend (RRH) (a remote base station connected to a serving base station). Alternatively, a non-co-located physical TRP can be the serving base station from which the UE receives measurement reports and a neighboring base station where the UE is measuring its reference radio frequency (RF) signal. Because, as used herein, a TRP is the point by which a base station transmits and receives radio signals, references to transmitting from or receiving at a base station should be understood to refer to a specific TRP of the base station.

[0055] In some specific implementations supporting UE positioning, the base station may not support the UE's radio access (e.g., it may not support data, voice, and / or signaling connections for the UE), but may instead transmit reference signals to the UE for measurement and / or receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of transmitting signals to the UE) and / or as a location measurement unit (e.g., in the case of receiving and measuring signals from the UE).

[0056] An “RF signal” refers to an electromagnetic wave of a given frequency that transmits information across the space between a transmitter and a receiver. As used herein, a transmitter may send a single “RF signal” or multiple “RF signals” to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple “RF signals” corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a “multipath” RF signal. As used herein, where the context clearly indicates that the term “signal” refers to a wireless signal or RF signal, an RF signal may also be referred to as a “wireless signal” or simply a “signal.”

[0057] Figure 1 An example wireless communication system 100 according to various aspects of this disclosure is illustrated. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled "BS") and various UEs 104. Base station 102 may include macro cell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macro cell base station may include an eNB and / or an ng-eNB (wherein the wireless communication system 100 corresponds to an LTE network), or a gNB (wherein the wireless communication system 100 corresponds to an NR network), or a combination of both, and the small cell base station may include femtocells, picocells, microcells, etc.

[0058] Base station 102 can collectively form a RAN and interface with core network 170 (e.g., evolved packet core (EPC) or 5G core (5GC)) via backhaul link 122, and interface with one or more location servers 172 (e.g., location management function (LMF) or secure user plane location (SUPL) location platform (SLP)) via core network 170. Location server 172 can be part of core network 170 or can be external to core network 170. Location server 172 can be integrated with base station 102. UE 104 can communicate with location server 172 directly or indirectly. For example, UE 104 can communicate with location server 172 via base station 102 currently serving UE 104. UE 104 can also communicate with location server 172 via another path, such as via application server (not shown), via another network, such as via wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), etc. For signaling purposes, communication between UE 104 and location server 172 can be represented as an indirect connection (e.g., via core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), wherein intermediate nodes (if present) are omitted from the signaling diagram for clarity.

[0059] In addition to other functions, base station 102 may perform functions associated with one or more of the following: transmitting user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base stations 102 may communicate with each other directly or indirectly (e.g., via EPC / 5GC) on backhaul link 134, which may be wired or wireless.

[0060] Base station 102 can wirelessly communicate with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells can be supported by base station 102 in each geographic coverage area 110. A “cell” is a logical communication entity used to communicate with a base station (e.g., via a frequency resource, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.) and can be associated with an identifier (e.g., Physical Cell Identifier (PCI), Enhanced Cell Identifier (ECI), Virtual Cell Identifier (VCI), Cell Global Identifier (CGI), etc.) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells can be configured according to different protocol types that can provide access for different types of UEs (e.g., Machine Type Communication (MTC), Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB), or other protocol types). Because a cell is supported by a specific base station, the term “cell” can refer to either or both of the logical communication entity and the base station supporting the logical communication entity, depending on the context. Furthermore, since the TRP is typically the physical transmission point of a cell, the terms "cell" and "TRP" can be used interchangeably. In some cases, the term "cell" can also refer to the geographical coverage area of ​​a base station (e.g., a sector), as long as the carrier frequency can be detected and used for communication within a portion of the geographical coverage area 110.

[0061] While the geographic coverage areas 110 of adjacent macro cell base stations 102 may partially overlap (e.g., in handover areas), some areas within geographic coverage areas 110 may substantially overlap with larger geographic coverage areas 110. For example, a small cell base station 102' (labeled "SC" for "small cell") may have a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macro cell base stations 102. A network that includes both small cell base stations and macro cell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB) that can provide service to a restricted group referred to as a Closed Subscriber Group (CSG).

[0062] The communication link 120 between base station 102 and UE 104 may include uplink (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use MIMO antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may use one or more carrier frequencies. Carrier allocation may be asymmetric for the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink compared to the uplink).

[0063] The wireless communication system 100 may also include a WLAN access point (AP) 150 that communicates with a wireless local area network (WLAN) station (STA) 152 via a communication link 154 in unlicensed spectrum (e.g., 5 GHz). When communicating in unlicensed spectrum, the WLAN STA 152 and / or WLAN AP 150 may perform a free channel assessment (CCA) or listen-before-talk (LBT) process before communication to determine whether the channel is available.

[0064] Small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell base station 102' can employ LTE or NR technology and use the same 5GHz unlicensed spectrum as WLAN AP 150. Small cell base station 102' employing LTE / 5G in unlicensed spectrum can improve the coverage and / or increase the capacity of the access network. NR in unlicensed spectrum may be referred to as NR-U. LTE in unlicensed spectrum may be referred to as LTE-U, Licensed Assisted Access (LAA), or MULTEFIRE. ® .

[0065] The wireless communication system 100 may also include a millimeter-wave (mmW) base station 180, which can operate at mmW and / or near-mmW frequencies to communicate with the UE 182. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF has a range of 30 GHz to 300 GHz with wavelengths between 1 mm and 10 mm. Radio waves in this band are referred to as millimeter waves. Near-mmW extends down to frequencies of 3 GHz with wavelengths of 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz, and are also referred to as centimeter waves. Communication using mmW / near-mmW radio bands has high path loss and relatively short range. The mmW base station 180 and the UE 182 can utilize beamforming (transmit and / or receive) on the mmW communication link 184 to compensate for the extremely high path loss and short range. Furthermore, it should be understood that, in alternative configurations, one or more base stations 102 may also use mmW or near-mmW and beamforming for transmission. Therefore, it should be understood that the foregoing examples are merely illustrative and should not be construed as limiting the various aspects disclosed herein.

[0066] Transmit beamforming is a technique used to focus RF signals in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). Using transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thus providing the receiving device with a faster and stronger RF signal (in terms of data rate). To change the directivity of the RF signal during transmission, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node can use an array of antennas (called a "phased array" or "antenna array") that forms an RF beam that can be "manipulated" to be pointed in different directions without actually moving the antennas. Specifically, RF currents from the transmitters are fed to individual antennas with the correct phase relationship, such that radio waves from the individual antennas add up in the desired direction to increase radiation, while canceling out in the undesired direction to suppress radiation.

[0067] Transmit beams can be quasi-co-located, meaning they appear to the receiver (e.g., the UE) as having the same parameters regardless of whether the network node's own transmit antennas are physically co-located. In NR, there are four types of quasi-co-located (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters of a second reference RF signal on a second beam can be derived based on information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is of type QCL D, the receiver can use the source reference RF signal to estimate the spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0068] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, the receiver may increase the gain setting of an antenna array in a particular direction and / or adjust the phase setting of the antenna array in a particular direction to amplify the RF signal received from that direction (e.g., increase its gain level). Therefore, when a receiver is described as performing beamforming in a certain direction, it means that the beam gain in that direction is high relative to the beam gain along other directions, or that the beam gain in that direction is the highest compared to the beam gain of all other receive beams available to the receiver in that direction. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.) of the RF signal received from that direction.

[0069] The transmit and receive beams can be spatially correlated. Spatial correlation means that parameters for a second beam (e.g., transmit or receive beam) for a second reference signal can be derived based on information about a first beam (e.g., receive or transmit beam) for a first reference signal. For example, a UE can use a specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam for transmitting an uplink reference signal (e.g., a sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

[0070] It is important to note that, depending on the entity forming the "downlink" beam, the beam can be either a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to transmit a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam for receiving the downlink reference signal. Similarly, depending on the entity forming the "uplink" beam, the beam can be either a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, the uplink beam is an uplink receive beam, while if the UE is forming an uplink beam, the uplink beam is an uplink transmit beam.

[0071] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. A similar naming issue sometimes occurs with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this differs from the designation used by the International Telecommunication Union. ® Extremely high frequency (EHF) bands (30 GHz to 300 GHz) are designated as “millimeter wave” bands.

[0072] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125GHz-24.25GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6GHz. For example, three higher operating bands have been identified as the frequency range designations FR4a or FR4-1 (52.6GHz to 71GHz), FR4 (52.6GHz to 114.25GHz), and FR5 (114.25GHz to 300GHz). Each of these higher frequency bands falls within the EHF band.

[0073] In light of the foregoing, unless otherwise specifically stated, it should be understood that, as used herein, the term "below 6 GHz" and the like can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that, as used herein, the term "millimeter wave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1 and / or FR5, or within the EHF band.

[0074] In multi-carrier systems such as 5G, one of the carrier frequencies is referred to as the "primary carrier," "anchor carrier," "primary serving cell," or "PCell," and the remaining carrier frequencies are referred to as "secondary carriers," "secondary serving cells," or "SCell." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by UE 104 / 182 and the cell, where UE 104 / 182 performs an initial Radio Resource Control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier on a licensed frequency (however, this is not always the case). The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured and used to provide additional radio resources once an RRC connection is established between UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier on an unlicensed frequency. Secondary carriers may contain only the necessary signaling information and signals. For example, since the primary uplink and primary downlink carriers are typically UE-specific, the UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 within a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to the carrier frequency / component carrier through which a base station communicates, the terms "cell," "serving cell," "component carrier," and "carrier frequency" can be used interchangeably.

[0075] For example, still refer to Figure 1One of the frequencies used by the macro cell base station 102 can be an anchor carrier (or "PCell"), and the other frequencies used by the macro cell base station 102 and / or the mmW base station 180 can be secondary carriers ("SCell"). Simultaneous transmission and / or reception on multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or data reception rates. For example, compared to the data rate obtained by a single 20MHz carrier, two aggregated 20MHz carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40MHz).

[0076] The wireless communication system 100 may also include a UE 164, which can communicate with the macro cell base station 102 via communication link 120 and / or with the mmW base station 180 via mmW communication link 184. For example, the macro cell base station 102 may support PCells and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0077] In some cases, UE 164 and UE 182 may be able to communicate via sidelink. A sidelink-capable UE (SL-UE) can communicate with base station 102 via communication link 120 using the Uu interface (i.e., the air interface between the UE and the base station). SL-UEs (e.g., UE 164, UE 182) can also communicate directly with each other via radio sidelink 160 using the PC5 interface (i.e., the air interface between sidelink-capable UEs). Radio sidelink (or simply "sidelink") is an adaptation of core cellular network (e.g., LTE, NR) standards that allows direct communication between two or more UEs without the need for communication through a base station. Sidelink communication can be unicast or multicast and can be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, emergency rescue applications, etc. One or more SL-UEs in a group of SL-UEs utilizing sidelink communication may be located within the geographical coverage area 110 of base station 102. Other SL-UEs in this group may be outside the geographical coverage area 110 of base station 102, or may be unable to receive transmissions from base station 102 for other reasons. In some cases, the groups of SL-UEs communicating via sidelink communication may utilize a one-to-many (1:M) system, where each SL-UE transmits to every other SL-UE in the group. In some cases, base station 102 facilitates the scheduling of resources used for sidelink communication. In other cases, sidelink communication is performed between the individual SL-UEs without involving base station 102.

[0078] On one hand, the sidelink 160 can operate via a wireless communication medium of interest that can be shared with other vehicles and / or infrastructure access points and other RATs for wireless communication. "Medium" can include one or more time, frequency, and / or space communication resources (e.g., covering one or more channels across one or more carriers) associated with wireless communication between one or more transmitter / receiver pairs. On another hand, the medium of interest may correspond to at least a portion of unlicensed frequency bands shared among various RATs. While different licensed frequency bands have been reserved for certain communication systems (e.g., by government entities such as the U.S. Federal Communications Commission (FCC), these systems (particularly those employing small cell access points) have recently expanded their operation to unlicensed frequency bands such as those used by wireless local area network (WLAN) technologies (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include various variants of CDMA, TDMA, FDMA, orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), and so on.

[0079] It should be noted that, although Figure 1 Only two of these UEs are exemplified as SL-UEs (i.e., UE 164 and UE 182), but any UE exemplified can be an SL-UE. Furthermore, although only UE 182 is described as capable of beamforming, any UE exemplified (including UE 164) can be capable of beamforming. When SL-UEs are capable of beamforming, they can beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UE 104), towards base stations (e.g., base station 102, base station 180, small cell 102', access point 150), etc. Therefore, in some cases, UE 164 and UE 182 can utilize beamforming via sidelink 160.

[0080] exist Figure 1 In the example, the UE shown (for simplicity, in) Figure 1Any UE (shown as a single UE 104) can receive signal 124 from one or more Earth-orbiting spacecraft (SV) 112 (e.g., satellites). In one aspect, SV 112 may be part of a satellite positioning system that allows UE 104 to use as an independent source of location information. Satellite positioning systems typically include a system of transmitters (e.g., SV 112) positioned such that a receiver (e.g., UE 104) can determine its location on or above the Earth based at least in part on positioning signals (e.g., signal 124) received from the transmitters. Such transmitters typically transmit signals marked with a set number of repeating pseudo-random noise (PN) codes. While typically located in SV 112, transmitters may sometimes be located at ground-based control stations, base stations 102, and / or other UEs 104. UE 104 may include one or more dedicated receivers specifically designed to receive signal 124 in order to derive geographic location information from SV 112.

[0081] In a satellite positioning system, the use of signal 124 can be enhanced by various satellite-based augmentation systems (SBAS), which may be associated with or otherwise made capable of being used with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential correction, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlap Service (EGNOS), Multifunctional Satellite Augmentation System (MSAS), GPS-assisted geographic augmentation navigation, or GPS and geographic augmentation navigation system (GAGAN). Therefore, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0082] On one hand, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 connects to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn connects to elements in the 5G network, such as the modified base station 102 (without a ground antenna) or network nodes in a 5GC. This element, in turn, provides access to other elements in the 5G network and ultimately to entities outside the 5G network, such as internet web servers and other user equipment. Thus, as a replacement or supplement to communication signals from the ground base station 102, UE 104 can receive communication signals (e.g., signal 124) from SV 112.

[0083] The wireless communication system 100 may also include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "side links"). Figure 1 In one example, UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of the base stations in base station 102 (e.g., UE 190 can indirectly obtain cellular connectivity through this D2D P2P link), and has a D2D P2P link 194 with a WLAN STA 152 connected to WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through this D2D P2P link). In one example, D2D P2P links 192 and 194 can utilize any known D2D RAT (such as LTE Direct (LTE-D), Wi-Fi Direct). ® ,Bluetooth ® (etc.) to support.

[0084] Figure 2A An example wireless network architecture 200 is illustrated. For instance, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be functionally viewed as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.), which work together to form the core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, specifically to user plane functions 212 and control plane functions 214, respectively. In an additional configuration, the ng-eNB 224 can also connect to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. Furthermore, the ng-eNB 224 can communicate directly with the gNB 222 via a backhaul connection 223. In some configurations, the next-generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of both ng-eNBs 224 and gNBs 222. Either or both of the gNBs 222 or ng-eNBs 224 can communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0085] Another optional aspect may include a location server 230 that can communicate with the 5GC 210 to provide location assistance to the UE 204. The location server 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The location server 230 may be configured to support one or more location services for the UE 204 that can be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). Furthermore, the location server 230 may be integrated into a component of the core network, or alternatively, may be located outside the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0086] Figure 2B Another example wireless network architecture 240.5GC 260 is illustrated (which can be used with...). Figure 2AThe 5GC 210 (corresponding to 5GC 210) can be functionally considered as a control plane function provided by the Access and Mobility Management Function (AMF) 264 and a user plane function provided by the User Plane Function (UPF) 262, which work together to form the core network (i.e., 5GC 260). The functions of AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and the Session Management Function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between UE 204 and the Short Message Service Function (SMSF) (not shown), and Secure Anchoring Functionality (SEAF). AMF 264 also interacts with the Authentication Server Function (AUSF) (not shown) and UE 204 and receives an intermediate key established as a result of the UE 204's authentication process. In the case of UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM) authentication, AMF 264 retrieves security material from the AMF. AMF 264 also includes Security Context Management (SCM). The SCM receives a key from the SEAF and uses this key to derive an access network-specific key. AMF 264 functionality also includes location service management for regulatory services, transmission of location service messages between UE 204 and Location Management Function (LMF) 270 (which acts as location server 230), transmission of location service messages between NG-RAN 220 and LMF 270, Evolved Packet System (EPS) bearer identifier allocation for EPS interoperability, and UE 204 mobility event notification. Furthermore, AMF 264 also supports non-3GPP... ® (Third Generation Partner Program) access network functionality.

[0087] The functions of UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (where applicable), acting as an external Protocol Data Unit (PDU) session point interconnecting to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., strobing, redirection, traffic steering), lawful eavesdropping (user plane collection), traffic usage reporting, quality of service (QoS) processing for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (Service Data Flow (SDF) to QoS flow mapping), transport-level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and delivering and forwarding one or more "end markers" to the source RAN node. UPF 262 can also support the delivery of location service messages between UE 204 and location servers (such as SLP 272) on the user plane.

[0088] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, service orientation configuration at UPF 262 for routing services to the correct destination, partial control of policy enforcement and QoS, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.

[0089] Another optional aspect may include an LMF 270, which can communicate with the 5GC 260 to provide location assistance to the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each can correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can connect to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). SLP 272 can support similar functions to LMF 270, but while LMF 270 can communicate with AMF 264, NG-RAN 220, and UE 204 on the control plane (e.g., using interfaces and protocols designed to transmit signaling messages rather than voice or data), SLP 272 can communicate with UE 204 and external clients (e.g., third-party server 274) on the user plane (e.g., using protocols designed to carry voice and / or data, such as Transmit Control Protocol (TCP) and / or IP).

[0090] Another optional aspect may include a third-party server 274 that can communicate with LMF 270, SLP 272, 5GC 260 (e.g., via AMF 264 and / or UPF 262), NG-RAN 220, and / or UE 204 to obtain location information (e.g., location estimation) of UE 204. Therefore, in some cases, the third-party server 274 may be referred to as a Location Services (LCS) client or an external client. The third-party server 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server.

[0091] User plane interface 263 and control plane interface 265 connect 5GC 260, and specifically connect UPF 262 and AMF 264 to one or more gNB 222 and / or ng-eNB 224 in NG-RAN 220. The interface between gNB 222 and / or ng-eNB 224 and AMF 264 is referred to as the "N2" interface, while the interface between gNB 222 and / or ng-eNB 224 and UPF 262 is referred to as the "N3" interface. The gNB 222 and / or ng-eNB 224 of NG-RAN 220 can communicate directly with each other via backhaul connection 223, referred to as the "Xn-C" interface. One or more of gNB 222 and / or ng-eNB 224 can communicate with one or more UEs 204 via a radio interface referred to as the "Uu" interface.

[0092] The functionality of the gNB 222 is divided among the gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically allocated to the gNB-DU 228, including user data delivery, mobility control, radio access network sharing, location, session management, etc. More specifically, the gNB-CU 226 typically hosts the Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that typically hosts the Radio Link Control (RLC) and Media Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and a cell is supported by only one gNB-DU 228. The interface 232 between gNB-CU 226 and one or more gNB-DU 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of gNB 222 is typically managed by one or more independent gNB-RU 229s, which perform functions such as power amplification and signal transmission / reception. The interface between gNB-DU 228 and gNB-RU 229 is referred to as the "Fx" interface. Therefore, UE 204 communicates with gNB-CU 226 via the RRC, SDAP, and PDCP layers, with gNB-DU 228 via the RLC and MAC layers, and with gNB-RU 229 via the PHY layer.

[0093] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, or network equipment (such as base stations or one or more units (or components) performing base station functions) can be implemented in aggregated or decomposed architectures. For example, base stations (such as Node B (NB), evolved NB (eNB), NR base stations, 5GNB, access points (APs), transmit / receive points (TRPs), or cells, etc.) can be implemented as aggregated base stations (also known as self-contained base stations or monolithic base stations) or decomposed base stations.

[0094] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0095] Base station type operation or network design can consider the aggregation characteristics of base station functionality. For example, decomposed base stations can be used in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN) (such as those developed by the O-RAN Alliance), and other similar networks. ® This can be used in proposed network configurations or virtualized radio access networks (vRAN, also known as cloud radio access networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which allows for flexibility in network design. Various units in a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0096] Figure 2C An example disaggregated base station architecture 250 according to various aspects of this disclosure is illustrated. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU 226) that can communicate directly with the core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 via one or more disaggregated base station units (such as a near real-time (near-RT) RAN intelligent controller (RIC) 259 via an E2 link or a non-real-time (non-RT) RIC 257 associated with a Service Management and Orchestration (SMO) framework 255, or both). CUs 280 may communicate with one or more duplex units (DUs) 285 (e.g., gNB-DU 228) via a corresponding midhaul link (e.g., an F1 interface). DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RU 229) via a corresponding fronthaul link. RU 287 can communicate with the corresponding UE 204 via one or more radio frequency (RF) access links. In some implementations, UE 204 can be served by multiple RU 287s simultaneously.

[0097] Each of the units (i.e., CU 280, DU 285, RU 287, and near-RT RIC 259, non-RT RIC 257, and SMO frame 255) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the unit, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals via wireless transmission media or transmit signals to one or more other units, or both.

[0098] In some aspects, the CU 280 can host one or more higher-level control functions. Such control functions may include RRC, PDCP, Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to communicate signaling with other control functions hosted by the CU 280. The CU 280 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 280 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 280 can be implemented to communicate with the DU 285 for network control and signaling, as needed.

[0099] DU 285 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 287s. In some aspects, DU 285 may be at least partially based on functional partitioning (such as that provided by the 3rd Generation Partnership Project (3GPP)). ® The DU285 is functionally partitioned to host one or more of the RLC layer, MAC layer, and one or more high-PHY layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation). In some respects, the DU285 may further host one or more low-PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU285 or with control functions hosted by the CU280.

[0100] Lower-layer functionality can be implemented by one or more RU 287s. In some deployments, an RU287 controlled by a DU 285 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 287 may be implemented to handle over-the-air (OTA) communications with one or more UE 204s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration enables the implementation of the DU 285 and CU 280 in cloud-based RAN architectures (such as vRAN architectures).

[0101] SMO framework 255 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 255 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 255 can be configured to interact with cloud computing platforms such as Open Cloud (O-Cloud) 269 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 280, DU 285, RU 287, and near-RT RIC 259. In some implementations, SMO framework 255 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 261) via the O1 interface. Additionally, in some implementations, SMO framework 255 can communicate directly with one or more RU 287s via the O1 interface. SMO framework 255 may also include a non-RT RIC 257 configured to support the functionality of SMO framework 255.

[0102] The non-RT RIC 257 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 259. The non-RT RIC 257 can be coupled to or communicate with the near-RT RIC 259, such as via an A1 interface. The near-RT RIC 259 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and action, connecting one or more CU 280s, one or more DU 285s, or both, and O-eNBs to the near-RT RIC 259.

[0103] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 259, the non-RT RIC 257 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 259 and may be received from non-network data sources or network functions at the SMO framework 255 or the non-RT RIC 257. In some examples, the non-RT RIC 257 or the near-RT RIC 259 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 257 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 255 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0104] Figure 3A , Figure 3B and Figure 3C Examples are shown that can be incorporated into UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270, or alternatively may be independent of...). Figure 2A and Figure 2BSeveral example components (represented by corresponding boxes) in the NG-RAN 220 and / or 5GC 210 / 260 infrastructure (such as private networks) depicted herein support the operation as described herein. It should be understood that these components may be implemented in different specific implementations in different types of devices (e.g., in ASICs, in System-on-Chip (SoCs), etc.). The illustrated components may also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Furthermore, a given device may contain one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0105] UE 302 and base station 304 each include one or more Wireless Wide Area Network (WWAN) transceivers 310 and 350, which provide components (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for blocking transmission, etc.) for communication via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356 for communication with other network nodes (such as other UEs, access points, base stations (e.g., eNB, gNB), etc.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) through a wireless communication medium of interest (e.g., a time / frequency resource set in a specific spectrum). WWAN transceivers 310 and 350 can be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, to receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, WWAN transceivers 310 and 350 each include: one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively; and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

[0106] In at least some cases, UE 302 and base station 304 each further include one or more short-range wireless transceivers 320 and 360, respectively. Short-range wireless transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide access over a wireless communication medium of interest via at least one designated RAT (e.g., Wi-Fi, LTE Direct, Bluetooth). ® ZIGBEE ® Z-WAVE ® Components (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for blocking transmission, etc.) that enable communication between PC5, Dedicated Short-Range Communication (DSRC), Wireless Access for Vehicle Environments (WAVE), Near Field Communication (NFC), Ultra-Wideband (UWB), etc.) and other network nodes (such as other UEs, access points, base stations, etc.). Short-range transceivers 320 and 360 can be configured in different ways to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.) respectively according to a specified RAT, and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.) respectively. Specifically, the short-range wireless transceiver 320 and short-range wireless transceiver 360 each include: one or more transmitters 324 and 364 respectively for transmitting and encoding signals 328 and 368, and one or more receivers 322 and 362 respectively for receiving and decoding signals 328 and 368. As a specific example, the short-range wireless transceiver 320 and short-range wireless transceiver 360 can be Wi-Fi transceivers, Bluetooth transceivers, etc. ® Transceiver, Zigbee ® and / or Z-WAVE ® Transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

[0107] In at least some cases, UE 302 and base station 304 also include satellite signal receivers 330 and 370. Satellite signal receivers 330 and 370 can be connected to one or more antennas 336 and 376 respectively, and can provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378 respectively. Where satellite signal receivers 330 and 370 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 can be Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, etc. ®The signals received include Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. When satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, satellite positioning / communication signals 338 and 378 can be communication signals originating from a 5G network (e.g., carrying control and / or user data). Satellite signal receivers 330 and 370 can include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request information and operations from other systems as needed, and in at least some cases, use measurements obtained by any suitable satellite positioning system algorithm to perform calculations to determine the locations of UE 302 and base station 304, respectively.

[0108] Base station 304 and network entity 306 each include one or more network transceivers 380 and 390, which provide components (e.g., transmitting components, receiving components, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, base station 304 may use one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. Similarly, network entity 306 may use one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or to communicate with other network entities 306 via one or more wired or wireless core network interfaces.

[0109] Transceivers can be configured to communicate via wired or wireless links. A transceiver (whether wired or wireless) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). In some embodiments, the transceiver may be an integrated device (e.g., implementing transmitter and receiver circuitry in a single device), in some embodiments it may include separate transmitter and receiver circuitry, or in other embodiments it may be implemented in a different manner. The transmitter and receiver circuitry of a wired transceiver (e.g., network transceiver 380 and network transceiver 390 in some embodiments) may be coupled to one or more wired network interface ports. Wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the corresponding device (e.g., UE 302, base station 304) to perform transmit beamforming, as described herein. Similarly, wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter and receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366), such that the corresponding device may perform only receive or only transmit at a given time, rather than both receive and transmit simultaneously. Wireless transceivers (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include network listening modules (NLMs) for performing various measurements.

[0110] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360 in some specific embodiments, and network transceivers 380 and 390) and wired transceivers (e.g., network transceivers 380 and 390 in some specific embodiments) may generally be described as "transceiver," "at least one transceiver," or "one or more transceivers." Therefore, whether a particular transceiver is a wired or wireless transceiver can be inferred from the type of communication performed. For example, backhaul communication between network devices or servers typically involves signaling via a wired transceiver, while wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via a wireless transceiver.

[0111] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operation disclosed herein. UE 302, base station 304, and network entity 306 each include one or more processors 332, 384, and 394 for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 332, 384, and 394 may provide components for processing, such as components for determining, components for calculating, components for receiving, components for transmitting, components for indicating, etc. In one aspect, processors 332, 384, and 394 may include, for example, one or more general-purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), other programmable logic devices or processing circuits, or various combinations thereof.

[0112] UE 302, base station 304, and network entity 306 each include memory circuitry implementing memories 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Therefore, memories 340, 386, and 396 can provide components for storage, retrieval, maintenance, etc. In some cases, UE 302, base station 304, and network entity 306 may each include sidelink resource components 342, 388, and 398. Sidelink resource components 342, 388, and 398 may be hardware circuitry that is part of or coupled to processors 332, 384, and 394, respectively, which, when executed, enable UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other respects, sidelink resource components 342, 388, and 398 may be external to processors 332, 384, and 394 (e.g., integrated with another processing system as part of a modem processing system, etc.). Alternatively, sidelink resource components 342, 388, and 398 may be memory modules stored in memories 340, 386, and 396, respectively, which, when executed by processors 332, 384, and 394 (or modem processing system, another processing system, etc.), enable UE 302, base station 304, and network entity 306 to perform the functionality described herein. Figure 3A Possible locations of the sidelink resource component 342 are illustrated. This sidelink resource component may be, for example, part of one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a standalone component. Figure 3BPossible locations of the sidelink resource component 388 are illustrated. This sidelink resource component may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a standalone component. Figure 3C Possible locations of the sidelink resource component 398 are illustrated. The sidelink resource component may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a standalone component.

[0113] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide components for sensing or detecting motion and / or orientation information independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. By way of example, sensor 344 may include accelerometers (e.g., microelectromechanical systems (MEMS) devices), gyroscopes, geomagnetic sensors (e.g., compasses), altimeters (e.g., barometric altimeters), and / or any other type of motion detection sensor. Furthermore, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of multi-axis accelerometers and orientation sensors to provide the ability to calculate positioning in two-dimensional (2D) and / or three-dimensional (3D) coordinate systems.

[0114] In addition, UE 302 includes a user interface 346 that provides components for providing instructions to a user (e.g., audible and / or visual instructions) and / or for receiving user input (e.g., when the user actuates a sensing device such as a keypad, touchscreen, microphone, etc.). Although not shown, base station 304 and network entity 306 may also include user interfaces.

[0115] Referring more specifically to one or more processors 384, in the downlink, IP packets from network entity 306 can be provided to processor 384. One or more processors 384 can implement functionality for the RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with broadcasting system information (e.g., Master Information Block (MIB), System Information Block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer PDUs, error correction via Automatic Repeat Request (ARQ), concatenation, segmentation, and reassembly of RLC Service Data Units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel priority ordering.

[0116] Transmitter 354 and receiver 352 implement Layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include: error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. Transmitter 354 processes the mapping to the signal constellation based on various modulation schemes (e.g., Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), M-Phase Shift Keying (M-PSK), M-QAM). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to Orthogonal Frequency Division Multiplexing (OFDM) subcarriers, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domains, and then combined using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM symbol stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from a channel estimator can be used to determine the decoding and modulation scheme, as well as for spatial processing. These channel estimates can be derived from a reference signal transmitted by UE 302 and / or channel condition feedback. Each spatial stream can then be provided to one or more different antennas 356. Transmitter 354 can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0117] At UE 302, receiver 312 receives signals via its corresponding antenna 316. Receiver 312 recovers the information modulated onto the RF carrier and provides this information to one or more processors 332. Transmitter 314 and receiver 312 implement Layer 1 functionality associated with various signal processing functions. Receiver 312 can perform spatial processing on the information to recover any spatial streams destined for UE 302. If multiple spatial streams are destined for UE 302, they can be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 304 on the physical channel. Then, data and control signals are provided to one or more processors 332, which implement layer 3 (L3) and layer 2 (L2) functionality.

[0118] In the downlink, one or more processors 332 provide demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the core network. One or more processors 332 are also responsible for error detection.

[0119] Similar to the functionality described in conjunction with downlink transmissions performed by base station 304, one or more processors 332 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with the delivery of upper-layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ), priority handling, and logical channel priority ordering.

[0120] The channel estimate derived by the channel estimator from the reference signal or feedback transmitted by the base station 304 can be used by the transmitter 314 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the transmitter 314 can be provided to different antennas 316. The transmitter 314 can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0121] Uplink transmissions are processed at base station 304 in a manner similar to that described in conjunction with the receiver function at UE 302. Receiver 352 receives signals via its corresponding antenna 356. Receiver 352 recovers the information modulated onto the RF carrier and provides this information to one or more processors 384.

[0122] In the uplink, one or more processors 384 provide demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from UE 302. IP packets from one or more processors 384 can be provided to the core network. One or more processors 384 are also responsible for error detection.

[0123] For convenience, UE 302, base station 304 and / or network entity 306 are in Figure 3A , Figure 3B and Figure 3C The document is shown as including various components that can be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionalities in different designs. In particular, Figures 3A to 3C Various components are optional in alternative configurations, and various aspects include configurations that can vary due to design choices, cost, equipment usage, or other considerations. For example, in Figure 3A In certain cases, specific implementations of UE 302 may omit WWAN transceiver 310 (e.g., wearable devices, tablets, personal computers (PCs), or laptops may have Wi-Fi and / or Bluetooth). ® (e.g., cellular only), or the short-range wireless transceiver 320 can be omitted (e.g., cellular only), or the satellite signal receiver 330 can be omitted, or the sensor 344 can be omitted, etc. For example, in Figure 3B In certain cases, specific implementations of base station 304 may omit WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or short-range wireless transceiver 360 (e.g., cellular only), or satellite signal receiver 370, etc. For the sake of brevity, examples of various alternative configurations are not provided herein, but will be readily understood by those skilled in the art.

[0124] Various components of UE 302, base station 304, and network entity 306 can be communicatively coupled to each other via data buses 334, 382, ​​and 392, respectively. In one aspect, data buses 334, 382, ​​and 392 can form or be part of the communication interfaces of UE 302, base station 304, and network entity 306, respectively. For example, in cases where different logical entities are embodied in the same device (e.g., gNB and location server functionality integrated into the same base station 304), data buses 334, 382, ​​and 392 can provide communication between these different logical entities.

[0125] Figure 3A , Figure 3B and Figure 3C The components can be implemented in various ways. In some specific implementations, Figure 3A , Figure 3B and Figure 3C The components can be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or combine at least one memory component for storing information or executable code used by the circuit to provide that functionality. For example, some or all of the functionalities represented by blocks 310 to 346 may be implemented by the processor and memory components of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Similarly, some or all of the functionalities represented by blocks 350 to 388 may be implemented by the processor and memory components of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Moreover, some or all of the functionalities represented by blocks 390 to 398 may be implemented by the processor and memory components of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed "by the UE," "by the base station," "by the network entity," etc. However, as will be understood, such operations, actions and / or functions may actually be performed by specific components or combinations of components of UE 302, base station 304, network entity 306, etc., such as processors 332, 384, 394, transceivers 310, 320, 350 and 360, memory 340, 386 and 396, sidelink resource components 342, 388 and 398, etc.

[0126] In some designs, network entity 306 may be implemented as a core network component. In other designs, network entity 306 may operate differently from the network operator or cellular network infrastructure (e.g., NG RAN 220 and / or 5GC 210 / 260). For example, network entity 306 may be a component of a private network that can be configured to communicate with UE 302 via base station 304 or independently of base station 304 (e.g., via a non-cellular communication link such as Wi-Fi).

[0127] Various frame structures can be used to support downlink and uplink transmission between network nodes (e.g., base stations and UEs). Figure 4 Figure 400 illustrates an example frame structure according to various aspects of this disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.

[0128] LTE (and in some cases NR) uses Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single-Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option to use OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are often referred to as tones, frequency slots, etc. Each subcarrier can be modulated using data. Generally, modulation symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz, and the minimum resource allocation (resource block) can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, the nominal Fast Fourier Transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.08 MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, there can be 1, 2, 4, 8, or 16 subbands, respectively.

[0129] LTE supports a single set of parameters (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR can support multiple sets of parameters (µ), for example, subcarrier spacings of 15kHz (µ=0), 30kHz (µ=1), 60kHz (µ=2), 120kHz (µ=3), and 240kHz (µ=4) or larger can be available. Within each subcarrier spacing, there are 14 symbols per time slot. For a 15kHz SCS (µ=0), there is one time slot per subframe, 10 time slots per frame, a time slot duration of 1 millisecond (ms), a symbol duration of 66.7 microseconds (µs), and a maximum nominal system bandwidth (in MHz) of 4K FFT size. For a 30kHz SCS (µ=1), there are two time slots per subframe, 20 time slots per frame, a time slot duration of 0.5ms, a symbol duration of 33.3µs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size. For a 60kHz SCS (µ=2), there are four time slots per subframe, 40 time slots per frame, a time slot duration of 0.25ms, a symbol duration of 16.7µs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size. For a 120kHz SCS (µ=3), there are eight time slots per subframe, 80 time slots per frame, a time slot duration of 0.125ms, a symbol duration of 8.33µs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size. For a 240kHz SCS (µ=4), there are 16 time slots per subframe, 160 time slots per frame, a time slot duration of 0.0625ms, a symbol duration of 4.17µs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size.

[0130] exist Figure 4 In the example, a parameter set of 15kHz is used. Therefore, in the time domain, a 10ms frame is divided into 10 equal-sized subframes, each 1ms long, and each subframe includes one time slot. Figure 4 In the diagram, time is represented horizontally (on the X-axis), with time increasing from left to right, while frequency is represented vertically (on the Y-axis), with frequency increasing (or decreasing) from bottom to top.

[0131] A resource grid can be used to represent time slots, each of which includes one or more time-concurrent resource blocks (RBs) (also known as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE corresponds to a symbol length in the time domain and a subcarrier in the frequency domain. Figure 4In the parameter set, for a normal cyclic prefix, the RB can contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, the RB can contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0132] Some REs may carry reference (pilot) signals (RS). These reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSB), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communication. Figure 4 An example location (labeled "R") of an RE carrying a reference signal is shown.

[0133] The set of resource elements (REs) used for PRS transmission is called a "PRS resource". The set of resource elements can span multiple PRBs in the frequency domain and span "N" (such as one or more) consecutive symbols within a time slot in the time domain. In a given OFDM symbol in the time domain, the PRS resource occupies a consecutive PRB in the frequency domain.

[0134] The transmission of PRS resources within a given PRB has a specific comb size (also known as "comb density"). The comb size "N" represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the PRS resource configuration. Specifically, for a comb size "N", the PRS is transmitted in every Nth subcarrier of a symbol within the PRB. For example, for comb size-4, for each symbol of the PRS resource configuration, the RE corresponding to every fourth subcarrier (such as subcarrier 0, 4, 8) is used to transmit the PRS resource. Currently, for DL-PRS, comb sizes-2, comb size-4, comb size-6, and comb size-12 are supported. Figure 4 An example PRS resource configuration for Comb-4 (which spans four symbols) is shown. That is, the location of the shaded RE (marked as "R") indicates the Comb-4 PRS resource configuration.

[0135] Currently, DL-PRS resources can span 2, 4, 6, or 12 consecutive symbols within a time slot using a full-frequency-domain interleaved mode. DL-PRS resources can be configured in any downlink or flexible (FL) symbol within a time slot configured by a higher layer. For all REs of a given DL-PRS resource, there may be a constant energy per resource element (EPRE). The following are the symbol-by-symbol frequency offsets for comb sizes 2, 4, 6, and 12 on 2, 4, 6, and 12 symbols. 2-symbol comb teeth-2: {0, 1}; 4-symbol comb teeth-2: {0, 1, 0, 1}; 6-symbol comb teeth-2: {0, 1, 0, 1, 0, 1}; 12-symbol comb teeth-2: {0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1}; 4-symbol comb teeth-4: {0, 2, 1, 3} (e.g., in...) Figure 4 (in the example); 12-symbol comb-4: {0, 2, 1, 3, 0, 2, 1, 3, 0, 2, 1, 3}; 6-symbol comb-6: {0, 3, 1, 4, 2, 5}; 12-symbol comb-6: {0, 3, 1, 4, 2, 5, 0, 3, 1, 4, 2, 5}; and 12-symbol comb-12: {0, 6, 3, 9, 1, 7, 4, 10, 2, 8, 5, 11}.

[0136] A “PRS resource set” is a collection of PRS resources used to transmit PRS signals, where each PRS resource has a PRS resource ID. Furthermore, PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and associated with a specific TRP (identified by the TRP ID). Additionally, PRS resources in a PRS resource set have the same periodicity, common silence mode configuration, and the same repetition factor (such as “PRS-ResourceRepetitionFactor”) across time slots. Periodicity is the time from the first repetition of the first PRS resource in the first PRS instance to the same first repetition of the same first PRS resource in the next PRS instance. Periodicity can have a length selected from: 2^µ The time slots are {4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240}, where µ = 0, 1, 2, 3. The repetition factor can have a length selected from {1, 2, 4, 6, 8, 16, 32} time slots.

[0137] In a PRS resource set, a PRS resource ID is associated with a single beam (or beam ID) transmitted from a single TRP (where one TRP can transmit one or more beams). That is, each PRS resource in a PRS resource set can be transmitted on a different beam, and therefore, a "PRS resource" (or simply "resource") can also be referred to as a "beam." It should be noted that this does not imply whether the UE knows the TRP and beam on which it transmits the PRS.

[0138] A “PRS instance” or “PRS timing” is an instance of a periodically repeating time window (such as a group of one or more consecutive time slots) in which a PRS is expected to be sent. A PRS timing may also be referred to as a “PRS positioning timing,” “PRS positioning instance,” “positioning timing,” “positioning instance,” “positioning repetition,” or simply “timing,” “instance,” or “repetition.”

[0139] A “positioning frequency layer” (also simply “frequency layer”) is a collection of one or more PRS resource sets with identical values ​​for certain parameters across one or more TRPs. Specifically, the collection of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning that all parameter sets supported for the Physical Downlink Shared Channel (PDSCH) are also supported by the PRS), the same point A, the same downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The point A parameter takes the value of the parameter “ARFCN-ValueNR” (where “ARFCN” stands for “Absolute Radio Channel Number”) and is an identifier / code specifying a pair of physical radio channels used for transmission and reception. The downlink PRS bandwidth can have a granularity of four PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs. Currently, up to four frequency layers have been defined, and up to two PRS resource sets can be configured per frequency layer per TRP.

[0140] The concept of a frequency layer is somewhat similar to that of component carriers and bandwidth portions (BWPs), but the difference is that component carriers and BWPs are used by a single base station (or macrocell base station and small cell base station) to transmit data channels, while a frequency layer is used by several (usually three or more) base stations to transmit PRS. A UE can indicate the number of frequency layers it can support when transmitting its positioning capabilities to the network (such as during an LTE Positioning Protocol (LPP) session). For example, a UE can indicate whether it can support one or four positioning frequency layers.

[0141] It should be noted that the terms "location reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "location reference signal" and "PRS" can also refer to any type of reference signal that can be used for positioning, such as, but not limited to, PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc., as defined in LTE and NR. Furthermore, the terms "location reference signal" and "PRS" can refer to downlink positioning reference signals, uplink positioning reference signals, or sidelink positioning reference signals, unless otherwise indicated by the context. If further distinction is required regarding the type of PRS, downlink positioning reference signals can be referred to as "DL-PRS," uplink positioning reference signals (e.g., positioning SRS, i.e., PTRS) as "UL-PRS," and sidelink positioning reference signals as "SL-PRS." Furthermore, for signals that can be transmitted in the downlink, uplink, and / or sidelink (e.g., DMRS), these signals may be preceded by "DL", "UL", or "SL" to distinguish the direction. For example, "UL-DMRS" may be different from "DL-DMRS".

[0142] Sidelink communication occurs within transmit or receive resource pools. In the frequency domain, the smallest unit of resource allocation is a subchannel (e.g., a set of consecutive PRBs in the frequency domain). In the time domain, resource allocation is performed within a time slot interval. However, some time slots are unavailable for sidelinks, and some time slots contain feedback resources. Furthermore, sidelink resources can be (pre-)configured to occupy fewer than 14 symbols in a time slot.

[0143] Configure sidelink resources at the Radio Resource Control (RRC) layer. RRC configuration can be pre-configured (e.g., pre-loaded on the UE) or configured (e.g., from the serving base station).

[0144] The NR side link supports Hybrid Automatic Repeat Request (HARQ) retransmission. Figure 5A This is a diagram 500 illustrating an example time slot structure without feedback resources based on various aspects of this disclosure. Figure 5A In the example, time is represented horizontally and frequency vertically. In the time domain, the length of each block is one Orthogonal Frequency Division Multiplexing (OFDM) symbol, and 14 symbols constitute a time slot. In the frequency domain, the height of each block is a subchannel. Currently, the (pre-)configured subchannel size can be selected from a set of {10, 15, 20, 25, 50, 75, 100} Physical Resource Blocks (PRBs).

[0145] For side-link time slots, the first symbol is a repetition of the previous symbol and is used for automatic gain control (AGC) settings. This is in Figure 5AThis is illustrated using vertical and horizontal hashing. For example... Figure 5A As shown, for sidelinks, the Physical Sidelink Control Channel (PSCCH) and the Physical Sidelink Shared Channel (PSSCH) are transmitted in the same time slot. Similar to the Physical Downlink Control Channel (PDCCH), the PSCCH carries control information about sidelink resource allocation and a description of the sidelink data sent to the UE. Likewise, similar to the Physical Downlink Shared Channel (PDSCH), the PSSCH carries the UE's user data. Figure 5A In the example, the PSCCH occupies half the bandwidth of the sub-channel and only takes up three symbols. Finally, the gap symbol appears after the PSSCH.

[0146] Figure 5B This is a diagram 550 illustrating an example time-slot structure with feedback resources based on various aspects of this disclosure. Figure 5B In the example, time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one OFDM symbol, and 14 symbols constitute a time slot. In the frequency domain, the height of each block is a subchannel.

[0147] Figure 5B The illustrated time slot structure and Figure 5A The illustrated time slot structures are similar, but the difference is... Figure 5B The illustrated time slot structure includes feedback resources. Specifically, the last two symbols of the time slot are dedicated to the Physical Side Link Feedback Channel (PSFCH). The first PSFCH symbol is a repetition of the second PSFCH symbol used for AGC setup. In addition to the gap symbol following the PSFCH, there is a gap symbol after the two PSFCH symbols. Currently, the resources used for the PSFCH can be configured periodically from a set of {0, 1, 2, 4} time slots.

[0148] The Physical Sidelink Control Channel (PSCCH) carries Sidelink Control Information (SCI). The first-level SCI (referred to as "SCI-1") is transmitted on the PSCCH and contains information for resource allocation and decoding of the second-level SCI (referred to as "SCI-2"). SCI-2 is transmitted on the Physical Sidelink Shared Channel (PSSCH) and contains information for decoding data to be transmitted on the sidelink's shared channel (SCH). SCI-1 information can be decoded by all UEs, while SCI-2 information may include formats that can only be decoded by certain UEs. This ensures that new features can be introduced in SCI-2 while maintaining backward compatibility for resource reservations in SCI-1.

[0149] Both SCI-1 and SCI-2 use the Physical Downlink Control Channel (PDCCH) polarity decoding chain, such as Figure 6 As shown. Figure 6 Figure 600 illustrates how a shared channel (SCH) is established on a side link between two or more UEs according to various aspects of this disclosure. Specifically, the network or the involved UE uses information in SCI-1 602 to perform resource allocation 604 for SCI-2 606 and SCH 608. Furthermore, information in SCI-1 602 is used to determine / decode the content of SCI-2 606 transmitted on the allocated resources. Therefore, the receiver UE requires both resource allocation 604 and SCI-1 602 to decode SCI-2 606. Information in SCI-2 606 is then used to determine / decode SCH 608.

[0150] The first 13 symbols of the time slot in the time domain and the allocated sub-channels in the frequency domain form the sidelink resource pool. The sidelink resource pool may include resources for sidelink communication (transmission and / or reception), sidelink positioning (referred to as the resource pool for positioning (RP-P)), or both communication and positioning. The resource pool configured for both communication and positioning is referred to as the "shared" resource pool. In the shared resource pool, the RP-P is indicated by offset, periodicity, the number of consecutive symbols within the time slot (e.g., as few as one symbol), and / or bandwidth within the component carriers (or bandwidth across multiple component carriers). Furthermore, the RP-P may be associated with a zone or with a distance from a reference location.

[0151] A base station (or UE, depending on the resource allocation mode) may assign one or more resource configurations from the RP-P to another UE. Alternatively, a UE (e.g., a relay or remote UE) may request one or more RP-P configurations, and the UE may include one or more of the following in the request: (1) the UE’s location information (or zone identifier), (2) periodicity, (3) bandwidth, (4) offset, (5) number of symbols, and (6) whether a “low interference” configuration is required (which can be determined by the assigned Quality of Service (QoS) or priority).

[0152] The base station or UE can configure / assign rate matching resources or RP-Ps for rate matching / silencing to the sidelink UE, such that when there is a conflict between the assigned resource and another resource pool containing data (PSSCH) and / or control (PSCCH), the sidelink UE is expected to perform rate matching / silencing / punching of data, DMRS, and / or CSI-RS within the conflicting resource. This will achieve orthogonality between positioning and data transmission to increase the coverage of PRS signals.

[0153] Figure 7 Figure 700 illustrates an example of a resource pool for location configured according to various aspects of this disclosure within a sidelink resource pool (i.e., a shared resource pool) for communication. Figure 7 In the example, time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one Orthogonal Frequency Division Multiplexing (OFDM) symbol, and 14 symbols constitute a time slot. In the frequency domain, the height of each block is a subchannel.

[0154] exist Figure 7 In the example, the entire time slot (excluding the first and last symbols) can be a resource pool for sidelink communication. That is, any symbol other than the first and last can be allocated for sidelink communication. However, the RP-P is allocated in the last four pre-gap symbols of the time slot. Therefore, non-sidelink positioning data (such as User Data (PSSCH), CSI-RS, and control information) can only be sent in the first eight AGC symbols, not in the last four pre-gap symbols, to prevent conflicts with the configured RP-P. Non-sidelink positioning data that would normally be sent in the last four pre-gap symbols can be pruned or silenced, or rate-matched non-sidelink data that typically spans more than eight AGC symbols can be used to accommodate eight AGC symbols.

[0155] Sidelink Positioning Reference Signal (SL-PRS) has been defined to support the sidelink positioning process between UEs. Similar to the downlink PRS (DL-PRS), an SL-PRS resource consists of one or more resource elements (i.e., an OFDM symbol in the time domain and a subcarrier in the frequency domain). SL-PRS resources are designed with a comb-based pattern to enable Fast Fourier Transform (FFT) based processing at the receiver. SL-PRS resources consist of uninterleaved or only partially interleaved resource elements in the frequency domain to provide small time-of-arrival (TOA) uncertainties and reduced overhead for each SL-PRS resource. SL-PRS can also be associated with a specific RP-P (e.g., some SL-PRS can be allocated in some RP-Ps). SL-PRS is also defined as having intra-slot repetition ( Figure 7 (not shown in the image) to allow for combined gain (if needed). RP-P inter-UE coordination may also exist to provide dynamic SL-PRS and data multiplexing while minimizing SL-PRS collisions.

[0156] During the positioning process, the UE assisting the target UE can be referred to as a "positioning peer" or "Pos-Peer" UE. Two types of positioning peer UE discovery procedures have been introduced for sidelink cooperative positioning, referred to as Mode A and Mode B. According to various aspects of this disclosure, Figure 8A Example call flow 800 for pattern A discovery is illustrated, and Figure 8BExample call flow 850 for Mode B discovery is illustrated. The purpose of these discovery procedures is to discover which location peer UEs are near the target UE. In Mode A, location peer UEs can announce their presence by broadcasting a sidelink location peer discovery message with a location flag, such as... Figure 8A As shown. In Mode B, a target UE that wishes to discover a location peer UE can initiate a peering request by broadcasting a sidelink location peering request message containing location-related fields, such as... Figure 8B As shown.

[0157] like Figure 8A and Figure 8B As shown, the location peer discovery and request messages can be divided into two parts labeled "A" and "B" to achieve a more power-efficient method and a handshake between the target UE and the potential location peer UE. The target UE can rank the potential location peer UE (also known as the anchor UE) according to the following criteria: (1) location quality criterion, (2) channel quality criterion, (3) response time criterion, (4) mobility status criterion, or any combination thereof.

[0158] NR supports or enables various sidelink positioning technologies. Figure 9A Various scenarios of interest, including sidelink-only positioning or joint Uu and sidelink positioning, are illustrated according to various aspects of this disclosure. In scenario 910, at least one peer UE with a known location can improve the Uu-based positioning of a target UE by providing additional anchors (e.g., using sidelink round-trip time (RTT) (SL-RTT)). In scenario 920, a low-end (e.g., a reduced-capability or “RedCap”) target UE can receive assistance from a high-end UE to determine its location using, for example, a sidelink positioning and ranging process with the high-end UE. Compared to the low-end UE, the high-end UE may have more capabilities, such as more sensors, a faster processor, more memory, more antenna elements, higher transmit power capabilities, access to additional frequency bands, or any combination thereof. In scenario 930, a relay UE (e.g., with a known location) participates in the positioning estimation of a remote UE without performing uplink positioning reference signal (PRS) transmission via the Uu interface. Scenario 940 illustrates joint positioning of multiple UEs. Specifically, in scenario 940, two UEs with unknown locations can co-locate under non-line-of-sight (NLOS) conditions by utilizing constraints from nearby UEs.

[0159] Figure 9BAdditional scenarios of interest are illustrated, including sidelink-only or combined Uu and sidelink positioning according to various aspects of this disclosure. In scenario 950, a UE used for public safety (e.g., by police, firefighters, etc.) may perform peer-to-peer (P2P) positioning and ranging for public safety and other purposes. For example, in scenario 950, a public safety UE may be outside network coverage and use sidelink positioning techniques to determine the location or relative distance and relative positioning between public safety UEs. Similarly, scenario 960 illustrates multiple UEs outside coverage and using sidelink positioning techniques such as SL-RTT to determine their location or relative distance and relative positioning.

[0160] Figure 10 Two resource allocation modes for transmission on the NR sidelink according to various aspects of this disclosure are illustrated. In the first mode 1010 (labeled "Mode 1"), base station 1002 (e.g., any of the base stations described herein) allocates time and / or frequency resources for sidelink communication between the involved V-UEs 1004 and 1006 (e.g., any of the V-UEs described herein or UEs with sidelink capability) via DCI 3_0. Each V-UE uses the allocated resources to transmit ranging signals (e.g., SL-PRS) to other V-UEs.

[0161] In Mode 1020 (labeled "Mode 2"), UEs 1004 and 1006 autonomously select sidelink resources for ranging signal transmission. V-UEs can use Mode 1 only when cellular coverage is available, and can use Mode 2 regardless of cellular coverage. It should be noted that although... Figure 10 Two V-UEs are illustrated, but as will be understood, they need not be V-UEs and can instead be any other type of UE capable of sidelink communication. Furthermore, more than the two illustrated V-UEs 1004 and 1006 may exist.

[0162] The signaling on the sidelink is identical between the two resource allocation modes. From the receiver's (e.g., V-UE1006) perspective, there is no difference between the modes. That is, it is not important to the receiver whether the resources used for ranging signals are allocated by the base station 1002 or the transmitter.

[0163] Mode 1 supports Dynamic Grant (DG), Configuration Grant (CG) Type 1, and CG Type 2. In some cases, CG Type 1 is activated via RRC signaling from base station 1002. In some cases, the modulation and decoding scheme (MCS) for sidelink transmission is determined by the involved V-UE 1004 and V-UE 1006 within constraints set by base station 1002. In Mode 2, the transmitting V-UE (e.g., V-UE 1004) performs channel sensing by blind decoding of all Physical Sidelink Control Channels (PSCCH) to determine resources reserved for other sidelink transmissions. The transmitting V-UE 1004 reports the available resources to its upper layer, which determines resource usage.

[0164] In addition, the NR sidelink supports Hybrid Automatic Repeat Request (HARQ) retransmission. In Mode 1, base station 1002 provides dynamic granting or active configuration sidelink granting for HARQ feedback. Sidelink feedback can be reported back to the base station by the sending UE (e.g., V-UE1004).

[0165] In some scenarios, the UE requesting the location of a target UE, the LCS client, or the application function (AF) knows when the location should be obtained. Some examples of this are as follows: Periodic location: The UE's location is obtained within a fixed periodic interval using the periodically delayed 5GC-MT-LR. Clearly, the positioning time is then known in advance.

[0166] IIot Location: In a factory or warehouse with moving tools, components, packages, etc., there may be a precise expectation of when the moving tools, components, or packages will arrive at a specific location or when a specific movement or operation will have been completed. Then, locating the tool, component, or package to confirm this expectation and make any further adjustments can be useful or critical.

[0167] Scheduled Location: The location of the UE can sometimes be scheduled to appear at a specific time in the future. For example, all vehicles on a road can be located simultaneously to provide indication of traffic congestion and assist V2X. People, containers, transportation systems, etc., can also be located at certain common times.

[0168] In the above scenarios, a known time, referred to as the scheduled location time, can be provided in advance to reduce the effective latency when providing location results.

[0169] Figure 11An example of the location preparation phase 1100 of the location estimation process according to various aspects of this disclosure is illustrated. At 1110, the LCS client transmits a location service request to the 5GC LCS entity for a location estimate of the UE at a future time T (denoted as, for example, T=12:34:0000Z). At 1120, the 5GC LCS entity forwards the location service request to the LMF. At 1130, the LMF schedules a location session so that the UE's location can be obtained / validated within the requested time T. For this purpose, operations 0 to 8 depict the location preparation phase for the location estimation process, for example: 1. LMF can use the LPP capability transfer procedure to request the positioning capability of the target device. 2. The LMF sends an NRPPa location information request message to the serving gNB to request UL information for the target device. 3. At operation 3a, the service gNB determines the resources available for UL-SRS and configures the target device with the UL-SRS resource set.

[0170] 4. The service gNB provides UL-SRS configuration information to the LMF in the NRPPa location information response message. Note: Whether SRS configuration is provided earlier than DL-PRS configuration depends on the specific implementation.

[0171] 5. In the case of semi-persistent or aperiodic SRS, the LMF can request activation of UE SRS transmission by sending an NRPPa location activation request message to the serving gNB of the target device. The gNB then activates UE SRS transmission and sends an NRPPa location activation response message. The target device begins UL-SRS transmission according to the time-domain behavior configured in the UL-SRS resource settings.

[0172] 6. The LMF provides UL information and an indication of time T' to the selected gNB in ​​the NRPPa Measurement Request message. This message includes all the information required for the gNB / TRP to perform the UL measurement.

[0173] 7. The LMF transmits an LPP (Assisted Data Provision) message to the target device. This message includes any auxiliary data required by the target device to perform the necessary DL-PRS measurements.

[0174] 8. The LMF transmits an LPP request location information message to request location measurements (e.g., TDOA, multiple RTT, AoA, etc.) and an indication of time T'.

[0175] Figure 12 Examples of various aspects according to this disclosure are illustrated. Figure 11 The location estimation process is executed in phase 1200. In one example: 9a: Target device execution originates from Figure 11 The DL-PRS measurements for all gNBs are provided in the auxiliary data at operation point 7.

[0176] 9b: In Figure 11 The operation of each gNB configured at point 6 measures the UE SRS transmission from the target device.

[0177] 10. The target device reports the DL-PRS measurement for multiple RTTs and the indication of time T'' to the LMF in the LPP location information message.

[0178] 11. Each gNB reports the UE SRS measurement and the indication of time T'' to the LMF in the NRPPa measurement response message.

[0179] 12. LMF sends an NRPPa location disabling message to the serving gNB.

[0180] 13. LMF determines the RTT from the UE and for... Figure 11 Operations 10 and 11 provide corresponding UL and DL measurements for each gNB and gNB Rx-Tx time difference, and calculate the positioning of the target device.

[0181] At 1210, the LMF sends a location service response to the 5GC LCS entity, and at 1220, the location service response is forwarded to the LCS client.

[0182] Figure 13 Depicting aspects related to this disclosure Figures 11 to 12 The timing information 1300 associated with the corresponding stage described in the text.

[0183] refer to Figure 13The location service request at 1110-1120 is configured to request the location of a target device at (future) T=12:34:0000Z. The LMF schedules the location process so that the UE location can be acquired / validated within the requested time T. The location preparation phase begins at T-t1, where t1 depends on the expected duration of the location preparation phase and on factors such as the selected location method. At operation 6, when a location measurement is to be acquired, the LMF provides the physical measurement time T' to the TRP and / or UE. Finally, t' defines the time when the target device location is valid / acquired. For example, T' may specify the SFN / time slot. T' has a 1:1 relationship with T (e.g., a 1:1 relationship with UTC). The UE / TRP performs the measurement so that the measurement / location is valid at time T'.

[0184] The location report at points 10 and 11 includes measurements / location estimates and a timestamp T'', where T'' is as close as possible to the requested time T', ideally T'' = T'. The location time error is δ = (T'' - T'). The client receives the target device location with timestamp T = 12:34:0000Z + δ at time T + t2 (i.e., at T = 12:34:0000Z + δ + t2), where t2 is the delay and δ is any error in the requested location time. The delay t2 observed by the client excludes the location preparation phase. Any UE movement during the delay t2 should have a negligible impact on the validity and accuracy of the location estimate; that is, the UE location at T is approximately the same as the UE location at T + t2.

[0185] In some designs, SCI Format 2-C is used to decode PSSCH and to provide or request inter-UE coordination information. SCI Format 2-C can only be used for unicast. The following information is transmitted using SCI Format 2-C: HARQ process ID - 4 digits New data indicator -1 bit Redundant version - 2 bits Source ID - 8 digits Destination ID - 16 digits HARQ Feedback Enable / Disable Indicator - 1 bit CSI Request - 1 bit Provide / request indicator -1 bit, where a value of 0 indicates that SCI format 2-C is used to provide inter-UE coordination information, and a value of 1 indicates that SCI format 2-C is used to request inter-UE coordination information. If the "Provide / Request Indicator" field is set to 0, then all remaining fields are set as follows: Resource Portfolio-2 ( +9+Y) bits, as defined in Clause 8.1.5 of [6,TS 38.214], where: If higher-level parameters sl-MultiReserveResource If configured, then Y =[log2 N rsv_period], and N rsv_period is a higher-level parameter sl-ResourceReservePeriodList The number of entries in; otherwise Y =0 N subChannel SL is determined by higher-level parameters. sl-NumSubchannel Number of sub-channels in the provided resource pool First resource position - 8th digit Reference slot position -(10+[log2(10) 2μ)]) position Resource set type -1 bit, where a value of 0 indicates a preferred resource set and a value of 1 indicates a non-preferred resource set.

[0186] Lowest subChannel index -2 [log2 N subChannel SL] position

[0187] In some designs, SL-ResourceReservePeriod is configured as follows:

[0188] In some designs, sl-ResourceReservePeriodList is configured in milliseconds as the set of possible resource reservation periods allowed in a resource pool. Up to 16 values ​​can be configured per resource pool. ms0 It is always configured.

[0189] Scheduled location sessions are used when the UE's location is expected at a specific future time. For example, all vehicles on a road can be located simultaneously to provide indication of traffic congestion and assist V2X. People, containers, transportation systems, etc., can also be located at certain common times. Scheduled location sessions are known within the Uu framework. However, the scheduling of sidelink resources for scheduled location estimation sessions is limited.

[0190] Various aspects of this disclosure relate to aperiodic sidelink resource reservation requests that request reservations for a set of time-frequency resources associated with a future time relative to a time reference offset, or alternatively, reservations for a set of time-frequency resources at a future absolute time. Such aspects can provide various technical advantages, such as flexible support for scheduled location estimation for sidelink-based location estimation sessions (e.g., which can facilitate location tracking that meets various application requirements for V2X, inventory tracking systems, etc.).

[0191] Figure 14 An exemplary process 1400 of communication according to one aspect of this disclosure is illustrated. Figure 14 The process 1400 is performed by the first UE (such as UE 302).

[0192] refer to Figure 14 At 1410, the first UE (e.g., transmitter 314 or 324, etc.) sends a first type of aperiodic sidelink resource reservation request to the second UE. In one aspect, the aperiodic sidelink resource reservation request requests reservations for a set of time-frequency resources associated with a future time relative to a time reference offset. In another aspect, the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and the second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options that is different from the first set of relative timing offset options.

[0193] refer to Figure 14 At 1420, the first UE (e.g., transmitter 314 or 324, receiver 312 or 322, etc.) communicates with the second UE on the time-frequency resource set according to an aperiodic sidelink resource reservation request.

[0194] Figure 15 An exemplary process 1500 of communication according to one aspect of this disclosure is illustrated. Figure 15 The process 1500 is performed by a second UE (such as UE 302).

[0195] refer to Figure 15At 1510, the second UE (e.g., receiver 312 or 322, etc.) receives a first type of aperiodic sidelink resource reservation request from the first UE. In one aspect, the aperiodic sidelink resource reservation request requests the reservation of a set of time-frequency resources associated with a future time relative to a time reference offset. In another aspect, the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and the second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options that is different from the first set of relative timing offset options.

[0196] refer to Figure 15 At 1520, the second UE (e.g., transmitter 314 or 324, receiver 312 or 322, etc.) communicates with the first UE on the time-frequency resource set according to the non-periodic sidelink resource reservation request.

[0197] refer to Figures 14 to 15 In some designs, the second set of relative timing offset options is a subset of the first set of relative timing offset options, or the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or the first set of relative timing offset options is defined in milliseconds, seconds, hours, or days, or any combination thereof.

[0198] refer to Figures 14 to 15 In some designs, the first type of aperiodic sidelink resource reservation request is associated with a sidelink-based location estimation session of a first UE, a second UE, or both. In one aspect, the sidelink-based location estimation session includes a location preparation phase and two or more location execution phases (e.g., Figure 11 A single instance, followed by Figure 12 (Multiple instances).

[0199] refer to Figures 14 to 15 In some designs, the maximum timing offset associated with the first set of relative timing offset options is based on a timing duration based on the subframe number (SFN). In some designs, the SFN-based timing duration corresponds to the subframe duration or superframe duration.

[0200] refer to Figures 14 to 15 In some designs, the time reference corresponds to the current time or a timing index based on the subframe number (SFN).

[0201] refer to Figures 14 to 15In some designs, the first type of non-periodic sidelink resource reservation request is sent by the first UE via a Media Access Control Command Element (MAC-CE) or via both MAC-CE and Sidelink Control Information (SCI) (and received by the second UE via either a Media Access Control Command Element (MAC-CE) or via both MAC-CE and Sidelink Control Information (SCI)).

[0202] refer to Figures 14 to 15 In some designs, the first UE further receives (and the second UE further transmits) resource availability information associated with the second UE, resource conflict information associated with the second UE, or both. In one aspect, the time-frequency resource set is selected based on resource availability information, resource conflict information, or both.

[0203] refer to Figures 14 to 15 In some designs, communication at 1420 or 1520 includes sending operations, receiving operations, or both.

[0204] refer to Figures 14 to 15 In a specific example, suppose the second set of relative timing offset options includes sl-ResourceReservePeriod1-r16 ENUMERATED {ms0, ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000}. In this case, in one example, these relative timing offset options can be extended from the first set of relative timing options, for example, sl-ResourceReservePeriod1-r16ENUMERATED {ms0, ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000, ms2000, ms4000, ms8000, ms16000}.

[0205] refer to Figures 14 to 15 In a specific example, a new IE can be defined for the first set of relative timing offset options, such as sl-ResourceReservePeriodHour-r18 INTEGER (1..99), or sl-ResourceReservePeriodmillsecond-r18 INTEGER (1..3600). 1000).

[0206] refer to Figures 14 to 15In a specific example, assuming the SFN rolls back after 1024 subframes, the maximum time span of the SFN loop is approximately 10.24 seconds. On one hand, utilizing the SFN time, the SL UE needs to ensure that the advance positioning session is within 10.24 seconds. For example, the maximum timing offset could be a timing index based on the SFN, such as 10.24 seconds (e.g., the UE could schedule the advance positioning session only with a maximum advance time of 10.24 seconds). On the other hand, the maximum timing offset could be a timing index based on the SFN, such as 2.84 hours (e.g., based on superframe duration or superframe number (HFN)). In this case, the UE could schedule the advance positioning session only with a maximum advance time of 2.84 hours.

[0207] refer to Figures 14 to 15 In a specific example, the client can tolerate a certain deviation relative to time T. On one hand, the tolerance level of LMF / anchor can be defined in msecs relative to a certain SFN (e.g., X msecs relative to SFN0).

[0208] Figure 16 An exemplary process 1600 of communication according to one aspect of this disclosure is illustrated. Figure 16 The process 1600 is performed by the first UE (such as UE 302).

[0209] refer to Figure 16 At 1610, the first UE (e.g., transmitter 314 or 324, etc.) sends an aperiodic sidelink resource reservation request to the second UE, which requests the reservation of a set of time-frequency resources at a future absolute time.

[0210] refer to Figure 16 At 1620, the first UE (e.g., transmitter 314 or 324, receiver 312 or 322, etc.) communicates with the second UE on the time-frequency resource set according to an aperiodic sidelink resource reservation request.

[0211] Figure 17 An exemplary process 1700 of communication according to one aspect of this disclosure is illustrated. Figure 17 The process 1700 is performed by a second UE (such as UE 302).

[0212] refer to Figure 17 At 1710, the second UE (e.g., receiver 312 or 322, etc.) receives an aperiodic sidelink resource reservation request, which requests the reservation of a set of time-frequency resources at a future absolute time.

[0213] refer to Figure 17At 1720, the second UE (e.g., transmitter 314 or 324, receiver 312 or 322, etc.) communicates with the first UE on the time-frequency resource set according to an aperiodic sidelink resource reservation request.

[0214] refer to Figures 16 to 17 In some designs, future absolute time is defined via Coordinated Universal Time (UTC). For example, there may be cases where both the SL UE and gNB have available UTC time. In such cases, as an example, both the SL UE and gNB can inform the LMF of this situation, which can facilitate advanced scheduling of sidelink location estimations on the order of days or longer.

[0215] refer to Figures 16 to 17 In some designs, non-periodic sidelink resource reservation requests are associated with a sidelink-based location estimation session of a first UE, a second UE, or both.

[0216] refer to Figures 16 to 17 In some designs, the first type of non-periodic sidelink resource reservation request is sent by the first UE via a Media Access Control Command Element (MAC-CE) or via both MAC-CE and Sidelink Control Information (SCI) (and received by the second UE via either a Media Access Control Command Element (MAC-CE) or via both MAC-CE and Sidelink Control Information (SCI)).

[0217] Figure 18 Examples of various aspects according to this disclosure are shown respectively. Figures 14 to 17 Example implementation 1800 of any of the processes in processes 1400 to 1700. At (1), UE-B sends a request to UE-A for preferred resources (or avoidance of non-preferred resources). At (2), UE-A sends an inter-UE coordination (IUC) signal (i.e., an aperiodic sidelink resource reservation request) to UE-B. At (3), UE-B performs a sidelink transmission (e.g., targeting UE-A and / or other sidelink UEs) on the resources selected based on the IUC signal. In some designs, in the resource avoidance IUC scheme, the UE includes which resources are non-preferred for use by others; in this case, the UE will include resources that the UE has already pre-scheduled (e.g., the IUC can convey to other nearby UEs that these specific resources should not be pre-scheduled by others). In some designs, in the conflict notification IUC scheme, the UE indicates that there is a conflict between a resource reserved by another UE and the UE's pre-scheduled reservation.

[0218] Figure 19 Examples of various aspects according to this disclosure are shown respectively. Figures 14 to 17Example implementation 1900 of any of the processes in processes 1400 to 1700. At (1), UE-A detects the triggering conditions for reserving resources. At (2), UE-A sends an inter-UE coordination (IUC) signal (i.e., an aperiodic sidelink resource reservation request) to UE-B. At (3), UE-B performs a sidelink transmission (e.g., targeting UE-A and / or other sidelink UEs) on the resources selected based on the IUC signal. In one aspect, in the case of a conflict notification IUC scheme, the IUC signal may be configured as a 1-bit indication indicating whether a particular resource will be conflicted. In another aspect, the IUC signal may be configured as a 1-bit indication indicating a set of preferred and / or non-preferred resources.

[0219] In some designs, IUC signaling is piggybacked on other data transmitted by UE-A. In some designs, IUC signaling is transmitted via MAC-CE or both MAC-CE and SCI-2C (e.g., SCI-2C reception is an optional feature, and the transmission of SCI-2C depends on the specific UE implementation in some designs; in some designs, SCI-2C is limited to unicast).

[0220] Figure 20 Examples of various aspects according to this disclosure are shown respectively. Figures 14 to 17 Example implementation of any of the processes in processes 1400 to 1700 in 2000. At (1), UE-A sends resource preferences to UE-B. At (2), UE-B selects resources for sidelink transmission based on resource preferences (e.g., therefore, if UE-B attempts to reserve resources, UE-B prefers to select preferred resources). At (3), UE-B and / or UE-A perform sidelink transmission on the preferred resources.

[0221] Figure 21 Examples of various aspects according to this disclosure are shown respectively. Figures 14 to 17 Example implementation of any of the procedures in processes 1400 to 1700 in 2000. At (1), UE-A and UE-B perform sidelink transmission, and UE-B attempts to reserve a resource. At (2), UE-B indicates a conflict with the resource that UE-B attempted to reserve. At (3), UE-B performs resource reselection (e.g., so that if UE-B attempts to reserve another resource, UE-B will reserve the reselected resource instead of the conflicting resource). At (4), UE-B and / or UE-A perform sidelink transmission on the reselected resource.

[0222] refer to Figures 14 to 17 In a specific example, the SL UE can receive advance reservations for SL resources. On one hand, the SL UE... Figure 18 or Figure 19The process includes non-preferred (or conflicting) resources, that is, resources that the SL UE has already received as "pre-scheduled" (e.g., to avoid other UEs trying to use those resources, i.e., to keep them reserved).

[0223] refer to Figures 14 to 17 In a specific example, if any other nearby SL UE uses the same resource in the future, then the SL UE can use... Figure 21 The process is to provide a conflict indicator for conflicting resource set A. In this case, another SL UE should remove / avoid transmission / reception on conflicting resource set A.

[0224] refer to Figures 14 to 17 In a specific example, suppose the first UE is determined as follows to provide conflict information in the PSFCH. If no resource pool is provided sl-TypeUE-A If the first UE has been instructed to use the first and second reserved resources as resources for PSSCH reception, or if the resource pool provides sl-TypeUE-A If the first UE has been instructed to use at least the first reserved resource or the second reserved resource for PSSCH reception, The detection includes the first priority value. The first SCI format 1-A and the first reserved resources for PSSCH transmission from the second UE, The detection includes the second priority value. The second SCI format 1-A and the second reserved resources for PSSCH transmission from the third UE, and Determine if the first and second resources overlap in time and frequency. PSFCH timing for conflict information between the second and third UEs is valid. if sl-IndicationUE-B If "Enabled", then the collision information receiver flag in SCI format 1-A from the second and third UEs is set to 1. Determining the first SCI format 1-A and the second SCI format 1-A no later than the PSFCH timing used for conflict information sl-MinTimeGapPSFCH Received Determine to send PSFCH with collision information to the second UE if Then, it is determined that a PSFCH with conflict information will be sent to the second or third UE. On the one hand, the UE may include a conflict indication if it detects the following: The first SCI format 1-A reserves the first reserved resource for transmission of SL-PRS from the second UE. as well as Indication (MAC-CE or higher layer (SLPP)) for advance scheduling of the same reserved resources for transmission of SL-PRS from a third UE.

[0225] On the other hand, the UE may include a conflict indication if it detects the following: Indication (MAC-CE or higher layer (SLPP)) for advance scheduling of the first reserved resources for transmission of SL-PRS from the second UE. as well as Indication (MAC-CE or higher layer (SLPP)) for advance scheduling of the same reserved resources for transmission of SL-PRS from a third UE.

[0226] Then, a conflict indication can be transmitted.

[0227] refer to Figures 14 to 17 In a specific example, a single location estimation session may include a single location execution phase and a single location preparation phase. On one hand, the location preparation phase includes resource sensing and selection. This configuration is suitable for latency use cases, but may not be optimal from a signaling and power perspective. On the other hand, multiple location execution phases can be executed for a given location preparation phase, for example: Position preparation phase (T-t1) Location execution phase (T) Location execution phase (T1) Position execution phase (T2) ... etc. In this scenario, both SL UE and LMF can support multiple location execution phases per location preparation phase.

[0228] As can be seen in the detailed description above, different features are grouped together in the examples. This manner of disclosure should not be construed as an intention to have more features than those explicitly mentioned in each clause. Rather, the various aspects of this disclosure may include fewer features than those in the individual example clauses disclosed. Therefore, the following clauses should be regarded accordingly as incorporated into the description, where each clause may serve as a separate example. Although each dependent clause may refer in the clause to a specific combination with one of the other clauses, the aspect of that dependent clause is not limited to that specific combination. It should be understood that other example clauses may also include combinations of aspects of a dependent clause with the subject matter of any other dependent or independent clause, or combinations of any feature with other dependent and independent clauses. The various aspects disclosed herein explicitly include these combinations unless explicitly stated or readily inferred that a particular combination is not intended for use (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). Furthermore, it is contemplated that aspects of a clause may be included in any other independent clause, even if that clause does not directly depend on the independent clause.

[0229] Specific implementation examples are described in the following numbered clauses: Clause 1. A method of operating a first user equipment (UE), the method comprising: sending a first type of aperiodic sidelink resource reservation request to a second UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources associated with a future time relative to a time reference offset, and wherein the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and a second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options different from the first set of relative timing offset options; and communicating with the second UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0230] Clause 2. The method according to Clause 1, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in milliseconds, seconds, hours, or days, or any combination thereof.

[0231] Clause 3. The method according to any one of Clauses 1 to 2, wherein the aperiodic sidelink resource reservation request of the first type is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

[0232] Clause 4. The method according to Clause 3, wherein the sidelink-based location estimation session includes a location preparation phase and two or more location execution phases.

[0233] Clause 5. The method according to any one of Clauses 1 to 4, wherein the maximum timing offset associated with the first set of relative timing offset options is based on a timing duration based on the subframe number (SFN).

[0234] Clause 6. The method according to Clause 5, wherein the timing duration based on SFN corresponds to the subframe duration or superframe duration.

[0235] Clause 7. The method according to any one of Clauses 1 to 6, wherein the time reference corresponds to the current time or a timing index based on the subframe number (SFN).

[0236] Clause 8. The method according to any one of Clauses 1 to 7, wherein the aperiodic sidelink resource reservation request of the first type is sent via a Media Access Control Command Element (MAC-CE) or via both MAC-CE and Sidelink Control Information (SCI).

[0237] Clause 9. The method according to any one of Clauses 1 to 8, the method further comprising: receiving resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the time-frequency resource set is selected based on the resource availability information, the resource conflict information, or both.

[0238] Clause 10. The method according to any one of Clauses 1 to 9, wherein the communication includes a sending operation, a receiving operation, or both.

[0239] Clause 11. A method of operating a second user equipment (UE), the method comprising: receiving from a first UE a first type of aperiodic sidelink resource reservation request, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources at a future time relative to a time reference offset, and wherein the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and a second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options different from the first set of relative timing offset options; and communicating with the first UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0240] Clause 12. The method according to Clause 11, the method further comprising: sending an indication to one or more other UEs of the reservation of the time-frequency resource set, or sending an indication that the time-frequency resource set is not preferred for the one or more other UEs.

[0241] Clause 13. The method according to any one of Clauses 11 to 12, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in milliseconds, seconds, hours, or days, or any combination thereof.

[0242] Clause 14. The method according to any one of Clauses 11 to 13, wherein the first type of aperiodic sidelink resource reservation request is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

[0243] Clause 15. The method according to Clause 14, wherein the sidelink-based location estimation session includes a location preparation phase and two or more location execution phases.

[0244] Clause 16. The method according to any one of Clauses 11 to 15, wherein the maximum timing offset associated with the first set of relative timing offset options is based on a timing duration based on the subframe number (SFN).

[0245] Clause 17. The method according to Clause 16, wherein the SFN-based timing duration corresponds to the subframe duration or superframe duration.

[0246] Clause 18. The method according to any one of Clauses 11 to 17, wherein the time reference corresponds to the current time or a timing index based on the subframe number (SFN).

[0247] Clause 19. The method according to any one of Clauses 11 to 18, wherein the aperiodic sidelink resource reservation request of the first type is received via a Media Access Control Command Element (MAC-CE) or via both MAC-CE and Sidelink Control Information (SCI).

[0248] Clause 20. The method according to any one of Clauses 11 to 19, the method further comprising: transmitting resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the time-frequency resource set is based on the resource availability information, the resource conflict information, or both.

[0249] Clause 21. The method according to any one of Clauses 11 to 20, wherein the communication includes a sending operation, a receiving operation, or both.

[0250] Clause 22. A method of operating a first user equipment (UE), the method comprising: sending an aperiodic sidelink resource reservation request to a second UE, the aperiodic sidelink resource reservation request requesting reservation of a set of time-frequency resources at a future absolute time; and communicating with the second UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request.

[0251] Clause 23. The method described in Clause 22, wherein the future absolute time is defined via Coordinated Universal Time (UTC).

[0252] Clause 24. The method according to any one of Clauses 22 to 23, wherein the aperiodic sidelink resource reservation request is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

[0253] Clause 25. The method according to any one of Clauses 22 to 24, wherein the aperiodic sidelink resource reservation request is sent via a Media Access Control Command Element (MAC-CE) or via both a MAC-CE and a Sidelink Control Message (SCI).

[0254] Clause 26. A method of operating a second user equipment (UE), the method comprising: receiving an aperiodic sidelink resource reservation request from a first UE, the aperiodic sidelink resource reservation request requesting reservation of a set of time-frequency resources at a future absolute time; and communicating with the first UE on the set of time-frequency resources in accordance with the aperiodic sidelink resource reservation request.

[0255] Clause 27. The method described in Clause 26, wherein the future absolute time is defined via Coordinated Universal Time (UTC).

[0256] Clause 28. The method according to any one of Clauses 26 to 27, wherein the aperiodic sidelink resource reservation request is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

[0257] Clause 29. The method according to any one of Clauses 26 to 28, the method further comprising: sending an indication to one or more other UEs of the reservation of the time-frequency resource set, or sending an indication that the time-frequency resource set is not preferred for the one or more other UEs.

[0258] Clause 30. The method according to any one of Clauses 26 to 29, wherein the aperiodic sidelink resource reservation request of the first type is received via a Media Access Control Command Element (MAC-CE) or via both MAC-CE and Sidelink Control Information (SCI).

[0259] Clause 31. A first user equipment (UE), the first user equipment (UE) comprising: one or more memories; and one or more processors communicatively coupled to the one or more memories, the one or more processors individually or in combination configured to: send a first type of aperiodic sidelink resource reservation request to a second UE, wherein the aperiodic sidelink resource reservation request requests reservations for a set of time-frequency resources associated with a future time relative to a time reference offset, and wherein the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and a second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options different from the first set of relative timing offset options; and communicate with the second UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0260] Clause 32. The UE as described in Clause 31, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in milliseconds, seconds, hours, or days, or any combination thereof.

[0261] Clause 33. The UE according to any one of Clauses 31 to 32, wherein the first type of aperiodic sidelink resource reservation request is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

[0262] Clause 34. The UE as described in Clause 33, wherein the sidelink-based location estimation session includes a location preparation phase and two or more location execution phases.

[0263] Clause 35. The UE pursuant to any one of Clauses 31 to 34, wherein the maximum timing offset associated with the first set of relative timing offset options is based on a timing duration based on the subframe number (SFN).

[0264] Clause 36. The UE as described in Clause 35, wherein the SFN-based timing duration corresponds to the subframe duration or superframe duration.

[0265] Clause 37. A UE pursuant to any one of Clauses 31 to 36, wherein the time reference corresponds to the current time or a timing index based on the subframe number (SFN).

[0266] Clause 38. The UE pursuant to any one of Clauses 31 to 37, wherein the aperiodic sidelink resource reservation request of the first type is sent via a Media Access Control Command Element (MAC-CE) or via both a MAC-CE and a Sidelink Control Message (SCI).

[0267] Clause 39. The UE according to any one of Clauses 31 to 38, wherein the one or more processors are further configured individually or in combination to: receive resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the time-frequency resource set is selected based on the resource availability information, the resource conflict information, or both.

[0268] Clause 40. The UE pursuant to any one of Clauses 31 to 39, wherein the communication includes a transmission operation, a reception operation, or both.

[0269] Clause 41. A second user equipment (UE), the second user equipment (UE) comprising: one or more memories; and one or more processors communicatively coupled to the one or more memories, the one or more processors individually or in combination configured to: receive from a first UE a first type of aperiodic sidelink resource reservation request, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources at a future time relative to a time reference offset, and wherein the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and a second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options different from the first set of relative timing offset options; and communicate with the first UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0270] Clause 42. The UE of claim 41, wherein the one or more processors are further configured individually or in combination to: send an indication of the reservation of the time-frequency resource set to one or more other UEs, or send an indication that the time-frequency resource set is not preferred for the one or more other UEs.

[0271] Clause 43. The UE pursuant to any one of Clauses 41 to 42, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in milliseconds, seconds, hours, or days, or any combination thereof.

[0272] Clause 44. The UE according to any one of Clauses 41 to 43, wherein the aperiodic sidelink resource reservation request of the first type is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

[0273] Clause 45. The UE as described in Clause 44, wherein the sidelink-based location estimation session includes a location preparation phase and two or more location execution phases.

[0274] Clause 46. The UE pursuant to any one of Clauses 41 to 45, wherein the maximum timing offset associated with the first set of relative timing offset options is based on a timing duration based on the subframe number (SFN).

[0275] Clause 47. The UE as described in Clause 46, wherein the SFN-based timing duration corresponds to the subframe duration or superframe duration.

[0276] Clause 48. A UE pursuant to any one of Clauses 41 to 47, wherein the time reference corresponds to the current time or a timing index based on the subframe number (SFN).

[0277] Clause 49. The UE pursuant to any one of Clauses 41 to 48, wherein the aperiodic sidelink resource reservation request of the first type is received via a Media Access Control Command Element (MAC-CE) or via both MAC-CE and Sidelink Control Information (SCI).

[0278] Clause 50. The UE according to any one of Clauses 41 to 49, wherein the one or more processors are further configured individually or in combination to: transmit resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the time-frequency resource set is based on the resource availability information, the resource conflict information, or both.

[0279] Clause 51. The UE according to any one of Clauses 41 to 50, wherein the communication includes a transmission operation, a reception operation, or both.

[0280] Clause 52. A user equipment (UE) comprising: one or more memories; and one or more processors communicatively coupled to the one or more memories, the one or more processors being individually or in combination configured to: send an aperiodic sidelink resource reservation request to a second UE, the aperiodic sidelink resource reservation request requesting reservation of a set of time-frequency resources at a future absolute time; and communicate with the second UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0281] Clause 53. The UE as described in Clause 52, wherein the future absolute time is defined via Coordinated Universal Time (UTC).

[0282] Clause 54. The UE pursuant to any one of Clauses 52 to 53, wherein the aperiodic sidelink resource reservation request is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

[0283] Clause 55. The UE pursuant to any one of Clauses 52 to 54, wherein the non-periodic sidelink resource reservation request is sent via a Media Access Control Command Element (MAC-CE) or via both a MAC-CE and a Sidelink Control Message (SCI).

[0284] Clause 56. A user equipment (UE) comprising: one or more memories; and one or more processors communicatively coupled to the one or more memories, the one or more processors being individually or in combination configured to: receive an aperiodic sidelink resource reservation request from a first UE, the aperiodic sidelink resource reservation request requesting reservation of a set of time-frequency resources at a future absolute time; and communicate with the first UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0285] Clause 57. The UE as described in Clause 56, wherein the future absolute time is defined via Coordinated Universal Time (UTC).

[0286] Clause 58. The UE pursuant to any one of Clauses 56 to 57, wherein the aperiodic sidelink resource reservation request is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

[0287] Clause 59. The UE according to any one of Clauses 56 to 58, wherein the one or more processors are further configured individually or in combination to: send an indication to one or more other UEs of the reservation of the time-frequency resource set, or send an indication that the time-frequency resource set is not preferred for the one or more other UEs.

[0288] Clause 60. The UE pursuant to any one of Clauses 56 to 59, wherein the aperiodic sidelink resource reservation request of the first type is received via a Media Access Control Command Element (MAC-CE) or via both MAC-CE and Sidelink Control Information (SCI).

[0289] Clause 61. A first user equipment (UE), the first user equipment (UE) comprising: means for sending a first type of aperiodic sidelink resource reservation request to a second UE, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources associated with a future time relative to a time reference offset, and wherein the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and a second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options different from the first set of relative timing offset options; and means for communicating with the second UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0290] Clause 62. The UE as described in Clause 61, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in milliseconds, seconds, hours, or days, or any combination thereof.

[0291] Clause 63. The UE according to any one of Clauses 61 to 62, wherein the aperiodic sidelink resource reservation request of the first type is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

[0292] Clause 64. The UE as described in Clause 63, wherein the sidelink-based location estimation session includes a location preparation phase and two or more location execution phases.

[0293] Clause 65. The UE pursuant to any one of Clauses 61 to 64, wherein the maximum timing offset associated with the first set of relative timing offset options is based on a timing duration based on the subframe number (SFN).

[0294] Clause 66. The UE as described in Clause 65, wherein the timing duration based on SFN corresponds to the subframe duration or superframe duration.

[0295] Clause 67. A UE pursuant to any one of Clauses 61 to 66, wherein the time reference corresponds to the current time or a timing index based on the subframe number (SFN).

[0296] Clause 68. The UE pursuant to any one of Clauses 61 to 67, wherein the aperiodic sidelink resource reservation request of the first type is sent via a Media Access Control Command Element (MAC-CE) or via both a MAC-CE and a Sidelink Control Message (SCI).

[0297] Clause 69. The UE according to any one of Clauses 61 to 68, the UE further comprising: a component for receiving resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the time-frequency resource set is selected based on the resource availability information, the resource conflict information, or both.

[0298] Clause 70. The UE pursuant to any one of Clauses 61 to 69, wherein the communication includes a transmission operation, a reception operation, or both.

[0299] Clause 71. A second user equipment (UE), the second user equipment (UE) comprising: means for receiving from a first UE a first type of aperiodic sidelink resource reservation request, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources at a future time relative to a time reference offset, and wherein the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and a second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options different from the first set of relative timing offset options; and means for communicating with the first UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0300] Clause 72. The UE according to Clause 71 further includes: means for sending an indication of the reservation of the time-frequency resource set to one or more other UEs, or means for sending an indication that the time-frequency resource set is not preferred for the one or more other UEs.

[0301] Clause 73. The UE pursuant to any one of Clauses 71 to 72, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in milliseconds, seconds, hours, or days, or any combination thereof.

[0302] Clause 74. The UE according to any one of Clauses 71 to 73, wherein the first type of aperiodic sidelink resource reservation request is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

[0303] Clause 75. The UE as described in Clause 74, wherein the sidelink-based location estimation session includes a location preparation phase and two or more location execution phases.

[0304] Clause 76. The UE pursuant to any one of Clauses 71 to 75, wherein the maximum timing offset associated with the first set of relative timing offset options is based on a timing duration based on the subframe number (SFN).

[0305] Clause 77. The UE as described in Clause 76, wherein the SFN-based timing duration corresponds to the subframe duration or superframe duration.

[0306] Clause 78. The UE pursuant to any one of Clauses 71 to 77, wherein the time reference corresponds to the current time or a timing index based on the subframe number (SFN).

[0307] Clause 79. The UE pursuant to any one of Clauses 71 to 78, wherein the aperiodic sidelink resource reservation request of the first type is received via a Media Access Control Command Element (MAC-CE) or via both MAC-CE and Sidelink Control Information (SCI).

[0308] Clause 80. The UE according to any one of Clauses 71 to 79, the UE further comprising: a component for transmitting resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the time-frequency resource set is based on the resource availability information, the resource conflict information, or both.

[0309] Clause 81. The UE pursuant to any one of Clauses 71 to 80, wherein the communication includes a transmission operation, a reception operation, or both.

[0310] Clause 82. A user equipment (UE) comprising: components for sending an aperiodic sidelink resource reservation request to a second UE, the aperiodic sidelink resource reservation request requesting reservation of a set of time-frequency resources at a future absolute time; and components for communicating with the second UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0311] Clause 83. The UE as described in Clause 82, wherein the future absolute time is defined via Coordinated Universal Time (UTC).

[0312] Clause 84. The UE pursuant to any one of Clauses 82 to 83, wherein the aperiodic sidelink resource reservation request is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

[0313] Clause 85. The UE pursuant to any one of Clauses 82 to 84, wherein the non-periodic sidelink resource reservation request is sent via a Media Access Control Command Element (MAC-CE) or via both a MAC-CE and a Sidelink Control Message (SCI).

[0314] Clause 86. A user equipment (UE) comprising: components for receiving an aperiodic sidelink resource reservation request from a first UE, the aperiodic sidelink resource reservation request requesting reservation of a set of time-frequency resources at a future absolute time; and components for communicating with the first UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0315] Clause 87. The UE as described in Clause 86, wherein the future absolute time is defined via Coordinated Universal Time (UTC).

[0316] Clause 88. The UE pursuant to any one of Clauses 86 to 87, wherein the aperiodic sidelink resource reservation request is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

[0317] Clause 89. The UE according to any one of Clauses 86 to 88, the UE further comprising: means for sending an indication of the reservation of the time-frequency resource set to one or more other UEs, or means for sending an indication that the time-frequency resource set is not preferred for the one or more other UEs.

[0318] Clause 90. The UE pursuant to any one of Clauses 86 to 89, wherein the aperiodic sidelink resource reservation request of the first type is received via a Media Access Control Command Element (MAC-CE) or via both MAC-CE and Sidelink Control Information (SCI).

[0319] Clause 91. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a first user equipment (UE), cause the UE to: send a first type of aperiodic sidelink resource reservation request to a second UE, wherein the aperiodic sidelink resource reservation request requests reservations for a set of time-frequency resources associated with a future time relative to a time reference offset, and wherein the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and a second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options different from the first set of relative timing offset options; and communicate with the second UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0320] Clause 92. A non-transitory computer-readable medium as described in Clause 91, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in milliseconds, seconds, hours, or days, or any combination thereof.

[0321] Clause 93. A non-transitory computer-readable medium according to any one of Clauses 91 to 92, wherein the aperiodic sidelink resource reservation request of the first type is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

[0322] Clause 94. The non-transitory computer-readable medium as described in Clause 93, wherein the sidelink-based location estimation session includes a location preparation phase and two or more location execution phases.

[0323] Clause 95. A non-transitory computer-readable medium according to any one of Clauses 91 to 94, wherein the maximum timing offset associated with the first set of relative timing offset options is based on a timing duration based on a subframe number (SFN).

[0324] Clause 96. The non-transitory computer-readable medium as described in Clause 95, wherein the SFN-based timing duration corresponds to the subframe duration or superframe duration.

[0325] Clause 97. A non-transitory computer-readable medium according to any one of Clauses 91 to 96, wherein the time reference corresponds to the current time or a timing index based on a subframe number (SFN).

[0326] Clause 98. A non-transitory computer-readable medium according to any one of Clauses 91 to 97, wherein the aperiodic sidelink resource reservation request of the first type is sent via a Media Access Control Command Element (MAC-CE) or via both a MAC-CE and a Sidelink Control Message (SCI).

[0327] Clause 99. A non-transitory computer-readable medium according to any one of Clauses 91 to 98, the non-transitory computer-readable medium further comprising computer-executable instructions, which, when executed by the UE, cause the UE to: receive resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the time-frequency resource set is selected based on the resource availability information, the resource conflict information, or both.

[0328] Clause 100. A non-transitory computer-readable medium pursuant to any one of Clauses 91 to 99, wherein the communication includes a sending operation, a receiving operation, or both.

[0329] Clause 101. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a second user equipment (UE), cause the UE to: receive from a first UE a first type of aperiodic sidelink resource reservation request, wherein the aperiodic sidelink resource reservation request requests reservation of a set of time-frequency resources at a future time relative to a time reference offset, and wherein the first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and a second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options different from the first set of relative timing offset options; and communicate with the first UE on the set of time-frequency resources according to the aperiodic sidelink resource reservation request.

[0330] Clause 102. The non-transitory computer-readable medium according to Clause 101 further includes computer-executable instructions that, when executed by the UE, cause the UE to: send an indication to one or more other UEs of the reservation of the time-frequency resource set, or send an indication that the time-frequency resource set is not preferred by the one or more other UEs.

[0331] Clause 103. A non-transitory computer-readable medium pursuant to any one of Clauses 101 to 102, wherein the second set of relative timing offset options is a subset of the first set of relative timing offset options, or wherein the first set of relative timing offset options is associated with a first information element (IE) and the second set of relative timing offset options is associated with a second IE, or wherein the first set of relative timing offset options is defined in milliseconds, seconds, hours, or days, or any combination thereof.

[0332] Clause 104. A non-transitory computer-readable medium according to any one of Clauses 101 to 103, wherein the first type of aperiodic sidelink resource reservation request is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

[0333] Clause 105. The non-transitory computer-readable medium as described in Clause 104, wherein the sidelink-based location estimation session includes a location preparation phase and two or more location execution phases.

[0334] Clause 106. A non-transitory computer-readable medium according to any one of Clauses 101 to 105, wherein the maximum timing offset associated with the first set of relative timing offset options is based on a timing duration based on a subframe number (SFN).

[0335] Clause 107. The non-transitory computer-readable medium as described in Clause 106, wherein the SFN-based timing duration corresponds to the subframe duration or superframe duration.

[0336] Clause 108. A non-transitory computer-readable medium pursuant to any one of Clauses 101 to 107, wherein the time reference corresponds to the current time or a timing index based on a subframe number (SFN).

[0337] Clause 109. A non-transitory computer-readable medium according to any one of Clauses 101 to 108, wherein the non-periodic sidelink resource reservation request of the first type is received via a Media Access Control Command Element (MAC-CE) or via both a MAC-CE and a Sidelink Control Message (SCI).

[0338] Clause 110. A non-transitory computer-readable medium according to any one of Clauses 101 to 109, the non-transitory computer-readable medium further comprising computer-executable instructions, which, when executed by the UE, cause the UE to: transmit resource availability information associated with the second UE, resource conflict information associated with the second UE, or both, wherein the time-frequency resource set is based on the resource availability information, the resource conflict information, or both.

[0339] Clause 111. A non-transitory computer-readable medium pursuant to any one of Clauses 101 to 110, wherein the communication includes a sending operation, a receiving operation, or both.

[0340] Clause 112. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), cause the UE to: send an aperiodic sidelink resource reservation request to a second UE, the aperiodic sidelink resource reservation request requesting reservation of a set of time-frequency resources at a future absolute time; and, according to the aperiodic sidelink resource reservation request, communicate with the second UE on the set of time-frequency resources.

[0341] Clause 113. The non-transitory computer-readable medium as described in Clause 112, wherein the future absolute time is defined via Coordinated Universal Time (UTC).

[0342] Clause 114. A non-transitory computer-readable medium according to any one of Clauses 112 to 113, wherein the non-periodic sidelink resource reservation request is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

[0343] Clause 115. A non-transitory computer-readable medium according to any one of Clauses 112 to 114, wherein the non-periodic sidelink resource reservation request is sent via a Media Access Control Command Element (MAC-CE) or via both a MAC-CE and a Sidelink Control Message (SCI).

[0344] Clause 116. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), cause the UE to: receive an aperiodic sidelink resource reservation request from a first UE, the aperiodic sidelink resource reservation request requesting reservation of a set of time-frequency resources at a future absolute time; and, in accordance with the aperiodic sidelink resource reservation request, communicate with the first UE on the set of time-frequency resources.

[0345] Clause 117. The non-transitory computer-readable medium as described in Clause 116, wherein the future absolute time is defined via Coordinated Universal Time (UTC).

[0346] Clause 118. A non-transitory computer-readable medium according to any one of Clauses 116 to 117, wherein the non-periodic sidelink resource reservation request is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

[0347] Clause 119. A non-transitory computer-readable medium according to any one of Clauses 116 to 118, the non-transitory computer-readable medium further comprising computer-executable instructions, which, when executed by the UE, cause the UE to: send an indication to one or more other UEs of the reservation of the time-frequency resource set, or send an indication that the time-frequency resource set is not preferred by the one or more other UEs.

[0348] Clause 120. A non-transitory computer-readable medium according to any one of Clauses 116 to 119, wherein the non-periodic sidelink resource reservation request of the first type is received via a Media Access Control Command Element (MAC-CE) or via both a MAC-CE and a Sidelink Control Message (SCI).

[0349] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and arts. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0350] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described above in general terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be construed as departing from the scope of this disclosure.

[0351] The various exemplary logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented or performed using a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternative embodiments, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0352] The methods, sequences, and / or algorithms described in conjunction with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or a combination of both. The software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. Example storage media are coupled to a processor such that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integral with the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., a UE). Alternatively, the processor and storage medium may reside as discrete components in the user terminal.

[0353] In one or more examples, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored as one or more instructions or code on or transmitted via a computer-readable medium. A computer-readable medium includes both computer storage media and communication media, which includes any medium that facilitates the transfer of a computer program from one place to another. A storage medium may be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and is accessible to a computer. Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of a medium. As used herein, disks and optical discs include: compact optical discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of these should also be included within the scope of computer-readable media.

[0354] While the foregoing disclosure illustrates exemplary aspects of this disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of this disclosure as defined by the appended claims. For example, the functions, steps, and / or actions of the method claims according to aspects of this disclosure described herein need not be performed in any particular order. Furthermore, no component, function, action, or instruction described or claimed herein should be construed as critical or essential unless explicitly stated otherwise. Additionally, as used herein, the terms “set,” “group,” etc., are intended to include one or more of the stated elements. Furthermore, as used herein, the terms “having,” “comprising,” “including,” etc., do not exclude the presence of one or more additional elements (e.g., element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be open-ended when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one”), or these alternatives are mutually exclusive (e.g., “one or more” should not be interpreted as “one and more”). Additionally, although components, functions, actions, and instructions may be described or claimed in the singular, plural forms may also be considered unless explicitly stated as singular. Therefore, as used herein, the articles “a,” “an,” “the,” and “the” are intended to include one or more of the described elements. Furthermore, as used herein, the terms “at least one” and “one or more” include “one” component, function, action, or instruction that performs or is capable of performing the described or claimed functionality, and also include “two or more” components, functions, actions, or instructions that perform or are capable of performing the described or claimed functionality in combination.

Claims

1. A method for operating a first user equipment (UE), the method comprising: Send a first type of aperiodic sidelink resource reservation request to the second UE. The aperiodic sidelink resource reservation request requests the reservation of a set of time-frequency resources associated with a future time relative to a time reference offset, and The first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and the second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options that are different from the first set of relative timing offset options. as well as Based on the non-periodic sidelink resource reservation request, communication is conducted with the second UE on the time-frequency resource set.

2. The method according to claim 1, The second set of relative timing offset options is a subset of the first set of relative timing offset options, or The first set of relative timing offset options is associated with a first information element (IE), and the second set of relative timing offset options is associated with a second IE, or The first set of relative timing offset options is defined in milliseconds, seconds, hours, or days, or Any combination of them.

3. The method of claim 1, wherein the first type of aperiodic sidelink resource reservation request is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

4. The method of claim 3, wherein the sidelink-based positioning estimation session includes a location preparation phase and two or more location execution phases.

5. The method of claim 1, wherein the maximum timing offset associated with the first set of relative timing offset options is based on a timing duration based on the subframe number (SFN).

6. The method according to claim 5, wherein the timing duration based on SFN corresponds to the subframe duration or superframe duration.

7. The method of claim 1, wherein the time reference corresponds to the current time or a timing index based on the subframe number (SFN).

8. The method of claim 1, wherein the first type of aperiodic sidelink resource reservation request is sent via a Media Access Control Command Element (MAC-CE) or via both MAC-CE and Sidelink Control Information (SCI).

9. The method according to claim 1, further comprising: Receive resource availability information associated with the second UE, resource conflict information associated with the second UE, or both. The time-frequency resource set is selected based on the resource availability information, the resource conflict information, or both.

10. The method of claim 1, wherein the communication includes a sending operation, a receiving operation, or both.

11. A method of operating a second user equipment (UE), the method comprising: Receive a first type of aperiodic sidelink resource reservation request from the first UE. The aperiodic sidelink resource reservation request requests the reservation of a set of time-frequency resources at a future time relative to a time reference offset, and The first type of aperiodic sidelink resource reservation request is associated with a first set of relative timing offset options, and the second type of aperiodic sidelink resource reservation request is associated with a second set of relative timing offset options that are different from the first set of relative timing offset options. as well as Based on the non-periodic sidelink resource reservation request, communication is performed with the first UE on the time-frequency resource set.

12. The method according to claim 11, further comprising: Send an indication of the reservation of the time-frequency resource set to one or more other UEs, or Sending the time-frequency resource set is an indication that the one or more other UEs are not preferred.

13. The method according to claim 11, The second set of relative timing offset options is a subset of the first set of relative timing offset options, or The first set of relative timing offset options is associated with a first information element (IE), and the second set of relative timing offset options is associated with a second IE, or The first set of relative timing offset options is defined in milliseconds, seconds, hours, or days, or Any combination of them.

14. The method of claim 11, wherein the first type of aperiodic sidelink resource reservation request is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

15. The method of claim 14, wherein the sidelink-based positioning estimation session includes a location preparation phase and two or more location execution phases.

16. The method of claim 11, wherein the maximum timing offset associated with the first set of relative timing offset options is based on a timing duration based on a subframe number (SFN).

17. The method of claim 16, wherein the timing duration based on SFN corresponds to the subframe duration or superframe duration.

18. The method of claim 11, wherein the time reference corresponds to the current time or a timing index based on a subframe number (SFN).

19. The method of claim 11, wherein the first type of aperiodic sidelink resource reservation request is received via a Media Access Control Command Element (MAC-CE) or via both MAC-CE and Sidelink Control Information (SCI).

20. The method according to claim 11, further comprising: Send resource availability information associated with the second UE, resource conflict information associated with the second UE, or both. The time-frequency resource set is based on the resource availability information, the resource conflict information, or both.

21. The method of claim 11, wherein the communication includes a sending operation, a receiving operation, or both.

22. A method of operating a first user equipment (UE), the method comprising: Send an aperiodic sidelink resource reservation request to the second UE, the aperiodic sidelink resource reservation request requesting the reservation of a set of time-frequency resources at a future absolute time; as well as Based on the non-periodic sidelink resource reservation request, communication is conducted with the second UE on the time-frequency resource set.

23. The method of claim 22, wherein the future absolute time is defined via Coordinated Universal Time (UTC).

24. The method of claim 22, wherein the aperiodic sidelink resource reservation request is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

25. The method of claim 22, wherein the aperiodic sidelink resource reservation request is sent via a Media Access Control Command Element (MAC-CE) or via both MAC-CE and Sidelink Control Information (SCI).

26. A method of operating a second user equipment (UE), the method comprising: The first UE receives an aperiodic sidelink resource reservation request, which requests the reservation of a set of time-frequency resources at a future absolute time. as well as Based on the non-periodic sidelink resource reservation request, communication is performed with the first UE on the time-frequency resource set.

27. The method of claim 26, wherein the future absolute time is defined via Coordinated Universal Time (UTC).

28. The method of claim 26, wherein the aperiodic sidelink resource reservation request is associated with a sidelink-based location estimation session of the first UE, the second UE, or both.

29. The method according to claim 26, further comprising: Send an indication of the reservation of the time-frequency resource set to one or more other UEs, or Sending the time-frequency resource set is an indication that the one or more other UEs are not preferred.

30. The method of claim 26, wherein the first type of aperiodic sidelink resource reservation request is received via a Media Access Control Command Element (MAC-CE) or via both MAC-CE and Sidelink Control Information (SCI).

Images