EP4659511A1 - Radio access network (ran) analytics exposure to the location server - Google Patents

Abstract

Disclosed are techniques for communication. In an aspect, a location server transmits, to a radio access network (RAN) controller entity, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE), the request including at least an identifier of the positioning session, receives, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics, and performs, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine a location of the UE.

Description

RADIO ACCESS NETWORK (RAN) ANALYTICS EXPOSURE TO THE

LOCATION SERVER

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present Application for Patent claims priority to Greek Patent Application No. 20230100089, entitled “RADIO ACCESS NETWORK (RAN) ANALYTICS EXPOSURE TO THE LOCATION SERVER,” filed February 3, 2023, which is assigned to the assignee hereof and expressly incorporated herein by reference in its entirety.

BACKGROUND OF THE DISCLOSURE

1. Field of the Disclosure

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

2. Description of the Related Art

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

[0004] 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

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

[0006] In an aspect, a method of communication performed by a location server includes transmitting, to a radio access network (RAN) controller entity, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE), the request including at least an identifier of the positioning session; receiving, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics; and performing, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine a location of the UE.

[0007] In an aspect, a method of communication performed by a radio access network (RAN) controller entity includes receiving, from a location server, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE) to determine a location of the UE, the request including at least an identifier of the positioning session; and transmitting, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics.

[0008] In an aspect, a location server 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 configured to: transmit, via the one or more transceivers, to a radio access network (RAN) controller entity, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE), the request including at least an identifier of the positioning session; receive, via the one or more transceivers, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics; and perform, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine a location of the UE.

[0009] In an aspect, a radio access network (RAN) controller entity 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 configured to: receive, via the one or more transceivers, from a location server, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE) to determine a location of the UE, the request including at least an identifier of the positioning session; and transmit, via the one or more transceivers, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics.

[0010] In an aspect, a location server includes means for transmitting, to a radio access network (RAN) controller entity, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE), the request including at least an identifier of the positioning session; means for receiving, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics; and means for performing, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine a location of the UE.

[0011] In an aspect, a radio access network (RAN) controller entity includes means for receiving, from a location server, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE) to determine a location of the UE, the request including at least an identifier of the positioning session; and means for transmitting, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics.

[0012] In an aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a location server, cause the location server to: transmit, to a radio access network (RAN) controller entity, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE), the request including at least an identifier of the positioning session; receive, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics; and perform, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine a location of the UE.

[0013] In an aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a radio access network (RAN) controller entity, cause the RAN controller entity to: receive, from a location server, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE) to determine a location of the UE, the request including at least an identifier of the positioning session; and transmit, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics.

[0014] 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

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

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

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

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

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

[0020] FIG. 5 illustrates example Long-Term Evolution (LTE) positioning protocol (LPP) reference sources for positioning.

[0021] FIG. 6 illustrates an example location services procedure, according to aspects of the disclosure. [0022] FIG. 7 illustrates an example LPP capability transfer procedure, assistance data transfer procedure, and location information transfer procedure between a target device and a location server, according to aspects of the disclosure.

[0023] FIG. 8 is a diagram illustrating an example scenario for using artificial intelligence / machine learning positioning techniques to position a UE, according to aspects of the disclosure.

[0024] FIG. 9 is a diagram of an example open radio access network (0-RAN) architecture, according to aspects of the disclosure.

[0025] FIG. 10 is a diagram of an example network architecture in which a modified Y 1 interface is implemented, according to aspects of the disclosure.

[0026] FIGS. 11 and 12 illustrate example methods of communication, according to aspects of the disclosure.

DETAILED DESCRIPTION

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

[0028] Various aspects relate generally to wireless technologies. Some aspects more specifically relate to exposing radio access network (RAN) analytics to a location server. In some examples, a location server may establish a positioning session with a user equipment (UE) to determine a location of the UE. The location server may then transmit, to a RAN controller entity, a request for RAN data analytics associated with the positioning session with the UE, the request including at least an identifier of the positioning session. In response, the location server may receive the RAN data analytics from the RAN controller entity. The location server may then perform, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine the location of the UE.

[0029] 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 transmitting a request for RAN data analytics associated with the positioning session with the UE and receiving the data analytics in response, the described techniques can be used to provide data exposure from the RAN (e.g., the RAN controller entity) to the core network (e.g., the location server).

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

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

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

[0033] 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, augmented reality (AR) / virtual reality (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.

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

[0035] 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 antennas connected 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.

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

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

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

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

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

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

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

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

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

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

[0046] 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. [0047] 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 that specific 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.

[0048] 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-1 ocati on (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. [0049] 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 direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal -to- interference-plus-noise ratio (SINR), etc.) of the RF signals received from that direction.

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

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

[0052] 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 Telecommunications Union (ITU) as a “millimeter wave” band.

[0053] 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 frequencies as 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.

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

[0055] 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 to change the primary carrier of any UE 104/182 at any time. This is done, for example, to balance the load on different carriers. 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.

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

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

[0058] 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 abase 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 geographic coverage 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.

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

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

[0061] 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 S Vs 112 may be part of a satellite positioning system that aUE 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.

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

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

[0064] 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), WiFi Direct (WiFi-D), Bluetooth®, and so on.

[0065] 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). [0066] 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 core network, 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).

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

[0068] 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 of interconnect 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, quality of service (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.

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

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

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

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

[0073] 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 communicates with 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.

[0074] 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, 5GNB, access point (AP), a transmit receive point (TRP), or a 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.

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

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

[0077] 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 (also referred to as an “O- CU” 280) may communicate with one or more distributed units (DUs) 285 (e.g., gNB- DUs 228) via respective midhaul links, such as an Fl interface. The DUs 285 (also referred to as “O-DUs” 285) may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective fronthaul links. The RUs 287 (also referred to as “O- 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.

[0078] 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 radio frequency (RF) transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0079] In some aspects, the CU 280 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (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 one or 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 0-RAN configuration. The CU 280 can be implemented to communicate with the DU 285, as necessary, for network control and signaling.

[0080] 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 radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, 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.

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

[0082] 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 interact with 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. The SMO Framework 255 also may include a Non-RT RIC 257 configured to support functionality of the SMO Framework 255.

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

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

[0085] FIGS. 3A, 3B, and 3C illustrate several example components (represented by corresponding blocks) that may be incorporated into a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (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. 2 A 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.

[0086] The UE 302 and the base station 304 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.

[0087] The UE 302 and the base station 304 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., WiFi, LTE-D, 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 WiFi 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.

[0088] The UE 302 and the base station 304 also include, at least in some cases, satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide means for receiving and/or measuring satellite positioning/communication signals 338 and 378, respectively. Where the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning/communication signals 338 and 378 may be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), QuasiZenith Satellite System (QZSS), etc. Where the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning/communication signals 338 and 378 may be communication signals (e.g., carrying control and/or user data) originating from a 5G network. The satellite signal receivers 330 and 370 may comprise any suitable hardware and/or software for receiving and processing satellite positioning/communication signals 338 and 378, respectively. The satellite signal receivers 330 and 370 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 302 and the base station 304, respectively, using measurements obtained by any suitable satellite positioning system algorithm.

[0089] The base station 304 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 304, other network entities 306). For example, the base station 304 may employ the one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 over one or more wired or wireless backhaul links. As another example, the network entity 306 may employ the one or more network transceivers 390 to communicate with one or more base station 304 over one or more wired or wireless backhaul links, or with other network entities 306 over one or more wired or wireless core network interfaces.

[0090] 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 302, base station 304) to perform transmit “beamforming,” as described herein. Similarly, wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus (e.g., UE 302, base station 304) 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.

[0091] 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 more transceivers.” 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 302) and a base station (e.g., base station 304) will generally relate to signaling via a wireless transceiver.

[0092] The UE 302, the base station 304, and the network entity 306 also include other components that may be used in conjunction with the operations as disclosed herein. The UE 302, the base station 304, and the network entity 306 include one or more processors 332, 384, and 394, respectively, for providing functionality relating to, for example, wireless communication, and for providing other processing functionality. The processors 332, 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 332, 384, and 394 may include, for example, one or more general purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuitry, or various combinations thereof.

[0093] The UE 302, the base station 304, 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 302, the base station 304, and the network entity 306 may include positioning component 342, 388, and 398, respectively. The positioning component 342, 388, and 398 may be hardware circuits that are part of or coupled to the processors 332, 384, and 394, respectively, that, when executed, cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. In other aspects, the positioning component 342, 388, and 398 may be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning component 342, 388, and 398 may be memory modules stored in the memories 340, 386, and 396, respectively, that, when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. FIG. 3A illustrates possible locations of the positioning component 342, which may be, for example, part of the one or more WWAN transceivers 310, the memory 340, the one or more processors 332, or any combination thereof, or may be a standalone component. FIG. 3B illustrates possible locations of the 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 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. [0094] The UE 302 may include one or more sensors 344 coupled to the one or more processors 332 to provide means for sensing or detecting movement and/or orientation information 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 receiver 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.

[0095] In addition, the UE 302 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 304 and the network entity 306 may also include user interfaces.

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

[0097] 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 spatial streams. 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 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a respective spatial stream for transmission.

[0098] At the UE 302, 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 332. The transmitter 314 and the receiver 312 implement Lay er- 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 302. If multiple spatial streams are destined for the UE 302, 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 304. 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 304 on the physical channel. The data and control signals are then provided to the one or more processors 332, which implements Layer-3 (L3) and Layer-2 (L2) functionality.

[0099] In the downlink, the one or more processors 332 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 332 are also responsible for error detection.

[0100] Similar to the functionality described in connection with the downlink transmission by the base station 304, the one or more processors 332 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.

[0101] Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station 304 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. [0102] The uplink transmission is processed at the base station 304 in a manner similar to that described in connection with the receiver function at the UE 302. The receiver 352 receives 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.

[0103] 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 302. 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.

