Positioning accuracy improvement through crowdsourcing

Abstract

Techniques for wireless communication are disclosed. In an aspect, a first wireless device may receive a first message from a second wireless device, the first message including an advertised location of the second wireless device (910). The wireless device may determine an estimated location of the second wireless device (920). The wireless device may detect a difference between the advertised location of the second wireless device and the estimated location of the second wireless device (930). The wireless device may transmit a second message to at least one other wireless device indicating that there is a difference between the advertised location of the second wireless device and the estimated location of the second wireless device (940).

Description

Technical Field

[0001] Aspects of the present disclosure generally relate to wireless positioning. Background Art

[0002] Wireless communication systems have evolved through many generations, including first-generation analog wireless telephone services (1G), second-generation (2G) digital wireless telephone services (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data, Internet-capable wireless services, and fourth-generation (4G) services (e.g., Long-Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular systems and Personal Communication Services (PCS) systems. Examples of known cellular systems include the cellular analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), etc.

[0003] The fifth-generation (5G) wireless standard, known as New Radio (NR), enables higher data transfer speeds, a greater number of connections, better coverage, and 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.

[0004] Furthermore, leveraging the increased data rate and reduced latency of 5G, Vehicle-to-Everything (V2X) communication technologies are being implemented to support autonomous driving applications, such as wireless communication between vehicles, between vehicles and roadside infrastructure, between vehicles and pedestrians, etc. Summary of the Invention

[0005] A simplified summary related to one or more aspects disclosed herein is presented below. Accordingly, the following summary should not be considered an exhaustive survey of all contemplated aspects, nor should it be considered to identify key or critical elements related to all contemplated aspects or to delineate the scope associated with any particular aspect. Thus, the sole purpose of the following summary is to present certain concepts related to one or more aspects involving the mechanisms disclosed herein in a simplified form prior to the detailed description presented below.

[0006] In one aspect, a method of wireless communication performed by a first wireless device includes: receiving a first message from a second wireless device, the first message including an advertised location of the second wireless device; determining an estimated location of the second wireless device; detecting a difference between the advertised location of the second wireless device and the estimated location of the second wireless device; and transmitting a second message to at least one other wireless device, the second message indicating the existence of a difference between the advertised location of the second wireless device and the estimated location of the second wireless device.

[0007] In one aspect, a method of wireless communication performed by a first wireless device includes: transmitting a first message, the first message including an advertised location of the first wireless device; and receiving a second message from a second wireless device, the second message indicating the existence of a difference between the advertised location of the first wireless device and an estimated location of the first wireless device.

[0008] In one aspect, a method of wireless communication performed by a network entity includes: monitoring a network for messages related to positioning; and detecting positioning misbehavior based on the content of the messages related to positioning.

[0009] In one aspect, a method of wireless communication performed by a wireless device includes: determining a set of weights to be applied to positioning information sources; and sending the set of weights to one or more other wireless devices.

[0010] In one aspect, a first wireless device includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: receive a first message from a second wireless device via the at least one transceiver, the first message including an advertised location of the second wireless device; determine an estimated location of the second wireless device; detect a difference between the advertised location of the second wireless device and the estimated location of the second wireless device; and transmit a second message to at least one other wireless device via the at least one transceiver, the second message indicating the existence of a difference between the advertised location of the second wireless device and the estimated location of the second wireless device.

[0011] In one aspect, a first wireless device includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: transmit a first message via the at least one transceiver, the first message including an advertised location of the first wireless device; and receive a second message from a second wireless device via the at least one transceiver, the second message indicating the existence of a difference between the advertised location of the first wireless device and an estimated location of the first wireless device.

[0012] In one aspect, a network entity includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: monitor the network for messages related to positioning; and detect positioning misbehavior based on the content of the messages related to positioning.

[0013] In one aspect, a wireless device includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: determine a set of weights to be applied to a positioning information source; and send the set of weights to one or more other wireless devices via the at least one transceiver.

[0014] Based on the drawings and the detailed description, other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The drawings are presented to assist in describing the various aspects of the present disclosure, and the drawings are provided for illustration only and not to limit the aspects.

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

[0017] Figure 2A 、 Figure 2B and Figure 2C An example wireless network structure in accordance with aspects of the present disclosure is illustrated.

[0018] Figure 3A 、 Figure 3B and Figure 3C are simplified block diagrams of several example aspects of components that can be employed in a user equipment (UE), a base station, and a network entity, respectively, and are configured to support communication as taught herein.

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

[0020] Figure 5 is a diagram illustrating various downlink channels within an example downlink time slot in accordance with aspects of the present disclosure.

[0021] Figure 6 is a diagram illustrating various uplink channels within an example uplink time slot in accordance with aspects of the present disclosure.

[0022] Figure 7 An example of a wireless communication system supporting unicast sidelink establishment in accordance with aspects of the present disclosure is illustrated.

[0023] Figure 8 Illustrates possible interactions between wireless devices in accordance with aspects of the present disclosure.

[0024] Figure 9 Is a flowchart of an example process performed by a wireless device in accordance with aspects of the present disclosure associated with improving location accuracy through crowdsourcing.

[0025] Figure 10 Is a flowchart of an example process performed by a wireless device in accordance with aspects of the present disclosure associated with improving location accuracy through crowdsourcing.

[0026] Figure 11 Is a flowchart of an example process performed by a network entity in accordance with aspects of the present disclosure associated with improving location accuracy through crowdsourcing.

[0027] Figure 12 Is a flowchart of an example process performed by a wireless device in accordance with aspects of the present disclosure associated with improving location accuracy through crowdsourcing. Detailed Description

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

[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 superior or better than other aspects. Similarly, the term "aspects of the present disclosure" does not require that all aspects of the present disclosure include the discussed features, advantages, or modes of operation.

[0030] Those skilled in the art will appreciate that any of a variety of different technologies 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 referred to throughout the following description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof, depending in part on the particular 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 sequences of actions to be performed by elements of, for example, a computing device. It will be recognized that the various actions described herein can be performed by specific circuitry (e.g., an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of both. Additionally, the sequences of actions described herein can be regarded as fully embodied within any form of non-transitory computer-readable storage medium having stored therein a corresponding set of computer instructions that, when executed, cause or direct a relevant associated processor of the device to perform the functionality described herein. Accordingly, the various aspects of the present disclosure can be embodied in many different forms, all of which are contemplated to be within the scope of the claimed subject matter. Additionally, for each of the aspects described herein, any such aspect's corresponding form can be described herein as, for example, "logic configured to perform the described actions."

[0032] As used herein, the terms "user equipment" (UE), "vehicle UE" (V-UE), "pedestrian UE" (P-UE), and "base station" are not intended to be dedicated to or otherwise limited to any particular radio access technology (RAT) unless otherwise specified. In general, a UE can be any wireless communication device that a user uses to communicate over a wireless communication network (e.g., an in-vehicle computer, a vehicle navigation device, a mobile phone, a router, a tablet computer, a laptop computer, an asset tracking device, a wearable device (e.g., a smartwatch, 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 "mobile device," "access terminal" or "AT," "client device," "wireless device," "subscriber device," "subscriber terminal," "subscriber station," "user terminal" or "UT," "mobile terminal," "mobile station," or variations thereof.

[0033] A V-UE is a type of UE and can be any vehicle-mounted wireless communication device, such as a navigation system, an alarm system, a head-up display (HUD), an on-board computer, an in-vehicle infotainment system, an autonomous driving system (ADS), an advanced driver assistance system (ADAS), etc. Alternatively, the V-UE can be a portable wireless communication device (e.g., a cellular phone, a tablet computer, etc.) carried by a driver of a vehicle or an occupant in the vehicle. The term "V-UE" can refer to the vehicle-mounted wireless communication device or the vehicle itself, depending on the context. A P-UE is a type of UE and can be a portable wireless communication device carried by a pedestrian (i.e., a user who is not driving or riding in a vehicle). Generally speaking, a UE can communicate with a core network via a RAN, and through the core network, the UE can connect to an external network such as the Internet and to other UEs. Of course, other mechanisms for a UE to connect to the core network and / or the Internet are possible, such as via a wired access network, a wireless local area network (WLAN) network (e.g., based on Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc.).

[0034] A base station can operate according to one of several RATs according to the network in which the base station is deployed to communicate with a UE, and alternatively can 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. The base station can mainly be used to support the wireless access of a UE, including supporting the data, voice, and / or signaling connections of the supported UE. In some systems, the base station can only provide edge node signaling functions, while in other systems, the base station can provide additional control and / or network management functions. The communication link by which a UE can transmit signals to the 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 the base station can transmit signals to the UE is referred to as a downlink (DL) or a 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) can refer to a UL / reverse or a DL / forward traffic channel.

[0035] The term "base station" can refer to a single physical transmit-receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, in the case where the term "base station" refers to a single physical TRP, the physical TRP can be the antenna of the base station corresponding to a cell (or several cell sectors) of the base station. In the case where the term "base station" refers to multiple co-located physical TRPs, the physical TRPs can be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or when beamforming is employed at the base station). In the case where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRPs can 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 TRPs can be the serving base station that receives measurement reports from the UE and an adjacent base station whose reference radio frequency (RF) signal the UE is measuring. Since, as used herein, a TRP is the point by which a base station transmits and receives wireless signals, a reference to transmitting from or receiving at a base station should be understood to refer to a particular TRP of the base station.

[0036] In some specific implementations that support 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 instead, can send a reference RF signal to the UE for measurement by the UE, and / or can receive and measure signals sent by the UE. Such a base station can be referred to as a positioning beacon (e.g., in the case of sending an RF signal to the UE) and / or as a positioning measurement unit (e.g., in the case of receiving and measuring an RF signal from the UE).

[0037] An "RF signal" includes an electromagnetic wave of a given frequency that transmits information through the space between a transmitter and a receiver. As used herein, a transmitter can send a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through a multipath channel, a receiver can receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and the receiver can be referred to as a "multipath" RF signal. As used herein, when it is clear from the context that the term "signal" refers to a wireless signal or an RF signal, the RF signal can also be referred to as a "wireless signal" or simply as a "signal".

[0038] Figure 1An example wireless communication system 100 in accordance with aspects of the present disclosure is illustrated. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled "BS") and various UEs 104. The base stations 102 may include macro cell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macro cell base stations 102 may include eNBs and / or ng-eNBs (where the wireless communication system 100 corresponds to an LTE network) or gNBs (where the wireless communication system 100 corresponds to an NR network) or a combination of both, and the small cell base stations may include femto cells, pico cells, micro cells, etc.

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

[0040] In addition to other functions, the base stations 102 may perform functions related to one or more of the following: transferring 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., via the EPC / 5GC) on the backhaul link 134, which may be wired or wireless.

[0041] The base station 102 can communicate wirelessly with the UE 104. Each base station in the base station 102 can provide communication coverage for the corresponding geographical coverage area 110. In one aspect, one or more cells can be supported by the base station 102 in each geographical coverage area 110. A "cell" is a logical communication entity for communicating with a base station (e.g., via a certain frequency resource, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.), and can be associated with an identifier for distinguishing cells operating via the same or different carrier frequencies (e.g., physical cell identifier (PCI), enhanced cell identifier (ECI), virtual cell identifier (VCI), cell global identifier (CGI), etc.). In some cases, different cells can be configured according to different protocol types that can provide access for different types of UEs (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types). Since a cell is supported by a specific base station, depending on the context, the term "cell" can refer to either or both of the logical communication entity and the base station that supports it. In some cases, the term "cell" can also refer to the geographical coverage area (e.g., sector) of a base station, as long as the carrier frequency can be detected and used for communication within a certain part of the geographical coverage area 110.

[0042] Although the geographical coverage areas 110 of adjacent macro cell base stations 102 can partially overlap (e.g., in a handover area), some areas in the geographical coverage area 110 can substantially overlap with a larger geographical coverage area 110. For example, a small cell base station 102' (marked as "SC" for "small cell") can have a geographical coverage area 110' that substantially overlaps with the geographical coverage area 110 of one or more macro cell base stations 102. A network including both small cell base stations and macro cell base stations can be referred to as a heterogeneous network. The heterogeneous network can also include a home eNB (HeNB), which can provide services to a restricted group called a closed subscriber group (CSG).

[0043] The communication link 120 between the base station 102 and the UE 104 can include an uplink (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 can use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 can be through one or more carrier frequencies. The allocation of carriers can be asymmetric for the downlink and the uplink (e.g., more or fewer carriers can be allocated to the downlink compared to the uplink).

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

[0045] The small cell base station 102' may operate in licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5 GHz unlicensed spectrum as that used by the WLAN AP 150. The small cell base station 102' adopting LTE / 5G in an unlicensed spectrum may enhance the coverage of the access network and / or increase the capacity of the access network. NR in an unlicensed spectrum may be referred to as NR-U. LTE in an unlicensed spectrum may be referred to as LTE-U, licensed-assisted access (LAA), or MulteFire.

[0046] The wireless communication system 100 may also include a mmW base station 180 that may operate at millimeter wave (mmW) frequencies and / or near-mmW frequencies to communicate with a UE 182. Extremely high frequency (EHF) is a part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz, with wavelengths between 1 millimeter and 10 millimeters. The radio waves in this frequency band may be referred to as millimeter waves. Near-mmW may extend down to a frequency of 3 GHz, with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using the mmW / near-mmW radio frequency bands have high path loss and relatively short distances. The mmW base station 180 and the UE 182 may utilize beamforming (transmitting and / or receiving) on a mmW communication link 184 to compensate for the extremely high path loss and short distances. Additionally, it should be understood that in an alternative configuration, one or more of the 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.

[0047] Transmit beamforming is a technique used to focus RF signals in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal omnidirectionally, i.e., in all directions. 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 and stronger RF signal (in terms of data rate) to the receiving device. To change the directivity of the RF signal during transmission, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters that broadcast the RF signal. For example, the network node can use an array of antennas (referred to as a "phased array" or "antenna array") that forms an RF beam that can be "manipulated" to point in different directions without actually moving the antennas. Specifically, the RF currents from the transmitters are fed to the individual antennas with the correct phase relationships such that the radio waves from the individual antennas add up in the desired direction to increase radiation, while canceling in the undesired directions to suppress radiation.

[0048] Transmit beams can be quasi - co - located, which means they appear to have the same parameters to the receiver (e.g., a UE), regardless of whether the transmitting antennas of the network node are 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 of a second reference RF signal on a second beam can be derived based on information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is of QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is of QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is of QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is of QCL type D, the receiver can use the source reference RF signal to estimate the spatial reception parameters of the second reference RF signal transmitted on the same channel.

[0049] In receive beamforming, the receiver uses receive beams to amplify the RF signals detected on a given channel. For example, the receiver can increase the gain setting of the antenna array in a specific direction and / or adjust the phase setting of the antenna array in a specific direction to amplify the RF signals received from that direction (e.g., increase its gain level). Thus, when the 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 gains in other directions, or the beam gain in that direction is the highest compared to the beam gains of all other receive beams available to the receiver in that direction. This results in a stronger received signal strength for the RF signals received from that direction (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.).

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

[0051] 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 a UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam for receiving downlink reference signals. 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, the uplink beam is an uplink receive beam, while if the UE is forming an uplink beam, the uplink beam is an uplink transmit beam.

[0052] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as Frequency Range Designation FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band. Regarding FR2, a similar naming issue sometimes occurs, which is typically (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 to 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0053] The 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.125 GHz to 24.25 GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to the mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as Frequency Range Designation FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher bands falls within the EHF band.

[0054] Taking the above aspects into account, unless otherwise specifically stated, it should be understood that if terms such as "sub-6 GHz" are used in this article, they can generally represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if terms such as "millimeter wave" are used in this article, they can generally represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or can be within the EHF band.

[0055] 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, where the UE 104 / 182 performs the initial radio resource control (RRC) connection establishment process or initiates the RRC connection re-establishment process in the cell. 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). The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that 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 can 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 can have different downlink primary carriers. The same holds for the primary uplink 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. Since a "serving cell" (whether PCell or SCell) corresponds to the carrier frequency / component carrier through which a certain base station communicates, terms such as "cell", "serving cell", "component carrier", "carrier frequency", etc. may be used interchangeably.

[0056] For example, still referring to Figure 1 , one of the frequencies used by the macro cell base station 102 can be the anchor carrier (or "PCell"), and the other frequencies used by the macro cell base station 102 and / or the mmW base station 180 can be secondary carriers ("SCells"). The simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, compared to the data rate obtained with a single 20 MHz carrier, two 20 MHz aggregated carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz).

