Location model failure detection

Abstract

In an aspect, a method of wireless communication performed by a user equipment (UE) includes determining that a positioning model error instance has occurred during a positioning opportunity based on: 1) a positioning uncertainty associated with a first positioning estimate satisfies a positioning uncertainty error criterion, the first positioning estimate is obtained by applying a first positioning model to radio frequency fingerprint (RFFP) measurements during a positioning opportunity, 2) a positioning mismatch between the first positioning estimate of the UE and a second positioning estimate of the UE satisfies a positioning mismatch error criterion, the second positioning estimate of the UE is obtained during the positioning opportunity by performing a positioning technique that does not use the first positioning model, or 3) any combination thereof; and determining that the first positioning model has failed based on the number of positioning model error instances satisfying a positioning model failure criterion.

Description

Technical Field

[0001]

[0013] Generally speaking, aspects of the present disclosure relate to wireless communications. Background Art

[0002] Wireless communication systems have evolved over several generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including 2.5G and 2.75G networks during the transition period), third generation (3G) high speed data, wireless service with Internet capabilities, and fourth generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). There are many different types of wireless communication systems in use today, including cellular and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog Advanced Mobile Phone System (AMPS) and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile Communications (GSM), etc.

[0003] The fifth generation (5G) wireless standard, referred to as New Radio (NR), enables higher data transfer speeds, a greater number of connections, and better coverage, among other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on 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, along with the use of higher frequency bands, advances in PRS procedures and technologies, and high-density deployments for 5G enable highly accurate 5G-based positioning. Summary of the invention

[0004] A simplified overview of one or more aspects disclosed herein is given below. Therefore, the following overview should not be considered an exhaustive review of all expected aspects, and the following overview should neither be considered to identify key or extremely important elements related to all expected aspects, nor should it be considered to depict the scope associated with any particular aspect. Accordingly, the following overview has the sole purpose of presenting certain concepts related to one or more aspects involving the mechanisms disclosed herein in a simplified form as a prelude to the specific embodiments given below.

[0005] In one aspect, a method of wireless communication performed by a user equipment (UE) includes: determining that a positioning model error instance has occurred during a positioning opportunity based on: 1) a positioning uncertainty associated with a first positioning estimate satisfies a positioning uncertainty error criterion, wherein the first positioning estimate is obtained during the positioning opportunity by applying a first positioning model to a radio frequency fingerprint (RFFP) measurement result, 2) a positioning mismatch between the UE's first positioning estimate and the UE's second positioning estimate satisfies a positioning mismatch error criterion, wherein the UE's second positioning estimate is obtained during the positioning opportunity by performing a positioning technique that does not use the first positioning model, or 3) any combination thereof; and determining that the first positioning model has failed based on the number of positioning model error instances satisfying a positioning model failure criterion.

[0006] In one aspect, a user equipment (UE) includes a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determine that a positioning model error instance has occurred during a positioning opportunity based on: 1) a positioning uncertainty associated with a first positioning estimate satisfies a positioning uncertainty error criterion, wherein the first positioning estimate is obtained during the positioning opportunity by applying a first positioning model to a radio frequency fingerprint (RFFP) measurement result, 2) a positioning mismatch between the first positioning estimate of the UE and a second positioning estimate of the UE satisfies a positioning mismatch error criterion, wherein the second positioning estimate of the UE is obtained during the positioning opportunity by performing a positioning technique that does not use the first positioning model, or 3) any combination thereof; and determine that the first positioning model has failed based on the number of positioning model error instances satisfying a positioning model failure criterion.

[0007] In one aspect, a user equipment (UE) includes a unit for determining that a positioning model error instance has occurred during a positioning opportunity based on: 1) a positioning uncertainty associated with a first positioning estimate satisfies a positioning uncertainty error criterion, wherein the first positioning estimate is obtained during the positioning opportunity by applying a first positioning model to a radio frequency fingerprint (RFFP) measurement result, 2) a positioning mismatch between the UE's first positioning estimate and a second positioning estimate of the UE satisfies a positioning mismatch error criterion, wherein the second positioning estimate of the UE is obtained during the positioning opportunity by performing a positioning technique that does not use the first positioning model, or 3) any combination thereof; and a unit for determining that the first positioning model has failed based on the number of positioning model error instances satisfying the positioning model failure criterion.

[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: determine that a positioning model error instance has occurred during a positioning opportunity based on: 1) a positioning uncertainty associated with a first positioning estimate satisfies a positioning uncertainty error criterion, wherein the first positioning estimate is obtained during the positioning opportunity by applying a first positioning model to a radio frequency fingerprint (RFFP) measurement result, 2) a positioning mismatch between the UE's first positioning estimate and the UE's second positioning estimate satisfies a positioning mismatch error criterion, wherein the UE's second positioning estimate is obtained during the positioning opportunity by performing a positioning technique that does not use the first positioning model, or 3) any combination thereof; and determine that the first positioning model has failed based on a number of positioning model error instances satisfying a positioning model failure criterion.

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

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

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

[0012] Figure 2A , Figure 2B and Figure 2C Example wireless network structures are shown in accordance with aspects of the present disclosure.

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

[0014] Figure 4 Examples of various positioning methods supported in New Radio (NR) according to aspects of the present disclosure are shown.

[0015] Figure 5 is a diagram illustrating an example frame structure in accordance with aspects of the present disclosure.

[0016] Figure 6 is a schematic diagram illustrating radio frequency (RF) channel estimation in accordance with aspects of the present disclosure.

[0017] Figure 7An example neural network in accordance with aspects of the present disclosure is shown.

[0018] Figure 8 is a schematic diagram illustrating the use of a machine learning (ML) model for RF fingerprint (RFFP) based positioning in accordance with aspects of the present disclosure.

[0019] Fig. 9 is a schematic diagram illustrating an inference period for UE-based downlink RFFP (DL-RFFP) positioning according to aspects of the present disclosure.

[0020] Fig.10 An example call flow for UE-based DL-RFFP positioning is shown in accordance with aspects of the present disclosure.

[0021] Fig.11 is a timing diagram illustrating an example of positioning model failure detection based on a total number of positioning model error instances in accordance with aspects of the present disclosure.

[0022] Fig.12 is a timing diagram illustrating an example of positioning model failure detection based on a total number of positioning model error instances occurring within a specified duration in accordance with aspects of the present disclosure.

[0023] Fig.13 is a timing diagram illustrating an example of positioning model failure detection based on a total number of positioning model error instances occurring within a specified duration in accordance with aspects of the present disclosure.

[0024] Fig.14 An example method of wireless communication performed by a UE according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

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

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

[0027] Those skilled in the art will recognize 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 mentioned throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, etc.

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

[0029] As used herein, unless otherwise noted, the terms "user equipment" (UE) and "base station" are not intended to be specific to or otherwise limited to any particular radio access technology (RAT). In general, a UE may be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a consumer asset location device, a wearable device (e.g., a smart watch, glasses, augmented reality (AR) / virtual reality (VR) headsets, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate on a wireless communication network. A UE may be mobile or may be fixed (e.g., at certain times) and may communicate with a radio access network (RAN). As used herein, the term "UE" may be interchangeably referred to as an "access terminal" or "AT", "client device", "wireless device", "subscriber equipment", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile device", "mobile terminal", "mobile station" or variants thereof. In general, a UE is able to communicate with a core network via a RAN, and the core network is able to connect the UE to external networks such as the Internet and to other UEs. Of course, other mechanisms for the UE to connect to the core network and / or the Internet are also possible, such as on a wired access network, a wireless local area network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.), etc.

[0030] The base station may operate according to one of several RATs in communication with the UE, depending on the network in which it is deployed, and the base station may be alternatively referred to as an access point (AP), a network node, a NodeB, an evolved NodeB (eNB), a next generation eNB (ng-eNB), a new radio (NR) NodeB (also referred to as a gNB or gNodeB), etc. The base station may be primarily 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 pure edge node signaling functions, while in other systems, it 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 send a signal to the UE is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term traffic channel (TCH) may refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0031] The term "base station" may refer to a single physical transmit receive point (TRP), or to multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common resource via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs may be a serving base station that receives measurement reports from the UE and a neighbor base station whose reference radio frequency (RF) signal the UE is measuring. Because, as used herein, a TRP is the point at which wireless signals are transmitted and received from its base station, references to transmissions from, or receptions at, a base station will be understood to refer to the specific TRP of a base station.

[0032] In some implementations of supporting positioning of a UE, a base station may not support wireless access by the UE (e.g., may not support data, voice, and / or signaling connections for the UE), but may instead send a reference signal to the UE to be measured by the UE, and / or may receive and measure signals 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 position measurement unit (e.g., when receiving and measuring a signal from the UE).

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

[0034] According to various aspects of the present disclosure, Figure 1An exemplary wireless communication system 100 is shown. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled "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 an aspect, the macrocell base stations may include eNBs and / or ng-eNBs (where the wireless communication system 100 corresponds to an LTE network) or gNBs (where the wireless communication system 100 corresponds to an NR network) or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0035] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) via a backhaul link 122, and interface with one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) via the core network 170. 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 via another path, such as via an application server (not shown), via another network (such as via a wireless local area network (WLAN) access point (AP) (e.g., the AP 150 described below)), etc. For signaling purposes, communications between UE 104 and location server 172 may be represented as an indirect connection (e.g., through core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with intervening nodes (if any) omitted from the signaling diagrams for clarity.

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

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

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

[0039] The communication link 120 between the base station 102 and the UE 104 may include an uplink (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also referred to as a 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 over one or more carrier frequencies. The allocation of carriers may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated for the downlink than for the uplink).

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

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

[0042] The wireless communication system 100 may also include a millimeter wave (mmW) base station 180 that communicates with the UE 182, and the mmW base station 180 may operate in mmW frequencies and / or near mmW frequencies. Extremely high frequency (EHF) is a portion of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. Radio waves in this frequency band may be referred to as millimeter waves. Near mmW may extend downward to a frequency of 3 GHz with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz and is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have high path loss and a relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (sending and / or receiving) on ​​the mmW communication link 184 to compensate for extremely high path loss and short range. Further, it will be appreciated that in an alternative configuration, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be appreciated that the foregoing description is merely exemplary and should not be construed as limiting the various aspects disclosed herein.

[0043] Transmit beamforming is a technique for focusing RF signals in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal to the (multiple) receiving devices. In order to change the direction of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that broadcast the RF signal. For example, a network node can use an array of antennas (called a "phased array" or "antenna array") that creates a beam of RF waves that can be "guided" to points in different directions without actually moving the antenna. Specifically, the RF current from the transmitter is fed to individual antennas with the correct phase relationship so that the radio waves from the individual antennas are added together to increase radiation in the desired direction and offset in the undesired direction to suppress radiation.

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