[0104] For convenience, the UE 302, the base station 304, 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 302 may omit the WWAN transceiver(s) 310 (e.g., a wearable device or tablet computer or PC or laptop may have Wi-Fi and/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 receiver 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 304 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 receiver 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.

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

[0106] 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 302 (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 304 (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,” “by a 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 302, base station 304, network entity 306, etc., such as the processors 332, 384, 394, the transceivers 310, 320, 350, and 360, the memories 340, 386, and 396, the positioning component 342, 388, and 398, etc.

[0107] 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 302 via the base station 304 or independently from the base station 304 (e.g., over a non-cellular communication link, such as WiFi).

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

[0109] 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 transmitting base 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).

[0110] 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. [0111] 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.

[0112] 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 trip propagation 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.

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

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

[0115] 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 positioning measurement(s) are in FR2, the value range for the uncertainty of the expected RSTD may be +/- 8 ps.

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

[0117] In LTE and, at least in some cases, NR, positioning measurements are reported through higher layer signaling, specifically, LTE positioning protocol (LPP) and/or RRC. LPP is used point-to-point between a location server (e.g., location server 230, LMF 270, SLP 272) and a UE (e.g., any of the UEs described herein) in order to position the UE using location related measurements obtained from one or more reference sources. FIG. 5 is a diagram 500 illustrating example LPP reference sources for positioning. In the example of FIG. 5, a target device, specifically a UE 504 (e.g., any of the UEs described herein), is engaged in an LPP session with a location server 530 (labeled as an “E-SMLC/SLP” in the specific example of FIG. 5). The UE 504 is also receiving/measuring wireless positioning signals from a first reference source, specifically one or more base stations 502 (which may correspond to any of the base stations described herein, and which is labelled as an “eNode B” in the specific example of FIG. 5), and a second reference source, specifically one or more satellite positioning system (SPS) satellites 520 (which may correspond to SVs 112 in FIG. 1).

[0118] An LPP session is used between a location server 530 and a UE 504 in order to obtain location-related measurements or a location estimate or to transfer assistance data. A single LPP session is used to support a single location request (e.g., for a single mobile- terminated location request (MT-LR), mobile originated location request (MO-LR), or network induced location request (NI-LR)). Multiple LPP sessions can be used between the same endpoints to support multiple different location requests. Each LPP session comprises one or more LPP transactions, with each LPP transaction performing a single operation (e.g., capability exchange, assistance data transfer, location information transfer). LPP transactions are referred to as LPP procedures. The instigator of an LPP session instigates the first LPP transaction, but subsequent transactions may be instigated by either endpoint. LPP transactions within a session may occur serially or in parallel. LPP transactions are indicated at the LPP protocol level with a transaction identifier in order to associate messages with one another (e.g., request and response). Messages within a transaction are linked by a common transaction identifier.

[0119] LPP signaling can be used to request and report measurements related to the following positioning methods: observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), assisted global navigation satellite system (A-GNSS), LTE enhanced cell identity (E-CID), NR E-CID, sensor, terrestrial beacon system (TBS), WLAN, Bluetooth, downlink angle of departure (DL-AoD), uplink angle of arrival (UL- AoA), and multi -round-trip-time (RTT). Currently, LPP measurement reports may contain the following measurements: (1) one or more time of arrival (ToA), time difference of arrival (TDOA), reference signal time difference (RSTD), or reception-to- transmission (Rx-Tx) measurements, (2) one or more AoA and/or AoD measurements (currently only for a base station to report UL-AoA and DL-AoD to the location server 530), (3) one or more multipath measurements (per-path To A, reference signal received power (RSRP), AoA/ AoD), (4) one or more motion states (e.g., walking, driving, etc.) and trajectories (currently only for the UE 504), and (5) one or more report quality indications. In the present disclosure, positioning measurements, such as the example measurements just listed, and regardless of the positioning technology, may be referred to collectively as positioning state information (PSI).

[0120] The UE 504 and/or the location server 530 may derive location information from one or more reference sources, illustrated in the example of FIG. 5 as SPS satellite(s) 520 and the base station(s) 502. Each reference source can be used to calculate an independent estimate of the location of the UE 504 using associated positioning techniques. In the example of FIG. 5, the UE 504 is measuring characteristics (e.g., ToA, RSRP, RSTD, etc.) of positioning signals received from the base station(s) 502 to calculate, or to assist the location server 530 to calculate, an estimate of the location of the UE 504 using one or more cellular network-based positioning methods (e.g., multi-RTT, OTDOA, DL- TDOA, DL-AoD, E-CID, etc.). Similarly, the UE 504 is measuring characteristics (e.g., ToA) of global navigation satellite system (GNSS) signals received from the SPS satellites 520 to triangulate its location in two or three dimensions, depending on the number of SPS satellites 520 measured. In some cases, the UE 504 or the location server 530 may combine the location solutions derived from each of the different positioning techniques to improve the accuracy of the final location estimate.

[0121] As noted above, the UE 504 uses LPP to report location related measurements obtained from different of reference sources (e.g., base stations 502, Bluetooth beacons, SPS satellites 520, WLAN access points, motion sensors, etc.). As an example, for GNSS- based positioning, the UE 504 uses the LPP information element (IE) “A-GNSS- ProvideLocationlnformation” to provide location measurements (e.g., pseudo ranges, location estimate, velocity, etc.) to the location server 530, together with time information. It may also be used to provide a GNSS positioning-specific error reason. The “A-GNSS-ProvideLocationlnformation” IE includes IES such as “GNSS- SignalMeasurementlnformation,” “GNSS-Locationlnformation,” “GNSS- MeasurementList,” and “GNSS-Error.” The UE 504 includes the “GNSS- Locationlnformation” IE when it provides location and optionally velocity information derived using GNSS or hybrid GNSS and other measurements to the location server 530. The UE 504 uses the “GNSS-SignalMeasurementlnformation” IE to provide GNSS signal measurement information to the location server 530 and the GNSS network time association if requested by the location server 530. This information includes the measurements of code phase, Doppler, C/No, and optionally accumulated carrier phase, also referred to as accumulated delta range (ADR), which enable the UE assisted GNSS method where location is computed in the location server 530. The UE 504 uses the “GNSS-MeasurementList” IE to provide measurements of code phase, Doppler, C/No, and optionally accumulated carrier phase (or ADR).

[0122] As another example, for motion sensor-based positioning, the currently supported positioning methods use a barometric pressure sensor and a motion sensor. The UE 504 uses the LPP IE “Sensor-ProvideLocationlnformation” to provide location information for sensor-based methods to the location server 530. It may also be used to provide a sensor-specific error reason. The UE 504 uses the “Sensor-Measurem entinformation” IE to provide sensor measurements (e.g., barometric readings) to the location server 530. The UE 504 uses the “Sensor-Motionlnformation” to provide movement information to the location server 530. The movement information may comprise an ordered series of points. This information may be obtained by the UE 504 using one or more motion sensors (e.g., accelerometers, barometers, magnetometers, etc.).

[0123] As yet another example, for Bluetooth-based positioning, the UE 504 uses the “BT- ProvideLocationlnformation” IE to provide measurements of one or more Bluetooth beacons to the location server 530. This IE may also be used to provide Bluetooth positioning specific error reason.

[0124] FIG. 6 illustrates an example location services procedure 600, according to aspects of the disclosure. The location services procedure 600 may be performed by a UE 204, an NG- RAN node 602 (e.g., gNB 222, gNB-CU 226, ng-eNB 224, or other node in the NG-RAN 220) in the NG-RAN 220, an AMF 264, an LMF 270, and a 5GC location services (LCS) entity 680 (e.g., any third-party application requesting the UE’s 204 location, a public service access point (PSAP), an E-911 server, etc.). [0125] A location services request to obtain the location of a target (i.e., UE 204) may be initiated by a 5GC LCS entity 680, the AMF 264 serving the UE 204, or the UE 204 itself. FIG. 6 illustrates these options as stages 610a, 610b, and 610c, respectively. Specifically, at stage 610a, a 5GC LCS entity 680 sends a location services request to the AMF 264. Alternatively, at stage 610b, the AMF 264 generates a location services request itself. Alternatively, at stage 610c, the UE 204 sends a location services request to the AMF 264.

[0126] Once the AMF 264 has received (or generated) a location services request, it forwards the location services request to the LMF 270 at stage 620. The LMF 270 then performs NG- RAN positioning procedures with the NG-RAN node 602 at stage 630a and UE positioning procedures with the UE 204 at stage 630b. The specific NG-RAN positioning procedures and UE positioning procedures may depend on the type(s) of positioning method(s) used to locate the UE 204, which may depend on the capabilities of the UE 204. The positioning method(s) may be downlink-based (e.g., LTE-OTDOA, DL-TDOA, DL-AoD, etc.), uplink-based (e.g., UL-TDOA, UL-AoA, etc.), and/or downlink-and- uplink-based (e.g., LTE/NR E-CID, multi-RTT, etc.). The NG-RAN positioning procedures and UE positioning procedures may utilize LPP signaling between the UE 204 and the LMF 270 and LPP type A (LPPa) or New Radio positioning protocol type A (NRPPa) signaling between the NG-RAN node 602 and the LMF 270.

[0127] A prerequisite for stage 630 is that an LCS Correlation identifier (ID) and an AMF ID has been passed to the LMF 270 by the serving AMF 264. Both, the LCS Correlation ID and the AMF ID may be represented as a string of characters selected by the AMF 264. The LCS Correlation ID and the AMF ID are provided by the AMF 264 to the LMF 270 in the location services request at stage 620. When the LMF 270 then instigates stage 630, the LMF 270 also includes the LCS Correlation ID for this location session, together with the AMF ID, which indicates the AMF instance serving the UE 204. The LCS Correlation ID is used to ensure that during a positioning session between the LMF 270 and the UE 204, positioning response messages from the UE 204 are returned by the AMF 264 to the correct LMF 270 and carrying an indication (the LCS Correlation ID) that can be recognized by the LMF 270.

[0128] Note that the LCS Correlation ID serves as a location session identifier that may be used to identify messages exchanged between the AMF 264 and the LMF 270 for a particular location session for a UE 204. As mentioned above and shown in stage 620, a location session between an AMF 264 and an LMF 270 for a particular UE 204 is instigated by the AMF 264, and the LCS Correlation ID may be used to identify this location session (e.g., may be used by the AMF 264 to identify state information for this location session, etc.).

[0129] As part of the NG-RAN node positioning procedures (stage 630a) and UE positioning procedures (stage 630b), the LMF 270 may provide LPP assistance data in the form of downlink positioning reference signal (DL-PRS) configuration information to the NG- RAN node 602 and the UE 204 for the selected positioning method(s). Alternatively or additionally, the NG-RAN node 602 may provide DL-PRS and/or uplink PRS (UL-PRS) configuration information to the UE 204 for the selected positioning method(s). Note that while FIG. 6 illustrates a single NG-RAN node 602, there may be multiple NG-RAN nodes 602 involved in the positioning session.

[0130] Once configured with the DL-PRS and/or UL-PRS configurations, the NG-RAN node 602 and the UE 204 transmit and receive/measure the respective PRS at the scheduled times. The NG-RAN node 602 and the UE 204 then send their respective measurements to the LMF 270. In some cases, the NG-RAN node 602 may send its measurements to the UE 204, which may forward them to the LMF 270 using LPP signaling. Alternatively, the NG-RAN node 602 may send its measurements directly to the LMF 270 in LPPa or NRPPa signaling. In some cases, the UE 204 may send its measurements to the NG-RAN node 602 in RRC, uplink control information (UCI), or MAC control element (MAC-CE) signaling, and the NG-RAN node 602 may forward the measurements to the LMF 270 using LPPa or NRPPa signaling. Alternatively, the UE 204 may send its measurements directly to the LMF 270 using LPP signaling.

[0131] Once the LMF 270 obtains the measurements from the UE 204 and/or the NG-RAN node 602 (depending on the type(s) of positioning method(s)), it calculates an estimate of the UE’s 204 location using those measurements. Then, at stage 640, the LMF 270 sends a location services response, which includes the location estimate for the UE 204, to the AMF 264. The AMF 264 then forwards the location services response to the entity that generated the location services request at stage 650. Specifically, if the location services request was received from a 5GC LCS entity 680 at stage 610a, then at stage 650a, the AMF 264 sends a location services response to the 5GC LCS entity 680. If, however, the location services request was received from the UE 204 at stage 610c, then at stage 650c, the AMF 264 sends a location services response to the UE 204. Or, if the AMF 264 generated the location services request at stage 610b, then at stage 650b, the AMF 264 stores/uses the location services response itself.

[0132] Note that although the foregoing has described the location services procedure 600 as a UE-assisted location services procedure, it may instead be a UE-based location services procedure. A UE-assisted location services procedure is one where the LMF 270 calculates the location of the UE 204, whereas a UE-based location services procedure is one where the UE 204 calculates its own location. In the case of a UE-based location services procedure, stages 610c and 650c would be performed. The LMF 270 may still coordinate the transmission/measurement of DL-PRS (and possibly UL-PRS), but the measurements would be forwarded to the UE 204 rather than the LMF 270. As such, the location services response at stages 640 and 650c may be the measurements from the involved NG-RAN node(s) 602 rather than a location estimate of the UE 204. Alternatively, where the involved NG-RAN node(s) 602 forward their respective measurements directly to the UE 204 (e.g., via RRC signaling), the location services response at stage 640 may simply be a confirmation that the NG-RAN node and UE positioning procedures at stage 630 are complete.

[0133] As noted above, a single LPP session is used to support a single location request and multiple LPP sessions can be used between the same endpoints to support multiple different location requests. Each LPP session comprises one or more LPP transactions (or procedures), with each LPP transaction performing a single operation (capability exchange, assistance data transfer, or location information transfer). Each LPP transaction involves the exchange of one or more LPP messages between the location server and the target device. The general format of an LPP message consists of a set of common fields followed by a body. The body (which may be empty) contains information specific to a particular message type. Each message type contains information specific to one or more positioning methods and/or information common to all positioning methods.

[0134] An LPP session generally includes at least a capability transfer or indication procedure, an assistance data transfer or delivery procedure, and a location information transfer or delivery procedure. FIG. 7 illustrates an example LPP capability transfer procedure 710, LPP assistance data transfer procedure 730, and LPP location information transfer procedure 750 between a target device (labeled “Target”) and a location server (labeled “Server”), according to aspects of the disclosure.

[0135] The purpose of an LPP capability transfer procedure 710 is to enable the transfer of capabilities from the target device (e.g., a UE 204) to the location server (e.g., an LMF 270). Capabilities in this context refer to positioning and protocol capabilities related to LPP and the positioning methods supported by LPP. In the LPP capability transfer procedure 710, the location server (e.g., an LMF 270) indicates the types of capabilities needed from the target device (e.g., UE 204) in an LPP Request Capabilities message. The target device responds with an LPP Provide Capabilities message. The capabilities included in the LPP Provide Capabilities message should correspond to any capability types specified in the LPP Request Capabilities message. Specifically, for each positioning method for which a request for capabilities is included in the LPP Request Capabilities message, if the target device supports this positioning method, the target device includes the capabilities of the target device for that supported positioning method in the LPP Provide Capabilities message. For an LPP capability indication procedure, the target device provides unsolicited (i.e., without receiving an LPP Request Capabilities message) capabilities to the location server in an LPP Provide Capabilities message.

[0136] The purpose of an LPP assistance data transfer procedure 730 is to enable the target device to request assistance data from the location server to assist in positioning, and to enable the location server to transfer assistance data to the target device in the absence of a request. In the LPP assistance data transfer procedure 730, the target device sends an LPP Request Assistance Data message to the location server. The location server responds to the target device with an LPP Provide Assistance Data message containing assistance data. The transferred assistance data should match or be a subset of the assistance data requested in the LPP Request Assistance Data. The location server may also provide any not requested information that it considers useful to the target device. The location server may also transmit one or more additional LPP Provide Assistance Data messages to the target device containing further assistance data. For an LPP assistance data delivery procedure, the location server provides unsolicited assistance data necessary for positioning. The assistance data may be provided periodically or non-periodically.

[0137] The purpose of an LPP location information transfer procedure 750 is to enable the location server to request location measurement data and/or a location estimate from the target device, and to enable the target device to transfer location measurement data and/or a location estimate to a location server in the absence of a request. In an LPP location information transfer procedure 750, the location server sends an LPP Request Location Information message to the target device to request location information, indicating the type of location information needed and potentially the associated QoS. The target device responds with an LPP Provide Location Information message to the location server to transfer location information. The location information transferred should match or be a subset of the location information requested by the LPP Request Location Information unless the location server explicitly allows additional location information. More specifically, if the requested information is compatible with the target device’s capabilities and configuration, the target device includes the requested information in an LPP Provide Location Information message. Otherwise, if the target device does not support one or more of the requested positioning methods, the target device continues to process the message as if it contained only information for the supported positioning methods and handles the signaling content of the unsupported positioning methods by LPP error detection. If requested by the LPP Request Lactation Information message, the target device sends additional LPP Provide Location Information messages to the location server to transfer additional location information. An LPP location information delivery procedure supports the delivery of positioning estimations based on unsolicited service.

[0138] LPP also defines procedures related to error indication for when a receiving endpoint (target device or location server) receives erroneous or unexpected data or detects that certain data are missing. Specifically, when a receiving endpoint determines that a received LPP message contains an error, it can return an Error message to the transmitting endpoint indicating the error or errors and discard the received/erroneous message. If the receiving endpoint is able to determine that the erroneous LPP message is an LPP Error or Abort Message, then the receiving endpoint discards the received message without returning an Error message to the transmitting endpoint.

[0139] LPP also defines procedures related to abort indication to allow a target device or location server to abort an ongoing procedure due to some unexpected event (e.g., cancellation of a location request by an LCS client). An Abort procedure can also be used to stop an ongoing procedure (e.g., periodic location reporting from the target device). In an Abort procedure, a first endpoint determines that procedure P must be aborted and sends an Abort message to a second endpoint carrying the transaction ID for procedure P. The second endpoint then aborts procedure P.

[0140] Artificial intelligence (Al) and machine learning (ML) techniques have been introduced for positioning purposes. Machine learning may be used to generate models that may be used to facilitate various aspects associated with processing of data. With respect to positioning, machine learning can be used to generate measurement models for processing reference signals for positioning (e.g., PRS), such as feature extraction, reporting of reference signal measurements (e.g., selecting which extracted features to report), and so on. In some cases, AI/ML positioning techniques may be applied at the RAN (e.g., near-real time RIC 259), meaning the RAN can train the AI/ML model and provide the resulting inference model. The inference model can then be deployed within the RAN, for example, at the near-real time RIC. In other cases, AI/ML positioning techniques may be applied at the network (e.g., LMF 270), meaning the network trains the AI/ML model and provides the resulting inference model. The inference model can be deployed at the LMF.

[0141] There are different scenarios where UE positioning using AI/ML positioning techniques at the RAN can increase the accuracy for deterministic positioning algorithms. As a first example scenario, optimization of the PRS pattern (including the muting pattern) can be applied at the RIC (e.g., near-real time RIC 259) considering the energy saving modes of the involved O-RUs (e.g., O-RUs 287). As another example scenario, the RAN can use AI/ML positioning techniques to select the UE positioning method(s) with respect to the current positioning scenario (e.g., line-of-sight (LOS), whether or not energy saving is enabled, reference signal overhead, etc.).

[0142] FIG. 8 is a diagram 800 illustrating a third example scenario for using AI/ML positioning techniques to position a UE 204, according to aspects of the disclosure. The various network components/entities illustrated in FIG. 8 are described above with reference to FIG. 2C. In this example scenario, for a UE 204 on a train, the track can be learned (or assumed to be known by the network), meaning that one dimension of UE position is known (track geometry). In this case, AI/ML techniques implemented in the RAN can provide a prediction of the position of the UE 204 for the LMF (e.g., LMF 270).

[0143] In the foregoing examples, the RAN has access to the information needed by the AI/ML models. For example, the RAN has access to the energy saving modes of the involved O-RUs (e.g., RUs 287), the LOS condition with respect to the UE, whether or not energy saving is enabled, reference signal overhead, and the track geometry of the train. As such, the RAN may be in a better position to apply the AI/ML positioning techniques. As the location server calculates the position of the UE, it would be beneficial for the RAN to be able to provide the output of the AI/ML models to the location server. However, to do so, the RAN exposes RAN data analytics (e.g., prediction of UE position) to the core network (e.g., LMF 270). As such, the analytics information should be exposed in a secure manner.

[0144] The RAN may support multiple vertical use cases, such as positioning, extended reality (XR), NTN, loT, and so on. From one side, the near-real time RIC (deployed as part of the RAN) can produce analytics related to UE mobility, RAN congestion, and UE positioning (including prediction). From another side, the 5G core (e.g., 5GC 260) can produce analytics related to the 5G core, such as 5G core congestion, UE location, and PRS pattern. As such, the RAN analytics would be beneficial to the 5G core.

[0145] FIG. 9 is a diagram 900 of an example 0-RAN architecture, according to aspects of the disclosure. Various network components/entities illustrated in FIG. 9 have been described above with reference to FIG. 2C. In addition, as shown in FIG. 9, an interface is defined between the near-real time RIC 259 and any 5G external application consumers, referred to as Y1 consumer(s) 910. The Y1 consumer(s) 910 are assumed to be under an O-RAN-trusted domain. That is, the Y1 consumer(s) are assumed to be within the same 0-RAN or the same public land mobile network (PLMN) (i.e., belongs to the same network operator) as the near-real time RIC 259.

[0146] As discussed above, AI/ML positioning techniques can benefit from near-real time RIC data analytics exposure to/from the LMF in the 5G core. However, there is currently no interface between the near-real time RIC and the LMF, as there is for the Y1 consumer(s) 910. Accordingly, the present disclosure proposes to extend the Y1 interface to support signaling between the near-real time RIC in the RAN and the LMF in the 5G core in a secure manner. In this way, the near-real time RIC will consider the LMF as a new Y1 consumer in the 5G core (within the same PLMN), which will allow the LMF to subscribe to the near-real time RIC to request RAN analytics data. This allows the LMF to retrieve and benefit from the RAN analytics for positioning purposes. The Y1 interface between the near-real time RIC 259 and the LMF 270 may be referred to herein as a “modified Yl” interface.

[0147] FIG. 10 is a diagram 1000 of an example network architecture in which a modified Yl interface is implemented, according to aspects of the disclosure. The various network components/entities illustrated in FIG. 10 have been described above with reference to FIGS. 2A - 2C. As shown in FIG. 10, the modified Yl interface allows communication from the LMF 270 to the near-real time RIC 259 and from the near-real time RIC 259 to the LMF 270. For example, the LMF 270 may subscribe to the near-real time RIC 259 and request data from or send data to the near-real time RIC 259. For security and privacy, the sent/received data should not include a UE identifier (e.g., international mobile equipment identity (IMEI)). The near-real time RIC 259 can respond to the request over the modified Y 1 interface.

[0148] A positioning procedure between the LMF 270 and a UE 204 and involving the near-real time RIC 259 is now described with reference to FIG. 10. At stage 1, the LMF 270 establishes a UE positioning session (or LPP session) with the UE 204 as during, for example, stage 630b of FIG. 6. As a first option (referred to as “alternative 1”), the LMF 270 controls any information about the UE 204 provided to the near-real time RIC 259. That is, while the messages between the LMF 270 and the UE 204 may pass through the near-real time RIC 259, the near-real time RIC 259 is not able to decode them. Instead, the LMF 270 sends any information about the UE/LPP session to the near-real time RIC 259 as needed.

[0149] As a second option (referred to as “alternative 2”), the UE session (or LPP session) is established between the UE 204 and the near-real time RIC 259 and the near-real time RIC 259 and the LMF 270. In other words, the UE/LPP session is extended to pass through the near-real time RIC 259. In that way, the near-real time RIC 259 can decode the messages (e.g., LPP messages) exchanged between the LMF 270 and the UE 204.

[0150] During session establishment for both alternative 1 and alternative 2, the LMF 270 sends an identifier of the UE session (or LPP session) to the near-real time RIC 259. The LPP session ID between the LMF 270 and the target UE 204 can be used over the modified Yl interface to define the UE session ID. If needed, the near-real time RIC 259 can associate the UE/LPP session ID to a RAN UE identifier (i.e., a UE identifier used in the RAN domain and not exposed outside the RAN domain). [0151] At stage 2, the UE 204 reports positioning measurements to the gNB 222 (e.g., as for an E-CID positioning procedure). These measurements are sent to the LMF 270 viaNRPPa. Alternatively, the UE 204 may report the measurements to the LMF 270 via LPP (e.g., in an LPP Location Information Transfer Procedure 750).

[0152] At stage 3, the LMF 270 sends the reported UE measurements to the near-real time RIC 259 via the modified Y 1 interface. Currently, the UE’s 204 positioning capabilities (such as whether DL-TDOA, DL-AOD, etc. are supported) are shared with the LMF 270 via the LPP session (e.g., via an LPP Capability Transfer Procedure 710) but are not available to the RAN. Using the Y1 interface, the UE’s 204 positioning capabilities can be shared with the near-real time RIC 259.

[0153] At stage 4, the near-real time RIC 259 can apply AI/ML techniques to the UE positioning measurements and expose the data analytics to the LMF 270 via the Y1 interface. For example, the AI/ML techniques may be used to predict the UE’s 204 trajectory and/or determine the appropriate inference model, PRS pattern, PRS muting pattern, positioning method, and/or the like.

[0154] More specifically, the near-real time RIC 259 can provide the following information to assist the LMF 270 to determine the position of the UE 204. First, the near-real time RIC 259 can determine the positioning method to be used, if more than one is available, based on UE capabilities (e.g., obtained from the LMF 270 based on an LPP Capability Transfer Procedure 710), the requested accuracy of the position, the response time, and/or the environment scenario (e.g., a scenario with higher LOS probability than non-line-of-sight (NLOS) probability with respect to the O-RUs 287 available for the positioning procedure, the types of network nodes deployed in the vicinity of the UE (e.g., positioning reference units (PRUs), access points, O-RUs, etc.), and the like).

[0155] Second, the near-real time RIC 259 can access information about energy savings for O- RUs 287, component carrier(s), and/or cell(s), and can exploit this information to select the appropriate positioning method(s), the appropriate pattern for the reference signals to be transmitted and measured (e.g., DL-PRS, SL-PRS, SRS), and/or the appropriate PRU. (A PRU is a UE or other mobile device whose location is known and can be used as a reference device/location for network calibration.)

[0156] Third, the near-real time RIC 259 can optimize the reference signal pattern to be selected jointly with the selected positioning method. The near-real time RIC 259 can transfer the optimized reference signal pattern to the LMF 270 and/or directly to the gNB 222. For DL-PRS, the LMF 270 may provide the reference signal pattern to the UE 204 via an LPP Assistance Data Transfer Procedure 730. For SL-PRS or SRS, the gNB 222 may provide the reference signal pattern to the UE 204 via RRC.

[0157] Fourth, the near-real time RIC 259 may predict an estimated trajectory of the UE 204. For example, the topology of a train track may be known at the near-real time RIC 259 (as in the example of FIG. 8) while only the topology of base station sites are known at the LMF 270. The near-real time RIC 259 can use this topology information to predict the estimated trajectory of the UE 204. The near-real time RIC 259 can send the estimated trajectory to the LMF 270 over the modified Y1 interface. The near-real time RIC 259 may encode the trajectory using LPP, such as in a “Sensor-Motionlnformation” IE.

[0158] FIG. 11 illustrates an example method 1100 of communication, according to aspects of the disclosure. In an aspect, method 1100 may be performed by a location server (e.g., LMF 270).

[0159] At 1110, the location server transmits, to a RAN controller entity (e.g., near-real time RIC 259), a request for RAN data analytics associated with a positioning session (e.g., a location services procedure 600, an LPP session, etc.) between the location server and a UE (e.g., UE 204), the request including at least an identifier of the positioning session. In an aspect, operation 1110 may be performed by the one or more network transceivers 390, the one or more processors 394, memory 396, and/or positioning component 398, any or all of which may be considered means for performing this operation.

[0160] At 1120, the location server receives, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics. In an aspect, operation 1120 may be performed by the one or more network transceivers 390, the one or more processors 394, memory 396, and/or positioning component 398, any or all of which may be considered means for performing this operation.

[0161] At 1130, the location server performs, based at least in part on the RAN data analytics, a positioning procedure (e.g., an LPP procedure, such as an LPP Location Information Transfer Procedure, for a particular positioning method, such as multi-RTT, DL-TDOA, etc.) with the UE to determine a location of the UE. In an aspect, operation 1130 may be performed by the one or more network transceivers 390, the one or more processors 394, memory 396, and/or positioning component 398, any or all of which may be considered means for performing this operation.

[0162] FIG. 12 illustrates an example method 1200 of communication, according to aspects of the disclosure. In an aspect, method 1200 may be performed by a RAN controller entity (e.g., near-real time RIC 259).

[0163] At 1210, the RAN controller entity receives, from a location server (e.g., LMF 270), a request for RAN data analytics associated with a positioning session between the location server and a UE (e.g., UE 204) to determine a location of the UE, the request including at least an identifier of the positioning session. In an aspect, operation 1210 may be performed by the one or more network transceivers 380, the one or more processors 384, memory 386, and/or positioning component 388, any or all of which may be considered means for performing this operation.

[0164] At 1220, the RAN controller entity transmits, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics. In an aspect, operation 1220 may be performed by the one or more network transceivers 380, the one or more processors 384, memory 386, and/or positioning component 388, any or all of which may be considered means for performing this operation.

[0165] As will be appreciated, a technical advantage of the methods 1100 and 1200 is to provide data exposure from the RAN (e.g., the RAN controller entity) to the core network (e.g., the location server) and from the core network to the RAN.

[0166] 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 can also 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.

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

[0168] Clause 1. A method of communication performed by a location server, comprising: establishing a positioning session with a user equipment (UE) to determine a location of the UE; transmitting, to a radio access network (RAN) entity, a request for RAN data analytics associated with the positioning session with the UE, the request including at least an identifier of the positioning session; receiving, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics; and performing, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine the location of the UE.

[0169] Clause 2. The method of clause 1, wherein: the request for the RAN data analytics is transmitted via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is received via the Y 1 interface.

[0170] Clause 3. The method of any of clauses 1 to 2, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

[0171] Clause 4. The method of any of clauses 1 to 3, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

[0172] Clause 5. The method of any of clauses 1 to 4, wherein the identifier of the positioning session comprises an LPP session identifier.

[0173] Clause 6. The method of any of clauses 1 to 5, wherein the RAN data analytics comprise: a positioning method to use for the positioning procedure, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning procedure, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning procedure, a trajectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof. [0174] Clause 7. The method of clause 6, wherein a determination of the positioning method to use for the positioning procedure is based on: positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning procedure, an environmental scenario of the UE, or any combination thereof.

[0175] Clause 8. The method of clause 7, wherein the environmental scenario is based on a probability of the UE being in a line-of-sight (LOS) scenario or a non-line-of-sight (NLOS) scenario with respect to one or more radio units (RUs) available for the positioning procedure.

[0176] Clause 9. The method of any of clauses 7 to 8, further comprising: receiving, from the UE, the positioning capabilities of the UE; and transmitting, to the RAN controller entity, the positioning capabilities of the UE.

[0177] Clause 10. The method of any of clauses 6 to 9, wherein the trajectory of the UE is based on a known topology of a route on which the UE is traveling.

[0178] Clause 11. The method of clause 10, wherein the route comprises a train track.

[0179] Clause 12. The method of any of clauses 6 to 11, further comprising: receiving, from the UE via LPP signaling, positioning measurements of the one or more PRS resources; or receiving, from the RAN controller entity via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

[0180] Clause 13. The method of clause 12, wherein the request for the RAN data analytics further includes the positioning measurements of the one or more PRS resources.

[0181] Clause 14. The method of any of clauses 6 to 13, wherein the one or more PRS resources comprise: one or more downlink PRS resources, one or more uplink PRS resources, one or more sidelink PRS resources, or any combination thereof.

[0182] Clause 15. The method of any of clauses 1 to 14, wherein messages exchanged between the location server and the UE during the positioning session are not exchanged via the RAN controller entity.

[0183] Clause 16. The method of any of clauses 1 to 14, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

[0184] Clause 17. The method of any of clauses 1 to 16, wherein the positioning session between the location server and the UE is established via the RAN controller entity. [0185] Clause 18. A method of communication performed by a radio access network (RAN) entity, comprising: receiving, from a location server, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE) to determine a location of the UE, the request including at least an identifier of the positioning session; and transmitting, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics.

