Channel occupancy time (COT) for sidelink positioning

Abstract

In one aspect, a sidelink (SL) device may obtain channel sensing information to determine availability of a channel for transmitting or measuring a positioning reference signal (PRS) for a positioning session. The SL may send an indication of at least one channel occupancy time (COT) window to one or more further SL devices for sending or measuring the PRS by the one or more further SL devices during the positioning session, wherein the at least one COT is based on the channel sensing information.

Description

TECHNICAL FIELD

[0001] Aspects of the disclosure relate generally to wireless communication. BACKGROUND

[0002] Wireless communication systems have developed through various generations, including first-generation analog wireless phone services, second-generation (2G) digital wireless phone services (including 2.5G and 2.75G networks), third-generation (3G) high speed data, Internet-capable wireless services, and fourth-generation (4G) services (e.g., Long-Term Evolution (LTE) or WiMax). There are now a number of different types of wireless communication systems in use, including cellular and personal communications service (PCS) systems. Examples of known cellular systems include the cellular Analog Advanced Mobile Phone System (AMPS), and 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), etc.

[0003] The fifth generation (5G) wireless standard, referred to as New Radio (NR), enables higher data transfer speeds, greater numbers of connections, and better coverage than previous standards. According to the Next Generation Mobile Networks Alliance, 5G technology should provide data transfer rates of several tens of megabits per second to each of several tens of users, with the ability to connect to hundreds of thousands of users in macro cells and provide service to tens of thousands of users in small cells. It should also be able to support more compact cells to increase network capacity.

[0004] In addition, with the increased data rates and reduced latency of 5G, vehicle-to-everything (V2X) communication technologies are being implemented to support autonomous driving applications, such as wireless communications between vehicles, between vehicles and roadside infrastructure, between vehicles and pedestrians, etc. SUMMARY

[0005] The following presents a simplified summary related to one or more aspects disclosed herein. Thus, the following summary should not be considered an extensive overview relating to all contemplated aspects, nor should the following summary be considered to identify key or critical elements relating to all contemplated aspects or to delineate the scope associated with any particular aspect. Accordingly, the following summary has the sole purpose to present certain concepts relating to one or more aspects disclosed herein in a simplified form to precede the detailed description presented below.

[0006] In one aspect, a method of wireless communication performed by a sidelink (SL) device includes obtaining channel sensing information to determine availability of a channel for transmitting or measuring positioning reference signals (PRSs) of a positioning session; and transmitting, to one or more additional SL devices, an indication of at least one channel occupancy time (COT) window for use by the one or more additional SL devices to transmit or measure the PRSs during the positioning session, where the at least one COT is based on the channel sensing information.

[0007] In one aspect, a method of wireless communication performed by a network server includes transmitting, to one or more sidelink (SL) devices, a first sensing threshold for use by the one or more SL devices in determining availability of a channel for transmitting or receiving data; and transmitting, to the one or more SL devices, a second sensing threshold for use by the one or more SL devices in determining the availability of a channel for transmitting or measuring positioning reference signals (PRSs) of a positioning session.

[0008] In one aspect, a method of wireless communication performed by a network server includes determining a plurality of channel occupancy time (COT) windows available for transmitting or receiving positioning reference signals (PRSs) of a positioning session; and transmitting a plurality of sets of assistance data for use during the positioning session, where each set of assistance data of the plurality of sets of assistance data is based on a corresponding COT window of the plurality of COT windows.

[0009] In one aspect, a sidelink (SL) device includes a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: obtain channel sensing information to determine availability of a channel for transmitting or measuring positioning reference signals (PRSs) of a positioning session; and transmit, to one or more additional SL devices via the at least one transceiver, an indication of at least one channel occupancy time (COT) window for use by the one or more additional SL devices to transmit or measure the PRSs during the positioning session, where the at least one COT is based on the channel sensing information.

[0010] In one aspect, a network server includes a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: transmit, via the at least one transceiver, a first sensing threshold to one or more sidelink (SL) devices for use by the one or more SL devices in determining availability of a channel for transmitting or receiving data; and transmit, via the at least one transceiver, a second sensing threshold to the one or more SL devices for use by the one or more SL devices in determining the availability of a channel for transmitting or measuring positioning reference signals (PRS) of a positioning session.

[0011] In one aspect, a network server includes a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: determine a plurality of channel occupancy time (COT) windows available for transmitting or receiving positioning reference signals (PRS) of a positioning session; and transmit, via the at least one transceiver, a plurality of sets of assistance data for use during the positioning session, wherein each set of assistance data of the plurality of sets of assistance data is based on a corresponding COT window of the plurality of COT windows.

[0012] In one aspect, a sidelink (SL) device includes means for obtaining channel sensing information to determine availability of a channel for transmitting or measuring positioning reference signals (PRS) of a positioning session; and means for transmitting, to one or more additional SL devices, an indication of at least one channel occupancy time (COT) window for use by the one or more additional SL devices in transmitting or measuring the PRS during the positioning session, wherein the at least one COT is based on the channel sensing information.

[0013] In one aspect, a network server includes means for transmitting, to one or more sidelink (SL) devices, a first sensing threshold for use by the one or more SL devices in determining availability of a channel for transmitting or receiving data; and means for transmitting, to the one or more SL devices, a second sensing threshold for use by the one or more SL devices in determining the availability of a channel for transmitting or measuring positioning reference signals (PRS) of a positioning session.

[0014] In one aspect, a network server includes means for determining a plurality of channel occupancy time (COT) windows available for transmitting or receiving positioning reference signals (PRS) of a positioning session; and means for transmitting a plurality of sets of assistance data for use during the positioning session, wherein each set of assistance data of the plurality of sets of assistance data is based on a corresponding COT window of the plurality of COT windows.

[0015] In one aspect, a non-transitory computer-readable medium stores computer- executable instructions that, when executed by a sidelink (SL) device, cause the SL device to: obtain channel sensing information to determine availability of a channel for transmitting or measuring a positioning reference signal (PRS) of a positioning session; and transmit, to one or more additional SL devices, an indication of at least one channel occupancy time (COT) window for use by the one or more additional SL devices to transmit or measure the PRS during the positioning session, wherein the at least one COT is based on the channel sensing information.

[0016] In one aspect, a non-transitory computer-readable medium stores computer- executable instructions that, when executed by a network server, cause the network server to: transmit, to one or more sidelink (SL) devices, a first sensing threshold for use by the one or more SL devices in determining availability of a channel for transmitting or receiving data; and transmit, to the one or more SL devices, a second sensing threshold for use by the one or more SL devices in determining the availability of a channel for transmitting or measuring a positioning reference signal (PRS) of a positioning session.

[0017] In one aspect, a non-transitory computer-readable medium stores computer- executable instructions that, when executed by a network server, cause the network server to: determine a plurality of channel occupancy time (COT) windows available for transmitting or receiving a positioning reference signal (PRS) of a positioning session; and transmit a plurality of sets of assistance data for use during the positioning session, wherein each set of assistance data of the plurality of sets of assistance data is based on a corresponding COT window of the plurality of COT windows.

[0018] Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. BRIEF DESCRIPTION OF DRAWINGS

[0019] The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration of the aspects and are not intended to limit the aspects in any way.

[0020] Figure 1 An example wireless communication system in accordance with aspects of the disclosure is illustrated.

[0021] Figure 2A 、 Figure 2B and Figure 2C An example wireless network structure in accordance with aspects of the disclosure is illustrated.

[0022] Figure 3A 、 Figure 3B and Figure 3Care simplified block diagrams of several example aspects of components that can be employed in user equipment (UE), base stations, and network entities, respectively, and configured to support communications as taught herein.

[0023] Figure 4 Examples of various positioning methods supported in New Radio (NR) are illustrated in accordance with aspects of the present disclosure.

[0024] Figure 5 is a diagram illustrating example downlink positioning reference signal (DL-PRS) configurations for two transmission reception points (TRPs) operating in the same positioning frequency layer in accordance with aspects of the present disclosure.

[0025] Figure 6A and Figure 6B Various scenarios of interest for sidelink-only positioning or joint Uu and sidelink positioning are illustrated in accordance with aspects of the present disclosure.

[0026] Figure 7 is a diagram illustrating example sidelink ranging and positioning procedures in accordance with aspects of the present disclosure.

[0027] Figure 8 A table showing examples of different sets of assistance data that can be used for a positioning session depicting different durations of a configured channel occupancy time (COT) window in accordance with aspects of the present disclosure is shown.

[0028] Figure 9 An example method of wireless communications performed by a network server in accordance with aspects of the present disclosure is illustrated.

[0029] Figure 10 An example method of wireless communications performed by a network server in accordance with aspects of the present disclosure is illustrated.

[0030] Figure 11 An example method of wireless communications performed by a network server in accordance with aspects of the present disclosure is illustrated.

[0031] Figure 12 is a table showing examples of sets of channel sensing parameters that can be associated with various channel access priority classes (CAPCs) in accordance with aspects of the present disclosure.

[0032] Figure 13 An example method of wireless communications performed by a sidelink (SL) device in accordance with aspects of the present disclosure is illustrated.

[0033] Figure 14 An example method of wireless communications performed by a SL device in accordance with aspects of the present disclosure is illustrated.

[0034] Figure 15Example methods of wireless communication performed by a SL device in accordance with aspects of the present disclosure are illustrated.

[0035] Figure 16 Example methods of wireless communication performed by a SL device in accordance with aspects of the present disclosure are illustrated. DETAILED DESCRIPTION

[0036] Aspects of the present disclosure are provided in the following description and related drawings, which are provided for illustrative purposes only and are not intended to limit the scope of the disclosure. Alternative aspects can be devised without departing from the scope of the disclosure. Additionally, well-known elements of the disclosure will not be described or will be omitted so as not to obscure the relevant details of the disclosure.

[0037] Various aspects generally relate to channel sensing and determining channel occupancy time (COT) for sidelink positioning. Some aspects more specifically relate to selecting a sidelink device to perform channel sensing and / or COT windows for transmission or measurement of positioning reference signals (PRS) by the sidelink device during a positioning session. In some examples, only a single sidelink device is assigned the task of channel sensing and / or COT windows used in a positioning session determination. In some examples, all sidelink devices in a positioning environment or a subset of less than all sidelink devices are assigned the task of channel sensing and / or COT computation. In some examples, channel sensing information and / or COT computation performed by a sidelink device is reported to a single entity that is responsible for a final determination of a COT window used in a positioning session. In some examples, the determination of which sidelink device will perform the COT window determination / final COT window determination and which sidelink devices will perform channel sensing and / or COT computation can be made by a sidelink device, an anchor device, a base station, a location server (e.g., location management function (LMF)).

[0038] Some aspects more specifically relate to using a sensing threshold for channel sensing that occurs for a positioning session that is different than a sensing threshold used for channel sensing in other contexts (e.g., data communications). In some examples, a network server (e.g., location server, LMF, etc.) determines a sensing threshold for channel sensing to determine a COT window for positioning. In some examples, a sidelink device receives a first channel sensing threshold for non-positioning COT window determination and a second channel sensing threshold for positioning COT window determination.

[0039] Some aspects more specifically relate to using different sets of assistance data for a positioning session based on COT window characteristics of a COT window. In some examples, the different sets of assistance data for a positioning session can depend on a duration of a COT window used to transmit or measure PRS. In some examples, the different sets of assistance data indicate different sidelink devices to use based on the duration of the COT window.

[0040] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, the described techniques can be used to reduce PRS transmission and measurement overhead (e.g., more efficiently use sidelink devices and / or radio frequency spectrum), while meeting positioning session requirements (e.g., latency, positioning estimate accuracy, etc.), by 1) customizing COT window determinations for a positioning session, 2) using channel sensing thresholds customized for the positioning COT window determinations, and / or 3) using different assistance data depending on characteristics of the COT window.

[0041] The words “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 preferred or advantageous over other aspects. Likewise, the term “aspects of the disclosure” does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation.

[0042] Those skilled in the art will understand that information and signals described below can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that can be referenced throughout the description below can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the particular applications, embodiments, and / or technologies involved, on the particular description being presented in this context, and / or on any combination thereof.

[0043] 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 to be 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 can be described herein as, for example, "logic configured to perform the described actions."

[0044] As used herein, the terms “user equipment” (UE), “vehicle UE” (V-UE), “pedestrian UE” (P-UE), and “base station” are not intended to be specific to or otherwise limited to any particular radio access technology (RAT) unless otherwise stated. In general, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., vehicle onboard computer, vehicle navigation device, mobile phone, router, tablet computer, laptop computer, asset location 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 “mobile device,” “access terminal” or “AT,” “client device,” “wireless device,” “subscriber equipment,” “subscriber terminal,” “subscriber station,” “user terminal” or UT,” “mobile terminal,” “mobile station,” or variations thereof.

[0045] A V-UE is a type of UE and can be any vehicular wireless communication device such as a navigation system, a warning system, a heads-up display (HUD), an on-board computer, an in-vehicle infotainment system, an autonomous driving system (ADS), an advanced driver-assistance system (ADAS), etc. Alternatively, a V-UE can be a portable wireless communication device (e.g., a cellular telephone, a tablet computer, etc.) carried by a driver of a vehicle or an occupant in the vehicle. The term “V-UE” can refer to either the vehicular wireless communication device or the vehicle itself, depending on the context. A P-UE is a type of UE and can be a portable wireless communication device carried by a pedestrian (i.e., a user that is not driving or riding in a vehicle). Collectively, UEs can communicate with one another, with core network, and / or with other devices (e.g., devices located on the Internet) through core network and / or RAN. Of course, other mechanisms of connecting to core network and / or the Internet are also possible for a UE, such as through a wired access network, a wireless local area network (WLAN) network (e.g., based on Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc.), and / or the like.

[0046] A base station can operate according to one of a number of RATs in communication with UEs in accordance with the network in which it is deployed, and can be alternatively referred to as an access point (AP), a network node, a NodeB, an evolved NodeB (eNB), a next generation eNB (ng-eNB), a new radio (NR) Node B (also referred to as gNB or gNodeB), etc. The base station can primarily function to support wireless access by UEs, including supporting voice, data, and / or signaling connections for the UEs. In some systems, the base station can only provide edge node signaling functions, while in other systems it can provide additional control and / or network management functions. A communication link through which UEs can send signals to the base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which the base station can send signals to UEs is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term “traffic channel” (TCH) can refer to UL / reverse or DL / forward traffic channels.

[0047] The term “base station” can refer to a single physical transmission-reception point (TRP) or multiple physical TRPs that can or can not be co-located. For example, where the term “base station” refers to a single physical TRP, the physical TRP can be an antenna of the base station corresponding to a cell (or cell sector) of the base station. Where the term “base station” refers to multiple co-located physical TRPs, the physical TRPs can be an array of antennas of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term “base station” refers to multiple non-co-located physical TRPs, the physical TRPs can be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs can be the serving base station receiving the measurement report from the UE and a neighbor base station whose reference radio frequency (RF) signals the UE is measuring. Because, as used herein, a TRP is a point from or to which the base station sends and receives wireless signals, references to transmissions from or receptions at a base station should be understood to refer to particular TRPs of the base station.

[0048] In some implementations that support positioning of UEs, a base station can not support wireless access by UEs (e.g., can not support data, voice, and / or signaling connections for UEs), but instead can transmit reference RF signals to UEs for measurement by the UEs and / or can receive and measure signals transmitted by the UEs. Such a base station can be referred to as a positioning beacon (e.g., where it transmits RF signals to UEs) and / or as a location measurement unit (e.g., where it receives and measures RF signals from UEs).

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

[0050] Figure 1An example wireless communications system 100 in accordance with aspects of the present disclosure is illustrated. The wireless communications system 100, which can also be referred to as a wireless wide area network (WW AN), can include various base stations 102, which can be referred to as gNBs, and various UEs 104. The base stations 102 can include macro cell base stations (high power cellular base stations) and / or small cell base stations (low power cellular base stations). In an aspect, the macro cell base station 102 can include eNBs and / or ng-eNBs (where the wireless communications system 100 corresponds to an LTE network) or gNBs (where the wireless communications system 100 corresponds to an NR network), or a combination of both, and the small cell base stations can include femto cells, pico cells, micro cells, and the like.

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

