Location reliability information about the device location

Abstract

Various aspects of the present disclosure relate to methods, apparatus, and systems that support location reliability information for device locations. For example, the location reliability information indicates an estimated trust state (e.g., reliability) of location information that a receiving device can utilize to determine how or whether to use the location information. In at least some implementations, a device (e.g., a user equipment (UE) and / or a network entity such as a gNB) can utilize location information that is indicated as reliable (e.g., trusted), while the device can ignore location information that is indicated as unreliable, e.g., untrusted.

Description

[Technical Field]

[0001] Related Applications This application claims priority to U.S. patent application Ser. No. 63 / 396,828, filed Aug. 10, 2022, entitled "POSITION RELIABILITY INFORMATION FOR DEVICE POSITION," and U.S. patent application Ser. No. 63 / 396,839, filed Aug. 10, 2022, entitled "PRIORITY FOR POSITIONING INFORMATION," the disclosures of which are incorporated herein by reference in their entireties.

[0002] FIELD OF THE DISCLOSURE The present disclosure relates to wireless communications, and more particularly to position determination in wireless communications. [Background technology]

[0003] A wireless communication system may include one or more network communication devices, such as base stations, which may also be known as eNodeBs (eNBs), next-generation NodeBs (gNBs), or other appropriate terminology. Each network communication device, such as a base station, may support wireless communication for one or more user communication devices, which may also be known as user equipment (UEs), or other appropriate terminology. A wireless communication system may support wireless communication with one or more user communication devices by utilizing wireless communication system resources (e.g., time resources, (e.g., symbols, slots, subframes, frames, etc.)) or frequency resources (e.g., subcarriers, carriers). Additionally, a wireless communication system may support wireless communication over various radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, or other suitable radio access technology beyond 5G (e.g., sixth-generation (6G)).

[0004] Some wireless communication systems provide methods for device positioning, such as UE positioning, but some techniques do not support efficient determination of which location information and which location information source to use to determine UE positioning. Summary of the Invention [Means for solving the problem]

[0005] The present disclosure relates to methods, apparatus, and systems that support location reliability information for device locations. For example, the location reliability information indicates an estimated trust state (e.g., reliability) of location information that a receiving device can utilize to determine how and / or whether to use the location information. In at least some implementations, a device (e.g., a network entity such as a UE and / or gNB) can utilize location information that is indicated as reliable (e.g., trusted), while the device can ignore location information that is indicated as unreliable, e.g., untrusted.

[0006] By utilizing the described techniques, the speed, accuracy, and reliability of location information and location determination in wireless systems is improved.

[0007] Some implementations of the methods and apparatus described herein may further include, at the apparatus, generating location reliability information, the location reliability information including an estimated indication of a location trust state for the device, and transmitting the location reliability information.

[0008] In some implementations of the methods and apparatus described herein, the location reliability information is or includes one or more determined by at least one of speed, accuracy, speed class, or accuracy class, the apparatus includes a device for which the location reliability information is generated and further includes transmitting the location reliability information and a positioning reference signal, the location reliability information includes a message from a location management function (LMF) entity, the apparatus includes a device other than the device for which the location reliability information is generated, the location reliability information includes an indication of the mobility of the device, the location reliability information includes an indication of location reliability with respect to multiple spatial dimensions, the location reliability information includes an indication of the validity time of the location reliability information, and the location reliability information includes an indication of a reliability value of the location reliability information relative to a defined threshold reliability.

[0009] Some implementations of the methods and apparatus described herein may further include, at the apparatus, receiving location reliability information, the location reliability information including an estimated indication of a location trust state for the first device, and estimating a location of the second device based at least in part on the location reliability information for the first device.

[0010] In some implementations of the methods and devices described herein, the location reliability information includes one or more of a speed, an accuracy, a speed class, or an accuracy class, the device includes a second device whose location is estimated, and further includes transmitting the location reliability information and a positioning reference signal, the location reliability information includes a message from a location management function (LMF) entity, the device includes a device other than the device for which the location reliability information is generated, the location reliability information includes an indication of the mobility of the device, the location reliability information includes an indication of location reliability with respect to multiple spatial dimensions, the location reliability information includes an indication of the validity time of the location reliability information, and the location reliability information includes an indication of a reliability value of the location reliability information relative to a defined threshold reliability. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 illustrates an example wireless communication system that supports location reliability information regarding device location, according to aspects of the present disclosure. [Figure 2] FIG. 1 illustrates a system that can utilize different types of connectivity to determine device location. [Figure 3] FIG. 1 illustrates an exemplary system that supports positioning. [Figure 4] FIG. 1 illustrates a system capable of transmitting a PRS. [Figure 5] FIG. 1 illustrates an overview of absolute and relative positioning scenarios. [Figure 6] FIG. 1 illustrates an example block diagram of a device that supports location authority information about a device location, according to aspects of the present disclosure. [Figure 7] FIG. 1 illustrates an example block diagram of a device that supports location authority information about a device location, according to aspects of the present disclosure. [Figure 8] 1 is a flowchart of a method for supporting location authority information regarding a device location, according to an aspect of the present disclosure. [Figure 9] 1 is a flowchart of a method for supporting location authority information regarding a device location, according to an aspect of the present disclosure. [Figure 10] 1 is a flowchart of a method for supporting location authority information regarding a device location, according to an aspect of the present disclosure. [Figure 11] 1 is a flowchart of a method for supporting location authority information regarding a device location, according to an aspect of the present disclosure. [Figure 12] 1 is a flowchart of a method for supporting location authority information regarding a device location, according to an aspect of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0012] In some wireless communication systems, methods are provided for device positioning, such as UE positioning. Furthermore, for PRS transmission, such as in the context of sidelink transmission, UE-based positioning estimation may rely on PRSs transmitted by multiple downlink and / or sidelink transmissions. Sidelink PRSs may be transmitted by mobile devices, but fixed sidelink transmitters, such as roadside units (RSUs) and / or temporarily stationary UEs, may also be utilized. A UE that estimates its location by measuring signals from other UEs may rely on accurate knowledge of the location of the PRS transmitters. To have a sufficiently reliable estimate, the PRSs of multiple PRS transmitters can be detected and evaluated. However, some wireless communication systems may not be able to demonstrate reliability in their knowledge of the location of the PRS transmitters, which may lead to reduced accuracy in position determination.

[0013] Accordingly, the present disclosure relates to methods, apparatus, and systems that support location reliability information for device locations. For example, the location reliability information indicates an estimated trust state (e.g., reliability) of location information that a receiving device can utilize to determine how and / or whether to use the location information. In at least some implementations, a device (e.g., a network entity such as a UE and / or gNB) can utilize location information that is indicated as reliable (e.g., trusted), while the device can ignore location information that is indicated as unreliable, e.g., untrusted.

