US20240085515A1 - Positioning model codepoint configuration - Google Patents

Positioning model codepoint configuration Download PDF

Info

Publication number
US20240085515A1
US20240085515A1 US17/930,844 US202217930844A US2024085515A1 US 20240085515 A1 US20240085515 A1 US 20240085515A1 US 202217930844 A US202217930844 A US 202217930844A US 2024085515 A1 US2024085515 A1 US 2024085515A1
Authority
US
United States
Prior art keywords
positioning
pmc
model
models
index
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
US17/930,844
Other languages
English (en)
Inventor
Marwen Zorgui
Mohammed Ali Mohammed Hirzallah
Srinivas Yerramalli
Ahmed Attia ABOTABL
Xiaoxia Zhang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to US17/930,844 priority Critical patent/US20240085515A1/en
Assigned to QUALCOMM INCORPORATED reassignment QUALCOMM INCORPORATED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: YERRAMALLI, Srinivas, ZHANG, XIAOXIA, ABOTABL, Ahmed Attia, HIRZALLAH, Mohammed Ali Mohammed, ZORGUI, MARWEN
Priority to PCT/US2023/070484 priority patent/WO2024054722A1/fr
Priority to TW112126845A priority patent/TW202412547A/zh
Publication of US20240085515A1 publication Critical patent/US20240085515A1/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
    • G01S5/02—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations using radio waves
    • G01S5/0252—Radio frequency fingerprinting
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
    • G01S5/02—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations using radio waves
    • G01S5/0205—Details
    • G01S5/0236—Assistance data, e.g. base station almanac
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
    • G01S5/02—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations using radio waves
    • G01S5/0257—Hybrid positioning
    • G01S5/0268—Hybrid positioning by deriving positions from different combinations of signals or of estimated positions in a single positioning system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1614—Details of the supervisory signal using bitmaps
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H04W64/003—Locating users or terminals or network equipment for network management purposes, e.g. mobility management locating network equipment
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
    • G01S5/02—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations using radio waves
    • G01S5/0278—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations using radio waves involving statistical or probabilistic considerations