[0186] Clause 19. The method of clause 18, wherein: the request for the RAN data analytics is received via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is transmitted via the Y1 interface.

[0187] Clause 20. The method of any of clauses 18 to 19, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

[0188] Clause 21. The method of any of clauses 18 to 20, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

[0189] Clause 22. The method of any of clauses 18 to 21, wherein the identifier of the positioning session comprises an LPP session identifier.

[0190] Clause 23. The method of any of clauses 18 to 22, further comprising: generating a RAN- specific identifier for the positioning session based on the identifier of the positioning session.

[0191] Clause 24. The method of any of clauses 18 to 23, wherein the RAN data analytics comprise: a positioning method to use for the positioning session, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning session, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning session, a trajectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

[0192] Clause 25. The method of clause 24, further comprising: determining the positioning method to use for the positioning session based on positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning session, an environmental scenario of the UE, or any combination thereof. [0193] Clause 26. The method of clause 25, further comprising: receiving, from the UE, the positioning capabilities of the UE; or receiving, from the location server, the positioning capabilities of the UE.

[0194] Clause 27. The method of any of clauses 24 to 26, further comprising: receiving, from the UE via radio resource control (RRC) signaling, positioning measurements of the one or more PRS resources; and transmitting, to the location server via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

[0195] Clause 28. The method of any of clauses 24 to 27, wherein the request for the RAN data analytics further includes positioning measurements of the one or more PRS resources obtained by the UE.

