Safety-related vehicle-to-x (v2x) transmission

Abstract

A user equipment (UE) for vehicle-to-everything (V2X) transmissions is provided. The UE includes at least one transceiver, at least one memory, and at least one processor coupled with the at least one transceiver and the at least one memory, the at least one processor configured to: detect a second position of a second UE relative to a first position of the UE; generate a warning time window based on the first position of the UE and the second position of the second UE; and schedule at least one transmission from the UE to the second UE based on the warning time window.

Description

Cross-reference to related applications

[0001] This application claims the benefit of U.S. Application No. 18 / 608,634, filed March 18, 2024, entitled “SAFETY-DEPENDENT VEHICLE-TO-EVERYTHING (V2X) TRANSMISSION,” which has been assigned to the assignee of this application and whose entire contents are incorporated herein by reference for all purposes. Background Technology

[0002] Currently, wireless vehicle communication systems are expected to enable higher levels of autonomous driving for certain vehicles using wireless access technologies known as vehicle-to-everything (V2X) communication or direct access technologies (known as DSRC (Dedicated Short Range Communication)). Generally, V2X technology involves high-bandwidth and low-latency communication using sensors, cameras, and wireless connections, allowing vehicles to share real-time information with their drivers, other vehicles, pedestrians, and road infrastructure such as traffic lights. It is typically desired to be able to determine the position of one or more target vehicles relative to a source vehicle. Generally, the source vehicle is configured to determine the position of the target vehicle by sending and receiving periodic messages to and from the target vehicle.

[0003] As an example, current V2X systems periodically broadcast Basic Safety Messages (BSM) or Cooperative Awareness Messages (CAM) at a sufficiently high rate to have a high enough probability of being received "on time" by neighboring target vehicles. However, this is not an efficient use of the wireless spectrum. Summary of the Invention

[0004] Techniques for systems and methods for safety-related vehicle-to-everything (V2X) transmissions performed by user equipment (UE) are discussed. The UE has a first location and includes: at least one transceiver; at least one memory; and at least one processor that communicates signalingly with the at least one transceiver and the at least one memory. The at least one processor is configured to: detect a second location of a second UE relative to the first location of the UE; generate an alert time window based on the first location of the UE and the second location of the second UE; and schedule at least one transmission from the first UE to the second UE based on the alert time window.

[0005] A method for security-related V2X transmissions performed by a first UE having a first location is also discussed. The method includes: using the first UE to detect a second location of a second UE relative to the first location of the first UE; generating an alert time window based on the first location of the first UE and the second location of the second UE; and scheduling at least one transmission from the first UE to the second UE based on the alert time window.

[0006] A UE is also discussed, comprising: components for detecting a second location of a second UE relative to the first location of the UE; components for generating a warning time window based on the first location of the UE and the second location of the second UE; and components for scheduling at least one transmission from the UE to the second UE based on the warning time window.

[0007] Other devices, apparatuses, systems, methods, features, and advantages of the present invention will be apparent to or will become apparent to those skilled in the art upon studying the following figures and detailed description. All such additional devices, apparatuses, systems, methods, features, and advantages are intended to be included within this description, within the scope of the invention, and protected by the appended claims. Attached Figure Description

[0008] Figure 1 This is a simplified diagram of an example wireless communication system.

[0009] Figure 2 yes Figure 1 The system block diagram shown is of the components of an example user equipment.

[0010] Figure 3 yes Figure 1 The system block diagram shown is of the components of an example send / receive point.

[0011] Figure 4 yes Figure 1 The system block diagram of the components of the example server is shown.

[0012] Figure 5 This is a functional system block diagram of an example of a specific implementation of a user equipment (UE) for security-related V2X transmission according to this disclosure.

[0013] Figure 6 It is a graph illustrating an example of the trajectory of a first vehicle and a second vehicle, including a UE, along a route according to this disclosure.

[0014] Figure 7 It is based on this disclosure for determining Figure 6 The graph shows an example of a specific implementation of a technique for providing useful warning time windows for the first and second vehicles along a route.

[0015] Figure 8 It is based on this disclosure Figure 5 A flowchart illustrating a specific implementation of a process for secure transmission performed by a UE.

[0016] Figure 9 This is a functional diagram illustrating examples of specific implementations of multiple V2X applications according to this disclosure, in which there are multiple receiving UEs with different useful warning times.

[0017] Figure 10 It is by Figure 5 The flowchart shows an example of a specific implementation of the method performed by the UE. Detailed Implementation

[0018] Techniques for systems and methods used for safety-related vehicle-to-everything (V2X) transmission by user equipment (UE) are discussed. Generally, these techniques optimize V2X transmission to improve spectrum efficiency. As examples, these techniques include aspects, features, or both: a discovery phase where the transmitting UE needs to know the location of any neighboring UEs in order to adjust its transmission schedule, wherein discovery can be based on various types of information indicating the location of neighboring UEs; a useful warning time window determination phase based on the location of neighboring UEs, wherein the transmitting UE can determine which receiving UEs (among neighboring UEs) will benefit most from messages from the transmitting UE, and this determination can be based on various factors, including the message's relevance to its relevant / useful applications and / or collision risk (RoC), etc.; and a scheduling and transmission phase where the transmitting UE then determines / adjusts its transmission schedule to maximize the probability that receiving UEs will receive messages for the maximum number of "applications" or the usage of messages transmitted by the transmitting UE within the useful warning time window.

[0019] As an example, these technologies may include a method for security-related V2X transmission performed by a first UE having a first location, wherein the method includes: using the first UE to detect a second location of a second UE relative to the first location of the first UE; generating an alert time window based on the first location of the first UE and the second location of the second UE; and scheduling at least one transmission from the first UE to the second UE based on the alert time window.

[0020] Using these techniques, V2X transmissions by the sending UE can be customized to be received by the receiving UE within a "useful warning" time window. Therefore, the receiving UE receives information from the sending UE that is not received too early or too late to be useful for the receiving UE's consumption applications. Generally, these techniques include: techniques for determining the useful warning time window for each V2X application within neighboring / target UEs; adjustments to the sending UE's transmission scheduling; and coordination for transmissions of concurrent applications.

[0021] The description herein can refer to a sequence of actions to be performed, for example, by elements of a computing device. The various actions described herein can be performed by special-purpose circuitry (e.g., an application-specific integrated circuit (ASIC)), by program instructions being executed by one or more processors, or by a combination of both. The sequence of actions described herein can be embodied in a non-transitory computer-readable medium storing a corresponding set of computer instructions that, when executed, will cause the associated processor to perform the functionality described herein. Therefore, the various examples described herein can be embodied in several different forms, all of which fall within the scope of this disclosure, including the claimed subject matter.

[0022] As used herein, the terms “User Equipment” (UE) and “Base Station” are not specific to or otherwise limited to any particular Radio Access Technology (RAT) unless otherwise indicated. Generally, a UE can be any wireless communication device (e.g., mobile phone, router, tablet computer, laptop computer, consumer asset tracking device, Internet of Things (IoT) device, etc.) used 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” can be interchangeably referred to as “Access Terminal” or “AT,” “Client Equipment,” “Wireless Equipment,” “Subscriber Equipment,” “Subscriber Terminal,” “Subscriber Station,” “User Terminal” or “UT,” “Mobile Terminal,” “Mobile Station,” “Mobile Equipment,” or variations thereof. In general, 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 via wired access networks, WiFi, etc. ® Networks (e.g., based on IEEE (Institute of Electrical and Electronics Engineers) 802.11, etc.). In addition to exchanging information with each other via a network, or instead of exchanging information with each other via a network, two or more UEs can communicate directly.

[0023] Depending on the network in which the base station is deployed, the base station can operate according to one of several RATs when communicating with the UE. Examples of base stations include access points (APs), network nodes, NodeBs, evolved NodeBs (eNBs), or generic NodeBs (gNodeBs, gNBs). Furthermore, in some systems, the base station may only provide edge node signaling functions, while in others, it may provide additional control and / or network management functions.

[0024] The UE can be represented by any of several types of devices, including but not limited to printed circuit (PC) cards, compact flash memory devices, external or internal modems, wireless or wired phones, smartphones, tablet devices, consumer asset tracking devices, asset tags, etc. The communication link through which the UE can transmit signals to the RAN is called an uplink channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the RAN can transmit signals to the UE is called a downlink or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term "traffic channel (TCH)" can refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0025] As used herein, depending on the context, the term "cell" or "sector" may correspond to one of a plurality of cells of a base station or to the base station itself. The term "cell" may refer to a logical communication entity used to communicate with a base station (e.g., on a carrier) and may be associated with identifiers to distinguish adjacent cells operating via the same or different carriers (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)). In some examples, a carrier may support multiple cells and may be configured with different cell types based on different protocol types that can provide access to different types of devices (e.g., Machine-Type Communication (MTC), Narrowband Internet of Things (NB-IoT), Enhanced Mobile Broadband (eMBB), or other protocol types). In some examples, the term "cell" may refer to a portion of the geographic coverage area on which a logical entity operates (e.g., a sector).

[0026] refer to Figure 1Examples of communication system 100 include UE 105, UE 106, radio access network (RAN) (here, fifth-generation (5G) next-generation (NG) RAN (NG-RAN) 135), 5G core network (5GC) 140, and server 150. UE 105 and / or UE 106 can be, for example, an IoT device, a location tracker device, a cellular phone, a vehicle (e.g., a car, truck, bus, ship, etc.), or another device. 5G network can also be referred to as a new radio (NR) network; NG-RAN 135 can be referred to as 5G RAN or NR RAN; and 5GC 140 can be referred to as NG core network (NGC). Standardization of NG-RAN and 5GC is underway within the 3rd Generation Partnership Project (3GPP). Therefore, NG-RAN 135 and 5GC 140 can follow current or future standards from 3GPP for 5G support. NG-RAN 135 can be another type of RAN, such as 3G RAN, 4G Long Term Evolution (LTE) RAN, etc. UE 106 can be configured and coupled similarly to UE 105 to transmit signals to and / or receive signals from similar other entities in system 100, but for the sake of simplicity in the accompanying drawings, Figure 1 Such signaling is not indicated in this document. Similarly, for simplicity, the discussion focuses on UE 105. Communication system 100 may utilize information from a constellation 185 of satellite spacecraft (SVs) 190, 191, 192, 193 from a satellite positioning system (SPS) such as GPS, GLONASS, Galileo, or BeiDou, or some other local or regional SPS (such as the Indian Regional Navigation Satellite System (IRNSS), the European Geostationary Navigation Coverage Service (EGNOS), or the Wide Area Augmentation System (WAAS)). Additional components of communication system 100 are described below. Communication system 100 may include additional or optional components.

[0027] like Figure 1As shown, NG-RAN 135 includes NR nodeBs (gNBs) 110a and 110b and a next-generation eNodeB (ng-eNB) 114, and 5GC 140 includes Access and Mobility Management Functions (AMF) 115, Session Management Functions (SMF) 117, Location Management Functions (LMF) 120, and Gateway Mobile Location Center (GMLC) 125. gNBs 110a, 110b, and ng-eNB 114 are communicatively coupled to each other, each configured to conduct bidirectional wireless communication with UE 105, and each communicatively coupled to AMF 115 and configured to conduct bidirectional communication with the AMF. gNBs 110a, 110b, and ng-eNB 114 may be referred to as base stations (BS). AMF 115, SMF 117, LMF 120, and GMLC 125 are communicatively coupled to each other, and the GMLC is communicatively coupled to an external client 130. SMF 117 can be used as the initial contact point for Service Control Function (SCF) (not shown) to create, control, and delete media sessions. Base stations (such as gNB 110a, 110b, and / or ng-eNB 114) can be macrocells (e.g., high-power cellular base stations), small cells (e.g., low-power cellular base stations), or access points (e.g., short-range base stations configured to use short-range technologies such as WiFi). ® WiFi ® Direct connection (WiFi) ® -D), Bluetooth ® ,Bluetooth ® Low power (BLE), Zigbee ® (e.g., one or more of gNB 110a, 110b and / or ng-eNB 114) can be configured to communicate with UE105 via multiple carriers. Each of gNB 110a, 110b and / or ng-eNB 114 can provide communication coverage for a corresponding geographic area (e.g., cell). Each cell can be divided into multiple sectors based on the base station antennas.

[0028] Figure 1Generalized examples of various components are provided, wherein any or all of the components may be appropriately utilized, and each component may be repeated or omitted as needed. Specifically, although a UE 105 is illustrated, many UEs (e.g., hundreds, thousands, millions, etc.) may be utilized in communication system 100. Similarly, communication system 100 may include a larger (or smaller) number of SVs (i.e., more or fewer than the four SVs 190-193 shown), gNBs 110a and 110b, ng-eNB 114, AMF 115, external client 130, and / or other components. The illustrated connections connecting the various components in communication system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. Furthermore, the components may be rearranged, combined, separated, replaced, and / or omitted according to desired functionality.

[0029] Although Figure 1 A 5G-based network is illustrated, but similar network implementations and configurations can be used for other communication technologies such as 3G, Long Term Evolution (LTE), etc. The specific implementations described herein (for 5G technology and / or for one or more other communication technologies and / or protocols) can be used to transmit (or broadcast) directional synchronization signals, receive and measure directional signals at a UE (e.g., UE 105), and / or provide location assistance to UE 105 (via GMLC 125 or other location servers), and / or calculate the location of UE 105 at a location-capable device (such as UE 105, gNB 110a, 110b, or LMF 120) based on measurement parameters received at UE 105 for such directional transmissions. Gateway Mobile Location Center (GMLC) 125, Location Management Function (LMF) 120, Access and Mobility Management Function (AMF) 115, SMF 117, ng-eNB (eNodeB) 114, and gNB (gNodeB) 110a, 110b are examples and may be replaced by, or include, various other location server functions and / or base station functions, respectively.

[0030] System 100 is capable of wireless communication because its components can communicate directly or indirectly (at least sometimes using a wireless connection), for example, via gNB 110a, 110b, ng-eNB 114 and / or 5GC 140 (and / or one or more other devices not shown, such as one or more other transceiver base stations). For indirect communication, the communication can be modified during transmission from one entity to another, for example, by changing the header information of data packets, changing the format, etc. UE 105 may include multiple UEs and may be mobile wireless communication devices, but can communicate wirelessly as well as via wired connections. UE 105 can be any of a variety of devices, such as smartphones, tablets, vehicle-based devices, etc., but these are merely examples, as UE 105 does not need to be any of these configurations, and other configurations of UEs can be used. Other UEs may include wearable devices (e.g., smartwatches, smart jewelry, smart glasses, or head-mounted devices, etc.). Other UEs, whether currently existing or developed in the future, may also be used. In addition, other wireless devices (whether mobile or not) can be implemented within system 100 and can communicate with each other and / or with UE 105, gNB 110a, 110b, ng-eNB 114, 5GC 140, and / or external client 130. For example, such other devices may include Internet of Things (IoT) devices, medical devices, home entertainment and / or automation devices, etc. 5GC 140 can communicate with external client 130 (e.g., a computer system), for example, to allow external client 130 (e.g., via GMLC 125) to request and / or receive location information about UE 105.

