Techniques for perception assistance using positioning and assistance data

Abstract

Disclosed are techniques for wireless communication. In an aspect, a user equipment (UE) may transmit, to a network entity, perception¬ based positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters. In some cases, the perception-based positioning-related information may be obtained by a modem of the UE through a cross-layer application programming interface (API). The UE may receive, from the network entity, a radio frequency (RF) -based positioning configuration responsive to the perception-based positioning-related information.

Description

TECHNIQUES FOR PERCEPTION ASSISTANCE USING POSITIONING AND ASSISTANCE DATABACKGROUND OF THE DISCLOSURE1. Field of the Disclosure

[0001] Aspects of the disclosure relate generally to wireless technologies.2. Description of the Related Art

[0002] Wireless communication systems have developed through various generations, including a first-generation analog wireless phone service (1G), a second-generation (2G) digital wireless phone service (including interim 2.5G and 2.75G networks), a third-generation (3G) high speed data, Internet-capable wireless service and a fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). There are presently many different types of wireless communication systems in use, including cellular and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog advanced mobile phone system (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), the Global System for Mobile communications (GSM), etc.

[0003] A fifth generation (5G) wireless standard, referred to as New Radio (NR), enables higher data transfer speeds, greater numbers of connections, and better coverage, among other improvements. The 5G standard, according to the Next Generation Mobile Networks Alliance, is designed to provide higher data rates as compared to previous standards, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements. These enhancements, as well as the use of higher frequency bands, advances in PRS processes and technology, and high-density deployments for 5G, enable highly accurate 5G-based positioning.SUMMARY

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

[0005] In an aspect, a method of wireless communication performed by a user equipment (UE) includes transmitting, to a network entity, perception-based positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters, wherein the perception-based positioning- related information is obtained by a modem of the UE through a cross-layer application programming interface (API); and receiving, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the perception-based positioning- related information.

[0006] In an aspect, a method of wireless communication performed by a network entity includes receiving, from a first user equipment (UE), first perception-based positioning-related information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters; and transmitting, to the first UE, a first radio frequency (RF)-based positioning configuration responsive to the first perception-based positioning-related information.

[0007] In an aspect, a user equipment (UE) includes one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: transmit, via the one or more transceivers, to a network entity, perception-based positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters, wherein the perception-based positioning-related information is obtained by a modem of the UE through a cross-layer application programming interface (API); and receive, via the one or more transceivers, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the perception-based positioning-related information.

[0008] In an aspect, a network entity includes one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories andthe one or more transceivers, the one or more processors, either alone or in combination, configured to: receive, via the one or more transceivers, from a first user equipment (UE), first perception-based positioning-related information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters; and transmit, via the one or more transceivers, to the first UE, a first radio frequency (RF)-based positioning configuration responsive to the first perception-based positioning-related information.

[0009] In an aspect, a user equipment (UE) includes means for transmitting, to a network entity, perception-based positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters, wherein the perception-based positioning-related information is obtained by a modem of the UE through a cross-layer application programming interface (API); and means for receiving, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the perception-based positioning-related information.

[0010] In an aspect, a network entity includes means for receiving, from a first user equipment (UE), first perception-based positioning-related information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters; and means for transmitting, to the first UE, a first radio frequency (RF)-based positioning configuration responsive to the first perception-based positioning-related information.

[0011] In an aspect, a non -transitory computer-readable medium stores computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: transmit, to a network entity, perception-based positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters, wherein the perception-based positioning-related information is obtained by a modem of the UE through a cross-layer application programming interface (API); and receive, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the perception-based positioning-related information.

[0012] In an aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a network entity, cause the network entity to: receive, from a first user equipment (UE), first perception-based positioning-related information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters; and transmit, to the first UE, a first radio frequency (RF)-based positioning configuration responsive to the first perception-based positioning-related information.

[0013] In an aspect, a method of wireless communication performed by a user equipment (UE) includes transmitting, to a network entity, positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters related to at least one of a position or an orientation of the UE; and receiving, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the positioning-related information.

[0014] In an aspect, a user equipment (UE) includes one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: transmit, via the one or more transceivers, to a network entity, positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters related to at least one of a position or an orientation of the UE; and receive, via the one or more transceivers, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the positioning-related information.

[0015] In an aspect, a user equipment (UE) includes means for transmitting, to a network entity, positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters related to at least one of a position or an orientation of the UE; and means for receiving, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the positioning- related information.

[0016] In an aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: transmit, to a network entity, positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters related to at least one of a position or an orientation of the UE; and receive, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the positioning- related information.

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

[0018] The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration of the aspects and not limitation thereof.

[0019] FIG. 1 illustrates an example wireless communications system, according to aspects of the disclosure.

[0020] FIGS. 2 A, 2B, and 2C illustrate example wireless network structures, according to aspects of the disclosure.

[0021] FIGS. 3A, 3B, and 3C are simplified block diagrams 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.

[0022] FIG. 4 illustrates examples of various positioning methods supported in New Radio (NR), according to aspects of the disclosure.

[0023] FIG. 5 illustrates an example Long-Term Evolution (LTE) positioning protocol (LPP) call flow between a UE and a location server for performing positioning operations.

[0024] FIG. 6 is a diagram illustrating an example frame structure, according to aspects of the disclosure.

[0025] FIG. 7 is a diagram illustrating various downlink channels within an example downlink slot, according to aspects of the disclosure.

[0026] FIG. 8 is a diagram illustrating various uplink channels within an example uplink slot, according to aspects of the disclosure.

[0027] FIG. 9 is a diagram of an example positioning reference signal (PRS) configuration for the PRS transmissions of a given base station, according to aspects of the disclosure.

[0028] FIGS. 10A and 10B illustrate various comb patterns supported for downlink positioning reference signals (PRS) within a resource block.

[0029] FIG. 11 illustrates an example wireless communications system that supports techniques for perception assistance using positioning and assistance data, according to aspects of the disclosure.

[0030] FIG. 12 illustrates an example scenario using techniques for perception assistance using positioning and assistance data, according to aspects of the disclosure.

[0031] FIG. 13 illustrates an example of a network entity -initiated on-demand PRS positioning procedure, according to aspects of the disclosure.

[0032] FIG. 14 illustrates an example of a UE-initiated on-demand PRS positioning procedure, according to aspects of the disclosure.

[0033] FIG. 15 illustrates an example of a downlink (DL)-PRS information element (IE), according to aspects of the disclosure.

[0034] FIGS. 16A and 16B illustrate an example position estimation procedure using LPP with an uplink (UL)-sounding reference signal (SRS) configuration, according to aspects of the disclosure.

[0035] FIGS. 17 and 18 illustrate example processes of wireless communication, according to aspects of the disclosure.DETAILED DESCRIPTION

[0036] Aspects of the disclosure are provided in the following description and related drawings directed to various examples provided for illustration purposes. Alternate aspects may be devised without departing from the scope of the disclosure. Additionally, well-known elements of the disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the disclosure.

[0037] Various aspects relate generally to wireless communication systems that support interactive applications, such as but not limited to augmented reality (AR), virtual reality (VR), mixed reality (MR), extended reality (XR), and metaverse-based applications. These interactive applications may include media sharing among multiple users in a single location. Additionally, these interactive applications may provide immersive experiences in various areas, such as but not limited to gaming, socializing, healthcare, industry, transportation, etc. In order to support enhanced services (e.g., enhanced XR- based services) associated with these interactive applications, devices of a wireless communication system may be configured to adhere to multiple key performance indicators (KPIs) corresponding to various aspects or characteristics of these enhanced services.

[0038] An aspect of some enhanced services includes degrees of freedom (DOF) parameters associated with a device. That is, for example, one or more DOF parameters relate to a position and / or an orientation of the device. In some cases, six mechanical degrees of freedom of movement (6DoF) of a device and / or associated body / structural element of the device in three-dimensional space may include three parameters corresponding topositioning (e.g., linear position, horizontal straightness, and vertical straightness) and three parameters corresponding to orientation (e.g., pitch, yaw, and roll). The 6D0F parameters of a device and / or associated body / structural element of the device may correspond to a pose of a user wearing the device and / or the associated body / structural element of the device in accordance with some aspects. That is, for example, the pose may be used in an interactive application for identifying the position and orientation of the user’s body or body part (e.g., head, eyes, hand, etc.).

[0039] In some examples, a user equipment (UE), such as a perception entity may transmit perception-based positioning-related information to a network entity. In some cases, the perception-based positioning-related information may include information associated with a metric corresponding to one or more DoF parameters. For example, the metric may correspond to a KPI metric and / or quality of service (QoS) metric associated with a DoF requirement for an enhanced service of an interactive application. The UE may receive a radio frequency (RF)-based positioning configuration (e.g., an NR positioning configuration of time and frequency resources) from the network entity responsive to the perception-based positioning-related information.

[0040] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by receiving an RF -based positioning configuration from the network entity, the described techniques can be used to save power by refraining from using one or more sensors during one or more perception-based positioning sessions performed by the UE and basing the one or more perception-based positioning sessions on positioning techniques using the RF-based positioning configuration. In some examples, by deciding that an RF-based positioning configuration would not assist a UE based on the perception-based positioning-related information, the network entity may refrain from configuring the UE running the interactive application with RF-based positioning resources. In some cases, these time and frequency resources may be allocated for data transmission purposes for the UE.

[0041] The words “exemplary” and / or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and / or “example” is not necessarily to be construed as preferred or advantageous over otheraspects. Likewise, the term “aspects of the disclosure” does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation.

[0042] Those of skill in the art will appreciate that the information and signals described below may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description below may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the particular application, in part on the desired design, in part on the corresponding technology, etc.

[0043] Further, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be recognized that various actions described herein can be performed by specific circuits (e.g., application specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequence(s) of actions described herein can be considered to be embodied entirely within any form of non- transitory computer-readable storage medium having stored therein a corresponding set of computer instructions that, upon execution, would cause or instruct an associated processor of a device to perform the functionality described herein. Thus, the various aspects of the disclosure may be embodied in a number of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the aspects described herein, the corresponding form of any such aspects may be described herein as, for example, “logic configured to” perform the described action.

[0044] As used herein, the terms “user equipment” (UE) and “base station” are not intended to be specific or otherwise limited to any particular radio access technology (RAT), unless otherwise noted. In general, a UE may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, consumer asset locating device, wearable (e.g., smartwatch, glasses, AR / VR headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.), Internet of Things (loT) device, etc.) used by a user to communicate over a wireless communications network. A UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a radio access network (RAN). As used herein, the term “UE” may be referred to interchangeably as an “access terminal” or “AT,” a “client device,” a “wireless device,” a “subscriber device,” a“subscriber terminal,” a “subscriber station,” a “user terminal” or “UT,” a “mobile device,” a “mobile terminal,” a “mobile station,” or variations thereof. Generally, UEs can communicate with a core network via a RAN, and through the core network the UEs can be connected with external networks such as the Internet and with other UEs. Of course, other mechanisms of connecting to the core network and / or the Internet are also possible for the UEs, such as over wired access networks, wireless local area network (WLAN) networks (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.) and so on.

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

[0046] The term “base station” may refer to a single physical transmission-reception point (TRP) or to 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 TRPs may be an array of antennas (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming) of the base station. Where the term “base station” refers to multiple non-co-located physical TRPs, the physical TRPs may be a distributed antenna system (DAS) (a network of spatially separated antennasconnected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs may be the serving base station receiving the measurement report from the UE and a neighbor base station whose reference radio frequency (RF) signals the UE is measuring. Because a TRP is the point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station are to be understood as referring to a particular TRP of the base station.

[0047] In some implementations that support positioning of UEs, a base station may not support wireless access by UEs (e.g., may not support data, voice, and / or signaling connections for UEs), but may instead transmit reference signals to UEs to be measured by the UEs, and / or may receive and measure signals transmitted by the UEs. Such a base station may be referred to as a positioning beacon (e.g., when transmitting signals to UEs) and / or as a location measurement unit (e.g., when receiving and measuring signals from UEs).

[0048] An “RF signal” comprises an electromagnetic wave of a given frequency that transports information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single “RF signal” or multiple “RF signals” to a receiver. However, the receiver may receive multiple “RF signals” corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a “multipath” RF signal. As used herein, 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.

[0049] FIG. 1 illustrates an example wireless communications system 100, according to aspects of the disclosure. The wireless communications system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled “BS”) and various UEs 104. The base stations 102 may include macro cell base stations (high power cellular base stations) and / or small cell base stations (low power cellular base stations). In an aspect, the macro cell base stations may include eNBs and / or ng-eNBs where the wireless communications system 100 corresponds to an LTE network, or gNBs where the wireless communications system 100 corresponds to a NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0050] 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 backhaul links 122, and through the core network 170 to one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)). The location server(s) 172 may be part of core network 170 or may be external to core network 170. A location server 172 may be integrated with a base station 102. A UE 104 may communicate with a location server 172 directly or indirectly. For example, a UE 104 may communicate with a location server 172 via the base station 102 that is currently serving that UE 104. A UE 104 may also communicate with a location server 172 through another path, such as via an application server (not shown), via another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), and so on. For signaling purposes, communication between a UE 104 and a location server 172 may be represented as an indirect connection (e.g., through the core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with the intervening nodes (if any) omitted from a signaling diagram for clarity.

[0051] In addition to other functions, the base stations 102 may perform functions that relate to one or more of transferring user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, 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 the EPC / 5GC) over backhaul links 134, which may be wired or wireless.

[0052] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more cells may be supported by a base station 102 in each geographic coverage area 110. A “cell” is a logical communication entity used for communication with a base station (e.g., over some frequency resource, referred to as a carrier frequency, component carrier, carrier, band, or the like), 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.) for distinguishing cells operating via the same or a different carrier frequency. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband loT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs. Because a cell is supported by a specific base station, the term “cell” may refer to either or both of the logical communication entity and the base station that supports it, depending on the context. In addition, because a TRP is typically the physical transmission point of a cell, the terms “cell” and “TRP” may be used interchangeably. In some cases, the term “cell” may also refer to a geographic coverage area of a base station (e.g., a sector), insofar as a carrier frequency can be detected and used for communication within some portion of geographic coverage areas 110.

[0053] While neighboring macro cell base station 102 geographic coverage areas 110 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may be substantially overlapped by 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 area 110 of one or more macro cell base stations 102. A network that includes both small cell and macro cell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG).

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

[0055] The wireless communications system 100 may further include a wireless local area network (WLAN) access point (AP) 150 in communication with WLAN stations (STAs) 152 via communication links 154 in an unlicensed frequency spectrum (e.g., 5 GHz).When communicating in an unlicensed frequency spectrum, the WLAN STAs 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communicating in order to determine whether the channel is available.

[0056] The small cell base station 102' may operate in a licensed and / or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum as used by the WLAN AP 150. The small cell base station 102', employing LTE / 5G in an unlicensed frequency spectrum, may boost coverage to and / or increase capacity of the access network. NR in unlicensed spectrum may be referred to as NR-U. LTE in an unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MULTEFIRE®.

[0057] The wireless communications system 100 may further include a millimeter wave (mmW) base station 180 that may operate in mmW frequencies and / or near mmW frequencies in communication with a UE 182. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW / near mmW radio frequency band have high path loss and a relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and / or receive) over a mmW communication link 184 to compensate for the extremely high path loss and short range. Further, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be appreciated that the foregoing illustrations are merely examples and should not be construed to limit the various aspects disclosed herein.

[0058] 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 (omni-directionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in thatspecific direction, thereby providing a faster (in terms of data rate) and stronger RF signal for the receiving device(s). To change the directionality of the RF signal when transmitting, a network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that are broadcasting the RF signal. For example, a network node may use an array of antennas (referred to as a “phased array” or an “antenna array”) that creates a beam of RF waves that can be “steered” to point in different directions, without actually moving the antennas. Specifically, the RF current from the transmitter is fed to the individual antennas with the correct phase relationship so that the radio waves from the separate antennas add together to increase the radiation in a desired direction, while cancelling to suppress radiation in undesired directions.

[0059] Transmit beams may be quasi-co-located, meaning that they appear to the receiver (e.g., a UE) as having the same parameters, regardless of whether or not the transmitting antennas of the network node themselves are physically co-located. In NR, there are four types of quasi-co-location (QCL) relations. Specifically, a QCL relation of a given type means that certain parameters about a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is QCL Type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate the spatial receive parameter of a second reference RF signal transmitted on the same channel.

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

[0061] Transmit and receive beams may be spatially related. A spatial relation means that parameters for a second beam (e.g., a transmit or receive beam) for a second reference signal can be derived from information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal. For example, a UE may use a particular receive beam to receive a reference downlink reference signal (e.g., synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam for sending an uplink reference signal (e.g., sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

[0062] Note that a “downlink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. If the UE is forming the downlink beam, however, it is a receive beam to receive the downlink reference signal. Similarly, an “uplink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the uplink beam, it is an uplink receive beam, and if a UE is forming the uplink beam, it is an uplink transmit beam.

[0063] The electromagnetic spectrum is often subdivided, based on frequency / wavelength, into various classes, bands, channels, etc. In 5G NR two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 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 referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the INTERNATIONAL TELECOMMUNICATION UNION® as a “millimeter wave” band.

[0064] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies.Recent 5G NR studies have identified an operating band for these mid-band frequenciesas frequency range designation FR3 (7.125 GHz - 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend features of FR1 and / or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 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.

[0065] With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band.

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

[0067] For example, still referring to FIG. 1, one of the frequencies utilized by the macro cell base stations 102 may be an anchor carrier (or “PCell”) and other frequencies utilized by the macro cell base stations 102 and / or the mmW base station 180 may be secondary carriers (“SCells”). The simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically lead to a two-fold increase in data rate (i.e., 40 MHz), compared to that attained by a single 20 MHz carrier.

[0068] The wireless communications system 100 may further include a UE 164 that may communicate with a macro cell base station 102 over a communication link 120 and / or the mmW base station 180 over a mmW communication link 184. For example, the macro cell base station 102 may support a PCell and one or more SCells for the UE 164 and the mmW base station 180 may support one or more SCells for the UE 164.

[0069] In some cases, the UE 164 and the UE 182 may be capable of sidelink communication. Sidelink-capable UEs (SL-UEs) may communicate with base stations 102 over communication links 120 using the Uu interface (i.e., the air interface between a UE and a base station). SL-UEs (e.g., UE 164, UE 182) may also communicate directly with each other over a wireless sidelink 160 using the PC5 interface (i.e., the air interface between sidelink-capable UEs). A wireless sidelink (or just “sidelink”) is an adaptation of the core cellular (e.g., LTE, NR) standard that allows direct communication between two or more UEs without the communication needing to go through a base station. Sidelink communication may be unicast or multicast, and may be used for device-to-device (D2D) media-sharing, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, etc.), emergency rescue applications, etc. One or more of a group of SL- UEs utilizing sidelink communications may be within the geographic coverage area 110 of a base station 102. Other SL-UEs in such a group may be outside the geographiccoverage area 110 of a base station 102 or be otherwise unable to receive transmissions from a base station 102. In some cases, groups of SL-UEs communicating via sidelink communications may utilize a one-to-many (1 :M) system in which each SL-UE transmits to every other SL-UE in the group. In some cases, a base station 102 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink communications are carried out between SL-UEs without the involvement of a base station 102.

[0070] In an aspect, the sidelink 160 may operate over a wireless communication medium of interest, which may be shared with other wireless communications between other vehicles and / or infrastructure access points, as well as other RATs. A “medium” may be composed of one or more time, frequency, and / or space communication resources (e.g., encompassing one or more channels across one or more carriers) associated with wireless communication between one or more transmitter / receiver pairs. In an aspect, 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 a government entity such as the Federal Communications Commission (FCC) in the United States), these systems, in particular those employing small cell access points, have recently extended operation into unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technologies, most notably IEEE 802.1 lx WLAN technologies generally referred to as “Wi-Fi.” Example systems of this type include different variants of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and so on.

[0071] Note that although FIG. 1 only illustrates two of the UEs as SL-UEs (i.e., UEs 164 and 182), any of the illustrated UEs may be SL-UEs. Further, although only UE 182 was described as being capable of beamforming, any of the illustrated UEs, including UE 164, may be capable of beamforming. Where SL-UEs are capable of beamforming, they may beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UEs 104), towards base stations (e.g., base stations 102, 180, small cell 102’, access point 150), etc. Thus, in some cases, UEs 164 and 182 may utilize beamforming over sidelink 160.

[0072] In the example of FIG. 1, any of the illustrated UEs (shown in FIG. 1 as a single UE 104 for simplicity) may receive signals 124 from one or more Earth orbiting space vehicles (SVs) 112 (e.g., satellites). In an aspect, the SVs 112 may be part of a satellite positioning system that a UE 104 can use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) positioned to enable receivers (e.g., UEs 104) to determine their location on or above the Earth based, at least in part, on positioning signals (e.g., signals 124) received from the transmitters. Such a transmitter typically transmits a signal marked with a repeating pseudo-random noise (PN) code of a set number of chips. While typically located in SVs 112, transmitters may sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. A UE 104 may include one or more dedicated receivers specifically designed to receive signals 124 for deriving geo location information from the SVs 112.

[0073] In a satellite positioning system, the use of signals 124 can be augmented 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, an SBAS may include an augmentation system(s) that provides integrity information, differential corrections, etc., such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multifunctional Satellite Augmentation System (MSAS), the Global Positioning System (GPS) Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and / or the like. 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.

[0074] In an aspect, SVs 112 may additionally or alternatively be part of one or more nonterrestrial networks (NTNs). In an NTN, an 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 a modified base station 102 (without a terrestrial antenna) or a network node in a 5GC. This element would in turn provide access to other elements in the 5G network and ultimately to entities external to the 5G network, such as Internet web servers and other user devices. In that way, a UE 104 may receive communication signals (e.g., signals 124) from an SV 112 instead of, or in addition to, communication signals from a terrestrial base station 102.

[0075] The wireless communications system 100 may further include one or more UEs, such as UE 190, that connects indirectly to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “sidelinks”). In the example of FIG. 1, UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which UE 190 may indirectly obtain cellular connectivity) and a D2D P2P link 194 with WLAN STA 152 connected to the WLAN AP 150 (through which UE 190 may indirectly obtain WLAN-based Internet connectivity). In an example, the D2D P2P links 192 and 194 may be supported with any well-known D2D RAT, such as LTE Direct (LTE-D), WI-FI DIRECT®, BLUETOOTH®, and so on.

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

[0077] Another optional aspect may include a location server 230, which may be in communication with the 5GC 210 to provide location assistance for UE(s) 204. The location server 230 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server. The location server 230 can be configured to support one or more location services for UEs 204 that can connect to the location server 230 via the corenetwork, 5GC 210, and / or via the Internet (not illustrated). Further, 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 service server).

