Reporting hash expected channel measurements
By receiving and comparing the set of hash values in the network nodes of the wireless communication system, and using hash operations to verify the actual measured values of the PRS resources, the problem of inefficient detection of positioning reference signal attacks in the prior art is solved, and more accurate and efficient PRS attack detection.
Patent Information
- Application Number
- CN202380029844.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-06
- Filing Date
- 2023-02-01
- Publication Date
- 2024-11-08
AI Technical Summary
Existing wireless communication systems have problems with inefficiency in positioning reference signal (PRS) attack detection, and it is difficult to accurately determine whether the actual measured value of the PRS resource is within the acceptable range of the expected measured value.
By receiving and comparing a set of hash values in a network node, the hash operation is used to verify whether the actual measured value of the PRS resource meets the limits of the expected measured value, and then perform PRS attack detection.
Improve the accuracy and efficiency of PRS attack detection, ensuring the reliability and security of positioning reference signals.
Smart Images

Figure CN118923140A_ABST
Abstract
Description
Background Art 1. Technical Field
[0001] Aspects of the present disclosure relate generally to wireless communications.
[0002] 2. Description of related technologies
[0003] Wireless communication systems have evolved over many generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including transitional 2.5G and 2.75G networks), third generation (3G) high speed data, wireless service with Internet capabilities, and fourth generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). There are many different types of wireless communication systems in use today, including cellular systems and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile Communications (GSM), and the like.
[0004] The fifth generation (5G) wireless standard, known as New Radio (NR), enables higher data transfer speeds, a greater number of connections, and better coverage, among other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements compared to previous standards. These enhancements, along with the use of higher frequency bands, advances in PRS processes and technologies, and high-density deployments of 5G, enable high-accuracy positioning based on 5G. Summary of the invention
[0005] The following presents a simplified summary of the invention related to one or more aspects disclosed herein. Therefore, the following summary of the invention should neither be considered as an exhaustive overview related to all conceived aspects, nor should it be considered to identify key or decisive elements related to all conceived aspects or to delineate the scope associated with any particular aspect. Therefore, the sole purpose of the following summary of the invention is to present certain concepts related to one or more aspects related to the mechanisms disclosed herein in a brief form before the detailed embodiments presented below.
[0006] In one aspect, a method of wireless communication performed by a network node includes: receiving a first set of one or more hash values, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs); measuring the one or more PRS resources to obtain one or more actual measurement values; and determining whether the one or more actual measurement values of the one or more PRS resources are within acceptable limits of the one or more expected measurement values based on a comparison of a second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying the one or more hash operations to the one or more actual measurement values.
[0007] In one aspect, a method of wireless communication performed by a network node includes: receiving a first set of one or more hash values from a location server, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values, wherein the one or more expected measurement values correspond to expected measurements of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs) measured by a user equipment (UE) during a positioning session; and using the first set of one or more hash values for PRS attack detection.
[0008] In one aspect, a network node includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive a first set of one or more hash values via the at least one transceiver, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs); measure the one or more PRS resources to obtain one or more actual measurement values; and determine whether the one or more actual measurement values of the one or more PRS resources are within acceptable limits of the one or more expected measurement values based on a comparison of a second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying the one or more hash operations to the one or more actual measurement values.
[0009] In one aspect, a network node comprises: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive a first set of one or more hash values from a location server via the at least one transceiver, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values, wherein the one or more expected measurement values correspond to expected measurements of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs) measured by a user equipment (UE) during a positioning session; and use the first set of one or more hash values for PRS attack detection.
[0010] In one aspect, a network node includes: a component for receiving a first set of one or more hash values, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs); a component for measuring the one or more PRS resources to obtain one or more actual measurement values; and a component for determining whether the one or more actual measurement values of the one or more PRS resources are within acceptable limits of the one or more expected measurement values based on a comparison of a second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying the one or more hash operations to the one or more actual measurement values.
[0011] In one aspect, a network node includes: a component for receiving a first set of one or more hash values from a location server, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values, wherein the one or more expected measurement values correspond to expected measurements of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs) measured by a user equipment (UE) during a positioning session; and a component for using the first set of one or more hash values for PRS attack detection.
[0012] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network node, cause the network node to: receive a first set of one or more hash values, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs); measure the one or more PRS resources to obtain one or more actual measurement values; and determine whether the one or more actual measurement values of the one or more PRS resources are within acceptable limits of the one or more expected measurement values based on a comparison of a second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying the one or more hash operations to the one or more actual measurement values.
[0013] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a network node, cause the network node to: receive a first set of one or more hash values from a location server, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values, wherein the one or more expected measurement values correspond to expected measurements of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs) measured by a user equipment (UE) during a positioning session; and use the first set of one or more hash values for PRS attack detection.
[0014] Other objects and advantages associated with the various aspects disclosed herein will be apparent to those skilled in the art based on the drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] The accompanying drawings are presented to aid in describing various aspects of the present disclosure and are provided solely for illustration and not limitation of the various aspects.
[0016] Figure 1 An example wireless communication system in accordance with aspects of the present disclosure is illustrated.
[0017] Figure 2A and Figure 2B Example wireless network structures according to aspects of the present disclosure are illustrated.
[0018] Figure 3A , Figure 3B and Figure 3C is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network node, respectively, and configured to support communications as taught herein.
[0019] Figure 4An example Long Term Evolution (LTE) Positioning Protocol (LPP) call flow between a UE and a location server for performing positioning operations is illustrated.
[0020] Figure 5 is a diagram illustrating an example frame structure according to aspects of the present disclosure.
[0021] Figure 6 Examples of various positioning methods supported in New Radio (NR) according to aspects of the present disclosure are illustrated.
[0022] Figure 7
[0013] A time difference of arrival (TDOA) based positioning procedure in an example wireless communication system in accordance with aspects of the present disclosure is illustrated.
[0023] Figure 8 is a diagram illustrating an example base station in communication with an example UE according to aspects of the present disclosure.
[0024] Fig. 9 Example network node location service procedures in accordance with aspects of the present disclosure are illustrated.
[0025] Fig.10 is a graph representing a radio frequency (RF) channel impulse response over time in accordance with aspects of the present disclosure.
[0026] Fig.11 An example method of wireless communication performed by a network node according to aspects of the present disclosure is illustrated.
[0027] Fig.12 An example method of wireless communication performed by a network node according to aspects of the present disclosure is illustrated. DETAILED DESCRIPTION
[0028] Various aspects of the present disclosure are provided in the following description and related drawings for various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of the present disclosure. In addition, well-known elements of the present disclosure will not be described in detail or will be omitted to avoid making the relevant details of the present disclosure difficult to understand.
[0029] The words "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term "aspects of the disclosure" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation.
[0030] Those skilled in the art will appreciate that any of a variety of different techniques and methods may be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, which depends in part on the specific application, in part on the desired design, in part on the corresponding technology, and so on.
[0031] In addition, many aspects are described in terms of a sequence of actions to be performed by, for example, an element of a computing device. It will be appreciated that the various actions described herein may be performed by a specific circuit (e.g., an application specific integrated circuit (ASIC)), by a program instruction executed by one or more processors, or by a combination of the two. In addition, the sequence of actions described herein may be considered to be fully embodied in any form of non-transient computer-readable storage medium, in which a corresponding computer instruction set is stored, which, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of the present disclosure may be embodied in a variety of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the various aspects described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions".
[0032] As used herein, unless otherwise specified, the terms "user equipment" (UE) and "base station" are not intended to be specific or otherwise limited to any specific radio access technology (RAT). In general, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a consumer asset location device, a wearable device (e.g., a smart watch, glasses, an augmented reality (AR) / virtual reality (VR) headset, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.). A UE can be mobile or can be stationary (e.g., at certain times) and can communicate with a radio access network (RAN). As used herein, the term "UE" can be interchangeably referred to 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. In general, the UE can communicate with the core network via the RAN, and through the core network, the UE can be connected to an external network such as the Internet and other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through a wired access network, a wireless local area network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.), etc.
[0033] A base station may operate according to one of several RATs to communicate with a UE, depending on the network in which the base station is deployed, and may alternatively be referred to as an access point (AP), a network node, a Node B, an evolved Node B (eNB), a next generation eNB (ng-eNB), a new radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be primarily used to support wireless access for UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, a base station may provide only edge node signaling functions, while in other systems, it may provide additional control and / or network management functions. The communication link by which a UE may transmit a signal to a base station is referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link by which a base station may transmit a signal to a UE is referred to as a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term "traffic channel (TCH)" may refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.
[0034] The term "base station" may refer to a single physical transmit receive point (TRP) or to multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRP may be a serving base station that receives measurement reports from a UE and a neighboring base station whose reference radio frequency (RF) signal the UE is measuring. Because, as used herein, a TRP is a point by which a base station transmits and receives wireless signals, references to transmitting from a base station or receiving at a base station should be understood to refer to a specific TRP of a base station.
[0035] In some specific implementations of supporting UE positioning, the base station may not support wireless access for the UE (e.g., may not support data, voice, and / or signaling connections for the UE), but may instead send a reference signal to be measured by the UE to the UE and / or may receive and measure a signal sent by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of sending a signal to the UE) and / or as a position measurement unit (e.g., in the case of receiving and measuring a signal from the UE).
[0036] "RF signals" include electromagnetic waves of a given frequency that transmit information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" where it is clear from the context that the term "signal" refers to either a wireless signal or an RF signal.
[0037] Figure 1An example wireless communication system 100 is illustrated in accordance with various aspects of the present disclosure. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled as "BS") and various UEs 104. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macrocell base stations may include eNBs and / or ng-eNBs (where the wireless communication system 100 corresponds to an LTE network), or gNBs (where the wireless communication system 100 corresponds to an NR network), or a combination of the two, and the small cell base stations may include femtocells, picocells, microcells, and the like.
[0038] 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 a backhaul link 122, and interface with one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 may be integrated with the base station 102. The UE 104 may communicate with the location server 172 directly or indirectly. For example, the UE 104 may communicate with the location server 172 via the base station 102 currently serving the UE 104. The UE 104 may also communicate with the location server 172 via another path, such as via an application server (not shown), via another network, such as via a WLAN access point (AP) (e.g., the AP 150 described below), and the like. For signaling purposes, communications between UE 104 and location server 172 may be represented as an indirect connection (e.g., through core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with intermediate nodes (if any) omitted from the signaling diagram for clarity.
[0039] Among other functions, the base station 102 may perform functions related to one or more of the following: delivering user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through EPC / 5GC) over a backhaul link 134, which may be wired or wireless.
[0040] Base station 102 may communicate wirelessly with UE 104. Each of base stations 102 may provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells may be supported by base station 102 in each geographic coverage area 110. A "cell" is a logical communication entity used to communicate with a base station (e.g., on a frequency resource, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.), and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that may provide access to different types of UEs. Because a cell is supported by a specific base station, the term "cell" may refer to either or both of the logical communication entity and the base station supporting it, depending on the context. In addition, because the TRP is generally the physical transmission point of the cell, the terms "cell" and "TRP" may be used interchangeably. In some cases, the term "cell" may also refer to the geographic coverage area (e.g., sector) of a base station, as long as the carrier frequency can be detected and used for communications within a portion of the geographic coverage area 110.
[0041] Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may substantially overlap with the larger geographic coverage areas 110. For example, a small cell base station 102′ (labeled “SC” for “small cell”) may have a geographic coverage area 110′ that substantially overlaps with the geographic coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB), which may provide services to a restricted group called a closed subscriber group (CSG).
[0042] The communication link 120 between the base station 102 and the UE 104 may include uplink (also referred to as reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be over one or more carrier frequencies. The allocation of carriers may be asymmetric for the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink than to the uplink).
[0043] The wireless communication system 100 may also include a WLAN access point (AP) 150 that communicates with a WLAN station (STA) 152 in an unlicensed spectrum (e.g., 5 GHz) via a communication link 154. When communicating in the unlicensed spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communication to determine whether a channel is available.
[0044] The small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell base station 102' can adopt LTE or NR technology and use the same 5GHz unlicensed spectrum used by the WLAN AP 150. The small cell base station 102' using LTE / 5G in the unlicensed spectrum can improve the coverage of the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum can be referred to as NR-U. LTE in the unlicensed spectrum can be referred to as LTE-U, Licensed Assisted Access (LAA) or MulteFire.
[0045] The wireless communication system 100 may also include a millimeter wave (mmW) base station 180, which can operate at mmW frequencies and / or near mmW frequencies to communicate with UE 182. Extremely high frequency (EHF) is part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz, with a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can be extended down to a frequency of 3 GHz, with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, and is also referred to as centimeter waves. Communications using mmW / near mmW RF bands have high path loss and relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (transmitting and / or receiving) on the mmW communication link 184 to compensate for the extremely high path loss and short range. In addition, it should be understood that in an alternative configuration, one or more base stations 102 may also use mmW or near mmW and beamforming for transmission. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.
[0046] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal to the receiving device. In order to change the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that broadcast the RF signal. For example, the network node can use an array of antennas (called a "phased array" or "antenna array") that creates RF beams that can be "steered" to point in different directions without actually moving the antennas. Specifically, the RF current from the transmitter is fed to each antenna in the correct phase relationship so that the radio waves from the separate antennas are added together to increase the radiation in the desired direction while canceling to suppress the radiation in the undesired direction.
[0047] The transmit beams can be quasi-co-located, which means that they appear to the receiver (e.g., UE) to have the same parameters, regardless of whether the network node's own transmit antenna is physically co-located. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about the second reference RF signal on the second beam can be derived from information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay and delay spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type D, the receiver may use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.
[0048] In receive beamforming, the receiver uses receive beams to amplify RF signals detected on a given channel. For example, the receiver may increase the gain setting of the antenna array in a particular direction and / or adjust the phase setting of the antenna array in a particular direction to amplify the RF signal received from that direction (e.g., increase its gain level). Therefore, when a receiver is said to perform beamforming in a certain direction, it means that 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 signal received from that direction.
[0049] The transmit beam and the receive beam may be spatially correlated. The spatial relationship means that parameters of a second beam (e.g., a transmit beam or a receive beam) for a second reference signal may be derived from information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal. For example, a UE may use a specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE may then form a transmit beam for transmitting an uplink reference signal (e.g., a sounding reference signal (SRS)) to the base station based on the parameters of the receive beam.
[0050] Note that depending on the entity forming the "downlink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to send a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam that receives a downlink reference signal. Similarly, depending on the entity forming the "uplink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, it is an uplink receive beam, and if the UE is forming an uplink beam, it is an uplink transmit beam.
[0051] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. Similar naming issues sometimes arise with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz), and the EHF band is identified as a "millimeter wave" band by the International Telecommunication Union (ITU).
[0052] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.
[0053] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used in this document, it can be broadly referred to as a frequency that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used in this document, it can be broadly referred to as a frequency 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.
[0054] In a multi-carrier system (such as 5G), one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are referred to as "secondary carriers" or "secondary serving cells" or "SCells". In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) used by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2), which can be configured and used to provide additional radio resources once an RRC connection is established between the UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, since the primary uplink carrier and the primary downlink carrier are usually UE-specific, those UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carrier. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Because a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier on which a base station communicates, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. are used interchangeably.
[0055] For example, still refer to Figure 1 , one of the frequencies used by macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies used by macrocell base station 102 and / or mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers enables UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz) compared to the data rate obtained with a single 20 MHz carrier.
[0056] The wireless communication system 100 may also include a UE 164, which may communicate with the macrocell base station 102 via a communication link 120 and / or communicate with the mmW base station 180 via a mmW communication link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.
[0057] In some cases, UE 164 and UE 182 are capable of sidelink communication. A UE with sidelink capability (SL-UE) can communicate with base station 102 via communication link 120 using a Uu interface (i.e., an air interface between UE and base station). SL-UE (e.g., UE 164, UE 182) can also communicate directly with each other via a wireless sidelink 160 using a PC5 interface (i.e., an air interface between UEs with sidelink capability). A wireless sidelink (or simply referred to as a "sidelink") is an adaptation of a core cellular network (e.g., LTE, NR) standard that allows direct communication between two or more UEs without communicating through a base station. Sidelink communications can be unicast or multicast and can be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communications, vehicle-to-vehicle (V2X) communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more SL-UEs in a group of SL-UEs utilizing sidelink communications may be located within the geographic coverage area 110 of the base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of the base station 102, or may be unable to receive transmissions from the base station 102 for other reasons. In some cases, groups of SL-UEs communicating via sidelink communications may utilize a one-to-many (1:M) system, in which each SL-UE transmits to each other SL-UE in the group. In some cases, the base station 102 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink communications are performed between SL-UEs without involving the base station 102.
[0058] In one aspect, the sidelink 160 may operate on a wireless communication medium of interest, which may be shared with other vehicles and / or infrastructure access points and other wireless communications between other RATs. A "medium" may include one or more time, frequency, and / or spatial communication resources associated with wireless communications between one or more transmitter / receiver pairs (e.g., covering one or more channels across one or more carriers). In one aspect, the medium of interest may correspond to at least a portion of an unlicensed band shared between various RATs. Although different licensed bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), these systems (particularly those employing small cell access points) have recently expanded operations into unlicensed bands such as the unlicensed National Information Infrastructure (U-NII) band used by WLAN technology (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include different variations of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single carrier FDMA (SC-FDMA) systems, and the like.
[0059] Note that although Figure 1 Only two of these UEs are illustrated as SL-UEs (i.e., UEs 164 and 182), but any of the illustrated UEs may be SL-UEs. In addition, although only UE 182 is described as being capable of beamforming, any of the illustrated UEs (including UE 164) may be capable of beamforming. Where SL-UEs are capable of beamforming, they may beamform toward each other (i.e., toward other SL-UEs), toward other UEs (e.g., UE 104), toward base stations (e.g., base stations 102, 180, small cells 102′, access point 150), and the like. Thus, in some cases, UE 164 and UE 182 may utilize beamforming on sidelink 160.
[0060] exist Figure 1 In the example of FIG. 1 , the UE illustrated (for simplicity, in Figure 1Any of the UEs 104 (shown as a single UE 104 in FIG. 1 ) can receive a signal 124 from one or more earth orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SV 112 can be part of a satellite positioning system that the UE 104 can use as an independent source of location information. A satellite positioning system typically includes a transmitter system (e.g., SV 112) positioned to enable a receiver (e.g., UE 104) to determine its position on or above the earth based at least in part on a positioning signal (e.g., signal 124) received from the transmitter. Such a transmitter typically transmits a signal that is marked with a repeating pseudo-random noise (PN) code of a set number of chips. Although typically located in the SV 112, the transmitter may sometimes be located on a ground-based control station, base station 102, and / or other UE 104. The UE 104 may include one or more dedicated receivers that are specifically designed to receive the signal 124 in order to derive geographic location information from the SV 112.
[0061] In a satellite positioning system, the use of signal 124 may be enhanced by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential corrections, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multifunction Satellite Augmentation System (MSAS), Global Positioning System (GPS) Assisted Geographic Augmented Navigation or GPS and Geographic Augmented Navigation System (GAGAN), etc. Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.
[0062] In one aspect, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as an improved base station 102 (without a ground antenna) or a network node in a 5GC. This element in turn will provide access to other elements in the 5G network, and ultimately provide access to entities outside the 5G network (such as Internet web servers and other user devices). In this way, instead of or in addition to communication signals from a ground base station 102, a UE 104 can receive communication signals (e.g., signal 124) from SV 112.
[0063] The wireless communication system 100 may also include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “side links”). Figure 1 In the example of FIG. 1 , UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through the D2D P2P link), and has a D2D P2P link 194 with WLAN STA 152 connected to WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through the D2D P2P link). In one example, D2D P2P links 192 and 194 can be supported by any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), etc.
[0064] Figure 2A An example wireless network architecture 200 is illustrated. For example, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be functionally viewed as a control plane (C-plane) function 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane (U-plane) function 212 (e.g., UE gateway function, access to data networks, Internet Protocol (IP) routing, etc.), which operate in conjunction to form a core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, and specifically to the user plane function 212 and the control plane function 214, respectively. In an additional configuration, the ng-eNB 224 can also be connected to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. In addition, the ng-eNB 224 can communicate directly with the gNB 222 via the backhaul connection 223. In some configurations, a next generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of ng-eNBs 224 and gNBs 222. Either (or both) the gNB 222 or the ng-eNB 224 may communicate with one or more UEs 204 (e.g., any of the UEs described herein).
[0065] Another optional aspect may include a location server 230 that can communicate with the 5GC 210 to provide location assistance for the UE 204. The location server 230 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively can each correspond to a single server. The location server 230 can be configured to support one or more location services for the UE 204 that can be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). In addition, the location server 230 can be integrated into a component of the core network, or alternatively can be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a maintenance server).
[0066] Figure 2B Another example wireless network structure 250 is illustrated. 5GC 260 (which may correspond to Figure 2AThe 5GC 210 in the 5GC 210 can be functionally considered as a control plane function provided by an access and mobility management function (AMF) 264, and a user plane function provided by a user plane function (UPF) 262, which operate in conjunction to form a core network (i.e., 5GC 260). The functions of the AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any UE described herein) and a session management function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between the UE 204 and a short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives an intermediate key established as a result of the UE 204 authentication process. In the case of authentication based on the UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), the AMF 264 retrieves security material from the AUSF. The functionality of the AMF 264 also includes security context management (SCM). The SCM receives keys from the SEAF, which it uses to derive access network specific keys. The functionality of the AMF 264 also includes location service management for regulatory services, for the transmission of location service messages between the UE 204 and the LMF 270 (which acts as a location server 230), for the transmission of location service messages between the NG-RAN 220 and the LMF 270, for the allocation of EPS bearer identifiers for interworking with the Evolved Packet System (EPS), and UE 204 mobility event notifications. In addition, the AMF 264 also supports functionality for non-3GPP (Third Generation Partnership Project) access networks.
[0067] The functions of UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, user plane quality of service (QoS) handling (e.g., uplink / downlink rate enforcement, reflective QoS marking in downlink), uplink traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering, and transmitting and forwarding one or more "end markers" to the source RAN node. UPF 262 can also support the delivery of location service messages between UE 204 and a location server (such as SLP 272) on the user plane.
[0068] The functions of SMF 266 include session management, UE IP address allocation and management, selection and control of user plane functions, service steering configuration for routing services to the correct destination at UPF 262, partial control of policy implementation and QoS, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.
[0069] Another optional aspect may include an LMF 270 that can communicate with the 5GC 260 to provide location assistance for the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively can each correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can be connected to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). SLP 272 may support similar functionality as LMF 270, but LMF 270 may communicate with AMF 264, NG-RAN 220, and UE 204 on a control plane (e.g., using interfaces and protocols intended to carry signaling messages rather than voice or data), and SLP 272 may communicate with UE 204 and external clients (e.g., third-party servers 274) on a user plane (e.g., using protocols intended to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP).
[0070] Yet another optional aspect may include a third-party server 274 that may communicate with the LMF 270, SLP 272, 5GC 260 (e.g., via AMF 264 and / or UPF 262), NG-RAN 220, and / or UE 204 to obtain location information (e.g., location estimate) of the UE 204. Thus, in some cases, the third-party server 274 may be referred to as a location service (LCS) client or external client. The third-party server 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server.
[0071] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and the AMF 264, respectively, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between the gNB 222 and / or ng-eNB 224 and the AMF 264 is referred to as the "N2" interface, while the interface between the gNB 222 and / or ng-eNB 224 and the UPF 262 is referred to as the "N3" interface. The gNBs 222 and / or ng-eNBs 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223 referred to as an "Xn-C" interface. One or more of the gNBs 222 and / or ng-eNBs 224 may communicate with one or more UEs 204 via a wireless interface referred to as a "Uu" interface.
[0072] The functionality of the gNB 222 is divided between a gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically assigned to the gNB-DU 228, including delivery of user data, mobility control, RAN sharing, positioning, session management, etc. More specifically, the gNB-CU 226 generally hosts the RRC, Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that generally hosts the Radio Link Control (RLC) and Medium Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and one or more gNB-DUs 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is typically hosted by one or more independent gNB-RUs 229, which perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is referred to as the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC layer, SDAP layer, and PDCP layer, communicates with the gNB-DU 228 via the RLC layer and MAC layer, and communicates with the gNB-RU 229 via the PHY layer.
[0073] Figure 3A , Figure 3B and Figure 3CThe examples may be incorporated into UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270, or alternatively may be independent of Figure 2A and Figure 2B Several example components (represented by corresponding boxes) in the NG-RAN 220 and / or 5GC210 / 260 infrastructure depicted in the present invention (such as a dedicated network) are shown to support operations as described herein. It should be understood that these components can be implemented in different types of devices with different specific implementations (for example, in an ASIC, in a system on a chip (SoC), etc.). The illustrated components can also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Moreover, a given device may include one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.
[0074] UE 302 and base station 304 each include one or more WWAN transceivers 310 and 350, respectively, which provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for preventing transmitting, etc.) for communicating via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. 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.) on a wireless communication medium of interest (e.g., a certain set of time / frequency resources in a specific spectrum). The WWAN transceivers 310 and 350 can be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to the specified RAT, and conversely, receive and decode the signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, the WWAN transceivers 310 and 350 include: one or more transmitters 314 and 354 for transmitting and encoding the signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding the signals 318 and 358, respectively.
[0075] At least in some cases, UE 302 and base station 304 each further include one or more short-range wireless transceivers 320 and 360, respectively. Short-range wireless transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide for communicating via at least one designated RAT (e.g., WiFi, LTE-D, The short-range wireless transceivers 320 and 360 are components (e.g., components for sending, components for receiving, components for measuring, components for tuning, components for preventing sending, etc.) for communicating with other network nodes (such as other UEs, access points, base stations, etc.) using a PC5, dedicated short-range communication (DSRC), wireless access for vehicle environments (WAVE), near field communication (NFC), ultra-wideband (UWB) communication, etc.). The short-range wireless transceivers 320 and 360 can be configured in different ways to send and encode signals 328 and 368 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, the short-range wireless transceivers 320 and 360 include: one or more transmitters 324 and 364 for sending and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As a specific example, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Transceiver, and / or transceiver, NFC transceiver or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceiver.
[0076] At least in some cases, UE 302 and base station 304 also include satellite signal receivers 330 and 370. Satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. In the case where satellite signal receivers 330 and 370 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 may be GPS signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian regional navigation satellite system (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. In the case where satellite signal receivers 330 and 370 are NTN receivers, satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. Satellite signal receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request appropriate information and operations from other systems and, at least in some cases, perform calculations using measurements obtained by any suitable satellite positioning system algorithm to determine the location of UE 302 and base station 304, respectively.
[0077] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide means (e.g., means for transmitting, means for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. As another example, the network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or communicate with other network entities 306 via one or more wired or wireless core network interfaces.
[0078] The transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes a transmitter circuit system (e.g., transmitters 314, 324, 354, 364) and a receiver circuit system (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., implementing the transmitter circuit system and the receiver circuit system in a single device), may include separate transmitter circuit systems and separate receiver circuit systems in some implementations, or may be implemented in other ways in other implementations. The transmitter circuit system and the receiver circuit system of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding devices (e.g., UE 302, base station 304) to perform transmit "beamforming", as described herein. Similarly, the wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding devices (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter circuitry and the receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366) so that the corresponding devices can only receive or only transmit at a given time, rather than both receive and transmit at the same time. The wireless transceivers (eg, WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listening module (NLM) or the like for performing various measurements.
[0079] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360 in some implementations, and network transceivers 380 and 390) and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) may be generally characterized as a "transceiver," "at least one transceiver," or "one or more transceivers." Thus, whether a particular transceiver is a wired or wireless transceiver may be inferred based on the type of communication being performed. For example, backhaul communications between network devices or servers typically involve signaling via a wired transceiver, while wireless communications between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via a wireless transceiver.
[0080] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operations disclosed herein. UE 302, base station 304, and network entity 306 include one or more processors 332, 384, and 394, respectively, for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 332, 384, and 394 may provide means for processing, such as means for determining, means for calculating, means for receiving, means for sending, means for indicating, etc. In one aspect, 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 circuit systems, or various combinations thereof.
[0081] UE 302, base station 304, and network entity 306 include memory circuitry implementing memory 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Thus, memory 340, 386, and 396 may provide means for storing, means for retrieving, means for maintaining, etc. In some cases, UE 302, base station 304, and network entity 306 may include positioning components 342, 388, and 398, respectively. Positioning components 342, 388, and 398, respectively, may be hardware circuits that are part of or coupled to processors 332, 384, and 394, respectively, which, when executed, cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, the positioning components 342, 388, and 398 can be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning components 342, 388, and 398 can be memory modules stored in the memories 340, 386, and 396, respectively, which when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. Figure 3A Illustrating possible locations of the positioning component 342, the positioning component 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 stand-alone component. Figure 3BIllustrated are possible locations for the location 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 stand-alone component. Figure 3C Illustrated are possible locations for the location component 398, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.
[0082] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide a means for sensing or detecting movement and / or orientation information that is independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. As an example, sensor 344 may include an accelerometer (e.g., a microelectromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of motion detection sensor. In addition, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate positioning in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.
[0083] In addition, the UE 302 includes a user interface 346, which provides means for providing indications to the user (e.g., audible and / or visual indications) and / or for receiving user input (e.g., when the user actuates a sensing device such as a keypad, touch screen, microphone, etc.). Although not shown, the base station 304 and the network entity 306 may also include a user interface.
[0084] Referring to the one or more processors 384 in more detail, in a downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functions for the RRC layer, the PDCP layer, the RLC layer, and the MAC layer. One or more processors 384 may provide: RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery 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.
[0085] The transmitter 354 and the receiver 352 may implement layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include: error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The transmitter 354 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine coding and modulation schemes and for spatial processing. Channel estimates may be derived from a reference signal and / or channel condition feedback sent by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a corresponding spatial stream for transmission.
[0086] At the UE 302, the receiver 312 receives the signal through its corresponding antenna 316. The receiver 312 recovers the information modulated onto the RF carrier and provides the information to one or more processors 332. The transmitter 314 and the receiver 312 implement layer 1 functionality associated with various signal processing functions. The receiver 312 can perform spatial processing on the information to recover any spatial streams destined for the UE 302. If the destination of multiple spatial streams is the UE 302, they can be combined into a single OFDM symbol stream by the receiver 312. Then, the receiver 312 converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point that is most likely to be sent by the base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. Then, the soft decisions are decoded and deinterleaved to recover the data and control signals originally sent by the base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332, which implement layer 3 (L3) and layer 2 (L2) functionality.
[0087] In the uplink, one or more processors 332 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the core network. One or more processors 332 are also responsible for error detection.
[0088] Similar to the functionality described in conjunction with downlink transmissions performed by the base station 304, the one or more processors 332 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery 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.
[0089] Channel estimates derived by a channel estimator from a reference signal or feedback sent by base station 304 may be used by transmitter 314 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by transmitter 314 may be provided to different antennas 316. Transmitter 314 may modulate an RF carrier with a corresponding spatial stream for transmission.
[0090] The uplink transmissions are processed at the base station 304 in a manner similar to that described in conjunction with the receiver functionality at the UE 302. The receiver 352 receives the signal through its respective antenna 356. The receiver 352 recovers the information modulated onto the RF carrier and provides the information to one or more processors 384.
[0091] In the uplink, one or more processors 384 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from UE 302. IP packets from one or more processors 384 may be provided to the core network. One or more processors 384 are also responsible for error detection.
[0092] For convenience, UE 302, base station 304 and / or network entity 306 may Figure 3A , Figure 3B and Figure 3C , is shown as including various components that can be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionality in different designs. Specifically, FIG. 3A to FIG. 3C The various components in are optional in alternative configurations, and various aspects include configurations that may vary due to design choice, cost, use of the device, or other considerations. For example, in Figure 3A In the case of , a specific implementation of UE 302 may omit WWAN transceiver 310 (e.g., a wearable device or tablet or PC or laptop may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), or may omit short-range wireless transceiver 320 (e.g., only cellular, etc.), or may omit satellite signal receiver 330, or may omit sensor 344, etc. In another example, in Figure 3B In the case of a wireless network, a specific implementation of the base station 304 may omit the WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or may omit the short-range wireless transceiver 360 (e.g., cellular only, etc.), or may omit the satellite receiver 370, etc. For the sake of brevity, illustrations of various alternative configurations are not provided herein, but will be readily apparent to those skilled in the art.
[0093] Various components of the UE 302, base station 304, and network entity 306 may be communicatively coupled to one another via data buses 334, 382, and 392, respectively. In an aspect, the data buses 334, 382, and 392 may form or be part of communication interfaces for the UE 302, base station 304, and network entity 306, respectively. For example, where different logical entities are embodied in the same device (e.g., gNB and location server functionality incorporated into the same base station 304), the data buses 334, 382, and 392 may provide for communication between the different logical entities.
[0094] Figure 3A , Figure 3B and Figure 3C The components of can be implemented in various ways. In some specific implementations, Figure 3A , Figure 3B and Figure 3C The components may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or be combined with at least one memory component for storing information or executable code used by the circuit to provide the functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by a processor and memory component of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by a processor and memory component of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Moreover, some or all of the functionality represented by blocks 390 to 398 may be implemented by a processor and memory component of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). For simplicity, various operations, actions, and / or functions are described herein as being performed by "UE", "by base station", "by network entity", etc. However, it should be understood that such operations, actions and / or functions may actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc. (such as processors 332, 384, 394, transceivers 310, 320, 350 and 360, memories 340, 386 and 396, positioning components 342, 388 and 398, etc.).
[0095] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be operated separately from a network operator or cellular network infrastructure (e.g., NG-RAN 220 and / or 5GC 210 / 260). For example, the network entity 306 may be a component of a dedicated network that may be configured to communicate with the UE 302 via the base station 304 or independently of the base station 304 (e.g., via a non-cellular communication link such as WiFi).
[0096] Figure 4 An example Long Term Evolution (LTE) Positioning Protocol (LPP) procedure 400 is illustrated for performing positioning operations between a UE 404 and a location server (illustrated as LMF 470). Figure 4 As illustrated, positioning of UE 404 is supported via the exchange of LPP messages between UE 404 and LMF 470. LPP messages may be exchanged between UE 404 and LMF 470 via a serving base station (illustrated as serving gNB 402) of UE 404 and a core network (not shown). LPP procedure 400 may be used to locate UE 404 in order to support various location-related services, such as for UE 404 (or for a user of UE 404), or for routing, or for providing accurate location to a public service access point (PSAP) in association with an emergency call from UE 404 to the PSAP, or for navigation for some other reason. LPP procedure 400 may also be referred to as a positioning session, and there may be multiple positioning sessions for different types of positioning methods (e.g., downlink time difference of arrival (DL-TDOA), round trip time (RTT), enhanced cell identification (E-CID), etc.).
[0097] Initially, at stage 410, UE 404 may receive a request for its positioning capabilities (e.g., an LPP Request Capabilities message) from LMF 470. At stage 420, UE 404 provides its positioning capabilities with respect to the LPP protocol to LMF 470 by transmitting an LPP Provide Capabilities message to LMF 470 indicating that UE 404 uses the positioning methods supported by LPP and the characteristics of these positioning methods. In some aspects, the capabilities indicated in the LPP Provide Capabilities message may indicate the types of positioning supported by UE 404 (e.g., DL-TDOA, RTT, E-CID, etc.) and may indicate the capabilities of UE 404 to support those types of positioning.
[0098] Upon receiving the LPP Provide Capability message, at stage 420, the LMF 470 determines to use a particular type of positioning method (e.g., DL-TDOA, RTT, E-CID, etc.) based on the indicated positioning type supported by the UE 404, and determines a set of one or more TRPs from which the UE 404 will measure downlink positioning reference signals or to which the UE 404 will send uplink positioning reference signals. At stage 430, the LMF 470 transmits an LPP Provide Assistance Data message to the UE 404 identifying the set of TRPs.
[0099] In some implementations, in response to an LPP request assistance data ( Figure 4 (not shown), the LPP provide assistance data message at stage 430 may be transmitted by LMF 470 to UE 404. The LPP request assistance data message may include an identifier of a serving TRP of UE 404 and a request for positioning reference signal (PRS) configuration of a neighboring TRP.
[0100] At stage 440, LMF 470 transmits a request for location information to UE 404. The request may be an LPP Request Location Information message. The message typically includes information elements defining the type of location information, the expected accuracy of the location estimate, and the response time (i.e., the expected latency). Note that a low latency requirement allows for a longer response time, while a high latency requirement requires a shorter response time. However, a long response time is referred to as high latency, and a short response time is referred to as low latency.
[0101] Note that in some implementations, the LPP provided assistance data transmitted at stage 430 may be transmitted after the LPP request location information message at 440, for example, if UE 404 transmits a request for assistance data to LMF 470 after receiving the request for location information at stage 440 (e.g., in the LPP request assistance data, Figure 4 This is the case (not shown).
[0102] At stage 450, UE 404 utilizes the assistance information received at stage 430 and any additional data received at stage 440 (e.g., desired position accuracy or maximum response time) to perform positioning operations (e.g., measurement of DL-PRS, transmission of UL-PRS, etc.) for the selected positioning method.
[0103] At stage 460, UE 404 may transmit an LPP Provide Location Information message to LMF 470 that conveys the results of any measurements (e.g., time of arrival (ToA), reference signal time difference (RSTD), received to transmitted (Rx-Tx), etc.) obtained at stage 450 and before or at the expiration of any maximum response time (e.g., the maximum response time provided by LMF 470 at stage 440). The LPP Provide Location Information message at stage 460 may also include one or more times at which the positioning measurements were obtained and an identification of the TRP from which the positioning measurements were obtained. Note that the time between the request for location information at 440 and the response at 460 is the "response time" and indicates the latency of the positioning session.
[0104] LMF 470 computes an estimated location of UE 404 based at least in part on the measurements received in the LPP Provide Location Information message at stage 460 using an appropriate positioning technique (eg, DL-TDOA, RTT, E-CID, etc.).
[0105] Various frame structures may be used to support downlink transmissions and uplink transmissions between network nodes (eg, a base station and a UE). Figure 5 5 is a diagram illustrating an example frame structure according to aspects of the present disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.
[0106] LTE (and in some cases NR) utilizes OFDM on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option of using OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often called tones, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15 kilohertz (kHz), and the minimum resource allocation (resource block) can be 12 subcarriers (or 180kHz). Therefore, for a system bandwidth of 1.25 megahertz (MHz), 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, the nominal FFT size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be divided into multiple subbands. For example, a subband may cover 1.08 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, respectively.
[0107] LTE supports a single parameter set (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR may support multiple parameter sets (μ), for example, 15kHz (μ=0), 30kHz (μ=1), 60kHz (μ=2), 120kHz (μ=3), and 240kHz (μ=4) or larger subcarrier spacings may be available. In each subcarrier spacing, there are 14 symbols per slot. For 15kHz SCS (μ=0), there is one slot per subframe, 10 slots per frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (μs), and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50. For 30kHz SCS (μ=1), there are two slots per subframe, 20 slots per frame, the slot duration is 0.5ms, the symbol duration is 33.3μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 100. For 60kHz SCS (μ=2), there are four slots per subframe, 40 slots per frame, the slot duration is 0.25ms, the symbol duration is 16.7μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 200. For 120kHz SCS (μ=3), there are eight slots per subframe, 80 slots per frame, the slot duration is 0.125ms, the symbol duration is 8.33μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 400. For 240kHz SCS (μ=4), there are 16 slots per subframe, 160 slots per frame, the slot duration is 0.0625ms, the symbol duration is 4.17μs, and the maximum nominal system bandwidth (in MHz) is 800 with 4K FFT size.
[0108] exist Figure 5 In the example of , a parameter set of 15 kHz is used. Thus, in the time domain, a 10 ms frame is divided into 10 equally sized subframes, each subframe is 1 ms, and each subframe includes one time slot. Figure 5 , time is represented horizontally (on the X-axis), where time increases from left to right, while frequency is represented vertically (on the Y-axis), where frequency increases (or decreases) from bottom to top.
[0109] A resource grid may be used to represent a time slot, each of which includes one or more time-concurrent resource blocks (RBs) in the frequency domain (also referred to as physical RBs (PRBs)). The resource grid is further divided into a plurality of resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. Figure 5In the parameter set of , for a normal cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an 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.
[0110] Some REs may carry reference (pilot) signals (RS). These 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), SSB, SRS, etc., depending on whether the illustrated frame structure is used for uplink or downlink communication. Figure 5 Example locations of REs carrying reference signals (labeled "R") are illustrated.
[0111] On the one hand, Figure 5 The reference signal carried on the RE marked with "R" in the figure can be an SRS. The SRS sent by the UE can be used by the base station to obtain the channel state information (CSI) of the sending UE. CSI describes how the RF signal propagates from the UE to the base station and represents the combined effects of scattering, fading, and power attenuation with distance. The system uses SRS for resource scheduling, link adaptation, massive MIMO, beam management, etc. In some aspects, SRS can be used as an uplink positioning reference signal (UL-PRS).
[0112] The set of REs used for transmission of PRS is called a "PRS resource". The RE set may span multiple PRBs in the frequency domain and "N" (such as 1 or more) consecutive symbols within a slot in the time domain. In a given OFDM symbol in the time domain, the PRS resource occupies consecutive PRBs in the frequency domain.
[0113] The transmission of PRS resources within a given PRB has a specific comb size (also referred to as "comb density"). The comb size "N" represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the PRS resource configuration. Specifically, for comb size "N", the PRS is transmitted in every Nth subcarrier of a symbol of the PRB. For example, for comb-4, for each symbol of the PRS resource configuration, the REs corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) are used to transmit the PRS of the PRS resource. Currently, comb sizes of comb-2, comb-4, comb-6, and comb-12 are supported for DL-PRS. Figure 5An example PRS resource configuration for comb-4 (which spans four symbols) is illustrated. That is, the positions of shaded REs (labeled as "R") indicate the PRS resource configuration of comb-4.
[0114] Currently, DL-PRS resources can span 2, 4, 6, or 12 consecutive symbols in a timeslot using a full frequency domain staggered pattern. DL-PRS resources can be configured in any downlink or flexible (FL) symbol configured by higher layers in a timeslot. There may be a constant energy per resource element (EPRE) for all REs of a given DL-PRS resource. The following are the symbol-by-symbol frequency offsets for comb sizes 2, 4, 6, and 12 on 2, 4, 6, and 12 symbols. 2-symbol Comb-2: {0,1}; 4-symbol Comb-2: {0,1,0,1}; 6-symbol Comb-2: {0,1,0,1,0,1}; 12-symbol Comb-2: {0,1,0,1,0,1,0,1,0,1,0,1}; 4-symbol Comb-4: {0,2,1,3} (as in Figure 5 in the example); 12-symbol comb-4: {0,2,1,3,0,2,1,3,0,2,1,3}; 6-symbol comb-6: {0,3,1,4,2,5}; 12-symbol comb-6: {0,3,1,4,2,5,0,3,1,4,2,5}; and 12-symbol comb-12: {0,6,3,9,1,7,4,10,2,8,5,11}.
[0115] A "PRS resource set" is a set of PRS resources used to send a PRS signal, where each PRS resource has a PRS resource ID. In addition, the PRS resources in the PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and is associated with a specific TRP (identified by the TRP ID). In addition, the PRS resources in the PRS resource set have the same periodicity, a common muting pattern configuration, and the same repetition factor (such as "PRS-ResourceRepetitionFactor") across time slots. The periodicity is the time from the first repetition of the first PRS resource of the first PRS instance to the same first repetition of the same first PRS resource of the next PRS instance. The periodicity may have a length selected from the following: 2^μ*{4,5,8,10,16,20,32,40,64,80,160,320,640,1280,2560,5120,10240} time slots, where μ=0,1,2,3. The repetition factor may have a length selected from {1, 2, 4, 6, 8, 16, 32} slots.
[0116] The PRS resource ID in a PRS resource set is associated with a single beam (or beam ID) transmitted from a single TRP (where a TRP may transmit one or more beams). That is, each PRS resource in a PRS resource set may be transmitted on a different beam, and therefore, a "PRS resource" (or simply "resource") may also be referred to as a "beam". Note that this does not have any implication on whether the UE knows the TRP and beam on which the PRS is transmitted.
[0117] A "PRS instance" or "PRS opportunity" is an instance of a periodically repeated time window (such as a group of one or more consecutive time slots) in which a PRS is expected to be sent. A PRS opportunity may also be referred to as a "PRS positioning opportunity," "PRS positioning instance," "positioning opportunity," "positioning instance," "positioning repetition," or simply "opportunity," "instance," or "repetition."
[0118] A "positioning frequency layer" (also referred to simply as a "frequency layer") is a set of one or more PRS resource sets with the same values for certain parameters across one or more TRPs. Specifically, the set of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning that all parameter sets supported by the physical downlink shared channel (PDSCH) are also supported by PRS), the same point A, the same value of the downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The point A parameter takes the value of the parameter "ARFCN-ValueNR" (where "ARFCN" stands for "absolute radio frequency channel number") and is an identifier / code that specifies a pair of physical radio channels used for transmission and reception. The downlink PRS bandwidth can have a granularity of four PRBs, and the minimum value is 24 PRBs and the maximum value is 272 PRBs. Currently, up to four frequency layers have been defined, and up to two PRS resource sets can be configured per TRP per frequency layer.
[0119] The concept of frequency layer is somewhat similar to the concept of component carrier and bandwidth part (BWP), but the difference is that component carrier and BWP are used by one base station (or macro cell base station and small cell base station) to send data channels, while frequency layer is used by several (usually three or more) base stations to send PRS. The UE can indicate the number of frequency layers that the UE can support when the UE transmits its positioning capabilities to the network (such as during an LTE Positioning Protocol (LPP) session). For example, the UE can indicate whether it can support one or four positioning frequency layers.
[0120] It should be noted that the terms "positioning reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "positioning reference signal" and "PRS" may also refer to any type of reference signal that can be used for positioning, such as but not limited to: PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc. as defined in LTE and NR. In addition, the terms "positioning reference signal" and "PRS" may refer to a downlink positioning reference signal, an uplink positioning reference signal, or a sidelink positioning reference signal, unless otherwise indicated by the context. If it is necessary to further distinguish the type of PRS, the downlink positioning reference signal may be referred to as a "DL-PRS", the uplink positioning reference signal (e.g., SRS, PTRS for positioning) may be referred to as a "UL-PRS", and the sidelink positioning reference signal may be referred to as a "SL-PRS". In addition, for signals (eg, DMRS) that may be transmitted in downlink, uplink, and / or sidelink, these signals may be prefixed with "DL", "UL", or "SL" to distinguish directions. For example, "UL-DMRS" may be different from "DL-DMRS".
[0121] NR supports a variety of cellular network-based positioning technologies, including downlink-based positioning methods, uplink-based positioning methods, and downlink and uplink-based positioning methods. Downlink-based positioning methods include: Observed Time Difference of Arrival (OTDOA) in LTE, Downlink Time Difference of Arrival (DL-TDOA) in NR, and Downlink Angle of Departure (DL-AoD) in NR. Figure 6 Examples of various positioning methods according to various aspects of the present disclosure are illustrated. In the OTDOA or DL-TDOA positioning procedure illustrated in scenario 610, the UE measures the difference between the ToA of the reference signal (e.g., PRS) received from the paired base stations (referred to as RSTD or TDOA measurement), and reports these differences to the positioning entity. More specifically, the UE receives identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in auxiliary data (auxiliary data). The UE then measures the RSTD between the reference base station and each non-reference base station. Based on the known positions of the base stations involved and the RSTD measurements, a positioning entity (e.g., a UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the position of the UE.
[0122] For DL-AoD positioning illustrated in scenario 620, the positioning entity uses measurement reports from the UE regarding received signal strength measurements of multiple downlink transmit beams to determine the angle between the UE and the transmitting base station. The positioning entity can then estimate the position of the UE based on the determined angle and the known position of the transmitting base station.
[0123] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle of arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but is based on uplink reference signals (e.g., SRS) sent by the UE to multiple base stations. Specifically, the UE sends one or more uplink reference signals measured by a reference base station and multiple non-reference base stations. Each base station then reports the reception time of the reference signal (referred to as relative time of arrival (RTOA)) to a positioning entity (e.g., a location server) that knows the location and relative timing of the base stations involved. Based on the received-to-receive (Rx-Rx) time difference between the reported RTOA of the reference base station and the reported RTOA of each non-reference base station, the known location of the base stations, and their known timing offsets, the positioning entity can use TDOA to estimate the position of the UE.
[0124] For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. The positioning entity uses the signal strength measurements and the angle of the receive beams to determine the angle between the UE and the base station. Based on the determined angle and the known location of the base station, the positioning entity can then estimate the location of the UE.
[0125] Downlink and uplink based positioning methods include: enhanced cell ID (E-CID) positioning and multi-RTT positioning (also referred to as "multi-cell RTT" and "multi-RTT"). In the RTT procedure, a first entity (e.g., a base station or UE) sends a first RTT-related signal (e.g., a PRS or SRS) to a second entity (e.g., a UE or a base station), and the second entity sends a second RTT-related signal (e.g., an SRS or PRS) back to the first entity. Each entity measures the time difference between the ToA of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. The time difference is called the received-to-transmit (Rx-Tx) time difference. The Rx-Tx time difference measurement can be made or adjusted to include only the time difference between the nearest time slot boundary of the received signal and the transmitted signal. The two entities may then transmit their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round trip propagation time (i.e., RTT) between the two entities based on the two Rx-Tx time difference measurements (e.g., calculated as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity may transmit its Rx-Tx time difference measurements to the other entity, which then calculates the RTT. The distance between the two entities may be determined based on the RTT and a known signal speed (e.g., the speed of light). For multi-RTT positioning illustrated in scenario 630, a first entity (e.g., a UE or a base station) performs an RTT positioning procedure with multiple second entities (e.g., multiple base stations or UEs) to enable the location of the first entity to be determined (e.g., using multilateration) based on the distance to the second entities and the known locations of the second entities. RTT and multi-RTT methods may be combined with other positioning techniques such as UL-AoA and DL-AoD to improve location accuracy, as illustrated in scenario 640.
[0126] The E-CID positioning method is based on radio resource management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), and the identifiers, estimated timing and signal strength of the detected neighboring base stations. The UE's position is then estimated based on this information and the known locations of the base stations.
[0127] To assist the positioning operation, the location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE. For example, the assistance data may include: an identifier of the base station (or cell / TRP of the base station) from which the reference signal is measured, reference signal configuration parameters (e.g., the number of consecutive time slots including PRS, the periodicity of consecutive time slots including PRS, the silent sequence, the frequency hopping sequence, the reference signal identifier, the reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, the assistance data may originate directly from the base station itself (e.g., in an overhead message broadcast periodically, etc.). In some cases, the UE itself may be able to detect neighboring network nodes without using assistance data.
[0128] In the case of OTDOA or DL-TDOA positioning procedures, the assistance data may also include an expected RSTD value and associated uncertainty, or a search window around the expected RSTD. In some cases, the value range of the expected RSTD may be + / -500 microseconds (μs). In some cases, when any resource used for positioning measurements is in FR1, the value range of the uncertainty of the expected RSTD may be + / -32μs. In other cases, when all resources used for positioning measurements are in FR2, the value range of the uncertainty of the expected RSTD may be + / -8μs.
[0129] The position estimate may be referred to by other names, such as a position estimate, a position, a fix, a position fix, a fix, etc. The position estimate may be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or may be municipal and include a street address, a postal address, or some other verbal description of the location. The position estimate may be further defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possibly altitude). The position estimate may include an expected error or uncertainty (e.g., by including an area or volume within which the location is expected to be contained with some specified or default confidence level).
[0130] Figure 7 The TDOA-based positioning procedure in an example wireless communication system 700 according to various aspects of the present disclosure is illustrated. The TDOA-based positioning procedure may be an OTDOA positioning procedure as in LTE, or a downlink time difference of arrival (DL-TDOA) positioning procedure as in 5G NR. Figure 7In the example of , a UE 704 (e.g., any UE described herein) is attempting to compute an estimate of its location (referred to as "UE-based" positioning), or assist another entity (e.g., a base station or core network component, another UE, a location server, a third-party application, etc.) in computing an estimate of its location (referred to as "UE-assisted" positioning). The UE 704 may communicate with (e.g., transmit information to and receive information from) one or more base stations of a plurality of base stations 702 (e.g., any combination of base stations described herein), the plurality of base stations being labeled "BS1" 702-1, "BS2" 702-2, and "BS3" 702-3.
[0131] To support position estimation, the base station 702 may be configured to broadcast PRS, TRS, CRS, channel state information reference signal (CSI-RS), demodulation reference signal (DMRS), etc.) to the UE 704 in its coverage area to enable the UE 704 to measure the characteristics of such reference signals. In a TDOA-based positioning procedure, the UE 704 measures the time difference (referred to as RSTD or TDOA) between specific downlink reference signals (e.g., PRS, TRS, CRS, CSI-RS, etc.) sent by different pairs of base stations 702, and reports these RSTD measurements to a location server (e.g., location server 230, LMF 270, SLP 272) or calculates a position estimate based on these RSTD measurements.
[0132] Generally speaking, in a reference cell (e.g., Figure 7 ) and one or more neighboring cells (e.g., Figure 7 RSTD is measured between cells supported by base stations 702-2 and 702-3 in the example of TDOA). For all RSTDs measured using the measurements by UE 704 for any single positioning for TDOA, the reference cell remains the same and will typically correspond to the serving cell for UE 704 or another nearby cell with good signal strength at UE 704. In one aspect, a neighboring cell is typically a cell supported by a different base station than the base station for the reference cell and may have good or poor signal strength at UE 704. The position calculation can be based on the measured RSTD and knowledge of the locations and relative transmit timings of the base stations 702 involved (e.g., whether the base stations 702 are accurately synchronized or whether each base station 702 transmits at some known time offset relative to the other base stations 702).
[0133] To assist in TDOA-based positioning operations, a location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data for a reference cell and neighboring cells relative to the reference cell to UE 704. For example, the assistance data may include an identifier (e.g., PCI, VCI, CGI, etc.) for each cell in a set of cells that the UE 704 is expected to measure (here, cells supported by the base station 702). The assistance data may also provide a center channel frequency for each cell, various reference signal configuration parameters (e.g., number of consecutive positioning slots, periodicity of positioning slots, silent sequence, frequency hopping sequence, reference signal identifier, reference signal bandwidth), and / or other cell-related parameters applicable to TDOA-based positioning procedures. The assistance data may also indicate a serving cell for the UE 704 as a reference cell.
[0134] In some cases, the assistance data may also include an "expected RSTD" parameter and the uncertainty of the expected RSTD parameter, which provides information to the UE 704 about the RSTD value that the UE 704 is expected to measure between the reference cell and each neighboring cell at its current location. The expected RSTD and the associated uncertainty may define a search window for the UE 704, within which the UE 704 is expected to measure the RSTD value. In some cases, the value range of the expected RSTD may be + / -500 microseconds (μs). In some cases, when any resource used for positioning measurements is in FR1, the value range of the uncertainty of the expected RSTD may be + / -32μs. In other cases, when all resources used for positioning measurements are in FR2, the value range of the uncertainty of the expected RSTD may be + / -8μs.
[0135] The TDOA assistance information may also include positioning reference signal configuration information parameters that allow UE 704 to determine when the positioning reference signal timing will occur on the signals received from various neighboring cells relative to the positioning reference signal timing of the reference cell, and to determine the reference signal sequences sent from various cells in order to measure reference signal ToA or RSTD.
[0136] In one aspect, although a location server (e.g., location server 230, LMF 270, SLP 272) can transmit assistance data to UE 704, alternatively, the assistance data can originate directly from base station 702 itself (e.g., in a periodically broadcast overhead message, etc.). Alternatively, UE 704 can detect neighboring base stations on its own without using assistance data.
[0137] UE 704 (e.g., based in part on assistance data, if provided) may measure and (optionally) report RSTD between reference signals received from pairs of base stations 702. Using RSTD measurements, known absolute transmit timing or relative transmit timing of each base station 702, and known locations of reference and neighboring base stations 702, a network (e.g., location server 230 / LMF270 / SLP 272, base stations 702) or UE 704 may estimate the location of UE 704. More specifically, the RSTD of neighboring cell "k" relative to reference cell "Ref" may be represented by (ToA_k-ToA_Ref). In Figure 7 In the example of , the RSTD measured between the reference cell of base station 702-1 and the cells of neighboring base stations 702-2 and 702-3 can be represented as T2-T1 and T3-T1, where T1, T2 and T3 represent the ToA of the reference signals from base stations 702-1, 702-2 and 702-3, respectively. Then, UE 704 (if it is not a positioning entity) can transmit the RSTD measurement to a location server or another positioning entity. Using (i) RSTD measurements, (ii) known absolute transmit timing or relative transmit timing of each base station 702, (iii) known location of base station 702 and / or (iv) directional reference signal characteristics (such as transmit direction), the location of UE 704 can be determined (by UE 704 or location server).
[0138] In one aspect, the position estimate may specify the position of the UE 704 in a two-dimensional (2D) coordinate system; however, the aspects disclosed herein are not limited in this regard and may also be adapted to determine a position estimate using a three-dimensional (3D) coordinate system where additional dimensions are desired. Figure 7 One UE 704 and three base stations 702 are illustrated, but it should be understood that more UEs 704 and more base stations 702 may exist.
[0139] Still reference Figure 7 , when UE 704 uses RSTD to obtain a position estimate, the necessary additional data (e.g., the position and relative transmit timing of base station 702) may be provided to UE 704 by a location server. In some implementations, a position estimate for UE 704 may be obtained (e.g., by UE 704 itself or by a location server) from RSTD and from other measurements made by UE 704 (e.g., measurements of signal timing from GPS or other global navigation satellite system (GNSS) satellites). In these implementations (referred to as hybrid positioning), RSTD measurements may help obtain a position estimate for UE 704, but may not fully determine the position estimate.
[0140] Figure 88 is a diagram 800 illustrating a base station (BS) 802 (which may correspond to any of the base stations described herein) communicating with a UE 804 (which may correspond to any of the UEs described herein). Figure 8 , the base station 802 may transmit beamforming signals to the UE 804 on one or more transmit beams 812a, 812b, 812c, 812d, 812e, 812f, 812g, 812h (collectively referred to as beams 812), each of which has a beam identifier that can be used by the UE 804 to identify the corresponding beam. In the case where the base station 802 performs beamforming toward the UE 804 with a single antenna array (e.g., a single TRP / cell), the base station 802 may perform "beam scanning" by transmitting a first beam 812a, then beam 812b, and so on, until finally transmitting beam 812h. Alternatively, the base station 802 may transmit beams 812 in a pattern, such as beam 812a, then beam 812h, then beam 812b, then beam 812g, and so on. In the case where the base station 802 uses multiple antenna arrays (e.g., multiple TRPs / cells) to perform beamforming toward the UE 804, each antenna array may perform beam scanning of a subset of the beams 812. Alternatively, each of the beams 812 may correspond to a single antenna or antenna array.
[0141] Figure 8 Paths 812c, 812d, 812e, 812f, and 812g are further illustrated as being followed by beamformed signals transmitted on beams 812c, 812d, 812e, 812f, and 812g, respectively. Each path 812c, 812d, 812e, 812f, 812g may correspond to a single "multipath," or may be composed of multiple "multipaths" (a "multipath" cluster) due to the propagation characteristics of RF signals through the environment. Note that while only paths for beams 812c-812g are shown, this is for simplicity, and the signal transmitted on each of the beams in beam 812 will follow a path. In the example shown, paths 812c, 812d, 812e, and 812f are straight lines, while path 812g is reflected by an obstacle 820 (e.g., a building, a vehicle, a terrain feature, etc.).
[0142] UE 804 may receive beamformed signals from base station 802 on one or more receive beams 814a, 814b, 814c, 814d (collectively referred to as beams 814). Note that for simplicity, Figure 8The illustrated beams represent either transmit beams or receive beams, depending on which of the base station 802 and the UE 804 is transmitting and which is receiving. Thus, the UE 804 may also transmit beamformed signals to the base station 802 on one or more of the beams 814, and the base station 802 may receive beamformed signals from the UE 804 on one or more of the beams 812.
[0143] In an aspect, the base station 802 and the UE 804 may perform beam training to align the transmit beams and receive beams of the base station 802 and the UE 804. For example, depending on environmental conditions and other factors, the base station 802 and the UE 804 may determine that the best transmit beam and receive beam are 812d and 814b, respectively, or beams 812e and 814c, respectively. The direction of the best transmit beam of the base station 802 may be the same as or different from the direction of the best receive beam, and similarly, the direction of the best receive beam of the UE 804 may be the same as or different from the direction of the best transmit beam. However, it is noted that aligning the transmit beam and the receive beam is not necessary to perform DL-AoD or UL-AoA positioning procedures.
[0144] To perform the DL-AoD positioning procedure, the base station 802 may transmit reference signals (e.g., PRS, CRS, TRS, CSI-RS, PSS, SSS, etc.) to the UE 804 on one or more of the beams 812, each of which has a different transmit angle. The different transmit angles of the beams will result in different received signal strengths (e.g., RSRP, RSRQ, SINR, etc.) at the UE 804. Specifically, compared to a transmit beam 812 that is closer to a line of sight (LOS) path 810 between the base station 802 and the UE 804, the received signal strength will be lower for a transmit beam 812 that is farther away from the LOS path 810.
[0145] exist Figure 8 In the example of FIG. 8 , if base station 802 transmits reference signals to UE 804 on beams 812c, 812d, 812e, 812f, and 812g, transmit beam 812e is optimally aligned with LOS path 810, while transmit beams 812c, 812d, 812f, and 812g are not optimally aligned with the LOS path. Therefore, beam 812e is likely to have a higher received signal strength at UE 804 than beams 812c, 812d, 812f, and 812g. Note that reference signals transmitted on some beams (e.g., beams 812c and / or 812f) may not reach UE 804, or the energy reaching UE 804 from these beams may be so low that the energy may not be detected or at least may be ignored.
[0146] UE 804 may report to base station 802 the received signal strength of each measured transmit beam 812c-812g and, optionally, the associated measurement quality, or, alternatively, the transmit beam with the highest received signal strength (in Figure 8 In the example of beam 812e), the UE 804 may also include an identifier of the transmit beam 812e. Alternatively or additionally, if the UE 804 is also participating in an RTT or TDOA positioning session with at least one base station 802 or multiple base stations 812, respectively, the UE 804 may report the received transmit (Rx-Tx) time difference or RSTD measurement (and optionally the associated measurement quality) to the serving base station 802 or other positioning entity, respectively. In any case, the positioning entity (e.g., base station 802, location server, third-party client, UE 804, etc.) may estimate the angle from the base station 802 to the UE 804 as the AoD of the transmit beam (here, transmit beam 812e) with the highest received signal strength at the UE 804.
[0147] In one aspect of DL-AoD based positioning, in the case where there is only one base station 802 involved, the base station 802 and the UE 804 may perform an RTT procedure to determine the distance between the base station 802 and the UE 804. Thus, the positioning entity may determine both the direction to the UE 804 (using DL-AoD positioning) and the distance to the UE 804 (using RTT positioning) to estimate the position of the UE 804. It should be noted that the AoD of the transmit beam with the highest received signal strength is not necessarily located along the LOS path 810, as shown in FIG. Figure 8 However, for the purpose of DL-AoD based positioning, it is assumed to be so.
[0148] In another aspect of DL-AoD based positioning, where there are multiple involved base stations 812, each involved base station 802 may report the determined AoD or RSRP measurement from the corresponding base station 802 to the UE 804 to the serving base station 802. The serving base station 802 may then report the AoD or RSRP measurements from the other involved base stations 812 to a positioning entity (e.g., a UE 804 for UE-based positioning or a location server for UE-assisted positioning). Using this information and knowledge of the geographic locations of the base stations 812, the positioning entity may estimate the location of the UE 804 as the intersection of the determined AoDs. For a two-dimensional (2D) location solution, there should be at least two involved base stations 812, but as will be appreciated, the more base stations 812 involved in the positioning procedure, the more accurate the estimated location of the UE 804 will be.
[0149] In order to perform the UL-AoA positioning procedure, the UE 804 transmits an uplink reference signal (e.g., UL-PRS, SRS, DMRS, etc.) to the base station 802 on one or more uplink transmit beams in the uplink transmit beams 814. The base station 802 receives the uplink reference signal on one or more uplink receive beams in the uplink receive beams 812. The base station 802 determines the angle of the best receive beam 812 for receiving the one or more reference signals from the UE 804 as the AoA from the UE 804 to itself. Specifically, each receive beam in the receive beams 812 will result in a different received signal strength (e.g., RSRP, RSRQ, SINR, etc.) of the one or more reference signals at the base station 802. In addition, compared to the receive beam 812 that is closer to the actual LOS path between the base station 802 and the UE 804, the channel impulse response of the one or more reference signals will be smaller for the receive beam 812 that is farther away from the LOS path. Likewise, the received signal strength will be lower for a receive beam 812 that is further away from the LOS path than for a receive beam 812 that is closer to the LOS path. Therefore, the base station 802 identifies the receive beam 812 that results in the highest received signal strength and, optionally, the strongest channel impulse response, and estimates the angle from itself to the UE 804 as the AoA of that receive beam 812. Note that, as with DL-AoD based positioning, the AoA of the receive beam 812 that results in the highest received signal strength (and, in the case of measurement, the strongest channel impulse response) is not necessarily located along the LOS path 810. However, in FR2, this may be assumed for UL-AoA based positioning purposes.
[0150] Note that although the UE 804 is illustrated as being capable of beamforming, this is not necessary for the DL-AoD and UL-AoA positioning procedures. Instead, the UE 804 may receive and transmit on omni-directional antennas.
[0151] In the case where UE 804 is estimating its position (i.e., UE is the positioning entity), it is necessary to obtain the geographic location of base station 802. UE 804 can obtain the position from, for example, base station 802 itself or a location server (e.g., location server 230, LMF 270, SLP 272). By knowing the distance to base station 802 (based on RTT or TA), the angle between base station 802 and UE 804 (based on UL-AoA of best receive beam 812), and the known geographic location of base station 802, UE 804 can estimate its position.
[0152] Alternatively, where a positioning entity such as a base station 802 or a location server is estimating the position of a UE 804, the base station 802 reports the AoA of the receive beam 812 that results in the highest received signal strength (and optionally the strongest channel impulse response) of the reference signal received from the UE 804, or all received signal strengths and channel impulse responses for all receive beams 812 (which allows the positioning entity to determine the best receive beam 812). The base station 802 may additionally report the Rx-Tx time difference to the UE 804. The positioning entity may then estimate the position of the UE 804 based on the distance of the UE 814 to the base station 802, the AoA of the identified receive beam 812, and the known geographic location of the base station 802.
[0153] Fig. 9 An example network node location service procedure 900 according to aspects of the present disclosure is illustrated. In this example, the network node that is the target device of the location service procedure is the UE 204. The network node location service procedure 900 may be performed by the UE 204, the NG-RAN node 902 in the NG-RAN 220 (e.g., the gNB 222, the gNB-CU 226, the ng-eNB 224, or other nodes in the NG-RAN 220), the AMF 264, the LMF 270, and the 5GC location service (LCS) entity 980 (e.g., any third-party application requesting the location of the UE 204, a PSAP, an E-911 server, etc.).
[0154] The location service request to obtain the location of the target (i.e., UE 204) can be initiated by the 5GC LCS entity 980, the AMF 264 serving UE 204, or the UE 204 itself. Fig. 9 These options are illustrated as stages 910a, 910b, and 910c, respectively. Specifically, at stage 910a, the 5GC LCS entity 980 transmits a location service request to the AMF 264. Alternatively, at stage 910b, the AMF 264 itself generates the location service request. Alternatively, at stage 910c, the UE 204 transmits a location service request to the AMF 264.
[0155] Once the AMF 264 receives (or generates) the location service request, it forwards the location service request to the LMF 270 at stage 920. The LMF 270 then performs NG-RAN positioning procedures with the NG-RAN node 902 at stage 930a and UE positioning procedures with the UE 204 at stage 930b. The specific NG-RAN positioning procedures and UE positioning procedures may depend on the type of positioning method used to locate the UE 204, which may depend on the capabilities of the UE 204. The positioning method may be downlink-based (e.g., LTE-OTDOA, DL-TDOA, DL-AoD, etc.), uplink-based (e.g., UL-TDOA, UL-AoA, etc.), and / or downlink and uplink-based (e.g., LTE / NR E-CID, multi-RTT, etc.), as described above.
[0156] The NG-RAN positioning procedures and the UE positioning procedures may utilize LPP signaling between the UE 204 and the LMF 270 and LPP Type A (LPPa) or New Radio Positioning Protocol Type A (NRPPa) signaling between the NG-RAN node 902 and the LMF 270. LPP is used point-to-point between a location server (e.g., LMF 270) and a UE (e.g., UE 204) to obtain location-related measurements or location estimates or to transfer assistance data. A single LPP session is used to support a single location request (e.g., for a single mobile-terminated location request (MT-LR), mobile-originated location request (MO-LR), or network-induced location request (NI-LR)). Multiple LPP sessions may be used between the same endpoints to support multiple different location requests. Each LPP session includes one or more LPP transactions, where each LPP transaction performs a single operation (e.g., capability exchange, assistance data transfer, or location information transfer). LPP transactions are referred to as LPP procedures.
[0157] A prerequisite for stage 930 is that the LCS correlation identifier (ID) and the AMF ID have been passed to the LMF 270 by the serving AMF 264. Both the LCS correlation ID and the AMF ID may be represented as strings selected by the AMF 264. The LCS correlation ID and the AMF ID are provided to the LMF 270 by the AMF 264 in the location service request at stage 920. When the LMF 270 subsequently initiates stage 930, the LMF 270 also includes the LCS correlation ID for the location session and the AMF ID indicating the AMF instance serving the UE 204. The LCS correlation ID is used to ensure that during the positioning session between the LMF 270 and the UE 204, the positioning response message from the UE 204 is returned by the AMF 264 to the correct LMF 270 and carries an indication (LCS correlation ID) that can be recognized by the LMF 270.
[0158] Note that the LCS correlation ID is used as a location session identifier, which can be used to identify messages exchanged between the AMF 264 and the LMF 270 for a specific location session for the UE 204, as described in more detail in 3GPP TS 23.273, which is publicly available and incorporated herein by reference in its entirety. As mentioned above and shown in stage 920, the location session between the AMF 264 and the LMF 270 for a specific UE 204 is initiated by the AMF 264, and the LCS correlation ID can be used to identify the location session (e.g., can be used by the AMF 264 to identify state information of the location session, etc.).
[0159] LPP signaling can be used to request and report measurement results related to the following positioning methods: LTE-OTDOA, DL-TDOA, A-GNSS, E-CID, Sensor, TBS, WLAN, Bluetooth, DL-AoD, UL-AoA, and Multi-RTT. Currently, an LPP measurement report can include the following measurement results: (1) one or more ToA, TDOA, RSTD, or Rx-Tx time difference measurement results, (2) one or more AoA and / or AoD measurement results (currently only used for base stations to report UL-AoA and DL-AoD to LMF 270), (3) one or more multipath measurement results (ToA, RSRP, AoA / AoD per path), (4) one or more motion states (e.g., walking, driving, etc.) and trajectories (currently only used for UE 204), and (5) one or more report quality indicators.
[0160] As part of the NG-RAN node positioning procedure (stage 930a) and the UE positioning procedure (stage 930b), the LMF 270 may provide LPP assistance data in the form of downlink positioning reference signal (DL-PRS) configuration information for the selected positioning method to the NG-RAN node 902 and the UE 204. Alternatively or additionally, the NG-RAN node 902 may provide DL-PRS and / or uplink PRS (UL-PRS) configuration information to the UE 204 for the selected positioning method. Note that although Fig. 9 A single NG-RAN node 902 is illustrated, but multiple NG-RAN nodes 902 may be involved in a positioning session.
[0161] Once configured with the DL-PRS and / or UL-PRS configuration, the NG-RAN node 902 and the UE 204 send and receive / measure the corresponding PRS at the scheduled time. The NG-RAN node 902 and the UE 204 then transmit their corresponding measurements to the LMF 270. In some cases, the NG-RAN node 902 may transmit its measurements to the UE 204, which may forward them to the LMF 270 using LPP signaling. Alternatively, the NG-RAN node 902 may transmit its measurements directly to the LMF 270 in LPPa or NRPPa signaling. In some cases, the UE 204 may transmit its measurements to the NG-RAN node 902 in RRC, uplink control information (UCI), or MAC control element (MAC-CE) signaling, and the NG-RAN node 902 may forward the measurements to the LMF 270 using LPPa or NRPPa signaling. Alternatively, the UE 204 may transmit its measurements directly to the LMF 270 using LPP signaling.
[0162] Once the LMF 270 obtains measurements from the UE 204 and / or the NG-RAN node 902 (depending on the type of positioning method), it uses those measurements to calculate an estimate of the location of the UE 204. Subsequently, at stage 940, the LMF 270 transmits a location service response including a location estimate for the UE 204 to the AMF 264. The AMF 264 then forwards the location service response to the entity that generated the location service request at stage 950. Specifically, if the location service request was received from the 5GC LCS entity 980 at stage 910a, then at stage 950a, the AMF 264 transmits the location service response to the 5GC LCS entity 980. However, if the location service request was received from the UE 204 at stage 910c, then at stage 950c, the AMF 264 transmits the location service response to the UE 204. Alternatively, if the AMF 264 generates a location services request at stage 910b, then at stage 950b, the AMF 264 itself stores / uses the location services response.
[0163] Note that although the foregoing has described the network node location service procedure 900 as a UE-assisted positioning operation, it may be replaced by a UE-based positioning operation. A UE-assisted positioning operation is an operation in which the LMF 270 calculates the location of the UE 204, while a UE-based positioning operation is an operation in which the UE 204 calculates its own location. In the case of a UE-based positioning operation, stages 910c and 950c will be performed. The LMF 270 may still coordinate the transmission / measurement of the DL-PRS (and possibly the UL-PRS), but the measurement will be forwarded to the UE 204 instead of the LMF 270. Therefore, the location service response at stages 940 and 950c may be a measurement from the NG-RAN node 902 involved, rather than a location estimate of the UE 204. Alternatively, where the NG-RAN nodes 902 involved forward their respective measurements directly to the UE 204 (e.g., via RRC signaling), the location service response at stage 940 may simply be an acknowledgement of completion of the NG-RAN node and UE positioning procedures at stage 930.
[0164] NR positioning operations have security vulnerabilities and can be subject to several PRS attack scenarios. In one PRS attack scenario, the PRS attacker has knowledge of the previous PRS sequence used in the positioning operation. The PRS attacker receives one or more PRS symbols, determines the transmission parameters, and sends a new signal for the subsequent PRS. Instead of measuring the PRS sent from the correct PRS source, the base station or UE measures the PRS sent by the PRS attacker, thereby generating measurements that result in an erroneous positioning determination.
[0165] In another PRS attack scenario, the PRS attacker receives a complete PRS configuration via broadcast assistance data or unicast RRC. The PRS attacker sends PRS based on information obtained from the complete PRS configuration. Again, instead of measuring the PRS sent from the correct PRS source, the base station or UE measures the PRS sent by the PRS attacker, thereby generating measurements that result in an erroneous positioning determination.
[0166] According to certain aspects of the present disclosure, certain characteristics of the received PRS can be used to distinguish between a PRS sent by a trusted TRP and a PRS sent by a PRS attacker. In one aspect, a UE or a base station (one or both of which are referred to herein as a "receiving entity") can perform a check for time domain consistency of the PRS and / or SRS. One way to check time domain consistency involves monitoring the channel impulse (energy) response (CER). In general, Fig.10 1000 is a diagram representing a channel impulse response 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 present disclosure. The channel impulse response represents the strength of an RF signal received through the multipath channel as a function of time delay. Thus, the horizontal axis is in units of time (e.g., milliseconds) and the vertical axis is in units of signal strength (e.g., decibels). It is noted that a multipath channel is a channel between a transmitter and a receiver over which an RF signal follows multiple paths or multipaths due to the transmission of the RF signal on multiple beams and / or due to the propagation characteristics of the RF signal (e.g., reflection, refraction, etc.).
[0167] exist Fig.10 In the example of , the receiver detects / measures multiple (four) clusters of channel taps. Each channel tap represents the multipath followed by the RF signal between the transmitter and the receiver, and in some instances, represents the RF signal sent by the attacker. That is, the channel taps represent the arrival of the RF signal on the multipath and / or from the attacker. Each cluster of channel taps indicates that the corresponding multipath follows substantially the same path. Different clusters may exist due to 1) the RF signal being transmitted on different transmit beams (and therefore at different angles), 2) the propagation characteristics of the RF signal (e.g., may follow different paths due to reflections), 3) the RF signal being transmitted by the attacker, or 4) any combination thereof.
[0168] The cluster of all channel taps for a given RF signal represents the multipath channel (or simply channel) between the transmitter and the receiver. Fig.10Under the illustrated channel, the receiver receives a first cluster of two RF signals on the channel taps at time T1, a second cluster of five RF signals on the channel taps at time T2, a third cluster of five RF signals on the channel taps at time T3, and a fourth cluster of four RF signals on the channel taps at time T4. Fig.10 In the example of , because the first RF signal cluster at time T1 arrives first, it is assumed to correspond to RF signals transmitted on a transmit beam aligned with the LOS or shortest path. The third cluster at time T3 includes the strongest RF signals and may correspond to, for example, RF signals transmitted on a transmit beam aligned with a non-line-of-sight (NLOS) path. Note that although Fig.10 Clusters of two to five channel taps are illustrated, but it should be understood that a cluster may have more or less channel taps than the illustrated number of channel taps.
[0169] In one aspect of PRS aggressor detection, a receiving entity repeatedly checks the consistency of the CER across multiple PRSs and / or SRSs (both of which are designated as "PRSs" hereinafter). To this end, the receiving entity may combine N PRS symbols for each PRS resource and estimate the ToA by CER peak detection. The receiving entity may repeatedly check the time domain consistency across different resources. The time domain consistency detection may include peak position consistency, power delay profile (also referred to as CER) consistency, etc. If such time domain parameters are inconsistent, certain PRSs and / or SRSs (hereinafter referred to as "PRSs") measured in the channel may originate from sources other than the trusted TRP and may include PRSs sent by a PRS aggressor.
[0170] On the other hand, the receiving entity may check the consistency of the CER across each PRS symbol within the PRS resource. To do this, the receiving entity may estimate the CER for each PRS symbol within the PRS resource. For a comb pattern of N PRS resources, the receiving entity should expect N CER peaks. The receiving entity may check the time domain consistency across different PRS symbols. The time domain consistency detection may include peak position consistency, power delay distribution consistency, etc. Similarly, if such measurement results are inconsistent, some of the measured PRSs may originate from sources that are not real TRPs and may include PRSs sent by PRS attackers.
[0171] On the other hand, the receiving entity may compare the CER across PRS symbols and / or PRS resources with other communication reference signal (RS) symbols and / or resources. For security purposes, PRS may be QCL with some unicast communication RS (e.g., TRS, CSI-RS, DMRS). The receiving entity may compare the CER estimated from the PRS with its associated unicast communication RS. If the receiving entity observes time domain inconsistency of the CER, the receiving entity may classify the received PRS as a PRS attack event.
[0172] According to certain aspects of the present disclosure, a receiving entity may receive RSTD assistance data for PRS processing from a base station and / or a location server. On the one hand, the receiving entity may be provided with an expected RSTD measurement value and a corresponding value uncertainty (e.g., a search window) of the TRP in the assistance data to be measured by the receiving entity. As an example, according to certain aspects, when any resource used for DL positioning measurements is in FR1, the value range of the uncertainty of the expected RSTD may be + / -32μs. According to certain aspects, when all resources used for DL positioning measurements are in FR2, the value range of the uncertainty of the expected RSTD may be + / -8μs.
[0173] The receiving entity may also monitor the PRS for angle domain consistency to detect transmissions by PRS attackers. In one aspect, the receiving entity may be able to estimate the AoA of each PRS through digital beamforming. The receiving entity (such as a UE) may also obtain its own position through a previous NR positioning lock and / or a non-RAT positioning method (such as a GNSS). Further, the UE may be able to obtain the position of the base station (e.g., gNB) or other TRP position through auxiliary data to estimate the AoA. Based on such estimates, the UE may check the angle domain consistency across different PRS symbols and / or PRS resources. For example, the receiving entity may check the difference between the AoA of the PRS estimated based on the known TRP position and the measurement of the AoA determined based on the measurement of the actual PRS transmission to determine the angle consistency. In one aspect, the receiving entity may compare the estimated angle with one or more previous angle measurements of one or more recently received PRSs. In various aspects, the estimated angle may be determined according to RAT-dependent techniques, RAT-independent techniques, or any combination thereof. In one aspect, the receiving entity may check the angle estimate consistency across multiple PRS symbols and resources. If the receiving entity observes angular domain inconsistency of the PRS, the receiving entity may classify the received PRS as a PRS attack event.
[0174] In certain aspects, angular domain consistency can be combined with the time domain consistency check to address situations where the PRS attacker is located along the propagation path between receiving entities (e.g., between the gNB and the UE). Moreover, this combination is advantageous in cases where the PRS attacker obtains a rough estimate of the location of the victim receiving entity and uses this rough estimate when determining the timing of the transmission of the attack PRS.
[0175] According to certain aspects of the present disclosure, a receiving entity (such as a UE) may receive angle assistance data (e.g., expected AoA, expected AoD, expected departure zenith angle (ZoD), expected arrival zenith angle (ZoA), or other expected angle measurements, any of which may be referred to as "expected angle measurements") from a base station, a location server, or any combination thereof. In one aspect, the expected angle measurement values and the corresponding expected angle measurement uncertainties for the TRP indicated in the assistance data may be provided to the UE. In one aspect, for each TRP that the UE is to measure during a positioning session, a single expected angle measurement value (e.g., AoD and / or ZoD) and the corresponding uncertainty range for the expected angle measurement value may be provided to the UE. In one aspect, indications of multiple expected angle measurements (e.g., AoD and / or ZoD) and corresponding uncertainty ranges may be signaled to the UE by a location server, a base station, or any combination thereof.
[0176] Additionally or in the alternative, one or more AoAs and / or ZoAs for UL-PRS (e.g., SRS) sent by the UE to be measured by the base station during a positioning session may be provided to a receiving entity such as a base station. In an aspect, a single expected AoA value and / or ZoA value and a corresponding uncertainty range for each AoA value and / or ZoA value may be provided to the base station for each UE. Additionally or in the alternative, the base station may receive multiple expected AoA values and / or ZoA values and a corresponding uncertainty range for each of the multiple expected AoA values and / or ZoA values for each UE. In an aspect, the base station may receive the expected angle measurement value and the corresponding uncertainty value range from the location server. Additionally or in the alternative, the base station may estimate the expected angle measurement value and the corresponding uncertainty value range by itself based on a previous UL-PRS (e.g., SRS) transmission of the UE that has been measured by the base station during a previous positioning session.
[0177] In one aspect, the receiving entity does not receive the expected angle measurement and the corresponding uncertainty. For example, if only time domain consistency is used for PRS aggressor detection, the expected angle measurement and the corresponding uncertainty do not need to be sent to the receiving entity.
[0178] According to aspects of the present disclosure, a positioning session using expected angular measurements and / or time domain measurements and corresponding uncertainty values can be protected by hashing such values to reduce the risk that a PRS attacker can intercept and use such values in a PRS attack. To this end, an entity sending such estimates and / or uncertainty values may perform a hash function on these values before sending them to one or more receiving entities. The receiving entity may then perform the same hash function on the actual measurements made by the receiving entity during the positioning session. The receiving entity may compare the hash values of the expected measurements, the expected uncertainty, and the actual measurements to determine whether the actual measurements are consistent with the expected measurements. In one aspect, whether the actual measurements are consistent with the expected measurements may be determined by determining whether the hash value of the expected measurement and the hash value of the actual measurement are within the range of the expected measurement uncertainty as reflected in the hash value of the expected measurement uncertainty.
[0179] A hash function is a mathematical function that converts a numerical input value into another compressed numerical value. The input to a hash function can be of arbitrary length, but the output is of fixed length. In order to be an effective cryptographic tool, it is desirable that a hash function possess certain properties. For example, a hash function should have a certain degree of pre-imageability, in that it should be computationally difficult to reverse a hash function. In other words, if a hash function h is applied to an input value x and produces a hash value z, then finding the input value x from the hash value z should be a difficult process. This property prevents an attacker who only has the hash value z from determining the input value x.
[0180] Another desirable feature of a hash function is that it possesses a secondary anti-imageability property, in that given an input x and its hash z, it should be difficult to find a different input that produces the same hash. In other words, if a hash function h for input x produces a hash value h(x), then it should be difficult to find any other input value y such that h(y)=h(x). This property of a hash function protects against an attacker who has an input value and its hash and wants to replace the original input value with a different value as a legitimate value.
[0181] Another desirable feature of a hash function is that it possesses a collision-resistant property. This property means that it should be difficult to find two different inputs of any length that produce the same hash. This property is also known as a collision-free hash function. In other words, for a hash function h, it is difficult to find any two different inputs x and y such that h(x)=h(y). Since a hash function is actually a compression function with a fixed hash length, it is generally impossible for a hash function to avoid all collisions. This collision-resistant property of a hash function only means that such collisions should not occur frequently. This property makes it difficult for an attacker to find two input values with the same hash.
[0182] The aforementioned desirable properties of hash functions can be used to protect expected measurement / uncertainty values from being used by a PRS attacker. Using hash values of expected measurement / uncertainty values helps a receiving entity assess the authenticity of such hash values, since a PRS attacker cannot alter such hash values in a way that the alteration is not detected, and the expected / uncertainty values cannot be derived, either individually or collectively, from the hash values sent to the receiving entity.
[0183] To further protect the transmission of the expected quantities, a hash value for each of these quantities and / or a single hash value for all quantities after placing all quantities into a single stream may be signaled to the receiving entity in one or more security layers (e.g., layer 3 data such as RRC data). Thus, even if the security of the RRC transmission is compromised, the expected and corresponding uncertainty information associated with each PRS is not compromised because the hash value of the quantity remains protected by the hash function. Thus, if the hash value of the quantity received by the receiving entity for the expected measurement and / or corresponding uncertainty range does not make sense (e.g., the hash value does not fall within the range of values that the receiving entity expects to receive in the context of the positioning session), the receiving entity may discard the PRS of an unauthorized source (e.g., a PRS attacker).
[0184] To maintain the integrity and authentication of positioning measurements, the entity sending the hashed expectation value / uncertainty may signal a hash value including, for example, the following: 1) one or more expected PRS reference signal received power (PRS-RSRP) measurement values; 2) one or more PRS-RSRP uncertainty values associated with one or more expected PRS-RSRP measurement values; 3) one or more expected RSTD measurement values; 4) one or more RSTD uncertainty values associated with one or more expected RSTD measurement values; 5) one or more expected AoA measurement values; 6) one or more AoA uncertainty values associated with one or more AoA measurement values; 7) one or more expected AoD measurement values; 8) one or more AoD uncertainty values associated with one or more AoD measurement values; 9) one or more expected ZoA measurement values; 10) one or more ZoA uncertainty values associated with one or more ZoA measurement values; 11) one or more expected ZoD measurement values; 12) one or more ZoD uncertainty values associated with one or more ZoD measurement values; or 13) any combination thereof.
[0185] According to certain aspects of the present disclosure, a receiving entity (such as a UE) receives a configuration of one or more of the resources of one or more TRPs to be measured during a positioning session. The UE further receives a first set of one or more hash values, the first set of one or more hash values being based on one or more hash operations applied to one or more expected measurement values and / or corresponding expected uncertainty values such as the expected measurement values and expected uncertainty values described herein. The hash values of the expected measurement values and / or corresponding expected uncertainty values are generated, for example, by a location server and / or a base station (e.g., a gNB). In one aspect, the expected measurement values and the expected uncertainty values are determined at the location server and / or the base station. In one aspect, the expected measurement values and / or the expected uncertainty values are generated for each time measurement and / or angle measurement of a PRS resource to be measured by the UE and used for PRS attacker detection. Before sending to the UE, the location server and / or the base station applies one or more hash functions to the expected measurement and / or expected uncertainty values.
[0186] In one aspect, one or more hash functions may be applied individually to each expected measurement value and / or expected uncertainty value for each PRS resource to be measured by the UE and used for PRS attacker detection. In one aspect, the same hash function may be applied to each such individual expected measurement value and / or expected uncertainty value. In one aspect, different hash functions may be applied to different ones of the individual expected measurement values and / or uncertainty values. The hash functions and the manner in which they are applied to the expected measurement values and / or uncertainty values are agreed upon between the UE and the location server and / or base station.
[0187] In one aspect, a hash function may be applied to multiple expected measurement values and / or expected uncertainty values. For example, one or more strings of multiple expected measurement values and / or corresponding uncertainty values may be generated at a location server and / or a base station based on a string generation method agreed upon by the UE and the location server and / or the base station. Then, the location server and / or the base station applies one or more hash functions to the string to generate a hash value, wherein the one or more hash functions are agreed upon by the UE and the location server and / or the base station. In one aspect, the same hash function may be applied to each string value in a plurality of string values. In one aspect, different hash functions may be applied to different string values in a plurality of string values. Similarly, the hash functions and the manner in which they are applied to a plurality of strings are agreed upon by the UE and the location server and / or the base station.
[0188] During the positioning session, the UE measures the PRS resources indicated in the received transmission (e.g., assistance data) to generate actual measurement values of the PRS resources. Based on whether the measurement of the PRS resources is to be used for PRS attacker detection, the UE uses the actual measurement values to generate one or more corresponding hash values in a manner agreed upon between the UE and the location server and / or the base station. Therefore, the UE now has hash values (e.g., a second set of one or more hash values) corresponding to the one or more actual measurement values of the PRS resources that can be used for PRS attacker detection.
[0189] Once the UE has generated the second set of hash values, the UE compares the second set of one or more hash values with the first set of one or more hash values to detect a PRS attack. In one aspect, the comparison is used to determine whether the one or more actual measurement values are within an acceptable limit for one or more expected measurement values. In one aspect, the comparison includes comparing the second set of one or more hash values with the first set of one or more hash values to determine whether at least one of the one or more actual measurement values is outside of an acceptable limit for at least one of the one or more expected measurement values.
[0190] If detected, the UE may report error information related to the actual measurement value, for which the corresponding hash value falls outside the acceptable limits, to the location server and / or the base station. The error information may indicate which actual measurements determined by the UE fall outside the acceptable limits. In one aspect, the error information may include a bitmap indicating which parameters (e.g., RSRP, RSTD, AoD, ZoD, etc.) of the actual PRS resource measurements fall outside the acceptable limits. In one aspect, individual bits of the bitmap may correspond to the corresponding parameters (e.g., bit 3 corresponds to RSRP, bit 2 corresponds to RSTD, bit 1 corresponds to AoD, and bit 0 corresponds to ZoD). Using this bit correspondence as an example, bitmap 1010 indicates that the measured RSRP and AoD values are outside the acceptable limits, while RSTD and ZoD are within the acceptable limits. Based on the teachings of the present disclosure, it will be appreciated that other bit mappings to various parameters may be used, and the foregoing constitutes one such example.
[0191] Additionally or in the alternative, the error information may indicate the extent to which the actual measurement is outside of acceptable limits. In one aspect, the extent may be expressed as a difference between a hash value of an expected measurement value and a hash value of an actual measurement value. Additionally or in the alternative, the extent may be expressed according to a calculation agreed upon by the UE and the location server and / or base station.
[0192] According to certain aspects of the present disclosure, the determination of an acceptable restricted range for comparison of a hash value for an expected measurement value with a hash value for an actual measurement value may be based on an expected uncertainty value associated with the expected measurement value. According to certain aspects, the expected measurement value of the PRS resource to be measured by the UE may be hashed with the corresponding expected uncertainty value to generate a hash value for comparison. According to certain aspects, multiple expected measurement values associated with the PRS resource to be measured by the UE may be hashed and transmitted to the UE by the location server and / or the base station as a basis for comparison. According to certain aspects, multiple expected uncertainty values associated with the PRS resource to be measured by the UE may be hashed and transmitted to the UE by the location server and / or the base station for use in comparison. Additionally or in an alternative, the acceptable restricted range may be based on another range agreed upon by the UE and the location server and / or the base station. In such instances, the agreed range may be expressed as a fixed value of the acceptable restricted range or a hash value corresponding to the acceptable restricted range.
[0193] According to certain aspects of the present disclosure, the UE and the location server and / or the base station may agree on a hash bin configuration for comparison. In one aspect, the hash bin configuration may be based on hash values that fall within an acceptable limit for hash values generated using expected measurement values and / or expected uncertainty values. Additionally or in an alternative, the hash bin configuration may include hash bins corresponding to hash values outside the acceptable limit.
[0194] According to certain aspects of the present disclosure, a single hash bin configuration may be associated with each given expected measurement value to be measured by the UE. Additionally or in the alternative, where the hash value corresponds to a set of multiple expected measurement values, a single hash bin configuration may be associated with each set.
[0195] In certain aspects of the present disclosure, each hash bin in a hash bin configuration may correspond to a range of hash values. This hash bin configuration may be implemented when the hash function used to generate the hash value is a locality-sensitive hash function. Locality-sensitive hashing is an algorithmic technique that hashes similar input entries into the same "bucket" (e.g., a bin corresponding to a range of hash values) with a high probability. Since similar hash values end up in the same bucket, this technique can be used for data clustering and nearest neighbor searches to determine whether the hash value corresponding to one or more actual measurement values is within an acceptable limit for the hash value corresponding to one or more expected measurement values. In such instances, depending on its specific implementation, the number of hash collisions associated with a locality-sensitive hash function may be greater than the number of hash collisions generated by other types of hash functions. In certain aspects, regardless of whether the hash function used is locally sensitive, the ability to detect PRS attacks can be increased by increasing the number of hash bins used in the configuration.
[0196] Since there may be errors in the measurement without a PRS attack, the UE may compare the hash value of the current hash bin, the current hash bin + Y, the current hash bin - X, or a defined set of hash bins with the received hash value of each parameter, where X and Y are RRC / MAC-CE configured and correspond to the number of bins adjacent to the current hash bin. If there is a mismatch in one or more quantities (e.g., according to the configuration between the UE and the location server and / or base station), the UE reports the occurrence. In one aspect, the occurrence may be indicated in a flag or other information in a report dedicated to PRS attack detection. Additionally or in an alternative, the occurrence may be indicated by a flag or other information in a report, where the other information is reported by the UE, where the other information is provided in a report not dedicated to PRS attack detection.
[0197] According to certain aspects of the present disclosure, the UE may attempt to assign a hash value corresponding to an actual measurement value to a hash bin of a hash bin configuration. As an example, the UE may perform an assignment operation to assign one or more hash values in the second set of hash values to one or more hash bins of an agreed hash bin configuration. In various aspects, the UE may report to the location server and / or the base station information related to: one or more hash values in the second set of hash values that cannot be assigned to a hash bin allowed in the set of hash bins, and / or one or more hash values that fall within a hash bin corresponding to a hash value indicating a PRS attack.
[0198] As mentioned, hash values can be generated using separate expected measurements. In such instances, a first set of one or more hash values may include a hash value of a fixed size L associated with each of the one or more expected measurements. Thus, a second set of one or more hash values may include a hash value of a fixed size L associated with each of the one or more actual measurements. In some aspects, the value of L may be selected based on the expected accuracy of the PRS attack determination. In some aspects, the value of L may be selected based on a tolerable hash collision factor. The value of L may be RRC / MAC-CE configured or based on a specification agreed upon between the UE and the location server and / or base station. Other factors for determining the value of L may also be used.
[0199] Additionally or in an alternative, the first set of one or more hash values includes hash values of size Z that are commonly associated with multiple expected measurement values in the one or more expected measurement values. In addition, the second set of one or more hash values may include hash values of size Z that are commonly associated with multiple actual measurement values in the one or more actual measurement values. In some aspects, the value of Z may be configured via RRC / MAC-CE. Additionally or in an alternative, the value of Z may be based on a specification agreed upon between the UE and the location server and / or the base station.
[0200] According to certain aspects of the present disclosure, the value of Z may be based on a modulation and coding scheme (MCS) similar to the transport block size (TBS) calculation set forth in the publicly available 3GPP TS 138.214. Determining the value of Z in this manner facilitates the generation of dynamic reports. In one aspect, the value of Z may be determined as:
[0201] Z=N info =#layers*spectral eff *#REs
[0202] in
[0203] #layers controls the number of information layers.
[0204] spectral eff is the spectral efficiency, and
[0205] #RE is the number of resource elements.
[0206] In some aspects, the value of Z determined based on the calculation can be modified based on the desired accuracy determined by the PRS attack. In some aspects, the value of Z can be modified based on a tolerable hash collision factor. Other factors for modifying the value of Z can also be used.
[0207] The hash values described herein may be signaled to a receiving entity in various ways. According to certain aspects of the present disclosure, the hash values are signaled via LPP. In a Uu link, the hash values may be signaled in an RRC message in a PDSCH data channel. In sidelink communications, the hash values may be signaled in an RRC message in a physical sidelink shared channel (PSSCH) data channel. In certain aspects, some hash values may be communicated via RRC / PDSCH, while other hash values may be communicated via RRC / P SSCH. Communicating hash values via RRC information is beneficial because the hash values are further encrypted as part of the encryption of the RRC data, thereby providing a further level of security to the predicted measurement values and / or corresponding uncertainty values.
[0208] According to certain aspects of the present disclosure, the hash value is signaled via RRC information.In certain aspects, the RRC information is carried in PDSCH, PSSCH, or a combination thereof.
[0209] In some instances, encryption / decryption of hash expected values / uncertainties and / or hash actual measurements in RRC transmissions may be slow, particularly for mobile UEs. To address such time constraints, hash expected values / uncertainties and / or hash actual measurements may be sent in PHY layer signaling to facilitate more efficient communication of such hash values. In some aspects, a PHY layer carrier dedicated to sending hash expected values / uncertainties and / or hash actual measurements may be employed. In some aspects, a UE and a base station (e.g., a gNB) may exchange hash expected values / uncertainties and / or hash actual measurements using such PHY layer signaling. In some aspects, the base station communicates with a location server via NRPPa to receive and / or forward hash expected values / uncertainties and / or hash actual measurements.
[0210] According to certain aspects of the present disclosure, the hash value may be signaled without additional encryption. In certain aspects, the hash value may be signaled via one or more MAC-CEs carried in a PDCCH, one or more MAC-CEs carried in a physical sidelink control channel (PSCCH), sidelink control information (e.g., SCI-2 data) carried in the PSCCH, or a combination thereof.
[0211] In some aspects, the secure use of hash measurements as disclosed herein is applicable to the sending and receiving of positioning information between various network entities. In some aspects, the communication can be from a base station (e.g., a gNB) to a UE, from a UE to another UE, from a UE to a base station (e.g., a gNB), etc.
[0212] In some aspects, if a non-secure channel is used to communicate the hash value, a private key may be used at the device that sends the hash value to encrypt the hash value. A public key may be used to decrypt the encrypted hash value at the receiver side. The public key and private key are generated at the device that sends the hash value, and the public key is shared with the device that receives the encrypted hash value. Therefore, the private key is used to encrypt at the sending device, and the public key is used to decrypt at the receiving device. Before receiving the encrypted hash value, an attacker cannot determine or generate the encrypted hash value because the private key is never shared. If a conventional method of public / private key use is adopted, the public key will be used to encrypt the hash value. However, since the public key will be known to all devices in the network (unless it is sent to a specific trusted device in unicast or multicast), an attacker can forge the hash value.
[0213] In certain aspects, a known payload of bits may be added to the hash value payload prior to encryption with a private key (e.g., a bit sequence of "1100" may be added to the hash value payload). A device receiving the hash value may use the public key to decrypt the transmission and determine whether the bits of the known payload (e.g., the bit sequence of "1100") are present. The known bit sequence added to the hash value payload of the hash value may be configured (e.g., by a base station) or defined in a specification (e.g., a 3GPP specification). The length of the sequence may be fixed or variable.
[0214] In certain aspects, the foregoing public key / private key operations may be extended to hash values sent in a secure channel.Additional layers of encryption may be used to enhance the security of hash values sent over a secure channel.
[0215] The encryption / decryption of the hash value in the aforementioned manner is different from the conventional encryption / decryption process. Among other differences, according to aspects of the present disclosure, a public key may be used for encryption and a private key may be used for decryption. In addition, both the private key and the public key are generated by the sending device, while in conventional public / private key scenarios the receiving side generates the public key and the private key.
[0216] Fig.11 An example method 1100 of wireless communication performed by a network node (e.g., a UE, a gNB, a base station, etc.) according to various aspects of the present disclosure is illustrated. At operation 1102, the network node receives a first set of one or more hash values, wherein the first set of one or more hash values is based on one or more hash operations of one or more expected measurement values of one or more positioning reference signal (PRS) resources applied to one or more transmit receive points (TRPs). In one aspect, operation 1102 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as means for performing the operation. In one aspect, operation 1102 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or positioning component 388, any or all of which may be considered as means for performing the operation.
[0217] At operation 1104, the network node measures one or more PRS resources to obtain one or more actual measurement values. In one aspect, operation 1104 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as means for performing the operation. In one aspect, operation 1104 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or positioning component 388, any or all of which may be considered as means for performing the operation.
[0218] At operation 1106, the network node determines whether one or more actual measured values of one or more PRS resources are within acceptable limits for one or more expected measured values based on a comparison of a second set of one or more hash values with a first set of one or more hash values, wherein the second set of one or more hash values is based on applying one or more hash operations to the one or more actual measured values. In one aspect, operation 1106 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as means for performing the operation. In one aspect, operation 1106 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or positioning component 388, any or all of which may be considered as means for performing the operation.
[0219] It should be appreciated that a technical advantage of method 1100 is that a network node (e.g., UE, gNB, base station, etc.) uses a secure hash value corresponding to an expected measurement value to authenticate the actual PRS measurement made by the network node during a positioning session, while also facilitating identification of PRS measurements that may have been tampered with through a PRS attack. Using such a secure hash value for the measurement quantity helps prevent a PRS attacker from using the expected measurement value in a PRS attack, in which the PRS attacker attempts to generate an erroneous PRS transmission.
[0220] Fig.12An example method 1200 of wireless communication performed by a network node (e.g., a UE, a gNB, a base station, etc.) according to various aspects of the present disclosure is illustrated. At operation 1202, the network node receives a first set of one or more hash values from a location server, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values, wherein the one or more expected measurement values correspond to expected measurements of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs) measured by the network node during a positioning session. In one aspect, operation 1202 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as means for performing the operation. In one aspect, operation 1202 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or positioning component 388, any or all of which may be considered as means for performing the operation.
[0221] At operation 1204, the network node uses a first set of one or more hash values for PRS attack detection. According to certain aspects of the present disclosure, using the first set of one or more hash values for PRS attack detection includes: sending the first set of one or more hash values to a UE; and receiving an indication from the UE that one or more actual measurement values made by the UE are outside of an acceptable limit for at least one of the one or more expected measurement values. According to certain aspects of the present disclosure, using the first set of one or more hash values for PRS attack detection includes: receiving a second set of one or more hash values corresponding to one or more actual measurement values taken by the UE for one or more PRS resources; and determining whether the one or more actual measurement values of the one or more PRS resources are within an acceptable limit for the one or more expected measurement values based on a comparison of the second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying one or more hash operations to the one or more actual measurement values. In one aspect, operation 1204 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as means for performing the operation. In an aspect, operation 1204 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or positioning component 388, any or all of which may be considered means for performing the operation.
[0222] It should be appreciated that a technical advantage of method 1200 is that a network node uses a secure hash value corresponding to an expected measurement value to detect a PRS measurement that may have been tampered with by a PRS attack. Using such a secure hash value for the measurement quantity helps prevent a PRS attacker from using the expected measurement value in a PRS attack in which the PRS attacker attempts to generate an erroneous PRS transmission.
[0223] It will be appreciated that an additional technical advantage of method 1200 is that a network node uses expected measurement values to authenticate actual PRS measurements made by the network node during a positioning session, while also facilitating identification of PRS measurements that may have been tampered with through a PRS attack.
[0224] In the above specific embodiments, it can be seen that different features are grouped together in each example. This disclosure should not be understood as an intention that the example clauses have more features than the features explicitly mentioned in each clause. On the contrary, various aspects of the present disclosure may include less than all the features of the disclosed individual example clauses. Therefore, the following clauses should be considered to be incorporated into the description accordingly, where each clause itself can be used as a separate example. Although each subordinate clause can refer to a specific combination of one clause with other clauses in a clause, the aspects of the subordinate clause are not limited to specific combinations. It should be understood that other example clauses may also include a combination of the subject matter of the subordinate clause aspect with any other subordinate clause or independent clause or any feature with other subordinate clauses and independent clauses. The various aspects disclosed herein explicitly include these combinations, unless it is explicitly expressed or can be easily inferred that a specific combination is not intended to be used (for example, contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). In addition, it is also expected that various aspects of the clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause.
[0225] Specific implementation examples are described in the following numbered clauses:
[0226] Clause 1. A method of wireless communication performed by a network node, comprising: receiving a first set of one or more hash values, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs); measuring the one or more PRS resources to obtain one or more actual measurement values; and determining whether the one or more actual measurement values of the one or more PRS resources are within acceptable limits of the one or more expected measurement values based on a comparison of a second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying the one or more hash operations to the one or more actual measurement values.
[0227] Clause 2. The method of clause 1 further comprising: receiving a configuration of the one or more PRS resources of the one or more TRPs to be measured during a positioning session.
[0228] Clause 3. The method according to any one of clauses 1 to 2 further includes: determining that at least one of the one or more actual measurement values is outside the acceptable limit of at least one of the one or more expected measurement values based on the comparison of the second set of one or more hash values with the first set of one or more hash values; and reporting error information related to the at least one of the one or more actual measurement values.
[0229] Clause 4. A method according to clause 3, wherein: the error information comprises a bitmap, the bitmap comprising flags indicating which parameters of the at least one actual measurement value are outside the acceptable limits.
[0230] Clause 5. A method according to any one of clauses 3 to 4, wherein: the error information comprises an indication of the extent to which the at least one actual measurement is outside the acceptable limits.
[0231] Clause 6. A method according to any one of clauses 1 to 5, wherein the first set of one or more hash values is based on applying the one or more hash operations to: one or more expected PRS reference signal received power (PRS-RSRP) measurements; one or more PRS-RSRP uncertainty values associated with the one or more expected PRS-RSRP measurements; one or more expected reference signal time difference (RSTD) measurements; one or more RSTD uncertainty values associated with the one or more expected RSTD measurements; one or more expected angle of arrival (AoA) measurements; one or more AoA uncertainty values associated with the one or more AoA measurements; one or more expected angle of departure (AoD) measurements; one or more AoD uncertainty values associated with the one or more AoD measurements; one or more expected zenith angle of arrival (ZoA) measurements; one or more ZoA expected uncertainty values associated with the one or more ZoA measurements; one or more expected zenith angle of departure (ZoD) measurements; one or more expected ZoD uncertainty values associated with the one or more ZoD measurements; or any combination thereof.
[0232] Clause 7. A method according to any one of clauses 1 to 6, wherein the second set of one or more hash values is based on applying the one or more hash operations to: one or more actual reference signal received power (RSRP) measurements; one or more actual relative signal time difference (RSTD) measurements; one or more actual angle of arrival (AoA) measurements; one or more actual zenith angle of arrival (ZoA) measurements; one or more actual zenith angle of departure (ZoD) measurements; or any combination thereof.
[0233] Clause 8. A method according to any one of clauses 1 to 7, wherein: the first set of one or more hash values includes a hash value of size L associated with each of the one or more expected measurement values, respectively; and the second set of one or more hash values includes a hash value of size L associated with each of the one or more actual measurement values, respectively.
[0234] Clause 9. The method according to Clause 8 also includes: receiving a first final hash value having a size L, wherein the first final hash value is based on all hash values in the first set of one or more hash values; and receiving a second final hash value having a size L, wherein the second final hash value is based on all hash values in the second set of one or more hash values.
[0235] Clause 10. A method according to any one of clauses 1 to 7, wherein: the first set of one or more hash values includes hash values of size Z that are commonly associated with multiple expected measurement values among the one or more expected measurement values; and the second set of one or more hash values includes hash values of size Z that are commonly associated with multiple actual measurement values among the one or more actual measurement values; and Z is calculated based on the transmission block size, which is determined as Z = #layers*spectraleff*#REs, where #layers is the number of control information layers, spectraleff is the spectral efficiency, and #REs is the number of resource elements.
[0236] Clause 11. The method of any one of clauses 1 to 10, wherein: the first set of one or more hash values is received using the Long Term Evolution Positioning Protocol (LPP).
[0237] Clause 12. A method according to any one of clauses 1 to 10, wherein: the network node is a base station; the one or more PRS resources are uplink PRS (UL-PRS) resources; and the second set of one or more hash values is received from a user equipment (UE).
[0238] Clause 13. A method according to any one of clauses 1 to 10, wherein: the network node is a user equipment (UE); the one or more PRS resources are downlink PRS (DL-PRS) resources; and the first set of one or more hash values is received from a base station.
[0239] Clause 14. A method according to any one of clauses 1 to 10, wherein: the network node is a first user equipment (UE); the first set of one or more hash values is received from a second UE; and the one or more PRS resources are sidelink PRS (SL-PRS) resources.
[0240] Clause 15. A method as described in any of clauses 1 to 10, wherein: the network node is a user equipment (UE); and the first set of one or more hash values is received in a radio resource control (RRC) message.
[0241] Clause 16. The method of clause 15, wherein: the RRC information is carried in a physical downlink shared channel (PDSCH), a physical sidelink shared channel (PSSCH), or a combination thereof.
[0242] Clause 17. A method according to any one of clauses 1 to 10, wherein: the first set of one or more hash values is received in one or more medium access control elements (MAC-CE) carried in a physical download control channel (PDCCH).
[0243] Clause 18. A method according to any one of clauses 1 to 10, wherein the first set of one or more hash values is received in one or more medium access control elements (MAC-CE) carried in a physical sidelink control channel (PSCCH), sidelink control information carried in the PSCCH, or a combination thereof.
[0244] Clause 19. A method according to any one of clauses 1 to 18, wherein the comparison of the second set of hash values with the first set of hash values includes: performing an assignment operation to assign one or more hash values in the second set of hash values to a set of hash bins, wherein the set of hash bins is based on the first set of hash values; and reporting information related to one or more hash values in the second set of hash values that cannot be assigned to allowed hash bins in the set of hash bins.
[0245] Clause 20. A method of wireless communication performed by a network node, comprising: receiving a first set of one or more hash values from a location server, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values, wherein the one or more expected measurement values correspond to expected measurements of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs) measured by a user equipment (UE) during a positioning session; and using the first set of one or more hash values for PRS attack detection.
[0246] Clause 21. A method according to clause 20, wherein using the first set of one or more hash values for PRS attack detection includes: sending the first set of one or more hash values to the UE; and receiving an indication from the UE that one or more actual measurement values obtained by the UE are outside of acceptable limits of one or more expected measurement values.
[0247] Clause 22. A method according to clause 21, wherein: the indication from the UE comprises a bitmap, the bitmap comprising flags indicating which parameters of the one or more actual measured values are outside the acceptable limits.
[0248] Clause 23. A method as described in any of clauses 21 to 22, wherein: the indication from the UE includes an indication of the extent to which the one or more actual measurement values are outside the acceptable limits.
[0249] Clause 24. A method according to any one of clauses 21 to 23, further comprising: reporting to the location server error information related to the one or more actual measurement values obtained by the UE that are outside the acceptable limits of the one or more expected measurement values.
[0250] Clause 25. A method according to any one of clauses 20 to 24, wherein using the first set of one or more hash values for PRS attack detection includes: receiving a second set of one or more hash values corresponding to one or more actual measurement values taken by the UE for the one or more PRS resources; and determining whether the one or more actual measurement values of the one or more PRS resources are within acceptable limits of the one or more expected measurement values based on a comparison of the second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying the one or more hash operations to the one or more actual measurement values.
[0251] Clause 26. A method according to clause 25, wherein the second set of one or more hash values is based on applying the one or more hash operations to: one or more actual reference signal received power (RSRP) measurements; one or more expected relative signal time difference (RSTD) measurements; one or more expected angle of arrival (AoA) measurements; or a combination thereof.
[0252] Clause 27. A method according to any one of clauses 20 to 26, wherein the first set of one or more hash values is based on applying the one or more hash operations to: one or more expected PRS reference signal received power (PRS-RSRP) measurement values; one or more expected PRS-RSRP uncertainty values associated with the one or more expected PRS-RSRP measurement values; one or more expected reference signal time difference (RSTD) measurement values; one or more expected RSTD uncertainty values associated with the one or more RSTD measurement values; one or more expected angle of arrival (AoA) measurement values; one or more expected AoA uncertainty values associated with the one or more AoA measurement values; one or more expected zenith angle of arrival (ZoA) measurement values; one or more expected ZoA uncertainty values associated with the one or more ZoA measurement values; one or more expected zenith angle of departure (ZoD) measurement values; one or more expected ZoD uncertainty values associated with the one or more ZoD measurement values; or any combination thereof.
[0253] Clause 28. A network node 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 being configured to: receive a first set of one or more hash values via the at least one transceiver, wherein the first set of one or more hash values is based on one or more hash operations of one or more expected measurement values of one or more positioning reference signal (PRS) resources applied to one or more transmit receive points (TRPs); measure the one or more PRS resources to obtain one or more actual measurement values; and determine whether the one or more actual measurement values of the one or more PRS resources are within acceptable limits of the one or more expected measurement values based on a comparison of a second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying the one or more hash operations to the one or more actual measurement values.
[0254] Clause 29. The network node of clause 28, wherein the at least one processor is further configured to: receive, via the at least one transceiver, a configuration of one or more PRS resources of the one or more TRPs to be measured during a positioning session.
[0255] Clause 30. A network node according to any one of clauses 28 to 29, wherein the at least one processor is further configured to: determine, based on the comparison of the second set of one or more hash values with the first set of one or more hash values, that at least one of the one or more actual measurement values is outside the acceptable limit of at least one of the one or more expected measurement values; and report error information related to the at least one of the one or more actual measurement values via the at least one transceiver.
[0256] Clause 31. A network node according to clause 30, wherein: the error information comprises a bitmap, the bitmap comprising flags indicating which parameters of the at least one actual measurement value are outside the acceptable limits.
[0257] Clause 32. A network node as described in any of clauses 30 to 31, wherein: the error information comprises an indication of the extent to which the at least one actual measurement is outside the acceptable limits.
[0258] Clause 33. A network node according to any one of clauses 28 to 32, wherein the first set of one or more hash values is based on applying the one or more hash operations to: one or more expected PRS reference signal received power (PRS-RSRP) measurements; one or more PRS-RSRP uncertainty values associated with the one or more expected PRS-RSRP measurements; one or more expected reference signal time difference (RSTD) measurements; one or more RSTD uncertainty values associated with the one or more expected RSTD measurements; one or more expected angle of arrival (AoA) measurements; one or more AoA uncertainty values associated with the one or more AoA measurements; one or more expected angle of departure (AoD) measurements; one or more AoD uncertainty values associated with the one or more AoD measurements; one or more expected zenith angle of arrival (ZoA) measurements; one or more ZoA expected uncertainty values associated with the one or more ZoA measurements; one or more expected zenith angle of departure (ZoD) measurements; one or more expected ZoD uncertainty values associated with the one or more ZoD measurements; or any combination thereof.
[0259] Clause 34. A network node according to any one of clauses 28 to 33, wherein the second set of one or more hash values is based on applying the one or more hash operations to: one or more actual reference signal received power (RSRP) measurements; one or more actual relative signal time difference (RSTD) measurements; one or more actual angle of arrival (AoA) measurements; one or more actual zenith angle of arrival (ZoA) measurements; one or more actual zenith angle of departure (ZoD) measurements; or any combination thereof.
[0260] Clause 35. A network node according to any one of clauses 28 to 34, wherein: the first set of one or more hash values includes a hash value of size L associated with each of the one or more expected measurement values; and the second set of one or more hash values includes a hash value of size L associated with each of the one or more actual measurement values.
[0261] Clause 36. A network node according to clause 35, wherein the at least one processor is further configured to: receive a first final hash value having a size L via the at least one transceiver, wherein the first final hash value is based on all hash values in the first set of one or more hash values; and receive a second final hash value having a size L via the at least one transceiver, wherein the second final hash value is based on all hash values in the second set of one or more hash values.
[0262] Clause 37. A network node according to any one of clauses 28 to 34, wherein: the first set of one or more hash values includes hash values of size Z that are commonly associated with multiple expected measurement values among the one or more expected measurement values; and the second set of one or more hash values includes hash values of size Z that are commonly associated with multiple actual measurement values among the one or more actual measurement values; and Z is calculated based on the transmission block size, which is determined as Z = #layers*spectraleff*#REs, where #layers is the number of control information layers, spectraleff is the spectral efficiency, and #REs is the number of resource elements.
[0263] Clause 38. A network node as described in any of clauses 28 to 37, wherein: the first set of one or more hash values is received using the Long Term Evolution Positioning Protocol (LPP).
[0264] Clause 39. A network node according to any one of clauses 28 to 36, wherein: the network node is a base station; the one or more PRS resources are uplink PRS (UL-PRS) resources; and the second set of one or more hash values is received from a user equipment (UE).
[0265] Clause 40. A network node according to any one of clauses 28 to 36, wherein: the network node is a user equipment (UE); the one or more PRS resources are downlink PRS (DL-PRS) resources; and the first set of one or more hash values is received from a base station.
[0266] Clause 41. A network node according to any one of clauses 28 to 38, wherein: the network node is a first user equipment (UE); the first set of one or more hash values is received from a second UE; and the one or more PRS resources are sidelink PRS (SL-PRS) resources.
[0267] Clause 42. A network node as described in any of clauses 28 to 36, wherein: the network node is a user equipment (UE); and the first set of one or more hash values is received in a radio resource control (RRC) message.
[0268] Clause 43. A network node according to clause 42, wherein: the RRC information is carried in a physical downlink shared channel (PDSCH), a physical sidelink shared channel (PSSCH), or a combination thereof.
[0269] Clause 44. A network node as described in any of clauses 28 to 36, wherein: the first set of one or more hash values is received in one or more Medium Access Control Elements (MAC-CEs) carried in a Physical Download Control Channel (PDCCH).
[0270] Clause 45. A network node according to any one of clauses 28 to 46, wherein the first set of one or more hash values is received in one or more medium access control elements (MAC-CE) carried in a physical sidelink control channel (PSCCH), sidelink control information carried in the PSCCH, or a combination thereof.
[0271] Clause 46. A network node according to any one of clauses 28 to 45, wherein the at least one processor is configured to determine whether the one or more actual measured values of the one or more PRS resources are within acceptable limits of the one or more expected measured values, including the at least one processor being configured to: perform an assignment operation to assign one or more hash values from the second set of hash values to a set of hash bins, wherein the set of hash bins is based on the first set of hash values; and report, via the at least one transceiver, information related to one or more hash values from the second set of hash values that cannot be assigned to allowed hash bins in the set of hash bins.
[0272] Clause 47. A network node 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 being configured to: receive a first set of one or more hash values from a location server via the at least one transceiver, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values, wherein the one or more expected measurement values correspond to expected measurements of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs) measured by a user equipment (UE) during a positioning session; and use the first set of one or more hash values for PRS attack detection.
[0273] Clause 48. A network node according to clause 47, wherein the at least one processor is configured to use the first set of one or more hash values for PRS attack detection, including the at least one processor being configured to: send the first set of one or more hash values to the UE via the at least one transceiver; and receive an indication from the UE via the at least one transceiver that one or more actual measurement values obtained by the UE are outside of acceptable limits of one or more expected measurement values.
[0274] Clause 49. A network node according to clause 48, wherein: the indication from the UE comprises a bitmap, the bitmap comprising flags indicating which parameters of the one or more actual measured values are outside the acceptable limits.
[0275] Clause 50. A network node as described in any of clauses 48 to 49, wherein the indication from the UE comprises an indication of the extent to which the one or more actual measurement values are outside the acceptable limits.
[0276] Clause 51. A network node according to any one of clauses 48 to 50, wherein the at least one processor is further configured to: report to the location server via the at least one transceiver error information related to the one or more actual measurement values obtained by the UE that are outside the acceptable limits of the one or more expected measurement values.
[0277] Clause 52. A network node according to any one of clauses 47 to 51, wherein the at least one processor is configured to use the first set of one or more hash values for PRS attack detection, including the at least one processor being configured to: receive, via the at least one transceiver, a second set of one or more hash values corresponding to one or more actual measurement values taken by the UE for the one or more PRS resources; and determine whether the one or more actual measurement values of the one or more PRS resources are within acceptable limits of the one or more expected measurement values based on a comparison of the second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying the one or more hash operations to the one or more actual measurement values.
[0278] Clause 53. A network node according to clause 52, wherein the second set of one or more hash values is based on applying the one or more hash operations to: one or more actual reference signal received power (RSRP) measurements; one or more expected relative signal time difference (RSTD) measurements; one or more expected angle of arrival (AoA) measurements; or a combination thereof.
[0279] Clause 54. A network node according to any one of clauses 47 to 53, wherein the first set of one or more hash values is based on applying the one or more hash operations to: one or more expected PRS reference signal received power (PRS-RSRP) measurement values; one or more expected PRS-RSRP uncertainty values associated with the one or more expected PRS-RSRP measurement values; one or more expected reference signal time difference (RSTD) measurement values; one or more expected RSTD uncertainty values associated with the one or more RSTD measurement values; one or more expected angle of arrival (AoA) measurement values; one or more expected AoA uncertainty values associated with the one or more AoA measurement values; one or more expected zenith angle of arrival (ZoA) measurement values; one or more expected ZoA uncertainty values associated with the one or more ZoA measurement values; one or more expected zenith angle of departure (ZoD) measurement values; one or more expected ZoD uncertainty values associated with the one or more ZoD measurement values; or any combination thereof.
[0280] Clause 55. A network node comprising: a component for receiving a first set of one or more hash values, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs); a component for measuring the one or more PRS resources to obtain one or more actual measurement values; and a component for determining whether the one or more actual measurement values of the one or more PRS resources are within acceptable limits of the one or more expected measurement values based on a comparison of a second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying the one or more hash operations to the one or more actual measurement values.
[0281] Clause 56. The network node of clause 55, further comprising means for receiving a configuration of the one or more PRS resources of the one or more TRPs to be measured during a positioning session.
[0282] Clause 57. A network node according to any one of clauses 55 to 56, further comprising: a component for determining that at least one of the one or more actual measurement values is outside the acceptable limit of at least one of the one or more expected measurement values based on the comparison of the second set of one or more hash values with the first set of one or more hash values; and a component for reporting error information related to the at least one of the one or more actual measurement values.
[0283] Clause 58. A network node according to clause 57, wherein: the error information comprises a bitmap, the bitmap comprising flags indicating which parameters of the at least one actual measurement value are outside the acceptable limits.
[0284] Clause 59. A network node as described in any of clauses 57 to 58, wherein: the error information includes an indication of the extent to which the at least one actual measurement is outside the acceptable limits.
[0285] Clause 60. A network node according to any one of clauses 55 to 59, wherein the first set of one or more hash values is based on applying the one or more hash operations to: one or more expected PRS reference signal received power (PRS-RSRP) measurements; one or more PRS-RSRP uncertainty values associated with the one or more expected PRS-RSRP measurements; one or more expected reference signal time difference (RSTD) measurements; one or more RSTD uncertainty values associated with the one or more expected RSTD measurements; one or more expected angle of arrival (AoA) measurements; one or more AoA uncertainty values associated with the one or more AoA measurements; one or more expected angle of departure (AoD) measurements; one or more AoD uncertainty values associated with the one or more AoD measurements; one or more expected zenith angle of arrival (ZoA) measurements; one or more ZoA expected uncertainty values associated with the one or more ZoA measurements; one or more expected zenith angle of departure (ZoD) measurements; one or more expected ZoD uncertainty values associated with the one or more ZoD measurements; or any combination thereof.
[0286] Clause 61. A network node according to any one of clauses 55 to 60, wherein the second set of one or more hash values is based on applying the one or more hash operations to: one or more actual reference signal received power (RSRP) measurements; one or more actual relative signal time difference (RSTD) measurements; one or more actual angle of arrival (AoA) measurements; one or more actual zenith angle of arrival (ZoA) measurements; one or more actual zenith angle of departure (ZoD) measurements; or any combination thereof.
[0287] Clause 62. A network node according to any one of clauses 55 to 61, wherein: the first set of one or more hash values includes a hash value of size L associated with each of the one or more expected measurement values; and the second set of one or more hash values includes a hash value of size L associated with each of the one or more actual measurement values.
[0288] Clause 63. The network node according to clause 62 further includes: a component for receiving a first final hash value having a size L, wherein the first final hash value is based on all hash values in the first set of one or more hash values; and a component for receiving a second final hash value having a size L, wherein the second final hash value is based on all hash values in the second set of one or more hash values.
[0289] Clause 64. A network node according to any one of clauses 55 to 61, wherein: the first set of one or more hash values includes hash values of size Z that are commonly associated with multiple expected measurement values among the one or more expected measurement values; and the second set of one or more hash values includes hash values of size Z that are commonly associated with multiple actual measurement values among the one or more actual measurement values; and Z is calculated based on the transmission block size, which is determined as Z = #layers*spectraleff*#REs, where #layers is the number of control information layers, spectraleff is the spectral efficiency, and #REs is the number of resource elements.
[0290] Clause 65. The network node of any of clauses 55 to 64, wherein: the first set of one or more hash values is received using the Long Term Evolution Positioning Protocol (LPP).
[0291] Clause 66. A network node according to any one of clauses 55 to 65, wherein: the network node is a base station; the one or more PRS resources are uplink PRS (UL-PRS) resources; and the second set of one or more hash values is received from a user equipment (UE).
[0292] Clause 67. A network node according to any one of clauses 55 to 64, wherein: the network node is a user equipment (UE); the one or more PRS resources are downlink PRS (DL-PRS) resources; and the first set of one or more hash values is received from a base station.
[0293] Clause 68. A network node according to any one of clauses 55 to 64, wherein: the network node is a first user equipment (UE); the first set of one or more hash values is received from a second UE; and the one or more PRS resources are sidelink PRS (SL-PRS) resources.
[0294] Clause 69. A network node as described in any of clauses 55 to 64, wherein: the network node is a user equipment (UE); and the first set of one or more hash values is received in a radio resource control (RRC) message.
[0295] Clause 70. A network node according to clause 69, wherein: the RRC information is carried in a physical downlink shared channel (PDSCH), a physical sidelink shared channel (PSSCH), or a combination thereof.
[0296] Clause 71. A network node as described in any of clauses 55 to 64, wherein: the first set of one or more hash values is received in one or more Medium Access Control Elements (MAC-CE) carried in a Physical Download Control Channel (PDCCH).
[0297] Clause 72. A network node according to any one of clauses 55 to 64, wherein the first set of one or more hash values is received in one or more medium access control elements (MAC-CE) carried in a physical sidelink control channel (PSCCH), sidelink control information carried in the PSCCH, or a combination thereof.
[0298] Clause 73. A network node according to any one of clauses 55 to 72, wherein the component for determining whether the one or more actual measured values of the one or more PRS resources are within acceptable limits of the one or more expected measured values includes: a component for performing an assignment operation to assign one or more hash values from the second set of hash values to a set of hash bins, wherein the set of hash bins is based on the first set of hash values; and a component for reporting information related to one or more hash values from the second set of hash values that cannot be assigned to allowed hash bins in the set of hash bins.
[0299] Clause 74. A network node comprising: a component for receiving a first set of one or more hash values from a location server, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values, wherein the one or more expected measurement values correspond to expected measurements of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs) measured by a user equipment (UE) during a positioning session; and a component for using the first set of one or more hash values for PRS attack detection.
[0300] Clause 75. A network node according to clause 74, wherein the component for using the first set of one or more hash values for PRS attack detection includes: a component for sending the first set of one or more hash values to the UE; and a component for receiving an indication from the UE that one or more actual measurement values obtained by the UE are outside of acceptable limits of one or more expected measurement values.
[0301] Clause 76. A network node according to clause 75, wherein: the indication from the UE comprises a bitmap, the bitmap comprising flags indicating which parameters of the one or more actual measured values are outside the acceptable limits.
[0302] Clause 77. A network node as described in any of clauses 75 to 76, wherein: the indication from the UE includes an indication of the extent to which the one or more actual measurement values are outside the acceptable limits.
[0303] Clause 78. A network node according to any of clauses 75 to 77, further comprising: means for reporting to the location server error information relating to the one or more actual measurement values obtained by the UE being outside the acceptable limits of the one or more expected measurement values.
[0304] Clause 79. A network node according to any one of clauses 74 to 78, wherein the component for using the first set of one or more hash values for PRS attack detection includes: a component for receiving a second set of one or more hash values corresponding to one or more actual measurement values taken by the UE for the one or more PRS resources; and a component for determining whether the one or more actual measurement values of the one or more PRS resources are within acceptable limits of the one or more expected measurement values based on a comparison of the second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying the one or more hash operations to the one or more actual measurement values.
[0305] Clause 80. A network node according to clause 79, wherein the second set of one or more hash values is based on applying the one or more hash operations to: one or more actual reference signal received power (RSRP) measurements; one or more expected relative signal time difference (RSTD) measurements; one or more expected angle of arrival (AoA) measurements; or a combination thereof.
[0306] Clause 81. A network node according to any one of clauses 74 to 80, wherein the first set of one or more hash values is based on applying the one or more hash operations to: one or more expected PRS reference signal received power (PRS-RSRP) measurement values; one or more expected PRS-RSRP uncertainty values associated with the one or more expected PRS-RSRP measurement values; one or more expected reference signal time difference (RSTD) measurement values; one or more expected RSTD uncertainty values associated with the one or more RSTD measurement values; one or more expected angle of arrival (AoA) measurement values; one or more expected AoA uncertainty values associated with the one or more AoA measurement values; one or more expected zenith angle of arrival (ZoA) measurement values; one or more expected ZoA uncertainty values associated with the one or more ZoA measurement values; one or more expected zenith angle of departure (ZoD) measurement values; one or more expected ZoD uncertainty values associated with the one or more ZoD measurement values; or any combination thereof.
[0307] Clause 82. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network node, cause the network node to: receive a first set of one or more hash values, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs); measure the one or more PRS resources to obtain one or more actual measurement values; and determine whether the one or more actual measurement values of the one or more PRS resources are within acceptable limits of the one or more expected measurement values based on a comparison of a second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying the one or more hash operations to the one or more actual measurement values.
[0308] Clause 83. The non-transitory computer-readable medium of clause 82, further comprising: computer-executable instructions which, when executed by the network node, cause the network node to: receive a configuration of the one or more PRS resources of the one or more TRPs to be measured during a positioning session.
[0309] Clause 84. The non-transitory computer-readable medium described in any one of clauses 82 to 83 further includes: computer executable instructions, which, when executed by the network node, cause the network node to: determine, based on the comparison of the second set of one or more hash values with the first set of one or more hash values, that at least one of the one or more actual measurement values is outside the acceptable limit of at least one of the one or more expected measurement values; and report error information related to the at least one of the one or more actual measurement values.
[0310] Clause 85. A non-transitory computer-readable medium as described in Clause 84, wherein: the error information includes a bitmap, the bitmap including flags indicating which parameters of the at least one actual measurement value are outside of the acceptable limits.
[0311] Clause 86. The non-transitory computer-readable medium of any one of clauses 84 to 85, wherein: the error information comprises an indication of the extent to which the at least one actual measurement is outside of the acceptable limits.
[0312] Clause 87. A non-transitory computer-readable medium according to any one of clauses 82 to 86, wherein the first set of one or more hash values is based on applying the one or more hash operations to: one or more expected PRS reference signal received power (PRS-RSRP) measurements; one or more PRS-RSRP uncertainty values associated with the one or more expected PRS-RSRP measurements; one or more expected reference signal time difference (RSTD) measurements; one or more RSTD uncertainty values associated with the one or more expected RSTD measurements; one or more expected angle of arrival (AoA) measurements; one or more AoA uncertainty values associated with the one or more AoA measurements; one or more expected angle of departure (AoD) measurements; one or more AoD uncertainty values associated with the one or more AoD measurements; one or more expected zenith angle of arrival (ZoA) measurements; one or more ZoA expected uncertainty values associated with the one or more ZoA measurements; one or more expected zenith angle of departure (ZoD) measurements; one or more expected ZoD uncertainty values associated with the one or more ZoD measurements; or any combination thereof.
[0313] Clause 88. A non-transitory computer-readable medium as described in any of clauses 82 to 87, wherein the second set of one or more hash values is based on applying the one or more hash operations to: one or more actual reference signal received power (RSRP) measurements; one or more actual relative signal time difference (RSTD) measurements; one or more actual angle of arrival (AoA) measurements; one or more actual zenith angle of arrival (ZoA) measurements; one or more actual zenith angle of departure (ZoD) measurements; or any combination thereof.
[0314] Clause 89. A non-transitory computer-readable medium according to any one of clauses 82 to 88, wherein: the first set of one or more hash values includes a hash value of size L associated with each of the one or more expected measurement values; and the second set of one or more hash values includes a hash value of size L associated with each of the one or more actual measurement values.
[0315] Clause 90. The non-transitory computer-readable medium of clause 89 further comprises: computer executable instructions which, when executed by the network node, cause the network node to: receive a first final hash value having a size L, wherein the first final hash value is based on all hash values in the first set of one or more hash values; and receive a second final hash value having a size L, wherein the second final hash value is based on all hash values in the second set of one or more hash values.
[0316] Clause 91. A non-transitory computer-readable medium according to any one of clauses 82 to 89, wherein: the first set of one or more hash values includes hash values of size Z that are commonly associated with multiple expected measurement values among the one or more expected measurement values; and the second set of one or more hash values includes hash values of size Z that are commonly associated with multiple actual measurement values among the one or more actual measurement values; and Z is calculated based on the transmission block size, which is determined as Z = #layers*spectraleff*#REs, where #layers is the number of control information layers, spectraleff is the spectral efficiency, and #REs is the number of resource elements.
[0317] Clause 92. The non-transitory computer-readable medium of any one of clauses 82 to 91, wherein: the first set of one or more hash values is received using a Long Term Evolution Positioning Protocol (LPP).
[0318] Clause 93. A non-transitory computer-readable medium according to any one of clauses 82 to 91, wherein: the network node is a base station; the one or more PRS resources are uplink PRS (UL-PRS) resources; and the second set of one or more hash values is received from a user equipment (UE).
[0319] Clause 94. A non-transitory computer-readable medium as described in any one of clauses 82 to 91, wherein: the network node is a user equipment (UE); the one or more PRS resources are downlink PRS (DL-PRS) resources; and the first set of one or more hash values is received from a base station.
[0320] Clause 95. A non-transitory computer-readable medium according to any one of clauses 82 to 91, wherein: the network node is a first user equipment (UE); the first set of one or more hash values is received from a second UE; and the one or more PRS resources are sidelink PRS (SL-PRS) resources.
[0321] Clause 96. A non-transitory computer-readable medium as described in any of clauses 82 to 91, wherein: the network node is a user equipment (UE); and the first set of one or more hash values is received in a radio resource control (RRC) message.
[0322] Clause 97. A non-transitory computer-readable medium according to clause 96, wherein: the RRC information is carried in a physical downlink shared channel (PDSCH), a physical sidelink shared channel (PSSCH), or a combination thereof.
[0323] Clause 98. A non-transitory computer-readable medium according to any one of clauses 82 to 91, wherein: the first set of one or more hash values is received in one or more medium access control elements (MAC-CE) carried in a physical download control channel (PDCCH).
[0324] Clause 99. A non-transitory computer-readable medium as described in any of clauses 82 to 91, wherein the first set of one or more hash values is received in one or more medium access control elements (MAC-CE) carried in a physical sidelink control channel (PSCCH), sidelink control information carried in the PSCCH, or a combination thereof.
[0325] Clause 100. A non-transitory computer-readable medium according to any one of clauses 82 to 99, wherein the computer executable instructions that, when executed by the network node, cause the network node to determine whether the one or more actual measured values of the one or more PRS resources are within acceptable limits of the one or more expected measured values include: computer executable instructions that, when executed by the network node, cause the network node to: perform an assignment operation to assign one or more hash values from the second set of hash values to a set of hash bins, wherein the set of hash bins is based on the first set of hash values; and report information related to one or more hash values from the second set of hash values that cannot be assigned to allowed hash bins in the set of hash bins.
[0326] Clause 10 1. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a network node, causes the network node to: receive a first set of one or more hash values from a location server, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values, wherein the one or more expected measurement values correspond to expected measurements of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs) measured by a user equipment (UE) during a positioning session; and use the first set of one or more hash values for PRS attack detection.
[0327] Clause 102. A non-transitory computer-readable medium as described in clause 101, wherein the computer executable instructions that, when executed by the network node, cause the network node to use the first set of one or more hash values for PRS attack detection include computer executable instructions that, when executed by the network node, cause the network node to perform the following actions: sending the first set of one or more hash values to the UE; and receiving an indication from the UE that one or more actual measurement values obtained by the UE are outside of acceptable limits for one or more expected measurement values.
[0328] Clause 103. A non-transitory computer-readable medium as described in clause 102, wherein: the indication from the UE comprises a bitmap, the bitmap comprising flags indicating which parameters of the one or more actual measured values are outside of the acceptable limits.
[0329] Clause 104. A non-transitory computer-readable medium as described in any of clauses 102 to 103, wherein: the indication from the UE includes an indication of the extent to which the one or more actual measurement values are outside the acceptable limits.
[0330] Clause 105. The non-transitory computer-readable medium described in any one of clauses 102 to 104 further includes: computer executable instructions that, when executed by the network node, cause the network node to perform the following actions: report to the location server error information related to the one or more actual measurement values obtained by the UE that are outside the acceptable limits of the one or more expected measurement values.
[0331] Clause 106. A non-transitory computer-readable medium according to any one of clauses 101 to 105, wherein the computer executable instructions that, when executed by the network node, cause the network node to use the first set of one or more hash values for PRS attack detection include computer executable instructions that, when executed by the network node, cause the network node to perform the following actions: receive a second set of one or more hash values corresponding to one or more actual measurement values taken by the UE for the one or more PRS resources; and determine whether the one or more actual measurement values of the one or more PRS resources are within acceptable limits of the one or more expected measurement values based on a comparison of the second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying the one or more hash operations to the one or more actual measurement values.
[0332] Clause 107. A non-transitory computer-readable medium as described in clause 106, wherein the second set of one or more hash values is based on applying the one or more hash operations to: one or more actual reference signal received power (RSRP) measurements; one or more expected relative signal time difference (RSTD) measurements; one or more expected angle of arrival (AoA) measurements; or a combination thereof.
[0333] Clause 108. A non-transitory computer-readable medium according to any one of clauses 101 to 107, wherein the first set of one or more hash values is based on applying the one or more hash operations to: one or more expected PRS reference signal received power (PRS-RSRP) measurements; one or more expected PRS-RSRP uncertainty values associated with the one or more expected PRS-RSRP measurements; one or more expected reference signal time difference (RSTD) measurements; one or more expected RSTD uncertainty values associated with the one or more RSTD measurements; one or more expected angle of arrival (AoA) measurements; one or more expected AoA uncertainty values associated with the one or more AoA measurements; one or more expected zenith angle of arrival (ZoA) measurements; one or more expected ZoA uncertainty values associated with the one or more ZoA measurements; one or more expected zenith angle of departure (ZoD) measurements; one or more expected ZoD uncertainty values associated with the one or more ZoD measurements; or any combination thereof.
[0334] It will be understood by those skilled in the art that information and signals may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.
[0335] In addition, it will be appreciated by those skilled in the art that the various exemplary logic blocks, modules, circuits and algorithmic steps described in conjunction with the various aspects disclosed herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, frames, modules, circuits and steps have been generally described in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints proposed to the entire system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
[0336] The various illustrative logical blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.
[0337] The methods, sequences and / or algorithms described in conjunction with the various aspects disclosed herein may be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be integral with the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In an alternative, the processor and the storage medium may reside in a user terminal as discrete components.
[0338] In one or more example aspects, the function can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the function can be stored on a computer-readable medium or sent by a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a computer. Exemplarily and not restrictively, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and can be accessed by a computer. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, a server, or other remote sources using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of the medium. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
[0339] Although the foregoing disclosure shows the exemplary aspects of the present disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the present disclosure as defined by the appended claims. In addition, the functions, steps and / or actions of the method claims according to the various aspects of the present disclosure described herein do not need to be performed in any particular order. In addition, although the elements of the present disclosure may be described or claimed in the singular, plural forms may also be considered unless explicitly stated to be limited to the singular.
Claims
1. A method of wireless communication performed by a network node, include: receiving a first set of one or more hash values, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs); measuring the one or more PRS resources to obtain one or more actual measurement values; as well as Determining whether the one or more actual measured values of the one or more PRS resources are within acceptable limits of the one or more expected measured values based on a comparison of a second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying the one or more hash operations to the one or more actual measured values.
2. The method according to claim 1, further comprising: include: Receive a configuration of the one or more PRS resources of the one or more TRPs to be measured during a positioning session.
3. The method according to claim 1, further comprising: include: determining, based on the comparison of the second set of one or more hash values with the first set of one or more hash values, that at least one of the one or more actual measurement values is outside of the acceptable limit for at least one of the one or more expected measurement values; as well as Error information related to the at least one actual measurement value of the one or more actual measurement values is reported.
4. The method according to claim 3, in: The error information comprises a bitmap comprising flags indicating which parameters of the at least one actual measurement value are outside the acceptable limits.
5. The method according to claim 3, in: The error information includes an indication of the extent to which the at least one actual measurement is outside the acceptable limits.
6. The method of claim 1 , wherein the first set of one or more hash values is based on applying the one or more hash operations to: one or more expected PRS reference signal received power (PRS-RSRP) measurement values; one or more PRS-RSRP uncertainty values associated with the one or more expected PRS-RSRP measurement values; one or more expected reference signal time difference (RSTD) measurements; one or more RSTD uncertainty values associated with the one or more expected RSTD measurements; One or more expected angle of arrival (AoA) measurements; one or more AoA uncertainty values associated with the one or more AoA measurements; one or more expected angle of departure (AoD) measurements; one or more AoD uncertainty values associated with the one or more AoD measurements; One or more expected zenith angle of arrival (ZoA) measurements; one or more ZoA expected uncertainty values associated with the one or more ZoA measurements; One or more expected departure zenith angle (ZoD) measurements; one or more expected ZoD uncertainty values associated with the one or more ZoD measurement values; or Any combination of them.
7. The method of claim 1 , wherein the second set of one or more hash values is based on applying the one or more hash operations to: one or more actual reference signal received power (RSRP) measurements; one or more actual relative signal time difference (RSTD) measurements; One or more actual Angle of Arrival (AoA) measurements; One or more actual zenith angle of arrival (ZoA) measurements; One or more actual departure zenith angle (ZoD) measurements; or Any combination of them.
8. The method according to claim 1, in: The first set of one or more hash values comprises a hash value of size L respectively associated with each of the one or more expected measurement values; and The second set of one or more hash values includes a hash value of size L respectively associated with each actual measurement value of the one or more actual measurement values.
9. The method according to claim 8, further comprising: include: receiving a first final hash value having a size L, wherein the first final hash value is based on all hash values in the first set of one or more hash values; as well as A second final hash value of size L is received, wherein the second final hash value is based on all hash values in the second set of one or more hash values.
10. The method according to claim 1, in: The first set of one or more hash values includes hash values of size Z commonly associated with a plurality of the one or more expected measurement values; and The second set of one or more hash values includes hash values of size Z commonly associated with a plurality of the one or more actual measurement values; and Z is calculated based on the transport block size, which is determined as Z=#layers*spectral eff *#REs in #layers controls the number of information layers. spectral eff is the spectral efficiency, and #REs is the number of resource elements.
11. The method according to claim 1, in: The first set of one or more hash values is received using a Long Term Evolution Positioning Protocol (LPP).
12. The method according to claim 1, in: The network node is a base station; The one or more PRS resources are uplink PRS (UL-PRS) resources; and The second set of one or more hash values is received from a user equipment (UE).
13. The method according to claim 1, in: The network node is a user equipment (UE); The one or more PRS resources are downlink PRS (DL-PRS) resources; and The first set of one or more hash values is received from a base station.
14. The method according to claim 1, in: The network node is a first user equipment (UE); The first set of one or more hash values is received from a second UE; and the one or more PRS resources are sidelink PRS (SL-PRS) resources.
15. The method according to claim 1, in: The network node is a user equipment (UE); and The first set of one or more hash values is received in a radio resource control (RRC) message.
16. The method according to claim 15, in: The RRC information is in Physical Downlink Shared Channel (PDSCH), Physical Sidelink Shared Channel (PSSCH) or Carried in their combination.
17. The method according to claim 1, in: The first set of one or more hash values is received in one or more Medium Access Control - Control Elements (MAC-CE) carried in a Physical Download Control Channel, PDCCH.
18. The method of claim 1, wherein the first set of one or more hash values is received in: One or more Medium Access Control-Control Elements (MAC-CEs) carried in the Physical Sidelink Control Channel (PSCCH), The sidelink control information carried in the PSCCH, or A combination of them.
19. The method of claim 1, wherein determining whether the one or more actual measured values of the one or more PRS resources are within acceptable limits of the one or more expected measured values include: performing an assignment operation to assign one or more hash values in the second set of hash values to a set of hash bins, wherein the set of hash bins is based on the first set of hash values; as well as Information related to one or more hash values in the second set of hash values that cannot be assigned to an allowed hash bin in the set of hash bins is reported.
20. A method of wireless communication performed by a network node, include: receiving a first set of one or more hash values from a location server, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values, wherein the one or more expected measurement values correspond to expected measurements of one or more positioning reference signal (PRS) resources of one or more transmit reception points (TRPs) measured by a user equipment (UE) during a positioning session; as well as The first set of one or more hash values is used for PRS attack detection.
21. The method of claim 20, wherein the first set of one or more hash values is used for PRS attack detection include: sending the first set of one or more hash values to the UE; as well as An indication is received from the UE that one or more actual measurement values obtained by the UE are outside of acceptable limits for one or more expected measurement values.
22. The method according to claim 21, in: The indication from the UE comprises a bitmap including flags indicating which parameters of the one or more actual measured values are outside the acceptable limits.
23. The method according to claim 21, in: The indication from the UE comprises an indication of the extent to which the one or more actual measurement values are outside the acceptable limits.
24. The method according to claim 21, further comprising: include: Error information related to the one or more actual measurement values obtained by the UE that are outside the acceptable limits of the one or more expected measurement values is reported to the location server.
25. The method of claim 20, wherein the first set of one or more hash values is used for PRS attack detection include: receiving a second set of one or more hash values corresponding to one or more actual measurements taken by the UE for the one or more PRS resources; as well as Determining whether the one or more actual measured values of the one or more PRS resources are within acceptable limits of the one or more expected measured values based on a comparison of the second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying the one or more hash operations to the one or more actual measured values.
26. The method of claim 25, wherein the second set of one or more hash values is based on applying the one or more hash operations to: one or more actual reference signal received power (RSRP) measurements; one or more expected relative signal time difference (RSTD) measurements; One or more expected angle of arrival (AoA) measurements; or A combination of them.
27. The method of claim 20, wherein the first set of one or more hash values is based on applying the one or more hash operations to: one or more expected PRS reference signal received power (PRS-RSRP) measurement values; one or more expected PRS-RSRP uncertainty values associated with the one or more expected PRS-RSRP measurement values; one or more expected reference signal time difference (RSTD) measurements; one or more expected RSTD uncertainty values associated with the one or more RSTD measurements; One or more expected angle of arrival (AoA) measurements; one or more expected AoA uncertainty values associated with the one or more AoA measurements; One or more expected zenith angle of arrival (ZoA) measurements; one or more expected ZoA uncertainty values associated with the one or more ZoA measurements; One or more expected departure zenith angle (ZoD) measurements; one or more expected ZoD uncertainty values associated with the one or more ZoD measurement values; or Any combination of them.
28. A network node, include: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receiving, via the at least one transceiver, a first set of one or more hash values, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs); measuring the one or more PRS resources to obtain one or more actual measurement values; as well as 29. Determine whether the one or more actual measured values of the one or more PRS resources are within acceptable limits of the one or more expected measured values based on a comparison of a second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying the one or more hash operations to the one or more actual measured values. The network node of claim 28, wherein the at least one processor is further configured to: A configuration of the one or more PRS resources of the one or more TRPs to be measured during a positioning session is received via the at least one transceiver.
30. The network node of claim 28, wherein the at least one processor is further configured to: determining, based on the comparison of the second set of one or more hash values and the first set of one or more hash values, that at least one of the one or more actual measurement values is outside of the acceptable limit for at least one of the one or more expected measurement values; and Error information related to the at least one actual measurement value of the one or more actual measurement values is reported via the at least one transceiver.
31. The network node according to claim 30, in: The error information comprises a bitmap comprising flags indicating which parameters of the at least one actual measurement value are outside the acceptable limits.
32. The network node according to claim 30, in: The error information includes an indication of the extent to which the at least one actual measurement is outside the acceptable limits.
33. The network node of claim 28, wherein the first set of one or more hash values is based on applying the one or more hash operations to: one or more expected PRS reference signal received power (PRS-RSRP) measurement values; one or more PRS-RSRP uncertainty values associated with the one or more expected PRS-RSRP measurement values; one or more expected reference signal time difference (RSTD) measurements; one or more RSTD uncertainty values associated with the one or more expected RSTD measurements; One or more expected angle of arrival (AoA) measurements; one or more AoA uncertainty values associated with the one or more AoA measurements; one or more expected angle of departure (AoD) measurements; one or more AoD uncertainty values associated with the one or more AoD measurements; One or more expected zenith angle of arrival (ZoA) measurements; one or more ZoA expected uncertainty values associated with the one or more ZoA measurements; One or more expected departure zenith angle (ZoD) measurements; one or more expected ZoD uncertainty values associated with the one or more ZoD measurement values; or Any combination of them.
34. The network node of claim 28, wherein the second set of one or more hash values is based on applying the one or more hash operations to: one or more actual reference signal received power (RSRP) measurements; one or more actual relative signal time difference (RSTD) measurements; One or more actual Angle of Arrival (AoA) measurements; One or more actual zenith angle of arrival (ZoA) measurements; One or more actual departure zenith angle (ZoD) measurements; or Any combination of them.
35. The network node according to claim 28, in: The first set of one or more hash values comprises a hash value of size L respectively associated with each of the one or more expected measurement values; and The second set of one or more hash values includes a hash value of size L respectively associated with each actual measurement value of the one or more actual measurement values.
36. The network node of claim 35, wherein the at least one processor is further configured to: receiving, via the at least one transceiver, a first final hash value having a size L, wherein the first final hash value is based on all hash values in the first set of one or more hash values; and A second final hash value having a size L is received via the at least one transceiver, wherein the second final hash value is based on all hash values in the second set of one or more hash values.
37. The network node according to claim 28, in: The first set of one or more hash values includes hash values of size Z commonly associated with a plurality of the one or more expected measurement values; and The second set of one or more hash values includes hash values of size Z commonly associated with a plurality of the one or more actual measurement values; and Z is calculated based on the transport block size, which is determined as Z=#layers*spectral eff *#REs in #layers controls the number of information layers. spectral eff is the spectral efficiency, and #REs is the number of resource elements.
38. The network node according to claim 28, in: The first set of one or more hash values is received using a Long Term Evolution Positioning Protocol (LPP).
39. The network node according to claim 28, in: The network node is a base station; The one or more PRS resources are uplink PRS (UL-PRS) resources; and The second set of one or more hash values is received from a user equipment (UE).
40. The network node according to claim 28, in: The network node is a user equipment (UE); The one or more PRS resources are downlink PRS (DL-PRS) resources; and The first set of one or more hash values is received from a base station.
41. The network node according to claim 28, in: The network node is a first user equipment (UE); The first set of one or more hash values is received from a second UE; and the one or more PRS resources are sidelink PRS (SL-PRS) resources.
42. The network node according to claim 28, in: The network node is a user equipment (UE); and The first set of one or more hash values is received in a radio resource control (RRC) message.
43. The network node according to claim 42, in: The RRC information is in Physical Downlink Shared Channel (PDSCH), Physical Sidelink Shared Channel (PSSCH) or Carried in their combination.
44. The network node according to claim 28, in: The first set of one or more hash values is received in one or more Medium Access Control - Control Elements (MAC-CE) carried in a Physical Download Control Channel, PDCCH.
45. The network node of claim 28, wherein the first set of one or more hash values is received in: One or more Medium Access Control-Control Elements (MAC-CEs) carried in the Physical Sidelink Control Channel (PSCCH), The sidelink control information carried in the PSCCH, or A combination of them.
46. The network node of claim 28, wherein the at least one processor is configured to determine whether the one or more actual measured values of the one or more PRS resources are within acceptable limits for the one or more expected measured values comprises the at least one processor being configured to: performing an assignment operation to assign one or more hash values in the second set of hash values to a set of hash bins, wherein the set of hash bins is based on the first set of hash values; and Information related to one or more hash values in the second set of hash values that cannot be assigned to an allowed hash bin in the set of hash bins is reported via the at least one transceiver.
47. A network node, include: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receiving, via the at least one transceiver, from a location server a first set of one or more hash values, wherein the first set of one or more hash values is based on one or more hash operations applied to one or more expected measurement values, wherein the one or more expected measurement values correspond to expected measurements of one or more positioning reference signal (PRS) resources of one or more transmit receive points (TRPs) measured by a user equipment (UE) during a positioning session; as well as The first set of one or more hash values is used for PRS attack detection.
48. The network node of claim 47, wherein the at least one processor is configured to use the first set of one or more hash values for PRS attack detection comprises the at least one processor being configured to: transmitting, via the at least one transceiver, the first set of one or more hash values to the UE; and An indication is received from the UE via the at least one transceiver that one or more actual measurement values obtained by the UE are outside of acceptable limits for one or more expected measurement values.
49. The network node according to claim 48, in: The indication from the UE comprises a bitmap including flags indicating which parameters of the one or more actual measured values are outside the acceptable limits.
50. The network node according to claim 48, in: The indication from the UE comprises an indication of the extent to which the one or more actual measurement values are outside the acceptable limits.
51. The network node of claim 48, wherein the at least one processor is further configured to: Error information related to the one or more actual measurement values obtained by the UE that are outside the acceptable limits of the one or more expected measurement values is reported to the location server via the at least one transceiver.
52. The network node of claim 47, wherein the at least one processor is configured to use the first set of one or more hash values for PRS attack detection comprises the at least one processor being configured to: receiving, via the at least one transceiver, a second set of one or more hash values corresponding to one or more actual measurements taken by the UE for the one or more PRS resources; and Determining whether the one or more actual measured values of the one or more PRS resources are within acceptable limits of the one or more expected measured values based on a comparison of the second set of one or more hash values with the first set of one or more hash values, wherein the second set of one or more hash values is based on applying the one or more hash operations to the one or more actual measured values.
53. The network node of claim 52, wherein the second set of one or more hash values is based on applying the one or more hash operations to: one or more actual reference signal received power (RSRP) measurements; one or more expected relative signal time difference (RSTD) measurements; One or more expected angle of arrival (AoA) measurements; or A combination of them.
54. The network node of claim 47, wherein the first set of one or more hash values is based on applying the one or more hash operations to: one or more expected PRS reference signal received power (PRS-RSRP) measurement values; one or more expected PRS-RSRP uncertainty values associated with the one or more expected PRS-RSRP measurement values; one or more expected reference signal time difference (RSTD) measurements; one or more expected RSTD uncertainty values associated with the one or more RSTD measurements; One or more expected angle of arrival (AoA) measurements; one or more expected AoA uncertainty values associated with the one or more AoA measurements; One or more expected zenith angle of arrival (ZoA) measurements; one or more expected ZoA uncertainty values associated with the one or more ZoA measurements; One or more expected departure zenith angle (ZoD) measurements; one or more expected ZoD uncertainty values associated with the one or more ZoD measurement values; or Any combination of them.