[0014] The described techniques can be utilized to improve the speed, accuracy, and reliability of location information and location determination in wireless systems. The described techniques can also reduce signaling overhead and device resource usage, such as processing and wireless resources.

[0015] Aspects of the present disclosure are described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described with reference to device drawings and flowcharts.

[0016] FIG. 1 illustrates an example of a wireless communication system 100 that supports location reliability information for device locations according to aspects of the present disclosure. The wireless communication system 100 may include one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technologies, including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), or IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G. Additionally, the wireless communication system 100 may support techniques such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0017] One or more network entities 102 may be distributed throughout a geographic region to form a wireless communication system 100. One or more of the network entities 102 described herein may be, include, or be referred to as a network node, base station, network element, Radio Access Network (RAN), base transceiver station, access point, NodeB, eNodeB (eNB), next generation NodeB (gNB), or other suitable terminology. The network entities 102 and the UEs 104 may communicate via a communication link 110, which may be a wireless connection or a wired connection. For example, the network entities 102 and the UEs 104 may perform wireless communication (e.g., receive signaling and transmit signaling) over a Uu interface.

[0018] A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) to one or more UEs 104 within the geographic coverage area 112. For example, the network entity 102 and the UEs 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, the network entity 102 may be mobile, e.g., a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, while different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout this specification may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0019] One or more UEs 104 may be dispersed throughout the geographic region of the wireless communication system 100. The UEs 104 may include or be referred to as mobile devices, wireless devices, remote devices, remote units, handheld devices, or subscriber devices, or some other suitable terminology. In some implementations, the UEs 104 may be referred to as units, stations, terminals, or clients, among other examples. Additionally or alternatively, the UEs 104 may be referred to as Internet-of-Things (IoT) devices, Internet-of-Everything (IoE) devices, or machine-type communication (MTC) devices, among other examples. In some implementations, the UEs 104 may be stationary within the wireless communication system 100. In some other implementations, the UEs 104 may be mobile within the wireless communication system 100.

[0020] One or more UEs 104 may be devices in different forms or with different capabilities. Some examples of UEs 104 are shown in FIG. 1. The UE 104 may be able to communicate with various types of devices, such as network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment), as shown in FIG. 1. Additionally or alternatively, the UE 104 may support communication with other network entities 102 or UEs 104 that may function as relays in the wireless communication system 100.

[0021] The UE 104 may also be able to support direct wireless communication with other UEs 104 via a communication link 114. For example, the UE 104 may support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V), V2X, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, the UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.

[0022] A network entity 102 may support communication with the core network 106, or another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 via one or more backhaul links 116 (e.g., via an S1, N2, N3, or another network interface). The network entities 102 may communicate with each other via the backhaul links 116 (e.g., via an X2, Xn, or another network interface). In some implementations, the network entities 102 may communicate directly with each other (e.g., between the network entities 102). In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more network entities 102 may include sub-components such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transmission entities, which may be referred to as a radio head, a smart radio head, or a transmission-reception point (TRP).

[0023] In some implementations, the network entities 102 may be configured in a disaggregated architecture that may be configured to utilize a physically or logically distributed protocol stack between two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., cloud RAN (C-RAN)). For example, the network entities 102 may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0024] An RU may also be referred to as a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of the network entity 102 in a split RAN architecture may be co-located, or one or more components of the network entity 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a split RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0025] The division of functionality among the CU, DU, and RU may be flexible and may support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are executed in the CU, DU, or RU. For example, a functional division of the protocol stack may be adopted between the CU and DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host functions of upper protocol layers (e.g., Layer 3 (L3), Layer 2 (L2)) and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU may be connected to one or more DUs or RUs, which may host the functionality and signaling of lower protocol layers such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer), each of which may be at least partially controlled by the CU.

[0026] Additionally or alternatively, a functional division of the protocol stack may be employed between the DU and the RU, such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or more different cells (e.g., via one or more RUs). In some implementations, the functional division between the CU and the DU or between the DU and the RU may be within a protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by a different one of the CU, DU, or RU).

[0027] The CU may be further functionally separated into a CU control plane (CU-CP) function and a CU user plane (CU-UP) function. The CU may be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and the DUs may be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul or fronthaul communication links may be implemented according to interfaces (e.g., channels) between layers of protocol stacks supported by the respective network entities 102 communicating via such communication links.

[0028] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)) and user plane entities that route packets or interconnect to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with the core network 106.

[0029] The core network 106 may communicate with the packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. The UE 104 may establish a session (e.g., a protocol data unit (PDU) session, etc.) with the core network 106 via the network entity 102. The core network 106 may route traffic (e.g., control information, data, etc.) between the UE 104 and the application server 118 using the established session (e.g., an established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106).

[0030] In the wireless communication system 100, the network entity 102 and the UE 104 may use resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the network entity 102 and the UE 104 may support different resource structures. For example, the network entity 102 and the UE 104 may support different frame structures. In some implementations, such as 4G, the network entity 102 and the UE 104 may support a single frame structure. In some other implementations, such as 5G and other suitable radio access technologies, the network entity 102 and the UE 104 may support various frame structures (i.e., multiple frame structures). The network entity 102 and the UE 104 may support various frame structures based on one or more numerologies.

[0031] One or more numerologies may be supported in the wireless communication system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. A first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0032] Time intervals of resources (e.g., communication resources) may be organized according to frames (also called radio frames). Each frame may have a duration, e.g., 10 milliseconds (ms). In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, e.g., 1 ms. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0033] Additionally or alternatively, time intervals of resources (e.g., communication resources) may be organized according to slots. For example, a subframe may include several (e.g., a certain amount) of slots. Each slot may include several (e.g., a certain amount) of symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols). In some implementations, the number (e.g., amount) of slots in a subframe may depend on the numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on the numerology. It should be understood that references to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframe and slot.

[0034] In the wireless communication system 100, the electromagnetic (EM) spectrum may be divided into various classes, frequency bands, frequency channels, etc. based on frequency or wavelength. By way of example, the wireless communication system 100 may support one or more operating frequency bands, such as frequency range designations FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some implementations, the network entity 102 and the UE 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entity 102 and the UE 104, among other equipment or devices, for cellular communication traffic (e.g., control information, data). In some implementations, FR2 may be used by the network entity 102 and the UE 104, among other equipment or devices, for short-range, high-data-rate capabilities.

[0035] FR1 may be associated with one or more numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., μ=0) including a subcarrier spacing of 15 kHz, a second numerology (e.g., μ=1) including a subcarrier spacing of 30 kHz, and a third numerology (e.g., μ=2) including a subcarrier spacing of 60 kHz. FR2 may be associated with one or more numerologies (e.g., at least two numerologies). For example, FR2 may be associated with a third numerology (e.g., μ=2) including a subcarrier spacing of 60 kHz, and a fourth numerology (μ=3) including a subcarrier spacing of 120 kHz.

[0036] According to an implementation related to location reliability information for a device location, the UE 104(1) can receive location reliability information 120 from a positioning reference node, such as a different UE 104, network entity 102, etc. The location reliability information 120 can be associated with a PRS from the positioning reference node, for example. Alternatively, the location reliability information 120 can include location reliability information without a PRS. Thus, based at least in part on the location reliability information 120, the UE 104(1) performs a position determination 122. For example, based on the location reliability information 120, the UE 104(1) processes the PRS to determine whether and / or which PRS to use to determine the location of the UE 104(1). Based on the position determination, the UE 104(1) generates a location notification 124 indicating an estimated location of the UE 104(1). In at least one implementation, the location notification 124 also indicates a confidence state of the location information, for example, how confident the UE 104(1) is that the position determination is accurate. Thus, the UE 104(1) may send a location notification 124 to the network entity 102 and / or to a different UE 104, etc.

[0037] 2 illustrates a system 200 that can utilize various types of connectivity to determine device location. The system 200 includes different infrastructure components, including roadside units (RSUs) and servers, interconnected via a network, such as the Internet. Additionally, the system 200 includes vehicles with onboard units (OBUs) capable of wireless communication. The various components of the system 200 can communicate with each other via wireless connectivity, including infrastructure-to-vehicle communication 202, infrastructure-to-infrastructure communication 204, and vehicle-to-vehicle communication 206. For example, different types of connectivity can be utilized to determine the location of vehicles in the system 200.

[0038] In some wireless communication systems, NR positioning based on NR Uu signals and a standalone (SA) architecture (e.g., beam-based transmission) is specified as specified in Rel-16. Targeted use cases include commercial and regulatory (emergency services) scenarios as in Rel-15. Performance requirements are as follows:

[0039] [Table 1]

[0040] The current 3GPP Rel-17 positioning recently defined the positioning performance requirements for commercial and IIoT use cases as follows:

[0041] [Table 2]

[0042] 5G NR offers several enhanced parameters for positioning accuracy estimation over previous mobile generations, especially for time-based and angle-based positioning methods. For example: The delay error variance decreases as the bandwidth increases, exponentially increasing as the square of the bandwidth. However, the angular variance is completely independent of the bandwidth. NR offers significant bandwidth improvements over LTE, with NR offering up to 100 MHz in frequency range 1 and 400 MHz in frequency range 2, compared to LTE's maximum of 20 MHz. Received power is inversely proportional to all estimation variances. In NR, received power can be increased by beamforming. This is especially important for numerologies with larger subcarrier spacing. NR offers five different choices for subcarrier spacing: 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. Subcarrier spacing is a bit peculiar because it gives a linear increase in angular dispersion while at the same time only a linear decrease in delay dispersion. This effect comes from noise variance, which increases linearly with subcarrier spacing. The natural way to counter this is to increase the receiver power. Different antenna patterns, such as spacing and number of polarizations relative to rows and columns in an antenna array, do not affect delay variance; only the total number of antenna elements in the array matters. For angle estimates, the variance is proportional to the inverse square of the antenna spacing. Furthermore, the number of rows and columns in an antenna array each gives a cubed reduction in the variance of the angle estimate. NR devices typically have a larger number of antennas.

[0043] FIG. 3 illustrates an example system 300 that supports positioning. In the system 300, a location management function (LMF) is central to the 5G positioning architecture. The LMF receives measurements and assistance information from the next generation radio access network (NG-RAN) and mobile device (UE) via the access and mobility management function (AMF) over the NL interface to calculate the UE's position. The new next-generation interface between the NG-RAN and the core network introduces the new NR positioning protocol A (NRPPa) protocol to carry positioning information between the NG-RAN and the LMF over the next-generation control plane interface (NG-C). These additions to the 5G architecture provide a framework for positioning in 5G. The LMF configures the UE using the LTE positioning protocol (LPP) over the AMF. The NG RAN configures the UE using the RRC protocol over LTE-Uu and NR-Uu.

[0044] To enable more accurate positioning measurements than LTE, new reference signals have been added to the NR specifications. These signals are the PRS in the downlink and the sounding reference signal (SRS) for positioning in the uplink. The downlink PRS is the primary reference signal supporting downlink-based positioning methods. While other signals can be used, the PRS is specifically designed to provide the highest possible accuracy, coverage, and interference avoidance and suppression.

[0045] To design an efficient PRS, special care was taken to give the signal a large delay spread range, since the signal must be received from potentially distant neighboring base stations for location estimation. This is achieved by transmitting the PRS over multiple symbols that can be aggregated to cover the entire NR band and accumulate power. The density of subcarriers occupied in a given PRS symbol is called the comb size. There are several configurable comb-based PRS patterns for combs 2, 4, 6, and 12 that suit different scenarios serving different use cases. The pattern shown corresponds to comb 6, with three base stations multiplexed over one slot period. For a comb N PRS, N symbols can be combined to cover all subcarriers in the frequency domain.

[0046] Each base station can then transmit on a different set of subcarriers to avoid interference. This solution is also latency-efficient, since several base stations can transmit simultaneously without interfering with each other. Furthermore, it is possible to mute the PRS signals from one or more base stations at a given time according to a muting pattern, further reducing potential interference. For use cases with higher transmission loss (e.g., in macrocell deployments), the PRS can also be configured to be repeated to improve listenability.

[0047] Examples of positioning techniques supported in Rel-16 are listed in Table 1.

[0048] [Table 3]

[0049] Individual positioning techniques, such as those shown in Table 1 (Table 3), can currently be configured and implemented based on the requirements of the Location Management Function (LMF) and the UE capabilities. The transmission of Uu (uplink and downlink) PRS enables the UE to perform UE positioning-related measurements to enable the calculation of the UE's absolute position estimate and is configured per Transmit / Receive Point (TRP), which may contain a set of one or more beams. A conceptual overview is shown in Figure 1.

[0050] FIG. 4 illustrates a system 400 capable of transmitting a PRS. The system 400 illustrates that, for example, in accordance with Rel-16, a PRS can be transmitted by different base stations (serving and neighboring) using narrow beams spanning FR1 and FR2, which is relatively different compared to LTE, in which a PRS was transmitted across the entire cell. A PRS can be locally associated with a PRS resource identifier (ID) and resource set ID of a base station (TRP). Similarly, UE positioning measurements, such as reference signal time difference (RSTD) measurements and PRS reference signal received power (RSRP) measurements, are performed between beams (e.g., between different pairs of downlink (DL) PRS resources or DL ​​PRS resource sets) rather than between different cells as in LTE. Additionally, there are additional uplink (UL) positioning methods that the network utilizes to calculate the location of a target UE. RAT-dependent positioning techniques involve 3GPP RATs and core network entities to perform location estimation of the UE, which is distinguished from RAT-independent positioning techniques that rely on global navigation satellite systems (GNSS), inertial measurement unit (IMU) sensors, WLAN, and Bluetooth technologies to perform positioning of the target device (UE).

[0051] FIG. 5 shows an overview of absolute and relative positioning scenarios as defined in the system architecture using three different coordinate systems. Absolute positioning, fixed coordinate system Relative positioning, variable and moving coordinate systems Relative positioning, variable coordinate system

[0052] The following RAT dependent positioning techniques are supported in Rel-16 and Rel-17:

[0053] DL-TDoA The DL time difference of arrival (TDOA) positioning method utilizes DL RSTD (and optionally DL PRS RSRP) of downlink signals received at a UE from multiple TPs. The UE measures the DL RSTD (and optionally DL PRS RSRP) of the received signals using assistance data received from a positioning server, and the resulting measurements are used together with other configuration information to determine the UE's position relative to neighboring TPs.

[0054] DL-AoD The DL AoD positioning method utilizes measured DL PRS RSRPs of downlink signals received at a UE from multiple TPs. The UE measures the DL PRS RSRPs of the received signals using assistance data received from a positioning server, and the resulting measurements are used together with other configuration information to determine the UE's position relative to neighboring TPs.

[0055] Multi-RTT The multi-round trip time (RTT) positioning method utilizes UE Rx-Tx measurements and DL PRS RSRP of downlink signals received from multiple TRPs measured by the UE, and gNB Rx-Tx measurements and UL SRS-RSRP measured at multiple TRPs of uplink signals transmitted from the UE.

[0056] The UE uses the assistance data received from the positioning server to measure UE Rx-Tx measurements (and optionally DL PRS RSRP of the received signal), and the TRP uses the assistance data received from the positioning server to measure gNB Rx-Tx measurements (and optionally UL SRS-RSRP of the received signal). The measurements are used to determine the RTT at the positioning server, which is used to estimate the UE's position (see Figure 4). Multi-RTT is only supported for UE-assisted / NG-RAN-assisted positioning techniques, as shown in Table 1.

[0057] E-CID / NR E-CID In the enhanced Cell ID (CID) positioning method, the UE's location is estimated using knowledge of its serving ng-eNB, gNB, and cells and is based on LTE signals. Information about the serving ng-eNB, gNB, and cells may be obtained by paging, registration, or other methods. NR enhanced Cell ID (NR E CID) positioning refers to techniques that use additional UE measurements and / or NR radio resources and other measurements to improve UE position estimation using NR signals.

[0058] Although NR E-CID positioning may utilize some of the same measurements as the measurement control system in the RRC protocol, the UE is generally not expected to perform additional measurements solely for positioning purposes; i.e., the positioning procedure does not provide measurement configuration or measurement control messages, and the UE reports available measurements rather than being required to perform additional measurement actions.

[0059] UL-TDoA The UL TDOA positioning method utilizes the UL TDOA (and optionally the UL SRS-RSRP) at multiple RPs of uplink signals transmitted from the UE. The RPs measure the UL TDOA (and optionally the UL SRS-RSRP) of the received signals using assistance data received from a positioning server, and the resulting measurements are used, along with other configuration information, to estimate the UE's position.

[0060] UL-AoA The UL AoA positioning method utilizes measured azimuth and apex angles of arrival at multiple RPs of uplink signals transmitted from a UE. The RPs use assistance data received from a positioning server to measure the A-AoA and Z-AoA of the received signals, and the resulting measurements are used, along with other configuration information, to estimate the UE's position.

[0061] RAT-independent positioning techniques: Network-assisted GNSS method These methods utilize a UE equipped with a radio receiver capable of receiving GNSS signals. In the 3GPP specifications, the term GNSS encompasses both global navigation satellite systems and regional / augmented navigation satellite systems.

[0062] Examples of global positioning satellite systems include the Global Positioning System (GPS), modernized GPS, Galileo, GLONASS, and the BeiDou Navigation Satellite System (BDS). Regional navigation satellite systems include the Quasi-Zenith Satellite System (QZSS), while many augmentation systems fall under the general term Space Based Augmentation System (SBAS) and provide regional augmentation services. In this concept, different GNSS (e.g., GPS, Galileo, etc.) can be used individually or in combination to determine the location of a UE.

[0063] Barometric pressure sensor positioning The barometric pressure sensor method utilizes a barometric pressure sensor to determine the vertical component of the UE's position. The UE measures barometric pressure data, optionally aided by assistance data, to calculate the vertical component of its position or to send measurements to a positioning server for position calculation. This method should be combined with other positioning methods to determine the UE's 3D position.

[0064] WLAN positioning Wireless local access network (WLAN) positioning methods utilize WLAN measurements (access point (AP) identifiers and optionally other measurements) and a database to determine the location of a UE. The UE measures received signals from WLAN access points, optionally aided by assistance data, to send the measurements to a positioning server for position calculation. Using the measurement results and a reference database, the UE's location is calculated.

[0065] Alternatively, the UE utilizes WLAN measurements provided by a positioning server and, optionally, WLAN AP assistance data to determine its location.

[0066] Bluetooth positioning The Bluetooth positioning method utilizes Bluetooth measurements (beacon identifiers and optionally other measurements) to determine the location of a UE. The UE measures the received signals from Bluetooth beacons. Using the measurements and a reference database, the location of the UE is calculated. The Bluetooth method can be combined with other positioning methods (e.g., WLAN) to improve the accuracy of UE positioning.

[0067] TBS Positioning A Terrestrial Beacon System (TBS) consists of a network of ground-based transmitters that broadcast signals solely for positioning purposes. Current types of TBS positioning signals are Metropolitan Beacon System (MBS) signals and PRS. A UE measures received TBS signals, optionally aided by assistance data, to calculate its position or send measurements to a positioning server for position calculation.

[0068] Motion sensor positioning The motion sensor method utilizes various sensors, such as accelerometers, gyros, and magnetometers, to calculate the displacement of the UE. The UE estimates the relative displacement based on a reference position and / or a reference time. The UE sends a report containing the determined relative displacement, which can be used to determine the absolute position. This method should be used with other positioning methods for hybrid positioning.

[0069] To ameliorate the challenges presented in device positioning in some wireless communication systems, this disclosure details solutions for determining and identifying the reliability of location information, e.g., PRS, as well as priority information for determining the priority of location information transmitters and the location information data itself.

[0070] The following terms may be used within this disclosure, and the following provides some exemplary, non-limiting explanations of these terms: ·Target UE may be referred to as the subject UE whose location (absolute or relative) should be obtained by the network or the UE itself. Sidelink positioning: Positioning a UE using reference signals transmitted over the sidelink (SL) (e.g., PC5 interface) to obtain absolute position, relative position, and / or ranging information. Ranging: Determining the distance and / or direction between the UE and another entity, e.g., an anchor UE. Anchor UE: A UE that supports the positioning of a target UE, e.g., by transmitting and / or receiving reference signals for positioning and providing positioning related information, such as via a sidelink interface. An SL positioning node may refer to a network entity and / or device (e.g., UE) participating in an SL positioning session and may be implemented as an LMF (location server), gNB, UE, RSU, anchor UE, initiator and / or responder UE, etc. · SL PRS (pre)configuration: (Pre)configured parameters of the SL PRS such as time-frequency resources including bandwidth and periodicity (other parameters are not excluded).

[0071] According to an implementation, location reliability information is generated and communicated to a positioning reference node (PRN) (e.g., an RSU) about the position accuracy of the PRN or the reliability of the PRN's mobility. This information can be used, for example, by other nodes determining their own position relative to the anchor node (e.g., the PRN) or by using knowledge of the anchor node's mobility.

[0072] A PRN may refer to a node capable of transmitting a PRS and / or other signals intended to measure relative or absolute position. This does not necessarily mean that such a node is actually used as a reference within the system; for example, if the node is highly mobile relative to other nodes, it may not be used as a positioning reference by such other nodes.

[0073] In at least one implementation, a node in a communication system communicates location reliability information, e.g., information regarding mobility and / or location reliability of positioning information such as PRS. Nodes communicating location reliability information can be, for example: A PRN that transmits location reliability information about itself. For example, the anchor node may transmit the location reliability information together with or independently of the PRS, such as in a unicast message, groupcast message, and / or broadcast message that can be received by other nodes in the communication system. The other nodes may be other UEs within the communication range of a network node such as an anchor node and / or a gNB or LMF entity. A network node (such as a gNB, LMF, and / or other network function entity) may transmit location reliability information regarding the PRN. For example, the LMF may indicate one or more identities of PRNs that may be considered stationary and / or whose location information may be expected to have high reliability. Alternatively or additionally, the LMF may indicate one or more identities of PRNs that may be considered mobile and / or whose location information may be expected to have low reliability.

[0074] In at least one implementation, the location reliability information for the PRN can be one or more of the following: Whether the PRN is stationary or mobile For example, a gNB, RSU, or CPE can be considered stationary Whether the PRS exceeds the preset speed Mobility class index as shown in Table 2 and Table 3 below, e.g.

[0075] [Table 4]

[0076] [Table 5]

[0077] In at least one implementation, if multiple rate indicators apply, the most stringent applicable rate class (eg, the lowest rate) may be utilized.

[0078] In at least one implementation, the configurability of the corresponding class / rate value or range is an optional element. Furthermore, in at least some implementations, the indicated rate, or the rate at which the indicated reliability class is determined, is an "absolute" rate, e.g., a rate relative to a stationary environment, such as a fixed installation of a global coordinate system, a gNB, a RUS, etc. According to alternative or additional implementations, the indicated rate, or the rate at which the indicated reliability class is determined, is a rate relative to a recipient of the information, such as another UE, such as the target UE.

[0079] The location reliability information for the PRN may also include one or more of the following: Standard deviation of estimated position for configurable values For example, if the variance is less than 0.5 meters, high confidence may be indicated, and if the variance is 0.5 meters or more, low confidence may be indicated. - The threshold may be configurable according to the accuracy parameters (e.g., accuracy requirements) of the positioning use case. Location reliability information may reflect multiple accuracies, for example, the information may indicate one or more accuracy thresholds that may or may not be met. For example, the reliability may indicate which of multiple accuracies are likely to be met so that other nodes may determine whether the PRN is a useful PRN for obtaining positioning information based on their positioning use case (e.g., accuracy parameters).

[0080] Tables 4 and 5 show examples of different accuracy metrics that can be included within the location reliability information.

[0081] [Table 6]

[0082] [Table 7]

[0083] With respect to Table 4 and Table 5, if multiple classes apply, the location reliability information may indicate the most stringent applicable accuracy / reliability class, e.g., the highest met accuracy. Furthermore, in at least some implementations, the configurability of the corresponding class / accuracy value or range is an optional element.

[0084] According to one or more implementations, the location reliability information can be further enhanced as follows. Mobility characteristics (e.g., stationary / moving) can be further described by dimension, e.g., a drone may be temporarily stationary in altitude but not in longitude or latitude. For example, vertical velocity may be small, but horizontal velocity may be relatively large. Additional location reliability information may include, for example, the speed and / or direction of movement of the PRS transmitter, either absolute or relative to the PRS measuring device, for example, towards or away from the target UE.

[0085] According to one or more implementations, location reliability information can be provided to: One or more PRS receivers, for example, by instruction together with DL / SL control information. For example, LMF along with position reports. The LMF may also provide mobility information of potential PRS transmitters to the target UE.

[0086] According to one or more implementations, the location reliability information includes a validity time indication, e.g., for how long (and / or until when) the corresponding location reliability information can be considered valid. Alternatively or additionally, the location reliability information includes an expiration indication, e.g., after how long (and / or what time value) the corresponding location reliability information should be considered valid.

[0087] Implementations described herein also enable prioritization of positioning according to different criteria (e.g., prioritization of positioning information transmitters and / or positioning information). Positioning prioritization can be applied to positioning purposes such as measuring PRS from trusted positioning nodes, calculating a position using PRS measurements based on PRS transmitted by trusted positioning nodes, reporting measurements based on trusted positioning nodes, and / or calculating a position based on PRS measurements.

[0088] According to implementations, one or more of the following criteria may be used to determine priority for purposes of positioning prioritization: PRS transmitter mobility: For example, among multiple PRS transmitters, the most stationary (eg, least mobile) PRS transmitter may be prioritized for evaluation. For example, lower mobility (eg, lower speed) is associated with higher priority and higher mobility (eg, higher speed) is associated with lower priority. · Estimated path loss between the PRS transmitter and the UE: For example, the PRS transmitter with the smallest estimated path loss (eg, based on signal to interference plus noise ratio (SINR)) is prioritized. For example, lower path loss is associated with higher priority and higher path loss is associated with lower priority. Line-of-Sight (LOS) indication: e.g., whether the channel from the UE from anchor to target is LOS or non-LOS (NLOS). For example, PRS measurements from LOS channels are preferred. For example, LOS channels are associated with higher priority and NLOS channels are associated with lower priority. Signal Metrics: Based on SL PRS measurement metrics such as RSRP, received signal strength indicator (RSSI), and / or other received signal quality metrics. For example, a lower signal metric (eg, RSRP, RSSI) is associated with a higher priority and a higher signal metric is associated with a lower priority. Based on a validity time indication: for example, how long (and / or until when) the location reliability information can be considered valid. Alternatively or additionally, the location reliability information may include an expiration indication, for example, after how long (and / or what time value) the corresponding location reliability information should be considered invalid. For example, location reliability information that is deemed valid may be associated with a higher priority, and location reliability information that is deemed invalid may be associated with a lower priority. Additionally or alternatively, location reliability information that is deemed valid for a longer remaining time may be associated with a higher priority than location reliability information that is deemed valid for a shorter remaining time.

[0089] According to an implementation, the target UE is configured with one or more priority criteria, e.g., which priority criteria are applied to determine the location reliability information. Based on the determined priority, the target UE can select a subset of PRS transmitters and / or a subset of measurements obtained from PRS reception from the subset of PRS transmitters. For example, if the target UE classifies PRS transmitters into low-priority PRS transmitters and high-priority PRS transmitters, it may evaluate only PRS received from high-priority PRS transmitters. Alternatively or additionally, the UE may report only measurements based on PRS reception from high-priority transmitters.

[0090] According to one or more implementations, the target UE is configured with the number of PRS transmitters to be selected. According to another implementation, the target UE establishes a ranking of the PRS transmitters based on their correspondence to a priority criterion. For example, the PRS transmitters can be ranked based on path loss, PRS transmitter speed, RSRP, RSSI, etc., and the N PRS transmitters exhibiting the highest priority can be selected. For example, if there are T PRS transmitters available and they are prioritized according to their speed, the target UE can select the N≦T PRS transmitters with the lowest speed. In at least one implementation, the target UE is configured with the number N.

[0091] According to one or more implementations, the target UE updates its determined priority when it detects updated information regarding the priority criteria of a PRS transmitter. For example, if the estimated path loss from a PRS transmitter changes from a previous value by more than a threshold, it may reevaluate the corresponding priority for the PRS transmitter. In another example, if the target UE receives information that a previously mobile PRS transmitter has become stationary, it may reevaluate the corresponding priority.

[0092] According to one or more implementations, the target UE reports (e.g., to the LMF and / or other computational units (e.g., RSUs)) only measurements from selected PRS transmitters to save reporting overhead. A configuration entity (e.g., the LMF) can set how many reports to include and / or criteria for selection (which may be positioning algorithm specific, for example), such as one or more of the priority criteria described above. Furthermore, the UE may determine the number of reports to be included, and header information associated with the information may indicate the number of reports.

[0093] According to one or more implementations, the target UE requests PRS transmissions from only selected PRS transmitters. The requests can be sent to the LMF and / or one or more selected PRS transmitters via PRS requests and / or PRS triggers in control messages, such as sidelink control information (SCI).

[0094] According to one or more implementations, the subset of PRS transmitters can be selected according to positioning accuracy parameters (e.g., accuracy requirements) for the positioning service. For example, for positioning IIoT devices, a very high position accuracy (e.g., less than 0.5 meters) can be indicated so that only PRS transmitters with very high reliability (e.g., very high priority) can be selected. In another example, positioning road vehicles may not have as strict an accuracy requirement (e.g., less than 1.5 meters) so that PRS transmitters with high or higher reliability (e.g., high priority) can be selected.

[0095] FIG. 6 illustrates an example block diagram 600 of a device 602 (e.g., apparatus) that supports location reliability information regarding device location, according to aspects of the present disclosure. The device 602 may be an example of a UE 104 described herein. The device 602 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 602 may include components for bidirectional communication, including components for transmitting and receiving communications, such as a processor 604, a memory 606, a transceiver 608, and an I / O controller 610. These components may communicate electrically or otherwise be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0096] The processor 604, the memory 606, the transceiver 608, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the disclosure as described herein. For example, the processor 604, the memory 606, the transceiver 608, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

[0097] In some implementations, the processor 604, the memory 606, the transceiver 608, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in this disclosure. In some implementations, the processor 604 and the memory 606 coupled to the processor 604 may be configured to perform one or more of the functions described herein (e.g., by the processor 604 executing instructions stored in the memory 606). In the context of the UE 104, for example, the transceiver 608 and the processor 604 coupled to the transceiver 608 are configured to cause the UE 104 to perform various operations and / or combinations thereof described.

[0098] For example, the processor 604 and / or the transceiver 608 may support wireless communication in the device 602 according to examples disclosed herein. For example, the processor 604 may be configured with and / or otherwise support a means for generating location reliability information, the location reliability information including an estimated indication of a location reliability state for the device, and transmitting the location reliability information.

[0099] Further, in some implementations, the location reliability information is or includes one or more determined by at least one of speed, accuracy, speed class, or accuracy class, the apparatus includes a device for which the location reliability information is generated, the processor is configured to transmit the location reliability information and a positioning reference signal, the location reliability information includes a message from a Location Management Function (LMF) entity, the apparatus includes a device other than the device for which the location reliability information is generated, the location reliability information includes an indication of the mobility of the device, the location reliability information includes an indication of location reliability with respect to multiple spatial dimensions, the location reliability information includes an indication of a validity time of the location reliability information, and the location reliability information includes an indication of a reliability value of the location reliability information relative to a defined threshold reliability.

[0100] The processor 604 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, the processor 604 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 604. The processor 604 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 606) to cause the device 602 to perform various functions of the present disclosure.

[0101] The memory 606 may include random access memory (RAM) and read-only memory (ROM). The memory 606 may store computer-readable, computer-executable code, including instructions that, when executed by the processor 604, cause the device 602 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 604, but may (e.g., when compiled or executed) cause a computer to perform the functions described herein. In some implementations, the memory 606 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.

[0102] The processor 604 of a device 602, such as a UE 104, may support wireless communication in accordance with examples disclosed herein. The processor 604 includes at least one controller coupled to at least one memory and is configured or operable to cause the processor to perform various operations described herein, such as with reference to the UE 104.

[0103] The I / O controller 610 may manage input and output signals for the device 602. The I / O controller 610 may also manage peripherals not integrated into the device M02. In some implementations, the I / O controller 610 may represent a physical connection or port to an external peripheral. In some implementations, the I / O controller 610 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I / O controller 610 may be implemented as part of a processor, such as the processor M08. In some implementations, a user may interact with the device 602 through the I / O controller 610 or through hardware components controlled by the I / O controller 610.

[0104] In some implementations, the device 602 may include a single antenna 612. However, in some other implementations, the device 602 may have two or more antennas 612 (e.g., multiple antennas), including multiple antenna panels or antenna arrays, which may be capable of simultaneously transmitting or receiving multiple wireless transmissions. The transceiver 608 may communicate bidirectionally via one or more antennas 612, a wired link, or a wireless link, as described herein. For example, the transceiver 608 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 608 may also include a modem for modulating packets to provide the modulated packets to the one or more antennas 612 for transmission and for demodulating packets received from the one or more antennas 612.

[0105] 7 illustrates an example block diagram 700 of a device 702 (e.g., apparatus) that supports location reliability information regarding device location, according to aspects of the present disclosure. The device 702 may be an example of a network entity 102 described herein. The device 702 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 702 may include components for bidirectional communication, including components for transmitting and receiving communications, such as a processor 704, a memory 706, a transceiver 708, and an I / O controller 710. These components may communicate electrically or otherwise be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0106] The processor 704, the memory 706, the transceiver 708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the disclosure as described herein. For example, the processor 704, the memory 706, the transceiver 708, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

[0107] In some implementations, the processor 704, the memory 706, the transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in this disclosure. In some implementations, the processor 704 and the memory 706 coupled to the processor 704 may be configured to perform one or more of the functions described herein (e.g., by the processor 704 executing instructions stored in the memory 706). In the context of the network entity 102, for example, the transceiver 708 and the processor 704 coupled to the transceiver 708 are configured to cause the network entity 102 to perform various operations and / or combinations thereof described.

[0108] For example, the processor 704 and / or the transceiver 708 may support wireless communication in the device 702 according to examples disclosed herein. For example, the processor 704 may be configured with or otherwise support a means for receiving location reliability information, where the location reliability information includes an estimated indication of a location confidence state for a first device, and estimating a location of a second device based at least in part on the location reliability information for the first device.

[0109] Further, in some implementations, the location reliability information includes one or more of speed, accuracy, speed class, or accuracy class, the apparatus includes a second device whose location is estimated, the processor is configured to transmit the location reliability information and the positioning reference signal, the location reliability information includes a message from a Location Management Function (LMF) entity, the apparatus includes a device other than the device for which the location reliability information is generated, the location reliability information includes an indication of the mobility of the device, the location reliability information includes an indication of location reliability with respect to multiple spatial dimensions, the location reliability information includes an indication of a validity time of the location reliability information, and the location reliability information includes an indication of a reliability value of the location reliability information relative to a defined threshold reliability.

[0110] The processor 704 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, the processor 704 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 704. The processor 704 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 706) to cause the device 702 to perform various functions of the present disclosure.

[0111] The memory 706 may include random access memory (RAM) and read-only memory (ROM). The memory 706 may store computer-readable, computer-executable code, including instructions that, when executed by the processor 704, cause the device 702 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 704, but may (e.g., when compiled or executed) cause a computer to perform the functions described herein. In some implementations, the memory 706 may include a basic I / O system (BIOS), which may control basic hardware and software operations, such as interaction with peripheral components or devices, among other things.

[0112] The I / O controller 710 may manage input and output signals for the device 702. The I / O controller 710 may also manage peripherals not integrated into the device M02. In some implementations, the I / O controller 710 may represent a physical connection or port to an external peripheral. In some implementations, the I / O controller 710 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I / O controller 710 may be implemented as part of a processor, such as the processor M06. In some implementations, a user may interact with the device 702 through the I / O controller 710 or through hardware components controlled by the I / O controller 710.

[0113] In some implementations, the device 702 may include a single antenna 712. However, in some other implementations, the device 702 may have two or more antennas 712 (e.g., multiple antennas), including multiple antenna panels or antenna arrays, which may be capable of simultaneously transmitting or receiving multiple wireless transmissions. The transceiver 708 may communicate bidirectionally via one or more antennas 712, a wired link, or a wireless link, as described herein. For example, the transceiver 708 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 708 may also include a modem for modulating packets to provide the modulated packets to the one or more antennas 712 for transmission and for demodulating packets received from the one or more antennas 712.

[0114] 8 illustrates a flowchart of a method 800 for supporting location reliability information regarding a device location according to an aspect of the present disclosure. The operations of method 800 may be implemented by a device or components thereof as described herein. For example, the operations of method 800 may be performed by a UE 104 as described with reference to FIGS. 1 through 7. In some embodiments, the device may execute a set of instructions that control functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform aspects of the described functions using dedicated hardware.

[0115] At 802, the method includes generating, at an apparatus, location trustworthiness information, where the location trustworthiness information may include an estimated indication of a location trustworthiness state for the device. The operations of 802 may be performed according to examples described herein. In some embodiments, aspects of the operations of 802 may be performed by a device described with reference to FIG.

[0116] At 804, the method may include transmitting location reliability information. The operations of 804 may be performed according to examples described herein. In some embodiments, aspects of the operations of 804 may be performed by a device described with reference to FIG.

[0117] 9 illustrates a flowchart of a method 900 for supporting location reliability information regarding a device location according to an aspect of the present disclosure. The operations of method 900 may be implemented by a device or components thereof as described herein. For example, the operations of method 900 may be performed by network entity 102 as described with reference to FIGS. 1 through 7. In some implementations, the device may execute a set of instructions that control functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform aspects of the described functions using dedicated hardware.

[0118] At 902, the method may include receiving, at an apparatus, location reliability information, the location reliability information including an estimated indication of a location reliability state for a first device. The operations of 902 may be performed according to examples described herein. In some implementations, aspects of the operations of 902 may be performed by a device described with reference to FIG.

[0119] At 904, the method may include estimating a location of the second device based at least in part on location reliability information about the first device. The operations of 904 may be performed according to examples described herein. In some implementations, aspects of the operations of 904 may be performed by a device described with reference to FIG.

[0120] 10 illustrates a flowchart of a method 1000 for supporting location reliability information for a device location according to an aspect of the present disclosure. The operations of method 1000 may be implemented by a device or components thereof as described herein. For example, the operations of method 1000 may be performed by a UE 104 as described with reference to FIGS. 1 through 7. In some implementations, the device may execute a set of instructions that control functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform aspects of the described functions using dedicated hardware.

[0121] At 1002, a method may include receiving, at an apparatus, one or more positioning reference signals (PRSs) from a set of one or more PRS transmitters. The operations of 1002 may be performed according to examples described herein. In some implementations, aspects of the operations of 1002 may be performed by a device described with reference to FIG.

[0122] At 1004, the method may include selecting a subset of the set of one or more PRS transmitters based at least in part on a positioning priority for the set of one or more PRS transmitters. The operations of 1004 may be performed according to examples described herein. In some implementations, aspects of the operations of 1004 may be performed by a device described with reference to FIG.

