User Equipment (UE)-Based Radio Frequency Fingerprint (RFFP) Positioning Using Downlink Positioning Reference Signals

Abstract

Techniques for wireless communication are disclosed. In one aspect, a user equipment (UE) transmits one or more provisioning capability messages indicating at least a first set of the UE's capabilities for participating in a downlink radio frequency fingerprint (DL-RFFP) positioning procedure to a location server, and receives one or more positioning assistance data messages for the DL-RFFP positioning procedure from the location server, based at least on the first set of capabilities.

Description

Technical Field

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

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

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

Summary of the Invention

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

[0005] In one aspect, a method of wireless communication performed by a user equipment (UE) includes transmitting, to a location server, one or more providing-capability messages indicating at least a first set of the UE's capabilities for participating in downlink radio frequency fingerprint (DL-RFFP) positioning procedures, and receiving, from the location server, one or more positioning assistance data messages for the DL-RFFP positioning procedures based at least on the first set of capabilities.

[0006] In one aspect, a user equipment (UE) comprises 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 transmitting, via the at least one transceiver, one or more offering capability messages indicating at least a first set of the UE's capabilities for participating in downlink radio frequency fingerprint (DL-RFFP) positioning procedures to a location server, and receiving, via the at least one transceiver, one or more positioning assistance data messages for the DL-RFFP positioning procedures based at least on the first set of capabilities from the location server, and is configured to do so.

[0007] In one aspect, a user equipment (UE) includes means for transmitting to a location server one or more offering capability messages indicating at least a first set of the UE's capabilities for participating in downlink radio frequency fingerprint (DL-RFFP) positioning procedures, and means for receiving from the location server one or more positioning assistance data messages for the DL-RFFP positioning procedures based at least on the first set of capabilities.

[0008] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a user equipment (UE), cause the UE to transmit to a location server one or more offering capability messages indicating at least a first set of the UE's capabilities for participating in downlink radio frequency fingerprint (DL-RFFP) positioning procedures, and to receive from the location server one or more positioning assistance data messages for the DL-RFFP positioning procedures based at least on the first set of capabilities.

[0009] Other objects and advantages related to the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description.

[0010] The accompanying drawings are presented to assist in the description of various aspects of the present disclosure and are provided only for purposes of exemplifying the aspects, not for limiting the aspects.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2A

Figure 2B

Figure 2C

Figure 3A

Figure 3B

Figure 3C

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

DETAILED DESCRIPTION OF THE INVENTION

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

[0013] As used herein, the terms "exemplary" and / or "example" are used to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" should not necessarily be construed as preferred or advantageous over other aspects. Similarly, the term "aspects of the present disclosure" does not necessarily require that all aspects of the present disclosure include the features, advantages, or modes of operation being discussed.

[0014] Those skilled in the art will understand 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 referred to throughout the following description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof, depending in part on a particular application, desired design, corresponding technology, and the like.

[0015] Furthermore, many aspects will be described from the perspective of sequences of actions that, for example, would be performed by elements of a computing device. It will be recognized that the various actions described herein can be implemented by a particular circuit (e.g., application specific integrated circuits (ASICs)), by program instructions executed by one or more processors, or by a combination of both. Additionally, the sequence(s) of actions described herein, when executed, can be considered to be fully embodied within any form of non-transitory computer-readable storage medium that stores a corresponding set of computer instructions that, when executed, cause the relevant processor(s) of the device to perform or cause to be performed the functionality described herein. Thus, the various aspects of the present disclosure can be embodied in several different forms, all of which are intended to fall within the scope of the claimed subject matter. Additionally, for each of the aspects described herein, a corresponding form of any such aspect can be described herein, for example, as “logic configured to” perform the described action.

[0016] As used herein, the terms "user equipment" (UE) and "base station" are not intended to be specific to, or limited to, any particular radio access technology (RAT) unless otherwise specified. Generally, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., a mobile phone, router, tablet computer, laptop computer, consumer location device, wearable (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.). The UE may be mobile or (e.g., for a certain period of time) stationary and may communicate with a radio access network (RAN). The term "UE" as used herein may be interchangeably referred to as "access terminal" or "AT", "client device", "wireless device", "subscriber device", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile device", "mobile terminal", "mobile station", or variations thereof. Generally, a UE can communicate with a core network via a RAN, and through the core network, the UE can be connected to an external network such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as via a wired access network, a wireless local area network (WLAN) network (e.g., based on Institute of Electrical and Electronics Engineers (IEEE) 802.11 specifications, etc.).

[0017] The base station may operate according to one of several RATs that the base station is communicating with the UE according to the network in which the base station is deployed. Alternatively, it may be called an access point (AP), a network node, a Node B, an evolved Node B (eNB), a next generation eNB (ng-eNB), a New Radio (NR) Node B (also called a gNB or g-node B), etc. The base station can be mainly used to support wireless access by the UE, including supporting data, voice, and / or signaling connections for the supported UE. In some systems, the base station may provide only the edge node signaling function, while in other systems, the base station may provide additional control and / or network management functions. The communication link through which the UE can send a signal to the base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link through which the base station can transmit a signal to the UE is called a downlink (DL) channel or a forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). The term traffic channel (TCH) as used herein may refer to either an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0018] The term "base station" may refer to a single physical transmission-reception point (TRP) or multiple physical TRPs that may or may not be collocated. For example, when the term "base station" refers to a single physical TRP, that physical TRP may be the base station's antenna corresponding to the base station's cell (or some cell sectors). When the term "base station" refers to multiple collocated physical TRPs, the physical TRPs may be an array of antennas of the base station (such as in a multiple-input multiple-output (MIMO) system or when the base station employs beamforming). When the term "base station" refers to multiple non-collocated 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-collocated physical TRPs may be the serving base station that receives measurement value reports from the UE and neighboring base stations whose reference radio frequency (RF) signals the UE is measuring. Since a TRP is the point from which the base station transmits and receives wireless signals, references to transmissions from the base station or receptions at the base station as used herein should be understood to refer to a specific TRP of the base station.

[0019] In some implementations that support UE positioning, the base station may not support wireless access by the UE (e.g., may not support a data connection, a voice connection, and / or a signaling connection for the UE), but instead may send to the UE a reference signal to be measured by the UE and / or may receive and measure a signal sent by the UE. Such a base station may be referred to as a positioning beacon (e.g., when sending a signal to the UE) and / or a location measurement unit (e.g., when receiving and measuring a signal from the UE).

[0020] An "RF signal" includes an electromagnetic wave of a given frequency that propagates information through the space between a transmitter and a receiver. A transmitter as used herein may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through a multipath channel, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same RF signal transmitted over different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. An RF signal as used herein may also be referred to as a "wireless signal" or simply a "signal" when the context clearly indicates that the term "signal" refers to a wireless signal or an RF signal.

[0021] FIG. 1 shows an exemplary wireless communication system 100 according to an aspect of the present disclosure. (Sometimes referred to as a wireless wide area network (WWAN)) The wireless communication system 100 may include various base stations 102 (labeled "BS") and various UEs 104. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macrocell base stations may include an eNB and / or ng-eNB corresponding to an LTE network of the wireless communication system 100, or a gNB corresponding to an NR network of the wireless communication system 100, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

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

[0023] In addition to other functions, the base station 102 may perform one or more functions related to transferring user data, wireless channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load distribution, delivery of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and device tracing, 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) via a backhaul link 134 that may be wired or wireless.

[0024] The base station 102 can communicate wirelessly with the UE 104. Each of the base stations 102 can provide communication coverage regarding its respective geographical coverage area 110. In one aspect, one or more cells can be supported by the base stations 102 within each geographical coverage area 110. A "cell" is a logical communication entity used for communication with a base station (e.g., via several frequency resources such as those referred to as carrier frequency, component carrier, carrier, band, etc.), and may be associated with an identifier (e.g., physical cell identifier (PCI), enhanced cell identifier (ECI), virtual cell identifier (VCI), cell global identifier (CGI), etc.) for distinguishing cells operating via the same or different carrier frequencies. In some cases, different cells can be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that can provide access to different types of UEs. Since a cell is supported by a specific base station, the term "cell" may, depending on the context, refer to one or both of the logical communication entity and the base station that supports it. Additionally, since the 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 the geographical coverage area (e.g., sector) of a base station as long as a carrier frequency can be detected and used for communication within a certain part of the geographical coverage area 110.

[0025] The geographical coverage area 110 of the neighboring macrocell base station 102 may partially overlap (e.g., in a handover area), and some of the geographical coverage areas 110 may be significantly overlapped by a larger geographical coverage area 110. For example, a small cell base station 102’ (labeled “SC” for “small cell”) may have a geographical coverage area 110’ that significantly overlaps with the geographical coverage area 110 of one or more macrocell base stations 102. A network including both small cell base stations and macrocell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs) that may provide services to a limited group known as a closed subscriber group (CSG).

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

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

[0028] The small cell base station 102' may operate in a licensed frequency spectrum and / or an unlicensed frequency spectrum. When operating in the unlicensed frequency spectrum, the small cell base station 102' may utilize LTE technology 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' adopting LTE / 5G in the unlicensed frequency spectrum may expand the coverage to the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum may be referred to as NR-U. LTE in the unlicensed spectrum may sometimes be referred to as LTE-U, licensed assisted access (LAA), or MulteFire.

[0029] The wireless communication system 100 may further include an mmW base station 180 that communicates with the UE 182 and can operate at millimeter wave (mmW) frequencies and / or near mmW. Extremely high frequency (EHF) is a part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength of 1 millimeter to 10 millimeters. Radio waves within this band can be called millimeter waves. Near mmW can drop down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band ranges from 3 GHz to 30 GHz and is also called centimeter waves. 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 (transmission and / or reception) via the mmW communication link 184 to compensate for the extremely high path loss and short range. Further, in an alternative configuration, it will be understood that one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be understood that the above illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.

[0030] Transmission beamforming is a technique for concentrating RF signals in a specific direction. Conventionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). Using transmission beamforming, the network node determines where a given target device (e.g., a UE) is located with respect to the transmitting network node and transmits a stronger downlink RF signal in that specific direction, thereby providing a faster and more powerful RF signal to the receiving device(s) from the perspective of data rate. To vary the directivity of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node can use an array of antennas (also referred to as a "phased array" or "antenna array") that can create a beam of RF waves that can be "steered" to point in different directions without actually moving the antennas. Specifically, the RF currents from the transmitters are supplied to the individual antennas in appropriate phase relationships such that the radio waves from the separate antennas are combined to cancel out and suppress radiation in unwanted directions while increasing radiation in the desired direction.

[0031] The transmission beam may be quasi-collocated, which means that the receiver (e.g., UE) sees the transmission beams as having the same parameters regardless of whether the transmission antennas of the network node itself are physically collocated. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a given type of QCL relationship means that some parameters for a second reference RF signal on a second beam can be derived from information about the source reference RF signal on the source beam. Thus, if the source reference RF signal is of QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is of QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is of QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is of QCL type D, the receiver can use the source reference RF signal to estimate the spatial reception parameters of the second reference RF signal transmitted on the same channel.

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

[0033] Transmit beams and receive beams may be spatially related. Spatial relationship means that the parameters for a second beam (e.g., transmit beam or receive beam) for a second reference signal can be derived from the information about a first beam (e.g., receive beam or transmit beam) for a first reference signal. For example, a UE may receive a reference downlink reference signal (e.g., synchronization signal block (SSB)) from a base station using a particular receive beam. 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.

[0034] Note that the "downlink" beam can be either a transmission beam or a reception beam depending on the entity that forms it. For example, when the base station forms a downlink beam to transmit a reference signal to the UE, the downlink beam is a transmission beam. However, when the UE forms a downlink beam, it is a reception beam for receiving the downlink reference signal. Similarly, the "uplink" beam can be either a transmission beam or a reception beam depending on the entity that forms it. For example, when the base station forms an uplink beam, it is an uplink reception beam, and when the UE forms an uplink beam, it is an uplink transmission beam.

[0035] The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands are identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Note that although a portion of FR1 is higher than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and papers. Similar nomenclature issues can arise for FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and papers, despite being different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band.

[0036] The frequency between FR1 and FR2 is often referred to as the intermediate band frequency. In recent 5G NR research, the operating band for these intermediate band frequencies is identified as frequency range designation FR3 (7.125 GHz to 24.25 GHz). The frequency bands included within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus, in effect, the features of FR1 and / or FR2 can be extended to the intermediate 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 are identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands is included within the EHF band.

[0037] With the above aspects in mind, unless otherwise specifically described, terms such as "sub-6 GHz" as used in this specification may be understood to broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include the intermediate band frequency. Furthermore, unless otherwise specified, terms such as "millimeter wave" as used in this specification may, in some cases, be understood to broadly represent frequencies that can include the intermediate band frequency, frequencies that can be within the range of FR2, FR4, FR4-a or FR4-1, and / or FR5, or frequencies that can be within the range of the EHF band.

[0038] 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 that operates on the primary frequency (e.g., FR1) used by the UE104 / 182 and the cell where the UE104 / 182 performs the initial radio resource control (RRC) connection establishment procedure or starts the RRC connection re-establishment procedure. The primary carrier carries all common control channels and UE-specific control channels and can be a carrier within the licensed frequency (however, it is not always the case). The secondary carrier can be configured when an RRC connection is established between the UE104 and the anchor carrier and is a carrier that operates on a second frequency (e.g., FR2) and can be used to provide additional radio resources. In some cases, the secondary carrier can be a carrier within the unlicensed frequency. Since both the primary uplink carrier and the primary downlink carrier are usually UE-specific, the secondary carrier is assumed to contain only the necessary signaling information and signals. For example, there should be no UE-specific signaling information and signals within the secondary carrier. This means that different UE104 / 182 within a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE104 / 182 at any time. This is done, for example, to balance the load on different carriers. The terms "cell", "serving cell", "component carrier", "carrier frequency", etc. can be used interchangeably since the "serving cell" (regardless of PCell or SCell) corresponds to the carrier frequency / component carrier through which several base stations communicate.