[0052] The base stations 102 can wirelessly communicate with the UEs 104 under the control of one or more base station controllers 106 to perform various aspects of the present disclosure, as will be described in more detail below. The base station 102 can communicate with one or more of the base station controllers 106 via a wired or wireless backhaul connection 134. The base station 102 can perform functions of a serving base station, a coordinating base station, a controlling base station, and / or the like. The base station 102 can also be used to perform functions of a maintenance and / or enhancement cell, e.g., in relation to positioning, as will be described in more detail below. The base station 102 can also be used to perform functions of a relay station, e.g., in relation to positioning, as will be described in more detail below. The base station 102 can also be used to perform functions of a measurement node, e.g., in relation to positioning, as will be described in more detail below. The base station 102 can also be used to perform functions of a location server, e.g., in relation to positioning, as will be described in more detail below. The base station 102 can also be used to perform functions of a location management function (LMF), e.g., in relation to positioning, as will be described in more detail below. The base station 102 can also be used to perform functions of a secure user plane location (SUPL) location platform (SLP), e.g., in relation to positioning, as will be described in more detail below.

[0053] The base stations 102 can wirelessly communicate with the UEs 104. Each of the base stations 102 can provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more of the cells can be supported by the base station 102 in each of the geographic coverage areas 110. A “cell” is a logical communication entity used for communication to a base station, e.g., through a certain frequency bandwidth, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc., and can be associated with an identifier unique within a cell group that is served by a base station, such as a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc. In some cases, different cells can be configured according to different protocol types, which can provide access for different types of UEs, such as machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types. Since a cell is supported by a particular base station, depending on the context, the term “cell” can refer to one or both of a logical communication entity and a base station that supports it. In some cases, the term “cell” can also refer to a geographic coverage area (e.g., a sector) of a base station as well, as long as a carrier frequency can be detected and used for communication within the geographic coverage area 110.

[0054] While the geographic coverage area 110 of a macro cell base station 102 can overlap with one or more other geographic coverage areas 110 of the same or different macro cell base stations 102 (as illustrated in FIG. 1A), and / or with one or more smaller cell geographic coverage areas 110 of a small cell base station 102' (as illustrated in FIG. IB), the coverage areas 110 of the same type of

[0055] The communication links 120 between the base stations 102 and the UEs 104 can include uplink (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 can use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links 120 can be through one or more carrier frequencies. Allocation of carriers can be asymmetric with respect to downlink and uplink (e.g., more or less carriers can be allocated for downlink than for uplink).

[0056] The wireless communications system 100 can also include a WLAN access point (AP) 150 in communication with WLAN station (STAs) 152 via communication link 154 in an unlicensed frequency spectrum (e.g., 5 GHz). When communicating in an unlicensed frequency spectrum, the WLAN STAs 152 and / or the WLAN AP 150 can perform clear channel assessment (CCA) or listen before talk (LBT) procedures prior to communicating to determine whether the channel is available.

[0057] The small cell base stations 102' can operate in a licensed spectrum and / or an unlicensed spectrum. When operating in an unlicensed spectrum, the small cell base stations 102' can employ LTE or NR technology and use the same 5 GHz unlicensed spectrum as used by the WLAN AP 150. The small cell base stations 102' employing LTE / 5G in an unlicensed spectrum can boost coverage and / or increase capacity of the access network. NR in unlicensed spectrum can be referred to as NR-U. LTE in unlicensed spectrum can be referred to as LTE-U, Licensed Assisted Access (LAA), or MulteFire.

[0058] The wireless communications system 100 can also include mmW base stations 180 that can operate in millimeter wave (mmW) frequencies and / or near mmW frequencies to communicate with UEs 182. Extremely high frequency (EHF) is the part of the radio frequency (RF) in the electromagnetic spectrum between 30 GHz and 300 GHz, also known as the millimeter band. Wireless communication in the EHF band is associated with wavelengths from 1 millimeter to 10 millimeters, also 1 cm to 10 cm. Radio waves in the EHF band tend to be blocked by buildings and other structures, and are generally unable to travel over long distances. The EHF band is ideal for short-range, high-bandwidth communication. The mmW base stations 180 and the UEs 182 can utilize beamforming (transmit and / or receive) to compensate for the extremely high path loss and short range of the EHF band. Further, it should be appreciated that in an alternative configuration, one or more base stations 102 can also transmit using mmW or near mmW and beamforming. Thus, it should be appreciated that the foregoing illustrative example is merely an example and should not be construed as limiting the various aspects disclosed herein.

[0059] Transmit beamforming is a technique used to focus the RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts a RF signal, it broadcasts the signal in all directions (omni-directionally). With 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, thereby providing a faster and stronger RF signal (in terms of data rate) for the receiving device. To change the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that broadcast the RF signal. For example, the network node can use an array of antennas (referred to as a “phased array” or “antenna array”), which forms a beam of RF waves that can be “steered” to point in different directions, without actually moving the antennas. Specifically, the RF current from the transmitter is fed to the individual antennas with the correct phase relationship so that the radio waves from the separate antennas add together to increase the radiation in a desired direction, while cancelling to suppress radiation in undesired directions.

[0060] Transmit beams can be quasi co-located, which means that they appear to have the same parameters at a receiver (e.g., a UE), regardless of whether the network node’s own transmit antennas are physically co-located. In NR, there are four types of quasi co-location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is QCL Type A, then 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, then 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, then 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 QCL Type D, then the receiver can use the source reference RF signal to estimate the spatial receive parameter of the second reference RF signal transmitted on the same channel.

[0061] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, the receiver can increase a gain setting and / or adjust a phase setting of an antenna array in a particular direction to amplify an RF signal received from that direction (e.g., increase its gain level). Thus, when a receiver is said to be beamformed in a certain direction, this means that the beam gain in that direction is high relative to the beam gain in other directions, or that the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. 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.

[0062] The transmit beam and the receive beam can be spatially related. Spatially related means that parameters for a second beam (e.g., a transmit beam or a receive beam) for a second reference signal can be derived from information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal. For example, a UE can use a particular 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 the base station based on parameters of the receive beam.

[0063] Note that depending on the entity forming the “downlink” beam, the beam can be a transmit beam or a receive beam. For example, if a base station is forming a downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. However, if a UE is forming a downlink beam, the downlink beam is a receive beam to receive a downlink reference signal. Similarly, depending on the entity forming the “uplink” beam, the beam can be a transmit beam or a receive beam. For example, if a base station is forming an uplink beam, the uplink beam is an uplink receive beam, while if a UE is forming an uplink beam, the uplink beam is an uplink transmit beam.

[0064] The electromagnetic spectrum is often subdivided based on frequency / wavelength into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 to 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub- 6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with respect to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

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

[0066] With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “Sub-6 GHz” or the like is used herein to generically refer to frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies, unless specifically stated otherwise. Further, unless specifically identified otherwise, it should be understood that the term “millimeter wave” or the like is used herein to generically refer to frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or can be within the EHF band.

[0067] In a multi-carrier system such as 5G, one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell" and the remaining carrier frequencies are referred to as "secondary carriers" or "secondary serving cells" or "SCells." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) used by the UE 104 / 182 in the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates a RRC connection reestablishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier in 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 the UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier can contain only necessary signaling information and signals, e.g., those that are UE-specific can not be present in the secondary carrier since both the primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 in a cell can have different downlink primary carriers. The same is true for the uplink primary carrier. The network is able to change the primary carrier for any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether a PCell or an SCell) corresponds to a carrier frequency / component carrier through which a certain base station communicates, the terms "cell," "serving cell," "component carrier," "carrier frequency," and the like can be used interchangeably.

[0068] For example, still referring to Figure 1 , one of the frequencies used by the macrocell base station 102 can be an anchor carrier (or "PCell") and other frequencies used by the macrocell base station 102 and / or mmW base station 180 can be secondary carriers ("SCells"). The simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz) compared to the data rate obtained with a single 20 MHz carrier.

[0069] In the example of Figure 1 , the illustrated UE (for simplicity, in Figure 1Any of the UEs 104 (shown as a single UE 104) can receive signals 124 from one or more Earth orbiting space vehicles (SVs) 112, such as satellites. In one aspect, the SVs 112 can be part of a satellite positioning system that the UEs 104 can use as a standalone source of location information. Satellite positioning systems typically include a system of transmitters (e.g., SVs 112) positioned in orbit about the Earth that enable a receiver (e.g., a UE 104) to determine its location on or above the Earth based, at least in part, on positioning signals (e.g., signals 124) received from the transmitters. Such transmitters typically transmit signals that are marked with a repeating pseudo-random noise (PN) code of a set number of chips. While typically located in SVs 112, transmitters can sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. The UEs 104 can include one or more specialized receivers designed specifically for receiving the signals 124 in order to derive geographic location information from the SVs 112.

[0070] In a satellite positioning system, the use of signals 124 can be augmented by various satellite-based augmentation systems (SBAS), which can be associated with one or more global and / or regional navigation satellite systems or which can otherwise enable the use of one or more global and / or regional navigation satellite systems. For example, an SBAS can include augmentation systems such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi

[0071] In one aspect, the SVs 112 additionally or alternatively can be part of one or more non-terrestrial networks (NTNs). In an NTN, the SVs 112 connect 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 a modified base station 102 (without a terrestrial antenna) or a network node in the 5GC. This element in turn will provide 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. In this way, the UEs 104 can receive communication signals (e.g., signals 124) from the SVs 112 as an alternative or supplement to communication signals from terrestrial base stations 102.

[0072] Vehicle-to-everything (V2X) communication technologies are being implemented to support intelligent transportation system (ITS) applications, such as wireless communications between vehicles (vehicle-to-vehicle (V2V)), between vehicles and roadside infrastructure (vehicle-to-infrastructure (V2I)), and between vehicles and pedestrians (vehicle-to-pedestrian (V2P)), with the increased data rates and reduced latency of NR, among other things. The goal is to enable vehicles to sense their surroundings and communicate that information to other vehicles, infrastructure, and personal mobile devices. Such vehicle communications will enable safety, mobility, and environmental advancements that current technology cannot provide. Once fully implemented, the technology is expected to reduce undamaged vehicle crashes by 80%.

[0073] Still referring to Figure 1 Wireless communications system 100 can include a plurality of V-UEs 160 that can communicate with base stations 102 using a Uu interface (i.e., the air interface between a UE and a base station) over communication links 120. V-UEs 160 can also communicate directly with one another over wireless sidelinks 162, with roadside units (RSUs) 164 (roadside access points) over wireless sidelinks 166, or with sidelink-capable UEs 104 over wireless sidelinks 168 using a PC5 interface (i.e., the air interface between sidelink-capable UEs). Wireless sidelinks (or simply “sidelinks”) are an adaptation of core cellular network (e.g., LTE, NR) standards that allow direct communication between two or more UEs without communicating through a base station. Sidelink communications can be unicast or multicast and can be used for device-to-device (D2D) media sharing, V2V communications, V2X communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more of the V-UEs 160 in a group utilizing sidelink communications can be within the geographic coverage area 110 of a base station 102. Other V-UEs 160 in such a group can be outside the geographic coverage area 110 of a base station 102 or be unable to receive transmissions from the base station 102 for other reasons. In some cases, groups of V-UEs 160 communicating via sidelink communications can utilize a one-to-many (1:M) system, where each V-UE 160 transmits to every other V-UE 160 in the group. In some cases, base station 102 facilitates scheduling of resources for sidelink communications. In other cases, sidelink communications are performed between V-UEs 160 without involvement of base station 102.

[0074] In one aspect, the sidelinks 162, 166, 168 can operate over a wireless communication medium of interest that can be shared with other wireless communications between other vehicles and / or infrastructure access points and other RATs. The "medium" can include one or more time, frequency, and / or space communication resources (e.g., encompassing one or more channels across one or more carriers) associated with wireless communications between one or more transmitter / receiver pairs.

[0075] In one aspect, the sidelinks 162, 166, 168 can be cV2X links. A first generation of cV2X has been standardized in LTE, and a next generation is expected to be defined in NR. cV2X is a cellular technology that also enables device-to-device communications. In the United States and Europe, cV2X is expected to operate in a licensed ITS band below 6 GHz. Other bands can be allocated in other countries. Thus, as a particular example, the medium of interest utilized by the sidelinks 162, 166, 168 can correspond to at least a portion of the licensed ITS band below 6 GHz. However, the present disclosure is not limited to this band or cellular technology.

[0076] In one aspect, the sidelinks 162, 166, 168 can be dedicated short-range communications (DSRC) links. DSRC is a one-way or two-way, short-to-medium range wireless communications protocol that uses the Wireless Access for Vehicular Environments (WAVE) protocol (also known as IEEE 802.1 Ip) for V2V, V2I, and V2P communications. IEEE 802.1 Ip is an approved amendment to the IEEE 802.11 standard and operates in a licensed ITS band of 5.9 GHz (5.85 GHz to 5.925 GHz) in the United States. In Europe, IEEE 802.1 Ip operates in the ITS G5A band (5.875 GHz to 5.905 MHz). Other bands can be allocated in other countries. V2V communications, briefly described above, occur on a safety channel, which is typically a 10 MHz channel dedicated for safety purposes in the United States. The remainder of the DSRC band (total bandwidth is 75 MHz) is intended for other services of interest to drivers, such as road rules, tolling, parking automation, etc. Thus, as a particular example, the medium of interest utilized by the sidelinks 162, 166, 168 can correspond to at least a portion of the licensed ITS band of 5.9 GHz.

[0077] Alternatively, the medium of interest can correspond to at least a portion of an unlicensed band that is shared among various RATs. Although different licensed frequency bands have been reserved for certain communication systems (e.g., by a government entity such as the Federal Communications Commission (FCC)), these systems, particularly those employing small cell access points, have recently extended operations into unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) band used by Wireless Local Area Network (WLAN) technologies, most notably the IEEE 802.1 lx WLAN technologies commonly referred to as“Wi-Fi.” Example systems of this type include different variations of CDMA systems, TDMA systems, FDMA systems, Orthogonal FDMA (OFDMA) systems, Single-Carrier FDMA (SC-FDMA) systems, etc.

[0078] Communications between V-UEs 160 are referred to as V2V communications, communications between a V-UE 160 and one or more RSUs 164 are referred to as V2I communications, and communications between a V-UE 160 and one or more UEs 104 (where these UEs 104 are P-UEs) are referred to as V2P communications. V2V communications between V-UEs 160 can include information regarding, for example, positioning, velocity, acceleration, heading, and other vehicle data for these V-UEs 160. V2I information received at a V-UE 160 from one or more RSUs 164 can include, for example, road rules, parking automation information, etc. V2P communications between a V-UE 160 and a UE 104 can include information regarding, for example, positioning, velocity, acceleration, and heading for the V-UE 160 and positioning, velocity (e.g., in cases where the UE 104 is carried by a user riding a bicycle), and heading for the UE 104.

[0079] Note that although Figure 1 Although only two of the UEs, the V-UEs 160, have been illustrated as V-UEs, any of the illustrated UEs (e.g., UEs 104, 152, 182, 190) can be a V-UE. Furthermore, although only these V-UEs 160 and a single UE 104 have been illustrated as being connected through sidelinks, any of the illustrated UEs (e.g., UEs 104, 152, 182, 190) can be connected through sidelinks. Figure 1Any of the UEs in the illustrated example, whether V-UEs, P-UEs, etc., can be capable of sidelink communication. Further, although only UE 182 is described as being capable of beamforming, any of the illustrated UEs, including the V-UEs 160, can be capable of beamforming. In cases where the V-UEs 160 are capable of beamforming, they can beamform toward one another (i.e., toward other V-UEs 160), toward the RSU 164, toward other UEs (e.g., UEs 104, 152, 182, 190), etc. Thus, in some cases, the V-UEs 160 can utilize beamforming on the sidelinks 162, 166, and 168.