Definitions

  • aspects of the disclosure relate generally to wireless communications.
  • Wireless communication systems have developed through various generations, including a first-generation analog wireless phone service (1G), a second-generation (2G) digital wireless phone service (including interim 2.5G and 2.75G networks), a third-generation (3G) high speed data, Internet-capable wireless service and a fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax).
  • 1G first-generation analog wireless phone service
  • 2G second-generation digital wireless phone service
  • 3G high speed data
  • 4G fourth-generation
  • 4G fourth-generation
  • LTE Long Term Evolution
  • PCS personal communications service
  • Examples of known cellular systems include the cellular analog advanced mobile phone system (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), the Global System for Mobile communications (GSM), etc.
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • GSM Global System for Mobile communications
  • a fifth generation (5G) wireless standard referred to as New Radio (NR)
  • NR New Radio
  • the 5G standard according to the Next Generation Mobile Networks Alliance, is designed to provide higher data rates as compared to previous standards, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements.
  • RS-P reference signals for positioning
  • PRS sidelink positioning reference signals
  • a method of wireless communication performed by a user equipment includes receiving a positioning model codepoint (PMC) index of a plurality of PMC indexes, wherein each PMC index of the plurality of PMC indexes is mapped to a corresponding positioning model of at least a subset of a plurality of positioning models configured at the UE; and applying a positioning model, mapped to the PMC index, to one or more RFFP positioning measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session.
  • PMC positioning model codepoint
  • a method of wireless communication performed by a user equipment includes applying a selected positioning model to one or more radio frequency fingerprint positioning (RFFP) measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session, wherein the selected positioning model is selected from a plurality of positioning models configured at the UE; transmitting, to a network server, at least one of the one or more position parameters; and transmitting, to the network server, a positioning model codepoint (PMC) index that is mapped to the selected positioning model, wherein the PMC index is one of a plurality of PMC indexes mapped to corresponding positioning models of at least a subset of the plurality of positioning models configured at the UE.
  • RFFP radio frequency fingerprint positioning
  • a user equipment 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 configured to: receive, via the at least one transceiver, a positioning model codepoint (PMC) index of a plurality of PMC indexes, wherein each PMC index of the plurality of PMC indexes is mapped to a corresponding positioning model of at least a subset of a plurality of positioning models configured at the UE; and apply a positioning model, mapped to the PMC index, to one or more RFFP positioning measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session.
  • PMC positioning model codepoint
  • a user equipment 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 configured to: apply a selected positioning model to one or more radio frequency fingerprint positioning (RFFP) measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session, wherein the selected positioning model is selected from a plurality of positioning models configured at the UE; transmit, via the at least one transceiver, to a network server, at least one of the one or more position parameters; and transmit, via the at least one transceiver, to the network server, a positioning model codepoint (PMC) index that is mapped to the selected positioning model, wherein the PMC index is one of a plurality of PMC indexes mapped to corresponding positioning models of at least a subset of the plurality of positioning models configured at the UE.
  • RFFP radio frequency fingerprint positioning
  • a user equipment includes means for receiving a positioning model codepoint (PMC) index of a plurality of PMC indexes, wherein each PMC index of the plurality of PMC indexes is mapped to a corresponding positioning model of at least a subset of a plurality of positioning models configured at the UE; and means for applying a positioning model, mapped to the PMC index, to one or more RFFP positioning measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session.
  • PMC positioning model codepoint
  • a user equipment includes means for applying a selected positioning model to one or more radio frequency fingerprint positioning (RFFP) measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session, wherein the selected positioning model is selected from a plurality of positioning models configured at the UE; means for transmitting, to a network server, at least one of the one or more position parameters; and means for transmitting, to the network server, a positioning model codepoint (PMC) index that is mapped to the selected positioning model, wherein the PMC index is one of a plurality of PMC indexes mapped to corresponding positioning models of at least a subset of the plurality of positioning models configured at the UE.
  • RFFP radio frequency fingerprint positioning
  • a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive a positioning model codepoint (PMC) index of a plurality of PMC indexes, wherein each PMC index of the plurality of PMC indexes is mapped to a corresponding positioning model of at least a subset of a plurality of positioning models configured at the UE; and apply a positioning model, mapped to the PMC index, to one or more RFFP positioning measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session.
  • PMC positioning model codepoint
  • a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: apply a selected positioning model to one or more radio frequency fingerprint positioning (RFFP) measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session, wherein the selected positioning model is selected from a plurality of positioning models configured at the UE; transmit, to a network server, at least one of the one or more position parameters; and transmit, to the network server, a positioning model codepoint (PMC) index that is mapped to the selected positioning model, wherein the PMC index is one of a plurality of PMC indexes mapped to corresponding positioning models of at least a subset of the plurality of positioning models configured at the UE.
  • RFFP radio frequency fingerprint positioning
  • FIG. 1 illustrates an example wireless communications system, according to aspects of the disclosure.
  • FIGS. 2 A, 2 B, and 2 C illustrate example wireless network structures, according to aspects of the disclosure.
  • FIGS. 3 A, 3 B, and 3 C are simplified block diagrams of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.
  • UE user equipment
  • base station base station
  • network entity network entity
  • FIG. 4 illustrates examples of various positioning methods supported in New Radio (NR), according to aspects of the disclosure.
  • NR New Radio
  • FIG. 5 is a diagram illustrating an example frame structure, according to aspects of the disclosure.
  • FIG. 6 is a graph representing a radio frequency (RF) channel estimate, according to aspects of the disclosure.
  • FIG. 7 illustrates an example neural network, according to aspects of the disclosure.
  • FIG. 8 is a diagram illustrating the use of a machine learning (ML) model for RF fingerprinting (RFFP)-based positioning, according to aspects of the disclosure.
  • ML machine learning
  • FIG. 9 is a diagram illustrating the inference cycle for UE-based downlink RFFP (DL-RFFP) positioning, according to aspects of the disclosure.
  • FIG. 10 illustrates an example call flow for UE-based DL-RFFP positioning, according to aspects of the disclosure.
  • FIG. 11 is a diagram showing one manner of indicating a positioning model codepoint (PMC) configuration for mapping positioning models configured at the UE to positioning model codepoint indexes, according to aspects of the disclosure.
  • PMC positioning model codepoint
  • FIG. 12 illustrates an example method of wireless communication performed by a UE, according to aspects of the disclosure.
  • FIG. 13 illustrates an example method of wireless communication performed by a UE, according to aspects of the disclosure.
  • sequences of actions to be performed by, for example, elements of a computing device. It will be recognized that various actions described herein can be performed by specific circuits (e.g., application specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequence(s) of actions described herein can be considered to be embodied entirely within any form of non-transitory computer-readable storage medium having stored therein a corresponding set of computer instructions that, upon execution, would cause or instruct an associated processor of a device to perform the functionality described herein.
  • ASICs application specific integrated circuits
  • a UE may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, consumer asset locating device, wearable (e.g., smartwatch, glasses, augmented reality (AR)/virtual reality (VR) headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communications network.
  • a UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a radio access network (RAN).
  • RAN radio access network
  • the term “UE” may be referred to interchangeably as an “access terminal” or “AT,” a “client device,” a “wireless device,” a “subscriber device,” a “subscriber terminal,” a “subscriber station,” a “user terminal” or “UT,” a “mobile device,” a “mobile terminal,” a “mobile station,” or variations thereof.
  • AT access terminal
  • client device a “wireless device”
  • subscriber device a “subscriber terminal”
  • a “subscriber station” a “user terminal” or “UT”
  • UEs can communicate with a core network via a RAN, and through the core network the UEs can be connected with external networks such as the Internet and with other UEs.
  • WLAN wireless local area network
  • IEEE Institute of Electrical and Electronics Engineers
  • a base station may operate according to one of several RATs in communication with UEs depending on the network in which it is deployed, and may be alternatively referred to as an access point (AP), a network node, a NodeB, an evolved NodeB (eNB), a next generation eNB (ng-eNB), a New Radio (NR) Node B (also referred to as a gNB or gNodeB), etc.
  • AP access point
  • eNB evolved NodeB
  • ng-eNB next generation eNB
  • NR New Radio
  • a base station may be used primarily to support wireless access by UEs, including supporting data, voice, and/or signaling connections for the supported UEs.
  • a base station may provide purely edge node signaling functions while in other systems it may provide additional control and/or network management functions.
  • a communication link through which UEs can send signals to a base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.).
  • a communication link through which the base station can send signals to UEs is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.).
  • DL downlink
  • forward link channel e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.
  • traffic channel can refer to either an uplink/reverse or downlink/forward traffic channel.
  • base station may refer to a single physical transmission-reception point (TRP) or to multiple physical TRPs that may or may not be co-located.
  • TRP transmission-reception point
  • the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station.
  • base station refers to multiple co-located physical TRPs
  • the physical TRPs may be an array of antennas (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming) of the base station.
  • MIMO multiple-input multiple-output
  • the physical TRPs may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station).
  • DAS distributed antenna system
  • RRH remote radio head
  • the non-co-located physical TRPs may be the serving base station receiving the measurement report from the UE and a neighbor base station whose reference radio frequency (RF) signals the UE is measuring.
  • RF radio frequency
  • a base station may not support wireless access by UEs (e.g., may not support data, voice, and/or signaling connections for UEs), but may instead transmit reference signals to UEs to be measured by the UEs, and/or may receive and measure signals transmitted by the UEs.
  • a base station may be referred to as a positioning beacon (e.g., when transmitting signals to UEs) and/or as a location measurement unit (e.g., when receiving and measuring signals from UEs).
  • An “RF signal” comprises an electromagnetic wave of a given frequency that transports information through the space between a transmitter and a receiver.
  • a transmitter may transmit a single “RF signal” or multiple “RF signals” to a receiver.
  • the receiver may receive multiple “RF signals” corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels.
  • the same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a “multipath” RF signal.
  • an RF signal may also be referred to as a “wireless signal” or simply a “signal” where it is clear from the context that the term “signal” refers to a wireless signal or an RF signal.
  • FIG. 1 illustrates an example wireless communications system 100 , according to aspects of the disclosure.
  • the wireless communications system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled “BS”) and various UEs 104 .
  • the base stations 102 may include macro cell base stations (high power cellular base stations) and/or small cell base stations (low power cellular base stations).
  • the macro cell base stations may include eNBs and/or ng-eNBs where the wireless communications system 100 corresponds to an LTE network, or gNBs where the wireless communications system 100 corresponds to a NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.
  • the base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through backhaul links 122 , and through the core network 170 to one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)).
  • the location server(s) 172 may be part of core network 170 or may be external to core network 170 .
  • a location server 172 may be integrated with a base station 102 .
  • a UE 104 may communicate with a location server 172 directly or indirectly.
  • a UE 104 may communicate with a location server 172 via the base station 102 that is currently serving that UE 104 .
  • a UE 104 may also communicate with a location server 172 through another path, such as via an application server (not shown), via another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), and so on.
  • WLAN wireless local area network
  • AP wireless local area network access point
  • communication between a UE 104 and a location server 172 may be represented as an indirect connection (e.g., through the core network 170 , etc.) or a direct connection (e.g., as shown via direct connection 128 ), with the intervening nodes (if any) omitted from a signaling diagram for clarity.
  • the base stations 102 may perform functions that relate to one or more of transferring user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages.
  • the base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC/5GC) over backhaul links 134 , which may be wired or wireless.
  • the base stations 102 may wirelessly communicate with the UEs 104 . Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110 . In an aspect, one or more cells may be supported by a base station 102 in each geographic coverage area 110 .
  • a “cell” is a logical communication entity used for communication with a base station (e.g., over some frequency resource, referred to as a carrier frequency, component carrier, carrier, band, or the like), and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) for distinguishing cells operating via the same or a different carrier frequency.
  • PCI physical cell identifier
  • ECI enhanced cell identifier
  • VCI virtual cell identifier
  • CGI cell global identifier
  • 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 others) that may provide access for different types of UEs.
  • MTC machine-type communication
  • NB-IoT narrowband IoT
  • eMBB enhanced mobile broadband
  • a cell may refer to either or both of the logical communication entity and the base station that supports it, depending on the context.
  • TRP is typically the physical transmission point of a cell
  • the terms “cell” and “TRP” may be used interchangeably.
  • the term “cell” may also refer to a geographic coverage area of a base station (e.g., a sector), insofar as a carrier frequency can be detected and used for communication within some portion of geographic coverage areas 110 .
  • While neighboring macro cell base station 102 geographic coverage areas 110 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may be substantially overlapped by a larger geographic coverage area 110 .
  • a small cell base station 102 ′ (labeled “SC” for “small cell”) may have a geographic coverage area 110 ′ that substantially overlaps with the geographic coverage area 110 of one or more macro cell base stations 102 .
  • a network that includes both small cell and macro cell base stations may be known as a heterogeneous network.
  • a heterogeneous network may also include home eNBs (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG).
  • HeNBs home eNBs
  • the communication links 120 between the base stations 102 and the UEs 104 may include uplink (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104 .
  • the communication links 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity.
  • the communication links 120 may be through one or more carrier frequencies. Allocation of carriers may be asymmetric with respect to downlink and uplink (e.g., more or less carriers may be allocated for downlink than for uplink).
  • the wireless communications system 100 may further include a wireless local area network (WLAN) access point (AP) 150 in communication with WLAN stations (STAs) 152 via communication links 154 in an unlicensed frequency spectrum (e.g., 5 GHz).
  • WLAN STAs 152 and/or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communicating in order to determine whether the channel is available.
  • CCA clear channel assessment
  • LBT listen before talk
  • the small cell base station 102 ′ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102 ′ may employ LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum as used by the WLAN AP 150 . The small cell base station 102 ′, employing LTE/5G in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.
  • NR in unlicensed spectrum may be referred to as NR-U.
  • LTE in an unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MulteFire.
  • the wireless communications system 100 may further include a millimeter wave (mmW) base station 180 that may operate in mmW frequencies and/or near mmW frequencies in communication with a UE 182 .
  • Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to as a millimeter wave.
  • Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters.
  • the super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave.
  • the mmW base station 180 and the UE 182 may utilize beamforming (transmit and/or receive) over a mmW communication link 184 to compensate for the extremely high path loss and short range.
  • one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be appreciated that the foregoing illustrations are merely examples and should not be construed to limit the various aspects disclosed herein.
  • Transmit beamforming is a technique for focusing an RF signal in a specific direction.
  • a network node e.g., a base station
  • transmit beamforming the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal for the receiving device(s).
  • a network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that are broadcasting the RF signal.
  • a network node may use an array of antennas (referred to as a “phased array” or an “antenna array”) that creates a beam of RF waves that can be “steered” to point in different directions, without actually moving the antennas.
  • the RF current from the transmitter is fed to the individual antennas with the correct phase relationship so that the radio waves from the separate antennas add together to increase the radiation in a desired direction, while cancelling to suppress radiation in undesired directions.
  • Transmit beams may be quasi-co-located, meaning that they appear to the receiver (e.g., a UE) as having the same parameters, regardless of whether or not the transmitting antennas of the network node themselves are physically co-located.
  • the receiver e.g., a UE
  • QCL relation of a given type means that certain parameters about a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam.
  • the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of a second reference RF signal transmitted on the same channel.
  • the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate the spatial receive parameter of a second reference RF signal transmitted on the same channel.
  • the receiver uses a receive beam to amplify RF signals detected on a given channel.
  • the receiver can increase the gain setting and/or adjust the phase setting of an array of antennas in a particular direction to amplify (e.g., to increase the gain level of) the RF signals received from that direction.
  • a receiver is said to beamform in a certain direction, it means the beam gain in that direction is high relative to the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.) of the RF signals received from that direction.
  • RSRP reference signal received power
  • RSRQ reference signal received quality
  • SINR signal-to-interference-plus-noise ratio
  • Transmit and receive beams may be spatially related.
  • a spatial relation means that parameters for a second beam (e.g., a transmit or receive beam) for a second reference signal can be derived from information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal.
  • a UE may use a particular receive beam to receive a reference downlink reference signal (e.g., synchronization signal block (SSB)) from a base station.
  • the UE can then form a transmit beam for sending an uplink reference signal (e.g., sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.
  • an uplink reference signal e.g., sounding reference signal (SRS)
  • a “downlink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. If the UE is forming the downlink beam, however, it is a receive beam to receive the downlink reference signal.
  • an “uplink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the uplink beam, it is an uplink receive beam, and if a UE is forming the uplink beam, it is an uplink transmit beam.
  • FR1 frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles.
  • FR2 which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
  • EHF extremely high frequency
  • ITU International Telecommunications Union
  • the frequencies between FR1 and FR2 are often referred to as mid-band frequencies.
  • FR3 frequency range designation 7.125 GHz-24.25 GHz
  • Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies.
  • higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz.
  • three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF band.
  • sub-6 GHz or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies.
  • millimeter wave or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band.
  • the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by a UE 104 / 182 and the cell in which the UE 104 / 182 either performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure.
  • RRC radio resource control
  • the primary carrier carries all common and UE-specific control channels, and may be a carrier in a licensed frequency (however, this is not always the case).
  • a secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once the RRC connection is established between the UE 104 and the anchor carrier and that may be used to provide additional radio resources.
  • the secondary carrier may be a carrier in an unlicensed frequency.
  • the secondary carrier may contain only necessary signaling information and signals, for example, those that are UE-specific may not be present in the secondary carrier, since both primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers.
  • the network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Because a “serving cell” (whether a PCell or an SCell) corresponds to a carrier frequency/component carrier over which some base station is communicating, the term “cell,” “serving cell,” “component carrier,” “carrier frequency,” and the like can be used interchangeably.
  • one of the frequencies utilized by the macro cell base stations 102 may be an anchor carrier (or “PCell”) and other frequencies utilized by the macro cell base stations 102 and/or the mmW base station 180 may be secondary carriers (“SCells”).
  • PCell anchor carrier
  • SCells secondary carriers
  • the simultaneous transmission and/or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission and/or reception rates.
  • two 20 MHz aggregated carriers in a multi-carrier system would theoretically lead to a two-fold increase in data rate (i.e., 40 MHz), compared to that attained by a single 20 MHz carrier.
  • the wireless communications system 100 may further include a UE 164 that may communicate with a macro cell base station 102 over a communication link 120 and/or the mmW base station 180 over a mmW communication link 184 .
  • the macro cell base station 102 may support a PCell and one or more SCells for the UE 164 and the mmW base station 180 may support one or more SCells for the UE 164 .
  • the UE 164 and the UE 182 may be capable of sidelink communication.
  • Sidelink-capable UEs may communicate with base stations 102 over communication links 120 using the Uu interface (i.e., the air interface between a UE and a base station).
  • SL-UEs e.g., UE 164 , UE 182
  • a wireless sidelink (or just “sidelink”) is an adaptation of the core cellular (e.g., LTE, NR) standard that allows direct communication between two or more UEs without the communication needing to go through a base station.
  • Sidelink communication may be unicast or multicast, and may be used for device-to-device (D2D) media-sharing, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, etc.), emergency rescue applications, etc.
  • V2V vehicle-to-vehicle
  • V2X vehicle-to-everything
  • cV2X cellular V2X
  • eV2X enhanced V2X
  • One or more of a group of SL-UEs utilizing sidelink communications may be within the geographic coverage area 110 of a base station 102 .
  • Other SL-UEs in such a group may be outside the geographic coverage area 110 of a base station 102 or be otherwise unable to receive transmissions from a base station 102 .
  • groups of SL-UEs communicating via sidelink communications may utilize a one-to-many (1:M) system in which each SL-UE transmits to every other SL-UE in the group.
  • a base station 102 facilitates the scheduling of resources for sidelink communications.
  • sidelink communications are carried out between SL-UEs without the involvement of a base station 102 .
  • the sidelink 160 may operate over a wireless communication medium of interest, which may be shared with other wireless communications between other vehicles and/or infrastructure access points, as well as other RATs.
  • a “medium” may be composed of one or more time, frequency, and/or space communication resources (e.g., encompassing one or more channels across one or more carriers) associated with wireless communication between one or more transmitter/receiver pairs.
  • the medium of interest may correspond to at least a portion of an unlicensed frequency band shared among various RATs.
  • FIG. 1 only illustrates two of the UEs as SL-UEs (i.e., UEs 164 and 182 ), any of the illustrated UEs may be SL-UEs.
  • UE 182 was described as being capable of beamforming, any of the illustrated UEs, including UE 164 , may be capable of beamforming.
  • SL-UEs are capable of beamforming, they may beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UEs 104 ), towards base stations (e.g., base stations 102 , 180 , small cell 102 ′, access point 150 ), etc.
  • UEs 164 and 182 may utilize beamforming over sidelink 160 .
  • any of the illustrated UEs may receive signals 124 from one or more Earth orbiting space vehicles (SVs) 112 (e.g., satellites).
  • SVs Earth orbiting space vehicles
  • the SVs 112 may be part of a satellite positioning system that a UE 104 can use as an independent source of location information.
  • a satellite positioning system typically includes a system of transmitters (e.g., SVs 112 ) positioned to enable receivers (e.g., UEs 104 ) to determine their location on or above the Earth based, at least in part, on positioning signals (e.g., signals 124 ) received from the transmitters.
  • Such a transmitter typically transmits a signal marked with a repeating pseudo-random noise (PN) code of a set number of chips. While typically located in SVs 112 , transmitters may sometimes be located on ground-based control stations, base stations 102 , and/or other UEs 104 .
  • a UE 104 may include one or more dedicated receivers specifically designed to receive signals 124 for deriving geo location information from the SVs 112 .
  • an SBAS may include an augmentation system(s) that provides integrity information, differential corrections, etc., such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi-functional Satellite Augmentation System (MSAS), the Global Positioning System (GPS) Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and/or the like.
  • WAAS Wide Area Augmentation System
  • GNOS European Geostationary Navigation Overlay Service
  • MSAS Multi-functional Satellite Augmentation System
  • GPS Global Positioning System Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system
  • GAGAN Global Positioning System
  • 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.
  • SVs 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs).
  • NTN non-terrestrial networks
  • an SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in a 5GC.
  • This element would in turn provide access to other elements in the 5G network and ultimately to entities external to the 5G network, such as Internet web servers and other user devices.
  • a UE 104 may receive communication signals (e.g., signals 124 ) from an SV 112 instead of, or in addition to, communication signals from a terrestrial base station 102 .
  • the wireless communications system 100 may further include one or more UEs, such as UE 190 , that connects indirectly to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “sidelinks”).
  • D2D device-to-device
  • P2P peer-to-peer
  • UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which UE 190 may indirectly obtain cellular connectivity) and a D2D P2P link 194 with WLAN STA 152 connected to the WLAN AP 150 (through which UE 190 may indirectly obtain WLAN-based Internet connectivity).
  • the D2D P2P links 192 and 194 may be supported with any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, and so on.
  • FIG. 2 A illustrates an example wireless network structure 200 .
  • a 5GC 210 also referred to as a Next Generation Core (NGC)
  • C-plane control plane
  • U-plane user plane
  • User plane interface (NG-U) 213 and control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210 and specifically to the user plane functions 212 and control plane functions 214 , respectively.
  • an ng-eNB 224 may also be connected to the 5GC 210 via NG-C 215 to the control plane functions 214 and NG-U 213 to user plane functions 212 . Further, ng-eNB 224 may directly communicate with gNB 222 via a backhaul connection 223 .
  • a Next Generation RAN (NG-RAN) 220 may have one or more gNBs 222 , while other configurations include one or more of both ng-eNBs 224 and gNBs 222 . Either (or both) gNB 222 or ng-eNB 224 may communicate with one or more UEs 204 (e.g., any of the UEs described herein).
  • the location server 230 may be in communication with the 5GC 210 to provide location assistance for UE(s) 204 .
  • the location server 230 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server.
  • the location server 230 can be configured to support one or more location services for UEs 204 that can connect to the location server 230 via the core network, 5GC 210 , and/or via the Internet (not illustrated). Further, the location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network (e.g., a third party server, such as an original equipment manufacturer (OEM) server or service server).
  • OEM original equipment manufacturer
  • FIG. 2 B illustrates another example wireless network structure 240 .
  • a 5GC 260 (which may correspond to 5GC 210 in FIG. 2 A ) can be viewed functionally as control plane functions, provided by an access and mobility management function (AMF) 264 , and user plane functions, provided by a user plane function (UPF) 262 , which operate cooperatively to form the core network (i.e., 5GC 260 ).
  • AMF access and mobility management function
  • UPF user plane function
  • the functions of the AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and a session management function (SMF) 266 , transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE 204 and the short message service function (SMSF) (not shown), and security anchor functionality (SEAF).
  • the AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204 , and receives the intermediate key that was established as a result of the UE 204 authentication process.
  • AUSF authentication server function
  • the AMF 264 retrieves the security material from the AUSF.
  • the functions of the AMF 264 also include security context management (SCM).
  • SCM receives a key from the SEAF that it uses to derive access-network specific keys.
  • the functionality of the AMF 264 also includes location services management for regulatory services, transport for location services messages between the UE 204 and a location management function (LMF) 270 (which acts as a location server 230 ), transport for location services messages between the NG-RAN 220 and the LMF 270 , evolved packet system (EPS) bearer identifier allocation for interworking with the EPS, and UE 204 mobility event notification.
  • LMF location management function
  • EPS evolved packet system
  • the AMF 264 also supports functionalities for non-3GPP (Third Generation Partnership Project) access networks.
  • Functions of the UPF 262 include acting as an anchor point for intra-/inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point of interconnect to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for the user plane (e.g., uplink/downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding of one or more “end markers” to the source RAN node.
  • the UPF 262 may also support transfer of location services messages over a user plane between the UE 204 and a location server, such as an SLP 272 .
  • the functions of the SMF 266 include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering at the UPF 262 to route traffic to the proper destination, control of part of policy enforcement and QoS, and downlink data notification.
  • IP Internet protocol
  • the interface over which the SMF 266 communicates with the AMF 264 is referred to as the N11 interface.
  • LMF 270 may be in communication with the 5GC 260 to provide location assistance for UEs 204 .
  • the LMF 270 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server.
  • the LMF 270 can be configured to support one or more location services for UEs 204 that can connect to the LMF 270 via the core network, 5GC 260 , and/or via the Internet (not illustrated).
  • the SLP 272 may support similar functions to the LMF 270 , but whereas the LMF 270 may communicate with the AMF 264 , NG-RAN 220 , and UEs 204 over a control plane (e.g., using interfaces and protocols intended to convey signaling messages and not voice or data), the SLP 272 may communicate with UEs 204 and external clients (e.g., third-party server 274 ) over a user plane (e.g., using protocols intended to carry voice and/or data like the transmission control protocol (TCP) and/or IP).
  • TCP transmission control protocol
  • Yet another optional aspect may include a third-party server 274 , which may be in communication with the LMF 270 , the SLP 272 , the 5GC 260 (e.g., via the AMF 264 and/or the UPF 262 ), the NG-RAN 220 , and/or the UE 204 to obtain location information (e.g., a location estimate) for the UE 204 .
  • the third-party server 274 may be referred to as a location services (LCS) client or an external client.
  • the third-party server 274 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server.
  • User plane interface 263 and control plane interface 265 connect the 5GC 260 , and specifically the UPF 262 and AMF 264 , respectively, to one or more gNBs 222 and/or ng-eNBs 224 in the NG-RAN 220 .
  • the interface between gNB(s) 222 and/or ng-eNB(s) 224 and the AMF 264 is referred to as the “N2” interface
  • the interface between gNB(s) 222 and/or ng-eNB(s) 224 and the UPF 262 is referred to as the “N3” interface.
  • the gNB(s) 222 and/or ng-eNB(s) 224 of the NG-RAN 220 may communicate directly with each other via backhaul connections 223 , referred to as the “Xn-C” interface.
  • One or more of gNBs 222 and/or ng-eNBs 224 may communicate with one or more UEs 204 over a wireless interface, referred to as the “Uu” interface.
  • a gNB 222 may be divided between a gNB central unit (gNB-CU) 226 , one or more gNB distributed units (gNB-DUs) 228 , and one or more gNB radio units (gNB-RUs) 229 .
  • a gNB-CU 226 is a logical node that includes the base station functions of transferring user data, mobility control, radio access network sharing, positioning, session management, and the like, except for those functions allocated exclusively to the gNB-DU(s) 228 . More specifically, the gNB-CU 226 generally host the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB 222 .
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • a gNB-DU 228 is a logical node that generally hosts the radio link control (RLC) and medium access control (MAC) layer of the gNB 222 . Its operation is controlled by the gNB-CU 226 .
  • One gNB-DU 228 can support one or more cells, and one cell is supported by only one gNB-DU 228 .
  • the interface 232 between the gNB-CU 226 and the one or more gNB-DUs 228 is referred to as the “F1” interface.
  • the physical (PHY) layer functionality of a gNB 222 is generally hosted by one or more standalone gNB-RUs 229 that perform functions such as power amplification and signal transmission/reception.
  • a UE 204 communicates with the gNB-CU 226 via the RRC, SDAP, and PDCP layers, with a gNB-DU 228 via the RLC and MAC layers, and with a gNB-RU 229 via the PHY layer.
  • Deployment of communication systems may be arranged in multiple manners with various components or constituent parts.
  • a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, or a network equipment, such as a base station, or one or more units (or one or more components) performing base station functionality may be implemented in an aggregated or disaggregated architecture.
  • a base station such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), a transmit receive point (TRP), or a cell, etc.
  • NB Node B
  • eNB evolved NB
  • 5G NB 5G NB
  • AP access point
  • TRP transmit receive point
  • a cell etc.
  • a base station may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.
  • An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node.
  • a disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).
  • CUs central or centralized units
  • DUs distributed units
  • RUs radio units
  • a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes.
  • the DUs may be implemented to communicate with one or more RUs.
  • Each of the CU, DU and RU also can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
  • Base station-type operation or network design may consider aggregation characteristics of base station functionality.
  • disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)).
  • IAB integrated access backhaul
  • O-RAN open radio access network
  • vRAN also known as a cloud radio access network
  • Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design.
  • the various units of the disaggregated base station, or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.
  • FIG. 2 C illustrates an example disaggregated base station architecture 250 , according to aspects of the disclosure.
  • the disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU 226 ) that can communicate directly with a core network 267 (e.g., 5GC 210 , 5GC 260 ) via a backhaul link, or indirectly with the core network 267 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 259 via an E2 link, or a Non-Real Time (Non-RT) RIC 257 associated with a Service Management and Orchestration (SMO) Framework 255 , or both).
  • CUs central units
  • a CU 280 may communicate with one or more distributed units (DUs) 285 (e.g., gNB-DUs 228 ) via respective midhaul links, such as an F1 interface.
  • the DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229 ) via respective fronthaul links.
  • the RUs 287 may communicate with respective UEs 204 via one or more radio frequency (RF) access links.
  • RF radio frequency
  • the UE 204 may be simultaneously served by multiple RUs 287 .
  • Each of the units may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium.
  • Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units can be configured to communicate with one or more of the other units via the transmission medium.
  • the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units.
  • the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a radio frequency (RF) transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
  • a wireless interface which may include a receiver, a transmitter or transceiver (such as a radio frequency (RF) transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
  • RF radio frequency
  • the CU 280 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 280 .
  • the CU 280 may be configured to handle user plane functionality (i.e., Central Unit—User Plane (CU-UP)), control plane functionality (i.e., Central Unit—Control Plane (CU-CP)), or a combination thereof.
  • CU-UP Central Unit—User Plane
  • CU-CP Central Unit—Control Plane
  • the CU 280 can be logically split into one or more CU-UP units and one or more CU-CP units.
  • the CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration.
  • the CU 280 can be implemented to communicate with the DU 285 , as necessary, for network control and signaling.
  • the DU 285 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 287 .
  • the DU 285 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP).
  • the DU 285 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 285 , or with the control functions hosted by the CU 280 .
  • Lower-layer functionality can be implemented by one or more RUs 287 .
  • an RU 287 controlled by a DU 285 , may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split.
  • the RU(s) 287 can be implemented to handle over the air (OTA) communication with one or more UEs 204 .
  • OTA over the air
  • real-time and non-real-time aspects of control and user plane communication with the RU(s) 287 can be controlled by the corresponding DU 285 .
  • this configuration can enable the DU(s) 285 and the CU 280 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
  • the SMO Framework 255 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements.
  • the SMO Framework 255 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an O1 interface).
  • the SMO Framework 255 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 269 ) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface).
  • a cloud computing platform such as an open cloud (O-Cloud) 269
  • network element life cycle management such as to instantiate virtualized network elements
  • a cloud computing platform interface such as an O2 interface
  • Such virtualized network elements can include, but are not limited to, CUs 280 , DUs 285 , RUs 287 and Near-RT RICs 259 .
  • the SMO Framework 255 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 261 , via an O1 interface. Additionally, in some implementations, the SMO Framework 255 can communicate directly with one or more RUs 287 via an O1 interface.
  • the SMO Framework 255 also may include a Non-RT RIC 257 configured to support functionality of the SMO Framework 255 .
  • the Non-RT RIC 257 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence/Machine Learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 259 .
  • the Non-RT RIC 257 may be coupled to or communicate with (such as via an AI interface) the Near-RT RIC 259 .
  • the Near-RT RIC 259 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 280 , one or more DUs 285 , or both, as well as an O-eNB, with the Near-RT RIC 259 .
  • the Non-RT RIC 257 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 259 and may be received at the SMO Framework 255 or the Non-RT RIC 257 from non-network data sources or from network functions.
  • the Non-RT RIC 257 or the Near-RT RIC 259 may be configured to tune RAN behavior or performance.
  • the Non-RT RIC 257 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 255 (such as reconfiguration via 01 ) or via creation of RAN management policies (such as AI policies).
  • FIGS. 3 A, 3 B, and 3 C illustrate several example components (represented by corresponding blocks) that may be incorporated into a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including the location server 230 and the LMF 270 , or alternatively may be independent from the NG-RAN 220 and/or 5GC 210 / 260 infrastructure depicted in FIGS. 2 A and 2 B , such as a private network) to support the operations described herein.
  • a UE 302 which may correspond to any of the UEs described herein
  • a base station 304 which may correspond to any of the base stations described herein
  • a network entity 306 which may correspond to or embody any of the network functions described herein, including the location server 230 and the LMF 270 , or alternatively may be independent from the NG-RAN
  • these components may be implemented in different types of apparatuses in different implementations (e.g., in an ASIC, in a system-on-chip (SoC), etc.).
  • the illustrated components may also be incorporated into other apparatuses in a communication system.
  • other apparatuses in a system may include components similar to those described to provide similar functionality.
  • a given apparatus may contain one or more of the components.
  • an apparatus may include multiple transceiver components that enable the apparatus to operate on multiple carriers and/or communicate via different technologies.
  • the UE 302 and the base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350 , respectively, providing means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) via one or more wireless communication networks (not shown), such as an NR network, an LTE network, a GSM network, and/or the like.
  • WWAN wireless wide area network
  • the WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356 , respectively, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc., via at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communication medium of interest (e.g., some set of time/frequency resources in a particular frequency spectrum).
  • a wireless communication medium of interest e.g., some set of time/frequency resources in a particular frequency spectrum.
  • the WWAN transceivers 310 and 350 may be variously configured for transmitting and encoding signals 318 and 358 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 318 and 358 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT.
  • the WWAN transceivers 310 and 350 include one or more transmitters 314 and 354 , respectively, for transmitting and encoding signals 318 and 358 , respectively, and one or more receivers 312 and 352 , respectively, for receiving and decoding signals 318 and 358 , respectively.
  • the UE 302 and the base station 304 each also include, at least in some cases, one or more short-range wireless transceivers 320 and 360 , respectively.
  • the short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366 , respectively, and provide means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth®, Zigbee®, Z-Wave®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), ultra-wideband (UWB), etc.) over a wireless communication medium of interest.
  • RAT e.g., WiFi, LTE-D, Bluetooth®, Zigbee®, Z-Wave®, PC
  • the short-range wireless transceivers 320 and 360 may be variously configured for transmitting and encoding signals 328 and 368 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 328 and 368 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT.
  • the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364 , respectively, for transmitting and encoding signals 328 and 368 , respectively, and one or more receivers 322 and 362 , respectively, for receiving and decoding signals 328 and 368 , respectively.
  • the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Bluetooth® transceivers, Zigbee® and/or Z-Wave® transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and/or vehicle-to-everything (V2X) transceivers.
  • the UE 302 and the base station 304 also include, at least in some cases, satellite signal receivers 330 and 370 .
  • the satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376 , respectively, and may provide means for receiving and/or measuring satellite positioning/communication signals 338 and 378 , respectively.
  • the satellite positioning/communication signals 338 and 378 may be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc.
  • the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers
  • the satellite positioning/communication signals 338 and 378 may be communication signals (e.g., carrying control and/or user data) originating from a 5G network.
  • the satellite signal receivers 330 and 370 may comprise any suitable hardware and/or software for receiving and processing satellite positioning/communication signals 338 and 378 , respectively.
  • the satellite signal receivers 330 and 370 may request information and operations as appropriate from the other systems, and, at least in some cases, perform calculations to determine locations of the UE 302 and the base station 304 , respectively, using measurements obtained by any suitable satellite positioning system algorithm.
  • the base station 304 and the network entity 306 each include one or more network transceivers 380 and 390 , respectively, providing means for communicating (e.g., means for transmitting, means for receiving, etc.) with other network entities (e.g., other base stations 304 , other network entities 306 ).
  • the base station 304 may employ the one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 over one or more wired or wireless backhaul links.
  • the network entity 306 may employ the one or more network transceivers 390 to communicate with one or more base station 304 over one or more wired or wireless backhaul links, or with other network entities 306 over one or more wired or wireless core network interfaces.
  • a transceiver may be configured to communicate over a wired or wireless link.
  • a transceiver (whether a wired transceiver or a wireless transceiver) includes transmitter circuitry (e.g., transmitters 314 , 324 , 354 , 364 ) and receiver circuitry (e.g., receivers 312 , 322 , 352 , 362 ).
  • a transceiver may be an integrated device (e.g., embodying transmitter circuitry and receiver circuitry in a single device) in some implementations, may comprise separate transmitter circuitry and separate receiver circuitry in some implementations, or may be embodied in other ways in other implementations.
  • the transmitter circuitry and receiver circuitry of a wired transceiver may be coupled to one or more wired network interface ports.
  • Wireless transmitter circuitry e.g., transmitters 314 , 324 , 354 , 364
  • wireless receiver circuitry may include or be coupled to a plurality of antennas (e.g., antennas 316 , 326 , 356 , 366 ), such as an antenna array, that permits the respective apparatus (e.g., UE 302 , base station 304 ) to perform receive beamforming, as described herein.
  • the transmitter circuitry and receiver circuitry may share the same plurality of antennas (e.g., antennas 316 , 326 , 356 , 366 ), such that the respective apparatus can only receive or transmit at a given time, not both at the same time.
  • a wireless transceiver e.g., WWAN transceivers 310 and 350 , short-range wireless transceivers 320 and 360
  • NLM network listen module
  • the various wireless transceivers e.g., transceivers 310 , 320 , 350 , and 360 , and network transceivers 380 and 390 in some implementations
  • wired transceivers e.g., network transceivers 380 and 390 in some implementations
  • a transceiver at least one transceiver
  • wired transceivers e.g., network transceivers 380 and 390 in some implementations
  • backhaul communication between network devices or servers will generally relate to signaling via a wired transceiver
  • wireless communication between a UE (e.g., UE 302 ) and a base station (e.g., base station 304 ) will generally relate to signaling via a wireless transceiver.
  • the UE 302 , the base station 304 , and the network entity 306 also include other components that may be used in conjunction with the operations as disclosed herein.
  • the UE 302 , the base station 304 , and the network entity 306 include one or more processors 332 , 384 , and 394 , respectively, for providing functionality relating to, for example, wireless communication, and for providing other processing functionality.
  • the processors 332 , 384 , and 394 may therefore provide means for processing, such as means for determining, means for calculating, means for receiving, means for transmitting, means for indicating, etc.
  • the processors 332 , 384 , and 394 may include, for example, one or more general purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuitry, or various combinations thereof.
  • the UE 302 , the base station 304 , and the network entity 306 include memory circuitry implementing memories 340 , 386 , and 396 (e.g., each including a memory device), respectively, for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, and so on).
  • the memories 340 , 386 , and 396 may therefore provide means for storing, means for retrieving, means for maintaining, etc.
  • the UE 302 , the base station 304 , and the network entity 306 may include positioning component 342 , 388 , and 398 , respectively.
  • the positioning component 342 , 388 , and 398 may be hardware circuits that are part of or coupled to the processors 332 , 384 , and 394 , respectively, that, when executed, cause the UE 302 , the base station 304 , and the network entity 306 to perform the functionality described herein.
  • the positioning component 342 , 388 , and 398 may be external to the processors 332 , 384 , and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.).
  • the positioning component 342 , 388 , and 398 may be memory modules stored in the memories 340 , 386 , and 396 , respectively, that, when executed by the processors 332 , 384 , and 394 (or a modem processing system, another processing system, etc.), cause the UE 302 , the base station 304 , and the network entity 306 to perform the functionality described herein.
  • FIG. 3 A illustrates possible locations of the positioning component 342 , which may be, for example, part of the one or more WWAN transceivers 310 , the memory 340 , the one or more processors 332 , or any combination thereof, or may be a standalone component.
  • FIG. 3 A illustrates possible locations of the positioning component 342 , which may be, for example, part of the one or more WWAN transceivers 310 , the memory 340 , the one or more processors 332 , or any combination thereof, or may be a standalone component.
  • FIG. 3 B illustrates possible locations of the positioning component 388 , which may be, for example, part of the one or more WWAN transceivers 350 , the memory 386 , the one or more processors 384 , or any combination thereof, or may be a standalone component.
  • FIG. 3 C illustrates possible locations of the positioning component 398 , which may be, for example, part of the one or more network transceivers 390 , the memory 396 , the one or more processors 394 , or any combination thereof, or may be a standalone component.
  • the UE 302 may include one or more sensors 344 coupled to the one or more processors 332 to provide means for sensing or detecting movement and/or orientation information that is independent of motion data derived from signals received by the one or more WWAN transceivers 310 , the one or more short-range wireless transceivers 320 , and/or the satellite signal receiver 330 .
  • the sensor(s) 344 may include an accelerometer (e.g., a micro-electrical mechanical systems (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric pressure altimeter), and/or any other type of movement detection sensor.
  • MEMS micro-electrical mechanical systems
  • the senor(s) 344 may include a plurality of different types of devices and combine their outputs in order to provide motion information.
  • the sensor(s) 344 may use a combination of a multi-axis accelerometer and orientation sensors to provide the ability to compute positions in two-dimensional (2D) and/or three-dimensional (3D) coordinate systems.
  • the UE 302 includes a user interface 346 providing means for providing indications (e.g., audible and/or visual indications) to a user and/or for receiving user input (e.g., upon user actuation of a sensing device such a keypad, a touch screen, a microphone, and so on).
  • a user interface 346 providing means for providing indications (e.g., audible and/or visual indications) to a user and/or for receiving user input (e.g., upon user actuation of a sensing device such a keypad, a touch screen, a microphone, and so on).
  • the base station 304 and the network entity 306 may also include user interfaces.
  • IP packets from the network entity 306 may be provided to the processor 384 .
  • the one or more processors 384 may implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer.
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • the one or more processors 384 may provide RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.
  • RRC layer functionality associated with broadcasting of system
  • the transmitter 354 and the receiver 352 may implement Layer-1 (L1) functionality associated with various signal processing functions.
  • Layer-1 which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing.
  • FEC forward error correction
  • the transmitter 354 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)).
  • BPSK binary phase-shift keying
  • QPSK quadrature phase-shift keying
  • M-PSK M-phase-shift keying
  • M-QAM M-quadrature amplitude modulation
  • Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream.
  • OFDM symbol stream is spatially precoded to produce multiple spatial streams.
  • Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, as well as for spatial processing.
  • the channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 302 .
  • Each spatial stream may then be provided to one or more different antennas 356 .
  • the transmitter 354 may modulate an RF carrier with a respective spatial stream for transmission.
  • the receiver 312 receives a signal through its respective antenna(s) 316 .
  • the receiver 312 recovers information modulated onto an RF carrier and provides the information to the one or more processors 332 .
  • the transmitter 314 and the receiver 312 implement Layer-1 functionality associated with various signal processing functions.
  • the receiver 312 may perform spatial processing on the information to recover any spatial streams destined for the UE 302 . If multiple spatial streams are destined for the UE 302 , they may be combined by the receiver 312 into a single OFDM symbol stream.
  • the receiver 312 then converts the OFDM symbol stream from the time-domain to the frequency domain using a fast Fourier transform (FFT).
  • FFT fast Fourier transform
  • the symbols on each subcarrier, and the reference signal are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 304 . These soft decisions may be based on channel estimates computed by a channel estimator. The soft decisions are then decoded and de-interleaved to recover the data and control signals that were originally transmitted by the base station 304 on the physical channel. The data and control signals are then provided to the one or more processors 332 , which implements Layer-3 (L3) and Layer-2 (L2) functionality.
  • L3 Layer-3
  • L2 Layer-2
  • the one or more processors 332 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the core network.
  • the one or more processors 332 are also responsible for error detection.
  • the one or more processors 332 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.
  • RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting
  • Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station 304 may be used by the transmitter 314 to select the appropriate coding and modulation schemes, and to facilitate spatial processing.
  • the spatial streams generated by the transmitter 314 may be provided to different antenna(s) 316 .
  • the transmitter 314 may modulate an RF carrier with a respective spatial stream for transmission.
  • the uplink transmission is processed at the base station 304 in a manner similar to that described in connection with the receiver function at the UE 302 .
  • the receiver 352 receives a signal through its respective antenna(s) 356 .
  • the receiver 352 recovers information modulated onto an RF carrier and provides the information to the one or more processors 384 .
  • the one or more processors 384 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 302 .
  • IP packets from the one or more processors 384 may be provided to the core network.
  • the one or more processors 384 are also responsible for error detection.
  • FIGS. 3 A, 3 B, and 3 C For convenience, the UE 302 , the base station 304 , and/or the network entity 306 are shown in FIGS. 3 A, 3 B, and 3 C as including various components that may be configured according to the various examples described herein. It will be appreciated, however, that the illustrated components may have different functionality in different designs. In particular, various components in FIGS. 3 A to 3 C are optional in alternative configurations and the various aspects include configurations that may vary due to design choice, costs, use of the device, or other considerations. For example, in case of FIG.
  • a particular implementation of UE 302 may omit the WWAN transceiver(s) 310 (e.g., a wearable device or tablet computer or PC or laptop may have Wi-Fi and/or Bluetooth capability without cellular capability), or may omit the short-range wireless transceiver(s) 320 (e.g., cellular-only, etc.), or may omit the satellite signal receiver 330 , or may omit the sensor(s) 344 , and so on.
  • WWAN transceiver(s) 310 e.g., a wearable device or tablet computer or PC or laptop may have Wi-Fi and/or Bluetooth capability without cellular capability
  • the short-range wireless transceiver(s) 320 e.g., cellular-only, etc.
  • satellite signal receiver 330 e.g., cellular-only, etc.
  • a particular implementation of the base station 304 may omit the WWAN transceiver(s) 350 (e.g., a Wi-Fi “hotspot” access point without cellular capability), or may omit the short-range wireless transceiver(s) 360 (e.g., cellular-only, etc.), or may omit the satellite signal receiver 370 , and so on.
  • WWAN transceiver(s) 350 e.g., a Wi-Fi “hotspot” access point without cellular capability
  • the short-range wireless transceiver(s) 360 e.g., cellular-only, etc.
  • satellite signal receiver 370 e.g., satellite signal receiver
  • the various components of the UE 302 , the base station 304 , and the network entity 306 may be communicatively coupled to each other over data buses 334 , 382 , and 392 , respectively.
  • the data buses 334 , 382 , and 392 may form, or be part of, a communication interface of the UE 302 , the base station 304 , and the network entity 306 , respectively.
  • the data buses 334 , 382 , and 392 may provide communication between them.
  • FIGS. 3 A, 3 B, and 3 C may be implemented in various ways.
  • the components of FIGS. 3 A, 3 B, and 3 C may be implemented in one or more circuits such as, for example, one or more processors and/or one or more ASICs (which may include one or more processors).
  • each circuit may use and/or incorporate at least one memory component for storing information or executable code used by the circuit to provide this functionality.
  • some or all of the functionality represented by blocks 310 to 346 may be implemented by processor and memory component(s) of the UE 302 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components).
  • some or all of the functionality represented by blocks 350 to 388 may be implemented by processor and memory component(s) of the base station 304 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). Also, some or all of the functionality represented by blocks 390 to 398 may be implemented by processor and memory component(s) of the network entity 306 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). For simplicity, various operations, acts, and/or functions are described herein as being performed “by a UE,” “by a base station,” “by a network entity,” etc.
  • the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be distinct from a network operator or operation of the cellular network infrastructure (e.g., NG RAN 220 and/or 5GC 210 / 260 ). For example, the network entity 306 may be a component of a private network that may be configured to communicate with the UE 302 via the base station 304 or independently from the base station 304 (e.g., over a non-cellular communication link, such as WiFi).
  • a non-cellular communication link such as WiFi
  • NR supports a number of cellular network-based positioning technologies, including downlink-based, uplink-based, and downlink-and-uplink-based positioning methods.
  • Downlink-based positioning methods include observed time difference of arrival (OTDOA) in LTE, downlink time difference of arrival (DL-TDOA) in NR, and downlink angle-of-departure (DL-AoD) in NR.
  • OTDOA observed time difference of arrival
  • DL-TDOA downlink time difference of arrival
  • DL-AoD downlink angle-of-departure
  • FIG. 4 illustrates examples of various positioning methods, according to aspects of the disclosure.
  • a UE measures the differences between the times of arrival (ToAs) of reference signals (e.g., positioning reference signals (PRS)) received from pairs of base stations, referred to as reference signal time difference (RSTD) or time difference of arrival (TDOA) measurements, and reports them to a positioning entity. More specifically, the UE receives the identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in assistance data (AD). The UE then measures the RSTD between the reference base station and each of the non-reference base stations. Based on the known locations of the involved base stations and the RSTD measurements, the positioning entity (e.g., the UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the UE's location.
  • ToAs times of arrival
  • PRS positioning reference signals
  • RSTD time difference
  • TDOA time difference of arrival
  • the positioning entity uses a measurement report from the UE of received signal strength measurements of multiple downlink transmit beams to determine the angle(s) between the UE and the transmitting base station(s). The positioning entity can then estimate the location of the UE based on the determined angle(s) and the known location(s) of the transmitting base station(s).
  • Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle-of-arrival (UL-AoA).
  • UL-TDOA is similar to DL-TDOA, but is based on uplink reference signals (e.g., sounding reference signals (SRS)) transmitted by the UE to multiple base stations.
  • uplink reference signals e.g., sounding reference signals (SRS)
  • SRS sounding reference signals
  • a UE transmits one or more uplink reference signals that are measured by a reference base station and a plurality of non-reference base stations.
  • Each base station reports the reception time (referred to as the relative time of arrival (RTOA)) of the reference signal(s) to a positioning entity (e.g., a location server) that knows the locations and relative timing of the involved base stations.
  • a positioning entity e.g., a location server
  • the positioning entity can estimate the location of the UE using TDOA.
  • one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from a UE on one or more uplink receive beams.
  • the positioning entity uses the signal strength measurements and the angle(s) of the receive beam(s) to determine the angle(s) between the UE and the base station(s). Based on the determined angle(s) and the known location(s) of the base station(s), the positioning entity can then estimate the location of the UE.
  • uplink reference signals e.g., SRS
  • 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”).
  • E-CID enhanced cell-ID
  • RTT multi-round-trip-time
  • a first entity e.g., a base station or a UE
  • a second entity e.g., a UE or base station
  • a second RTT-related signal e.g., an SRS or PRS
  • Each entity measures the time difference between the time of arrival (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal.
  • ToA time of arrival
  • This time difference is referred to as a reception-to-transmission (Rx-Tx) time difference.
  • the Rx-Tx time difference measurement may be made, or may be adjusted, to include only a time difference between nearest slot boundaries for the received and transmitted signals.
  • Both entities may then send their Rx-Tx time difference measurement to a location server (e.g., an LMF 270 ), which calculates the round trip propagation time (i.e., RTT) between the two entities from the two Rx-Tx time difference measurements (e.g., as the sum of the two Rx-Tx time difference measurements).
  • a location server e.g., an LMF 270
  • RTT round trip propagation time
  • one entity may send its Rx-Tx time difference measurement to the other entity, which then calculates the RTT.
  • the distance between the two entities can be determined from the RTT and the known signal speed (e.g., the speed of light).
  • a first entity e.g., a UE or base station
  • multiple second entities e.g., multiple base stations or UEs
  • RTT and multi-RTT methods can be combined with other positioning techniques, such as UL-AoA and DL-AoD, to improve location accuracy, as illustrated by scenario 440 .
  • the E-CID positioning method is based on radio resource management (RRM) measurements.
  • RRM radio resource management
  • the UE reports the serving cell ID, the timing advance (TA), and the identifiers, estimated timing, and signal strength of detected neighbor base stations.
  • the location of the UE is then estimated based on this information and the known locations of the base station(s).
  • a location server may provide assistance data (AD) to the UE.
  • the assistance data may include identifiers of the base stations (or the cells/TRPs of the base stations) from which to measure reference signals, the reference signal configuration parameters (e.g., the number of consecutive slots including PRS, periodicity of the consecutive slots including PRS, muting sequence, frequency hopping sequence, reference signal identifier, reference signal bandwidth, etc.), and/or other parameters applicable to the particular positioning method.
  • the assistance data may originate directly from the base stations themselves (e.g., in periodically broadcasted overhead messages, etc.).
  • the UE may be able to detect neighbor network nodes itself without the use of assistance data.
  • the assistance data may further include an expected RSTD value and an associated uncertainty, or search window, around the expected RSTD.
  • the value range of the expected RSTD may be +/ ⁇ 500 microseconds ( ⁇ s).
  • the value range for the uncertainty of the expected RSTD may be +/ ⁇ 32 ⁇ s.
  • the value range for the uncertainty of the expected RSTD may be +/ ⁇ 8 ⁇ s.
  • a location estimate may be referred to by other names, such as a position estimate, location, position, position fix, fix, or the like.
  • a location estimate may be geodetic and comprise coordinates (e.g., latitude, longitude, and possibly altitude) or may be civic and comprise a street address, postal address, or some other verbal description of a location.
  • a location estimate may further be defined relative to some other known location or defined in absolute terms (e.g., using latitude, longitude, and possibly altitude).
  • a location estimate may include an expected error or uncertainty (e.g., by including an area or volume within which the location is expected to be included with some specified or default level of confidence).
  • FIG. 5 is a diagram 500 illustrating an example frame structure, according to aspects of the disclosure.
  • the frame structure may be a downlink or uplink frame structure.
  • Other wireless communications technologies may have different frame structures and/or different channels.
  • 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.
  • OFDM orthogonal frequency-division multiplexing
  • SC-FDM single-carrier frequency division multiplexing
  • OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data.
  • modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM.
  • the spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth.
  • the spacing of the subcarriers may be 15 kilohertz (kHz) and the minimum resource allocation (resource block) may be 12 subcarriers (or 180 kHz). Consequently, the nominal fast Fourier transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048 for system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively.
  • the system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively.
  • LTE supports a single numerology (subcarrier spacing (SCS), symbol length, etc.).
  • p subcarrier spacing
  • 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)
  • the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50.
  • For 120 kHz SCS ( ⁇ 3), there are eight slots per subframe, 80 slots per frame, the slot duration is 0.125 ms, the symbol duration is 8.33 ⁇ s, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 400.
  • For 240 kHz SCS ( ⁇ 4), there are 16 slots per subframe, 160 slots per frame, the slot duration is 0.0625 ms, the symbol duration is 4.17 ⁇ s, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 800.
  • a numerology of 15 kHz is used.
  • a 10 ms frame is divided into 10 equally sized subframes of 1 ms each, and each subframe includes one time slot.
  • time is represented horizontally (on the X axis) with time increasing from left to right, while frequency is represented vertically (on the Y axis) with frequency increasing (or decreasing) from bottom to top.
  • a resource grid may be used to represent time slots, each time slot including one or more time-concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain.
  • the resource grid is further divided into multiple resource elements (REs).
  • An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain.
  • an RB may contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs.
  • an RB may contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs.
  • the number of bits carried by each RE depends on the modulation scheme.
  • the REs may carry reference (pilot) signals (RS).
  • the reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSBs), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communication.
  • PRS positioning reference signals
  • TRS tracking reference signals
  • PTRS phase tracking reference signals
  • CRS cell-specific reference signals
  • CSI-RS channel state information reference signals
  • DMRS demodulation reference signals
  • PSS primary synchronization signals
  • SSS secondary synchronization signals
  • SSBs synchronization signal blocks
  • SRS sounding reference signals
  • a collection of resource elements (REs) that are used for transmission of PRS is referred to as a “PRS resource.”
  • the collection of resource elements can span multiple PRBs in the frequency domain and ‘N’ (such as 1 or more) consecutive symbol(s) within a slot in the time domain.
  • N such as 1 or more
  • a PRS resource occupies consecutive PRBs in the frequency domain.
  • a comb size ‘N’ represents the subcarrier spacing (or frequency/tone spacing) within each symbol of a PRS resource configuration.
  • PRS are transmitted in every Nth subcarrier of a symbol of a PRB.
  • REs corresponding to every fourth subcarrier such as subcarriers 0, 4, 8 are used to transmit PRS of the PRS resource.
  • comb sizes of comb-2, comb-4, comb-6, and comb-12 are supported for DL-PRS.
  • FIG. 5 illustrates an example PRS resource configuration for comb-4 (which spans four symbols). That is, the locations of the shaded REs (labeled “R”) indicate a comb-4 PRS resource configuration.
  • a DL-PRS resource may span 2, 4, 6, or 12 consecutive symbols within a slot with a fully frequency-domain staggered pattern.
  • a DL-PRS resource can be configured in any higher layer configured downlink or flexible (FL) symbol of a slot.
  • FL downlink or flexible
  • EPRE energy per resource element
  • 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 the example of FIG.
  • 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 ⁇
  • 12-symbol comb-12 ⁇ 0, 6, 3, 9, 1, 7, 4, 10, 2, 8, 5, 11 ⁇ .
  • a “PRS resource set” is a set of PRS resources used for the transmission of PRS signals, where each PRS resource has a PRS resource ID.
  • the PRS resources in a PRS resource set are associated with the same TRP.
  • a PRS resource set is identified by a PRS resource set ID and is associated with a particular TRP (identified by a TRP ID).
  • the PRS resources in a PRS resource set have the same periodicity, a common muting pattern configuration, and the same repetition factor (such as “PRS-ResourceRepetitionFactor”) across slots.
  • the periodicity is the time from the first set repetition of the first PRS resource of a first PRS instance to the same first repetition of the same first PRS resource of the next PRS instance.
  • the repetition factor may have a length selected from ⁇ 1, 2, 4, 6, 8, 16, 32 ⁇ slots.
  • 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 of a PRS resource set may be transmitted on a different beam, and as such, a “PRS resource,” or simply “resource,” also can be referred to as a “beam.” Note that this does not have any implications on whether the TRPs and the beams on which PRS are transmitted are known to the UE.
  • a “PRS instance” or “PRS occasion” is one instance of a periodically repeated time window (such as a group of one or more consecutive slots) where PRS are expected to be transmitted.
  • a PRS occasion also may be referred to as a “PRS positioning occasion,” a “PRS positioning instance, a “positioning occasion,” “a positioning instance,” a “positioning repetition,” or simply an “occasion,” an “instance,” or a “repetition.”
  • a “positioning frequency layer” (also referred to simply as a “frequency layer”) is a collection of one or more PRS resource sets across one or more TRPs that have the same values for certain parameters. Specifically, the collection of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning all numerologies 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 start PRB (and center frequency), and the same comb-size.
  • CP subcarrier spacing and cyclic prefix
  • 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 channel used for transmission and reception.
  • the downlink PRS bandwidth may have a granularity of four PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs.
  • up to four frequency layers have been defined, and up to two PRS resource sets may be configured per TRP per frequency layer.
  • a frequency layer is somewhat like the concept of component carriers and bandwidth parts (BWPs), but different in that component carriers and BWPs are used by one base station (or a macro cell base station and a small cell base station) to transmit data channels, while frequency layers are used by several (usually three or more) base stations to transmit PRS.
  • a UE may indicate the number of frequency layers it can support when it sends the network its positioning capabilities, such as during an LTE positioning protocol (LPP) session. For example, a UE may indicate whether it can support one or four positioning frequency layers.
  • LPP LTE positioning protocol
  • positioning reference signal generally refer to specific reference signals that are used for positioning in NR and LTE systems.
  • the terms “positioning reference signal” and “PRS” may also refer to any type of reference signal that can be used for positioning, such as but not limited to, PRS as defined in LTE and NR, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc.
  • the terms “positioning reference signal” and “PRS” may refer to downlink, uplink, or sidelink positioning reference signals, unless otherwise indicated by the context.
  • a downlink positioning reference signal may be referred to as a “DL-PRS”
  • an uplink positioning reference signal e.g., an SRS-for-positioning, PTRS
  • a sidelink positioning reference signal may be referred to as an “SL-PRS.”
  • the signals may be prepended with “DL,” “UL,” or “SL” to distinguish the direction.
  • DL-DMRS is different from “DL-DMRS.”
  • FIG. 6 is a graph 600 representing the channel estimate of a multipath channel between a receiver device (e.g., any 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 disclosure.
  • the channel estimate represents the intensity 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 the channel energy response (CER), channel impulse response (CIR), or power delay profile (PDP) of the channel.
  • RF radio frequency
  • 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 to the propagation characteristics of the RF signal (e.g., reflection, refraction, etc.).
  • the receiver detects/measures multiple (four) clusters of channel taps.
  • Each channel tap represents a multipath that an RF signal followed between the transmitter and the receiver. That is, a channel tap represents the arrival of an RF signal on a multipath.
  • Each cluster of channel taps indicates that the corresponding multipaths followed essentially the same path. There may be different clusters due to the RF signal being transmitted on different transmit beams (and therefore at different angles), or because of the propagation characteristics of RF signals (e.g., potentially following different paths due to reflections), or both.
  • All of the clusters of channel taps for a given RF signal represent the multipath channel (or simply channel) between the transmitter and receiver.
  • the receiver receives a first cluster of two RF signals on channel taps at time T 1 , a second cluster of five RF signals on channel taps at time T 2 , a third cluster of five RF signals on channel taps at time T 3 , and a fourth cluster of four RF signals on channel taps at time T 4 .
  • the first cluster of RF signals at time T 1 arrives first, it is assumed to correspond to the RF signal transmitted on the transmit beam aligned with the line-of-sight (LOS), or the shortest, path.
  • LOS line-of-sight
  • the third cluster at time T 3 is comprised of the strongest RF signals, and may correspond to, for example, the RF signal transmitted on a transmit beam aligned with a non-line-of-sight (NLOS) path.
  • NLOS non-line-of-sight
  • Machine learning 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 generation of positioning models for processing of reference signals for positioning (e.g., PRS), such as feature extraction, reporting of reference signal measurements (e.g., selecting which extracted features to report), and so on.
  • PRS reference signals for positioning
  • feature extraction e.g., feature extraction
  • reporting of reference signal measurements e.g., selecting which extracted features to report
  • ML models are generally categorized as either supervised or unsupervised.
  • a supervised model may further be sub-categorized as either a regression or classification model.
  • Supervised learning involves learning a function that maps an input to an output based on example input-output pairs. For example, given a training dataset with two variables of age (input) and height (output), a supervised learning model could be generated to predict the height of a person based on their age. In regression models, the output is continuous.
  • a regression model is a linear regression, which simply attempts to find a line that best fits the data. Extensions of linear regression include multiple linear regression (e.g., finding a plane of best fit) and polynomial regression (e.g., finding a curve of best fit).
  • ML model Another example of an ML model is a decision tree model.
  • a decision tree model a tree structure is defined with a plurality of nodes. Decisions are used to move from a root node at the top of the decision tree to a leaf node at the bottom of the decision tree (i.e., a node with no further child nodes). Generally, a higher number of nodes in the decision tree model is correlated with higher decision accuracy.
  • Random forests are an ensemble learning technique that builds off of decision trees. Random forests involve creating multiple decision trees using bootstrapped datasets 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 of the predictions of each decision tree. By relying on a “majority wins” model, the risk of error from an individual tree is reduced.
  • a neural network is essentially a network of mathematical equations. Neural networks accept one or more input variables, and by going through a network of equations, result in one or more output variables. Put another way, a neural network takes in a vector of inputs and returns a vector of outputs.
  • FIG. 7 illustrates an example neural network 700 , according to aspects of the disclosure.
  • the neural network 700 includes an input layer ‘i’ that receives ‘n’ (one or more) inputs (illustrated as “Input 1 ,” “Input 2 ,” and “Input n”), one or more hidden layers (illustrated as hidden layers ‘h 1 ,’ ‘h 2 ,’ and ‘h 3 ’) for processing the inputs from the input layer, and an output layer ‘o’ that provides ‘m’ (one or more) outputs (labeled “Output 1 ” and “Output m”).
  • the number of inputs ‘n,’ hidden layers ‘h,’ and outputs ‘m’ may be the same or different.
  • the hidden layers ‘h’ may include linear function(s) and/or activation function(s) that the nodes (illustrated as circles) of each successive hidden layer process from the nodes of the previous hidden layer.
  • a classification model In classification models, the output is discrete.
  • logistic regression is similar to linear regression but is used to model the probability of a finite number of outcomes, typically two. In essence, a logistic equation is created in such a way that the output values can only be between ‘0’ and ‘1.’
  • a classification model is a support vector machine. For example, for two classes of data, a support vector machine will find a hyperplane or a boundary between the two classes of data that maximizes the margin between the two classes. There are many planes that can separate the two classes, but only one plane can maximize the margin or distance between the classes.
  • Na ⁇ ve Bayes which is based on Bayes Theorem.
  • Other examples of classification models include decision tree, random forest, and neural network, similar to the examples described above except that the output is discrete rather than continuous.
  • unsupervised learning is used to draw inferences and find patterns from input data without references to labeled outcomes.
  • Two examples of unsupervised learning models include clustering and dimensionality reduction.
  • Clustering is an unsupervised technique that involves the grouping, or clustering, of data points. Clustering is frequently used for customer segmentation, fraud detection, and document classification. Common clustering techniques include k-means clustering, hierarchical clustering, mean shift clustering, and density-based clustering.
  • PCA principal component analysis
  • an ML module e.g., implemented by a processing system, such as processors 332 , 384 , or 394
  • a processing system such as processors 332 , 384 , or 394
  • an output data set e.g., a set of possible or likely candidate locations of the various target UEs
  • NR supports RF fingerprint (RFFP)-based positioning, a type of positioning and localization technique that utilizes RFFPs captured by mobile devices to determine the locations of the mobile devices.
  • An RFFP may be a histogram of a received signal strength indicator (RSSI), a CER, a CIR, a PDP, or a channel frequency response (CFR).
  • RSSI received signal strength indicator
  • CER channel frequency response
  • CFR channel frequency response
  • An RFFP may represent a single channel received from a transmitter (e.g., a PRS), all channels received from a particular transmitter, or all channels detectable at the receiver.
  • a transmitter e.g., a PRS
  • all channels received from a particular transmitter e.g., all channels received from a particular transmitter, or all channels detectable at the receiver.
  • the RFFP(s) measured by a mobile device e.g., a UE
  • the locations of the transmitter(s) associated with the measured RFFP(s) i.e., the transmitters transmitting the RF signals measured by the mobile device to determine the RFFP(s)
  • an ML model (e.g., neural network 700 ) takes as input the RFFPs of downlink reference signals (e.g., PRS) and outputs the positioning measurement (e.g., ToA, RSTD) or mobile device location corresponding to the inputted RFFPs.
  • the ML model (e.g., neural network 700 ) is trained using the “ground truth” (i.e., known) positioning measurements or mobile device locations as the reference (i.e., expected) output of a training set of RFFPs.
  • an ML model may be trained to determine the RSTD measurement of a pair of TRPs from RFFPs of PRS transmitted by the TRPs.
  • the reference output for training such a model would be the correct (i.e., ground truth) RSTD measurement for the location of the mobile device at the time the mobile device obtained the RFFP measurements of the PRS.
  • the network e.g., location server
  • the network can determine the RSTD that would be expected for the pair of TRPs based on the known location of the mobile device and the known locations of the involved (measured) TRPs.
  • the known location of the mobile device may be determined from multiple reported RSTD measurements and/or any other measurements reported by the mobile device (e.g., GPS measurements).
  • FIG. 8 is a diagram 800 illustrating the use of an ML model for RFFP-based positioning, according to aspects of the disclosure.
  • RFFPs e.g., CERs/CIRs/CFRs
  • the database may be located at the mobile device or a network entity (e.g., a location server), and each RFFP may include measurements of RF signals (or channels or links) transmitted by one or more transmitters, illustrated in FIG. 8 as base stations 1 to N (i.e., “BS 1 ” to “BS N”).
  • the network e.g., the location server
  • the network configures the base stations to transmit downlink reference signals (e.g., PRS) to the mobile device
  • the RFFPs are the CER(s)/CIR(s)/CFR(s) of the configured downlink reference signals detected by the mobile device.
  • PRS downlink reference signals
  • the disclosure describes application of ML positioning models to RFFP measurements, it will be recognized, based on the teachings of the present disclosure, that other types of positioning models may be used in addition to, or as alternatives to ML positioning models.
  • Each measured RFFP is associated with the known location of the mobile device at the time the mobile device measured the RFFP, illustrated in FIG. 8 as positions 1 to L (i.e., “Pos 1 ” to “Pos L”).
  • the mobile device's location may be known via another positioning technique, such as discussed above with reference to FIG. 4 .
  • FIG. 8 illustrates RFFP information for a single mobile device, as will be appreciated, RFFP information for multiple mobile devices can be collected and stored in the database.
  • an ML model (e.g., neural network 700 ) is trained to predict the location of a mobile device based on RFFPs measured by the mobile devices. More specifically, a training set of RFFP measurements is used as input to the ML model and the known locations of the mobile devices when capturing the RFFPs are used as labels.
  • the trained ML model can be used to predict (infer) the location of a mobile device (illustrated as “Pos M”) based on the RFFP(s) currently measured by the mobile device.
  • the network e.g., the location server
  • the mobile device may provide the RFFP measurements to the network for processing.
  • FIG. 8 illustrates using an RFFP-based ML model to estimate the location of a UE
  • the outputs (or extracted features) of the ML model may instead be positioning measurements based on the input RFFPs, such as RSTD measurements, ToA measurements, DL-AoD measurements, etc.
  • FIG. 9 is a diagram 900 illustrating an example inference cycle for UE-based DL-RFFP positioning, according to aspects of the disclosure.
  • the location server e.g., LMF 270
  • the TRP(s) then transmit the configured DL-PRS to the UE, which measures the RFFPs of the DL-PRS.
  • the location server previously trained an ML model for RFFP positioning (labeled “RFFP ML”), as discussed above with reference to FIGS. 7 and 8 .
  • the location server provides the ML model to the UE to perform inferences (e.g., determining a positioning measurement based on the measured RFFPs) during the positioning session.
  • inferences e.g., determining a positioning measurement based on the measured RFFPs
  • the UE inputs the measured RFFPs to the received ML model to obtain the associated positioning measurement(s) (e.g., ToA, RSTD).
  • FIG. 10 illustrates an example call flow 1000 for UE-based DL-RFFP positioning, according to aspects of the disclosure.
  • the UE 204 and LMF 270 perform an LPP positioning capability transfer procedure during which the UE 204 provides its positioning capabilities to the LMF 270 .
  • the LMF 270 provides assistance information to the UE's 204 serving ng-eNB/gNB 222 / 224 and any neighboring ng-eNBs/gNBs 222 / 224 , such as the PRS resource configuration of the DL-PRS to be transmitted to the UE 204 .
  • the UE 204 and LMF 270 perform an LPP assistance data exchange.
  • the LMF 270 provides assistance data to the UE 204 for the positioning session, such as the configuration of the DL-PRS transmitted by the involved ng-eNBs/gNBs 222 / 224 and the ML model to use to report positioning measurements of the DL-PRS.
  • the LMF 270 optionally provides assistance information to the involved ng-eNBs/gNBs 222 / 224 via New Radio positioning protocol type A (NRPPa) messages.
  • 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).
  • the LMF 270 and the UE 204 perform an LPP request/provide location information procedure, during which the UE 204 provides positioning measurements taken of the DL-PRS transmitted by the ng-eNBs/gNBs 222 / 224 .
  • the positioning measurements may be derived by applying the ML model received in the assistance data to the RFFPs of the measured DL-PRS.
  • the UE can be configured with a plurality of positioning models that can be individually applied to RFFP measurements to obtain positioning parameters associated with the location of the UE.
  • a plurality of positioning models that can be individually applied to RFFP measurements to obtain positioning parameters associated with the location of the UE.
  • certain aspects of the disclosure recognize that there are no procedures currently available for determining how the UE selects which of the plurality of positioning models it will use for a positioning session. Further, certain aspects of the disclosure recognize that there are no procedures currently available for signaling which of the plurality of positioning models are used or have been used for a particular positioning session. Accordingly, certain aspects of the disclosure are directed to efficiently selecting and signaling a positioning model from a plurality of positioning models for use during a positioning session.
  • a plurality of positioning models may be configured at the UE.
  • the positioning models may be configured at the start of the positioning session.
  • the plurality of positioning models may be configured by a network server based on the network server's knowledge of the current UE environment, UE area of operation, etc.
  • the UE may be configured with the plurality of positioning models before the start of a positioning session during one or more positioning model configuration operations occurring outside of the positioning session.
  • Such model configuration operations may take place during the manufacture of the UE, during or prior to deployment of the UE, after deployment of the UE but prior to the start of a positioning session, and/or between positioning sessions.
  • each positioning model (or a subset of available positioning models) may be mapped to a positioning model codepoint (PMC) index.
  • the PMC index is used in communications between the UE and network server to reference the mapped positioning model.
  • the network server may indicate which positioning model is to be used by the UE for the positioning session by referencing the corresponding PMC index in a transmission to the UE.
  • the UE may indicate which positioning model was used to obtain position parameters for the positioning session by referencing the corresponding PMC index in a transmission to the network server.
  • the maximum number of positioning models that may be configured at the UE and/or the maximum number of positioning models configured at the UE that can be mapped to the PMC indexes may be specified in a standard. In an aspect, the number of positioning models that are mapped to the PMC indexes may be less than or equal to the total number of positioning models configured at the UE. As such, the positioning models that are mapped to PMC indexes may be a subset of a larger pool of positioning models configured at the UE.
  • FIG. 11 is a diagram 1100 showing one manner of indicating a PMC configuration for mapping positioning models configured at the UE to positioning model codepoint indexes, according to aspects of the disclosure.
  • the UE has been configured with more positioning models than will be mapped to the PMC indexes.
  • the total number of positioning models configured at the UE may be on the order of one hundred, while only four positioning models of the hundred positioning models will be mapped to corresponding PMC indexes.
  • a PMC configuration (e.g., the mapping of the positioning models to the PMC indexes) may be indicated by a bitmap 1104 received from a network server.
  • the positioning models may be mapped to the PMC indexes based on the enabled bits of the bitmap, where the enabled bits of the bitmap indicate which positioning models of the plurality of positioning models is mapped to a sequence of PMC indexes.
  • the bitmap 1104 transmitted by the network server to the UE may have a bitmap size of 100 bits, where each bit position corresponds to a positioning model (e.g., bit 1 corresponds to positioning model 1 , bit 2 corresponds to positioning model 2 , etc.).
  • Bits that are enabled e.g., bits having a value of 1) indicate which positioning models will be used in the PMC configuration.
  • the sequence in which the enabled positioning models are encountered in the bitmap is used to map the positioning model to a corresponding PMC index.
  • Bitmap 1104 may be used to configure the PMC configuration (e.g., PMC index/positioning model mapping) shown in table 1102.
  • the PMC configuration e.g., PMC index/positioning model mapping
  • bits 1 , 7 , 10 , and 12 of the bitmap 1104 are enabled, indicating that positioning models 1 , 7 , 10 , and 12 will be used in the PMC configuration.
  • positioning model 1 is mapped to the first PMC index labeled PMC( 0 )
  • positioning model 7 is mapped to the second PMC index labeled PMC( 1 )
  • positioning model 10 is mapped to the third PMC index labeled PMC( 2 )
  • positioning model 12 is mapped to the fourth PMC index labeled PMC( 3 ).
  • the subset of positioning models that are mapped to the PMC indexes may include all of the plurality of positioning models configured at the UE or less than all of the plurality of positioning models configured at the UE as indicated by the enabled bits of the bitmap. It will be recognized, based on the teachings of the present disclosure, that other manners of indicating the PMC configuration to the UE may be employed, the foregoing bitmap mapping technique being an example of one such manner.
  • the number of bits used to indicate each PMC index may be based on the number of positioning models enabled in the PMC configuration (e.g., codepoint size).
  • each of the plurality of PMC indexes may have a data size of log 2 (codepoint size) bits.
  • the codepoint size is four (e.g., there are four positioning models enabled in the PMC configuration). Therefore, each PMC index may be represented by two bits. If the codepoint size is 1 (e.g., only one positioning model is configured or otherwise enabled at the UE), no UE selection is applied. Instead, the UE defaults to using the same positioning model for all RFFP positioning techniques.
  • a network server may transmit, to the UE, an indication of the PMC index corresponding to the particular positioning model that is to be used by the UE for the positioning session.
  • the network server may select which positioning model is to be used based on various criteria, including knowledge of the positioning environment in which the UE is operating and/or knowledge of the accuracy of the positioning models configured at the UE.
  • the UE may transmit, to the network server, an indication of the PMC index mapped to the positioning model used by the UE to determine the positioning parameters associated with the UEs location.
  • each PMC index may be associated with a positioning model having different sets of positioning measurements as outputs.
  • the PMC configuration provided to the UE by the network server may include the measurements associated with the corresponding PMC index.
  • the UE measures the measurements associated with the selected PMC index.
  • PMC indexes may be used in both UE-based positioning and UE-assisted positioning scenarios.
  • the UE may receive, from the network server, an indication of the PMC index mapped to the positioning model that has been selected by the network server for use in the positioning session.
  • the indication of the PMC index may be transmitted to the UE at the start of the positioning session as part of the LPP exchange.
  • the UE may apply the positioning model mapped to the PMC index to the RFFP measurements obtained by the UE to determine its position.
  • the UE may report 1) the PMC index of the positioning model used to determine its position, 2) the positioning parameters associated with its determined position, or 3) a combination thereof to the network server. The reported information may be used by the network server for model monitoring and/or model management.
  • Selection of the positioning model that is to be used in the UE-based positioning scenario may take place at the UE without input from the network server.
  • the UE may select the positioning model based on channel conditions existing between the UE and one or more of the transmission points (e.g., transmission points transmitting the PRS from which the RFFP measurements are obtained) used in the positioning session.
  • different positioning models may be indicated for use under different channel conditions (e.g., different scattering conditions, different fading conditions, different Doppler shift conditions, different Doppler spread conditions, different power decay conditions, etc.).
  • a given positioning model may be more accurate under high Doppler shift conditions when compared to other positioning models configured at the UE.
  • the UE may select the given positioning model when the Doppler shift conditions meet a Doppler shift threshold.
  • another positioning model may be more suitable for use in high scattering environments when compared to the other positioning models configured at the UE. In such instances, the UE may select that positioning model when the scattering characteristics of the channel exceed a channel scattering threshold.
  • the positioning model mapped to PMC( 0 ) can be suited for large delay-spread channels, whereas the positioning model mapped to PMC( 1 ) may be suited for small delay-spread channels.
  • certain positioning models may be better suited to a combination of different channel conditions and be selected when the combination of channel conditions meet the threshold criteria. Allowing the UE to select the positioning model according to the channel conditions saves the burden of uploading the channel conditions to the network server for positioning model selection.
  • the channel conditions for which a particular positioning model configured at the UE is most suited may be indicated to the UE in various manners.
  • the channel conditions for which one or more of the positioning models is suited may be indicated in metadata associated with the one or more positioning models.
  • the particular positioning index to which a positioning model is mapped may provide an indication of one or more of the channel conditions for which it is most suited.
  • a positioning model configured at the UE that is suitable for high Doppler shift channel conditions may have a standardized PMC index of PMC( 2 ).
  • a positioning model that is configured at the UE that is suitable for high scattering channel conditions may have a standardized PMC index of PMC( 3 ).
  • the network node may configure the PMC indexes and corresponding positioning models based on such a standard.
  • the UE may have a general knowledge of its location and select the positioning model most suitable for that location.
  • the location for which a positioning model is most suitable may be indicated in metadata and/or standardized based on the PMC index to which the positioning model is mapped.
  • the UE may obtain channel state information based on reference signals (e.g., CSI-RS) received from transmission points used in the positioning session.
  • the transmission points may be indicated to the UE in AD provided during the LPP exchange.
  • model channel reference signal can be configured for the purpose of environment detection positioning/model selection.
  • the model channel reference signal need not be used primarily for positioning and may be dedicated (or at least semi-dedicated) to obtaining measurements used for positioning model selection.
  • the model channel reference signal may be a reference signal that is not necessarily used for obtaining positioning measurements from which the location of the UE is determined.
  • the model channel reference signal may be employed in various manners.
  • the model channel reference signal may be received from the transmission points used in the positioning session and indicated in the AD during the LPP exchange.
  • one or more model channel reference signals may be transmitted by the UE and used in a radar-type detection of the positioning environment.
  • the UE may transmit one or more model channel reference signals and determine the channel conditions and/or positioning environment based on one or more environmental reflections of the model channel reference signals received at the UE from the positioning environment. Measurements of the environmental reflections, in turn, may be used by the UE to select the positioning model.
  • the UE may receive a configuration for transmitting the one or more model channel reference signals from a network server.
  • the configuration may indicate 1) a frequency domain resource allocation for the one or more model channel reference signals, 2) a time domain resource allocation for the one or more model channel reference signals, 3) power parameters associated with the one or more model channel reference signals; or 4) any combination thereof.
  • the UE may monitor the performances of the different positioning models under various conditions.
  • the UE may determine, based on the model performance monitoring, that certain positioning models are more accurate than others under different channel conditions, in different areas of operation, etc.
  • the performance and related variables e.g., channel conditions, UE areas, etc.
  • the performance and related variables may be correlated for each positioning model and used to select which of the positioning models are to be used based on the variables determined at the UE.
  • At least one PMC index may be a special PMC index (e.g., PMC( 0 )) that is mapped to a classical positioning technique.
  • the special PMC index may specify the classical positioning technique to be used (e.g., DL-TDOA, DL-AOD, multi-RTT, etc.). Mapping a special PMC index to the classical positioning technique allows the UE to use a classical positioning technique if a determination is made that the classical positioning technique is desirable in lieu of a positioning technique that uses a positioning model or to supplement a positioning technique that uses a positioning model.
  • the decision to use the classical positioning technique may be made at the UE.
  • the decision to use the classical positioning technique may be made at the network server, which signals the appropriate PMC index corresponding to the classical positioning technique.
  • the network server may choose the positioning model used by the UE for UE-assisted positioning.
  • the UE may provide the network server with the positioning measurements provided at the positioning model output and the codepoint index of the positioning model used to obtain the positioning measurements.
  • the network server may configure the positioning models used by the UE based on various factors.
  • the network server may configure the positioning models based on an approximate location of the UE or area in which the UE is operating (e.g., identified by tracking area ID).
  • the network server may select which of the configured positioning models the UE is to use based on lower granularities of the location and/or area.
  • the network server may select which of the positioning models of the configured positioning models the UE is to use based on channel conditions uploaded to the network server.
  • UE channel conditions as seen from different transmission points (e.g., TRPs) obtained at the network server using channel sounding techniques in DL or UL, may be used in the positioning model selection process.
  • the channel sounding may be performed outside the time allocated to the positioning session.
  • FIG. 12 illustrates an example method 1200 of wireless communication performed by a UE, according to aspects of the disclosure.
  • the UE receives a positioning model codepoint (PMC) index of a plurality of PMC indexes, wherein each PMC index of the plurality of PMC indexes is mapped to a corresponding positioning model of at least a subset of a plurality of positioning models configured at the UE.
  • operation 1202 may be performed by the one or more WWAN transceivers 310 , the one or more processors 332 , memory 340 , and/or positioning component 342 , any or all of which may be considered means for performing this operation.
  • the UE applies a positioning model, mapped to the PMC index, to one or more RFFP positioning measurements to obtain one or more position parameters corresponding to the location of the UE during a positioning session.
  • operation 1202 may be performed by the one or more WWAN transceivers 310 , the one or more processors 332 , memory 340 , and/or positioning component 342 , any or all of which may be considered means for performing this operation.
  • a technical advantage of the method 1200 is that the method enables the UE to determine which of a plurality of positioning models the UE will use based on an efficient signaling of the positioning model using a positioning model codepoint index. Also, in certain aspects, the network server may make an initial selection of the models from which the UE may make a final selection of the positioning model that is used for positioning during the positioning session.
  • FIG. 13 illustrates an example method 1300 of wireless communication performed by a UE, according to aspects of the disclosure.
  • the UE applies a selected positioning model to one or more RFFP measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session, wherein the selected positioning model is selected from a plurality of positioning models configured at the UE.
  • operation 1302 may be performed by the one or more WWAN transceivers 310 , the one or more processors 332 , memory 340 , and/or positioning component 342 , any or all of which may be considered means for performing this operation.
  • the UE transmits, to a network server, at least one of the one or more position parameters.
  • operation 1304 may be performed by the one or more WWAN transceivers 310 , the one or more processors 332 , memory 340 , and/or positioning component 342 , any or all of which may be considered means for performing this operation.
  • the UE transmits, to the network server, a positioning model codepoint (PMC) index that is mapped to the selected positioning model, wherein the PMC index is one of a plurality of PMC indexes mapped to corresponding positioning models of at least a subset of the plurality of positioning models configured at the UE.
  • operation 1306 may be performed by the one or more WWAN transceivers 310 , the one or more processors 332 , memory 340 , and/or positioning component 342 , any or all of which may be considered means for performing this operation.
  • a technical advantage of the method 1300 is that the method enables the UE to identify which of a plurality of positioning models the UE uses to determine the position parameters sent to the network server based on an efficient signaling of the positioning model using a positioning model codepoint index. Also, in certain aspects, the network server may make an initial selection of the models from which the UE may make a final selection of the positioning model that is used for positioning during the positioning session.
  • example clauses can also include a combination of the dependent clause aspect(s) with the subject matter of any other dependent clause or independent clause or a combination of any feature with other dependent and independent clauses.
  • the various aspects disclosed herein expressly include these combinations, unless it is explicitly expressed or can be readily inferred that a specific combination is not intended (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor).
  • aspects of a clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause.
  • a method of wireless communication performed by a user equipment comprising: receiving a positioning model codepoint (PMC) index of a plurality of PMC indexes, wherein each PMC index of the plurality of PMC indexes is mapped to a corresponding positioning model of at least a subset of a plurality of positioning models configured at the UE; and applying a positioning model, mapped to the PMC index, to one or more RFFP positioning measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session.
  • PMC positioning model codepoint
  • Clause 2 The method of clause 1, further comprising: receiving the plurality of positioning models from a network server.
  • Clause 3 The method of any of clauses 1 to 2, wherein: the plurality of positioning models is received at the UE during a start of the positioning session.
  • Clause 4 The method of any of clauses 1 to 2, wherein: the plurality of positioning models is configured at the UE before a start of the positioning session during one or more model configuration operations occurring outside of the positioning session.
  • each of the plurality of PMC indexes are configured based on a bitmap received from a network server, wherein bits of the bitmap indicate which positioning models of the plurality of positioning models are mapped to a sequence of PMC indexes.
  • each of the plurality of PMC indexes has a data size of log 2 (codepoint size) bits, wherein the codepoint size corresponds to a number of positioning models in the subset of the plurality of positioning models configured at the UE.
  • Clause 7 The method of any of clauses 1 to 6, wherein: at least one PMC index of the plurality of PMC indexes is mapped to a classical New Radio positioning technique specified by a network server.
  • Clause 8 The method of any of clauses 1 to 7, wherein the position parameters comprise: the location of the UE; one or more position coordinates associated with the location of the UE; one or more positioning measurements associated with the location of the UE; or a combination thereof.
  • Clause 9 The method of any of clauses 1 to 8, wherein: the plurality of positioning models is determined based on an approximate UE location of the UE, a UE area as identified by a tracking area identifier of the UE, or a combination thereof.
  • Clause 10 The method of any of clauses 1 to 9, further comprising: receiving a further PMC index, wherein the further PMC index is mapped to a further positioning model providing a position measurement output that is different than the one or more position parameters provided by the positioning model; and transmitting, to a network server, the position measurement output of the further positioning model.
  • a method of wireless communication performed by a user equipment comprising: applying a selected positioning model to one or more radio frequency fingerprint positioning (RFFP) measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session, wherein the selected positioning model is selected from a plurality of positioning models configured at the UE; transmitting, to a network server, at least one of the one or more position parameters; and transmitting, to the network server, a positioning model codepoint (PMC) index that is mapped to the selected positioning model, wherein the PMC index is one of a plurality of PMC indexes mapped to corresponding positioning models of at least a subset of the plurality of positioning models configured at the UE.
  • RFFP radio frequency fingerprint positioning
  • Clause 12 The method of clause 11, wherein: one or more positioning models of the plurality of positioning models are indicated for use with one or more channel conditions measured by the UE.
  • Clause 13 The method of clause 12, wherein: the selected positioning model is selected based on channel conditions detected by the UE.
  • Clause 14 The method of any of clauses 12 to 13, wherein: the one or more positioning models of the plurality of positioning models are indicated for use with the one or more channel conditions in metadata associated with the one or more positioning models.
  • Clause 15 The method of clause 14, further comprising: receiving assistance data indicating one or more transmission points used in the positioning session; receiving one or more model channel reference signals from the one or more transmission points used in the positioning session; and determining the one or more channel conditions based on measuring the one or more model channel reference signals.
  • Clause 16 The method of clause 15, wherein: the one or more model channel reference signals are received outside of a time allocated to the positioning session; and the one or more channel conditions are determined outside of the time allocated to the positioning session.
  • Clause 18 The method of any of clauses 14 to 17, further comprising: transmitting one or more model channel reference signals; and determining the one or more channel conditions based on receiving one or more environmental reflections of the one or more model channel reference signals received at the UE.
  • Clause 19 The method of clause 18, further comprising: receiving a configuration for transmitting the one or more model channel reference signals.
  • Clause 20 The method of clause 19, wherein the configuration for transmitting the one or more model channel reference signals comprises: a frequency domain resource allocation for the one or more model channel reference signals; a time domain resource allocation for the one or more model channel reference signals; power parameters associated with the one or more model channel reference signals; or any combination thereof.
  • Clause 21 The method of any of clauses 11 to 20, wherein: the plurality of positioning models is configured at the UE during a start of the positioning session.
  • Clause 22 The method of any of clauses 11 to 21, wherein: the plurality of positioning models is configured at the UE before a start of the positioning session during one or more positioning model configuration operations occurring outside of the positioning session.
  • Clause 23 The method of any of clauses 11 to 22, further comprising: receiving, from the network server, a PMC configuration for mapping the plurality of PMC indexes to at least the subset of the plurality of positioning models configured at the UE.
  • each of the plurality of PMC indexes is configured based on a bitmap received from a network server, wherein bits of the bitmap indicate which positioning models of the plurality of positioning models are mapped to a sequence of PMC indexes.
  • Clause 25 The method of any of clauses 11 to 24, wherein: at least one PMC index of the plurality of PMC indexes is mapped to a classical new radio positioning technique specified by a network server.
  • a user equipment comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: receive, via the at least one transceiver, a positioning model codepoint (PMC) index of a plurality of PMC indexes, wherein each PMC index of the plurality of PMC indexes is mapped to a corresponding positioning model of at least a subset of a plurality of positioning models configured at the UE; and apply a positioning model, mapped to the PMC index, to one or more RFFP positioning measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session.
  • PMC positioning model codepoint
  • Clause 28 The UE of clause 27, wherein the at least one processor is further configured to: receive, via the at least one transceiver, the plurality of positioning models from a network server.
  • Clause 29 The UE of any of clauses 27 to 28, wherein: the plurality of positioning models is received at the UE during a start of the positioning session.
  • Clause 30 The UE of any of clauses 27 to 28, wherein: the plurality of positioning models is configured at the UE before a start of the positioning session during one or more model configuration operations occurring outside of the positioning session.
  • each of the plurality of PMC indexes are configured based on a bitmap received from a network server, wherein bits of the bitmap indicate which positioning models of the plurality of positioning models are mapped to a sequence of PMC indexes.
  • each of the plurality of PMC indexes has a data size of log 2 (codepoint size) bits, wherein the codepoint size corresponds to a number of positioning models in the subset of the plurality of positioning models configured at the UE.
  • Clause 33 The UE of any of clauses 27 to 32, wherein: at least one PMC index of the plurality of PMC indexes is mapped to a classical New Radio positioning technique specified by a network server.
  • Clause 35 The UE of any of clauses 27 to 34, wherein: the plurality of positioning models is determined based on an approximate UE location of the UE, a UE area as identified by a tracking area identifier of the UE, or a combination thereof.
  • Clause 36 The UE of any of clauses 27 to 35, wherein the at least one processor is further configured to: receive, via the at least one transceiver, a further PMC index, wherein the further PMC index is mapped to a further positioning model providing a position measurement output that is different than the one or more position parameters provided by the positioning model; and transmit, via the at least one transceiver, to a network server, the position measurement output of the further positioning model.
  • a user equipment comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: apply a selected positioning model to one or more radio frequency fingerprint positioning (RFFP) measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session, wherein the selected positioning model is selected from a plurality of positioning models configured at the UE; transmit, via the at least one transceiver, to a network server, at least one of the one or more position parameters; and transmit, via the at least one transceiver, to the network server, a positioning model codepoint (PMC) index that is mapped to the selected positioning model, wherein the PMC index is one of a plurality of PMC indexes mapped to corresponding positioning models of at least a subset of the plurality of positioning models configured at the UE.
  • RFFP radio frequency fingerprint positioning
  • Clause 38 The UE of clause 37, wherein: one or more positioning models of the plurality of positioning models are indicated for use with one or more channel conditions measured by the UE.
  • Clause 39 The UE of clause 38, wherein: the selected positioning model is selected based on channel conditions detected by the UE.
  • Clause 40 The UE of any of clauses 38 to 39, wherein: the one or more positioning models of the plurality of positioning models are indicated for use with the one or more channel conditions in metadata associated with the one or more positioning models.
  • Clause 41 The UE of clause 40, wherein the at least one processor is further configured to: receive, via the at least one transceiver, assistance data indicating one or more transmission points used in the positioning session; receive, via the at least one transceiver, one or more model channel reference signals from the one or more transmission points used in the positioning session; and determine the one or more channel conditions based on measuring the one or more model channel reference signals.
  • Clause 42 The UE of clause 41, wherein: the one or more model channel reference signals are received outside of a time allocated to the positioning session; and the one or more channel conditions are determined outside of the time allocated to the positioning session.
  • Clause 44 The UE of any of clauses 40 to 43, wherein the at least one processor is further configured to: transmit, via the at least one transceiver, one or more model channel reference signals; and determine the one or more channel conditions based on receiving one or more environmental reflections of the one or more model channel reference signals received at the UE.
  • Clause 45 The UE of clause 44, wherein the at least one processor is further configured to: receive, via the at least one transceiver, a configuration for transmitting the one or more model channel reference signals.
  • Clause 46 The UE of clause 45, wherein the configuration for transmitting the one or more model channel reference signals comprises: a frequency domain resource allocation for the one or more model channel reference signals; a time domain resource allocation for the one or more model channel reference signals; power parameters associated with the one or more model channel reference signals; or any combination thereof.
  • Clause 47 The UE of any of clauses 37 to 46, wherein: the plurality of positioning models is configured at the UE during a start of the positioning session.
  • Clause 48 The UE of any of clauses 37 to 47, wherein: the plurality of positioning models is configured at the UE before a start of the positioning session during one or more positioning model configuration operations occurring outside of the positioning session.
  • Clause 49 The UE of any of clauses 37 to 48, wherein the at least one processor is further configured to: receive, via the at least one transceiver, from the network server, a PMC configuration for mapping the plurality of PMC indexes to at least the subset of the plurality of positioning models configured at the UE.
  • each of the plurality of PMC indexes is configured based on a bitmap received from a network server, wherein bits of the bitmap indicate which positioning models of the plurality of positioning models are mapped to a sequence of PMC indexes.
  • Clause 51 The UE of any of clauses 37 to 50, wherein: at least one PMC index of the plurality of PMC indexes is mapped to a classical new radio positioning technique specified by a network server.
  • a user equipment comprising: means for receiving a positioning model codepoint (PMC) index of a plurality of PMC indexes, wherein each PMC index of the plurality of PMC indexes is mapped to a corresponding positioning model of at least a subset of a plurality of positioning models configured at the UE; and means for applying a positioning model, mapped to the PMC index, to one or more RFFP positioning measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session.
  • PMC positioning model codepoint
  • Clause 54 The UE of clause 53, further comprising: means for receiving the plurality of positioning models from a network server.
  • Clause 55 The UE of any of clauses 53 to 54, wherein: the plurality of positioning models is received at the UE during a start of the positioning session.
  • Clause 56 The UE of any of clauses 53 to 54, wherein: the plurality of positioning models is configured at the UE before a start of the positioning session during one or more model configuration operations occurring outside of the positioning session.
  • each of the plurality of PMC indexes are configured based on a bitmap received from a network server, wherein bits of the bitmap indicate which positioning models of the plurality of positioning models are mapped to a sequence of PMC indexes.
  • each of the plurality of PMC indexes has a data size of log 2 (codepoint size) bits, wherein the codepoint size corresponds to a number of positioning models in the subset of the plurality of positioning models configured at the UE.
  • Clause 59 The UE of any of clauses 53 to 58, wherein: at least one PMC index of the plurality of PMC indexes is mapped to a classical New Radio positioning technique specified by a network server.
  • Clause 60 The UE of any of clauses 53 to 59, wherein the position parameters comprise: the location of the UE; one or more position coordinates associated with the location of the UE; one or more positioning measurements associated with the location of the UE; or a combination thereof.
  • Clause 61 The UE of any of clauses 53 to 60, wherein: the plurality of positioning models is determined based on an approximate UE location of the UE, a UE area as identified by a tracking area identifier of the UE, or a combination thereof.
  • Clause 62 The UE of any of clauses 53 to 61, further comprising: means for receiving a further PMC index, wherein the further PMC index is mapped to a further positioning model providing a position measurement output that is different than the one or more position parameters provided by the positioning model; and means for transmitting, to a network server, the position measurement output of the further positioning model.
  • a user equipment comprising: means for applying a selected positioning model to one or more radio frequency fingerprint positioning (RFFP) measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session, wherein the selected positioning model is selected from a plurality of positioning models configured at the UE; means for transmitting, to a network server, at least one of the one or more position parameters; and means for transmitting, to the network server, a positioning model codepoint (PMC) index that is mapped to the selected positioning model, wherein the PMC index is one of a plurality of PMC indexes mapped to corresponding positioning models of at least a subset of the plurality of positioning models configured at the UE.
  • RFFP radio frequency fingerprint positioning
  • Clause 64 The UE of clause 63, wherein: one or more positioning models of the plurality of positioning models are indicated for use with one or more channel conditions measured by the UE.
  • Clause 65 The UE of clause 64, wherein: the selected positioning model is selected based on channel conditions detected by the UE.
  • Clause 66 The UE of any of clauses 64 to 65, wherein: the one or more positioning models of the plurality of positioning models are indicated for use with the one or more channel conditions in metadata associated with the one or more positioning models.
  • Clause 67 The UE of clause 66, further comprising: means for receiving assistance data indicating one or more transmission points used in the positioning session; means for receiving one or more model channel reference signals from the one or more transmission points used in the positioning session; and means for determining the one or more channel conditions based on measuring the one or more model channel reference signals.
  • Clause 68 The UE of clause 67, wherein: the one or more model channel reference signals are received outside of a time allocated to the positioning session; and the one or more channel conditions are determined outside of the time allocated to the positioning session.
  • Clause 70 The UE of any of clauses 66 to 69, further comprising: means for transmitting one or more model channel reference signals; and means for determining the one or more channel conditions based on receiving one or more environmental reflections of the one or more model channel reference signals received at the UE.
  • Clause 71 The UE of clause 70, further comprising: means for receiving a configuration for transmitting the one or more model channel reference signals.
  • Clause 72 The UE of clause 71, wherein the configuration for transmitting the one or more model channel reference signals comprises: a frequency domain resource allocation for the one or more model channel reference signals; a time domain resource allocation for the one or more model channel reference signals; power parameters associated with the one or more model channel reference signals; or any combination thereof.
  • Clause 73 The UE of any of clauses 63 to 72, wherein: the plurality of positioning models is configured at the UE during a start of the positioning session.
  • Clause 74 The UE of any of clauses 63 to 73, wherein: the plurality of positioning models is configured at the UE before a start of the positioning session during one or more positioning model configuration operations occurring outside of the positioning session.
  • Clause 75 The UE of any of clauses 63 to 74, further comprising: means for receiving, from the network server, a PMC configuration for mapping the plurality of PMC indexes to at least the subset of the plurality of positioning models configured at the UE.
  • each of the plurality of PMC indexes is configured based on a bitmap received from a network server, wherein bits of the bitmap indicate which positioning models of the plurality of positioning models are mapped to a sequence of PMC indexes.
  • Clause 77 The UE of any of clauses 63 to 76, wherein: at least one PMC index of the plurality of PMC indexes is mapped to a classical new radio positioning technique specified by a network server.
  • Clause 78 The UE of any of clauses 63 to 77, wherein the position parameters comprise: the location of the UE; one or more position coordinates associated with the location of the UE; one or more positioning measurements associated with the location of the UE; or a combination thereof.
  • a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive a positioning model codepoint (PMC) index of a plurality of PMC indexes, wherein each PMC index of the plurality of PMC indexes is mapped to a corresponding positioning model of at least a subset of a plurality of positioning models configured at the UE; and apply a positioning model, mapped to the PMC index, to one or more RFFP positioning measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session.
  • PMC positioning model codepoint
  • Clause 80 The non-transitory computer-readable medium of clause 79, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: receive the plurality of positioning models from a network server.
  • Clause 81 The non-transitory computer-readable medium of any of clauses 79 to 80, wherein: the plurality of positioning models is received at the UE during a start of the positioning session.
  • Clause 82 The non-transitory computer-readable medium of any of clauses 79 to 80, wherein: the plurality of positioning models is configured at the UE before a start of the positioning session during one or more model configuration operations occurring outside of the positioning session.
  • each of the plurality of PMC indexes are configured based on a bitmap received from a network server, wherein bits of the bitmap indicate which positioning models of the plurality of positioning models are mapped to a sequence of PMC indexes.
  • each of the plurality of PMC indexes has a data size of log 2 (codepoint size) bits, wherein the codepoint size corresponds to a number of positioning models in the subset of the plurality of positioning models configured at the UE.
  • Clause 85 The non-transitory computer-readable medium of any of clauses 79 to 84, wherein: at least one PMC index of the plurality of PMC indexes is mapped to a classical New Radio positioning technique specified by a network server.
  • Clause 87 The non-transitory computer-readable medium of any of clauses 79 to 86, wherein: the plurality of positioning models is determined based on an approximate UE location of the UE, a UE area as identified by a tracking area identifier of the UE, or a combination thereof.
  • Clause 88 The non-transitory computer-readable medium of any of clauses 79 to 87, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: receive a further PMC index, wherein the further PMC index is mapped to a further positioning model providing a position measurement output that is different than the one or more position parameters provided by the positioning model; and transmit, to a network server, the position measurement output of the further positioning model.
  • a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: apply a selected positioning model to one or more radio frequency fingerprint positioning (RFFP) measurements to obtain one or more position parameters corresponding to a location of the UE during a positioning session, wherein the selected positioning model is selected from a plurality of positioning models configured at the UE; transmit, to a network server, at least one of the one or more position parameters; and transmit, to the network server, a positioning model codepoint (PMC) index that is mapped to the selected positioning model, wherein the PMC index is one of a plurality of PMC indexes mapped to corresponding positioning models of at least a subset of the plurality of positioning models configured at the UE.
  • RFFP radio frequency fingerprint positioning
  • Clause 90 The non-transitory computer-readable medium of clause 89, wherein: one or more positioning models of the plurality of positioning models are indicated for use with one or more channel conditions measured by the UE.
  • Clause 91 The non-transitory computer-readable medium of clause 90, wherein: the selected positioning model is selected based on channel conditions detected by the UE.
  • Clause 92 The non-transitory computer-readable medium of any of clauses 90 to 91, wherein: the one or more positioning models of the plurality of positioning models are indicated for use with the one or more channel conditions in metadata associated with the one or more positioning models.
  • Clause 93 The non-transitory computer-readable medium of clause 92, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: receive assistance data indicating one or more transmission points used in the positioning session; receive one or more model channel reference signals from the one or more transmission points used in the positioning session; and determine the one or more channel conditions based on measuring the one or more model channel reference signals.
  • Clause 94 The non-transitory computer-readable medium of clause 93, wherein: the one or more model channel reference signals are received outside of a time allocated to the positioning session; and the one or more channel conditions are determined outside of the time allocated to the positioning session.
  • Clause 95 The non-transitory computer-readable medium of any of clauses 93 to 94, wherein: the one or more model channel reference signals are dedicated for use in selecting the positioning model.
  • Clause 96 The non-transitory computer-readable medium of any of clauses 92 to 95, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: transmit one or more model channel reference signals; and determine the one or more channel conditions based on receiving one or more environmental reflections of the one or more model channel reference signals received at the UE.
  • Clause 97 The non-transitory computer-readable medium of clause 96, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: receive a configuration for transmitting the one or more model channel reference signals.
  • Clause 98 The non-transitory computer-readable medium of clause 97, wherein the configuration for transmitting the one or more model channel reference signals comprises: a frequency domain resource allocation for the one or more model channel reference signals; a time domain resource allocation for the one or more model channel reference signals; power parameters associated with the one or more model channel reference signals; or any combination thereof.
  • Clause 99 The non-transitory computer-readable medium of any of clauses 89 to 98, wherein: the plurality of positioning models is configured at the UE during a start of the positioning session.
  • Clause 100 The non-transitory computer-readable medium of any of clauses 89 to 99, wherein: the plurality of positioning models is configured at the UE before a start of the positioning session during one or more positioning model configuration operations occurring outside of the positioning session.
  • Clause 101 The non-transitory computer-readable medium of any of clauses 89 to 100, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: receive, from the network server, a PMC configuration for mapping the plurality of PMC indexes to at least the subset of the plurality of positioning models configured at the UE.
  • each of the plurality of PMC indexes is configured based on a bitmap received from a network server, wherein bits of the bitmap indicate which positioning models of the plurality of positioning models are mapped to a sequence of PMC indexes.
  • Clause 103 The non-transitory computer-readable medium of any of clauses 89 to 102, wherein: at least one PMC index of the plurality of PMC indexes is mapped to a classical new radio positioning technique specified by a network server.
  • Clause 104 The non-transitory computer-readable medium of any of clauses 89 to 103, wherein the position parameters comprise: the location of the UE; one or more position coordinates associated with the location of the UE; one or more positioning measurements associated with the location of the UE; or a combination thereof.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field-programable gate array
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • a software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • An example storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium.
  • the storage medium may be integral to the processor.
  • the processor and the storage medium may reside in an ASIC.
  • the ASIC may reside in a user terminal (e.g., UE).
  • the processor and the storage medium may reside as discrete components in a user terminal.
  • the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media may be any available media that can be accessed by a computer.
  • such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • Disk and disc includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Remote Sensing (AREA)
  • Mobile Radio Communication Systems (AREA)