[0031] UE 105 or other devices can be configured to communicate in various networks and / or for various purposes and / or using various technologies (e.g., 5G, Wi-Fi). ® Communication, multi-frequency Wi-Fi ® Communication, satellite positioning, and one or more types of communication (e.g., GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), LTE (Long Term Evolution), V2X (vehicle-to-everything communication, e.g., V2P (vehicle-to-pedestrian), V2I (vehicle-to-infrastructure), V2V (vehicle-to-vehicle), etc.), IEEE 802.11p, etc.). V2X communication can be cellular (Cellular-V2X (C-V2X)) and / or WiFi. ®(For example, DSRC (Dedicated Short Range Connection)). System 100 can support operation on multiple carriers (waveform signals of different frequencies). A multi-carrier transmitter can transmit modulated signals simultaneously on multiple carriers. Each modulated signal can be a Code Division Multiple Access (CDMA) signal, a Time Division Multiple Access (TDMA) signal, an Orthogonal Frequency Division Multiple Access (OFDMA) signal, a Single Carrier Frequency Division Multiple Access (SC-FDMA) signal, etc. Each modulated signal can be transmitted on different carriers and can carry pilot, overhead information, data, etc. UEs 105 and 106 can communicate with each other via UE-to-UE sidelink (SL) communication by transmitting on one or more sidelink (SL) channels (such as the Physical Sidelink Synchronization Channel (PSSCH), Physical Sidelink Broadcast Channel (PSBCH), or Physical Sidelink Control Channel (PSCCH)). Direct device-to-device communication (without a network) is generally referred to as sidelink communication, without limiting the communication to a specific protocol.

[0032] UE 105 may include and / or may be referred to as a device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), Secure User Plane Location Enabled (SUPL) terminal (SET), or some other name. Furthermore, UE 105 may correspond to a cellular phone, smartphone, laptop computer, tablet device, PDA, consumer asset tracking device, navigation device, Internet of Things (IoT) device, health monitor, security system, smart city sensor, smart meter, wearable tracker, or some other portable or mobile device. Typically, although not mandatory, UE 105 may use one or more Radio Access Technologies (RATs) to support wireless communication, such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), LTE, High Rate Packet Data (HRPD), IEEE 802.11 WiFi, etc. ® (Also known as Wi-Fi) ® ),Bluetooth ® (BT), WiMax (Global Microwave Access) ® 5G New Radio (NR) (e.g., using NG-RAN 135 and 5GC 140), etc. UE 105 can use a Wireless Local Area Network (WLAN) to support wireless communication, which can connect to other networks (e.g., the Internet) using, for example, digital subscriber line (DSL) or packet cable. Using one or more of these RATs allows UE 105 (e.g., via elements of 5GC 140) Figure 1(not shown in the image), or possibly via GMLC 125, to communicate with external client 130 and / or allow external client 130 (e.g., via GMLC 125) to receive location information about UE 105.

[0033] UE 105 may include a single entity or may include multiple entities, such as in a personal area network, where the user may employ audio, video, and / or data I / O (input / output) devices, and / or body sensors, as well as separate wired or wireless modems. An estimate of the location of UE 105 may be referred to as location, location estimate, location fixed, fixed, positioning, location estimation, or location fixed, and may be geographic, providing the location coordinates of UE 105 (e.g., latitude and longitude), which may or may not include an elevation component (e.g., height above sea level; height above ground level, floor level, or basement level, or depth below). Alternatively, the location of UE 105 may be expressed as a municipal location (e.g., a postal address or designation of a point or smaller area within a building, such as a specific room or floor). The location of UE 105 may be represented as an area or volume (geographically or municipally defined) within which UE 105 is expected to be located with a certain probability or confidence level (e.g., 67%, 95%, etc.). The location of UE 105 can be represented as a relative location, which includes, for example, distance and direction relative to a known location. This relative location can be represented as relative coordinates (e.g., X, Y (and Z) coordinates) defined relative to an origin at a known location, which can be, for example, geographically, municipally, or with reference to a point, area, or volume indicated, for example, on a map, floor plan, or building plan. In the description contained herein, the use of the term "location" can include any of these variations unless otherwise indicated. When calculating the location of the UE, local x, y, and (possibly also) z coordinates are typically solved, and then (if necessary) the local coordinates are converted to absolute coordinates (e.g., with respect to latitude, longitude, and altitude above or below mean sea level).

[0034] UE 105 can be configured to communicate with other entities using one or more of a variety of technologies. UE 105 can be configured to indirectly connect to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. D2D P2P links can use any suitable D2D radio access technology (RAT) such as LTE Direct (LTE-D), WiFi, etc. ® Direct connection (WiFi) ® -D), Bluetooth ®Support is provided. One or more UEs in a UE group utilizing D2D communication may be located within the geographic coverage area of ​​a Transmit / Receive Point (TRP) (such as one or more of gNB 110a, 110b and / or ng-eNB 114). Other UEs in such a group may be outside such geographic coverage area or may be unable to receive transmissions from the base station for other reasons. A UE group communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE can transmit to other UEs in the group. The TRP can facilitate the scheduling of resources for D2D communication. In other cases, D2D communication may be performed between UEs without involving the TRP. One or more UEs in a UE group utilizing D2D communication may be located within the geographic coverage area of ​​a TRP. Other UEs in such a group may be outside such geographic coverage area or may be unable to receive transmissions from the base station for other reasons. A UE group communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE can transmit to other UEs in the group. TRP can facilitate the scheduling of resources used for D2D communication. In other cases, D2D communication can be performed between UEs without involving TRP.

[0035] Figure 1 The base stations (BS) in NG-RAN 135 shown include NR Node Bs (referred to as gNB 110a and gNB 110b). Each pair of gNBs 110a and 110b in NG-RAN 135 can be interconnected via one or more other gNBs. Access to the 5G network is provided to UE 105 via wireless communication with one or more of the gNBs 110a and 110b. These gNBs can use 5G to provide wireless communication access to the 5GC 140 on behalf of UE 105. Figure 1 In this context, it is assumed that the serving gNB of UE 105 is gNB 110a, but another gNB (e.g., gNB 110b) may act as the serving gNB or as a secondary gNB to provide additional throughput and bandwidth to UE 105 if UE 105 moves to another location.

[0036] Figure 1The base station (BS) in NG-RAN 135 shown may include ng-eNB 114, also known as Next Generation Evolved Node B. ng-eNB 114 may be connected to one or more of gNBs 110a and 110b in NG-RAN 135 via one or more other gNBs and / or one or more other ng-eNBs. ng-eNB 114 may provide LTE radio access and / or evolved LTE (eLTE) radio access to UE 105. One or more of gNBs 110a, 110b and / or ng-eNB 114 may be configured to act as a location-only beacon, which may transmit signals to assist in determining the location of UE 105, but may not receive signals from UE 105 or other UEs.

[0037] gNB 110a, 110b, and / or ng-eNB 114 may each include one or more TRPs. For example, each sector within a cell of the BS may include a TRP, but multiple TRPs may share one or more components (e.g., a shared processor but with separate antennas). System 100 may include only macro TRPs, or system 100 may have different types of TRPs, such as macro TRPs, pico TRPs, and / or femto TRPs. Macro TRPs may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by terminals with service subscriptions. Pico TRPs may cover a relatively small geographic area (e.g., a pico cell) and may allow unrestricted access by terminals with service subscriptions. Femto or home TRPs may cover a relatively small geographic area (e.g., a femto cell) and may allow restricted access by terminals associated with that femto cell (e.g., terminals of users in a home).

[0038] Each of the gNBs 110a, 110b, and / or ng-eNB 114 may include a Radio Unit (RU), a Distributed Unit (DU), and a Central Unit (CU). For example, the gNB 110b includes RU 111, DU 112, and CU 113. RU 111, DU 112, and CU 113 define the functionality of the gNB 110b. Although the gNB 110b is shown as having a single RU, a single DU, and a single CU, a gNB may include one or more RUs, one or more DUs, and / or one or more CUs. The interface between CU 113 and DU 112 is referred to as the F1 interface. RU 111 is configured to perform digital front-end (DFE) functions (e.g., analog-to-digital conversion, filtering, power amplification, transmit / receive) and digital beamforming, and includes part of the physical (PHY) layer. RU 111 may perform DFE using massive MIMO and may be integrated with one or more antennas of the gNB 110b. DU 112 hosts the Radio Link Control (RLC), Media Access Control (MAC), and Physical Layer of gNB 110b. A DU can support one or more cells, and each cell is supported by a single DU. The operation of DU 112 is controlled by CU 113. CU 113 is configured to perform functions for delivering user data, mobility control, radio access network sharing, location, session management, etc., although some functions are only assigned to DU 112. CU 113 hosts the Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) of gNB 110b. UE 105 can communicate with CU 113 via the RRC, SDAP, and PDCP layers, with DU 112 via the RLC, MAC, and PHY layers, and with RU 111 via the PHY layer.

[0039] As pointed out, although Figure 1 The diagram depicts nodes configured to communicate according to 5G communication protocols, but nodes configured to communicate according to other communication protocols (such as, for example, LTE or IEEE 802.11x) can also be used. For instance, in an evolved packet system (EPS) providing LTE radio access to UE 105, the RAN may include an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), which may include base stations containing evolved Node Bs (eNBs). The core network for the EPS may include an evolved packet core (EPC). The EPS may include the E-UTRAN plus the EPC, where the E-UTRAN corresponds to... Figure 1 NG-RAN 135 in the figure and EPC corresponds to 5GC 140 in the figure.

[0040] gNB 110a, 110b, and ng-eNB 114 can communicate with AMF 115; for location functionality, AMF communicates with LMF 120. AMF 115 can support the mobility of UE 105 (including cell changes and handover) and can participate in supporting signaling connections with UE 105 and (possibly) data and voice bearers for UE 105. LMF 120 can communicate directly with UE 105, for example, wirelessly, or directly with gNB 110a, 110b, and / or ng-eNB 114. LMF 120 can support UE 105 positioning when UE 105 accesses NG-RAN 135, and can support various positioning procedures / methods, such as Auxiliary GNSS (A-GNSS), Observation Time Difference of Arrival (OTDOA) (e.g., Downlink (DL) OTDOA or Uplink (UL) OTDOA), Round Trip Time (RTT), Multi-Cell RTT, Real-Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (E-CID), Angle of Arrival (AoA), Angle of Departure (AoD), and / or other positioning methods. LMF 120 can process, for example, location service requests for UE 105 received from AMF 115 or GMLC 125. LMF 120 can connect to AMF 115 and / or GMLC 125. LMF 120 can be referred to by other names, such as Location Manager (LM), Location Function (LF), Commercial LMF (CLMF), or Value-Added LMF (VLMF). The node / system implementing LMF 120 may additionally or alternatively implement other types of location support modules, such as an Enhanced Serving Mobility Location Center (E-SMLC) or a Secure User Plane Location (SUPL) Location Platform (SLP). At least a portion of the location functionality (including the derivation of the location of UE 105) can be performed at UE 105 (e.g., using signal measurements obtained by UE 105 against signals transmitted by radio nodes (such as gNB 110a, 110b and / or ng-eNB 114), and / or auxiliary data provided to UE 105, for example, by LMF 120). AMF 115 can be used as a control node to process signaling between UE 105 and 5GC 140 and can provide QoS (Quality of Service) streaming and session management. AMF 115 can support the mobility of UE 105 (including cell changes and handover) and can participate in supporting signaling connections with UE 105.

[0041] Server 150 (e.g., a cloud server) is configured to obtain the location estimate of UE 105 and provide it to external client 130. Server 150 may be configured, for example, to run a microservice / service for obtaining the location estimate of UE 105. Server 150 may, for example (e.g., by sending a location request to it), pull the location estimate from one or more of UE 105, gNB 110a, 110b (e.g., via RU 111, DU 112, and CU 113) and / or ng-eNB 114 and / or LMF 120. As another example, one or more of UE 105, gNB 110a, 110b (e.g., via RU 111, DU 112, and CU 113) and / or LMF 120 may push the location estimate of UE 105 to server 150.

[0042] GMLC 125 can support location requests for UE 105 received from external client 130 via server 150, and can forward such location requests to AMF 115 for forwarding to LMF 120, or can forward the location request directly to LMF 120. A location response from LMF 120 (e.g., containing a location estimate for UE 105) can be returned to GMLC 125 directly or via AMF 115, and GMLC 125 can then return the location response (e.g., containing the location estimate) to external client 130 via server 150. GMLC 125 is shown connected to both AMF 115 and LMF 120, but in some specific implementations it may not be connected to either AMF 115 or LMF 120.

[0043] like Figure 1 As a further example, the LMF 120 can use the new radio positioning protocol A (which may be referred to as NPPa or NRPPa) to communicate with gNB 110a, 110b and / or ng-eNB 114, which can be defined in 3GPP Technical Specification (TS) 38.455. NRPPa can be the same as, similar to or an extension of the LTE Positioning Protocol A (LPPa) defined in 3GPP TS 36.455, where NRPPa messages are transmitted via AMF 115 between gNB 110a (or gNB 110b) and LMF 120, and / or between ng-eNB 114 and LMF 120. Figure 1As a further example, LMF 120 and UE 105 can communicate using the LTE Location Protocol (LPP), which is defined in 3GPP TS 36.355. LMF 120 and UE 105 can also communicate using a new radio positioning protocol (which may be referred to as NPP or NRPP), which may be the same as, similar to, or an extension of LPP. Here, LPP and / or NPP messages can be transmitted between UE 105 and LMF 120 via AMF 115 and UE 105's serving gNB 110a, 110b, or serving ng-eNB 114. For example, LPP and / or NPP messages can be transmitted between LMF 120 and AMF 115 using the 5G Location Services Application Protocol (LCS AP), and between AMF 115 and UE 105 using the 5G Non-Access Stratum (NAS) protocol. The LPP and / or NPP protocols can be used to support the location of UE 105 using UE-assisted and / or UE-based positioning methods (such as A-GNSS, RTK, OTDOA, and / or E-CID). The NRPPa protocol can be used to support the location of UE 105 using network-based positioning methods (such as E-CID) (e.g., when used in conjunction with measurements obtained by gNB 110a, 110b, or ng-eNB 114) and / or can be used by LMF 120 to obtain location-related information from gNB 110a, 110b, and / or ng-eNB 114, such as defining parameters sent by directional SS or PRS from gNB 110a, 110b, and / or ng-eNB 114. LMF 120 can be co-located or integrated with gNB or TRP, or can be configured to be located away from gNB and / or TRP and communicate directly or indirectly with gNB and / or TRP.