[0078] FIG. 2B illustrates another example wireless network structure 240. A 5GC 260 (which may correspond to 5GC 210 in FIG. 2A) can be viewed functionally as control plane functions, provided by an access and mobility management function (AMF) 264, and user plane functions, provided by a user plane function (UPF) 262, which operate cooperatively to form the core network (i.e., 5GC 260). The functions of the AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and a session management function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE 204 and the 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 the intermediate key that was established as a result of the UE 204 authentication process. In the case of authentication based on a UMTS (universal mobile telecommunications system) subscriber identity module (USIM), the AMF 264 retrieves the security material from the AUSF. The functions of the AMF 264 also include security context management (SCM). The SCM receives a key from the SEAF that it uses to derive access-network specific keys. The functionality of the AMF 264 also includes location services management for regulatory services, transport for location services messages between the UE 204 and a location management function (LMF) 270 (which acts as a location server 230), transport for location services messages between the NG-RAN 220 and the LMF 270, evolved packet system (EPS) bearer identifier allocation for interworking with the EPS, and UE 204 mobility event notification. In addition, the AMF 264 also supports functionalities for non-3GPP® (Third Generation Partnership Project) access networks.

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

[0080] The functions of the SMF 266 include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering at the UPF 262 to route traffic to the proper destination, control of part of policy enforcement and QoS, and downlink data notification. The interface over which the SMF 266 communicates with the AMF 264 is referred to as the Ni l interface.

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

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

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

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

[0085] Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. 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) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, AP, TRP, cell, etc.) may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.

[0086] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among 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 throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU also can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0087] Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (0-RAN (such as the network configuration sponsored by the 0-RAN ALLIANCE®)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C- RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0088] FIG. 2C illustrates an example disaggregated base station architecture 250, according to aspects of the disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU 226) that can communicate directly with 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 (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 259 via an E2 link, or a Non-Real Time (Non-RT) RIC 257 associated with a Service Management and Orchestration (SMO) Framework 255, or both). A CU 280 may communicate with one or more DUs 285 (e.g., gNB-DUs 228) via respective midhaul links, such as an Fl interface. The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective fronthaul links. The RUs 287 may communicate with respective UEs 204 via one or more radio frequency (RF) access links. In some implementations, the UE 204 may be simultaneously served by multiple RUs 287.

[0089] Each of the units, i.e., the CUs 280, the DUs 285, the RUs 287, as well as the Near-RT RICs 259, the Non-RT RICs 257 and the SMO Framework 255, may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0090] In some aspects, the CU 280 may host one or more higher layer control functions. Such control functions can include RRC, PDCP, service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 280. The 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 implementations, the CU 280 can be logically split into oneor more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the El interface when implemented in an O-RAN configuration. The CU 280 can be implemented to communicate with the DU 285, as necessary, for network control and signaling.

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

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

[0093] The SMO Framework 255 may be configured to support RAN deployment and provisioning of non-virtualized 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 operations and maintenance interface (such as an 01 interface). For virtualized network elements, the SMO Framework 255 may be configured to interactwith a cloud computing platform (such as an open cloud (O-Cloud) 269) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 280, DUs 285, RUs 287 and Near-RT RICs 259. In some implementations, the SMO Framework 255 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 261, via an 01 interface. Additionally, in some implementations, the SMO Framework 255 can communicate directly with one or more RUs 287 via an 01 interface. The SMO Framework 255 also may include a Non-RT RIC 257 configured to support functionality of the SMO Framework 255.

[0094] The Non-RT RIC 257 may be configured to include a logical function that enables non- real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near-RT RIC 259. The Non-RT RIC 257 may be coupled to or communicate with (such as via an Al interface) the Near- RT RIC 259. The Near-RT RIC 259 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 280, one or more DUs 285, or both, as well as an O-eNB, with the Near-RT RIC 259.

[0095] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 259, the Non-RT RIC 257 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 259 and may be received at the SMO Framework 255 or the Non-RT RIC 257 from non-network data sources or from network functions. 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 reconfiguration via 01) or via creation of RAN management policies (such as Al policies).

[0096] FIGS. 3A, 3B, and 3C illustrate several example components (represented by corresponding blocks) that may be incorporated into a UE 304 (which may correspond toany of the UEs described herein), a base station 302 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including the location server 230 and the LMF 270, or alternatively may be independent from the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in FIGS. 2A and 2B, such as a private network) to support the operations described herein. It will be appreciated that these components may be implemented in different types of apparatuses in different implementations (e.g., in an ASIC, in a system-on-chip (SoC), etc.). The illustrated components may also be incorporated into other apparatuses in a communication system. For example, other apparatuses in a system may include components similar to those described to provide similar functionality. Also, a given apparatus may contain one or more of the components. For example, an apparatus may include multiple transceiver components that enable the apparatus to operate on multiple carriers and / or communicate via different technologies.

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

[0098] The UE 304 and the base station 302 each also include, at least in some cases, one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and provide means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., Wi-Fi, LTE Direct, BLUETOOTH®, ZIGBEE®, Z-WAVE®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), ultra- wideband (UWB), etc.) over a wireless communication medium of interest. The short- range wireless transceivers 320 and 360 may be variously configured for transmitting and encoding signals 328 and 368 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 328 and 368 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 320 and 360 may be Wi-Fi transceivers, BLUETOOTH® transceivers, ZIGBEE® and / or Z-WAVE® transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to- everything (V2X) transceivers.

[0099] The UE 304 and the base station 302 also include, at least in some cases, satellite signal interfaces 330 and 370, which each include one or more satellite signal receivers 332 and 372, respectively, and may optionally include one or more satellite signal transmitters 334 and 374, respectively. In some cases, the base station 302 may be a terrestrial base station that may communicate with space vehicles (e.g., space vehicles 112) via the satellite signal interface 370. In other cases, the base station 302 may be a space vehicle (or other non-terrestrial entity) that uses the satellite signal interface 370 to communicate with terrestrial networks and / or other space vehicles.

[0100] The satellite signal receivers 332 and 372 may be connected to one or more antennas 336 and 376, respectively, and may provide means for receiving and / or measuring satellitepositioning / communication signals 338 and 378, respectively. Where the satellite signal receiver(s) 332 and 372 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) signals, etc. Where the satellite signal receiver(s) 332 and 372 are nonterrestrial 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 receiver(s) 332 and 372 may comprise any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. The satellite signal receiver(s) 332 and 372 may request information and operations as appropriate from the other systems, and, at least in some cases, perform calculations to determine locations of the UE 304 and the base station 302, respectively, using measurements obtained by any suitable satellite positioning system algorithm.

[0101] The optional satellite signal transmitter(s) 334 and 374, when present, may be connected to the one or more antennas 336 and 376, respectively, and may provide means for transmitting satellite positioning / communication signals 338 and 378, respectively. Where the satellite signal transmitter(s) 374 are satellite positioning system transmitters, the satellite positioning / communication signals 378 may be GPS signals, GLONASS® signals, Galileo signals, Beidou signals, NAVIC, QZSS signals, etc. Where the satellite signal transmitter(s) 334 and 374 are NTN transmitters, 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 transmitter(s) 334 and 374 may comprise any suitable hardware and / or software for transmitting satellite positioning / communication signals 338 and 378, respectively. The satellite signal transmitter(s) 334 and 374 may request information and operations as appropriate from the other systems.

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

[0103] A transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). A transceiver may be an integrated device (e.g., embodying transmitter circuitry and receiver circuitry in a single device) in some implementations, may comprise separate transmitter circuitry and separate receiver circuitry in some implementations, or may be embodied in other ways in other implementations. The transmitter circuitry and receiver circuitry 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. Wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus (e.g., UE 304, base station 302) to perform transmit “beamforming,” as described herein. Similarly, wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus (e.g., UE 304, base station 302) to perform receive beamforming, as described herein. In an aspect, the transmitter circuitry and receiver circuitry may share the same plurality of antennas (e.g., antennas 316, 326, 356, 366), such that the respective apparatus can only receive or transmit at a given time, not both at the same time. A wireless transceiver (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listen module (NLM) or the like for performing various measurements.

[0104] As used herein, the various wireless transceivers (e.g., transceivers 310, 320, 350, and 360, and network transceivers 380 and 390 in some implementations) and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) may generally be characterized as “a transceiver,” “at least one transceiver,” or “one or moretransceivers.” As such, whether a particular transceiver is a wired or wireless transceiver may be inferred from the type of communication performed. For example, backhaul communication between network devices or servers will generally relate to signaling via a wired transceiver, whereas wireless communication between a UE (e.g., UE 304) and a base station (e.g., base station 302) will generally relate to signaling via a wireless transceiver.

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

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

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

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

[0109] Referring to the one or more processors 384 in more detail, in the 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. The one or more processors 384 may provide RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0110] The transmitter 354 and the receiver 352 may implement Layer- 1 (LI) functionality associated with various signal processing functions. Layer- 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols 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., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to produce multiple spatialstreams. Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and / or channel condition feedback transmitted by the UE 304. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a respective spatial stream for transmission.

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

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

[0113] Similar to the functionality described in connection with the downlink transmission by the base station 302, the one or more processors 342 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection,integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and 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 transmitted by the base station 302 may be used by the transmitter 314 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antenna(s) 316. The transmitter 314 may modulate an RF carrier with a respective spatial stream for transmission.

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

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

[0117] For convenience, the UE 304, the base station 302, and / or the network entity 306 are shown in FIGS. 3 A, 3B, and 3C as including various components that may be configured according to the various examples described herein. It will be appreciated, however, that the illustrated components may have different functionality in different designs. In particular, various components in FIGS. 3A to 3C are optional in alternative configurations and the various aspects include configurations that may vary due to design choice, costs, use of the device, or other considerations. For example, in case of FIG. 3A, a particular implementation of UE 304 may omit the WWAN transceiver(s) 310 (e.g., a wearable device or tablet computer or personal computer (PC) or laptop may have Wi-Fiand / or BLUETOOTH® capability without cellular capability), or may omit the short- range wireless transceiver(s) 320 (e.g., cellular-only, etc.), or may omit the satellite signal interface 330, or may omit the sensor(s) 344, and so on. In another example, in case of FIG. 3B, a particular implementation of the base station 302 may omit the WWAN transceiver(s) 350 (e.g., a Wi-Fi “hotspot” access point without cellular capability), or may omit the short-range wireless transceiver(s) 360 (e.g., cellular-only, etc.), or may omit the satellite signal interface 370, and so on. For brevity, illustration of the various alternative configurations is not provided herein, but would be readily understandable to one skilled in the art.

[0118] The various components of the UE 304, the base station 302, and the network entity 306 may be communicatively coupled to each other over data buses 308, 382, and 392, respectively. In an aspect, the data buses 308, 382, and 392 may form, or be part of, a communication interface of the UE 304, the base station 302, and the 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 302), the data buses 308, 382, and 392 may provide communication between them.

[0119] The components of FIGS. 3A, 3B, and 3C may be implemented in various ways. In some implementations, the components of FIGS. 3 A, 3B, and 3C 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 incorporate at least one memory component for storing information or executable code used by the circuit to provide this functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by processor and memory component(s) of the UE 304 (e.g., by execution of appropriate code and / or by appropriate configuration of processor components). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by processor and memory component(s) of the base station 302 (e.g., by execution of appropriate code and / or by appropriate configuration of processor components). Also, some or all of the functionality represented by blocks 390 to 398 may be implemented by processor and memory component(s) of the network entity 306 (e.g., by execution of appropriate code and / or by appropriate configuration of processor components). For simplicity, various operations, acts, and / or functions are described herein as being performed “by a UE,” “bya base station,” “by a network entity,” etc. However, as will be appreciated, such operations, acts, and / or functions may actually be performed by specific components or combinations of components of the UE 304, base station 302, network entity 306, etc., such as the processors 342, 384, 394, the transceivers 310, 320, 350, and 360, the memories 340, 386, and 396, the DoF positioning component 348, 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 distinct from a network operator or operation of the 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 private network that may be configured to communicate with the UE 304 via the base station 302 or independently from the base station 302 (e.g., over a non-cellular communication link, such as Wi-Fi).

[0121] NR supports a number of cellular network-based positioning technologies, including downlink-based, uplink-based, 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. FIG. 4 illustrates examples of various positioning methods, according to aspects of the disclosure. In an OTDOA or DL-TDOA positioning procedure, illustrated by scenario 410, a UE measures the differences between the times of arrival (ToAs) of reference signals (e.g., positioning reference signals (PRS)) received from pairs of base stations, referred to as reference signal time difference (RSTD) or time difference of arrival (TDOA) measurements, and reports them to a positioning entity. More specifically, the UE receives the identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in assistance data. The UE then measures the RSTD between the reference base station and each of the non-reference base stations. Based on the known locations of the involved base stations and the RSTD measurements, the positioning entity (e.g., the UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the UE’s location.

[0122] For DL-AoD positioning, illustrated by scenario 420, the positioning entity uses a measurement report from the UE of received signal strength measurements of multiple downlink transmit beams to determine the angle(s) between the UE and the transmittingbase station(s). The positioning entity can then estimate the location of the UE based on the determined angle(s) and the known location(s) of the transmitting base station(s).

[0123] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle-of-arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but is based on uplink reference signals (e.g., sounding reference signals (SRS)) transmitted by the UE to multiple base stations. Specifically, a UE transmits one or more uplink reference signals that are measured by a reference base station and a plurality of non-reference base stations. Each base station then reports the reception time (referred to as the relative time of arrival (RTOA)) of the reference signal(s) to a positioning entity (e.g., a location server) that knows the locations and relative timing of the involved base stations. Based on the reception-to-reception (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 locations of the base stations, and their known timing offsets, the positioning entity can estimate the location of the UE using TDOA.

[0124] 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 a UE on one or more uplink receive beams. The positioning entity uses the signal strength measurements and the angle(s) of the receive beam(s) to determine the angle(s) between the UE and the base station(s). Based on the determined angle(s) and the known location(s) of the base station(s), the positioning entity can then estimate the location of the UE.

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

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

[0127] To assist positioning operations, a 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 identifiers of the base stations (or the cells / TRPs of the base stations) from which to measure reference signals, the reference signal configuration parameters (e.g., the number of consecutive slots including PRS, periodicity of the consecutive slots including PRS, muting sequence, frequency hopping sequence, reference signal identifier, reference signal bandwidth, etc.), and / or other parameters applicable to the particular positioning method. Alternatively, the assistance data may originate directly from the base stations themselves (e.g., in periodically broadcasted overhead messages, etc.). In some cases, the UE may be able to detect neighbor network nodes itself without the use of assistance data.

[0128] In the case of an OTDOA or DL-TDOA positioning procedure, the assistance data may further 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 (ps). In some cases, when any of the resources used for the positioning measurement are in FR1, the value range for the uncertainty of the expected RSTD may be + / - 32 ps. In other cases, when all of the resources used for the positioningmeasurement(s) are in FR2, the value range for the uncertainty of the expected RSTD may be + / - 8 ps.

[0129] A location estimate may be referred to by other names, such as a position estimate, location, position, position fix, fix, or the like. A location estimate may be geodetic and comprise coordinates (e.g., latitude, longitude, and possibly altitude) or may be civic and comprise a street address, postal address, or some other verbal description of a location. A location estimate may further be defined relative to some other known location or defined in absolute terms (e.g., using latitude, longitude, and possibly altitude). A location 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 level of confidence).

[0130] FIG. 5 illustrates an example Long-Term Evolution (LTE) positioning protocol (LPP) procedure 500 between a UE 504 and a location server (illustrated as a location management function (LMF) 570) for performing positioning operations. As illustrated in FIG. 5, positioning of the UE 504 is supported via an exchange of LPP messages between the UE 504 and the LMF 570. The LPP messages may be exchanged between UE 504 and the LMF 570 via the UE’s 504 serving base station (illustrated as a serving gNB 502) and a core network (not shown). The LPP procedure 500 may be used to position the UE 504 in order to support various location-related services, such as navigation for UE 504 (or for the user of UE 504), or for routing, or for provision of an accurate location to a public safety answering point (PSAP) in association with an emergency call from UE 504 to a PSAP, or for some other reason. The LPP procedure 500 may also be referred to as a positioning session, and there may be multiple positioning sessions for different types of positioning methods (e.g., downlink time difference of arrival (DL-TDOA), round-trip-time (RTT), enhanced cell identity (E-CID), etc.). It is to be noted that while LPP techniques were first used in LTE, these LPP techniques are also used in NR.

[0131] Initially, the UE 504 may receive a request for its positioning capabilities from the LMF 570 at stage 510 (e.g., an LPP Request Capabilities message). At stage 520, the UE 504 provides its positioning capabilities to the LMF 570 relative to the LPP protocol by sending an LPP Provide Capabilities message to LMF 570 indicating the position methods and features of these position methods that are supported by the UE 504 usingLPP. The capabilities indicated in the LPP Provide Capabilities message may, in some aspects, indicate the type of positioning the UE 504 supports (e.g., DL-TDOA, RTT, E- CID, etc.) and may indicate the capabilities of the UE 504 to support those types of positioning.

[0132] Upon reception of the LPP Provide Capabilities message, at stage 520, the LMF 570 determines to use a particular type of positioning method (e.g., DL-TDOA, RTT, E-CID, etc.) based on the indicated type(s) of positioning the UE 504 supports and determines a set of one or more transmission-reception points (TRPs) from which the UE 504 is to measure downlink positioning reference signals or towards which the UE 504 is to transmit uplink positioning reference signals. At stage 530, the LMF 570 sends an LPP Provide Assistance Data message to the UE 504 identifying the set of TRPs.

[0133] In some implementations, the LPP Provide Assistance Data message at stage 530 may be sent by the LMF 570 to the UE 504 in response to an LPP Request Assistance Data message sent by the UE 504 to the LMF 570 (not shown in FIG. 5). An LPP Request Assistance Data message may include an identifier of the UE’s 504 serving TRP and a request for the positioning reference signal (PRS) configuration of neighboring TRPs.

[0134] At stage 540, the LMF 570 sends a request for location information to the UE 504. The request may be an LPP Request Location Information message. This message usually includes information elements defining the location information type, desired accuracy of the location estimate, and response time (i.e., desired latency). Note that a low latency requirement allows for a longer response time while a high latency requirement requires a shorter response time. However, a long response time is referred to as high latency and a short response time is referred to as low latency.

[0135] Note that in some implementations, the LPP Provide Assistance Data message sent at stage 530 may be sent after the LPP Request Location Information message at 540 if, for example, the UE 504 sends a request for assistance data to LMF 570 (e.g., in an LPP Request Assistance Data message, not shown in FIG. 5) after receiving the request for location information at stage 540.

[0136] At stage 550, the UE 504 utilizes the assistance information received at stage 530 and any additional data (e.g., a desired location accuracy or a maximum response time) received at stage 540 to perform positioning operations (e.g., measurements of DL-PRS, transmission of UL-PRS, etc.) for the selected positioning method.

[0137] At stage 560, the UE 504 may send an LPP Provide Location Information message to the LMF 570 conveying the results of any measurements that were obtained at stage 550 (e.g., time of arrival (ToA), reference signal time difference (RSTD), reception-to-transmission (Rx-Tx), etc.) and before or when any maximum response time has expired (e.g., a maximum response time provided by the LMF 570 at stage 540). The LPP Provide Location Information message at stage 560 may also include the time (or times) at which the positioning measurements were obtained and the identity of the TRP(s) from which the positioning measurements were obtained. Note that the time between the request for location information at 540 and the response at 560 is the “response time” and indicates the latency of the positioning session. It is to be noted that, in some examples (not shown in FIG. 5), the LPP Provide Location Information message may be sent by the serving gNB 502 when UL positioning methods are used.

[0138] The LMF 570 computes an estimated location of the UE 504 using the appropriate positioning techniques (e.g., DL-TDOA, RTT, E-CID, etc.) based, at least in part, on measurements received in the LPP Provide Location Information message at stage 560.

[0139] Various frame structures may be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). FIG. 6 is a diagram 600 illustrating an example frame structure, according to aspects of the disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communications technologies may have different frame structures and / or different channels.