US17/930,844 2022-09-09 2022-09-09 Positioning model codepoint configuration Pending US20240085515A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US17/930,844 US20240085515A1 (en) 2022-09-09 2022-09-09 Positioning model codepoint configuration
PCT/US2023/070484 WO2024054722A1 (fr) 2022-09-09 2023-07-19 Configuration de point de code de modèle de positionnement
TW112126845A TW202412547A (zh) 2022-09-09 2023-07-19 定位模型編碼點配置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US17/930,844 US20240085515A1 (en) 2022-09-09 2022-09-09 Positioning model codepoint configuration

Publications (1)

Publication Number Publication Date
US20240085515A1 true US20240085515A1 (en) 2024-03-14

Family

ID=87570987

Family Applications (1)

Application Number Title Priority Date Filing Date
US17/930,844 Pending US20240085515A1 (en) 2022-09-09 2022-09-09 Positioning model codepoint configuration

Country Status (3)

Country Link
US (1) US20240085515A1 (fr)
TW (1) TW202412547A (fr)
WO (1) WO2024054722A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240019528A1 (en) * 2022-07-18 2024-01-18 Qualcomm Incorporated Positioning model failure detection

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7970575B2 (en) * 2007-04-20 2011-06-28 Industrial Technology Research Institute Method and apparatus for determining accuracy of the estimated location for a target in a wireless system
US8880105B2 (en) * 2011-12-29 2014-11-04 Khalifa University Of Science, Technology And Research Method and system for localization
CN108702585B (zh) * 2016-02-19 2021-07-23 瑞典爱立信有限公司 混合指纹识别/otdoa定位技术和系统
CN107948924B (zh) * 2017-10-10 2019-07-16 深圳数位传媒科技有限公司 无线信号指纹信息的校准方法、系统、服务器和介质
EP3803438B1 (fr) * 2018-05-30 2024-06-19 HERE Global B.V. Collecte ou déclenchement de données de positionnement de collecte pour la mise à jour et/ou la génération d'une carte de positionnement

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240019528A1 (en) * 2022-07-18 2024-01-18 Qualcomm Incorporated Positioning model failure detection