[0045] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, the receiver may increase a gain setting and / or adjust a phase setting of an antenna array in a particular direction to amplify (e.g., to increase the gain level of) an RF signal received from that direction. Thus, when a receiver is said to be beamforming in a certain direction, this means that the beam gain in that direction is high relative to the beam gain along other directions, or that the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), etc.) of the RF signal received from that direction.

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

[0047] It is to be noted that a "downlink" beam can be a transmit beam or a receive beam, depending on the entity forming it. For example, if the base station is forming a downlink beam for sending a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, it is a receive beam for receiving a downlink reference signal. Similarly, an "uplink" beam can be a transmit beam or a receive beam, depending on the entity forming it. For example, if the base station is forming an uplink beam, it is an uplink receive beam, and if the UE is forming an uplink beam, it is an uplink transmit beam.

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

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

[0050] In view of the above, unless otherwise specifically stated, it should be understood that the term "sub-6 GHz" and the like, if used herein, can broadly refer to frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. Further, unless otherwise specifically stated, it should be understood that the term "millimeter wave" and the like, if used herein, can broadly refer to frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0051] In a multi-carrier system (such as 5G), one of the carrier frequencies is referred to as a "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are referred to as "secondary carriers" or "secondary serving cells" or "SCells". In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) utilized by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels, and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2), which can be configured once an RRC connection is established between the UE 104 and the anchor carrier and can be used to provide additional radio resources. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, there may be no UE-specific signaling information and signals in the secondary carrier, because both the primary uplink carrier and the primary downlink carrier are typically UE-specific. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. This is also true for the uplink primary carrier. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done to, for example, balance the load on different carriers. Since a "serving cell" (whether a PCell or an SCell) corresponds to a carrier frequency / component carrier on which a base station is communicating, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. may be used interchangeably.

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

[0053] The wireless communication system 100 may also include a UE 164, which may communicate with the macrocell base station 102 over the communication link 120 and / or communicate with the mmW base station 180 over the mmW communication link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

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

[0055] In one aspect, the sidelink 160 can operate on a wireless communication medium of interest, which can be shared with other wireless communications between other vehicles and / or infrastructure access points and other RATs. A "medium" can consist of one or more time, frequency, and / or spatial communication resources (e.g., including one or more channels across one or more carriers) associated with wireless communications between one or more transmitter / receiver pairs. In one aspect, the medium of interest can correspond to at least a portion of an unlicensed band shared among various RATs. Although different licensed bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) of the United States), these systems (particularly those employing small cell access points) have recently expanded operations into unlicensed bands (such as the unlicensed national information infrastructure (U-NII) bands used by wireless local area network (WLAN) technologies, most notably IEEE 802.11x WLAN technologies, commonly referred to as "Wi-Fi"). Example systems of this type include different variations of CDMA systems, TDMA systems, FDMA systems, Orthogonal FDMA (OFDMA) systems, Single-Carrier FDMA (SC-FDMA) systems, and the like.

[0056] Note that although Figure 1 Only two of the UEs are shown as SL-UEs (i.e., UEs 164 and 182), but any of the UEs shown may be SL-UEs. Further, although only UE 182 is described as being capable of beamforming, any of the UEs shown (including UE 164) may be capable of beamforming. In the case where the SL-UEs are capable of beamforming, they may beamform toward each other (i.e., toward other SL UEs), toward other UEs (e.g., UE 104), toward a base station (e.g., base station 102, 180, cell 102', access point 150), etc. Therefore, in some cases, UEs 164 and 182 may utilize beamforming on the sidelink 160.

[0057] exist Figure 1 In the example of FIG. 1 , any UE among the UEs shown (for simplicity, in FIG. 1 ) Figure 1 104) can be accessed from one or more Earth orbiting spacecraft Space Vehicles(SV) 112 (e.g., satellite) receives signal 124. In one aspect, SV 112 can be part of a satellite positioning system, which UE 104 can use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SV 112) positioned so that receivers (e.g., UE 104) can determine their positions on or above the earth based at least in part on positioning signals (e.g., signal 124) received from the transmitters. Such transmitters typically send signals marked with a repetitive pseudo-random noise (PN) code of a set number of chips. Although typically located in SV 112, the transmitters can sometimes be located in ground-based control stations, base stations 102, and / or other UEs 104. UE 104 may include one or more dedicated receivers specifically designed to receive signal 124 for deriving geographic location information from SV 112.

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

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

[0060] The wireless communication system 100 may also include one or more UEs (such as UE 190) indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “sidelinks”). Figure 1 In the example of FIG. 1 , UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of base stations 102 (e.g., through D2D P2P link 192, UE 190 can indirectly obtain cellular connectivity) and a D2D P2P link 194 with WLAN STA 152 connected to WLAN AP 150 (through D2D P2P link 194, UE 190 can indirectly obtain WLAN-based Internet connectivity). In an example, D2D P2P links 192 and 194 can be D2D links using any well-known D2D RAT (such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), etc.) to support.

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

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

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

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

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

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

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

[0068] The user plane interface 263 and the control plane interface 265 connect the 5GC 260 (and specifically, the UPF 262 and the AMF 264) to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220, respectively. The interface between the gNB(s) 222 and / or ng-eNB(s) 224 and the AMF 264 is referred to as the "N2" interface, and the interface between the gNB(s) 222 and / or ng-eNB(s) 224 and the UPF 262 is referred to as the "N3" interface. The gNB(s) 222 and / or ng-eNB(s) 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223 referred to as an "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 referred to as a "Uu" interface.

[0069] The functions of the gNB 222 may be divided between a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DU) 228, and one or more gNB radio units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions for transmitting user data, mobility control, radio access network sharing, positioning, session management, etc., except for those functions that are specifically assigned to (multiple) gNB-DUs 228. More specifically, the gNB-CU 226 typically hosts the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that typically hosts the radio link control (RLC) and medium access control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 may support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and one or more gNB-DUs 228 is referred to as the "F1" interface. The physical (PHY) layer functions of the gNB 222 are typically hosted by one or more independent gNB-RUs 229 that perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is referred to as the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC, SDAP, and PDCP layers, communicates with the gNB-DU 228 via the RLC and MAC layers, and communicates with the gNB-RU 229 via the PHY layer.

[0070] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways with various components or parts. In a 5G NR system or network, a network node, a network entity, a mobile element of a network, a RAN node, a core network node, a network element or a network device (such as a base station or one or more units (or one or more components) performing base station functions) can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), a NR base station, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station.

[0071] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can be configured to utilize a protocol stack physically or logically distributed among two or more units (such as one or more central or centralized units (CU), one or more distributed units (DU), or one or more radio units (RU)). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be distributed geographically or virtually throughout 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)).

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

[0073] Figure 2C An example disaggregated base station architecture 250 is shown in accordance with aspects of the present disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CUs 226), which may communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with a core network 267 through one or more disaggregated base station units (e.g., near real-time (near-RT) RAN intelligent controller (RIC) 259 via an E2 link, or a non-real-time (non-RT) RIC 257 associated with a service management and orchestration (SMO) framework 255, or both). The CU 280 may communicate with one or more distributed units (DUs) 285 (e.g., gNB-DUs 228) via respective midhaul links such as F1 interfaces. The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective fronthaul links. The RUs 287 may communicate with respective UEs 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 may be served by multiple RUs 287 simultaneously.

[0074] Each of the units (i.e., CU 280, DU 285, RU 287, and near-RT RIC 259, non-RT RIC 257, and SMO framework 255) may include one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. 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 a transmission medium. For example, a unit may include a wired interface configured to receive a signal on a wired transmission medium or to send a signal to one or more of the other units. In addition, a unit may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver), which is configured to receive a signal on a wireless transmission medium or to send a signal to one or more of the other units, or both.

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

[0076] DU 285 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RU 287. In some aspects, DU 285 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split such as defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 285 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to transmit signals to other layers (and modules) hosted by DU 285 or control functions hosted by CU 280.

[0077] The lower layer functions may be implemented by one or more RUs 287. In some deployments, based at least in part on the functional split (such as the lower layer functional split), the RU 287 controlled by the DU 285 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.), or both. In such an architecture, (multiple) RUs 287 may be implemented to handle over-the-air (OTA) communications with one or more UEs 204. In some implementations, real-time and non-real-time aspects of control and user plane communications with (multiple) RUs 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration may enable (multiple) DUs 285 and CUs 280 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

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

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

[0080] In some implementations, in order to generate the AI / ML model to be deployed in the near-RT RIC 259, the non-RT RIC 257 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 259 and may be received from a non-network data source or from a network function at the SMO framework 255 or the non-RT RIC 257. In some examples, the non-RT RIC 257 or the near-RT RIC 259 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 257 may monitor long-term trends and patterns for performance and perform corrective actions using the AI / ML model through the SMO framework 255 (e.g., via reconfiguration of O1) or via the creation of a RAN management policy (such as an A1 policy).

[0081] Figure 3A , Figure 3B and Figure 3C 302 (which may correspond to any of the UEs described herein), base station 304 (which may correspond to any of the base stations described herein), and 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 Figure 2A and Figure 2B 20 and / or 5GC 210 / 260 infrastructure, such as a dedicated network, to support the operations described herein (represented by corresponding blocks). It will be understood that these components may be implemented in different types of devices in different implementations (e.g., in an ASIC, in a system on a chip (SoC), etc.). The components shown may also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described to provide similar functionality. In addition, 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.

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

[0083] At least in some cases, the UE 302 and the base station 304 each further include one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide for communicating over the wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, Zigbee Z-Wave The short-range wireless transceivers 320 and 360 are units (e.g., units for sending, units for receiving, units for measuring, units for tuning, units for avoiding sending, etc.) for communicating with other network nodes (such as other UEs, access points, base stations, etc.) such as PC5, dedicated short-range communication (DSRC), wireless access for vehicular environments (WAVE), near field communication (NFC), ultra-wideband (UWB), etc.). The short-range wireless transceivers 320 and 360 can be configured differently to send and encode signals 328 and 368 (e.g., messages, indications, information, etc.) respectively according to a specified RAT and conversely to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.) respectively according to a specified RAT. Specifically, the short-range wireless transceivers 320 and 360 respectively include one or more transmitters 324 and 364 for sending and encoding signals 328 and 368, respectively, and one or more receivers 322 and 322 for receiving and decoding signals 328 and 368, respectively. As a specific example, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Transceiver, and / or transceiver, NFC transceiver, UWB transceiver, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceiver.

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

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

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

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

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

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

[0090] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide a means for sensing or detecting motion and / or directional information independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. By way of example, sensor(s) 344 may include an accelerometer (e.g., a micro-electromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of motion detection sensor. In addition, sensor(s) 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, 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.

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

[0092] Referring to the one or more processors 384 in more detail, in a downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functions for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. One or more processors 384 may provide RRC layer functions associated with: broadcasting of system information (e.g., master information block (MIB), system information block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with: header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and switching support functions; RLC layer functions associated with: transmission of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0093] The transmitter 354 and the receiver 352 may implement layer-1 (L1) functions associated with various signal processing functions. Layer-1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) encoding / 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 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel for carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator may be used to determine the coding and modulation schemes, as well as for spatial processing. The channel estimate may be derived from a reference signal and / or channel condition feedback sent by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier for transmission using a respective spatial stream.

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

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