[0039] For example, still referring to FIG. 1, one of the frequencies utilized by macrocell base station 102 can be an anchor carrier (or "PCell"), and the other frequencies utilized by macrocell base station 102 and / or mmW base station 180 can be secondary carriers ("SCells"). By simultaneous transmission and / or reception of multiple carriers, UE 104 / 182 can significantly increase its data transmission and / or reception rate. For example, two 20 MHz carriers aggregated within a multi-carrier system would, in theory, result in a two-fold increase in data rate (i.e., 40 MHz) compared to the data rate achieved by a single 20 MHz carrier.

[0040] Wireless communication system 100 may further include a UE 164 that may communicate with macrocell base station 102 via communication link 120 and / or with mmW base station 180 via mmW communication link 184. For example, macrocell base station 102 may support a PCell and one or more SCells for UE 164, and mmW base station 180 may support one or more SCells for UE 164.

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

[0042] In one aspect, the sidelink 160 can operate on a target wireless communication medium, and the relevant communication medium can be shared with other wireless communications between other vehicles and / or infrastructure access points, and other RATs. The "medium" can be composed of one or more time, frequency, and / or spatial communication resources associated with wireless communication between one or more transmitter / receiver pairs (including, for example, one or more channels over one or more carriers). In one aspect, the target medium can correspond to at least a portion of an unlicensed frequency band shared among various RATs. Different licensed frequency bands are reserved for some communication systems (e.g., by a government agency such as the Federal Communications Commission (FCC) in the United States), but these systems, especially those employing small cell access points, have recently extended their operations to unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technologies, most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi". Exemplary systems of this type include various variants such as CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and the like.

[0043] FIG. 1 shows only two of the UEs as SL-UEs (i.e., UEs 164 and 182), but it should be noted that any of the illustrated UEs may be an SL-UE. Further, although only UE 182 was described as being beamforming capable, any of the illustrated UEs, including UE 164, may be beamforming capable. The SL-UEs, when beamforming capable, can beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UE 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 via sidelink 160.

[0044] 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 one aspect, the SV 112 may be part of a satellite positioning system that can be used by UE 104 as an independent source of location information. A satellite positioning system is typically arranged to enable a receiver (e.g., UE 104) to determine its location on or above the earth, at least in part based on positioning signals received from a transmitter (e.g., signal 124), and includes a system of transmitters (e.g., SV 112). Such transmitters typically transmit signals marked with a set number of repetitions of a pseudo-random noise (PN) code. Although typically located within the SV 112, the transmitter may sometimes be located on a ground-based control station, base station 102, and / or another UE 104. UE 104 may include one or more dedicated receivers specifically designed to receive signals 124 for deriving geolocation information from the SV 112.

[0045] In a satellite positioning system, the use of signal 124 may be associated with use involving one or more global and / or regional navigation satellite systems or may be enabled in another way for such use and may be enhanced by various satellite-based augmentation systems (SBAS). For example, SBAS may include augmentation system(s) (singular or plural) that provide integrity information, error correction, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multi-functional Satellite Augmentation System (MSAS), Global Positioning System (GPS)-aided Geo Augmented Navigation, or GPS and Geo Augmented Navigation system (GAGAN). Thus, the satellite positioning system as used herein may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0046] In one aspect, SV112 can be part of one or more non-terrestrial networks (NTNs), additionally or alternatively. In an NTN, SV112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which is then connected to an element in the 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in the 5GC. This element then provides 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, UE104 can receive communication signals (e.g., signal 124) from SV112 instead of or in addition to communication signals from terrestrial base station 102.

[0047] Wireless communication system 100 may further include one or more UEs, such as UE190, that are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "side links"). In the example of FIG. 1, UE190 has a D2D P2P link 192 with one of the UEs104 connected to one of the base stations 102 (e.g., through which UE190 may indirectly obtain a cellular connection), and a D2D P2P link 194 with a WLAN STA152 connected to a WLAN AP150 (e.g., through which UE190 may indirectly obtain a WLAN-based internet connection). In one example, D2D P2P links 192 and 194 can be supported using any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®.

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

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

[0050] FIG. 2B shows another exemplary wireless network structure 240. 5GC 260 (which may correspond to 5GC 210 in FIG. 2A) can be considered functionally as a control plane function provided by an access and mobility management function (AMF) 264 that operates cooperatively to form a core network (i.e., 5GC 260), and a user plane function provided by a user plane function (UPF) 262. The functions of 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, a transparent proxy service for routing SM messages, access authentication and authorization, transport for short message service (SMS) messages between UE 204 and a short message service function (SMSF) (not shown), and security anchor functionality (SEAF). AMF 264 also interacts with an authentication server function (AUSF) (not shown) and UE 204 and receives an intermediate key 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), AMF 264 retrieves security material from the AUSF. The functions of AMF 264 also include security context management (SCM). SCM receives from SEAF a key that SCM uses to derive an access network specific key.The functionality of the AMF 264 also includes location service management for regulatory services, transport of location service messages between the UE 204 and the Location Management Function (LMF) 270 acting as the location server 230, transport of location service messages between the NG-RAN 220 and the LMF 270, EPS bearer identifier allocation for interacting with the Evolved Packet System (EPS), and UE 204 mobility event notification. In addition, the AMF 264 also supports functions for non-3GPP (Third Generation Partnership Project) access networks.

[0051] The functions of the UPF 262 include acting as an anchor point for intra-RAT / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point of interconnection to a data network (not shown), routing and forwarding packets, 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 (mapping from service data flow (SDF) to QoS flow), transport level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more "end markers" to the source RAN node. The UPF 262 may also support the transfer of location service messages on the user plane between the UE 204 and a location server such as the SLP 272.

[0052] The functions of the SMF266 include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering in the UPF262 for routing traffic to appropriate destinations, policy enforcement and some control of QoS, and downlink data notification. The interface through which the SMF266 communicates with the AMF264 is called the N11 interface.

[0053] Another optional aspect may include an LMF270 that may communicate with the 5GC260 to provide location assistance to the UE204. The LMF270 may be implemented as a plurality of distinct servers (e.g., physically distinct servers, different software modules on a single server, different software modules across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The LMF270 may be configured to support one or more location services for the UE204 that can connect to the LMF270 via the core network, the 5GC260, and / or the Internet (not shown). The SLP272 may support functions similar to the LMF270, while on the other hand, the LMF270 may communicate with the AMF264, the NG-RAN220, and the UE204 via the control plane (e.g., using interfaces and protocols intended to convey signaling messages rather than voice or data), and the SLP272 may communicate with the UE204 and external clients (e.g., third-party server 274) via the user plane (e.g., using protocols intended to carry voice and / or data such as the Transmission Control Protocol (TCP) and / or IP).

[0054] Another optional aspect may include communicating 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 a third-party server 274 that may be communicating with the UE 204 to obtain location information (e.g., a location estimate) for the UE 204. Thus, in some cases, the third-party server 274 may be referred to as a location service (LCS) client or an external client. The third-party server 274 may be implemented as multiple distinct servers (e.g., physically distinct servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternatively, each may correspond to a single server.

[0055] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, specifically the UPF 262 and the AMF 264 respectively, to one or more gNBs 222 and / or ng-eNBs 224 within the NG-RAN 220. The interface between the gNB(s) 222 and / or ng-eNB(s) 224 and the AMF 264 is called the "N2" interface, and the interface between the gNB(s) 222 and / or ng-eNB(s) 224 and the UPF 262 is called 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 a backhaul connection 223 called the "Xn-C" interface. One or more of the gNB 222 and / or ng-eNB 224 may communicate with one or more UEs 204 via a wireless interface called the "Uu" interface.

[0056] The functionality of gNB 222 can be split 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. The gNB-CU 226 is a logical node that includes base station functions such as transferring user data, mobility control, radio access network sharing, positioning, session management, etc., except for those functions that are exclusively allocated to the gNB-DU(s) 228. More specifically, the gNB-CU 226 generally hosts the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of gNB 222. The gNB-DU 228 is a logical node that generally hosts the radio link control (RLC) and media access control (MAC) layers of 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 one or more gNB-DUs 228 is called the "F1" interface. The physical (PHY) layer functionality of gNB 222 is generally hosted by one or more stand-alone gNB-RUs 229 that perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is called the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC, SDAP, and PDCP layers, with the gNB-DU 228 via the RLC and MAC layers, and with the gNB-RU 229 via the PHY layer.

[0057] The deployment of communication systems such as 5G NR systems can be configured in multiple ways using various components or parts. In a 5G NR system or network, network devices such as network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, or base stations, or one or more units (or one or more components) implementing base station functionality, can be implemented in an integrated or separated architecture. For example, a base station (such as Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), transmit receive point (TRP), or cell, etc.) can be implemented as an integrated base station (also known as a stand-alone base station or a monolithic base station) or a separated base station.

[0058] An integrated base station can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A separated base station can be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more centralized units or central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs), etc.). In some aspects, the CU may be implemented within the RAN node, one or more DUs may be collocated with the CU, or alternatively, one or more DUs may be geographically or virtually distributed across one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0059] The operation or network design of a base station type may consider the aggregation characteristics of base station functions. For example, a distributed base station can be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration supported by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functions across two or more units at various physical locations and virtually distributing functions for at least one unit, which may enable flexibility in network design. The various units of a distributed base station, or a distributed RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0060] FIG. 2C shows an exemplary distributed base station architecture 250 according to an aspect of the present disclosure. The distributed base station architecture 250 can communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link or indirectly communicate with the core network 267 through one or more distributed base station units (e.g., 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), and may include one or more Central Units (CUs) 280 (e.g., gNB-CU 226). The CU 280 can communicate with one or more Distributed Units (DUs) 285 (e.g., gNB-DU 228) via respective midhaul links such as an F1 interface. The DU 285 can communicate with one or more Radio Units (RUs) 287 (e.g., gNB-RUs 229) via respective fronthaul links. The RU 287 can communicate with respective UEs 204 via one or more Radio Frequency (RF) access links. In some implementations, the UE 204 can be served simultaneously by multiple RUs 287.

[0061] Each of the units, namely, CU280, DU285, RU287, and quasi-RT RIC259, non-RT RIC257, and SMO framework 255, may include one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired transmission medium or a wireless transmission medium, or may be coupled to such one or more interfaces. Each of the units, or an associated processor or controller that provides instructions to the communication interface of the unit, may be configured to communicate with one or more of the other units via the transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more of the other units via a wired transmission medium. Further, the units may include a wireless interface that includes a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive, transmit, or receive and transmit signals to one or more of the other units via a wireless transmission medium.

[0062] In some embodiments, CU280 can host one or more upper layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function can be implemented using an interface configured to communicate signals with other control functions hosted by CU280. CU280 can be configured to handle user plane functions (i.e., Central Unit - User Plane (CU-UP)), control plane functions (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some implementations, CU280 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. CU280 can be implemented to communicate with DU285 as needed for network control and signaling.

[0063] DU285 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 287. In some aspects, DU285 may host one or more of the radio link control (RLC) layer, the media access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules related to forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation), at least in part in accordance with a functional split, such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, DU285 may further host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU285 or with control functions hosted by CU280.

[0064] The lower layer functions can be implemented by one or more RUs 287. In some deployments, the RUs 287 controlled by the DU 285 may correspond to logical nodes that host an RF processing function, or a lower PHY layer function (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, at least partially based on function splitting such as lower layer function splitting. 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, the real-time and non-real-time aspects of the control plane communication 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.

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

[0066] 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, an artificial intelligence / machine learning (AI / ML) workflow including model training and updating, or policy-based guidance of applications / features in the quasi-RT RIC 259. The non-RT RIC 257 may be coupled to the quasi-RT RIC 259 or communicate with the quasi-RT RIC 259 (e.g., via an A1 interface). The quasi-RT RIC 259 may be configured to include a logical function that enables quasi-real-time control and optimization of RAN elements and resources by data collection and actions (e.g., via an E2 interface) through an interface connecting one or more CU 280, one or more DU 285, or both, and the O-eNB to the quasi-RT RIC 259.

[0067] In some implementations, the non-RT RIC 257 may receive parameters or external enrichment information from an external server to generate an AI / ML model deployed in the quasi-RT RIC 259. Such information may be utilized by the quasi-RT RIC 259 and may be received from non-network data sources or network functions in the SMO framework 255 or the non-RT RIC 257. In some examples, the non-RT RIC 257 or the quasi-RT RIC 259 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 257 may monitor long-term trends and patterns in performance and employ an AI / ML model to implement corrective measures through the SMO framework 255 (e.g., reconfiguration via O1) or via the creation of RAN management policies (e.g., A1 policies).

[0068] Figures 3A, 3B, and 3C show some exemplary components (represented by corresponding blocks) that may be incorporated within a User Equipment (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 Location Server 230 and LMF 270, or alternatively, may be independent of the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in FIGS. 2A and 2B, such as a private network) to support the operations described herein. It will be appreciated that these components may be implemented in different types of devices in different implementation forms (e.g., within an ASIC, within a system-on-chip (SoC), etc.). The components shown may also be incorporated within other devices in the communication system. For example, other devices in the system may include components similar to those described to provide similar functionality. Also, a given device may include one or more of the components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0069] UE 302 and base station 304 each include one or more Wireless Wide Area Network (WWAN) transceivers 310 and 350, and provide means (e.g., means for transmitting, means for receiving, means for measuring, means for synchronizing, means for refraining from transmitting, etc.) for communicating via one or more wireless communication networks (not shown), such as an NR network, an LTE network, a GSM network, etc. WWAN transceivers 310 and 350 can each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes such as other UEs, access points, base stations (e.g., eNB, gNB), etc. via at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a target wireless communication medium (e.g., some set of time / frequency resources in a particular frequency spectrum). WWAN transceivers 310 and 350 can be variously configured to transmit and encode signals 318 and 358 (e.g., messages, instructions, information, etc.) according to the designated RAT, and conversely, to receive and decode signals 318 and 358 (e.g., messages, instructions, information, pilots, etc.). Specifically, WWAN transceivers 310 and 350 each include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, and each include one or more receivers 312 and 352, respectively, for receiving and decoding signals 318 and 358.