[0057] In Figure 1 's example, the illustrated UE (for simplicity, in Figure 1Any UE shown as a single UE 104 in the figure can receive signals 124 from one or more space vehicles (SVs) 112 in Earth orbit (e.g., satellites). In one aspect, the SV 112 can be part of a satellite positioning system where the UE 104 can use it as an independent source of position information. A satellite positioning system generally includes a system of transmitters (e.g., SV 112) that are positioned such that a receiver (e.g., UE 104) can determine its position on or above the Earth at least in part based on positioning signals received from the transmitters (e.g., signal 124). Such transmitters typically send signals marked with a repeating pseudo-random noise (PN) code with a set number of chips. Although typically located in the SV 112, the transmitters can sometimes be located on a ground-based control station, a base station 102, and / or other UEs 104. The UE 104 can include one or more dedicated receivers that are specifically designed to receive the signal 124 in order to derive geographical location information from the SV 112.

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

[0059] In one aspect, the SV 112 can additionally or alternatively be part of one or more non-terrestrial networks (NTN). In an NTN, the 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 elements in a 5G network, such as a modified base station 102 (without a ground antenna) or a network node in the 5GC. This element then provides access to other elements in the 5G network and ultimately provides access to entities external to the 5G network (such as Internet web servers and other user devices). Thus, instead of or in addition to communication signals from the ground base station 102, the UE 104 can receive communication signals (e.g., signal 124) from the SV 112.

[0060] In particular, leveraging the increased data rate and reduced latency of NR, vehicle-to-everything (V2X) communication technologies are being implemented to support intelligent transportation system (ITS) applications, such as wireless communication between vehicles (vehicle-to-vehicle (V2V)), between vehicles and roadside infrastructure (vehicle-to-infrastructure (V2I)), and between vehicles and pedestrians (vehicle-to-pedestrian (V2P)). The goal is to enable vehicles to sense their surrounding environment and communicate this information to other vehicles, infrastructure, and personal mobile devices. Such vehicle communication will achieve safety, mobility, and environmental improvements not offered by current technologies. Once fully implemented, the technology is expected to reduce unimpaired vehicle collisions by 80%.

[0061] Still referring to Figure 1 , the wireless communication system 100 may include a plurality of V-UEs 160, which may communicate with the base station 102 on the communication link 120 using the Uu interface (i.e., the air interface between the UE and the base station). The V-UEs 160 may also communicate directly with each other on the wireless sidelink 162, communicate with the roadside unit (RSU) 164 (roadside access point) on the wireless sidelink 166, or communicate with the UE 104 with sidelink capabilities on the wireless sidelink 168 using the PC5 interface (i.e., the air interface between UEs with sidelink capabilities). The wireless sidelink (or simply referred to as "sidelink") is an adaptation of the core cellular network (e.g., LTE, NR) standard that allows direct communication between two or more UEs without communicating through a base station. Sidelink communication can be unicast or multicast and can be used for device-to-device (D2D) media sharing, V2V communication, V2X communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, etc.), emergency rescue applications, etc. One or more of the V-UEs 160 in a group of V-UEs 160 that utilize sidelink communication may be within the geographical coverage area 110 of the base station 102. Other V-UEs 160 in such a group may be outside the geographical coverage area 110 of the base station 102 or may not be able to receive transmissions from the base station 102 for other reasons. In some cases, the groups of V-UEs 160 that communicate via sidelink communication may utilize a one-to-many (1:M) system, where each V-UE 160 transmits to each other V-UE 160 in the group. In some cases, the base station 102 facilitates the scheduling of resources for sidelink communication. In other cases, sidelink communication is performed between the V-UEs 160 without involving the base station 102.

[0062] In one aspect, the sidelinks 162, 166, 168 may operate over a wireless communication medium of interest, which may be shared with other wireless communications between other vehicles and / or infrastructure access points and other RATs. The "medium" may include one or more time, frequency, and / or spatial communication resources associated with wireless communication between one or more transmitter / receiver pairs (e.g., covering one or more channels across one or more carriers).

[0063] In one aspect, the sidelinks 162, 166, 168 may be cV2X links. First-generation cV2X has been standardized in LTE, and the next generation is expected to be defined in NR. cV2X is a cellular technology that also enables device-to-device communication. In the United States and Europe, cV2X is expected to operate in the licensed ITS band below 6 GHz. Other bands may be allocated in other countries. Thus, as a specific example, the medium of interest utilized by the sidelinks 162, 166, 168 may correspond to at least a portion of the licensed ITS band below 6 GHz. However, the present disclosure is not limited to this band or cellular technology.

[0064] In one aspect, the sidelinks 162, 166, 168 may be dedicated short-range communication (DSRC) links. DSRC is a unidirectional or bidirectional short-range to medium-range wireless communication protocol that uses the Wireless Access in Vehicular Environment (WAVE) protocol (also known as IEEE 802.11p) for V2V, V2I, and V2P communications. IEEE 802.11p is an approved modification to the IEEE 802.11 standard and operates in the licensed ITS band at 5.9 GHz (5.85 GHz - 5.925 GHz) in the United States. In Europe, IEEE 802.11p operates in the ITS G5A band (5.875 GHz - 5.905 MHz). Other bands may be allocated in other countries. The V2V communication described above occurs over a secure channel, which is typically a 10 MHz channel dedicated for security purposes in the United States. The remainder of the DSRC band (total bandwidth is 75 MHz) is intended for other services of interest to drivers, such as road rules, tolling, parking automation, etc. Thus, as a specific example, the medium of interest utilized by the sidelinks 162, 166, 168 may correspond to at least a portion of the licensed ITS band at 5.9 GHz.

[0065] Alternatively, the medium of interest may correspond to at least a portion of an unlicensed band shared among various RATs. Although different licensed bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), these systems (especially those employing small cell access points) have recently extended their operation into unlicensed bands such as the unlicensed National Information Infrastructure (U-NII) bands used by wireless local area network (WLAN) technologies (most notably the IEEE 802.11x WLAN technologies commonly referred to as “Wi-Fi”). Example systems of this type include different variants of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and the like.

[0066] Communication between V-UEs 160 is referred to as V2V communication, communication between a V-UE 160 and one or more RSUs 164 is referred to as V2I communication, and communication between a V-UE 160 and one or more UEs 104 (where these UEs 104 are P-UEs) is referred to as V2P communication. V2V communication between V-UEs 160 may include, for example, information regarding the location, speed, acceleration, heading, and other vehicle data of these V-UEs 160. V2I information received at a V-UE 160 from one or more RSUs 164 may include, for example, road rules, parking automation information, and the like. V2P communication between a V-UE 160 and a UE 104 may include information regarding, for example, the location, speed, acceleration, and heading of the V-UE 160 and the location, speed (e.g., in the case where the UE 104 is carried by a bicycling user), and heading of the UE 104.

[0067] Note that although Figure 1 only two of the UEs are illustrated as V-UEs (V-UE 160), any of the illustrated UEs (e.g., UEs 104, 152, 182, 190) may be a V-UE. Additionally, although only these V-UEs 160 and a single UE 104 have been illustrated as being connected via a sidelink, Figure 1Any of the illustrated UEs, whether a V-UE, P-UE, etc., may be capable of performing sidelink communication. Additionally, although only UE 182 is described as being capable of beamforming, any of the illustrated UEs (including V-UE 160) may be capable of beamforming. In the case where V-UEs 160 are capable of beamforming, they may beamform towards each other (i.e., towards other V-UEs 160), towards RSU 164, towards other UEs (e.g., UEs 104, 152, 182, 190), etc. Thus, in some cases, V-UEs 160 may utilize beamforming on sidelinks 162, 166, and 168.

[0068] Wireless communication system 100 may also include one or more UEs (such as UE 190) indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. In Figure 1 the example, UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., UE 190 may indirectly obtain cellular connectivity through this D2D P2P link), and has a D2D P2P link 194 with WLAN STA 152 connected to WLAN AP 150 (UE 190 may indirectly obtain WLAN-based Internet connectivity through this D2D P2P link). In one example, D2D P2P links 192 and 194 may be supported by any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth ® etc. As another example, D2D P2P links 192 and 194 may be sidelinks, as described above with reference to sidelinks 162, 166, and 168.

[0069] Figure 2AAn example wireless network structure 200 is illustrated. For example, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be functionally considered as a control plane (C-plane) function 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane (U-plane) function 212 (e.g., UE gateway function, access to data networks, IP routing, etc.), which cooperate to form the 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. Additionally, the ng-eNB 224 can communicate directly with the gNB 222 via the backhaul connection 223. In some configurations, the Next Generation RAN (NG-RAN) 220 can have one or more gNBs 222, while other configurations include one or more of either the ng-eNB 224 and the gNB 222. Either or both of the gNB 222 or the ng-eNB 224 can communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0070] Another optional aspect can include a location server 230, which 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). Additionally, the location server 230 can be integrated into a component of the core network, or alternatively can be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0071] Figure 2B Another example wireless network structure 240 is illustrated. The 5GC 260 (which can correspond to Figure 2AAmong them, the 5GC 210) can be functionally regarded as the control plane function provided by the Access and Mobility Management Function (AMF) 264 and the user plane function provided by the User Plane Function (UPF) 262, which cooperate to form the 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 among the UEs described herein) and the Session Management Function (SMF) 266, transparent proxy service for routing SM messages, access authentication and access authorization, transmission of Short Message Service (SMS) messages between the UE 204 and the Short Message Service Function (SMSF) (not shown), and Security Anchor Functionality (SEAF). The AMF 264 also interacts with the Authentication Server Function (AUSF) (not shown) and the UE 204, and receives the intermediate key established as a result of the UE 204 authentication process. In the case of authentication based on a UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), the AMF 264 retrieves the security material from the AUSF. The functions of the AMF 264 also include Security Context Management (SCM). The SCM receives the key from the SEAF, and the SCM uses this key to derive the access network-specific key. The functionality of the AMF 264 also includes location service management for regulatory services, transmission of location service messages between the UE 204 and the Location Management Function (LMF) 270 (which acts as the location server 230), transmission of location service messages between the NG-RAN 220 and the LMF 270, allocation of evolved packet system (EPS) bearer identifiers for EPS interoperability, and UE 204 mobility event notification. In addition, the AMF 264 also supports functionality for non-3GPP (Third Generation Partnership Project) access networks.

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