[0044] Using a UE-assisted positioning method, UE 105 can obtain location measurements and transmit these measurements to a location server (e.g., LMF 120) for calculating a location estimate for UE 105. For example, location measurements may include one or more of the following: Received Signal Strength Indication (RSSI), Round-Trip Time (RTT), Reference Signal Time Difference (RSTD), Reference Signal Received Power (RSRP), and / or Reference Signal Received Quality (RSRQ) for gNB 110a, 110b, ng-eNB 114, and / or WLAN AP. Location measurements may additionally or alternatively include measurements of GNSS pseudorange, code phase, and / or carrier phase for SV 190-193.

[0045] Using a UE-based positioning method, UE 105 can obtain a location measurement (e.g., which may be the same as or similar to the location measurement of a UE-assisted positioning method) and can calculate the location of UE 105 (e.g., by means of auxiliary data received from a location server (such as LMF 120) or broadcast by gNB 110a, 110b, ng-eNB 114 or other base stations or APs).

[0046] Using a network-based positioning method, one or more base stations (e.g., gNB 110a, 110b and / or ng-eNB 114) or APs can obtain location measurements (e.g., measurements of RSSI, RTT, RSRP, RSRQ, or Time of Arrival (ToA) of signals transmitted by UE 105) and / or can receive measurements obtained by UE 105. One or more base stations or APs can transmit the measurements to a location server (e.g., LMF 120) for calculating a location estimate for UE 105.

[0047] The information provided to the LMF 120 by the gNB 110a, 110b and / or ng-eNB 114 using NRPPa may include timing and configuration information for directing SS or PRS transmissions, as well as location coordinates. The LMF 120 may provide some or all of this information as supplementary data to the UE 105 in LPP and / or NPP messages via NG-RAN 135 and 5GC140.

[0048] The LPP or NPP message transmitted from LMF 120 to UE 105 can command UE 105 to perform any of a variety of tasks depending on the desired functionality. For example, the LPP or NPP message may contain instructions for UE 105 to obtain measurements of GNSS (or A-GNSS), WLAN, E-CID, and / or OTDOA (or some other positioning method). In the case of E-CID, the LPP or NPP message may command UE 105 to obtain measurements supported by one or more of gNB 110a, 110b, and / or ng-eNB 114 (or by some other type of base station such as eNB or WiFi). ® One or more measurement parameters (e.g., beam ID, beamwidth, average angle, RSRP, RSRQ measurements) of directional signals transmitted within a specific cell supported by the AP. UE 105 can transmit these measurement parameters back to LMF 120 via serving gNB110a (or serving ng-eNB 114) and AMF 115 in an LPP or NPP message (e.g., within a 5G NAS message).

[0049] As noted, while a communication system 100 is described in relation to 5G technology, the communication system 100 can be implemented to support other communication technologies (such as GSM, WCDMA, LTE, etc.) for supporting and interacting with mobile devices (such as UE 105) (e.g., to provide voice, data, location, and other functionalities). In some such specific implementations, the 5GC 140 can be configured to control different air interfaces. For example, the 5GC 140 can use non-3GPP interoperability functions (N3IWF) within the 5GC 140. Figure 1 (Not shown) Connected to a WLAN. For example, the WLAN may support IEEE 802.11 WiFi for UE 105. ® Access, and may include one or more WiFi networks. ® AP. Here, the N3IWF can connect to the WLAN and other components in the 5GC 140, such as the AMF 115. In some specific implementations, both the NG-RAN 135 and the 5GC 140 can be replaced by one or more other RANs and one or more other core networks. For example, in EPS, the NG-RAN 135 can be replaced by an E-UTRAN containing eNBs, and the 5GC 140 can be replaced by an EPC containing a Mobility Management Entity (MME) instead of the AMF 115, an E-SMLC instead of the LMF 120, and a GMLC that can be similar to the GMLC 125. In such EPS, the E-SMLC can use LPPa instead of NRPPa to transmit location information to and receive location information from eNBs in the E-UTRAN, and can use LPP to support the location of the UE 105. In these other examples, the location of UE 105 using directional PRS can be supported in a manner similar to that described herein for 5G networks. The difference lies in the fact that the functions and procedures described herein for gNB 110a, 110b, ng-eNB 114, AMF 115, and LMF 120 can, in some cases, be alternatively applied to other network elements, such as eNBs and WiFi. ® AP, MME, and E-SMLC.

[0050] As noted, in some examples, positioning functionality can be achieved at least in part using directional SS or PRS beams transmitted by base stations (such as gNB 110a, 110b and / or ng-eNB 114) at the location of the UE (e.g., whose location is to be determined). Figure 1 Within the range of UE 105. In some instances, the UE can use directional SS or PRS beams from multiple base stations (such as gNB 110a, 110b, ng-eNB 114, etc.) to calculate the UE's location.

[0051] Also refer to Figure 2UE 200 may be an example of one of UEs 105 and 106, and may include a computing platform containing processor 210, a memory 211 containing software (SW) 212, one or more sensors 213, a transceiver interface 214 for transceivers 215 (including wireless transceiver 240 and wired transceiver 250), a user interface 216, a satellite positioning system (SPS) receiver 217, a camera 218, and a positioning device (PD) 219. The processor 210, memory 211, sensors 213, transceiver interface 214, user interface 216, SPS receiver 217, camera 218, and positioning device 219 may be communicatively coupled to each other via a bus 220 (which may be configured for, for example, optical and / or electrical communication). One or more of the devices shown (e.g., camera 218, positioning device 219, and / or one or more sensors in sensor 213, etc.) may be omitted from UE 200. Processor 210 may include one or more hardware devices, such as a central processing unit (CPU), microcontroller, application-specific integrated circuit (ASIC), etc. Processor 210 may include multiple processors, including a general-purpose / application processor 230, a digital signal processor (DSP) 231, a modem processor 232, a video processor 233, and / or a sensor processor 234. One or more of processors 230 to 234 may include multiple devices (e.g., multiple processors). For example, sensor processor 234 may include processors for, for example, RF (radio frequency) sensing (where one or more transmitted (cellular) wireless signals and reflections are used to identify, map, and / or track objects) and / or ultrasound, etc. Modem processor 232 may support dual SIM / dual connectivity (or even more SIMs). For example, a SIM (subscriber identity module or subscriber identification module) may be used by an original equipment manufacturer (OEM), and another SIM may be used by the end user of UE 200 to obtain connectivity. Memory 211 may be a non-transitory storage medium that may include random access memory (RAM), flash memory, disk memory, and / or read-only memory (ROM), etc. Memory 211 may store software 212, which may be processor-readable, processor-executable software code containing instructions that can be configured to cause processor 210 to perform the various functions described herein when executed. Alternatively, software 212 may not be directly executable by processor 210, but may be configured to cause processor 210 to perform these functions, for example, when compiled and executed. The description herein may refer to processor 210 performing functions, but this includes other specific implementations, such as specific implementations of processor 210 performing software and / or firmware. The description herein may refer to the execution of functions by processor 210 as a shortened form of processor-executed functions by one or more of processors 230 to 234.The description herein may be referred to as the abbreviation for the execution function of UE 200 by one or more appropriate components of UE 200. Processor 210 may include memory with stored instructions as a supplement to and / or replacement of memory 211. The functionality of processor 210 is discussed more fully below.

[0052] Figure 2 The configuration of UE 200 shown is exemplary and not intended to limit this disclosure (including the claims), and other configurations may be used. For example, an exemplary configuration of the UE may include one or more of processors 230 to 234 in processor 210, memory 211, and wireless transceiver 240. Other exemplary configurations may include one or more of processors 230 to 234 in processor 210, memory 211, wireless transceiver, and one or more of the following devices: sensor 213, user interface 216, SPS receiver 217, camera 218, PD 219, and / or wired transceiver.

[0053] UE 200 may include a modem processor 232 capable of performing baseband processing on signals received and downconverted by transceiver 215 and / or SPS receiver 217. Modem processor 232 may also perform baseband processing on signals to be upconverted for transmission by transceiver 215. Alternatively, baseband processing may be performed by general-purpose / application processor 230 and / or DSP 231. However, other configurations may be used to perform baseband processing.

[0054] UE 200 may include sensor 213, which may include, for example, an inertial measurement unit (IMU) 270, one or more magnetometers 271, and / or one or more environmental sensors 272. IMU 270 may include, for example, one or more accelerometers 273 (e.g., collectively responding to acceleration of UE 200 in three dimensions) and / or one or more gyroscopes 274 (e.g., three-dimensional gyroscopes). Sensor 213 may include one or more magnetometers 271 (e.g., three-dimensional magnetometers) to determine (e.g., relative to magnetic north and / or true north) orientation, which can be used for any of a variety of purposes, such as supporting one or more compass applications. Environmental sensors 272 may include, for example, one or more temperature sensors, one or more barometric pressure sensors, one or more ambient light sensors, one or more camera imagers, and / or one or more microphones, etc. Sensor 213 may generate analog and / or digital signals, indications of which may be stored in memory 211 and processed by DSP 231 and / or general-purpose / application processor 230 to support one or more applications, such as applications involving positioning and / or navigation operations. Sensor 213 may include one or more of other various types of sensors, such as one or more optical sensors, one or more weight sensors and / or one or more radio frequency (RF) sensors.

[0055] Sensor 213 can be used for relative position measurement, relative position determination, motion determination, etc. Information detected by sensor 213 can be used for motion detection, relative displacement, dead reckoning, sensor-based position determination, and / or sensor-assisted position determination. Sensor 213 can be used to determine whether UE 200 is stationary or moving and / or whether certain useful information related to the mobility of UE 200 needs to be reported to LMF 120. For example, based on information obtained / measured by sensor 213, UE 200 can notify / report to LMF 120 that UE 200 has detected movement or that UE 200 has moved, and report relative displacement / distance (e.g., via dead reckoning implemented by sensor 213, or sensor-based position determination, or sensor-assisted position determination). In another example, for relative positioning information, the sensor / IMU can be used to determine the angle and / or orientation of another device relative to UE 200, etc.

[0056] IMU 270 can be configured to provide measurements of the direction and / or velocity of motion of UE 200, which can be used for relative position determination. For example, one or more accelerometers 273 and / or one or more gyroscopes 274 of IMU 270 can detect the linear acceleration and rotational velocity of UE 200, respectively. The linear acceleration and rotational velocity measurements of UE 200 can be integrated over time to determine the instantaneous direction of motion and displacement of UE 200. The instantaneous direction of motion and displacement can be integrated to track the position of UE 200. For example, a reference position of UE 200 at a given moment can be determined, for example, using SPS receiver 217 (and / or by some other means), and measurements acquired from accelerometers 273 and gyroscopes 274 after that moment can be used for dead reckoning to determine the current position of UE 200 based on the movement (direction and distance) of UE 200 relative to that reference position.

[0057] Magnetometer 271 can determine the strength of magnetic fields in different directions, which can be used to determine the orientation of UE 200. For example, this orientation can be used to provide a digital compass for UE 200. The magnetometer may include a two-dimensional magnetometer configured to detect and provide an indication of magnetic field strength in two orthogonal dimensions. Magnetometer 271 may also include a three-dimensional magnetometer configured to detect and provide an indication of magnetic field strength in three orthogonal dimensions. Magnetometer 271 may provide components for sensing magnetic fields and, for example, providing an indication of the magnetic field to processor 210.

[0058] Transceiver 215 may include a wireless transceiver 240 and a wired transceiver 250 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 240 may include a wireless transmitter 242 and a wireless receiver 244 coupled to antenna 246 for transmitting (e.g., on one or more uplink channels and / or one or more sidelink channels) and / or receiving (e.g., on one or more downlink channels and / or one or more sidelink channels) wireless signals 248 and converting signals from wireless signals 248 to wired (e.g., electrical and / or optical) signals and from wired (e.g., electrical and / or optical) signals to wireless signals 248. Wireless transmitter 242 includes suitable components (e.g., power amplifiers and digital-to-analog converters). Wireless receiver 244 includes suitable components (e.g., one or more amplifiers, one or more frequency filters, and analog-to-digital converters). Wireless transmitter 242 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wireless receiver 244 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 240 can be configured to transmit signals according to various radio access technologies (RATs) (e.g., with TRP and / or one or more other devices), such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone Systems), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), and WiFi. ® WiFi ® Direct connection (WiFi) ® -D), Bluetooth ® Zigbee ®The new radio can use millimeter wave frequencies and / or frequencies below 6 GHz. Wired transceiver 250 may include a wired transmitter 252 and a wired receiver 254 configured for wired communication, for example, a network interface used to communicate with and receive communications from NG-RAN 135. Wired transmitter 252 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wired receiver 254 may include multiple receivers that may be discrete components or combined / integrated components. Wired transceiver 250 may be configured, for example, for optical and / or electrical communication. Transceiver 215 may be communicatively coupled to transceiver interface 214, for example, via optical and / or electrical connections. Transceiver interface 214 may be at least partially integrated with transceiver 215. The wireless transmitter 242, the wireless receiver 244, and / or the antenna 246 may each include multiple transmitters, multiple receivers, and / or multiple antennas for transmitting and / or receiving appropriate signals, respectively.

[0059] User interface 216 may include one or more of a number of devices, such as speakers, microphones, display devices, vibration devices, keyboards, touchscreens, etc. User interface 216 may include more than one of these devices. User interface 216 may be configured to enable a user to interact with one or more applications hosted by UE 200. For example, user interface 216 may store indications of analog and / or digital signals in memory 211 in response to actions from the user, for processing by DSP 231 and / or general-purpose / application processor 230. Similarly, applications hosted on UE 200 may store indications of analog and / or digital signals in memory 211 to present output signals to the user. User interface 216 may include audio input / output (I / O) devices, including, for example, speakers, microphones, digital-to-analog circuitry, analog-to-digital circuitry, amplifiers, and / or gain control circuitry (including more than one of these devices). Other configurations of the audio I / O devices may be used. Alternatively or additionally, the user interface 216 may include one or more touch sensors that respond to touch and / or pressure on, for example, the keyboard and / or touchscreen of the user interface 216.

[0060] SPS receiver 217 (e.g., a GPS receiver) can receive and acquire SPS signal 260 via SPS antenna 262. SPS antenna 262 is configured to convert SPS signal 260 from a wireless signal to a wired signal (e.g., an electrical or optical signal) and can be integrated with antenna 246. SPS receiver 217 can be configured to process the acquired SPS signal 260 fully or partially to estimate the location of UE 200. For example, SPS receiver 217 can be configured to determine the location of UE 200 by performing trilateration using SPS signal 260. The acquired SPS signal can be processed fully or partially using general-purpose / application processor 230, memory 211, DSP 231, and / or one or more dedicated processors (not shown) in conjunction with SPS receiver 217 to calculate the estimated location of UE 200. Memory 211 can store indications (e.g., measurements) of SPS signal 260 and / or other signals (e.g., signals acquired from wireless transceiver 240) for use in performing positioning operations. A general-purpose / application processor 230, a DSP 231, and / or one or more dedicated processors, and / or a memory 211 may provide or support a position engine for processing measurements to estimate the position of the UE 200.