[0096] Similar to the functions described in conjunction with downlink transmissions performed by the base station 304, one or more processors 332 provide RRC layer functions associated with: system information (e.g., MIB, SIB) capture, RRC connection, and measurement reporting; PDCP layer functions associated with: header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with: transmission of upper layer PDUs, error correction through 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 through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

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

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

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

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

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

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

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

[0104] NR supports a number of cellular network-based positioning techniques, including downlink-based, uplink-based, and downlink and uplink-based positioning methods. Downlink-based positioning methods include Observed Time Difference of Arrival (OTDOA) in LTE, Downlink Time Difference of Arrival (DL-TDOA) in NR, and Downlink Angle of Detection (DL-AoD) in NR. Figure 4Examples of various positioning methods according to various aspects of the present disclosure are shown. In the OTDOA or DL-TDOA positioning process shown by scenario 410, the UE measures the difference between the arrival time (ToA) of the reference signal (e.g., positioning reference signal (PRS)) received from the base station pair (referred to as the reference signal time difference (RSTD) or arrival time difference (TDOA) measurement results), and reports them to the positioning entity. More specifically, the UE receives identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in the auxiliary data. The UE then measures the RSTD between the reference base station and each non-reference base station in the non-reference base stations. Based on the known positions of the base stations involved and the RSTD measurement results, a positioning entity (e.g., a UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the position of the UE.

[0105] For DL-AoD positioning as shown by scenario 420, the positioning entity uses measurement reports of received signal strength measurements of multiple downlink transmit beams from the UE to determine the angle(s) between the UE and the transmitting base station(s). The positioning entity may then estimate the position of the UE based on the determined angle(s) and the known positions of the transmitting base station(s).

[0106] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle of arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but UL-TDOA is based on uplink reference signals (e.g., sounding reference signals (SRS)) sent by the UE to multiple base stations. Specifically, the UE sends one or more uplink reference signals measured by a reference base station and multiple non-reference base stations. Each base station then reports the reception time of (multiple) reference signals (called relative time of arrival (RTOA)) to a positioning entity (e.g., a location server) that knows the location and relative timing of the base stations involved. Based on the receive-to-receive (Rx-Rx) time difference between the reported RTOA of the reference base station and the reported RTOA of each non-reference base station, the known location of the base stations, and their known timing offsets, the positioning entity can use TDOA to estimate the position of the UE.

[0107] For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. The positioning entity uses the signal strength measurements and the angles of the receive beams to determine the angles between the UE and the base station. Based on the determined angles and the known positions of the base stations, the positioning entity can then estimate the position of the UE.

[0108] 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 process, a first entity (e.g., a base station or UE) sends a first RTT-related signal (e.g., a PRS or SRS) to a second entity (e.g., a UE or a base station), and the second entity sends a second RTT-related signal (e.g., an SRS or PRS) back to the first entity. Each entity measures the time difference between the arrival time (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. This time difference is called the received-transmitted (Rx-Tx) time difference. The Rx-Tx time difference measurement result can be made or adjusted to include only the time difference between the nearest time slot boundary for the received signal and the nearest time slot boundary for the transmitted signal. The two entities may then send their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round trip propagation time (i.e., RTT) between the two entities based on the two Rx-Tx time difference measurements (e.g., as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity may send its Rx-Tx time difference measurements to the other entity, which then calculates the RTT. The distance between the two entities may be determined based on the RTT and a known signal speed (e.g., the speed of light). For multi-RTT positioning as shown by scenario 430, a first entity (e.g., a UE or base station) performs an RTT positioning process with multiple second entities (e.g., multiple base stations or UEs) so that the location of the first entity can be determined based on the distance to the second entity and the known location of the second entity (e.g., using multi-point positioning). RTT and multi-RTT methods may be combined with other positioning techniques such as UL-AoA and DL-AoD to improve location accuracy as shown by scenario 440.

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

[0110] To assist the positioning operation, the location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE. For example, the assistance data may include an identifier of the base station (or cell / TRP of the base station) from which the reference signal is measured, reference signal configuration parameters (e.g., the number of consecutive time slots including PRS, the period of consecutive time 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 directly derived from the base station itself (e.g., in a periodically broadcast overhead message, etc.). In some cases, the UE may be able to detect neighboring network nodes on its own without using assistance data.

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

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

[0113] Various frame structures may be used to support downlink and uplink transmissions between network nodes (eg, base stations and UEs). Figure 5 5 is a diagram 500 illustrating an example frame structure according to aspects 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.

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

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

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

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

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

[0119] The set of resource elements (REs) used for transmission of PRS is called "PRS resource". The set of resource elements may span multiple PRBs in the frequency domain and "N" (such as 1 or more) (multiple) consecutive symbols 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.

[0120] The transmission of PRS resources 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, for comb size "N", the PRS is sent in every Nth subcarrier of the symbol of the PRB. For example, for comb-4, for each symbol of the PRS resource configuration, the REs corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) 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 An example PRS resource configuration for Comb-4 (which spans four symbols) is shown. That is, the positions of the shaded REs (labeled "R") indicate a Comb-4 PRS resource configuration.

[0121] Currently, DL-PRS resources can span 2, 4, 6, or 12 consecutive symbols within a slot with a full frequency domain staggered pattern. DL-PRS resources can be configured in any higher layer configured downlink or flexible (FL) symbols in a slot. There can be a constant energy per resource element (EPRE) for all REs of a given DL-PRS resource. The following are the frequency offsets from symbol to symbol over 2, 4, 6, and 12 symbols for comb sizes 2, 4, 6, and 12. 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}; 4-symbol Comb-4: {0,2,1,3} (as in Figure 5 in the example); 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}.

[0122] A "PRS resource set" is a set of PRS resources used for transmission of a PRS signal, wherein each PRS resource has a PRS resource ID, and in addition, the PRS resources in the 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 a TRP ID). In addition, the PRS resources in the PRS resource set have the same period, common muting pattern configuration, and the same repetition factor (such as "PRS-ResourceRepetitionFactor") across time slots. The period is the time from the first group repetition of the first PRS resource of the first PRS instance to the same first repetition of the same first PRS resource of the next PRS instance. The period may have a length selected from 2^μ*{4,5,8,10,16,20,32,40,64,80,160,320,640,1280,2560,5120,10240} time slots, where μ=0, 1, 2, 3. The repetition factor can have a length selected from {1, 2, 4, 6, 8, 16, 32} time slots.

[0123] A PRS resource ID in a PRS resource set is associated with a single beam (or beam ID) transmitted from a single TRP (where a TRP may transmit one or more beams). That is, each PRS resource in a PRS resource set may be transmitted on a different beam, and as such, a "PRS resource" or simply "resource" may also be referred to as a "beam". Note that this does not have any implication as to whether the UE is aware of the TRP and the beam on which the PRS is transmitted.

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

[0125] A "positioning frequency layer" (also referred to simply as a "frequency layer") is a set of one or more PRS resource sets spanning one or more TRPs with the same values ​​for certain parameters. Specifically, the set of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning that all digital schemes supported for the physical downlink shared channel (PDSCH) are also supported for PRS), the same point A, the same value of the 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" stands for "absolute radio frequency channel number") and is an identifier / code that specifies a pair of physical radio channels for transmission and reception. The downlink PRS bandwidth can have a granularity of four PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs. Currently, up to four frequency layers have been defined, and up to two PRS resource sets can be configured per TRP per frequency layer.

[0126] The concept of frequency layer is a bit like the concept of component carrier and bandwidth part (BWP), but the difference is that component carrier and BWP are used by one base station (or macro cell base station and small cell base station) to send data channels, while frequency layer is used by several (usually three or more) base stations to send PRS. When the UE sends its positioning capabilities to the network (such as during an LTE Positioning Protocol (LPP) session), the UE can indicate the number of frequency layers it can support. For example, the UE can indicate whether it can support one or four positioning frequency layers.

[0127] 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" may also refer to any type of reference signal that may be used for positioning, such as but not limited to TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, PRS as defined in LTE and NR, etc. In addition, unless otherwise indicated by the context, the terms "positioning reference signal" and "PRS" may refer to downlink, uplink, or sidelink positioning reference signals. If further distinction is needed between the types of PRS, the downlink positioning reference signal may be referred to as "DL-PRS", the uplink positioning reference signal (e.g., SRS, PTRS used for positioning) may be referred to as "UL-PRS", and the sidelink positioning reference signal may be referred to as "SL-PRS". In addition, for signals (e.g., DMRS) that may be sent in the downlink, uplink, and / or sidelink, the signals may be prefixed with "DL", "UL", or "SL" to distinguish the direction. For example, "UL-DMRS" is different from "DL-DMRS".

[0128] Figure 6 600 is a graph representing a channel estimate of a multipath channel between a receiver device (e.g., any one of the UEs or base stations described herein) and a transmitter device (e.g., any other of the UEs or base stations described herein) according to aspects of the present disclosure. The channel estimate represents the strength of a radio frequency (RF) signal (e.g., a PRS) received through a 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 strength (e.g., decibels). Note that a multipath channel is a channel between a transmitter and a receiver over which an RF signal follows multiple paths or multipaths due to transmission of the RF signal on multiple beams and / or propagation characteristics of the RF signal (e.g., reflection, refraction, etc.).

[0129] exist Figure 6In the example of , the receiver detects / measures multiple (four) clusters of channel taps. Each channel tap represents the multipath followed by the RF signal between the transmitter and the receiver. That is, the channel taps represent the arrival of the RF signal on the multipath. Each cluster of channel taps indicates that the corresponding multipath follows substantially the same path. Different clusters may exist because the RF signal is sent on different transmit beams (and therefore at different angles), or because of the propagation characteristics of the RF signal (e.g., potentially following different paths due to reflections), or both.

[0130] All clusters of channel taps for a given RF signal represent the multipath channel (or simply channel) between the transmitter and the receiver. Figure 6 Under the channel shown, the receiver receives a first cluster of two RF signals at the channel taps at time T1, a second cluster of five RF signals at the channel taps at time T2, a third cluster of five RF signals at the channel taps at time T3, and a fourth cluster of four RF signals at the channel taps at time T4. Figure 6 In the example of , because the first cluster of RF signals at time T1 arrives first, it is assumed to correspond to RF signals sent on a transmit beam aligned with line of sight (LOS) or the shortest path. The third cluster at time T3 includes the strongest RF signals and may correspond to, for example, RF signals sent on a transmit beam aligned with a non-line of sight (NLOS) path. Note that although Figure 6 Clusters of two to five channel taps are shown, but as will be understood, a cluster may have more or fewer channel taps than the number of channel taps shown.