[0070] UE 302 and base station 304 also each include, in at least some cases, one or more short-range wireless transceivers 320 and 360, respectively. Short-range wireless transceivers 320 and 360 may each be connected to one or more antennas 326 and 366, respectively, and provide means (e.g., means for transmitting, receiving, measuring, synchronizing, refraining from transmitting, etc.) for communicating with other network nodes such as other UEs, access points, base stations, etc. via the wireless communication medium over 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.). Short-range wireless transceivers 320 and 360 may be variously configured to transmit and encode signals 328 and 368 (e.g., messages, instructions, information, etc.) and, conversely, to receive and decode signals 328 and 368 (e.g., messages, instructions, information, pilots, etc.) according to the designated RAT. Specifically, short-range wireless transceivers 320 and 360 each include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, and each include one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368. As a specific example, 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.

[0071] UE 302 and the base station 304 also include satellite signal receivers 330 and 370 in at least some cases. The satellite signal receivers 330 and 370 can be connected to one or more antennas 336 and 376 respectively, and can respectively provide means for receiving and / or measuring satellite positioning / communication signals 338 and 378. When the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 can be Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. When the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 can be communication signals transmitted from a 5G network (for example, carrying control and / or user data). The satellite signal receivers 330 and 370 can each be provided with any suitable hardware and / or software for receiving and processing the satellite positioning / communication signals 338 and 378. The satellite signal receivers 330 and 370 can appropriately request information and operations from other systems, and in at least some cases, perform calculations using the obtained measurement values by any suitable satellite positioning system algorithm to respectively determine the locations of the UE 302 and the base station 304.

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

[0073] The transceiver may be configured to communicate via a wired link or a wireless link. (Regardless of whether it is a wired transceiver or a wireless transceiver), the transceiver includes a transmitter circuit configuration (e.g., transmitters 314, 324, 354, 364) and a receiver circuit configuration (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., embodying the transmitter circuit configuration and the receiver circuit configuration within a single device), in some implementations, it may include separate transmitter and receiver circuit configurations, or in other implementations, it may be embodied in other ways. The transmitter and receiver circuit configurations of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. The wireless transmitter circuit configurations (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 enables each device (e.g., UE 302, base station 304) to perform transmission “beamforming” as described herein. Similarly, the wireless receiver circuit configurations (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 enables each device (e.g., UE 302, base station 304) to perform receive beamforming as described herein. In one aspect, the transmitter and receiver circuit configurations may share a plurality of the same antennas (e.g., antennas 316, 326, 356, 366) such that each device can only receive or transmit at a given time and not both at the same time. The wireless transceivers (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include, for example, a network listen module (NLM) for performing various measurements.

[0074] 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) used in this specification may generally be characterized as a "transceiver", "at least one transceiver", or "one or more transceivers". Thus, whether a particular transceiver is a wired transceiver or a wireless transceiver can be inferred from the type of communication being implemented. For example, backhaul communication between network devices or servers generally involves signaling via a wired transceiver, while wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) generally involves signaling via a wireless transceiver.

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

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

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

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

[0079] Looking more specifically at one or more processors 384, 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 functions for the RRC layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, and the media access control (MAC) layer. The one or more processors 384 may perform RRC layer functions associated with the broadcast of system information (e.g., master information block (MIB), system information block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with the transfer of upper layer PDUs, error correction by automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with the mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0080] The transmitter 354 and the receiver 352 may implement Layer-1 (L1) functions associated with various signal processing functions. Layer 1, including the Physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The transmitter 354 handles the mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols may then be split into parallel streams. Each stream is then mapped to orthogonal frequency division multiplexing (OFDM) subcarriers, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then synthesized together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to generate a plurality of spatial streams. Channel estimates from the channel estimator may be used to determine the coding and modulation scheme and for spatial processing. The channel estimates may be derived from reference signals transmitted by the UE 302 and / or channel state feedback. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier using individual spatial streams for transmission.

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

[0082] On the uplink, one or more processors 332 provide demultiplexing in reverse between the transport channel and the logical channel, packet reassembly, decoding, header recovery, and control signal processing to recover IP packets from the core network. One or more processors 332 are also responsible for error detection.

[0083] Similar to the functions described in relation to downlink transmission by base station 304, one or more processors 332 perform RRC layer functions related to system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); and RLC layer functions associated with transfer of upper layer PDUs, error correction by ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions 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 by hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0084] Channel estimates derived by a channel estimator from a reference signal or feedback transmitted by base station 304 can be used by transmitter 314 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by transmitter 314 can be provided to different antennas 316. Transmitter 314 can modulate an RF carrier using individual spatial streams for transmission.

[0085] Uplink transmission is processed at base station 304 in a manner similar to the method described for the receiver function in UE 302. Receiver 352 receives signals via its respective antennas 356. Receiver 352 recovers the information modulated on the RF carrier and provides the information to one or more processors 384.

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

[0087] For convenience, the UE 302, base station 304, and / or network entity 306 are shown in FIGS. 3A, 3B, and 3C as including various components that can be configured according to the various examples described herein. However, it should be understood that the components shown may have different functions in different designs. Specifically, the various components in FIGS. 3A - 3C are optional in alternative configurations, and the various aspects include configurations that may vary due to design choices, cost, device usage, or other considerations. For example, in the case of FIG. 3A, a particular implementation of the UE 302 may omit the WWAN transceiver(s) 310 (e.g., a wearable device or a tablet computer or a PC or a laptop may have Wi-Fi and / or Bluetooth capabilities without cellular capabilities), 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, etc. In another example, in the 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 functionality), 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 the sake of brevity, examples of various alternative configurations are not provided herein, but should be readily understandable to those skilled in the art.

[0088] The various components of the UE 302, base station 304, and network entity 306 can be communicatively coupled to each other via data buses 334, 382, and 392, respectively. In one aspect, the data buses 334, 382, and 392 can form, or be part of, the communication interfaces of the UE 302, base station 304, and network entity 306, respectively. For example, if different logical entities are implemented within the same device (e.g., a gNB and location server functionality incorporated within the same base station 304), the data buses 334, 382, and 392 can provide communication between them.

[0089] The components of FIGS. 3A, 3B, and 3C can be implemented in various ways. In some implementations, the components of FIGS. 3A, 3B, and 3C can be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit can 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 functions represented by blocks 310 - 346 can be implemented by the processor and memory component(s) of UE 302 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor component). Similarly, some or all of the functions represented by blocks 350 - 388 can be implemented by the processor and memory component(s) of base station 304 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor component). Also, some or all of the functions represented by blocks 390 - 398 can be implemented by the processor and memory component(s) of network entity 306 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor component). For simplicity, in this specification, various operations, actions, and / or functions are described as being performed "by the UE", "by the base station", "by the network entity", etc. However, as will be understood, such operations, actions, and / or functions are actually performed by specific components or combinations of components of UE 302, base station 304, network entity 306, such as processors 332, 384, 394, transceivers 310, 320, 350, and 360, memories 340, 386, and 396, positioning components 342, 388, and 398, etc.

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

[0091] NR supports several cellular network-based positioning techniques, including downlink-based positioning methods, uplink-based positioning methods, and downlink and uplink-based positioning methods. Downlink-based positioning methods include observed time difference of arrival (OTDOA) in LTE, downlink time difference of arrival (DL-TDOA) in NR, and downlink angle-of-departure (DL-AoD) in NR. Figure 4 shows examples of various positioning methods according to aspects of the present disclosure. In the OTDOA or DL-TDOA positioning procedure shown by scenario 410, the UE measures the difference between the times of arrival (ToAs) of reference signals (e.g., positioning reference signals (PRS)) received from a pair of base stations, which are referred to as reference signal time difference (RSTD) measurements or time difference of arrival (TDOA) measurements, and reports them to a positioning entity. More specifically, the UE receives identifiers (IDs) of a reference base station (e.g., serving base station) and a plurality of non-reference base stations in assistance data. The UE then measures the RSTD between each of the reference base station and the non-reference base stations. Based on the known locations of the involved base stations and the RSTD measurements, a positioning entity (e.g., the UE in the case of UE-based positioning, or a location server in the case of UE-assisted positioning) can estimate the location of the UE.

[0092] In the case of DL-AoD positioning shown by scenario 420, the positioning entity uses measurement reports from the UE of the received signal strength measurements of a plurality of downlink transmission 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).

[0093] The uplink-based positioning method includes uplink time difference of arrival (UL-TDOA) and uplink angle-of-arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but is based on uplink reference signals (e.g., sounding reference signals (SRS)) transmitted by the UE to multiple base stations. Specifically, the UE transmits one or more uplink reference signals measured by a reference base station and multiple non-reference base stations. Each base station then reports the reception time of the reference signal(s) (referred to as relative time of arrival (RTOA)) to a positioning entity (e.g., a location server) that knows the location and relative timing of the 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.

[0094] In the case of UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink reception beams. The positioning entity uses the signal strength measurements and the angle(s) of the reception 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.