[0061] UE 200 may include a camera 218 for capturing still or moving images. Camera 218 may include, for example, an imaging sensor (e.g., a charge-coupled device or CMOS (complementary metal-oxide-semiconductor) imager), lenses, analog-to-digital circuitry, frame buffers, etc. Additional processing, conditioning, encoding, and / or compression of signals representing the captured images may be performed by a general-purpose / application processor 230 and / or a DSP 231. Alternatively or additionally, a video processor 233 may perform conditioning, encoding, compression, and / or manipulation of signals representing the captured images. The video processor 233 may decode / decompress stored image data for presentation on a display device (not shown), for example, the user interface 216.

[0062] Location device (PD) 219 may be configured to determine the location of UE 200, the movement of UE 200, and / or the relative location of UE 200, and / or time. For example, PD 219 may communicate with SPS receiver 217 and / or include part or all of the SPS receiver. PD 219 may, where appropriate, work in conjunction with processor 210 and memory 211 to perform at least a portion of one or more location methods, although the description herein may refer to PD 219 being configured to perform according to a location method or the PD performing according to a location method. PD 219 may additionally or alternatively be configured to: perform trilateration using terrestrial signals (e.g., at least some radio signals 248), assist in acquisition, and use SPS signal 260, or both, to determine the location of UE 200. PD 219 may be configured to determine the location of UE 200 based on the cell of the serving base station (e.g., cell center) and / or another technology (such as E-CID). PD 219 can be configured to determine the location of UE 200 using one or more images from camera 218 and image recognition combined with the known location of landmarks (e.g., natural landmarks such as mountains and / or man-made landmarks such as buildings, bridges, streets, etc.). PD 219 can be configured to determine the location of UE 200 using one or more other technologies (e.g., relying on the UE's self-reported location (e.g., part of the UE's positioning beacon)), and can use a combination of these technologies (e.g., SPS and terrestrial positioning signals) to determine the location of UE 200. PD 219 may include one or more sensors 213 (e.g., gyroscopes, accelerometers, magnetometers, etc.) that can sense the orientation and / or motion of UE 200 and provide an indication of such orientation and / or motion, and processor 210 (e.g., general-purpose / application processor 230 and / or DSP 231) can be configured to use this indication to determine the motion of UE 200 (e.g., velocity vector and / or acceleration vector). PD219 can be configured to provide an indication of uncertainty and / or error in the determined positioning and / or motion. The functionality of PD219 can be provided in a variety of ways and / or configurations, such as by a general-purpose / application processor 230, transceiver 215, SPS receiver 217 and / or another component of UE 200, and can be provided by hardware, software, firmware or various combinations thereof.

[0063] Also refer to Figure 3Examples of TRP 300 for gNB 110a, 110b and / or ng-eNB 114 may include a computing platform containing processor 310, memory 311 including software (SW) 312, and transceiver 315. Processor 310, memory 311 and transceiver 315 may be communicatively coupled to each other via bus 320 (which may be configured for, for example, optical communication and / or electrical communication). One or more devices in the illustrated apparatus (e.g., wireless transceivers) may be omitted from TRP 300. Processor 310 may include one or more hardware devices, such as a central processing unit (CPU), microcontroller, application-specific integrated circuit (ASIC), etc. Processor 310 may include multiple processors (e.g., including general-purpose / application processors, DSPs, modem processors, video processors and / or sensor processors, such as... Figure 2 (As shown). Memory 311 may be a non-transitory storage medium including random access memory (RAM), flash memory, disk storage, and / or read-only memory (ROM). Memory 311 may store software 312, which may be processor-readable, processor-executable software code containing instructions configured to cause processor 310 to perform the various functions described herein when executed. Alternatively, software 312 may not be directly executable by processor 310, but may be configured to cause processor 310 to perform these functions, for example, when compiled and executed.

[0064] The description herein may refer to the functions performed by processor 310, but this includes other specific implementations, such as specific implementations of processor 310 performing software and / or firmware. The description herein may refer to the functions performed by processor 310 as a shorthand for the functions performed by one or more processors included in processor 310. The description herein may refer to the functions performed by TRP 300 as a shorthand for the functions performed by one or more appropriate components of TRP 300 (and therefore one of gNB 110a, 110b and / or ng-eNB 114), such as processor 310 and memory 311. Processor 310 may include memory with stored instructions as a complement and / or replacement for memory 311. The functionality of processor 310 is discussed more fully below.

[0065] Transceiver 315 may include a wireless transceiver 340 and / or a wired transceiver 350 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 340 may include a wireless transmitter 342 and a wireless receiver 344 coupled to one or more antennas 346 for transmitting (e.g., on one or more uplink channels and / or one or more downlink channels) and / or receiving (e.g., on one or more downlink channels and / or one or more uplink channels) wireless signals 348 and converting signals from wireless signals 348 to wired (e.g., electrical and / or optical) signals and from wired (e.g., electrical and / or optical) signals to wireless signals 348. Therefore, wireless transmitter 342 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wireless receiver 344 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 340 can be configured to transmit signals according to a variety of radio access technologies (RATs) (e.g., with UE 200, one or more other UEs, and / or one or more other devices), such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone Systems), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), and WiFi. ® WiFi ® Direct connection (WiFi) ® -D), Bluetooth ® Zigbee ® The wired transceiver 350 may include a wired transmitter 352 and a wired receiver 354 configured for wired communication, for example, a network interface that can be used to communicate with NG-RAN 135 to transmit and receive communications to, for example, LMF 120 and / or one or more other network entities. The wired transmitter 352 may include multiple transmitters that may be discrete components or combined / integrated components, and / or the wired receiver 354 may include multiple receivers that may be discrete components or combined / integrated components. The wired transceiver 350 may be configured, for example, for optical communication and / or electrical communication.

[0066] Figure 3The configuration of TRP 300 shown is illustrative and not intended to limit this disclosure (including the claims), and other configurations may be used. For example, the description herein discusses that TRP 300 may be configured to perform several functions or that the TRP performs several functions, but one or more of these functions may be performed by LMF 120 and / or UE 200 (i.e., LMF 120 and / or UE 200 may be configured to perform one or more of these functions).

[0067] Also refer to Figure 4 Server 400 (LMF 120 may be an example thereof) may include: a computing platform including processor 410, a memory 411 including software (SW) 412, and a transceiver 415. Processor 410, memory 411, and transceiver 415 may be communicatively coupled to each other via bus 420 (which may be configured for, for example, optical communication and / or electrical communication). One or more devices in the illustrated apparatus (e.g., a wireless transceiver) may be omitted from server 400. Processor 410 may include one or more hardware devices, such as a central processing unit (CPU), microcontroller, application-specific integrated circuit (ASIC), etc. Processor 410 may include multiple processors (e.g., including general-purpose / application processors, DSPs, modem processors, video processors, and / or sensor processors, such as… Figure 2 (As shown). Memory 411 may be a non-transitory storage medium including random access memory (RAM), flash memory, disk storage, and / or read-only memory (ROM). Memory 411 may store software 412, which may be processor-readable, processor-executable software code containing instructions configured to cause processor 410 to perform the various functions described herein when executed. Alternatively, software 412 may not be directly executable by processor 410, but may be configured to cause processor 410 to perform these functions, for example, when compiled and executed. The description herein may refer to processor 410 performing functions, but this includes other specific implementations, such as specific implementations of processor 410 performing software and / or firmware. The description herein may refer to the execution of functions by processor 410 as an abbreviation of one or more processors included in processor 410 performing functions. The description herein may refer to the execution of functions by server 400 as an abbreviation of one or more suitable components of server 400 performing functions. Processor 410 may include memory with stored instructions as a supplement and / or replacement for memory 411. The functionality of processor 410 will be discussed more comprehensively below.

[0068] Transceiver 415 may include a wireless transceiver 440 and / or a wired transceiver 450 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 440 may include a wireless transmitter 442 and a wireless receiver 444 coupled to one or more antennas 446 for transmitting (e.g., on one or more downlink channels) and / or receiving (e.g., on one or more uplink channels) wireless signals 448, and for converting signals from wireless signals 448 to wired (e.g., electrical and / or optical) signals and from wired (e.g., electrical and / or optical) signals to wireless signals 448. Therefore, wireless transmitter 442 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wireless receiver 444 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 440 can be configured to transmit signals according to a variety of radio access technologies (RATs) (e.g., with UE 200, one or more other UEs, and / or one or more other devices), such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone Systems), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), and WiFi. ® WiFi ® Direct connection (WiFi) ® -D), Bluetooth ® Zigbee ® The wired transceiver 450 may include a wired transmitter 452 and a wired receiver 454 configured for wired communication, for example, a network interface that can be used to communicate with NG-RAN 135 to transmit and receive communications to, for example, TRP 300 and / or one or more other network entities. The wired transmitter 452 may include multiple transmitters that may be discrete components or combined / integrated components, and / or the wired receiver 454 may include multiple receivers that may be discrete components or combined / integrated components. The wired transceiver 450 may be configured, for example, for optical communication and / or electrical communication.

[0069] The description herein may refer to the processor 410 performing functions, but this includes other specific implementations, such as specific implementations of software and / or firmware (stored in memory 411) performed by the processor 410. The description herein may refer to the server 400 performing functions as an abbreviation for one or more appropriate components of the server 400 (e.g., processor 410 and memory 411) performing functions.

[0070] Figure 4The configuration of server 400 shown is exemplary and not intended to limit this disclosure (including the claims), and other configurations may be used. For example, wireless transceiver 440 may be omitted. Furthermore or alternatively, the description herein discusses server 400 being configured to perform certain functions or the server performing certain functions, but one or more of these functions may be performed by TRP 300 and / or UE 200 (i.e., TRP 300 and / or UE 200 may be configured to perform one or more of these functions).

[0071] Positioning technology

[0072] For terrestrial positioning of UEs in cellular networks, techniques such as Advanced Forward Link Trilateral Measurement (AFLT) and Observational Time Difference of Arrival (OTDOA) typically operate in a "UE-assisted" mode, where measurements of reference signals (e.g., PRS, CRS, etc.) transmitted by the base station are acquired by the UE and subsequently provided to a location server. The location server calculates the UE's location based on this measurement and the known location of the base station. Because these techniques use a location server (rather than the UE itself) to calculate the UE's location, they are not frequently used in applications such as car or cellular phone navigation, which typically rely on satellite-based positioning instead.

[0073] UEs can use Satellite Positioning System (SPS) (Global Navigation Satellite System (GNSS)) to achieve high-accuracy positioning using Precise Point Positioning (PPP) or Real-Time Kinematics (RTK) techniques. These techniques use auxiliary data, such as measurements from ground-based stations. LTE Release 15 allows data to be encrypted so that only UEs subscribed to the service can read it. This auxiliary data changes over time. Therefore, a UE with a subscribed service may not be able to easily "crack" the encryption for other UEs by passing the data to them without paying for the subscription. This transmission needs to be repeated every time the auxiliary data changes.

[0074] In UE-assisted positioning, the UE transmits measurements (e.g., TDOA, Angle of Arrival (AoA), etc.) to a positioning server (e.g., LMF / eSMLC). The positioning server has a Base Station Almanac (BSA), which contains multiple "entries" or "records," one record per cell, where each record contains the geographic cell location, but may also include other data. Identifiers of the "records" among the multiple "records" in the BSA can be referenced. The BSA and measurements from the UE can be used to calculate the UE's positioning.

[0075] In conventional UE-based positioning, the UE calculates its own location, thus avoiding transmitting measurements to the network (e.g., a location server), which improves latency and scalability. The UE uses relevant BSA (Best-Side Allocation) information from the network (e.g., the location of the gNB (more broadly, the base station)). BSA information can be encrypted. However, because BSA information changes much less frequently than, for example, PPP or RTK auxiliary data described earlier, it may be easier (compared to PPP or RTK information) to make BSA information available to UEs that have not subscribed and have not paid for decryption keys. The gNB's transmission of reference signals makes BSA information potentially accessible to crowdsourcing or driving attacks, essentially enabling the generation of BSA information based on in-the-field and / or over-the-top observations.