[0140] 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. Unlike LTE, however, NR has an option to use OFDM on the uplink as well. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the spacing of the subcarriers may be 15 kilohertz (kHz) and the minimum resource allocation (resource block) may be 12 subcarriers (or 180 kHz). Consequently, the nominal fast Fourier transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048 for system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz(MHz), respectively. The system bandwidth may also be partitioned 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 system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0141] LTE supports a single numerology (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR may support multiple numerologies (p), for example, subcarrier spacings of 15 kHz (p=0), 30 kHz (p=l), 60 kHz (p=2), 120 kHz (p=3), and 240 kHz (p=4) or greater may be available. In each subcarrier spacing, there are 14 symbols per slot. For 15 kHz SCS (p=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 (ps), and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50. For 30 kHz SCS (p=l), there are two slots per subframe, 20 slots per frame, the slot duration is 0.5 ms, the symbol duration is 33.3 ps, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 100. For 60 kHz SCS (p=2), there are four slots per subframe, 40 slots per frame, the slot duration is 0.25 ms, the symbol duration is 16.7 ps, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 200. For 120 kHz SCS (p=3), there are eight slots per subframe, 80 slots per frame, the slot duration is 0.125 ms, the symbol duration is 8.33 ps, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 400. For 240 kHz SCS (p=4), there are 16 slots per subframe, 160 slots per frame, the slot duration is 0.0625 ms, the symbol duration is 4.17 ps, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 800.

[0142] In the example of FIG. 6, a numerology of 15 kHz is used. Thus, in the time domain, a 10 ms frame is divided into 10 equally sized subframes of 1 ms each, and each subframe includes one time slot. In FIG. 6, time is represented horizontally (on the X axis) with time increasing from left to right, while frequency is represented vertically (on the Y axis) with frequency increasing (or decreasing) from bottom to top.

[0143] A resource grid may be used to represent time slots, each time slot including 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 multiple resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In the numerology of FIG. 6, 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 RBmay 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.

[0144] Some of the REs may carry reference (pilot) signals (RS). The 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 (SSBs), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communication. FIG. 6 illustrates example locations of REs carrying a reference signal (labeled “R”).

[0145] FIG. 7 is a diagram 700 illustrating various downlink channels within an example downlink slot. In FIG. 7, time is represented horizontally (on the X axis) with time increasing from left to right, while frequency is represented vertically (on the Y axis) with frequency increasing (or decreasing) from bottom to top. In the example of FIG. 7, a numerology of 15 kHz is used. Thus, in the time domain, the illustrated slot is one millisecond (ms) in length, divided into 14 symbols.

[0146] In NR, the channel bandwidth, or system bandwidth, is divided into multiple bandwidth parts (BWPs). A BWP is a contiguous set of RBs selected from a contiguous subset of the common RBs for a given numerology on a given carrier. Generally, a maximum of four BWPs can be specified in the downlink and uplink. That is, a UE can be configured with up to four BWPs on the downlink, and up to four BWPs on the uplink. Only one BWP (uplink or downlink) may be active at a given time, meaning the UE may only receive or transmit over one BWP at a time. On the downlink, the bandwidth of each BWP should be equal to or greater than the bandwidth of the SSB, but it may or may not contain the SSB.

[0147] Referring to FIG. 7, a primary synchronization signal (PSS) is used by a UE to determine subframe / symbol timing and a physical layer identity. A secondary synchronization signal (SSS) is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a PCI. Based on the PCI, the UE can determine the locations of the aforementioned DL-RS. The physical broadcast channel (PBCH), whichcarries a master information block (MIB), may be logically grouped with the PSS and SSS to form an SSB (also referred to as an SS / PBCH). The MIB provides a number of RBs in the downlink system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH, such as system information blocks (SIBs), and paging messages.

[0148] The physical downlink control channel (PDCCH) carries downlink control information (DCI) within one or more control channel elements (CCEs), each CCE including one or more RE group (REG) bundles (which may span multiple symbols in the time domain), each REG bundle including one or more REGs, each REG corresponding to 12 resource elements (one resource block) in the frequency domain and one OFDM symbol in the time domain. The set of physical resources used to carry the PDCCH / DCI is referred to in NR as the control resource set (CORESET). In NR, a PDCCH is confined to a single CORESET and is transmitted with its own DMRS. This enables UE-specific beamforming for the PDCCH.

[0149] In the example of FIG. 7, there is one CORESET per BWP, and the CORESET spans three symbols (although it may be only one or two symbols) in the time domain. Unlike LTE control channels, which occupy the entire system bandwidth, in NR, PDCCH channels are localized to a specific region in the frequency domain (i.e., a CORESET). Thus, the frequency component of the PDCCH shown in FIG. 7 is illustrated as less than a single BWP in the frequency domain. Note that although the illustrated CORESET is contiguous in the frequency domain, it need not be. In addition, the CORESET may span less than three symbols in the time domain.

[0150] The DCI within the PDCCH carries information about uplink resource allocation (persistent and non-persistent) and descriptions about downlink data transmitted to the UE, referred to as uplink and downlink grants, respectively. More specifically, the DCI indicates the resources scheduled for the downlink data channel (e.g., PDSCH) and the uplink data channel (e.g., physical uplink shared channel (PUSCH)). Multiple (e.g., up to eight) DCIs can be configured in the PDCCH, and these DCIs can have one of multiple formats. For example, there are different DCI formats for uplink scheduling, for downlink scheduling, for uplink transmit power control (TPC), etc. A PDCCH may be transportedby 1, 2, 4, 8, or 16 CCEs in order to accommodate different DCI payload sizes or coding rates.

[0151] FIG. 8 is a diagram 800 illustrating various uplink channels within an example uplink slot. In FIG. 8, time is represented horizontally (on the X axis) with time increasing from left to right, while frequency is represented vertically (on the Y axis) with frequency increasing (or decreasing) from bottom to top. In the example of FIG. 8, a numerology of 15 kHz is used. Thus, in the time domain, the illustrated slot is one millisecond (ms) in length, divided into 14 symbols.

[0152] A random-access channel (RACH), also referred to as a physical random-access channel (PRACH), may be within one or more slots within a frame based on the PRACH configuration. The PRACH may include six consecutive RB pairs within a slot. The PRACH allows the UE to perform initial system access and achieve uplink synchronization. A physical uplink control channel (PUCCH) may be located on edges of the uplink system bandwidth. The PUCCH carries uplink control information (UCI), such as scheduling requests, CSI reports, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and HARQ ACK / NACK feedback. The physical uplink shared channel (PUSCH) carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0153] FIG. 9 is a diagram of an example PRS configuration 900 for the PRS transmissions of a given base station, according to aspects of the disclosure. In FIG. 9, time is represented horizontally, increasing from left to right. Each long rectangle represents a slot and each short (shaded) rectangle represents an OFDM symbol. In the example of FIG. 9, a PRS resource set 910 (labeled “PRS resource set 1”) includes two PRS resources, a first PRS resource 912 (labeled “PRS resource 1”) and a second PRS resource 914 (labeled “PRS resource 2”). The base station transmits PRS on the PRS resources 912 and 914 of the PRS resource set 910.

[0154] The PRS resource set 910 has an occasion length (N PRS) of two slots and a periodicity (T PRS) of, for example, 160 slots or 160 milliseconds (ms) (for 15 kHz subcarrier spacing). As such, both the PRS resources 912 and 914 are two consecutive slots in length and repeat every T PRS slots, starting from the slot in which the first symbol of the respective PRS resource occurs. In the example of FIG. 9, the PRS resource 912 has a symbol length (N symb) of two symbols, and the PRS resource 914 has a symbol length(N_symb) of four symbols. The PRS resource 912 and the PRS resource 914 may be transmitted on separate beams of the same base station.

[0155] Each instance of the PRS resource set 910, illustrated as instances 920a, 920b, and 920c, includes an occasion of length ‘2’ (i.e., N_PRS=2) for each PRS resource 912, 914 of the PRS resource set. The PRS resources 912 and 914 are repeated every T PRS slots up to the muting sequence periodicity T REP. In some cases, a bitmap of length T REP may be used to indicate which occasions of instances 920a, 920b, 920c, and any others (not shown) of PRS resource set 910 are muted (i.e., not transmitted).

[0156] In an aspect, there may be additional constraints on the PRS configuration 900. For example, for all PRS resources (e.g., PRS resources 912, 914) of a PRS resource set (e.g., PRS resource set 910), the base station can configure the following parameters to be the same: (a) the occasion length (N_PRS), (b) the number of symbols (N_symb), (c) the comb type, and / or (d) the bandwidth. In addition, for all PRS resources of all PRS resource sets, the subcarrier spacing and the cyclic prefix can be configured to be the same for one base station or for all base stations. Whether it is for one base station or all base stations may depend on the UE’s capability to support the first and / or second option.

[0157] FIGS. 10A and 10B illustrate various comb patterns supported for DL-PRS within a resource block. In FIGS. 10A and 10B, time is represented horizontally, and frequency is represented vertically. Each large block in FIGS. 10A and 10B represents a resource block and each small block represents a resource element. As discussed above, a resource element consists of one symbol in the time domain and one subcarrier in the frequency domain. In the example of FIGS. 10A and 10B, each resource block comprises 14 symbols in the time domain and 12 subcarriers in the frequency domain. The shaded resource elements carry, or are scheduled to carry, DL-PRS. As such, the shaded resource elements in each resource block correspond to a PRS resource, or the portion of the PRS resource within one resource block (since a PRS resource can span multiple resource blocks in the frequency domain).

[0158] The illustrated comb patterns correspond to various DL-PRS comb patterns described above. Specifically, FIG. 10A illustrates a DL-PRS comb pattern 1010 for comb-2 with two symbols, a DL-PRS comb pattern 1020 for comb-4 with four symbols, a DL-PRS comb pattern 1030 for comb-6 with six symbols, and a DL-PRS comb pattern 1040 for comb-12 with 12 symbols. FIG. 10B illustrates a DL-PRS comb pattern 1050 for comb-2 with 12 symbols, a DL-PRS comb pattern 1060 for comb-4 with 12 symbols, a DL-PRS comb pattern 1070 for comb-2 with six symbols, and a DL-PRS comb pattern 1080 for comb-6 with 12 symbols.

[0159] Note that in the example comb patterns of FIG. 10 A, the resource elements on which the DL-PRS are transmitted are staggered in the frequency domain such that there is only one such resource element per subcarrier over the configured number of symbols. For example, for DL-PRS comb pattern 1020, there is only one resource element per subcarrier over the four symbols. This is referred to as “frequency domain staggering.”

[0160] Further, there is some DL-PRS resource symbol offset (given by the parameter “DL-PRS- ResourceSymbolOffsef ’) from the first symbol of a resource block to the first symbol of the DL-PRS resource. In the example of DL-PRS comb pattern 1010, the offset is three symbols. In the example of DL-PRS comb pattern 1020, the offset is eight symbols. In the examples of DL-PRS comb patterns 1030 and 1040, the offset is two symbols. In the examples of DL-PRS comb pattern 1050 to 1080, the offset is two symbols.

[0161] As will be appreciated, a UE would need to have higher capabilities to measure the DL- PRS comb pattern 1010 than to measure the DL-PRS comb pattern 1020, as the UE would have to measure resource elements on twice as many subcarriers per symbol for DL-PRS comb pattern 1010 as for DL-PRS comb pattern 1020. In addition, a UE would need to have higher capabilities to measure the DL-PRS comb pattern 1030 than to measure the DL-PRS comb pattern 1040, as the UE will have to measure resource elements on twice as many subcarriers per symbol for DL-PRS comb pattern 1030 as for DL-PRS comb pattern 1040. Further, the UE would need to have higher capabilities to measure the DL- PRS comb patterns 1010 and 1020 than to measure the DL-PRS comb patterns 1030 and 1040, as the resource elements of DL-PRS comb patterns 1010 and 1020 are denser than the resource elements of DL-PRS comb patterns 1030 and 1040.

[0162] Aspects of the disclosure relate to techniques for perception assistance of a device using positioning and assistance data. That is, for example, a UE may receive perception assistance in the form of an RF-based positioning configuration from a network entity. Additionally, or alternatively, the UE may receive perception assistance in the form of assistance data from the network entity, which may include perception-based positioning- related information that the network entity receives from other UEs (e.g., other UEs involved in a same interactive application as the UE receiving the assistance data).

[0163] FIG. 11 illustrates an example wireless communications system 1100 that supports techniques for perception assistance using positioning and assistance data, according to aspects of the disclosure. In certain aspects, the wireless communication system 1100 may be an example of, or include features of, the corresponding or similar elements described with reference to FIGS. 1-10B, as well as other features described herein. The wireless communication system 1100 may include one or more base stations, such as base station 1102 (e.g., gNBs 222, ng-eNBs 224, base station 302, or other network entities in the NG-RAN 220 described herein) and one or more UEs, such as first UE 1104a and second UE 1104b (e.g., UE 204, UE 304, or other network devices in the NG-RAN 220 described herein).

[0164] The wireless communication system 1100 may also include one or more network elements, such as network element 1106 (e.g., LMF 270, SLP 272, third-party server 274, SMF 266, network entity 306, and / or any other network entity, LMF, or location-based server described herein). In some examples, the first UE 1104a and the second UE 1104b may be involved in one or more interactive applications. As noted in the example of FIG. 11, the first UE 1104a and the second UE 1104b may be configured with and running an XR or metaverse-based interactive application. Additionally, or alternatively, the network entity 1106 may be configured with and running an XR or metaverse-based interactive application. It is to be understood that other interactive applications and / or enhanced services may be configured and running on the first UE 1104a, the second UE 1104b, and / or the network entity 1106 that may benefit from the techniques for perception assistance using positioning and assistance data described herein.

[0165] In some examples, the interactive application and / or enhanced service of the first UE 1104a, the second UE 1104b, and / or the network entity 1106 may provide immersive experiences in various areas, such as but not limited to gaming, socializing, healthcare, industry, transportation, etc. In some cases, the wireless communication 1100 is configured to support enhanced services involving interactive media sharing (e.g., enhanced XR-based services) among multiple users (e.g., the first UE 1104a and / or the second UE 1104b) in a single location. In order to support enhanced services associated with these interactive applications, the first UE 1104a and / or the second UE 1104b in the wireless communication system 1100 may be configured to adhere to multiple KPIs corresponding to various aspects or characteristics of these enhanced services of theinteractive application. In some examples, the network entity 1106 may alternatively, or additionally, manage the multiple KPIs.

[0166] For example, some KPIs may correspond to latency, throughput, connection density of the wireless communication system 1100 and devices therein. Some KPIs correspond to acquiring local spatial / environmental information and user information from the first UE 1104a and / or the second UE 1104b. In some cases, the KPIs may correspond to 6DoF parameters and / or related parameters including, but not limited to, viewing angle, position, and orientation. Additionally, some KPIs may correspond to providing or exposing local acquired spatial, environmental, and user / UE-based information to third party networks or systems, for example, to further enhance the interactive or immersive experience.

[0167] For example, Table 1 below shows example six-dimensional (6D) localization KPI requirements for context aware services.Table 1

[0168] Additionally, Table 2 below shows example 6D localization KPI requirements for context aware services when placing virtual objects in real world environments.Table 2

[0169] The 6D localization KPI requirements provided in Table 1 and Table 2 are examples of metrics that include high accuracy and / or low latency of operations involving the first UE 1104a and / or the second UE 1104b. In some cases, one or more of these 6D localization KPI requirements may correspond to the 6DoF parameters associated with the first UE1104a and / or the second UE 1104b. Meeting these and other KPI requirements may depend on various factors associated with the first UE 1104a and / or the second UE 1104b, such as a device state (e.g., regular state, boot up, etc.), a type of sensor (and a corresponding quality of the sensor) that the first UE 1104a and / or the second UE 1104b will use in perception-based operations (e.g., a camera, an inertial measurement unit (IMU) sensor, etc.). For example, if the first UE 1104a is equipped with one or more high quality cameras and IMU sensors, the first UE 1104a may be capable of achieving KPI metrics associated with one or more DoF requirements without assistance from the network entity 1106 (e.g., NR positioning configurations) in the wireless communication system 1100.

[0170] In some cases, the device state of the first UE 1104a and / or the second UE 1104b as well as certain available sensors (and a corresponding quality for these available sensors) of the first UE 1104a and / or the second UE 1104b may not be sufficient to meet the KPI metrics associated with one or more DoF parameters. That is, for example, the first UE 1104a may be in a device state that does not allow for meeting the KPI metrics associated with one or more DoF parameters. In some cases, the first UE 1104a may be in an initialization state where first UE 1104a begins tracking functions or starts a boot-up process. In some cases, the first UE 1104a may be operating in a restricted mode (e.g., an airplane mode, a low power mode, etc.).

[0171] Additionally, even when the device state of the first UE 1104a and / or the second UE 1104b is a regular or normal operating state, certain conditions may exist that do not allow for meeting the KPI metrics associated with one or more DoF parameters. For example, a high-quality camera may be blocked, and a physical object may be occluded in the environment. In some cases, the first UE 1104a and / or the second UE 1104b may be in a room or environment that has poor lighting and / or insufficient number of physical features for performing perception-based operations. In some cases, the first UE 1104a and / or the second UE 1104b may be designed with low-quality camera and / or IMU sensors that are insufficient for meeting the KPI metrics associated with one or more DoF parameters.

[0172] To assist with meeting the KPI metrics associated with one or more DoF parameters in various scenarios and / or for various designs of the first UE 1104a and / or the second UE 1104b, the first UE 1104a and / or the second UE 1104b may be configured with RF-basedpositioning configurations from the network entity 1106. In some examples, an application, such as an interactive application (e.g., an XR or metaverse-based application) running on the first UE 1104a, the second UE 1104b, and / or the network entity 1106 may request that one of both of the first UE 1104a and the second UE 1104b be configured with an RF -based positioning configuration. In some examples, the RF- based positioning configuration may include an allocation of resources in the time and frequency domains for the transmission of reference signals. This allocation of resources may be otherwise assignable for data transmission purposes and / or for allocation to other UEs. In some examples, the RF-based positioning configuration may be an NR positioning configuration.

[0173] For example, the wireless communication system 1100 may be configured to assist an XR or metaverse-based interactive application running on the first UE 1104a and / or the second UE 1104b. In some examples, the first UE 1104a and / or the second UE 1104b may transmit perception-based positioning-related information to the network entity 1106. As described herein, perception-based positioning-related information may include various information obtained via multiple sources of the first UE 1104a or the second UE 1104b, such as but not limited to one or more sensors of the first UE 1104a or the second UE 1104b. This information may include positioning and / or orientation information derived from these various sensors.

[0174] Non-limiting examples of perception-based positioning-related information include data associated with camera frames of a camera device (e.g., an RGB camera, an infrared camera, etc.) of the first UE 1104a or the second UE 1104b, data associated with an IMU sensor (e.g., accelerometer, gyroscope, etc.) of the first UE 1104a or the second UE 1104b, a resolution of the one or more perception-based components (e.g., the camera device and / or the IMU sensor), a rate of the one or more perception-based components (e.g., the camera device and / or the IMU sensor). In some cases, the perception-based positioning-related information may be comprised of raw data from these perceptionbased components. In some cases, the perception-based positioning-related information may include measurements and / or determinations made by the first UE 1104a or the second UE 1104b based on these perception-based components. The perception-based positioning-related information may include any combination of raw data from perception-based components of the UE as well as measurements and / or determinationsmade by the first UE 1104a or the second UE 1104b based on these perception -based components.

[0175] In some examples, the perception-based positioning-related information transmitted by the first UE 1104a and / or the second UE 1104b may include information associated with a metric corresponding to one or more DoF parameters. In some cases, the metric may correspond to a KPI metric and / or QoS metric associated with one or more DoF parameters of the 6DoF parameters. That is, for example, the first UE 1104a and / or the second UE 1104b may request assistance from the network entity 1106 in order to enhance a 6DoF estimation corresponding to the metric by using RF -based positioning techniques.

[0176] In some examples, the network entity 1106 may assist the XR or metaverse-based interactive application running on the first UE 1104a and / or the second UE 1104b. That is, for example, the network entity 1106 may analyze the perception-based positioning- related information and determine whether to assist the XR or metaverse-based interactive application running on the first UE 1104a and / or the second UE 1104b in satisfying the metric associated with the one or more DoF parameters. If the network entity 1106 determines to assist the XR or metaverse-based interactive application, the network entity 1106 may provide an RF-based positioning configuration to the first UE 1104a and / or the second UE 1104b.

[0177] If the network entity 1106 determines not to assist the XR or metaverse-based interactive application (e.g., determining that an RF-based positioning configuration would not advance or satisfy the metric associated with the one or more DoF parameters), the network entity 1106 may refrain from configuring the first UE 1104a and / or the second UE 1104b with RF-based positioning resources. In some cases, these time and frequency resources may be allocated for data transmission purposes for the first UE 1104a and / or the second UE 1104b.

[0178] In some examples, the RF-based positioning configurations may include LTE and / or NR positioning configurations, and various reporting and configuration aspects associated with LTE and / or NR positioning may be used with respect to the wireless communication network 1100. That is, for example, multiple positioning techniques used by devices in the wireless communication network 1100 may include E-CID, DL-TDOA, UL-TDOA, multi-RTT, UL-AOA, and DL-AOD techniques. In some cases, enhancements to thesemultiple positioning techniques may enable horizontal and vertical positioning accuracies of less than one meter and three meters, respectively, for 90% of the UEs in the wireless communication network 1100 within a 100-millisecond end-to-end latency requirement.

[0179] In some examples, the RF-based positioning configurations may include always-on DL- PRS resources. In some examples, the RF-based positioning configurations may include on-demand DL-PRS resources. In some cases, the RF-based positioning configurations that include on-demand DL-PRS resources may include a capability to allow the first UE 1104a, the second UE 1104b, and / or the network entity 1106 to request the DL-PRS resources for positioning measurements or a modification associated with the available DL-PRS resources.

[0180] In some aspects, the first UE 1104a and / or the second UE 1104b may request specific beams that are mapped to a degradation corresponding to one or more particular orientation parameters or characteristics (e.g., pitch, yaw, and / or roll). For example, an application (e.g., an XR or metaverse-based interactive application) may be running on the first UE 1104a. The application may estimate and track the 6DoF parameters of the first UE 1104a such that the application can determine the quality and corresponding metrics associated with the 6DoF parameters. Accordingly, the first UE 1104a may initiate an on-demand PRS (e.g., DL-PRS or UL-SRS) procedure with the network entity 1106. In some cases, the on-demand PRS procedure may relate to improving one or more DoF parameters of the 6DoF parameters.

[0181] That is, for example, the application may trigger the on-demand PRS procedure based on a metric corresponding to the one or more DoF parameters when a threshold associated with the metric is not satisfied. In some cases, the metric may correspond to an orientation accuracy in which one or more of the pitch, yaw, and roll is greater than 1 degree. In some cases, the metric may correspond to a location accuracy in which the linear position, horizontal straightness, and vertical straightness is greater than 0.5 centimeters. In some examples, the application may apply a transformation process to translate and / or rotate a 6DoF coordinate system to a coordinate system of the TRP(s) and / or or the NG-RAN device(s). For example, the application may perform a transformation for position in a 3D coordinate system (e.g., X, Y, and Z) of the TRP(s) and / or or the NG-RAN device(s) into the 6DoF coordinate system to determine the 6DoF parameters associated with for position / location accuracy and / or orientation / rotation accuracy.

[0182] In some examples, an application (e.g., an interactive application) may communicate with a modem of the first UE 1104a through a cross-layer application programming interface (API). In some cases, the cross-layer API may be designed to efficiently pass data through multiple protocol layers (e.g., one or more of a service data adaptation protocol (SDAP), packet data convergence protocol (PDCP), radio link control (RLC), medium access control (MAC), or physical layer (PHY)). That is, for example, the cross-layer API may be designed to pass data from an application running on the first UE 1104a to the modem of the first UE 1104a, such that the data is efficiently passed through one or more protocol layer entities therebetween. In some cases, however, the cross-layer API may be designed to efficiently pass data through multiple protocol layers from an application running on a server to the modem of the first UE 1104a through one or more NG-RAN elements and to the 5GC element (e.g., network entity 1106) and / or an edge cloud server or application. In some cases, the cross-layer API may be designed to optimize support of fully immersive and low latency applications. In some examples, the application may communicate perception-based positioning-related information through the cross-layer API. The perception-based positioning-related information may include, for example, the metric corresponding to the one or more DoF parameters for which the threshold associated with the metric was not satisfied. In some cases, the perception-based positioning-related information communicated through the cross-layer API may correspond to a drop in quality of the position / location KPI metrics, a drop in quality of the orientation / rotation orientation KPI metrics, or both.

[0183] In some examples, the perception-based positioning-related information communicated through the cross-layer API may include information indicating which dimension or DoF parameter has dropped. For example, the perception-based positioning-related information may indicate that a KPI metric corresponding to a particular DoF orientation parameter has not been satisfied. In some examples, when a DoF orientation parameter has dropped, the network entity 1106 may respond with updated QCL information for the first UE 1104a. In some examples, when a DoF orientation parameter has dropped, the first UE 1104a may request PRS resources quasi-collocated (QCL-ed) to specific beam(s) based on the DoF orientation parameter from network entity 1106.

[0184] As illustrated in the example of FIG. 11, the base station 1102 may transmit signals via transmit beams 1112 (e.g., using beamforming techniques) towards the first UE 1104aand the second UE 1104b. The first UE 1104a and the second UE 1104b may receive the transmitted signals via receive beams 1114 (e.g., using beamforming techniques). The beamforming between the base station 1102 and each of the first UE 1104a and the second UE 1104b may include a number of beams. For example, six beams (e.g., Beam 1, Beam 2, Beam 3, Beam 4, Beam 5, and Beam 6) may be formed for the transmit beams 1112 and the receive beams 1114 between the base station 1102 and the first UE 1104a.

[0185] In some cases, when the first UE 1104a determines that the “roll” DoF orientation parameter has dropped, the perception-based positioning-related information may indicate for the network entity 1106 to configure DL-PRS signal resources QCL-ed with Beam 1 and Beam 2 for transmission by the base station 1102. In some cases, when the first UE 1104a determines that the “pitch” DoF orientation parameter has dropped, the perception-based positioning-related information may indicate for the network entity 1106 to configure DL-PRS signal resources QCL-ed with Beam 3 and Beam 4 for transmission by the base station 1102. In some cases, when the first UE 1104a determines that the “yaw” DoF orientation parameter has dropped, the perception-based positioning- related information may indicate for the network entity 1106 to configure DL-PRS signal resources QCL-ed with Beam 5 and Beam 6 for transmission by the base station 1102.

[0186] In some examples, the first UE 1104a may transmit perception -based positioning-related information as part of an on-demand PRS (e.g., DL-PRS and / or UL-SRS) procedure with the network entity 1106. In some cases, the first UE 1104a may initiate (e.g., UE-initiated) the on-demand PRS procedure with the network entity 1106. In some cases, the network entity 1106 may initiate (e.g., network-initiated) the on-demand PRS procedure with the first UE 1104a. Aspects of these on-demand PRS procedures are further described herein.

[0187] In some aspects, the first UE 1104a and / or the second UE 1104b may transmit the perception-based positioning-related information as assistance information to the network entity 1106. In some examples, the assistance information may relate to a degradation corresponding to one or more particular orientation parameters or characteristics (e.g., pitch, yaw, and / or roll). For example, an application (e.g., an XR or metaverse-based interactive application) may be running on the second UE 1104b. The application may estimate and track the 6DoF parameters of the second UE 1104b such that the application can determine the quality and corresponding metrics associated with the 6DoF parameters.

[0188] In some examples, the network entity 1106 may initiate an on-demand PRS (e.g., DL- PRS or UL-SRS) procedure with the second UE 1104b. In some cases, the on-demand PRS procedure may be triggered by information from an application (e.g., an XR or metaverse-based interactive application) running on the network entity 1106. In some cases, the on-demand PRS procedure may be triggered by information from an application (e.g., an XR or metaverse-based interactive application) running on the first UE 1104a that communicates to the network entity 1106 to initiate the on-demand PRS procedure with the second UE 1104b. The second UE 1104b may transmit UE assistance information to the network entity 1106 related to one or more DoF parameters of the 6DoF parameters during the on-demand PRS procedure. In some cases, the on-demand PRS procedure may relate to improving the one or more DoF parameters of the 6DoF parameters. A subsequent PRS positioning configuration resulting from the on-demand PRS procedure may be based on the UE assistance information.

[0189] That is, for example, the perception-based positioning-related information from the first UE 1104a and / or the second UE 1104b may be transmitted as UE assistance information through LPP signaling or other signaling to the base station 1102 and / or the network entity 1106. In some examples, a specific reason for the drop in a KPI metric may be provided as UE assistance data, which may indicate to the network entity 1106 where assistance is needed with respect to one or more DoF parameters or otherwise.

[0190] In some examples, when MIMO beamforming has been established between the first UE 1104a and the base station 1102, the network entity 1106 may use the beamforming configuration to precisely configure DL-PRS resources for various DoF parameters associated with the first UE 1104a. For example, when the first UE 1104a transmits perception-based positioning-related UE assistance information indicating that the “roll” DoF orientation parameter has dropped, the network entity 1106 may configure DL-PRS signal resources QCL-ed with Beam 1 and Beam 2 for transmission by the base station 1102. When the first UE 1104a transmits perception-based positioning-related UE assistance information indicating that the “pitch” DoF orientation parameter has dropped, the network entity 1106 may configure DL-PRS signal resources QCL-ed with Beam 3 and Beam 4 for transmission by the base station 1102. When the first UE 1104a transmits perception-based positioning-related UE assistance information indicating that the “yaw” DoF orientation parameter has dropped, the network entity 1106 may configure DL-PRSsignal resources QCL-ed with Beam 5 and Beam 6 for transmission by the base station 1102.

[0191] In some examples, the network entity 1106 may determine a beamforming configuration to precisely configure DL-PRS resources for various DoF parameters associated with the second UE 1104b. For example, when the second UE 1104b transmits perception-based positioning-related UE assistance information indicating that one or more DoF positioning parameters has dropped (e.g., the “horizontal straightness” or “X” DoF positioning parameter, the “vertical straightness” or “ Y” DoF positioning parameter, etc.), the network entity 1106 may configure DL-PRS signal resources on beams for transmission by the base station 1102 that are optimized for determining the one or more DoF positioning parameters.

[0192] In some examples, the UE assistance information transmitted from the UE 1104a and / or the second UE 1104b may be associated with other perception-related information. For example, the second UE 1104b may transmit UE-assistance information related to the power consumption experienced or a communication latency experienced by the second UE 1104b. In some cases, the power consumption information may be translated by the network entity 1106 into a bandwidth that may be configured for the second UE 1104b. In some cases, this bandwidth may be included in a subsequent PRS positioning configuration provided by network entity 1106 to the second UE 1104b.

[0193] In some examples, the network entity 1106 may prioritize PRS resources based on perception-based positioning-related information. For example, when the first UE 1104a and / or the second UE 1104b transmits perception-based positioning-related information (e.g., whether as UE assistance information or otherwise), the network entity 1106 may prioritize a set of PRS resources over another set of PRS resources based on this perception-based positioning-related information.

[0194] In some examples, the first UE 1104a may transmit perception -based positioning-related information associated with a KPI metric corresponding to one or more DoF parameters to the network entity 1106. In some cases, the perception-based positioning-related information may include an implicit or explicit request to enhance the KPI metric associated with the one or more DoF parameters. The network entity 1006 may utilize this perception-based positioning-related information for determining one or more resource sets for an RF -based positioning configuration (e.g., PRS resource sets for a DL-PRS configuration) and / or a prioritization of the one or more resource sets (e.g., prioritize PRS resource set 1 over PRS resource set 2) for a particular positioning session associated with the RF -based positioning configuration.

[0195] For example, when the first UE 1104a transmits perception-based positioning-related information indicating that a KPI metric for the “horizontal straightness” or “X” DoF positioning parameter has dropped and / or may be enhanced by RF-based positioning techniques, the network entity may schedule a positioning session in which PRS resource set 1 is prioritized over PRS resource set 2. By contrast, when the first UE 1104a transmits perception-based positioning-related information indicating that a KPI metric for the “roll” DoF orientation parameter has dropped and / or may be enhanced by RF-based positioning techniques, the network entity may schedule a positioning session in which PRS resource set 2 is prioritized over PRS resource set 1. That is, based on one or more characteristics of the resource set (e.g., DL-PRS comb pattern, frequency range, etc.), the network entity 1106 may prioritize the resource sets in a positioning session for enhancing the particular KPI metric associated with the one or more DoF parameters.

[0196] In some examples, an application (e.g., an XR or metaverse-based interactive application) running on the network entity 1106 may request the reprioritization of the resource sets in an RF-based positioning configuration for the first UE 1104a and / or the second UE 1104b. In some examples, the first UE 1104a and / or the second UE 1104b may determine the reprioritization of the resource sets in an RF-based positioning configuration based on the KPI metric corresponding to one or more DoF parameters.

[0197] In some examples, SRS enhancements relating to KPI metrics corresponding to one or more DoF parameters may be performed in the wireless communication network 1100. That is, for example, the network entity 1106 may indicate one or more DoF parameters to the base station 1102. For example, the network entity 1106 may indicate to the base station 1102 that a KPI metric for the “yaw” DoF orientation parameter has dropped. The base station 1102 may be capable of configuring and updating a PRS (e.g., UL-SRS) positioning configuration, as well as performing an UL-SRS positioning session to be optimized based on the particular DoF orientation parameter.

[0198] In some examples, the network entity 1106 may transmit the information associated with the KPI metric to the base station 1102 in the form of a NRPPa positioning information request. That is, for example, the NRPPa positioning information request transmittedfrom the network entity 1106 in a PRS (e.g., DL-PRS and / or UL-SRS) procedure may include perception-based positioning-related information associated with one or more DoF parameters. This perception-based positioning-related information included in the NRPPa positioning information request may be used by the base station 1102 to influence the PRS (e.g., UL-SRS) positioning configuration and / or how an UL-SRS positioning session is performed between the base station 1102 and the first UE 1104a and / or the second UE 1104b.

[0199] In some examples, the first UE 1104a and / or the second UE 1104b may be configured to perform positioning measurements for a positioning session corresponding to one or more DoF parameters during a measurement gap. Measurement gaps may be defined as periods that the UE may use to perform measurements. That is, rather than performing these positioning measurements during a positioning processing window (PPW), the positioning measurements corresponding to one or more DoF parameters are configured to be performed during a measurement gap.

[0200] In certain situations, using a PPW may provide benefits for traditional positioning sessions. For example, a PPW may minimize communications interruptions that may occur due to positioning requirements. In a PPW, a UE may not change an operating BWP while performing a positioning session but may process the positioning signals of the positioning session in the current operating BWP. However, using a PPW may restrict a number of transmit / receive chains that can be used for a positioning session. In some designs, for example, even if a UE has four antennas, typically only two antennas can be used for the positioning session.

[0201] For 6DoF operations, a high number of transmit / receive chains may aid in angle estimation, which can be beneficial for determining DoF orientation parameters. For example, some AoD measurements at the UE side may require phase measurements across multiple antennas. Accordingly, in some examples, the first UE 1104a and / or the second UE 1104b utilizes measurement gaps for positioning sessions corresponding to the one or more DoF parameters so that the UE may utilize more hardware and / or computational resources when performing positioning measurements. By contrast, while a PPW may minimize communications interruptions, the PPW process may not allow for the utilization of sufficient hardware and / or computational resources desired for 6DoF operations, in accordance with some aspects.

[0202] In some aspects, a measurement gap during which the first UE 1104a and / or the second UE 1104b may perform positioning measurements for a positioning session corresponding to one or more DoF parameters has one or more different parameters or characteristics as compared to measurement gaps for conventional location-related positioning procedures. That is, the processing associated with 6DoF positioning and orientation operations may be more demanding of hardware and computational resources than legacy 2D or 3D location-related positioning operations. For example, positioning- related resource signals used in positioning sessions corresponding to 6DoF positioning and orientation operations may involve multi-port transmissions as compared to singleport transmissions for legacy 2D or 3D location-related positioning operations.

[0203] In some cases, a measurement gap configuration associated with 6DoF positioning and orientation operations may have a measurement gap length greater than the measurement gap length (e.g., an nr-MeasPRS-length field of the IE LocationMeasurementlnfo) for location-related NR DL-PRS measurements associated with 2D or 3D location-related positioning operations. In some cases, a measurement gap configuration associated with 6DoF positioning and orientation operations may have a gap offset with a greater number of subframes than the gap offset (e.g., an nr-MeasPRS-RepetitionAndOffset field of the IE LocationMeasurementlnfo) for location-related NR DL-PRS measurements associated with 2D or 3D location-related positioning operations. In some cases, a measurement gap configuration associated with 6DoF positioning and orientation operations may have a gap periodicity with a greater frequency than the gap periodicity (e.g., an nr-MeasPRS- RepetitionAndOffset field of the IE LocationMeasurementlnfo) for location-related NR DL-PRS measurements associated with 2D or 3D location-related positioning operations.

[0204] It is to be appreciated that the aspects and examples described with respect to the wireless communication system 1100 may be applied to various contexts. In some designs, the first UE 1104a and / or the second UE 1104b may be considered or classified as perception entities by the network. That is, for example, the first UE 1104a and / or the second UE 1104b may be capable of perception-based positioning. In some cases, the first UE 1104a and / or the second UE 1104b may report the perception-based positioning capability via a capabilities message. In some cases, the capability message may be transmitted by the first UE 1104a and / or the second UE 1104b responsive to the capability request from the network (e.g., the network entity 1106). In some cases, the first UE 1104a and / or thesecond UE 1104b may transmit the capabilities message on its own volition absent any request from the network. In some cases, the network entity 1106 may store information related to the perception-based positioning capability of the first UE 1104a and / or the second UE 1104b as a configuration. The configuration may be associated with one or more aspects of the 6DoF parameters and may be used at a later time, for example, when a particular 6DoF parameter needs to be improved using PRS or SRS resources.

[0205] In some examples, the first UE 1104a and / or the second UE 1104b may be running an application corresponding to smart transport. The first UE 1104a and / or the second UE 1104b may utilize real-time information and data delivery for traffic participants including, but not limited to pedestrians, bicycle riders, and vehicles with or without autonomous driving mode. In some cases, physical objects may include road infrastructure and vehicles including, but not limited to cars and trucks in each lane. The physical objects may have a corresponding digital counterpart in the virtual world. In some examples, the virtual objects and physical objects may form a mobile metaverse scenario.

[0206] In some examples, the first UE 1104a and / or the second UE 1104b may be running an application corresponding to a collaborative and concurrent engineering scenario. This scenario may include a distributed virtual environment (DVE) allowing multiple users from different geographical locations to interact over a network. Some of the users, for example, a first user with the first UE 1104a and a second user with the second UE 1104b may be present at the same location. The DVE may include multi-user virtual reality aspects that actively support communication, collaboration, and coordination.

[0207] FIG. 12 illustrates an example scenario 1200 using techniques for perception assistance using positioning and assistance data, according to aspects of the disclosure. In certain aspects, scenario 1200 may be operative in the wireless communication system 1100 and may be an example of, or include features of, the corresponding or similar elements described with reference to FIGS. 1-11, as well as other features described herein. Scenario 1200 may include one or more UEs, such as a first UE 1204a and a second UE 1204b (e.g., UE 204, UE 304, first UE 1204a, second UE 1204b, or other network devices in the NG-RAN 220 described herein).

[0208] Scenario 1200 is a non-limiting example of a coffee shop that uses spatial anchors to access virtual information related to physical objects. A first user wearing the first UE1204a may enter the coffee shop and examine what is on display. For example, a first physical object 1216a (e.g., a first painting on a wall), a second physical object 1216b (e.g., a second painting on the wall), a third physical object 1216c (e.g., a first coffee bean cannister on a display stand), a fourth physical object 1216d (e.g., a second coffee bean cannister on the display stand), and a fifth physical object 1216e (e.g., a third coffee bean cannister on a display stand) may be observed by the first user wearing the first UE 1204a.

[0209] The first user wearing the first UE 1204a may capture the scene at the coffee shop with sensors and share this information with a network entity (e.g., an LMF with spatial mapping and localization service functionality) in a wireless communication network (e.g., a 5G system). This initial capture by the first user wearing the first UE 1204a may allow precise identification of localization information, including positioning and orientation information. In some cases, the network entity in the wireless communication network may use the localization information to identify one or more spatial anchors in the area of interest in the coffee shop. In some cases, a spatial anchor may include information that can be provided by a content producer to a content consumer.

[0210] For example, the network entity may identify a first spatial anchor 1218a corresponding to the first physical object 1216a, a second spatial anchor 1218b corresponding to the second physical object 1216b, a third spatial anchor 1218c corresponding to the third physical object 1216c, a fourth spatial anchor 1218d corresponding to the fourth physical object 1216d, and a fifth spatial anchor 1218e corresponding to the fifth physical object 1216e. The network entity may provide the spatial anchors to the first UE 1204a. Additionally, a second user wearing the second UE 1204b may be present in the store, and the network entity may provide the spatial anchors to the second UE 1204b.

[0211] In some examples, content may be displayed to the first user wearing the first UE 1204a and the second user wearing the second UE 1204b for the physical objects of interest. Content related to product information and price may be presented as virtual objects linked to spatial anchors. For example, a first virtual object 1220a (e.g., a first virtual tag) may be spatially associated with the first spatial anchor 1218a for the first physical object 1216a, a second virtual object 1220c (e.g., a second virtual tag) may be spatially associated with the third spatial anchor 1218c for the third physical object 1216c, and a third virtual object 1220d (e.g., a third virtual tag) may be spatially associated with the fourth spatial anchor 1218d for the fourth physical object 1216d.

[0212] The first user wearing the first UE 1204a may be interested in product information related to the third physical object 1216c (e.g., the first coffee bean cannister on the display stand) and the fourth physical object 1216d (e.g., the second coffee bean cannister on the display stand). The first UE 1204a may display the second virtual object 1220c (e.g., the second virtual tag) for the third physical object 1216c (e.g., the first coffee bean cannister on the display stand) and the third virtual object 1220d (e.g., the third virtual tag) for the fourth physical object 1216d (e.g., the second coffee bean cannister on the display stand).

[0213] The second user wearing the second UE 1204b may be interested in product information related to the first physical object 1216a (e.g., the first painting on the wall). The second UE 1204b may display the first virtual object 1220a (e.g., the first virtual tag) for the first physical object 1216a (e.g., the first painting on the wall). Due to the close proximity of the products as physical objects and the corresponding spatial anchors to provide virtual objects in scenario 1200, KPI metrics corresponding to 6DOF parameters may have tight ranges or require high accuracy so as not to adversely influence the user experience.

[0214] For example, the first UE 1204a may transmit perception-based positioning-related information comprising information associated with a metric corresponding to one or more DoF parameters to a network entity. In some case, the transmit perception-based positioning-related information may comprise an achieved KPI associated with the metric corresponding to the one or more DoF parameters. This achieved KPI may be determined by one or more sensors of the first UE 1204a absent any positioning information from the network entity. In some cases, the first UE 1204a may transmit perception-based positioning-related information comprising a desired KPI or KPI range associated with the metric corresponding to the one or more DoF parameters.

[0215] In some examples, the first UE 1204a may receive an RF -based positioning configuration responsive to the perception-based positioning-related information. In some cases, the first UE 1204a may receive an indication from the network entity that the RF-based positioning configuration is expected to satisfy the metric corresponding to the one or more DoF parameters.

[0216] In some cases, the perception-based positioning-related information transmitted by the first UE 1204a may include information corresponding to DoF orientation information of the first UE 1204a. That is, for example, the perception-based positioning-related information may include information corresponding to one or more of a “pitch” DoForientation parameter, a “yaw” DoF orientation parameter, a “roll” DoF orientation parameter, or any combination thereof.

[0217] In some examples, a sensor of the first UE 1204a that was previously used for determining DoF parameters may be temporarily blocked (e.g., by another customer in the coffee shop). In some cases, the first UE 1204a may refrain from using the sensor that is blocked. Rather, the first UE 1204a may utilize the received RF -based positioning configuration to determine one or more 6DoF parameters. That is, for example, the first UE 1204a may perform a positioning session based on the received RF -based positioning configuration to determine one or more 6DoF parameters related to positioning and / or orientation of the first UE 1204a on the first user’s head.

[0218] In some examples, the first UE 1204a may receive a reporting request from the network entity. The reporting request may include an indication to include the perception-based positioning-related information in a positioning measurement report. In some cases, the perception-based positioning-related information may be transmitted responsive to the reporting request. In some cases, the perception-based positioning-related information in the positioning measurement report may include an error indication corresponding to a perception-based component, such as a sensor of the first UE 1204a. In some cases, the error indication corresponding to the perception-based component in the positioning measurement report may indicate to the network entity that at least some information corresponding to perception-based positioning measurements by the first UE 1204a is unavailable.

[0219] In some examples, the first UE 1204a may transmit an indication that the first UE 1204a is refraining from using at least one positioning measurement gap associated with a positioning measurement gap configuration. In some cases, the indication that the first UE 1204a is refraining from using the at least one positioning measurement gap may be transmitted based on a determination that the metric corresponding to the one or more DoF parameters is satisfied. In some cases, the first UE 1204a may receive an indication corresponding to a number of positioning measurement reports for which the first UE 1204a is to use perception-based components. In some cases, the first UE 1204a may transmit data on a PUSCH during at least one positioning measurement gap associated with the positioning measurement gap configuration.

[0220] In some examples, the network entity or the first UE 1204a may determine that the RF- based positioning configuration is expected to improve the metric corresponding to the one or more DoF parameters. In some cases, the network entity or the first UE 1204a may determine to trigger an RF -based position estimation session for the first UE 1204a using the RF -based positioning configuration.

[0221] In some examples, the network entity may transmit positioning assistance data based on at least some information corresponding to the perception-based positioning-related information received from the first UE 1204a to the second UE 1204b. For example, the network entity may update a location of the fourth spatial anchor 1218d corresponding to the fourth physical object 1216d based on the perception-based positioning-related information received from the first UE 1204a. For example, the fourth physical object 1216d (e.g., the second coffee bean cannister on the display stand) may have been slightly moved from its original position by another customer. The network entity may then transmit the updated location information for the fourth spatial anchor 1218d to the second UE 1204b so that a more precise location for the fourth physical object 1216d may be detected by the second user wearing the second UE 1204b if or when the second user moves to that area of the coffee shop.

[0222] In some examples, the network entity may receive perception-based positioning-related information from the second UE 1204b. In some cases, the network entity may determine that all KPI metrics are met. In some cases, the network entity may determine that an RF- based positioning configuration is not expected to improve any KPI metrics corresponding to the 6DoF parameters. Accordingly, the network entity may refrain from transmitting an RF-based positioning configuration based on this perception-based positioning-related information from the second UE 1204b.

[0223] In accordance with some aspects described herein, a UE may transmit (and a network entity may receive) perception -based positioning-related information. This perceptionbased positioning-related information may be transmitted and received using various signaling techniques and / or configuration procedures. For example, the network entity may initiate (e.g., network-initiated) an on-demand PRS procedure with the UE. In some cases, the UE may initiate (e.g., UE-initiated) an on-demand PRS procedure with the network entity.

[0224] FIG. 13 illustrates an example of a network entity -initiated on-demand PRS positioning procedure 1300, according to aspects of the disclosure. In certain aspects, elements described in the network entity-initiated on-demand PRS positioning procedure 1300 may be examples of, or include features of, the corresponding or similar elements described with reference to FIGS. 1-12, as well as other features described herein. For example, the TRPs of gNBs 222, the UE 204, and the LMF 270 described with respect to the network entity-initiated on-demand PRS positioning procedure 1300 may correspond to the base station 1102, the first UE 1104a, the second UE 1104b, and the network entity 1106 described with respect to the wireless communication system 1100 in accordance with some aspects. In some examples, the UE 204 described with respect to the network entity- initiated on-demand PRS positioning procedure 1300 may correspond to the first UE 1204a and the second UE 1204b described with respect to the scenario 1200 in accordance with some aspects.

[0225] At stage 1310, a TRP information exchange procedure may provide the on-demand DL- PRS parameters supported by the TRPs to the LMF 270. In some examples, one or more of the TRPs of gNBs 222 may provide a bit map (e.g., an “On-demand PRS Request Allowed” bit map) to the LMF 270. That is, for example, the bit map may include: Bitl corresponding to a Resource Set Periodicity; Bit2 corresponding to a PRS Bandwidth; Bit3 corresponding to a Resource Repetition Factor; Bit4 corresponding to a Resource Number of Symbols; Bit5 corresponding to a Comb Size; Bit6 corresponding to a Number of Frequency Layers; Bit7 corresponding to a Start Time and Duration; Bit8 corresponding to an Off Indication; and Bit9 corresponding to a QCL Information. In some cases, for each bit in the bit map indicating support associated with an on-demand DL-PRS parameter, supported values may be provided to the LMF 270.

[0226] In some cases, a serving AMF 264 for a target UE 204 may invoke a service operation (e.g., a “Nlmf Location DetermineLocation” service operation) towards the UE’s 204 LMF 270 to request the current location of the UE 204. The service operation may include the UE’s 204 serving cell identity, the location services (LCS) client type (e.g., an emergency services client type or a commercial client type). In some cases, the service operation may include a required QoS. In some cases, the LMF 270 may send an LPP Request Capabilities message to the target UE 204 to request the positioning capabilities of the UE 204. The UE 204 may return an LPP Provide Capabilities message to the LMF270 to provide the positioning capabilities of the UE 204. The positioning capabilities may include the DL-PRS measurement capabilities of the UE 204.

[0227] At stage 1315, the UE 204 may send UE assistance information to the LMF 270. The UE assistance information may include perception-based positioning-related information as described herein.

[0228] At stage 1320, based on the LCS client type, the QoS (if provided), and the DL-PRS measurement capabilities of the UE 204 (if provided), the LMF 270 may determine gNBs 222 proximate to the location of the UE 204 (e.g., as indicated by the serving cell identity) to be measured by the UE 204 and a new DL-PRS configuration (for the requested on- demand PRS) for each of the gNBs 222. The determination at stage 1320 for determining the new DL-PRS configuration may be based on the UE assistance information. Additionally, or alternatively, the determination at stage 1320 may also be based on location requests for other UEs 204 proximate to the target UE 204, which are received by the LMF 270 at about the same time.

[0229] The new DL-PRS configuration may be initiated by the LMF 270 to request a gNB 222 to configure or update PRS transmission. That is, for example, a new DL-PRS configuration for one or more or gNB 222 may use increased DL-PRS bandwidth, a longer duration of DL-PRS positioning occasions, DL-PRS transmission on new frequencies, a higher frequency of DL-PRS positioning occasions, and / or the like. In some cases, the DL-PRS configuration may be selected from a set of one or more preconfigured sets of DL-PRS configuration parameters to support increased DL-PRS transmission. In the case of directional DL-PRS beams, the LMF 270 may determine directional DL-PRS beams for each gNB 222 that should be received by the target UE 204. The directional DL-PRS beams may be selected by the LMF 270 according to a known approximate location for the target UE 204 (e.g., as given by the serving cell identity).

[0230] At stage 1325, the LMF 270 sends an NRPPa DL-PRS Reconfiguration Request message to each of the gNBs 222 determined at stage 1320 and includes the new DL-PRS configuration (for on-demand PRS) determined for that gNB 222. For example, the Request message may include requested DL-PRS transmission characteristics and DL- PRS transmission off information (e.g., to turn off the DL-PRS transmission for certainTRPs). In some cases, the Request message may also include a start time for each new DL-PRS configuration and a duration.

[0231] At stage 1330, each of the gNBs 222 returns a response to the LMF 270 indicating whether the new DL-PRS configuration can be supported. In some cases, the gNBs 222 may send NRPPa DL-PRS Reconfiguration Response messages to the LMF 270 to indicate successful (or unsuccessful) reconfiguration of the DL-PRS. If some gNBs 222 indicate that the new DL-PRS configuration cannot be supported, the LMF 270 may restore the old DL-PRS configurations in each of the gNBs 222 that indicated a new DL- PRS configuration can be supported in order to avoid interference between gNBs 222 that support the new DL-PRS configuration and gNBs 222 that do not. In this case, the LMF 270 would provide the old DL-PRS configurations to the UE 204 at stage 1340 instead of the new DL-PRS configurations. At stage 1335, the gNBs 222 transmit the DL-PRS using the new configuration.

[0232] At stage 1340, the LMF 270 sends an LPP Provide Assistance Data message to the UE 204. The LPP Provide Assistance Data message includes the new (on-demand) PRS configuration. In some cases, the LMF 270 may send an LPP Request Location Information message to the UE 204. The LPP Request Location Information message may instruct the UE 204 to measure and report the DL-PRS from the nearby gNBs 222. As such, the UE 204 may measure the DL-PRS from the nearby gNBs 222. That is, for example, the UE 204 may measure the ToA, RSRP, RSTD, Rx-Tx time difference, etc. of the DL-PRS from the gNBs 222. In some cases, the UE 204 optionally determines a location of the UE 204 (for UE-based positioning). In some cases, the UE 204 may send an LPP Provide Location Information message to the LMF 270. The LPP Provide Location Information message may include the measurements of the DL-PRS performed.

[0233] In some cases, the LMF 270 may determine a location and orientation of the UE 204 based on the measurements in the LPP Provide Location Information message and the known locations of the gNBs 222. In some cases, the LMF 270 may send the determined location of the UE 204 to the AMF 264 (e.g., in an “Nlmf Location DetermineLocation Response message).

[0234] FIG. 14 illustrates an example of a UE-initiated on-demand PRS positioning procedure 1400, according to aspects of the disclosure. In certain aspects, elements described in the UE-initiated on-demand PRS positioning procedure 1400 may be examples of, or includefeatures of, the corresponding or similar elements described with reference to FIGS. 1- 13, as well as other features described herein. For example, the NG-RAN node 222, the UE 204, and the LMF 270 described with respect to the UE-initiated on-demand PRS positioning procedure 1400 may correspond to the base station 1102, the first UE 1104a, the second UE 1104b, and the network entity 1106 described with respect to the wireless communication system 1100 in accordance with some aspects. In some examples, the UE 204 described with respect to the UE-initiated on-demand PRS positioning procedure 1400 may correspond to the first UE 1204a and the second UE 1204b described with respect to the scenario 1200 in accordance with some aspects.

[0235] At stage 1410, the LMF 270 sends an NRPPa Assistance Information Control message to the NG-RAN node 222 with an indication to start broadcasting assistance information. In some cases, the NRPPa Assistance Information Control message includes one or more system information (SI) groups, where each group contains the broadcast periodicity and one or more positioning system information block (posSIB) types together with metadata to be scheduled in the same SI message. Each posSIB type may be ciphered and / or segmented at the LMF 270.

[0236] In some cases, the NG-RAN node 222 may include the received SI groups in RRC System Information messages and corresponding scheduling information in SIB1 to the UE 204. In some cases, the UE 204 may apply a system information acquisition procedure for acquiring the assistance data information that is broadcasted.

[0237] At stage 1415, in the case of UE-initiated On-Demand PRS, the LMF 270 may configure the UE 204 with available or pre-defined PRS configurations via LPP Provide Assistance Data message or via posSIB.

[0238] At stage 1420, the UE 204 may send a mobile originated location request (MO-LR) location service request message, which may include a LPP Request Assistance Data message for UE-initiated on-demand PRS request. In some cases, the UE-initiated on- demand PRS request may include one or more identifiers for a desired DL-PRS configuration. In some cases, the desired DL-PRS configuration may be ordered in priority. In some cases, the priority order for the desired DL-PRS configuration may be based on the UE 204 determinations with respect to KPI metrics corresponding to 6DOF parameters. In some cases, the UE-initiated on-demand PRS request may include perception-based positioning-related information as described herein.

[0239] At stage 1425, the LMF 270 may perform LMF-initiated on-demand PRS procedures. For example, the LMF 270 may determine an NG-RAN node 222 that is proximate to the location of the UE 204 (e.g., as indicated by the serving cell identity) to be measured by the UE 204 and a new DL-PRS configuration (for the requested on-demand PRS). In some cases, the determination at stage 1425 may be based on perception-based positioning-related information from UE 204.

[0240] The new DL-PRS configuration may be initiated by the LMF 270 to request the NG-RAN node 222 to configure or update PRS transmission. That is, for example, a new DL-PRS configuration for one or more or gNB 222 may use increased DL-PRS bandwidth, a longer duration of DL-PRS positioning occasions, DL-PRS transmission on new frequencies, a higher frequency of DL-PRS positioning occasions, and / or the like. In some cases, the DL-PRS configuration may be selected from a set of one or more preconfigured sets of DL-PRS configuration parameters to support increased DL-PRS transmission. In the case of directional DL-PRS beams, the LMF 270 may determine directional DL-PRS beams for one or more NG-RAN nodes 222 that should be received by the target UE 204. The directional DL-PRS beams may be selected by the LMF 270 according to a known approximate location for the target UE 204 (e.g., as given by the serving cell identity). At stage 1430, the NG-RAN node 222 transmits the DL-PRS using the new configuration.

[0241] At stage 1435, the LMF 270 sends an LPP Provide Assistance Data message to the UE 204. The LPP Provide Assistance Data message includes the new (on-demand) PRS configuration. In some cases, the LMF 270 may send an LPP Request Location Information message to the UE 204. The LPP Request Location Information message may instruct the UE 204 to measure and report the DL-PRS from the nearby NG-RAN nodes 222. As such, the UE 204 may measure the DL-PRS from the nearby NG-RAN nodes 222. That is, for example, the UE 204 may measure the ToA, RSRP, RSTD, Rx- Tx time difference, etc. of the DL-PRS from the NG-RAN nodes 222. In some cases, the UE 204 optionally determines a location of the UE 204 (for UE-based positioning). In some cases, the UE 204 may send an LPP Provide Location Information message to the LMF 270. The LPP Provide Location Information message may include the measurements of the DL-PRS performed.

[0242] In some cases, the LMF 270 may determine a location and orientation of the UE 204 based on the measurements in the LPP Provide Location Information message and the known locations of the gNBs 222. In some cases, the LMF 270 may send the determined location of the UE 204 to the AMF 264 (e.g., in an “Nlmf Location DetermineLocation Response message). In some cases, the gNBs 222 may send NRPPa DL-PRS Reconfiguration Response messages to the LMF 270 to indicate successful (or unsuccessful) reconfiguration of the DL-PRS.

[0243] In some examples, an RF-based positioning configuration may indicate PRS resources that are configured to improve a metric corresponding to 6DoF parameters. That is, for example, the PRS resources may be configured by the LMF 270 to provide a DL-PRS beam from a particular TRP of a gNBs 222 based on a location of the UE 204. In some cases, a characteristic of the particular 6DoF parameter may be considered in the configuration. That is, the PRS resources may be configured to have a certain periodicity, bandwidth, repetition factor, number of symbols, comb-size, or QCL information, for example, based on the 6DoF parameter corresponding to a “pitch” DoF orientation parameter, a “yaw” DoF orientation parameter, or a “roll” DoF orientation parameter.

[0244] FIG. 15 illustrates an example of a DL-PRS IE 1500, according to aspects of the disclosure. Aspects described with respect to the DL-PRS IE 1500 may be examples of, or include features of, the elements described with reference to FIGS. 1-14, as well as other features described herein. The DL-PRS IE 1500 in the example of FIG. 15 is the IE NR-On-Demand-DL-PRS-Information, which may be used by a UE to define the requested on-demand DL-PRS. In some cases, IES different from the IE NR-On-Demand- DL-PRS-Infor mation or modified given the benefit of the disclosure may be used in accordance with some aspects.

[0245] In some examples, the IE NR-On-Demand-DL-PRS-Information may include a dl-prs- FrequencyRangeReq field that specifies the frequency range for which the on-demand DL-PRS is requested. The IE NR-On-Demand-DL-PRS-Information may also include a dl-prs-CombSizeN-Req field that specifies the requested number of symbols per DL-PRS Resource within a slot. The IE NR- On-Demand-DL-PRS-Information may also include a dl-prs-NumSymbolsReq field that specifies the requested resource element spacing in each symbol of the DL-PRS resource.

[0246] In some examples, the IE NR-On-Demand-DL-PRS-Information may include a dl-prs- QCL-InformationReqTRPlist field that specifies the recommended or requested QCL indication with other DL reference signals. For example, the dl-PRS-ID indicates the DL- PRS ID of the TRP for which the QCL information is recommended. In some examples, a UE may provide the recommended QCL information using the dl-prs-QCL- InformationReqTRPlist field based on perception-based positioning-related information as described herein. For example, the UE may recommend QCL information based on a determination that a KPI metric corresponding to one or more DoF parameters has dropped.

[0247] FIGS. 16A and 16B illustrate an example position estimation procedure 1600 using LPP with an UL-SRS configuration, according to aspects of the disclosure. In certain aspects, elements described in the position estimation procedure 1600 may be examples of, or include features of, the corresponding or similar elements described with reference to FIGS. 1-15, as well as other features described herein. For example, the TRPs of gNBs 222, the UE 204, and the LMF 270 described with respect to the position estimation procedure 1600 may correspond to the base station 1102, the first UE 1104a, the second UE 1104b, and the network entity 1106 described with respect to the wireless communication system 1100 in accordance with some aspects. In some examples, the UE 204 described with respect to the position estimation procedure 1600 may correspond to the first UE 1204a and the second UE 1204b described with respect to the scenario 1200 in accordance with some aspects.

[0248] At stage 1605, the LMF 270 may request the positioning capabilities of the target UE 204 using the LPP Capability Transfer procedure. At stage 1610, the LMF 270 sends an NRPPa Positioning Information Request to the target UE’ s 204 serving gNB 222 (or TRP) to request UL-SRS configuration information for the UE 204. In some cases, the NRPPa Positioning Information Request may include 6DoF information. The 6DoF information may include perception-based positioning-related information as described herein. That is, for example, the LMF 270 may receive the perception-based positioning-related information from the UE 204 and / or other UEs involved in an interactive application. The LMF 270 may process the perception-based positioning-related information to make a determination regarding a KPI metric corresponding to one or more DoF parameters. Forexample, the 6D0F information may include an indication that the KPI metric has dropped.

[0249] At stage 1615, the serving gNB 222 may determine the resources available for UL-SRS and configure the target UE 204 with the UL-SRS resource sets. In some examples, the target UE’s 204 serving gNB 222 may utilize the 6DoF information from the NRPPa Positioning Information Request to optimize an UL-SRS configuration. At stage 1620, the serving gNB 222 may provide the UL-SRS configuration to the UE 204. At stage 1625, the serving gNB 222 sends an NRPPa Positioning Information Response message to the LMF 270. In some cases, the NRPPa Positioning Information Response message includes the UL-SRS configuration information sent to the UE 204.

[0250] At stage 1630, the LMF 270 sends an NRPPa Measurement Request message to the serving gNB 222 and candidate neighbor gNBs 222 (or TRPs). The NRPPa Measurement Request message includes information needed to enable the gNBs 222 to perform measurements of the UL-SRS transmissions from the target UE 204. At stage 1635, the LMF 270 sends an LPP Provide Assistance Data message to the UE 204. The LPP Provide Assistance Data message may include a PRS configuration (e.g., DL-PRS configuration).

[0251] At stage 1640, the LMF 270 sends an LPP Request Location Information message to the target UE 204. At stage 1645, the LMF 270 may request activation of UE SRS transmission by sending a NRPPa UL-SRS Activation Request message to the serving gNB 222 of the target UE 204. At stage 1650, the target UE 204 may begin the UL-SRS transmission according to a trigger (e.g., the time domain behavior of UL-SRS resource configuration). At stage 1655, the UE 204 may perform the DL-PRS measurements. At stage 1660, the involved gNBs 222 (e.g., the serving gNB 222 and the neighbor gNBs 222) may perform positioning measurements of the UL-SRS transmissions from the target UE 204. For example, the gNBs 222 may measure the ToA, UL-RSTD, AoA, etc. of the UL-SRS transmitted by the UE 204.

[0252] At stage 1665, the UE 204 may report the DL-PRS measurements (e.g., for a multi-RTT procedure, etc.) to the LMF 270 in a LPP Provide Location Information message. The LPP Provide Location Information message includes the DL-PRS measurements performed at stage 1655. At stage 1670, the involved gNBs 222 may send NRPPa Measurement Response messages to the LMF 270. The NRPPa Measurement Responsemessages includes the measurements of the UL-SRS transmissions measured at stage 1660.

[0253] FIG. 17 is a flowchart of an example process 1700 associated with techniques for perception assistance using positioning and assistance data, according to aspects of the disclosure. In some implementations, one or more process blocks of FIG. 17 may be performed by a user equipment (UE) (e.g., UE 104). In some implementations, one or more process blocks of FIG. 17 may be performed by another device or a group of devices separate from or including the UE. Additionally, or alternatively, one or more process blocks of FIG. 17 may be performed by one or more components of UE 304, such as processor(s) 342, memory 340, WWAN transceiver(s) 310, short-range wireless transceiver(s) 320, satellite signal receiver 330, sensor(s) 344, user interface 346, and DoF positioning component(s) 348, any or all of which may be means for performing the operations of process 1700.

[0254] As shown in FIG. 17, process 1700 may include, at block 1710, transmitting, to a network entity, perception-based positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters. In some cases, the perception-based positioning-related information is obtained by a modem of the UE through a cross-layer application programming interface (API). Means for performing the operation of block 1710 may include the processor(s) 342, memory 340, or WWAN transceiver(s) 310 of the UE 304. For example, the UE 304 may transmit, to a network entity, perception-based positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters, using WWAN transceiver(s) 310.

[0255] As further shown in FIG. 17, process 1700 may include, at block 1720, receiving, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the perception-based positioning-related information. Means for performing the operation of block 1720 may include the processor(s) 332, memory 340, or WWAN transceiver(s) 310 of the UE 304. For example, the UE 304 may receive, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the perception-based positioning-related information, using WWAN transceiver(s) 310.

[0256] Process 1700 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in connection with one or more other processes described elsewhere herein.

[0257] In some aspects, the cross-layer API is between the modem and an interactive application running on the UE.

[0258] In some aspects, the perception-based positioning-related information comprises a request for positioning reference signal (PRS) resources on one or more transmission beams.

[0259] In some aspects, the perception-based positioning-related information comprises UE assistance data in an on-demand positioning reference signal (PRS) procedure.

[0260] In some aspects, the RF -based positioning configuration indicates one or more PRS resources configured to improve the metric corresponding to the one or more DoF parameters.

[0261] In some aspects, the configured one or more PRS resources are associated with at least one directional downlink PRS (DL-PRS) beam from a transmission reception point (TRP) based on a location of the UE and a characteristic of the one or more DoF parameters.

[0262] In some aspects, the perception-based positioning-related information comprises an achieved key performance indicator (KPI) associated with the metric corresponding to the one or more DoF parameters.

[0263] In some aspects, the achieved KPI associated with the metric is based on a KPI value determination absent positioning information from the network entity.

[0264] In some aspects, the perception-based positioning-related information comprises a desired key performance indicator (KPI) or KPI range associated with the metric corresponding to the one or more DoF parameters.

[0265] In some aspects, the perception-based positioning-related information comprises data associated with camera frames of a camera device of the UE, data associated with an inertial measurement unit (IMU) sensor of the UE, data associated with one or more sensors of the UE, a resolution of the one or more sensors, a rate of the one or more sensors, or a combination thereof.

[0266] In some aspects, process 1700 includes receiving an indication from the network entity that the RF-based positioning configuration is expected to satisfy the metric corresponding to the one or more DoF parameters.

[0267] In some aspects, the perception-based positioning-related information is associated with information corresponding to one or more DoF that includes orientation information of the UE different from position information of the UE.

[0268] In some aspects, the orientation information of the UE comprises DoF information corresponding to one or more of a pitch, a yaw, or a roll.

[0269] In some aspects, the RF-based positioning configuration comprises positioning reference signal (PRS) resources on one or more transmission beams with updated quasi -collocation (QCL) information based on the orientation information of the UE.

[0270] In some aspects, process 1700 includes receiving a first prioritization of a plurality of positioning reference signal (PRS) resource sets associated with the RF-based positioning configuration, wherein the first prioritization is based on the orientation information of the UE.

[0271] In some aspects, process 1700 includes receiving a second prioritization of the plurality of PRS resource sets associated with the RF-based positioning configuration, wherein the second prioritization is based on the position information of the UE and different from the first prioritization.

[0272] In some aspects, the RF-based positioning configuration comprises one or more sets of sounding reference signal (SRS) resources based on the orientation information of the UE.

[0273] In some aspects, process 1700 includes refraining from using at least one sensor of the UE based on the received RF-based positioning configuration.

[0274] In some aspects, the at least one sensor was used in at least one perception-based positioning determination prior to a transmission of the perception-based positioning- related information.

[0275] In some aspects, process 1700 includes transmitting a capability indication of support for perception-based positioning.

[0276] In some aspects, the capability indication is transmitted responsive to a capability request from the network entity.

[0277] In some aspects, the capability indication is stored at the network entity as a configuration associated with the one or more DoF parameters.

[0278] In some aspects, process 1700 includes receiving, from the network entity, a reporting request to include the perception-based positioning-related information in a positioningmeasurement report, wherein the perception-based positioning-related information is transmitted responsive to the reporting request.

[0279] In some aspects, the transmitting, to the network entity, the perception-based positioning- related information comprises transmitting, to the network entity, the positioning measurement report to include the perception-based positioning-related information, or transmitting, to the network entity, the positioning measurement report to include an error indication corresponding to a perception-based component.

[0280] In some aspects, the error indication corresponding to the perception-based component in the positioning measurement report indicates to the network entity that at least some information corresponding to perception-based positioning measurements by the UE is unavailable.

[0281] In some aspects, process 1700 includes performing measurements for the positioning measurement report using one or more positioning measurement gaps associated with a positioning measurement gap configuration, wherein the measurements for the positioning measurement report are performed using the one or more positioning measurement gaps based on an inclusion of the perception-based positioning-related information in the positioning measurement report, and transmitting, to the network entity, an indication that the UE used the one or more positioning measurement gaps associated with the positioning measurement gap configuration to perform the measurements for the positioning measurement report.

[0282] In some aspects, process 1700 includes a first measurement gap length of the one or more positioning measurement gaps is different than a second measurement gap length of second positioning measurement gaps associated with the positioning measurement gap configuration, and the second positioning measurement gaps are for a second positioning measurement report that does not include measurements corresponding to the perceptionbased positioning-related information.

[0283] In some aspects, process 1700 includes transmitting data on a physical uplink shared channel (PUSCH) during at least one positioning measurement gap associated with a positioning measurement gap configuration, and transmitting a positioning measurement report based on perception-based components of the UE.

[0284] In some aspects, at least one measurement indication of the positioning measurement report is determined absent reference signals associated with the positioning measurement gap configuration.

[0285] In some aspects, process 1700 includes transmitting an indication that the UE is refraining from using at least one positioning measurement gap associated with a positioning measurement gap configuration.

[0286] In some aspects, the indication that the UE is refraining from using the at least one positioning measurement gap is transmitted based on a determination that the metric corresponding to the one or more DoF parameters is satisfied.

[0287] In some aspects, process 1700 includes receiving an indication corresponding to a number of positioning measurement reports for which the UE is to use perception-based components.

[0288] In some aspects, the UE comprises a perception entity.

[0289] In some aspects, the UE is running an extended reality (XR) or metaverse-based application that utilizes at least one sensor of the UE.

[0290] Although FIG. 17 shows example blocks of process 1700, in some implementations, process 1700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 17. Additionally, or alternatively, two or more of the blocks of process 1700 may be performed in parallel.

[0291] As will be appreciated, a technical advantage of the process 1700 is that by receiving an RF-based positioning configuration from the network entity, the process can be used to save power by refraining from using one or more sensors during one or more perceptionbased positioning sessions performed by the UE. That is, for example, the UE may base the one or more perception-based positioning sessions on positioning techniques using the RF-based positioning configuration. In some examples, by using the RF-based positioning configuration, the process can be used to more precisely meet KPI metrics corresponding to 6DoF parameters.

[0292] FIG. 18 is a flowchart of an example process 1800 associated with techniques for perception assistance using positioning and assistance data, according to aspects of the disclosure. In some implementations, one or more process blocks of FIG. 18 may be performed by a network entity (e.g., network entity 306, LMF 206, etc.). In some implementations, one or more process blocks of FIG. 18 may be performed by anotherdevice or a group of devices separate from or including the network entity. Additionally, or alternatively, one or more process blocks of FIG. 18 may be performed by one or more components of network entity 306, such as processor(s) 394, memory 396, network transceiver(s) 390, and DoF positioning component(s) 398, any or all of which may be means for performing the operations of process 1800.

[0293] As shown in FIG. 18, process 1800 may include, at block 1810, receiving, from a first user equipment (UE), first perception-based positioning-related information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters. Means for performing the operation of block 1810 may include the processor(s) 394, memory 396, or network transceiver(s) 390 of the network entity 306. For example, the network entity 306 may receive, from a first user equipment (UE), first perception-based positioning-related information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters, using network transceiver s) 390.