[0131] Machine learning (ML) or other techniques may be used to generate models that may be used to facilitate various aspects associated with processing of data. One specific application of ML relates to the generation of positioning models for processing reference signals (e.g., PRS) used for positioning, such as feature extraction, reporting of reference signal measurements (e.g., selecting which extracted features to report), etc.

[0132] ML models are generally classified as supervised or unsupervised. Supervised models can be further subclassified as regression models or classification models. Supervised learning involves learning a function that maps inputs to outputs based on example input-output pairs. For example, given a training data set 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 tries to find the line that best fits the data. Extensions of linear regression include multiple linear regression (e.g., finding the plane of best fit) and polynomial regression (e.g., finding the curve of best fit).

[0133] Another example of an ML model is a decision tree model. In a decision tree model, a tree structure is defined using a number of nodes. Decisions are made to move from a root node at the top of the decision tree to leaf nodes (i.e., nodes that have no further children) at the bottom of the decision tree. Typically, a greater number of nodes in a decision tree model is associated with a higher decision accuracy.

[0134] Another example of an ML model is a decision forest. Random forest is an ensemble learning technique built off of decision trees. Random forest involves creating multiple decision trees using a bootstrapped dataset 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 predictions of each decision tree. By relying on a "majority wins" model, the risk of errors from a single tree can be reduced.

[0135] Another example of an ML 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 going through the network of equations. In other words, a neural network takes in a vector of inputs and returns a vector of outputs.

[0136] Figure 7 An example neural network 700 is shown in accordance with aspects of the present disclosure. The neural network 700 includes an input layer "i" that receives "n" input(s) (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" output(s) (labeled "output 1" and "output m"). The number of inputs "n", hidden layers "h", and outputs "m" can be the same or different. In some designs, the hidden layer "h" can include linear functions (multiple) and / or activation functions (multiple) that the nodes of each successive hidden layer (shown as circles) process from the nodes of the previous hidden layer.

[0137] 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 probability of a limited number of results (typically two). In essence, the logistic equation is created in a way that the output value can only be between "0" and "1". Another example of a classification model is a support vector machine. For example, for two classes of data, a support vector machine will find a hyperplane or boundary that maximizes the margin between the two classes of data. 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, which is 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.

[0138] Unlike supervised learning, unsupervised learning is used to make inferences and find patterns from input data without reference to labeled results. Two examples of unsupervised learning models include clustering and dimensionality reduction.

[0139] Clustering is an unsupervised technique that involves grouping or clustering 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. Simply put, dimensionality reduction is the process of reducing the dimensionality of a feature set (or more simply, reducing the number of features). Most dimensionality reduction techniques can be classified as feature elimination 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., three dimensions) into a smaller space (e.g., two dimensions). This results in lower dimensional data (e.g., two dimensions instead of three dimensions) while maintaining all the original variables in the model.

[0140] Regardless of which ML model is used, at a high level, the ML module (e.g., implemented by a processing system such as processor 332, 384, or 394) can be 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 candidate locations or a set of likely candidate locations for various target UEs), thereby enabling the determination of the same output data set when similar input data is later presented (e.g., from other target UEs at the same or similar locations).

[0141] NR supports RF fingerprint (RFFP) based positioning, a type of positioning and localization technology that uses RFFP captured by a mobile device to determine the location of a mobile device. RFFP can be a histogram of received signal strength indicator (RSSI), CER, CIR, PDP, or channel frequency response (CFR). 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 position of (multiple) RFFPs measured by a mobile device (e.g., UE) and (multiple) transmitters associated with the measured (multiple) RFFPs (i.e., transmitters that send RF signals measured by the mobile device to determine (multiple) RFFPs) can be used to determine (e.g., triangulate) the position of the mobile device.

[0142] Compared with the classical positioning scheme, model-based positioning techniques have been shown to provide superior positioning performance. In ML RFFP-based positioning, the ML model (e.g., neural network 700) takes the RFFP of the downlink reference signal (e.g., PRS) as input, and outputs the positioning measurement results (e.g., ToA, RSTD) or mobile device position corresponding to the input RFFP. The ML model (e.g., neural network 700) is trained using the "ground truth" (i.e., known) positioning measurement results or mobile device positions as the reference (i.e., expected) output of the training set of RFFP.

[0143] For example, an ML model may be trained to determine RSTD measurements for a TRP pair based on the RFFP of the PRS sent by the TRP. The reference output for training such a model would be the correct (i.e., ground truth) RSTD measurements for the location of the mobile device at the time the mobile device obtains the RFFP measurements of the PRS. The network (e.g., a location server) may determine the RSTD that would be expected for the TRP pair based on the known location of the mobile device and the known location of the (measured) TRP involved. The known location of the mobile device may be determined based on multiple reported RSTD measurements and / or any other measurements reported by the mobile device (e.g., GPS measurements).

[0144] Figure 8 8 is a schematic diagram 800 illustrating the use of an ML model for RFFP-based positioning in accordance with aspects of the present disclosure. Figure 8In the example of FIG. 1 , during the “offline” phase, RFFPs (e.g., CER(s) / CIR(s) / CFR(s)) captured by the mobile device are stored in a database. The database may be located at the mobile device or a network entity (e.g., a location server), and each RFFP may include a plurality of RFFPs transmitted by one or more transmitters (in Figure 8 , the measurement results of RF signals (or channels or links) transmitted by base stations 1 to N (i.e., "BS1" to "BS N") are shown. For UE-based downlink RFFP (DL-RFFP) positioning, the network (e.g., location server) configures the base station to send a downlink reference signal (e.g., PRS) to the mobile device, and the RFFP is the CER / CIR / CFR of the configured downlink reference signal detected by the mobile device. Although the present disclosure describes applying the ML positioning model to the RFFP measurement results, based on the teachings of the present disclosure, it will be recognized that other types of positioning models can be used in addition to or instead of the ML positioning model.

[0145] Each measured RFFP is compared to the known position of the mobile device at the time the mobile device measured the RFFP (in Figure 8 The location of the mobile device may be known via another positioning technology, such as that described above with reference to Figure 4 Note that although Figure 8 RFFP information is shown for a single mobile device, but as will be appreciated, RFFP information for multiple mobile devices may be collected and stored in a database.

[0146] Based on the information captured during the offline phase, an ML 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 ML model, and the known location of the mobile device when the RFFP is captured is used as a label. After training, during the "online" phase, the trained ML model can be used to predict (infer) the location of the mobile device (shown as "Pos M") based on the (multiple) RFFPs currently measured by the mobile device. For UE-based RFFP positioning, the network (e.g., a location server) provides the trained ML model to the mobile device. For UE-assisted positioning, the mobile device can provide the RFFP measurements to the network for processing.

[0147] Note that although Figure 8It is shown that the RFFP-based ML model is used to estimate the position of the UE, but the output (or extracted features) of the ML model may instead be positioning measurement results based on the input RFFP, such as RSTD measurement results, ToA measurement results, DL-AoD measurement results, etc.

[0148] Fig. 9 9 is a diagram illustrating an example inference loop for UE-based DL-RFFP positioning according to aspects of the present disclosure. Fig. 9 As shown, a location server (e.g., LMF 270) configures DL-PRS resources to be sent by one or more TRPs during a positioning session with a UE. The (multiple) TRPs then send the configured DL-PRS to the UE, which measures the RFFP of the DL-PRS.

[0149] exist Fig. 9 In the example of , the location server previously trained an ML model (labeled as “RFFPML”) for RFFP positioning, as described above with reference to Figure 7 and Figure 8 As discussed. The positioning server provides the ML model to the UE to perform inference during the positioning session (e.g., determining positioning measurement results based on the measured RFFP). As such, after measuring the RFFP of the DL-PRS, the UE inputs the measured RFFP to the received ML model to obtain associated (multiple) positioning measurement results (e.g., ToA, RSTD).

[0150] Fig.10 An example call flow 1000 for UE-based DL-RFFP positioning in accordance with aspects of the present disclosure is shown. At stage 1, the UE 204 and the LMF 270 perform an LPP positioning capability transfer procedure during which the UE 204 provides its positioning capabilities to the LMF 270. At stage 2, the LMF 270 provides assistance information, such as the PRS resource configuration of the DL-PRS to be sent to the UE 204, to the serving ng-eNB / gNB 222 / 224 of the UE 204 and any neighboring ng-eNB / gNB 222 / 244. At stage 3, the UE 204 and the LMF 270 perform an LPP assistance data exchange. During the exchange, the LMF 270 provides the UE 204 with assistance data for the positioning session, such as the configuration of the DL-PRS sent by the involved ng-eNB / gNB 222 / 224 and the ML model for reporting positioning measurements of the DL-PRS.

[0151] At stage 4, the LMF 270 optionally provides assistance information to the involved ng-eNB / gNB 222 / 224 via a New Radio Positioning Protocol Type A (NRPPa) message. At stage 5, the serving ng-eNB / gNB 222 / 224 optionally broadcasts the assistance information received from the LMF 270 as assistance data in one or more positioning SIBs (posSIBs). At stage 6, the LMF 270 and the UE 204 perform an LPP request / provide location information procedure, during which the UE 204 provides positioning measurements made on the DL-PRS sent by the ng-eNB / gNB 222 / 224. The positioning measurements may be derived by applying the ML model received in the assistance data to the RFFP of the measured DL-PRS. Fig.10 The various stages shown in will be discussed in more detail below.

[0152] The RFFP localization model can be trained on different environments (e.g., through crowdsourcing, federated learning). However, challenges still exist considering the full diversity of environmental and propagation conditions (e.g., a single indoor factory environment, where the machines and objects in the environment often vary depending on the current production system).

[0153] Certain aspects of the present disclosure are achieved in recognition that successful deployment and use of a positioning model for RFFP positioning can benefit from: 1) timely monitoring (e.g., typically continuous monitoring) of the effectiveness of the positioning model, and 2) selecting a fallback positioning technique that does not use the positioning model in response to determining that the positioning model is invalid or otherwise fails. To this end, methods of wireless communication performed by a UE are disclosed that facilitate monitoring the effectiveness of a positioning model used by the UE for RFFP positioning. In certain aspects, if the UE determines that the positioning model has failed, the UE can autonomously revert to a fallback positioning technique.

[0154] When the positioning model does not provide a positioning estimate that meets the position threshold requirement, the UE may determine that the positioning model has failed. For example, the UE may determine that the positioning model has failed based on the number of positioning model error instances that have occurred.

[0155] In one aspect, positioning model error "instances" can be accumulated and used to determine that the positioning model has failed (e.g., the positioning model is not suitable for use in the current positioning environment). Certain aspects of the present disclosure consider different types of positioning model error "instances", any of which can be used individually or in combination to determine that the positioning model is not suitable for continued use in the current positioning environment. One type of positioning model error instance according to various aspects of the present disclosure is referred to herein as an "uncertainty error instance". Another type of positioning model error instance according to various aspects of the present disclosure is referred to herein as a "mismatch error instance". If the UE detects multiple (i.e., continuous or cumulative) positioning model error instances, the positioning model may not be suitable for the current positioning environment, and another positioning technology (e.g., fallback positioning technology) can be used. In some aspects, the UE can use a counter or other counting mechanism to maintain a count of positioning model error instances.

[0156] An uncertainty error instance may be determined to have occurred based on a comparison of a positioning uncertainty associated with a positioning estimate obtained using a positioning model (e.g., by applying the positioning model to RFFP measurements) with a positioning uncertainty error criterion. In this regard, the UE may associate a positioning uncertainty value with a positioning estimate obtained using a positioning model. The positioning uncertainty value may be determined in various ways. In one aspect, the positioning model may provide such a positioning uncertainty value together with a corresponding positioning estimate at the output of the positioning model. Additionally or in an alternative, the UE may determine a positioning uncertainty value for a positioning estimate in different ways. Regardless of how the positioning uncertainty value is obtained, the UE may determine that an uncertainty error instance has occurred based on a comparison of a positioning uncertainty value corresponding to the positioning estimate with a positioning uncertainty error threshold indicated in, for example, a positioning model uncertainty error threshold indicated in a positioning uncertainty error criterion. In one aspect, if the positioning uncertainty value associated with a positioning estimate made during a positioning opportunity exceeds the positioning uncertainty threshold indicated in the positioning uncertainty error criterion, the UE may determine that an uncertainty error instance has occurred, and increase the number of positioning model error instances. In one aspect, parameters of the positioning uncertainty error criterion may be 1) indicated in one or more LPP messages, 2) pre-configured at the UE (e.g., during manufacturing, prior to UE deployment, during deployment of the UE in a positioning environment, etc.), or 3) any combination thereof.

[0157] A model mismatch error instance may be determined to have occurred based on a comparison of a positioning estimate obtained using a positioning model (e.g., by applying the positioning model to RFFP measurements) with a positioning estimate obtained using a positioning technology that does not use the positioning model. For example, the UE may compare a positioning estimate obtained during a positioning opportunity using a positioning model with a second positioning estimate obtained during a positioning opportunity using another positioning technology that does not employ a positioning model (e.g., a cellular-based positioning technology, a GNSS-based positioning technology, an RFFP positioning technology using a different positioning model, an NR positioning technology, or a combination thereof). The UE may determine a positioning difference between the first positioning estimate and the second positioning estimate. A mismatch error instance may be determined to have occurred based on a comparison of the positioning difference with a positioning mismatch threshold indicated in a positioning mismatch error criterion. In one aspect, if the positioning difference exceeds the positioning mismatch threshold indicated in the positioning mismatch error criterion, the UE may determine that a mismatch error instance has occurred, and increase the number of positioning model error instances. In one aspect, the parameters of the positioning mismatch error criterion may be 1) indicated in one or more LPP messages, 2) pre-configured at the UE, or 3) any combination thereof.

[0158] Positioning errors and corresponding positioning mismatch thresholds may be specified in a variety of ways. Such positioning errors and / or thresholds may be specified as 1) horizontal errors, 2) vertical errors, 3) three-dimensional errors, or 4) any combination thereof. Positioning uncertainty values ​​and corresponding positioning uncertainty error criteria may be specified in a similar manner.

[0159] In certain aspects, the UE may determine that the positioning model has failed based on a comparison of the cumulative number of model error instances associated with the positioning model failure criteria. Various positioning model failure criteria may be used. For example, the UE may compare the total number of cumulative model error instances that occur using the positioning model with the total number of allowed model error instances indicated by the configured positioning model failure criteria. In this case, when the cumulative number of model error instances exceeds the total number of allowed model error instances, the UE may determine that the positioning model has failed. Additionally or in an alternative, the UE may compare the cumulative number of model error instances that occur within a specified duration with the maximum number of allowed model error instances that may occur over the duration indicated by the configured positioning model failure criteria. In this case, when the number of model error instances that occur within a specified duration exceeds the maximum number of model error instances that can be allowed within the duration, the UE may determine that the positioning model has failed.

[0160] The UE may respond to the failure of the positioning model in various ways. For example, in response to determining that the number of model error instances meets the model failure criteria, the UE may deactivate the positioning model. In some aspects, during a positioning opportunity that occurs after the UE has detected a positioning model failure, the positioning model that has failed is not used. Additionally or in an alternative, the UE may activate a fallback positioning technique that does not use the positioning model for a positioning opportunity that occurs after the UE has detected a positioning model failure. In some aspects, the fallback technique is used for a positioning opportunity that occurs after the UE has determined that the positioning model has failed.

[0161] The duration during which the fallback positioning technique is used instead of the positioning technique associated with the failed positioning model can vary. In some aspects, the fallback technique is used instead of the positioning technique associated with the failed positioning model for all positioning opportunities after a detected positioning model failure, or until remedial action has been taken to restore the validity of the failed positioning model. In some aspects, the UE can reactivate the positioning model based on: 1) expiration of a time threshold since deactivating the positioning model, 2) expiration of a time threshold since activating the fallback positioning technique, 3) using the fallback positioning technique for a threshold number of positioning opportunities, 4) receiving a request to reactivate the positioning model, or 5) any combination thereof.

[0162] The UE may be configured with a positioning model failure criterion in various ways. In one aspect, the UE may receive a transmission of one or more parameters indicating a positioning model failure criterion from a network device (e.g., another UE, a location server, an LMF, a positioning model server, etc.). The transmission of one or more parameters indicating a model failure criterion may be received via a first group of one or more LPP messages. Additionally or in an alternative, the UE may be pre-configured with one or more parameters of a positioning model failure criterion. In certain aspects, the pre-configuration may be performed prior to the execution of an RFFP positioning operation using a positioning model (e.g., during manufacturing, prior to UE deployment, during deployment of the UE in a positioning environment, etc.). Based on the teachings of the present disclosure, it will be appreciated that other ways of configuring the UE with a model failure criterion may be employed.

[0163] Various positioning technologies can be used for the fallback positioning technology. In some aspects, the fallback positioning technology can be 1) a further RFFP technology using a different positioning model, 2) a GNSS positioning technology, 3) a NR positioning technology, or 4) any combination thereof.

[0164] The UE may similarly be configured with a fallback positioning technology in various ways. In certain aspects, the UE may receive one or more transmissions indicating: 1) the type of positioning technology to be used as a fallback positioning technology, 2) one or more parameters of the fallback positioning technology, or 3) any combination thereof. Additionally or in an alternative, the UE may be pre-configured with: 1) the type of positioning technology to be used for the fallback positioning technology, 2) one or more parameters of the fallback positioning technology, or 3) a combination thereof. In certain aspects, the pre-configuration may be performed prior to the execution of an RFFP positioning operation using a positioning model (e.g., during manufacturing, before UE deployment, during deployment of the UE in a positioning environment, etc.). Further, a mixture of any of the aforementioned methods of configuring the fallback positioning technology may be used. It will be appreciated that, based on the teachings of the present disclosure, other methods of configuring the UE with a fallback positioning technology may be employed.

[0165] According to certain aspects of the present disclosure, a UE may send a model failure report indicating that a positioning model has failed. The content and timing of the transmission of the model failure report may be configured by the network (e.g., a location server). In various aspects, the model failure report may be sent in response to: 1) determining that the positioning model has failed, 2) (e.g., receiving a model failure report request from a location server, a positioning model server, etc.), or 3) a combination thereof.

[0166] A model failure report may include various information that may be useful in evaluating a failure of a positioning model. For example, a model failure report may indicate: 1) a first model identifier associated with a first positioning model, 2) a second model identifier associated with a second positioning model applied to the RFFP measurement results to obtain a second positioning estimate, 3) identification of one or more positioning techniques used to obtain the second positioning estimate, 4) one or more timestamps associated with one or more of the positioning model error instances, 5) a time span associated with determining the one or more positioning model error instances, 6) one or more positioning uncertainty error values ​​associated with the one or more positioning model error instances, 7) channel condition parameters associated with the one or more positioning model error instances (e.g., channel delay spread, Doppler spread, etc. (if available)), or 8) any combination thereof. It will be appreciated that, based on the teachings of the present disclosure, other information may be indicated in the mismatch report, and the foregoing list constitutes an example of such information.

[0167] According to various aspects of the present disclosure, a model failure report may be sent to one or more network entities. In one aspect, a network entity may be responsible for maintaining, training, and / or distributing a positioning model to multiple UEs in a network. The network entity may be a location server (e.g., LMF). Additionally or alternatively, the network entity may be a model supervision server dedicated to managing the positioning model used by the UE. In either case, the network entity may perform functions including: 1) distributing a new positioning model to the UE, 2) retraining the positioning model based on information in the mismatch report, or 3) any combination thereof. Additionally or alternatively, such functions may be included in a location server.

[0168] Figures 11 to 13 Various ways of detecting positioning model failures in accordance with aspects of the present disclosure are described. Fig.11 1 is a timing diagram 1100 illustrating an example of positioning model failure detection based on a total number of positioning model error instances in accordance with aspects of the present disclosure. Fig.11In the example, the UE may employ a counter (e.g., labeled "posModelErrorInstanceCount") that is used to maintain a count of the total number of positioning model error instances that have occurred. Upon detecting a positioning model error instance, the UE increments the counter (e.g., increases the value of posModelErrorInstanceCount by 1). In this example, the UE has detected positioning model error instances at 1102, 1104, and 1106. As the value of posModelErrorInstanceCount is incremented, the value of posModelErrorInstanceCount is compared to the maximum number of model error instances indicated by the positioning model failure criteria (labeled "posModelErrorInstanceMaxCount"). In certain aspects, the value of posModelErrorInstanceMaxCount is selected to correspond to a value for indicating that the maximum number of allowed positioning failure instances has been exceeded. At model error instances 1102 and 1104, the value of posModelErrorInstanceCount is less than posModelErrorInstanceMaxCount, indicating that the positioning model has not yet failed. However, at positioning model error instance 1106, the value of posModelErrorInstanceCount is equal to the value of posModelErrorInstanceMaxCount, indicating that the number of allowed positioning model instances has been exceeded. As a result, the UE determines at positioning model error instance 1106 that the positioning model has failed.

[0169] Fig.12 1200 is a timing diagram illustrating an example of positioning model failure detection based on the total number of positioning model error instances occurring within a specified duration in accordance with aspects of the present disclosure. In addition to using counters posModelErrorInstanceCount and posModelErrorInstanceMaxCount, Fig.12The example shown in 1202 also specifies a duration 1202 during which posModelErrorInstanceCount is maintained. Although positioning model error instances are detected at 1210 and 1212, the value of posModelErrorInstanceCount does not reach the value of posModelErrorInstanceMaxCount within the duration 1202. Therefore, the UE does not detect a positioning model failure. Instead, the UE resets the value of posModelErrorInstanceCount and restarts tracking the number of positioning model error instances at positioning model error instance 1214 based on the positioning model error instance criteria for subsequent positioning opportunities. Note that the positioning model error instance criteria for subsequent positioning opportunities may be different from the positioning model error instance criteria for subsequent positioning opportunities. Fig.12 The positioning model error examples shown in the standards are the same or different.

[0170] Duration 1202 may be defined in a variety of ways. Fig.12 , the duration 1202 is defined by a start time 1204 (labeled “PosModelFailureDetectionTimerStart”), a window timer duration value 1206 (labeled “PosModelFailureDetectionTimerDuration”), and an end time 1208 (labeled “PosModelFailureDetectionTimerExpiry”). In certain aspects, the UE may start a timer at PosModelFailureDetectionTimer 1204 at a determined time or upon the occurrence of a specified event (e.g., the occurrence of an initial positioning model error instance). The timer may have a specified limit (e.g., a duration count) defined by PosModelFailureDetectionTimerDuration 1206. A determination is made that the timer has expired at PosModelFailureDetectionTimerExpiry 1208. It will be appreciated that other ways of specifying the duration 1202 may be used in light of the teachings of the present disclosure.

[0171] Fig.131300 is a timing diagram illustrating an example of positioning model failure detection based on a total number of positioning model error instances occurring within a specified duration in accordance with aspects of the present disclosure. At model error instances 1302 and 1304, the value of posModelErrorInstanceCount is less than posModelErrorInstanceMaxCount, indicating that the positioning model has not failed. However, at positioning model error instance 1306, the value of posModelErrorInstanceCount is equal to the value of posModelErrorInstanceMaxCount, indicating that the number of allowed positioning model instances has been exceeded before the expiration of the duration indicated at PosModelFailureDetectionTimerExpiry 1208. As a result, the UE determines at positioning model error instance 1306 that the positioning model has failed.

[0172] Fig.14 An example method 1400 of wireless communication performed by a UE in accordance with various aspects of the present disclosure is shown. At operation 1402, the UE determines that a positioning model error instance has occurred during a positioning opportunity based on: 1) a positioning uncertainty associated with a first positioning estimate satisfies a positioning uncertainty error criterion, wherein the first positioning estimate is obtained during the positioning opportunity by applying a first positioning model to a radio frequency fingerprint (RFFP) measurement, 2) a positioning mismatch between the UE's first positioning estimate and the UE's second positioning estimate satisfies a positioning mismatch error criterion, wherein the UE's second positioning estimate is obtained during the positioning opportunity by performing a positioning technique that does not use the first positioning model, or 3) any combination thereof. In an aspect, operation 1402 may be performed by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, one or more processors 332, memory 340, and / or positioning component 342, any one or all of which may be considered as a means for performing this operation.

[0173] At operation 1404, the UE determines that the first positioning model has failed based on the number of positioning model error instances satisfying the positioning model failure criteria. In an aspect, operation 1404 may be performed by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, one or more processors 332, memory 340, and / or positioning component 342, any one or all of which may be considered as a means for performing this operation.

[0174] As will be appreciated, the technical advantage of method 1400 is that the method enables the UE to detect the failure of the positioning model used in the RFFP positioning operation. Once the failure of the positioning model has been detected, the UE can perform various remedial measures, such as, for example, switching to a fallback technology for subsequent positioning opportunities, reporting the positioning model failure to the network, etc.

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

[0176] Examples of implementations are described in the following numbered clauses:

[0177] Clause 1. A method of wireless communication performed by a user equipment (UE), comprising: determining that a positioning model error instance has occurred during a positioning opportunity based on: 1) a positioning uncertainty associated with a first positioning estimate satisfies a positioning uncertainty error criterion, wherein the first positioning estimate is obtained during the positioning opportunity by applying a first positioning model to a radio frequency fingerprint (RFFP) measurement result, 2) a positioning mismatch between the first positioning estimate of the UE and a second positioning estimate of the UE satisfies a positioning mismatch error criterion, wherein the second positioning estimate of the UE is obtained during the positioning opportunity by performing a positioning technique that does not use the first positioning model, or 3) any combination thereof; and determining that the first positioning model has failed based on the number of positioning model error instances satisfying a positioning model failure criterion.

[0178] Clause 2. The method according to clause 1 further includes: in response to determining that the number of positioning model error instances meets the positioning model failure criteria, deactivating the first positioning model, and activating a fallback positioning technology that does not use the first positioning model in further positioning opportunities.

[0179] Clause 3. The method according to Clause 2 further includes: receiving an indication of the type of positioning technology to be used as a fallback positioning technology; receiving one or more parameters of the fallback positioning technology; configuring the UE with the type of positioning technology to be used for the fallback positioning technology based on pre-configuration of the type of positioning technology to be used for the fallback positioning technology at the UE; configuring the UE with one or more parameters of the fallback timing technology based on pre-configuration of one or more parameters of the fallback positioning technology at the UE; or any combination thereof.

[0180] Clause 4. A method according to clause 3, wherein: the type of positioning technology used for the fallback positioning technology is received via a first LPP message set; one or more parameters of the fallback positioning technology are received via a second LPP message set; or any combination thereof.

[0181] Clause 5. A method according to any one of clauses 2 to 4, wherein the fallback positioning technology comprises: further RFFP technology using a second positioning model; global navigation satellite system (GNSS) positioning technology; new radio (NR) positioning technology; or any combination thereof.

[0182] Clause 6. The method according to any one of clauses 2 to 5 further includes: reactivating the first positioning model based on: expiration of a time threshold since deactivation of the first positioning model, expiration of a time threshold since activation of the fallback positioning technology, use of the fallback positioning technology for a threshold number of positioning opportunities, receiving a request to reactivate the first positioning model, or any combination thereof.

[0183] Clause 7. A method according to any one of clauses 1 to 6, wherein the positioning model failure criteria comprises: the total number of positioning model error instances; the number of positioning model error instances occurring within a duration; or any combination thereof.

[0184] Clause 8. A method according to any one of clauses 1 to 7, wherein the positioning uncertainty error criterion comprises: the positioning uncertainty associated with the first positioning estimate exceeds a positioning uncertainty threshold.

[0185] Clause 9. A method according to any one of clauses 1 to 8, wherein the positioning mismatch error criterion includes: a positioning difference between the first positioning estimate and the second positioning estimate exceeds a positioning difference threshold.

[0186] Clause 10. The method according to any one of clauses 1 to 9 further includes: receiving one or more parameters for indicating a positioning model failure criterion; configuring one or more parameters of the positioning model failure criterion based on pre-configuration of one or more parameters of the positioning model failure criterion at the UE; or a combination thereof.

[0187] Clause 11. The method of clause 10, wherein: the one or more parameters indicating positioning model failure criteria are received via a Long Term Evolution Positioning Protocol (LPP) message set.

[0188] Clause 12. The method according to any one of clauses 1 to 11 further includes: sending a model failure report indicating that the first positioning model has failed.

[0189] Clause 13. A method according to clause 12, wherein: the model failure report is sent in response to: determining that the number of positioning model error instances meets the positioning model failure criteria; receiving a model failure report request; or any combination thereof.

[0190] Clause 14. A method according to clause 13, wherein the model failure report indicates: a first model identifier associated with a first positioning model; a second model identifier associated with a second positioning model applied to RFFP measurement results to obtain a second positioning estimate; an identifier of one or more positioning techniques used to obtain the second positioning estimate; one or more timestamps associated with one or more positioning model error instances in the positioning model error instances; a time span associated with determining one or more positioning model error instances; one or more positioning uncertainty error values ​​associated with one or more positioning model error instances; a channel condition parameter associated with one or more positioning model error instances; or any combination thereof.

[0191] Clause 15. 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 being configured to: determine that a positioning model error instance has occurred during a positioning opportunity based on: 1) a positioning uncertainty associated with a first positioning estimate satisfies a positioning uncertainty error criterion, wherein the first positioning estimate is obtained during the positioning opportunity by applying a first positioning model to a radio frequency fingerprint (RFFP) measurement result, 2) a positioning mismatch between the first positioning estimate of the UE and a second positioning estimate of the UE satisfies a positioning mismatch error criterion, wherein the second positioning estimate of the UE is obtained during the positioning opportunity by performing a positioning technique that does not use the first positioning model, or 3) any combination thereof; and determine that the first positioning model has failed based on the number of positioning model error instances satisfying the positioning model failure criterion.

[0192] Clause 16. A UE according to clause 15, wherein at least one processor is further configured to: in response to determining that the number of positioning model error instances meets the positioning model failure criteria, deactivate the first positioning model, and activate a fallback positioning technology that does not use the first positioning model in further positioning opportunities.

[0193] Clause 17. A UE according to clause 16, wherein at least one processor is further configured to: receive, via at least one transceiver, an indication of the type of positioning technology to be used as a fallback positioning technology; receive, via at least one transceiver, one or more parameters of the fallback positioning technology; based on pre-configuration of the type of positioning technology to be used for the fallback positioning technology at the UE, configure the UE with the type of positioning technology to be used for the fallback positioning technology; based on pre-configuration of one or more parameters of the fallback positioning technology at the UE, configure the UE with one or more parameters of the fallback timing technology; or any combination thereof.

[0194] Clause 18. A UE according to clause 17, wherein: the type of positioning technology used for the fallback positioning technology is received via a first LPP message set; one or more parameters of the fallback positioning technology are received via a second LPP message set; or any combination thereof.

[0195] Clause 19. A UE according to any one of clauses 16 to 18, wherein the fallback positioning technology comprises: a further RFFP technology using a second positioning model; a global navigation satellite system (GNSS) positioning technology; a new radio (NR) positioning technology; or any combination thereof.

[0196] Clause 20. A UE according to any one of clauses 16 to 19, wherein at least one processor is further configured to: reactivate the first positioning model based on: expiration of a time threshold since deactivation of the first positioning model, expiration of a time threshold since activation of the fallback positioning technology, use of the fallback positioning technology for a threshold number of positioning opportunities, receiving a request to reactivate the first positioning model via at least one transceiver, or any combination thereof.

[0197] Clause 21. A UE according to any one of clauses 15 to 20, wherein the positioning model failure criteria comprises: a total number of positioning model error instances; a number of positioning model error instances occurring within a duration; or any combination thereof.

[0198] Clause 22. A UE according to any one of clauses 15 to 21, wherein the positioning uncertainty error criterion comprises: the positioning uncertainty associated with the first positioning estimate exceeds a positioning uncertainty threshold.

[0199] Clause 23. A UE according to any one of clauses 15 to 22, wherein the positioning mismatch error criterion comprises: a positioning difference between the first positioning estimate and the second positioning estimate exceeds a positioning difference threshold.

[0200] Clause 24. A UE according to any one of clauses 15 to 23, wherein at least one processor is further configured to: receive one or more parameters indicating a positioning model failure criterion via at least one transceiver; configure one or more parameters of the positioning model failure criterion based on pre-configuration of the one or more parameters of the positioning model failure criterion at the UE; or a combination thereof.

[0201] Clause 25. A UE according to clause 24, wherein: the one or more parameters indicating positioning model failure criteria are received via a Long Term Evolution Positioning Protocol (LPP) message set.

[0202] Clause 26. A UE as defined in any one of clauses 15 to 25, wherein the at least one processor is further configured to: send, via the at least one transceiver, a model failure report indicating that the first positioning model has failed.

[0203] Clause 27. A UE according to clause 26, wherein: the model failure report is sent in response to: determining that a number of positioning model error instances meets a positioning model failure criterion; receiving a model failure report request; or any combination thereof.

[0204] Clause 28. A UE according to clause 27, wherein the model failure report indicates: a first model identifier associated with a first positioning model; a second model identifier associated with a second positioning model applied to RFFP measurement results to obtain a second positioning estimate; an identifier of one or more positioning techniques used to obtain the second positioning estimate; one or more timestamps associated with one or more positioning model error instances in the positioning model error instances; a time span associated with determining one or more positioning model error instances; one or more positioning uncertainty error values ​​associated with one or more positioning model error instances; a channel condition parameter associated with one or more positioning model error instances; or any combination thereof.

[0205] Clause 29. A user equipment (UE), comprising: a unit for determining that a positioning model error instance has occurred during a positioning opportunity based on: 1) a positioning uncertainty associated with a first positioning estimate satisfies a positioning uncertainty error criterion, wherein the first positioning estimate is obtained during the positioning opportunity by applying a first positioning model to a radio frequency fingerprint (RFFP) measurement result, 2) a positioning mismatch between the first positioning estimate of the UE and a second positioning estimate of the UE satisfies a positioning mismatch error criterion, wherein the second positioning estimate of the UE is obtained during the positioning opportunity by performing a positioning technique that does not use the first positioning model, or 3) any combination thereof; and a unit for determining that the first positioning model has failed based on the number of positioning model error instances satisfying the positioning model failure criterion.

[0206] Clause 30. The UE according to Clause 29 further includes: a unit for deactivating the first positioning model in response to determining that the number of positioning model error instances meets the positioning model failure criterion; and a unit for activating a fallback positioning technology that does not use the first positioning model in a further positioning opportunity in response to determining that the number of positioning model error instances meets the positioning model failure criterion.

[0207] Clause 31. The UE according to clause 30 further includes: a unit for receiving an indication of the type of positioning technology to be used as a fallback positioning technology; a unit for receiving one or more parameters of the fallback positioning technology; a unit for configuring the UE with the type of positioning technology to be used for the fallback positioning technology based on the pre-configuration of the type of positioning technology to be used for the fallback positioning technology at the UE; a unit for configuring the UE with one or more parameters of the fallback timing technology based on the pre-configuration of one or more parameters of the fallback positioning technology at the UE; or any combination thereof.

[0208] Clause 32. A UE according to clause 31, wherein: the type of positioning technology used for the fallback positioning technology is received via a first LPP message set; one or more parameters of the fallback positioning technology are received via a second LPP message set; or any combination thereof.

[0209] Clause 33. A UE according to any one of clauses 30 to 32, wherein the fallback positioning technology comprises: a further RFFP technology using a second positioning model; a global navigation satellite system (GNSS) positioning technology; a new radio (NR) positioning technology; or any combination thereof.

[0210] Clause 34. A UE according to any one of clauses 30 to 33, further comprising: a unit for reactivating the first positioning model based on: expiration of a time threshold since deactivation of the first positioning model, expiration of a time threshold since activation of the fallback positioning technology, use of the fallback positioning technology for a threshold number of positioning opportunities, receiving a request to reactivate the first positioning model, or any combination thereof.

[0211] Clause 35. A UE according to any one of clauses 29 to 34, wherein the positioning model failure criteria comprises: a total number of positioning model error instances; a number of positioning model error instances occurring within a duration; or any combination thereof.

[0212] Clause 36. A UE according to any one of clauses 29 to 35, wherein the positioning uncertainty error criterion comprises: the positioning uncertainty associated with the first positioning estimate exceeds a positioning uncertainty threshold.

[0213] Clause 37. A UE according to any one of clauses 29 to 36, wherein the positioning mismatch error criterion comprises: a positioning difference between the first positioning estimate and the second positioning estimate exceeds a positioning difference threshold.

[0214] Clause 38. A UE according to any one of clauses 29 to 37, further comprising: a unit for receiving one or more parameters for indicating a positioning model failure criterion; a unit for configuring one or more parameters of the positioning model failure criterion based on pre-configuration of the one or more parameters of the positioning model failure criterion at the UE; or a combination thereof.

[0215] Clause 39. A UE according to clause 38, wherein: the one or more parameters indicating positioning model failure criteria are received via a Long Term Evolution Positioning Protocol (LPP) message set.

[0216] Clause 40. A UE according to any one of clauses 29 to 39, further comprising: means for sending a model failure report indicating that the first positioning model has failed.

[0217] Clause 41. A UE according to clause 40, wherein: the model failure report is sent in response to: determining that a number of positioning model error instances meets a positioning model failure criterion; receiving a model failure report request; or any combination thereof.

[0218] Clause 42. A UE according to clause 41, wherein the model failure report indicates: a first model identifier associated with a first positioning model; a second model identifier associated with a second positioning model applied to RFFP measurement results to obtain a second positioning estimate; an identifier of one or more positioning techniques used to obtain the second positioning estimate; one or more timestamps associated with one or more positioning model error instances in the positioning model error instances; a time span associated with determining one or more positioning model error instances; one or more positioning uncertainty error values ​​associated with one or more positioning model error instances; a channel condition parameter associated with one or more positioning model error instances; or any combination thereof.

[0219] Clause 43. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to perform the following operations: determining that a positioning model error instance has occurred during a positioning opportunity based on: 1) a positioning uncertainty associated with a first positioning estimate satisfies a positioning uncertainty error criterion, wherein the first positioning estimate is obtained during the positioning opportunity by applying a first positioning model to a radio frequency fingerprint (RFFP) measurement result, 2) a positioning mismatch between the UE's first positioning estimate and the UE's second positioning estimate satisfies a positioning mismatch error criterion, wherein the UE's second positioning estimate is obtained during the positioning opportunity by performing a positioning technique that does not use the first positioning model, or 3) any combination thereof; and determining that the first positioning model has failed based on the number of positioning model error instances satisfying a positioning model failure criterion.

[0220] Clause 44. The non-transitory computer-readable medium according to clause 43 further includes computer executable instructions that, when executed by the UE, cause the UE to perform the following operations: in response to determining that the number of positioning model error instances meets the positioning model failure criteria, deactivate the first positioning model, and activate a fallback positioning technology that does not use the first positioning model in further positioning opportunities.

[0221] Clause 45. The non-transitory computer-readable medium according to clause 44 further includes computer executable instructions that, when executed by the UE, cause the UE to perform the following operations: receive an indication of the type of positioning technology to be used as a fallback positioning technology; receive one or more parameters of the fallback positioning technology; configure the UE with the type of positioning technology to be used for the fallback positioning technology based on the pre-configuration of the type of positioning technology to be used for the fallback positioning technology at the UE; configure the UE with one or more parameters of the fallback timing technology based on the pre-configuration of one or more parameters of the fallback positioning technology at the UE; or any combination thereof.

[0222] Clause 46. A non-transitory computer-readable medium according to clause 45, wherein: the type of positioning technology used for the fallback positioning technology is received via a first LPP message set; one or more parameters of the fallback positioning technology are received via a second LPP message set; or any combination thereof.

[0223] Clause 47. A non-transitory computer-readable medium according to any one of clauses 44 to 46, wherein the fallback positioning technology includes: further RFFP technology using a second positioning model; global navigation satellite system (GNSS) positioning technology; new radio (NR) positioning technology; or any combination thereof.

[0224] Clause 48. A non-transitory computer-readable medium according to any one of clauses 44 to 47, further comprising computer executable instructions that, when executed by the UE, cause the UE to perform the following operations: reactivating the first positioning model based on: expiration of a time threshold since deactivation of the first positioning model, expiration of a time threshold since activation of the fallback positioning technology, use of the fallback positioning technology for a threshold number of positioning opportunities, receiving a request to reactivate the first positioning model, or any combination thereof.

[0225] Clause 49. A non-transitory computer-readable medium according to any one of clauses 43 to 48, wherein the positioning model failure criteria includes: a total number of positioning model error instances; a number of positioning model error instances occurring within a duration; or any combination thereof.

[0226] Clause 50. The non-transitory computer-readable medium of any one of clauses 43 to 49, wherein the positioning uncertainty error criterion comprises: the positioning uncertainty associated with the first positioning estimate exceeds a positioning uncertainty threshold.

[0227] Clause 51. A non-transitory computer-readable medium according to any one of clauses 43 to 50, wherein the positioning mismatch error criterion includes: a positioning difference between the first positioning estimate and the second positioning estimate exceeds a positioning difference threshold.

[0228] Clause 52. A non-transitory computer-readable medium according to any one of clauses 43 to 51, further comprising computer-executable instructions that, when executed by a UE, cause the UE to perform the following operations: receiving one or more parameters indicating a positioning model failure criterion; configuring one or more parameters of the positioning model failure criterion based on pre-configuration of the one or more parameters of the positioning model failure criterion at the UE; or a combination thereof.

[0229] Clause 53. The non-transitory computer-readable medium of clause 52, wherein: the one or more parameters indicating positioning model failure criteria are received via a Long Term Evolution Positioning Protocol (LPP) message set.

[0230] Clause 54. The non-transitory computer-readable medium of any one of clauses 43 to 53, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: send a model failure report indicating that the first positioning model has failed.

[0231] Clause 55. A non-transitory computer-readable medium according to clause 54, wherein: the model failure report is sent in response to: determining that a number of positioning model error instances meets positioning model failure criteria; receiving a model failure report request; or any combination thereof.

[0232] Clause 56. A non-transitory computer-readable medium according to clause 55, wherein the model failure report indicates: a first model identifier associated with a first positioning model; a second model identifier associated with a second positioning model applied to RFFP measurement results to obtain a second positioning estimate; an identification of one or more positioning techniques used to obtain the second positioning estimate; one or more timestamps associated with one or more positioning model error instances in the positioning model error instances; a time span associated with determining the one or more positioning model error instances; one or more positioning uncertainty error values ​​associated with the one or more positioning model error instances; a channel condition parameter associated with the one or more positioning model error instances; or any combination thereof.

[0233] It will be appreciated by those skilled in the art 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 mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0234] Further, it will be appreciated by those skilled in the art that the various illustrative logic blocks, modules, circuits and algorithmic steps described in conjunction with the various aspects disclosed herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits and steps have been generally described above in terms of their functions. Whether such functions are implemented as hardware or software depends on specific applications and the design constraints imposed on the entire system. A skilled person can implement the described functions in an alternative manner for each specific application, but such implementation decisions should not be interpreted as causing deviations from the scope of the present disclosure.

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

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

[0237] In one or more example aspects, the functions described may be implemented in hardware, software, firmware or any combination thereof. If implemented in software, the functions may be stored on a computer-readable medium or transmitted therethrough as one or more instructions or codes. Computer-readable media may include both computer storage media and communication media, and the communication media include any media that facilitates the transfer of a computer program from one place to another. Storage media may be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or may be used to carry or store desired program codes and any other media that can be accessed by a computer in the form of instructions or data structures. In addition, any connection is appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, a server or other remote source using a coaxial cable, an optical fiber cable, a twisted pair, a digital subscriber line (DSL) or wireless technology (such as infrared, radio and microwave), then the coaxial cable, the optical fiber cable, the twisted pair, the DSL or wireless technology (such as infrared, radio and microwave) is included in the definition of the medium. As used herein, disk and optical disk include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, wherein disk usually reproduces data magnetically, while optical disc utilizes laser to reproduce data optically. Combinations of the above should also be included in the scope of computer readable media.

[0238] Although the foregoing disclosure shows the illustrative aspects of the disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the disclosure as defined by the appended claims. The steps and / or actions of the method claims according to the various aspects of the disclosure described herein do not need to be performed in any particular order. In addition, although the elements of the disclosure may be described or claimed in the singular, the plural form is contemplated unless expressly stated to be limited to the singular form.

Claims

1. A method of wireless communication performed by a user equipment (UE), comprising: Determining that a positioning model error instance has occurred during a positioning opportunity is based on: a positioning uncertainty associated with a first positioning estimate, obtained during the positioning occasion by applying a first positioning model to a radio frequency fingerprint (RFFP) measurement, satisfies a positioning uncertainty error criterion, and a positioning mismatch between the first positioning estimate for the UE and a second positioning estimate for the UE, obtained during the positioning occasion by performing a positioning technique that does not use the first positioning model, satisfies a positioning mismatch error criterion, or any combination thereof; and Based on a number of positioning model error instances satisfying a positioning model failure criterion, it is determined that the first positioning model has failed.

2. The method according to claim 1, further comprising: In response to determining that the number of positioning model error instances satisfies the positioning model failure criterion, deactivating the first positioning model, and A fallback positioning technique that does not use the first positioning model is activated in further positioning occasions.

3. The method according to claim 2, further comprising: receiving an indication of a type of positioning technology to be used as the fallback positioning technology; receiving one or more parameters of the fallback positioning technique; configuring the UE with the type of positioning technology for the fallback positioning technique based on pre-configuration at the UE of the type of positioning technology to be used for the fallback positioning technique; configuring the UE with the one or more parameters of the fallback timing technique based on pre-configuration of the one or more parameters of the fallback positioning technique at the UE; or Any combination thereof.

4. The method according to claim 3, wherein: The type of the positioning technology used for the fallback positioning technology is received via a first LPP message set; The one or more parameters of the fallback positioning technique are received via a second LPP message set; or Any combination thereof.

5. The method according to claim 2, wherein: The fallback positioning technology includes: A further RFFP technique using a second positioning model; Global Navigation Satellite System (GNSS) positioning technology; New Radio (NR) positioning technology; or Any combination thereof.

6. The method according to claim 2, further comprising: The first positioning model is reactivated based on: expiry of a time threshold since deactivation of said first positioning model, the expiration of a time threshold since activation of the fallback positioning technique, using the fallback positioning technique for a threshold number of positioning opportunities, receiving a request to reactivate the first positioning model, or Any combination thereof.

7. The method according to claim 1, wherein: The positioning model failure criteria include: The total number of positioning model error instances; the number of positioning model error instances that occur over a duration; or Any combination thereof.

8. The method according to claim 1, wherein: The positioning uncertainty error criteria include: The positioning uncertainty associated with the first positioning estimate exceeds a positioning uncertainty threshold.

9. The method according to claim 1, wherein: The positioning mismatch error criteria include: A positioning difference between the first positioning estimate and the second positioning estimate exceeds a positioning difference threshold.

10. The method according to claim 1, further comprising: receiving one or more parameters indicating failure criteria of the positioning model; configuring the one or more parameters of the positioning model failure criterion based on pre-configuration of the one or more parameters of the positioning model failure criterion at the UE; or Its combination.

11. The method according to claim 10, wherein: The one or more parameters indicating the positioning model failure criteria are received via a Long Term Evolution Positioning Protocol (LPP) message set.

12. The method according to claim 1, further comprising: A model failure report is sent indicating that the first positioning model has failed.

13. The method according to claim 12, wherein: The model failure report is sent in response to: Determining a number of the positioning model error instances that satisfy the positioning model failure criterion; receiving a model failure report request; or Any combination thereof.

14. The method according to claim 13, wherein: The model failure report indicates: a first model identifier associated with the first positioning model; a second model identifier associated with a second positioning model applied to the RFFP measurements to obtain the second positioning estimate; identification of one or more positioning techniques used to obtain the second position estimate; one or more timestamps associated with one or more of the positioning model error instances; a time span associated with determining the one or more positioning model error instances; one or more positioning uncertainty error values ​​associated with the one or more positioning model error instances; channel condition parameters associated with the one or more positioning model error instances; or Any combination thereof.

15. A user equipment (UE), comprising: Memory; at least one transceiver; as well as at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: Determining that a positioning model error instance has occurred during a positioning opportunity is based on: a positioning uncertainty associated with a first positioning estimate obtained by applying a first positioning model to radio frequency fingerprint (RFFP) measurements during the positioning opportunity satisfies a positioning uncertainty error criterion, a positioning mismatch between the first positioning estimate of the UE and a second positioning estimate of the UE, wherein the second positioning estimate of the UE is obtained during the positioning opportunity by performing a positioning technique that does not use the first positioning model, or any combination thereof; and Based on a number of positioning model error instances satisfying a positioning model failure criterion, it is determined that the first positioning model has failed.

16. The UE according to claim 15, wherein: The at least one processor is further configured to: In response to determining that the number of positioning model error instances satisfies the positioning model failure criterion, deactivating the first positioning model, and A fallback positioning technique that does not use the first positioning model is activated in further positioning occasions.

17. The UE according to claim 16, wherein: The at least one processor is further configured to: receiving, via the at least one transceiver, an indication of a type of positioning technology to be used as the fallback positioning technology; receiving, via the at least one transceiver, one or more parameters of the fallback positioning technique; configuring the UE with the type of positioning technology for the fallback positioning technique based on pre-configuration at the UE of the type of positioning technology to be used for the fallback positioning technique; configuring the UE with the one or more parameters of the fallback timing technique based on pre-configuration of the one or more parameters of the fallback positioning technique at the UE; or Any combination thereof.

18. The UE according to claim 17, wherein: The type of the positioning technology used for the fallback positioning technology is received via a first LPP message set; The one or more parameters of the fallback positioning technique are received via a second LPP message set; or Any combination thereof.

19. The UE according to claim 16, wherein: The fallback positioning technology includes: A further RFFP technique using a second positioning model; Global Navigation Satellite System (GNSS) positioning technology; New Radio (NR) positioning technology; or Any combination thereof.

20. The UE according to claim 16, wherein: The at least one processor is further configured to: The first positioning model is reactivated based on: expiry of a time threshold since deactivation of said first positioning model, the expiration of a time threshold since activation of the fallback positioning technique, using the fallback positioning technique for a threshold number of positioning opportunities, receiving, via the at least one transceiver, a request to reactivate the first positioning model, or Any combination thereof.

21. The UE according to claim 15, wherein: The positioning model failure criteria include: The total number of positioning model error instances; the number of positioning model error instances that occur over a duration; or Any combination thereof.

22. The UE according to claim 15, wherein: The positioning uncertainty error criteria include: The positioning uncertainty associated with the first positioning estimate exceeds a positioning uncertainty threshold.

23. The UE according to claim 15, wherein: The positioning mismatch error criteria include: A positioning difference between the first positioning estimate and the second positioning estimate exceeds a positioning difference threshold.

24. The UE according to claim 15, wherein: The at least one processor is further configured to: receiving, via the at least one transceiver, one or more parameters indicative of failure criteria for the positioning model; configuring the one or more parameters of the positioning model failure criterion based on pre-configuration of the one or more parameters of the positioning model failure criterion at the UE; or Its combination.

25. The UE according to claim 24, wherein: The one or more parameters indicating the positioning model failure criteria are received via a Long Term Evolution Positioning Protocol (LPP) message set.

26. The UE according to claim 15, wherein: The at least one processor is further configured to: A model failure report is sent via the at least one transceiver indicating that the first positioning model has failed.

27. The UE according to claim 26, wherein: The model failure report is sent in response to: Determining a number of the positioning model error instances that satisfy the positioning model failure criterion; receiving a model failure report request; or Any combination thereof.

28. The UE according to claim 27, wherein: The model failure report indicates: a first model identifier associated with the first positioning model; a second model identifier associated with a second positioning model applied to the RFFP measurements to obtain the second positioning estimate; identification of one or more positioning techniques used to obtain the second position estimate; one or more timestamps associated with one or more of the positioning model error instances; a time span associated with determining the one or more positioning model error instances; one or more positioning uncertainty error values ​​associated with the one or more positioning model error instances; channel condition parameters associated with the one or more positioning model error instances; or Any combination thereof.

29. A user equipment (UE), comprising: Means for determining that a positioning model error instance has occurred during a positioning opportunity based on: a positioning uncertainty associated with a first positioning estimate, obtained during the positioning occasion by applying a first positioning model to a radio frequency fingerprint (RFFP) measurement, satisfies a positioning uncertainty error criterion, and a positioning mismatch between the first positioning estimate for the UE and a second positioning estimate for the UE, obtained during the positioning occasion by performing a positioning technique that does not use the first positioning model, satisfies a positioning mismatch error criterion, or any combination thereof; and Used to determine the unit where the first positioning model has failed based on the number of positioning model error instances satisfying the positioning model failure criterion.

30. A non-transitory computer-readable medium storing computer-executable instructions, which when executed by a user equipment (UE) cause the UE to: Determining that a positioning model error instance has occurred during a positioning opportunity is based on: The positioning uncertainty associated with the first positioning estimate satisfies a positioning uncertainty error criterion where, The first positioning estimate is obtained by applying a first positioning model to a radio frequency fingerprint (RFFP) measurement result during the positioning opportunity, and a positioning mismatch between the first positioning estimate of the UE and a second positioning estimate of the UE satisfies a positioning mismatch error criterion, wherein the second positioning estimate of the UE is obtained by performing a positioning technique that does not use the first positioning model during the positioning opportunity, or any combination thereof; and Based on a number of positioning model error instances satisfying a positioning model failure criterion, it is determined that the first positioning model has failed.

Images