[0076] Positioning technologies can be characterized and / or evaluated based on one or more criteria, such as positioning accuracy and / or latency. Latency is the time elapsed between the event that triggers the determination of positioning-related data and the availability of that data at the positioning system interface (e.g., the interface of an LMF 120). The latency for the availability of positioning-related data at the time of positioning system initialization is called the First Fix (TTFF), and is greater than the latency after the TTFF. The reciprocal of the time elapsed between two consecutive availability periods of positioning-related data is called the update rate, i.e., the rate at which positioning-related data is generated after the TTFF. Latency can depend on (e.g., the UE's) processing capacity. For example, assuming an allocation of 272 PRBs (Physical Resource Blocks), the UE can report its processing capacity as the duration (in time units, e.g., milliseconds) of DL PRS symbols that it can process per T time units (e.g., Tms). Other examples of capabilities that may affect latency include the number of TRPs from which the UE can process PRS, the number of PRSs the UE can process, and the UE's bandwidth.

[0077] One or more of many different positioning techniques (also known as positioning methods) can be used to determine the location of an entity (such as one of UE105, 106). Known positioning techniques include RTT, multiple RTT, OTDOA (also known as TDOA and including UL-TDOA and DL-TDOA), Enhanced Cell Identification (E-CID), DL-AoD, UL-AoA, etc. RTT uses the time it takes for a signal to travel from one entity to another and back to determine the range between the two entities. The range, plus the known location of the first entity and the angle between the two entities (e.g., azimuth), can be used to determine the location of the second entity. In multiple RTT (also known as multi-cell RTT), multiple ranges from one entity (e.g., UE) to other entities (e.g., TRP) and the known locations of other entities can be used to determine the location of that one entity. In TDOA, the time difference of travel between an entity and other entities can be used to determine the relative range with respect to other entities, and this relative range, combined with the known locations of other entities, can be used to determine the location of that one entity. Angle of arrival and / or angle of departure can be used to help determine the location of an entity. For example, the angle of arrival or departure of a signal, combined with the range between devices (distances determined using signals (e.g., signal travel time, signal received power, etc.)) and the known location of one of these devices, can be used to determine the location of another device. The angle of arrival or departure can be an azimuth angle relative to a reference direction (such as true north). The angle of arrival or departure can also be a zenith angle relative to directly upwards from the entity (i.e., radially outwards from the Earth's center). E-CID uses the identity of the serving cell, timing advance (i.e., the difference between the reception time and transmission time at the UE), estimated timing and power of detected neighboring cell signals, and possible angles of arrival (e.g., the angle of arrival of signals from the base station at the UE, or vice versa) to determine the location of the UE. In TDOA, the time difference of arrival of signals from different sources at the receiving device, along with the known locations of these sources and the known offsets of the transmission times from these sources, are used to determine the location of the receiving device.

[0078] In network-centric RTT estimation, the serving base station instructs the UE to scan / receive RTT measurement signals (e.g., PRS) on the serving cells of two or more neighboring base stations (and typically the serving base station, as at least three base stations are required). These one or more base stations transmit the RTT measurement signals on low-reuse resources (e.g., resources used by the base station to transmit system information) allocated by the network (e.g., a location server, such as LMF 120). The UE records the arrival time (also referred to as the reception time, received time, time of receipt, or time of arrival (ToA)) of each RTT measurement signal relative to the UE's current downlink timing (e.g., as derived by the UE from DL signals received from its serving base station), and (e.g., when instructed by its serving base station) transmits a shared or individual RTT response message (e.g., an SRS (Sound Reference Signal) for positioning, i.e., UL-PRS) to these one or more base stations, and may include the time difference T_(Rx→Tx) between the ToA of the RTT measurement signal and the transmission time of the RTT response message (i.e., UE TRx-Tx or UERx-Tx) in the payload of each RTT response message. The RTT response message will include a reference signal from which the base station can infer the Time of Arrival (ToA) of the RTT response. By comparing the difference T_(Tx→Rx) between the transmission time of the RTT measurement signal from the base station and the ToA of the RTT response at the base station with the time difference T_(Rx→Tx) reported by the UE and subtracting UERx-Tx, the base station can infer the propagation time between the base station and the UE. Based on this propagation time, the base station can determine the distance between the UE and the base station by assuming the speed of light during this propagation time.

[0079] UE-centric RTT estimation is similar to network-based methods, except that the UE sends an uplink RTT measurement signal (e.g., when commanded by a serving base station), which is received by multiple base stations near the UE. Each base station involved responds with a downlink RTT response message, which may include in its payload the time difference between the ToA of the RTT measurement signal at the base station and the time of transmission of the RTT response message from the base station.

[0080] For both network-centric and UE-centric procedures, the side performing RTT calculation (network or UE) typically (but not always) sends a first message or signal (e.g., an RTT measurement signal), while the other side responds with one or more RTT response messages or signals, which may include the difference between the ToA of the first message or signal and the transmission time of the RTT response message or signal.

[0081] Multiple RTT (Multiple Real-Time Toll) technology can be used to determine location. For example, a first entity (e.g., a UE) may transmit one or more signals (e.g., unicast, multicast, or broadcast from a base station), and multiple second entities (e.g., other TSPs, such as a base station and / or the UE) may receive signals from the first entity and respond to those received signals. The first entity receives responses from the multiple second entities. The first entity (or another entity, such as an LMF) may use the responses from the second entities to determine the range to the second entities, and the location of the first entity may be determined by trilateration using the multiple ranges and the known locations of the second entities.

[0082] In some instances, additional information in the form of angle of arrival (AoA) or angle of departure (AoD) can be obtained, which defines a straight-line direction (e.g., this direction can be in a horizontal plane or in three dimensions) or a possible (e.g., the UE's direction as seen from the base station's location) range of directions. The intersection of the two directions can provide another estimate of the UE's location.

[0083] For positioning techniques that use PRS (Location Reference Signal) signals (e.g., TDOA and RTT), the PRS signals transmitted by multiple TRPs are measured, and the arrival time, known transmission time, and known location of the TRPs are used to determine the range from the UE to the TRPs. For example, RSTD (Reference Signal Time Difference) can be determined for PRS signals received from multiple TRPs, and this RSTD is used in TDOA techniques to determine the UE's location. The Location Reference Signal may be referred to as the PRS or PRS signal. PRS signals are typically transmitted using the same power, and PRS signals with the same signal characteristics (e.g., the same frequency shift) may interfere with each other, causing a PRS signal from a more distant TRP to be overwhelmed by a PRS signal from a closer TRP, making the signal from the more distant TRP undetectable. PRS silencing can be used to help reduce interference by silencing some PRS signals (reducing the power of the PRS signal, e.g., reducing it to zero and thus not transmitting the PRS signal). In this way, the UE can more easily detect the weaker PRS signal (at the UE) without the interference of the stronger PRS signal. The term RS and its variations (e.g., PRS, SRS, CSI-RS (Channel State Information - Reference Signal)) can refer to one or more reference signals.

[0084] The Positioning Reference Signal (PRS) comprises a downlink PRS (DL PRS, often simply referred to as PRS) and an uplink PRS (UL PRS) (the uplink PRS may be referred to as the SRS (Sound Reference Signal) used for positioning). The PRS may include PN codes (pseudo-random codes) or be generated using PN codes (e.g., by modulating a carrier signal with PN codes) so that the PRS source can be used as a pseudo-satellite. The PN code can be unique for the PRS source (at least unique within a specified region, such that the same PRS from different PRS sources does not overlap). The PRS may include PRS resources of a frequency layer and / or a set of PRS resources. The DL PRS positioning frequency layer (or simply frequency layer) is a collection of DL PRS resource sets from one or more TRPs, whose PRS resources have common parameters configured by the higher-level parameters DL-PRS-PositioningFrequencyLayer (DL-PRS-PositioningFrequencyLayer), DL-PRS-ResourceSet (DL-PRS-Resource Set), and DL-PRS-Resource (DL-PRS-Resource). Each frequency layer has a DL PRS subcarrier spacing (SCS) for the DL PRS resource set and DL PRS resources within that frequency layer. Each frequency layer also has a DL PRS cyclic prefix (CP) for the DL PRS resource set and DL PRS resources within that frequency layer. In 5G, a resource block occupies 12 consecutive subcarriers and a specified number of symbols. A shared resource block is a set of resource blocks that occupy the channel bandwidth. A bandwidth portion (BWP) is a set of consecutive shared resource blocks and may include all shared resource blocks within the channel bandwidth or a subset of those shared resource blocks. Furthermore, the DL PRS point A parameter defines the frequency of a reference resource block (and its lowest subcarrier), where DL PRS resources belonging to the same DL PRS resource set have the same point A, and all DL PRS resource sets belonging to the same frequency layer have the same point A. The frequency layers also have the same DL PRS bandwidth, the same starting PRB (and center frequency), and the same comb size value (i.e., the frequency of the PRS resource element per symbol, such that for comb-N, every Nth resource element is a PRS resource element). A PRS resource set is identified by a PRS resource set ID and can be associated with a specific TRP (identified by a cell ID) transmitted by the antenna panel of a base station. The PRS resource ID in a PRS resource set can be associated with an omnidirectional signal and / or with a single beam (and / or beam ID) transmitted from a single base station (where a base station can transmit one or more beams). Each PRS resource in a PRS resource set can be transmitted on a different beam, and thus, a PRS resource (or simply a resource) can also be referred to as a beam. There is no indication as to whether the base station and beam transmitting the PRS on it are known to the UE.

[0085] The TRP can be configured, for example, by instructions received from a server and / or by software within the TRP, to transmit DL PRS according to a schedule. Depending on this schedule, the TRP can transmit DL PRS intermittently (e.g., periodically at consistent intervals from the initial transmission). The TRP can be configured to transmit one or more PRS resource sets. A resource set is a collection of PRS resources spanning a TRP, wherein the resources have the same periodicity, a shared silent mode configuration (if any), and the same cross-slot repetition factor. Each PRS resource set comprises multiple PRS resources, wherein each PRS resource comprises multiple OFDM (Orthogonal Frequency Division Multiplexing) resource elements (REs), which may reside in multiple resource blocks (RBs) within N (or more) consecutive symbols in a time slot. PRS resources (or, in general, reference signal (RS) resources) may be referred to as OFDM PRS resources (or OFDMRS resources). An RB is a set of REs spanning a certain number of one or more consecutive symbols in the time domain and a certain number (12 for 5G RBs) of consecutive subcarriers in the frequency domain. Each PRS resource is configured using RE offset, slot offset, and symbol offset within a slot, as well as the number of consecutive symbols that a PRS resource can occupy within a slot. The RE offset defines the initial RE offset of the first symbol within a DL PRS resource in the frequency. The relative RE offsets of the remaining symbols within a DL PRS resource are defined based on the initial offset. The slot offset is the starting slot of the DL PRS resource relative to the corresponding resource set slot offset. The symbol offset determines the starting symbol of the DL PRS resource within the starting slot. Transmitted REs can be repeated across slots, with each transmission referred to as a repetition, allowing for multiple repetitions within a PRS resource. DL PRS resources in a DL PRS resource set are associated with the same TRP, and each DL PRS resource has a DL PRS resource ID. The DL PRS resource ID in a DL PRS resource set is associated with a single beam transmitted from a single TRP (although a TRP can transmit one or more beams).

[0086] PRS resources can also be defined by quasi-co-location parameters and starting PRB parameters. The quasi-co-location (QCL) parameter defines any quasi-co-location information of the DLPRS resource with other reference signals. The DL PRS can be configured to be of QCL type D with DL PRS or SS / PBCH (Synchronization Signal / Physical Broadcast Channel) blocks from the serving cell or non-serving cell. The DL PRS can be configured to be of QCL type C with SS / PBCH blocks from the serving cell or non-serving cell. The starting PRB parameter defines the starting PRB index of the DLPRS resource with respect to reference point A. This starting PRB index has a granularity of one PRB and can have a minimum value of 0 PRBs and a maximum value of 2176 PRBs.

[0087] A PRS resource set is a collection of PRS resources with the same periodicity, the same silent mode configuration (if any), and the same cross-slot repetition factor. Each time all repetitions of all PRS resources in a PRS resource set are configured to be transmitted is called an "instance". Therefore, an "instance" of a PRS resource set is a specified number of repetitions for each PRS resource and a specified number of PRS resources within the PRS resource set, such that the instance is complete once the specified number of repetitions has been transmitted for each of the specified number of PRS resources. An instance can also be referred to as an "opportunity". A DLPRS configuration, including DL PRS transmission scheduling, can be provided to the UE to facilitate (or even enable) the UE to measure DL PRS.

[0088] Multiple frequency layers of a PRS can be aggregated to provide an effective bandwidth greater than any bandwidth in the individual layers. Multiple frequency layers belonging to component carriers (which can be consecutive and / or separate) and satisfying criteria such as Quasi-Co-location (QCL) and having the same antenna port can be stitched together to provide a larger effective PRS bandwidth (for DL ​​PRS and UL PRS), thereby improving the accuracy of time of arrival measurements. Stitching involves combining PRS measurements on individual bandwidth segments into a unified fragment, such that the stitched PRS can be considered as taken from a single measurement. In the case of QCL, different frequency layers behave similarly, resulting in a larger effective bandwidth for PRS stitching. The larger effective bandwidth (which may be referred to as the bandwidth of the aggregated PRS or the frequency bandwidth of the aggregated PRS) provides better time-domain resolution (e.g., the resolution of TDOA). The aggregated PRS comprises a collection of PRS resources, and each PRS resource in the aggregated PRS may be referred to as a PRS component, and each PRS component may be transmitted on different component carriers, frequency bands, or frequency layers, or on different portions of the same frequency band.

[0089] RTT positioning is an active positioning technology because RTT uses positioning signals transmitted from the TRP to the UE and from the UE (participating in RTT positioning) to the TRP. The TRP can transmit DL-PRS signals received by the UE, and the UE can transmit SRS (Sound Reference Signal) signals received by multiple TRPs. The Sound Reference Signal may be referred to as SRS or SRS signal. In 5G multi-RTT, coordinated positioning can be used, where the UE transmits a single UL-SRS for positioning received by multiple TRPs, instead of transmitting a separate UL-SRS for positioning for each TRP. A participating TRP will typically search for UEs currently residing on that TRP (the served UE, where the TRP is the serving TRP) and also search for UEs residing on neighboring TRPs (neighbor UEs). A neighboring TRP can be a TRP of a single BTS (Broadband Transceiver Station) (e.g., gNB), or it can be a TRP of one BTS and a TRP of a single BTS. For RTT positioning (including multi-RTT positioning), the DL-PRS and UL-SRS positioning signals in the PRS / SRS positioning signal pair used to determine the RTT (and thus the range between the UE and TRP) may occur close to each other in time, so that the errors caused by UE movement and / or UE clock drift and / or TRP clock drift are within acceptable limits. For example, the signals in the PRS / SRS positioning signal pair may be transmitted from the TRP and the UE within approximately 10 ms of each other. In cases where the SRS for positioning is being transmitted by the UE and the PRS and the SRS for positioning are transmitted close to each other in time, it has been found that this may lead to radio frequency (RF) signal congestion (which may result in excessive noise, etc.) (especially if many UEs are concurrently attempting positioning), and / or may lead to computational congestion at the TRP where many UEs are concurrently attempting to measure.

[0090] RTT positioning can be UE-based or UE-assisted. In UE-based RTT, UE 200 determines the RTT and corresponding range to each TRP in TRP 300, and determines the location of UE 200 based on the range to TRP 300 and the known location of TRP 300. In UE-assisted RTT, UE 200 measures positioning signals and provides measurement information to TRP 300, and TRP 300 determines the RTT and range. TRP 300 provides the range to a location server (e.g., server 400), and the server determines the location of UE 200, for example, based on the range to different TRP 300s. RTT and / or range can be determined by TRP 300 receiving signals from UE 200, by TRP 300 in conjunction with one or more other devices (e.g., one or more other TRP 300s and / or server 400), or by one or more devices other than TRP 300 receiving signals from UE 200.

[0091] 5G NR supports various positioning technologies. NR-native positioning methods supported in 5G NR include DL-only positioning, UL-only positioning, and DL+UL positioning. Downlink-based positioning methods include DL-TDOA and DL-AoD. Uplink-based positioning methods include UL-TDOA and UL-AoA. Combined DL+UL positioning methods include RTT with one base station and RTT with multiple base stations (multi-RTT).

[0092] Location estimates (e.g., for a UE) may be referred to by other names, such as location estimation, location, positioning, fixed positioning, etc. Location estimates may be geodesic and include coordinates (e.g., latitude, longitude, and possible altitude), or they may be municipal and include street addresses, postal addresses, or some other textual description of the location. Location estimates may be further defined relative to another known location or (e.g., using latitude, longitude, and possible altitude) in absolute terms. Location estimates may include expected errors or uncertainties (e.g., by including areas or volumes that the location is expected to be included with a specified or default confidence level). Location information may include (e.g., one or more satellite signals, PRS, and / or one or more other signals) one or more location signal measurements, and / or one or more values ​​based on one or more location signal measurements (e.g., one or more distances (possibly including one or more pseudoranges), and / or one or more location estimates, etc.).

[0093] exist Figure 5The diagram illustrates a functional system block diagram of an example implementation of a UE 500 for security-related V2X transmission according to this disclosure. The UE 500 includes at least one transceiver 502, at least one memory 504, and at least one processor 506 that communicates signalingly with the at least one transceiver 502 and the at least one memory 504. In this example, the UE 500 may be integrated into or part of a vehicle 508, which may be an autonomous or semi-autonomous vehicle configured to travel along a road 510. The UE 500 may include at least one sensor 512 configured to detect the environment surrounding the UE 500 and the vehicle 508. In this example, the at least one sensor 512 may be, for example, a camera, radar, a light detection and ranging (Lidar) device, an acoustic sensor, or other types of sensors.

[0094] In this example, vehicle 508 is shown located at a first position 514 along road 510, and vehicle 508 is shown located among a plurality of adjacent vehicles along road 510, including, for example, a second vehicle 516 at a second position 518 (which may also be referred to as a second UE located within the second vehicle 516), a third vehicle 520 at a third position 522, and a fourth vehicle 524 at a fourth position 526.

[0095] As an example, at least one processor 506 is configured to: detect a second location 518 of a second UE (of the second vehicle 516) relative to a first location 514 of UE 500 (which may be interchangeably referred to as the first UE); generate an alert time window (ATW) from the first location 514 of UE 500 and the second location 518 of the second UE; and schedule at least one transmission from UE 500 to the second UE based on the ATW. In this example, at least one transceiver 502 communicates with at least one antenna 528, which is configured to transmit and receive one or more signals 530.

[0096] In this example, the environment along road 510 may include wireless devices configured to communicate with multiple vehicles 508, 516, 520, and 524. These example wireless devices may include, for example, a roadside unit (RSU) 532 and / or a wireless base station 534. In this example, RSU 532 may be a wireless communication device located on one side 536 of road 510, configured to provide connectivity and information to the multiple passing vehicles 508, 516, 520, and 524.

[0097] RSU 532 may include one or more sensors, including, for example, cameras, radar, LiDAR devices, acoustic sensors, or other types of sensors. RSU 532 may transmit multiple signals 538 related to, for example, sensor data acquired of the environment surrounding road 50, including multiple vehicles 508, 516, 520, and 524, safety warnings, traffic information, etc.

[0098] Wireless base station 534 can be a base station of a wireless communication network having a remote server 540 (or alternatively referred to as a network entity). Wireless base station 534 can communicate signalically with multiple vehicles 508, 516, 520, and 524, thereby providing both communication and positioning assistance data. In this example, wireless base station 534 can be an NG-RAN 135, gNB 110a, and / or TRP 300, and the remote server can be the previously described server 400.

[0099] In this example, the first UE 500, the second UE in the second vehicle 516, the third UE in the third vehicle 520, and the fourth UE in the fourth vehicle 524 can communicate with each other using V2X transmissions to perform sidelink (SL) positioning using V2X signaling and protocols. As an example, the first UE 500 and the second UE in the second vehicle 516 can communicate with each other via UE-to-UE SL communication by transmitting on one or more sidelink channels, such as the Physical Sidelink Synchronization Channel (PSSCH), Physical Sidelink Broadcast Channel (PSBCH), or Physical Sidelink Control Channel (PSCCH). Direct wireless device-to-wireless communication (without a network) can generally be referred to as SL communication, without limiting the communication to a specific protocol. Alternatively, the first UE 500, the second UE in the second vehicle 516, the third UE in the third vehicle 520, and the fourth UE in the fourth vehicle 524 may communicate with each other via V2X on a communication network of a wireless base station 534 and a remote server 540, or a combination of a wireless base station 534 and an RSU 532.

[0100] The circuits, components, modules, and / or devices of the first UE 500 and other devices, or circuits, components, modules, and / or devices associated with these devices, are described as signaling, communicatively coupled, and / or electrically coupled (or simply “coupled”) to each other, wherein signaling communication refers to any type of communication and / or connection between these circuits, components, modules, and / or devices that allows these circuits, components, modules, and / or devices to transmit and / or receive signals and / or information from another circuit, component, module, and / or device. This communication and / or connection can be along any signal path between these circuits, components, modules, and / or devices that allows signals and / or information to be transmitted from one circuit, component, module, and / or device to another, and includes wireless or wired signal paths. These signal paths can be physical, such as, for example, wires, electromagnetic waveguides, cables, attached and / or electromagnetically or mechanically coupled terminals, semiconductor or dielectric materials or devices, or other similar physical connections or couplings. Additionally, the signal path can be non-physical, such as free space (in the case of electromagnetic propagation) or an information path via digital components, where communication information can be transferred from one circuit, component, module, and / or device to another in different digital formats without the need for a direct electromagnetic connection.

[0101] This disclosure discusses techniques for systems and methods used for security-related V2X transmission by a UE 500. Generally, these techniques optimize V2X transmission to improve spectral efficiency. As examples, these techniques include the following aspects, features, or both: a discovery phase, where UE 500 (acting as the transmitting UE) needs to know where any neighboring UEs (i.e., UEs in the multiple vehicles 516, 520, and 524) are located in order to adjust the transmission schedule of UE 500, wherein discovery may be based on various types of information indicating where the multiple vehicles 516, 520, and 524 are located; a useful ATW determination phase based on the locations of the multiple vehicles 516, 520, and 524, where UE 500 can determine which receiving UEs (among neighboring UEs within vehicles 516, 520, and 524) will benefit most from messages from UE 500, and this determination may be based on various factors, including the message's relevance to its relevant / useful applications and / or collision risk (RoC), etc.; and a scheduling and transmission phase, where UE 500 then determines / adjusts its transmission schedule to maximize the probability of receiving by the receiving UEs (of vehicles 516, 520, and 524) for the maximum number of "applications" within the useful ATW, or by the UEs... The use of 500 messages.

[0102] Using these techniques, V2X transmissions of UE 500 can be customized to be received by receiving UEs of vehicles 516, 520, and 524 within a "useful ATW" time window. Therefore, receiving UEs of vehicles 516, 520, and 524 receive information from UE 500 that is not received too early or too late to be useful for their consuming applications. Generally, these techniques include: techniques for determining the useful ATW for each V2X application within the neighboring / target / receiving UEs of vehicles 516, 520, and 524; adjustments to the transmission scheduling of UE 500; and coordination for transmissions of concurrent applications.

[0103] As an example, the second vehicle 516 is located at a second location 518, which is at a first distance 542 away from the first location 514 of the UE 500. In this example, at least one processor 506 of the UE 500 may be configured to detect the second location 518 of the second UE 516 relative to the first location 514 of the UE 500, and generate an ATW based on the first location 514 of the UE 500 and the second location 518 of the second UE. The ATW is then based on the resulting first distance 542 between the UE 500 and the second UE 516. At least one processor 506 of the UE 500 is then configured to schedule at least one transmission from the UE 500 to the second UE 516 based on the ATW to achieve spectral efficiency. Once scheduled, at least one processor is also configured to send a Basic Security Message (BSM) or a Cooperation Aware Message (CAM) to the second UE at a configurable baseline frequency.

[0104] In this example, the BSM transmitted by UE 500 contains data regarding the location (i.e., first location 514), speed, direction of travel, and acceleration of vehicle 508. Similarly, the CAM transmitted by UE 500 is a security-related message containing information about the state of vehicle 508, such as, for example, the location (i.e., first location 514), direction, and / or speed of vehicle 508. UE 500 may be configured to receive a second location 518 of the second UE for the second vehicle 516 from at least one RSU (i.e., RSU 532), sense the second location 518 of the second UE using at least one sensor 512, or both.

[0105] In this example, at least one processor 506 may be configured to generate an ATW by being configured to determine the RoC between UE 500 and a second UE in the second vehicle 516. At least one processor 506 may also be configured to schedule at least one transmission by being configured to establish a transmission schedule to maximize the probability of the second UE within the second vehicle 516 receiving within the ATW. Furthermore, at least one processor 506 may also be configured to schedule at least one transmission by being configured to establish a transmission schedule to maximize the number of applications on the second UE in the second vehicle 516. Additionally, at least one processor may be configured to first detect the second location 518 of the second UE in the second vehicle 516 by being configured to track the second UE and update the second location 518 of the second UE to a third location (i.e., a fifth location 544) based on the tracking of the second UE; and then generate the ATW by being configured to determine the RoC based on the first location 514 of UE 500 and the third location of the second UE in the second vehicle 516. In this example, at least one processor may also be configured to receive kinematic data of UE 500 via at least one sensor 512, and update the first position 514 of UE 500 to a fourth position of UE 500 (i.e., a sixth position 546 of vehicle 508) based on the kinematic data generated by at least one sensor 512. In this example, at least one processor 506 is configured to generate ATW by updating RoC based on the fourth position of UE 500 (i.e., the sixth position 546) and the third position of the second UE of the second vehicle 516 (i.e., the fifth position 544).

[0106] In these examples, at least one processor 506 may be configured to schedule at least one transmission by determining whether a BSM, CAM, or both are scheduled to be transmitted, and rescheduling a new transmission from UE 500 to a second UE 516 based on RoC. In this manner, at least one processor 506 is configured to transmit a BSM, CAM, or both to the second UE if RoC is higher than a predetermined threshold during a first distance 542 between UE 500 and the second vehicle 516 within the Useful Warning (UA) period of the ATW.

[0107] Therefore, utilizing these techniques, UE 500 is configured to perform a discovery phase, useful ATW determination, and scheduling determination and transmission. As previously discussed, in the discovery phase, UE 500 detects / determines the location of neighboring UEs in order to adjust its transmission scheduling. A first example of determining the location of neighboring UEs is receiving BSM / CAM transmissions from each neighboring UE at a baseline frequency (e.g., 1 Hz). In this example, the baseline BSM transmission frequency can be configurable. Another example of determining the location of neighboring UEs for UE 500 to detect their presence is via a sensing system associated with at least one sensor 512 (i.e., camera, radar, Lidar, etc.) or by receiving broadcast locations from multiple vehicles 516, 520, and 524 from RSU 532. UE 500 can then determine the useful ATW based on the location of neighboring UEs, and UE 500 can determine which neighboring UE will benefit most from UE 500 transmitting messages indicating its location (i.e., at the first location 514 or the sixth location 546). This determination can be based on the RoC (Route of Capacity) between UE 500 and the neighboring UE (e.g., the second vehicle 516) that will benefit most from transmitting messages from UE 500. In the example where UE 500 is following the second vehicle 516, even if the RoC is not high, the determination can also be based on the location of UE 500 (i.e., at the first location 514 or the sixth location 546). UE 500 can then determine and / or adjust its transmission schedule to maximize the probability that the second UE in the second vehicle 516 is within the useful ATW and for the maximum number of "applications" of the second UE.

[0108] In this example, ATW can be divided into, for example, three time periods, including an Early Warning (EA) time, an UA time, and a Late Warning (LA) time. In this example, EA could be a warning or status report generated too early at the second vehicle 516 to affect the collision probability, since the collision probability is low and will not decrease. UA could be a warning generated at the second vehicle 516 that is useful because the probability of collision with another vehicle (i.e., vehicle 508) is high, and UA reduces the collision probability by causing vehicle 508 and / or the second vehicle 516 to modify their movement to avoid a collision. LA is a warning generated too late at the second vehicle 516 that is useless, because the warning is at the point where a collision between vehicle 508 and the second vehicle 516 cannot be avoided.

[0109] Go to Figure 6A graph 600 is shown illustrating an example of the trajectories of a first vehicle (i.e., vehicle 508) and a second vehicle 516 along a route according to this disclosure. Graph 600 is a relationship between relative positioning 602 and normalized time 604. In this example, vehicle 508 is shown traveling along a first trajectory 606, and the second vehicle 516 is shown traveling along a second trajectory 608. In this example, both vehicles 508 and 516 may travel in the same direction, with vehicle 508 potentially positioned ahead of the second vehicle 516. As an example, at a first point 610, if the first vehicle 508 brakes suddenly along the first trajectory 606 at time 604 equals 3 and the second vehicle 516 does not react, a collision between vehicle 508 and the second vehicle 516 will occur at a second point 612 at time 604 equals 6. Based on the first trajectory 606 and the second trajectory 608, time 604 can be divided into three time periods corresponding to EA time 614, UA time 616, and LA time 618. In this example, EA time 614 is useless because it is too early to affect the probability of a collision between vehicle 508 and the second vehicle 516 at the second point 612, as the collision probability is low and will not be reduced. In contrast, UA time 616 is useful because the probability of a collision between vehicle 508 and the second vehicle 516 is high at the second point 612, and there is sufficient time in UA time 616 to modify the speed and / or direction of vehicle 508, the second vehicle 516, or both to avoid a collision at the second point 612. Therefore, a warning to the second vehicle 516 within UA time 616 reduces the probability of a collision by causing vehicle 508 and / or the second vehicle 516 to modify its movement to avoid a collision. At LA time 618, a warning generated within LA time 618 is too late to avoid a collision at the second point 612, and is therefore not a useful warning because a collision between vehicle 508 and the second vehicle 516 cannot be avoided within LA time 618. Therefore, V2X messages (e.g., CAM / BSM) sent by UE 500 of vehicle 508 and received by the second UE of the second vehicle 516 are most useful within UA time 616.

[0110] In this example, currently known V2X systems send messages based on the sending UE's state and channel congestion. Therefore, these messages are sent throughout EA time 614, UA time 616, and LA time 618 because they are transmitted frequently; however, these sent messages are not targeted at the actual sending time, in order to optimize message delivery at UA time 616.

[0111] In this disclosure, the transmitting UE (e.g., UE 500) selects its transmission time to facilitate message delivery during the UA time 618 interval. As previously described, the transmitting UE determines its transmission time by tracking nearby vehicles (e.g., second vehicle 516, third vehicle 520, and fourth vehicle 524) and identifying whether any of these additional vehicles is in RoC. If a nearby vehicle is in RoC, the transmitting UE then uses standard dynamic techniques to identify the useful ATW for the selected vehicle. Identifying the useful ATW for the selected vehicle includes determining the EA time 614, UA time 616, and LA time 618 for the trajectory of the selected vehicle. The transmitting UE then transmits a safety message during UA time 616 and, possibly, LA time 618. Generally, the transmitting UE will transmit the safety message during UA time 616, but in some cases, it may also transmit the safety message during LA time 618 to attempt to minimize damage caused by an eventual collision between the transmitting UE and the selected vehicle.

[0112] In these examples, there will typically be a receiving vehicle at the highest risk, and RoC with that selected vehicle can be avoided using a UA time period for that selected vehicle. However, these techniques can be extended to cover multiple receiving vehicles in order to avoid RoC between the sending UE and more than one receiving vehicle.

[0113] In these examples, the sending UE determines the UA time 616 based on one or more applications of the receiving UE on the receiving vehicle, as well as relevant conditions and / or factors of the environment surrounding the sending UE and the receiving vehicle. Examples of these applications may include (relative to the position of the sending UE) a forward collision warning (FCW) or emergency electronic brake light (EEBL) application when the receiving vehicle is directly behind the sending UE. As another example, when the receiving vehicle is at an upcoming intersection and the sending UE is approaching the intersection (i.e., within a configurable distance to a position deemed relevant to the area), the receiving vehicle's intersection mobility assistance (IMA) application will consider information from the sending UE to be relevant and useful. As an example of relevant conditions and / or factors of the environment surrounding the sending UE, RoC may exist because the sending UE in the sending vehicle may have a trajectory that conflicts with the trajectory of the receiving vehicle.

[0114] exist Figure 7The diagram shows a graph 700 illustrating an example of a specific implementation of a useful ATW technique according to the present disclosure for determining the route of a first vehicle (i.e., vehicle 508) and a second vehicle 516. Graph 700 is the relationship between relative positioning 702 and normalized time 704. This example utilizes an EEBL application. In this example, for simplicity, vehicle 508 and the second vehicle 516 are shown as two vehicles traveling in the same lane of road 510 at the same speed, where vehicle 508 is the leading vehicle traveling along a first track 706, and the second vehicle 516 is the following vehicle traveling along a second track 708. In this example, vehicle 508 and the second vehicle 516 maintain a distance (d). FL 710.

[0115] As an example, at point 712, if the first vehicle 508 brakes suddenly along the first trajectory 706 at position 702 equal to the braking distance (d0) 714 and time 704 equal to the braking time (t0) 716, and the second vehicle 516 does not react, then a collision between vehicle 508 and the second vehicle 516 will occur. When the second vehicle 516 stops due to the EEBL application based on information received from vehicle 508 or from its onboard sensors, it should be within a distance (d0) from vehicle 508. 容差 Stop within the tolerance range specified by 718.

[0116] In this example, the UA time 720 used to avoid RoC is defined as the time interval between the first time (t1) 722 and the second time (t2) 724. In this example, t2 724 can be defined as...

[0117]

[0118] Where V F Let t1 represent the speed of vehicle 508 along the first trajectory 706, and t1 722 can be defined as...

[0119] .

[0120] As an example, if the second vehicle 516 is a semi-autonomous or driver-assisted vehicle, there may be a time delay (t) between the EEBL warning generated based on the message received from vehicle 508 within UA time 720 and the braking applied to the second vehicle 516. 延迟 ). t 延迟 It could also be the result of the transmission delay from vehicle 508 to the second vehicle 516. If t exists... 延迟 Then the values ​​of t1 722 and t2 724 can be updated as follows:

[0121]

[0122] as well as

[0123]

[0124] In this example, for ease of description, we assume a velocity V. F It is constant, but if vehicle 508, second vehicle 516, or both are accelerating, these can also be adjusted by adjusting the relationship between t1 722 and t2 724 and the corresponding time of acceleration of vehicle 508 or second vehicle 516 relative to each other.

[0125] Go to Figure 8 The diagram illustrates a flowchart of an example implementation of a specific embodiment of a security-based transmission process 800 performed by a UE 500 according to this disclosure. In this example, the UE 500 receives sensor data 802 and / or external environment data surrounding the UE 500. In this example, the sensor information is obtained from at least one sensor 512 and may include perception (i.e., image and / or video) information from a camera, radar information, Lidar information, acoustic information, etc. The external environment data may be V2X data, such as BSM / CAM data from other adjacent vehicles, vehicle-to-vehicle (V2V) data from SL or other vehicle-to-vehicle applications, telematics and communications, vehicle-to-infrastructure (V2I) communications for devices such as RSUs, and intangible visualization (I2V) data utilizing an augmented reality interface that merges the real and virtual worlds to make information data that would otherwise be invisible to the driver of a semi-autonomous vehicle visible to the driver. The UE 500 uses this information to discover and track adjacent vehicles around 804 based on sensor input and / or external environment data. The UE 500 also senses the movement of the vehicle 508 to generate vehicle kinematic data 806, which is then used by a security application to trigger 808 once the vehicle status is updated.

[0126] In this example, the safety application trigger 808 could be a trigger that determines whether a warning regarding a safety application should be issued. For example, a forward collision warning is triggered when the following vehicle is traveling too fast and may collide with the leading vehicle, and this trigger should issue a warning that should be presented to the driver of the following vehicle. UE 500 then determines 810 the RoC of the adjacent vehicle based on the corresponding location, speed / rate, and direction of travel of the adjacent vehicle. UE 500 then determines 812 the UA time window for each vehicle's RoC and determines 814 whether the next safe transmission (BSM or CAM) should be scheduled within the determined UA time. If the next safe transmission is scheduled within the determined UA time, UE 500 transmits 816 BSM or CAM in the scheduled resource block (RB). Conversely, if the next safe transmission is not scheduled within the determined UA time, UE 500 reschedules 818 a new subchannel (or one-off) (i.e., a time-frequency block for transmitting a message) falling within the UA time of the next transmission. UE 500 then sends 816 BSM or CAM in the scheduled resource block (RB) and updates the periodic sending schedule of 820 BSM or CAM messages.

[0127] exist Figure 9 The diagram illustrates a functional diagram of an example implementation of several V2X applications according to this disclosure, where multiple receiving UEs with different UA times are present. In this example, four vehicles are present, including a first vehicle 900, a second vehicle 902, a third vehicle 904, and a fourth vehicle 906. The first vehicle 900 and the second vehicle 902 are located on a first road 908, the fourth vehicle 906 is located on a second road 910, and the third vehicle 904 is located on a lane 912 or home 914 outside the first road 908. The first road 908 and the second road 910 meet at an intersection 916 near home 914. In this example, the first vehicle 900 is the leading vehicle, and the second vehicle 902 is the following vehicle; both are traveling along the first road 908 in the same direction toward the intersection 916. As an example, the first vehicle 900 includes a sending UE (e.g., UE 500), the second vehicle 902 is a following vehicle in the EEBL relevant area, the third vehicle 904 may be a vehicle leaving lane 912 to enter the first road 908 in the FCW relevant area, and the fourth vehicle 906 travels along the second road 910 toward the intersection 916 and is in the IMA relevant area.

[0128] In this example, from the perspective of the first vehicle 900, there are three (3) competing UA times. As an example, when the first vehicle 900 travels along the first road 908 toward the intersection 916, the time 918 of the first vehicle 900 is shown as having a first time 920 and a second time 922. When the second vehicle 902 travels behind the first vehicle 900 along the first road 908 toward the intersection 916, the time 924 of the second vehicle 902 is shown as having a first time 920 and a second time 922. In this example, the second vehicle 902 has a UA time 926, which is the EEBL correlation zone between the first time 920 and the second time 922, because the second vehicle 902 always follows the first vehicle 900 from the first time 920 to the second time 922. When the third vehicle 904 travels along lane 912 toward the first road 908, the time 928 of the third vehicle 904 is shown as having a first time 920 and a second time 922. The third vehicle 904 has a UA time 930, which is the FCW related zone of the first time 920 rather than the second time 922, because in this example, when the first vehicle 900 approaches lane 912 at the first time 920, the third vehicle 904 is traveling towards the first road 908. Therefore, at the first time 920, there is a RoC between the first vehicle 900 and the third vehicle 904, but in this example, at the second time 922, the first vehicle 900 has already passed lane 912, so there is no longer a RoC with the third vehicle 904. When the fourth vehicle 906 travels along the second road 910 towards the intersection 916, the time 932 of the fourth vehicle 906 is shown as having both the first time 920 and the second time 922. The fourth vehicle 906 has a UA time 934, which is the IMA related zone of the second time 922 rather than the first time 920, because in this example, at the first time 922, the fourth vehicle 906 is traveling toward the intersection 916 and has no chance of colliding with the first vehicle 900. However, once at the second time 920, the fourth vehicle 906 approaches the intersection 916 and the first vehicle 900 passes through lane 912 along the first road 908 toward the intersection 916, the probability of RoC between the first vehicle 900 and the fourth vehicle 906 increases.

[0129] Go to Figure 10The diagram illustrates a flowchart of an example implementation of a specific method 1000 performed by UE 500. In this example, method 1000 may include: detecting, via the first UE (i.e., UE 500), a second position 518 of the second UE (of the second vehicle 516) relative to a first position 514 of the first UE; generating an ATW 1004 based on the first position 514 of the first UE and the second position 518 of the second UE; and scheduling at least one transmission 1006 from the first UE to the second UE based on an alert time window.

[0130] Specifically, refer to Figure 10 At point 1002, the first UE (i.e., UE 500) detects the second UE (i.e., the second vehicle 516) relative to the first UE's first position (i.e., the first position 514) as a second position (i.e., the second position 518). The components used to perform the detection at point 1002 may include... Figure 2 transceiver 215 or Figure 5 502 transceiver Figure 2 General purpose / application processor 230 or Figure 5 At least one processor 506, Figure 2 Sensor 213 or Figure 5 Sensor 512.

[0131] Reference Figure 10 At point 1004, the first UE generates a warning time window based on its first location and the second location of the second UE. The components used to perform the generation of point 1004 may include... Figure 2 General purpose / application processor 230 or Figure 5 At least one processor 506.

[0132] Reference Figure 10 At point 1006, the first UE schedules at least one transmission from the first UE to the second UE based on a warning time window. The components used to perform the generation at point 1004 may include... Figure 2 General purpose / application processor 230 or Figure 5 At least one processor 506.

[0133] As previously mentioned Figure 5As discussed with respect to vehicle 508, method 1000 can be executed by at least one processor 506, wherein at least one processor 506 can be configured to detect 1002 the second location 518 of the second UE by receiving information including a second location 518 of the second UE from at least one RSU 532, sensing the second location 518 of the second UE by at least one sensor 512 and / or information indicating the second location 518 from the second UE. As an example, at least one sensor 512 may include a camera, a LiDAR device or radar. At least one processor 506 can also be configured to generate 1004 ATW by determining the RoC between the first UE and the second UE as previously described based on the first location of the first UE, the second location of the second UE, the first trajectory 606 of the first UE, the second trajectory 608 of the second UE, and the collision probability between the first UE and the second UE at the intersection (i.e., point 612) of the first trajectory 606 and the second trajectory 608. In addition, at least one processor 506 may be configured to schedule at least one transmission by establishing a transmission schedule to maximize the probability of the second UE receiving within the ATW and / or to maximize the number of applications on the second UE.

[0134] In this example, at least one processor 506 may also be configured to detect the second location 518 of the second UE 1002 by being configured to: track the second UE; and update the second location of the second UE to a third location of the second UE based on tracking the second UE, wherein generating 1004 ATW may include determining RoC based on the first location of the first UE and the third location of the second UE.

[0135] Specific implementation examples

[0136] Specific implementation examples are provided in the following numbered clauses.

[0137] Clause 1. A method for vehicle-to-everything (V2X) transmission performed by a first user equipment (UE) at a first location, the method comprising: using the first UE to detect a second location of a second UE relative to the first location of the first UE; generating an alert time window based on the first location of the first UE and the second location of the second UE; and scheduling at least one transmission from the first UE to the second UE based on the alert time window.

[0138] Clause 2. The method described in Clause 1 further includes sending a Basic Security Message (BSM) or a Cooperation Aware Message (CAM) to the second UE.

[0139] Clause 3. The method according to Clause 1, wherein detecting the second location of the second UE includes receiving information selected from the group consisting of: the second location of the second UE from at least one roadside unit (RSU), sensing the second location of the second UE by at least one sensor, and information from the second UE indicating the second location.

[0140] Clause 4. The method according to Clause 3, wherein the at least one sensor includes a camera, a light detection and ranging (Lidar) device, or radar.

[0141] Clause 5. The method according to Clause 1, wherein generating the warning time window includes determining the collision risk (RoC) between the first UE and the second UE based on the first location of the first UE, the second location of the second UE, the first trajectory of the first UE, the second trajectory of the second UE, and the collision probability between the first UE and the second UE at the intersection of the first trajectory and the second trajectory.

[0142] Clause 6. The method according to Clause 1, wherein scheduling the at least one transmission includes establishing a transmission schedule to maximize the probability that the second UE will receive within the warning time window.

[0143] Clause 7. The method according to Clause 1, wherein scheduling the at least one transmission includes establishing a transmission schedule to maximize the number of applications on the second UE.

[0144] Clause 8. The method according to Clause 1, wherein detecting the second location of the second UE comprises: tracking the second UE; and updating the second location of the second UE to a third location of the second UE based on tracking the second UE, wherein generating the warning time window comprises determining a collision risk (RoC) based on the first location of the first UE and the third location of the second UE.

[0145] Clause 9. The method according to Clause 8, the method further comprising: receiving kinematic data of the first UE; and updating the first location of the first UE to a fourth location of the first UE based on the kinematic data, wherein generating the warning time window further comprises: updating the RoC based on the fourth location of the first UE and the third location of the second UE.

[0146] Clause 10. The method according to Clause 9, wherein scheduling the at least one transmission includes rescheduling a new transmission from the first UE to the second UE based on the updated RoC.

[0147] Clause 11. A user equipment (UE) for vehicle-to-everything (V2X) transmission, wherein the UE is at a first location, the UE comprising: at least one transceiver; at least one memory; and at least one processor coupled to the at least one transceiver and the at least one memory, the at least one processor being configured to: detect a second location of a second UE relative to the first location of the UE; generate an alert time window based on the first location of the UE and the second location of the second UE; and schedule at least one transmission from the UE to the second UE based on the alert time window.

[0148] Clause 12. The UE as described in Clause 11, wherein the at least one processor is further configured to send a Basic Security Message (BSM) or a Cooperation Aware Message (CAM) to the second UE.

[0149] Clause 13. The UE according to Clause 11, wherein the at least one processor is configured to detect the second location of the second UE by being configured to receive information selected from the group consisting of: the second location of the second UE from at least one roadside unit (RSU), the second location of the second UE sensed by at least one sensor, and information from the second UE indicating the second location.

[0150] Clause 14. The UE as described in Clause 13, wherein the at least one sensor includes a camera, a light detection and ranging (Lidar) device, or radar.

[0151] Clause 15. The UE according to Clause 11, wherein the at least one processor is configured to generate the warning time window by being configured to determine the collision risk (RoC) between the UE and the second UE based on the first location of the first UE, the second location of the second UE, the first trajectory of the first UE, the second trajectory of the second UE, and the collision probability between the first UE and the second UE at the intersection of the first trajectory and the second trajectory.

[0152] Clause 16. The UE according to Clause 11, wherein the at least one processor is configured to schedule the at least one transmission by being configured to establish a transmission schedule to maximize the probability that the second UE will receive within the warning time window.

[0153] Clause 17. The UE according to Clause 11, wherein the at least one processor is configured to schedule the at least one transmission by being configured to establish a transmission schedule to maximize the number of applications on the second UE.

[0154] Clause 18. The UE according to Clause 11, wherein the at least one processor is configured to detect a second location of the second UE by being configured to: track the second UE; update the second location of the second UE to a third location of the second UE based on tracking the second UE; and generate the warning time window by being configured to determine a collision risk (RoC) based on the first location of the UE and the third location of the second UE.

[0155] Clause 19. The UE according to Clause 18, wherein the at least one processor is further configured to: receive kinematic data of the UE; and update the first location of the UE to a fourth location of the UE based on the kinematic data, wherein the at least one processor is configured to generate the warning time window by also being configured to update the RoC based on the fourth location of the UE and the third location of the second UE.

[0156] Clause 20. The UE as described in Clause 19, wherein the at least one processor is further configured to reschedule new transmissions from the first UE to the second UE based on the updated RoC.

[0157] Clause 21. A user equipment (UE) for vehicle-to-everything (V2X) transmission, wherein the UE is at a first location, the UE comprising: means for detecting a second location of a second UE relative to the first location of the UE; means for generating a warning time window based on the first location of the UE and the second location of the second UE; and means for scheduling at least one transmission from the UE to the second UE based on the warning time window.

[0158] Clause 22. The UE as described in Clause 21 further includes components for sending a Basic Security Message (BSM) or a Cooperation Aware Message (CAM) to the second UE.

[0159] Clause 23. The UE as described in Clause 21, wherein the components for detecting the second location of the second UE include components for receiving information selected from the group consisting of: the second location of the second UE from at least one roadside unit (RSU), the second location of the second UE sensed by at least one sensor, and information from the second UE indicating the second location.

[0160] Clause 24. The UE as described in Clause 23, wherein the at least one sensor includes a camera, a light detection and ranging (Lidar) device, or radar.

[0161] Clause 25. The UE as described in Clause 21, wherein the components for generating the warning time window include components for determining the collision risk (RoC) between the first UE and the second UE based on the first location of the first UE, the second location of the second UE, the first trajectory of the first UE, the second trajectory of the second UE, and the collision probability between the first UE and the second UE at the intersection of the first trajectory and the second trajectory.

[0162] Clause 26. The UE according to Clause 21, wherein the component for scheduling the at least one transmission includes a component for establishing a transmission schedule to maximize the probability that the second UE will receive within the warning time window.

[0163] Clause 27. The UE as described in Clause 21, wherein the component for scheduling the at least one transmission includes a component for establishing a transmission schedule to maximize the number of applications on the second UE.

[0164] Clause 28. The UE as described in Clause 21, wherein the components for detecting the second location of the second UE include: components for tracking the second UE; and components for updating the second location of the second UE to a third location of the second UE based on tracking the second UE, wherein the components for generating the warning time window include components for determining a collision risk (RoC) based on the first location of the first UE and the third location of the second UE.

[0165] Clause 29. The UE according to Clause 28, the UE further comprising: means for receiving kinematic data of the first UE; and means for updating the first position of the first UE to a fourth position of the first UE based on the kinematic data, wherein the means for generating the warning time window further comprises: means for updating the RoC based on the fourth position of the first UE and the third position of the second UE.

[0166] Clause 30. The UE as described in Clause 29, wherein the components for scheduling the at least one transmission include components for determining whether a Basic Security Message (BSM), a Cooperation Aware Message (CAM), or both are scheduled to be transmitted, and further include components for rescheduling new transmissions from the first UE to the second UE based on the RoC.

[0167] Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software and computers, the functions described above can be implemented using software, hardware, firmware, hardwiring, or any combination thereof executed by a processor. Features implementing the functions can also be physically located in various locations, including portions distributed such that the functions are implemented in different physical locations.

[0168] As used herein, the singular forms “a,” “an,” and “the” also include the plural forms, unless the context clearly indicates otherwise. Thus, references to a device in the singular form included in the claims (e.g., “device,” “the device”) include at least one of such devices (i.e., one or more) (e.g., “processor” includes at least one processor (e.g., one processor, two processors, etc.), “the processor” includes at least one processor, “memory” includes at least one memory, “the memory” includes at least one memory, etc.). The phrases “at least one” and “one or more” are used interchangeably, and such that the object referred to by “at least one” and the object referred to by “one or more” include embodiments having one referred object and embodiments having multiple referred objects. For example, “at least one processor” and “one or more processors” each include embodiments having one processor and embodiments having multiple processors.

[0169] As used herein, the term "comprising" indicates the presence of the described features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0170] Furthermore, as used herein, the "or" (possibly followed by "at least one of" or "one or more of") used in the item enumeration indicates a disjunctive enumeration such that an enumeration of, for example, "at least one of A, B, or C," or an enumeration of "one or more of A, B, or C," or an enumeration of "A or B or C" represents A or B or C or AB (A and B) or AC (A and C) or BC (B and C) or ABC (i.e., A and B and C), or a combination having more than one feature (e.g., AA, AAB, ABBC, etc.). Therefore, a statement that an item (e.g., a processor) is configured to perform a function relating to at least one of A or B, or a statement that an item is configured to perform function A or function B, indicates that the item can be configured to perform a function relating to A, or can be configured to perform a function relating to B, or can be configured to perform a function relating to both A and B. For example, the phrase "a processor configured to measure at least one of A or B" or "a processor configured to measure A or measure B" means that the processor can be configured to measure A (and may or may not be configured to measure B), or can be configured to measure B (and may or may not be configured to measure A), or can be configured to measure both A and B (and can be configured to select which of A and B or measure both). Similarly, a description of a component for measuring at least one of A or B includes: a component for measuring A (which may or may not be able to measure B), or a component for measuring B (which may or may not be configured to measure A), or a component for measuring A and B (which may be able to select which of A and B or measure both). As another example, a description of an item (e.g., a processor) being configured to perform at least one of function X or function Y means that the item can be configured to perform function X, or can be configured to perform function Y, or can be configured to perform both functions X and Y. For example, the phrase "processor configured to measure at least one of X or Y" means that the processor can be configured to measure X (and may or may not be configured to measure Y), or can be configured to measure Y (and may or may not be configured to measure X), or can be configured to measure both X and Y (and can be configured to select which of X and Y or measure both).

[0171] As used herein, unless otherwise stated, a description of a function or operation as “based on” an item or condition means that the function or operation is based on the described item or condition and may be based on one or more items and / or conditions in addition to the described item or condition.

[0172] Substantial changes can be made depending on specific requirements. For example, custom hardware may be used, and / or specific elements may be implemented in the hardware, in software executed by the processor (including portable software such as applets), or both. Furthermore, connections to other computing devices, such as network input / output devices, may be employed. Unless otherwise specified, components shown in the figures and / or discussed herein that are connected or communicate with each other (functionally or otherwise) are communicatively coupled. That is, these components may be connected directly or indirectly to enable communication between them.

[0173] The systems and devices discussed above are examples. Various configurations may appropriately omit, substitute, or add various processes or components. For example, features described with respect to certain configurations may be combined in various other configurations. Different aspects and elements of configurations may be combined in a similar manner. Furthermore, technology is constantly evolving, and therefore many elements are examples and do not limit the scope of this disclosure or the claims.

[0174] A wireless communication system is a system in which communication is wirelessly transmitted between wireless communication devices, that is, through the propagation of electromagnetic waves and / or sound waves through the atmosphere rather than through wires or other physical connections. A wireless communication system (also called a wireless communication system or wireless communication network) may not transmit all communication wirelessly, but is configured to transmit at least some communication wirelessly. Furthermore, the term "wireless communication device" or similar terms do not require the device to be functionally exclusive or even primarily used for communication, do not require that communication using the wireless communication device be exclusive or even primarily wireless, and do not require that the device be a mobile device, but rather indicate that the device includes wireless communication capabilities (one-way or two-way), for example, including at least one radio component (each radio component being part of a transmitter, receiver, or transceiver) for wireless communication.

[0175] Specific details are provided in this description to offer a thorough understanding of the example configurations, including specific implementations. However, the configurations can be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques have been shown without unnecessary detail to avoid obscuring these configurations. The description herein provides example configurations and does not limit the scope, applicability, or configuration of the claims. Rather, the preceding description of the configurations provides a description for implementing the described techniques. Various changes can be made to the function and arrangement of the elements.

[0176] As used herein, the terms “processor-readable medium,” “machine-readable medium,” and “computer-readable medium” refer to any medium that participates in providing data that enables a machine to operate in a particular manner. Using a computing platform, various processor-readable media may involve providing instructions / code to a processor for execution, and / or may be used to store and / or carry such instructions / code (e.g., as signals). In many specific implementations, processor-readable media are physical and / or tangible storage media. Such media can take many forms, including but not limited to non-volatile and volatile media. Non-volatile media include, for example, optical discs and / or magnetic disks. Volatile media include, but are not limited to, dynamic memory.

[0177] Having described several example configurations, various modifications, alternative constructions, and equivalents can be used. For example, the above elements can be components of a larger system, where other rules may take precedence over or otherwise modify the application of this disclosure. Furthermore, several operations may be performed before, during, or after considering the above elements. Accordingly, the above description does not limit the scope of the claims.

[0178] Unless otherwise indicated, the terms "about" and / or "approximately" as used herein when referring to measurable values ​​(such as quantities, durations of time, etc.) cover variations of ±20%, ±10%, ±5%, or ±0.1% from the specified value, as appropriate in the context of the systems, devices, circuits, methods, and other specific embodiments described herein. Similarly, unless otherwise indicated, the term "substantially" as used herein when referring to measurable values ​​(such as quantities, durations of time, physical properties (such as frequencies), etc.) also covers variations of ±20%, ±10%, ±5%, or ±0.1% from the specified value, as appropriate in the context of the systems, devices, circuits, methods, and other specific embodiments described herein.

[0179] A statement that a value exceeds (or is greater than or higher than) a first threshold is equivalent to a statement that a value meets or exceeds a second threshold slightly greater than the first threshold. For example, in the resolution of the computing system, the second threshold is one value higher than the first threshold. A statement that a value is less than the first threshold (or within or below the first threshold) is equivalent to a statement that a value is less than or equal to a second threshold slightly lower than the first threshold. For example, in the resolution of the computing system, the second threshold is one value lower than the first threshold.

Claims

1. A method for transmitting data in a vehicle-to-everything (V2X) network by a first user equipment (UE), the method comprising: The second UE is detected relative to the first UE's first location using the first UE; A warning time window is generated based on the first location of the first UE and the second location of the second UE. as well as At least one transmission from the first UE to the second UE is scheduled based on the warning time window.

2. The method of claim 1, further comprising sending a Basic Security Message (BSM) or a Cooperation Aware Message (CAM) to the second UE according to at least one scheduled transmission.

3. The method of claim 1, wherein detecting the second location of the second UE comprises at least one of: (a) receiving information about the second location of the second UE from at least one roadside unit (RSU), (b) sensing the second location of the second UE by at least one sensor, (c) receiving information indicating the second location from the second UE, or (d) any combination thereof.

4. The method of claim 3, wherein the at least one sensor comprises a camera, a light detection and ranging (Lidar) device, or radar.

5. The method of claim 1, wherein generating the warning time window comprises determining the collision risk (RoC) between the first UE and the second UE based on the first location of the first UE, the second location of the second UE, the first trajectory of the first UE, the second trajectory of the second UE, and the collision probability between the first UE and the second UE at the intersection of the first trajectory and the second trajectory.

6. The method of claim 1, wherein scheduling the at least one transmission includes establishing a transmission schedule to maximize the probability that the second UE will receive within the warning time window.

7. The method of claim 1, wherein scheduling the at least one transmission includes establishing a transmission schedule to maximize the number of applications on the second UE.

8. The method of claim 1, wherein detecting the second location of the second UE comprises: Track the second UE; as well as The second location of the second UE is updated to the third location of the second UE based on tracking the second UE. The generation of the warning time window includes determining the collision risk (RoC) based on the first location of the first UE and the third location of the second UE.

9. The method according to claim 8, further comprising: Receive the kinematic data of the first UE; as well as The first location of the first UE is updated to the fourth location of the first UE based on the kinematic data. The generation of the warning time window also includes: The RoC is updated based on the fourth location of the first UE and the third location of the second UE.

10. The method of claim 9, further comprising rescheduling new transmissions from the first UE to the second UE based on the updated RoC.

11. A user equipment (UE) for vehicle-to-everything (V2X) transmission, wherein the UE comprises: At least one transceiver; At least one memory; as well as At least one processor, coupled to the at least one transceiver and the at least one memory, wherein the at least one processor is configured to: Detect the second position of the second UE relative to the first position of the UE; A warning time window is generated based on the first location of the UE and the second location of the second UE; as well as At least one transmission from the UE to the second UE is scheduled based on the warning time window.

12. The UE of claim 11, wherein the at least one processor is configured to send a Basic Security Message (BSM), a Cooperation Aware Message (CAM), or both to the second UE according to at least one scheduled transmission.

13. The UE of claim 12, wherein the at least one processor is further configured to detect the second location of the second UE by being configured to perform at least one of the following operations: (a) receiving information about the second location of the second UE from at least one roadside unit (RSU), (b) sensing the second location of the second UE by at least one sensor, (c) receiving information indicating the second location from the second UE, or (d) any combination thereof.

14. The UE of claim 11, wherein the at least one processor is configured to generate the warning time window by being configured to determine the collision risk (RoC) between the UE and the second UE based on the first location of the first UE, the second location of the second UE, the first trajectory of the first UE, the second trajectory of the second UE, and the collision probability between the first UE and the second UE at the intersection of the first trajectory and the second trajectory.

15. The UE of claim 11, wherein the at least one processor is configured to schedule the at least one transmission by being configured to establish a transmission schedule to maximize the probability that the second UE will receive within the warning time window.

16. The UE of claim 11, wherein the at least one processor is configured to schedule the at least one transmission by being configured to establish a transmission schedule to maximize the number of applications on the second UE.

17. The UE of claim 11, wherein the at least one processor is configured to The second location of the second UE is detected by being configured to perform the following operations: Track the second UE; as well as The second location of the second UE is updated to the third location of the second UE based on tracking the second UE; as well as The warning time window is generated by being configured to determine the collision risk (RoC) based on the first location of the UE and the third location of the second UE.

18. The UE of claim 17, wherein the at least one processor is further configured to: Receive the kinematic data of the UE; and The first location of the UE is updated to the fourth location of the UE based on the kinematic data. The at least one processor is configured to generate the warning time window by also being configured to perform the following operations. The RoC is updated based on the fourth location of the UE and the third location of the second UE.

19. The UE of claim 18, wherein the at least one processor is configured to reschedule new transmissions from the first UE to the second UE based on the updated RoC.

20. A user equipment (UE) for vehicle-to-everything (V2X) transmission, wherein the UE comprises: A component for detecting the second position of the second UE relative to the first position of the UE; A component for generating a warning time window based on the first location of the UE and the second location of the second UE; as well as A component for scheduling at least one transmission from the UE to the second UE based on the warning time window.

Images