[0294] As further shown in FIG. 18, process 1800 may include, at block 1820, transmitting, to the first UE, a first radio frequency (RF)-based positioning configuration responsive to the first perception-based positioning-related information. Means for performing the operation of block 1820 may include the processor(s) 394, memory 396, or network transceiver(s) 390 of the network entity 306. For example, the network entity 306 may transmit, to the first UE, a first radio frequency (RF)-based positioning configuration responsive to the first perception-based positioning-related information, using network transceiver(s) 390.

[0295] Process 1800 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in connection with one or more other processes described elsewhere herein.

[0296] In some aspects, process 1800 includes determining that the first RF -based positioning configuration is expected to improve the metric corresponding to the one or more DoF parameters, wherein the first RF-based positioning configuration is transmitted based on the determining.

[0297] In some aspects, process 1800 includes determining to trigger an RF-based position estimation session of the first UE using the first RF-based positioning configuration based on the first perception-based positioning-related information.

[0298] In some aspects, process 1800 includes determining to update quasi-collocation (QCL) information associated with one or more transmission beams based on the received first perception-based positioning-related information, wherein the first RF-based positioning configuration includes positioning reference signal (PRS) resources based on the updated QCL information.

[0299] In some aspects, process 1800 includes transmitting positioning assistance data based on at least some information corresponding to the first perception-based positioning-related information to a second UE different from the first UE.