[0080] The wireless communications system 100 can also include one or more UEs, such as UE 190, that are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. In the example of FIG. 1, UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which UE 190 can indirectly access cellular Figure 1 connections), and has a D2D P2P link 194 with the WLAN STA 152 connected to the WLAN AP 150 (through which UE 190 can indirectly access WLAN-based Internet connections). In one example, the D2D P2P links 192 and 194 can be supported with any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth, etc. As another example, the D2D P2P links 192 and 194 can be sidelinks, as described above with reference to the sidelinks 162, 166, and 168. ®

[0081] Figure 2A ​An example wireless network structure 200 is illustrated. For example, a 5GC 210 (also referred to as a Next Generation Core (NGC)) can be viewed functionally 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 function, access to data networks, IP

[0082] Another optional aspect can include a location server 230, which can be in communication with the 5GC 210 to provide location assistance for UEs 204. The location server 230 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternately can each correspond to a single server. The location server 230 can be configured to support one or more location services for UEs 204 that can be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). Moreover, the location server 230 can be integrated into a component of the core network, or alternately can be external to the core network (e.g., a third party server, such as an Original Equipment Manufacturer (OEM) server, or a service server).

[0083] Figure 2B Another example wireless network structure 240 is illustrated. A 5GC 260 (which can correspond to the 5GC 210) can be viewed functionally as control plane (C-plane) functions 264 (e.g., access and mobility management functions (AMF), unified data management (UDM), unified data management (UDR), authentication server function (AUSF), security anchor function (SEAF), network exposure function (NEF), policy control function (PCF), etc.) and user plane (U-plane) functions 262 (e.g., session management function (SMF), access and mobility management function (AMF), radio access network Figure 2AThe 5GC 210) can be viewed functionally as control plane functions provided by an access and mobility management function (AMF) 264, user plane functions provided by a user plane function (UPF) 262, which operate cooperatively to form the core network (i.e., 5GC 260). The functions of the AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transport for one or more UE 204 (e.g., any of the UEs described herein) session management (SM) messages between the UE 204 and a session management function (SMF) 266, transparent proxy services for routing SM messages, access authentication and authorization, transport for short message service (SMS) messages between the UE 204 and an SMS function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and

[0084] Functions of the UPF 262 include acting as an anchor point (when applicable) for intra- / inter-RAT mobility, acting as an external protocol data unit (PDU) session point of interconnect to data networks (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for 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 transmitting and forwarding of one or more “end markers.” The UPF 262 can also support transfer of location services messages between the UE 204 and a location server, such as the SLP 272, over the user plane.

[0085] Functions of the SMF 266 include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering at the UPF 262 for proper

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

[0087] Yet another optional aspect can include a third party server 274 that can communicate with the LMF 270, the SLP 272, the 5GC 260 (e.g., via the AMF 264 and / or the UPF 262), the NG-RAN 220, and / or the UE 204 to obtain location information (e.g., a location estimate) for the UE 204. Thus, in some cases, the third party server 274 can be referred to as a Location Services (LCS) client or an external client. The third party server 274 can be implemented as a number of 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 can each correspond to a single server.

[0088] The user plane interface 263 and control plane interface 265 connect the 5GC 260, and in particular the UPF 262 and AMF 264, respectively, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between gNBs 222 and / or ng-eNBs 224 and AMF 264 is referred to as the “N2” interface, while the interface between gNBs 222 and / or ng-eNBs 224 and UPF 262 is referred to as the “N3” interface. The gNBs 222 and / or ng-eNBs 224 of the NG-RAN 220 can communicate with one another directly via backhaul connections 223, referred to as the “Xn-C” interface. One or more of the gNBs 222 and / or ng-eNBs 224 can communicate with one or more UEs 204 over a wireless interface referred to as the “Uu” interface.

[0089] The functionality of the gNB 222 is divided among a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DUs) 228, and one or more gNB radio units (gNB-RUs) 229. The gNB-CU 226 is a logical node that includes base station functionality other than those functions specifically allocated to the gNB-DUs 228, including transfer of user data, mobility control, radio access network sharing, positioning, and session management, among others. More specifically, the gNB-CU 226 typically hosts the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB 222. The gNB-DUs 228 are logical nodes that typically host the radio link control (RLC) and medium access control (MAC) layers of the gNB 222. Their operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and the one or more gNB-DUs 228 is referred to as the “Fl” interface. The physical (PHY) layer functionality of the gNB 222 is typically hosted by one or more standalone gNB-RUs 229 that perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is referred to as the “Fx” interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC layer, the SDAP layer, and the PDCP layer, with the gNB-DU 228 via the RLC layer and the MAC layer, and with the gNB-RU 229 via the PHY layer.

[0090] Deployment of communication systems, such as 5G NR systems, can utilize various components or constituent parts arranged in a variety of ways. In a 5G NR system or network, a network node, network entity, mobility element of a network, RAN node, core network node, network element, or network equipment, such as a base station or one or more units (or one or more components) performing base station functionality, can be implemented in an aggregated or disaggregated architecture. For example, a base station, such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a transmission reception point (TRP), or a cell, among others, can be implemented as an aggregated base station (also referred to as a standalone base station or a monolithic base station) or a disaggregated base station.

[0091] A disaggregated base station can be configured to utilize a radio protocol stack integrated physically or logically within a single RAN node. A disaggregated base station can be configured to utilize a protocol stack distributed physically or logically 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 aspects, a CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU or, alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DUs can be implemented to be in communication with one or more RUs. Each of the CU, DU, and RU can also be implemented as virtual units, i.e., a virtual central unit (VCU), virtual distributed unit (VDU), or virtual radio unit (VRU).

[0092] Base station type operations or network designs can take into account the disaggregated nature of base station functionality. For example, a disaggregated base station can be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also referred to as a cloud radio access network (C-RAN)). Disaggregation can include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which can enable flexibility in network design. The various units of a disaggregated base station or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0093] Figure 2C An example disaggregated base station architecture 250 is illustrated in accordance with aspects of the present disclosure. The disaggregated base station architecture 250 can include one or more central units (CUs) 280 (e.g., gNB-CUs 226) that can communicate with a core network 267 (e.g., 5GC 210, 5GC 260) directly via a backhaul link or indirectly through 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. The CUs 280 can communicate with one or more distributed units (DUs) 285 (e.g., gNB-DUs 228) via respective fronthaul links, such as F1 interfaces. The DUs 285 can communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective front-haul links. The RUs 287 can communicate with respective UEs 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 can be simultaneously served by multiple RUs 287.

[0094] Each of these units (i.e., CU 280, DU 285, RU 287, and near-RT RIC 259, non-RT RIC 257, and SMO framework 255) can 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 mediums. The associated processor or controller providing instructions to the communication interfaces of each of these units or to these units can be configured to communicate with one or more of the other units via the transmission mediums. For example, the units can include wired interfaces configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Additionally, the units can include wireless interfaces, which can include receivers, transmitters, or transceivers (such as radio frequency (RF) transceivers) configured to receive or transmit signals to one or more of the other units over a wireless transmission medium, or both.

[0095] In some aspects, the CU 280 can host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), or service data adaptation protocol (SDAP), among others. Each control function can utilize an interface configured to communicate signals 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 bi-directionally with the CU-CP units via an interface, such as an El interface. The CU 280 can be implemented to communicate with the DU 285 as needed for network control and signaling.

[0096] The DU 285 can correspond to a logical unit that includes one or more base station functions for controlling operation of one or more RUs 287. In some aspects, the DU 285 can host, at least in part depending on a functional split, such as one defined by the Third Generation Partnership Project (3GPP), one or more of a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and one or more high physical (PHY) layers, such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 285 can also host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 285 or with control functions hosted by the CU 280.

[0097] Lower layer functionality can be implemented by one or more RUs 287. In some deployments, an RU 287 controlled by a DU 285 can 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, etc., or both, based at least in part on a functional split, such as a lower layer functional split. In such an architecture, the RU 287 can be implemented to handle over-the-air (OTA) communications with one or more UEs 204. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 287 can be controlled by the corresponding DU 285. In some scenarios, this configuration can enable the DUs 285 and CUs 280 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0098] The SMO framework 255 can be configured to support RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non- virtualized network elements, the SMO framework 255 can be configured to support deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface, such as an Ol interface. For virtualized network elements, the SMO framework 255 can be configured to interact with a cloud computing platform, such as Open Cloud (O-Cloud) 269, to perform network element lifecycle management, such as to instantiate virtualized network elements, via a cloud computing platform interface, such as an 02 interface. Such virtualized network elements can include, but are not limited to, CUs 280, DUs 285, RUs 287, and near-RT RICs 259. In some implementations, the SMO framework 255 can communicate with hardware aspects of a 4G RAN, such as Open eNB (O-eNB) 261, via an Ol interface. Additionally, in some implementations, the SMO framework 255 can communicate directly with one or more RUs 287 via an Ol interface. The SMO framework 255 can also include a non-RT RIC 257 configured to support functionality of the SMO framework 255.

[0099] The non-RT RIC 257 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based direction of applications / features in the near-RT RIC 259. The non-RT RIC 257 can be coupled to, or in communication with, the near-RT RIC 259, such as via an Al interface. The near-RT RIC 259 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions through interfaces, such as via an E2 interface, that connect one or more CUs 280, one or more DUs 285, or both, and an O-eNB with the near-RT RIC 259.

[0100] 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).

[0101] 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 2B Several 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. Moreover, 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.

[0102] The UE 302 and the base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, which provide components (e.g., components for transmitting, for receiving, for measuring, for tuning, for refraining from transmitting, etc.) for communicating over one or more wireless communication networks, such as NR network, an LTE network, and / or a GSM network, etc. (not shown). The WWAN transceivers 310 and 350 can each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc., via at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communication medium (e.g., a set of time / frequency resources in a particular frequency spectrum) of interest. The WWAN transceivers 310 and 350 can be variously configured for transmitting and encoding signals 318 and 358 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 318 and 358 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352, respectively, for receiving and decoding signals 318 and 358, respectively.

[0103] At least in some cases, the UE 302 and the base station 304 each also include one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide components (e.g., components for transmitting, for receiving, for measuring, for tuning, for refraining from transmitting, etc.) for communicating via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth, Zigbee, Z-Wave, etc.) over a wireless communication medium (e.g., a set of time / frequency resources in a particular frequency spectrum) of interest. The short-range wireless transceivers 320 and 360 can be variously configured for transmitting and encoding signals 328 and 368 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 328 and 368 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368, respectively. ® ® ® ​​, PC5, dedicated short-range communications (DSRC), wireless access for vehi cl e environments (WAVE), near-field communications (NFC), ultra-wideband (UWB), etc.) to communicate with other network nodes (such as other UEs, access points, base stations, etc.). The short-range wireless transceivers 320 and 360 can be variously configured for transmitting and encoding signals 328 and 368 (e.g., messages, indications, information, etc.), respectively, and vice-versa, in accordance with a designated RAT. Specifically, the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 320 and 360 can be WiFi transceivers, Bluetooth ® ® ® Zigbeeand / or Z-Wave transceivers, NFC transceivers, UWB transceivers, or vehicle-to- vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

[0104] At least in some cases, the UE 302 and the base station 304 also include satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 can be connected to one or more antennas 336 and 376, respectively, and can provide means for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. In cases where the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 can be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigational Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. In cases where the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 can be communication signals (e.g., carrying control and / or user data) originating from a 5G network. The 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. The satellite signal receivers 330 and 370 can request information and operations as appropriate to other systems, and, at least in some cases, perform calculations using measurements obtained by any suitable satellite positioning system algorithm to determine the location of the UE 302 and the base station 304, respectively.

[0105] ​The base stations 304 and network entities 306 each include one or more network transceivers 380 and 390, respectively, that provide means for communicating (e.g., means for transmitting, means for receiving, etc.) with other network entities (e.g., other base stations 304, other network entities 306) over a network. For example, a base station 304 can employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 over one or more wired or wireless backhaul links. As another example, a network entity 306 can employ one or more network transceivers 390 to communicate with one or more base stations 304 over one or more wired or wireless backhaul links, or with other network entities 306 over one or more wired or wireless core network interfaces.