[0123] At 1006, the method may include determining one or more position measurements based at least in part on a subset of the set of one or more PRS transmitters. The operations of 1006 may be performed according to examples described herein. In some implementations, aspects of the operations of 1006 may be performed by a device described with reference to FIG.

[0124] 11 shows a flowchart of a method 1100 for supporting location reliability information for a device location according to an aspect of the present disclosure. The operations of method 1100 may be implemented by a device or components thereof as described herein. For example, the operations of method 1100 may be performed by network entity 102 as described with reference to FIGS. 1 through 7. In some implementations, the device may execute a set of instructions that control functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform aspects of the described functions using dedicated hardware.

[0125] At 1102, the method may include generating, at the apparatus, a positioning indication including positioning priority information for selecting a PRS transmitter. The operations of 1102 may be performed according to examples described herein. In some implementations, aspects of the operations of 1102 may be performed by the device described with reference to FIG.

[0126] At 1104, the method may include transmitting a positioning indication. The operations of 1104 may be performed according to examples described herein. In some implementations, aspects of the operations of 1104 may be performed by a device described with reference to FIG.

[0127] 12 illustrates a flowchart of a method 1200 for supporting location reliability information regarding a device location according to an aspect of the present disclosure. The operations of method 1200 may be implemented by a device or components thereof as described herein. For example, the operations of method 1200 may be performed by network entity 102 as described with reference to FIGS. 1 through 7. In some implementations, the device may execute a set of instructions that control functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform aspects of the described functions using dedicated hardware.

[0128] At 1202, the method may include transmitting a positioning instruction to the second device. The operations of 1202 may be performed according to examples described herein. In some implementations, aspects of the operations of 1202 may be performed by a device described with reference to FIG.

[0129] At 1204, the method may include receiving a position measurement report from the second device, the position measurement report including at least one position measurement. The operations of 1204 may be performed according to examples described herein. In some implementations, aspects of the operations of 1204 may be performed by a device described with reference to FIG. 1.

[0130] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible. Additionally, aspects from two or more methods may be combined.

[0131] The various example blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration).

[0132] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented in different physical locations.

[0133] Computer-readable media include both non-transitory computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or processor.

[0134] Any connection may be properly termed a computer-readable medium. For example, if software is transmitted from a website, a server, or other remote source using coaxial cable, fiber optic cable, twisted pair wire, a digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair wire, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disk and disc include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically and discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0135] As used herein, including within the claims, "or" when used in a list of items (e.g., a list of items preceded by phrases such as "at least one of," "one or more of," or "one or both of") indicates an inclusive list, such as, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be construed similarly to the phrase "based at least in part on." Additionally, as used herein, including within the claims, a "set" may include one or more elements.

[0136] The terms "transmit," "receive," or "communicate," when referring to a network entity, may refer to any part of the network entity of the RAN (e.g., a base station, a CU, a DU, a RU) communicating with another device (e.g., directly or through one or more network entities).

[0137] The description set forth herein with reference to the accompanying drawings describes exemplary configurations and does not represent every example that may be implemented or every example that falls within the scope of the claims. As used herein, the term "example" means "serving as an example, instance, or illustration" and not "preferred or advantageous over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0138] The description herein is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. [Explanation of symbols]

[0139] 100 Wireless Communication System 102 Network Entities 104UE 106 Core Network 108 Packet Data Network 110 Communication Links 112 Geographic Coverage Areas 114 Communication Links 116 backhaul links 118 Application Server 120 Location Reliability Information 122 Position determination 124 Location notification 200 systems 202 Infrastructure to Vehicle Communication 204 Infrastructure to Infrastructure Communication 206 Vehicle-to-Vehicle Communications 300 System 400 System 600 Block Diagram 602 devices 604 processor 606 memory 608 Transceiver 610 I / O Controller 612 Antenna 700 Block Diagram 702 devices 704 processor 706 memory 708 Transceiver 710 I / O Controller 712 Antenna

Claims

1. A user equipment (UE) for wireless communications, comprising: at least one memory; coupled to the at least one memory, to the UE; generating location authority information, the location authority information including an estimated indication of a trust state of a location for the device; Transmitting location reliability information; at least one processor configured to cause UE equipped with.

2. 10. The UE of claim 1, wherein the location reliability information is one or more determined by at least one of speed, accuracy, speed class, or accuracy class, or includes at least one of speed, accuracy, speed class, or accuracy class.

3. The UE of claim 1 , wherein the UE comprises a device from which the location reliability information is generated.

4. The UE of claim 1 , wherein the at least one processor is configured to cause the UE to transmit location reliability information and a positioning reference signal.

5. The UE of claim 1 , wherein the location reliability information includes a message from a Location Management Function (LMF) entity.

6. The UE of claim 1 , wherein the UE includes a device other than the device for which the location reliability information is generated.

7. The UE of claim 1 , wherein the location reliability information includes an indication of device mobility.

8. The UE of claim 1 , wherein the location reliability information includes an indication of location reliability with respect to multiple spatial dimensions.

9. The UE of claim 1 , wherein the location reliability information includes a validity time indication for the location reliability information.

10. The UE of claim 1 , wherein the location reliability information includes an indication of a reliability value of the location reliability information relative to a defined threshold reliability.

11. 1. A processor for wireless communications, comprising: coupled to at least one memory, and configured to: generating location authority information, the location authority information including an estimated indication of a trust state of a location for the device; Transmitting location reliability information; At least one controller configured to A processor comprising:

12. 12. The processor of claim 11, wherein the location reliability information is one or more determined by or includes at least one of speed, accuracy, speed class, or accuracy class.

13. The processor of claim 11 , wherein the device comprises a device from which the location authority information is generated.

14. The processor of claim 11 , wherein the at least one controller is configured to cause the processor to transmit the location reliability information and a positioning reference signal.

15. 12. The processor of claim 11, wherein the location reliability information comprises a message from a Location Management Function (LMF) entity.

16. The processor of claim 11 , wherein the devices include devices other than the device for which the location authority information is generated.

17. The processor of claim 11 , wherein the location reliability information includes an indication of mobility of the device.

18. The processor of claim 11 , wherein the location reliability information includes an indication of location reliability with respect to multiple spatial dimensions.

19. generating location authority information in the apparatus, the location authority information including an estimated indication of a location confidence state for the device; transmitting the location reliability information; A method comprising:

20. 1. A base station for wireless communications, comprising: at least one memory; coupled to the at least one memory, to the base station; receiving location reliability information, the location reliability information including an estimated indication of a location confidence state for the first device; estimating a location of a second device based at least in part on the location reliability information for the first device; and at least one processor configured to cause A base station comprising:

Images