[0300] In some aspects, process 1800 includes transmitting a second RF-based positioning configuration to a second UE different from the first UE based on the received first perception-based positioning-related information from the first UE.

[0301] In some aspects, the second RF-based positioning configuration comprises second positioning reference signal (PRS) resources configured with at least one of a second bandwidth, a second periodicity, or a second comb pattern different from a corresponding prior bandwidth, prior periodicity, or prior comb pattern of PRS resources of a prior RF- based positioning configuration of the second UE.

[0302] In some aspects, process 1800 includes receiving, from a second UE, second perceptionbased positioning-related information, and refraining from transmitting an RF-based positioning configuration based on second perception-based positioning-related information.

[0303] In some aspects, process 1800 includes determining that the RF-based positioning configuration is not expected to improve the metric corresponding to the one or more DoF parameters, wherein the refraining from transmitting the RF-based positioning configuration is based on the determining.

[0304] In some aspects, the received first perception-based positioning-related information comprises sensor information from one or more sensors of the first UE.

[0305] In some aspects, process 1800 includes transmitting, to the first UE, a request for perception-based positioning-related information based on the metric corresponding to the one or more DoF parameters managed by the network entity.

[0306] In some aspects, the request for the perception-based positioning-related information includes a request for DoF information corresponding to orientation information of the first UE different from position information of the first UE.