[0196] Clause 29. The method of any of clauses 18 to 28, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

[0197] Clause 30. The method of any of clauses 18 to 29, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

[0198] Clause 31. A location server, comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: establish a positioning session with a user equipment (UE) to determine a location of the UE; transmit, via the at least one transceiver, to a radio access network (RAN) entity, a request for RAN data analytics associated with the positioning session with the UE, the request including at least an identifier of the positioning session; receive, via the at least one transceiver, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics; and perform, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine the location of the UE.

[0199] Clause 32. The location server of clause 31, wherein: the request for the RAN data analytics is transmitted via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is received via the Y 1 interface.

[0200] Clause 33. The location server of any of clauses 31 to 32, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC). [0201] Clause 34. The location server of any of clauses 31 to 33, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

[0202] Clause 35. The location server of any of clauses 31 to 34, wherein the identifier of the positioning session comprises an LPP session identifier.

[0203] Clause 36. The location server of any of clauses 31 to 35, wherein the RAN data analytics comprise: a positioning method to use for the positioning procedure, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning procedure, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning procedure, a trajectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

[0204] Clause 37. The location server of clause 36, wherein a determination of the positioning method to use for the positioning procedure is based on: positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning procedure, an environmental scenario of the UE, or any combination thereof.

[0205] Clause 38. The location server of clause 37, wherein the environmental scenario is based on a probability of the UE being in a line-of-sight (LOS) scenario or a non-line-of-sight (NLOS) scenario with respect to one or more radio units (RUs) available for the positioning procedure.