[0073] The functions of the SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, traffic steering configuration for routing traffic to the correct destination at the UPF 262, partial control of policy enforcement and QoS, and downlink data notification. The interface through which the SMF 266 communicates with the AMF 264 is referred to as the N11 interface.

[0074] Another optional aspect may include an LMF 270, which may communicate with the 5GC 260 to provide location assistance for the UE 204. The LMF 270 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. The LMF 270 may be configured to support one or more location services for the UE 204, which may be connected to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). The SLP 272 may support similar functions to the LMF 270, but the LMF 270 may communicate with the AMF 264, the NG-RAN 220, and the UE 204 on the control plane (e.g., using interfaces and protocols designed to carry signaling messages rather than voice or data), and the SLP 272 may communicate with the UE 204 and an external client (e.g., a third-party server 274) on the user plane (e.g., using protocols designed to carry voice and / or data, such as the Transmission Control Protocol (TCP) and / or IP).

[0075] Another optional aspect may include a third-party server 274 that may communicate with the LMF 270, SLP 272, 5GC 260 (e.g., via the AMF 264 and / or UPF 262), NG-RAN 220, and / or UE 204 to obtain location information (e.g., a 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 an 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.

[0076] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and the AMF 264, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220, respectively. The interface between the gNB 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 the "Xn-C" interface. One or more of the gNB 222 and / or ng-eNB 224 may communicate with one or more UEs 204 via a radio interface referred to as the "Uu" interface.

[0077] The functionality of 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 allocated to the gNB-DU 228, including passing user data, mobility control, radio access network sharing, positioning, session management, etc. More specifically, the gNB-CU 226 typically hosts the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that typically hosts the radio link control (RLC) and media 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-DU 228s 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.

[0078] The deployment of a communication system such as a 5G NR system can be arranged in various ways with various components or constituent parts. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, RAN nodes, core network nodes, network elements, or network equipment (such as base stations or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), transmit receive point (TRP), or cell, etc.) can be implemented as an aggregated base station (also referred to as a stand-alone base station or a monolithic base station) or a disaggregated base station.

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

[0080] Base station type operations or network designs may consider the aggregation characteristics of base station functionality. For example, a split base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration initiated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Splitting may include distributing functionality across two or more units at various physical locations, as well as virtually distributing the functionality of at least one unit, which may enable flexibility in network design. The various units of a split base station or a split RAN architecture may be configured for wired or wireless communication with at least one other unit.

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

[0082] Each of the units (i.e., CU 280, DU 285, RU 287, and the near RT RIC 259, non-RT RIC 257, and SMO framework 255) may include one or more interfaces or be coupled to one or more interfaces that are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or the associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, the units may include a wired interface that is configured to receive or transmit signals to one or more of the other units via a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or transmit signals, or both, to one or more of the other units via a wireless transmission medium.

[0083] In some aspects, the CU 280 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may utilize an interface that is configured to communicate signals with other control functions hosted by the CU 280. The CU 280 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some specific implementations, the CU 280 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bi-directionally with the CU-CP units via an interface (such as an E1 interface). As needed, the CU 280 may be implemented to communicate with the DU 285 for network control and signaling.

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

[0085] The lower layer functionality may be implemented by one or more RUs 287. In some deployments, the RUs 287 controlled by the DU 285 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both at least in part based on a functional split (such as a lower layer functional split). In such an architecture, the RUs 287 may be implemented to handle over-the-air (OTA) communication with one or more UEs 204. In some embodiments, the real-time aspects and non-real-time aspects of the control plane and user plane communication with the RUs 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration may enable the implementation of the DU 285 and the CU 280 in a cloud-based RAN architecture (such as a vRAN architecture).

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

[0087] The Non-RT RIC 257 can be configured to include a logical function that implements non-real-time control and optimization of RAN elements and resources, an artificial intelligence / machine learning (AI / ML) workflow including model training and update, or policy-based guidance of applications / features in the Near RT RIC 259. The Non-RT RIC 257 can be coupled to or communicate with the Near RT RIC 259 (such as via the A1 interface). The Near RT RIC 259 can be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via an interface (such as via the E2 interface) through data collection and actions, and this interface connects one or more CUs 280, one or more DUs 285, or both, and the O-eNB to the Near RT RIC 259.

[0088] In some specific implementations, to generate the AI / ML models to be deployed in the near-RT RIC 259, the non-RT RIC 257 may receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 259 and can be received from non-network data sources or from network functions at the SMO framework 255 or the non-RT RIC 257. In some examples, the non-RT RIC 257 or the near-RT RIC 259 may be configured to tune the RAN behavior or performance. For example, the non-RT RIC 257 may monitor the long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions via the SMO framework 255 (such as reconfiguration via O1) or via creating RAN management policies (such as A1 policies).

[0089] Figure 3A , Figure 3B and Figure 3C illustrate several example components (represented by the corresponding boxes) that can be incorporated into the UE 302 (which may correspond to any UE described herein), the base station 304 (which may correspond to any base station described herein), and the network entity 306 (which may correspond to or embody any network function described herein, including the location server 230 and the LMF 270, or alternatively may be independent of Figure 2A and Figure 2B the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in, such as a private network) to support operations as described herein. It should be understood that these components can be implemented in different specific implementations in different types of devices (e.g., in an ASIC, in a system-on-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. Additionally, 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.

[0090] UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively. These wireless wide area network (WWAN) transceivers provide components (e.g., components for transmission, components for reception, components for measurement, components for tuning, components for blocking transmission, etc.) for communication via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. WWAN transceivers 310 and 350 can each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes (such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc.) via at least one specified RAT (e.g., NR, LTE, GSM, etc.) through an interested wireless communication medium (e.g., a set of time / frequency resources in a specific spectrum). WWAN transceivers 310 and 350 can be configured in various ways according to the specified RAT for transmitting and encoding signals 318 and 358 (e.g., messages, indications, information, etc.), and vice versa for receiving and decoding signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, WWAN transceivers 310 and 350 each include: one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

[0091] In at least 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 communication via an interested wireless communication medium via at least one specified RAT (e.g., WiFi, LTE-D, Bluetooth ® , Zigbee ® , Z-Wave ®, PC5, dedicated short-range communication (DSRC), wireless access for vehicle environments (WAVE), near-field communication (NFC), ultra-wideband (UWB), etc.) communicate with other network nodes (such as other UEs, access points, base stations, etc.) through components (e.g., components for transmission, components for reception, components for measurement, components for tuning, components for blocking transmission, etc.). The short-range wireless transceivers 320 and 360 can be respectively configured in various ways for transmitting and encoding signals 328 and 368 (e.g., messages, indications, information, etc.) according to the specified RAT, and vice versa for receiving and decoding signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, the short-range wireless transceivers 320 and 360 respectively include: one or more transmitters 324 and 364 for respectively transmitting and encoding signals 328 and 368, and one or more receivers 322 and 362 for respectively receiving and decoding signals 328 and 368. As a specific example, the short-range wireless transceivers 320 and 360 can be WiFi transceivers, Bluetooth ® transceivers, Zigbee ® and / or Z-Wave ® transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

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

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

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

[0095] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360 in some embodiments, and network transceivers 380 and 390), and wired transceivers (e.g., network transceivers 380 and 390 in some embodiments) may generally be referred to as "transceivers", "at least one transceiver", or "one or more transceivers". Thus, the particular transceiver being a wired transceiver or a wireless transceiver may be inferred based on the type of communication being performed. For example, fronthaul communication between network devices or servers typically involves signaling via a wired transceiver, while wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via a wireless transceiver.

[0096] UE 302, base station 304, and network entity 306 also include other components that may be used in conjunction with the operations disclosed herein. UE 302, base station 304, and network entity 306 each include one or more processors 332, 384, and 394 for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 332, 384, and 394 may provide components for processing, such as components for determining, components for calculating, components for receiving, components for sending, components 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 circuits, or various combinations thereof.

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

[0098] The UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide components for sensing or detecting movement and / or orientation information unrelated to movement data derived from signals received from one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. By way of example, the sensors 344 may include an accelerometer (e.g., a microelectromechanical systems (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of movement detection sensor. Additionally, the sensors 344 may include multiple different types of devices and combine their outputs to provide movement information. For example, the sensors 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.

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

[0100] Referring in more detail to one or more processors 384, in the downlink, IP packets from the network entity 306 may be provided to the processor 384. One or more processors 384 may implement functionality for the RRC layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, and the media access control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with the broadcast of system information (e.g., master information block (MIB), system information block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer PDUs, error correction via 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 the mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0101] The transmitter 354 and the receiver 352 can implement layer 1 (L1) functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, can include: error detection on the transport channel, forward error correction (FEC) encoding / 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 disposes of 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 encoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to orthogonal frequency division multiplexing (OFDM) subcarriers, multiplexed with reference signals (e.g., pilots) in the time domain and / or frequency domain, and then combined together using the inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream. The OFDM symbol stream is spatially pre-coded to produce multiple spatial streams. Channel estimates from the channel estimator can be used to determine the encoding and modulation schemes and for spatial processing. The channel estimates can be derived from reference signals transmitted by the UE 302 and / or channel status feedback. Each spatial stream can then be provided to one or more different antennas 356. The transmitter 354 can modulate an RF carrier using the corresponding spatial stream for transmission.

[0102] At the UE 302, the receiver 312 receives signals via its corresponding antennas 316. The receiver 312 recovers the information modulated onto the RF carrier and provides the information to one or more processors 332. The transmitter 314 and the receiver 312 implement layer 1 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 there are multiple spatial streams destined for the UE 302, they can be combined by the receiver 312 into a single OFDM symbol stream. The receiver 312 then uses the fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 304. These soft decisions can be based on the channel estimates calculated by the channel estimator. The soft decisions are then decoded and de-interleaved to recover the data and control signals originally transmitted 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.

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

[0104] Similar to the functionality described in connection with downlink transmissions performed by base station 304, 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 transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and re-ordering 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 via hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0105] Channel estimates derived by a channel estimator from reference signals or feedback transmitted by base station 304 can be used by transmitter 314 to select appropriate decoding and modulation schemes and to facilitate spatial processing. The spatial streams generated by transmitter 314 can be provided to different antennas 316. Transmitter 314 can modulate RF carriers using the respective spatial streams for transmission.

[0106] Uplink transmissions are processed at base station 304 in a manner similar to that described in connection with the receiver functionality at UE 302. Receiver 352 receives signals via its respective antennas 356. Receiver 352 recovers the information modulated onto the RF carriers and provides the information to one or more processors 384.

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

[0108] For convenience, UE 302, base station 304, and / or network entity 306 are in Figure 3A 、 Figure 3B and Figure 3Cis shown to include 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. In particular, Figures 3A to 3C the various components in are optional in alternative configurations, and the various aspects include configurations that can vary due to design choices, cost, use of the device, or other considerations. For example, in Figure 3A the case of, a particular implementation of the UE 302 may omit the WWAN transceiver 310 (e.g., a wearable device or a tablet computer or a PC or a laptop may have Wi-Fi and / or Bluetooth capabilities without cellular capabilities), or may omit the short-range wireless transceiver 320 (e.g., only cellular, etc.), or may omit the satellite signal receiver 330, or may omit the sensor 344, etc. As another example, in Figure 3B the case of, a particular 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., only cellular, etc.), or may omit the satellite signal receiver 370, etc. For the sake of brevity, illustrations of the various alternative configurations are not provided herein, but will be readily understood by those skilled in the art.

[0109] The various components of the UE 302, the base station 304, and the network entity 306 may be communicatively coupled to each other via data buses 334, 382, and 392, respectively. In one aspect, the data buses 334, 382, and 392 may respectively form or be part of the communication interfaces of the UE 302, the base station 304, and the network entity 306. For example, in the case 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 communication between the different logical entities.

[0110] Figure 3A , Figure 3B and Figure 3C the components of can be implemented in various ways. In some implementations, Figure 3A , Figure 3B and Figure 3CThe components can be implemented in one or more circuits, such as one or more processors and / or one or more ASICs (which can include one or more processors). Here, each circuit can use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide the functionality. For example, some or all of the functionality represented by blocks 310 to 346 can be implemented by the processor and memory components of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Similarly, some or all of the functionality represented by blocks 350 to 388 can be implemented by the processor and memory components of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Also, some or all of the functionality represented by blocks 390 to 398 can be implemented by the processor and memory components of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). For simplicity, various operations, actions, and / or functions are described herein as being "performed by the UE", "performed by the base station", "performed by the network entity", etc. However, as will be understood, such operations, actions, and / or functions can actually be performed by specific components or combinations of components of 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.

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

[0112] Figure 4 FIG. 400 is a diagram illustrating an example frame structure in accordance with aspects of the present disclosure. The frame structure can be a downlink or uplink frame structure. Other wireless communication technologies can have different frame structures and / or different channels. Various frame structures can be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs).