[0307] In some aspects, process 1800 includes receiving, from the first UE, a capability indication of support for perception-based positioning, and storing the capability indication as a configuration associated with the one or more DoF parameters.

[0308] In some aspects, process 1800 includes receiving, from a device running an extended reality (XR) or metaverse-based application, the metric corresponding to the one or more DoF parameters.

[0309] In some aspects, the network entity comprises a location management function (LMF) or a session management function (SMF).

[0310] Although FIG. 18 shows example blocks of process 1800, in some implementations, process 1800 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 18. Additionally, or alternatively, two or more of the blocks of process 1800 may be performed in parallel.

[0311] As will be appreciated, a technical advantage of the process 1800 is that by transmitting an RF -based positioning configuration from the network entity, the process can be used to save power by refraining from using one or more sensors during one or more perception-based positioning sessions performed by the UE. That is, for example, the UE may base the one or more perception-based positioning sessions on positioning techniques using the RF -based positioning configuration. In some examples, by deciding that an RF -based positioning configuration would not assist a UE based on the perceptionbased positioning-related information, the network entity may refrain from configuring the UE running the interactive application with RF-based positioning resources. In some cases, these time and frequency resources may be allocated for data transmission purposes for the UE.

[0312] In the detailed description above it can be seen that different features are grouped together in examples. This manner of disclosure should not be understood as an intention that the example clauses have more features than are explicitly mentioned in each clause. Rather, the various aspects of the disclosure may include fewer than all features of an individual example clause disclosed. Therefore, the following clauses should hereby be deemed to be incorporated in the description, wherein each clause by itself can stand as a separate example. Although each dependent clause can refer in the clauses to a specific combination with one of the other clauses, the aspect(s) of that dependent clause are not limited to the specific combination. It will be appreciated that other example clauses canalso include a combination of the dependent clause aspect(s) with the subject matter of any other dependent clause or independent clause or a combination of any feature with other dependent and independent clauses. The various aspects disclosed herein expressly include these combinations, unless it is explicitly expressed or can be readily inferred that a specific combination is not intended (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). Furthermore, it is also intended that aspects of a clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

[0313] Implementation examples are described in the following numbered clauses:

[0314] Clause 1. A method of wireless communication performed by a user equipment (UE), comprising: transmitting, to a network entity, perception-based positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters, wherein the perception-based positioning- related information is obtained by a modem of the UE through a cross-layer application programming interface (API); and receiving, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the perception-based positioning- related information.

[0315] Clause 2. The method of clause 1, wherein the cross-layer API is between the modem and an interactive application running on the UE.

[0316] Clause 3. The method of any of clauses 1 to 2, wherein the perception-based positioning- related information comprises a request for positioning reference signal (PRS) resources on one or more transmission beams.

[0317] Clause 4. The method of any of clauses 1 to 3, wherein the perception-based positioning- related information comprises UE assistance data in an on-demand positioning reference signal (PRS) procedure.

[0318] Clause 5. The method of any of clauses 1 to 4, wherein the perception-based positioning- related information comprises UE assistance data in an on-demand positioning reference signal (PRS) procedure.

[0319] Clause 6. The method of clause 5, wherein the RF-based positioning configuration indicates one or more PRS resources configured to improve the metric corresponding to the one or more DoF parameters.

[0320] Clause 7. The method of clause 6, wherein the configured one or more PRS resources are associated with at least one directional downlink PRS (DL-PRS) beam from a transmission reception point (TRP) based on a location of the UE, a characteristic of the one or more DoF parameters, or both.

[0321] Clause 8. The method of any of clauses 1 to 7, wherein the perception-based positioning- related information comprises an achieved key performance indicator (KPI) associated with the metric corresponding to the one or more DoF parameters.

[0322] Clause 9. The method of clause 8, wherein the achieved KPI associated with the metric is based on a KPI value determination absent positioning information from the network entity.

[0323] Clause 10. The method of any of clauses 1 to 9, wherein the perception-based positioning- related information comprises a desired key performance indicator (KPI) or KPI range associated with the metric corresponding to the one or more DoF parameters.

[0324] Clause 11. The method of any of clauses 1 to 10, wherein the perception-based positioning-related information comprises: data associated with one or more perceptionbased components of the UE, a resolution of the one or more perception-based components, a rate of the one or more perception-based components, or a combination thereof.

[0325] Clause 12. The method of any of clauses 1 to 11, further comprising: receiving an indication from the network entity that the RF -based positioning configuration is expected to satisfy the metric corresponding to the one or more DoF parameters.

[0326] Clause 13. The method of any of clauses 1 to 12, wherein the perception-based positioning-related information is associated with information corresponding to one or more DoF that includes orientation information of the UE different from position information of the UE.

[0327] Clause 14. The method of clause 13, wherein the orientation information of the UE comprises DoF information corresponding to one or more of a pitch, a yaw, or a roll.

[0328] Clause 15. The method of any of clauses 13 to 14, wherein the RF -based positioning configuration comprises positioning reference signal (PRS) resources on one or more transmission beams with updated quasi-collocation (QCL) information based on the orientation information of the UE.

[0329] Clause 16. The method of any of clauses 13 to 15, further comprising: receiving a first prioritization of a plurality of positioning reference signal (PRS) resource sets associated with the RF-based positioning configuration, wherein the first prioritization is based on the orientation information of the UE.

[0330] Clause 17. The method of clause 16, further comprising: receiving a second prioritization of the plurality of PRS resource sets associated with the RF-based positioning configuration, wherein the second prioritization is based on the position information of the UE and different from the first prioritization.

[0331] Clause 18. The method of any of clauses 13 to 17, wherein the RF-based positioning configuration comprises one or more sets of sounding reference signal (SRS) resources based on the orientation information of the UE.

[0332] Clause 19. The method of any of clauses 1 to 18, further comprising: refraining from using at least one sensor of the UE based on the received RF-based positioning configuration.

[0333] Clause 20. The method of clause 19, wherein the at least one sensor was used in at least one perception-based positioning determination prior to a transmission of the perceptionbased positioning-related information.

[0334] Clause 21. The method of any of clauses 1 to 20, further comprising: transmitting a capability indication of support for perception-based positioning, or transmitting a capability message of capabilities supported for perception-based positioning.

[0335] Clause 22. The method of clause 21, wherein the capability indication is transmitted responsive to a capability request from the network entity, or the capability message is transmitted responsive to a capability request from the network entity.

[0336] Clause 23. The method of any of clauses 21 to 22, wherein the capability indication is stored at the network entity as a configuration associated with the one or more DoF parameters, or the capability message is stored at the network entity as a configuration associated with the one or more DoF parameters.

[0337] Clause 24. The method of any of clauses 1 to 23, further comprising: receiving, from the network entity, a reporting request indicating the UE to include the perception-based positioning-related information in a positioning measurement report, wherein the perception-based positioning-related information is transmitted responsive to the reporting request.

[0338] Clause 25. The method of clause 24, wherein the transmitting, to the network entity, the perception-based positioning-related information comprises: transmitting, to the network entity, the positioning measurement report to include the perception-based positioning- related information; or transmitting, to the network entity, the positioning measurement report to include an error indication corresponding to a perception-based component.

[0339] Clause 26. The method of clause 25, wherein the error indication corresponding to the perception-based component in the positioning measurement report indicates to the network entity that at least some information corresponding to perception-based positioning measurements by the UE is unavailable.

[0340] Clause 27. The method of any of clauses 24 to 26, further comprising: performing measurements for the positioning measurement report using one or more positioning measurement gaps associated with a positioning measurement gap configuration, wherein the measurements for the positioning measurement report are performed using the one or more positioning measurement gaps based on an inclusion of the perception-based positioning-related information in the positioning measurement report; and transmitting, to the network entity, an indication that the UE used the one or more positioning measurement gaps associated with the positioning measurement gap configuration to perform the measurements for the positioning measurement report.

[0341] Clause 28. The method of clause 27, wherein: a first measurement gap length of the one or more positioning measurement gaps is greater than a second measurement gap length of second positioning measurement gaps associated with the positioning measurement gap configuration; and the second positioning measurement gaps are for a second positioning measurement report that does not include measurements corresponding to the perception-based positioning-related information.

[0342] Clause 29. The method of any of clauses 1 to 28, further comprising: transmitting data on a physical uplink shared channel (PUSCH) during at least one positioning measurement gap associated with a positioning measurement gap configuration; and transmitting a positioning measurement report based on perception-based components of the UE.

[0343] Clause 30. The method of clause 29, wherein at least one measurement indication of the positioning measurement report is determined absent reference signals associated with the positioning measurement gap configuration.

[0344] Clause 31. The method of any of clauses 1 to 30, further comprising: transmitting an indication that the UE is refraining from using at least one positioning measurement gap associated with a positioning measurement gap configuration.

[0345] Clause 32. The method of clause 31, wherein the indication that the UE is refraining from using the at least one positioning measurement gap is transmitted based on a determination that the metric corresponding to the one or more DoF parameters is satisfied.

[0346] Clause 33. The method of any of clauses 1 to 32, further comprising: receiving an indication corresponding to a number of positioning measurement reports for which the UE is to use perception-based components.

[0347] Clause 34. The method of any of clauses 1 to 33, wherein the UE comprises a perception entity.

[0348] Clause 35. The method of any of clauses 1 to 34, wherein the UE is running an extended reality (XR) or metaverse-based application that utilizes at least one sensor of the UE.

[0349] Clause 36. A method of wireless communication performed by a network entity, comprising: receiving, from a first user equipment (UE), first perception-based positioning-related information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters; and transmitting, to the first UE, a first radio frequency (RF)-based positioning configuration responsive to the first perception-based positioning-related information.

[0350] Clause 37. The method of clause 36, further comprising: determining that the first RF- based positioning configuration is expected to improve the metric corresponding to the one or more DoF parameters, wherein the first RF-based positioning configuration is transmitted based on the determining.

[0351] Clause 38. The method of any of clauses 36 to 37, further comprising: determining to trigger an RF-based position estimation session of the first UE using the first RF-based positioning configuration based on the first perception-based positioning-related information.

[0352] Clause 39. The method of any of clauses 36 to 38, further comprising: determining to update quasi-collocation (QCL) information associated with one or more transmission beams based on the received first perception-based positioning-related information,wherein the first RF-based positioning configuration includes positioning reference signal (PRS) resources based on the updated QCL information.

[0353] Clause 40. The method of any of clauses 36 to 39, further comprising: transmitting positioning assistance data based on at least some information corresponding to the first perception-based positioning-related information to a second UE different from the first UE.

[0354] Clause 41. The method of any of clauses 36 to 40, further comprising: transmitting a second RF-based positioning configuration to a second UE different from the first UE based on the received first perception-based positioning-related information from the first UE.

[0355] Clause 42. The method of clause 41, wherein the second RF-based positioning configuration comprises second positioning reference signal (PRS) resources configured with at least one of a second bandwidth, a second periodicity, or a second comb pattern different from a corresponding prior bandwidth, prior periodicity, or prior comb pattern of PRS resources of a prior RF-based positioning configuration of the second UE.

[0356] Clause 43. The method of any of clauses 36 to 42, further comprising: receiving, from a second UE, second perception-based positioning-related information; and refraining from transmitting an RF-based positioning configuration based on second perception-based positioning-related information.

[0357] Clause 44. The method of clause 43, further comprising: determining that the RF-based positioning configuration is not expected to improve the metric corresponding to the one or more DoF parameters, wherein the refraining from transmitting the RF-based positioning configuration is based on the determining.

[0358] Clause 45. The method of any of clauses 36 to 44, wherein the received first perceptionbased positioning-related information comprises sensor information from one or more sensors of the first UE.

[0359] Clause 46. The method of any of clauses 36 to 45, further comprising: transmitting, to the first UE, a request for perception-based positioning-related information based on the metric corresponding to the one or more DoF parameters managed by the network entity.

[0360] Clause 47. The method of clause 46, wherein the request for the perception-based positioning-related information includes a request for DoF information corresponding to orientation information of the first UE different from position information of the first UE.

[0361] Clause 48. The method of any of clauses 36 to 47, further comprising: receiving, from the first UE, a capability indication of support for perception-based positioning; and storing the capability indication as a configuration associated with the one or more DoF parameters.

[0362] Clause 49. The method of any of clauses 36 to 48, further comprising: determining one or more positioning reference signal (PRS) resource sets associated with the first RF- based positioning configuration and / or a prioritization of the one or more PRS resource sets, based on the perception-based positioning-related information.

[0363] Clause 50. The method of any of clauses 36 to 49, further comprising: receiving, from a device running an extended reality (XR) or metaverse-based application, the metric corresponding to the one or more DoF parameters.

[0364] Clause 51. The method of any of clauses 36 to 50, wherein the network entity comprises a location management function (LMF) or a session management function (SMF).

[0365] Clause 52. A user equipment (UE), comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: transmit, via the one or more transceivers, to a network entity, perception-based positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters, wherein the perception-based positioning-related information is obtained by a modem of the UE through a cross-layer application programming interface (API); and receive, via the one or more transceivers, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the perception-based positioning-related information.

[0366] Clause 53. The UE of clause 52, wherein the cross-layer API is between the modem and an interactive application running on the UE.

[0367] Clause 54. The UE of any of clauses 52 to 53, wherein the perception-based positioning- related information comprises a request for positioning reference signal (PRS) resources on one or more transmission beams.

[0368] Clause 55. The UE of any of clauses 52 to 54, wherein the perception-based positioning- related information comprises UE assistance data in an on-demand positioning reference signal (PRS) procedure.

[0369] Clause 56. The UE of any of clauses 52 to 55, wherein the perception-based positioning- related information comprises UE assistance data in an on-demand positioning reference signal (PRS) procedure.

[0370] Clause 57. The UE of clause 56, wherein the RF -based positioning configuration indicates one or more PRS resources configured to improve the metric corresponding to the one or more DoF parameters.

[0371] Clause 58. The UE of clause 57, wherein the configured one or more PRS resources are associated with at least one directional downlink PRS (DL-PRS) beam from a transmission reception point (TRP) based on a location of the UE, a characteristic of the one or more DoF parameters, or both.

[0372] Clause 59. The UE of any of clauses 52 to 58, wherein the perception-based positioning- related information comprises an achieved key performance indicator (KPI) associated with the metric corresponding to the one or more DoF parameters.

[0373] Clause 60. The UE of clause 59, wherein the achieved KPI associated with the metric is based on a KPI value determination absent positioning information from the network entity.

[0374] Clause 61. The UE of any of clauses 52 to 60, wherein the perception-based positioning- related information comprises a desired key performance indicator (KPI) or KPI range associated with the metric corresponding to the one or more DoF parameters.

[0375] Clause 62. The UE of any of clauses 52 to 61, wherein the perception-based positioning- related information comprises: data associated with one or more perception-based components of the UE, a resolution of the one or more perception-based components, a rate of the one or more perception-based components, or a combination thereof.

[0376] Clause 63. The UE of any of clauses 52 to 62, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, an indication from the network entity that the RF -based positioning configuration is expected to satisfy the metric corresponding to the one or more DoF parameters.

[0377] Clause 64. The UE of any of clauses 52 to 63, wherein the perception-based positioning- related information is associated with information corresponding to one or more DoF that includes orientation information of the UE different from position information of the UE.

[0378] Clause 65. The UE of clause 64, wherein the orientation information of the UE comprises DoF information corresponding to one or more of a pitch, a yaw, or a roll.

[0379] Clause 66. The UE of any of clauses 64 to 65, wherein the RF-based positioning configuration comprises positioning reference signal (PRS) resources on one or more transmission beams with updated quasi-collocation (QCL) information based on the orientation information of the UE.

[0380] Clause 67. The UE of any of clauses 64 to 66, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, a first prioritization of a plurality of positioning reference signal (PRS) resource sets associated with the RF-based positioning configuration, wherein the first prioritization is based on the orientation information of the UE.

[0381] Clause 68. The UE of clause 67, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, a second prioritization of the plurality of PRS resource sets associated with the RF-based positioning configuration, wherein the second prioritization is based on the position information of the UE and different from the first prioritization.

[0382] Clause 69. The UE of any of clauses 64 to 68, wherein the RF-based positioning configuration comprises one or more sets of sounding reference signal (SRS) resources based on the orientation information of the UE.

[0383] Clause 70. The UE of any of clauses 52 to 69, wherein the one or more processors, either alone or in combination, are further configured to: refrain from using at least one sensor of the UE based on the received RF-based positioning configuration.

[0384] Clause 71. The UE of clause 70, wherein the at least one sensor was used in at least one perception-based positioning determination prior to a transmission of the perceptionbased positioning-related information.

[0385] Clause 72. The UE of any of clauses 52 to 71, wherein the one or more processors, either alone or in combination, are further configured to: transmit, via the one or more transceivers, a capability indication of support for perception-based positioning, or transmit, via the one or more transceivers, a capability message of capabilities supported for perception-based positioning.

[0386] Clause 73. The UE of clause 72, wherein the capability indication is transmitted responsive to a capability request from the network entity, or the capability message is transmitted responsive to a capability request from the network entity.

[0387] Clause 74. The UE of any of clauses 72 to 73, wherein the capability indication is stored at the network entity as a configuration associated with the one or more DoF parameters, or the capability message is stored at the network entity as a configuration associated with the one or more DoF parameters.

[0388] Clause 75. The UE of any of clauses 52 to 74, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, from the network entity, a reporting request indicating the UE to include the perception-based positioning-related information in a positioning measurement report, wherein the perception-based positioning-related information is transmitted responsive to the reporting request.

[0389] Clause 76. The UE of clause 75, wherein the transmitting, to the network entity, the perception-based positioning-related information comprises: transmit, via the one or more transceivers, to the network entity, the positioning measurement report to include the perception-based positioning-related information; or transmit, via the one or more transceivers, to the network entity, the positioning measurement report to include an error indication corresponding to a perception-based component.

[0390] Clause 77. The UE of clause 76, wherein the error indication corresponding to the perception-based component in the positioning measurement report indicates to the network entity that at least some information corresponding to perception-based positioning measurements by the UE is unavailable.

