Sidelink positioning status determination and reporting

Abstract

Techniques for wireless communication are disclosed. In one aspect, a user equipment (UE) receives a configuration of a first set of sidelink positioning reference signal (SL-PRS) resources configured for transmission by a first set of sidelink UEs including the UE, and determining a sidelink transmission state of a first subset of SL-PRS resources of the first set of SL-PRS resources based on a signal strength measurement of the first set of SL-PRS resources, availability information of the first set of SL-PRS resources, or both. A sidelink transmit status for a given UE may also be inferred from configuration information associated with and received at the given UE.

Description

Background Art 1. Technical Field

[0002] Aspects of the present disclosure relate generally to wireless communications.

[0003] 2. Description of related technologies

[0004] Wireless communication systems have evolved over many generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including transitional 2.5G and 2.75G networks), third generation (3G) high speed data, wireless service with Internet capabilities, and fourth generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). There are many different types of wireless communication systems in use today, including cellular systems 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), and the like.

[0005] The fifth generation (5G) wireless standard, known as New Radio (NR), enables higher data transfer speeds, a greater number of connections, and better coverage, among other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on a reference signal for positioning (RS-P), such as a downlink, uplink, or sidelink positioning reference signal (PRS)), and other technical enhancements compared to previous standards.

[0006] In addition, leveraging the increased data rates and reduced latency of 5G, device-to-device communication technology is being implemented to support wireless communications between vehicles, between vehicles and roadside infrastructure, between vehicles and pedestrians, between personal devices, etc. Summary of the invention

[0007] The following presents a simplified summary of the invention related to one or more aspects disclosed herein. Therefore, the following summary of the invention should neither be considered as an exhaustive overview related to all conceived aspects, nor should it be considered to identify key or decisive elements related to all conceived aspects or to delineate the scope associated with any particular aspect. Therefore, the sole purpose of the following summary of the invention is to present certain concepts related to one or more aspects of the mechanisms disclosed herein in a brief form before the detailed embodiments presented below.

[0008] In one aspect, a method for wireless communication performed by a user equipment (UE) includes: receiving a configuration of a first sidelink positioning reference signal (SL-PRS) resource set configured for transmission by a first sidelink UE set including the UE; and determining a sidelink transmission status of a first SL-PRS resource subset of the first SL-PRS resource set based on a signal strength measurement result of the first SL-PRS resource set, availability information of the first SL-PRS resource set, or both.

[0009] In one aspect, a wireless communication method performed by a user equipment (UE) includes: receiving configuration information associated with a location-based discontinuous reception (DRX) mode; obtaining a location of the UE; and when in an inactive state of the location-based DRX mode, sending a sidelink positioning reference signal (SL-PRS) based on the location.

[0010] In one aspect, a method of wireless communication performed by a user equipment (UE) includes: receiving a request to send an on-demand sidelink positioning reference signal (SL-PRS) during a time period during which the UE is requested to send the SL-PRS; refraining from transmitting, receiving, or both on a transmit channel, a receive channel, or both that conflicts with the requested on-demand SL-PRS; and sending the requested on-demand SL-PRS.

[0011] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, a configuration of a first side link positioning reference signal (SL-PRS) resource set configured for transmission by a first side link UE set; and determine a side link transmission state of a first SL-PRS resource subset of the first SL-PRS resource set based on a signal strength measurement result of the first SL-PRS resource set, availability information of the first SL-PRS resource set, or both.

[0012] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive configuration information associated with a location-based discontinuous reception (DRX) mode via the at least one transceiver; obtain a location of the UE; and when in an inactive state of the location-based DRX mode, send a sidelink positioning reference signal (SL-PRS) based on the location via the at least one transceiver.

[0013] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, a request to send an on-demand sidelink positioning reference signal (SL-PRS) during a time period during which the UE is requested to send the SL-PRS; refrain from transmitting, receiving, or both on a transmit channel, a receive channel, or both that conflict with the requested on-demand SL-PRS; and send the requested SL-PRS via the at least one transceiver.

[0014] In one aspect, a user equipment (UE) includes: a component for receiving a configuration of a first sidelink positioning reference signal (SL-PRS) resource set configured for transmission by a first sidelink UE set; and a component for determining a sidelink transmission state of a first SL-PRS resource subset based on a signal strength measurement result of the first SL-PRS resource set, availability information of the first SL-PRS resource set, or both.

[0015] In one aspect, a user equipment (UE) includes: a component for receiving configuration information associated with a location-based discontinuous reception (DRX) mode; a component for obtaining a location of the UE; and a component for sending a sidelink positioning reference signal (SL-PRS) based on the location when in an inactive state of the location-based DRX mode.

[0016] In one aspect, a user equipment (UE) includes: a component for receiving a request to send an on-demand sidelink positioning reference signal (SL-PRS) during a time period during which the UE is requested to send the SL-PRS; a component for refraining from transmitting, receiving, or both on a transmit channel, a receive channel, or both that conflicts with the requested on-demand SL-PRS; and a component for sending the requested on-demand SL-PRS.

[0017] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive a configuration of a first sidelink positioning reference signal (SL-PRS) resource set configured for transmission by a first set of sidelink UEs; and determine a sidelink transmission state of a first SL-PRS resource subset based on a signal strength measurement result of the first SL-PRS resource set, availability information of the first SL-PRS resource set, or both.

[0018] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive configuration information associated with a location-based discontinuous reception (DRX) mode; obtain a location of the UE; and, when in an inactive state of the location-based DRX mode, send a sidelink positioning reference signal (SL-PRS) based on the location.

[0019] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive a request to send an on-demand sidelink positioning reference signal (SL-PRS) during a time period during which the UE is requested to send the SL-PRS; refrain from transmitting, receiving, or both on a transmit channel, a receive channel, or both that conflict with the requested on-demand SL-PRS; and send the requested on-demand SL-PRS.

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

[0021] The accompanying drawings are presented to aid in describing various aspects of the present disclosure and are provided solely for illustration and not limitation of the various aspects.

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

[0023] Figure 2A , Figure 2B and Figure 2C Example wireless network structures according to aspects of the present disclosure are illustrated.

[0024] Figure 3A , Figure 3B and Figure 3C is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.

[0025] Figure 4 An example wireless communication system in which a vehicle user equipment (V-UE) is exchanging ranging signals with a roadside unit (RSU) and another V-UE is illustrated in accordance with aspects of the present disclosure.

[0026] Figure 5 Examples of various positioning methods supported in New Radio (NR) according to aspects of the present disclosure are illustrated.

[0027] Fig. 6A and Figure 6B Various interesting scenarios for sidelink-only or joint Uu and sidelink positioning according to aspects of the present disclosure are illustrated.

[0028] Figure 7 is a diagram illustrating an example frame structure according to aspects of the present disclosure.

[0029] Fig. 8A and Figure 8B is a diagram of example sidelink slot structures with and without feedback resources in accordance with aspects of the present disclosure.

[0030] Fig. 9 is a diagram illustrating example resource pools for positioning within a sidelink resource pool in accordance with aspects of the present disclosure.

[0031] Fig.10 is a diagram illustrating an example process for scheduling sidelink resources according to aspects of the present disclosure.

[0032] Fig.11 Example scenarios for sidelink activity in accordance with aspects of the present disclosure are illustrated.

[0033] FIG. 12A to FIG. 12C Example discontinuous reception (DRX) configurations in accordance with aspects of the present disclosure are illustrated.

[0034] Fig.13 is a diagram illustrating an example of a positioning method using DRX according to aspects of the present disclosure.

[0035] Fig.14 is an illustration of an example connection scenario for devices in proximity to a radio unit in accordance with aspects of the present disclosure.

[0036] Figures 15 to 17

[0013] Example methods of wireless communications in accordance with aspects of the present disclosure are illustrated. DETAILED DESCRIPTION

[0037] Various aspects of the present disclosure are provided in the following description and related drawings for various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of the present disclosure. Additionally, well-known elements of the present disclosure will not be described in detail or will be omitted to avoid making the relevant details of the present disclosure difficult to understand.

[0038] 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.

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

[0040] In addition, many aspects are described in terms of a sequence of actions to be performed by, for example, an element of a computing device. It will be appreciated that the various actions described herein may be performed by a specific circuit (e.g., an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of the two. Additionally, the sequence of actions described herein may be considered to be fully embodied in any form of non-transient computer-readable storage medium, in which a corresponding computer instruction set is stored, which, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of the present disclosure may be embodied in a variety of different forms, all of which have been contemplated to be within the scope of the subject matter claimed. In addition, for each of the various aspects described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions".

[0041] As used herein, the terms "user equipment" (UE), "vehicle UE" (V-UE), "pedestrian UE" (P-UE), and "base station" are not intended to be dedicated to or otherwise limited to any particular radio access technology (RAT), unless otherwise specified. In general, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., a vehicle onboard computer, a vehicle navigation device, a mobile phone, a router, a tablet computer, a laptop computer, an asset location device, a wearable device (e.g., a smart watch, glasses, an augmented reality (AR) / virtual reality (VR) headset, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.). A UE can be mobile or can be stationary (e.g., at certain times) and can communicate with a radio access network (RAN). As used herein, the term "UE" can be interchangeably referred to as a "mobile device," "access terminal" or "AT," "client device," "wireless device," "subscriber device," "subscriber terminal," "subscriber station," "user terminal" or UT, "mobile terminal," "mobile station," or variations thereof.

[0042] A V-UE is a type of UE and may be any vehicle-mounted wireless communication device, such as a navigation system, a warning system, a head-up display (HUD), an onboard computer, an in-vehicle infotainment system, an automated driving system (ADS), an advanced driver assistance system (ADAS), etc. Alternatively, a V-UE may be a portable wireless communication device (e.g., a mobile phone, a tablet computer, etc.) carried by a driver of a vehicle or a passenger in the vehicle. The term "V-UE" may refer to an in-vehicle wireless communication device or the vehicle itself, depending on the context. A P-UE is a type of UE and may be a portable wireless communication device carried by a pedestrian (i.e., a user who is not driving or riding a vehicle). In general, a UE may communicate with a core network via a RAN, and through the core network, the UE may be connected to an external network such as the Internet and to other UEs. Of course, other mechanisms for connecting to a 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 the Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc.), etc.

[0043] A base station may operate according to one of several RATs to communicate with a UE, depending on the network in which the base station is deployed, and may alternatively be referred to as an access point (AP), a network node, a Node B, an evolved Node B (eNB), a next generation eNB (ng-eNB), a new radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may primarily be used to support wireless access for a UE, including supporting data, voice, and / or signaling connections for the supported UE. In some systems, a base station may only provide edge node signaling functions, while in other systems, it may provide additional control and / or network management functions. The communication link by which a UE may transmit a signal to a base station is referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link by which a base station may transmit a signal to a UE is referred to as a downlink (DL) channel or a 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) may refer to a UL / reverse traffic channel or a DL / forward traffic channel.

[0044] The term "base station" may refer to a single physical transmit receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array 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 TRP may 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 TRP may be a serving base station that receives measurement reports from a UE and an adjacent base station whose reference radio frequency (RF) signal the UE is measuring. As used herein, since a TRP is a point by which a base station transmits and receives wireless signals, references to transmitting from a base station or receiving at a base station should be understood to refer to a specific TRP of a base station.

[0045] In some implementations of supporting UE positioning, the base station may not support wireless access for the UE (e.g., may not support data, voice, and / or signaling connections for the UE), but instead may send reference RF signals to the UE for measurement by the UE and / or may receive and measure signals sent by the UE. Such base stations may be referred to as positioning beacons (e.g., when sending RF signals to the UE) and / or as position measurement units (e.g., when receiving and measuring RF signals from the UE).

[0046] An "RF signal" includes an electromagnetic wave of a given frequency that transmits information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" where it is clear from the context that the term "signal" refers to a wireless signal or an RF signal.

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

[0048] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through a backhaul link 122, and interface with one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 may be integrated with the base station 102. The UE 104 may communicate with the location server 172 directly or indirectly. For example, the UE 104 may communicate with the location server 172 via the base station 102 currently serving the UE 104. The UE 104 may 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), etc. For signaling purposes, communication between UE 104 and location server 172 may be represented as an indirect connection (e.g., through core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with intermediate nodes (if any) omitted from the signaling diagram for clarity.

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

[0050] Base station 102 may communicate wirelessly with UE 104. Each of base stations 102 may provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells may be supported by base station 102 in each geographic coverage area 110. A "cell" is a logical communication entity used to communicate with a base station (e.g., on a frequency resource, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.), and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that may provide access to different types of UEs. Because a cell is supported by a specific base station, the term "cell" may refer to one or both of a logical communication entity and a base station supporting it, depending on the context. In some cases, the term "cell" may also refer to a geographic coverage area (eg, a sector) of a base station, as long as a carrier frequency can be detected and used for communications within some portion of the geographic coverage area 110.

[0051] Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover zone), some of the geographic coverage areas 110 may substantially overlap with a larger geographic coverage area 110. For example, a small cell base station 102' (labeled "SC" for "small cell") may have a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB) that may provide services to a restricted group referred to as a closed subscriber group (CSG).

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

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

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

[0055] The wireless communication system 100 may also include a mmW base station 180, which may operate in millimeter wave (mmW) frequencies and / or near mmW frequencies to communicate with UE 182. Extremely high frequency (EHF) is a part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz, and a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW may extend downward to a frequency of 3 GHz, where the wavelength is 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have high path loss and relatively short distances. The mmW base station 180 and the UE 182 may utilize beamforming (transmitting and / or receiving) via the mmW communication link 184 to compensate for extremely high path loss and short distances. In addition, it should be understood that in an alternative configuration, one or more base stations 102 may also use mmW or near mmW and beamforming for transmission. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.

[0056] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). 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 (in terms of data rate) and stronger RF signal to the receiving device. In order 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") that produces RF beams that can be "steered" to point in different directions without actually moving the antennas. Specifically, the RF current from the transmitter is fed to each antenna in the correct phase relationship so that the radio waves from the separate antennas are added together to increase the radiation in the desired direction while canceling to suppress the radiation in the undesired direction.

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

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

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

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

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

[0062] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz–71 GHz), FR4 (52.6 GHz–114.25 GHz), and FR5 (114.25 GHz–300 GHz). Each of these higher frequency bands falls within the EHF band.