[0206] Clause 39. The location server of any of clauses 37 to 38, wherein the at least one processor is further configured to: receive, via the at least one transceiver, from the UE, the positioning capabilities of the UE; and transmit, via the at least one transceiver, to the RAN controller entity, the positioning capabilities of the UE.

[0207] Clause 40. The location server of any of clauses 36 to 39, wherein the trajectory of the UE is based on a known topology of a route on which the UE is traveling.

[0208] Clause 41. The location server of clause 40, wherein the route comprises a train track.

[0209] Clause 42. The location server of any of clauses 36 to 41, wherein the at least one processor is further configured to: receive, via the at least one transceiver, from the UE via LPP signaling, positioning measurements of the one or more PRS resources; or receive, via the at least one transceiver, from the RAN controller entity via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

[0210] Clause 43. The location server of clause 42, wherein the request for the RAN data analytics further includes the positioning measurements of the one or more PRS resources.

[0211] Clause 44. The location server of any of clauses 36 to 43, wherein the one or more PRS resources comprise: one or more downlink PRS resources, one or more uplink PRS resources, one or more sidelink PRS resources, or any combination thereof.

[0212] Clause 45. The location server of any of clauses 31 to 44, wherein messages exchanged between the location server and the UE during the positioning session are not exchanged via the RAN controller entity.

[0213] Clause 46. The location server of any of clauses 31 to 44, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

[0214] Clause 47. The location server of any of clauses 31 to 46, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

[0215] Clause 48. A radio access network (RAN) entity, comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: receive, via the at least one transceiver, from a location server, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE) to determine a location of the UE, the request including at least an identifier of the positioning session; and transmit, via the at least one transceiver, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics.

[0216] Clause 49. The RAN controller entity of clause 48, wherein: the request for the RAN data analytics is received via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is transmitted via the Y 1 interface.

[0217] Clause 50. The RAN controller entity of any of clauses 48 to 49, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC). [0218] Clause 51. The RAN controller entity of any of clauses 48 to 50, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

[0219] Clause 52. The RAN controller entity of any of clauses 48 to 51, wherein the identifier of the positioning session comprises an LPP session identifier.

[0220] Clause 53. The RAN controller entity of any of clauses 48 to 52, wherein the at least one processor is further configured to: generate a RAN-specific identifier for the positioning session based on the identifier of the positioning session.

[0221] Clause 54. The RAN controller entity of any of clauses 48 to 53, wherein the RAN data analytics comprise: a positioning method to use for the positioning session, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning session, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning session, a trajectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

[0222] Clause 55. The RAN controller entity of clause 54, wherein the at least one processor is further configured to: determine the positioning method to use for the positioning session based on: positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning session, an environmental scenario of the UE, or any combination thereof.

[0223] Clause 56. The RAN controller entity of clause 55, wherein the at least one processor is further configured to: receive, via the at least one transceiver, from the UE, the positioning capabilities of the UE; or receive, via the at least one transceiver, from the location server, the positioning capabilities of the UE.

[0224] Clause 57. The RAN controller entity of any of clauses 54 to 56, wherein the at least one processor is further configured to: receive, via the at least one transceiver, from the UE via radio resource control (RRC) signaling, positioning measurements of the one or more PRS resources; and transmit, via the at least one transceiver, to the location server via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources. [0225] Clause 58. The RAN controller entity of any of clauses 54 to 57, wherein the request for the RAN data analytics further includes positioning measurements of the one or more PRS resources obtained by the UE.

[0226] Clause 59. The RAN controller entity of any of clauses 48 to 58, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

[0227] Clause 60. The RAN controller entity of any of clauses 48 to 59, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

[0228] Clause 61. A location server, comprising: means for establishing a positioning session with a user equipment (UE) to determine a location of the UE; means for transmitting, to a radio access network (RAN) entity, a request for RAN data analytics associated with the positioning session with the UE, the request including at least an identifier of the positioning session; means for receiving, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics; and means for performing, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine the location of the UE.

[0229] Clause 62. The location server of clause 61, wherein: the request for the RAN data analytics is transmitted via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is received via the Y 1 interface.

[0230] Clause 63. The location server of any of clauses 61 to 62, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

[0231] Clause 64. The location server of any of clauses 61 to 63, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

[0232] Clause 65. The location server of any of clauses 61 to 64, wherein the identifier of the positioning session comprises an LPP session identifier.

[0233] Clause 66. The location server of any of clauses 61 to 65, wherein the RAN data analytics comprise: a positioning method to use for the positioning procedure, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning procedure, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning procedure, a trajectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

[0234] Clause 67. The location server of clause 66, wherein a determination of the positioning method to use for the positioning procedure is based on: positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning procedure, an environmental scenario of the UE, or any combination thereof.

[0235] Clause 68. The location server of clause 67, wherein the environmental scenario is based on a probability of the UE being in a line-of-sight (LOS) scenario or a non-line-of-sight (NLOS) scenario with respect to one or more radio units (RUs) available for the positioning procedure.

[0236] Clause 69. The location server of any of clauses 67 to 68, further comprising: means for receiving, from the UE, the positioning capabilities of the UE; and means for transmitting, to the RAN controller entity, the positioning capabilities of the UE.

[0237] Clause 70. The location server of any of clauses 66 to 69, wherein the trajectory of the UE is based on a known topology of a route on which the UE is traveling.

[0238] Clause 71. The location server of clause 70, wherein the route comprises a train track.

[0239] Clause 72. The location server of any of clauses 66 to 71, further comprising: means for receiving, from the UE via LPP signaling, positioning measurements of the one or more PRS resources; or means for receiving, from the RAN controller entity via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

[0240] Clause 73. The location server of clause 72, wherein the request for the RAN data analytics further includes the positioning measurements of the one or more PRS resources.

[0241] Clause 74. The location server of any of clauses 66 to 73, wherein the one or more PRS resources comprise: one or more downlink PRS resources, one or more uplink PRS resources, one or more sidelink PRS resources, or any combination thereof.

[0242] Clause 75. The location server of any of clauses 61 to 74, wherein messages exchanged between the location server and the UE during the positioning session are not exchanged via the RAN controller entity. [0243] Clause 76. The location server of any of clauses 61 to 74, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

[0244] Clause 77. The location server of any of clauses 61 to 76, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

[0245] Clause 78. A radio access network (RAN) entity, comprising: means for receiving, from a location server, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE) to determine a location of the UE, the request including at least an identifier of the positioning session; and means for transmitting, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics.

[0246] Clause 79. The RAN controller entity of clause 78, wherein: the request for the RAN data analytics is received via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is transmitted via the Y 1 interface.

[0247] Clause 80. The RAN controller entity of any of clauses 78 to 79, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

[0248] Clause 81. The RAN controller entity of any of clauses 78 to 80, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

[0249] Clause 82. The RAN controller entity of any of clauses 78 to 81, wherein the identifier of the positioning session comprises an LPP session identifier.

[0250] Clause 83. The RAN controller entity of any of clauses 78 to 82, further comprising: means for generating a RAN-specific identifier for the positioning session based on the identifier of the positioning session.

[0251] Clause 84. The RAN controller entity of any of clauses 78 to 83, wherein the RAN data analytics comprise: a positioning method to use for the positioning session, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning session, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning session, a trajectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

[0252] Clause 85. The RAN controller entity of clause 84, further comprising: means for determining the positioning method to use for the positioning session based on: positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning session, an environmental scenario of the UE, or any combination thereof.

[0253] Clause 86. The RAN controller entity of clause 85, further comprising: means for receiving, from the UE, the positioning capabilities of the UE; or means for receiving, from the location server, the positioning capabilities of the UE.

[0254] Clause 87. The RAN controller entity of any of clauses 84 to 86, further comprising: means for receiving, from the UE via radio resource control (RRC) signaling, positioning measurements of the one or more PRS resources; and means for transmitting, to the location server via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

[0255] Clause 88. The RAN controller entity of any of clauses 84 to 87, wherein the request for the RAN data analytics further includes positioning measurements of the one or more PRS resources obtained by the UE.

[0256] Clause 89. The RAN controller entity of any of clauses 78 to 88, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

[0257] Clause 90. The RAN controller entity of any of clauses 78 to 89, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

[0258] Clause 91. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to: establish a positioning session with a user equipment (UE) to determine a location of the UE; transmit, to a radio access network (RAN) entity, a request for RAN data analytics associated with the positioning session with the UE, the request including at least an identifier of the positioning session; receive, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics; and perform, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine the location of the UE.

[0259] Clause 92. The non-transitory computer-readable medium of clause 91, wherein: the request for the RAN data analytics is transmitted via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is received via the Y1 interface.

[0260] Clause 93. The non-transitory computer-readable medium of any of clauses 91 to 92, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

[0261] Clause 94. The non-transitory computer-readable medium of any of clauses 91 to 93, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

[0262] Clause 95. The non-transitory computer-readable medium of any of clauses 91 to 94, wherein the identifier of the positioning session comprises an LPP session identifier.

[0263] Clause 96. The non-transitory computer-readable medium of any of clauses 91 to 95, wherein the RAN data analytics comprise: a positioning method to use for the positioning procedure, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning procedure, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning procedure, a traj ectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

[0264] Clause 97. The non-transitory computer-readable medium of clause 96, wherein a determination of the positioning method to use for the positioning procedure is based on: positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning procedure, an environmental scenario of the UE, or any combination thereof.

[0265] Clause 98. The non-transitory computer-readable medium of clause 97, wherein the environmental scenario is based on a probability of the UE being in a line-of-sight (LOS) scenario or a non-line-of-sight (NLOS) scenario with respect to one or more radio units (RUs) available for the positioning procedure. [0266] Clause 99. The non-transitory computer-readable medium of any of clauses 97 to 98, further comprising computer-executable instructions that, when executed by the location server, cause the location server to: receive, from the UE, the positioning capabilities of the UE; and transmit, to the RAN controller entity, the positioning capabilities of the UE.