[0391] Clause 78. The UE of any of clauses 75 to 77, wherein the one or more processors, either alone or in combination, are further configured to: perform measurements for the positioning measurement report using one or more positioning measurement gaps associated with a positioning measurement gap configuration, wherein the measurements for the positioning measurement report are performed using the one or more positioning measurement gaps based on an inclusion of the perception-based positioning-related information in the positioning measurement report; and transmit, via the one or more transceivers, to the network entity, an indication that the UE used the one or morepositioning measurement gaps associated with the positioning measurement gap configuration to perform the measurements for the positioning measurement report.

[0392] Clause 79. The UE of clause 78, wherein: a first measurement gap length of the one or more positioning measurement gaps is greater than a second measurement gap length of second positioning measurement gaps associated with the positioning measurement gap configuration; and the second positioning measurement gaps are for a second positioning measurement report that does not include measurements corresponding to the perceptionbased positioning-related information.

[0393] Clause 80. The UE of any of clauses 52 to 79, wherein the one or more processors, either alone or in combination, are further configured to: transmit, via the one or more transceivers, data on a physical uplink shared channel (PUSCH) during at least one positioning measurement gap associated with a positioning measurement gap configuration; and transmit, via the one or more transceivers, a positioning measurement report based on perception-based components of the UE.

[0394] Clause 81. The UE of clause 80, wherein at least one measurement indication of the positioning measurement report is determined absent reference signals associated with the positioning measurement gap configuration.

[0395] Clause 82. The UE of any of clauses 52 to 81, wherein the one or more processors, either alone or in combination, are further configured to: transmit, via the one or more transceivers, an indication that the UE is refraining from using at least one positioning measurement gap associated with a positioning measurement gap configuration.

[0396] Clause 83. The UE of clause 82, wherein the indication that the UE is refraining from using the at least one positioning measurement gap is transmitted based on a determination that the metric corresponding to the one or more DoF parameters is satisfied.

[0397] Clause 84. The UE of any of clauses 52 to 83, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, an indication corresponding to a number of positioning measurement reports for which the UE is to use perception-based components.

[0398] Clause 85. The UE of any of clauses 52 to 84, wherein the UE comprises a perception entity.

[0399] Clause 86. The UE of any of clauses 52 to 85, wherein the UE is running an extended reality (XR) or metaverse-based application that utilizes at least one sensor of the UE.

[0400] Clause 87. A network entity, comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: receive, via the one or more transceivers, from a first user equipment (UE), first perception-based positioning-related information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters; and transmit, via the one or more transceivers, to the first UE, a first radio frequency (RF)-based positioning configuration responsive to the first perception-based positioning-related information.

[0401] Clause 88. The network entity of clause 87, wherein the one or more processors, either alone or in combination, are further configured to: determine that the first RF-based positioning configuration is expected to improve the metric corresponding to the one or more DoF parameters, wherein the first RF-based positioning configuration is transmitted based on the determining.

[0402] Clause 89. The network entity of any of clauses 87 to 88, wherein the one or more processors, either alone or in combination, are further configured to: determine to trigger an RF-based position estimation session of the first UE using the first RF-based positioning configuration based on the first perception-based positioning-related information.

[0403] Clause 90. The network entity of any of clauses 87 to 89, wherein the one or more processors, either alone or in combination, are further configured to: determine to update quasi-collocation (QCL) information associated with one or more transmission beams based on the received first perception-based positioning-related information, wherein the first RF-based positioning configuration includes positioning reference signal (PRS) resources based on the updated QCL information.

[0404] Clause 91. The network entity of any of clauses 87 to 90, wherein the one or more processors, either alone or in combination, are further configured to: transmit, via the one or more transceivers, positioning assistance data based on at least some information corresponding to the first perception-based positioning-related information to a second UE different from the first UE.

[0405] Clause 92. The network entity of any of clauses 87 to 91, wherein the one or more processors, either alone or in combination, are further configured to: transmit, via the one or more transceivers, a second RF-based positioning configuration to a second UE different from the first UE based on the received first perception-based positioning- related information from the first UE.

[0406] Clause 93. The network entity of clause 92, wherein the second RF -based positioning configuration comprises second positioning reference signal (PRS) resources configured with at least one of a second bandwidth, a second periodicity, or a second comb pattern different from a corresponding prior bandwidth, prior periodicity, or prior comb pattern of PRS resources of a prior RF -based positioning configuration of the second UE.

[0407] Clause 94. The network entity of any of clauses 87 to 93, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, from a second UE, second perception-based positioning-related information; and refrain from transmitting an RF -based positioning configuration based on second perception-based positioning-related information.

[0408] Clause 95. The network entity of clause 94, wherein the one or more processors, either alone or in combination, are further configured to: determine that the RF-based positioning configuration is not expected to improve the metric corresponding to the one or more DoF parameters, wherein the refraining from transmitting the RF-based positioning configuration is based on the determining.

[0409] Clause 96. The network entity of any of clauses 87 to 95, wherein the received first perception-based positioning-related information comprises sensor information from one or more sensors of the first UE.

[0410] Clause 97. The network entity of any of clauses 87 to 96, wherein the one or more processors, either alone or in combination, are further configured to: transmit, via the one or more transceivers, to the first UE, a request for perception-based positioning-related information based on the metric corresponding to the one or more DoF parameters managed by the network entity.

[0411] Clause 98. The network entity of clause 97, wherein the request for the perception-based positioning-related information includes a request for DoF information corresponding to orientation information of the first UE different from position information of the first UE.

[0412] Clause 99. The network entity of any of clauses 87 to 98, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, from the first UE, a capability indication of support for perceptionbased positioning; and store the capability indication as a configuration associated with the one or more DoF parameters.

[0413] Clause 100. The network entity of any of clauses 87 to 99, wherein the one or more processors, either alone or in combination, are further configured to: determine one or more positioning reference signal (PRS) resource sets associated with the first RF -based positioning configuration and / or a prioritization of the one or more PRS resource sets, based on the perception-based positioning-related information.

[0414] Clause 101. The network entity of any of clauses 87 to 100, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, from a device running an extended reality (XR) or metaverse-based application, the metric corresponding to the one or more DoF parameters.

[0415] Clause 102. The network entity of any of clauses 87 to 101, wherein the network entity comprises a location management function (LMF) or a session management function (SMF).

[0416] Clause 103. A user equipment (UE), comprising: means for transmitting, to a network entity, perception-based positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters, wherein the perception-based positioning-related information is obtained by a modem of the UE through a cross-layer application programming interface (API); and means for receiving, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the perception-based positioning-related information.

[0417] Clause 104. The UE of clause 103, wherein the cross-layer API is between the modem and an interactive application running on the UE.

[0418] Clause 105. The UE of any of clauses 103 to 104, wherein the perception-based positioning-related information comprises a request for positioning reference signal (PRS) resources on one or more transmission beams.

[0419] Clause 106. The UE of any of clauses 103 to 105, wherein the perception-based positioning-related information comprises UE assistance data in an on-demand positioning reference signal (PRS) procedure.

[0420] Clause 107. The UE of any of clauses 103 to 106, wherein the perception-based positioning-related information comprises UE assistance data in an on-demand positioning reference signal (PRS) procedure.

[0421] Clause 108. The UE of clause 107, wherein the RF-based positioning configuration indicates one or more PRS resources configured to improve the metric corresponding to the one or more DoF parameters.

[0422] Clause 109. The UE of clause 108, wherein the configured one or more PRS resources are associated with at least one directional downlink PRS (DL-PRS) beam from a transmission reception point (TRP) based on a location of the UE, a characteristic of the one or more DoF parameters, or both.

[0423] Clause 110. The UE of any of clauses 103 to 109, wherein the perception-based positioning-related information comprises an achieved key performance indicator (KPI) associated with the metric corresponding to the one or more DoF parameters.

[0424] Clause 111. The UE of clause 110, wherein the achieved KPI associated with the metric is based on a KPI value determination absent positioning information from the network entity.

[0425] Clause 112. The UE of any of clauses 103 to 111, wherein the perception-based positioning-related information comprises a desired key performance indicator (KPI) or KPI range associated with the metric corresponding to the one or more DoF parameters.

[0426] Clause 113. The UE of any of clauses 103 to 112, wherein the perception-based positioning-related information comprises: data associated with one or more perceptionbased components of the UE, a resolution of the one or more perception-based components, a rate of the one or more perception-based components, or a combination thereof.

[0427] Clause 114. The UE of any of clauses 103 to 113, further comprising: means for receiving an indication from the network entity that the RF-based positioning configuration is expected to satisfy the metric corresponding to the one or more DoF parameters.

[0428] Clause 115. The UE of any of clauses 103 to 114, wherein the perception-based positioning-related information is associated with information corresponding to one or more DoF that includes orientation information of the UE different from position information of the UE.

[0429] Clause 116. The UE of clause 115, wherein the orientation information of the UE comprises DoF information corresponding to one or more of a pitch, a yaw, or a roll.

[0430] Clause 117. The UE of any of clauses 115 to 116, wherein the RF-based positioning configuration comprises positioning reference signal (PRS) resources on one or more transmission beams with updated quasi-collocation (QCL) information based on the orientation information of the UE.

[0431] Clause 118. The UE of any of clauses 115 to 117, further comprising: means for receiving a first prioritization of a plurality of positioning reference signal (PRS) resource sets associated with the RF-based positioning configuration, wherein the first prioritization is based on the orientation information of the UE.

[0432] Clause 119. The UE of clause 118, further comprising: means for receiving a second prioritization of the plurality of PRS resource sets associated with the RF-based positioning configuration, wherein the second prioritization is based on the position information of the UE and different from the first prioritization.

[0433] Clause 120. The UE of any of clauses 115 to 119, wherein the RF-based positioning configuration comprises one or more sets of sounding reference signal (SRS) resources based on the orientation information of the UE.

[0434] Clause 121. The UE of any of clauses 103 to 120, further comprising: means for refraining from using at least one sensor of the UE based on the received RF-based positioning configuration.

[0435] Clause 122. The UE of clause 121, wherein the at least one sensor was used in at least one perception-based positioning determination prior to a transmission of the perceptionbased positioning-related information.

[0436] Clause 123. The UE of any of clauses 103 to 122, further comprising: means for transmitting a capability indication of support for perception-based positioning, or means for transmitting a capability message of capabilities supported for perception-based positioning.

[0437] Clause 124. The UE of clause 123, wherein the capability indication is transmitted responsive to a capability request from the network entity, or the capability message is transmitted responsive to a capability request from the network entity.

[0438] Clause 125. The UE of any of clauses 123 to 124, wherein the capability indication is stored at the network entity as a configuration associated with the one or more DoFparameters, or the capability message is stored at the network entity as a configuration associated with the one or more DoF parameters.

[0439] Clause 126. The UE of any of clauses 103 to 125, further comprising: means for receiving, from the network entity, a reporting request indicating the UE to include the perceptionbased positioning-related information in a positioning measurement report, wherein the perception-based positioning-related information is transmitted responsive to the reporting request.

[0440] Clause 127. The UE of clause 126, wherein the transmitting, to the network entity, the perception-based positioning-related information comprises: means for transmitting, to the network entity, the positioning measurement report to include the perception-based positioning-related information; or means for transmitting, to the network entity, the positioning measurement report to include an error indication corresponding to a perception-based component.

[0441] Clause 128. The UE of clause 127, wherein the error indication corresponding to the perception-based component in the positioning measurement report indicates to the network entity that at least some information corresponding to perception-based positioning measurements by the UE is unavailable.

[0442] Clause 129. The UE of any of clauses 126 to 128, further comprising: means for performing measurements for the positioning measurement report using one or more positioning measurement gaps associated with a positioning measurement gap configuration, wherein the measurements for the positioning measurement report are performed using the one or more positioning measurement gaps based on an inclusion of the perception-based positioning-related information in the positioning measurement report; and means for transmitting, to the network entity, an indication that the UE used the one or more positioning measurement gaps associated with the positioning measurement gap configuration to perform the measurements for the positioning measurement report.

[0443] Clause 130. The UE of clause 129, wherein: a first measurement gap length of the one or more positioning measurement gaps is greater than a second measurement gap length of second positioning measurement gaps associated with the positioning measurement gap configuration; and the second positioning measurement gaps are for a second positioningmeasurement report that does not include measurements corresponding to the perceptionbased positioning-related information.

[0444] Clause 131. The UE of any of clauses 103 to 130, further comprising: means for transmitting data on a physical uplink shared channel (PUSCH) during at least one positioning measurement gap associated with a positioning measurement gap configuration; and means for transmitting a positioning measurement report based on perception-based components of the UE.

[0445] Clause 132. The UE of clause 131, wherein at least one measurement indication of the positioning measurement report is determined absent reference signals associated with the positioning measurement gap configuration.

[0446] Clause 133. The UE of any of clauses 103 to 132, further comprising: means for transmitting an indication that the UE is refraining from using at least one positioning measurement gap associated with a positioning measurement gap configuration.

[0447] Clause 134. The UE of clause 133, wherein the indication that the UE is refraining from using the at least one positioning measurement gap is transmitted based on a determination that the metric corresponding to the one or more DoF parameters is satisfied.

[0448] Clause 135. The UE of any of clauses 103 to 134, further comprising: means for receiving an indication corresponding to a number of positioning measurement reports for which the UE is to use perception-based components.

[0449] Clause 136. The UE of any of clauses 103 to 135, wherein the UE comprises a perception entity.

[0450] Clause 137. The UE of any of clauses 103 to 136, wherein the UE is running an extended reality (XR) or metaverse-based application that utilizes at least one sensor of the UE.

[0451] Clause 138. A network entity, comprising: means for receiving, from a first user equipment (UE), first perception-based positioning-related information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters; and means for transmitting, to the first UE, a first radio frequency (RF)-based positioning configuration responsive to the first perception-based positioning-related information.

[0452] Clause 139. The network entity of clause 138, further comprising: means for determining that the first RF-based positioning configuration is expected to improve the metriccorresponding to the one or more DoF parameters, wherein the first RF -based positioning configuration is transmitted based on the determining.

[0453] Clause 140. The network entity of any of clauses 138 to 139, further comprising: means for determining to trigger an RF -based position estimation session of the first UE using the first RF-based positioning configuration based on the first perception-based positioning-related information.

[0454] Clause 141. The network entity of any of clauses 138 to 140, further comprising: means for determining to update quasi-collocation (QCL) information associated with one or more transmission beams based on the received first perception-based positioning-related information, wherein the first RF-based positioning configuration includes positioning reference signal (PRS) resources based on the updated QCL information.

[0455] Clause 142. The network entity of any of clauses 138 to 141, further comprising: means for transmitting positioning assistance data based on at least some information corresponding to the first perception-based positioning-related information to a second UE different from the first UE.

[0456] Clause 143. The network entity of any of clauses 138 to 142, further comprising: means for transmitting a second RF-based positioning configuration to a second UE different from the first UE based on the received first perception-based positioning-related information from the first UE.

[0457] Clause 144. The network entity of clause 143, wherein the second RF-based positioning configuration comprises second positioning reference signal (PRS) resources configured with at least one of a second bandwidth, a second periodicity, or a second comb pattern different from a corresponding prior bandwidth, prior periodicity, or prior comb pattern of PRS resources of a prior RF-based positioning configuration of the second UE.

[0458] Clause 145. The network entity of any of clauses 138 to 144, further comprising: means for receiving, from a second UE, second perception-based positioning-related information; and means for refraining from transmitting an RF-based positioning configuration based on second perception-based positioning-related information.

[0459] Clause 146. The network entity of clause 145, further comprising: means for determining that the RF-based positioning configuration is not expected to improve the metric corresponding to the one or more DoF parameters, wherein the refraining from transmitting the RF-based positioning configuration is based on the determining.

[0460] Clause 147. The network entity of any of clauses 138 to 146, wherein the received first perception-based positioning-related information comprises sensor information from one or more sensors of the first UE.

[0461] Clause 148. The network entity of any of clauses 138 to 147, further comprising: means for transmitting, to the first UE, a request for perception-based positioning-related information based on the metric corresponding to the one or more DoF parameters managed by the network entity.

[0462] Clause 149. The network entity of clause 148, wherein the request for the perceptionbased positioning-related information includes a request for DoF information corresponding to orientation information of the first UE different from position information of the first UE.

[0463] Clause 150. The network entity of any of clauses 138 to 149, further comprising: means for receiving, from the first UE, a capability indication of support for perception-based positioning; and means for storing the capability indication as a configuration associated with the one or more DoF parameters.

[0464] Clause 151. The network entity of any of clauses 138 to 150, further comprising: means for determining one or more positioning reference signal (PRS) resource sets associated with the first RF -based positioning configuration and / or a prioritization of the one or more PRS resource sets, based on the perception-based positioning-related information.

[0465] Clause 152. The network entity of any of clauses 138 to 151, further comprising: means for receiving, from a device running an extended reality (XR) or metaverse-based application, the metric corresponding to the one or more DoF parameters.

[0466] Clause 153. The network entity of any of clauses 138 to 152, wherein the network entity comprises a location management function (LMF) or a session management function (SMF).

[0467] Clause 154. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: transmit, to a network entity, perception-based positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters, wherein the perception-based positioning-related information is obtained by a modem of the UE through a cross-layer application programming interface(API); and receive, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the perception-based positioning-related information.

[0468] Clause 155. The non-transitory computer-readable medium of clause 154, wherein the cross-layer API is between the modem and an interactive application running on the UE.

[0469] Clause 156. The non-transitory computer-readable medium of any of clauses 154 to 155, wherein the perception-based positioning-related information comprises a request for positioning reference signal (PRS) resources on one or more transmission beams.

[0470] Clause 157. The non-transitory computer-readable medium of any of clauses 154 to 156, wherein the perception-based positioning-related information comprises UE assistance data in an on-demand positioning reference signal (PRS) procedure.

[0471] Clause 158. The non-transitory computer-readable medium of any of clauses 154 to 157, wherein the perception-based positioning-related information comprises UE assistance data in an on-demand positioning reference signal (PRS) procedure.

[0472] Clause 159. The non-transitory computer-readable medium of clause 158, wherein the RF-based positioning configuration indicates one or more PRS resources configured to improve the metric corresponding to the one or more DoF parameters.

[0473] Clause 160. The non-transitory computer-readable medium of clause 159, wherein the configured one or more PRS resources are associated with at least one directional downlink PRS (DL-PRS) beam from a transmission reception point (TRP) based on a location of the UE, a characteristic of the one or more DoF parameters, or both.

[0474] Clause 161. The non-transitory computer-readable medium of any of clauses 154 to 160, wherein the perception-based positioning-related information comprises an achieved key performance indicator (KPI) associated with the metric corresponding to the one or more DoF parameters.

[0475] Clause 162. The non-transitory computer-readable medium of clause 161, wherein the achieved KPI associated with the metric is based on a KPI value determination absent positioning information from the network entity.

[0476] Clause 163. The non-transitory computer-readable medium of any of clauses 154 to 162, wherein the perception-based positioning-related information comprises a desired key performance indicator (KPI) or KPI range associated with the metric corresponding to the one or more DoF parameters.

[0477] Clause 164. The non-transitory computer-readable medium of any of clauses 154 to 163, wherein the perception-based positioning-related information comprises: data associated with one or more perception-based components of the UE, a resolution of the one or more perception-based components, a rate of the one or more perception-based components, or a combination thereof.

[0478] Clause 165. The non-transitory computer-readable medium of any of clauses 154 to 164, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: receive an indication from the network entity that the RF-based positioning configuration is expected to satisfy the metric corresponding to the one or more DoF parameters.

[0479] Clause 166. The non-transitory computer-readable medium of any of clauses 154 to 165, wherein the perception-based positioning-related information is associated with information corresponding to one or more DoF that includes orientation information of the UE different from position information of the UE.

[0480] Clause 167. The non-transitory computer-readable medium of clause 166, wherein the orientation information of the UE comprises DoF information corresponding to one or more of a pitch, a yaw, or a roll.

[0481] Clause 168. The non-transitory computer-readable medium of any of clauses 166 to 167, wherein the RF-based positioning configuration comprises positioning reference signal (PRS) resources on one or more transmission beams with updated quasi-collocation (QCL) information based on the orientation information of the UE.

[0482] Clause 169. The non-transitory computer-readable medium of any of clauses 166 to 168, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: receive a first prioritization of a plurality of positioning reference signal (PRS) resource sets associated with the RF-based positioning configuration, wherein the first prioritization is based on the orientation information of the UE.

[0483] Clause 170. The non-transitory computer-readable medium of clause 169, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: receive a second prioritization of the plurality of PRS resource sets associated with the RF-based positioning configuration, wherein the second prioritization is based on the position information of the UE and different from the first prioritization.

[0484] Clause 171. The non-transitory computer-readable medium of any of clauses 166 to 170, wherein the RF -based positioning configuration comprises one or more sets of sounding reference signal (SRS) resources based on the orientation information of the UE.

[0485] Clause 172. The non-transitory computer-readable medium of any of clauses 154 to 171, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: refrain from using at least one sensor of the UE based on the received RF-based positioning configuration.

[0486] Clause 173. The non-transitory computer-readable medium of clause 172, wherein the at least one sensor was used in at least one perception-based positioning determination prior to a transmission of the perception-based positioning-related information.

[0487] Clause 174. The non-transitory computer-readable medium of any of clauses 154 to 173, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: transmit a capability indication of support for perception-based positioning, or transmit a capability message of capabilities supported for perceptionbased positioning.

[0488] Clause 175. The non-transitory computer-readable medium of clause 174, wherein the capability indication is transmitted responsive to a capability request from the network entity, or the capability message is transmitted responsive to a capability request from the network entity.

[0489] Clause 176. The non-transitory computer-readable medium of any of clauses 174 to 175, wherein the capability indication is stored at the network entity as a configuration associated with the one or more DoF parameters, or the capability message is stored at the network entity as a configuration associated with the one or more DoF parameters.

[0490] Clause 177. The non-transitory computer-readable medium of any of clauses 154 to 176, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: receive, from the network entity, a reporting request indicating the UE to include the perception-based positioning-related information in a positioning measurement report, wherein the perception-based positioning-related information is transmitted responsive to the reporting request.

[0491] Clause 178. The non-transitory computer-readable medium of clause 177, wherein the transmitting, to the network entity, the perception-based positioning-related information comprises: transmit, to the network entity, the positioning measurement report to includethe perception-based positioning-related information; or transmit, to the network entity, the positioning measurement report to include an error indication corresponding to a perception-based component.

[0492] Clause 179. The non-transitory computer-readable medium of clause 178, wherein the error indication corresponding to the perception-based component in the positioning measurement report indicates to the network entity that at least some information corresponding to perception-based positioning measurements by the UE is unavailable.

[0493] Clause 180. The non-transitory computer-readable medium of any of clauses 177 to 179, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: perform measurements for the positioning measurement report using one or more positioning measurement gaps associated with a positioning measurement gap configuration, wherein the measurements for the positioning measurement report are performed using the one or more positioning measurement gaps based on an inclusion of the perception-based positioning-related information in the positioning measurement report; and transmit, to the network entity, an indication that the UE used the one or more positioning measurement gaps associated with the positioning measurement gap configuration to perform the measurements for the positioning measurement report.