[0095] 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 the RTT procedure, a first entity (e.g., a base station or a UE) transmits a first RTT-related signal (e.g., a PRS or an SRS) to a second entity (e.g., a UE or a base station), and the second entity transmits a second RTT-related signal (e.g., an SRS or a PRS) back to the first entity. Each entity measures the time difference between the arrival time (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. This time difference is referred to as the reception-to-transmission (Rx-Tx) time difference. The Rx-Tx time difference measurements can be made or adjusted to include only the time difference between the closest slot boundaries for the received and transmitted signals. Then, both entities can send their Rx-Tx time difference measurements to a location server (e.g., an LMF270), and the location server can calculate the round-trip propagation time (i.e., the 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, and then the other entity calculates the RTT. The distance between the two entities can be determined from the RTT and a known signal speed (e.g., the speed of light). In the case of multi-RTT positioning as shown by scenario 430, a first entity (e.g., a UE or a base station) performs RTT positioning procedures with a plurality of second entities (e.g., a plurality of base stations or UEs) to enable the determination of the location of the first entity based on the distance to the second entity and the known location of the second entity (e.g., using multi-lateration). As shown by scenario 440, the RTT and multi-RTT methods can be combined with other positioning techniques such as UL-AoA and DL-AoD to improve the accuracy of location.

[0096] The E-CID positioning method is based on Radio Resource Management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), and the identifiers, estimated timing, and signal strengths of detected neighboring base stations. The location of the UE is then estimated based on this information and the known location(s) of the base station(s).

[0097] To assist the positioning operation, 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 the identifier of the base station (or cell / TRP of the base station) from which to measure the reference signal, reference signal configuration parameters (e.g., the number of consecutive slots including PRS, the periodicity of consecutive slots including PRS, the muting sequence, the frequency hopping sequence, the reference signal identifier, the reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, the assistance data may be obtained directly from the base station itself (e.g., in an overhead message broadcast periodically). In some cases, the UE may be able to detect neighboring network nodes themselves without using the assistance data.

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

[0099] Location estimation may be referred to by other names such as position estimation, location, position, position fix, fix, etc. A location estimate may be geodesic and have coordinates (e.g., latitude, longitude, and optionally altitude), or may be civic and have a street address, postal address, or some other linguistic description of the location. Location estimation may also be defined relative to some other known location or may be defined absolutely (e.g., using latitude, longitude, and optionally 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 level or default level of confidence).

[0100] To support downlink and uplink transmissions between network nodes (e.g., base stations and UEs), various frame structures may be used. FIG. 5 is a diagram 500 showing an exemplary frame structure according to an aspect of the present disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.

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

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

[0103] In the example of FIG. 5, a numerology of 15 kHz is used. Thus, in the time domain, a 10 ms frame is divided into 10 sub-frames each sized equally at 1 ms, and each sub-frame contains one time slot. In FIG. 5, time is represented horizontally (on the X-axis), with time increasing from left to right, and frequency is represented vertically (on the Y-axis), with frequency increasing (or decreasing) from bottom to top.

[0104] A resource grid may be used to represent time slots, and each time slot contains one or more time-parallel resource blocks (RBs) (also called physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into a plurality of resource elements (REs). An RE may correspond to a length of 1 symbol in the time domain and 1 sub-carrier in the frequency domain. In the numerology of FIG. 5, for a normal cyclic prefix, an RB may contain 12 consecutive sub-carriers in the frequency domain and 7 consecutive symbols in the time domain to obtain a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive sub-carriers in the frequency domain and 6 consecutive symbols in the time domain to obtain a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0105] Some of the REs may carry a reference (pilot) signal (RS). The reference signal may include a positioning reference signal (PRS), a tracking reference signal (TRS), a phase tracking reference signal (PTRS), a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a synchronization signal block (SSBs), a sounding reference signal (SRS), etc., depending on whether the shown frame structure is used for uplink communication or downlink communication. FIG. 5 shows an exemplary location of the REs carrying the reference signal (labeled "R").

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

[0107] The transmission of the PRS resource within a given PRB has a specific comb size (also called "comb density"). The comb size "N" represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the PRS resource configuration. Specifically, in the case of comb size "N", the PRS is transmitted on every Nth subcarrier of the symbol of the PRB. For example, in the case of comb 4, for each symbol of the PRS resource configuration, the REs corresponding to every 4th subcarrier (such as subcarriers 0, 4, 8, etc.) are used to transmit the PRS of the PRS resource. Currently, comb sizes of comb 2, comb 4, comb 6, and comb 12 are supported for DL-PRS. Figure 5 shows an exemplary PRS resource configuration for comb 4 (spanning 4 symbols). That is, the location of the shaded REs (labeled "R") indicates the comb 4 PRS resource configuration.

[0108] Currently, the DL-PRS resources can span 2, 4, 6, or 12 consecutive symbols within a slot with a staggered pattern across the entire frequency band. The DL-PRS resources can be configured within any downlink symbol or flexible (FL) symbol configured by the upper layer of the slot. For all the REs of a given DL-PRS resource, there can be a constant energy per resource element (EPRE). The following are the frequency offsets from symbol to symbol for comb sizes 2, 4, 6, and 12 spanning 2, 4, 6, and 12 symbols. 2-symbol comb 2: {0,1}, 4-symbol comb 2: {0,1,0,1}, 6-symbol comb 2: {0,1,0,1,0,1}, 12-symbol comb 2: {0,1,0,1,0,1,0,1,0,1,0,1}, (in the case of the example in Figure 5), 4-symbol comb 4: {0,2,1,3}, 12-symbol comb 4: {0,2,1,3,0,2,1,3,0,2,1,3}, 6-symbol comb 6: {0,3,1,4,2,5}, 12-symbol comb 6: {0,3,1,4,2,5,0,3,1,4,2,5}, and 12-symbol comb 12: {0,6,3,9,1,7,4,10,2,8,5,11}.

[0109] A "PRS resource set" is a set of PRS resources used for the transmission of a PRS signal, where each PRS resource has a PRS resource ID. In addition, the PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and is associated with a specific TRP (identified by the TRP ID). In addition, the PRS resources in a PRS resource set have the same periodicity, common muting pattern configuration, and the same repetition factor (such as "PRS-ResourceRepetitionFactor") across slots. Periodicity is the time from the first repetition of the first PRS resource of the first PRS instance to the first repetition of the same first PRS resource of the next PRS instance. The periodicity is μ = 0, 1, 2, 3, and 2^μ *It may have a length selected from the slots {4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240}. The repetition factor may have a length selected from the slots {1, 2, 4, 6, 8, 16, 32}.

[0110] The PRS resource ID in the PRS resource set is associated with a single beam (or beam ID) transmitted from a single TRP (where the TRP can transmit one or more beams). That is, each PRS resource in the PRS resource set may be transmitted on a different beam, and thus may also be referred to as a "PRS resource" or simply a "resource", or also a "beam". It should be noted that this has no meaning regarding whether the TRP and beam on which the PRS is transmitted are known to the UE.

[0111] A "PRS instance" or "PRS occasion" is one instance of a periodically repeated time window (such as a group of one or more consecutive slots) in which the PRS is expected to be transmitted. A PRS occasion may also be referred to as a "PRS positioning occasion", "PRS positioning instance", "positioning occasion", "positioning instance", "positioning repetition", or simply an "occasion", "instance", or "repetition".

[0112] A "positioning frequency layer" (also simply referred to as "frequency layer") is a set of one or more PRS resource sets across one or more TRPs having the same values for several parameters. Specifically, the set of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning that all numerologies supported for the physical downlink shared channel (PDSCH) are also supported for the PRS), the same Point A, the same value of downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The Point A parameter takes the value of the parameter "ARFCN-ValueNR" (where "ARFCN" represents "absolute radio-frequency channel number") and is an identifier / code that designates a pair of physical radio channels used for transmission and reception. The downlink PRS bandwidth may have a granularity of 4 PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs. Currently, a maximum of four frequency layers are defined, and up to two PRS resource sets per TRP can be configured for each frequency layer.

[0113] The concept of a frequency layer is somewhat similar to the concepts of component carriers and bandwidth parts (BWPs), but component carriers and BWPs are used by one base station (or a macrocell base station and a small cell base station) to transmit data channels, while frequency layers are used by several (usually three or more) base stations to transmit PRS. The UE may indicate the number of frequency layers it can support, for example, during an LTE positioning protocol (LPP) session when the UE transmits its positioning capabilities to the network. For example, the UE may indicate whether it can support one positioning frequency layer or four positioning frequency layers.

[0114] Note that the terms "positioning reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "positioning reference signal" and "PRS" can also refer to any type of reference signal that can be used for positioning, such as, but not limited to, PRS defined in LTE and NR, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc. Further, the terms "positioning reference signal" and "PRS" can refer to downlink, uplink, or sidelink positioning reference signals, unless otherwise indicated by the context. If necessary to further distinguish the types of PRS, the downlink positioning reference signal may be referred to as "DL-PRS", the uplink positioning reference signal (e.g., SRS for positioning, PTRS) may be referred to as "UL-PRS", and the sidelink positioning reference signal may be referred to as "SL-PRS". In addition, for signals that can be transmitted in the downlink, uplink, and / or sidelink (e.g., DMRS), "DL", "UL", or "SL" may be prepended to the signal to distinguish the direction. For example, "UL-DMRS" is different from "DL-DMRS".

[0115] FIG. 6 is a graph 600 representing channel estimation of a multipath channel between a receiver device (e.g., either a UE or a base station described herein) and a transmitter device (e.g., the other of either a UE or a base station described herein) according to an aspect of the present disclosure. The channel estimation represents the intensity of a radio frequency (RF) signal (e.g., a PRS) received via the multipath channel as a function of time delay, and may be referred to as a channel energy response (CER), a channel impulse response (CIR), or a power delay profile (PDP) of the channel. Thus, the horizontal axis is in units of time (e.g., milliseconds), and the vertical axis is in units of signal intensity (e.g., decibels). Note that the multipath channel is the channel between the transmitter and the receiver for the RF signal to follow multiple paths, or multipaths, due to transmission of the RF signal in multiple beams and / or due to propagation characteristics of the RF signal (e.g., reflection, refraction, etc.).

[0116] In the example of FIG. 6, the receiver detects / measures multiple (four) clusters of channel taps. Each channel tap represents a multipath that the RF signal has followed between the transmitter and the receiver. That is, the channel tap represents the arrival of the RF signal on the multipath. Each cluster of channel taps indicates that the corresponding multipath has basically followed the same path. Different clusters may exist due to the RF signal being transmitted on different transmit beams (and thus at different angles), and / or due to the propagation characteristics of the RF signal (which may follow different paths, e.g., due to reflection), or both.

[0117] All clusters of channel taps for a given RF signal represent the multipath channel (or simply channel) between the transmitter and the receiver. Under the channel shown in FIG. 6, the receiver receives a first cluster of two RF signals on the channel tap at time T1, a second cluster of five RF signals on the channel tap at time T2, a third cluster of five RF signals on the channel tap at time T3, and a fourth cluster of four RF signals on the channel tap at time T4. In the example of FIG. 6, the first cluster of RF signals at time T1 is assumed to correspond to the RF signal transmitted on the line-of-sight (LOS), or shortest path, aligned transmit beam since it arrives first. The third cluster at time T3 consists of the strongest RF signals and may correspond to, for example, an RF signal transmitted on a transmit beam aligned with a non-line-of-sight (NLOS) path. Although FIG. 6 shows clusters of two to five channel taps, it should be noted that a cluster may have more or fewer channel taps than the number of channel taps shown.

[0118] Machine learning can be used to generate models that can be used to facilitate various aspects related to the processing of data. One particular application of machine learning relates to the generation of measurement models for the processing of reference signals for positioning (e.g., PRS), such as feature extraction, reporting of reference signal measurements (e.g., selecting which of the extracted features to report).

[0119] Machine learning models are generally classified into either supervised or unsupervised. Supervised models can be further subcategorized as either regression models or classification models. Supervised learning involves learning a function that maps inputs to outputs based on exemplary input and output pairs. For example, given a training dataset with two variables, age (input) and height (output), a supervised learning model can be generated to predict a person's height based on their age. In a regression model, the output is continuous. An example of a regression model is linear regression, which simply attempts to find the line that best fits the data. Extensions of linear regression include multiple regression (e.g., finding the best-fitting plane) and polynomial regression (e.g., finding the best-fitting curve).

[0120] Another example of a machine learning model is the decision tree model. In a decision tree model, the tree structure is defined by multiple nodes. Decisions are used to move from the topmost root node of the decision tree to the bottommost leaf node (i.e., the node that has no further child nodes). Generally, the more nodes there are in a decision tree model, the higher the decision accuracy correlation is.

[0121] Another example of a machine learning model is the decision forest. Random forest is an ensemble learning technique that creates new decision trees. Random forest involves creating multiple decision trees using a bootstrap sample of the original data and randomly selecting a subset of variables at each step of the decision tree. The model then selects the mode of all the predictions of each decision tree. By relying on a "majority vote" model, the risk of error from individual trees is reduced.

[0122] Another example of a machine learning model is a neural network (NN). A neural network is essentially a network of mathematical equations. A neural network accepts one or more input variables and produces one or more output variables by passing through a network of equations. Put another way, a neural network takes in a vector of inputs and returns a vector of outputs.

[0123] FIG. 7 shows an exemplary neural network 700 according to an aspect of the present disclosure. Neural network 700 includes an input layer “i” that receives “n” (one or more) inputs (shown as “input 1”, “input 2”, and “input n”), one or more hidden layers (shown as hidden layers “h1”, “h2”, and “h3”) for processing the inputs from the input layer, and an output layer “o” that provides “m” (one or more) outputs (labeled “output 1” and “output m”). The number of inputs “n”, hidden layers “h”, and outputs “m” may be the same or different. In some designs, the hidden layer “h” may include a linear function(s) and / or activation function(s) that are processed by the nodes (shown as circles) of each successive hidden layer process from the nodes of the previous hidden layer.

[0124] In a classification model, the output is discrete. An example of a classification model is logistic regression. Logistic regression is similar to linear regression but is used to model the probabilities of a finite number, typically two, of outcomes. Essentially, the logistic equation is created in such a way that the output values can only be between "0" and "1". Another example of a classification model is the support vector machine. For example, for data of two classes, the support vector machine finds a hyperplane or boundary between the data of the two classes that maximizes the margin between the two classes. There are many planes that can separate the two classes, but only one plane can maximize the margin or distance between the classes. Another example of a classification model is naive Bayes based on Bayes' theorem. Other examples of classification models include decision trees, random forests, and neural networks, which are similar to the examples described above except that the output is discrete rather than continuous.

[0125] Unlike supervised learning, unsupervised learning is used to derive inferences from input data and find patterns without referring to labeled results. Two examples of unsupervised learning models are clustering and dimensionality reduction.

[0126] Clustering is an unsupervised technique involving the grouping or clustering of data points. Clustering is frequently used for customer segmentation, fraud detection, and document classification. Common clustering techniques include k-means clustering, hierarchical clustering, mean shift clustering, and density-based clustering. Dimensionality reduction is the process of reducing the number of random variables under consideration by obtaining a set of principal variables. Put more simply, dimensionality reduction is the process of reducing the dimensionality of the feature set (or, even more simply, reducing the number of features). Most dimensionality reduction techniques can be classified as either feature removal or feature extraction. An example of dimensionality reduction is called principal component analysis (PCA). In the simplest sense, PCA involves projecting higher-dimensional data (e.g., 3D) into a smaller space (e.g., 2D). This results in a lower dimension of the data (e.g., 2D instead of 3D) while maintaining all of the original variables within the model.

[0127] Regardless of which machine learning model is used, at a high level, a machine learning module (e.g., implemented by a processing system such as processors 332, 384, or 394) is configured to iteratively analyze training input data (e.g., measurements of reference signals to / from various target UEs) and associate this training input data with an output data set (e.g., a set of possible or likely location candidates for various target UEs), thereby enabling subsequent determination of the same output data set when similar input data is presented (e.g., from other target UEs at the same or a similar location).

[0128] NR supports RF fingerprint (RFFP)-based positioning, which is a type of positioning and localization technique that utilizes RFFPs captured by a mobile device to determine the location of the mobile device. The RFFP can be a histogram of received signal strength indicator (RSSI), CER, CIR, PDP, or channel frequency response (CFR). The RFFP can represent a single channel received from a transmitter (e.g., PRS), all channels received from a specific transmitter, or all channels detectable at the receiver. The RFFP(s) measured by a mobile device (e.g., UE) and the location of the transmitter(s) associated with the measured RFFP(s) (i.e., the transmitter that transmits the RF signal measured by the mobile device to determine the RFFP(s)) can be used to determine the location of the mobile device (e.g., triangulation).

[0129] Machine learning positioning techniques have been shown to provide superior positioning performance compared to classical positioning methods. In machine learning-RFFP-based positioning, a machine learning model (e.g., neural network 700) takes the RFFP of a downlink reference signal (e.g., PRS) as input and outputs a positioning measurement (e.g., ToA, RSTD) or mobile device location corresponding to the input RFFP. The machine learning model (e.g., neural network 700) is trained using "ground truth" (i.e., known) positioning measurements or mobile device locations as the reference (i.e., expected) output of the training set of RFFPs.

[0130] For example, a machine learning model can be trained to determine the RSTD measurements of pairs of TRPs from the RFFPs of PRSs transmitted by the TRPs. The reference output for training such a model would be the correct (i.e., ground truth) RSTD measurement for the location of the mobile device when the mobile device obtains RFFP measurements of the PRS. A network (e.g., a location server) can determine the RSTD that would be expected for a pair of TRPs based on the known location of the mobile device and the known locations of the involved (measured) TRPs. The known location of the mobile device can be determined from a plurality of reported RSTD measurements and / or any other measurements reported by the mobile device (e.g., GPS measurements).

[0131] FIG. 8 is a diagram 800 showing the use of a machine learning model for RFFP-based positioning, according to an aspect of the present disclosure. In the example of FIG. 8, during the “offline” phase, RFFPs (e.g., CER / CIR / CFR) captured by a mobile device are stored in a database. The database can be located on the mobile device or a network entity (e.g., a location server), and each RFFP can include measurements of RF signals (or channels or links) transmitted by one or more transmitters shown as base stations 1 to N (i.e., “BS 1” to “BS N”) in FIG. 8. In the case of UE-based downlink RFFP (DL-RFFP) positioning, a network (e.g., a location server) configures the base stations to transmit a downlink reference signal (e.g., a PRS) to the mobile device, and the RFFP is the CER(s) / CIR(s) / CFR(s) of the configured downlink reference signal detected by the mobile device.

[0132] Each measured RFFP is associated with a known location of the mobile device at the time the mobile device measured the RFFP, shown in FIG. 8 as positions 1 through L (i.e., "Pos 1" through "Pos L"). The location of the mobile device may be known via another positioning technique, as discussed above with reference to FIG. 4. FIG. 8 shows RFFP information for a single mobile device, but it should be noted that RFFP information for multiple mobile devices can be collected and stored in a database, as will be understood.

[0133] Based on the information captured during the offline phase, a machine learning model (e.g., neural network 700) is trained to predict the location of the mobile device based on the RFFP measured by the mobile device. More specifically, a training set of RFFP measurements is used as input to the machine learning model, and the known location of the mobile device when the RFFP was captured is used as a label. After training, during the "online" phase, the trained machine learning model can be used to predict (infer) the location of the mobile device (shown as "Pos M") based on the RFFP(s) currently being measured by the mobile device. In the case of UE-based RFFP positioning, the network (e.g., a location server) provides the trained machine learning model to the mobile device. In the case of UE-assisted positioning, the mobile device may provide the RFFP measurements to the network for processing.

[0134] FIG. 8 shows the use of an RFFP-based machine learning model to estimate the location of the UE, but it should be noted that the output (or extracted features) of the machine learning model can instead be positioning measurements based on the input RFFP, such as RSTD measurements, ToA measurements, DL-AoD measurements, etc.

[0135] FIG. 9 is a diagram 900 showing an inference cycle for UE-based DL-RFFP positioning according to an aspect of the present disclosure. As shown in FIG. 9, a location server (e.g., LMF 270) configures DL-PRS resources to be transmitted by one or more TRPs during a positioning session with a UE. The TRP(s) then transmits the configured DL-PRS to the UE, and the UE measures the RFFP of the DL-PRS.

[0136] In the example of FIG. 9, the location server has pre-trained a machine learning model for RFFP positioning (labeled "RFFP ML") as discussed above with reference to FIGS. 7 and 8. The location server provides the machine learning model to the UE to perform an inference (e.g., determine a positioning measurement based on the measured RFFP) during the positioning session. Therefore, after measuring the RFFP of the DL-PRS, the UE inputs the measured RFFP into the received machine learning model to obtain the relevant positioning measurement(s) (e.g., ToA, RSTD).

[0137] FIG. 10 shows an exemplary call flow 1000 for UE-based DL-RFFP positioning according to an aspect of the present disclosure. In step 1, UE 204 and LMF 270 perform an LPP positioning capability transfer procedure, during which UE 204 provides its positioning capabilities to LMF 270. In step 2, LMF 270 provides assistance information such as the PRS resource configuration of the DL-PRS to be transmitted to UE 204 to the serving ng-eNB / gNB 222 / 224 of UE 204 and any neighboring ng-eNB / gNB 222 / 224. In step 3, UE 204 and LMF 270 perform LPP assistance data exchange. During the exchange, LMF 270 provides assistance data for the positioning session to UE 204, such as the configuration of the DL-PRS transmitted by the involved ng-eNB / gNB 222 / 224 and the machine learning model used to report the positioning measurements of the DL-PRS.

[0138] In stage 4, LMF270 optionally provides assistance information to the involved ng-eNB / gNB222 / 224 via a New Radio positioning protocol type A (NRPPa) message. In stage 5, the serving ng-eNB / gNB222 / 224 optionally broadcasts the assistance information received from LMF270 as assistance data in one or more positioning system information blocks (posSIBs). In stage 6, LMF270 and UE204 perform an LPP request / location information provision procedure, during which UE204 provides positioning measurements taken from the DL-PRS transmitted by ng-eNB / gNB222 / 224. The positioning measurements may be derived by applying the machine learning model received in the assistance data to the RFFP of the measured DL-PRS. The various stages shown in FIG. 10 are discussed in more detail below.

[0139] Currently, LPP and NRPPa do not support RFFP positioning procedures. Accordingly, the present disclosure provides LPP and NRPPa signaling and procedures for enabling UE-based DL-RFFP positioning.

[0140] Referring more specifically to the LPP positioning capability transfer in stage 1 of FIG. 10, FIG. 11 shows two procedures for exchanging network and UE positioning capabilities currently supported by LPP. The first is a capability transfer procedure and the second is a capability indication procedure. FIG. 1100 shows the capability transfer procedure, during which a location server (e.g., LMF270) indicates the types of capabilities required from UE204 (e.g., in the "LPP RequestCapabilities" information element (IE)). FIG. 1150 shows the capability indication procedure, during which the target (e.g., UE204) provides unsolicited capabilities to the server (e.g., in the LPP "ProvideCapabilities" IE).

[0141] Currently, LPP does not support UE-based DL-RFFP capability requests or indications. Therefore, the present disclosure provides signaling to enable a location server to request and a UE to provide UE capabilities for UE-based DL-RFFP positioning. Specifically, the location server can request the target UE to provide capabilities related to UE-based DL-RFFP positioning as part of the LPP positioning capability transfer procedure in stage 1 of FIG. 10. For example, the request can be a "nr-DL-RFFP-RequestCapabilities" parameter (e.g., an IE) in the LPP "RequestCapabilities" IE similar to the LPP "otdoa-RequestCapabilities" IE, LPP "ecid-RequestCapabilities" IE, LPP "nr-Multi-RTT-RequestCapabilities" IE, etc.

[0142] Such a request can first query the target UE about its general capabilities description (e.g., whether the UE can support UE-based DL-RFFP positioning). The request can include a flag to notify the target UE whether it should provide a detailed capabilities response or wait for a specific request. Further specific requests can claim certain capabilities based on the UE's response.

[0143] The target UE may provide its UE-based DL-RFFP positioning capabilities to the location server as part of the LPP capability transfer procedure (shown by Figure 1100 of Figure 11 in FIG. 11) or the LPP capability indication procedure (shown by Figure 1150 of Figure 11 in FIG. 11). In the case of the LPP capability indication procedure, the target UE may indicate an initial set of its UE-based DL-RFFP positioning capabilities and then wait for the capability requirements requested by the location server. The UE may report its RFFP positioning capabilities in a "nr-DL-RFFP-ProvideCapabilities" parameter (e.g., an IE) within the LPP "ProvideCapabilities" IE, similar to the "otdoa-ProvideCapabilities" IE, the LPP "nr-DL-AoD-ProvideCapabilities" IE, etc.

[0144] As another option, some of the UE-based DL-RFFP positioning capabilities can be exchanged as part of the LPP capability transfer procedure or the LPP capability indication procedure, and the remaining RFFP positioning capabilities can be provided through other artificial intelligence (AI) or machine learning network entities (e.g., 3GPP or non-3GPP). Then, the location server will need to cooperate with other network entities to retrieve these remaining capabilities.

[0145] The capability message from the target UE may include a flag indicating the capabilities of the target UE for performing DL-RFFP positioning using a network-provided machine learning model. For example, a value of "0" may indicate that UE-based DL-RFFP positioning is not supported, and a value of "1" may indicate that UE-based DL-RFFP positioning is supported.

[0146] When UE-based DL-RFFP positioning is supported, the capability message may include a flag indicating how the location server should retrieve the capabilities of the target UE to handle the machine learning model for positioning. For example, a value of "0" may indicate that the machine learning model capability parameters will be sent as part of the LPP "ProvideCapabilities" message. A value of "1" may indicate that the machine learning model capability parameters will be sent via another AI or machine learning network entity. The location server will then need to cooperate with other network entities to retrieve these remaining capabilities. The flag may be associated with each capability parameter, or group of capability parameters.

[0147] The capability message may include the maximum number of concurrent machine learning instances that the target UE can handle (i.e., concurrent instances of the machine learning model that can be activated for concurrent positioning sessions). The capability message may also include resource capabilities (e.g., LPP IE "NR-DL-PRS-ResourcesCapability") and resource processing capabilities (e.g., LPP IE "NR-DL-PRS-ProcessingCapability") related to UE-based DL-RFFP positioning. These capabilities may include, for example, the maximum number of frequency layers, frequency band indicators, bandwidth, PRS buffer capabilities, etc.

[0148] The capabilities message may further include a list of supported machine learning model formats (e.g., Open Neural Network Exchange (ONNX), etc.). The capabilities message may also include the maximum machine learning model size (e.g., the maximum number of parameters). The capabilities message may also include a list of supported features (e.g., CFR, CIR, Doppler statistics, delay spread statistics, etc.), the maximum IFFT size, the maximum number of antenna pairs that the target UE can process (which may be a buffering capability), the maximum channel estimation (e.g., CIR, CFR) window (which may be a buffering capability), etc., parameters related to inference. The purpose of these parameters is that the machine learning model will be provided by the location server, and thus, the location server needs to know which machine learning model(s) the target UE can support.

[0149] Referring more specifically to the LPP assistance data exchange in stage 3 of FIG. 10, FIG. 12 shows two procedures for exchanging positioning assistance data currently supported by LPP. The first is the assistance data transfer procedure, and the second is the assistance data delivery procedure. FIG. 1200 shows the assistance data transfer procedure, during which the location server (e.g., LMF 270) provides the assistance data required for positioning (e.g., in the LPP "ProvideAssistanceData" IE) in response to a request for assistance data from the target UE (e.g., the LPP "RequestAssistanceData" IE). The assistance data may be provided on demand, periodically, or periodically updated. FIG. 1250 shows the assistance data delivery procedure, during which the location server provides unsolicited assistance data required for positioning. The assistance data may be provided periodically or aperiodically.

[0150] Currently, LPP does not support the request or delivery of UE-based DL-RFFP positioning assistance data. Therefore, the present disclosure provides signaling to enable a target UE to request and a location server to provide positioning assistance data for UE-based DL-RFFP positioning. Specifically, the target UE can request the location server to provide assistance data related to UE-based DL-RFFP positioning as part of the LPP assistance data transfer procedure (shown by Figure 1200 of Figure 12). For example, the request can be the "nr-DL-RFFP-RequestAssistanceData" parameter (e.g., IE) in the LPP "RequestAssistanceData" IE.

[0151] The location server can then provide assistance data related to UE-based DL-RFFP positioning as part of the LPP assistance data transfer procedure (shown by Figure 1200 of Figure 12) or the LPP assistance data delivery procedure (shown by Figure 1250 of Figure 12). For example, the assistance data can be provided in the "nr-DL-RFFP-ProvideAssistanceData" parameter (e.g., IE) in the LPP "ProvideAssistanceData" IE.

[0152] The assistance data message can include a flag indicating whether the target UE should expect machine learning model details as part of the LPP assistance data message or whether the target UE should retrieve the machine learning model through another AI or machine learning network entity (e.g., 3GPP or non-3GPP). For example, a value of "0" can indicate that the assistance data does not include a description of the machine learning model, and a value of "1" can indicate that the assistance data includes a description of the machine learning model.

[0153] The support data message may provide information related to the description of the machine learning model, such as the machine learning model identifier (ID), machine learning model details (format (e.g., ONNX), machine learning model structure and parameters (i.e., weights), etc.), input feature types (e.g., CFR, CIR, etc.). The support data message may also provide information related to the mapping of measurement values to the machine learning model input (e.g., a bitmap of measurement values to the machine learning model input).

[0154] The support data message may further include a flag indicating whether the target UE should perform pre-measurement processing before positioning. For example, a value of "0" may indicate that no pre-measurement processing is required (meaning that any pre-measurement processing is part of the machine learning model design). A value of "1" may indicate that pre-measurement processing is required (meaning that pre-measurement processing steps are explicitly provided).

[0155] If the target UE is expected to perform preprocessing, the support data message may also provide information on how to preprocess the measurement values before passing them to the machine learning model. Pre-measurement processing operations include (1) calibration, (2) IFFT, (3) cyclic sample shift, (4) windowing, and (5) scaling. The support data may indicate the sequence in which these operations are to be performed. Pre-measurement processing parameters may include calibration values, IFFT size, cyclic sample shift value, window parameters (weights, length, and center location), and / or scaling options (e.g., per antenna, per TRP, all).

[0156] The assistance data may also include information related to the resources to be used for UE-based DL-RFFP positioning. For example, the assistance data may include physical cell IDs (PCIs), global cell IDs (GCIs), ARFCN, and PRS ID of candidate TRPs for measurement, DL-PRS configuration of candidate TRPs, SSB information of the TRP (e.g., time / frequency occupancy of the SSB), spatial direction information of the DL-PRS resources of the TRP (e.g., azimuth, elevation, etc.), geographical coordinates of the TRP (including the transmission reference location of each DL-PRS resource ID, the reference location of the transmission antenna of the reference TRP, the relative location of the transmission antennas of other TRPs), PRS dedicated transmission point indication, etc.

[0157] Referring more specifically to the LPP location information exchange in step 6 of FIG. 10, FIG. 13 shows two procedures for exchanging the location information currently supported by LPP. The first is the location information transfer procedure, and the second is the location information distribution procedure. FIG. 1300 shows the location information transfer procedure, and FIG. 1350 shows the location information distribution procedure. The location information transfer procedure (FIG. 1300) is used to support the transfer of positioning estimations based on the requested service. The location server may send an LPP "RequestLocationInformation" IE indicating the type of location information required and the associated QoS. The location information distribution procedure (FIG. 1350) supports the distribution of positioning estimations based on unsolicited services. In both the location information transfer procedure and the location information distribution procedure, the target UE sends an LPP "ProvideLocationInformation" IE containing the requested information or unsolicited information.

[0158] Currently, LPP does not support the request or delivery of location information related to UE-based DL-RFFP procedures. Therefore, the present disclosure provides signaling to enable a location server to request and a target UE to provide location information for UE-based DL-RFFP positioning. Specifically, the location server can request the target UE to provide location information related to UE-based DL-RFFP positioning as part of the LPP location information transfer procedure in stage 6 of FIG. 10. For example, the request can be the "nr-DL-RFFP-RequestLocationInformation" parameter (e.g., IE) in the LPP "RequestLocationInformation" IE.

[0159] The location information request message may include a reporting configuration indicating the periodicity of reporting the estimated location of the target UE. The request message may also include the type of the requested location (e.g., absolute, relative, TDOA estimate, ToA estimate, etc.). The request message may also include a rough estimate of the location of the target UE to enable the UE to utilize the rough location estimate to improve positioning.

[0160] The location information request message may optionally include an update regarding the downlink resources (e.g., DL-PRS resources) that can be used for positioning. The request message may also optionally include an update to the measurement preprocessing operations to be applied by the target UE (e.g., calibration, IFFT, windowing, etc.). The request message may also optionally include an update to the machine learning model to be used for positioning (e.g., updated model ID, request for the target UE to download an updated machine learning model from another network-side model repository). The request message may further optionally include a flag to trigger the target UE to report the downlink resources used for positioning.

[0161] In response to the location information request, the target UE performs UE-based DL-RFFP positioning as requested and provides location information as part of the provided location information message. For example, the UE may provide the requested location information in the "nr-DL-RFFP-ProvideLocationInformation" parameter (e.g., IE) as part of the location information transfer or delivery procedure shown in FIG. 13. The "nr-DL-RFFP-ProvideLocationInformation" parameter / IE may be included in the LPP "ProvideLocationInformation" IE.

[0162] The provided location information message may include the estimated location of the target UE and / or the estimated ToA or RSTD if a machine learning model is used to estimate those measurements. The provided location information message may also include a metric for indicating the quality / reliability of the estimated target location. The provided location information message may also include the time required to execute the machine learning model and obtain an inference of the target UE's location. The provided location information message may also include the timestamp of the reported measurements. The provided location information message may also include measurements of the downlink resources (e.g., DL-PRS) used in RFFP positioning (e.g., RSRP). The provided location information may also include the ID of the resources used in RFFP positioning.

[0163] The provided location information message may further include customized additional measurement elements. These may be customized by the UE vendor, network operator, machine learning model vendor, etc.

[0164] Next, referring to the optional broadcast of assistance information in steps 4 and 5 of FIG. 10, the broadcast of positioning assistance data is currently supported via the broadcast of posSIB. The posSIB is carried in the RRC system information (SI) message. In the case of NR RRC SI, a single "SIBpos" IE is defined, which is carried in the IE "PosSystemInformation". There is a mapping of the positioning SIB type (in the IE "posSibType") to the assistance data elements carried in the posSIB. For example, posSibType1-1 to posSibType1-8 provide common assistance data for global navigation satellite system (GNSS) positioning, posSibType3-1 provides assistance data for OTDOA positioning, and posSibType6-1 to posSibType6-3 provide assistance data for DL-TDOA / DL-AoD positioning.

[0165] The location server (e.g., LMF270) may signal positioning assistance information to the NG-RAN node in order to broadcast assistance data in posSIB. FIG. 14 is a diagram 1400 showing the assistance information control procedure between the location server (e.g., LMF270) and the NG-RAN node (e.g., gNB). The assistance information control procedure is applicable when the NG-RAN node is a gNB and may be implemented at stage 4 of FIG. 10. As described with reference to FIG. 10, the signaling between the location server and the NG-RAN node is via NRPPa. The purpose of the assistance information control procedure is to enable the location server to signal positioning assistance information to the NG-RAN node for assistance data broadcast. That is, the location server sends the content of the posSIB(s) to be broadcast via RRC. The location server may send assistance information in response to a UE request for "on-demand assistance data" to be broadcast by the NG-RAN node or such assistance data simply referred to as cell-wide assistance data.

[0166] Currently, there is no support for broadcasting assistance information related to UE-based DL-RFFP positioning. Therefore, the present disclosure provides signaling to support the broadcast of assistance data for UE-based DL-RFFP positioning. The location server may provide assistance information related to UE-based DL-RFFP positioning as part of the assistance information control procedure shown in FIG. 14. The assistance information may then be broadcast in one or more RRC posSIBs.

[0167] Similar to the currently defined posSIB, there may be a mapping of the positioning SIB type (in the IE "posSibType") to the assistance data elements transmitted in the posSIB. Table 1 below shows an exemplary mapping.

[0168]

Table 1

[0169] For the broadcasted posSIB, a flag may be included indicating whether the target UE should anticipate the machine learning model details as part of the LPP assistance data message (at stage 3 of FIG. 10 and as shown in FIG. 13), or whether the target UE should retrieve the model through another AI or machine learning model network entity. For example, a value of "0" may indicate that the broadcasted posSIB assistance data does not include a description of the machine learning model, and a value of "1" may indicate that the broadcasted posSIB assistance data includes a description of the machine learning model.

[0170] The posSIB message for DL-RFFP positioning may provide information related to the machine learning model description, such as the machine learning model ID, machine learning model details (format (e.g., ONNX), machine learning model structure and parameters (i.e., weights), etc.), input feature types (e.g., CFR, CIR, etc.). The posSIB message may also provide information regarding the mapping of measurements to the machine learning model input (e.g., a bitmap of measurements to the machine learning model input).

[0171] The posSIB message for DL-RFFP positioning may include a flag indicating whether the target UE should perform pre-measurement processing before positioning. For example, a value of "0" may indicate that pre-measurement processing is not required (i.e., pre-measurement processing is part of the machine learning model design), and a value of "1" may indicate that pre-measurement processing is required (and the pre-measurement processing steps are explicitly provided).

[0172] If a flag indicates that preprocessing is required, the posSIB message may provide assistance data regarding how to preprocess the measurement values before the target UE passes the measurement values to the machine learning model. As described above, the pre-measurement processing operations include (1) calibration, (2) IFFT, (3) cyclic sample shift, (4) windowing, and (5) scaling. The assistance data may indicate the sequence of performing these operations. The pre-measurement processing parameters may include calibration values, IFFT sizes, cyclic sample shift values, window parameters (weights, lengths, and center locations), and / or scaling options (e.g., per antenna, per TRP, all).

[0173] The posSIB message for DL-RFFP positioning may also provide assistance data related to the resources (e.g., DL-PRS resources) to be used for positioning. For example, as shown in Table 1, posSIBType7-1 may provide assistance data for the DL-PRS resources to be measured.

[0174] FIG. 15 shows an exemplary method 1500 of wireless communication according to an aspect of the present disclosure. In one aspect, the method 1500 may be performed by a UE (e.g., any of the UEs described herein).

[0175] At 1510, the UE transmits one or more provide-capability messages indicating at least a first set of the UE's capabilities for participating in DL-RFFP positioning procedures to a location server. In one aspect, operation 1510 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be regarded as means for performing this operation.

[0176] At 1520, the UE receives from the location server one or more positioning assistance data messages for DL-RFFP positioning procedures, based at least on a first set of capabilities. In one aspect, operation 1520 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be regarded as means for performing this operation.

[0177] As will be appreciated, the technical advantage of method 1500 is that it enables the UE to provide positioning capabilities and receive assistance data specific to DL-RFFP positioning.

[0178] FIG. 16 shows an exemplary method 1600 of wireless communication according to an aspect of the present disclosure. In one aspect, method 1600 may be performed by a UE (e.g., any of the UEs described herein).

[0179] At 1610, the UE receives from a first network entity one or more positioning assistance data messages for DL-RFFP positioning procedures, including at least one parameter related to a machine learning model configured for use by the UE for DL-RFFP positioning procedures. In one aspect, operation 1610 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be regarded as means for performing this operation.

[0180] At 1620, the UE transmits to a second network entity one or more location information messages including one or more parameters related to DL-RFFP positioning procedures. In one aspect, operation 1620 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be regarded as means for performing this operation.

[0181] As will be appreciated, the technical advantage of method 1600 is to provide the UE with assistance data specific to DL-RFFP positioning and enable the UE to provide location information specific to DL-RFFP positioning.

[0182] FIG. 17 shows an exemplary method 1700 of wireless communication according to an aspect of the present disclosure. In one aspect, method 1700 may be performed by a UE (e.g., any of the UEs described herein).

[0183] At 1710, the base station receives from the location server one or more assistance information control messages indicating one or more parameters related to a machine learning model configured for use by at least one UE for DL-RFFP positioning procedures. In one aspect, operation 1710 may be performed by one or more WWAN transceivers 350, one or more network transceivers 380, one or more processors 384, memory 386, and / or positioning component 388, any or all of which may be regarded as means for performing this operation.

[0184] At 1720, the base station transmits to at least one UE one or more posSIBs specific to DL-RFFP positioning indicating at least one or more parameters. In one aspect, operation 1720 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or positioning component 388, any or all of which may be regarded as means for performing this operation.

[0185] As will be appreciated, the technical advantage of method 1700 is to provide the UE with assistance data specific to DL-RFFP positioning.

[0186] In the embodiments for carrying out the above invention, it can be seen that in each example, various features are grouped together. This manner of disclosure should not be understood as an intention that the exemplary clauses have more features than are explicitly stated within each clause. Rather, various aspects of the present disclosure may include fewer features than all the features of the individual exemplary clauses being disclosed. Accordingly, the following clauses should be considered as incorporated into the description, and each clause may be valid separately as a distinct example. Each dependent clause may refer within that clause to a particular combination with one of the other clauses, but the aspect(s) of that dependent clause is not limited to that particular combination. It will be understood that other exemplary clauses may also include combinations of aspect(s) of dependent clauses with the subject matter of any other dependent or independent clause, or any combination of features with other dependent and independent clauses. Various aspects disclosed herein do not explicitly include these combinations unless it is explicitly stated or cannot be readily inferred that a particular combination (such as defining an element as both an electrical insulator and an electrical conductor, conflicting aspects) is not intended. Further, even if a clause is not directly dependent on an independent clause, it is also intended that the aspect of the clause may be included in any other independent clause.

[0187] In the following numbered clauses, implementation examples are described. Clause 1. A method of wireless communication implemented by a user equipment (UE), the method comprising: transmitting, to a location server, one or more provisioning capability messages indicating at least a first set of capabilities of the UE for participating in a downlink radio frequency fingerprint (DL-RFFP) positioning procedure; and receiving, from the location server, one or more positioning assistance data messages for the DL-RFFP positioning procedure based at least on the first set of capabilities.

[0188] Clause 2. The method according to clause 1, wherein the first set of capabilities is an initial set of capabilities of the UE for participating in the DL-RFFP positioning procedure.

[0189] The method according to clause 1 or 2, further comprising receiving, from a location server, a first capability request message that requests at least a first set of capabilities of the UE.

[0190] Clause 4. The method according to clause 3, wherein the first capability request message includes a flag, and the flag configures the UE to provide all capabilities of the UE related to the DL-RFFP positioning procedure in one or more provided capability messages, or to wait for a subsequent request for specific capabilities of the UE related to the DL-RFFP positioning procedure.

[0191] Clause 5. The method according to clause 4, further comprising receiving, from a location server, a second capability request message that requests a second set of capabilities of the UE, based on configuring the UE to wait for a subsequent request for specific capabilities of the UE related to the DL-RFFP positioning procedure.

[0192] Clause 6. The method according to any one of clauses 1 to 5, further comprising transmitting, to a network entity other than the location server, a second provided capability message that includes a second set of capabilities of the UE for participating in the DL-RFFP positioning procedure, the second set of capabilities including capabilities different from the first set of capabilities.

[0193] Clause 7. The method according to clause 6, wherein the first set of capabilities of the UE includes a flag indicating that the UE supports DL-RFFP positioning, and the second set of capabilities of the UE includes all capabilities of the UE related to the DL-RFFP positioning procedure.

[0194] Clause 8. The method according to any one of clauses 1 to 7, wherein one or more provided capability messages include a first flag indicating whether the UE is capable of using a network-provided machine learning model for the DL-RFFP positioning procedure.

[0195] Clause 9. The method according to clause 8, wherein one or more provisioning capability messages include a second flag indicating how the location server can retrieve the UE's capabilities for using a network-provided machine learning model.

[0196] Clause 10. The method according to clause 9, wherein a first value of the second flag indicates that the UE's capabilities for using a network-provided machine learning model are included in one or more provisioning capability messages, and a second value of the second flag indicates that the UE's capabilities for using a network-provided machine learning model are stored in a network entity other than the location server.

[0197] Clause 11. The method according to any one of clauses 8 to 10, wherein a first set of capabilities indicates the maximum number of simultaneous machine learning positioning instances supported by the UE, the downlink positioning reference signal (DL-PRS) resource capabilities related to the DL-RFFP positioning procedure, the DL-PRS resource processing capabilities related to the DL-RFFP positioning procedure, or any combination thereof.

[0198] Clause 12. The method according to any one of clauses 8 to 11, wherein a first set of capabilities indicates a list of machine learning model formats supported by the UE, the maximum number of parameters for a network-provided machine learning model supported by the UE, one or more parameters related to the inference using a network-provided machine learning model, or any combination thereof.

[0199] Clause 13. The method according to clause 12, wherein one or more parameters related to the inference using a network-provided machine learning model indicate a list of features supported by the UE, the maximum inverse fast Fourier transform (IFFT) size supported by the UE, the maximum number of antenna pairs that the UE can process, the maximum channel estimation window size supported by the UE, or any combination thereof.

[0200] The method according to any one of clauses 8 to 13, further comprising receiving a machine learning model for network provision from a location server or a network entity other than the location server.

[0201] Clause 15. A user equipment (UE), comprising a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor transmits, via the at least one transceiver, one or more offering capability messages indicating at least a first set of the UE's capabilities for participating in a downlink radio frequency fingerprint (DL-RFFP) positioning procedure to a location server, and receives, via the at least one transceiver, one or more positioning assistance data messages for the DL-RFFP positioning procedure based at least on the first set of capabilities from the location server.

[0202] Clause 16. The UE according to clause 15, wherein the first set of capabilities is an initial set of the UE's capabilities for participating in the DL-RFFP positioning procedure.

[0203] Clause 17. The UE according to clause 15 or 16, wherein the at least one processor is further configured to receive, via the at least one transceiver, a first capability request message requesting at least the first set of the UE's capabilities from the location server.

[0204] Clause 18. The UE according to clause 17, wherein the first capability request message includes a flag, and the flag configures the UE to provide all of the UE's capabilities related to the DL-RFFP positioning procedure in one or more offering capability messages, or to wait for a subsequent request for specific capabilities of the UE related to the DL-RFFP positioning procedure.

[0205] Clause 19. The UE according to Clause 18, further configured to receive, via at least one transceiver, a second capability request message requesting a second set of UE capabilities, based on at least one processor configuring the UE to wait for a subsequent request in which the flag requests a specific capability of the UE relevant to the DL-RFFP positioning procedure.

[0206] Clause 20. The UE according to any of Clauses 15 to 19, further configured to transmit, via at least one transceiver, a second provided capability message including a second set of UE capabilities for participating in the DL-RFFP positioning procedure, the second set of capabilities including capabilities different from the first set of capabilities, to a network entity other than the location server.

[0207] Clause 21. The UE according to Clause 20, wherein the first set of UE capabilities includes a flag indicating that the UE supports DL-RFFP positioning, and the second set of UE capabilities includes all capabilities of the UE relevant to the DL-RFFP positioning procedure.

[0208] Clause 22. The UE according to any of Clauses 15 to 21, wherein one or more provided capability messages include a first flag indicating whether the UE is capable of using a network-provided machine learning model for the DL-RFFP positioning procedure.

[0209] Clause 23. The UE according to Clause 22, wherein one or more provided capability messages include a second flag indicating how the location server can extract the UE's capabilities for using a network-provided machine learning model.

[0210] Clause 24. The UE according to clause 23, wherein the first value of the second flag indicates that the UE's capabilities for using the network-provided machine learning model are included in one or more provisioning capability messages, and the second value of the second flag indicates that the UE's capabilities for using the network-provided machine learning model are stored in a network entity other than the location server.

[0211] Clause 25. The UE according to any one of clauses 22 to 24, wherein the first set of capabilities indicates the maximum number of simultaneous machine learning positioning instances supported by the UE, the downlink positioning reference signal (DL-PRS) resource capabilities related to the DL-RFFP positioning procedure, the DL-PRS resource processing capabilities related to the DL-RFFP positioning procedure, or any combination thereof.

[0212] Clause 26. The UE according to any one of clauses 22 to 25, wherein the first set of capabilities indicates a list of machine learning model formats supported by the UE, the maximum number of parameters for the network-provided machine learning model supported by the UE, one or more parameters related to the inference using the network-provided machine learning model, or any combination thereof.

[0213] Clause 27. The UE according to clause 26, wherein the one or more parameters related to the inference using the network-provided machine learning model indicate a list of features supported by the UE, the maximum inverse fast Fourier transform (IFFT) size supported by the UE, the maximum number of antenna pairs that the UE can process, the maximum channel estimation window size supported by the UE, or any combination thereof.

[0214] Clause 28. The UE according to any one of clauses 22 to 27, wherein at least one processor is further configured to receive a network-provided machine learning model from a location server or a network entity other than the location server via at least one transceiver.

[0215] Clause 29. A user equipment (UE) comprising means for transmitting to a location server one or more provided-capability messages indicating at least a first set of the UE's capabilities for participating in a downlink radio frequency fingerprint (DL-RFFP) positioning procedure, and means for receiving from the location server one or more positioning assistance data messages for the DL-RFFP positioning procedure, based at least on the first set of capabilities.

[0216] Clause 30. The UE according to clause 29, wherein the first set of capabilities is an initial set of the UE's capabilities for participating in the DL-RFFP positioning procedure.

[0217] Clause 31. The UE according to clause 29 or 30, further comprising means for receiving from the location server a first capability request message requesting at least the first set of the UE's capabilities.

[0218] Clause 32. The UE according to clause 32 or 31, wherein the first capability request message includes a flag, and the flag configures the UE to provide all of the UE's capabilities related to the DL-RFFP positioning procedure in one or more provided-capability messages, or to wait for a subsequent request for specific capabilities of the UE related to the DL-RFFP positioning procedure.

[0219] Clause 33. The UE according to clause 33 or 32, further comprising means for receiving from the location server a second capability request message requesting a second set of the UE's capabilities, based on configuring the UE to wait for a subsequent request for specific capabilities of the UE related to the DL-RFFP positioning procedure.

[0220] Clause 34. The UE according to any one of clauses 29 to 33, further comprising means for transmitting to a network entity other than the location server a second provided-capability message including a second set of the UE's capabilities for participating in the DL-RFFP positioning procedure, the second set of capabilities including capabilities different from the first set of capabilities.

[0221] Clause 35. The UE according to Clause 34, wherein a first set of UE capabilities includes a flag indicating that the UE supports DL-RFFP positioning, and a second set of UE capabilities includes all the capabilities of the UE related to the DL-RFFP positioning procedure.

[0222] Clause 36. The UE according to any one of Clauses 29 to 35, wherein one or more provisioning capability messages include a first flag indicating whether the UE is capable of using a network-provided machine learning model for the DL-RFFP positioning procedure.

[0223] Clause 37. The UE according to Clause 36, wherein one or more provisioning capability messages include a second flag indicating how the location server can retrieve the UE's capabilities for using a network-provided machine learning model.

[0224] Clause 38. The UE according to Clause 37, wherein a first value of the second flag indicates that the UE's capabilities for using a network-provided machine learning model are included in one or more provisioning capability messages, and a second value of the second flag indicates that the UE's capabilities for using a network-provided machine learning model are stored in a network entity other than the location server.

[0225] Clause 39. The UE according to any one of Clauses 36 to 38, wherein the first set of capabilities indicates the maximum number of concurrent machine learning positioning instances supported by the UE, the downlink positioning reference signal (DL-PRS) resource capabilities related to the DL-RFFP positioning procedure, the DL-PRS resource processing capabilities related to the DL-RFFP positioning procedure, or any combination thereof.

[0226] Clause 40. The UE as described in any of Clauses 36 to 39, wherein the first set of capabilities indicates a list of machine learning model formats supported by the UE, the maximum number of parameters for a network-provided machine learning model supported by the UE, one or more parameters related to inferences using the network-provided machine learning model, or any combination thereof.

[0227] Clause 41. The UE as described in Clause 40, wherein one or more parameters related to inferences using the network-provided machine learning model indicate a list of features supported by the UE, the maximum inverse fast Fourier transform (IFFT) size supported by the UE, the maximum number of antenna pairs that the UE can process, the maximum channel estimation window size supported by the UE, or any combination thereof.

[0228] Clause 42. The UE as described in any of Clauses 36 to 41, further comprising means for receiving a network-provided machine learning model from a location server or a network entity other than the location server.

[0229] Clause 43. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), cause the UE to send to a location server one or more provisioning capability messages indicating at least a first set of the UE's capabilities for participating in downlink radio frequency fingerprint (DL-RFFP) positioning procedures, and receive from the location server one or more positioning assistance data messages for the DL-RFFP positioning procedures based at least on the first set of capabilities.

[0230] Clause 44. The non-transitory computer-readable medium as described in Clause 43, wherein the first set of capabilities is an initial set of the UE's capabilities for participating in DL-RFFP positioning procedures.

[0231] Clause 45. The non-transitory computer-readable medium according to clause 43 or 44, further comprising computer-executable instructions which, when executed by a UE, cause the UE to receive from a location server a first capability request message that requests at least a first set of the UE's capabilities.

[0232] Clause 46. The non-transitory computer-readable medium according to clause 45, wherein the first capability request message includes a flag that configures the UE to provide all of the UE's capabilities related to the DL-RFFP positioning procedure in one or more provide-capability messages, or to wait for a subsequent request that requests specific capabilities of the UE related to the DL-RFFP positioning procedure.

[0233] Clause 47. The non-transitory computer-readable medium according to clause 46, further comprising computer-executable instructions which, when executed by a UE, cause the UE to receive from a location server a second capability request message that requests a second set of the UE's capabilities, based on configuring the UE to wait for a subsequent request that requests specific capabilities of the UE related to the DL-RFFP positioning procedure.

[0234] Clause 48. The non-transitory computer-readable medium according to any one of clauses 43 to 47, further comprising computer-executable instructions which, when executed by a UE, cause the UE to send to a network entity other than the location server a second provide-capability message that includes a second set of the UE's capabilities for participating in the DL-RFFP positioning procedure, the second set of capabilities including capabilities different from the first set of capabilities.

[0235] Clause 49. The non-transitory computer-readable medium according to clause 48, wherein the first set of the UE's capabilities includes a flag indicating that the UE supports DL-RFFP positioning, and the second set of the UE's capabilities includes all of the UE's capabilities related to the DL-RFFP positioning procedure.

[0236] Clause 50. A non-transitory computer-readable medium according to any of Clauses 43 to 49, wherein one or more provisioning capability messages include a first flag indicating whether the UE can use a network-provided machine learning model for DL-RFFP positioning procedures.

[0237] Clause 51. A non-transitory computer-readable medium according to Clause 50, wherein one or more provisioning capability messages include a second flag indicating how the location server can retrieve the UE's capabilities for using a network-provided machine learning model.

[0238] Clause 52. A non-transitory computer-readable medium according to Clause 51, wherein a first value of the second flag indicates that the UE's capabilities for using a network-provided machine learning model are included in one or more provisioning capability messages, and a second value of the second flag indicates that the UE's capabilities for using a network-provided machine learning model are stored in a network entity other than the location server.

[0239] Clause 53. A non-transitory computer-readable medium according to any of Clauses 50 to 52, wherein a first set of capabilities indicates the maximum number of simultaneous machine learning positioning instances supported by the UE, the downlink positioning reference signal (DL-PRS) resource capabilities related to the DL-RFFP positioning procedure, the DL-PRS resource processing capabilities related to the DL-RFFP positioning procedure, or any combination thereof.

[0240] Clause 54. A non-transitory computer-readable medium according to any of Clauses 50 to 53, wherein a first set of capabilities indicates a list of machine learning model formats supported by the UE, the maximum number of parameters for a network-provided machine learning model supported by the UE, one or more parameters related to the inference using a network-provided machine learning model, or any combination thereof.

[0241] Clause 55. One or more parameters related to inference using a machine learning model for network provisioning are the list of features supported by the UE, the maximum inverse fast Fourier transform (IFFT) size supported by the UE, the maximum number of antenna pairs that the UE can process, the maximum channel estimation window size supported by the UE, or any combination thereof, in the non-transitory computer-readable medium described in Clause 54.

[0242] Clause 56. The non-transitory computer-readable medium according to any of Clauses 50 to 55, further comprising computer-executable instructions that, when executed by the UE, cause the UE to receive a machine learning model for network provisioning from a location server or a network entity other than the location server.

[0243] One of ordinary 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 referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0244] Furthermore, one of ordinary 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. One of ordinary skill in the art 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.

[0245] With respect to the aspects disclosed in this specification, the various exemplary logical blocks, modules, and circuits described may be implemented or carried out using a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gates or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0246] The methods, sequences, and / or algorithms described in connection with the aspects disclosed in this specification may be embodied directly in hardware, in software modules executed by a processor, or in a combination of the two. The software modules 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, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may be present in a user terminal (e.g., a UE). Alternatively, the processor and the storage medium may be present in the user terminal as separate components.

[0247] In one or more exemplary aspects, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functionality may be stored on or transmitted via a computer-readable medium as one or more instructions or code. A computer-readable medium includes both a computer storage medium and a communication medium including any medium that facilitates transfer of a computer program from one place to another. The storage medium may be any available medium 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 software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, 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. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray (registered trademark) disc, where disk typically magnetically reproduces data and disc optically reproduces data using a laser. Combinations of the above should also be included within the scope of computer-readable media.

[0248] Note that the above disclosure shows exemplary aspects of the present disclosure, but various changes and modifications can be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps, and / or acts of the method claims according to the aspects of the present disclosure described herein need not be performed in any particular order. Further, elements of the present disclosure may be described or claimed in the singular, but the plural is contemplated unless expressly stated to the contrary.