[0063] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used in this article, the term "below 6 GHz" and the like can be broadly referred to as frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" and the like are used in this article, they can be broadly referred to as 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.

[0064] 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 a carrier operating on the primary frequency (e.g., FR1) used by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common control channels and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured once an RRC connection is established between the UE 104 and the anchor carrier, and which can be used to provide additional radio resources. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, since the primary uplink carrier and the primary downlink carrier are usually UE-specific, those UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carrier. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier on which a base station communicates, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. are used interchangeably.

[0065] For example, still referring to Figure 1 , one of the frequencies used by the macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies used by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission rate and / or data 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.

[0066] exist Figure 1 In the example of FIG. 1 , the UE illustrated (for simplicity, in Figure 1Any UE in the embodiment of the present invention (shown as a single UE 104 in FIG. 1 ) may receive a signal 124 from one or more earth orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SVs 112 may be part of a satellite positioning system that the UEs 104 may use as an independent source of location information. A satellite positioning system typically includes a transmitter system (e.g., SV 112) positioned to enable a receiver (e.g., UE 104) to determine its position on or above the earth based at least in part on a positioning signal (e.g., signal 124) received from the transmitter. Such a transmitter typically transmits a signal that is marked with a repeating pseudo-random noise (PN) code of a set number of chips. Although typically located in the SV 112, the transmitter may sometimes be located on a ground-based control station, base station 102, and / or other UEs 104. The UE 104 may include one or more dedicated receivers that are specifically designed to receive the signal 124 in order to derive geographic location information from the SV 112.

[0067] In a satellite positioning system, the use of signal 124 may be enhanced by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential corrections, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multifunction Satellite Augmentation System (MSAS), Global Positioning System (GPS) Assisted Geographic Augmented Navigation, or GPS and Geographic Augmented Navigation System (GAGAN), etc. Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0068] In one aspect, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as an improved base station 102 (without a ground antenna) or a network node in a 5GC. This element in turn will provide access to other elements in the 5G network, and ultimately provide access to entities outside the 5G network (such as Internet web servers and other user devices). In this way, instead of or in addition to communication signals from a ground base station 102, a UE 104 can receive communication signals (e.g., signal 124) from a SV 112.

[0069] Especially taking advantage of the increased data rates and reduced latency of NR, vehicle-to-everything (V2X) communication technology is 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)). The goal is to enable vehicles to sense the environment around them and communicate that information to other vehicles, infrastructure, and personal mobile devices. Such vehicle communications will enable safety, mobility, and environmental advances that current technology cannot provide. Once fully implemented, the technology is expected to reduce non-fault vehicle collisions by 80%.

[0070] Still reference Figure 1 , the wireless communication system 100 may include a plurality of V-UEs 160 that may communicate with a base station 102 over a communication link 120 using a Uu interface (i.e., an air interface between a UE and a base station). The V-UEs 160 may also communicate directly with each other over a wireless side link 162, with a roadside unit (RSU) 164 (roadside access point) over a wireless side link 166, or with a sidelink-capable UE 104 over a wireless side link 168 using a PC5 interface (i.e., an air interface between sidelink-capable UEs). A wireless side link (or simply "sidelink") is an adaptation of a core cellular network (e.g., LTE, NR) standard that allows direct communication between two or more UEs without communicating through a base station. Sidelink communications may be unicast or multicast and may 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 V-UEs in a group of V-UEs 160 utilizing sidelink communication may be within the geographic coverage area 110 of the base station 102. Other V-UEs 160 in such a group may be outside the geographic coverage area 110 of the base station 102, or otherwise unable to receive transmissions from the base station 102. In some cases, groups of V-UEs 160 communicating via sidelink communication may utilize a one-to-many (1:M) system in which each V-UE 160 transmits to each other V-UE 160 in the group. In some cases, the base station 102 facilitates the scheduling of resources for sidelink communication. In other cases, sidelink communication is performed between V-UEs 160 without involving the base station 102.

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

[0072] In one aspect, the sidelinks 162, 166, 168 may be cV2X links. The first generation of cV2X has been standardized in LTE, and the 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 the licensed ITS bands below 6 GHz. Other frequency bands may be allocated in other countries. Thus, as a specific example, the medium of interest utilized by the sidelinks 162, 166, 168 may correspond to at least a portion of the licensed ITS bands below 6 GHz. However, the present disclosure is not limited to this frequency band or cellular technology.

[0073] In one aspect, the side links 162, 166, 168 may be dedicated short-range communication (DSRC) links. DSRC is a unidirectional or bidirectional short-range to medium-range wireless communication protocol that uses the Wireless Access in Vehicular Environment (WAVE) protocol (also known as IEEE 802.11p) for V2V, V2I, and V2P communications. IEEE 802.11p is an approved modification to the IEEE 802.11 standard and operates in the licensed ITS band at 5.9 GHz (5.85 GHz-5.925 GHz) in the United States. In Europe, IEEE 802.11p operates in the ITS G5A band (5.875 GHz-5.905 MHz). Other frequency bands may be allocated in other countries. The V2V communications briefly described above occur on a safety channel, which is typically a 10 MHz channel dedicated to 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 regulations, toll collection, parking automation, etc. Thus, as a specific example, the medium of interest utilized by the sidelinks 162, 166, 168 may correspond to at least a portion of the licensed ITS band at 5.9 GHz.

[0074] Alternatively, the medium of interest may correspond to at least a portion of an unlicensed frequency band shared among various RATs. Although different licensed frequency bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), these systems (particularly those employing small cell access points) have recently expanded 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.11x WLAN technology 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, and the like.

[0075] Communication between V-UEs 160 is referred to as V2V communication, communication between V-UEs 160 and one or more RSUs 164 is referred to as V2I communication, and communication between V-UEs 160 and one or more UEs 104 (where these UEs 104 are P-UEs) is referred to as V2P communication. V2V communication between V-UEs 160 may include, for example, information about the position, speed, acceleration, heading, and other vehicle data of these V-UEs 160. V2I information received at V-UEs 160 from one or more RSUs 164 may include, for example, road rules, parking automation information, etc. V2P communication between V-UEs 160 and UEs 104 may include information about, for example, the position, speed, acceleration, and heading of the V-UEs 160 and the position, speed (for example, in the case where the UE 104 is carried by a user on a bicycle) and heading of the UEs 104.

[0076] Note that although Figure 1 Only two of the UEs are illustrated as V-UEs (V-UE 160), but any of the illustrated UEs (e.g., UE 104, 152, 182, 190) may be V-UEs. In addition, although only these V-UEs 160 and a single UE 104 have been illustrated as being connected via a side link, Figure 1Any of the illustrated UEs (whether V-UE, P-UE, etc.) may be capable of sidelink communications. Furthermore, although only UE 182 is described as being capable of beamforming, any of the illustrated UEs (including V-UE 160) may be capable of beamforming. In the event that V-UE 160 is capable of beamforming, they may beamform toward each other (i.e., toward other V-UE 160), toward RSU 164, toward other UEs (e.g., UE 104, 152, 182, 190), etc. Thus, in some cases, V-UE 160 may utilize beamforming on sidelinks 162, 166, and 168.

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

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

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

[0080] Figure 2B Another example wireless network structure 240 is illustrated. 5GC 260 (which may correspond to Figure 2AThe 5GC 210 in the 5GC 210 can be functionally considered as a control plane function provided by an access and mobility management function (AMF) 264, and a user plane function provided by a user plane function (UPF) 262, which operate in conjunction to form a core network (i.e., 5GC 260). The functions of the AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any UE described herein) and a session management function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between the UE 204 and a short message service 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 receives an intermediate key established as a result of the UE 204 authentication process. In case of authentication based on UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), AMF 264 retrieves security material from AUSF. The functionality of AMF 264 also includes Security Context Management (SCM). SCM receives keys from SEAF, which it uses to derive access network specific keys. The functionality of AMF 264 also includes location service management for regulatory services, for transmission of location service messages between UE 204 and Location Management Function (LMF) 270 (which acts as location server 230), for transmission of location service messages between NG-RAN 220 and LMF 270, for allocation of Evolved Packet System (EPS) bearer identifiers for interoperation with EPS, and UE 204 mobility event notifications. In addition, AMF 264 also supports functionality for non-3GPP (Third Generation Partnership Project) access networks.

[0081] The functions of UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, service steering), lawful interception (user plane collection), service usage reporting, user plane quality of service (QoS) handling (e.g., uplink / downlink rate enforcement, reflective QoS marking in downlink), uplink service verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering, and transmitting and forwarding one or more "end markers" to the source RAN node. UPF 262 can also support the delivery of location service messages between UE 204 and a location server (such as SLP 272) on the user plane.

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

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

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

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

[0086] The functionality of the gNB 222 may be divided between a gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically assigned to the gNB-DU 228, including delivery of user data, mobility control, radio access network sharing, positioning, session management, etc. More specifically, the gNB-CU 226 generally hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that generally hosts the Radio Link Control (RLC) and Medium Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 may 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 one or more gNB-DUs 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is typically hosted by one or more independent gNB-RUs 229, which 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, communicates with the gNB-DU 228 via the RLC layer and the MAC layer, and communicates with the gNB-RU 229 via the PHY layer.

[0087] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, or a network equipment (such as a base station or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, a 5GNB, an access point (AP), a transmit receive point (TRP), or a cell, etc.) can be implemented as an aggregated base station (also referred to as a standalone base station or a monolithic base station) or a decomposed base station.

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

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

[0090] Figure 2C 2 is a diagram illustrating an example disaggregated base station architecture according to aspects of the present disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CUs 226) that may communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 through one or more disaggregated base station units (e.g., 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 CU 280 may communicate with one or more distributed units (DUs) 285 (e.g., gNB-DUs 228) via corresponding midhaul links (e.g., F1 interfaces). The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via corresponding fronthaul links. The RU 287 can communicate with a corresponding UE 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 can be served by multiple RUs 287 simultaneously.

[0091] 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) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired transmission medium or a wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0092] In some aspects, CU 280 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 280. CU 280 may 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 specific implementations, CU 280 may 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 unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 280 may be implemented to communicate with DU 285 for network control and signaling.

[0093] DU 285 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 287. In some aspects, DU 285 may host 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.) depending at least in part on a functional split, such as a functional split defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 285 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 285 or with control functions hosted by CU 280.

[0094] The lower layer functionality may be implemented by one or more RUs 287. In some deployments, the RU 287 controlled by the DU 285 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 287 may be implemented to handle over-the-air (OTA) communications with one or more UEs 204. In some specific implementations, real-time and non-real-time aspects of control plane communications and user plane communications with the RU 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration may enable the DU 285 and the CU 280 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

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

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

[0097] In some implementations, in order to generate an AI / ML model 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. Such information may be utilized by the near-RT RIC 259 and may be received from a non-network data source or from a network function 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 for performance and employ AI / ML models to perform corrective actions through the SMO framework 255 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0098] Figure 3A , Figure 3B and Figure 3C 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 depicted in the 5GC 210 / 260 (such as a dedicated network) are shown to support operations as described herein. It should be understood that these components can be implemented in different types of devices with different specific implementations (e.g., in an ASIC, in a system on a chip (SoC), etc.). The illustrated components are also incorporated into other devices in the 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 include 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.

[0099] UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, which provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for preventing transmitting, etc.) for communicating via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. 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.) on a wireless communication medium of interest (e.g., a certain set of time / frequency resources in a specific spectrum). The WWAN transceivers 310 and 350 can be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to the specified RAT, and conversely, receive and decode the signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, the WWAN transceivers 310 and 350 include: one or more transmitters 314 and 354 for transmitting and encoding the signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding the signals 318 and 358, respectively.

[0100] At least in some cases, the UE 302 and the base station 304 each further 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 for communicating over the wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, The short-range wireless transceivers 320 and 360 are components (e.g., components for sending, components for receiving, components for measuring, components for tuning, components for preventing sending, etc.) for communicating with other network nodes (such as other UEs, access points, base stations, etc.) using a PC5, dedicated short-range communication (DSRC), wireless access for vehicle environments (WAVE), near field communication (NFC), etc.). The short-range wireless transceivers 320 and 360 can be configured in different ways to send and encode signals 328 and 368 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, the short-range wireless transceivers 320 and 360 include: one or more transmitters 324 and 364 for sending and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As a specific example, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Transceiver, Transceiver and / or transceiver, NFC transceiver or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceiver.