[0494] Clause 181. The non-transitory computer-readable medium of clause 180, wherein: a first measurement gap length of the one or more positioning measurement gaps is greater than a second measurement gap length of second positioning measurement gaps associated with the positioning measurement gap configuration; and the second positioning measurement gaps are for a second positioning measurement report that does not include measurements corresponding to the perception-based positioning-related information.

[0495] Clause 182. The non-transitory computer-readable medium of any of clauses 154 to 181, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: transmit data on a physical uplink shared channel (PUSCH) during at least one positioning measurement gap associated with a positioning measurement gap configuration; and transmit a positioning measurement report based on perception-based components of the UE.

[0496] Clause 183. The non-transitory computer-readable medium of clause 182, wherein at least one measurement indication of the positioning measurement report is determined absent reference signals associated with the positioning measurement gap configuration.

[0497] Clause 184. The non-transitory computer-readable medium of any of clauses 154 to 183, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: transmit an indication that the UE is refraining from using at least one positioning measurement gap associated with a positioning measurement gap configuration.

[0498] Clause 185. The non-transitory computer-readable medium of clause 184, wherein the indication that the UE is refraining from using the at least one positioning measurement gap is transmitted based on a determination that the metric corresponding to the one or more DoF parameters is satisfied.

[0499] Clause 186. The non-transitory computer-readable medium of any of clauses 154 to 185, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: receive an indication corresponding to a number of positioning measurement reports for which the UE is to use perception-based components.

[0500] Clause 187. The non-transitory computer-readable medium of any of clauses 154 to 186, wherein the UE comprises a perception entity.

[0501] Clause 188. The non-transitory computer-readable medium of any of clauses 154 to 187, wherein the UE is running an extended reality (XR) or metaverse-based application that utilizes at least one sensor of the UE.

[0502] Clause 189. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network entity, cause the network entity to: receive, from a first user equipment (UE), first perception-based positioning-related information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters; and transmit, to the first UE, a first radio frequency (RF)-based positioning configuration responsive to the first perception-based positioning-related information.

[0503] Clause 190. The non-transitory computer-readable medium of clause 189, further comprising computer-executable instructions that, when executed by the network entity, cause the network entity to: determine that the first RF-based positioning configuration is expected to improve the metric corresponding to the one or more DoF parameters, wherein the first RF-based positioning configuration is transmitted based on the determining.

[0504] Clause 191. The non-transitory computer-readable medium of any of clauses 189 to 190, further comprising computer-executable instructions that, when executed by the networkentity, cause the network entity to: determine to trigger an RF-based position estimation session of the first UE using the first RF-based positioning configuration based on the first perception-based positioning-related information.

[0505] Clause 192. The non-transitory computer-readable medium of any of clauses 189 to 191, further comprising computer-executable instructions that, when executed by the network entity, cause the network entity to: determine to update quasi-collocation (QCL) information associated with one or more transmission beams based on the received first perception-based positioning-related information, wherein the first RF-based positioning configuration includes positioning reference signal (PRS) resources based on the updated QCL information.

[0506] Clause 193. The non-transitory computer-readable medium of any of clauses 189 to 192, further comprising computer-executable instructions that, when executed by the network entity, cause the network entity to: transmit positioning assistance data based on at least some information corresponding to the first perception-based positioning-related information to a second UE different from the first UE.

[0507] Clause 194. The non-transitory computer-readable medium of any of clauses 189 to 193, further comprising computer-executable instructions that, when executed by the network entity, cause the network entity to: transmit a second RF-based positioning configuration to a second UE different from the first UE based on the received first perception-based positioning-related information from the first UE.

[0508] Clause 195. The non-transitory computer-readable medium of clause 194, wherein the second RF-based positioning configuration comprises second positioning reference signal (PRS) resources configured with at least one of a second bandwidth, a second periodicity, or a second comb pattern different from a corresponding prior bandwidth, prior periodicity, or prior comb pattern of PRS resources of a prior RF-based positioning configuration of the second UE.

[0509] Clause 196. The non-transitory computer-readable medium of any of clauses 189 to 195, further comprising computer-executable instructions that, when executed by the network entity, cause the network entity to: receive, from a second UE, second perception-based positioning-related information; and refrain from transmitting an RF-based positioning configuration based on second perception-based positioning-related information.

[0510] Clause 197. The non-transitory computer-readable medium of clause 196, further comprising computer-executable instructions that, when executed by the network entity, cause the network entity to: determine that the RF-based positioning configuration is not expected to improve the metric corresponding to the one or more DoF parameters, wherein the refraining from transmitting the RF-based positioning configuration is based on the determining.

[0511] Clause 198. The non-transitory computer-readable medium of any of clauses 189 to 197, wherein the received first perception-based positioning-related information comprises sensor information from one or more sensors of the first UE.

[0512] Clause 199. The non-transitory computer-readable medium of any of clauses 189 to 198, further comprising computer-executable instructions that, when executed by the network entity, cause the network entity to: transmit, to the first UE, a request for perception-based positioning-related information based on the metric corresponding to the one or more DoF parameters managed by the network entity.

[0513] Clause 200. The non-transitory computer-readable medium of clause 199, wherein the request for the perception-based positioning-related information includes a request for DoF information corresponding to orientation information of the first UE different from position information of the first UE.

[0514] Clause 201. The non-transitory computer-readable medium of any of clauses 189 to 200, further comprising computer-executable instructions that, when executed by the network entity, cause the network entity to: receive, from the first UE, a capability indication of support for perception-based positioning; and store the capability indication as a configuration associated with the one or more DoF parameters.

[0515] Clause 202. The non-transitory computer-readable medium of any of clauses 189 to 201, further comprising computer-executable instructions that, when executed by the network entity, cause the network entity to: determine one or more positioning reference signal (PRS) resource sets associated with the first RF-based positioning configuration and / or a prioritization of the one or more PRS resource sets, based on the perception-based positioning-related information.

[0516] Clause 203. The non-transitory computer-readable medium of any of clauses 189 to 202, further comprising computer-executable instructions that, when executed by the network entity, cause the network entity to: receive, from a device running an extended realityI l l(XR) or metaverse-based application, the metric corresponding to the one or more DoF parameters.

[0517] Clause 204. The non-transitory computer-readable medium of any of clauses 189 to 203, wherein the network entity comprises a location management function (LMF) or a session management function (SMF).

[0518] Clause 205. A method of wireless communication performed by a user equipment (UE), comprising: transmitting, to a network entity, positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters related to at least one of a position or an orientation of the UE; and receiving, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the positioning-related information.

[0519] Clause 206. The method of clause 205, wherein the positioning-related information is provided through a cross-layer application programming interface (API) associated with an interactive application.

[0520] Clause 207. The method of any of clauses 205 to 206, wherein the positioning-related information comprises a request for positioning reference signal (PRS) resources on one or more transmission beams.

[0521] Clause 208. The method of any of clauses 205 to 207, wherein the positioning-related information comprises UE assistance data in an on-demand positioning reference signal (PRS) procedure.

[0522] Clause 209. The method of any of clauses 205 to 208, wherein the positioning-related information comprises: data associated with one or more perception-based components of the UE, a resolution of the one or more perception-based components, a rate of the one or more perception-based components, or a combination thereof.

[0523] Clause 210. The method of any of clauses 205 to 209, wherein the positioning-related information is associated with information corresponding to one or more DoF that includes orientation information of the UE different from position information of the UE.

[0524] Clause 211. The method of any of clauses 205 to 210, further comprising: receiving, from the network entity, a reporting request to include the positioning-related information in a positioning measurement report, wherein the positioning-related information is transmitted responsive to the reporting request.

[0525] Clause 212. The method of clause 211, wherein the transmitting, to the network entity, the positioning-related information comprises: transmitting, to the network entity, the positioning measurement report to include the positioning-related information; or transmitting, to the network entity, the positioning measurement report to include an error indication corresponding to a component.

[0526] Clause 213. The method of any of clauses 211 to 212, further comprising: performing measurements for the positioning measurement report using one or more positioning measurement gaps associated with a positioning measurement gap configuration, wherein the measurements for the positioning measurement report are performed using the one or more positioning measurement gaps based on an inclusion of the positioning-related information in the positioning measurement report; and transmitting, to the network entity, an indication that the UE used the one or more positioning measurement gaps associated with the positioning measurement gap configuration to perform the measurements for the positioning measurement report.

[0527] Clause 214. The method of clause 213, wherein: a first measurement gap length of the one or more positioning measurement gaps is different than a second measurement gap length of second positioning measurement gaps associated with the positioning measurement gap configuration; and the second positioning measurement gaps are for a second positioning measurement report that does not include measurements corresponding to the positioning-related information.

[0528] Clause 215. A user equipment (UE), comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: transmit, via the one or more transceivers, to a network entity, positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters related to at least one of a position or an orientation of the UE; and receive, via the one or more transceivers, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the positioning-related information.

[0529] Clause 216. The UE of clause 215, wherein the positioning-related information is provided through a cross-layer application programming interface (API) associated with an interactive application.

[0530] Clause 217. The UE of any of clauses 215 to 216, wherein the positioning-related information comprises a request for positioning reference signal (PRS) resources on one or more transmission beams.

[0531] Clause 218. The UE of any of clauses 215 to 217, wherein the positioning-related information comprises UE assistance data in an on-demand positioning reference signal (PRS) procedure.

[0532] Clause 219. The UE of any of clauses 215 to 218, wherein the positioning-related information comprises: data associated with one or more perception-based components of the UE, a resolution of the one or more perception-based components, a rate of the one or more perception-based components, or a combination thereof.

[0533] Clause 220. The UE of any of clauses 215 to 219, wherein the positioning-related information is associated with information corresponding to one or more DoF that includes orientation information of the UE different from position information of the UE.

[0534] Clause 221. The UE of any of clauses 215 to 220, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, from the network entity, a reporting request to include the positioning- related information in a positioning measurement report, wherein the positioning-related information is transmitted responsive to the reporting request.

[0535] Clause 222. The UE of clause 221, wherein the transmitting, to the network entity, the positioning-related information comprises: transmit, via the one or more transceivers, to the network entity, the positioning measurement report to include the positioning-related information; or transmit, via the one or more transceivers, to the network entity, the positioning measurement report to include an error indication corresponding to a component.

[0536] Clause 223. The UE of any of clauses 221 to 222, wherein the one or more processors, either alone or in combination, are further configured to: perform measurements for the positioning measurement report using one or more positioning measurement gaps associated with a positioning measurement gap configuration, wherein the measurements for the positioning measurement report are performed using the one or more positioning measurement gaps based on an inclusion of the positioning-related information in the positioning measurement report; and transmit, via the one or more transceivers, to the network entity, an indication that the UE used the one or more positioning measurementgaps associated with the positioning measurement gap configuration to perform the measurements for the positioning measurement report.

[0537] Clause 224. The UE of clause 223, wherein: a first measurement gap length of the one or more positioning measurement gaps is different than a second measurement gap length of second positioning measurement gaps associated with the positioning measurement gap configuration; and the second positioning measurement gaps are for a second positioning measurement report that does not include measurements corresponding to the positioning-related information.

[0538] Clause 225. A user equipment (UE), comprising: means for transmitting, to a network entity, positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters related to at least one of a position or an orientation of the UE; and means for receiving, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the positioning- related information.

[0539] Clause 226. The UE of clause 225, wherein the positioning-related information is provided through a cross-layer application programming interface (API) associated with an interactive application.

[0540] Clause 227. The UE of any of clauses 225 to 226, wherein the positioning-related information comprises a request for positioning reference signal (PRS) resources on one or more transmission beams.

[0541] Clause 228. The UE of any of clauses 225 to 227, wherein the positioning-related information comprises UE assistance data in an on-demand positioning reference signal (PRS) procedure.

[0542] Clause 229. The UE of any of clauses 225 to 228, wherein the positioning-related information comprises: data associated with one or more perception-based components of the UE, a resolution of the one or more perception-based components, a rate of the one or more perception-based components, or a combination thereof.

[0543] Clause 230. The UE of any of clauses 225 to 229, wherein the positioning-related information is associated with information corresponding to one or more DoF that includes orientation information of the UE different from position information of the UE.

[0544] Clause 231. The UE of any of clauses 225 to 230, further comprising: means for receiving, from the network entity, a reporting request to include the positioning-related informationin a positioning measurement report, wherein the positioning-related information is transmitted responsive to the reporting request.

[0545] Clause 232. The UE of clause 231, wherein the transmitting, to the network entity, the positioning-related information comprises: means for transmitting, to the network entity, the positioning measurement report to include the positioning-related information; or means for transmitting, to the network entity, the positioning measurement report to include an error indication corresponding to a component.

[0546] Clause 233. The UE of any of clauses 231 to 232, further comprising: means for performing measurements for the positioning measurement report using one or more positioning measurement gaps associated with a positioning measurement gap configuration, wherein the measurements for the positioning measurement report are performed using the one or more positioning measurement gaps based on an inclusion of the positioning-related information in the positioning measurement report; and means for transmitting, to the network entity, an indication that the UE used the one or more positioning measurement gaps associated with the positioning measurement gap configuration to perform the measurements for the positioning measurement report.

[0547] Clause 234. The UE of clause 233, wherein: a first measurement gap length of the one or more positioning measurement gaps is different than a second measurement gap length of second positioning measurement gaps associated with the positioning measurement gap configuration; and the second positioning measurement gaps are for a second positioning measurement report that does not include measurements corresponding to the positioning-related information.

[0548] Clause 235. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: transmit, to a network entity, positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters related to at least one of a position or an orientation of the UE; and receive, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the positioning- related information.

[0549] Clause 236. The non-transitory computer-readable medium of clause 235, wherein the positioning-related information is provided through a cross-layer application programming interface (API) associated with an interactive application.

[0550] Clause 237. The non-transitory computer-readable medium of any of clauses 235 to 236, wherein the positioning-related information comprises a request for positioning reference signal (PRS) resources on one or more transmission beams.

[0551] Clause 238. The non-transitory computer-readable medium of any of clauses 235 to 237, wherein the positioning-related information comprises UE assistance data in an on- demand positioning reference signal (PRS) procedure.

[0552] Clause 239. The non-transitory computer-readable medium of any of clauses 235 to 238, wherein the positioning-related information comprises: data associated with one or more perception-based components of the UE, a resolution of the one or more perception-based components, a rate of the one or more perception-based components, or a combination thereof.

[0553] Clause 240. The non-transitory computer-readable medium of any of clauses 235 to 239, wherein the positioning-related information is associated with information corresponding to one or more DoF that includes orientation information of the UE different from position information of the UE.

[0554] Clause 241. The non-transitory computer-readable medium of any of clauses 235 to 240, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: receive, from the network entity, a reporting request to include the positioning-related information in a positioning measurement report, wherein the positioning-related information is transmitted responsive to the reporting request.

[0555] Clause 242. The non-transitory computer-readable medium of clause 241, wherein the transmitting, to the network entity, the positioning-related information comprises: transmit, to the network entity, the positioning measurement report to include the positioning-related information; or transmit, to the network entity, the positioning measurement report to include an error indication corresponding to a component.

[0556] Clause 243. The non-transitory computer-readable medium of any of clauses 241 to 242, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: perform measurements for the positioning measurement report using one or more positioning measurement gaps associated with a positioning measurement gap configuration, wherein the measurements for the positioning measurement report are performed using the one or more positioning measurement gaps based on an inclusion of the positioning-related information in the positioning measurement report; and transmit,to the network entity, an indication that the UE used the one or more positioning measurement gaps associated with the positioning measurement gap configuration to perform the measurements for the positioning measurement report.

[0557] Clause 244. The non-transitory computer-readable medium of clause 243, wherein: a first measurement gap length of the one or more positioning measurement gaps is different than a second measurement gap length of second positioning measurement gaps associated with the positioning measurement gap configuration; and the second positioning measurement gaps are for a second positioning measurement report that does not include measurements corresponding to the positioning-related information.

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

[0559] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field-programable 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 the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0560] The methods, sequences and / or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard 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 such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to 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 the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

[0561] In one or more example aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes 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.

[0562] While the foregoing disclosure shows illustrative aspects of the disclosure, it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. For example, the functions, steps and / or actions of the method claims in accordance with the aspects of the disclosure described herein need not be performed in any particular order. Further, no component, function, action, or instruction described or claimed herein should be construed as critical or essential unless explicitly described as such. Furthermore, as used herein, the terms “set,” “group,” and the like are intended to include one or more of the stated elements. Also, as used herein, the terms “has,” “have,” “having,” “comprises,” “comprising,” “includes,” “including,” and the like does not preclude the presence of one or more additional elements (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of’) or the alternatives are mutually exclusive (e.g., “one or more” should ...

Claims

CLAIMSWhat is claimed is:

1. A method of wireless communication performed by a user equipment (UE), comprising: transmitting, to a network entity, perception-based positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters, wherein the perception-based positioning- related information is obtained by a modem of the UE through a cross-layer application programming interface (API); and receiving, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the perception-based positioning-related information.

2. The method of claim 1, wherein the cross-layer API is between the modem and an interactive application running on the UE.

3. The method of claim 1, wherein the perception-based positioning-related information comprises a request for positioning reference signal (PRS) resources on one or more transmission beams.

4. The method of claim 1, wherein the one or more DoF parameters relate to at least one of a position or an orientation of the UE.

5. The method of claim 1, wherein the perception-based positioning-related information comprises UE assistance data in an on-demand positioning reference signal (PRS) procedure.

6. The method of claim 5, wherein the RF-based positioning configuration indicates one or more PRS resources configured to improve the metric corresponding to the one or more DoF parameters.

7. The method of claim 6, wherein the configured one or more PRS resources are associated with at least one directional downlink PRS (DL-PRS) beam from atransmission reception point (TRP) based on a location of the UE, a characteristic of the one or more DoF parameters, or both.

8. The method of claim 1, wherein the perception-based positioning-related information comprises: data associated with one or more perception-based components of the UE, a resolution of the one or more perception-based components, a rate of the one or more perception-based components, or a combination thereof.

9. The method of claim 1, wherein the perception-based positioning-related information is associated with information corresponding to one or more DoF that includes orientation information of the UE different from position information of the UE.

10. The method of claim 9, wherein the orientation information of the UE comprises DoF information corresponding to one or more of a pitch, a yaw, or a roll.

11. The method of claim 9, wherein the RF -based positioning configuration comprises positioning reference signal (PRS) resources on one or more transmission beams with updated quasi-collocation (QCL) information based on the orientation information of the UE.

12. The method of claim 9, wherein the RF-based positioning configuration comprises one or more sets of sounding reference signal (SRS) resources based on the orientation information of the UE.

13. The method of claim 1, further comprising: transmitting a capability indication of support for perception-based positioning.

14. The method of claim 13, wherein the capability indication is transmitted responsive to a capability request from the network entity.

15. The method of claim 13, wherein the capability indication is stored at the network entity as a configuration associated with the one or more DoF parameters.

16. The method of claim 1, further comprising: receiving, from the network entity, a reporting request indicating the UE to include the perception-based positioning-related information in a positioning measurement report, wherein the perception-based positioning-related information is transmitted responsive to the reporting request.

17. The method of claim 16, wherein the transmitting, to the network entity, the perception-based positioning-related information comprises: transmitting, to the network entity, the positioning measurement report to include the perception-based positioning-related information; or transmitting, to the network entity, the positioning measurement report to include an error indication corresponding to a perception-based component.

18. The method of claim 16, further comprising: performing measurements for the positioning measurement report using one or more positioning measurement gaps associated with a positioning measurement gap configuration, wherein the measurements for the positioning measurement report are performed using the one or more positioning measurement gaps based on an inclusion of the perception-based positioning-related information in the positioning measurement report; and transmitting, to the network entity, an indication that the UE used the one or more positioning measurement gaps associated with the positioning measurement gap configuration to perform the measurements for the positioning measurement report.

19. The method of claim 18, wherein: a first measurement gap length of the one or more positioning measurement gaps is greater than a second measurement gap length of second positioning measurement gaps associated with the positioning measurement gap configuration; andthe second positioning measurement gaps are for a second positioning measurement report that does not include measurements corresponding to the perception-based positioning-related information.

20. The method of claim 1, further comprising: transmitting data on a physical uplink shared channel (PUSCH) during at least one positioning measurement gap associated with a positioning measurement gap configuration; and transmitting a positioning measurement report based on perception-based components of the UE.

21. The method of claim 20, wherein at least one measurement indication of the positioning measurement report is determined absent reference signals associated with the positioning measurement gap configuration.

22. The method of claim 1, further comprising: transmitting an indication that the UE is refraining from using at least one positioning measurement gap associated with a positioning measurement gap configuration.

23. The method of claim 22, wherein the indication that the UE is refraining from using the at least one positioning measurement gap is transmitted based on a determination that the metric corresponding to the one or more DoF parameters is satisfied.

24. The method of claim 1, further comprising: receiving an indication corresponding to a number of positioning measurement reports for which the UE is to use perception-based components.

25. The method of claim 1, wherein the UE comprises a perception entity.

26. The method of claim 1, wherein the UE is running an extended reality (XR) or metaverse-based application that utilizes at least one sensor of the UE.

27. A method of wireless communication performed by a network entity, comprising: receiving, from a first user equipment (UE), first perception-based positioning- related information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters; and transmitting, to the first UE, a first radio frequency (RF)-based positioning configuration responsive to the first perception-based positioning-related information.

28. A user equipment (UE), comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: transmit, via the one or more transceivers, to a network entity, perception-based positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters, wherein the perception-based positioning-related information is obtained by a modem of the UE through a cross-layer application programming interface (API); and receive, via the one or more transceivers, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the perceptionbased positioning-related information.

29. The UE of claim 28, wherein the perception-based positioning-related information is associated with information corresponding to one or more DoF that includes orientation information of the UE different from position information of the UE.

30. The UE of claim 29, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, a first prioritization of a plurality of positioning reference signal (PRS) resource sets associated with the RF-based positioning configuration, wherein the first prioritization is based on the orientation information of the UE.

31. The UE of claim 30, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, a second prioritization of the plurality of PRS resource sets associated with the RF-based positioning configuration, wherein the second prioritization is based on the position information of the UE and different from the first prioritization.

32. The UE of claim 29, wherein the RF-based positioning configuration comprises one or more sets of sounding reference signal (SRS) resources based on the orientation information of the UE.

33. A user equipment (UE), compri sing : means for transmitting, to a network entity, perception-based positioning-related information comprising information associated with a metric corresponding to one or more degrees of freedom (DoF) parameters, wherein the perception-based positioning- related information is obtained by a modem of the UE through a cross-layer application programming interface (API); and means for receiving, from the network entity, a radio frequency (RF)-based positioning configuration responsive to the perception-based positioning-related information.

34. The UE of claim 33, further comprising: means for refraining from using at least one sensor of the UE based on the received RF-based positioning configuration.

Images