Also Published As

Publication number Publication date
TW202412547A (zh) 2024-03-16
WO2024054722A1 (fr) 2024-03-14

Similar Documents

Publication Publication Date Title
WO2022031687A1 (fr) Déclenchement sélectif de fonctions de réseau neuronal pour la localisation d'un équipement utilisateur
US20230037704A1 (en) Data gathering and data selection to train a machine learning algorithm
US20230336229A1 (en) Base station-to-server signaling of time-angle channel profile
US20240012089A1 (en) Positioning model reporting
US20240069143A1 (en) User equipment-based (ue-based) positioning based on self-radio frequency fingerprint (self-rffp)
US20230417866A1 (en) User equipment (ue) positioning with frequency domain windowing
US20230354248A1 (en) Network-assisted and round-trip radio frequency fingerprint-based (rffp) position estimation
WO2024054722A1 (fr) Configuration de point de code de modèle de positionnement
WO2024019809A1 (fr) Détection d'un échec d'un modèle de positionnement
WO2024030174A1 (fr) Sélection de nœud pour apprentissage fédéré d'empreinte digitale radiofréquence (rffp)
WO2023211584A1 (fr) Positionnement par empreinte radiofréquence (rffp) basé sur un équipement utilisateur (ue) avec signaux de référence de positionnement de liaison descendante
WO2023211580A1 (fr) Positionnement par empreinte radiofréquence (rffp) basé sur un équipement utilisateur (ue) avec signaux de référence de positionnement de liaison descendante
US20240073855A1 (en) Node configuration for positioning model monitoring
US20240098453A1 (en) Positioning model based on multiple transmission point and/or multiple bandwidth configurations
US20240129879A1 (en) Bandwidth aggregation for radio frequency fingerprint positioning
US20240230828A9 (en) Positioning model training based on radio frequency fingerprint positioning (rffp) measurements corresponding to position displacements
US20240172165A1 (en) Positioning based on composite radio frequency fingerprint measurement
US20230422278A1 (en) User equipment (ue) positioning with frequency domain windowing
US20240179663A1 (en) Radio frequency fingerprint positioning of transmission-reception point
US20240107356A1 (en) Virtual instance for reference signal for positioning
US20230354247A1 (en) Machine learning model positioning performance monitoring and reporting
US20240061066A1 (en) Network-based positioning based on self-radio frequency fingerprint (self-rffp)
US20230354254A1 (en) Measurement error feedback to enable machine learning-based positioning
WO2023211627A1 (fr) Estimation de position basée sur une empreinte radiofréquence (rffp) assistée par réseau et aller-retour
WO2023212017A1 (fr) Structure de comptes rendus de mesures basées sur l'apprentissage automatique en vue d'un positionnement

Legal Events

Date Code Title Description
AS Assignment

Owner name: QUALCOMM INCORPORATED, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ZORGUI, MARWEN;HIRZALLAH, MOHAMMED ALI MOHAMMED;YERRAMALLI, SRINIVAS;AND OTHERS;SIGNING DATES FROM 20220919 TO 20221004;REEL/FRAME:061320/0620

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION