Sidelink positioning anchor user equipment selection criteria

Abstract

Systems and techniques for wireless communication are disclosed. For example, a first network device can receive, from a plurality of second network devices, a corresponding anchor selection criterion for each of the plurality of second network devices. The first network device can determine a network device from the plurality of second network devices as an anchor device for determining the location of the first network device based on the corresponding anchor selection criterion for each of the plurality of second network devices. The first network device can determine the location of the first network device based on the anchor device.

Description

Technical Field

[0001] This disclosure relates to wireless communications in general. For example, aspects of this disclosure relate to sidelink (SL) anchor user equipment (UE) selection criteria. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0003] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CWB) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. Various aspects of wireless communication can include direct communication between devices, such as in V2X, vehicle-to-vehicle (V2V), and / or device-to-device (D2D) communications. There is a need for further improvements to V2X, V2V, and / or D2D technologies. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0004] The following is a simplified summary of the invention relating to one or more aspects disclosed herein. Therefore, this summary should not be considered an exhaustive overview relating to all conceived aspects, nor should it be considered to identify key or decisive elements relating to all conceived aspects or to depict the scope associated with any particular aspect. Thus, the sole purpose of this summary is to present, in a concise form, certain concepts relating to one or more aspects involving the mechanisms disclosed herein, prior to the detailed description presented below.

[0005] Systems, apparatuses, methods, and computer-readable media for selecting anchor UEs for SL positioning are disclosed. According to some aspects, a first network device for wireless communication is provided. The first network device includes at least one memory and at least one processor coupled to the at least one memory and configured to: receive from a plurality of second network devices a corresponding anchor selection criterion for each of the plurality of second network devices; determine a network device from the plurality of second network devices as an anchor device for determining the location of the first network device based on the corresponding anchor selection criterion for each of the plurality of second network devices; and determine the location of the first network device based on the anchor device.

[0006] In some aspects, a method for wireless communication performed at a first network device is provided. The method includes: receiving, by the first network device, a corresponding anchor selection criterion for each of the plurality of second network devices from a plurality of second network devices; determining, by the first network device, a network device from the plurality of second network devices as an anchor device for determining the location of the first network device based on the corresponding anchor selection criterion for each of the plurality of second network devices; and determining the location of the first network device based on the anchor device.

[0007] In some aspects, an apparatus for wireless communication is provided. The apparatus includes: components for receiving from a plurality of second network devices a corresponding anchor selection criterion for each of the plurality of second network devices; components for: determining, based on the corresponding anchor selection criterion for each of the plurality of second network devices, a network device as an anchor device for determining the location of a first network device; and components for determining the location of the first network device based on the anchor device.

[0008] In some aspects, a non-transitory computer-readable medium stores instructions that, when executed by at least one processor, cause the at least one processor to: receive from a plurality of second network devices a corresponding anchor selection criterion for each of the plurality of second network devices; determine from the plurality of second network devices, based on the corresponding anchor selection criterion for each of the plurality of second network devices, a network device as an anchor device for determining the location of a first network device; and determine the location of the first network device based on the anchor device.

[0009] In some aspects, a first network device for wireless communication is provided. The first network device includes at least one memory and at least one processor coupled to the at least one memory and configured to: determine anchor selection criteria for the first network device, wherein the anchor selection criteria for the first network device include at least one of: user equipment (UE) type of the first network device, one or more sources of the location of the first network device, age of the location of the first network device, validity duration of the location of the first network device, accuracy duration of the location of the first network device, or auxiliary data validity of the location of the first network device; and output the anchor selection criteria for transmission to a second network device.

[0010] In some aspects, a method for performing wireless communication at a first network device is provided. The method includes: determining anchor selection criteria for the first network device, wherein the anchor selection criteria for the first network device include at least one of: user equipment (UE) type of the first network device, one or more sources of the location of the first network device, age of the location of the first network device, validity duration of the location of the first network device, accuracy duration of the location of the first network device, or auxiliary data validity of the location of the first network device; and transmitting the anchor selection criteria to a second network device.

[0011] In some aspects, an apparatus for wireless communication is provided. The apparatus includes: components for determining anchor selection criteria for a first network device, wherein the anchor selection criteria for the first network device include at least one of: the user equipment (UE) type of the first network device, one or more sources of the location of the first network device, the age of the location of the first network device, the validity period of the location of the first network device, the accuracy period of the location of the first network device, or the validity of auxiliary data of the location of the first network device; and components for transmitting the anchor selection criteria to a second network device.

[0012] In some aspects, a non-transitory computer-readable medium stores instructions that, when executed by at least one processor, cause the at least one processor to: determine anchor selection criteria for a first network device, wherein the anchor selection criteria for the first network device include at least one of: the user equipment (UE) type of the first network device, one or more sources of the location of the first network device, the age of the location of the first network device, the validity period of the location of the first network device, the accuracy period of the location of the first network device, or the validity of auxiliary data of the location of the first network device; and output the anchor selection criteria for transmission to a second network device.

[0013] The aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices and / or processing systems, as fully described herein with reference to the accompanying drawings and description, and as illustrated in the accompanying drawings and description.

[0014] In some aspects, one or more of the devices described herein are vehicles (e.g., cars, trucks, etc., or components or systems of cars, trucks, etc.), mobile devices (e.g., mobile phones or so-called "smartphones" or other mobile devices), wearable devices, extended reality devices (e.g., virtual reality (VR) devices, augmented reality (AR) devices, or mixed reality (MR) devices), personal computers, laptop computers, server computers, robotic devices, or other devices, or parts thereof. In some aspects, the device includes radio detection and ranging (radar) for capturing radio frequency (RF) signals. In some aspects, each device includes one or more light detection and ranging (LIDAR) sensors, radar sensors, or other light-based sensors for capturing light-based (e.g., light frequency) signals. In some aspects, each device includes one or more cameras for capturing one or more images. In some aspects, each device also includes a display for displaying one or more images, notifications, and / or other displayable data. In some aspects, the device described herein may include one or more sensors that can be used to determine the location of the device, the state of the device (e.g., temperature, humidity level, and / or other states), and / or for other purposes.

[0015] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily utilized as the basis for modifying or designing other structures for achieving the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each drawing provided in the drawings is for illustrative and descriptive purposes and not as a limitation of the definitions in the claims.

[0016] While aspects are described herein by way of example, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user equipment of various sizes, shapes, and configurations.

[0017] Based on the accompanying drawings and detailed description, other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used in isolation to define the scope of the claimed subject matter. This subject matter should be understood with reference to the appropriate portions of the entire specification, any or all of the drawings, and each claim.

[0018] The foregoing and other features and aspects will become more apparent from the following description, claims and accompanying drawings. Attached Figure Description

[0019] The exemplary aspects of this application are described in detail below with reference to the following figures: Figure 1 This is a diagram illustrating an example wireless communication system according to some aspects of this disclosure.

[0020] Figure 2 This is a diagram illustrating an example of a decomposed base station architecture that can be used by the disclosed system to employ SL positioning anchor UE selection criteria, according to some aspects of this disclosure.

[0021] Figure 3 This is an illustration of various user equipment (UEs) communicating through a direct communication interface (e.g., a cellular-based PC5 sidelink interface, an 802.11p-defined DSRC interface, or other direct interfaces) and a wide area network (Uu) interface, according to some aspects of this disclosure.

[0022] Figure 4 This is a block diagram illustrating an example of a computing system for a vehicle according to some aspects of this disclosure.

[0023] Figure 5 This is a block diagram illustrating an example of a computing system for a user device according to some aspects of this disclosure.

[0024] Figure 6 This is an illustration of an example of a device involved in wireless communication (e.g., sidelink communication) according to some aspects of this disclosure.

[0025] Figure 7 This is an illustration of an example system for sidelink localization using candidate anchor UEs, including mobile UEs and stationary UEs, according to some aspects of this disclosure.

[0026] Figure 8 This is an illustration of an example system for sidelink localization using a candidate anchor UE, including a mobile UE, according to some aspects of this disclosure.

[0027] Figure 9 This is a table illustrating examples of criteria for anchor UE selection for sidelink positioning according to some aspects of this disclosure.

[0028] Figure 10 This is an example illustrating some aspects of this disclosure. Figure 9 The table is an example of the definition of the criteria in the table.

[0029] Figure 11A This is a flowchart illustrating an example of a process for wireless communication according to some aspects of this disclosure.

[0030] Figure 11B This is a flowchart illustrating another example of a process for wireless communication according to some aspects of this disclosure.

[0031] Figure 12 This is a block diagram illustrating an example computing system according to various aspects of this disclosure. Detailed Implementation

[0032] Certain aspects of this disclosure are provided below for illustrative purposes. Alternative aspects may be devised without departing from the scope of this disclosure. Additionally, well-known elements of this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure. Some aspects described herein can be applied independently, and some of them can be combined, as will be apparent to those skilled in the art. Specific details are set forth in the following description for purposes of explanation to provide a thorough understanding of various aspects of this application. However, it will be apparent that various aspects can be practiced without these specific details. The figures and descriptions are not intended to be limiting.

[0033] The following description provides only exemplary aspects and is not intended to limit the scope, applicability, or configuration of this disclosure. Rather, the following description of the exemplary aspects will provide those skilled in the art with a description that can be used to implement the exemplary aspects. It should be understood that various changes may be made to the function and arrangement of the elements without departing from the spirit and scope of this application as set forth in the appended claims.

[0034] The terms “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 to or better than other aspects. Similarly, the term “aspects of this disclosure” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed.

[0035] Wireless communication systems are deployed to provide a variety of telecommunications services, including telephone, video, data, messaging, and broadcasting. Wireless communication systems have undergone several generations of development. The 5G mobile standard demands higher data transmission speeds, a greater number of connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard (also known as "New Radio" or "NR") is designed to provide tens of megabits per second of data rate to each of tens of thousands of users.

[0036] Vehicles are examples of devices or systems that may include wireless communication capabilities. For example, vehicles (e.g., motorized vehicles, autonomous vehicles, aircraft, ships, etc.) can communicate with other vehicles and / or other devices with wireless communication capabilities. Wireless vehicle communication systems include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-pedestrian (V2P) communications, which are collectively referred to as vehicle-to-everything (V2X) communications. V2X communications are vehicle communication systems that enable the wireless transmission of information from vehicles to other entities located within the transportation system (e.g., other vehicles, pedestrians with smartphones, and / or other transportation infrastructure).

[0037] In V2X communication systems, information (e.g., location information) can be transmitted wirelessly from vehicle sensors (and other sources) to allow that information to be communicated to other vehicles, pedestrians, and / or traffic infrastructure. This information can be transmitted using one or more vehicle-based messages (such as C-V2X messages), which may include Sensor Data Sharing Messages (SDSM), Basic Safety Messages (BSM), Cooperative Sense Messages (CAM), Collective Sense Messages (CPM), and / or other types of messages. By sharing this information with other vehicles, V2X technology enhances context awareness.

[0038] The IEEE 802.11p standard supports (uses) the Dedicated Short Range Communication (DSRC) interface for V2X wireless communication. Features of the IEEE 802.11p-based DSRC interface include low latency and the use of the unlicensed 5.9 GHz band. Cellular V2X (C-V2X) is an alternative to using the IEEE 802.11p-based DSRC interface for wireless communication. The 5G Automotive Association (5GAA) supports the use of C-V2X technology. In some cases, C-V2X technology uses Long Term Evolution (LTE) as the underlying technology, and C-V2X functionality is based on LTE. C-V2X includes multiple operating modes. One of these operating modes allows direct wireless communication between vehicles via the LTE sidelink PC5 interface. Similar to the IEEE 802.11p-based DSRC interface, the LTE C-V2X sidelink PC5 interface operates in the 5.9 GHz band. Vehicle-based messages (such as BSM and CAM as application layer messages) are designed to be broadcast wirelessly over the 802.11p-based DSRC interface and the LTE C-V2X sidelink PC5 interface.

[0039] Many commercially available vehicles in the United States are equipped with C-V2X communication capabilities to communicate with other vehicles similarly equipped with C-V2X communication capabilities (e.g., sending and / or receiving vehicle-based messages) using a C-V2X sidelink PC5 interface. Some of these vehicles in the United States are also equipped with DSRC communication capabilities to communicate with other vehicles similarly equipped with DSRC communication capabilities (e.g., sending and / or receiving vehicle-based messages) using an 802.11p-based DSRC interface. Therefore, these vehicles with dual communication capabilities are referred to as having heterogeneous C-V2X / DSRC communication capabilities.

[0040] Sidelink-capable UEs (such as vehicles) capable of communicating via the C-V2X sidelink PC5 interface can use 3GPP sidelink ranging and positioning for geolocation (e.g., to obtain their own location). Sidelink ranging is based on measurements of sidelink signals obtained by the UE, such as round-trip time (RTT) and angle of arrival (AoA). Sidelink positioning uses similar measurements but also requires the participation of a fixed UE (e.g., a stationary UE, or a static or fixed mobile UE) that knows its absolute location; this fixed UE is referred to as an "anchor UE" or "anchor." Sidelink-capable UEs can include mobile UEs (e.g., which can sometimes be static or fixed), such as vehicles, mobile phones associated with pedestrians or cyclists, and / or drones. Sidelink-capable UEs can include stationary UEs, such as roadside units (RSUs). If any sidelink-capable UE has established its own location, that sidelink-capable UE can act as an anchor UE. As defined by 3GPP in Release 18, the Side Link Positioning Protocol (SLPP) can be used to establish side link ranging and positioning to identify participating UEs (e.g., candidate anchor UEs), perform session establishment, and exchange measurements and measurement results.

[0041] Currently, the inherent mobility of UEs with sidelink capabilities means that different UEs can know their absolute positions with varying levels of accuracy and can determine their absolute positions using different sources. These different sources can be one or more Global Navigation Satellite System (GNSS) sources, one or more geodetic sources (e.g., for stationary UEs, such as RSUs), one or more sidelink signal sources, one or more wireless network (Uu) signal sources (e.g., cellular network) sources, one or more Uu positioning sources, and / or one or more WiFi positioning sources. Employing multiple sources for positioning allows UEs to achieve greater absolute position accuracy and maintain position knowledge and accuracy over longer time periods.

[0042] When a UE (e.g., the first UE) is selecting another UE (e.g., the second UE, which is a candidate anchor UE) as the anchor UE for sidelink positioning, the UE (e.g., the first UE) preferably selects the UE with the best location accuracy (e.g., the second UE) and the UE most likely to maintain that location accuracy over an extended period of time (e.g., the second UE). Knowing the following enables the sidelink positioning UE (e.g., the first UE) to select the most suitable UE (e.g., the second UE) as the anchor UE: how the UE (e.g., the second UE, which is a candidate anchor UE) has determined its location (e.g., by comparing the use of a single source with the use of multiple sources), how long the location has been established, how long the UE (e.g., the second UE) expects the location to be known, the accuracy of the location, and the UE type (e.g., a static or fixed stationary UE, or a mobile UE).

[0043] Currently in 3GPP, the SLPP procedure allows UEs (e.g., candidate anchor UEs) to provide indications of whether they can act as anchor UEs and the accuracy of their location. However, the SLPP procedure currently does not allow UEs to provide indications of their UE type (e.g., stationary UE or mobile UE), how their location was established, and the duration for which their location is expected to be valid.

[0044] In some cases, when the anchor UE's location knowledge and / or location accuracy degrades or is lost, the anchor UE can continue transmitting to avoid losing over-the-air (OTA) transmission resources. Currently, in 3GPP, the SLPP procedure does not support signaling via SLPP (e.g., via flags) indicating that auxiliary data should currently be ignored even though the anchor UE is continuing to transmit. Therefore, improved techniques for providing a more comprehensive list of sidelink positioning anchor UE selection criteria (e.g., including candidate anchor UE types, how candidate anchor UE locations are established, the expected validity period of candidate anchor UE locations, and anchor UE indications including invalid and / or outdated auxiliary information) could be beneficial.

[0045] In some aspects of this disclosure, systems, apparatus, methods (also referred to as processes), and computer-readable media (collectively referred to herein as “systems and techniques”) are described for providing sidelink positioning anchor UE selection criteria.

[0046] The various aspects as a whole involve wireless communication. Some aspects more specifically involve providing anchor UE selection criteria for sidelink positioning via wireless communication. In some examples, candidate anchor UEs (e.g., stationary or mobile UEs) can provide their ability to act as anchor UEs for sidelink positioning and their positioning accuracy. In order for a sidelink-capable UE to be able to select the best candidate anchor UE for sidelink positioning, the sidelink-capable UE can benefit from receiving additional information about the candidate anchor UEs. In one or more examples, the system and technology provide signaling mechanisms for the candidate anchor UEs to provide the sidelink-capable UE with a comprehensive list of anchor UE selection criteria for sidelink positioning (e.g., a comprehensive list of information about the candidate anchor UEs). In some examples, a comprehensive list of anchor UE selection criteria may include information about candidate anchor UEs, such as indications of the candidate anchor UE's location, the UE type of the candidate anchor UE (e.g., stationary UE or mobile UE), how long the candidate anchor UE's location has been established (e.g., the age of the candidate anchor UE's location), the expected validity period of the candidate anchor UE's location (e.g., the validity period of the candidate anchor UE's location), how the candidate anchor UE's location was established (e.g., one or more sources used to obtain the candidate anchor UE's location), the source diversity of the candidate anchor UE's location, the accuracy period of the candidate anchor UE's location, and / or the validity of the auxiliary data provided by the candidate anchor UE (e.g., the validity of the auxiliary data for the candidate anchor UE's location data). Using these anchor UE selection criteria enables a UE with sidelink capabilities to select (e.g., from candidate anchor UEs) one or more anchor UEs best suited for sidelink positioning transactions.

[0047] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by employing the disclosed signaling mechanism to provide a comprehensive list of anchor UE selection criteria, the described techniques can be used by a sidelink-capable UE to identify the optimal anchor UE for sidelink positioning. By employing the optimal anchor UE for sidelink positioning, a sidelink-capable UE can obtain its own more accurate location with improved sidelink positioning performance.

[0048] Additional aspects of this disclosure are described in more detail below.

[0049] As used herein, the terms “User Equipment” (UE) and “Network Entity” are not intended to be specific to or otherwise limited to any particular Radio Access Technology (RAT) unless otherwise specified. In general, a UE can be any wireless communication device (e.g., mobile phone, router, tablet computer, laptop computer, and / or tracking device, etc.), wearable device (e.g., smartwatch, smart glasses, wearable ring, and / or extended reality (XR) device (such as virtual reality (VR) headset, augmented reality (AR) headset or glasses, or mixed reality (MR) headset)), vehicle (e.g., car, motorcycle, bicycle, etc.), and / or Internet of Things (IoT) device, etc., for a user to communicate over a wireless communication network. A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term "UE" may be interchangeably referred to as "access terminal" or "AT," "client device," "wireless device," "subscriber device," "subscriber terminal," "subscriber station," "user terminal," or "UT," "mobile device," "mobile terminal," "mobile station," or variations thereof. Generally, a UE can communicate with the core network via the RAN, and through the core network, the UE can connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through wired access networks, wireless local area network (WLAN) networks (e.g., based on the IEEE 802.11 communication standard), etc.

[0050] In some cases, network entities may be implemented in aggregated or monolithic base station or server architectures, or alternatively, in decomposed base station or server architectures, and may include one or more of a central unit (CU), distributed unit (DU), radio unit (RU), near real-time (near RT) RAN intelligent controller (RIC), or non-real-time (non-RT) RIC. In some cases, network entities may include server equipment, such as multi-access edge computing (MEC) equipment. A base station or server (e.g., having an aggregated / monolithic or decomposed base station architecture) may operate according to one of several RATs based on the network in which the base station or server is deployed to communicate with the UE, roadside unit (RSU), and / or other equipment, and may alternatively be referred to as an access point (AP), network node, node B (NB), evolved node B (eNB), next-generation eNB (ng-eNB), new radio (NR) node B (also referred to as gNB or gNodeB), etc. Base stations are primarily used to support the radio access of the UE, including supporting data, voice, and / or signaling connections for the supported UE. In some systems, the base station can provide edge node signaling functions, while in others, it can provide additional control and / or network management functions. The communication links through which the UE can transmit signals to the base station are called uplink (UL) channels (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication links through which the base station can transmit signals to the UE are called downlink (DL) or forward link channels (e.g., paging channel, control channel, broadcast channel, or forward traffic channel, etc.). As used herein, the term traffic channel (TCH) can refer to uplink, reverse or downlink, and / or forward traffic channel.

[0051] The terms "network entity" or "base station" (e.g., having a converged / monolithic base station architecture or a disaggregated base station architecture) can refer to a single physical TRP or multiple physical TRPs that may or may not be co-located. For example, when the term "network entity" or "base station" refers to a single physical TRP, the physical TRP may be a base station antenna corresponding to a cell (or several cell sectors) of the base station. When the term "network entity" or "base station" refers to multiple co-located physical TRPs, these physical TRPs may be antenna arrays of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). When the term "base station" refers to multiple non-co-located physical TRPs, the physical TRPs may be a distributed antenna system (DAS) (a network of spatially separated antennas connected via a transmission medium to a common source) or a remote radio headend (RRH) (a remote base station connected to a serving base station). Alternatively, a non-co-located physical TRP may be a serving base station from which a measurement report is received from a UE and a neighboring base station from which the UE is measuring its reference radio frequency (RF) signal (or simply "reference signal"). As used in this article, a TRP is the point by which a base station transmits and receives wireless signals, so any mention of transmitting from or receiving at a base station should be understood as referring to a specific TRP of the base station.

[0052] In some specific implementations supporting UE positioning, network entities or base stations may not support the UE's radio access (e.g., may not support data, voice, and / or signaling connections regarding the UE), but instead may transmit reference signals to the UE for measurement, and / or receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of transmitting signals to the UE) and / or as a location measurement unit (e.g., in the case of receiving and measuring signals from the UE).

[0053] Roadside units (RSUs) are communication links or interfaces (e.g., cellular-based side links or PC5 interfaces, 802.11-based or WiFi-based). ™ An RSU is a device that uses a Dedicated Short Range Communication (DSRC) interface and / or other interfaces to send and receive messages to or from one or more UEs, other RSUs, and / or base stations. Examples of messages that can be sent and received by an RSU include Vehicle-to-Everything (V2X) messages, which are described in more detail below. An RSU may reside on various transportation infrastructure systems, including roads, bridges, parking lots, toll booths, and / or other infrastructure systems. In some examples, an RSU may facilitate communication between a UE (e.g., a vehicle, pedestrian user equipment, and / or other UE) and the transportation infrastructure system. In some implementations, an RSU may communicate with servers, base stations, and / or other systems that can perform centralized management functions.

[0054] The RSU can communicate with the UE's communication system. For example, the UE's (e.g., a vehicle and / or other UE) Intelligent Transport System (ITS) can be used to generate and sign messages for transmission to the RSU and to verify messages received from the RSU. The RSU can communicate (e.g., via a PC5 interface, DSRC interface, etc.) with vehicles traveling along roads, bridges, or other infrastructure systems to obtain traffic-related data (e.g., vehicle time, speed, location, etc.). In some cases, in response to obtaining traffic-related data, the RSU can determine or estimate traffic congestion information (e.g., the start of traffic congestion, the end of traffic congestion, etc.), travel time, and / or other information for a specific location. In some examples, the RSU can communicate with other RSUs (e.g., via a PC5 interface, DSRC interface, etc.) to determine traffic-related data. The RSU can send information (e.g., traffic congestion information, travel time information, and / or other information) to other vehicles, pedestrian UEs, and / or other UEs. For example, the RSU may broadcast or otherwise send information to any UE (e.g., vehicle, pedestrian UE, etc.) within the RSU's coverage area.

[0055] Radio frequency signals, or “RF signals,” comprise electromagnetic waves of a given frequency that transmit information across the space between a transmitter and a receiver. As used herein, a transmitter may send a single “RF signal” or multiple “RF signals” to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple “RF signals” corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and receiver can be referred to as a “multipath” RF signal. As used herein, where the context clearly indicates that the term “signal” refers to a wireless signal or RF signal, an RF signal may also be referred to as a “wireless signal” or simply a “signal.”

[0056] According to various aspects, Figure 1An exemplary wireless communication system 100 is illustrated. The wireless communication system 100 (also referred to as a wireless wide area network (WWAN)) may include individual base stations 102 and individual UEs 104. In some aspects, base station 102 may also be referred to as a "network entity" or "network node". One or more of base stations 102 may be implemented in an aggregated or monolithic base station architecture. Additionally or alternatively, one or more of base stations 102 may be implemented in a decomposed base station architecture and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. Base station 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, a macro cell base station may include an eNB and / or an ng-eNB (where the wireless communication system 100 corresponds to a Long Term Evolution (LTE) network), or a gNB (where the wireless communication system 100 corresponds to an NR network), or a combination of both, and a small cell base station may include femtocells, picocells, microcells, etc.

[0057] Base station 102 can collectively form a RAN and interface with core network 170 (e.g., evolved packet core (EPC) or 5G core (5GC)) via backhaul link 122, and interface with one or more location servers 172 (which may be part of core network 170 or external to core network 170) via core network 170. Among other functions, base station 102 can perform functions related to one or more of the following: delivering user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base station 102 can communicate with each other directly or indirectly (e.g., via EPC or 5GC) via backhaul link 134 (which may be wired and / or wireless).

[0058] Base station 102 can wirelessly communicate with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographical coverage area 110. In one aspect, base station 102 in each coverage area 110 can support one or more cells. A “cell” is a logical communication entity used to communicate with a base station (e.g., on a frequency resource, referred to as a carrier frequency, component carrier, carrier, frequency band, etc.) and can be associated with an identifier (e.g., Physical Cell Identifier (PCI), Virtual Cell Identifier (VCI), Cell Global Identifier (CGI)) to distinguish cells operating via the same or different carrier frequencies. 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). Because a cell is supported by a specific base station, the term “cell” can refer to either or both of the logical communication entity and the base station supporting the logical communication entity, depending on the context. Furthermore, since the TRP is typically the physical transmission point of the cell, the terms “cell” and “TRP” can be used interchangeably. In some cases, the term "cell" can also refer to the geographic coverage area of ​​a base station (e.g., a sector), as long as the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.

[0059] While the geographic coverage areas 110 of adjacent macro cell base stations 102 may partially overlap (e.g., in handover areas), some areas within geographic coverage areas 110 may substantially overlap with larger geographic coverage areas 110. For example, a small cell base station 102' may have a coverage area 110' that substantially overlaps with the coverage areas 110 of one or more macro cell base stations 102. A network that includes both small cell base stations and macro cell base stations can be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB) that can provide service to a restricted group referred to as a Closed Subscriber Group (CSG).

[0060] The communication link 120 between base station 102 and UE 104 may include uplink (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (also known as forward link) transmission from base station 102 to UE 104. Communication link 120 may use MIMO antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. Communication link 120 may use one or more carrier frequencies. Carrier allocation may be asymmetric for downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink compared to the uplink).

[0061] The wireless communication system 100 may also include a WLAN AP 150 communicating with a WLAN station (STA) 152 via a communication link 154 in unlicensed spectrum (e.g., 5 GHz). When communicating in unlicensed spectrum, the WLAN STA 152 and / or WLAN AP 150 may perform a Free Channel Assessment (CCA) or Listen-After-Talk (LBT) process before communication to determine if the channel is available. In some examples, the wireless communication system 100 may include devices (e.g., UEs, etc.) that communicate with one or more UEs 104, base stations 102, APs 150, etc., using ultra-wideband (UWB) spectrum. The UWB spectrum can range from 3.1 GHz to 10.5 GHz.

[0062] Small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell base station 102' can employ LTE or NR technology and use the same 5 GHz unlicensed spectrum as WLAN AP 150. Small cell base station 102' employing LTE and / or 5G in unlicensed spectrum can enhance coverage of the access network and / or increase the capacity of the access network. NR in unlicensed spectrum can be referred to as NR-U. LTE in unlicensed spectrum can be referred to as LTE-U, Licensed Assisted Access (LAA), or MulteFire.

[0063] The wireless communication system 100 may further include a millimeter-wave (mmW) base station 180, which can operate at mmW and / or near-mmW frequencies to communicate with the UE 182. The mmW base station 180 may be implemented in a converged or monolithic base station architecture, or alternatively, in a decomposed base station architecture (e.g., including one or more of a CU, DU, RU, near-RT RIC, or non-RT RIC). Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF has a range of 30 GHz to 300 GHz, with wavelengths between 1 mm and 10 mm. Radio waves in this band can be referred to as millimeter waves. Near-mmW extends down to frequencies of 3 GHz with wavelengths of 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz, and are also referred to as centimeter waves. Communication using mmW and / or near-mmW radio bands has high path loss and relatively short range. mmW base station 180 and UE 182 can utilize beamforming (transmit and / or receive) on mmW communication link 184 to compensate for extremely high path loss and short range. Furthermore, it should be understood that in alternative configurations, one or more base stations 102 may also use mmW or near-mmW and beamforming for transmission. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.

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

[0065] Transmit beams can be quasi-co-located, meaning they have the same parameters for the receiver (e.g., UE), regardless of whether the transmit antennas of the network nodes are physically co-located. In NR, there are four types of quasi-co-located (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 the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is of type QCL D, the receiver can use the source reference RF signal to estimate the spatial reception parameters of a second reference RF signal transmitted on the same channel.

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

[0067] The receive beam can be spatially dependent. Spatial dependency means that parameters for the transmit beam for the second reference signal can be derived based on information about the receive beam for the first reference signal. For example, a UE can use a specific receive beam to receive one or more reference downlink reference signals (e.g., Position Reference Signal (PRS), Tracking Reference Signal (TRS), Phase Tracking Reference Signal (PTRS), Cell Specific Reference Signal (CRS), Channel State Information Reference Signal (CSI-RS), Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Synchronization Signal Block (SSB), etc.) from a network node or entity (e.g., a base station). The UE can then form a transmit beam based on the parameters of the receive beam to transmit one or more uplink reference signals (e.g., Uplink Position Reference Signal (UL-PRS), Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), PTRS, etc.) to that network node or entity (e.g., a base station).

[0068] It should be noted that, depending on the entity forming the "downlink" beam, the beam can be either a transmit beam or a receive beam. For example, if a network node or entity (e.g., a base station) is forming a downlink beam to transmit a reference signal to the UE, then the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, then 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 either a transmit beam or a receive beam. For example, if a network node or entity (e.g., a base station) is forming an uplink beam, then the uplink beam is an uplink receive beam, while if the UE is forming an uplink beam, then the uplink beam is an uplink transmit beam.

[0069] In 5G, the spectrum in which wireless network nodes or entities (e.g., base stations 102 / 180, UE 104 / 182) operate is divided into multiple frequency ranges: FR1 (from 450 MHz to 6000 MHz), FR2 (from 24250 MHz to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). In multi-carrier systems such as 5G, one of the carrier frequencies is referred to as the "primary carrier," "anchor carrier," "primary serving cell," or "PCell," and the remaining carrier frequencies are referred to as "secondary carriers," "secondary serving cells," or "SCell." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) used by UE 104 / 182 and the cell, where UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier on 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 UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier on an unlicensed frequency. The secondary carrier may contain only the necessary signaling information and signals; for example, since the primary uplink and primary downlink carriers are typically UE-specific, those UE-specific signaling information and signals may not be present on the secondary carrier. This means that different UEs 104 / 182 within a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can 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 a carrier frequency or component carrier that some base station is using for communication, the terms “cell,” “serving cell,” “component carrier,” “carrier frequency,” etc., can be used interchangeably.

[0070] For example, still refer to Figure 1 One of the frequencies used by macro cell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies used by macro cell base station 102 and / or mmW base station 180 may be secondary carriers ("SCell"). In carrier aggregation, base station 102 and / or UE 104 may use up to [number missing] frequencies per carrier. Y A spectrum with a bandwidth of MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz), having up to a total of [number missing] in each direction. Yx MHz ( x(Multiple component carriers) are used for transmission. Component carriers may or may not be adjacent to each other in the spectrum. Carrier allocation may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink compared to the uplink). Simultaneous transmission and / or reception on multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two aggregated 20MHz carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40MHz) compared to the data rate obtained by a single 20MHz carrier.

[0071] To operate on multiple carrier frequencies, base station 102 and / or UE 104 are equipped with multiple receivers and / or transmitters. For example, UE 104 may have two receivers, namely "Receiver 1" and "Receiver 2", where "Receiver 1" is a multi-band receiver that can be tuned to band "X" or band "Y", while "Receiver 2" is a single-band receiver that can be tuned to only band "Z". In this example, if UE 104 is being served in band "X", then band "X" will be referred to as PCell or active carrier frequency, and "Receiver 1" will need to tune from band "X" to band "Y" (SCell) to measure band "Y" (and vice versa). In contrast, regardless of whether UE 104 is being served in band "X" or band "Y", due to the separate "Receiver 2", UE 104 can measure band "Z" without interrupting service on band "X" or band "Y".

[0072] The wireless communication system 100 may also include a UE 164, which can communicate with the macro cell base station 102 on the communication link 120 and / or with the mmW base station 180 on the mmW communication link 184. For example, the macro cell base station 102 may support PCells and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0073] The wireless communication system 100 may further include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "side links"). Figure 1In one example, UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of the base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through this D2D P2P link), and has a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through this D2D P2P link). In one example, D2D P2P links 192 and 194 can use any known D2D RAT (such as LTE Direct (LTE-D), Wi-Fi Direct (Wi-Fi-D), Bluetooth). ® (etc.) to support.

[0074] Figure 2 This is an illustration of an example of a decomposed base station architecture that can be used by the disclosed system to employ SL positioning anchor UE selection criteria, based on some examples. The deployment of communication systems (such as 5G NR systems) can involve various components or constituent parts arranged in multiple ways. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)), or one or more units (or components) performing base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a NodeB (NB), evolved NB (eNB), NR BS, 5G NB, AP, transmit / receive point (TRP), or cell, etc.) can be implemented as an aggregated base station (also known as a standalone BS or monolithic BS) or a decomposed base station.

[0075] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across 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 respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0076] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations advocated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units in a decomposed base station or decomposed RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0077] As mentioned earlier, Figure 2 A diagram illustrating an example decomposed base station 201 architecture is shown. The decomposed base station 201 architecture may include one or more central units (CUs) 211, which may communicate directly with the core network 223 via a backhaul link, or indirectly with the core network 223 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 227 via an E2 link, or a non-real-time (non-RT) RIC 217 associated with a Service Management and Orchestration (SMO) framework 207, or both. CUs 211 may communicate with one or more distributed units (DUs) 231 via corresponding midhaul links (such as F1 interfaces). DUs 231 may communicate with one or more radio units (RUs) 241 via corresponding fronthaul links. RUs 241 may communicate with corresponding UEs 221 via one or more RF access links. In some implementations, a UE 221 may be served simultaneously by multiple RUs 241.

[0078] Each of the units (i.e., CU 211, DU 231, RU 241, and near-RT RIC 227, non-RT RIC 217, and SMO frame 207) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via a transmission medium. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via a wired transmission medium. Additionally, units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive or transmit signals, or both, to one or more other units over a wireless transmission medium.

[0079] In some aspects, CU 211 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by CU 211. CU 211 can 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 implementations, CU 211 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units can communicate bidirectionally with CU-CP units via an interface such as an E1 interface. CU 211 can be implemented to communicate with DU 131 for network control and signaling, as needed.

[0080] DU 231 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 241s. In some aspects, DU 231 may at least partially 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.) according to functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 231 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 231 or with control functions hosted by CU 211.

[0081] Lower-layer functionality can be implemented by one or more RU 241s. In some deployments, the RU241 controlled by DU 231 may correspond to a logical node that at least partially hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.) based on functional decomposition such as lower-layer functional decomposition, or both. In such architectures, RU 241 may be implemented to handle over-the-air (OTA) communications with one or more UE 221s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with RU 241 may be controlled by the corresponding DU 231. In some scenarios, this configuration allows DU 231 and CU 211 to be implemented in cloud-based RAN architectures such as vRAN architectures.

[0082] SMO framework 207 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 207 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 207 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 291 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 211, DU 231, RU 241, and near-RT RIC 227. In some implementations, SMO framework 207 can communicate with hardware aspects of the 4G RAN, such as Open eNB (O-eNB) 213, via the O1 interface. Additionally, in some implementations, SMO framework 207 can communicate directly with one or more RU 241s via the O1 interface. SMO framework 207 may also include a non-RT RIC 217 configured to support the functionality of SMO framework 207.

[0083] The non-RT RIC 217 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 227. The non-RT RIC 217 can be coupled to or communicate with the near-RT RIC 227, such as via an A1 interface. The near-RT RIC 227 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as via an E2 interface, through data collection and action, connecting one or more CUs 211, one or more DUs 231, or both, and an O-eNB 213 to the near-RT RIC 227.

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

[0085] Figure 3 Examples of different communication mechanisms used by various UEs are illustrated. In one example of sidelink communication, Figure 3 Vehicles 304, 305, and RSU 303 are illustrated using PC5, DSRC, or other device-to-device direct signaling interfaces. Additionally, vehicles 304 and 305 can use a network (Uu) interface to communicate with base station 302 (shown as BS 302). In some examples, base station 302 may include a gNB. Figure 3 The example also illustrates user equipment 307 using a network (Uu) interface to communicate with base station 302. As described below, functionality can be transferred from a vehicle (e.g., vehicle 304) to user equipment (e.g., user equipment 307) based on one or more characteristics or factors (e.g., temperature, humidity, etc.). In an illustrative example, V2X functionality can be transferred from vehicle 304 to user equipment 307, after which user equipment 307 can communicate with other vehicles (e.g., vehicle 305) via a PC5 interface (or other device-to-device direct interfaces, such as a DSRC interface), as... Figure 3 As shown.

[0086] Although Figure 3An example is illustrated of a specific number of vehicles (e.g., two vehicles 304 and 305) communicating with each other and / or with RSU 303, BS 302, and / or User Equipment 307, but this disclosure is not limited thereto. For example, dozens or hundreds of such vehicles may be communicating with each other and / or with RSU 303, BS 302, and / or User Equipment 307. At any given time, each such vehicle, RSU 303, BS 302, and / or User Equipment 307 may send various types of information as messages to other nearby vehicles, resulting in each vehicle (e.g., vehicle 304 and / or 305), RSU 303, BS 302, and / or User Equipment 307 receiving hundreds or thousands of messages per second from other nearby vehicles, RSUs, base stations, and / or other UEs.

[0087] Although Figure 3 The PC5 interface is shown, but various UEs (e.g., vehicles, user equipment, etc.) and RSUs can use any suitable type of direct interface such as 802.11 DSRC interface, Bluetooth, etc. ™ Communication can be achieved directly through interfaces and / or other interfaces. For example, a vehicle can communicate with a user equipment (UE) via a direct communication interface (e.g., using PC5 and / or DSRC), a vehicle can communicate with another vehicle via a direct communication interface, a UE can communicate with another UE via a direct communication interface, a UE (e.g., a vehicle, UE, etc.) can communicate with an RSU via a direct communication interface, an RSU can communicate with another RSU via a direct communication interface, and so on.

[0088] Figure 4This is a block diagram illustrating an example of a vehicle computing system 450 for a vehicle 404. The vehicle 404 is an example of a UE that can communicate with a network (e.g., eNB, gNB, location beacon, location measurement unit, and / or other network entities) via a Uu interface and can communicate with other UEs using V2X communication via a PC5 interface (or other device-to-device direct interfaces, such as a DSRC interface). As shown, the vehicle computing system 450 may include at least a power management system 451, a control system 452, an infotainment system 454, an intelligent transmission system (ITS) 455, one or more sensor systems 456, and a communication system 458. In some cases, the vehicle computing system 450 may include any type of processing device or system or may be implemented using any type of processing device or system, such as one or more central processing units (CPUs), digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), application processors (APs), graphics processing units (GPUs), vision processing units (VPUs), neural network signal processors (NSPs), microcontrollers, special-purpose hardware, any combination thereof, and / or other processing devices or systems.

[0089] Control system 452 may be configured to control the operation of one or more of the following systems of vehicle 404: power management system 451, computing system 450, infotainment system 454, ITS 455, and / or other systems of vehicle 404 (e.g., braking system, steering system, safety systems other than ITS 455, cockpit system, and / or other systems). In some examples, control system 452 may include one or more electronic control units (ECUs). ECUs may control one or more of the electrical systems or subsystems in the vehicle. Examples of specific ECUs that may be included as part of control system 452 include engine control module (ECM), powertrain control module (PCM), transmission control module (TCM), brake control module (BCM), central control module (CCM), central timing module (CTM), etc. In some cases, control system 452 may receive sensor signals from one or more sensor systems 456 and may communicate with other systems of vehicle computing system 450 to operate vehicle 404.

[0090] The vehicle computing system 450 also includes a power management system 451. In some implementations, the power management system 451 may include a power management integrated circuit (PMIC), a backup battery, and / or other components. In some cases, other systems of the vehicle computing system 450 may include one or more PMICs, batteries, and / or other components. The power management system 451 may perform power management functions of the vehicle 404, such as managing the power supply to the computing system 450 and / or other parts of the vehicle. For example, the power management system 451 may provide a stable power supply in response to power fluctuations, such as those based on starting the vehicle's engine. In another example, the power management system 451 may perform thermal monitoring operations, such as by checking the ambient and / or transistor junction temperatures. In another example, the power management system 451 may perform certain functions based on the detection of a certain temperature level, such as cooling certain components of the vehicle computing system 450 (e.g., control system 452, such as one or more ECUs) by a cooling system (e.g., one or more fans, air conditioning system, etc.), shutting down certain functions of the vehicle computing system 450 (e.g., limiting the infotainment system 454, such as by turning off one or more displays, disconnecting from wireless networks, etc.), and other functions.

[0091] The vehicle computing system 450 also includes a communication system 458. The communication system 458 may include communication methods for communicating with a network (e.g., via a Uu interface to a gNB or other network entity) and / or with other UEs (e.g., via a PC5 interface, a WiFi interface (e.g., DSRC), Bluetooth). ™ Both software and hardware components that transmit signals to and from another vehicle or UE via an interface and / or other wireless and / or wired interfaces, and receive signals from that network and / or from that other UE. For example, communication system 458 is configured to transmit signals via any suitable wireless network (e.g., 3G network, 4G network, 5G network, WiFi network, Bluetooth). ™ The communication system 458 wirelessly transmits and receives information via a network and / or other networks. The communication system 458 includes various components or devices for performing wireless communication functionality, including an Original Equipment Manufacturer (OEM) subscriber identity module (referred to as a SIM or SIM card) 460, a subscriber SIM 462, and a modem 464. Although the vehicle computing system 450 is shown as having two SIMs and one modem, in some specific implementations, the computing system 450 may have any number of SIMs (e.g., one SIM or more than two SIMs) and any number of modems (e.g., one modem, two modems, or more than two modems).

[0092] A SIM is a device (e.g., an integrated circuit) that securely stores a specific subscriber's or user's International Mobile Subscriber Identity (IMSI) number and associated keys (e.g., encryption-decryption keys). The IMSI and keys can be used to identify and authenticate subscribers on a specific UE. The OEM SIM 460 can be used by the communication system 458 to establish a wireless connection for vehicle-based operations, such as for emergency call (eCall) functionality, communication with the vehicle manufacturer's communication system (e.g., for software updates), and other operations. The OEM SIM 460 can be crucial for supporting key services such as eCalls for making emergency calls in the event of a car accident or other emergency. For example, eCalls could include automatically dialing emergency numbers (e.g., "9-1-1" in the US, "1-1-2" in Europe, etc.) in the event of a vehicle accident and relaying the vehicle's location to emergency services (such as police stations, fire departments, etc.).

[0093] The user SIM 462 can be used by the communication system 458 to perform wireless network access functions to support user data connections (e.g., for making telephone calls, sending and receiving messages, infotainment-related services, etc.). In some cases, the user's user equipment can access the network via an interface (e.g., via PC5, Bluetooth). ™ Wi-Fi ™ The user equipment (UE) can connect to the vehicle computing system 450 via a wireless network access function (e.g., DSRC, USB port, and / or other wireless or wired interface). Once connected, the UE can transfer wireless network access functionality from the UE to the vehicle's communication system 458, in which case the UE can stop the execution of the wireless network access function (e.g., during the period when the communication system 458 is performing the wireless access function). The communication system 458 can begin interacting with the base station to perform one or more wireless communication operations, such as facilitating telephone calls, sending and / or receiving data (e.g., message sending and receiving, video, audio, etc.), and other operations. In such cases, other components of the vehicle computing system 450 can be used to output the data received by the communication system 458. For example, the infotainment system 454 (described below) can display the video received by the communication system 458 on one or more displays, and / or can use one or more speakers to output the audio received by the communication system 458.

[0094] A modem is a device that modulates one or more carrier signals to encode digital information for transmission and demodulates the signals to decode the transmitted information. Modem 464 (and / or one or more other modems of communication system 458) can be used for data communication of OEM SIM 460 and / or user SIM 462. In some examples, modem 464 may include a 4G (or LTE) modem, and another modem (not shown) of communication system 458 may include a 5G (or NR) modem. In some examples, communication system 458 may include one or more Bluetooth devices. ™ Modem (e.g., for Bluetooth) ™ Bluetooth Low Energy (BLE) or other types of Bluetooth communication), or one or more WiFi networks. ™ Modems (e.g., for DSRC communication and / or other WiFi communication), broadband modems (e.g., ultra-wideband (UWB) modems), any combination thereof and / or other types of modems.

[0095] In some cases, modem 464 (and / or one or more other modems of communication system 458) may be used to perform V2X communication (e.g., V2V communication with other vehicles, D2D communication with other devices, V2I communication with infrastructure systems, V2P communication with pedestrian UEs, etc.). In some examples, communication system 458 may include a V2X modem for performing V2X communication (e.g., sidelink communication via PC5 interface or DSRC interface), in which case the V2X modem may be separate from one or more modems for wireless network access functions (e.g., network communication via network / Uu interface and / or sidelink communication other than V2X communication).

[0096] In some examples, the communication system 458 may be or may include a Telematics Control Unit (TCU). In some implementations, the TCU may include a Network Access Device (NAD) (also referred to in some cases as a Network Control Unit or NCU). The NAD may include a modem 464, Figure 4 This includes any other modems, OEM SIM 460, user SIM 462, and / or other components for wireless communication not shown. In some examples, the communication system 458 may include a Global Navigation Satellite System (GNSS). In some cases, the GNSS may be part of one or more sensor systems 456, as described below. The GNSS may provide the vehicle computing system 450 with the ability to perform one or more location services, navigation services, and / or other services that can utilize GNSS functionality.

[0097] In some cases, the communication system 458 may also include one or more wireless interfaces for transmitting and receiving wireless communications (e.g., including one or more transceivers and one or more baseband processors for each wireless interface), one or more wired interfaces for performing communication via one or more hardwired connections (e.g., serial interfaces such as Universal Serial Bus (USB) inputs, lighting connectors and / or other wired interfaces), and / or other components that may allow the vehicle 404 to communicate with a network and / or other UEs.

[0098] The vehicle computing system 450 may also include an infotainment system 454 with controllable content and one or more output devices for outputting content from the vehicle 404. The infotainment system 454 may also be referred to as an in-vehicle infotainment (IVI) system or an in-vehicle entertainment (ICE) system. Content may include navigation content, media content (e.g., video content, music or other audio content, and / or other media content), and other content. One or more output devices may include one or more graphical user interfaces, one or more displays, one or more speakers, one or more extended reality devices (e.g., VR, AR, and / or MR headsets), one or more haptic feedback devices (e.g., one or more devices configured to vibrate the seat, steering wheel, and / or other parts of the vehicle 404), and / or other output devices.

[0099] In some examples, computing system 450 may include Intelligent Transport System (ITS) 455. In some examples, ITS 455 may be used to implement V2X communication. For example, the ITS stack of ITS 455 may generate V2X messages based on information from the application layer of the ITS. In some cases, the application layer may determine whether certain conditions have been met to generate messages for use by ITS 455 and / or generate messages to be transmitted to other vehicles (for V2V communication), pedestrian UEs (for V2P communication), and / or infrastructure systems (for V2I communication). In some cases, communication system 458 and / or ITS 455 may obtain Vehicle Access Network (CAN) information (e.g., from other components of the vehicle via the CAN bus). In some examples, communication system 458 (e.g., TCU NAD) may obtain CAN information via the CAN bus and may transmit the CAN information to the PHY / MAC layer of ITS 455. ITS 455 may provide CAN information to the ITS stack of ITS 455. CAN information may include vehicle-related information, such as the vehicle's direction of travel, speed, braking information, and other information. CAN information may be provided to the ITS 455 continuously or periodically (e.g., every 1 millisecond (ms), every 10 ms, etc.).

[0100] The conditions used to determine whether to generate a message can be based on CAN information used by safety-related applications and / or other applications (including applications related to road safety, traffic efficiency, infotainment, business, and / or other applications). In an exemplary example, ITS 455 can perform lane change assistance or negotiation. For example, using CAN information, ITS 455 can determine that the driver of vehicle 404 is attempting to change lanes from the current lane to an adjacent lane (e.g., based on the activation of hazard lights, based on the user changing direction or turning into an adjacent lane, etc.). Based on determining that vehicle 404 is attempting to change lanes, ITS 455 can determine that lane change conditions have been met, associated with messages to be transmitted to other vehicles nearby in the adjacent lane. ITS 455 can trigger the ITS stack to generate one or more messages to be sent to other vehicles, which can be used to negotiate a lane change with other vehicles. Other examples of applications include forward collision warning, automatic emergency braking, lane departure warning, pedestrian avoidance or protection (e.g., when a pedestrian is detected near vehicle 404, such as through V2P communication with the user's UE), traffic sign recognition, and so on.

[0101] ITS 455 may use any suitable protocol to generate messages (e.g., V2X messages). Examples of protocols that ITS 455 may use include one or more Society of Automotive Engineers (SAE) standards (such as SAE J2735, SAE J2945, SAE J3161 and / or other standards), which are incorporated herein by reference in their entirety and used for all purposes.

[0102] The security layer of ITS 455 can be used to securely sign messages from the ITS stack, which are then delivered to and verified by other UEs configured for V2X communication (such as other vehicles, pedestrian UEs, and / or infrastructure systems). The security layer can also verify messages received from such other UEs. In some implementations, the signing and verification process may be based on the security context of the vehicle. In some examples, the security context may include one or more encryption-decryption algorithms, a public key and / or private key used to generate the signature using the encryption-decryption algorithms, and / or other information. For example, each ITS message generated by ITS 455 can be signed by the security layer of ITS 455. The signature can be derived using the public key and the encryption-decryption algorithm. The vehicle, pedestrian UE, and / or infrastructure system receiving the signed message can verify the signature to ensure that the message originates from an authorized vehicle. In some examples, one or more encryption-decryption algorithms may include one or more symmetric encryption algorithms (e.g., Advanced Encryption Standard (AES), Data Encryption Standard (DES), and / or other symmetric encryption algorithms), one or more asymmetric encryption algorithms using public and private keys (e.g., Levitt-Shamir-Adlerman (RSA) and / or other asymmetric encryption algorithms), and / or other encryption-decryption algorithms.

[0103] In some examples, ITS 455 may determine certain actions to be performed (e.g., V2X-based actions) based on messages received from other UEs. These actions may include safety-related and / or other operations, such as those for road safety, traffic efficiency, infotainment, business, and / or other applications. In some examples, these actions may include causing a vehicle (e.g., control system 452) to perform automatic functions, such as automatic braking, automatic steering (e.g., maintaining direction of travel in a specific lane), automatic lane change negotiation with other vehicles, and other automatic functions. In one exemplary example, communication system 458 may receive a message from another vehicle (e.g., via a PC5 interface, DSRC interface, or other device-to-device direct interface) indicating that the other vehicle is about to stop suddenly. In response to receiving the message, the ITS stack may generate a message or instruction and may transmit the message or instruction to control system 452, which may cause control system 452 to automatically brake vehicle 404 to stop it before colliding with another vehicle. In other exemplary examples, these actions may include triggering a message to warn the driver that another vehicle is in the lane adjacent to the vehicle, a message to warn the driver to stop the vehicle, a message to warn the driver that a pedestrian is at an upcoming intersection, a message to warn the driver that a toll station is within a certain distance of the vehicle (e.g., within 1 mile), and so on.

[0104] In some examples, the ITS 455 may receive a large number of messages from other UEs (e.g., vehicles, RSUs, etc.). In such cases, the ITS 455 will authenticate (e.g., decode and decrypt) each message and / or determine which operations to perform. Such a large number of messages can result in a high computational load on the vehicle computing system 450. In some cases, this high computational load can cause the temperature of the computing system 450 to rise. The temperature rise of the components of the computing system 450 can adversely affect its ability to process a large number of incoming messages. One or more functionalities may be transferred from vehicle 404 to another device (e.g., user equipment, RSUs, etc.) based on the temperature of the vehicle computing system 450 (or its components) exceeding or approaching one or more thermal levels. Transferring one or more functionalities can reduce the computational load on vehicle 404 and help lower the temperature of the components. A thermal load balancer may be provided, which, depending on the temperature of the computing system 450 and the processing power of the vehicle computing system 450, enables the vehicle computing system 450 to perform thermal-based load balancing to control the processing load.

[0105] The computing system 450 also includes one or more sensor systems 456 (e.g., a first sensor system through an Nth sensor system, where N is a value equal to or greater than 0). When multiple sensor systems are included, the sensor systems 456 may include different types of sensor systems that can be arranged on or within different parts of the vehicle 404. The sensor systems 456 may include one or more camera sensor systems, LIDAR sensor systems, RADAR sensor systems, EmDAR sensor systems, SONAR sensor systems, SODAR sensor systems, GNSS receiver systems (e.g., one or more GPS receiver systems), accelerometers, gyroscopes, inertial measurement units (IMUs), infrared sensor systems, laser rangefinder systems, ultrasonic sensor systems, infrasound sensor systems, microphones, any combination thereof, and / or other sensor systems. It should be understood that any number of sensors or sensor systems may be included as part of the computing system 450 of the vehicle 404.

[0106] Although the vehicle computing system 450 is shown as including certain components and / or systems, those skilled in the art will understand that the vehicle computing system 450 may include more than Figure 4The components shown may include more or fewer of those shown. For example, the vehicle computing system 450 may also include one or more input devices and one or more output devices (not shown). In some embodiments, the vehicle computing system 450 may also include (e.g., as part of or separate from a control system 452, infotainment system 454, communication system 458, and / or sensor system 456) at least one processor and at least one memory having computer-executable instructions executed by the at least one processor. The at least one processor communicates with and / or is electrically connected to (referred to as "coupled to" or "communically coupled to") the at least one memory. The at least one processor may include, for example, one or more microcontrollers, one or more central processing units (CPUs), one or more field-programmable gate arrays (FPGAs), one or more graphics processing units (GPUs), one or more application processors (e.g., for running or executing one or more software applications), and / or other processors. The at least one memory may include, for example, read-only memory (ROM), random access memory (RAM) (e.g., static RAM (SRAM)), electrically erasable programmable read-only memory (EEPROM), flash memory, one or more buffers, one or more databases, and / or other memories. Computer-executable instructions stored in or on at least memory can be executed to perform one or more of the functions or operations described herein.

[0107] Figure 5 An example of a computing system 570 for user equipment 507 is illustrated. User equipment 507 is an example of a UE that can be used by an end user. For example, user equipment 507 may include a mobile phone, router, tablet computer, laptop computer, tracking device, wearable device (e.g., smartwatch, glasses, XR device, etc.), Internet of Things (IoT) device, and / or other devices used by the user to communicate over a wireless communication network. Computing system 570 includes software and hardware components that can be electrically coupled or communicatively coupled (or otherwise communicate, as applicable) via bus 589. For example, computing system 570 includes one or more processors 584. One or more processors 584 may include one or more CPUs, ASICs, FPGAs, APs, GPUs, VPUs, NSPs, microcontrollers, dedicated hardware, any combination thereof, and / or other processing devices or systems. Bus 589 may be used by one or more processors 584 to communicate between cores and / or with one or more memory devices 586.

[0108] The computing system 570 may also include one or more memory devices 586, one or more digital signal processors (DSPs) 582, one or more SIMs 574, one or more modems 576, one or more wireless transceivers 578, antennas 587, one or more input devices 572 (e.g., camera, mouse, keyboard, touchscreen, touchpad, keypad and / or microphone, etc.) and one or more output devices 580 (e.g., display, speaker and / or printer, etc.).

[0109] One or more wireless transceivers 578 can transmit data via antenna 587 from one or more other devices (such as other user equipment, vehicles, etc., as described above). Figure 4 The computing system 570 may receive wireless signals (e.g., signal 588) via vehicles 404, network devices (e.g., base stations, such as eNBs and / or gNBs, WiFi routers, etc.), cloud networks, etc. In some examples, the computing system 570 may include multiple antennas. Wireless signal 588 may be transmitted via a wireless network. The wireless network may be any wireless network, such as cellular or telecommunications networks (e.g., 3G, 4G, 5G, etc.), wireless local area networks (e.g., WiFi networks), Bluetooth, etc. ™ Networks and / or other networks. In some examples, one or more wireless transceivers 578 may include an RF front end, which includes one or more components such as amplifiers, a mixer for down-converting signals (also called a signal multiplier), a frequency synthesizer (also called an oscillator) that supplies signals to the mixer, a baseband filter, an analog-to-digital converter (ADC), one or more power amplifiers, and other components. The RF front end generally handles the selection of the wireless signal 588 and the conversion of the wireless signal to baseband or intermediate frequency, and can convert the RF signal to the digital domain.

[0110] In some cases, computing system 570 may include a decoder-decoder device (or codec) configured to encode and / or decode data transmitted and / or received using one or more wireless transceivers 578. In some cases, computing system 570 may include an encryption-decryption device or component configured to encrypt and / or decrypt (e.g., according to AES and / or DES standards) data transmitted and / or received by one or more wireless transceivers 578.

[0111] One or more SIMs 574 may each securely store the IMSI number and associated key of the user assigned to user equipment 507. As noted above, the IMSI and key can be used to identify and authenticate the subscriber when accessing a network provided by a network service provider or operator associated with one or more SIMs 574. One or more modems 576 may modulate one or more signals to encode information to be transmitted using one or more wireless transceivers 578. One or more modems 576 may also demodulate signals received by one or more wireless transceivers 578 to decode the transmitted information. In some examples, one or more modems 576 may include a 4G (or LTE) modem, a 5G (or NR) modem, a modem configured for V2X communication, and / or other types of modems. One or more modems 576 and one or more wireless transceivers 578 may be used to transmit data from one or more SIMs 574.

[0112] The computing system 570 may also include one or more non-transitory machine-readable storage media or storage devices (e.g., one or more memory devices 586) (and / or communicate with them), which may include, but are not limited to, local and / or network-accessible storage devices, disk drives, drive arrays, optical storage devices, solid-state storage devices (such as RAM and / or ROM), which may be programmable, flash-updatable, and / or the like. Such storage devices may be configured to implement any suitable data storage, including but not limited to various file systems and / or database structures.

[0113] In various aspects, functionality may be stored in memory device 586 as one or more computer program products (e.g., instructions or code) and executed by one or more processors 584 and / or one or more DSPs 582. Computing system 570 may also include software elements (e.g., residing within one or more memory devices 586) including, for example, operating systems, device drivers, executable libraries, and / or other code, such as one or more application programs, which may include computer programs implementing the functionality provided by various aspects, and / or may be designed to implement methods and / or configure systems as described herein.

[0114] Figure 6Example 600 illustrates wireless communication between devices based on sidelink communication (such as V2X or other D2D communication). This communication may be based on a time-slot structure. For example, transmitting UE 602 may transmit 614, which can be received by receiving UEs 604, 606, and 608, and this transmission may include, for example, a control channel and / or a corresponding data channel. At least one UE may include an autonomous vehicle or an unmanned aerial vehicle. The control channel may include information for decoding the data channel and may also be used by the receiving devices to avoid interference by avoiding transmission on occupied resources during data transmission. The number of TTIs and RBs occupied by the data transmission may be indicated in a control message from the transmitting device. In addition to operating as receiving devices, UEs 602, 604, 606, and 608 may each be capable of operating as transmitting devices. Therefore, UEs 606 and 608 are illustrated as transmitting 616 and 620, respectively. Transmissions 614, 616, 620 (and 618 performed by RSU 607) may be broadcast or multicast to nearby devices. For example, UE 614 may transmit communications intended to be received by other UEs within range 601 of UE 614. Additionally / alternatively, RSU 607 may receive communication 618 from UEs 602, 604, 606, 608 and / or transmit the communication to these UEs. UEs 602, 604, 606, 608 or RSU 607 may include detection components. UEs 602, 604, 606, 608 or RSU 607 may also include BSM or mitigation components.

[0115] As previously described, sidelink-capable UEs (such as vehicles) capable of communicating via the C-V2X sidelink PC5 interface can use 3GPP sidelink ranging and positioning to obtain their own location. Sidelink ranging is based on measurements of sidelink signals (e.g., RTT and AoA) obtained by the UE. Sidelink positioning utilizes similar measurements but also requires the participation of a fixed UE (e.g., a stationary UE, or a static or fixed mobile UE) that knows its absolute location. Sidelink-capable UEs can include mobile UEs (e.g., which may sometimes be static or fixed), such as vehicles, mobile phones associated with pedestrians or cyclists, and / or drones. Sidelink-capable UEs can include stationary UEs, such as RSUs. If any sidelink-capable UE has established its own location, that sidelink-capable UE can act as an anchor UE. As defined in 3GPP Release 18, SLPP can be used to establish sidelink ranging and positioning to identify participating UEs (e.g., candidate anchor UEs), perform session establishment, and exchange measurements and measurement results.

[0116] The inherent mobility of UEs with sidelink capabilities means that different UEs can know their absolute positions with varying degrees of accuracy and can determine their absolute positions using different sources. These different sources can be one or more GNSS sources, one or more geodetic sources (e.g., stationary UEs whose positions are determined by measurements, such as RSUs), one or more sidelink signal sources (e.g., UE sources transmitting one or more sidelink signals), one or more wireless network (Uu) (e.g., cellular network) signal sources (e.g., UE sources transmitting one or more Uu-based signals), signal sources, one or more Uu positioning sources, and / or one or more WiFi positioning sources. In one or more examples, each GNSS source can be a Global Positioning System (GPS) satellite, a Global Navigation Satellite System (GLONASS) satellite, a Galileo satellite, a BeiDou Navigation Satellite System (BDS) satellite, a Quasi-Zenith Satellite System (QZSS) satellite, or a NavIC (Indian Navigation Satellite System) satellite. Employing multiple sources for positioning allows UEs to achieve greater absolute position accuracy and maintain position knowledge and accuracy over longer durations.

[0117] When a UE (e.g., the first UE) selects another UE (e.g., the second UE, which is a candidate anchor UE) as the anchor UE for sidelink positioning, the UE (e.g., the first UE) may preferably select the UE with the best location accuracy (e.g., the second UE) and the UE most likely to maintain that location accuracy over an extended duration (e.g., the second UE). Knowing the following allows the sidelink positioning UE (e.g., the first UE) to select the most suitable UE (e.g., the second UE) as the anchor UE: how the UE (e.g., the second UE, which is a candidate anchor UE) determines its location (e.g., using a single source or multiple sources), how long the location has been established, how long the UE (e.g., the second UE) expects the location to be known, the accuracy of the location, and the UE type (e.g., a stationary UE or a mobile UE).

[0118] In 3GPP, the SLPP procedure currently allows UEs (e.g., candidate anchor UEs) to provide indications of whether they can act as anchor UEs and the accuracy of their location. However, the SLPP procedure currently does not allow UEs to provide indications of their UE type (e.g., stationary UE or mobile UE), how their location was established, and the duration for which their location is expected to be valid.

[0119] When anchor UE location knowledge and / or location accuracy degrades or is lost, in some cases the anchor UE may continue transmitting to avoid losing OTA transmission resources. In 3GPP, the SLPP procedure currently does not support signaling via SLPP (e.g., via flags) indicating that auxiliary data should currently be ignored even though the anchor UE is continuing to transmit. Therefore, improved techniques for providing a more comprehensive list of sidelink positioning anchor UE selection criteria (e.g., including candidate anchor UE types, how candidate anchor UE locations are established, the expected validity period of candidate anchor UE locations, and anchor UE indications including invalid and / or outdated auxiliary information) may be useful.

[0120] In some aspects, the system and technology provide sidelink positioning anchor UE selection criteria. In one or more examples, candidate anchor UEs (e.g., stationary or mobile UEs) can provide their ability to act as anchor UEs for sidelink positioning and their positioning accuracy. For a sidelink-capable UE to be able to select the best candidate anchor UE for sidelink positioning, the sidelink-capable UE can benefit from receiving additional information about the candidate anchor UEs. In one or more examples, the system and technology provide signaling mechanisms for the candidate anchor UEs to provide the sidelink-capable UE with a comprehensive list of anchor UE selection criteria for sidelink positioning (e.g., a comprehensive list of information about the candidate anchor UEs). In some examples, a comprehensive list of anchor UE selection criteria may include information about candidate anchor UEs, such as indications of the location of the candidate anchor UEs, the UE type of the candidate anchor UE (e.g., stationary UE or mobile UE), how long the candidate anchor UE's location has been established (e.g., the age of the candidate anchor UE's location), the expected validity period of the candidate anchor UE's location (e.g., the validity period of the candidate anchor UE's location), how the candidate anchor UE's location was established (e.g., one or more sources used to obtain the candidate anchor UE's location), the source diversity of the candidate anchor UE's location, the accuracy period of the candidate anchor UE's location, and / or the validity of the ancillary data provided by the candidate anchor UE (e.g., the validity of the ancillary data for the candidate anchor UE's location). Using this anchor UE selection criterion allows a UE with sidelink capabilities to select (e.g., from candidate anchor UEs) one or more anchor UEs best suited for sidelink positioning transactions.

[0121] Figure 7 and Figure 8 Examples of systems 700 and 800 are shown respectively, which can employ the disclosed signaling mechanism for candidate anchor UEs to provide UEs with sidelink capabilities with a comprehensive list of anchor UE selection criteria for sidelink positioning (e.g., a comprehensive list of information about candidate anchor UEs). Specifically, Figure 7This is a diagram illustrating an example of a system 700 used for sidelink localization using candidate anchor UEs, including mobile UEs and stationary UEs.

[0122] exist Figure 7 In this embodiment, system 700 is shown as including multiple network devices in the form of UEs with sidelink capabilities. The multiple network devices include network device 710 as a mobile UE in the form of a vehicle, network devices 720a and 720b each as a stationary UE in the form of an RSU, and network device 730 as a mobile UE in the form of a fire truck. In one or more examples, system 700 may include, for example... Figure 7 The number of network devices shown may be more or less. In some examples, system 700 may include more or fewer network devices. Figure 7 The network device is represented by different types of UEs (e.g., vehicles and RSUs) and different types of UEs (e.g., smartphones).

[0123] In one or more examples, network devices 720a and 720b (e.g., in the form of a stationary RSU) may obtain their respective locations based on geodetic sources. In some examples, network device 730 (e.g., in the form of a mobile fire truck) may obtain its location based on sidelink signal sources (e.g., sidelink-based positioning), Uu signal sources (e.g., Uu-based positioning), Uu positioning sources, and / or WiFi positioning sources.

[0124] exist Figure 7 In this context, network device 710 is a UE with sidelink capability that wants to establish its location using sidelink positioning. Network devices 720a, 720b, and 730 are candidate anchor UEs from which network device 710 can select to use as the anchor UE for sidelink positioning.

[0125] exist Figure 7During the operation of system 700, network devices 720a, 720b, and 730 may each transmit (e.g., via SLPP signaling) a corresponding anchor selection criterion for each of network devices 720a, 720b, and 730 to network device 710. For example, network device 720a may transmit (e.g., via SLPP signaling) an anchor selection criterion associated with network device 720a to network device 710, network device 720b may transmit (e.g., via SLPP signaling) an anchor selection criterion associated with network device 720b to network device 710, and network device 730 may transmit (e.g., via SLPP signaling) an anchor selection criterion associated with network device 730 to network device 710. In one or more examples, anchor selection criteria may include indications of the location of a network device, the UE type of the network device (e.g., a stationary UE or a mobile UE), the age of the network device's location, the validity period of the network device's location, one or more sources used to obtain the location of the network device, the source diversity of the network device's location, the accuracy period of the network device's location, and / or the validity of auxiliary data for the network device's location.

[0126] Network device 710 can then receive anchor selection criteria for each of network devices 720a, 720b, and 730 from network devices 720a, 720b, and 730. One or more processors of network device 710 can then determine (e.g., select) one or more of network devices 720a, 720b, and 730 to act as anchor UEs (e.g., anchor devices) for determining the location of network device 710 based on the received anchor selection criteria. Figure 7 For example, network device 710 may determine (e.g., select) network device 720a or network device 720b instead of network device 730 to act as anchor UE because a stationary UE (e.g., network devices 720a, 720b are stationary RSUs) is preferred over a mobile UE (e.g., network device 730 is a mobile fire truck) to act as anchor UE.

[0127] One or more processors of network device 710 may then determine the location of network device 710 based on a selected network device (such as network device 720a), which may act as an anchor UE. In one or more examples, determining the location of network device 710 may include network device 710 receiving one or more sidelink signals from the selected network device (e.g., network device 720a) acting as the anchor UE. Network device 710 may then obtain measurements of the received one or more sidelink signals. One or more processors of network device 710 may then determine the location of network device 710 based on the measurements of the one or more sidelink signals.

[0128] Figure 8This is a diagram illustrating an example of a system 800 used for sidelink localization using candidate anchor UEs, including a mobile UE. Figure 8 In this system 800, multiple network devices are included in the form of UEs with sidelink capabilities. These network devices include network device 710 as a mobile UE in the form of a vehicle, and network devices 820a and 820b, each as a mobile UE in the form of a fire truck (e.g., FD1, FD2). In one or more examples, system 800 may include, for example... Figure 8 The number of network devices shown may be more or less. In some examples, system 800 may include more or fewer network devices. Figure 8 The network device is represented by different types of UEs (e.g., vehicles) and different types of UEs (e.g., smartphones and RSUs).

[0129] In one or more examples, network device 820a (e.g., in the form of a mobile fire truck FD1) may obtain its location based on a GNSS source. In some examples, network device 820a may obtain its location using measurements from signals transmitted from GPS satellite 830a. In one or more examples, network device 820b (e.g., in the form of a mobile fire truck FD2) may obtain its location based on a GNSS source. In some examples, network device 820b may obtain its location using measurements from signals transmitted from GPS satellite 830b and measurements from signals transmitted from GLONASS satellite 830b.

[0130] exist Figure 8 In this context, network device 810 is a UE with sidelink capability that wants to establish its location using sidelink positioning. Network devices 820a and 820b are candidate anchor UEs from which network device 810 can select to use as the anchor UE for sidelink positioning.

[0131] exist Figure 8During the operation of system 800, network devices 820a and 820b may each transmit (e.g., via SLPP signaling) a corresponding anchor selection criterion for each of network devices 820a and 820b to network device 810. For example, network device 820a may transmit (e.g., via SLPP signaling) an anchor selection criterion associated with network device 820a to network device 810, and network device 820b may transmit (e.g., via SLPP signaling) an anchor selection criterion associated with network device 820b to network device 810. In one or more examples, the anchor selection criterion may include an indication of the location of the network device, the UE type of the network device (e.g., a stationary UE or a mobile UE), the age of the location of the network device, the validity period of the location of the network device, one or more sources used to obtain the location of the network device, the source diversity of the location of the network device, the accuracy period of the location of the network device, and / or the validity of auxiliary data for the location of the network device.

[0132] Network device 810 can then receive anchor selection criteria for each of network devices 820a and 820b from network devices 820a and 820b. One or more processors of network device 810 can then determine (e.g., select) one or more of network devices 820a and 820b to act as an anchor UE (e.g., anchor device) for determining the location of network device 810 based on the received anchor selection criteria. Figure 8 For example, network device 810 may determine (e.g., select) network device 820b instead of network device 820a to act as anchor UE, because a network device with a location determined using multiple sources (e.g., GPS satellite 830a and GLONASS satellite 830b) is preferred to act as anchor UE than a network device with a location determined using a single type of source (e.g., GPS satellite 830a).

[0133] One or more processors of network device 810 may then determine the location of network device 810 based on a selected network device (such as network device 820b), which may act as an anchor UE. In one or more examples, determining the location of network device 810 may include network device 810 receiving one or more sidelink signals from the selected network device (e.g., network device 820b) acting as the anchor UE. Network device 810 may then obtain measurements of the received one or more sidelink signals. One or more processors of network device 810 may then determine the location of network device 810 based on the measurements of the one or more sidelink signals.

[0134] Figure 9 Table 900 is an example of the criteria for anchor UE selection used for sidelink positioning. Specifically, Figure 9Table 900 shows an example UE sidelink positioning SLPP anchor UE selection criterion with information element descriptions.

[0135] In one or more examples, Figure 9 In Table 900, SLPP Anchor UE Properties 905 are shown as including SLPP Anchor Position Source 910, SLPP Anchor Position Source Diversity 920, SLPP Anchor Position Age 930, SLPP Anchor Position Duration 940, SLPP Anchor Position Accuracy Duration 950, and SLPP Anchor Assistance Data Validity 960.

[0136] In Table 900, the SLPP AnchorPositionSource 910 can be enumerated 970 by a specific type of source used to determine the position (e.g., GNSS source, measurement source, Uu source, SL source, etc.). The SLPP AnchorPositionSource 910 can also be specified as a sequence 980 (e.g., GNSS sources can be listed sequentially as GPS, GLONASS, Galileo, BDS, QZSS, and NavIC).

[0137] In one or more examples, the SLPP Anchor Position Age (SLPPAnchorPositionAge) 930, the SLPP Anchor Position Duration (SLPPAnchorPositionDur) 940, and the SLPP Anchor Position Accuracy Duration (SLPPAnchorPositionDur) 950 may include an Elapsed Time (TimeElapsed) 990. In some examples, the Elapsed Time (TimeElapsed) 990 may be specified in days, hours, minutes, and / or seconds. In one or more examples, for the Elapsed Time (TimeElapsed) 990, the number of days may be represented by integers from zero to seven, the number of hours may be represented by integers from zero to 168, the number of minutes may be represented by integers from zero to 1440, and the number of seconds may be represented by integers from zero to 3600.

[0138] Figure 10 This is an example Figure 9 The table 1000 is an example of the definition of the criteria in the table. Figure 10In Table 1000, SLPP AnchorPositionSource 910 is defined as the source used by a specified sidelink positioning anchor UE to determine its location. In one or more examples, the specified source may include, but is not limited to, one or more GNSS sources, one or more geodetic sources (e.g., a stationary UE whose location is determined by measurement, such as an RSU), one or more sidelink signal sources (e.g., a UE source transmitting one or more sidelink signals), one or more Uu signal sources (e.g., a UE source transmitting one or more Uu-based signals), one or more Uu positioning sources, and / or one or more WiFi positioning sources.

[0139] In one or more examples, SLPP Anchor Position Source Diversity 920 is defined in Table 1000 as the GNSS sources used by a specified sidelink positioning anchor UE to determine its position. In one or more examples, different GNSS sources may include, but are not limited to, GPS satellites, GLONASS satellites, Galileo satellites, BDS satellites, QZSS satellites, and / or NavIC satellites.

[0140] In some examples, the SLPP Anchor Position Age (SLPPAnchorPositionAge) 930 is defined in Table 1000 as the elapsed time (e.g., a time quantity, which may be defined in days, hours, minutes, and / or seconds) during which a specified sidelink anchor UE has established (e.g., confirmed) its position. In some examples, the SLPP Anchor Position Age (SLPPAnchorPositionAge) 930 may be set to all zeros to indicate infinity.

[0141] In one or more examples, the SLPP AnchorPositionDur 940 is defined in Table 1000 as the expected duration (e.g., a time quantity, which may be defined in days, hours, minutes, and / or seconds) during which the anchor UE's position will be valid for a specified sidelink positioning. For example, when determining the anchor UE's position using a GNSS source (e.g., a satellite), the anchor UE's position may become invalid when the GNSS source (e.g., a satellite) is no longer in the anchor UE's field of view. The anchor UE can know when the GNSS source will no longer be in its field of view, and therefore, the anchor UE can know that its position will no longer be valid after that time. In one or more examples, the SLPP AnchorPositionDur 940 may be set to all zeros to indicate infinity.

[0142] In some examples, the SLPP Anchor Position Accuracy Duration (SLPPAnchorPositionDur) 950 is defined in Table 1000 as the expected duration (e.g., a time quantity, which can be defined in days, hours, minutes, and / or seconds) during which the anchor UE's position accuracy will be valid for a given sidelink positioning. For example, the anchor UE's position can be determined using two different GNSS sources (e.g., GPS satellites and GLONASS satellites). When one of the GNSS source types (e.g., GPS satellites) is no longer in the anchor UE's field of view, the position accuracy will no longer be valid because the position will be less accurate when using less diverse sources. The anchor UE can know when the GPS satellite will no longer be in its field of view, and therefore, the anchor UE can know that its position accuracy will no longer be valid after that time. In one or more examples, the SLPP Anchor Position Accuracy Duration (SLPPAnchorPositionDur) 950 can be set to all zeros to indicate infinity.

[0143] In one or more examples, SLPP Anchor Assistance Data Validity 960 is defined in Table 1000 as indicating that the assistance data currently being transmitted by the sidelink positioning anchor UE is invalid, and the UE should avoid using the anchor UE as a sidelink positioning anchor. For example, the anchor UE's location knowledge and / or location accuracy may be degraded or lost. However, in some cases, the anchor UE may continue transmitting to avoid losing OTA transmission resources. In these cases, the anchor UE may indicate that its assistance data is invalid (e.g., its data should be ignored) and it should not act as an anchor UE.

[0144] Figure 11A This is a flowchart illustrating an example of a process 1100 for selecting a UE using SL positioning anchor criteria. Process 1100 may be performed by a first network device (e.g., Figure 7 Network equipment 710, Figure 8 The operation of process 1100 can be performed by network device 810 or other network devices, or by components or systems of the device (e.g., chipset, at least one processor (such as CPU, GPU, DSP, etc.) or other components or systems). The first network device can be user equipment (UE), such as a vehicle, mobile device, XR device, or other type of network device. The operation of process 1100 can be implemented in one or more processors (e.g., Figure 12 Software components that execute and run on the processor 1210 or other processor. Furthermore, the device may be enabled to transmit and receive signals in process 1100, for example, via one or more antennas and / or one or more transceivers (e.g., wireless transceivers).

[0145] At box 1110, a first network device (or a component thereof) may receive, from a plurality of second network devices, a corresponding anchor selection criterion for each of the plurality of second network devices. In some cases, the corresponding anchor selection criterion is received via Side Link Positioning Protocol (SLPP) signaling. In some aspects, the corresponding anchor selection criterion for each of the plurality of second network devices may include the corresponding User Equipment (UE) type of each second network device, one or more sources of the corresponding location of each second network device, the age of the corresponding location of each second network device, the validity duration of the corresponding location of each second network device, the accuracy duration of the corresponding location of each second network device, the validity of auxiliary data of the corresponding location of each second network device, the corresponding location of each second network device, the source diversity of the corresponding location of each second network device, any combination thereof, and / or other information.

[0146] In some aspects, one or more sources at the corresponding location of each second network device may include one or more Global Navigation Satellite System (GNSS) sources, one or more geodetic sources, one or more side-link (SL) signal sources, one or more wireless network (Uu) signal sources, one or more Uu positioning sources, one or more WiFi positioning sources, any combination thereof, and / or other sources. In some aspects, each of the one or more GNSS sources is a Global Positioning System (GPS) satellite, a Global Navigation Satellite System (GLONASS) satellite, a Galileo satellite, a BeiDou Navigation Satellite System (BDS) satellite, a Quasi-Zenith Satellite System (QZSS) satellite, or a NavIC (Indian Navigation Satellite System) satellite. In some examples, the corresponding UE type is a stationary UE or a mobile UE. An exemplary example of a stationary UE is a roadside unit (RSU). Exemplary examples of a mobile UE include vehicles, mobile phones, or other mobile UEs.

[0147] At box 1120, a first network device (or a component thereof) may determine a network device from a plurality of second network devices as an anchor device for determining the location of the first network device based on a corresponding anchor selection criterion for each of the plurality of second network devices.

[0148] At box 1130, the first network device (or a component thereof) may determine its location based on the anchor device. In some aspects, in order to determine the location of the first network device based on the anchor device, the first network device (or a component thereof) may receive one or more side link (SL) signals from the anchor device, and may determine the location of the first network device based on measurements of the one or more SL signals.

[0149] Figure 11BThis is a flowchart illustrating an example of a process 1150 for selecting a UE using SL positioning anchor criteria. Process 1150 may be performed by a first network device (e.g., Figure 7 Network device 730 or network device 720a, Figure 8 The operation of process 1150 can be performed by network device 820a or network device 820b, or other network devices, or by components or systems of the device (e.g., chipset, at least one processor (such as CPU, GPU, DSP, etc.), or other components or systems). The first network device can be user equipment (UE), such as a vehicle, mobile device, XR device, or other type of network device. The operation of process 1150 can be implemented in one or more processors (e.g., Figure 12 Software components that execute and run on the processor 1210 or other processor. Furthermore, the device may be enabled to transmit and receive signals in process 1150, for example, via one or more antennas and / or one or more transceivers (e.g., wireless transceivers).

[0150] At box 1160, the first network device (or a component thereof) may determine anchor selection criteria for the first network device. Anchor selection criteria for the first network device may include the user equipment (UE) type of the first network device, one or more sources of the first network device's location, the age of the first network device's location, the validity period of the first network device's location, the accuracy period of the first network device's location, the validity of auxiliary data for the first network device's location, the corresponding location of the first network device, the source diversity of the first network device's location, any combination thereof, and / or other information.

[0151] In some aspects, one or more sources of the location of the first network device may include one or more Global Navigation Satellite System (GNSS) sources, one or more geodetic sources, one or more side-link (SL) signal sources, one or more wireless network (Uu) signal sources, one or more Uu positioning sources, one or more WiFi positioning sources, any combination thereof, and / or other sources. In some cases, each of the one or more GNSS sources is a Global Positioning System (GPS) satellite, a Global Navigation Satellite System (GLONASS) satellite, a Galileo satellite, a BeiDou Navigation Satellite System (BDS) satellite, a Quasi-Zenith Satellite System (QZSS) satellite, or a NavIC (Indian Navigation Satellite System) satellite. In some examples, the UE type is a stationary UE or a mobile UE. An exemplary example of a stationary UE is a roadside unit (RSU). Exemplary examples of a mobile UE include vehicles, mobile phones, or other mobile UEs.

[0152] At box 1170, the first network device (or a component thereof) may send anchor selection criteria to the second network device. In some cases, the anchor selection criteria are sent via Side Link Positioning Protocol (SLPP) signaling.

[0153] In some cases, a network device configured to perform the operations of process 1100 and / or process 1150 may include various components such as one or more input devices, one or more output devices, one or more processors, one or more microprocessors, one or more microcomputers, one or more cameras, one or more sensors, and / or other components configured to perform the steps of the processes described herein. In some examples, the device may include a display, one or more network interfaces configured to communicate and / or receive data, any combination thereof, and / or other components. One or more network interfaces may be configured to communicate and / or receive wired and / or wireless data, including data according to 3G, 4G, 5G, and / or other cellular standards, data according to the Wi-Fi (802.11x) standard, and data according to Bluetooth. ™ Standard data, data according to the Internet Protocol (IP) standard, and / or other types of data.

[0154] Components of the device may be implemented in circuitry. For example, components may include electronic circuitry or other electronic hardware, and / or may be implemented using electronic circuitry or other electronic hardware, which may include one or more programmable electronic circuits (e.g., a microprocessor, graphics processing unit (GPU), digital signal processor (DSP), central processing unit (CPU), and / or other suitable electronic circuitry), and / or may include computer software, firmware, or any combination thereof for performing the various operations described herein, and / or may be implemented using computer software, firmware, or any combination thereof for performing the various operations described herein. The computing device may also include a display (as an example of an output device or as a supplement to an output device), a network interface configured to communicate and / or receive data, any combination thereof, and / or other components. The network interface may be configured to communicate and / or receive Internet Protocol (IP)-based data or other types of data.

[0155] Process 1100 is illustrated as a logic flowchart, the operations of which represent a sequence of operations that can be implemented by hardware, computer instructions, or combinations thereof. In the context of computer instructions, each operation represents a computer-executable instruction stored on one or more computer-readable storage media that, when executed by one or more processors, performs the described operation. Generally, computer-executable instructions include routines, programs, objects, components, data structures, etc., that perform a specific function or implement a specific data type. The order in which the operations are described is not intended to be construed as limiting, and any number of described operations can be combined in any order and / or in parallel to implement the process.

[0156] Additionally, process 1100 may be executed under the control of one or more computer systems configured using executable instructions, and may be implemented by hardware or a combination thereof as code (e.g., executable instructions, one or more computer programs, or one or more applications) that executes jointly on one or more processors. As noted above, the code may be stored on a computer-readable or machine-readable storage medium, for example, in the form of a computer program comprising multiple instructions executable by one or more processors. The computer-readable or machine-readable storage medium may be non-transitory.

[0157] Figure 12 This is a block diagram illustrating an example of a computing system 1200 that can be used to select UEs using SL positioning anchors. Specifically, Figure 12 An example of computing system 1200 is illustrated. This computing system can be any computing device, such as constituting an internal computing system, a remote computing system, a camera, or any component thereof, wherein the components of the system communicate with each other using connection 1205. Connection 1205 can be a physical connection using a bus, or a direct connection to processor 1210, such as in a chipset architecture. Connection 1205 can also be a virtual connection, a networking connection, or a logical connection.

[0158] In some aspects, computing system 1200 is a distributed system in which the functions described herein can be distributed across a data center, multiple data centers, a peer-to-peer network, etc. In some aspects, one or more of the described system components represent a plurality of such components, each performing some or all of the functions described for that component. In some aspects, the components can be physical or virtual devices.

[0159] Example system 1200 includes at least one processing unit (CPU or processor) 1210 and a connection 1205 that communicatively couples various system components, including system memories 1215 such as read-only memory (ROM) 1220 and random access memory (RAM) 1225, to processor 1210. Computing system 1200 may include a cache 1212 of high-speed memory that is directly connected to, closely proximate to, or integrated into processor 1210.

[0160] Processor 1210 may include any general-purpose processor and hardware or software services (such as services 1232, 1234, and 1236 stored in storage device 1230 and configured to control processor 1210), as well as dedicated processors in which software instructions are incorporated into the actual processor design. Processor 1210 may be a substantially completely independent computing system containing multiple cores or processors, buses, memory controllers, caches, etc. Multi-core processors may be symmetric or asymmetric.

[0161] To enable user interaction, the computing system 1200 includes an input device 1245 that can represent any number of input mechanisms, such as a microphone for voice, a touch-sensitive screen for gesture or graphic input, a keyboard, a mouse, motion input, voice input, etc. The computing system 1200 may also include an output device 1235 that can be one or more of a plurality of output mechanisms. In some instances, a multi-mode system allows the user to provide multiple types of input / output to communicate with the computing system 1200.

[0162] The computing system 1200 may include a communication interface 1240, which typically controls and manages user input and system output. The communication interface may perform or facilitate the receiving and / or transmitting of wired or wireless communications using wired and / or wireless transceivers, including utilizing audio jacks / plugs, microphone jacks / plugs, Universal Serial Bus (USB) ports / plugs, Apple... ™ Lightning ™ Ports / plugs, Ethernet ports / plugs, fiber optic ports / plugs, dedicated wired ports / plugs, 3G, 4G, 5G and / or other cellular data network wireless signal transmission, Bluetooth ™ Wireless signal transmission, Bluetooth ™ Low-power (BLE) wireless signal transmission, IBEACON ™Wireless signal transmission, radio frequency identification (RFID) wireless signal transmission, near field communication (NFC) wireless signal transmission, dedicated short range communication (DSRC) wireless signal transmission, 802.11 Wi-Fi wireless signal transmission, wireless local area network (WLAN) signal transmission, visible light communication (VLC), microwave access global interoperability (WiMAX), infrared (IR) wireless signal transmission, public switched telephone network (PSTN) signal transmission, integrated services digital network (ISDN) signal transmission, ad hoc network signal transmission, radio wave signal transmission, microwave signal transmission, infrared signal transmission, visible light signal transmission, ultraviolet light signal transmission, wireless signal transmission along the electromagnetic spectrum, or those communications in some combination thereof.

[0163] The communication interface 1240 may also include one or more ranging sensors (e.g., LIDAR sensors, laser rangefinders, RF radars, ultrasonic sensors, and infrared (IR) sensors) configured to collect data and provide measurements to the processor 1210, thereby configuring the processor 1210 to perform determinations and calculations required to obtain various measurements from the one or more ranging sensors. In some examples, measurements may include time of flight, wavelength, azimuth, elevation, distance, linear velocity, and / or angular velocity, or any combination thereof. The communication interface 1240 may also include one or more Global Navigation Satellite System (GNSS) receivers or transceivers used to determine the position of the computing system 1200 based on one or more signals received from one or more satellites associated with one or more GNSS systems. GNSS systems include, but are not limited to, the U.S. GPS, the Russian GLONASS, the Chinese BeiDou Navigation Satellite System (BDS), and the European Galileo GNSS. There are no limitations on operation on any particular hardware arrangement, and therefore the basic features here can be easily replaced to obtain improved hardware or firmware arrangements as they are developed.

[0164] Storage device 1230 may be a non-volatile and / or non-transitory and / or computer-readable medium (e.g., a computer-readable storage device), and may be a hard disk or other type of computer-readable medium capable of storing data accessible by a computer, such as magnetic tape, flash memory cards, solid-state storage devices, digital versatile discs, cartridges, floppy disks, hard disks, magnetic tapes, magnetic stripes, any other magnetic storage media, flash memory, memristor memory, any other solid-state storage, CD-ROM, rewritable CD, digital video disc (DVD), Blu-ray Disc (BDD), holographic disc, another optical medium, secure digital (SD) card, micro-secure digital (microSD) card, Memory Stick. ® Cards, smart card chips, EMV chips, Subscriber Identity Module (SIM) cards, mini / micro / nano / micro SIM cards, another integrated circuit (IC) chip / card, random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash EPROM, cache memory (e.g., layer 1 (L1) cache, layer 2 (L2) cache, layer 3 (L3) cache, layer 4 (L4) cache, layer 5 (L5) cache, or other (L#) cache), resistive random access memory (RRAM / ReRAM), phase change memory (PCM), spin-transfer torque RAM (STT-RAM), another memory chip or cassette and / or combinations thereof.

[0165] Storage device 1230 may include software services, servers, services, etc., which enable the system to perform functions when the code defining such software is executed by processor 1210. In some aspects, hardware services performing specific functions may include software components for performing functions stored in a computer-readable medium connected to necessary hardware components such as processor 1210, connection 1205, output device 1235, etc. The term "computer-readable medium" includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other media capable of storing, containing, or carrying instructions and / or data. Computer-readable media may include non-transitory media in which data can be stored and which does not include carrier waves and / or transient electronic signals propagating wirelessly or over a wired connection. Examples of non-transitory media may include, but are not limited to, magnetic disks or magnetic tapes, optical storage media such as compact discs (CDs) or digital versatile discs (DVDs), flash memory, memory, or memory devices. Computer-readable media may store code and / or machine-executable instructions thereon, which may represent procedures, functions, subroutines, programs, routines, subroutines, modules, software packages, classes, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or hardware circuitry by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc., may be passed, forwarded, or transmitted via any suitable means, including memory sharing, message passing, token passing, network transmission, etc.

[0166] Specific details have been provided in the foregoing description to offer a thorough understanding of the aspects and examples presented herein, but those skilled in the art will recognize that this application is not limited thereto. Therefore, although illustrative aspects of this application have been described in detail herein, it is to be understood that the various inventive concepts may be embodied and employed in various other ways, and the appended claims are not intended to be construed as including these variations unless limited by prior art. The various features and aspects of the applications described above may be used individually or in combination. Furthermore, without departing from the broader scope of this specification, aspects may be used in any number of environments and applications beyond those described herein. Therefore, the specification and drawings should be considered illustrative rather than restrictive. For illustrative purposes, the methods are described in a particular order. It should be understood that, in alternative aspects, the methods may be performed in a different order than described.

[0167] For clarity, in some instances, this technology may be presented as comprising various functional blocks, which include devices, device components, steps, or routines embodied in a method, either in software or a combination of hardware and software. Additional components may be used in addition to those shown in the figures and / or described herein. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form to avoid obscuring these aspects in unnecessary detail. In other cases, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail to avoid obscuring the aspects.

[0168] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, modules, circuits, and algorithm 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 between hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described above in general terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific 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 specific application, but such specific implementation decisions should not be construed as departing from the scope of this disclosure.

[0169] Various aspects described above can be presented as processes or methods, depicted as flowcharts, diagrams, data flow graphs, structure diagrams, or block diagrams. Although flowcharts can describe operations as sequential processes, many operations within an operation can be executed in parallel or concurrently. Furthermore, the order of operations can be rearranged. A process terminates when its operations are completed, but a process may have additional steps not included in the accompanying diagrams. A process can correspond to a method, function, procedure, subroutine, subroutine, etc. When a process corresponds to a function, its termination may correspond to the function returning to the calling function or the main function.

[0170] The processes and methods described in the examples above can be implemented using stored computer-executable instructions or computer-executable instructions otherwise obtainable from a computer-readable medium. Such instructions may include, for example, instructions and data that configure, or otherwise configure, a general-purpose computer, special-purpose computer, or processing device to perform a function or group of functions. The portion may be accessible via a network of the computer resources used. The computer-executable instructions may be, for example, binary, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that can be used to store the instructions, the information used, and / or information created during the methods according to the described examples include disks or optical discs, flash memory, USB devices with non-volatile memory, networked storage devices, etc.

[0171] In some respects, computer-readable storage devices, media, and memories may include cables or wireless signals containing bit streams, etc. However, when referred to, non-transitory computer-readable storage media explicitly exclude media such as energy, carrier signals, electromagnetic waves, and the signals themselves.

[0172] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may, in some cases, be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, etc.

[0173] The various exemplary logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented or performed using hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof, and may take any form factor of various form factors. When implemented in software, firmware, middleware, or microcode, program code or code segments (e.g., computer program products) for performing necessary tasks may be stored in a computer-readable or machine-readable medium. A processor may perform the necessary tasks. Examples of form factors include laptop computers, smartphones, mobile phones, tablet devices, or other small form factor personal computers, personal digital assistants, rack-mounted devices, standalone devices, etc. The functionality described herein may also be embodied in peripheral devices or intercalation cards. By further example, such functionality may also be implemented on circuit boards of different chips or different processes executed on a single device.

[0174] Instructions, media for transmitting such instructions, computing resources for executing them, and other structures for supporting such computing resources are example components for providing the functionality described in this disclosure.

[0175] The techniques described herein can also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such techniques can be implemented in any of a variety of devices, such as general-purpose computers, wireless communication devices (mobile phones), or integrated circuit devices with multiple uses, including applications in wireless communication devices (mobile phones) and other devices. Any feature described as a module or component can be implemented together in an integrated logic device or separately as discrete but interoperable logic devices. If implemented in software, the techniques can be implemented at least in part by a computer-readable data storage medium comprising program code including instructions that, when executed, perform one or more of the methods, algorithms, and / or operations described above. The computer-readable data storage medium can form part of a computer program product, which may include packaging material. The computer-readable medium may include memory or data storage media, such as random access memory (RAM) (such as synchronous dynamic random access memory (SDRAM)), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic or optical data storage media, etc. Additionally or alternatively, the technology may be implemented at least in part by a computer-readable communication medium that carries or conveys program code in the form of instructions or data structures that can be accessed, read and / or executed by a computer, such as propagated signals or waves.

[0176] The program code can be executed by a processor, which may include one or more processors, such as one or more digital signal processors (DSPs), general-purpose microprocessors, application-specific integrated circuits (ASICs), field-programmable arrays (FPGAs), or other equivalent integrated or discrete logic circuits. Such processors can be configured to perform any of the techniques described in this disclosure. A general-purpose processor may be a microprocessor; however, in alternatives, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. Therefore, as used herein, the term "processor" may refer to any of the foregoing structures, any combination of the foregoing structures, or any other structure or means suitable for implementing the techniques described herein.

[0177] Those skilled in the art will understand that, without departing from the scope of this description, the less than (“<”) and greater than (“>”) symbols or terms used herein may be replaced with less than or equal to (“>”) respectively. ") and greater than or equal to (" The symbol ) is used instead.

[0178] When a component is described as being “configured” to perform certain operations, such configuration can be achieved, for example, by designing electronic circuits or other hardware to perform the operations, by programming programmable electronic circuits (e.g., microprocessors or other suitable electronic circuits) to perform the operations, or any combination thereof.

[0179] The phrase “coupled to” or “communicatively coupled to” means that any component is physically connected directly or indirectly to another component, and / or that any component is in communication with another component directly or indirectly (e.g., connected to that other component via a wired or wireless connection and / or other suitable communication interface).

[0180] Claim language or other languages ​​that state "at least one of" and / or "one or more of" in a set indicate that one member of the set or multiple members of the set (in any combination) satisfy the claim. For example, claim language stating "at least one of A and B" or "at least one of A or B" means A, B, or A and B. In another example, claim language stating "at least one of A, B, and C" or "at least one of A, B, or C" means A, B, C, or A and B, or A and C, or B and C, A and B and C, or any repetition is information or data (e.g., A and A, B and B, C and C, A and A and B, etc.), or any other ordering, repetition, or combination of A, B, and C. The language "at least one of the set" and / or "one or more of the set" does not limit the set to the items listed in the set. For example, the language of a claim stating "at least one of A and B" or "at least one of A or B" may refer to A, B, or A and B, and may additionally include items not listed in the set of A and B. The phrases "at least one" and "one or more" are used interchangeably herein.

[0181] Claims using language such as "at least one processor, the at least one processor being configured to," "at least one processor being configured to," "one or more processors, the one or more processors being configured to," or "one or more processors being configured to," indicate that one or more processors (in any combination) are capable of performing associated operations. For example, a claim using language stating "at least one processor, the at least one processor being configured to: X, Y, and Z" means that a single processor can be used to perform operations X, Y, and Z; or that multiple processors are each assigned a specific subset of tasks of operations X, Y, and Z, such that the multiple processors together perform X, Y, and Z; or that a group of multiple processors work together to perform operations X, Y, and Z. In another example, a claim using language stating "at least one processor, the at least one processor being configured to: X, Y, and Z" may mean that any single processor can perform only at least one subset of operations X, Y, and Z.

[0182] When referring to one or more elements that perform functions (e.g., steps of a method), one element may perform all functions, or more than one element may jointly perform these functions. When more than one element jointly performs these functions, each function does not need to be performed by every single element (e.g., different functions may be performed by different elements), and / or each function does not need to be performed by only one element as a whole (e.g., different elements may perform different sub-functions of a function). Similarly, when referring to one or more elements configured to cause another element (e.g., a device) to perform functions, one element may be configured to cause another element to perform all functions, or more than one element may be jointly configured to cause another element to perform these functions.

[0183] When referring to an entity that performs or is configured to perform functions (e.g., steps of a method) (e.g., any entity or device described herein), the entity may be configured to cause one or more elements (individually or collectively) to perform those functions. One or more components of the entity may include at least one memory, at least one processor, at least one communication interface, another component configured to perform one or more of those functions, and / or any combination thereof. When referring to an entity that performs functions, the entity may be configured to cause one component to perform all functions, or to cause more than one component to perform those functions collectively. When the entity is configured to cause more than one component to perform those functions collectively, each function does not need to be performed by every single component (e.g., different functions may be performed by different components), and / or each function does not need to be performed by only one component as a whole (e.g., different components may perform different sub-functions of a function).

[0184] The various exemplary logic blocks, modules, engines, circuits, and algorithm steps described in conjunction with the embodiments disclosed herein can be implemented as electronic hardware, computer software, firmware, or combinations thereof. To clearly illustrate this interchangeability between hardware and software, various exemplary components, blocks, engines, modules, circuits, and steps have been broadly described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as departing from the scope of this application.

[0185] The techniques described herein can also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such techniques can be implemented in any of a variety of devices, such as general-purpose computers, wireless communication devices (mobile phones), or integrated circuit devices with multiple uses, including applications in wireless communication devices (mobile phones) and other devices. Any feature described as an engine, module, or component can be implemented together in an integrated logic device or separately as discrete but interoperable logic devices. If implemented in software, these techniques can be implemented at least in part by a computer-readable data storage medium comprising program code including instructions that, when executed, perform one or more of the methods described above. The computer-readable data storage medium can form part of a computer program product, which may include packaging material. The computer-readable medium may include memory or data storage media, such as random access memory (RAM) (such as synchronous dynamic random access memory (SDRAM)), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic or optical data storage media, etc. Additionally or alternatively, the technology may be implemented at least in part by a computer-readable communication medium that carries or conveys program code in the form of instructions or data structures that can be accessed, read and / or executed by a computer, such as propagated signals or waves.

[0186] The program code can be executed by a processor, which may include one or more processors, such as one or more digital signal processors (DSPs), general-purpose microprocessors, application-specific integrated circuits (ASICs), field-programmable arrays (FPGAs), or other equivalent integrated or discrete logic circuits. Such processors can be configured to perform any of the techniques described in this disclosure. A general-purpose processor may be a microprocessor; however, in alternatives, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. Therefore, as used herein, the term "processor" may refer to any of the foregoing structures, any combination of the foregoing structures, or any other structure or means suitable for implementing the techniques described herein. Furthermore, in some aspects, the functionality described herein may be provided within dedicated software or hardware modules configured for encoding and decoding, or incorporated into a combined video encoder-decoder (CODEC).

[0187] The exemplary aspects of this disclosure include: Aspect 1. A first network device for wireless communication, the first network device comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to: receive from a plurality of second network devices a corresponding anchor selection criterion for each of the plurality of second network devices; determine from the plurality of second network devices a network device as an anchor device for determining the location of the first network device based on the corresponding anchor selection criterion for each of the plurality of second network devices; and determine the location of the first network device based on the anchor device.

[0188] Aspect 2. The first network device according to aspect 1, wherein the corresponding anchor selection criterion for each of the plurality of second network devices includes at least one of the following: the corresponding user equipment (UE) type of each second network device, one or more sources of the corresponding location of each second network device, the age of the corresponding location of each second network device, the validity period of the corresponding location of each second network device, the accuracy period of the corresponding location of each second network device, or the auxiliary data validity of the corresponding location of each second network device.

[0189] Aspect 3. The first network device according to aspect 2, wherein the corresponding anchor selection criterion for each of the plurality of second network devices further includes at least one of the following: the corresponding location of each second network device, or the source diversity of the corresponding location of each second network device.

[0190] Aspect 4. The first network device according to any one of Aspects 2 or 3, wherein the one or more sources at the respective location of each second network device include at least one of the following: one or more Global Navigation Satellite System (GNSS) sources, one or more geodetic sources, one or more sidelink (SL) signal sources, one or more wireless network (Uu) signal sources, one or more Uu positioning sources, or one or more WiFi positioning sources.

[0191] Aspect 5. The first network device according to aspect 4, wherein each of the one or more GNSS sources is one of the following: a Global Positioning System (GPS) satellite, a Global Navigation Satellite System (GLONASS) satellite, a Galileo satellite, a BeiDou Navigation Satellite System (BDS) satellite, a Quasi-Zenith Satellite System (QZSS) satellite, or an Indian Navigation Constellation (NavIC) satellite.

[0192] Aspect 6. The first network device according to any one of Aspects 2 to 5, wherein the corresponding UE type is a resident UE or a mobile UE.

[0193] Aspect 7. The first network device according to aspect 6, wherein the camped UE is a roadside unit (RSU).

[0194] Aspect 8. The first network device according to any one of Aspects 6 or 7, wherein the mobile UE is a vehicle or a mobile phone.

[0195] Aspect 9. A first network device according to any one of Aspects 1 to 8, wherein, in order to determine the location of the first network device based on the anchor device, the at least one processor is configured to: receive one or more side link (SL) signals from the anchor device by the first network device; and determine the location of the first network device based on measurements of the one or more SL signals by the first network device.

[0196] Aspect 10. The first network device according to any one of Aspects 1 to 9, wherein the at least one processor is configured to receive the corresponding anchor selection criteria via Side Link Positioning Protocol (SLPP) signaling.

[0197] Aspect 11. A method for wireless communication at a first network device, the method comprising: receiving, by the first network device, a corresponding anchor selection criterion for each of the plurality of second network devices from a plurality of second network devices; determining, by the first network device, a network device from the plurality of second network devices as an anchor device for determining the location of the first network device based on the corresponding anchor selection criterion for each of the plurality of second network devices; and determining the location of the first network device based on the anchor device.

[0198] Aspect 12. The method according to aspect 11, wherein the corresponding anchor selection criterion for each of the plurality of second network devices includes at least one of the following: the corresponding user equipment (UE) type of each second network device, one or more sources of the corresponding location of each second network device, the age of the corresponding location of each second network device, the validity period of the corresponding location of each second network device, the accuracy period of the corresponding location of each second network device, or the auxiliary data validity of the corresponding location of each second network device.

[0199] Aspect 13. The method according to aspect 12, wherein the corresponding anchor selection criterion for each of the plurality of second network devices further includes at least one of the following: the corresponding location of each second network device, or the source diversity of the corresponding location of each second network device.

[0200] Aspect 14. The method according to any one of Aspects 12 or 13, wherein the one or more sources of the respective location of each second network device include at least one of the following: one or more Global Navigation Satellite System (GNSS) sources, one or more geodetic sources, one or more sidelink (SL) signal sources, one or more wireless network (Uu) signal sources, one or more Uu positioning sources, or one or more WiFi positioning sources.

[0201] Aspect 15. The method according to aspect 14, wherein each of the one or more GNSS sources is one of the following: a Global Positioning System (GPS) satellite, a Global Navigation Satellite System (GLONASS) satellite, a Galileo satellite, a BeiDou Navigation Satellite System (BDS) satellite, a Quasi-Zenith Satellite System (QZSS) satellite, or an Indian Navigation Constellation (NavIC) satellite.

[0202] Aspect 16. The method according to any one of Aspects 12 to 15, wherein the corresponding UE type is a stationary UE or a mobile UE.

[0203] Aspect 17. The method according to aspect 16, wherein the stationed UE is a roadside unit (RSU).

[0204] Aspect 18. The method according to any one of Aspects 16 or 17, wherein the mobile UE is a vehicle or a mobile phone.

[0205] Aspect 19. The method according to any one of Aspects 11 to 18, wherein determining the location of the first network device based on the anchor device comprises: the first network device receiving one or more side link (SL) signals from the anchor device; and the first network device determining the location of the first network device based on measurements of the one or more SL signals.

[0206] Aspect 20. The method according to any one of Aspects 11 to 19, wherein the corresponding anchor selection criteria are received via Side Link Positioning Protocol (SLPP) signaling.

[0207] Aspect 21. A first network device for wireless communication, the first network device comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to: determine anchor selection criteria for the first network device, wherein the anchor selection criteria for the first network device includes at least one of: user equipment (UE) type of the first network device, one or more sources of the location of the first network device, age of the location of the first network device, validity duration of the location of the first network device, accuracy duration of the location of the first network device, or auxiliary data validity of the location of the first network device; and output the anchor selection criteria for transmission to a second network device.

[0208] Aspect 22. The first network device according to aspect 21, wherein the anchor selection criterion for the first network device further includes at least one of the following: the corresponding location of the first network device, or the source diversity of the location of the first network device.

[0209] Aspect 23. The first network device according to any one of Aspects 21 or 22, wherein the one or more sources of the location of the first network device include at least one of the following: one or more Global Navigation Satellite System (GNSS) sources, one or more geodetic sources, one or more sidelink (SL) signal sources, one or more wireless network (Uu) signal sources, one or more Uu positioning sources, or one or more WiFi positioning sources.

[0210] Aspect 24. The first network device according to aspect 23, wherein each of the one or more GNSS sources is one of the following: a Global Positioning System (GPS) satellite, a Global Navigation Satellite System (GLONASS) satellite, a Galileo satellite, a BeiDou Navigation Satellite System (BDS) satellite, a Quasi-Zenith Satellite System (QZSS) satellite, or an Indian Navigation Constellation (NavIC) satellite.

[0211] Aspect 25. The first network device according to any one of Aspects 21 to 24, wherein the UE type is a resident UE or a mobile UE.

[0212] Aspect 26. The first network device according to aspect 25, wherein the camped UE is a roadside unit (RSU).

[0213] Aspect 27. The first network device according to any one of Aspects 25 or 26, wherein the mobile UE is a vehicle or a mobile phone.

[0214] Aspect 28. The first network device according to any one of Aspects 21 to 27, wherein the at least one processor is configured to output the anchor selection criteria for transmission via Side Link Positioning Protocol (SLPP) signaling.

[0215] Aspect 29. A method for wireless communication at a first network device, the method comprising: determining anchor selection criteria for the first network device, wherein the anchor selection criteria for the first network device includes at least one of: user equipment (UE) type of the first network device, one or more sources of the location of the first network device, age of the location of the first network device, validity duration of the location of the first network device, accuracy duration of the location of the first network device, or auxiliary data validity of the location of the first network device; and transmitting the anchor selection criteria to a second network device.

[0216] Aspect 30. The method according to aspect 29, wherein the anchor selection criterion for the first network device further includes at least one of the following: the corresponding location of the first network device, or the source diversity of the location of the first network device.

[0217] Aspect 31. The method according to any one of Aspects 29 or 30, wherein the one or more sources of the location of the first network device include at least one of the following: one or more Global Navigation Satellite System (GNSS) sources, one or more geodetic sources, one or more sidelink (SL) signal sources, one or more wireless network (Uu) signal sources, one or more Uu positioning sources, or one or more WiFi positioning sources.

[0218] Aspect 32. The method according to aspect 31, wherein each of the one or more GNSS sources is one of the following: a Global Positioning System (GPS) satellite, a Global Navigation Satellite System (GLONASS) satellite, a Galileo satellite, a BeiDou Navigation Satellite System (BDS) satellite, a Quasi-Zenith Satellite System (QZSS) satellite, or an Indian Navigation Constellation (NavIC) satellite.

[0219] Aspect 33. The method according to any one of Aspects 29 to 32, wherein the UE type is a stationary UE or a mobile UE.

[0220] Aspect 34. The method according to aspect 33, wherein the stationed UE is a roadside unit (RSU).

[0221] Aspect 35. The method according to any one of Aspects 33 or 34, wherein the mobile UE is a vehicle or a mobile phone.

[0222] Aspect 36. The method according to any one of Aspects 29 to 35, wherein the anchor selection criteria are transmitted via Side Link Positioning Protocol (SLPP) signaling.

[0223] Aspect 37. An apparatus comprising one or more components for performing operations according to any one of aspects 11 to 20.

[0224] Aspect 38. A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform any one of aspects 11 to 20.

[0225] Aspect 39. An apparatus comprising one or more components for performing the operation according to any one of aspects 29 to 36.

[0226] Aspect 40. A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform any one of aspects 29 to 36.

[0227] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be consistent with the full scope of the language claims, wherein an element referred to in the singular is not intended to mean "one and only one," but rather "one or more" unless specifically stated otherwise.

Claims

1. A first network device for wireless communication, the first network device comprising: At least one memory; and At least one processor, the at least one processor being coupled to the at least one memory and being configured to: Receive the corresponding anchor selection criteria for each of the plurality of second network devices; A network device is selected from the plurality of second network devices as an anchor device for determining the location of the first network device based on the corresponding anchor selection criteria for each of the plurality of second network devices; as well as The location of the first network device is determined based on the anchor device.

2. The first network device of claim 1, wherein the corresponding anchor selection criterion for each of the plurality of second network devices includes at least one of the following: the corresponding user equipment (UE) type of each second network device, one or more sources of the corresponding location of each second network device, the age of the corresponding location of each second network device, the validity period of the corresponding location of each second network device, the accuracy period of the corresponding location of each second network device, or the auxiliary data validity of the corresponding location of each second network device.

3. The first network device according to claim 2, wherein the corresponding anchor selection criterion for each of the plurality of second network devices further includes at least one of the following: the corresponding location of each second network device, or the source diversity of the corresponding location of each second network device.

4. The first network device of claim 2, wherein the one or more sources at the respective locations of each second network device include at least one of the following: one or more Global Navigation Satellite System (GNSS) sources, one or more geodetic sources, one or more sidelink (SL) signal sources, one or more wireless network (Uu) signal sources, one or more Uu positioning sources, or one or more WiFi positioning sources.

5. The first network device according to claim 4, wherein each of the one or more GNSS sources is one of the following: a Global Positioning System (GPS) satellite, a Global Navigation Satellite System (GLONASS) satellite, a Galileo satellite, a BeiDou Navigation Satellite System (BDS) satellite, a Quasi-Zenith Satellite System (QZSS) satellite, or an Indian Navigation Constellation (NavIC) satellite.

6. The first network device according to claim 2, wherein the corresponding UE type is a stationary UE or a mobile UE.

7. The first network device according to claim 6, wherein the camped UE is a roadside unit (RSU).

8. The first network device according to claim 6, wherein the mobile UE is a vehicle or a mobile phone.

9. The first network device of claim 1, wherein, in order to determine the location of the first network device based on the anchor device, the at least one processor is configured to: The first network device receives one or more side link (SL) signals from the anchor device; and The location of the first network device is determined by the first network device based on measurements of the one or more SL signals.

10. The first network device of claim 1, wherein the at least one processor is configured to receive the corresponding anchor selection criteria via Side Link Positioning Protocol (SLPP) signaling.

11. A method for wireless communication at a first network device, the method comprising: The first network device receives, from a plurality of second network devices, a corresponding anchor selection criterion for each of the plurality of second network devices; The first network device determines a network device from the plurality of second network devices as an anchor device for determining the location of the first network device based on the corresponding anchor selection criteria for each of the plurality of second network devices; as well as The location of the first network device is determined based on the anchor device.

12. The method of claim 11, wherein the corresponding anchor selection criterion for each of the plurality of second network devices includes at least one of the following: the corresponding user equipment (UE) type of each second network device, one or more sources of the corresponding location of each second network device, the age of the corresponding location of each second network device, the validity period of the corresponding location of each second network device, the accuracy period of the corresponding location of each second network device, or the auxiliary data validity of the corresponding location of each second network device.

13. The method of claim 12, wherein the corresponding anchor selection criterion for each of the plurality of second network devices further includes at least one of the following: the corresponding location of each second network device, or the source diversity of the corresponding location of each second network device.

14. The method of claim 12, wherein the one or more sources for the respective location of each second network device include at least one of the following: one or more Global Navigation Satellite System (GNSS) sources, one or more geodetic sources, one or more sidelink (SL) signal sources, one or more wireless network (Uu) signal sources, one or more Uu positioning sources, or one or more WiFi positioning sources.

15. The method of claim 14, wherein each of the one or more GNSS sources is one of the following: a Global Positioning System (GPS) satellite, a Global Navigation Satellite System (GLONASS) satellite, a Galileo satellite, a BeiDou Navigation Satellite System (BDS) satellite, a Quasi-Zenith Satellite System (QZSS) satellite, or an Indian Navigation Constellation (NavIC) satellite.

16. The method of claim 12, wherein the corresponding UE type is a stationary UE or a mobile UE.

17. The method of claim 16, wherein the stationed UE is a roadside unit (RSU).

18. The method of claim 16, wherein the mobile UE is a vehicle or a mobile phone.

19. The method of claim 11, wherein determining the location of the first network device based on the anchor device comprises: The first network device receives one or more side link (SL) signals from the anchor device; as well as The location of the first network device is determined by the first network device based on measurements of the one or more SL signals.

20. The method of claim 11, wherein the corresponding anchor selection criteria are received via Side Link Positioning Protocol (SLPP) signaling.

21. A first network device for wireless communication, the first network device comprising: At least one memory; and At least one processor, the at least one processor being coupled to the at least one memory and being configured to: Determine anchor selection criteria for the first network device, wherein the anchor selection criteria for the first network device include at least one of the following: the user equipment (UE) type of the first network device, one or more sources of the location of the first network device, the age of the location of the first network device, the validity period of the location of the first network device, the accuracy period of the location of the first network device, or the validity of auxiliary data for the location of the first network device; and The anchor selection criteria are output for transmission to the second network device.

22. The first network device of claim 21, wherein the anchor selection criterion for the first network device further includes at least one of the following: the corresponding location of the first network device, or the source diversity of the location of the first network device.

23. The first network device of claim 21, wherein the one or more sources of the location of the first network device include at least one of the following: one or more Global Navigation Satellite System (GNSS) sources, one or more geodetic sources, one or more sidelink (SL) signal sources, one or more wireless network (Uu) signal sources, one or more Uu positioning sources, or one or more WiFi positioning sources.

24. The first network device of claim 23, wherein each of the one or more GNSS sources is one of the following: a Global Positioning System (GPS) satellite, a Global Navigation Satellite System (GLONASS) satellite, a Galileo satellite, a BeiDou Navigation Satellite System (BDS) satellite, a Quasi-Zenith Satellite System (QZSS) satellite, or an Indian Navigation Constellation (NavIC) satellite.

25. The first network device according to claim 21, wherein the UE type is a stationary UE or a mobile UE.

26. The first network device according to claim 25, wherein the camped UE is a roadside unit (RSU).

27. The first network device of claim 25, wherein the mobile UE is a vehicle or a mobile phone.

28. The first network device of claim 21, wherein the at least one processor is configured to output the anchor selection criteria for transmission via Side Link Positioning Protocol (SLPP) signaling.

29. A method for wireless communication at a first network device, the method comprising: Determine anchor selection criteria for the first network device, wherein the anchor selection criteria for the first network device include at least one of the following: the user equipment (UE) type of the first network device, one or more sources of the location of the first network device, the age of the location of the first network device, the validity period of the location of the first network device, the accuracy period of the location of the first network device, or the validity of auxiliary data of the location of the first network device. as well as Send the anchor selection criteria to the second network device.

30. The method of claim 29, wherein the anchor selection criterion for the first network device further includes at least one of the following: the corresponding location of the first network device, or the source diversity of the location of the first network device.

Images