[0267] Clause 100. The non-transitory computer-readable medium of any of clauses 96 to 99, wherein the trajectory of the UE is based on a known topology of a route on which the UE is traveling.

[0268] Clause 101. The non-transitory computer-readable medium of clause 100, wherein the route comprises a train track.

[0269] Clause 102. The non-transitory computer-readable medium of any of clauses 96 to 101, further comprising computer-executable instructions that, when executed by the location server, cause the location server to: receive, from the UE via LPP signaling, positioning measurements of the one or more PRS resources; or receive, from the RAN controller entity via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

[0270] Clause 103. The non-transitory computer-readable medium of clause 102, wherein the request for the RAN data analytics further includes the positioning measurements of the one or more PRS resources.

[0271] Clause 104. The non-transitory computer-readable medium of any of clauses 96 to 103, wherein the one or more PRS resources comprise: one or more downlink PRS resources, one or more uplink PRS resources, one or more sidelink PRS resources, or any combination thereof.

[0272] Clause 105. The non-transitory computer-readable medium of any of clauses 91 to 104, wherein messages exchanged between the location server and the UE during the positioning session are not exchanged via the RAN controller entity.

[0273] Clause 106. The non-transitory computer-readable medium of any of clauses 91 to 104, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

[0274] Clause 107. The non-transitory computer-readable medium of any of clauses 91 to 106, wherein the positioning session between the location server and the UE is established via the RAN controller entity. [0275] Clause 108. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a radio access network (RAN) entity, cause the RAN controller entity to: receive, from a location server, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE) to determine a location of the UE, the request including at least an identifier of the positioning session; and transmit, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics.

[0276] Clause 109. The non-transitory computer-readable medium of clause 108, wherein: the request for the RAN data analytics is received via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is transmitted via the Y1 interface.

[0277] Clause 110. The non-transitory computer-readable medium of any of clauses 108 to 109, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

[0278] Clause 111. The non-transitory computer-readable medium of any of clauses 108 to 110, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

[0279] Clause 112. The non-transitory computer-readable medium of any of clauses 108 to 111, wherein the identifier of the positioning session comprises an LPP session identifier.

[0280] Clause 113. The non-transitory computer-readable medium of any of clauses 108 to 112, further comprising computer-executable instructions that, when executed by the RAN controller entity, cause the RAN controller entity to: generate a RAN-specific identifier for the positioning session based on the identifier of the positioning session.

[0281] Clause 114. The non-transitory computer-readable medium of any of clauses 108 to 113, wherein the RAN data analytics comprise: a positioning method to use for the positioning session, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning session, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning session, a trajectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof. [0282] Clause 115. The non-transitory computer-readable medium of clause 114, further comprising computer-executable instructions that, when executed by the RAN controller entity, cause the RAN controller entity to: determine the positioning method to use for the positioning session based on: positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning session, an environmental scenario of the UE, or any combination thereof.

[0283] Clause 116. The non-transitory computer-readable medium of clause 115, further comprising computer-executable instructions that, when executed by the RAN controller entity, cause the RAN controller entity to: receive, from the UE, the positioning capabilities of the UE; or receive, from the location server, the positioning capabilities of the UE.

[0284] Clause 117. The non-transitory computer-readable medium of any of clauses 114 to 116, further comprising computer-executable instructions that, when executed by the RAN controller entity, cause the RAN controller entity to: receive, from the UE via radio resource control (RRC) signaling, positioning measurements of the one or more PRS resources; and transmit, to the location server via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

[0285] Clause 118. The non-transitory computer-readable medium of any of clauses 114 to 117, wherein the request for the RAN data analytics further includes positioning measurements of the one or more PRS resources obtained by the UE.

[0286] Clause 119. The non-transitory computer-readable medium of any of clauses 108 to 118, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

[0287] Clause 120. The non-transitory computer-readable medium of any of clauses 108 to 119, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

[0288] Additional implementation examples are described in the following numbered clauses:

[0289] Clause 1. A method of communication performed by a location server, comprising: transmitting, to a radio access network (RAN) entity, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE), the request including at least an identifier of the positioning session; receiving, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics; and performing, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine a location of the UE.

[0290] Clause 2. The method of clause 1, wherein: the request for the RAN data analytics is transmitted via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is received via the Y 1 interface.

[0291] Clause 3. The method of any of clauses 1 to 2, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

[0292] Clause 4. The method of any of clauses 1 to 3, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

[0293] Clause 5. The method of any of clauses 1 to 4, wherein the identifier of the positioning session comprises an LPP session identifier.

[0294] Clause 6. The method of any of clauses 1 to 5, wherein the RAN data analytics comprise: a positioning method to use for the positioning procedure, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning procedure, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning procedure, a trajectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

[0295] Clause 7. The method of clause 6, wherein a determination of the positioning method to use for the positioning procedure is based on: positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning procedure, an environmental scenario of the UE, or any combination thereof.

[0296] Clause 8. The method of clause 7, wherein the environmental scenario is based on a probability of the UE being in a line-of-sight (LOS) scenario or a non-line-of-sight (NLOS) scenario with respect to one or more radio units (RUs) available for the positioning procedure.

[0297] Clause 9. The method of any of clauses 7 to 8, further comprising: receiving, from the UE, the positioning capabilities of the UE; and transmitting, to the RAN controller entity, the positioning capabilities of the UE. [0298] Clause 10. The method of any of clauses 6 to 9, wherein the trajectory of the UE is based on a known topology of a route on which the UE is traveling.

[0299] Clause 11. The method of clause 10, wherein the route comprises a train track.

[0300] Clause 12. The method of any of clauses 6 to 11, further comprising: receiving, from the UE via LPP signaling, positioning measurements of the one or more PRS resources; or receiving, from the RAN controller entity via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

[0301] Clause 13. The method of any of clauses 6 to 12, wherein the request for the RAN data analytics further includes positioning measurements of the one or more PRS resources received from the UE.

[0302] Clause 14. The method of any of clauses 6 to 13, wherein the one or more PRS resources comprise: one or more downlink PRS resources, one or more uplink PRS resources, one or more sidelink PRS resources, or any combination thereof.

[0303] Clause 15. The method of any of clauses 1 to 14, wherein messages exchanged between the location server and the UE during the positioning session are not exchanged via the RAN controller entity.

[0304] Clause 16. The method of any of clauses 1 to 14, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

[0305] Clause 17. The method of any of clauses 1 to 16, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

[0306] Clause 18. A method of communication performed by a radio access network (RAN) entity, comprising: receiving, from a location server, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE) to determine a location of the UE, the request including at least an identifier of the positioning session; and transmitting, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics.

[0307] Clause 19. The method of clause 18, wherein: the request for the RAN data analytics is received via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is transmitted via the Y1 interface. [0308] Clause 20. The method of any of clauses 18 to 19, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

[0309] Clause 21. The method of any of clauses 18 to 20, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

[0310] Clause 22. The method of any of clauses 18 to 21, wherein the identifier of the positioning session comprises an LPP session identifier.

[0311] Clause 23. The method of any of clauses 18 to 22, further comprising: generating a RAN- specific identifier for the positioning session based on the identifier of the positioning session.

[0312] Clause 24. The method of any of clauses 18 to 23, wherein the RAN data analytics comprise: a positioning method to use for the positioning session, a pattern for one or more positioning reference signal (PRS) resources (e.g., one or more DL-PRS resources, one or more UL-PRS resources, one or more SL-PRS resources, or any combination thereof) to be transmitted and measured during the positioning session, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning session, a trajectory of the UE (e.g., where the trajectory of the UE is based on a known topology of a route, such as a train track, on which the UE is traveling), an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

[0313] Clause 25. The method of clause 24, further comprising: determining the positioning method to use for the positioning session based on positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning session, an environmental scenario of the UE (e.g., where the environmental scenario is based on a probability of the UE being in a line-of-sight (LOS) scenario or a non-line-of-sight (NLOS) scenario with respect to one or more radio units (RUs) available for the positioning procedure), or any combination thereof.

[0314] Clause 26. The method of clause 25, further comprising: receiving, from the UE, the positioning capabilities of the UE; or receiving, from the location server, the positioning capabilities of the UE.

[0315] Clause 27. The method of any of clauses 24 to 26, further comprising: receiving, from the UE via radio resource control (RRC) signaling, positioning measurements of the one or more PRS resources; and transmitting, to the location server via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

[0316] Clause 28. The method of any of clauses 24 to 27, wherein the request for the RAN data analytics further includes positioning measurements of the one or more PRS resources obtained by the UE.

[0317] Clause 29. The method of any of clauses 18 to 28, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

[0318] Clause 30. The method of any of clauses 18 to 29, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

[0319] Clause 31. A location server, comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: transmit, via the at least one transceiver, to a radio access network (RAN) entity, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE), the request including at least an identifier of the positioning session; receive, via the at least one transceiver, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics; and perform, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine a location of the UE.

[0320] Clause 32. The location server of clause 31, wherein: the request for the RAN data analytics is transmitted via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is received via the Y 1 interface.

[0321] Clause 33. The location server of any of clauses 31 to 32, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

[0322] Clause 34. The location server of any of clauses 31 to 33, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

[0323] Clause 35. The location server of any of clauses 31 to 34, wherein the identifier of the positioning session comprises an LPP session identifier.

[0324] Clause 36. The location server of any of clauses 31 to 35, wherein the RAN data analytics comprise: a positioning method to use for the positioning procedure, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning procedure, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning procedure, a trajectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

[0325] Clause 37. The location server of clause 36, wherein a determination of the positioning method to use for the positioning procedure is based on: positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning procedure, an environmental scenario of the UE, or any combination thereof.

[0326] Clause 38. The location server of clause 37, wherein the environmental scenario is based on a probability of the UE being in a line-of-sight (LOS) scenario or a non-line-of-sight (NLOS) scenario with respect to one or more radio units (RUs) available for the positioning procedure.

[0327] Clause 39. The location server of any of clauses 37 to 38, wherein the at least one processor is further configured to: receive, via the at least one transceiver, from the UE, the positioning capabilities of the UE; and transmit, via the at least one transceiver, to the RAN controller entity, the positioning capabilities of the UE.

[0328] Clause 40. The location server of any of clauses 36 to 39, wherein the trajectory of the UE is based on a known topology of a route on which the UE is traveling.

[0329] Clause 41. The location server of clause 40, wherein the route comprises a train track.

[0330] Clause 42. The location server of any of clauses 36 to 41, wherein the at least one processor is further configured to: receive, via the at least one transceiver, from the UE via LPP signaling, positioning measurements of the one or more PRS resources; or receive, via the at least one transceiver, from the RAN controller entity via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

[0331] Clause 43. The location server of any of clauses 36 to 42, wherein the request for the RAN data analytics further includes positioning measurements of the one or more PRS resources received from the UE. [0332] Clause 44. The location server of any of clauses 36 to 43, wherein the one or more PRS resources comprise: one or more downlink PRS resources, one or more uplink PRS resources, one or more sidelink PRS resources, or any combination thereof.