[0106] Transceivers can be configured to communicate over wired or wireless links. Transceivers, whether wired or wireless, include transmitter circuitry (e.g., the transmitters 314, 324, 354, 364) and receiver circuitry (e.g., the receivers 312, 322, 352, 362). In some implementations, the transceivers can be integrated devices (e.g., implementing the transmitter circuitry and receiver circuitry in a single device), can include separate transmitter circuitry and separate receiver circuitry in some implementations, or can be implemented in other manners in other implementations. The transmitter circuitry and receiver circuitry of wired transceivers (e.g., the network transceivers 380 and 390, in some implementations) can be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., the transmitters 314, 324, 354, 364) can include or be coupled to a plurality of antennas (e.g., the antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus (e.g., the UE 302, the base station 304) to perform transmit “beamforming,” as described herein. Similarly, the wireless receiver circuitry (e.g., the receivers 312, 322, 352, 362) can include or be coupled to a plurality of antennas (e.g., the antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus (e.g., the UE 302, the base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter circuitry and receiver circuitry can share the same plurality of antennas (e.g., the antennas 316, 326, 356, 366) such that the respective apparatus can only receive or transmit at a given moment, rather than both transmit and receive at the same time. Wireless transceivers (e.g., the WWAN transceivers 310 and 350, the short-range wireless transceivers 320 and 360) can also include a network listen module (NLM) or the like for performing various measurements.

[0107] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360, and network transceivers 380 and 390 in some implementations, and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) can be generally referred to as “transceivers,” “at least one transceiver,” or “one or more transceivers.” Thus, whether a particular transceiver is a wired or wireless transceiver can be inferred from the type of communication being performed. For example, backhaul communications between network devices or servers typically involve signaling via wired transceivers, while wireless communications between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via wireless transceivers.

[0108] UE 302, base station 304, and network entity 306 also include other components that can be beneficial in conjunction with the operations disclosed herein. UE 302, base station 304, and network entity 306 each include one or more processors 332, 384, and 394 for providing functionality

[0109] The UE 302, the base stations 304, and the network entity 306 each include memory circuitry implementing memory 340, 386, and 396 (e.g., including a memory device, respectively) to maintain information (e.g., information indicative of reserved resources, thresholds, parameters, etc.). Thus, the memory 340, 386, and 396 can provide a means for storing, a means for retrieving, a means for maintaining, etc. In some cases, the UE 302, the base stations 304, and the network entity 306 can each include a positioning component 342, 388, and 398, respectively. The positioning component 342, 388, and 398 can be hardware circuits that are part of, or coupled to, the processor 332, 384, and 394, respectively, which when executed, cause the UE 302, the base stations 304, and the network entity 306 to perform the functionality described herein. In other aspects, the positioning component 342, 388, and 398 can be external to the processor 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning component 342, 388, and 398 can be memory modules stored in the memory 340, 386, and 396, respectively, which when executed by the processor 332, 384, and 394 (or a modem processing system, another processing system, etc.) cause the UE 302, the base stations 304, and the network entity 306 to perform the functionality described herein. Figure 3A Possible locations for the positioning component 342 are illustrated, which can be part of, for example, the one or more WWAN transceivers 310, the memory 340, the one or more processors 332, or any combination thereof, or can be a standalone component. Figure 3B Possible locations for the positioning component 388 are illustrated, which can be part of, for example, the one or more WWAN transceivers 350, the memory 386, the one or more processors 384, or any combination thereof, or can be a standalone component. Figure 3C Possible locations for the positioning component 398 are illustrated, which can be part of, for example, the one or more network transceivers 390, the memory 396, the one or more processors 394, or any combination thereof, or can be a standalone component.

[0110] The UE 302 can include one or more sensors 344 coupled to the one or more processors 332 to provide means for sensing or detecting movement and / or orientation information unrelated to motion data derived from signals received by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, and / or the satellite signal receiver 330. By way of example, the sensors 344 can include an accelerometer (e.g., a micro-electrical mechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of movement detection sensor. Moreover, the sensors 344 can include multiple different types of devices and combine their outputs in order to provide motion information. For example, the sensors 344 can use a combination of a multi-axis accelerometer and orientation sensors to provide the ability to calculate positioning in two-dimensional (2D) and / or three-dimensional (3D) coordinate systems.

[0111] Further, the UE 302 includes a user interface 346 that provides means for providing indications (e.g., audible and / or visual indications) to a user and / or for receiving user input (e.g., upon the user actuating a sensing device, such as a keypad, a touch screen, a microphone, etc.). Although not shown, the base station 304 and the network entity 306 can also include user interfaces.

[0112] Referring to the one or more processors 384 in more detail, in the downlink, IP packets from the network entity 306 can be provided to the processor 384. The one or more processors 384 can implement functionality for a RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The one or more processors 384 can provide RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information blocks (SIBs)), 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 (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation 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 prioritization.

[0113] The transmitter 354 and receiver 352 can implement layer 1 (LI) functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, can include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols are then split into parallel streams. Each stream can then be mapped to a orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator can be used to determine the spatial processing and / or beamforming

[0114] At the UE 302, the receiver 312 receives a signal through its respective antenna 316. The receiver 312 recovers information modulated onto an RF carrier and provides the information to the one or more processors 332. The transmitter 314 and the receiver 312 implement layer 1 functionality associated with various signal processing functions. The receiver 312 can perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they can be combined by the receiver 312 into a single OFDM symbol stream. The receiver 312 then converts the OFDM symbol stream from the time-domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 304. These soft decisions can be based on channel estimates computed by a channel estimator. The soft decisions are then decoded and de-interleaved to recover the data and control signals that were originally transmitted on the physical channel. The data and control signals are then provided to the one or more processors 332, which implement layer 3 (L3) and layer 2 (L2) functionality.

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

[0116] Similar to the functionality described in connection with the downlink transmission by the base station 304, the one or more processors 332 provide RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transmission channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0117] Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station 304 can be used by the transmitter 314 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the transmitter 314 can be provided to different antenna 316. The transmitter 314 can modulate an RF carrier with a respective spatial stream for transmission.

[0118] The uplink transmissions are processed at the base station 304 in a manner similar to that described in connection with the receiver function at the UE 302. The receiver 352 receives information from its respective antenna 356. The receiver 352 recovers the information modulated onto the RF carrier and provides the information to the one or more processors 384.

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

[0120] For convenience, the UE 302, base station 304, and / or network entity 306 are referred to as Figure 3A , Figure 3B and Figure 3CThe example shown herein includes 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, PCs, or laptops may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), or short-range wireless transceiver 320 (e.g., cellular only), or satellite signal receiver 330, or sensor 344, etc. In another 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, and so on. 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.

[0121] 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 the different logical entities.

[0122] 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 3CThe components of the network entity 306 can be implemented in one or more circuits such as, for example, one or more processors and / or ASICs (which can include one or more processors). Here, each circuit can use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide functionality. For example, some or all of the functionality represented by blocks 390-398 can be implemented by processor and memory components of the network entity 306 (e.g., by execution of appropriate code and / or by appropriate configuration of processor components). For simplicity, various operations, acts, and / or functions are described herein as being performed by a UE, a base station, a network entity, and / or the like. However, as will be appreciated, such operations, acts, and / or functions can actually be performed by specific components or combinations of components of the UE 302, the base station 304, the network entity 306, and / or the like, such as the processors 332, 384, 394, the transceivers 310, 320, 350, and 360, the memories 340, 386, and 396, the positioning components 342, 388, and 398, and / or the like.

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

[0124] NR supports multiple cellular network-based positioning techniques, including downlink-based positioning methods, uplink-based positioning methods, and downlink- and uplink-based positioning methods. Downlink-based positioning methods include observed time difference of arrival (OTDOA) in LTE, downlink time difference of arrival (DL-TDOA) in NR, and downlink angle of departure (DL-AoD) in NR. Figure 4Examples of various positioning methods in accordance with aspects of the present disclosure are illustrated. In the OTDOA or DL-TDOA positioning procedure illustrated in scenario 410, a UE measures the differences between the times of arrival (ToAs) of reference signals (e.g., Positioning Reference Signals (PRS)) received from pairs of base stations (referred to as Reference Signal Time Difference (RSTD) or Time Difference of Arrival (TDOA) measurements) and reports these differences to a positioning entity. More specifically, the UE receives the identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in assistance data. The UE then measures the RSTD between the reference base station and each of the non-reference base stations. Based on the known locations of the involved base stations and the RSTD measurements, a positioning entity (e.g., a UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the location of the UE.

[0125] For DL-AoD positioning illustrated in scenario 420, a positioning entity determines the angles between a UE and the transmitting base stations using measurement reports from the UE of received signal strength measurements for multiple downlink transmit beams. The positioning entity can then estimate the location of the UE based on the determined angles and the known locations of the transmitting base stations.

[0126] Uplink-based positioning methods include Uplink Time Difference of Arrival (UL-TDOA) and Uplink Angle of Arrival (UL-AoA). UL-TDOA is similar to DL-TDOA but is based on uplink reference signals (e.g., Sounding Reference Signals (SRS)) transmitted by the UE to multiple base stations. Specifically, the UE transmits one or more uplink reference signals, which are measured by a reference base station and multiple non-reference base stations. Each base station then reports the time of reception of the reference signal (referred to as Relative Time of Arrival (RTOA)) to a positioning entity (e.g., a location server) that knows the locations and relative timings of the involved base stations. Based on the reported RTOA of the reference base station and the reported RTOA of each non-reference base station, the known locations of the base stations, and their known timing offsets, the positioning entity can estimate the location of the UE using TDOA.

[0127] For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. A positioning entity determines the angles between the UE and the base stations using the signal strength measurements and the angles of the receive beams. Based on the determined angles and the known locations of the base stations, the positioning entity can then estimate the location of the UE.

[0128] Downlink- and uplink-based positioning methods include Enhanced Cell-ID (E-CID) positioning and multi-round trip time (RTT) positioning (also referred to as “multi-cell RTT” and “multi-RTT”). In an RTT procedure, a first entity (e.g., a base station or a UE) transmits a first RTT-related signal (e.g., a PRS or SRS) to a second entity (e.g., a UE or base station), which transmits a second RTT-related signal (e.g., an SRS or PRS) back to the first entity. Each entity measures the time difference between the time of arrival (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. This time difference is referred to as the receive-to-transmit (Rx-Tx) time difference. The Rx-Tx time difference measurement can be made or adjusted to include only the time difference between the closest time slot boundaries of the received and transmitted signals. Both entities can then communicate their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which computes the round trip propagation time (i.e., RTT) between the two entities from these two Rx-Tx time difference measurements (e.g., as the sum of these two Rx-Tx time difference measurements). Alternatively, one entity can communicate its Rx-Tx time difference measurement to the other entity, which then computes the RTT. The distance between the two entities can be determined from the RTT and the known speed of signals (e.g., the speed of light). For multi-RTT positioning illustrated by scenario 430, a first entity (e.g., a UE or base station) performs an RTT positioning procedure with multiple second entities (e.g., multiple base stations or UEs) to enable determination of the position of the first entity based on distances to the second entities and known positions of the second entities (e.g., using multilateration). RTT and multi-RTT methods can be combined with other positioning techniques, such as UL-AoA and DL-AoD, to improve position accuracy, as illustrated by scenario 440.

[0129] E-CID positioning methods are based on radio resource management (RRM) measurements. In E-CID, a UE reports the serving cell ID, timing advance (TA), and identifiers of detected neighbor base stations, estimated timing, and signal strengths. The position of the UE is then estimated based on this information and known positions of the base stations.

[0130] To assist in positioning operations, a location server (e.g., location server 230, LMF 270, SLP 272) can provide assistance data to a UE. For example, the assistance data can include identifiers of base stations (or cells / TRPs of base stations) from which to measure reference signals, reference signal configuration parameters (e.g., including a number of consecutive time slots comprising a PRS, a periodicity of consecutive time slots comprising a PRS, a muting sequence, a frequency hopping sequence, a reference signal identifier, a reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, the assistance data can originate directly from the base stations themselves (e.g., in periodically broadcasted overhead messages, etc.). In some cases, a UE can be able to detect neighboring network nodes without the use of assistance data.

[0131] In the case of OTDOA or DL-TDOA positioning procedures, the assistance data can also include an expected RSTD value and an associated uncertainty or search window around the expected RSTD. In some cases, the value range for the expected RSTD can be + / - 500 microseconds (ps). In some cases, the value range for the uncertainty of the expected RSTD can be + / - 32 ps when any of the resources used for positioning measurements are in FR1. In other cases, the value range for the uncertainty of the expected RSTD can be + / - 8 ps when all of the resources used for positioning measurements are in FR2.

[0132] A location estimate can be referred to by other names, such as a position estimate, location, fix, or fix, among others. A location estimate can be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or can be civic and include a street address, postal address, or some other verbal description of a location. A location estimate can be further defined relative to some other known location or defined in absolute terms (e.g., using latitude, longitude, and possibly altitude). A location estimate can include an expected error or uncertainty (e.g., by including an area or volume within which the location is expected to be included with some specified or default confidence level).

[0133] Figure 5 is a diagram 500 illustrating an example PRS configuration for two TRPs (labeled “TRP1” and “TRP2”) operating in the same positioning frequency layer (labeled “Positioning Frequency Layer 1”) according to aspects of the present disclosure. For a positioning session, a UE can be provided assistance data indicating the illustrated PRS configuration. In Figure 5In the example of FIG. 1, a first TRP (“TRP1”) is associated with (e.g., transmits) two PRS resource sets labeled “PRS Resource Set 1” and “PRS Resource Set 2,” and a second TRP (“TRP2”) is associated with one PRS resource set labeled “PRS Resource Set 3.” Each PRS resource set includes at least two PRS resources. Specifically, the first PRS resource set (“PRS Resource Set 1”) includes PRS resources labeled “PRS Resource 1” and “PRS Resource 2,” the second PRS resource set (“PRS Resource Set 2”) includes PRS resources labeled “PRS Resource 3” and “PRS Resource 4,” and the third PRS resource set (“PRS Resource Set 3”) includes PRS resources labeled “PRS Resource 5” and “PRS Resource 6.”

[0134] When a UE is configured with multiple PRS resources in the assistance data for a positioning method that exceed its capabilities, the UE assumes that the PRS resources in the assistance data are ordered in descending order of measurement priority. Currently, 64 TRPs per frequency layer are ordered according to priority, and two PRS resource sets per TRP of a frequency layer are ordered according to priority. However, the four frequency layers can or can not be ordered according to priority, and the 64 PRS resources in a PRS resource set per TRP of each frequency layer can or can not be ordered according to priority. The reference indicated by the assistance data parameter “nr-DL-PRS-ReferenceInfo” for each frequency layer has the highest priority at least for DL-TDOA positioning procedures.

[0135] There are two resource allocation modes for transmission on NR sidelink according to aspects of the present disclosure. In a first mode (Mode 1), a base station allocates time and / or frequency resources for sidelink communications between involved V-UEs via downlink control information 3 0 (DCI 3 0). Each V-UE transmits ranging signals (e.g., SL-PRS) to other V-UEs using the allocated resources.

[0136] In a second mode (Mode 2), involved UEs autonomously select sidelink resources for transmission of ranging signals. V-UEs can use the first mode only if they have cellular coverage, and can use the second mode regardless of whether they have cellular coverage. Note that although Figure 5 Two V-UEs are illustrated, but as will be appreciated, they need not be V-UEs and instead can be any other type of UE capable of sidelink communications. Moreover, there can be more than the two V-UEs 504 and 506 illustrated.

[0137] NR supports or implements various sidelink positioning techniques. Figure 6AVarious scenarios of interest for sidelink-only or joint Uu and sidelink positioning are illustrated in accordance with aspects of the present disclosure. In scenario 610, at least one peer UE with known location can improve Uu-based positioning of a target UE (e.g., multi-cell RTT, downlink time difference of arrival (DL-TDOA), etc.) by providing additional anchor points (e.g., using sidelink round trip time (RTT) (SL-RTT)). In scenario 620, a low-end (e.g., reduced capability or “RedCap”) target UE can obtain assistance from an advanced UE to determine its location using, for example, a sidelink positioning and ranging procedure with the advanced UE. The advanced UE can have more capabilities compared to the low-end UE, such as more sensors, faster processor, more memory, more antenna elements, higher transmit power capability, access to additional frequency bands, or any combination thereof. In scenario 630, a relay UE (e.g., with known location) participates in the positioning estimation of a remote UE without performing uplink positioning reference signal (PRS) transmission over the Uu interface. Scenario 640 illustrates joint positioning of multiple UEs. Specifically, in scenario 640, by leveraging constraints from nearby UEs, two UEs with unknown locations can be jointly positioned under non-line-of-sight (NLOS) conditions.

[0138] Figure 6B Additional scenarios of interest for sidelink-only or joint Uu and sidelink positioning are illustrated in accordance with aspects of the present disclosure. In scenario 650, UEs for public safety (e.g., used by police, firefighters, etc.) can perform peer-to-peer (P2P) positioning and ranging for public safety and other uses. For example, in scenario 650, the public safety UEs can be out of coverage of the network and use sidelink positioning techniques to determine the locations or relative distances and relative positioning between the public safety UEs. Similarly, scenario 660 shows multiple UEs that are out of coverage and use sidelink positioning techniques (such as SL-RTT) to determine the locations or relative distances and relative positioning.

[0139] Sidelink-based ranging enables determination of the relative distances between UEs and optionally their absolute positioning, where the absolute positioning of at least one of the involved UEs is known. This technique is valuable in cases of Global Navigation Satellite System (GNSS) positioning degradation or unavailability (e.g., tunnels, urban canyons, etc.) and can also enhance ranging and positioning accuracy when GNSS is available. Sidelink-based ranging can be implemented using a three-way handshake for session establishment, followed by exchange of positioning reference signals (PRS), and finally exchange of measurements based on PRS transmission and reception from the peer UE messaging.

[0140] Sidelink ranging is based on computing inter-UE round-trip time (RTT) measurements, as determined from the transmission and reception times of PRS (wideband positioning signals defined in LTE and NR). Each UE reports the RTT measurements along with its position (if known) to all other participating UEs. For UEs that do not know or do not accurately know their position, the RTT procedure yields inter-UE ranges between the involved UEs. For UEs that accurately know their position, the ranges yield absolute positioning. The UE participation, PRS transmission, and subsequent RTT computation are coordinated by an initial three-way messaging handshake (PRS request, PRS response, and PRS acknowledgement) and a post-PRS message exchange (post-PRS messages) for sharing measurements after receiving the PRS of the peer UE.

[0141] Figure 7 An example sidelink ranging and positioning procedure 700 is illustrated in accordance with aspects of the present disclosure. The sidelink ranging and positioning procedure 700 can also be referred to as a sidelink RTT positioning procedure. Sidelink ranging is based on computing inter-UE RTT measurements, as determined from the transmission and reception times of PRS (wideband reference signals defined for positioning in LTE and NR). Each UE reports the RTT measurements along with its position (if known) to all other participating UEs. For UEs that do not know or do not accurately know their position, the RTT procedure yields inter-UE ranges between the involved UEs. For UEs that accurately know their position, the ranges yield absolute position. The UE participation, PRS transmission, and subsequent RTT computation are coordinated by an initial three-way messaging handshake (PRS request, PRS response, and PRS acknowledgement) and a post-PRS message exchange (post-PRS messages) for sharing measurements after receiving the PRS of the peer UE.

[0142] The sidelink ranging and positioning procedure 700 (or session) begins at stage 705 with the broadcast of capability information by the involved peer UEs. As Figure 7As shown, one of the peer UEs, UE 204-1 (e.g., any of the sidelink-capable UEs described herein), is capable of being an anchor UE for the sidelink ranging and positioning procedure 700, meaning that its location is known. Accordingly, the anchor UE 204-1 includes an indication in its capability message that it is capable of being an anchor UE for the sidelink ranging and positioning procedure 700. The capability message can also include the location of the anchor UE 204-1, or that location can be provided later. The other UE, UE 204-2 (e.g., any other of the sidelink-capable UEs described herein), is a target UE, meaning that its location is unknown or inaccurate and that it is attempting to be located. Based on the capability information received from the anchor UE 204-1 indicating that the anchor UE 204-1 is an anchor UE, the target UE 204-2 knows that it will be able to determine its location based on performing the sidelink ranging and positioning procedure 700 with the anchor UE 204-1.

[0143] After the initial capability exchange, the involved UEs 204 perform a three-way messaging handshake. At stage 710, the anchor UE 204-1 sends a PRS request (labeled “PRSrequest”) to the target UE 204-2. At stage 715, the target UE 204-2 sends a PRS response (labeled “PRSresponse”) to the anchor UE 204-1. At stage 720, the anchor UE 204-1 sends a PRS acknowledgement to the target UE 204-2. At this point, the three-way messaging handshake is complete. Note that although Figure 7 The anchor UE 204-1 is illustrated as initiating the three-way messaging handshake, but it could instead be initiated by the target UE 204-2.

[0144] At stages 725 and 730, the involved peer UEs 204 send PRS to each other. The resources on which the PRS are sent can be configured / assigned by the network (e.g., a serving base station of one of the UEs 204) or negotiated by the UEs 204 during the three-way messaging handshake. The anchor UE 204-1 measures the transmit-to-receive (Tx-Rx) time difference between the transmission time of the PRS at stage 725 and the reception time of the PRS at stage 730. The target UE 204-2 measures the receive-to-transmit (Rx-Tx) time difference between the reception time of the PRS at stage 725 and the transmission time of the PRS at stage 730. Note that although Figure 7 The anchor UE 204-1 is illustrated as first sending the PRS, but the target UE 204-2 could instead first send the PRS.

[0145] At stages 735 and 740, the peer UEs 204 exchange their respective time difference measurements in a post-PRS message (labeled "post PRS"). If the anchor UE 204-1 has not already provided its location to the target UE 204-2, it does so at this time. Each UE 204 can then determine the RTT between each UE 204 based on the Tx-Rx and Rx-Tx time difference measurements (specifically, the difference between the Tx-Rx and Rx-Tx time difference measurements). Based on the RTT measurements and the speed of light, each UE 204 can then estimate the distance (or range) between the two UEs 204 (specifically, the RTT measurement multiplied by half the speed of light). Since the target UE 204-2 also has the absolute location (e.g., geographic coordinates) of the anchor UE 204-1, the target UE 204-2 can use that location and the distance to the anchor UE 204-1 to determine its own absolute location.

[0146] Note that although Figure 7 Two UEs 204 are illustrated, but a UE can perform or attempt to perform the sidelink ranging and positioning procedure 700 with multiple UEs.

[0147] According to aspects of the present disclosure, a network device can perform a channel sensing operation to access a channel that the network device wishes to use for communication. To this end, the following terminology can be considered for such channel access operations:

[0148] • Channel refers to a carrier or a portion of a carrier consisting of a contiguous set of resource blocks (RBs) on which a channel access procedure is performed in a shared spectrum.

[0149] • Channel access procedure can be considered a procedure based on sensing that evaluates the availability of a channel for performing a transmission. In one aspect, the basic unit for sensing is a sensing slot having a duration of, e.g., T si = 9 microseconds (μβ). A sensing slot duration T Thresh may be considered idle in the case where the eNB / gNB or UE senses the channel during the sensing slot duration and determines that the detected power is less than an energy detection threshold X si for at least a predetermined time (e.g., 4 μβ) within the sensing slot duration. Otherwise, the sensing slot duration T si is considered busy.

[0150] • Channel occupancy can be considered to refer to a transmission by an eNB / gNB / UE on a channel after performing a corresponding channel access procedure disclosed herein.

[0151] • Channel occupancy time (COT) can be considered to refer to the total time of channel occupancy transmission by an eNB / gNB / UE and any eNB / gNB / UE on a shared channel after the eNB / gNB / UE performs the corresponding channel access procedure described above. To determine COT, if a transmission gap is less than or equal to a certain duration (e.g., 25us), the gap duration can be counted in COT. COT can be shared for transmissions between an eNB / gNB and a corresponding UE.

[0152] • DL transmission burst can be considered to refer to a set of transmissions from an eNB / gNB without any gap that is greater than a threshold (e.g., 16us). Transmissions from an eNB / gNB that are separated by a gap that is greater than a threshold (e.g., 16us) can be considered separate DL transmission bursts. In one aspect, an eNB / gNB can transmit a transmission after a gap within a DL transmission burst without sensing availability of the corresponding channel.

[0153] • UL transmission burst can be considered to refer to a set of transmissions from a UE without any gap that is greater than a threshold (e.g., 16us). Transmissions from a UE that are separated by a gap that is greater than a threshold (e.g., 16us) can be considered separate UL transmission bursts. In one aspect, a UE can transmit a transmission after a gap within a UL transmission burst without sensing availability of the corresponding channel.

[0154] • Discovery burst can be considered to refer to a DL transmission burst that includes a set of signals and / or channels that are confined within a window and are associated with a duty cycle. In one aspect, a discovery burst can be any of the following:

[0155] - transmissions initiated by an eNB that include primary synchronization signals (PSS), secondary synchronization signals (SSS), and cell-specific reference signals (CRS), and can include non-zero-power channel state information reference signals (CSI-RS); and / or

[0156] - transmissions initiated by a gNB that include at least SS / PBCH blocks consisting of primary synchronization signals (PSS), secondary synchronization signals (SSS), physical broadcast channel (PBCH) with associated demodulation reference signals (DM-RS), and can also include control resource sets (CORESETs) for scheduling physical downlink shared channels (PDSCHs) with system information block 1 (SIB 1) and PDCCHs carrying SIB 1 and / or non-zero-power CSI-RS.

[0157] In certain scenarios, COT sharing can be used in conjunction with data communications between sidelink (SL) devices. In one aspect, a responding SL UE (e.g., a sidelink UE responding to an information request from another sidelink UE as illustrated in FIG. 2) can utilize a COT shared by a COT initiating UE (e.g., the UE requesting information) when the responding SL UE is a target receiver of a PSSCH data transmission by the COT initiating UE in the COT. In one aspect, sharing can occur when the responding UE using its transmission with the shared COT has a channel access priority class (CAPC) that is equal to or less than a CAPC indicated in the shared COT information. Figure 7

[0158] In one aspect, a responding SL UE can utilize a COT shared by a COT initiating UE when the responding SL UE is a target receiver of a transmission by the COT initiating UE in the COT. Sharing COT can be used in such scenarios when the responding UE using its transmission with the shared COT has a CAPC that is equal to or less than a CAPC indicated in the shared COT information.

[0159] While COT sharing has been defined at least minimally for sidelink data communications, certain aspects of the present disclosure are implemented with recognition that such COT sharing procedures for data can not be optimal for COT sharing between sidelink UEs participating in a sidelink positioning session. Accordingly, certain aspects of the present disclosure relate to ways in which one or more COTs can be shared by sidelink UEs during a positioning session. Certain aspects of the present disclosure are implemented with recognition that it can be desirable to determine which network device is responsible for channel sensing, setting sensing thresholds for channel sensing, selecting COTs for use during a positioning session, communicating shared COTs to sidelink UEs participating in a positioning session, and the like. Certain aspects of the present disclosure can be used for COT sharing for positioning operations occurring in unlicensed spectrum.

[0160] ​According to certain aspects of the present disclosure, a single sidelink device (e.g., an anchor UE, a UE operating as a server for other UEs, etc.) or a base station can be assigned the task of channel sensing operations for a positioning session. Based on information obtained during the channel sensing operations, the sidelink device can determine that a COT window is available on a channel for transmitting or measuring PRS during the positioning session. In one aspect, an indication of the COT window can be transmitted for reception by sidelink devices located in the positioning environment. The indication of the COT window can be broadcast, groupcast, or unicast to the sidelink devices for their reception. For groupcast of the COT window, the sidelink device transmitting the COT indication can target all sidelink devices in the positioning environment or only a more limited subset of sidelink devices selected by the transmitting sidelink device for such participation. In one aspect, individual sidelink devices can determine whether the sidelink device is available to participate in the positioning session during the COT window indicated in the transmission. In an example scenario, multiple COT windows can be indicated in the transmission. In that case, individual sidelink devices can make a determination that they will use all COT windows or only select certain COT windows to transmit or measure PRS.

[0161] The particular sidelink devices that transmit or measure PRS during the positioning session in the positioning environment can vary. In one aspect, only sidelink devices that are able to transmit or measure PRS within the indicated COT window can participate in the positioning session. In one aspect, sidelink devices that are not able to transmit or measure PRS within the indicated COT window can refrain from transmitting or measuring PRS even though the sidelink devices can otherwise be indicated to participate in the positioning session (e.g., otherwise indicated in assistance data for the positioning session).

[0162] In the foregoing example, only a single sidelink device (e.g., the anchor UE in Figure 7 has been assigned the task of channel sensing and COT window computation. Such scenarios can be used for positioning sessions involving single-RTT positioning techniques, double-sided RTT techniques, or a combination of both single-RTT and double-sided RTT techniques.

[0163] However, certain aspects of the present disclosure are implemented with an understanding that channel sensing by a single sidelink device can not be sufficient to obtain a COT window (e.g., a COT window having a sufficient duration for a longer PRS measurement occasion) that can be used to satisfy the requirements of a positioning session. For example, when PRS resources available for sidelink positioning are distributed in the time domain between a sidelink device and an anchor device, a COT window of sufficient duration for a positioning session can not be obtained. Accordingly, certain aspects of the present disclosure include assigning the task of channel sensing and / or COT computation to multiple sidelink devices within a positioning environment. In one aspect, the multiple sidelink devices can perform channel sensing and / or COT computation and send this information to a given sidelink device (e.g., an anchor UE or other sidelink device assigned the task of COT window computation). In certain scenarios, the sidelink device assigned the task of channel sensing and COT computation can be fixed (e.g., the same anchor UE or other sidelink device) for all positioning sessions, or can vary with different positioning sessions. In certain scenarios, a network server (e.g., a location server, LMF, etc.) can specify which sidelink devices in a positioning environment perform channel sensing and / or compute a COT window for a positioning session.

[0164] In certain scenarios, the network can operate independently of a location server using pre-selected sidelink devices or a pre-programmed sequence of sidelink devices to determine which sidelink devices are assigned the task of channel sensing and / or COT computation. In scenarios where positioning occurs independently of a network server, a sidelink device (e.g., an anchor UE or other sidelink device that initiates or manages a positioning session) can determine which sidelink devices in a positioning environment perform channel sensing and / or COT computation.

[0165] According to certain aspects of the present disclosure, an anchor UE and all other sidelink devices (e.g., sidelink UEs) within a positioning environment perform channel sensing and COT computation. In such scenarios, all of the sidelink devices in a positioning environment can report their channel sensing and / or COT computation to a single entity (e.g., an anchor UE, a target UE, a sidelink UE that initiates a positioning session, a sidelink UE that operates as a server for other sidelink UEs, etc.). The single entity to which channel sensing and COT computation is reported can determine a final COT window to be used for a positioning session and send an indication of the final COT window to other sidelink devices in the positioning environment.

[0166] According to certain aspects of the present disclosure, a subset of less than all sidelink devices in a positioning environment and anchor UEs can be tasked with channel sensing and COT computation. In various scenarios, the subset of sidelink devices that perform channel sensing and / or COT computation can be selected by an anchor UE, a target UE, a UE that initiates a positioning session, a server UE that operates as a server to other sidelink devices in the positioning environment, a base station, a location server, and / or an LMF. In one aspect, the entity tasked with selecting the subset of sidelink devices can transmit a request to the subset of sidelink devices to perform channel sensing and / or COT computation. The subset of sidelink devices can report their channel measurements and / or COT computations to the entity tasked with making a final COT window determination, which can or can not be the same entity tasked with sidelink device selection. The entity tasked with making a final COT window determination can do so based at least on the channel sensing and / or COT computations reported by the subset of sidelink devices, and in certain scenarios, based on channel sensing and / or COT computations made by the entity tasked with the task. In turn, the entity to which channel sensing and COT measurements are reported sends an indication of a final COT window for a positioning session to other sidelink devices in the positioning environment. In one aspect, sidelink devices that receive the indication of the final COT window can determine whether they are able to participate in the positioning session during the indicated final COT window.

[0167] In certain scenarios, sidelink devices that perform channel sensing operations can do so using the same channel sensing threshold used by the sidelink devices to determine a COT window for data communications (e.g., non-positioning scenarios). However, according to certain aspects of the present disclosure, sidelink devices that perform channel sensing operations can do so using a channel sensing threshold for a positioning COT window (e.g., a COT window for positioning) that is different from the channel sensing threshold used for other sidelink communications. In certain scenarios, a location server (e.g., an LMF) can set the different channel sensing threshold. The location server can send an indication of the different threshold to sidelink devices in a positioning environment, which can use the different channel sensing threshold based on whether the channel sensing is for a positioning COT determination or a COT determination for other sidelink communications. In certain aspects, the different threshold can be based on a set of standardized thresholds with a channel sensing threshold specifically intended for positioning COT determinations. In certain scenarios, the particular channel sensing threshold for positioning COT determinations can be static between different positioning sessions. In other scenarios, the channel sensing threshold for positioning COT determinations can be dynamic between different positioning sessions.

[0168] According to various aspects of the present disclosure, assistance data provided to a sidelink device in a positioning environment can be based on a COT window configured for transmitting or receiving positioning PRS during a positioning session. In certain scenarios, an anchor UE or location server can configure multiple assistance data sets based on the configured COT window.

[0169] Figure 8 A table 800 illustrating an example of different assistance data sets (e.g., different TRPs, different PRS configurations, different response times, etc.) depicting positioning sessions that can be conducted based on different durations of a configured COT window is shown in accordance with aspects of the present disclosure. In this example, a first assistance data set “Set 1” is used when the configured COT window for a positioning session Wp has a duration greater than or equal to Wi but less than duration W2. A second assistance data set “Set 2” is used when the configured COT window Wp has a duration greater than or equal to W2 but less than duration W3. A third assistance data set “Set 3” is used when the configured COT window Wp has a duration greater than or equal to W3 but less than duration W4. A fourth assistance data set “Set 4” is used when the configured COT window Wp has a duration greater than or equal to W4 but less than duration W5. It will be appreciated that the types of data included in the assistance data sets and the particular configured window ranges associated with the assistance data sets can vary based on the teachings of the present disclosure, the foregoing being non-limiting examples.

[0170] Figure 9 An example method 900 of wireless communication performed by a sidelink device in accordance with aspects of the present disclosure is illustrated. At operation 902, the sidelink device obtains channel sensing information to determine availability of a channel for transmitting or measuring positioning reference signals (PRS) for a positioning session. In one aspect, operation 902 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, memory 340, and / or positioning component 342, any or all of which can be considered means for performing this operation.

[0171] At operation 904, the sidelink device transmits an indication of at least one channel occupancy time (COT) window to one or more additional SL devices for transmitting or measuring PRS during the positioning session by the one or more additional SL devices, wherein the at least one COT is based on the channel sensing information. In one aspect, operation 904 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, memory 340, and / or positioning component 342, any or all of which can be considered means for performing this operation.

[0172] In some aspects, the method 900 includes determining a positioning estimate of the at least one target SL device based on the PRS measured during the at least one COT window.

[0173] In some aspects, the method 900 includes receiving a positioning channel sensing threshold; and determining availability of a channel for transmitting or measuring PRS for a positioning session using the positioning channel sensing threshold.

[0174] In some aspects of the method 900, obtaining the channel sensing information comprises, at least in part, performing a channel sensing operation at the SL device; and the at least one COT window is determined based, at least in part, on the channel sensing information obtained during the channel sensing operation performed by the SL device.

[0175] In some aspects of the method 900, obtaining the channel sensing information comprises, at least in part, obtaining the channel sensing information from one or more additional SL devices.

[0176] In some aspects of the method 900, the method includes transmitting, to one or more additional SL devices, a request for channel sensing information from the one or more additional SL devices.

[0177] In some aspects, the method 900 includes determining the at least one COT window is further based on one or more COT windows reported by one or more additional SL devices.

[0178] In some aspects, the method 900 includes transmitting, to one or more additional SL devices, a request for one or more COT windows determined at the one or more additional SL devices.

[0179] In some aspects of the method 900, the SL device is: an anchor user equipment (UE); a server UE; or an initiating UE that initiates the positioning session.

[0180] In some aspects of the method 900, the SL device is the initiating UE.

[0181] In some aspects of the method 900, the initiating UE is a target SL device that determines its position estimate during the positioning session.

[0182] In some aspects of the method 900, the at least one COT window is determined by a UE that initiates the positioning session.

[0183] As will be appreciated, the method 900 has the technical advantage that it can be used to determine COT windows tailored for transmitting or receiving PRS during a positioning session. The COT windows for positioning can be superior to COT windows determined and used for other types of sidelink communications.

[0184] Figure 10An example method 1000 of wireless communication performed by a network server in accordance with aspects of the present disclosure is illustrated. At operation 1002, the network server transmits, to one or more sidelink (SL) devices, a first sensing threshold for use by the one or more SL devices in determining availability of a channel for transmitting or receiving data. In one aspect, operation 1002 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, the memory 340, and / or the positioning component 342, any or all of which can be considered means for performing this operation. In one aspect, operation 1002 can be performed by the one or more WWAN transceivers 350, the one or more processors 384, the memory 386, and / or the positioning component 388, any or all of which can be considered means for performing this operation.

[0185] At operation 1004, the network server transmits, to the one or more SL devices, a second sensing threshold for use by the one or more SL devices in determining availability of a channel for transmitting or measuring positioning reference signals (PRSs) of a positioning session. In one aspect, operation 1004 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, the memory 340, and / or the positioning component 342, any or all of which can be considered means for performing this operation. In one aspect, operation 1004 can be performed by the one or more WWAN transceivers 350, the one or more processors 384, the memory 386, and / or the positioning component 388, any or all of which can be considered means for performing this operation.

[0186] In some aspects of the method 1000, the second sensing threshold is based on a standardized threshold for channel sensing during the positioning session.

[0187] In some aspects of the method 1000, the network server comprises a location server, a base station, an anchor user equipment (UE) operating as a network server for one or more additional sidelink devices, or a combination thereof.

[0188] As will be appreciated, the method 1000 is advantageous in that it can be used to assign and use channel sensing thresholds to determine COT windows for transmitting or receiving PRSs during a positioning session. The COT windows for such positioning determinations can be different from channel sensing thresholds used to determine COT windows for other sidelink communications.

[0189] Figure 11An example method 1100 of wireless communication performed by a network server in accordance with aspects of the present disclosure is illustrated. At operation 1102, the network server determines a plurality of channel occupancy time (COT) windows available for transmission or reception of positioning reference signals (PRS) for a positioning session. In one aspect, operation 1102 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, the memory 340, and / or the positioning component 342, any or all of which can be considered means for performing this operation. In one aspect, operation 1102 can be performed by the one or more WWAN transceivers 350, the one or more processors 384, the memory 386, and / or the positioning component 388, any or all of which can be considered means for performing this operation.

[0190] At operation 1104, the network server transmits a plurality of sets of assistance data for use during the positioning session, where each set of assistance data of the plurality of sets of assistance data is based on a corresponding COT window of the plurality of COT windows. In one aspect, operation 1104 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, the memory 340, and / or the positioning component 342, any or all of which can be considered means for performing this operation. In one aspect, operation 1104 can be performed by the one or more WWAN transceivers 350, the one or more processors 384, the memory 386, and / or the positioning component 388, any or all of which can be considered means for performing this operation.

[0191] In some aspects of the method 1100, the network server comprises a location server, a base station, an anchor user equipment (UE) operating as a network server for one or more sidelink devices, or a combination thereof.

[0192] In some aspects of the method 1100, the network server comprises a location server, a base station, an anchor user equipment (UE) operating as a network server for one or more sidelink devices, or a combination thereof.

[0193] In some aspects of the method 1100, each of the plurality of sets of assistance data includes an indication of a corresponding set of user equipment (UE) based on the corresponding COT window.

[0194] As will be appreciated, a technical advantage of the method 1100 is that it can be used to assign different sets of assistance data based on various criteria satisfied by the COT windows assigned for transmission or reception of PRS during the positioning session.

[0195] Certain aspects of the present disclosure are implemented in recognition that there is currently no way for a sidelink (SL) device, such as a UE, to select a channel access priority class (CAPC) that is specific to channel sensing during a positioning session. Rather, any CAPC assigned to a sidelink device is designated for channel sensing for radio resource management (RRM) for sidelink communications, such as data communications, only. Thus, current standards do not contemplate using a CAPC that is specific to a positioning session, and this CAPC can be the same or different from the CAPC assigned to the SL device for general RRM for sidelink communications.

[0196] Figure 12 Table 1200 illustrates an example of sets of channel sensing parameters that can be associated with various channel access priority class (CAPC) levels, in accordance with aspects of the present disclosure. In this example, column 1202 indicates a channel access priority class assignment (p) associated with each set of channel sensing parameters. Column 1204 shows a value m corresponding to a number of consecutive sensing slots used in a defined delay duration for each priority class p p During this delay duration, a SL device with priority level p senses the channel. Column 1204 shows a value CWmin corresponding to a minimum contention window associated with a SL device with a given priority class p min, p Column 1208 shows a value CWmax corresponding to a maximum contention window associated with a SL device with a given priority class p max, p Column 1210 shows a value Tm corresponding to a maximum channel occupancy time associated with a SL device with a given priority class p cot, p Column 1212 shows a value of allowed CWsize, where CWsize is a contention window size associated with a SL device with a given priority class p p Column 1214 shows a value of allowed Tm size, where Tm size is a channel occupancy time size associated with a SL device with a given priority class p p Column 1216 shows a value of allowed Tm size, where Tm size is a channel occupancy time size associated with a SL device with a given priority class p

[0197] Certain aspects of the present disclosure relate to selecting a CAPC for a SL device that is to be used explicitly by the SL device for channel sensing to transmit or measure PRS during a positioning session. In certain aspects, a SL device performs a channel sensing procedure during a positioning session based on a positioning-specific CAPC selected for use by the SL device in the positioning session. The CAPC is associated with sensing parameters used by the SL device to determine availability of a channel for transmitting or measuring PRS during the positioning session. In certain aspects, the SL device transmits an indication of a COT window to other SL devices for use during the positioning session, where the COT window is based on channel sensing using the channel sensing parameters associated with the positioning-specific CAPC.

[0198] A positioning-specific CAPC can be assigned to a SL device, or otherwise selected by a SL device in various manners. In certain scenarios, the positioning-specific CAPC can be the same as used for channel sensing in other RRM operations. In such scenarios, both the positioning-specific CAPC and the CAPC for RRM of sidelink communications are associated with the same (or overlapping) channel sensing parameters, and can be based on obtaining data channel resources and PRS resources from a shared resource pool.

[0199] In certain scenarios, the positioning-specific CAPC can be different than the CAPC used for RRM of sidelink data channels, and thus associated with a different set of channel sensing parameters. In one aspect, the different set of channel sensing parameters can be based on obtaining PRS channel resources from a dedicated positioning resource pool. In such scenarios, the dedicated positioning resource pool includes resources that are different than the resources of the data channel resource pool used for sidelink communications. In certain scenarios, an indication of the positioning-specific CAPC can be received from another network device (e.g., another SL device, a positioning server, a location management function, etc.).

[0200] In certain scenarios, the channel sensing parameters associated with an initial positioning-specific CAPC assigned to a SL device can not be sufficient to determine a COT window suitable for a positioning session. In accordance with certain aspects of the present disclosure, when a SL device fails to detect availability of a suitable COT window on a channel while using the set of channel sensing parameters associated with the initial positioning-specific CAPC, the SL device can increase the channel access priority class level of the initial CAPC to a higher level CAPC. In certain scenarios, when a SL device fails to detect availability of a suitable COT window on a channel within a threshold number of channel sensing attempts using the set of channel sensing parameters associated with a current CAPC, the SL device can increase its current CAPC. By increasing the CAPC to a higher priority level, the SL device can use the set of channel sensing parameters that makes it more likely for the SL device to detect a suitable COT window for transmitting or measuring PRS during a positioning session. In certain scenarios, the SL device can incrementally increase the CAPC to a higher level until the channel sensing parameters result in a time to find a suitable COT window for a positioning session. As an example, after a number N of consecutive failures (e.g., a timer expiring, a number of failures within a time window, a total number of failures from the start of a positioning session, or any combination thereof), the SL device can increase its priority by an amount X + 1, where X corresponds to the CAPC level associated with the failed attempts. In certain scenarios, when the highest allowable CAPC available to the SL device is reached without finding a suitable COT window for a positioning session, the SL device can abort the positioning session.

[0201] According to aspects of the present disclosure, each positioning session will have its own latency requirement as well as a minimum number of positioning occasion measurements required to obtain a meaningful positioning estimate during the positioning session. Accordingly, certain aspects of the present disclosure relate to handling instances where a SL device is unable to meet the channel access requirements for a positioning session. Various options for handling such instances are disclosed. According to a first option, a failure is declared by the SL device based on a maximum number of times an attempt to transmit or measure PRS during a measurement occasion. According to a second option, the SL device can abort the positioning session if there are more than a threshold number of failures at any given measurement occasion.

[0202] One such error instance occurs when a UE that has received a COT window for transmitting or receiving PRS during a positioning session is unable to sufficiently access the channel to meet the minimum requirements of the positioning session. To this end, the SL device can obtain (e.g., from another SL device, a network entity, etc.) at least one COT window for transmitting or measuring PRS on the channel during a positioning occasion of the positioning session. According to certain aspects of the present disclosure, the SL device can abort (e.g., stop its current participation or prevent further participation in the positioning session) based on various failure conditions. Such failure conditions can include: 1) a number of failed attempts by the SL device to access the channel for the positioning occasion during the at least one COT window exceeds a first threshold number of failed attempts, 2) a number of failed attempts by the SL device to access the channel for the positioning session during the at least one COT window exceeds a second threshold number of failed attempts, or 3) any combination thereof. In various scenarios, the SL device can transmit 1) an indication that the SL device has aborted the positioning session, 2) an indication of the failure condition (e.g., number of failures, type of failure, etc.) encountered that caused the SL device to abort the positioning session, or 3) a combination thereof.