Claims

1. A method of wireless communication performed by a user equipment (UE), comprising: transmitting, to a location server, one or more provisioning capability messages indicating at least a first set of capabilities of the UE for participating in a downlink radio frequency fingerprint (DL-RFFP) positioning procedure; receiving, from the location server, one or more positioning assistance data messages for the DL-RFFP positioning procedure based at least on the first set of capabilities.

2. The method according to claim 1, wherein the first set of capabilities is an initial set of capabilities of the UE for participating in the DL-RFFP positioning procedure.

3. The method according to claim 1, further comprising receiving, from the location server, a first capability request message requesting at least the first set of capabilities of the UE.

4. The method according to claim 3, wherein the first capability request message includes a flag, and the flag configures the UE to provide all capabilities of the UE related to the DL-RFFP positioning procedure in the one or more provisioning capability messages, or to wait for a subsequent request for specific capabilities of the UE related to the DL-RFFP positioning procedure.

5. The method according to claim 4, further comprising receiving, from the location server, a second capability request message requesting a second set of capabilities of the UE based on the flag configuring the UE to wait for a subsequent request for specific capabilities of the UE related to the DL-RFFP positioning procedure.

6. The method according to claim 1, further comprising transmitting, to a network entity other than the location server, a second provisioning capability message including a second set of capabilities of the UE for participating in the DL-RFFP positioning procedure, the second set of capabilities including capabilities different from the first set of capabilities.

7. The method according to claim 6, wherein the first set of capabilities of the UE includes a flag indicating that the UE supports DL-RFFP positioning, and the second set of capabilities of the UE includes all capabilities of the UE related to the DL-RFFP positioning procedure.

8. The method according to claim 1, wherein the one or more provisioning capability messages include a first flag indicating whether the UE can use a machine learning model provided by the network for the DL-RFFP positioning procedure.

9. The method according to claim 8, wherein the one or more provisioning capability messages include a second flag indicating how the location server can retrieve the UE's capability to use the machine learning model provided by the network.

10. A first value of the second flag indicates that the UE's capability to use the machine learning model provided by the network is included in the one or more provisioning capability messages, The method according to claim 9, wherein a second value of the second flag indicates that the UE's capability to use the machine learning model provided by the network is stored in a network entity other than the location server.

11. The first set of capabilities includes the maximum number of simultaneous machine learning positioning instances supported by the UE, the downlink positioning reference signal (DL-PRS) resource capability related to the DL-RFFP positioning procedure, the DL-PRS resource processing capability related to the DL-RFFP positioning procedure, or any combination thereof, according to the method of claim 8.

12. The first set of capabilities includes a list of machine learning model formats supported by the UE, the maximum number of parameters for the machine learning model provided by the network supported by the UE, one or more parameters related to the inference using the machine learning model provided by the network, or any combination thereof, according to the method of claim 8.

13. The one or more parameters related to the inference using the machine learning model provided by the network are a list of features supported by the UE, the maximum inverse fast Fourier transform (IFFT) size supported by the UE, the maximum number of antenna pairs that the UE can process, the maximum channel estimation window size supported by the UE, or any combination thereof, according to the method of claim 12.

14. The method according to claim 8, further comprising receiving the machine learning model for network provision from the location server or a network entity other than the location server.

15. A user equipment (UE), a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor transmits, via the at least one transceiver, one or more provisioning capability messages indicating at least a first set of capabilities of the UE for participating in a downlink radio frequency fingerprint (DL-RFFP) positioning procedure to a location server, and is configured to receive, via the at least one transceiver, one or more positioning assistance data messages for the DL-RFFP positioning procedure based at least on the first set of capabilities from the location server.

16. The UE according to claim 15, wherein the first set of capabilities is an initial set of capabilities of the UE for participating in the DL-RFFP positioning procedure.

17. The at least one processor is further configured to receive, via the at least one transceiver, a first capability request message requesting at least the first set of capabilities of the UE from the location server.

18. The first capability request message includes a flag, and the flag configures the UE to provide all capabilities of the UE related to the DL-RFFP positioning procedure in the one or more provisioning capability messages, or to wait for a subsequent request for specific capabilities of the UE related to the DL-RFFP positioning procedure.

19. The at least one processor is further configured to receive, via the at least one transceiver, a second capability request message requesting a second set of capabilities of the UE from the location server based on the flag configuring the UE to wait for a subsequent request for specific capabilities of the UE related to the DL-RFFP positioning procedure.

20. The at least one processor A second provided-capability message including a second set of the UE's capabilities for participating in the DL-RFFP positioning procedure, the second set of capabilities including capabilities different from the first set of capabilities, is further configured to be transmitted via the at least one transceiver to a network entity other than the location server. The UE according to claim 15.

21. The first set of the UE's capabilities includes a flag indicating that the UE supports DL-RFFP positioning. The UE according to claim 20, wherein the second set of the UE's capabilities includes all the capabilities of the UE related to the DL-RFFP positioning procedure.

22. The UE according to claim 15, wherein the one or more provided-capability messages include a first flag indicating whether the UE can use a network-provided machine learning model for the DL-RFFP positioning procedure.

23. The UE according to claim 22, wherein the one or more provided-capability messages include a second flag indicating how the location server can extract the UE's capabilities for using the network-provided machine learning model.

24. The first value of the second flag indicates that the UE's capabilities for using the network-provided machine learning model are included in the one or more provided-capability messages. The UE according to claim 23, wherein the second value of the second flag indicates that the UE's capabilities for using the network-provided machine learning model are stored in a network entity other than the location server.

25. The first set of capabilities is the maximum number of simultaneous machine learning positioning instances supported by the UE, the downlink positioning reference signal (DL-PRS) resource capabilities related to the DL-RFFP positioning procedure, the DL-PRS resource processing capabilities related to the DL-RFFP positioning procedure, or any combination thereof. The UE according to claim 22.

26. The first set of capabilities is a list of machine learning model formats supported by the UE, the maximum number of parameters for the network-provided machine learning model supported by the UE. One or more parameters related to the inference using the machine learning model provided by the network, or The UE according to claim 22, indicating any combination thereof. **Claim 27** The one or more parameters related to the inference using the machine learning model provided by the network are A list of features supported by the UE, The maximum inverse fast Fourier transform (IFFT) size supported by the UE, The maximum number of antenna pairs that the UE can process, The maximum channel estimation window size supported by the UE, or The UE according to claim 26, indicating any combination thereof. **Claim 28** The at least one processor is Further configured to receive the machine learning model provided by the network from the location server or a network entity other than the location server via the at least one transceiver, the UE according to claim 22. **Claim 29** A user equipment (UE) comprising Means for transmitting to a location server one or more provisioning capability messages indicating at least a first set of the UE's capabilities for participating in a downlink radio frequency fingerprint (DL-RFFP) positioning procedure; and Means for receiving from the location server one or more positioning assistance data messages for the DL-RFFP positioning procedure, based at least on the first set of capabilities. **Claim 30** The UE according to claim 29, wherein the first set of capabilities is an initial set of the UE's capabilities for participating in the DL-RFFP positioning procedure. **Claim 31** The UE according to claim 29, further comprising means for receiving from the location server a first capability request message requesting at least the first set of the UE's capabilities. **Claim 32** The UE according to claim 32, wherein the first capability request message includes a flag that configures the UE to provide all of the UE's capabilities related to the DL-RFFP positioning procedure in the one or more provisioning capability messages, or to wait for a subsequent request for specific capabilities of the UE related to the DL-RFFP positioning procedure. **Claim 33** Means for receiving, from the location server, a second capability request message requesting a second set of capabilities of the UE, based on configuring the UE with the flag to wait for subsequent requests for specific capabilities of the UE related to the DL-RFFP positioning procedure. The UE according to claim 33, further comprising:

34. Means for transmitting, to a network entity other than the location server, a second provided-capability message including a second set of capabilities of the UE for participating in the DL-RFFP positioning procedure, the second set of capabilities including capabilities different from the first set of capabilities. The UE according to claim 29, further comprising:

35. The first set of capabilities of the UE includes a flag indicating that the UE supports DL-RFFP positioning. The second set of capabilities of the UE includes all capabilities of the UE related to the DL-RFFP positioning procedure. The UE according to claim 34.

36. The one or more provided-capability messages include a first flag indicating whether the UE is capable of using a network-provided machine learning model for the DL-RFFP positioning procedure. The UE according to claim 29.

37. The one or more provided-capability messages include a second flag indicating how the location server can retrieve the capabilities of the UE for using the network-provided machine learning model. The UE according to claim 36.

38. The first value of the second flag indicates that the capabilities of the UE for using the network-provided machine learning model are included in the one or more provided-capability messages. The second value of the second flag indicates that the capabilities of the UE for using the network-provided machine learning model are stored in a network entity other than the location server. The UE according to claim 37.

39. The first set of capabilities includes The maximum number of simultaneous machine learning positioning instances supported by the UE, The downlink positioning reference signal (DL-PRS) resource capabilities related to the DL-RFFP positioning procedure, The DL-PRS resource processing capabilities related to the DL-RFFP positioning procedure, or Any combination thereof. The UE according to claim 36.

40. wherein the first set of capabilities comprises a list of machine learning model formats supported by the UE, a maximum number of parameters for the machine learning model provided by the network supported by the UE, one or more parameters related to inference using the machine learning model provided by the network, or any combination thereof, the UE according to claim 36. **Claim 41** wherein the one or more parameters related to inference using the machine learning model provided by the network comprise a list of features supported by the UE, a maximum inverse fast Fourier transform (IFFT) size supported by the UE, a maximum number of antenna pairs that the UE can process, a maximum channel estimation window size supported by the UE, or any combination thereof, the UE according to claim 40. **Claim 42** The UE according to claim 36, further comprising means for receiving the machine learning model provided by the network from the location server or a network entity other than the location server. **Claim 43** A non-transitory computer-readable storage medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to send to a location server one or more provisioning capability messages indicating at least a first set of the UE's capabilities for participating in downlink radio frequency fingerprint (DL-RFFP) positioning procedures, receive from the location server one or more positioning assistance data messages for the DL-RFFP positioning procedures based at least on the first set of capabilities. **Claim 44** The non-transitory computer-readable storage medium according to claim 43, wherein the first set of capabilities is an initial set of the UE's capabilities for participating in the DL-RFFP positioning procedures. **Claim 45** The non-transitory computer-readable storage medium according to claim 43, further comprising computer-executable instructions that, when executed by the UE, cause the UE to receive from the location server a first capability request message requesting at least the first set of the UE's capabilities. **Claim 46** The non-transitory computer-readable storage medium according to claim 45, wherein the first capability request message includes a flag, and the flag configures the UE to provide all capabilities of the UE related to the DL-RFFP positioning procedure in the one or more provided capability messages, or to wait for a subsequent request for a specific capability of the UE related to the DL-RFFP positioning procedure. **Claim 47** Further comprising computer-executable instructions that, when executed by the UE, cause the UE to Based on configuring the UE to wait for a subsequent request for a specific capability of the UE related to the DL-RFFP positioning procedure, cause the UE to receive from the location server a second capability request message requesting a second set of capabilities of the UE. The non-transitory computer-readable storage medium according to claim 46. **Claim 48** Further comprising computer-executable instructions that, when executed by the UE, cause the UE to Send a second provided capability message including a second set of capabilities of the UE for participating in the DL-RFFP positioning procedure, the second set of capabilities including capabilities different from the first set of capabilities, to a network entity other than the location server. The non-transitory computer-readable storage medium according to claim 43. **Claim 49** The first set of capabilities of the UE includes a flag indicating that the UE supports DL-RFFP positioning, The non-transitory computer-readable storage medium according to claim 48, wherein the second set of capabilities of the UE includes all capabilities of the UE related to the DL-RFFP positioning procedure. **Claim 50** The non-transitory computer-readable storage medium according to claim 43, wherein the one or more provided capability messages include a first flag indicating whether the UE can use a network-provided machine learning model for the DL-RFFP positioning procedure. **Claim 51** The non-transitory computer-readable storage medium according to claim 50, wherein the one or more provided capability messages include a second flag indicating how the location server can retrieve the capabilities of the UE for using the network-provided machine learning model. **Claim 52** The first value of the second flag indicates that the capability of the UE for using the machine learning model provided by the network is included in the one or more provisioning capability messages. The non-transitory computer-readable storage medium according to claim 51, wherein the second value of the second flag indicates that the capability of the UE for using the machine learning model provided by the network is stored in a network entity other than the location server. **Claim 53** The first set of capabilities includes the maximum number of simultaneous machine learning positioning instances supported by the UE, the downlink positioning reference signal (DL-PRS) resource capability related to the DL-RFFP positioning procedure, the DL-PRS resource processing capability related to the DL-RFFP positioning procedure, or any combination thereof. The non-transitory computer-readable storage medium according to claim 50. **Claim 54** The first set of capabilities includes a list of machine learning model formats supported by the UE, the maximum number of parameters for the machine learning model provided by the network supported by the UE, one or more parameters related to the inference using the machine learning model provided by the network, or any combination thereof. The non-transitory computer-readable storage medium according to claim 50. **Claim 55** The one or more parameters related to the inference using the machine learning model provided by the network are a list of features supported by the UE, the maximum inverse fast Fourier transform (IFFT) size supported by the UE, the maximum number of antenna pairs that the UE can process, the maximum channel estimation window size supported by the UE, or any combination thereof. The non-transitory computer-readable storage medium according to claim 54. **Claim 56** Further comprising computer-executable instructions, which when executed by the UE, cause the UE to receive the machine learning model provided by the network from the location server or a network entity other than the location server. The non-transitory computer-readable storage medium according to claim 50.

Images