[0333] Clause 45. The location server of any of clauses 31 to 44, wherein messages exchanged between the location server and the UE during the positioning session are not exchanged via the RAN controller entity.

[0334] Clause 46. The location server of any of clauses 31 to 44, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

[0335] Clause 47. The location server of any of clauses 31 to 46, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

[0336] Clause 48. A radio access network (RAN) entity, comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: receive, via the at least one transceiver, from a location server, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE) to determine a location of the UE, the request including at least an identifier of the positioning session; and transmit, via the at least one transceiver, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics.

[0337] Clause 49. The RAN controller entity of clause 48, wherein: the request for the RAN data analytics is received via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is transmitted via the Y 1 interface.

[0338] Clause 50. The RAN controller entity of any of clauses 48 to 49, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

[0339] Clause 51. The RAN controller entity of any of clauses 48 to 50, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

[0340] Clause 52. The RAN controller entity of any of clauses 48 to 51, wherein the identifier of the positioning session comprises an LPP session identifier. [0341] Clause 53. The RAN controller entity of any of clauses 48 to 52, wherein the at least one processor is further configured to: generate a RAN-specific identifier for the positioning session based on the identifier of the positioning session.

[0342] Clause 54. The RAN controller entity of any of clauses 48 to 53, wherein the RAN data analytics comprise: a positioning method to use for the positioning session, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning session, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning session, a trajectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

[0343] Clause 55. The RAN controller entity of clause 54, wherein the at least one processor is further configured to: determine the positioning method to use for the positioning session based on: positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning session, an environmental scenario of the UE, or any combination thereof.

[0344] Clause 56. The RAN controller entity of clause 55, wherein the at least one processor is further configured to: receive, via the at least one transceiver, from the UE, the positioning capabilities of the UE; or receive, via the at least one transceiver, from the location server, the positioning capabilities of the UE.

[0345] Clause 57. The RAN controller entity of any of clauses 54 to 56, wherein the at least one processor is further configured to: receive, via the at least one transceiver, from the UE via radio resource control (RRC) signaling, positioning measurements of the one or more PRS resources; and transmit, via the at least one transceiver, to the location server via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

[0346] Clause 58. The RAN controller entity of any of clauses 54 to 57, wherein the request for the RAN data analytics further includes positioning measurements of the one or more PRS resources obtained by the UE.

[0347] Clause 59. The RAN controller entity of any of clauses 48 to 58, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity. [0348] Clause 60. The RAN controller entity of any of clauses 48 to 59, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

[0349] Clause 61. A location server, comprising: means for transmitting, to a radio access network (RAN) entity, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE), the request including at least an identifier of the positioning session; means for receiving, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics; and means for performing, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine a location of the UE.

[0350] Clause 62. The location server of clause 61, wherein: the request for the RAN data analytics is transmitted via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is received via the Y 1 interface.

[0351] Clause 63. The location server of any of clauses 61 to 62, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

[0352] Clause 64. The location server of any of clauses 61 to 63, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

[0353] Clause 65. The location server of any of clauses 61 to 64, wherein the identifier of the positioning session comprises an LPP session identifier.

[0354] Clause 66. The location server of any of clauses 61 to 65, wherein the RAN data analytics comprise: a positioning method to use for the positioning procedure, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning procedure, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning procedure, a trajectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

[0355] Clause 67. The location server of clause 66, wherein a determination of the positioning method to use for the positioning procedure is based on: positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning procedure, an environmental scenario of the UE, or any combination thereof.

[0356] Clause 68. The location server of clause 67, wherein the environmental scenario is based on a probability of the UE being in a line-of-sight (LOS) scenario or a non-line-of-sight (NLOS) scenario with respect to one or more radio units (RUs) available for the positioning procedure.

[0357] Clause 69. The location server of any of clauses 67 to 68, further comprising: means for receiving, from the UE, the positioning capabilities of the UE; and means for transmitting, to the RAN controller entity, the positioning capabilities of the UE.

[0358] Clause 70. The location server of any of clauses 66 to 69, wherein the trajectory of the UE is based on a known topology of a route on which the UE is traveling.

[0359] Clause 71. The location server of clause 70, wherein the route comprises a train track.

[0360] Clause 72. The location server of any of clauses 66 to 71, further comprising: means for receiving, from the UE via LPP signaling, positioning measurements of the one or more PRS resources; or means for receiving, from the RAN controller entity via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

[0361] Clause 73. The location server of any of clauses 66 to 72, wherein the request for the RAN data analytics further includes positioning measurements of the one or more PRS resources received from the UE.

[0362] Clause 74. The location server of any of clauses 66 to 73, wherein the one or more PRS resources comprise: one or more downlink PRS resources, one or more uplink PRS resources, one or more sidelink PRS resources, or any combination thereof.

[0363] Clause 75. The location server of any of clauses 61 to 74, wherein messages exchanged between the location server and the UE during the positioning session are not exchanged via the RAN controller entity.

[0364] Clause 76. The location server of any of clauses 61 to 74, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

[0365] Clause 77. The location server of any of clauses 61 to 76, wherein the positioning session between the location server and the UE is established via the RAN controller entity. [0366] Clause 78. A radio access network (RAN) entity, comprising: means for receiving, from a location server, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE) to determine a location of the UE, the request including at least an identifier of the positioning session; and means for transmitting, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics.

[0367] Clause 79. The RAN controller entity of clause 78, wherein: the request for the RAN data analytics is received via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is transmitted via the Y 1 interface.

[0368] Clause 80. The RAN controller entity of any of clauses 78 to 79, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

[0369] Clause 81. The RAN controller entity of any of clauses 78 to 80, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

[0370] Clause 82. The RAN controller entity of any of clauses 78 to 81, wherein the identifier of the positioning session comprises an LPP session identifier.

[0371] Clause 83. The RAN controller entity of any of clauses 78 to 82, further comprising: means for generating a RAN-specific identifier for the positioning session based on the identifier of the positioning session.

[0372] Clause 84. The RAN controller entity of any of clauses 78 to 83, wherein the RAN data analytics comprise: a positioning method to use for the positioning session, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning session, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning session, a trajectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

[0373] Clause 85. The RAN controller entity of clause 84, further comprising: means for determining the positioning method to use for the positioning session based on: positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning session, an environmental scenario of the UE, or any combination thereof.

[0374] Clause 86. The RAN controller entity of clause 85, further comprising: means for receiving, from the UE, the positioning capabilities of the UE; or means for receiving, from the location server, the positioning capabilities of the UE.

[0375] Clause 87. The RAN controller entity of any of clauses 84 to 86, further comprising: means for receiving, from the UE via radio resource control (RRC) signaling, positioning measurements of the one or more PRS resources; and means for transmitting, to the location server via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

[0376] Clause 88. The RAN controller entity of any of clauses 84 to 87, wherein the request for the RAN data analytics further includes positioning measurements of the one or more PRS resources obtained by the UE.

[0377] Clause 89. The RAN controller entity of any of clauses 78 to 88, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

[0378] Clause 90. The RAN controller entity of any of clauses 78 to 89, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

[0379] Clause 91. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to: transmit, to a radio access network (RAN) entity, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE), the request including at least an identifier of the positioning session; receive, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics; and perform, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine a location of the UE.

[0380] Clause 92. The non-transitory computer-readable medium of clause 91, wherein: the request for the RAN data analytics is transmitted via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is received via the Y1 interface. [0381] Clause 93. The non -transitory computer-readable medium of any of clauses 91 to 92, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

[0382] Clause 94. The non-transitory computer-readable medium of any of clauses 91 to 93, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

[0383] Clause 95. The non-transitory computer-readable medium of any of clauses 91 to 94, wherein the identifier of the positioning session comprises an LPP session identifier.

[0384] Clause 96. The non-transitory computer-readable medium of any of clauses 91 to 95, wherein the RAN data analytics comprise: a positioning method to use for the positioning procedure, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning procedure, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning procedure, a traj ectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

[0385] Clause 97. The non-transitory computer-readable medium of clause 96, wherein a determination of the positioning method to use for the positioning procedure is based on: positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning procedure, an environmental scenario of the UE, or any combination thereof.

[0386] Clause 98. The non-transitory computer-readable medium of clause 97, wherein the environmental scenario is based on a probability of the UE being in a line-of-sight (LOS) scenario or a non-line-of-sight (NLOS) scenario with respect to one or more radio units (RUs) available for the positioning procedure.

[0387] Clause 99. The non-transitory computer-readable medium of any of clauses 97 to 98, further comprising computer-executable instructions that, when executed by the location server, cause the location server to: receive, from the UE, the positioning capabilities of the UE; and transmit, to the RAN controller entity, the positioning capabilities of the UE.

[0388] Clause 100. The non-transitory computer-readable medium of any of clauses 96 to 99, wherein the trajectory of the UE is based on a known topology of a route on which the UE is traveling. [0389] Clause 101. The non-transitory computer-readable medium of clause 100, wherein the route comprises a train track.

[0390] Clause 102. The non-transitory computer-readable medium of any of clauses 96 to 101, further comprising computer-executable instructions that, when executed by the location server, cause the location server to: receive, from the UE via LPP signaling, positioning measurements of the one or more PRS resources; or receive, from the RAN controller entity via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

[0391] Clause 103. The non-transitory computer-readable medium of any of clauses 96 to 102, wherein the request for the RAN data analytics further includes positioning measurements of the one or more PRS resources received from the UE.

[0392] Clause 104. The non-transitory computer-readable medium of any of clauses 96 to 103, wherein the one or more PRS resources comprise: one or more downlink PRS resources, one or more uplink PRS resources, one or more sidelink PRS resources, or any combination thereof.

[0393] Clause 105. The non-transitory computer-readable medium of any of clauses 91 to 104, wherein messages exchanged between the location server and the UE during the positioning session are not exchanged via the RAN controller entity.

[0394] Clause 106. The non-transitory computer-readable medium of any of clauses 91 to 104, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

[0395] Clause 107. The non-transitory computer-readable medium of any of clauses 91 to 106, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

[0396] Clause 108. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a radio access network (RAN) entity, cause the RAN controller entity to: receive, from a location server, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE) to determine a location of the UE, the request including at least an identifier of the positioning session; and transmit, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics. [0397] Clause 109. The non-transitory computer-readable medium of clause 108, wherein: the request for the RAN data analytics is received via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is transmitted via the Y1 interface.

[0398] Clause 110. The non-transitory computer-readable medium of any of clauses 108 to 109, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

[0399] Clause 111. The non-transitory computer-readable medium of any of clauses 108 to 110, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

[0400] Clause 112. The non-transitory computer-readable medium of any of clauses 108 to 111, wherein the identifier of the positioning session comprises an LPP session identifier.

[0401] Clause 113. The non-transitory computer-readable medium of any of clauses 108 to 112, further comprising computer-executable instructions that, when executed by the RAN controller entity, cause the RAN controller entity to: generate a RAN-specific identifier for the positioning session based on the identifier of the positioning session.

[0402] Clause 114. The non-transitory computer-readable medium of any of clauses 108 to 113, wherein the RAN data analytics comprise: a positioning method to use for the positioning session, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning session, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning session, a trajectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