[0203] Certain aspects of the present disclosure relate to using different sidelink assistance data in response to a SL device being unable to use current assistance data to meet minimum requirements for a positioning session. To this end, a SL device can obtain at least one COT window for transmitting or measuring PRS on a channel during a positioning session. The SL device can then attempt to transmit or measure the PRS channel during the COT window based on a current set of assistance data (e.g., PRS configuration). When the SL device experiences a threshold number of failed attempts to transmit or measure PRS during the COT window using the current assistance data, the SL device can request and obtain another (e.g., second, third, etc.) set of assistance data that the SL device can use in an effort to meet minimum channel access requirements imposed on the SL device for the positioning session. The request for and / or use of another set of assistance data can occur when the SL device experiences a threshold number of failed attempts to transmit or measure PRS during the COT window using the current set of assistance data. According to various aspects, the threshold number of failed attempts can include 1) a number of failed attempts by the SL device to access the channel for the positioning session during the at least one COT window, 2) a number of failed attempts by the SL device to access the channel for a positioning occasion of the positioning session during the at least one COT window, or 3) any combination thereof. In certain aspects, the different sets of assistance data can be based on multiple sets of assistance data having different slot offsets, different bandwidths, different numbers of PRS repetitions, different frequency bands, different component carriers, or any combination thereof. In certain scenarios, the SL device can send a request to another network entity (e.g., another SL device, a network server, a positioning server, an LMF) to transfer other sets of assistance data when a failure condition occurs. In certain aspects, the SL device can request a series of different sets of assistance data until a set of assistance data is obtained that the SL device can utilize to meet the channel access requirements, or until all allowable sets of assistance data available to the SL device have been exhausted.