[0101] 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 may be connected to one or more antennas 336 and 376, respectively, and may provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. In the case where the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 may be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian regional navigation satellite system (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. In the case where the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. The satellite signal receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request appropriate information and operations from 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 UE 302 and base station 304, respectively.

[0102] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide means (e.g., means for sending, means for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 through one or more wired or wireless backhaul links. As another example, the network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 through one or more wired or wireless backhaul links, or communicate with other network entities 306 through one or more wired or wireless core network interfaces.

[0103] The transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes a transmitter circuit system (e.g., transmitters 314, 324, 354, 364) and a receiver circuit system (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., embodying the transmitter circuit system and the receiver circuit system in a single device), in some implementations may include separate transmitter circuit systems and separate receiver circuit systems, or may be embodied in other ways in other implementations. The transmitter circuit system and the receiver circuit system of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform transmit "beamforming", as described herein. Similarly, the wireless receiver circuitry (e.g., receiver 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter circuitry and the receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366) so that the corresponding device can only receive or only transmit at a given time, rather than both receive and transmit at the same time. The wireless transceivers (eg, WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listening module (NLM) or the like for performing various measurements.

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

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

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

[0107] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide a means for sensing or detecting movement and / or orientation information that is independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. Exemplarily, sensor 344 may include an accelerometer (e.g., a microelectromechanical 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 motion detection sensor. In addition, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate positioning in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

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

[0109] Referring to the one or more processors 384 in more detail, in a downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery 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.

[0110] The transmitter 354 and the receiver 352 may implement layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on transport channels, forward error correction (FEC) coding / decoding of transport channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles the 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 may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a 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 pre-decoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine coding and modulation schemes and for spatial processing. Channel estimates may be derived based on a reference signal and / or channel condition feedback sent by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a corresponding spatial stream for transmission.

[0111] At the UE 302, the receiver 312 receives the signal through its corresponding antenna 316. The receiver 312 recovers the information modulated onto the RF carrier and provides the information to 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 into a single OFDM symbol stream by the receiver 312. 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 includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the signal constellation point that is most likely to be sent by the base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent by the base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332, which implement layer 3 (L3) and layer 2 (L2) functionality.

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

[0113] Similar to the functionality described in conjunction with downlink transmissions performed by the base station 304, the one or more processors 332 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery 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 transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

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

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

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

[0117] For convenience, UE 302, base station 304 and / or network entity 306 may Figure 3A , Figure 3B and Figure 3C, is shown as including various components that can be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionality in different designs. Specifically, FIG. 3A to FIG. 3C The various components in are optional in alternative configurations, and various aspects include configurations that may vary due to design choice, cost, use of the device, or other considerations. For example, in Figure 3A In the case of , a specific implementation of UE 302 may omit WWAN transceiver 310 (e.g., a wearable device or tablet or PC or laptop may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), or may omit short-range wireless transceiver 320 (e.g., only cellular, etc.), or may omit satellite signal receiver 330, or may omit sensor 344, etc. In another example, in Figure 3B In the case of a wireless cellular network, a specific implementation of the base station 304 may omit the WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or may omit the short-range wireless transceiver 360 (e.g., cellular only, etc.), or may omit the satellite receiver 370, etc. For the sake of brevity, illustrations of various alternative configurations are not provided herein, but will be readily apparent to those skilled in the art.

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

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

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

[0121] Figure 4An example wireless communication system 400 is illustrated in accordance with aspects of the present disclosure, in which a V-UE 404 is exchanging ranging signals with an RSU 410 and another V-UE 406. As illustrated in FIG6 , a wideband (e.g., FR1) ranging signal (e.g., a Zadoff Chu sequence) is sent by two endpoints (e.g., the V-UE 404 and the RSU 410 and the V-UE 404 and the V-UE 406). In one aspect, the ranging signal may be a sidelink positioning reference signal (SL-PRS) sent by the V-UEs 404 and 406 involved on an uplink resource. After receiving a ranging signal from a transmitter (e.g., V-UE 404), a receiver (e.g., RSU 410 and / or V-UE 406) responds by transmitting a ranging signal that includes a measurement of the difference between the time the ranging signal was received and the time the response ranging signal was sent (referred to as the receiver's received-to-transmit (Rx-Tx) time difference measurement).

[0122] After receiving the response ranging signal, the transmitter (or other positioning entity) can calculate the RTT between the transmitter and the receiver based on the receiver's Rx-Tx time difference measurement and the measurement of the difference between the transmission time of the first ranging signal and the reception time of the response ranging signal (referred to as the transmitter's transmit-to-receive (Tx-Rx) time difference measurement). The transmitter (or other positioning entity) uses the RTT and the speed of light to estimate the distance between the transmitter and the receiver. If one or both of the transmitter and the receiver are capable of beamforming, the angle between the V-UE 604 and the V-UE 606 can also be determined. In addition, if the receiver provides its global positioning system (GPS) position in the response ranging signal, the transmitter (or other positioning entity) may be able to determine the absolute position of the transmitter, rather than the relative position of the transmitter relative to the receiver.

[0123] As will be appreciated, ranging accuracy increases with the bandwidth of the ranging signal. Specifically, a higher bandwidth can better separate the different multipaths of the ranging signal.

[0124] Note that this positioning procedure assumes that the V-UE involved is time synchronized (i.e., its system frame time is the same as other V-UEs, or has a known offset relative to other V-UEs). Figure 4 Two V-UEs are illustrated, but as will be understood, they need not be V-UEs, and may instead be any other type of UE capable of sidelink communication.

[0125] NR supports a variety of cellular network-based positioning technologies, 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 5 Examples of various positioning methods according to various aspects of the present disclosure are illustrated. In the OTDOA or DL-TDOA positioning procedure illustrated in scenario 510, the UE measures the difference between the arrival times (ToA) of reference signals (e.g., positioning reference signals (PRS)) received from paired base stations (referred to as reference signal time difference (RSTD) or arrival time difference (TDOA) measurements), and reports these differences to a positioning entity. More specifically, the UE receives identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in auxiliary data. The UE then measures the RSTD between the reference base station and each of the non-reference base stations. Based on the known positions of the base stations involved 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 position of the UE.

[0126] For DL-AoD positioning illustrated in scenario 520, the positioning entity uses the measurement report of the received signal strength measurement results of multiple downlink transmission beams from the UE to determine the angle between the UE and the transmitting base station. The positioning entity can then estimate the position of the UE based on the determined angle and the known position of the transmitting base station.

[0127] 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)) sent by the UE to multiple base stations. Specifically, the UE sends 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 reception time of the reference signal (referred to as relative time of arrival (RTOA)) to a positioning entity (e.g., a location server) that knows the location and relative timing of the base stations involved. Based on the receive-to-receive (Rx-Rx) time difference between the reported RTOA of the reference base station and the reported RTOA of each non-reference base station, the known location of the base stations, and their known timing offsets, the positioning entity can use TDOA to estimate the position of the UE.

[0128] 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. The positioning entity uses the signal strength measurements and the angle of the receive beam to determine the angle between the UE and the base station. Based on the determined angle and the known location of the base station, the positioning entity can then estimate the location of the UE.

[0129] Downlink and uplink based positioning methods include: enhanced cell ID (E-CID) positioning and multiple round trip time (RTT) positioning (also referred to as "multi-cell RTT" and "multi-RTT"). In the RTT procedure, a first entity (e.g., a base station or UE) sends a first RTT-related signal (e.g., a PRS or SRS) to a second entity (e.g., a UE or a base station), and the second entity sends a second RTT-related signal (e.g., an SRS or PRS) back to the first entity. Each entity measures the time difference between the arrival time (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. The time difference is called the received to transmitted (Rx-Tx) time difference. The Rx-Tx time difference measurement can be made or adjusted to include only the time difference between the nearest time slot boundary of the received signal and the transmitted signal. The two entities may then transmit their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round trip propagation time (i.e., RTT) between the two entities based on the two Rx-Tx time difference measurements (e.g., calculated as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity may transmit its Rx-Tx time difference measurements to another entity, which then calculates the RTT. The distance between the two entities may be determined based on the RTT and a known signal speed (e.g., the speed of light). For multi-RTT positioning illustrated in scenario 530, a first entity (e.g., a UE or a base station) performs an RTT positioning procedure with a plurality of second entities (e.g., a plurality of base stations or UEs) to enable the position of the first entity to be determined based on the distance to the second entity and the known position of the second entity (e.g., using multilateration). RTT and multi-RTT methods may be combined with other positioning techniques (such as UL-AoA and DL-AoD) to improve position accuracy, as illustrated in scenario 540.

[0130] The E-CID positioning method is based on radio resource management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), and the identifiers of detected neighboring base stations, estimated timing and signal strength. The UE's position is then estimated based on this information and the known locations of the base stations.

[0131] To assist the positioning operation, the location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE. For example, the assistance data may include: an identifier of the base station (or cell / TRP of the base station) from which the reference signal is measured, reference signal configuration parameters (e.g., the number of consecutive time slots including PRS, the periodicity of consecutive time slots including PRS, the silent sequence, the frequency hopping sequence, the reference signal identifier, the reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, the assistance data may originate directly from the base station itself (e.g., in a periodically broadcast overhead message, etc.). In some cases, the UE itself may be able to detect neighboring network nodes without using assistance data.

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

[0133] The position estimate may be referred to by other names such as a position estimate, a position, a fix, a position fix, a fix, etc. The position estimate may be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or may be municipal and include a street address, a postal address, or some other verbal description of the location. The position estimate may be further qualified relative to some other known position or qualified in absolute terms (e.g., using latitude, longitude, and possibly altitude). The position estimate may 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).

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

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

[0136] Various frame structures may be used to support downlink transmissions and uplink transmissions between network nodes (eg, base stations and UEs). Figure 7 700 is a diagram illustrating an example frame structure according to aspects of the present disclosure. The frame structure may be a downlink frame structure or an uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.

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

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

[0139] exist Figure 7 In the example of , a parameter set of 15 kHz is used. Therefore, in the time domain, a 10 ms frame is divided into 10 equally sized subframes, each subframe is 1 ms, and each subframe includes one time slot. Figure 7 , time is represented horizontally (on the X-axis), where time increases from left to right, while frequency is represented vertically (on the Y-axis), where frequency increases (or decreases) from bottom to top.

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

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

[0142] In addition to downlink-based, uplink-based, and downlink and uplink-based positioning methods, NR also supports various sidelink positioning techniques. For example, link-level ranging signals can be used to estimate the distance between V-UE pairs or between V-UE and roadside units (RSUs), similar to the round-trip time (RTT) positioning procedure.

[0143] Sidelink communication occurs in either the transmit resource pool or the receive resource pool. In the frequency domain, the minimum resource allocation unit is a subchannel (e.g., a set of consecutive PRBs in the frequency domain). In the time domain, resource allocation is performed in a time slot interval. However, some time slots are not available for sidelinks, and some time slots contain feedback resources. In addition, sidelink resources can be (pre)configured to occupy less than 14 symbols in a time slot.

[0144] The sidelink resources are configured at the Radio Resource Control (RRC) layer. The RRC configuration can be pre-configured (e.g., preloaded on the UE) or configured (e.g., from a serving base station).

[0145] The NR sidelink supports Hybrid Automatic Repeat Request (HARQ) retransmissions. Fig. 8A 900 is a diagram of an example time slot structure without feedback resources according to aspects of the present disclosure. Fig. 8AIn the example of , time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one orthogonal frequency division multiplexing (OFDM) symbol, and 14 symbols constitute a time slot. In the frequency domain, the height of each block is one subchannel. Currently, the (pre-)configured subchannel size can be selected from the set of {10, 15, 20, 25, 50, 75, 100} physical resource blocks (PRBs).

[0146] For a sidelink slot, the first symbol is a repetition of the previous symbol and is used for automatic gain control (AGC) settings. Fig. 8A This is illustrated in the example by vertical and horizontal hashing. Fig. 8A As shown, for the sidelink, the physical sidelink control channel (PSCCH) and the physical sidelink shared channel (PSSCH) are transmitted in the same time slot. Similar to the physical downlink control channel (PDCCH), the PSCCH carries control information about the sidelink resource allocation and a description of the sidelink data sent to the UE. Similarly, similar to the physical downlink shared channel (PDSCH), the PSSCH carries the user data of the UE. Fig. 8A In the example of , the PSCCH occupies half of the bandwidth of the subchannel and occupies only three symbols. Finally, the gap symbol appears after the PSSCH.

[0147] Figure 8B 9 is a diagram of an example time slot structure with feedback resources according to aspects of the present disclosure. Figure 8B In the example of , time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one OFDM symbol, and 14 symbols constitute a time slot. In the frequency domain, the height of each block is one subchannel.

[0148] Apart from Figure 8B The illustrated time slot structure includes, in addition to feedback resources, Figure 8B The illustrated time slot structure is similar to Fig. 8A The time slot structure is similar to that illustrated in . Specifically, the two symbols at the end of the time slot have been dedicated to the physical side link feedback channel (PSFCH). The first PSFCH symbol is a repetition of the second PSFCH symbol used for AGC setting. In addition to the gap symbol after the PSSCH, there is also a gap symbol after two PSFCH symbols. Currently, the resources for PSFCH can be configured with a periodicity selected from a set of {0,1,2,4} time slots.

[0149] Another aspect of sidelink positioning is the configuration of a sidelink resource pool (RP-P) for positioning. The 12 symbols between the first and last symbols (gap) of a sidelink slot (for AGC) in the time domain and the allocated subchannels in the frequency domain form a resource pool for sidelink transmission and / or reception. RP-Ps may be configured specifically within a resource pool for positioning purposes. Each RP-P includes an offset, a periodicity, a number of consecutive symbols within a slot (e.g., as few as one symbol), and / or a bandwidth within a component carrier (or across multiple component carriers). In addition, each RP-P may be associated with a certain area or with a distance from a reference location.

[0150] A base station (or UE) may assign one or more resource configurations from the RP-P to another UE. Additionally or alternatively, a UE (e.g., a relay or remote UE) may request one or more RP-P configurations, and the UE may include one or more of the following in the request: (1) location information (or zone identifier) ​​of the UE; (2) periodicity; (3) bandwidth; (4) offset; (5) number of symbols; and (6) whether a configuration with "low interference" is required (which may be determined by the assigned quality of service (QoS) or priority).

[0151] The base station or UE may configure / assign rate matching resources or RP-P for rate matching / silencing to the sidelink UE, so that when there is a conflict between the assigned resources and another resource pool containing data (PSSCH) and / or control (PSCCH), the sidelink UE is expected to rate match / silence / puncture the data, DMRS and / or CSI-RS within the conflicting resources. This will achieve orthogonalization between positioning and data transmission to increase the coverage of the PRS signal.

[0152] Fig. 9 900 is a diagram illustrating an example of a resource pool for positioning within a side link resource pool according to aspects of the present disclosure. Fig. 9 In the example of , time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one orthogonal frequency division multiplexing (OFDM) symbol, and 14 symbols constitute a time slot. In the frequency domain, the height of each block is one subchannel.

[0153] exist Fig. 9In the example of , the entire time slot (except the first symbol and the last symbol) can be a resource pool for sidelink transmission and / or reception. That is, any symbol except the first symbol and the last symbol can be allocated for transmission and / or reception. However, the RP-P for sidelink transmission / reception is allocated in the last four front slot symbols of the time slot. Therefore, non-side link positioning data (such as user data, CSI-RS, and control information) can only be sent in the first eight post-AGC symbols, but not in the last four front slot symbols to prevent conflicts with the configured RP-P. Non-side link positioning data that could have been sent in the last four front slot symbols can be punctured or silenced, or non-side link data that would normally span more than eight post-AGC symbols can be rate matched to accommodate the eight post-AGC symbols.

[0154] A Sidelink Positioning Reference Signal (SL-PRS) has been defined to support sidelink positioning procedures between UEs. Similar to the downlink PRS (DL-PRS), the SL-PRS resource consists of one or more resource elements (i.e., one OFDM symbol in the time domain and one subcarrier in the frequency domain). The SL-PRS resource has been designed to have a comb-based pattern to enable Fast Fourier Transform (FFT) based processing at the receiver. The SL-PRS resource consists of uninterleaved or only partially interleaved resource elements in the frequency domain to provide small time of arrival (TOA) uncertainty for each SL-PRS resource and reduced overhead. The SL-PRS may also be associated with a specific RP-P (e.g., certain SL-PRS may be allocated in certain RP-Ps). The SL-PRS has also been defined to have intra-slot repetition ( Fig. 9 ), to allow combining gain if needed. There may also be inter-UE coordination of RP-P to provide dynamic SL-PRS and data multiplexing while minimizing SL-PRS collisions.

[0155] Fig.10 Different resource pool (RP-P) assignment procedures for positioning according to various aspects of the present disclosure are illustrated. Specifically, diagram 1000 illustrates a reservation-based approach between two relay UEs to minimize the overhead / conflict caused by their associated target UEs using the same RP-P. Diagram 1050 illustrates a two-step assignment procedure with a serving base station. In the first stage, the base station may assign orthogonal RP-Ps. In the second stage, each relay UE decides which resources within the assigned RP-P should be assigned to the target UE.

[0156] There are two types of resource allocation for sidelink communications, referred to as "mode 1" and "mode 2". For mode 1 resource allocation, the base station allocates resources for sidelink communications between UEs. For mode 2 resource allocation, the involved UEs autonomously select sidelink resources. Congestion control mechanisms are applied in NR-V2X for mode 2 resource allocation and are similar to those in LTE-V2X. When mode 2 resource allocation is applied, the UE can use two types of measurements to detect and mitigate the effects of congestion: channel busy rate (CBR) and channel occupancy rate (CR). CBR is calculated in each subframe as the portion of busy resources in the resource pool in the last 100 milliseconds (ms). If the received energy level in a resource (e.g., a set of resource elements, one or more symbols, one or more time slots, etc.) is above a given threshold, the resource is considered busy. The CBR measurement reflects congestion on the medium. CR reflects the UE's occupation of resources. CR is the number of subchannels that the UE occupies and will occupy within a 1000ms time window.

[0157] With further reference to congestion control, the priority of packets is defined by higher layers and passed to the physical layer indicated in SCI-1. The CR and transmission parameters are adapted based on the relative priority of the UE's traffic and CBR. In order to react to rapid changes in resource congestion, NR-V2X defines shorter intervals for the calculation of CBR and CR. Currently, the intervals in NR-V2X are 1ms or 2ms compared to 4ms in LTE-V2X.

[0158] The NR sidelink supports CBR as a metric for congestion control. Sidelink received signal strength indication (RSSI) measurements are used for CBR estimation. Alternatively, RSRP measurements can be used. Congestion control can limit the following transmission parameters: (1) modulation and coding scheme (MCS) index and MCS table; (2) number of subchannels per transmission; (3) number of retransmissions; and (4) transmit power. For example, the more congestion on the medium, the lower the MCS, resulting in a lower data rate. Similarly, the more congestion, the lower the transmit power to reduce interference. The absolute speed of the UE can also limit the transmission parameters.

[0159] Fig.111100 is an illustration of an urban setting in which various UEs may be turned on or actively transmitting a sidelink SL-PRS, while various other UEs may be turned off or not actively transmitting a SL-PRS. For example, in a power save mode or other setting, certain UEs may not be transmitting a SL-PRS despite being configured for sidelink communications. As illustrated, a pedestrian UE (e.g., a vulnerable road user (VRU)) may be turned on and actively transmitting a SL-PRS, such that a nearby UE may measure the SL-PRS of the pedestrian UE. Various UE devices that are turned off or not actively transmitting a SL-PRS may be configured for sidelink communications and may be receiving signals from nearby UEs that are turned on or actively transmitting a SL-PRS. Thus, based on the UE's settings, the UE may be powered on and certain sidelink communications may not be activated (e.g., SL-PRS reception and / or transmission is disabled).

[0160] As mentioned, a vulnerable road user (VRU) may be an NR UE for vehicle-to-VRU communications or VRU-to-vehicle communications. For example, when a vehicle approaches, a hearing impaired person may receive vibrations from a wearable device (VRU) based on signals from the vehicle. Likewise, the wearable device may send its location to the vehicle, and such location may be used by its driving assistance functionality. In some cases, the UE may be configured to turn off, disable, or disconnect the transmit and / or receive functions for sidelink communications. For example, the determination of wakeup or "sleep" may be based on the UE's discontinuous reception (DRX) cycle. FIG. 12A to FIG. 12C These DRX cycles are described in more detail.

[0161] The UE may have settings for sleep, wake-up, activation, deactivation, or discontinuous operation of transmission (Tx) or reception (Rx) of a sidelink positioning reference signal (SL-PRS). Various aspects of the present disclosure contemplate local activation of these modes or settings based on location data, priority status of the network, demand from other UEs, and priority of the UE. Since these features and other features may reduce the reliability of the UE to provide SL-PRS and may waste sidelink resources within a resource pool, various processes are disclosed below that enable the reduced reliability or perforability of the UE's SL-PRS to be more predictable. That is, based on the information shared between devices, auxiliary data, and previous history of transmission, the UE may predict when another UE will deactivate one or more SL-PRS functions, where one or more SL-PRS functions will be deactivated, and whether one or more SL-PRS functions will be deactivated. For example, various settings or configurations of the UE and specifically Tx / Rx capabilities may provide an override of at least a portion of the UE's DRX mode. In short, a balance between power saving via DRX mode and location monitoring / transmission via SL-PRS can be achieved.

[0162] Even when there is no traffic sent from the network to the UE, the UE is expected to monitor every downlink subframe on the physical downlink control channel (PDCCH). This means that the UE must always be "on" or active even when there is no traffic, because the UE cannot know exactly when the network will send data to it. However, being active all the time is a considerable power drain on the UE.

[0163] To address this issue, the UE may implement discontinuous reception (DRX) and / or connected mode discontinuous reception (CDRX) techniques. DRX and CDRX are mechanisms by which the UE enters a "sleep" mode for scheduled time periods and "wakes up" for other time periods. During the wake-up or active period, the UE checks to see if there is any data from the network, and if not, returns to sleep mode.

[0164] In order to implement DRX and CDRX, the UE and the network need to be synchronized. In the worst scenario, the network may try to transmit some data to the UE while the UE is in sleep mode, and the UE may wake up when there is no data to be received. To prevent such scenarios, the UE and the network should have a well-defined agreement on when the UE can be in sleep mode and when the UE should be awake / active. This agreement has been standardized in various technical specifications. It is noted that DRX includes CDRX, and thus references to DRX refer to both DRX and CDRX, unless otherwise indicated.

[0165] The network (e.g., serving cell) may configure the UE with DRX / CDRX timing using an RRC Connection Reconfiguration message (for CDRX) or an RRC Connection Setup message (for DRX). The network may signal the following DRX configuration parameters to the UE: (1) DRX cycle: the duration of one 'on time' plus one 'off time'. This value is not explicitly specified in the RRC message; instead, it is calculated from the subframe / slot time and the "Long DRX Cycle Start Offset". (2) On Duration Timer: the duration of the 'on time' within one DRX cycle. (3) DRX Inactivity Timer: how long the UE should remain 'on' after receiving a PDCCH (e.g., the number of expected transmission instances). When this timer is on, the UE remains in the 'on state', which may extend the on period into a period that was originally an 'off' period. (4) DRX Retransmission Timer: the maximum number of consecutive PDCCH subframes / slots that the UE should remain active for waiting for incoming retransmissions after the first available retransmission time. (5) Short DRX cycle: A DRX cycle that can be implemented during the 'off' period of a long DRX cycle. (6) DRX short cycle timer: The number of consecutive subframes / slots that should be followed by a short DRX cycle after the DRX inactivity timer expires.

[0166] FIG. 12A to FIG. 12C Example DRX configurations according to aspects of the present disclosure are illustrated. Fig. 12A An example DRX configuration 1200A is illustrated in which a long DRX cycle (the time from the start of one On Duration to the start of the next On Duration) is configured and no PDCCH is received during the cycle. Fig. 12B An example DRX configuration 1200B is illustrated in which a long DRX cycle is configured and a PDCCH is received during the on duration 1210 of the illustrated second DRX cycle. Note that the on duration 1210 ends at time 1212. However, based on the length of the DRX inactivity timer and the time when the PDCCH is received, the time that the UE is awake / active ("active time") is extended to time 1214. Specifically, when a PDCCH is received, the UE starts the DRX inactivity timer and remains in the active state until the timer expires (the timer is reset each time a PDCCH is received during the active time).

[0167] Fig. 12CAn example DRX configuration 1200C is illustrated in which a long DRX cycle is configured and a PDCCH and a DRX command MAC control element (MAC-CE) are received during the on duration 1220 of the illustrated second DRX cycle. Note that since the PDCCH is received at time 1222 and the DRX inactivity timer subsequently expires at time 1224, the active time that started during the on duration 1220 will normally end at time 1224, as described above with reference to Fig. 12B However, in Fig. 12C In the example of , the active time is shortened to time 1226 based on the time of receiving the DRX command MAC CE instructing the UE to terminate the DRX inactivity timer and start the duration timer.

[0168] In more detail, the active time of the DRX cycle is the time during which the UE is considered to be monitoring the PDCCH. The active time may include the time during which the on duration timer is running, the DRX inactivity timer is running, the DRX retransmission timer is running, the MAC contention resolution timer is running, the scheduling request has been transmitted on the PUCCH and is pending, an uplink grant for a pending HARQ retransmission may occur and there is data in the corresponding HARQ buffer, or a newly transmitted PDCCH indicating a cell radio network temporary identifier (C-RNTI) addressed to the UE has not been received after successfully receiving a random access response (RAR) for a preamble not selected by the UE. And, in non-contention based random access, after receiving the RAR, the UE should be in an active state until a newly transmitted PDCCH indicating a C-RNTI addressed to the UE is received.

[0169] According to one aspect of the present disclosure, the DRX cycle may be configured based on other aspects of the UE's environment. That is, the duration of active time, the inactive period required for sleep mode or off state, and the transition from a long DRX cycle to a short DRX cycle may be configured as variables that depend on environmental variables and measurements. For example, a UE may have a location-based power saving feature (e.g., a DRX mode or state). Fig.13 As illustrated, the configuration defined for the DRX Active Time enables the behavior of the UE to be more predictable to its peers.

[0170] The configuration or setting for determining when the UE's SL-PRS signal may be turned on or off may be based on the device's location (e.g., indoors), the device's activity (e.g., motion, charging, etc.), the remaining available power (e.g., power save mode), the distance from other UEs, the operating mode (e.g., mode 1 or mode 2), or other settings. For example, a public safety UE may be active only when in an emergency location or outside a station perimeter. Fig.11 As illustrated, UEs not associated with a vulnerable situation (e.g., non-roadside pedestrians) have their SL-PRS signaling turned off. One or more regions or locations may be pre-configured into the UE or automatically configured such that the UE's SL-PRS transmission is switched to an off mode in that location or region. Although the UE's SL-PRS communication is off (e.g., Tx and Rx), the UE itself may be on and may communicate with a radio unit (RU) over an access link.

[0171] In order to save power or reduce interference, the UE can turn on / off the transmission and reception through the radio link with the radio unit. That is, the transmission (Tx) channel and the reception (Rx) channel can be able to be turned on / off respectively, so that the transmission channel to the radio unit is controlled independently of the reception channel. The DRX cycle or DRX mode can control the reception of downlink control channels (e.g., PDCCH) from the radio unit. Similarly, the UE can turn on / off the transmission and reception of sidelink signals (and specifically, positioning reference signals (PRS)). The previously mentioned DRX cycle or DRX mode can be adapted to control the reception (Rx) of sidelink signals. This capability or extension of the DRX mode may be referred to as SL-DRX. Using the SL-DRX functionality, the UE can turn on / off the above-mentioned DRX cycle or DRX mode. FIG. 12A to FIG. 12C One or more of the mentioned DRX functions are applied to a Physical Sidelink Control Channel (PSCCH) or to a Sidelink Positioning Reference Signal (SL-PRS).

[0172] For example, during the active time of SL-DRX or in the active state of SL-DRX, the UE may power on the antenna or receiver to receive (listen to) PSCCH and SL-PRS signals. During the inactive time of SL-DRX or in the inactive state of SL-DRX, the UE may power off or turn off the antenna or receiver so that it cannot receive PSCCH or SL-PRS. When the UE does turn off its sidelink receiver, the UE may be excluded from the resource pool or may be removed from the auxiliary data (AD) supporting sidelink management. Similarly, if the SL-DRX function is in connected mode, various sidelink functionalities may be maintained, while if the SL-DRX function is in idle mode, less sidelink functionalities may be maintained or no sidelink functionality may be maintained. Therefore, when the UE has SL-DRX capability, the network may not consider the UE to be an always-on resource or a reliable resource.

[0173] In the off state of DL-DRX, although the UE does not monitor PDCCH or other control channels, it can still receive positioning reference signals (PRS) from nearby UEs. Based on the received PRS, the UE can keep or maintain a list of nearby UEs. After turning on or reactivating the downlink of the UE, the UE may have accurate location information (e.g., from RTT) and may know the surrounding UEs for coordinating resource pools. Similarly, in the off state of SL-DRX, the active UE (i.e., DL is on) may know the nearby UEs and may receive or calculate positioning information based on RTT. This information about nearby UEs may be based on non-side link signals or network information from the RU. PRS-active UEs may keep a list of nearby UEs and may also record their PRS status (on / off). That is, DL-DRX and SL-DRX may have different DRX cycles and may be activated / deactivated separately. This stored information related to nearby UEs (which may be received from the radio unit as auxiliary data or from inter-UE coordination) may enable the UE to coordinate access to the resource pool more quickly when waking up. In Mode 1 or Mode 2, the UE may keep or maintain these local UE lists and may store additional information (such as configuration information) to assist in sidelink coordination.

[0174] Fig.13 Two peer UEs 1310 and 1320 are illustrated with active access links 1302 and 1304, respectively. UE 1310 may be turned off and may not be sending PRS signals to peer UE 1320. SL-PRS 1306 may be sent to UE 1310 even though UE 1320 has not received a signal from UE 1310 for a defined period of time. Another side link enhancement is support for inter-UE coordination. With inter-UE coordination, UE 1320 may assist UE 1310 in its resource selection. There are two types of inter-UE coordination (Type A and Type B). Regardless of whether SL-PRS of UE 1310 is turned on or off, UE 1320 may directly limit the use of certain resources by the assisted UE 1310 (Type A). UE 1320 may instruct UE 1310 to limit the use of certain resources or recommend which resources should be used (Type B). After receiving in Type B, UE 1310 may decide whether to use or follow the recommended, restricted, or X resource set transmitted by UE 1320. UE 1320 may also unilaterally restrict the use of its resources for one or more UEs including UE 1310, and notify these UEs of such restrictions. Sidelink resource information including DRX configuration information for these UEs may be received from access links 1302 and 1304 and from peer UEs (e.g., 1310 and 1320).

[0175] Fig.14Various sidelink connections between a first UE (labeled “UE 1”) and several other UEs (labeled “UE 2 to UE 7”) utilizing mode 1 resource allocation in accordance with various aspects of the present disclosure are illustrated. These connections may be allocated in a sidelink resource pool (RP) provided by a gNB or base station. In the arrangement 1400 as illustrated, UE 1 may participate in a positioning session to determine an estimate of its location, and UE 2, UE 3, UE 4, UE 5, UE 6, and UE 7 may be available to assist UE 1 or be within range of assisting the UE. The gNB or other network entity may provide assistance data (AD) to UE 1 indicating the SL-PRS configuration for UE 2 to UE 7 in the arrangement 1400. The AD configuration may include a SL-DRX configuration for each of UE 1 to UE 7. There will be some UEs that have enabled the location-based power saving feature. For example, UE 3 and UE 6 may be configured to be in a power saving mode for SL-PRS transmission (e.g., in a DRX off state) and therefore cannot be used for positioning. UEs in power saving mode for sidelink (UE 3 and UE 6) may maintain a connection to the gNB such that power saving or SL-DRX is applied to the sidelink Rx instead of the radio unit (DL) signal.

[0176] Used for Fig.14 The location server of the gNB (e.g., LMF 270) may not know the SL transmission state of each UE or the power optimization being adopted by each UE when providing assistance data for the positioning session. Therefore, in order to determine which UEs are transmitting SL-PRS, UE 1 may attempt to measure the SL-PRS from each of the other UEs 2 to UE 7. However, this may be inefficient and wasteful of UE 1's resources because not all UEs 2 to UE 7 may be transmitting SL-PRS.

[0177] Therefore, the present disclosure provides power saving techniques for sidelink operation. Power saving at the UE can be achieved by determining and reporting the SL-PRS state using inter-UE positioning coordination signaling. In a specific implementation, the LMF may provide auxiliary data including a list of UEs that can be used for positioning. The LMF may maintain and provide configuration information for the UE as well as the auxiliary data. At any given time, some of the UEs may not transmit due to their power saving functionality. Therefore, the LMF's list of UEs ready for assistance may not be the latest at any given time. The LMF's list may only indicate that the UE is configured to provide SL-PRS, without indicating that such UE is actively doing so or is currently able to do so (enabled).

[0178] In one implementation, a UE in Mode 1 resource allocation (e.g., UE 1) may maintain a transmission / detection status report for sidelink PRS from nearby UEs. Fig.14 UE 1) may have a procedure for periodically checking whether the configured SL-PRS / RP-P is detectable. The positioning session configuration received at UE 1 may assist UE 1 in determining parameters and procedures for periodically checking nearby UEs. LMF may assist UE 1 in determining parameters and procedures for periodically checking nearby UEs (e.g., those UEs configured with SL-PRS on the LMF's list). For example, the LMF may provide the UE with a positioning session configuration that defines one or more conditions that the UE's measurement of the SL-PRS must meet in order to confirm that the SL-PRS of another UE is turned off or inactive. The applicable wireless standard may define one or more conditions that the UE's measurement of the SL-PRS must meet in order to confirm that the SL-PRS of another UE is turned off or inactive. That is, the UE has (or may be provided with via the AD) one or more conditions for determining whether the SL-PRS of a nearby UE is turned off (e.g., in an inactive SL-DRX mode), even though the nearby UE is configured for SL-PRS or listed in the AD of the location server. In this way, UE 1 may determine that UE 3 and UE 6 are not available for SL-PRS assistance even though they are configured for SL-PRS or listed as such. The detecting UE may record a list of inactive or undetectable UEs and share the list with other UEs.

[0179] The conditions for determining that the SL-PRS resource is inactive may correspond to multiple measurement results, including reference signal received power (RSRP) (power level), signal to interference plus noise ratio (SINR) (interference level) and / or signal to noise ratio (SNR) (noise level). Determination of whether it is turned on / off or active / inactive may be determined by one or more thresholds corresponding to these or other measurement results and may be averaged over a time period. The AD may include pre-specified conditions that the measurement results should meet in order to determine or record whether the SL-PRS is turned off or inactive. The determination may be stored on the measuring UE to improve the efficiency of the UE. For example, UE 1 may stop attempting to measure the SL-PRS from UE 3 after determining that UE 3 is turned off via one or more of the above conditions. The detecting UE may send a list of these conditions and inactive UEs for the determination.

[0180] Still reference Fig.14, UE 1 requiring positioning assistance may determine that UE 3 and UE 6 are inactive after satisfying certain conditions as mentioned above. These conditions may be specified by the UE itself or by the LMF or gNB. In one specific implementation, UE 1 may inform the LMF which UEs in the AD have been measured and determined to be turned off. In addition, UE 3 or UE 6 may, for example, inform the LMF and / or peer UEs (e.g., UE 1, UE 7) that their device type or configuration may disable SL-PRS without warning. That is, UEs or low-end UEs that cannot reliably send SL-PRS (e.g., due to SL-DRX) may inform the LMF and / or its peers that they may deactivate SL-PRS at any time (e.g., puncturable / non-continuous). Such puncturability, reliability, and availability information may be determined by the LMF based on configuration information from the UE (including DRX capabilities, location-based power saving modes, and priority status). Therefore, the LMF may store two AD lists: a first reliable (and non-puncturable) UE list (set), which may be assumed to be turned on when configured for SL-PRS; and a second unreliable (puncturable / non-continuous) UE list (set), which may or may not be turned on (e.g., conditionally turned on). UEs receiving these AD lists may decide for themselves which UEs to contact for positioning assistance, or may be instructed to use only the first list (non-puncturable or available UEs).

[0181] UE 1 or LMF may adopt implicit rules (conditions) to determine which SL-PRS / RP-P may be assumed to be turned on and / or which SL-PRS / RP-P may be potentially turned off / potentially puncturable. The relevant wireless standard may define rules or conditions for determining which SL-PRS / RP-P may be assumed to be turned on and / or which SL-PRS / RP-P may be potentially turned off / potentially puncturable. For example, a low priority SL-PRS may be assumed to be potentially inactive. The UE and LMF may determine the UE positioning assistance reliability by the following: inference based on UE configuration data (e.g., the presence of DRX configuration), explicit information from the UE, or a determined state as recorded by a UE or other UE on the network that expects assistance, or a combination thereof. The assistance data (AD) from the LMF may include transmission deterministic data or reliability (puncturability / discontinuity) for each SL-PRS. The UE requiring assistance may use the deterministic data to set the signal gain and determine whether to allocate resources to detect the SL-PRS. This deterministic data may assist the UE in distinguishing a low signal from a UE and a low signal from an inactive UE (eg, where SL-DRX is inactive), and reduce the power consumed in searching for inactive devices.

[0182] Inter-UE coordination for positioning may include determining that one or more SL-PRS provided by the AD information is indeed turned off. If a UE (e.g., UE 7) receives information that some SL-PRS / RP-P may potentially be turned off / punctured / inactive, the positioning UE may apply the additional information together with the AD configuration to any measurement. If the UE determines through measurement that one or more conditions of the AD configuration are met, the UE may stop measuring the SL-PRS that has been determined to be not transmitted for a certain period of time. The UE may notify the LMF whether the measured SL-PRS resources are turned on or may potentially be turned off in the future. The UE may notify nearby UEs (e.g., within the RP) that it determines that these SL-PRS resources are considered to be turned off, as well as the thresholds, associated measurement results, specifications or other determining factors used for determination. That is, for example, different UEs may have different conditions for determining that SL-PRS / RP-P is turned off based on their respective hardware capabilities.

[0183] Continue to refer Fig.14 In mode 2 resource allocation, inter-UE coordination for positioning may be used to determine whether one or more SL-PRS are turned off or inactive. At any given time, some of these UEs (e.g., UE 3) may not be transmitting SL-PRS (e.g., due to power saving functionality or DRX cycle). One UE (master UE) may maintain a record of the active / inactive status of SL-PRS transmissions by nearby UEs through signal measurement or inter-UE coordination signaling. The UE in mode 2 may report the measured SL-PRS status of other UEs to nearby UEs, as well as a timestamp, a series of timestamps, measurement conditions, and / or other information that forms a status determination. These UEs may each have a threshold for determining the status of other UEs. For example, if a SL-PRS / RP-P resource has been determined to be turned off for more than X milliseconds or has been determined to be turned off for at least Y instances (where X and Y may be integers), the UE is not expected to include the SL-PRS resource in the inter-UE coordination signaling. In other words, the UE may have a confidence metric that should be satisfied to determine that a particular SL-PRS / RP-P resource has been turned off.

[0184] A UE may request the SL-PRS transmission status of nearby UEs via inter-UE coordination signaling. Similarly, broadcast, multicast, or unicast signaling may be used to notify nearby UEs of the status of the SL-PRS. An anchor UE that manages a resource pool may perform a positioning resource reallocation procedure after obtaining the transmission status of SL UEs in the area (i.e., within the RP-P or on the AD list). The anchor UE may perform detection and determination of the transmission / activity status (e.g., on / off) itself prior to the positioning resource reallocation procedure. The anchor UE may perform any of the notification features performed by the previously described LMF (e.g., AD broadcast).

[0185] A UE (e.g., UE 3) may be configured to enable or activate SL PRS resource transmission based on location. That is, the DRX mode may be location-based DRX (such as the location-based DRX illustrated in FIG. 12), in which some UEs are in a DRX inactive state based on their location (e.g., within a building). Similarly, the DRX mode may be a motion-based or motion-activated power saving function (e.g., a wearable device that sleeps in a DRX inactive state before moving). The location may be associated with proximity to other UEs (e.g., in the workplace). For example, even if the UE is configured for DRX, the transmission condition of the UE may be predictable by the LMF. That is, the LMF may be adapted to predict when the UE will enter the DRX off state based on location criteria, and the UE may be included in its AD list as long as the location criteria are not met. If the UE is in a specific area or has not moved from the initial area where the SL-PRS is provided, the UE is expected to send the SL-PRS independently of the SL-DRX configuration. If the LMF or anchor UE detects that a device configured with SL-DRX is moving towards a deactivation zone (where DRX will be inactive), the LMF may remove the UE from the AD list.

[0186] The UE may be allowed (or decided) to send SL-PRS in the DRX off state based on the determination of the UE. For example, if the SL-PRS resource is associated with a high priority state, the state may override the DRX off state, and the SL-PRS may be sent despite the UE being in the DRX off state. The UE may report that even if it is configured for DRX, if the UE has a high priority state or is in a high priority RP, the UE may notify other UEs or LMFs that its DRX cycle will be overwritten. When in high priority, the SL-PRS for the UE may be sent even during the DRX off period. The UE may include an override configuration that allows positioning resource transmission during a location-based DRX off period. As a result, the UE may be used as a positioning reference during the DRX period.

[0187] The UE may request on-demand SL-PRS resources or high priority status based on its configuration in mode 1 or mode 2, so that the requesting UE is only supplied with SL-PRS resources that are expected to be turned on / not punctured. That is, the UE may request that the AD list only include reliable UEs for positioning assistance. The base station / radio unit (in mode 1) or the anchor UE (in mode 2) may interpret the request for high-priority positioning as a request for on-demand SL-PRS resources that are not punctured or intermittently turned off. The request may include the minimum time period or time window information during which the SL-PRS resources are expected to be turned on. The request is received by the LMF and / or other SLUEs. One or more of the UEs receiving the request may switch to a transmit-only mode to provide on-demand SL-PRS resources to the requesting UE.

[0188] UEs designated to transmit such SL-PRS to requesting peer UEs are expected to drop other conflicting Tx channels and other conflicting Rx channels. For example, a SL UE may not switch to Rx mode as it normally would, but instead maintain dedicated or on-demand SL-PRS transmission resources for a defined period of time. The override of the Rx mode of the SL transceiver ensures that the on-demand UE transmits the SL-PRS and that the SL-PRS is not queued or delayed by other transmissions. For longer periods of requested on-demand SL-PRS resources, the LMF or anchor UE may rotate or periodically deliver the on-demand tasks. For example, emergency responder UEs may request high priority or on-demand resources as long as they are on site or responding.

[0189] Fig.15 An example method 1500 of wireless communication according to various aspects of the present disclosure is illustrated. In one aspect, the method 1500 may be performed by a UE (e.g., any of the UEs described herein). At 1502, the UE may receive a configuration of a first sidelink positioning reference signal (SL-PRS) resource set configured for transmission by a first set of sidelink UEs including the UE. In one aspect, operation 1502 may be performed by one or more transceivers 310 to 320, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as means for performing the operation.

[0190] At 1504, the UE may determine a sidelink transmission state of a first SL-PRS resource subset of the first SL-PRS resource set based on a signal strength measurement result of the first SL-PRS resource set, availability information of the first SL-PRS resource set, or both. In one aspect, operation 1504 may be performed by one or more transceivers 310 to 320, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as a means for performing the operation.

[0191] As will be appreciated, a technical advantage of method 1500 is saving power.

[0192] The determination of method 1500 may include: determining that the sidelink transmission state of the first SL-PRS resource subset is inactive based on the signal strength measurement result of the first SL-PRS resource subset being lower than a threshold, and determining that the sidelink transmission state of the second SL-PRS resource subset is active based on the signal strength measurement value of the second SL-PRS resource subset being higher than a threshold. The signal strength measurement result may include a power level, a noise level, or an interference level, or any combination thereof. The threshold may be received from a location server or a base station. Method 1500 may report the sidelink transmission state of the first SL-PRS resource subset to at least one additional UE that shares the first SL-PRS resource set. The availability information of the first SL-PRS resource set indicates available SL-PRS resources and conditionally available SL-PRS resources. The available SL-PRS resources are configured to be transmitted, and the conditionally available SL-PRS resources are non-contiguous, puncturable, or conditionally active.

[0193] The configuration may receive at least a portion of the availability information of the first SL-PRS resource set. Some availability information is advanced (e.g., the device has DRX mode capability) and may be included in an AD or configuration from a network node. Other availability information may originate from other UEs, such as "whether DRX mode is enabled" or "which location triggers the device to switch to DRX off mode". The availability information of the first SL-PRS resource set may be received from a first UE or a network node in the first side link UE set. The availability information of the first SL-PRS resource set indicates a discontinuous reception (DRX) mode or a power saving mode of a second UE in the first side link UE set. The availability information of the first SL-PRS resource set may include configuration information related to location-based triggering for the DRX mode or the power saving mode. The availability information of the first SL-PRS resource set may be received from a location server or a network node, and may include criteria for determining a time period during which the SL-PRS is configured to be sent by at least one other UE in the first side link UE set, the criteria including the DRX mode configuration of at least one other UE.

[0194] The determination of method 1500 may include determining the sidelink transmission state of the first SL-PRS resource subset as active or inactive after a defined time period based on the signal strength measurement result detected at the UE. The sidelink transmission state of the first SL-PRS resource subset is recorded with a timestamp. The determination of method 1500 may include determining the sidelink transmission state of the first SL-PRS resource subset based on the presence or absence of the associated SL-PRS within a defined time period or for a given number of expected transmission instances. Method 1500 may include sending the first sidelink transmission state of the UE as active or inactive to the first sidelink UE set via inter-UE coordination. Method 1500 may include allocating a resource pool of the first SL-PRS resource set based on the sidelink transmission state of the first SL-PRS resource subset by the UE. Method 1500 may include receiving configuration information associated with another UE in the first sidelink UE set at the UE, predicting the SL-PRS availability of the other UE at the UE based on the configuration information, and sending auxiliary data (AD), the AD being based on the predicted SL-PRS availability. Predicting the SL-PRS availability of another UE may be based on the configuration information and the location of the other UE.

[0195] Another UE in the first set of sidelink UEs may be configured with a discontinuous reception (DRX) mode, and the UE predicts that the DRX mode is disabled for the other UE at a location based on a previous SL-PRS transmission from the other UE at the location. Receiving configuration information may be associated with the other UE in the first set of sidelink UEs, and reserving SL-PRS resources of the resource pool for the other UE may be based on the configuration information and priority status of the other UE. The other UE may be in an inactive time of the DRX mode.

[0196] Fig.16 An example method 1600 of wireless communication according to various aspects of the present disclosure is illustrated. In one aspect, the method 1600 may be performed by a UE (e.g., any of the UEs described herein). At 1602, the UE may receive configuration information associated with a location-based discontinuous reception (DRX) mode. In one aspect, operation 1602 may be performed by one or more transceivers 310 to 320, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as components for performing the operation. At 1604, the UE may obtain the location of the UE. In one aspect, operation 1604 may be performed by one or more transceivers 310 to 320, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as components for performing the operation.

[0197] At 1606, the UE may send a sidelink positioning reference signal (SL-PRS) based on location while in an inactive state of a location-based discontinuous reception (DRX) mode. The DRX mode may involve a downlink signal or a PDCCH signal. In one aspect, operation 1606 may be performed by one or more transceivers 310 to 320, one or more processors 332, memory 340, and / or a positioning component 342, any or all of which may be considered as a means for performing the operation.

[0198] As will be appreciated, technical advantages of method 1600 are saving power and increasing location awareness.

[0199] The location of the UE is based on satellite signals, cellular signals, Wi-Fi signals, sensor information, or any combination thereof. The transmission of the SL-PRS at 1606 may be associated with a priority state or an on-demand request, and the SL-PRS monitoring capability is non-continuous in DRX mode.

[0200] Fig.17 An example method 1700 of wireless communication in accordance with aspects of the present disclosure is illustrated. In one aspect, the method 1700 may be performed by a UE (eg, any of the UEs described herein).

[0201] At 1702, the UE may receive a request to transmit an on-demand sidelink positioning reference signal (SL-PRS) during a time period during which the UE is requested to transmit an on-demand SL-PRS. In one aspect, operation 1702 may be performed by one or more transceivers 310 to 320, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as a means for performing the operation.

[0202] At 1704, the UE may refrain from transmitting, receiving, or both on a transmit channel, a receive channel, or both that conflicts with the requested on-demand SL-PRS. In one aspect, operation 1704 may be performed by one or more transceivers 310-320, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered a means for performing the operation.

[0203] At 1706, the UE may send the requested on-demand SL-PRS. The on-demand SL-PRS request may override the DRX mode or power saving mode for a time period based on the request. The request is received from a location server, a network node, or a second UE. In one aspect, operation 1706 may be performed by one or more transceivers 310 to 320, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as means for performing the operation.

[0204] As will be appreciated, technical advantages of method 1700 are saving power and increasing location awareness.

[0205] In the above detailed description, it can be seen that different features are grouped together in each example. This disclosure should not be understood as an intention that the example clauses have more features than the features explicitly mentioned in each clause. On the contrary, various aspects of the present disclosure may include less than all the features of the disclosed individual example clauses. Therefore, the following clauses should be considered to be incorporated into the description accordingly, wherein each clause itself can be used as a separate example. Although each dependent clause may refer to a specific combination of one clause with other clauses in a clause, the aspects of the dependent clause are not limited to a specific combination. It should be understood that other example clauses may also include a combination of the subject matter of the dependent clause aspect with any other dependent clause or independent clause or any feature with other dependent clauses and independent clauses. The various aspects disclosed herein explicitly include these combinations, unless it is clearly expressed or can be easily inferred that a specific combination is not intended to be used (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). In addition, it is also expected that various aspects of the clause may be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

[0206] Specific implementation examples are described in the following numbered clauses:

[0207] Clause 1. A method for wireless communication performed by a user equipment (UE), the method comprising: receiving a configuration of a first sidelink positioning reference signal (SL-PRS) resource set configured for transmission by a first sidelink UE set including the UE; and determining a sidelink transmission status of a first SL-PRS resource subset of the first SL-PRS resource set based on a signal strength measurement result of the first SL-PRS resource set, availability information of the first SL-PRS resource set, or both.

[0208] Clause 2. A method according to Clause 1, wherein the determination further comprises: determining that the sidelink transmission state of the first SL-PRS resource subset is inactive based on the signal strength measurement result of the first SL-PRS resource subset being lower than a threshold, and determining that the sidelink transmission state of the second SL-PRS resource subset is active based on the signal strength measurement value of the second SL-PRS resource subset being higher than the threshold, wherein the signal strength measurement result includes a power level, a noise level, or an interference level, or any combination thereof.

[0209] Clause 3. The method of clause 2, wherein the threshold is received from a location server or a base station.

[0210] Clause 4. The method according to any one of clauses 1 to 3, further comprising: reporting the sidelink transmission status of the first SL-PRS resource subset to at least one additional UE sharing the first SL-PRS resource set.

[0211] Clause 5. A method according to any one of clauses 1 to 4, wherein the availability information of the first SL-PRS resource set indicates available SL-PRS resources and conditionally available SL-PRS resources, wherein the available SL-PRS resources are configured to be sent, and wherein the conditionally available SL-PRS resources are non-contiguous, perforated or conditionally active.

[0212] Clause 6. A method according to any one of clauses 1 to 5, wherein at least a portion of the availability information of the first SL-PRS resource set is received in the configuration.

[0213] Clause 7. A method according to any one of clauses 1 to 6, wherein the availability information of the first SL-PRS resource set is received from a first UE or a network node in the first side link UE set, and wherein the availability information of the first SL-PRS resource set indicates a discontinuous reception (DRX) mode or a power saving mode of a second UE in the first side link UE set.

[0214] Clause 8. The method of clause 7, wherein the availability information of the first SL-PRS resource set includes configuration information related to location-based triggering for the DRX mode or the power saving mode.

[0215] Clause 9. A method according to any one of clauses 1 to 8, wherein the availability information of the first SL-PRS resource set is received from a location server or a network node, and includes criteria for determining a time period during which the SL-PRS is configured to be transmitted by at least one other UE in the first side link UE set, the criteria including the DRX mode configuration of the at least one other UE.

[0216] Clause 10. A method according to any one of clauses 1 to 9, wherein the determination further comprises: determining the sidelink transmission state of the first SL-PRS resource subset as active or inactive after a defined time period based on the signal strength measurement result detected at the UE.

[0217] Clause 11. A method as described in any of clauses 1 to 10, wherein the sidelink transmission status of the first SL-PRS resource subset is recorded together with a timestamp.

[0218] Clause 12. A method according to any one of clauses 1 to 11, wherein the determination further comprises: determining the sidelink transmission state of the first SL-PRS resource subset based on the presence or absence of associated SL-PRS within a defined time period or for a given number of expected transmission instances.

[0219] Clause 13. A method as described in any of clauses 1 to 12, the method further comprising: sending a first sidelink transmission status of the UE as active or inactive to the first sidelink UE set via inter-UE coordination.

[0220] Clause 14. A method according to any one of clauses 1 to 13, the method further comprising: allocating, by the UE, a resource pool of the first SL-PRS resource set based on the sidelink transmission state of the first SL-PRS resource subset.

[0221] Clause 15. A method according to any one of clauses 1 to 14, the method further comprising: receiving, at the UE, configuration information associated with another UE within the first side link UE set; predicting, at the UE, the SL-PRS availability of the other UE based on the configuration information; and sending auxiliary data (AD), the AD being based on the predicted SL-PRS availability.

[0222] Clause 16. The method of clause 15, wherein predicting the SL-PRS availability for the other UE is based on the configuration information and a location of the other UE.

[0223] Clause 17. A method according to any one of clauses 1 to 16, wherein another UE in the first side link UE set may be configured with a discontinuous reception (DRX) mode, and wherein the UE predicts that the DRX mode is disabled for the other UE at a location based on a previous SL-PRS transmission from the other UE at the location.

[0224] Clause 18. A method according to any one of clauses 1 to 17, the method further comprising: receiving configuration information associated with another UE in the first side link UE set; and reserving SL-PRS resources of a resource pool for the other UE based on the configuration information and priority status of the other UE, wherein the other UE is in an inactive time in DRX mode.

[0225] Clause 19. A wireless communication method performed by a user equipment (UE), the method comprising: receiving configuration information associated with a location-based discontinuous reception (DRX) mode; obtaining the location of the UE; and when in an inactive state of the location-based DRX mode, sending a sidelink positioning reference signal (SL-PRS) based on the location.

[0226] Clause 20. The method of clause 19, wherein the location of the UE is based on satellite signals, cellular signals, Wi-Fi signals, sensor information, or any combination thereof.

[0227] Clause 21. A method as described in any of clauses 19 to 20, wherein sending the SL-PRS is associated with a priority status or an on-demand request, and wherein the SL-PRS monitoring capability is non-continuous in DRX mode.

[0228] Clause 22. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a request to send an on-demand sidelink positioning reference signal (SL-PRS) during a time period during which the UE is requested to send the SL-PRS; refraining from transmitting, receiving, or both on a transmit channel, a receive channel, or both that conflicts with the requested on-demand SL-PRS; and sending the requested on-demand SL-PRS.

[0229] Clause 23. The method of clause 22, wherein the request is received from a location server, a network node, or a second UE.

[0230] Clause 24. The method of any of clauses 22 to 23, further comprising overriding a DRX off cycle within the time period based on the request.

[0231] Clause 25. A user equipment (UE), comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, a configuration of a first sidelink positioning reference signal (SL-PRS) resource set configured for transmission by a first sidelink UE set; and determine a sidelink transmission state of a first SL-PRS resource subset of the first SL-PRS resource set based on a signal strength measurement result of the first SL-PRS resource set, availability information of the first SL-PRS resource set, or both.

[0232] Clause 26. A UE according to clause 25, wherein the at least one processor is configured to determine, including the at least one processor being configured to: determine that the sidelink transmission state of the first SL-PRS resource subset is inactive based on the signal strength measurement result of the first SL-PRS resource subset being lower than a threshold, and determine that the sidelink transmission state of the second SL-PRS resource subset is active based on the signal strength measurement value of the second SL-PRS resource subset being higher than the threshold, wherein the signal strength measurement result includes a power level, a noise level, or an interference level, or any combination thereof.

[0233] Clause 27. The UE of clause 26, wherein the threshold is received from a location server.

[0234] Clause 28. A UE according to any one of clauses 25 to 27, wherein the at least one processor is further configured to: report the sidelink transmission status of the first SL-PRS resource subset to at least one additional UE sharing the first SL-PRS resource set via the at least one transceiver.

[0235] Clause 29. A UE according to any one of clauses 25 to 28, wherein the availability information of the first SL-PRS resource set indicates available SL-PRS resources and conditionally available SL-PRS resources, wherein the available SL-PRS resources are configured to be sent, and wherein the conditionally available SL-PRS resources are non-contiguous, perforated or conditionally active.

[0236] Clause 30. A UE as described in any of clauses 25 to 29, wherein at least a portion of the availability information of the first set of SL-PRS resources is received in the configuration.

[0237] Clause 31. A UE according to any one of clauses 25 to 30, wherein the availability information of the first SL-PRS resource set is received from a first UE or a network node in the first side link UE set, wherein the availability information of the first SL-PRS resource set indicates a discontinuous reception (DRX) mode or a power saving mode of a second UE in the first side link UE set.

[0238] Clause 32. A UE according to clause 31, wherein the availability information of the first SL-PRS resource set includes configuration information related to location-based triggering for the DRX mode or the power saving mode.

[0239] Clause 33. A UE according to any one of clauses 25 to 32, wherein the availability information of the first SL-PRS resource set is received from a location server or a network node and includes criteria for determining a time period during which the SL-PRS is configured to be sent by at least one other UE in the first side link UE set, the criteria including the DRX mode configuration of the at least one other UE.

[0240] Clause 34. A UE according to any one of clauses 25 to 33, wherein the at least one processor is configured to determine, including the at least one processor being configured to: determine the sidelink transmission state of the first SL-PRS resource subset as active or inactive after a defined time period based on the signal strength measurement result detected at the UE.

[0241] Clause 35. A UE as described in any of clauses 25 to 34, wherein the sidelink transmission status of the first SL-PRS resource subset is recorded together with a timestamp.

[0242] Clause 36. A UE according to any one of clauses 25 to 35, wherein the at least one processor is configured to determine, including the at least one processor being configured to: determine the sidelink transmission state of the first SL-PRS resource subset based on the presence or absence of associated SL-PRS within a defined time period or for a given number of expected transmission instances.

[0243] Clause 37. A UE as described in any of clauses 25 to 36, the UE further comprising: sending a first sidelink transmission status of the UE as active or inactive to the first set of sidelink UEs via inter-UE coordination.

[0244] Clause 38. A UE according to any one of clauses 25 to 37, wherein the at least one processor is further configured to: allocate a resource pool of the first SL-PRS resource set based on the sidelink transmission state of the first SL-PRS resource subset.

[0245] Clause 39. A UE according to any one of clauses 25 to 38, wherein the at least one processor is further configured to: receive configuration information associated with another UE within the first side link UE set at the UE via the at least one transceiver; predict the SL-PRS availability of the other UE based on the configuration information at the UE; and send auxiliary data (AD) via the at least one transceiver, the AD being based on the predicted SL-PRS availability.

[0246] Clause 40. The UE of clause 39, wherein the UE predicts the SL-PRS availability for the other UE based on the configuration information and a location of the other UE.

[0247] Clause 41. A UE according to any one of clauses 25 to 40, wherein another UE in the first side link UE set may be configured with a discontinuous reception (DRX) mode, and wherein the UE predicts that the DRX mode is disabled for the other UE at a location based on a previous SL-PRS transmission from the other UE at the location.

[0248] Clause 42. A UE according to any one of clauses 25 to 41, wherein the at least one processor is further configured to: receive configuration information associated with another UE in the first side link UE set via the at least one transceiver; and reserve SL-PRS resources of a resource pool for the other UE based on the configuration information and priority status of the other UE, wherein the other UE is in an inactive time in DRX mode.

[0249] Clause 43. A user equipment (UE), the user equipment (UE) comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive configuration information associated with a location-based discontinuous reception (DRX) mode via the at least one transceiver; obtain the location of the UE; and when in an inactive state of the location-based DRX mode, send a sidelink positioning reference signal (SL-PRS) based on the location via the at least one transceiver.

[0250] Clause 44. The UE of clause 43, wherein the location of the UE is based on satellite signals, cellular signals, Wi-Fi signals, sensor information, or any combination thereof.

[0251] Clause 45. A UE as set forth in any of clauses 43 to 44, wherein the UE sending the SL-PRS is associated with a priority status or an on-demand request, and wherein the SL-PRS monitoring capability is non-continuous in DRX mode.

[0252] Clause 46. A user equipment (UE), the user equipment (UE) comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, a request to send an on-demand sidelink positioning reference signal (SL-PRS) during a time period during which the UE is requested to send the SL-PRS; refrain from transmitting, receiving, or both on a transmit channel, a receive channel, or both that conflict with the requested on-demand SL-PRS; and send the requested SL-PRS via the at least one transceiver.

[0253] Clause 47. The UE of clause 46, wherein the request is received from a location server, a network node, or a second UE.

[0254] Clause 48. A UE as set forth in any of clauses 46 to 47, wherein the at least one processor is further configured to: override a DRX off cycle within the time period based on the request.

[0255] Clause 49. A user equipment (UE), comprising: a component for receiving a configuration of a first sidelink positioning reference signal (SL-PRS) resource set configured for transmission by a first sidelink UE set including the UE; and a component for determining a sidelink transmission status of a first SL-PRS resource subset of the first SL-PRS resource set based on a signal strength measurement result of the first SL-PRS resource set, availability information of the first SL-PRS resource set, or both.

[0256] Clause 50. A UE according to clause 49, wherein the determination further comprises: a component for determining that the sidelink transmission state of the first SL-PRS resource subset is inactive based on that the signal strength measurement result of the first SL-PRS resource subset is lower than a threshold, and a component for determining that the sidelink transmission state of the second SL-PRS resource subset is active based on that the signal strength measurement value of the second subset is higher than the threshold, wherein the signal strength measurement result comprises a power level, a noise level, or an interference level, or any combination thereof.

[0257] Clause 51. The UE of clause 50, wherein the threshold is received from a location server or a base station.

[0258] Clause 52. A UE according to any one of clauses 49 to 51, the UE further comprising: means for reporting the sidelink transmission status of the first SL-PRS resource subset to at least one additional UE sharing the first SL-PRS resource set.

[0259] Clause 53. A UE according to any one of clauses 49 to 52, wherein the availability information of the first SL-PRS resource set indicates available SL-PRS resources and conditionally available SL-PRS resources, wherein the available SL-PRS resources are configured to be sent, and wherein the conditionally available SL-PRS resources are non-contiguous, perforated or conditionally active.

[0260] Clause 54. A UE as described in any of clauses 49 to 53, wherein at least a portion of the availability information of the first set of SL-PRS resources is received in the configuration.

[0261] Clause 55. A UE according to any one of clauses 49 to 54, wherein the availability information of the first SL-PRS resource set is received from a first UE or a network node in the first side link UE set, and wherein the availability information of the first SL-PRS resource set indicates a discontinuous reception (DRX) mode or a power saving mode of a second UE in the first side link UE set.

[0262] Clause 56. A UE as described in clause 55, wherein the availability information of the first set of SL-PRS resources includes configuration information related to location-based triggering for the DRX mode or the power saving mode.

[0263] Clause 57. A UE according to any one of clauses 49 to 56, wherein the availability information of the first SL-PRS resource set is received from a location server or a network node and includes criteria for determining a time period during which the SL-PRS is configured to be sent by at least one other UE in the first side link UE set, the criteria including the DRX mode configuration of the at least one other UE.

[0264] Clause 58. A UE according to any one of clauses 49 to 57, wherein the determination further comprises: a component for determining the sidelink transmission state of the first SL-PRS resource subset as active or inactive after a defined time period based on the signal strength measurement result detected at the UE.

[0265] Clause 59. A UE as described in any of clauses 49 to 58, wherein the sidelink transmission status of the first SL-PRS resource subset is recorded together with a timestamp.

[0266] Clause 60. A UE according to any one of clauses 49 to 59, wherein the determination further comprises: a component for determining the sidelink transmission state of the first SL-PRS resource subset based on the presence or absence of associated SL-PRS within a defined time period or for a given number of expected transmission instances.

[0267] Clause 61. A UE as described in any of clauses 49 to 60, the UE further comprising: means for sending a first sidelink transmission status of the UE as active or inactive to the first set of sidelink UEs via inter-UE coordination.

[0268] Clause 62. A UE according to any one of clauses 49 to 61, the UE further comprising: means for allocating a resource pool of the first set of SL-PRS resources based on the sidelink transmission state of the first subset of SL-PRS resources.

[0269] Clause 63. A UE according to any one of clauses 49 to 62, wherein the UE further comprises: a component for receiving, at the UE, configuration information associated with another UE within the first side link UE set; a component for predicting, at the UE, the SL-PRS availability of the other UE based on the configuration information; and a component for sending auxiliary data (AD), the AD being based on the predicted SL-PRS availability.

[0270] Clause 64. The UE of clause 63, wherein predicting the SL-PRS availability for the other UE is based on the configuration information and a location of the other UE.

[0271] Clause 65. A UE according to any one of clauses 49 to 64, wherein another UE in the first side link UE set may be configured with a discontinuous reception (DRX) mode, and wherein the UE predicts that the DRX mode is disabled for the other UE at a location based on a previous SL-PRS transmission from the other UE at the location.

[0272] Clause 66. A UE according to any one of clauses 49 to 65, wherein the UE further includes: receiving configuration information associated with another UE in the first side link UE set; and reserving SL-PRS resources of a resource pool for the other UE based on the configuration information and priority status of the other UE, wherein the other UE is in an inactive time in DRX mode.

[0273] Clause 67. A UE comprising: a component for receiving configuration information associated with a location-based discontinuous reception (DRX) mode; a component for obtaining the location of the UE; and a component for sending a sidelink positioning reference signal (SL-PRS) based on the location when in an inactive state of the location-based DRX mode.

[0274] Clause 68. The UE of clause 67, wherein the location of the UE is based on satellite signals, cellular signals, Wi-Fi signals, sensor information, or any combination thereof.

[0275] Clause 69. A UE as set forth in any of clauses 67 to 68, wherein sending the SL-PRS is associated with a priority status or an on-demand request, and wherein the SL-PRS monitoring capability is non-continuous in DRX mode.

[0276] Clause 70. A UE comprising: a component for receiving a request to send an on-demand sidelink positioning reference signal (SL-PRS) during a time period during which the UE is requested to send the SL-PRS; a component for preventing transmission, reception, or both on a transmission channel, a reception channel, or both that conflicts with the requested on-demand SL-PRS; and a component for sending the requested on-demand SL-PRS.

[0277] Clause 71. The UE of clause 70, wherein the request is received from a location server, a network node, or a second UE.

[0278] Clause 72. A UE as set forth in any of clauses 70 to 71, the UE further comprising means for overriding a DRX off cycle within the time period based on the request.

[0279] Clause 73. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by a user equipment (UE), cause the UE to: receive a configuration of a first sidelink positioning reference signal (SL-PRS) resource set configured for transmission by a first sidelink UE set including the UE; and determine a sidelink transmission state of a first SL-PRS resource subset of the first SL-PRS resource set based on a signal strength measurement result of the first SL-PRS resource set, availability information of the first SL-PRS resource set, or both.

[0280] Clause 74. A non-transitory computer-readable medium according to clause 73, wherein the determination further comprises: determining that the sidelink transmission state of the first SL-PRS resource subset is inactive based on the signal strength measurement result of the first SL-PRS resource subset being lower than a threshold, and determining that the sidelink transmission state of the second SL-PRS resource subset is active based on the signal strength measurement value of the second SL-PRS resource subset being higher than the threshold, wherein the signal strength measurement result comprises a power level, a noise level, or an interference level, or any combination thereof.

[0281] Clause 75. The non-transitory computer-readable medium of Clause 74, wherein the threshold is received from a location server or a base station.

[0282] Clause 76. A non-transitory computer-readable medium according to any one of clauses 73 to 75, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the UE, cause the UE to: report the sidelink transmission status of the first SL-PRS resource subset to at least one additional UE that shares the first SL-PRS resource set.

[0283] Clause 77. A non-transitory computer-readable medium according to any one of clauses 73 to 76, wherein the availability information of the first SL-PRS resource set indicates available SL-PRS resources and conditionally available SL-PRS resources, wherein the available SL-PRS resources are configured to be transmitted, and wherein the conditionally available SL-PRS resources are non-contiguous, perforated or conditionally active.

[0284] Clause 78. The non-transitory computer-readable medium of any one of clauses 73 to 77, wherein at least a portion of the availability information for the first set of SL-PRS resources is received in the configuration.

[0285] Clause 79. A non-transitory computer-readable medium according to any one of clauses 73 to 78, wherein the availability information of the first SL-PRS resource set is received from a first UE or a network node in the first side link UE set, and wherein the availability information of the first SL-PRS resource set indicates a discontinuous reception (DRX) mode or a power saving mode of a second UE in the first side link UE set.

[0286] Clause 80. The non-transitory computer-readable medium of Clause 79, wherein the availability information for the first set of SL-PRS resources comprises configuration information related to location-based triggering for the DRX mode or the power saving mode.

[0287] Clause 81. A non-transitory computer-readable medium according to any one of clauses 73 to 80, wherein the availability information of the first SL-PRS resource set is received from a location server or a network node and includes criteria for determining a time period during which the SL-PRS is configured to be transmitted by at least one other UE in the first side link UE set, the criteria including a DRX mode configuration of the at least one other UE.

[0288] Clause 82. A non-transitory computer-readable medium according to any one of clauses 73 to 81, wherein the determination further comprises: determining the sidelink transmission state of the first SL-PRS resource subset as active or inactive after a defined time period based on the signal strength measurement result detected at the UE.

[0289] Clause 83. The non-transitory computer-readable medium of any one of clauses 73 to 82, wherein the sidelink transmission state of the first subset of SL-PRS resources is recorded with a timestamp.

[0290] Clause 84. A non-transitory computer-readable medium according to any one of clauses 73 to 83, wherein the determination further comprises: determining the sidelink transmission state of the first SL-PRS resource subset based on the presence or absence of associated SL-PRS within a defined time period or for a given number of expected transmission instances.

[0291] Clause 85. A non-transitory computer-readable medium according to any one of clauses 73 to 84, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the UE, cause the UE to: send a first side link transmission status of the UE as active or inactive to the first side link UE set via inter-UE coordination.

[0292] Clause 86. A non-transitory computer-readable medium according to any one of clauses 73 to 85, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the UE, cause the UE to: allocate a resource pool of the first SL-PRS resource set based on the sidelink transmission status of the first SL-PRS resource subset.

[0293] Clause 87. A non-transitory computer-readable medium according to any one of clauses 73 to 86, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the UE, cause the UE to: receive configuration information associated with another UE within the first side link UE set at the UE; predict the SL-PRS availability of the other UE based on the configuration information at the UE; and send auxiliary data (AD), wherein the AD is based on the predicted SL-PRS availability.

[0294] Clause 88. The non-transitory computer-readable medium of clause 87, wherein predicting the SL-PRS availability for the other UE is based on the configuration information and a location of the other UE.

[0295] Clause 89. A non-transitory computer-readable medium according to any one of clauses 73 to 88, wherein another UE in the first side link UE set is configured with a discontinuous reception (DRX) mode, and wherein the UE predicts that the DRX mode is disabled for the other UE at a location based on a previous SL-PRS transmission from the other UE at the location.

[0296] Clause 90. A non-transitory computer-readable medium according to any one of clauses 73 to 89, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the UE, cause the UE to: receive configuration information associated with another UE in the first side link UE set; and reserve SL-PRS resources of a resource pool for the other UE based on the configuration information and priority status of the other UE, wherein the other UE is in an inactive time in DRX mode.

[0297] Clause 91. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by a UE, cause the UE to: receive configuration information associated with a location-based discontinuous reception (DRX) mode; obtain the location of the UE; and, when in an inactive state of the location-based DRX mode, send a sidelink positioning reference signal (SL-PRS) based on the location.

[0298] Clause 92. The non-transitory computer-readable medium of Clause 91, wherein the location of the UE is based on satellite signals, cellular signals, Wi-Fi signals, sensor information, or any combination thereof.

[0299] Clause 93. The non-transitory computer-readable medium of any one of clauses 91 to 92, wherein sending the SL-PRS is associated with a priority status or an on-demand request, and wherein the SL-PRS monitoring capability is non-continuous in a DRX mode.

[0300] Clause 94. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by a UE, cause the UE to: receive a request to send an on-demand sidelink positioning reference signal (SL-PRS) during a time period during which the UE is requested to send the SL-PRS; refrain from transmitting, receiving, or both on a transmit channel, a receive channel, or both that conflict with the requested on-demand SL-PRS; and send the requested on-demand SL-PRS.

[0301] Clause 95. The non-transitory computer-readable medium of Clause 94, wherein the request is received from a location server, a network node, or a second UE.

[0302] Clause 96. A non-transitory computer-readable medium according to any one of clauses 94 to 95, the non-transitory computer-readable medium also comprising computer-executable instructions which, when executed by the UE, cause the UE to: overwrite a DRX off cycle within the time period based on the request.

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

[0304] In addition, it will be appreciated by those skilled in the art that the various exemplary logic blocks, modules, circuits and algorithmic steps described in conjunction with the various aspects disclosed herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, frames, modules, circuits and steps have been generally described in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints proposed to the entire system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

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

[0306] The methods, sequences and / or algorithms described in conjunction with the various aspects disclosed herein may be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be integral with the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In an alternative, the processor and the storage medium may reside in a user terminal as discrete components.

[0307] In one or more example aspects, the function may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the function may be stored on a computer-readable medium or sent via a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. Storage media may be any available medium that can be accessed by a computer. Exemplarily and not restrictively, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, and any other medium that can also be used to carry or store desired program codes in the form of instructions or data structures and can be accessed by a computer. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, a server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of the 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.

[0308] Although the foregoing disclosure shows the exemplary aspects of the present disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the present disclosure as defined by the appended claims. In addition, the functions, steps and / or actions of the method claims according to the various aspects of the present disclosure described herein do not need to be performed in any particular order. In addition, although the elements of the present disclosure may be described or claimed in the singular, plural forms may also be considered unless explicitly stated to be limited to the singular.

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a configuration of a first set of sidelink positioning reference signal (SL-PRS) resources configured for transmission by a first set of sidelink UEs including the UE; as well as The sidelink transmission state of the first SL-PRS resource subset of the first SL-PRS resource set is determined based on the signal strength measurement result of the first SL-PRS resource set, the availability information of the first SL-PRS resource set, or both.

2. The method of claim 1, wherein the determining further comprises: determining that the sidelink transmission state of the first SL-PRS resource subset is inactive based on the signal strength measurement result of the first SL-PRS resource subset being lower than a threshold, and determining that the sidelink transmission state of the second subset of SL-PRS resources is active based on the signal strength measurement result of the second subset of SL-PRS resources being higher than the threshold, The signal strength measurement results may include power level, noise level, or interference level, or any combination thereof. The method of claim 2 , wherein the threshold is received from a location server or a base station.

4. The method according to claim 1, further comprising: The sidelink transmission status of the first SL-PRS resource subset is reported to at least one additional UE that shares the first SL-PRS resource set.

5. The method according to claim 1, wherein the availability information of the first SL-PRS resource set indicates available SL-PRS resources and conditionally available SL-PRS resources, wherein the available SL-PRS resources are configured to be sent, and wherein the conditionally available SL-PRS resources are non-contiguous, puncturable or conditionally active.

6. The method of claim 1, wherein at least a portion of the availability information of the first SL-PRS resource set is received in the configuration.

7. The method of claim 1, wherein the availability information of the first SL-PRS resource set is received from a first UE or a network node in the first sidelink UE set, and The availability information of the first SL-PRS resource set indicates a discontinuous reception (DRX) mode or a power saving mode of a second UE in the first sidelink UE set.

8. The method of claim 7, wherein the availability information of the first SL-PRS resource set comprises configuration information related to location-based triggering for the DRX mode or the power saving mode.

9. A method according to claim 1, wherein the availability information of the first SL-PRS resource set is received from a location server or a network node, and includes criteria for determining a time period during which the SL-PRS is configured to be sent by at least one other UE in the first side link UE set, the criteria including the DRX mode configuration of the at least one other UE.

10. The method of claim 1, wherein the determining further comprises: The sidelink transmission state of the first SL-PRS resource subset is determined as active or inactive after a defined time period based on the signal strength measurement result detected at the UE.

11. The method of claim 1, wherein the sidelink transmission status of the first SL-PRS resource subset is recorded together with a timestamp.

12. The method of claim 1, wherein the determining further comprises: The sidelink transmission state of the first SL-PRS resource subset is determined based on the presence or absence of an associated SL-PRS within a defined time period or for a given number of expected transmission instances.

13. The method according to claim 1, further comprising: A first sidelink transmission state of the UE as active or inactive is transmitted to the first sidelink UE set via inter-UE coordination.

14. The method according to claim 1, further comprising: The resource pool of the first SL-PRS resource set is allocated by the UE based on the sidelink transmission status of the first SL-PRS resource subset.

15. The method according to claim 1, further comprising: receiving, at the UE, configuration information associated with another UE within the first set of sidelink UEs; predicting, at the UE, SL-PRS availability of the other UE based on the configuration information; as well as Assistance data (AD) is sent, the AD being based on the predicted SL-PRS availability.

16. The method of claim 15, wherein predicting the SL-PRS availability for the other UE is based on the configuration information and a location of the other UE.

17. The method of claim 1, wherein another UE in the first set of sidelink UEs is configured with a discontinuous reception (DRX) mode, and Wherein the UE predicts that the DRX mode is disabled for the other UE at a location based on a previous SL-PRS transmission from the other UE at the location.

18. The method according to claim 1, further comprising: receiving configuration information associated with another UE in the first set of sidelink UEs; as well as reserving SL-PRS resources of a resource pool for the other UE based on the configuration information and the priority status of the other UE, The other UE is in an inactive time in a DRX mode.

19. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving configuration information associated with a location-based discontinuous reception (DRX) mode; Obtaining a location of the UE; as well as When in an inactive state of the location-based DRX mode, a sidelink positioning reference signal (SL-PRS) is sent based on the location.

20. The method of claim 19, wherein the location of the UE is based on satellite signals, cellular signals, Wi-Fi signals, sensor information, or any combination thereof.

21. The method of claim 19, wherein sending the SL-PRS is associated with a priority status or an on-demand request, and wherein the SL-PRS monitoring capability is non-continuous in a DRX mode.

22. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a request to send an on-demand sidelink positioning reference signal (SL-PRS) during a time period during which the UE is requested to send the SL-PRS; refraining from transmitting, receiving, or both on a transmit channel, a receive channel, or both that conflicts with the requested on-demand SL-PRS; and Send the requested on-demand SL-PRS.

23. The method of claim 22, wherein the request is received from a location server, a network node, or a second UE.

24. The method according to claim 22, further comprising: A DRX off cycle is overwritten within the time period based on the request.

25. A user equipment (UE), the user equipment (UE) comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receiving, via the at least one transceiver, a configuration of a first set of sidelink positioning reference signal (SL-PRS) resources configured for transmission by a first set of sidelink UEs; and The sidelink transmission state of the first SL-PRS resource subset of the first SL-PRS resource set is determined based on the signal strength measurement result of the first SL-PRS resource set, the availability information of the first SL-PRS resource set, or both.

26. The UE of claim 25, wherein the at least one processor is configured to determine comprises the at least one processor being configured to: determining that the sidelink transmission state of the first SL-PRS resource subset is inactive based on the signal strength measurement result of the first SL-PRS resource subset being lower than a threshold, determining that the sidelink transmission state of the second subset of SL-PRS resources is active based on the signal strength measurement result of the second subset of SL-PRS resources being higher than the threshold, The signal strength measurement results may include power level, noise level, or interference level, or any combination thereof.

27. The UE of claim 26, wherein the threshold is received from a location server.

28. The UE of claim 25, wherein the at least one processor is further configured to: The sidelink transmission status of the first SL-PRS resource subset is reported to at least one additional UE sharing the first SL-PRS resource set via the at least one transceiver.

29. The UE according to claim 25, wherein the availability information of the first SL-PRS resource set indicates available SL-PRS resources and conditionally available SL-PRS resources, wherein the available SL-PRS resources are configured to be sent, and wherein the conditionally available SL-PRS resources are non-contiguous, perforated or conditionally active.

30. The UE of claim 25, wherein at least a portion of the availability information of the first SL-PRS resource set is received in the configuration.

31. The UE of claim 25, wherein the availability information of the first SL-PRS resource set is received from a first UE or a network node in the first sidelink UE set, The availability information of the first SL-PRS resource set indicates a discontinuous reception (DRX) mode or a power saving mode of a second UE in the first sidelink UE set.

32. The UE of claim 31, wherein the availability information of the first SL-PRS resource set comprises configuration information related to location-based triggering for the DRX mode or the power saving mode.

33. A UE according to claim 25, wherein the availability information of the first SL-PRS resource set is received from a location server or a network node, and includes criteria for determining a time period during which the SL-PRS is configured to be sent by at least one other UE in the first side link UE set, and the criteria include the DRX mode configuration of the at least one other UE.

34. The UE of claim 25, wherein the at least one processor is configured to determine comprises the at least one processor being configured to: The sidelink transmission state of the first SL-PRS resource subset is determined as active or inactive after a defined time period based on the signal strength measurement result detected at the UE.

35. The UE of claim 25, wherein the sidelink transmission status of the first SL-PRS resource subset is recorded together with a timestamp.

36. The UE of claim 25, wherein the at least one processor is configured to determine comprises the at least one processor being configured to: The sidelink transmission state of the first SL-PRS resource subset is determined based on the presence or absence of an associated SL-PRS within a defined time period or for a given number of expected transmission instances.

37. The UE according to claim 25, further comprising: A first sidelink transmission state of the UE as active or inactive is transmitted to the first sidelink UE set via inter-UE coordination.

38. The UE of claim 25, wherein the at least one processor is further configured to: A resource pool of the first SL-PRS resource set is allocated based on the sidelink transmission status of the first SL-PRS resource subset.

39. The UE of claim 25, wherein the at least one processor is further configured to: receiving, at the UE, via the at least one transceiver, configuration information associated with another UE within the first set of sidelink UEs; predicting, at the UE, SL-PRS availability of the other UE based on the configuration information; and Assistance data (AD) is transmitted via the at least one transceiver, the AD being based on the predicted SL-PRS availability.

40. The UE of claim 39, wherein the UE predicts the SL-PRS availability of the other UE based on the configuration information and a location of the other UE.

41. The UE of claim 25, wherein another UE in the first set of sidelink UEs is configured with a discontinuous reception (DRX) mode, and Wherein the UE predicts that the DRX mode is disabled for the other UE at a location based on a previous SL-PRS transmission from the other UE at the location.

42. The UE of claim 25, wherein the at least one processor is further configured to: receiving, via the at least one transceiver, configuration information associated with another UE in the first set of sidelink UEs; and reserving SL-PRS resources of a resource pool for the other UE based on the configuration information and the priority status of the other UE, The other UE is in an inactive time in a DRX mode.

43. A user equipment (UE), the user equipment (UE) comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receiving, via the at least one transceiver, configuration information associated with a location-based discontinuous reception (DRX) mode; Obtaining a location of the UE; as well as When in an inactive state of the location-based DRX mode, a sidelink positioning reference signal (SL-PRS) is transmitted based on the location via the at least one transceiver.

44. The UE of claim 43, wherein the location of the UE is based on satellite signals, cellular signals, Wi-Fi signals, sensor information, or any combination thereof.

45. The UE of claim 43, wherein the UE sending the SL-PRS is associated with a priority status or an on-demand request, and wherein the SL-PRS monitoring capability is non-continuous in a DRX mode.

46. ​​A user equipment (UE), the user equipment (UE) comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receiving, via the at least one transceiver, a request to send an on-demand sidelink positioning reference signal (SL-PRS) during a time period during which the UE is requested to send the SL-PRS; refraining from transmitting, receiving, or both on a transmit channel, a receive channel, or both that conflicts with the requested on-demand SL-PRS; and The requested SL-PRS is transmitted via the at least one transceiver.

47. The UE of claim 46, wherein the request is received from a location server, a network node, or a second UE.

48. The UE of claim 46, wherein the at least one processor is further configured to: A DRX off cycle is overwritten within the time period based on the request.

49. A user equipment (UE), the user equipment (UE) comprising: means for receiving a configuration of a first set of sidelink positioning reference signal (SL-PRS) resources configured for transmission by a first set of sidelink UEs; and A component for determining a sidelink transmission state of a first SL-PRS resource subset based on a signal strength measurement result of the first SL-PRS resource set, availability information of the first SL-PRS resource set, or both.

50. A user equipment (UE), the user equipment (UE) comprising: means for receiving configuration information associated with a location-based discontinuous reception (DRX) mode; means for obtaining a location of the UE; and Means for transmitting a sidelink positioning reference signal (SL-PRS) based on the location while in an inactive state of the location-based DRX mode.

51. A user equipment (UE), the user equipment (UE) comprising: means for receiving a request to transmit an on-demand sidelink positioning reference signal (SL-PRS) during a time period during which the UE is requested to transmit the SL-PRS; means for refraining from transmitting, receiving, or both on a transmit channel, a receive channel, or both, that conflicts with the requested on-demand SL-PRS; and Means for sending the requested on-demand SL-PRS.

52. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by a user equipment (UE), cause the UE to: receiving a configuration of a first set of sidelink positioning reference signal (SL-PRS) resources configured for transmission by a first set of sidelink UEs; and The sidelink transmission state of the first SL-PRS resource subset is determined based on the signal strength measurement result of the first SL-PRS resource set, the availability information of the first SL-PRS resource set, or both.

53. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by a user equipment (UE), cause the UE to: receiving configuration information associated with a location-based discontinuous reception (DRX) mode; Obtaining a location of the UE; as well as When in an inactive state of the location-based DRX mode, a sidelink positioning reference signal (SL-PRS) is sent based on the location.

54. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by a user equipment (UE), cause the UE to: receiving a request to send an on-demand sidelink positioning reference signal (SL-PRS) during a time period during which the UE is requested to send the SL-PRS; refraining from transmitting, receiving, or both on a transmit channel, a receive channel, or both that conflicts with the requested on-demand SL-PRS; and Send the requested on-demand SL-PRS.

Images