[0403] Clause 115. The non-transitory computer-readable medium of clause 114, further comprising computer-executable instructions that, when executed by the RAN controller entity, cause the RAN controller entity to: determine the positioning method to use for the positioning session based on: positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning session, an environmental scenario of the UE, or any combination thereof.

[0404] Clause 116. The non-transitory computer-readable medium of clause 115, further comprising computer-executable instructions that, when executed by the RAN controller entity, cause the RAN controller entity to: receive, from the UE, the positioning capabilities of the UE; or receive, from the location server, the positioning capabilities of the UE.

[0405] Clause 117. The non-transitory computer-readable medium of any of clauses 114 to 116, further comprising computer-executable instructions that, when executed by the RAN controller entity, cause the RAN controller entity to: receive, from the UE via radio resource control (RRC) signaling, positioning measurements of the one or more PRS resources; and transmit, to the location server via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

[0406] Clause 118. The non-transitory computer-readable medium of any of clauses 114 to 117, wherein the request for the RAN data analytics further includes positioning measurements of the one or more PRS resources obtained by the UE.

[0407] Clause 119. The non-transitory computer-readable medium of any of clauses 108 to 118, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

[0408] Clause 120. The non-transitory computer-readable medium of any of clauses 108 to 119, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

[0409] Those of skill in the art will appreciate that information and signals 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 above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

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

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

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

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

[0414] 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 not be interpreted as “one and more”). Furthermore, although components, functions, actions, and instructions may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Accordingly, as used herein, the articles “a,” “an,” “the,” and “said” are intended to include one or more of the stated elements. Additionally, as used herein, the terms “at least one” and “one or more” encompass “one” component, function, action, or instruction performing or capable of performing a described or claimed functionality and also “two or more” components, functions, actions, or instructions performing or capable of performing a described or claimed functionality in combination.

Claims

CLAIMS What is claimed is:

1. A method of communication performed by a location server, comprising: transmitting, to a radio access network (RAN) controller entity, a request for

RAN data analytics associated with a positioning session between the location server and a user equipment (UE), the request including at least an identifier of the positioning session; receiving, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics; and performing, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine a location of the UE.

2. The method of claim 1, wherein: the request for the RAN data analytics is transmitted via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is received via the Y 1 interface.

3. The method of claim 1, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

4. The method of claim 1, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

5. The method of claim 1, wherein the identifier of the positioning session comprises an LPP session identifier.

6. The method of claim 1, wherein the RAN data analytics comprise: a positioning method to use for the positioning procedure, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning procedure, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning procedure, a trajectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

7. The method of claim 6, wherein a determination of the positioning method to use for the positioning procedure is based on: positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning procedure, an environmental scenario of the UE, or any combination thereof.

8. The method of claim 7, wherein the environmental scenario is based on a probability of the UE being in a line-of-sight (LOS) scenario or a non-line-of-sight (NLOS) scenario with respect to one or more radio units (RUs) available for the positioning procedure.

9. The method of claim 7, further comprising: receiving, from the UE, the positioning capabilities of the UE; and transmitting, to the RAN controller entity, the positioning capabilities of the UE.

10. The method of claim 6, wherein the trajectory of the UE is based on a known topology of a route on which the UE is traveling.

11. The method of claim 10, wherein the route comprises a train track.

12. The method of claim 6, further comprising: receiving, from the UE via Long-Term Evolution (LTE) positioning protocol (LPP) signaling, positioning measurements of the one or more PRS resources; or receiving, from the RAN controller entity via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

13. The method of claim 6, wherein the request for the RAN data analytics further includes positioning measurements of the one or more PRS resources received from the UE.

14. The method of claim 6, wherein the one or more PRS resources comprise: one or more downlink PRS resources, one or more uplink PRS resources, one or more sidelink PRS resources, or any combination thereof.

15. The method of claim 1, wherein messages exchanged between the location server and the UE during the positioning session are not exchanged via the RAN controller entity.

16. The method of claim 1, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

17. The method of claim 1, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

18. A method of communication performed by a radio access network (RAN) controller entity, comprising: receiving, from a location server, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE) to determine a location of the UE, the request including at least an identifier of the positioning session; and transmitting, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics.

19. The method of claim 18, wherein: the request for the RAN data analytics is received via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is transmitted via the Y 1 interface.

20. The method of claim 18, wherein the RAN controller entity comprises a near- real time RAN intelligent controller (RIC).

21. The method of claim 18, wherein the positioning session comprises a Long- Term Evolution (LTE) positioning protocol (LPP) positioning session.

22. The method of claim 18, wherein the identifier of the positioning session comprises an LPP session identifier.

23. The method of claim 18, further comprising: generating a RAN-specific identifier for the positioning session based on the identifier of the positioning session.

24. The method of claim 18, wherein the RAN data analytics comprise: a positioning method to use for the positioning session, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning session, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning session, a trajectory of the UE, types of network nodes deployed in a vicinity of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

25. The method of claim 24, further comprising: determining the positioning method to use for the positioning session based on positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning session, an environmental scenario of the UE, or any combination thereof.

26. The method of claim 25, further comprising: receiving, from the UE, the positioning capabilities of the UE; or receiving, from the location server, the positioning capabilities of the UE.

27. The method of claim 24, further comprising: receiving, from the UE via radio resource control (RRC) signaling, positioning measurements of the one or more PRS resources; and transmitting, to the location server via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

28. The method of claim 24, wherein the request for the RAN data analytics further includes positioning measurements of the one or more PRS resources obtained by the UE.

29. The method of claim 18, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

30. The method of claim 18, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

31. A location server, 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 radio access network (RAN) controller entity, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE), the request including at least an identifier of the positioning session; receive, via the one or more transceivers, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics; and perform, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine a location of the UE.

32. The location server of claim 31, wherein: the request for the RAN data analytics is transmitted via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is received via the Y 1 interface.

33. The location server of claim 31, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

34. The location server of claim 31, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

35. The location server of claim 31, wherein the identifier of the positioning session comprises an LPP session identifier.

36. The location server of claim 31, wherein the RAN data analytics comprise: a positioning method to use for the positioning procedure, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning procedure, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning procedure, a trajectory of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

37. The location server of claim 36, wherein a determination of the positioning method to use for the positioning procedure is based on: positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning procedure, an environmental scenario of the UE, or any combination thereof.

38. The location server of claim 37, wherein the environmental scenario is based on a probability of the UE being in a line-of-sight (LOS) scenario or a non-line-of-sight (NLOS) scenario with respect to one or more radio units (RUs) available for the positioning procedure.

39. The location server of claim 37, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, from the UE, the positioning capabilities of the UE; and transmit, via the one or more transceivers, to the RAN controller entity, the positioning capabilities of the UE.

40. The location server of claim 36, wherein the trajectory of the UE is based on a known topology of a route on which the UE is traveling.

41. The location server of claim 40, wherein the route comprises a train track.

42. The location server of claim 36, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, from the UE via Long-Term Evolution (LTE) positioning protocol (LPP) signaling, positioning measurements of the one or more PRS resources; or receive, via the one or more transceivers, from the RAN controller entity via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

43. The location server of claim 36, wherein the request for the RAN data analytics further includes positioning measurements of the one or more PRS resources received from the UE.

44. The location server of claim 36, wherein the one or more PRS resources comprise: one or more downlink PRS resources, one or more uplink PRS resources, one or more sidelink PRS resources, or any combination thereof.

45. The location server of claim 31, wherein messages exchanged between the location server and the UE during the positioning session are not exchanged via the RAN controller entity.

46. The location server of claim 31, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

47. The location server of claim 31, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

48. A radio access network (RAN) controller 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 location server, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE) to determine a location of the UE, the request including at least an identifier of the positioning session; and transmit, via the one or more transceivers, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics.

49. The RAN controller entity of claim 48, wherein: the request for the RAN data analytics is received via a Y1 interface between the location server and the RAN controller entity, and the response to the request for the RAN data analytics is transmitted via the Y 1 interface.

50. The RAN controller entity of claim 48, wherein the RAN controller entity comprises a near-real time RAN intelligent controller (RIC).

51. The RAN controller entity of claim 48, wherein the positioning session comprises a Long-Term Evolution (LTE) positioning protocol (LPP) positioning session.

52. The RAN controller entity of claim 48, wherein the identifier of the positioning session comprises an LPP session identifier.

53. The RAN controller entity of claim 48, wherein the one or more processors, either alone or in combination, are further configured to: generate a RAN-specific identifier for the positioning session based on the identifier of the positioning session.

54. The RAN controller entity of claim 48, wherein the RAN data analytics comprise: a positioning method to use for the positioning session, a pattern for one or more positioning reference signal (PRS) resources to be transmitted and measured during the positioning session, a muting pattern for the one or more PRS resources, an identification of one or more positioning reference units (PRUs) available for the positioning session, a trajectory of the UE, types of network nodes deployed in a vicinity of the UE, an inference model for determining the location of the UE, types of network nodes deployed in a vicinity of the UE, or any combination thereof.

55. The RAN controller entity of claim 54, wherein the one or more processors, either alone or in combination, are further configured to: determine the positioning method to use for the positioning session based on positioning capabilities of the UE, a requested accuracy of the location of the UE, a response time for the positioning session, an environmental scenario of the UE, or any combination thereof.

56. The RAN controller entity of claim 55, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, from the UE, the positioning capabilities of the UE; or receive, via the one or more transceivers, from the location server, the positioning capabilities of the UE.

57. The RAN controller entity of claim 54, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, from the UE via radio resource control (RRC) signaling, positioning measurements of the one or more PRS resources; and transmit, via the one or more transceivers, to the location server via New Radio positioning protocol type A (NRPPa) signaling, the positioning measurements of the one or more PRS resources.

58. The RAN controller entity of claim 54, wherein the request for the RAN data analytics further includes positioning measurements of the one or more PRS resources obtained by the UE.

59. The RAN controller entity of claim 48, wherein messages exchanged between the location server and the UE during the positioning session are exchanged via the RAN controller entity.

60. The RAN controller entity of claim 48, wherein the positioning session between the location server and the UE is established via the RAN controller entity.

61. A location server, comprising: means for transmitting, to a radio access network (RAN) controller entity, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE), the request including at least an identifier of the positioning session; means for receiving, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics; and means for performing, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine a location of the UE.

62. A radio access network (RAN) controller entity, comprising: means for receiving, from a location server, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE) to determine a location of the UE, the request including at least an identifier of the positioning session; and means for transmitting, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics.

63. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to: transmit, to a radio access network (RAN) controller entity, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE), the request including at least an identifier of the positioning session; receive, from the RAN controller entity, a response to the request for the RAN data analytics, the response including the RAN data analytics; and perform, based at least in part on the RAN data analytics, a positioning procedure with the UE to determine a location of the UE.

64. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a radio access network (RAN) controller entity, cause the RAN controller entity to: receive, from a location server, a request for RAN data analytics associated with a positioning session between the location server and a user equipment (UE) to determine a location of the UE, the request including at least an identifier of the positioning session; and transmit, to the location server, a response to the request for the RAN data analytics, the response including the RAN data analytics.