[0204] According to certain aspects of the present disclosure, in situations where a SL device is unable to meet channel access requirements for a positioning session based on its current CAPC, the SL device can incrementally increase its current CAPC. In certain scenarios, the SL device can be unable to transmit or measure a PRS channel during a given COT window while operating with its current CAPC. The SL device can experience a failure to access the channel for transmitting or measuring PRS during the COT window, and increase its CAPC in response to a failure condition. The failure condition can be declared based on exceeding a threshold number of failed attempts by the SL device to transmit or measure PRS during the COT window. In various scenarios, the threshold number of failed attempts can include 1) a number of failed attempts by the SL device to access the channel for the positioning session during the COT window, 2) a number of failed attempts by the SL device to access the channel for a positioning occasion of the positioning session during the COT window, or 3) any combination thereof.

[0205] Figure 13 An example method 1300 of wireless communication performed by a SL device in accordance with aspects of the present disclosure is illustrated. At operation 1302, the SL device performs a channel sensing procedure during a positioning session based on a first channel access priority class (CAPC), where the first CAPC is selected by the SL device to determine availability of a channel for transmitting or measuring a positioning reference signal (PRS) during the positioning session, and the first CAPC is associated with a first set of channel sensing parameters for the channel sensing procedure. In one aspect, operation 1302 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, the memory 340, and / or the positioning component 342, any or all of which can be considered means for performing this operation.

[0206] At operation 1304, the SL device transmits, to one or more additional SL devices, an indication of at least one channel occupancy time (COT) window for transmitting or measuring a PRS by the one or more additional SL devices during the positioning session, where the at least one COT window is based on channel sensing using the first set of channel sensing parameters associated with the first CAPC. In one aspect, operation 1302 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, the memory 340, and / or the positioning component 342, any or all of which can be considered means for performing this operation.

[0207] In some aspects of the method 1300, the first CAPC selected by the SL device for use in the positioning session is a same priority class CAPC as a second CAPC associated with channel sensing indicated for radio resource management with sidelink data communications.

[0208] In some aspects of the method 1300, the first set of channel sensing parameters is a same set of channel sensing parameters as a second set of channel sensing parameters associated with the second CAPC, and the PRS channel resources and data channel resources are obtained from a shared sidelink resource pool.

[0209] In some aspects of the method 1300, the first CAPC selected by the SL device for use in the positioning session is a different priority class CAPC than a second CAPC associated with channel sensing indicated for radio resource management with sidelink data communications.

[0210] In some aspects of the method 1300, the first set of channel sensing parameters and a second set of channel sensing parameters associated with the second CAPC correspond to different sets of channel sensing parameters, and the different sets of channel sensing parameters are based on obtaining the PRS channel resources from a dedicated positioning resource pool that is different from data channel resources of a data channel resource pool.

[0211] In some aspects, the method 1300 includes receiving, from the network entity, the first CAPC.

[0212] In some aspects, the method 1300 includes obtaining an initial CAPC, wherein the first CAPC is based on the initial CAPC.

[0213] In some aspects, the method 1300 includes obtaining the initial CAPC includes receiving, from the network entity, the initial CAPC.