[0113] LTE (and in some cases NR) utilizes Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. However, different from 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 referred to as tones, frequency slots, etc. Each subcarrier can be modulated with data. Generally speaking, modulation symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The interval between adjacent subcarriers can be fixed, and the total number (K) of subcarriers can depend on the system bandwidth. For example, the interval of subcarriers can be 15 kilohertz (kHz), and the minimum resource allocation (resource block) can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25 megahertz (MHz), 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, the nominal Fast Fourier Transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048 respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.8 MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, there can be 1, 2, 4, 8, or 16 subbands respectively.

[0114] LTE supports a single parameter set (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR can support multiple parameter sets (µ), e.g., 15 kHz (µ = 0), 30 kHz (µ = 1), 60 kHz (µ = 2), 120 kHz (µ = 3), and 240 kHz (µ = 4) or larger subcarrier spacings may be available. In each subcarrier spacing, there are 14 symbols per time slot. For 15 kHz SCS (µ = 0), there is one time slot per subframe, 10 time slots per frame, the time 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 30 kHz SCS (µ = 1), there are two time slots per subframe, 20 time slots per frame, the time slot duration is 0.5 ms, the symbol duration is 33.3 µs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 100. For 60 kHz SCS (µ = 2), there are four time slots per subframe, 40 time slots per frame, the time slot duration is 0.25 ms, the symbol duration is 16.7 µs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 200. For 120 kHz SCS (µ = 3), there are eight time slots per subframe, 80 time slots per frame, the time slot duration is 0.125 ms, the symbol duration is 8.33 µs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 400. For 240 kHz SCS (µ = 4), there are 16 time slots per subframe, 160 time slots per frame, the time slot duration is 0.0625 ms, the symbol duration is 4.17 µs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 800.

[0115] In Figure 4 's example, a parameter set of 15 kHz is used. Thus, in the time domain, a 10 ms frame is divided into 10 equal-sized subframes, each subframe being 1 ms, and each subframe includes one time slot. In Figure 4 , 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.

[0116] A resource grid can be used to represent a time slot, and each time slot includes one or more time-concurrent resource blocks (RBs) (also known as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE can correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In Figure 4In the parameter set, for the normal cyclic prefix, an RB can contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For the extended cyclic prefix, an RB can 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.

[0117] Some REs can carry reference (pilot) signals (RSs). These reference signals can include positioning reference signals (PRSs), tracking reference signals (TRSs), phase tracking reference signals (PTRSs), cell-specific reference signals (CRSs), channel state information reference signals (CSI-RSs), demodulation reference signals (DMRSs), primary synchronization signals (PSSs), secondary synchronization signals (SSSs), synchronization signal blocks (SSBs), sounding reference signals (SRSs), etc., depending on whether the illustrated frame structure is used for uplink communication or downlink communication. Figure 4 Examples of the example locations of REs carrying reference signals (marked as "R") are illustrated.

[0118] Figure 5 FIG. 500 is a diagram illustrating various downlink channels within an example downlink time slot. In Figure 5 it, 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. In Figure 5 the example, a parameter set of 15 kHz is used. Thus, in the time domain, the illustrated time slot length is one millisecond (ms), divided into 14 symbols.

[0119] In NR, the channel bandwidth or system bandwidth is divided into multiple bandwidth parts (BWPs). A BWP is a contiguous set of RBs selected from a contiguous subset of the common RBs for a given parameter set on a given carrier. Generally, a maximum of four BWPs can be specified in the downlink and uplink. That is, a UE can be configured to have at most four BWPs on the downlink and at most four BWPs on the uplink. Only one BWP (uplink or downlink) can be active at a given time, which means that a UE can only receive or transmit on one BWP at a time. On the downlink, the bandwidth of each BWP should be equal to or greater than the bandwidth of the SSB, but it can contain the SSB or not contain the SSB.

[0120] Refer to Figure 5, the Primary Synchronization Signal (PSS) is used by the UE to determine subframe / symbol timing and the physical layer identity. The Secondary Synchronization Signal (SSS) is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the PCI. Based on the PCI, the UE can determine the location of the aforementioned DL-RS. The Physical Broadcast Channel (PBCH) carrying the Master Information Block (MIB) can be logically grouped with the PSS and SSS to form an SSB (also known as SS / PBCH). The MIB provides the number of RBs in the downlink system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0121] The Physical Downlink Control Channel (PDCCH) carries downlink control information (DCI) within one or more Control Channel Elements (CCEs). Each CCE includes one or more sets of Resource Element Groups (REGs) bundled (which can span multiple symbols in the time domain). Each REG bundle includes one or more REGs, and each REG corresponds to 12 resource elements (one resource block) in the frequency domain and one OFDM symbol in the time domain. The physical resource set used to carry PDCCH / DCI is called a Control Resource Set (CORESET) in NR. In NR, the PDCCH is restricted to a single CORESET and is transmitted together with its own DMRS. This enables UE-specific beamforming for the PDCCH.

[0122] In Figure 5 the example, there is one CORESET per BWP, and this CORESET spans three symbols in the time domain (although it can be just one symbol or two symbols). Different from the LTE control channel that occupies the entire system bandwidth, in NR, the PDCCH channel is localized to a specific region in the frequency domain (i.e., the CORESET). Therefore, Figure 5 the frequency components of the PDCCH shown in

[0123] The DCI within the PDCCH carries information regarding uplink resource allocation (persistent and non-persistent) and a description of the downlink data sent to the UE (referred to as uplink grant and downlink grant, respectively). More specifically, the DCI indicates the resources scheduled for the downlink data channel (e.g., PDSCH) and the uplink data channel (e.g., Physical Uplink Shared Channel (PUSCH)). Multiple (e.g., up to eight) DCIs can be configured in the PDCCH, and these DCIs can have one of multiple formats. For example, there are different DCI formats for uplink scheduling, downlink scheduling, uplink transmit power control (TPC), etc. The PDCCH can be transmitted by 1, 2, 4, 8, or 16 CCEs to accommodate different DCI payload sizes or decoding rates.

[0124] Figure 6 FIG. 600 is a diagram illustrating various uplink channels within an exemplary uplink time slot. In Figure 6 it, 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. In the example of Figure 6 a parameter set of 15 kHz is used. Thus, in the time domain, the illustrated time slot has a length of one millisecond (ms) and is divided into 14 symbols.

[0125] The Random Access Channel (RACH) (also known as the Physical Random Access Channel (PRACH)) can be within one or more time slots in a frame based on the PRACH configuration. The PRACH can include six consecutive RB pairs within a time slot. The PRACH allows the UE to perform initial system access and achieve uplink synchronization. The Physical Uplink Control Channel (PUCCH) can be located at the edge of the uplink system bandwidth. The PUCCH carries uplink control information (UCI), such as a scheduling request, CSI report, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and HARQ ACK / NACK feedback. The Physical Uplink Shared Channel (PUSCH) carries data and can additionally be used to carry a Buffer Status Report (BSR), Power Headroom Report (PHR), and / or UCI.

[0126] Figure 7 FIG. 700 illustrates an example of a wireless communication system 700 that supports wireless unicast sidelink establishment in accordance with aspects of the present disclosure. In some examples, the wireless communication system 700 can implement aspects of the wireless communication systems 100, 200, and 250. The wireless communication system 700 can include a first UE 702 and a second UE 704, which can be examples of any UE described herein. As a specific example, UEs 702 and 704 can correspond to Figure 1the V-UE 160 therein.

[0127] In Figure 7 the example of, UE 702 may attempt to establish a unicast connection with UE 704 via a sidelink, which may be a V2X sidelink between UE 702 and UE 704. As a specific example, the established sidelink connection may correspond to <� Figure 1 the sidelinks 162 and / or 168 therein. The sidelink connection may be established within an omnidirectional frequency range (e.g., FR1) and / or a mmW frequency range (e.g., FR2). In some cases, UE 702 may be referred to as the initiating UE that initiates the sidelink connection procedure, and UE 704 may be referred to as the target UE that is the target of the sidelink connection procedure performed by the initiating UE.

[0128] To establish a unicast connection, access stratum (AS) (a functional layer in the UMTS and LTE protocol stacks between the RAN and the UE, which is responsible for transmitting data via the radio link and managing radio resources and is part of layer 2) parameters may be configured and negotiated between UE 702 and UE 704. For example, the matching of transmission and reception capabilities may be negotiated between UE 702 and UE 704. Each UE may have different capabilities (e.g., transmission and reception capabilities, 64 - quadrature amplitude modulation (QAM), transmit diversity, carrier aggregation (CA) capabilities, supported communication frequency bands, etc.). In some cases, different services may be supported at the upper layers of the corresponding protocol stacks of UE 702 and UE 704. Additionally, a security association for the unicast connection may be established between UE 702 and UE 704. Unicast traffic may benefit from link - level security protection (e.g., integrity protection). Security requirements may be different for different radio communication systems. For example, V2X systems and Uu systems may have different security requirements (e.g., Uu security does not include confidentiality protection). Additionally, the IP configuration (e.g., IP version, address, etc.) for the unicast connection may be negotiated between UE 702 and UE 704.

[0129] In some cases, the UE 704 may create a service announcement (e.g., service capability message) for transmission over a cellular network (e.g., cV2X) to assist in sidelink connection establishment. Conventionally, the UE 702 may identify and locate candidates for sidelink communication based on unencrypted basic service messages (BSMs) broadcast by nearby UEs (e.g., UE 704). The BSM may include location information, security and identity information, and vehicle information (e.g., speed, maneuver, size, etc.) about the corresponding UE. However, for different wireless communication systems (e.g., D2D or V2X communication), a discovery channel may not be configured such that the UE 702 can detect the BSM. Thus, service announcements (e.g., discovery signals) sent by the UE 704 and other nearby UEs may be upper layer signals and are broadcast (e.g., in NR sidelink broadcasts). In some cases, the UE 704 may include one or more parameters for itself in the service announcement, including connection parameters and / or capabilities it possesses. The UE 702 may then monitor and receive the broadcast service announcements to identify potential UEs for the corresponding sidelink connection. In some cases, the UE 702 may identify potential UEs based on the capabilities indicated by each UE in its respective service announcement.

[0130] The service announcement may include information to assist the UE 702 (e.g., or any initiating UE) in identifying the UE ( Figure 7 such as the UE 704 in the example) that sent the service announcement. For example, the service announcement may include channel information where a direct communication request may be transmitted. In some cases, the channel information may be RAT-specific (e.g., specific to LTE or NR) and may include a resource pool within which the UE 702 sends a communication request. Additionally, in cases where the destination address is different from the current address (e.g., the address of the streaming media provider or UE that sent the service announcement), the service announcement may include the specific destination address of the UE (e.g., layer 2 destination address). The service announcement may also include the network layer or transport layer on which the UE 702 sends a communication request. For example, the network layer (also referred to as "layer 3" or "L3") or transport layer (also referred to as "layer 4" or "L4") may indicate the port number of the application for which the UE sends the service announcement. In some cases, in situations where the signaling (e.g., PC5 signaling) directly carries a protocol (e.g., Real-Time Transport Protocol (RTP)) or gives a locally generated random protocol, IP addressing may not be required. Additionally, the service announcement may include the protocol type for credential establishment and QoS-related parameters.

[0131] After identifying a potential sidelink connection target ( Figure 7 such as the UE 704 in the example), the initiating UE ( Figure 7The UE 702 in the example of can send a connection request 715 to the identified target UE 704. In some cases, the connection request 715 can be the first RRC message (e.g., "RRCSetupRequest" message) sent by the UE 702 to request a unicast connection with the UE 704. For example, the unicast connection can utilize the PC5 interface for the side link, and the connection request 715 can be an RRC connection establishment request message. Additionally, the UE 702 can use the side link signaling radio bearer 705 to transmit the connection request 715.

[0132] After receiving the connection request 715, the UE 704 can determine whether to accept or reject the connection request 715. The UE 704 can base this determination on the transmit / receive capabilities, the ability to accommodate a unicast connection over the side link, the specific service indicated for the unicast connection, the content to be sent over the unicast connection, or a combination thereof. For example, in a case where the UE 702 wants to send or receive data using a first RAT, but the UE 704 does not support the first RAT, the UE 704 can reject the connection request 715. Additionally or alternatively, the UE 704 can reject the connection request 715 based on the inability to accommodate a unicast connection over the side link due to limited radio resources, scheduling issues, etc. Thus, the UE 704 can send an indication in the connection response 720 of whether to accept or reject the request. Similar to the UE 702 and the connection request 715, the UE 704 can use the side link signaling radio bearer 710 to transmit the connection response 720. Additionally, the connection response 720 can be the second RRC message (e.g., "RRCResponse" message) sent by the UE 704 in response to the connection request 715.

[0133] In some cases, the side link signaling radio bearers 705 and 710 can be the same side link signaling radio bearer, or can be separate side link signaling radio bearers. Thus, the radio link control (RLC) layer acknowledged mode (AM) can be used for the side link signaling radio bearers 705 and 710. UEs that support unicast connections can listen on the logical channels associated with these side link signaling radio bearers. In some cases, the AS layer (i.e., layer 2) can pass information directly via RRC signaling (e.g., control plane) rather than the V2X layer (e.g., data plane). [[ID=(7]]

[0134] In the case where the connection response 720 indicates that the UE 704 has accepted the connection request 715, the UE 702 may subsequently send a connection establishment 725 message on the sidelink signaling radio bearer 705 to indicate that the unicast connection establishment is complete. In some cases, the connection establishment 725 may be a third RRC message (e.g., an "RRCSetupComplete" message). Each of the connection request 715, the connection response 720, and the connection establishment 725 may use the basic capabilities when being transmitted from one UE to another UE to enable each UE to receive and decode the corresponding transmission (e.g., an RRC message).

[0135] Additionally, an identifier may be used for each of the connection request 715, the connection response 720, and the connection establishment 725. For example, the identifier may indicate which UE 702 / 704 is sending which message and / or which UE 702 / 704 the message is intended for. For physical (PHY) layer channels, the RRC signaling and any subsequent data transmission may use the same identifier (e.g., a layer 2 ID). However, for logical channels, these identifiers may be separate for the RRC signaling and the data transmission. For example, on a logical channel, the RRC signaling and the data transmission may be processed differently and have different acknowledgment (ACK) feedback message reception and transmission. In some cases, for RRC message reception and transmission, a physical layer ACK may be used to ensure that the corresponding message is correctly sent and received.

[0136] One or more information elements may be included in the connection request 715 and / or the connection response 720 for the UE 702 and / or the UE 704 respectively to enable negotiation of the corresponding AS layer parameters for the unicast connection. For example, the UE 702 and / or the UE 704 may include packet data convergence protocol (PDCP) parameters in the corresponding unicast connection establishment message to set up the PDCP context for the unicast connection. In some cases, the PDCP context may indicate whether PDCP duplication is used for the unicast connection. Additionally, the UE 702 and / or the UE 704 may include RLC parameters when establishing the unicast connection to set up the RLC context for the unicast connection. For example, the RLC context may indicate whether the RLC layer for the unicast communication uses AM (e.g., a reordering timer (t-reordering) is used) or uses the unacknowledged mode (UM).

[0137] Additionally, UE 702 and / or UE 704 may include Media Access Control (MAC) parameters to set up the MAC context for the unicast connection. In some cases, the MAC context may enable a resource selection algorithm for the unicast connection, a Hybrid Automatic Repeat reQuest (HARQ) feedback scheme (e.g., ACK or Negative ACK (NACK) feedback), parameters of the HARQ feedback scheme, carrier aggregation, or a combination thereof. Additionally, UE 702 and / or UE 704 may include PHY layer parameters when establishing the unicast connection to set up the PHY layer context for the unicast connection. For example, the PHY layer context may indicate the transmission format for the unicast connection (unless a transmission profile is included for each UE 702 / 704) and radio resource configuration (e.g., Bandwidth Part (BWP), parameter set, etc.). These information elements may be supported for different frequency range configurations (e.g., FR1 and FR2).

[0138] In some cases, a security context may also be set up for the unicast connection (e.g., after sending the connection establishment 725 message). Before a security association (e.g., security context) is established between UE 702 and UE 704, the sidelink signaling radio bearers 705 and 710 may not be protected. After the security association is established, the sidelink signaling radio bearers 705 and 710 may be protected. Thus, the security context may enable secure data transmission over the unicast connection and the sidelink signaling radio bearers 705 and 710. Additionally, IP layer parameters (e.g., local link IPv4 or IPv6 address) may also be negotiated. In some cases, the IP layer parameters may be negotiated through an upper layer control protocol that runs after the RRC signaling is established (e.g., establishing the unicast connection). As described above, UE 704 may base its decision on whether to accept or reject the connection request 715 on the specific service indicated for the unicast connection and / or the content to be sent over the unicast connection (e.g., upper layer information). The specific service and / or content may also be indicated through an upper layer control protocol that runs after the RRC signaling is established.

[0139] After the unicast connection is established, UE 702 and UE 704 may communicate using the unicast connection over sidelink 730, where sidelink data 735 is sent between the two UEs 702 and 704. Sidelink 730 may correspond to Figure 1The sidelinks 162 and / or 168 therein. In some cases, the sidelink data 735 may include RRC messages sent between two UEs 702 and 704. To maintain this unicast connection on the sidelink 730, the UE 702 and / or the UE 704 may send keep-alive messages (e.g., "RRCLinkAlive" messages, the fourth RRC message, etc.). In some cases, the keep-alive messages may be triggered periodically or on demand (e.g., event-triggered). Thus, the triggering and sending of the keep-alive messages may be invoked by the UE 702 or by both the UE 702 and the UE 704. Additionally or alternatively, MAC control elements (CEs) (e.g., defined on the sidelink 730) may be used to monitor the state of the unicast connection on the sidelink 730 and maintain the connection. When the unicast connection is no longer needed (e.g., the UE 702 travels far enough away from the UE 704), the UE 702 and / or the UE 704 may initiate a release procedure to discard the unicast connection on the sidelink 730. Thus, subsequent RRC messages may not be sent between the UE 702 and the UE 704 over the unicast connection.

[0140] A UE within a vehicle or as part of a vehicle may be referred to as a vehicle UE (VUE). The VUE may broadcast its location using a basic safety message (BSM) that announces the type, location, and motion state of the VUE or using a sensor data sharing message (SDSM). Other nearby VUEs may receive the BSM and determine the location of the transmitting VUE, and by reading the location information from the BSM, expand to determine the location of the vehicle. This allows other VUEs to determine the locations of other nearby VUEs without having to perform time-consuming ranging operations.

[0141] However, there is a possibility that the actual location of the VUE is different from the location announced by the VUE in the sent BSM. This may occur, for example, due to component failures of sensors, GPS transceivers, etc. or other unexpected reasons, or may be the deliberate target of malicious applications or malware. Figure 8 Examples thereof are illustrated in

[0142] Figure 8 Illustrates possible interactions between wireless devices according to aspects of the present disclosure. Figure 8 Illustrates the interaction between VUE1 800, VUE2 802, an access point 804, and a third entity 806, which may be a roadside unit (RSU) or a base station (BS). In Figure 8 this, one of the wireless devices may be able to detect a difference between the announced location of another wireless device and the actual location of that other wireless device.

[0143] For example, VUE1 800 may report its location in BSM 808. VUE2 802 or AP 804 receives the BSM 808 containing the advertised location of VUE1 800, and calculates the distance between its own location and the advertised location of VUE1 800. VUE2 802 or AP 804 then knows the distance from VUE1 800 and knows the advertised transmit power of BSM 808, and can thus calculate what the expected received signal strength indicator (RSSI) value of BSM 808 should be.

[0144] If the actual RSSI value of BSM 808 is different from the expected value of RSSI, this indicates that the assumed distance between VUE1 800 and VUE2 802 (or between VUE1 800 and AP 804) may be incorrect, which may be because the advertised location of VUE1 800 is incorrect. In this scenario, VUE2 802 or AP 804 may request confirmation of the location of VUE1 800 from the network server 806. This request is shown as the signaling 810 from VUE2 802 in Figure 8 In addition, VUE2 802 or AP 804 may notify the difference to VUE1 800 and / or the network. This notification is shown as the message 812 from VUE2 802 in Figure 8 In some aspects, VUE2 802 or AP 804 may issue what is referred to as a "misconduct report", but this report is transmitted to a "misconduct agency" that oversees GPS (such as the Federal Communications Commission (FCC)).

[0145] In another example, AP 804 may advertise its location, and one of the other wireless devices may determine that the advertised location of AP 804 does not match its actual location. There are scenarios in which the AP and other non-mobile devices do not know their true locations. For example, AP 804 may be an indoor AP that was initially installed for communication purposes but is now being repurposed to act as an anchor node to provide location services to other wireless devices. Many such APs rely on crowdsourcing (where they make measurements with several UEs over time) to come up with location estimates. Another scenario is where the measured true value of the AP is itself incorrect due to human error and calibration errors. Yet another scenario is when a stationary AP is relocated or redeployed for some reason. Thus, these estimates may be incorrect, and the techniques disclosed herein can help an AP (such as the Figure 8 AP 804 in

[0146] However, there is currently no provision in the 3GPP specifications to extend "differential detection" to include crowdsourcing. Accordingly, techniques for improving positioning accuracy via crowdsourcing are now presented. These techniques can include crowdsourcing of misbehavior notifications, identifying specific measurements and / or positioning anchors as suspect or potential sources of error, and identifying and avoiding security vulnerabilities.

[0147] Notification of Misconduct through Crowdsourcing

[0148] In some aspects, improving positioning accuracy via crowdsourcing can involve sharing differential information among multiple nodes, which can be VUEs, RSUs, network entities, etc. Using VUE1 and VUE2 as an example, VUE1 reports its own positioning in a BSM or SDSM. In some aspects, VUE1 may also report the list of measurements on which its own positioning calculation is based. In some aspects, VUE1 may also provide information about the anchor location and the specific technique used to estimate its own positioning. In this example, VUE2 receives all the information reported or provided by VUE1 and determines that there is a difference between the positioning of VUE1 as reported by VUE1 and the positioning of VUE1 determined from sources other than VUE1's self-reported positioning.

[0149] In some aspects, VUE2 may report the difference via an extension of the BSM or SDSM or via a new message. In some aspects, VUE2 provides an explanation of why it believes the positioning reported by VUE1 is incorrect, the list of measurements on which VUE2 based its conclusion, or both. In some aspects, VUE2 may also provide a confidence value for its conclusion, e.g., the degree to which VUE2 determines or does not determine that the positioning reported by VUE1 is incorrect. In some aspects, VUE2 may identify a specific positioning anchor as a positioning anchor that may lead to an incorrect positioning estimate. For example, VUE2 may determine or detect that a specific positioning anchor is reporting an incorrect true value. In some aspects, VUE2 may detect that a specific positioning anchor may be a source of error by observing that each of the target nodes using the specific positioning anchor as a common anchor node has perceived an incorrect positioning estimate.

[0150] Response to Notification of Misconduct

[0151] When VUE1 receives a warning, e.g., from VUE2, that the reported location of VUE1 may be incorrect, VUE1 can respond in several ways. In some aspects, VUE1 may simply ignore the warning from VUE2. In some aspects, VUE1 may ignore the warning from VUE2 until a threshold number of other VUEs also transmit the same or a similar warning. In some aspects, VUE1 may perform additional measurements with other VUEs to confirm, verify, or validate that the warning from VUE2 is correct. In some aspects, VUE1 may choose to use only a subset of devices of the same brand and / or model or a subset of devices belonging to a certain group of devices that have been certified by VUE1 for performing such verification to verify the warning from VUE2. In some aspects, details of such groups (e.g., their membership lists) may be stored on a server and may be requested by VUE1 on demand. These techniques of confirming or validating a warning by comparing the detection of the warning from one source (e.g., VUE2) with warnings from other sources (e.g., VUE3, VUE4, etc.) can prevent VUE1 from being misled or deceived by bad information from VUE2. This provides enhanced security against potential spoofing attacks by one or a small number of malicious VUEs.

[0152] In some aspects, such as when the warning from VUE2 identifies sources that VUE2 has determined may be incorrect or unreliable, VUE1 may remove those sources from VUE1's location calculation. In some aspects, removing the sources may trigger VUE1 to recalculate its location without the suspect sources and issue another BSM with updated location information.

[0153] In some aspects, VUE1 may respond to VUE2. For example, in some aspects, VUE1 may notify VUE2 that VUE1 is ignoring the warning from VUE2. In some aspects, VUE1 may indicate to VUE2 that the warning from VUE2 is unreasonable. For example, VUE1 may provide a list of devices that have not transmitted similar warnings to VUE2 (e.g., to make VUE2 aware that VUE2 may be wrong in its assessment). In some aspects, VUE1 may notify VUE2 that VUE1 has confirmed that the warning from VUE2 is correct. In some aspects, VUE1 may notify VUE2 that VUE1 will now ignore some specific location sources, which may be the same as or different from the sources that VUE2 suspects to be incorrect or unreliable.

[0154] Selective Reporting or Filtering of Crowdsourced Data

[0155] In some aspects, improving location accuracy through crowdsourcing may involve using a third-party arbiter to review, filter, and / or report crowdsourced data. In some aspects, one or more dedicated devices may be deployed to identify good crowdsourced data and then broadcast that good crowdsourced data to the rest of the network. In some aspects, these devices may be deployed at known locations. In some aspects, these devices may be proprietary servers, e.g., such as Connected Intelligent Edge (CIE). In some aspects, these devices may passively listen to, e.g., measurement exchanges between VUEs and may then maintain a list of devices and measurements that are considered "good" (which helps in making accurate location estimates). In some aspects, these devices may also actively perform location measurements with other VUEs and then collect good crowdsourced data after performing misbehavior detection.

[0156] In some aspects, these devices may then broadcast / multicast the good crowdsourced data (which contains valid measurements) to other target nodes seeking to verify or enhance the accuracy of their existing location estimates. In some aspects, these devices may also include information about error sources (such as anchors with incorrect ground truth) such that other target devices can exclude measurements made using such anchor nodes from their final location estimate calculations. In some aspects, these devices may relay information to a network entity which then broadcasts the crowdsourced data. In some aspects, the data may be region-specific, e.g., it may be broadcast only to target devices within a specific region.

[0157] Crowdsourced Measurements from Various Devices - Fusion Weights

[0158] In some aspects, improving location accuracy through crowdsourcing may involve crowdsourced measurement - fusion weights from various devices. In some aspects, a device may broadcast a set of weights it applies to various sources, e.g., in a SDSM message, a Vehicle - to - Everything (V2X) message, another type of message, or a new message. In some aspects, when a first device detects a difference in another device, the first device may adjust the weight associated with that other device and broadcast the adjustment to neighboring devices so that they can also make the weight adjustment. Similarly, the first device may notify the server of the adjustment and the server may notify other devices of the adjustment, e.g., via transmitting updated assistance data.

[0159] In some aspects, a particular brand / model of device may be leveraging a particular strategy in terms of how it combines measurements to obtain a positioning estimate. In some aspects, the fusion process can be abstracted as a collection of weights across different types of measurements and technology applications. In some aspects, the device may broadcast or multicast this information, along with brand / model details, to neighboring devices. In some aspects, through misbehavior detection, a receiving device may be able to learn an appropriate weighting scheme to improve the positioning accuracy of the transmitting device; these weights can be relayed to a network entity such as a location server or LMF, or a proprietary server such as a CIE. In some aspects, the server may record and maintain a table of such data, which can then be used as auxiliary data in future positioning sessions. In some aspects, the auxiliary data can be in the form of an appropriate weighting scheme across measurements and technologies. In some aspects, the auxiliary data may also vary between regions. For example, a coarse region may be defined as an area in the city center as opposed to another area along a highway, etc. In some aspects, such information may be exchanged between devices operating under a subscription service, or such information may pertain to a particular class of devices of a particular brand / model / operating system.

[0160] Figure 9 is a flowchart of an example process 900 associated with improving positioning accuracy through crowdsourcing, in accordance with aspects of the present disclosure. In some particular implementations, Figure 9 one or more of the process blocks of Figure 9 may be performed by a first wireless device (e.g., UE 104, AP 150). In some particular implementations, Figure 9 one or more of the process blocks of

[0161] As Figure 9 shown, process 900 may include receiving a first message from a second UE, the first message including an advertised location of the second UE (block 910). The components for performing the operations of block 910 may include the processor 332, the memory 340, or the WWAN transceiver 310 of UE 302. For example, UE 302 may use the receiver 312 to receive the first message.

[0162] As Figure 9As further shown in, process 900 may include determining an estimated location of a second UE (block 920). The components for performing the operations of block 920 may include the processor 332, the memory 340, or the WWAN transceiver 310 of UE 302. For example, UE 302 may determine the estimated location of the second UE based on the analysis of the first message by the processor 332.

[0163] As Figure 9 As further shown in, process 900 may include detecting a difference between the advertised location of the second UE and the estimated location of the second UE (block 930). The components for performing the operations of block 930 may include the processor 332, the memory 340, or the WWAN transceiver 310 of UE 302. For example, UE 302 may use the processor 332 to detect the difference between the advertised location of the second UE and the estimated location of the second UE.

[0164] As Figure 9 As further shown in, process 900 may include transmitting a second message to at least one other UE, the second message indicating the existence of a difference between the advertised location of the second UE and the estimated location of the second UE (block 940). The components for performing the operations of block 940 may include the processor 332, the memory 340, or the WWAN transceiver 310 of UE 302. For example, UE 302 may use the transmitter 314 to transmit the second message.

[0165] In some aspects, receiving the first message includes receiving a Basic Safety Message (BSM) or a Sensor Data Sharing Message (SDSM).

[0166] In some aspects, determining the estimated location of the second UE includes determining the estimated location of the second UE based on a positioning operation involving the second UE.

[0167] In some aspects, determining the estimated location of the second UE includes receiving an indication of the estimated location of the second UE from another UE, a base station, or a network entity.

[0168] ?In some aspects, the first message includes an indication of transmit power and is received in terms of received power, and wherein determining the estimated location of the second UE includes calculating a first estimated distance between the first UE and the second UE based on a difference between the transmit power of the first message and the received power of the first message.

[0169] In some aspects, detecting the difference between the advertised location of the second UE and the estimated location of the second UE includes: calculating a second estimated distance between the first UE and the second UE based on the advertised location of the first UE and the current location of the second UE; and detecting that the first estimated distance and the second estimated distance do not match.

[0170] In some aspects, reporting the difference between the advertised location of the second UE and the estimated location of the second UE to the at least one UE includes reporting the difference to the second UE.

[0171] In some aspects, reporting the difference between the advertised location of the second UE and the estimated location of the second UE to the at least one UE includes at least one of the following: reporting the advertised location of the second UE and the estimated location of the second UE; indicating the method used to determine the estimated location; indicating a confidence value of the accuracy of the estimated location; or identifying at least one positioning anchor as a potential source or cause of the difference.

[0172] In some aspects, transmitting the second message to at least one other UE includes transmitting the second message via a third entity that collects, filters, or aggregates messages.

[0173] Process 900 may include additional specific implementations, such as any single specific implementation or any combination of specific implementations described below and / or in combination with one or more other processes described elsewhere herein. Although Figure 9 example boxes of process 900 are shown, in some specific implementations, process 900 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner compared to those depicted in Figure 9 . Additionally or alternatively, two or more boxes of process 900 may be executed in parallel.

[0174] Figure 10 is a flowchart of an example process 1000 associated with improving positioning accuracy through crowdsourcing according to aspects of the present disclosure. In some specific implementations, Figure 10 one or more process boxes of Figure 10 may be executed by a UE (e.g., UE 104, AP 150). In some specific implementations, Figure 10 one or more process boxes of

[0175] As Figure 10As shown, process 1000 may include sending a first message that includes an advertised location of a first UE (block 1010). Components for performing the operation of block 1010 may include processor 332, memory 340, or WWAN transceiver 310 of UE 302. For example, UE 302 may use transmitter 314 to send the first message.

[0176] As Figure 10 Further shown therein, process 1000 may include receiving a second message from a second UE, the second message indicating a difference between the advertised location of the first UE and an estimated location of the first UE (block 1020). Components for performing the operation of block 1020 may include processor 332, memory 340, or WWAN transceiver 310 of UE 302. For example, UE 302 may use receiver 312 to receive the second message.

[0177] In some aspects, process 1000 includes verifying the accuracy of the advertised location of the first UE.

[0178] In some aspects, verifying the accuracy of the advertised location of the first UE includes performing a positioning operation to determine a current positioning of the first UE and comparing the advertised location of the first UE with the current positioning of the first UE.

[0179] In some aspects, when it is determined that the advertised location of the first UE is accurate, the first UE may notify the second UE that the advertised location of the first UE is accurate, and when it is determined that the advertised location of the first UE is inaccurate, the first UE may notify the second UE that the advertised location of the first UE is inaccurate.

[0180] In some aspects, when it is determined that the advertised location of the first UE is inaccurate, the first UE may perform a positioning operation to determine a current positioning of the first UE and may send a third message that includes the current positioning of the first UE as the advertised location of the first UE.

[0181] In some aspects, the first UE may choose not to verify the accuracy of the advertised location of the first UE unless a threshold number of other UEs indicate or have indicated a difference between the advertised location of the first UE and an estimated location of the first UE.

[0182] In some aspects, the second message includes information identifying at least one positioning anchor as a potential source or cause of the difference, and wherein the method further includes excluding the at least one positioning anchor from the positioning operation.

[0183] In some aspects, the first UE may send to the second UE a list of other UEs that have not indicated to the first UE the difference between the advertised location and the estimated location of the first UE.

[0184] In some aspects, receiving the second message includes receiving the second message from the second UE via a third entity that collects, filters, or aggregates messages.

[0185] Process 1000 may include additional embodiments, such as any individual embodiment or any combination of embodiments described below and / or in combination with one or more other processes described elsewhere herein. Although Figure 10 example boxes of process 1000 are shown, in some embodiments, process 1000 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner compared to the boxes depicted in Figure 10 . Additionally or alternatively, two or more boxes of process 1000 may be executed in parallel.

[0186] Figure 11 is a flowchart of an example process 1100 associated with improving positioning accuracy through crowdsourcing according to aspects of the present disclosure. In some embodiments, Figure 11 one or more process boxes of Figure 11 may be performed by a network entity (e.g., location server 172, customization server, CIE). In some embodiments, Figure 11 one or more process boxes of

[0187] such as Figure 11 shown, process 1100 may include monitoring the network for positioning-related messages (block 1110). The components for performing the operations of block 1110 may include the processor 394, the memory 396, or the network transceiver 390 of the network entity 306. For example, the network entity 306 may use the network transceiver to monitor the network for positioning-related messages.

[0188] such as Figure 11As further shown in FIG. 0, process 1100 may include detecting positioning misconduct (block 1120) based on the content of positioning-related messages. Components for performing the operations of block 1120 may include processor 394, memory 396, or network transceiver 390 of network entity 306. For example, network entity 306 may use processor 394 and memory 396 to detect positioning misconduct based on the content of positioning-related messages.

[0189] In some aspects, process 1100 may include initiating a positioning operation through at least one network device, where monitoring the network for positioning-related messages includes monitoring the network for messages related to the positioning operation initiated by the network entity.

[0190] In some aspects, detecting positioning misconduct includes identifying a first set of network devices that are potential sources or causes of positioning errors, identifying a second set of network devices that are not potential sources or causes of positioning errors, or identifying both the first set and the second set.

[0191] In some aspects, identifying the first set of network devices that are potential sources or causes of positioning errors includes: identifying the network device that receives a notification of the difference between the advertised location of the receiving network device and the estimated location of the network device; or identifying the network device involved in one or more positioning operations that result in a notification of the difference between the advertised location of the network device and the estimated location of the network device.

[0192] In some aspects, identifying the first set of network devices that are potential sources or causes of positioning errors includes receiving from a network device a message identifying one or more network devices that are potential sources or causes of positioning errors.

[0193] In some aspects, process 1100 may include sending a message identifying the first set of network devices, the second set of network devices, or both.

[0194] In some aspects, process 1100 may include sending positioning information from positioning-related messages for which no positioning misconduct has been detected.

[0195] Process 1100 may include additional specific implementations, such as any single specific implementation or any combination of specific implementations described below and / or in combination with one or more other processes described elsewhere herein. Although Figure 11 example blocks of process 1100 are shown, in some specific implementations, process 1100 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner compared to the Figure 11 blocks depicted in FIG. Additionally or alternatively, two or more blocks of process 1100 may be executed in parallel.

[0196] Figure 12 is a flowchart of an example process 1200 associated with improving positioning accuracy through crowdsourcing, in accordance with aspects of the present disclosure. In some particular implementations, Figure 12 one or more of the process blocks of Figure 12 may be performed by a wireless device (e.g., UE 104, AP 150). In some particular implementations, Figure 12 one or more of the process blocks of

[0197] As Figure 12 shown, process 1200 may include determining a set of weights to be applied to positioning information sources (block 1210). The components for performing the operations of block 1210 may include the processor 332, the memory 340, or the WWAN transceiver 310 of UE 302. For example, UE 302 may use the processor 332 to determine a set of weights to be applied to positioning information sources.

[0198] As Figure 12 further shown, process 1200 may include sending the set of weights to one or more other UEs (block 1220). The components for performing the operations of block 1220 may include the processor 332, the memory 340, or the WWAN transceiver 310 of UE 302. For example, UE 302 may use a transmitter to send the set of weights to one or more other UEs.

[0199] In some aspects, determining the set of weights to be applied to positioning information sources includes receiving the set of weights as auxiliary data.

[0200] In some aspects, sending the set of weights to the one or more other UEs includes sending the set of weights in a sensor data sharing message (SDSM) or a vehicle-to-everything (V2X) message.

[0201] In some aspects, sending the set of weights to the one or more other UEs includes sending the set of weights to a server that will send the set of weights to the one or more other UEs.

[0202] In some aspects, process 1200 includes: receiving information identifying a first positioning information source as a possible cause or source of positioning error; updating a weight to be applied to the first positioning information source; and sending a set of the updated weights to the one or more other UEs.

[0203] Process 1200 may include additional embodiments, such as any individual embodiment or any combination of embodiments of one or more other processes described below and / or in combination with other places herein. Although Figure 12 example boxes of process 1200 are shown, in some embodiments, process 1200 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner compared to those Figure 12 depicted. Additionally or alternatively, two or more boxes of process 1200 may be executed in parallel.

[0204] As will be appreciated, a technical advantage of the methods described herein is that crowdsourcing provides a larger amount of data from which inferences about possible sources of positioning error can be drawn, and provides a mechanism by which network devices can directly benefit from that amount of data. Benefits include, but are not limited to, the ability to identify positioning misbehavior and correct or mitigate such behavior, and to verify positioning estimates in a secure manner, e.g., by potentially leveraging a trusted group of other devices for verification.

[0205] In the above detailed description, it can be seen that different features are grouped together in the examples. This manner of disclosure should not be construed as intending that the example clauses have more features than those explicitly mentioned in each clause. Rather, various aspects of the present disclosure may include fewer than all of the features of the disclosed individual example clauses. Accordingly, the following clauses are hereby incorporated into the description, where each clause may stand on its own as a separate example. Although each dependent clause may refer in the clause to a particular combination with one of the other clauses, the aspect of that dependent clause is not limited to the particular combination. It should be understood that other example clauses may also include combinations of the aspects of the dependent clause with the subject matter of any other dependent clause or independent clause, or any feature with other dependent clauses and independent clauses. The various aspects disclosed herein expressly include these combinations, unless explicitly stated or readily inferable as not intended to use a particular combination (e.g., conflicting aspects, such as defining an element as both an electrical insulator and an electrical conductor). Additionally, it is also contemplated that aspects of the clauses may be included in any other independent clause, even if the clause does not directly depend on the independent clause.

[0206] Specific example embodiments are described in the following numbered clauses:

[0207] Clause 1. A method for wireless communication performed by a first wireless device, the method comprising: receiving a first message from a second wireless device, the first message including an advertised location of the second wireless device; determining an estimated location of the second wireless device; detecting a difference between the advertised location of the second wireless device and the estimated location of the second wireless device; and transmitting a second message to at least one other wireless device, the second message indicating the existence of a difference between the advertised location of the second wireless device and the estimated location of the second wireless device.

[0208] Clause 2. The method according to Clause 1, wherein receiving the first message includes receiving a Basic Safety Message (BSM) or a Sensor Data Sharing Message (SDSM).

[0209] Clause 3. The method according to any one of Clauses 1 to 2, wherein determining the estimated location of the second wireless device includes determining the estimated location of the second wireless device based on a positioning operation involving the second wireless device.

[0210] Clause 4. The method according to any one of Clauses 1 to 3, wherein determining the estimated location of the second wireless device includes receiving an indication of the estimated location of the second wireless device from another wireless device, a base station, or a network entity.

[0211] Clause 5. The method according to any one of Clauses 1 to 4, wherein the first message includes an indication of transmit power and is received at a received power, and wherein determining the estimated location of the second wireless device includes calculating a first estimated distance between the first wireless device and the second wireless device based on a difference between the transmit power of the first message and the received power of the first message.

[0212] Clause 6. The method according to Clause 5, wherein detecting the difference between the advertised location of the second wireless device and the estimated location of the second wireless device includes: calculating a second estimated distance between the first wireless device and the second wireless device based on the advertised location of the first wireless device and the current location of the second wireless device; and detecting a mismatch between the first estimated distance and the second estimated distance.

[0213] Clause 7. The method according to any one of Clauses 1 to 6, wherein reporting the existence of a difference between the advertised location of the second wireless device and the estimated location of the second wireless device to the at least one wireless device includes reporting the difference to the second wireless device.

[0214] Clause 8. The method according to any one of Clauses 1 to 7, wherein reporting the difference between the announced location of the second wireless device and the estimated location of the second wireless device to the at least one wireless device includes at least one of the following: reporting the announced location of the second wireless device and the estimated location of the second wireless device; indicating the method for determining the estimated location; indicating a confidence value of the accuracy of the estimated location; or identifying at least one positioning anchor as a potential source or cause of the difference.

[0215] Clause 9. The method according to any one of Clauses 1 to 8, wherein transmitting the second message to at least one other wireless device includes transmitting the second message via a third entity that collects, filters, or aggregates messages.

[0216] Clause 10. A method of wireless communication performed by a first wireless device, the method including: sending a first message that includes the announced location of the first wireless device; and receiving a second message from a second wireless device, the second message indicating a difference between the announced location of the first wireless device and the estimated location of the first wireless device.

[0217] Clause 11. The method according to Clause 10, the method further including verifying the accuracy of the announced location of the first wireless device.

[0218] Clause 12. The method according to Clause 11, wherein verifying the accuracy of the announced location of the first wireless device includes performing a positioning operation to determine the current location of the first wireless device and comparing the announced location of the first wireless device with the current location of the first wireless device.

[0219] Clause 13. The method according to any one of Clauses 11 to 12, the method further including: when determining that the announced location of the first wireless device is accurate, notifying the second wireless device that the announced location of the first wireless device is accurate; and when determining that the announced location of the first wireless device is inaccurate, notifying the second wireless device that the announced location of the first wireless device is inaccurate.

[0220] Clause 14. The method according to any one of Clauses 11 to 13, wherein, when determining that the announced location of the first wireless device is inaccurate, performing a positioning operation to determine the current location of the first wireless device and sending a third message that includes the current location of the first wireless device as the announced location of the first wireless device.

[0221] Clause 15. A method according to any one of clauses 10 to 14, further comprising not verifying the accuracy of the advertised location of the first wireless device unless a threshold number of other wireless devices indicate or have indicated that there is a difference between the advertised location of the first wireless device and the estimated location of the first wireless device.

[0222] Clause 16. A method according to any one of clauses 10 to 15, wherein the second message includes information identifying at least one positioning anchor point as a potential source or cause of the discrepancy, and wherein the method further comprises excluding the at least one positioning anchor point from the positioning operation.

[0223] Clause 17. A method according to any one of clauses 10 to 16, the method further comprising sending to the second wireless device a list of other wireless devices that have not indicated to the first wireless device that there is a difference between the advertised position of the first wireless device and the estimated position of the first wireless device.

[0224] Clause 18. The method of any of clauses 10 to 17, wherein receiving the second message comprises receiving the second message from the second wireless device via a third entity that collects, filters, or aggregates messages.

[0225] Clause 19. A method of wireless communication performed by a network entity, the method comprising: monitoring a network for positioning-related messages; and detecting positioning misconduct based on content of the positioning-related messages.

[0226] Clause 20. The method of clause 19, further comprising initiating a positioning operation by at least one network device, wherein monitoring the network for positioning-related messages comprises monitoring the network for messages related to the positioning operation initiated by the network entity.

[0227] Clause 21. A method according to any one of clauses 19 to 20, wherein detecting positioning misbehavior includes identifying a first set of network devices that are potential sources or causes of positioning errors, identifying a second set of network devices that are not potential sources or causes of positioning errors, or identifying both the first set and the second set.

[0228] Clause 22. A method according to clause 21, wherein identifying the first set of network devices that are potential sources or causes of positioning errors includes: identifying the network device that receives notification of a difference between the advertised position of the network device and the estimated position of the network device; or identifying the network device involved in one or more positioning operations, wherein the one or more positioning operations result in notification of a difference between the advertised position of the network device and the estimated position of the network device.

[0229] Clause 23. The method according to any one of Clauses 21 to 22, wherein the first set of network devices identifying a potential source or cause of a positioning error comprises receiving, from a network device, a message identifying one or more network devices as a potential source or cause of a positioning error.

[0230] Clause 24. The method according to any one of Clauses 21 to 23, the method further comprising sending a message identifying the first set of network devices, the second set of network devices, or both.

[0231] Clause 25. The method according to any one of Clauses 19 to 24, the method further comprising sending positioning information from a message related to a positioning for which no positioning misbehavior has been detected.

[0232] Clause 26. A method of wireless communication performed by a wireless device, the method comprising: determining a set of weights to be applied to a positioning information source; and sending the set of weights to one or more other wireless devices.

[0233] Clause 27. The method according to Clause 26, wherein determining the set of weights to be applied to the positioning information source comprises receiving the set of weights as auxiliary data.

[0234] Clause 28. The method according to any one of Clauses 26 to 27, wherein sending the set of weights to the one or more other wireless devices comprises sending the set of weights in a sensor data sharing message (SDSM) or a vehicle-to-everything (V2X) message.

[0235] Clause 29. The method according to any one of Clauses 26 to 28, wherein sending the set of weights to the one or more other wireless devices comprises sending the set of weights to a server, the server sending the set of weights to the one or more other wireless devices.

[0236] Clause 30. The method according to any one of Clauses 26 to 29, the method further comprising: receiving information identifying a first positioning information source as a possible cause or source of a positioning error; updating the weights to be applied to the first positioning information source; and sending the updated set of weights to the one or more other wireless devices.

[0237] Clause 31. A first wireless device, the first wireless device 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 message from a second wireless device via the at least one transceiver, the first message including an advertised location of the second wireless device; determine an estimated location of the second wireless device; detect a difference between the advertised location of the second wireless device and the estimated location of the second wireless device; and transmit a second message via the at least one transceiver to at least one other wireless device, the second message indicating the existence of a difference between the advertised location of the second wireless device and the estimated location of the second wireless device.

[0238] Clause 32. The first wireless device according to Clause 31, wherein, in order to receive the first message, the at least one processor is configured to receive a Basic Safety Message (BSM) or a Sensor Data Sharing Message (SDSM).

[0239] Clause 33. The first wireless device according to any one of Clauses 31 to 32, wherein, in order to determine the estimated location of the second wireless device, the at least one processor is configured to determine the estimated location of the second wireless device based on a positioning operation involving the second wireless device.

[0240] Clause 34. The first wireless device according to any one of Clauses 31 to 33, wherein, in order to determine the estimated location of the second wireless device, the at least one processor is configured to receive an indication of the estimated location of the second wireless device from another wireless device, a base station, or a network entity.

[0241] Clause 35. The first wireless device according to any one of Clauses 31 to 34, wherein the first message includes an indication of transmit power and is received at a received power, and wherein determining the estimated location of the second wireless device includes calculating a first estimated distance between the first wireless device and the second wireless device based on a difference between the transmit power of the first message and the received power of the first message.

[0242] Clause 36. The first wireless device according to Clause 35, wherein, in order to detect the difference between the advertised location of the second wireless device and the estimated location of the second wireless device, the at least one processor is configured to: calculate a second estimated distance between the first wireless device and the second wireless device based on the advertised location of the first wireless device and the current location of the second wireless device; and detect a mismatch between the first estimated distance and the second estimated distance.

[0243] Clause 37. The first wireless device according to any one of Clauses 31 to 36, wherein, in order to report to the at least one wireless device the difference between the announced location of the second wireless device and the estimated location of the second wireless device, the at least one processor is configured to report the difference to the second wireless device.

[0244] Clause 38. The first wireless device according to any one of Clauses 31 to 37, wherein, in order to report to the at least one wireless device the difference between the announced location of the second wireless device and the estimated location of the second wireless device, the at least one processor is configured to: report the announced location of the second wireless device and the estimated location of the second wireless device; indicate the method for determining the estimated location; indicate a confidence value of the accuracy of the estimated location; or identify at least one positioning anchor as a potential source or cause of the difference.

[0245] Clause 39. The first wireless device according to any one of Clauses 31 to 38, wherein, in order to transmit the second message to at least one other wireless device, the at least one processor is configured to transmit the second message via a third entity that collects, filters, or aggregates messages.

[0246] Clause 40. A first wireless device, the first wireless device comprising: a memory; at least one transceiver; and at least one processor, the at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: send, via the at least one transceiver, a first message that includes the announced location of the first wireless device; and receive, via the at least one transceiver, a second message from a second wireless device, the second message indicating a difference between the announced location of the first wireless device and the estimated location of the first wireless device.

[0247] Clause 41. The first wireless device according to Clause 40, wherein the at least one processor is further configured to verify the accuracy of the announced location of the first wireless device.

[0248] Clause 42. The first wireless device according to Clause 41, wherein, in order to verify the accuracy of the announced location of the first wireless device, the at least one processor is configured to perform a positioning operation to determine the current positioning of the first wireless device and compare the announced location of the first wireless device with the current positioning of the first wireless device.

[0249] Clause 43. The first wireless device according to any one of Clauses 41 to 42, wherein the at least one processor is further configured to: notify the second wireless device that the advertised location of the first wireless device is accurate when determining that the advertised location of the first wireless device is accurate; and notify the second wireless device that the advertised location of the first wireless device is inaccurate when determining that the advertised location of the first wireless device is inaccurate.

[0250] Clause 44. The first wireless device according to any one of Clauses 41 to 43, wherein when determining that the advertised location of the first wireless device is inaccurate, a positioning operation is performed to determine the current positioning of the first wireless device, and a third message is sent, the third message including the current positioning of the first wireless device as the advertised location of the first wireless device.

[0251] Clause 45. The first wireless device according to any one of Clauses 40 to 44, wherein the at least one processor is further configured not to verify the accuracy of the advertised location of the first wireless device unless a threshold number of other wireless devices indicate or have indicated a difference between the advertised location of the first wireless device and the estimated location of the first wireless device.

[0252] Clause 46. The first wireless device according to any one of Clauses 40 to 45, wherein the second message includes information identifying at least one positioning anchor as a potential source or cause of the difference, and wherein the method further includes excluding the at least one positioning anchor from the positioning operation.

[0253] Clause 47. The first wireless device according to any one of Clauses 40 to 46, wherein the at least one processor is further configured to send, via the at least one transceiver, a list of other wireless devices that have not indicated to the first wireless device the existence of a difference between the advertised location of the first wireless device and the estimated location of the first wireless device to the second wireless device.

[0254] Clause 48. The first wireless device according to any one of Clauses 40 to 47, wherein, in order to receive the second message, the at least one processor is configured to receive the second message from the second wireless device via a third entity that collects, filters, or aggregates messages.

[0255] Clause 49. A network entity, the network entity comprising: a memory; at least one transceiver; and at least one processor, the at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: monitor the network for location-related messages; and detect positioning misbehavior based on the content of the location-related messages.

[0256] Clause 50. The network entity according to clause 49, wherein the at least one processor is further configured to initiate a positioning operation through at least one network device, and wherein monitoring the network for location-related messages includes monitoring the network for messages related to the positioning operation initiated by the network entity.

[0257] Clause 51. The network entity according to any one of clauses 49 to 50, wherein, in order to detect positioning misbehavior, the at least one processor is configured to identify a first set of network devices that are potential sources or causes of positioning errors, identify a second set of network devices that are not potential sources or causes of positioning errors, or identify both the first set and the second set.

[0258] Clause 52. The network entity according to clause 51, wherein, in order to identify the first set of network devices that are potential sources or causes of positioning errors, the at least one processor is configured to: identify the network devices that receive notifications of the difference between the advertised location of the network device and the estimated location of the network device; or identify the network devices involved in one or more positioning operations that result in notifications of the difference between the advertised location of the network device and the estimated location of the network device.

[0259] Clause 53. The network entity according to any one of clauses 51 to 52, wherein, in order to identify the first set of network devices that are potential sources or causes of positioning errors, the at least one processor is configured to receive from the network devices messages identifying one or more network devices that are potential sources or causes of positioning errors.

[0260] Clause 54. The network entity according to any one of clauses 51 to 53, wherein the at least one processor is further configured to send, via the at least one transceiver, a message identifying the first set of network devices, the second set of network devices, or both.

[0261] Clause 55. The network entity according to any one of clauses 49 to 54, wherein the at least one processor is further configured to send, via the at least one transceiver, positioning information from location-related messages for which no positioning misbehavior has been detected.

[0262] Clause 56. A wireless device, the wireless device comprising: a memory; at least one transceiver; and at least one processor, the at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determine a set of weights to be applied to a positioning information source; and transmit the set of weights to one or more other wireless devices via the at least one transceiver.

[0263] Clause 57. The wireless device according to Clause 56, wherein, in order to determine the set of weights to be applied to the positioning information source, the at least one processor is configured to receive the set of weights as auxiliary data.

[0264] Clause 58. The wireless device according to any one of Clauses 56 to 57, wherein, in order to transmit the set of weights to the one or more other wireless devices, the at least one processor is configured to transmit the set of weights in a sensor data sharing message (SDSM) or a vehicle-to-everything (V2X) message.

[0265] Clause 59. The wireless device according to any one of Clauses 56 to 58, wherein, in order to transmit the set of weights to the one or more other wireless devices, the at least one processor is configured to transmit the set of weights to a server, and the server will transmit the set of weights to the one or more other wireless devices.

[0266] Clause 60. The wireless device according to any one of Clauses 56 to 59, wherein the at least one processor is further configured to: receive, via the at least one transceiver, information identifying a first positioning information source as a possible cause or source of positioning error; update the weight to be applied to the first positioning information source; and transmit, via the at least one transceiver, the updated set of weights to the one or more other wireless devices.

[0267] Clause 61. A device, the device comprising: a memory; a transceiver; and a processor, the processor communicatively coupled to the memory and the transceiver, the memory, the transceiver and the processor being configured to execute the method according to any one of Clauses 1 to 30.

[0268] Clause 62. A device, the device comprising components for performing the method according to any one of Clauses 1 to 30.

[0269] Clause 63. A non-transitory computer-readable medium, the non-transitory computer-readable medium storing computer-executable instructions, the computer-executable including at least one instruction for causing a computer or a processor to execute the method according to any one of Clauses 1 to 30.

[0270] Those skilled in the art should understand that information and signals can be represented using any of a variety of different technologies and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may have been mentioned throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0271] In addition, those skilled in the art should understand that the various illustrative logical blocks, modules, circuits, and algorithmic steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in different ways for each particular application, but such specific implementation decisions should not be construed as causing a departure from the scope of the present disclosure.

[0272] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein can 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 can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0273] The methods, sequences, and / or algorithms described in connection with the aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of both. The software module can 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 the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal (e.g., a UE). In the alternative, the processor and the storage medium can reside as discrete components in a user terminal.

[0274] In one or more example aspects, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. The storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc where disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0275] While the foregoing disclosure shows illustrative aspects of the present disclosure, it should be noted that various changes and modifications can be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps, and / or acts of the method claims according to aspects of the present disclosure described herein need not be performed in any particular order. Moreover, although elements of the present disclosure may be described or claimed in the singular, the plural is also contemplated unless expressly stated to be limited to the singular.

Claims

1. A method of wireless communication performed by a first wireless device, the method comprising: Receiving a first message from a second wireless device, the first message including an advertised location of the second wireless device; Determining an estimated location of the second wireless device; Detecting a difference between the advertised location of the second wireless device and the estimated location of the second wireless device; And Transmitting a second message to at least one other wireless device, the second message indicating the existence of a difference between the advertised location of the second wireless device and the estimated location of the second wireless device.

2. The method according to claim 1, wherein receiving the first message includes receiving a Basic Safety Message (BSM) or a Sensor Data Sharing Message (SDSM).

3. The method according to claim 1, wherein determining the estimated location of the second wireless device includes determining the estimated location of the second wireless device based on a positioning operation involving the second wireless device.

4. The method according to claim 1, wherein determining the estimated location of the second wireless device includes receiving an indication of the estimated location of the second wireless device from another wireless device, a base station, or a network entity.

5. The method according to claim 1, wherein the first message includes an indication of transmit power and is received in terms of received power, and wherein determining the estimated location of the second wireless device includes calculating a first estimated distance between the first wireless device and the second wireless device based on a difference between the transmit power of the first message and the received power of the first message.

6. The method according to claim 5, wherein detecting the difference between the advertised location of the second wireless device and the estimated location of the second wireless device includes: Calculating a second estimated distance between the first wireless device and the second wireless device based on the advertised location of the first wireless device and the current location of the second wireless device; And Detecting that the first estimated distance and the second estimated distance do not match.

7. The method according to claim 1, wherein reporting the existence of a difference between the advertised location of the second wireless device and the estimated location of the second wireless device to the at least one wireless device includes reporting the difference to the second wireless device.

8. The method according to claim 1, wherein reporting the existence of a difference between the advertised location of the second wireless device and the estimated location of the second wireless device to the at least one wireless device includes at least one of the following: Reporting the advertised location of the second wireless device and the estimated location of the second wireless device; Indicating the method used to determine the estimated location; Indicating a confidence value of the accuracy of the estimated location; or Identifying at least one positioning anchor as a potential source or cause of the difference.

9. The method according to claim 1, wherein transmitting the second message to at least one other wireless device includes transmitting the second message via a third entity that collects, filters, or aggregates messages.

10. A method of wireless communication performed by a first wireless device, the method comprising: Sending a first message, the first message including an advertised location of the first wireless device; And Receiving a second message from a second wireless device, the second message indicating a difference between the advertised location of the first wireless device and an estimated location of the first wireless device.

11. The method according to claim 10, the method further comprising verifying an accuracy of the advertised location of the first wireless device.

12. The method according to claim 11, wherein verifying the accuracy of the advertised location of the first wireless device includes performing a positioning operation to determine a current positioning of the first wireless device, and comparing the advertised location of the first wireless device with the current positioning of the first wireless device.

13. The method according to claim 11, the method further comprising: When determining that the advertised location of the first wireless device is accurate, notifying the second wireless device that the advertised location of the first wireless device is accurate; And When determining that the advertised location of the first wireless device is inaccurate, notifying the second wireless device that the advertised location of the first wireless device is inaccurate.

14. The method according to claim 11, wherein, When determining that the advertised location of the first wireless device is inaccurate, performing a positioning operation to determine a current positioning of the first wireless device, and sending a third message, the third message including the current positioning of the first wireless device as the advertised location of the first wireless device.

15. The method according to claim 10, the method further comprising not verifying the accuracy of the advertised location of the first wireless device unless a threshold number of other wireless devices indicate or have indicated a difference between the advertised location of the first wireless device and an estimated location of the first wireless device.

16. The method according to claim 10, wherein the second message includes information identifying at least one positioning anchor as a potential source or cause of the difference, and wherein the method further comprises excluding the at least one positioning anchor from a positioning operation.

17. The method according to claim 10, the method further comprising sending to the second wireless device a list of other wireless devices that have not indicated to the first wireless device a difference between the advertised location of the first wireless device and an estimated location of the first wireless device.

18. The method according to claim 10, wherein receiving the second message includes receiving the second message from the second wireless device via a third entity that collects, filters or aggregates messages.

19. A method of wireless communication performed by a network entity, the method comprising: Monitoring a network for messages related to positioning; And Detecting positioning misbehavior based on content of the messages related to positioning.

20. The method according to claim 19, the method further comprising initiating a positioning operation by at least one network device, wherein monitoring the network for messages related to positioning comprises monitoring the network for messages related to the positioning operation initiated by the network entity.

21. The method according to claim 19, wherein detecting positioning misbehavior comprises identifying a first set of network devices that are potential sources or causes of positioning errors, identifying a second set of network devices that are not potential sources or causes of positioning errors, or identifying both the first set and the second set.

22. The method according to claim 21, wherein identifying the first set of network devices that are potential sources or causes of positioning errors comprises: identifying the network devices that receive notifications of the difference between the advertised location of the network device and the estimated location of the network device; or identifying the network devices involved in one or more positioning operations that result in notifications of the difference between the advertised location of the network device and the estimated location of the network device.

23. The method according to claim 21, wherein identifying the first set of network devices that are potential sources or causes of positioning errors comprises receiving from a network device a message identifying one or more network devices that are potential sources or causes of positioning errors.

24. The method according to claim 21, the method further comprising sending a message identifying the first set of network devices, the second set of network devices, or both.

25. The method according to claim 19, the method further comprising sending positioning information from messages related to positioning for which no positioning misbehavior has been detected.

26. A method of wireless communication performed by a wireless device, the method comprising: determining a set of weights to be applied to a positioning information source; and sending the set of weights to one or more other wireless devices.

27. The method according to claim 26, wherein determining the set of weights to be applied to the positioning information source comprises receiving the set of weights as auxiliary data.

28. The method according to claim 26, wherein sending the set of weights to the one or more other wireless devices comprises sending the set of weights in a sensor data sharing message (SDSM) or a vehicle-to-everything (V2X) message.

29. The method according to claim 26, wherein sending the set of weights to the one or more other wireless devices comprises sending the set of weights to a server, and the server will send the set of weights to the one or more other wireless devices.

30. The method according to claim 26, the method further comprising: receiving information identifying a first positioning information source as a possible cause or source of a positioning error; updating the weight to be applied to the first positioning information source; and sending the updated set of weights to the one or more other wireless devices.

31. A first wireless device, the first wireless device comprising: a memory; at least one transceiver; and At least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: Receive, via the at least one transceiver, a first message from a second wireless device, the first message including an advertised location of the second wireless device; Determine an estimated location of the second wireless device; Detect a difference between the advertised location of the second wireless device and the estimated location of the second wireless device; And Transmit, via the at least one transceiver, a second message to at least one other wireless device, the second message indicating the existence of a difference between the advertised location of the second wireless device and the estimated location of the second wireless device.

32. The first wireless device according to claim 31, wherein, To receive the first message, the at least one processor is configured to receive a Basic Safety Message (BSM) or a Sensor Data Sharing Message (SDSM).

33. The first wireless device according to claim 31, wherein, To determine the estimated location of the second wireless device, the at least one processor is configured to determine the estimated location of the second wireless device based on a positioning operation involving the second wireless device, or receive an indication of the estimated location of the second wireless device from another wireless device, a base station, or a network entity.

34. The first wireless device according to claim 31, wherein the first message includes an indication of transmit power and is received in terms of received power, and wherein determining the estimated location of the second wireless device includes calculating a first estimated distance between the first wireless device and the second wireless device based on a difference between the transmit power of the first message and the received power of the first message.

35. A first wireless device, the first wireless device comprising: A memory; At least one transceiver; And At least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: Transmit, via the at least one transceiver, a first message including an advertised location of the first wireless device; And Receive, via the at least one transceiver, a second message from a second wireless device, the second message indicating the existence of a difference between the advertised location of the first wireless device and the estimated location of the first wireless device.

36. The first wireless device according to claim 35, wherein the at least one processor is further configured to verify the accuracy of the advertised location of the first wireless device.

37. The first wireless device according to claim 35, wherein the at least one processor is further configured not to verify the accuracy of the advertised location of the first wireless device unless a threshold number of other wireless devices indicate or have indicated the existence of a difference between the advertised location of the first wireless device and the estimated location of the first wireless device.

38. The first wireless device according to claim 35, wherein the second message includes information identifying at least one positioning anchor as a potential source or cause of the difference, and wherein the method further includes excluding the at least one positioning anchor from the positioning operation.

39. A network entity, the network entity 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: monitor the network for location-related messages; and detect positioning misbehavior based on the content of the location-related messages.

40. The network entity according to claim 39, wherein the at least one processor is further configured to initiate a positioning operation via at least one network device, and wherein monitoring the network for location-related messages includes monitoring the network for messages related to the positioning operation initiated by the network entity.

41. The network entity according to claim 39, wherein, To detect positioning misbehavior, the at least one processor is configured to identify a first set of network devices that are potential sources or causes of positioning errors, identify a second set of network devices that are not potential sources or causes of positioning errors, or identify both the first set and the second set.

42. The network entity according to claim 39, wherein the at least one processor is further configured to transmit, via the at least one transceiver, positioning information from location-related messages for which no positioning misbehavior has been detected.

43. A wireless device, the wireless device 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: determine a set of weights to be applied to a source of positioning information; and transmit, via the at least one transceiver, the set of weights to one or more other wireless devices.

44. The wireless device according to claim 43, wherein, To determine the set of weights to be applied to the source of positioning information, the at least one processor is configured to receive the set of weights as auxiliary data.

45. The wireless device according to claim 43, wherein, To transmit the set of weights to the one or more other wireless devices, the at least one processor is configured to transmit the set of weights in a sensor data sharing message (SDSM) or a vehicle-to-everything (V2X) message, or transmit the set of weights to a server that will transmit the set of weights to the one or more other wireless devices.

Images