[0214] In some aspects of the method 1300, the initial CAPC is based on a second CAPC indicated for channel sensing associated with radio resource management for the sidelink data communication.

[0215] In some aspects, the method 1300 includes increasing a channel access priority class level of the initial CAPC to a higher level CAPC for use as the first CAPC based on failing to detect availability of a channel for transmitting or receiving PRS during a channel sensing procedure when using the first set of channel sensing parameters.

[0216] In some aspects of the method 1300, the channel access priority class level of the initial CAPC is increased based on failing to detect availability of the channel within a threshold number of channel sensing attempts using the first set of channel sensing parameters.

[0217] In some aspects of the method 1300, the channel access priority class level of the initial CAPC is increased based on failing to sense availability of the channel within a threshold time duration using the first set of channel sensing parameters.

[0218] In some aspects of the method 1300, the first set of channel sensing parameters includes one or more of: one or more allowed contention window sizes associated with the first CAPC; a maximum contention window size associated with the first CAPC; a minimum contention window size associated with the first CAPC; a maximum channel occupancy time associated with the first CAPC; or any combination thereof.

[0219] As will be appreciated, the technical advantage of the method 1300 is that the SL device uses positioning-specific CAPC to establish channel sensing parameters used by the SL device to perform channel sensing to determine availability of a channel for transmitting or measuring PRS during a positioning session.

[0220] Figure 14An example method 1400 of wireless communication performed by a SL device in accordance with aspects of the present disclosure is illustrated. At operation 1402, the SL device obtains at least one channel occupancy time (COT) window for transmitting or measuring positioning reference signals (PRSs) on a channel during a positioning occasion of a positioning session. In one aspect, operation 1402 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, the memory 340, and / or the positioning component 342, any or all of which can be considered means for performing this operation.

[0221] At operation 1404, the SL device aborts the positioning session based on a failure condition comprising a number of failed attempts by the SL device to access the channel for the positioning occasion during the at least one COT window exceeding a first threshold number of failed attempts, a number of failed attempts by the SL device to access the channel for the positioning session during the at least one COT window exceeding a second threshold number of failed attempts, or any combination thereof. In one aspect, operation 1404 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, the memory 340, and / or the positioning component 342, any or all of which can be considered means for performing this operation.

[0222] In some aspects, the method 1400 includes transmitting an indication that the positioning session has been aborted; transmitting an indication of the failure condition; or a combination thereof.

[0223] In some aspects, the method 1400 includes receiving, from a network device, an indication of the at least one COT window.

[0224] In some aspects of the method 1400, the network device comprises: a sidelink UE; a location server; or a base station.

[0225] As will be appreciated, the method 1400 is advantageous in that the SL device aborts the positioning session in situations where the SL device is unable to meet channel access requirements needed to transmit or measure PRSs in a manner that satisfies requirements of the positioning session.

[0226] Figure 15 An example method 1500 of wireless communication performed by a SL device in accordance with aspects of the present disclosure is illustrated. At operation 1502, the SL device obtains at least one channel occupancy time (COT) window for transmitting or measuring positioning reference signals (PRSs) on a channel during a positioning session. In one aspect, operation 1502 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, the memory 340, and / or the positioning component 342, any or all of which can be considered means for performing this operation.

[0227] At operation 1504, the SL device attempts to transmit or measure PRS on the channel during the COT window based on the first set of assistance data. In one aspect, operation 1504 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, the memory 340, and / or the positioning component 342, any or all of which can be considered means for performing this operation.

[0228] At operation 1506, the SL device transmits or measures PRS on the channel during the COT window based on a second set of assistance data, where the second set of assistance data is used based on a number of failed attempts by the SL device to transmit or measure PRS during the at least one COT window using the first set of assistance data exceeding a threshold number of failed attempts. In one aspect, operation 1506 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, the memory 340, and / or the positioning component 342, any or all of which can be considered means for performing this operation.

[0229] In some aspects of the method 1500, the threshold number of failed attempts includes: a number of failed attempts by the SL device to access the channel during the at least one COT window for the positioning session; a number of failed attempts by the SL device to access the channel during the at least one COT window for a positioning occasion of the positioning session; or any combination thereof.

[0230] In some aspects of the method 1500, the second set of assistance data is different from the first set of assistance data based on the first set of assistance data and the second set of assistance data having different slot offsets, different bandwidths, different numbers of PRS repetitions, different frequency bands, different component carriers, or any combination thereof.

[0231] In some aspects, the method 1500 includes transmitting a request for the second set of assistance data based on the number of failed attempts by the SL device to transmit or measure PRS during the at least one COT window using the first set of assistance data exceeding the threshold number of failed attempts.

[0232] In some aspects of the method 1500, obtaining the at least one COT window includes: receiving an indication of the at least one COT window from a network device.

[0233] In some aspects of the method 1500, the network device includes: a sidelink UE; a location server; or a base station.

[0234] As will be appreciated, the technical advantage of the method 1500 is that the SL device switches to using another set of assistance data during the positioning session in the event that the SL device is unable to meet the channel access requirements needed to transmit or measure PRS in a manner that meets the requirements of the positioning session based on the current set of assistance data. The new set of assistance data can provide the SL device with a configuration that allows it to meet the channel access requirements.

[0235] Figure 16 An example method 1600 of wireless communication by a SL device is illustrated in accordance with aspects of the present disclosure. At operation 1602, the SL device obtains at least one channel occupancy time (COT) window for transmitting or measuring a positioning reference signal (PRS) on a channel during a positioning session. In one aspect, operation 1602 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, the memory 340, and / or the positioning component 342, any or all of which can be considered means for performing this operation.

[0236] At operation 1604, the SL device attempts to transmit or measure the PRS on the channel during the COT window based on a first channel access priority class (CAPC) of the SL device. In one aspect, operation 1604 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, the memory 340, and / or the positioning component 342, any or all of which can be considered means for performing this operation.

[0237] At operation 1606, the SL device transmits or measures the PRS on the channel during the COT window based on a second CAPC, where the second CAPC is based on an operation that increments a priority level of the first CAPC based on a number of failed attempts by the SL device to transmit or measure the PRS during the at least one COT window based on the first CAPC exceeding a threshold number of failed attempts. In one aspect, operation 1606 can be performed by the one or more WWAN transceivers 310, the one or more processors 332, the memory 340, and / or the positioning component 342, any or all of which can be considered means for performing this operation.

[0238] In some aspects of the method 1600, the threshold number of failed attempts includes a number of failed attempts by the SL device to access the channel for the positioning session during the at least one COT window, a number of failed attempts by the SL device to access the channel for a positioning occasion of the positioning session during the at least one COT window, or any combination thereof.

[0239] In some aspects of the method 1600, the second set of assistance data is different from the first set of assistance data based on the first set of assistance data and the second set of assistance data having different slot offsets, different bandwidths, different numbers of PRS repetitions, different frequency bands, different component carriers, or any combination thereof.

[0240] In some aspects of the method 1600, the method includes transmitting the request for the second set of assistance data based on a number of failed attempts by the SL device to transmit or measure PRS during the at least one COT window using the first set of assistance data exceeding a threshold number of failed attempts.

[0241] In some aspects of the method 1600, obtaining the at least one COT window includes receiving an indication of the at least one COT window from a network device.

[0242] In some aspects of the method 1600, the network device includes a sidelink UE; a location server; or a base station.

[0243] In some aspects of the method 1600, the threshold number of failed attempts includes a number of failed attempts by the SL device to access a channel for the positioning session during the at least one COT window; a number of failed attempts by the SL device to access a channel for a positioning occasion of the positioning session during the at least one COT window; or any combination thereof.

[0244] In some aspects of the method 1600, the first CAPC and the second CAPC are associated with a channel sensing parameter including one or more allowed contention window sizes associated with the first CAPC; a maximum contention window size associated with the first CAPC; a minimum contention window size associated with the first CAPC; a maximum channel occupancy time associated with the first CAPC; or any combination thereof.

[0245] In some aspects of the method 1600, obtaining the at least one COT window includes receiving an indication of the at least one COT window from a network device.

[0246] In some aspects of the method 1600, the network device includes a sidelink UE; a location server; or a base station.

[0247] As will be appreciated, a technical advantage of the method 1600 is that the SL device increases its CAPC during the positioning session in a situation where the SL device is unable to meet channel access requirements needed to transmit or measure PRS to satisfy requirements of the positioning session based on the current CAPC. The increased CAPC can provide the SL device with a channel access priority level that allows it to meet the channel access requirements.

[0248] In the detailed description above, various features are grouped together in examples. This manner of disclosure should not be understood as an intention that the example clauses are to be taken in a way that requires every feature to be in place for each and every example clause to achieve its goals. For example, various aspects are described as being part of one or more examples. Such aspects can be combined with aspects of other examples that are not explicitly mentioned in a particular clause. Such aspects will always be within the scope of the example clauses. Further, the various examples need not always educate the recipient of the various examples regarding what the various examples can not teach. Additionally, the various examples need not always provide information on why one feature is not in some examples but is in other examples. Such information is not necessary for the recipients of the various examples to practice the various examples. Such information is further not necessary to enable practitioners possessing an average skill in the art to practice the examples. Furthermore, the various aspects of the examples can be used together, in any combination, unless otherwise noted by the context of the relevant clause.

[0249] Various implementation examples are described in the following numbered clauses:

[0250] Clause 1. A method of wireless communication performed by a sidelink (SL) device, the method comprising: obtaining channel sensing information to determine availability of a channel for transmitting or measuring positioning reference signals (PRSs) of a positioning session; and transmitting, to one or more additional SL devices, an indication of at least one channel occupancy time (COT) window for transmitting or measuring the PRSs by the one or more additional SL devices during the positioning session, wherein the at least one COT is based on the channel sensing information.

[0251] Clause 2. The method of clause 1, further comprising: determining a positioning estimate of at least one target SL device based on PRSs measured during the at least one COT window.

[0252] Clause 3. The method of any of clauses 1-2, further comprising: receiving a positioning channel sensing threshold; and using the positioning channel sensing threshold to determine the availability of the channel for transmitting or measuring the PRSs of the positioning session.

[0253] Clause 4. The method of any of clauses 1-3, wherein: obtaining the channel sensing information comprises, at least in part, performing a channel sensing operation at the SL device; and the at least one COT window is determined based, at least in part, on the channel sensing information obtained during the channel sensing operation performed by the SL device.

[0254] Clause 5. The method of any one of clauses 1-4, wherein: obtaining the channel sensing information comprises at least in part obtaining the channel sensing information from the one or more further SL devices.

[0255] Clause 6. The method of clause 5, further comprising: transmitting, to the one or more further SL devices, a request for the channel sensing information from the one or more further SL devices.

[0256] Clause 7. The method of any one of clauses 1-6, wherein: determining the at least one COT window is further based on one or more COT windows reported by the one or more further SL devices.

[0257] Clause 8. The method of clause 7, further comprising: transmitting, to the one or more further SL devices, a request for the one or more COT windows determined at the one or more further SL devices.

[0258] Clause 9. The method of any one of clauses 1-8, wherein the SL device is: an anchor user equipment (UE); a server UE; or an initiating UE that initiates the positioning session.

[0259] Clause 10. The method of clause 9, wherein: the SL device is the initiating UE.

[0260] Clause 11. The method of clause 10, wherein: the initiating UE is a target SL device for which a positioning estimate is determined during the positioning session.

[0261] Clause 12. The method of any one of clauses 10-11, wherein: the at least one COT window is determined by the UE that initiates the positioning session.

[0262] Clause 13. A method of wireless communication performed by a network server, the method comprising: transmitting, to one or more sidelink (SL) devices, a first sensing threshold for use by the one or more SL devices in determining availability of a channel for transmitting or receiving data; and transmitting, to the one or more SL devices, a second sensing threshold for use by the one or more SL devices in determining the availability of the channel for transmitting or measuring a positioning reference signal (PRS) of a positioning session.

[0263] Clause 14. The method of clause 13, wherein: the second sensing threshold is based on a standardized threshold for channel sensing during the positioning session.

[0264] Clause 15. The method of any of clauses 13-14, wherein: the network server comprises a location server, a base station, an anchor user equipment (UE) operating as a network server for one or more additional sidelink devices, or a combination thereof.

[0265] Clause 16. A method of wireless communication performed by a network server, the method comprising: determining a plurality of channel occupancy time (COT) windows available for transmission or reception of positioning reference signals (PRSs) of a positioning session; and transmitting a plurality of sets of assistance data for use during the positioning session, wherein each set of assistance data of the plurality of sets of assistance data is based on a corresponding COT window of the plurality of COT windows.

[0266] Clause 17. The method of clause 16, wherein: the network server comprises a location server, a base station, an anchor user equipment (UE) operating as a network server for one or more sidelink devices, or a combination thereof.

[0267] Clause 18. The method of any of clauses 16-17, wherein: the plurality of sets of assistance data each comprise an indication of a corresponding set of user equipment (UEs) based on the corresponding COT window.

[0268] Clause 19. A sidelink (SL) device, comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: obtain channel sensing information to determine availability of a channel for transmission or measurement of positioning reference signals (PRSs) of a positioning session; and transmit, via the at least one transceiver, an indication of at least one channel occupancy time (COT) window to one or more additional SL devices for transmission or measurement of the PRSs by the one or more additional SL devices during the positioning session, wherein the at least one COT is based on the channel sensing information.

[0269] Clause 20. The SL device of clause 19, wherein the at least one processor is further configured to: determine a positioning estimate of at least one target SL device based on PRSs measured during the at least one COT window.

[0270] Clause 21. The SL device of any of clauses 19-20, wherein the at least one processor is further configured to: receive, via the at least one transceiver, a positioning channel sensing threshold; and use the positioning channel sensing threshold to determine the availability of the channel for transmission or measurement of the PRSs of the positioning session.

[0271] Clause 22. The SL device of any of clauses 19-21, wherein: obtaining the channel sensing information comprises, at least in part, performing a channel sensing operation at the SL device; and the at least one COT window is determined based at least in part on the channel sensing information obtained during the channel sensing operation performed by the SL device.

[0272] Clause 23. The SL device of any of clauses 19-22, wherein: obtaining the channel sensing information comprises, at least in part, obtaining the channel sensing information from the one or more other SL devices.

[0273] Clause 24. The SL device of clause 23, wherein the at least one processor is further configured to: transmit, via the at least one transceiver, a request to the one or more other SL devices for the channel sensing information from the one or more other SL devices.

[0274] Clause 25. The SL device of any of clauses 19-24, wherein: determining the at least one COT window is further based on one or more COT windows reported by the one or more other SL devices.

[0275] Clause 26. The SL device of clause 25, wherein the at least one processor is further configured to: transmit, via the at least one transceiver, a request to the one or more other SL devices for the one or more COT windows determined at the one or more other SL devices.

[0276] Clause 27. The SL device of any of clauses 19-26, wherein the SL device is: an anchor user equipment (UE); a server UE; or an initiating UE that initiates the positioning session.

[0277] Clause 28. The SL device of clause 27, wherein: the SL device is the initiating UE.

[0278] Clause 29. The SL device of clause 28, wherein: the initiating UE is a target SL device for which a positioning estimate is determined during the positioning session.

[0279] Clause 30. The SL device of any of clauses 28-29, wherein: the at least one COT window is determined by the UE that initiates the positioning session.

[0280] Clause 31. A network server, the network server comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: transmit, via the at least one transceiver, a first sensing threshold to one or more sidelink (SL) devices for use by the one or more SL devices in determining availability of a channel for transmitting or receiving data; and transmit, via the at least one transceiver, a second sensing threshold to the one or more SL devices for use by the one or more SL devices in determining the availability of the channel for transmitting or measuring a positioning reference signal (PRS) of a positioning session.

[0281] Clause 32. The network server of clause 31, wherein: the second sensing threshold is based on a standardized threshold for channel sensing during the positioning session.

[0282] Clause 33. The network server of any of clauses 31-32, wherein: the network server comprises a location server, a base station, an anchor user equipment (UE) operating as a network server for one or more additional sidelink devices, or a combination thereof.

[0283] Clause 34. A network server, the network server comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: determine a plurality of channel occupancy time (COT) windows available for transmitting or receiving a positioning reference signal (PRS) of a positioning session; and transmit, via the at least one transceiver, a plurality of sets of assistance data for use during the positioning session, wherein each set of assistance data of the plurality of sets of assistance data is based on a corresponding COT window of the plurality of COT windows.

[0284] Clause 35. The network server of clause 34, wherein: the network server comprises a location server, a base station, an anchor user equipment (UE) operating as a network server for one or more sidelink devices, or a combination thereof.

[0285] Clause 36. The network server of any of clauses 34-35, wherein: each of the plurality of sets of assistance data comprises an indication of a corresponding set of user equipment (UE) based on the corresponding COT window.

[0286] Clause 37. A sidelink (SL) device, the SL device comprising: means for obtaining channel sensing information to determine availability of a channel for transmitting or measuring positioning reference signals (PRS) of a positioning session; and means for transmitting, to one or more further SL devices, an indication of at least one channel occupancy time (COT) window for transmitting or measuring the PRS by the one or more further SL devices during the positioning session, wherein the at least one COT is based on the channel sensing information.

[0287] Clause 38. The SL device of clause 37, the SL device further comprising: means for determining a positioning estimate of at least one target SL device based on PRS measured during the at least one COT window.

[0288] Clause 39. The SL device of any one of clauses 37 to 38, the SL device further comprising: means for receiving a positioning channel sensing threshold; and means for determining the availability of the channel for transmitting or measuring the PRS of the positioning session using the positioning channel sensing threshold.

[0289] Clause 40. The SL device of any one of clauses 37 to 39, wherein: obtaining the channel sensing information comprises at least in part performing a channel sensing operation at the SL device; and the at least one COT window is determined based at least in part on the channel sensing information obtained during the channel sensing operation performed by the SL device.

[0290] Clause 41. The SL device of any one of clauses 37 to 40, wherein: obtaining the channel sensing information comprises at least in part obtaining the channel sensing information from the one or more further SL devices.

[0291] Clause 42. The SL device of clause 41, the SL device further comprising: means for transmitting, to the one or more further SL devices, a request for the channel sensing information from the one or more further SL devices.

[0292] Clause 43. The SL device of any one of clauses 37 to 42, wherein: the means for determining the at least one COT window is further based on one or more COT windows reported by the one or more further SL devices.

[0293] Clause 44. The SL device of clause 43, the SL device further comprising: means for transmitting, to the one or more further SL devices, a request for the one or more COT windows determined at the one or more further SL devices.

[0294] Clause 45. The SL device of any of clauses 37 to 44, wherein the SL device is: an anchor user equipment (UE); a server UE; or an initiating UE that initiates the positioning session.

[0295] Clause 46. The SL device of clause 45, wherein: the SL device is the initiating UE.

[0296] Clause 47. The SL device of clause 46, wherein: the initiating UE is a target SL device that determines its position estimate during the positioning session.

[0297] Clause 48. The SL device of any of clauses 46 to 47, wherein: the at least one COT window is determined by the UE that initiates the positioning session.

[0298] Clause 49. A network server, comprising: means for sending, to one or more sidelink (SL) devices, a first sensing threshold for use by the one or more SL devices in determining availability of a channel for transmitting or receiving data; and means for sending, to the one or more SL devices, a second sensing threshold for use by the one or more SL devices in determining the availability of the channel for transmitting or measuring a positioning reference signal (PRS) of a positioning session.

[0299] Clause 50. The network server of clause 49, wherein: the second sensing threshold is based on a standardized threshold for channel sensing during the positioning session.

[0300] Clause 51. The network server of any of clauses 49 to 50, wherein: the network server comprises a location server, a base station, an anchor user equipment (UE) operating as a network server for one or more additional sidelink devices, or a combination thereof.

[0301] Clause 52. A network server, comprising: means for determining a plurality of channel occupancy time (COT) windows available for transmitting or receiving a positioning reference signal (PRS) of a positioning session; and means for sending a plurality of sets of assistance data for use during the positioning session, wherein each set of assistance data of the plurality of sets of assistance data is based on a corresponding COT window of the plurality of COT windows.

[0302] Clause 53. The network server of clause 52, wherein: the network server comprises a location server, a base station, an anchor user equipment (UE) operating as a network server for one or more sidelink devices, or a combination thereof.

[0303] Clause 54. The network server of any of clauses 52 to 53, wherein: the plurality of sets of assistance data each comprise an indication of a corresponding set of user equipment (UE) based on the corresponding COT window.

[0304] Clause 55. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a sidelink (SL) device, cause the SL device to: obtain channel sensing information to determine an availability of a channel for transmitting or measuring a positioning reference signal (PRS) of a positioning session; and transmit, to one or more additional SL devices, an indication of at least one channel occupancy time (COT) window for transmitting or measuring the PRS by the one or more additional SL devices during the positioning session, wherein the at least one COT is based on the channel sensing information.

[0305] Clause 56. The non-transitory computer-readable medium of clause 55, further comprising computer-executable instructions that, when executed by the SL device, cause the SL device to: determine a positioning estimate of at least one target SL device based on a PRS measured during the at least one COT window.

[0306] Clause 57. The non-transitory computer-readable medium of any of clauses 55 to 56, further comprising computer-executable instructions that, when executed by the SL device, cause the SL device to: receive a positioning channel sensing threshold; and use the positioning channel sensing threshold to determine the availability of the channel for transmitting or measuring the PRS of the positioning session.

[0307] Clause 58. The non-transitory computer-readable medium of any of clauses 55 to 57, wherein: obtaining the channel sensing information comprises, at least in part, performing a channel sensing operation at the SL device; and the at least one COT window is determined based, at least in part, on the channel sensing information obtained during the channel sensing operation performed by the SL device.

[0308] Clause 59. The non-transitory computer-readable medium of any of clauses 55 to 58, wherein: obtaining the channel sensing information comprises, at least in part, obtaining the channel sensing information from the one or more additional SL devices.

[0309] Clause 60. The non-transitory computer-readable medium of clause 59, further comprising computer-executable instructions that, when executed by the SL device, cause the SL to: transmit, to the one or more further SL devices, a request for the channel sensing information from the one or more further SL devices.

[0310] Clause 61. The non-transitory computer-readable medium of any one of clauses 55 to 60, wherein: determining the at least one COT window is further based on one or more COT windows reported by the one or more further SL devices.

[0311] Clause 62. The non-transitory computer-readable medium of clause 61, further comprising computer-executable instructions that, when executed by the SL device, cause the SL device to: transmit, to the one or more further SL devices, a request for the one or more COT windows determined at the one or more further SL devices.

[0312] Clause 63. The non-transitory computer-readable medium of any one of clauses 55 to 62, wherein the SL device is: an anchor user equipment (UE); a server UE; or an initiating UE that initiates the positioning session.

[0313] Clause 64. The non-transitory computer-readable medium of clause 63, wherein: the SL device is the initiating UE.

[0314] Clause 65. The non-transitory computer-readable medium of clause 64, wherein: the initiating UE is a target SL device for which a positioning estimate is determined during the positioning session.

[0315] Clause 66. The non-transitory computer-readable medium of any one of clauses 64 to 65, wherein: the at least one COT window is determined by the UE that initiates the positioning session.

[0316] Clause 67. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network server, cause the network server to: transmit, to one or more sidelink (SL) devices, a first sensing threshold for use by the one or more SL devices in determining availability of a channel for transmitting or receiving data; and transmit, to the one or more SL devices, a second sensing threshold for use by the one or more SL devices in determining the availability of a channel for transmitting or measuring a positioning reference signal (PRS) of a positioning session.

[0317] Clause 68. The non-transitory computer-readable medium of clause 67, wherein: the second sensing threshold is based on a standardized threshold for channel sensing during the positioning session.

[0318] Clause 69. The non-transitory computer-readable medium of any one of clauses 67 to 68, wherein: the network server comprises a location server, a base station, an anchor user equipment (UE) operating as a network server for one or more additional sidelink devices, or a combination thereof.

[0319] Clause 70. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network server, cause the network server to: determine a plurality of channel occupancy time (COT) windows available for transmission or reception of positioning reference signals (PRS) for a positioning session; and transmit a plurality of sets of assistance data for use during the positioning session, wherein each set of assistance data of the plurality of sets of assistance data is based on a corresponding COT window of the plurality of COT windows.

[0320] Clause 71. The non-transitory computer-readable medium of clause 70, wherein: the network server comprises a location server, a base station, an anchor user equipment (UE) operating as a network server for one or more sidelink devices, or a combination thereof.

[0321] Clause 72. The non-transitory computer-readable medium of any one of clauses 70 to 71, wherein: the plurality of sets of assistance data each comprise an indication of a corresponding set of user equipment (UE) based on the corresponding COT window.

[0322] Those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that can be referenced throughout the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0323] Further, those skilled in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0324] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein can be implemented or performed with 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, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0325] The methods, sequences, and / or algorithms described in connection with the aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in Random-Access Memory (RAM), flash memory, Read-Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal (e.g., an UE). In the alternative, the processor and the storage medium can reside as discrete components in a user terminal.

[0326] In one or more example aspects, the functions described can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0327] While the foregoing disclosure shows illustrative aspects of the present disclosure, it should be noted that various changes and modifications could be made therein without departing from the scope of the present disclosure as defined by the appended claims. Moreover, the functions, steps and / or actions of the methods described herein need not be performed in any particular order. Furthermore, although elements of the present disclosure can be described or claimed in singular form, plural forms can also be considered unless explicitly stated otherwise.

Claims

1. A method of wireless communication performed by a sidelink (SL) device, the method comprising: obtaining channel sensing information to determine availability of a channel for transmitting or measuring positioning reference signals (PRSs) of a positioning session; and transmitting, to one or more additional SL devices, an indication of at least one channel occupancy time (COT) window for transmitting or measuring the PRSs by the one or more additional SL devices during the positioning session, wherein the at least one COT is based on the channel sensing information.

2. The method of claim 1, further comprising: determining a positioning estimate of at least one target SL device based on PRSs measured during the at least one COT window.

3. The method of claim 1, further comprising: receiving a positioning channel sensing threshold; and using the positioning channel sensing threshold to determine the availability of the channel for transmitting or measuring the PRSs of the positioning session.

4. The method of claim 1, wherein: obtaining the channel sensing information comprises, at least in part, performing a channel sensing operation at the SL device; and the at least one COT window is determined based, at least in part, on the channel sensing information obtained during the channel sensing operation performed by the SL device.

5. The method of claim 1, wherein: obtaining the channel sensing information comprises, at least in part, obtaining the channel sensing information from the one or more additional SL devices.

6. The method of claim 5, further comprising: transmitting, to the one or more additional SL devices, a request for the channel sensing information from the one or more additional SL devices.

7. The method of claim 1, wherein: determining the at least one COT window is further based on one or more COT windows reported by the one or more additional SL devices.

8. The method of claim 7, further comprising: transmitting, to the one or more additional SL devices, a request for the one or more COT windows determined at the one or more additional SL devices.

9. The method of claim 1, wherein the SL device is: an anchor user equipment (UE); a server UE; or an initiating UE that initiates the positioning session.

10. The method of claim 9, wherein: the SL device is the initiating UE.

11. The method of claim 10, wherein: the initiating UE is a target SL device that determines its positioning estimate during the positioning session.

12. The method of claim 10, wherein: the at least one COT window is determined by the UE that initiates the positioning session.

13. A method of wireless communication performed by a network server, the method comprising: transmitting, to one or more sidelink (SL) devices, a first sensing threshold for use by the one or more SL devices in determining availability of a channel for transmitting or receiving data; and transmitting, to the one or more SL devices, a second sensing threshold for use by the one or more SL devices in determining availability of the channel for transmitting or receiving data. transmitting, to the one or more SL devices, a second sensing threshold for use by the one or more SL devices in determining the availability of a channel for transmitting or measuring positioning reference signals (PRSs) of a positioning session.

14. The method of claim 13, wherein: the second sensing threshold is based on a standardized threshold for channel sensing during the positioning session.

15. The method of claim 13, wherein: the network server comprises a location server, a base station, an anchor user equipment (UE) operating as a network server for one or more additional sidelink devices, or a combination thereof.

16. A method of wireless communication performed by a network server, the method comprising: determining a plurality of channel occupancy time (COT) windows available for transmitting or receiving positioning reference signals (PRSs) of a positioning session; and transmitting a plurality of sets of assistance data for use during the positioning session, wherein each set of assistance data of the plurality of sets of assistance data is based on a corresponding COT window of the plurality of COT windows.

17. The method of claim 16, wherein: the network server comprises a location server, a base station, an anchor user equipment (UE) operating as a network server for one or more sidelink devices, or a combination thereof.

18. The method of claim 16, wherein: each of the plurality of sets of assistance data comprises an indication of a corresponding set of user equipments (UEs) based on the corresponding COT window.

19. A sidelink (SL) device, the SL device comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: obtain channel sensing information to determine availability of a channel for transmitting or measuring positioning reference signals (PRSs) of a positioning session; and transmit, via the at least one transceiver, an indication of at least one channel occupancy time (COT) window to one or more additional SL devices for use by the one or more additional SL devices in transmitting or measuring the PRSs during the positioning session, wherein the at least one COT is based on the channel sensing information.

20. The SL device of claim 19, wherein the at least one processor is further configured to: determine a positioning estimate of at least one target SL device based on PRSs measured during the at least one COT window.

21. The SL device of claim 19, wherein the at least one processor is further configured to: receive, via the at least one transceiver, a positioning channel sensing threshold; and determine the availability of the channel for transmitting or measuring the PRSs of the positioning session using the positioning channel sensing threshold.

22. The SL device of claim 19, wherein: obtaining the channel sensing information comprises, at least in part, performing a channel sensing operation at the SL device; and the at least one processor is further configured to: determine a positioning estimate of at least one target SL device based on PRSs measured during the at least one COT window. The at least one COT window is determined based at least in part on the channel sensing information obtained during the channel sensing operation performed by the SL device.

23. The SL device of claim 19, wherein: obtaining the channel sensing information comprises, at least in part, obtaining the channel sensing information from the one or more other SL devices.

24. The SL device of claim 23, wherein the at least one processor is further configured to: transmit, via the at least one transceiver, a request to the one or more other SL devices for the channel sensing information from the one or more other SL devices.

25. The SL device of claim 19, wherein: determining the at least one COT window is further based on one or more COT windows reported by the one or more other SL devices.

26. The SL device of claim 25, wherein the at least one processor is further configured to: transmit, via the at least one transceiver, a request to the one or more other SL devices for the one or more COT windows determined at the one or more other SL devices.

27. The SL device of claim 19, wherein the SL device is: an anchor user equipment (UE); a server UE; or an initiating UE that initiates the positioning session.

28. The SL device of claim 27, wherein: the SL device is the initiating UE.

29. The SL device of claim 28, wherein: the initiating UE is a target SL device for which a positioning estimate is determined during the positioning session.

30. The SL device of claim 28, wherein: the at least one COT window is determined by the UE that initiates the positioning session.

31. A network server, the network server comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: transmit, via the at least one transceiver, a first sensing threshold to one or more sidelink (SL) devices for use by the one or more SL devices in determining availability of a channel for transmitting or receiving data; and transmit, via the at least one transceiver, a second sensing threshold to the one or more SL devices for use by the one or more SL devices in determining the availability of a channel for transmitting or measuring a positioning reference signal (PRS) of a positioning session.

32. A network server, the network server comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: determine a plurality of channel occupancy time (COT) windows available for transmitting or receiving a positioning reference signal (PRS) of a positioning session; and transmit, via the at least one transceiver, a plurality of sets of assistance data for use during the positioning session, wherein each set of assistance data of the plurality of sets of assistance data is based on a corresponding COT window of the plurality of COT windows.

Images