Priority indication in piloting coordination messages

The V2X communication system facilitates coordinated vehicle maneuvers by exchanging maneuver intentions and priorities, reducing collisions and enhancing traffic efficiency.

JP7579876B2Active Publication Date: 2024-11-08QUALCOMM INC
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2022554552
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2020-04-09
Publication Date
2024-11-08
Estimated Expiration
2040-04-09

AI Technical Summary

Technical Problem

Existing vehicle-to-everything (V2X) communication systems lack efficient methods for coordinating vehicle maneuvers, particularly in complex traffic scenarios, leading to potential collisions and inefficiencies due to uncoordinated lane changes and intersection crossings.

Method used

Implementing a V2X communication system that enables vehicles to exchange maneuver intentions, priority levels, and time windows through standardized messages, allowing receiving entities to grant or deny requests based on priority and traffic conditions, thereby optimizing maneuver coordination.

Benefits of technology

Enhances safety and efficiency in vehicle maneuvering by reducing collisions and improving traffic flow through coordinated vehicle actions based on priority and environmental factors.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007579876000002
    Figure 0007579876000002
  • Figure 0007579876000003
    Figure 0007579876000003
  • Figure 0007579876000004
    Figure 0007579876000004
Patent Text Reader

Abstract

For maneuver coordination among autonomous and / or semi-autonomous vehicles, a first vehicle can determine a maneuver and submit a maneuver request to a receiving device (e.g., a second device, a roadside unit, or other device). The maneuver request can include a priority designation based on the vehicle type of the first vehicle, the requested maneuver type, and / or other factors. The receiving device can then determine whether to grant the maneuver request based at least in part on the priority included in the maneuver request.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] Regarding vehicle maneuver coordination. [Background technology]

[0002]

[0001] Vehicle-to-everything (V2X) is a communication standard for vehicles and related entities to exchange information about the traffic environment. V2X can include vehicle-to-vehicle (V2V) communication between V2X-enabled vehicles, vehicle-to-infrastructure (V2I) communication between vehicles and infrastructure-based devices (commonly referred to as road side units (RSUs)), and vehicle-to-person (V2P) communication between vehicles and nearby people (pedestrians, cyclists, and other road users). In addition, V2X can use any of a variety of wireless radio frequency (RF) communication technologies. For example, cellular V2X (CV2X) is a form of V2X that uses cellular-based communication, such as Long Term Evolution (LTE), Fifth Generation New Radio (5G NR), and / or other cellular technologies in a direct communication mode defined by the Third Generation Partnership Project (3GPP). Components or devices on a vehicle, RSU, or other V2X entity used to communicate V2X messages are collectively referred to as V2X devices or V2X user equipment (UE).

[0003]

[0002] Autonomous and semi-autonomous vehicles, including vehicles with Advanced Driver-Assistance Systems (ADAS), can use V2X to communicate and coordinate maneuvers. To help V2X-enabled vehicles ("V2X vehicles") safely navigate on roads, V2X vehicles can communicate intended maneuvers to other V2X vehicles. This can include maneuvers such as lane changes and intersection crossings, and corresponding time windows for behavior trajectories. [Brief description of the drawings]

[0004] [Figure 1]

[0003] FIG. 1 is an illustration of an overhead view of a traffic scenario on a road. [Diagram 2]

[0004] A call flow diagram illustrating the communication and basic functions between entities when communicating an intended maneuver in accordance with one embodiment. [Diagram 3]

[0005] 1 is an illustration of an overhead view of another traffic scenario on a road; [Figure 4]

[0006] FIG. 2 is a block diagram of an embodiment of a V2X device, according to one embodiment. [Diagram 5]

[0007] FIG. 1 is a flow diagram of a method for vehicle maneuver coordination according to one embodiment. [Figure 6]

[0008] FIG. 4 is a flow diagram of another method for vehicle steering coordination, according to one embodiment. [Figure 7]

[0009] 1 is an illustration of a system in which a vehicle may communicate with various devices, vehicles, and servers over various networks, according to one embodiment. [Figure 8]

[0010] FIG. 2 is a functional block diagram of a vehicle, according to one embodiment. [Figure 9]

[0011] FIG. 1 is a perspective view of an exemplary vehicle according to one embodiment. Detailed Description

[0005]

[0012] Like reference symbols in various figures indicate like elements according to certain exemplary implementations. In addition, multiple instances of an element can be indicated by a first number for that element followed by a letter or a hyphen and a second number. For example, multiple instances of element 110 can be indicated as 110-1, 110-2, 110-3, etc., or 110a, 110b, 110c, etc. When referring to such an element using only the first number, any instance of the element should be understood (e.g., element 110 in the previous example would refer to elements 110-1, 110-2, and 110-3, or elements 110a, 110b, and 110c).

[0006]

[0013] Certain example embodiments will now be described in connection with the accompanying drawings, which form a part hereof. Specific embodiments in which one or more aspects of the present disclosure may be practiced are described below, but other embodiments may be utilized and various changes may be made without departing from the spirit of the scope of the disclosure or the appended claims.

[0007]

[0014] As used herein, "V2X device," "V2X vehicle," and "V2X entity" refer to devices, vehicles, and entities capable of sending and receiving V2X messages, respectively. Similarly, "non-V2X vehicle" and "non-V2X entity" refer to vehicles and entities that do not or cannot engage in V2X communications. Additionally, "V2X device," as detailed herein, refers to devices, systems, or components, etc. that may be incorporated into and / or used by a V2X entity to enable V2X communications. While many embodiments refer to "V2X vehicles" and "non-V2X vehicles," it will be appreciated that many embodiments may be extended to include non-vehicle entities, such as, for example, pedestrians, bicyclists, road hazards, obstacles, and / or other traffic-related objects. Additionally, it should be noted that the embodiments may apply to vehicles and / or RSUs capable of traffic-related communications, but not necessarily V2X-enabled vehicles / RSUs. Additionally, while the embodiments provided herein may be performed by autonomous and / or semi-autonomous vehicles, the embodiments are not so limited. Embodiments may include, for example, conventional (non-autonomous) vehicles that have the capability to determine and communicate an intended maneuver (e.g., within an on-board navigation computer that can communicate instructions to a human driver). Those skilled in the art will appreciate such variations.

[0008]

[0015] FIG. 1 is an illustration of an overhead view of a road 100, according to one embodiment, provided to help illustrate that V2X vehicles can communicate intended maneuvers. Here, several vehicles, including vehicles 110-1, 110-2, 110-3, and 110-4 (collectively and generically referred to herein as vehicles 110), are traveling along the road 100, and an RSU 120 is located near the road 100 (not all vehicles 110 are labeled to avoid confusion). It will be understood that FIG. 1, as well as other diagrams provided herein, is provided as a non-limiting example. Those skilled in the art will appreciate that, as with other aspects of FIG. 1, various characteristics of the road (number of lanes, shape, direction, intersections, etc.) may change. Of course, the number, location, relative speed, and other characteristics of the vehicles along the road 100 will change as traffic conditions change.

[0009]

[0016] As previously mentioned, vehicles 110 can communicate intended maneuvers to one another to aid in maneuvering safely on roadways. More specifically, vehicles 110 can communicate intended maneuvers by sending messages to one or more other vehicles 110 that may be affected by the maneuver (e.g., by accelerating or decelerating the other vehicle 110, or by coming within a certain distance of the other vehicle 110). These messages include information about the trajectory of the maneuver (which may include, e.g., lane changes, intersection crossings, etc.) and a corresponding time window for the behavior or trajectory. The other vehicles can respond by accepting or rejecting these requests.

[0010]

[0017] FIG. 2 is a call flow diagram illustrating communication and basic functions between entities when communicating an intended maneuver, according to one embodiment. Here, the vehicle 110 that communicates the intended maneuver is referred to as a "requesting vehicle." In addition, the entity that receives the request and responds thereto is referred to as a "receiving V2X entity." This is because, according to some embodiments, the receiving V2X entity may not necessarily be limited to the receiving vehicle 110. For example, referring to FIG. 2, the RSU 120 may coordinate vehicle movement for a specified portion of the road 100 (e.g., a given length of the road 100, intersections, etc.). So, in such a case, the RSU 120 may receive requests from various vehicles 110 that are within the specified portion of the road 100. However, the receiving V2X entity may often comprise a vehicle that may be affected by the intended maneuver of the requesting vehicle.

[0011]

[0018] Returning again to FIG. 2, maneuver coordination begins with a requesting vehicle sending a maneuver coordination request 210 to a receiving V2X entity. In V2X, this maneuver coordination request 210 may comprise a “Msg_Intention” message, which, as previously described, may include the planned trajectory or desired behavior of the requesting vehicle and the time window during which the host vehicle intends to execute the maneuver. The planned trajectory and time window may be determined based on the current calculated characteristics of the vehicles, such as location, speed, etc.

[0012]

[0019] As described in more detail below, vehicles 110 in a V2X system, such as a requesting vehicle, may determine their respective locations based on one or more of a variety of location determination techniques. This may include, for example, Global Navigation Satellite System (GNSS) location determination, trilateration or triangulation using ground transceivers (e.g., techniques utilizing wide area network (WAN)-based observed time difference of arrival, round trip time (RTT) determination, received signal strength indication (RSSI), angle of arrival (AoA) and / or angle of departure (AoD), and the like), image-based location determination (e.g., comparing imagery to high-resolution map data), sensor-based location determination (e.g., using accelerometers, gyroscopes, magnetometers, etc.), or the like. Vehicle 110 may utilize data fusion to integrate multiple location determination techniques to determine its final location, which may be broadcast or otherwise mitigated using beacons or similar wireless techniques.

[0013]

[0020] In addition, the requesting vehicle may identify which nearby vehicles 110 may be affected by the intended maneuver based on the current calculated characteristics of the nearby vehicles 110 (and thus identify one or more vehicles to send the maneuver cooperation request 210 to, according to some embodiments). These characteristics may be determined by communications from these nearby vehicles 110, sensor measurements, information about the vehicles provided by the RSU 120 and / or other devices, and the like. For example, in accordance with V2X communications, the nearby vehicles 110 may broadcast a Basic Safety Message (BSM) or a Cooperative Awareness Message (CAM). Additionally or alternatively, the requesting vehicle may use measurements (e.g., RTT measurements, sonar, radar, camera images, and the like) to determine the absolute or relative location of the nearby vehicles 110.

[0014]

[0021] According to an embodiment, the steering coordination request 210 may further include a priority level to help the receiving V2X entity decide whether to grant the request (as shown in block 220 of FIG. 2).

[0015]

[0022] Maneuvering coordination request 210 (another messaging described herein) may be transmitted and received via a variety of means, protocols, and standards, and may include message elements standardized by V2X-related groups such as the Society of Automotive Engineers (SAE) or the European Telecommunications Standards Institute (ETSI). Thus, message elements used in maneuvering coordination request 210 (e.g., used to convey intended maneuvers, time windows, and priorities) may comprise application layer information elements.

[0016]

[0023] The requesting vehicle may determine the priority of the steering cooperation request 210 based on factors such as the type of the requesting vehicle and the justification for the requested maneuver. These priority levels may be based on standardized common rules and factors at the application layer. Table 1 provides an example of a priority definition for a lane change steering cooperation request. Priority levels for other types of maneuvers may be determined similarly.

[0017] [Table 1]

[0018]

[0024] Here, factors considered include the reason for the maneuver and the vehicle type. As can be seen, the reason for the requested lane change is divided into one of three categories: Strategy (e.g., continue the route), Cooperative (e.g., make room for other vehicles), or Tactic (e.g., increase speed). Furthermore, the vehicle type is divided into one of two categories: emergency vehicle or regular vehicle. However, alternative embodiments may include additional or alternative prioritization factors (e.g., based on emergency vehicle type, the maneuver or other capabilities of the requesting vehicle, etc.). Alternative embodiments may also have additional or alternative vehicle types or reasons for the lane change (e.g., including accident avoidance, which may be given a relatively high priority). In Table 1, the maneuver with priority 0 is given the highest priority, and the maneuver with priority 5 is given the lowest priority.

[0019]

[0025] The receiving V2X entity may then decide to grant the request (220) based on, for example, the requested maneuver type, the priority level, maneuver requests from other requesting vehicles, its own motion state (if the receiving V2X entity comprises a receiving vehicle), road conditions, traffic environment, and / or other such factors. Different factors may be given different weights, and the receiving V2X entity may balance each of the factors to make a decision. The ability of the maneuvering coordination request 210 to include a priority level allows the receiving V2X entity to make a more intelligent decision on whether to grant the request.

[0020]

[0026] For example, a receiving V2X entity comprising the receiving vehicle may ignore a lane change request from a requesting vehicle if granting the request would cause the receiving vehicle to respond by altering its operation in a manner that would expose passengers to some danger. However, in some embodiments, the receiving vehicle may grant such a lane change request if the priority is above a certain threshold (e.g., priority 0 or 1 in Table 1) and the risk to passengers of the receiving vehicle is relatively low.

[0021]

[0027] If the receiving V2X entity determines to grant the request, it may send a steering cooperation acceptance 230. In accordance with V2X communications, this steering cooperation acceptance 230 may comprise a “Msg_Response” message indicating the receiving V2X entity's acceptance of the requested steering (alternatively, if the receiving V2X entity rejects the request, it may send a rejection in a similar manner).

[0022]

[0028] Upon receiving the acceptance, the requesting vehicle may then decide to perform the maneuver (240) (note, however, that the requesting vehicle may have sent a similar maneuver coordination request to one or more other receiving V2X entities and may therefore wait until it receives acceptance from all receiving V2X entities before deciding to perform the maneuver). However, upon deciding to perform the maneuver, the requesting vehicle may send a maneuver coordination decision 250 to the receiving V2X entity, as illustrated in FIG. 2, informing the receiving V2X entity that the requesting vehicle will be performing the maneuver. The requesting vehicle may then begin the maneuver (260).

[0023]

[0029] Returning to FIG. 1, for example, a first vehicle 110-1 may wish to travel along route 130 and change lanes to increase speed. Given the location and speed of the second vehicle 110-2 (determined by the first vehicle 110-1), the first vehicle 110-1 may send a maneuver coordination request 210 to the second vehicle 110-2 indicating the route 130, a time window for performing the maneuver, and a priority level of the maneuver. Because the maneuver is a maneuver (to increase speed) and the first vehicle 110-1 is considered a normal (non-emergency) vehicle, the priority of the maneuver is priority 5, according to Table 1. Despite the relatively low priority, the second vehicle 110-2 may grant the request depending on the factors discussed above.

[0024]

[0030] However, if the second vehicle 110-2 receives another higher priority request, it may reject the maneuver request from the first vehicle 110-1 if the second vehicle 110-2 cannot grant both requests. For example, if a third vehicle 110-3, which comprises an emergency vehicle, sends a maneuver cooperation request 210 to the second vehicle 110-2, this may cause the second vehicle 110-2 to grant the maneuver request from the third vehicle 110-3 and reject the request of the first vehicle 110-1. More specifically, if the maneuver request from the third vehicle 110-3 indicates a maneuver (for a speed increase) along the route 140, the maneuver request may correspondingly include a priority 2 (again based on Table 1). After receiving the maneuver request from the third vehicle 110-3, the second vehicle 110-2 may determine that it cannot grant the requests of both the third vehicle 110-3 and the first vehicle 110-1 based on overlapping time windows for each vehicle to execute their respective maneuvers and / or conflicting resulting responses from the vehicles 110-2 (e.g., granting the request from the third vehicle 110-3 may require the second vehicle 110-2 to slow down, while granting the request from the first vehicle 110-1 may require the second vehicle 110-2 to accelerate). Since it cannot grant both requests, the second vehicle 110-2 may therefore grant the request of the third vehicle 110-3 and deny the request of the first vehicle 110-1 based on the request from the third vehicle 110-3 having a higher priority than the request of the first vehicle 110-1. 2, the second vehicle 110-2 may send a maneuver cooperation acceptance 230 message to the third vehicle 110-3 and a rejection message to the first vehicle 110-1. Then, after receiving a maneuver cooperation decision 250 from the third vehicle 110-3 indicating that the third vehicle 110-3 will initiate the maneuver, the second vehicle 110-2 may decelerate to allow the third vehicle 110-3 to perform the maneuver.

[0025]

[0031] 3 is an illustration of an overhead view of road 100, providing yet another example of how prioritization of maneuver request messages may be used by vehicle 110 to determine whether to allow and / or reject the maneuver request messages. Here, a fourth vehicle 110-4 sends a maneuver request to a fifth vehicle 110-5 indicating an intended maneuver along route 310 within a respective time window and with a corresponding priority. In this case, the reason for the fourth vehicle 110-4 to change lanes is for strategy (continue the route). For this reason, and because the fourth vehicle 110-4 is a regular vehicle, the maneuver request may include a priority level of 3 according to the priority levels shown in Table 1.

[0026]

[0032] However, the sixth vehicle 110-6 further sends a maneuver request to the fifth vehicle 110-5 indicating an intended maneuver along the route 320 within a respective time window that may overlap with (or be within a threshold time difference of) the time window of the intended maneuver of the fourth vehicle 110-4. Here, the reason for the sixth vehicle 110-6 to change lanes is maneuvering (to increase speed). Since the sixth vehicle 110-6 is also a normal vehicle, the corresponding maneuver request may have a priority level of 5 according to the priority levels shown in Table 1.

[0027]

[0033] Similar to the scenario of FIG. 1, there are conflicting requests. That is, the fourth vehicle 110-4 and the sixth vehicle 110-6 cannot execute their intended maneuvers because both would move to substantially the same location on the road 100 at substantially the same time, which would result in a vehicle collision. However, unlike the scenario of FIG. 1, the fifth vehicle 110-5 still needs to slow down to grant either request. However, even if the fifth vehicle 110-5 could take the same action (slow down) to grant both requests, the fifth vehicle 110-5 may still determine that granting maneuver requests from both the fourth vehicle 110-4 and the sixth vehicle 110-6 would result in conflicts. Thus, the fifth vehicle 110-5 may decide to grant one request and deny the other. And because the priority of the request of the fourth vehicle 110-4 is higher than the priority of the sixth vehicle 110-6, the fifth vehicle 110-5 can grant the request of the fourth vehicle 110-4 and deny the request of the sixth vehicle 110-6.

[0028]

[0034] FIG. 4 is a block diagram of an embodiment of a V2X device 400 that may be utilized by and / or integrated into the vehicle 110, the RSU 120, or any other system or device to wirelessly communicate with the vehicle 110 and / or the RSU as described above. When utilized by the vehicle 110, the V2X device 400 may comprise or be integrated into a vehicle computer system used to manage one or more systems related to navigation and / or autonomous driving of the vehicle and to communicate with other on-board systems and / or other traffic entities. When utilized by the RSU 120, the V2X device 400 may cause the RSU 120 to perform one or more of the functions of the receiving V2X entity described in connection with FIG. 2 and / or the functions of the method 600 shown in FIG. 6, which will be described later. Additionally, the V2X device 400 may be integrated into an RSU computer system that may include additional components and perform additional RSU-related functions. Such RSU-related functions and additional components of the RSU are described in more detail below in connection with FIG. 7. With this in mind, according to some embodiments, the V2X device 400 may comprise a standalone device or component of the vehicle 110 or the RSU 120, which may be communicatively coupled to other components / devices of the vehicle 110 or the RSU 120. It should also be noted that the V2X device 400 may be utilized by V2X entities other than the vehicle 110 or the RSU 120 as well. In addition, the embodiments may not necessarily be limited to V2X communications. Thus, alternative embodiments may include devices similar to the V2X device 400 having components similar to those shown in FIG. 4 and capable of performing the functions of the vehicle 110 and / or the RSU 120 described in the previous embodiments, but without V2X functionality.

[0029]

[0035] It should also be noted that Figure 4 is intended only to provide a generic illustration of the various components, any or all of which may be utilized as appropriate. It should also be noted that in some cases, the components illustrated by Figure 4 may be localized into a single physical device and / or distributed among various networked devices that may be located in different physical locations, for example, of the vehicle 110, the RSU 120, or other V2X entity.

[0030]

[0036] A V2X device 400 is shown comprising hardware elements that may be electrically coupled (or in communication otherwise, as appropriate) via a bus 405. The hardware elements may include processing unit(s) 410, which may include, but are not limited to, one or more general-purpose processors, one or more special-purpose processors (such as digital signal processing (DSP) chips, graphics acceleration processors, application specific integrated circuits (ASICs), and / or the like), and / or other processing structures or means.

[0031]

[0037] The V2X device 400 also can include one or more input devices 470, which can include devices related to a user interface (e.g., a touch screen, a touch pad, a microphone, button(s), dial(s), switch(es), and / or the like) and / or devices related to navigation, autonomous driving, and the like. Similarly, the one or more output devices 415 can be devices related to interaction with a user (e.g., via a display, light emitting diode(s) (LED(s)), speaker(s), etc.) and / or devices related to navigation, autonomous driving, and the like.

[0032]

[0038] The V2X device 400 may also include a wireless communication interface 430, which may comprise, without limitation, a modem, a network card, an infrared communication device, a wireless communication device, and / or a chipset (e.g., a Bluetooth device, an IEEE 802.11 device, an IEEE 802.15.4 device, a Wi-Fi device, a WiMAX device, a WAN device, and / or various cellular devices, etc.), and / or the like (examples of such communication are provided in FIG. 7 and detailed below). The wireless communication interface 430 may enable the V2X device 400 to communicate with other V2X devices. This may include various forms of communication of the aforementioned embodiments, including messaging as illustrated in FIG. 2. Thus, it may be capable of sending direct communications, broadcasting wireless signals, receiving direct and / or broadcast wireless signals, etc. Thus, the wireless communication interface 430 may be capable of transmitting and / or receiving RF signals from various RF channels / frequency bands. Communication using the wireless communication interface 430 may be performed via one or more wireless communication antenna(s) 432 that transmit and / or receive wireless signals 434.

[0033]

[0039] The V2X device 400 may further include sensor(s) 440. The sensor(s) 440 may comprise, without limitation, one or more inertial sensors and / or other sensors (e.g., accelerometer(s), gyroscope(s), camera(s), magnetometer(s), altimeter(s), microphone(s), proximity sensor(s), light sensor(s), barometer(s), and the like). The sensor(s) 440 may be used to determine certain real-time characteristics of the vehicle, such as, for example, location, speed, and acceleration. As previously mentioned, the sensor(s) 440 may be used to assist the vehicle 110 in determining its location.

[0034]

[0040] Embodiments of the V2X device 400 may also include a GNSS receiver 480 capable of receiving signals 484 from one or more GNSS satellites using an antenna 482 (which in some embodiments may be the same as antenna 432). Positioning based on the GNSS signal measurements may be utilized to determine a current location of the V2X device 400 and may further be used as a reference for determining the location of detected objects. The GNSS receiver 480 may extract a position of the V2X device 400 using conventional techniques from GNSS satellites of a GNSS system, such as the Global Positioning System (GPS) and / or similar satellite systems.

[0035]

[0041] The V2X device 400 may further comprise and / or be in communication with a memory 460. The memory 460 may include, but is not limited to, local and / or network accessible storage devices, disk drives, drive arrays, optical storage devices, solid-state storage devices such as random access memory (RAM) and / or read-only memory (ROM) that may be programmable and flash updatable, and / or the like. Such storage devices may be configured to implement any suitable data store, including, but not limited to, various file systems, database structures, and / or the like.

[0036]

[0042] The memory 460 of the V2X device 400 may also comprise software elements (not shown in FIG. 4 ) including an operating system, device drivers, executable libraries, and / or other code, such as one or more application programs, that may comprise computer programs provided by various embodiments and / or that may be designed to implement methods and / or configure systems as described herein. Software applications stored in the memory 460 and executed by the processing unit(s) 410 may be used to implement functions of the vehicle 110 or the RSU 120 as described herein. Furthermore, one or more procedures described in connection with the method(s) described herein may be implemented as code and / or instructions in the memory 460 that are executable by the V2X device 400 (and / or the processing unit(s) 410 or the DSP 420 within the V2X device 400), including functions illustrated in the methods of FIGS. 5 and 6 described below. In one aspect, such code and / or instructions may then be used to configure and / or adapt a general-purpose computer (or other device) to perform one or more operations in accordance with the described methods.

[0037]

[0043] FIG. 5 is a flow diagram of a method 500 of vehicle steering coordination according to one embodiment. Alternate embodiments may vary the functionality by combining, separating, or otherwise modifying the functions set forth in the blocks illustrated in FIG. 5. The method 500 of FIG. 5 illustrates how the requesting vehicle functionality described above (e.g., in relation to FIG. 2) may be implemented according to one embodiment. Thus, the means for performing the functionality of one or more of the blocks illustrated in FIG. 5 may comprise hardware and / or software components of the vehicle 110, which may include one or more components of the V2X device 400 illustrated in FIG. 4 and described above (as previously described).

[0038]

[0044] In block 510, the function comprises determining, at the first vehicle, a maneuver for the first vehicle to execute. As previously mentioned, this determination may be made by an on-board computer of the first vehicle (e.g., performing vehicle navigation, autonomous driving, and / or semi-autonomous driving, etc.). Thus, in some embodiments, the determination may be made by the V2X device 400, which may perform vehicle sensing, prediction, planning, and execution (as shown in FIG. 8 and described in more detail below). The maneuver may include any of a variety of maneuvers that may affect nearby vehicles, such as, for example, changing lanes, accelerating / decelerating, maneuvering through an intersection, etc. Means for performing the function in block 510 may include one or more software and / or hardware components of the V2X device, such as the bus 405, processing unit(s) 410, memory 460, and / or other software and / or hardware components of the V2X device 400 illustrated in FIG. 4.

[0039]

[0045] The functionality in block 520 comprises determining a priority level corresponding to the maneuver. As noted in the previous embodiments, the priority level may be predetermined based on various factors, such as the vehicle type (e.g., emergency or normal), the reason for the maneuver, or both. In some embodiments, the priority may be predetermined based on the maneuver type (e.g., some maneuvers may be given higher priority than others), but as noted above, embodiments may additionally or alternatively provide similar functionality by allowing the maneuver type to be considered by the receiving vehicle when determining whether to grant the maneuver request. The means for performing the functionality in block 520 may include one or more software and / or hardware components of the V2X device, such as the bus 405, processing unit(s) 410, memory 460, and / or other software and / or hardware components of the V2X device 400 illustrated in FIG. 4.

[0040]

[0046] At block 530, the function comprises wirelessly transmitting, from the first vehicle, a request to perform the maneuver. The request comprises information indicating the maneuver, a priority level, and a time window for performing the maneuver. As previously described, the time window for performing the maneuver may be determined by the first vehicle (e.g., by the processing unit(s) 410 of the V2X device 400 integrated in the first vehicle) based on characteristics such as, for example, vehicle speed, maneuvering capabilities, location, etc. According to some embodiments, the first message may be wirelessly transmitted in accordance with a V2X communication standard or other wireless communication standard enabling communication between vehicles, infrastructure, and / or other traffic-related entities. Means for performing the function at block 530 may include one or more software and / or hardware components of the V2X device, such as the bus 405, the processing unit(s) 410, the memory 460, the wireless communication interface 430, and / or other software and / or hardware components of the V2X device 400 illustrated in FIG. 4.

[0041]

[0047] 2, the request may be granted or denied, and the requesting vehicle may respond accordingly. Thus, an embodiment of method 500 may further include receiving, at the first vehicle, an acceptance message from the second vehicle, and performing the maneuver with the first vehicle in response to receiving the acceptance message from the second vehicle.

[0042]

[0048] FIG. 6 is a flow diagram of a method 600 of vehicle steering coordination according to one embodiment. Alternate embodiments may vary the functionality by combining, separating, or otherwise modifying the functions described in the blocks illustrated in FIG. 6. The method 600 of FIG. 6 illustrates how the functionality of a receiving V2X entity (e.g., a receiving vehicle or RSU) described above (e.g., in relation to FIG. 2) may be implemented according to one embodiment. Thus, the means for performing the functionality of one or more of the blocks illustrated in FIG. 6 may comprise hardware and / or software components of the V2X device 400 illustrated in FIG. 4 and described above.

[0043]

[0049] In block 610, the function comprises wirelessly receiving a request to perform a maneuver from a vehicle, where the request comprises information indicating the maneuver, a priority level, and a time window for performing the maneuver. The request may be received wirelessly via V2X communications and / or other wireless means. The means for performing the function in block 610 may include one or more software and / or hardware components of a V2X device, such as the bus 405, processing unit(s) 410, memory 460, wireless communications interface 430, and / or other software and / or hardware components of the V2X device 400 illustrated in FIG.

[0044]

[0050] The function in block 620 comprises determining whether to grant a request based at least in part on a priority level of the request. As described in the above embodiment, the priority level may be used to determine which of multiple requests to grant. Additionally or alternatively, the priority level may be used in conjunction with other factors, such as, for example, road conditions, traffic environment, and motion state of the receiving vehicle. The means for performing the function in block 620 may include one or more software and / or hardware components of the V2X device, such as the bus 405, processing unit(s) 410, memory 460, and / or other software and / or hardware components of the V2X device 400 illustrated in FIG. 4.

[0045]

[0051] In block 630, the function comprises wirelessly sending a response indicating whether the request was granted. Granting the request may allow the requesting vehicle to perform the maneuver, and denial may result in the requesting vehicle not performing the maneuver. Additionally, as illustrated in the above embodiment, the receiving V2X entity may grant some requests and deny others if the requests are conflicting (e.g., if granting the requests would pose a danger to one or more vehicles). The means for performing the function in block 630 may include one or more software and / or hardware components of the V2X device, such as the bus 405, processing unit(s) 410, memory 460, wireless communication interface 430, and / or other software and / or hardware components of the V2X device 400 illustrated in FIG. 4.

[0046]

[0052] In some cases where the requesting vehicle comprises a first vehicle, the method 600 may be performed by a receiving vehicle that comprises a second vehicle. In such cases, receiving the request, determining whether to grant the request, and wirelessly sending the response may all be performed by the second vehicle. Additionally, in some cases (e.g., as described in the embodiments of Figs. 1 and 3), the second vehicle may receive one or more requests from different vehicles, e.g., receiving a first request from the first vehicle and a second request from a third vehicle. The second vehicle may decide to grant the first request further based on a priority level of the second request received by the second vehicle from the third vehicle. In such cases, determining whether to grant the first request may comprise deciding to deny the first request based on a determination that the priority level of the second request is higher than the priority level of the first request, and thus the response comprises information indicating the denial of the first request. Alternatively, determining whether to grant the first request may comprise determining to accept the first request based on a determination that the priority level of the second request is lower than the priority level of the first request, in which case the response may comprise information indicating the acceptance of the first request.

[0047]

[0053] 7-9 are illustrations of systems, structural devices, vehicle components, and other devices, components, and systems related to V2X communications that may be used to implement techniques provided herein for coordination of vehicle steering among multiple vehicles, according to some embodiments. It should be noted that some components in these figures (e.g., RSU(s) 725 and vehicles 780, 790, 800, 900) may correspond to similar components (e.g., RSU 120 and vehicle 110) in previous embodiments and figures.

[0048]

[0054] FIG. 7 is an illustration of a system in which vehicles may communicate with various devices, vehicles, and servers over various networks, according to one embodiment. In one embodiment, a V2X vehicle A 780 may communicate with a V2X or otherwise communication transceiver-enabled vehicle B 790 over a link 723 using a V2X or other wireless communication transceiver. Some embodiments may communicate, for example, to perform vehicle-to-vehicle relative positioning, negotiate lane changes, negotiate to traverse an intersection, and / or to exchange V2X data elements such as GNSS measurements, vehicle states, vehicle location and vehicle capabilities, measurement data, and / or calculated states. Such communications may additionally or alternatively be used to exchange other V2X vehicle state steps that may not be included in the V2X capability data elements.

[0049]

[0055] In some embodiments, vehicle A 780 may also communicate with vehicle B 790 through the network. This may be done using wireless signals 722 / 724 to / from base station 720 and / or via wireless signals 732 to / from access point 730. Additionally or alternatively, such communication may be done via one or more communication-enabled RSU(s) 725, any of which may relay communications, information, and / or convert protocols for use by other vehicles, such as vehicle B 790. This latter function may be done, for example, in embodiments where vehicle B 790 is not able to directly communicate with vehicle A 780 in a common protocol. In one embodiment, the RSU(s) 725 may comprise various types of roadside beacons, traffic and / or vehicle monitors, traffic control devices, and location beacons. Further, as previously mentioned, the RSU(s) 725 may correspond to the RSU 120 illustrated in FIGS. 1 and 3 and may therefore include the components of the V2X device 400 illustrated in FIG. 4 (which may be used in addition to or as an alternative to the components of the RSU(s) 725 illustrated in FIG. 7 described below) and may be configured to perform the method 600 of vehicle steering coordination of FIG. 6.

[0050]

[0056] In one embodiment, the RSU(s) 725 may have a processor 725A configured to operate a wireless transceiver 725E to transmit and receive wireless messages, e.g., BSM, CAM, or other V2X messages, to / from vehicle A 780 and / or vehicle B 790 from the base station 720 and / or access point 730. For example, the wireless transceiver 725E may transmit and / or receive wireless messages in various protocols, such as V2X communications with vehicles (e.g., using sidelink communications) and / or using various wide area network (WAN), wireless local area network (WLAN), and / or personal area network (PAN) protocols for communicating over wireless communications networks. In one embodiment, the RSU(s) 725 may include one or more processors 725A communicatively coupled to a wireless transceiver 725E and a memory, and may include instructions and / or hardware for acting as a traffic control unit 725C and / or for providing and / or processing environmental and roadside sensor information 725D or for serving as a location reference for a GNSS relative location between it and the vehicle. In one embodiment, the RSU(s) 725 may include a network interface 725B (and / or a wireless transceiver 725E), which in one embodiment may communicate with an external server, such as a traffic optimization server 765, a vehicle information server 755, and / or an environmental data server 740. In one embodiment, the wireless transceiver 725E may communicate over a wireless communication network by transmitting or receiving wireless signals from a wireless base transceiver subsystem (BTS), a Node B, or an evolved Node B (eNodeB) or next generation Node B (gNodeB) via a wireless communication link. In one embodiment, the wireless transceiver(s) 725E may comprise various combinations of WAN, WLAN, and / or PAN transceivers.Also, in one embodiment, the local transceiver may be a Bluetooth transceiver, a ZigBee transceiver, or other PAN transceiver. The local transceiver, WAN wireless transceiver, and / or mobile wireless transceiver may comprise a WAN transceiver, an access point (AP), a femtocell, a home base station, a small cell base station, a home node B (HNB), a home eNodeB (HeNB), or a next generation node B (gNodeB), and may provide access to a wireless local area network (WLAN, e.g., an IEEE 902.11 network), a wireless personal area network (PAN, e.g., a Bluetooth network), or a cellular network (e.g., an LTE network, or other wireless wide area network such as those described in the next paragraph). It should be understood that these are merely examples of networks that may communicate with the RSU(s) 725 via a wireless link, and that claimed subject matter is not limited in this respect.

[0051]

[0057] The RSU(s) 725 may receive location, status, GNSS and other sensor measurements, and capability information from vehicle A 780 and / or vehicle B 790, such as, for example, GNSS measurements, sensor measurements, speed, heading, location, stopping distance, priority or emergency conditions, and other vehicle-related information. In an embodiment, environmental information such as road surface information / conditions, weather conditions, and camera information may be collected and shared with the vehicles via either point-to-point or broadcast messaging. The RSU(s) 725 may utilize information received from vehicle A 780 and / or vehicle B 790 via wireless transceiver 725E, environmental and roadside sensors 725D, and network information and control messages, for example, from traffic control and optimization server 765, to coordinate and direct traffic flow and provide environmental, vehicle, safety, and announcement messages to vehicle A 780 and vehicle B 790.

[0052]

[0058] The processor 725A, in one embodiment, may be configured to operate a network interface 725B, which may be connected to a network 770 via a backhaul and, in one embodiment, may be used to communicate and coordinate with various centralized servers, such as a centralized traffic control and optimization server 765 that monitors and optimizes traffic flow within an area or region, such as within a city or section of a city. The network interface 725B may also be utilized for remote access to the RSU(s) 725 for crowdsourcing of vehicle data, maintenance of the RSU(s) 725, and / or coordination with other RSU(s) 725 or other uses. The RSU(s) 725 may have a processor 725A configured to operate a traffic control unit 725C, which may be configured to process data received from vehicles, such as vehicle A 780 and vehicle B 790, such as location data, stopping distance data, road condition data, identification data, and status of nearby vehicles as well as other information related to the location and environment. The RSU(s) 725 may have a processor 725A configured to acquire data from environmental and roadside sensors 725D, which may include temperature sensors, weather sensors, camera sensors, air pressure sensors, road sensors (e.g., for automobile detection), accident detection sensors, movement detection sensors, speed detection sensors, and other vehicle and environmental monitoring sensors.

[0053]

[0059] In one embodiment, vehicle A 780 may also communicate with mobile device 700 using short range communications and personal networks such as Bluetooth, Wi-Fi, or Zigbee, for example, to access WAN and / or Wi-Fi networks in one embodiment, and / or to obtain sensor and / or location measurements from mobile device 700 in one embodiment, or via V2X (e.g., CV2X / sidelink communications) or other vehicle related communications protocols. In one embodiment, vehicle A 780 may communicate with mobile device 700 through a WAN network using WAN related protocols, such as via a WAN base station 720, or directly peer-to-peer using Wi-Fi or via a Wi-Fi access point. Vehicle A 780 and / or vehicle B 790 may communicate using a variety of communications protocols. In one embodiment, vehicle A 780 and / or vehicle B 790 may support a variety of wireless communication modes, such as using V2X, Global System for Mobile Communications (GSM), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), High Rate Packet Data (HRPD), Wi-Fi, Bluetooth, WiMAX, LTE, 5G New Radio Access Technology (NR) communication protocols, etc.

[0054]

[0060] In one embodiment, vehicle A may communicate over a WAN network via base station 720 using a WAN protocol, or with a WLAN access point 730 using a WLAN protocol such as Wi-Fi. The vehicle may also support wireless communications using, for example, a WLAN or PAN (such as Bluetooth or ZigBee).

[0055]

[0061] Vehicle A 780 and / or vehicle B 790 may include one or more GNSS receivers, such as GNSS receiver 480, for receiving GNSS signals 712 from GNSS satellites 710 for location determination, time acquisition, and time keeping, in one embodiment. Various GNSS systems may be supported, alone or in combination, using GNSS receiver 480 or other receivers to receive signals from Beidou, Galileo, GLONASS (GLObal NAvigation Satellite System), and / or Global Positioning System (GPS), and various regional navigation systems, such as Quasi-Zenith Satellite System (QZSS) and NavIC or Indian Regional Navigation Satellite System (IRNSS). In one example, other wireless systems, such as those that rely on beacons, such as one or more RSU(s) 725, one or more WLAN access points 730, or one or more base stations 720, may be utilized. Various GNSS signals 712 may be utilized in conjunction with vehicle sensors to determine location, speed, and proximity to other vehicles, such as between vehicle A 780 and vehicle B 790.

[0056]

[0062] In one embodiment, vehicle A and / or vehicle B may access a location determined at least in part using GNSS measurements and / or GNSS provided by mobile device 700, which in one embodiment also has GNSS, WAN, Wi-Fi, and other communications receivers and / or transceivers. In one embodiment, vehicle A 780 and / or vehicle B 790 may access a location determined at least in part using GNSS measurements (such as pseudorange measurements, Doppler measurements, and satellite IDs) and / or GNSS provided by mobile device 700 as a fallback in case GNSS receiver 480 does not function or provides location accuracy below a threshold level.

[0057]

[0063] Vehicle A 780 and / or vehicle B 790 may access various servers on the network, such as a vehicle information server 755, a route server 745, a location server 760, a map server 750, and an environmental data server 740.

[0058]

[0064] The vehicle information server 755 may provide information describing various vehicles, such as antenna locations, vehicle size, and vehicle capabilities, which may be utilized in making maneuvering decisions regarding nearby vehicles, such as whether the nearby vehicles are capable of stopping or accelerating in a timely manner, whether the nearby vehicles are autonomous, whether they are capable of autonomous driving, whether they are capable of communication, etc. In one embodiment, the vehicle information server 755 may also provide information regarding vehicle size, shape, capabilities, identification information, ownership, occupancy, and / or the determined location point (e.g., the location of the GNSS receiver, etc.) and the location of the vehicle boundary relative to the determined location point.

[0059]

[0065] The route server 745 may receive current location and destination information and provide routing information, map data, alternate route data, and / or traffic and street condition data for the vehicle.

[0060]

[0066] Location server 760, in one embodiment, may provide location determination capabilities, transmitter signal acquisition assistance (such as GNSS satellite orbit prediction information, time information approximate location information, and / or approximate time information), transceiver almanacs such as those including identification information and locations for Wi-Fi access points and base stations, and, in some embodiments, additional information related to the route such as speed limits, traffic, and road / construction conditions. Map server 750 may provide map data such as road locations, points of interest along roads, address locations along roads, road sizes, road speed limits, traffic conditions, and / or road conditions (wet, slippery, snowy / icy, etc.), road conditions (open, under construction, accidents, etc.). Environmental data server 740, in one embodiment, may provide weather and / or road-related information, traffic information, terrain information, and / or road quality and speed information, and / or other related environmental data.

[0061]

[0067] In one embodiment, the vehicles 780 and 790 and mobile device 700 of FIG. 7 may communicate over network 770 via various network access points, such as WLAN access point 730 or over network 770 via wireless WAN base station 720. The vehicles 780 and 790 and mobile device 700 may also communicate directly between devices, between vehicles, from device to vehicle, and from vehicle to device using various short range communication mechanisms for communicating directly without going through network 770, such as via Bluetooth, Zigbee, and 5G new radio standards, in some embodiments.

[0062]

[0068] 8 comprises a functional block diagram of a vehicle 800, according to one embodiment. As previously mentioned, the vehicle 800 may comprise a V2X device 400. Accordingly, example hardware and / or software components for implementing the blocks shown in FIG. 8 are illustrated in FIG.

[0063]

[0069] 8, vehicle 800 may receive vehicle and environmental information from vehicle external sensors 802, vehicle internal sensors 804, vehicle capabilities 806, external wireless information 808 such as other vehicle location and GNSS measurement information (from the environment, from other vehicles, from RSU(s), from a system server), and / or vehicle motion states 810 (describing current and / or future motion states). The received vehicle, sensor, and environmental information may be processed in one embodiment in one or more processing units 410, DSP(s) 420, and memory 460 (shown in FIG. 4), which are connected and configured to provide external object sensing and classification, prediction and planning, and maneuver execution, as well as to determine and update V2X or other wireless data element values, including GNSS data element values, and to transmit messaging including the determined data elements via wireless communication interface 430. Messaging and data elements may be transmitted and received via various means, protocols, and standards, such as Society of Automotive Engineers (SAE) or European Telecommunications Standards Institute (ETSI) CV2X messages and / or other wireless V2X protocols supported by the wireless communications interface 430.

[0064]

[0070] The vehicle-to-vehicle relative location determination block 828 may be used to determine the relative locations of the vehicles within the area of ​​interest. In one embodiment, GNSS data is exchanged with the vehicles or with other devices, such as RSUs, to determine and / or verify and / or increase the accuracy of the relative locations associated with the other vehicles or devices. In one embodiment, determining the vehicles (or other devices) within the area of ​​interest may utilize broadcast location information, such as broadcast latitude and longitude received in messages from other vehicles, other devices, and location information for the vehicle 800 to determine approximate relative locations and / or approximate distances between the vehicles.

[0065]

[0071] In one embodiment, other vehicle-related input sources, such as servers 755, 745, 760, 750, and 740, provide information such as vehicle information, routing, location assistance, map data, and environmental data, and may provide input regarding and / or complement and / or be used in conjunction with other inputs, such as input of road location data, map data, driving situation data, and other vehicle-related data, used in conjunction with inter-vehicle maneuver coordination 824 to determine maneuver execution 826. In one embodiment, map data may include the location of roadside units relative to road locations, where vehicles may utilize relative positioning between RSUs in combination with map data to determine positioning relative to the road surface, especially in situations where other systems may not function due to low visibility weather conditions (snow, rain, dust storms, etc.), etc. In one embodiment, map data from map server 750 may be utilized in conjunction with relative and / or absolute data from neighboring vehicles and / or RSU(s) 725 to determine high confidence absolute locations for multiple vehicles and relative locations relative to the road / map. For example, if vehicle A 780 has a more accurate / reliable location than other vehicles communicating with vehicle A 780, then vehicle B 790, for example, may use the GNSS information for high accuracy location and high accuracy relative location from vehicle A 780 sent to vehicle B 790 to determine a high accuracy location for vehicle B 790, even if vehicle B's system is unable to calculate a high accuracy location in a particular situation or environment. In this situation, vehicle A having a high accuracy location determination system benefits all surrounding vehicles by sharing one or more high accuracy locations along with ongoing relative location information. Furthermore, assuming the map data from map server 750 is accurate, being able to propagate high accuracy location data from vehicle A 780 to surrounding vehicles such as vehicle B 790 allows the surrounding vehicles to also accurately determine their relative location relative to the map data, even in difficult signal / location environments.The vehicle information server 755 may provide vehicle information such as size, shape, and antenna location, which may be utilized, for example, by vehicle A or other vehicles to determine the relative location between the GNSS receiver on vehicle A 780 and, for example, vehicle B 790, as well as the distance between the closest points of vehicle A 780 and vehicle B 790. In one embodiment, traffic information from the traffic control and optimization server 765 may be utilized to determine overall route selection and rerouting, which is used (in one embodiment) in conjunction with the route server 745. In one embodiment, the environmental data server 740 may provide input regarding road conditions, black ice, snow, water on the road, and other environmental conditions, which may also affect the decisions and criteria in the vehicle-to-vehicle steering coordination block 824 and the steering execution block 826. For example, in icy or rainy conditions, the vehicle 800 may implement and / or request increased vehicle-to-vehicle distance from adjacent vehicles, or may select route options that avoid road hazard conditions such as black ice and puddles.

[0066]

[0072] Block 828 may be implemented using various dedicated or general-purpose hardware and software, such as, for example, using processing unit(s) 410 and / or DSP 420 and memory 460 (also shown in FIG. 4), or in one embodiment, in specialized hardware blocks such as dedicated sensor processing and / or vehicle messaging cores. According to some embodiments, the location of nearby vehicles may be determined through various means, such as based on signal-based timing measurements, such as round trip time, time of arrival (TOA), signal strength of the vehicle's broadcast signal, and / or distance determined based on the broadcast latitude and longitude from neighboring vehicles and the vehicle's current location. Additionally or alternatively, the location of nearby vehicles may be determined from sensor measurements, such as LIght Detection And Ranging (LIDAR), RAdio Detection And Ranging (RADAR), SOund Navigation And Ranging (SONAR), and camera measurements. In one embodiment, some or all of blocks 802, 804, 806, 808, and / or 810 may have dedicated processing cores, for example to improve performance and reduce measurement latency. In one embodiment, some or all of blocks 802, 804, 806, 808, and / or 810 may share processing with block 828.

[0067]

[0073] Vehicle external sensors 802 may comprise cameras, LIDAR, RADAR, SONAR, proximity sensors, rain sensors, weather sensors, GNSS receiver 480 in some embodiments, and received data used with the sensors, such as map data, environmental data, location, route, and / or other vehicle information, may be received from other vehicles, devices, and servers, such as in one embodiment from map server 750, route server 745, vehicle information server 755, environmental data server 740, location server 760, etc., and / or from associated devices such as mobile device 700 that may be present in or near a vehicle, such as vehicle A 780. For example, in one embodiment, mobile device 700 may provide an additional source of GNSS measurements, may provide an additional source of motion sensor measurements, or may provide network access as a communications portal to a WAN, Wi-Fi, or other network and as a gateway to various information servers, such as servers 740, 745, 750, 755, 760, and / or 765.

[0068]

[0074] It is understood that the vehicle 800 may include one or more cameras. In one embodiment, the cameras may be forward-facing, side-facing, rear-facing, or adjustable in field of view (e.g., rotatable cameras). For example, there may be multiple cameras 906 facing the same plane as shown in FIG. 9. For example, the camera 906 and the bumper-mounted camera 908 may comprise two forward-facing cameras, one focused on lower objects and / or a lower viewpoint for parking purposes (e.g., bumper-mounted), and one focused on a higher viewpoint for tracking traffic, other vehicles, pedestrians, and objects that are further away, etc. In one embodiment, the various fields of view may be stitched and / or correlated to other inputs, such as V2X inputs from other vehicles, to optimize tracking of other vehicles and external entities and objects, and / or to calibrate the sensor systems to each other. The LIDAR 904 may be roof-mounted and rotated, or may be focused on a particular viewpoint (e.g., forward-facing, rear-facing, side-facing). The LIDAR 904 may be solid-state or mechanical. The proximity sensors may be ultrasonic, RADAR-based, light-based (such as based on infrared distance measurements), and / or capacitive (surface tactile-directed or capacitive detection of metal objects). The rain and weather sensors may include various sensing capabilities and technologies, such as air pressure sensors, moisture detectors, rain sensors, and / or light sensors, and / or may leverage other existing sensor systems. The GNSS receiver may be roof-mounted, such as on a fin antenna assembly at the rear of the roof of an automobile, hood or dash-mounted, or otherwise located on the exterior or interior of the vehicle.

[0069]

[0075] In one embodiment, the interior vehicle sensors 804 may include tire pressure sensors, brake pad sensors, brake condition sensors, speedometers and other speed sensors, heading and / or orientation sensors such as magnetometers and magnetic compasses, distance sensors such as odometers and wheel tick sensors, inertial sensors such as accelerometers and gyros and inertial positioning results using the above-mentioned sensors, and wheel sensors 912 such as yaw, pitch, and / or roll sensors that may be determined individually or using other sensor systems such as accelerometers, gyros, and / or tilt sensors.

[0070]

[0076] Both the vehicle interior sensors 804 and the vehicle exterior sensors 802 may have shared or dedicated processing capabilities. For example, a sensor system or subsystem may have one or more sensor processing cores that determine vehicle state values ​​such as yaw, pitch, roll, heading, speed, acceleration capabilities and / or distance, and / or stopping distance based on measurements and other inputs from accelerometers, gyros, magnetometers, and / or other sensing systems. Different sensing systems may communicate with each other to determine measurements or may send values ​​to block 828 to determine vehicle location. Vehicle state values ​​derived from measurements from the interior and exterior sensors may be further combined with vehicle state values ​​and / or measurements from other sensor systems using a general purpose or application processor. For example, blocks 828 and / or 824 may be implemented on a dedicated or centralized processor to determine data element values ​​for V2X messaging that may be sent utilizing wireless communication interface 430 or via other communication transceivers. In one embodiment, the sensors may be separated into associated systems, e.g., LIDAR, RADAR, motion, wheel systems, etc., which are operated by dedicated cores that process raw results from each core to output vehicle state values ​​that are combined and interpreted to derive a combined vehicle state value, which includes capability data elements and status data elements, that may be used to control or otherwise affect the operation of the vehicle and / or messaging steps shared with other vehicles and / or systems via V2X or other messaging capabilities. These messaging capabilities, in one embodiment, may be based on various wireless-related, optical-related, or other communication standards, such as those supported by wireless communication interface 430 and antenna(s) 432.

[0071]

[0077] In one embodiment, the vehicle capabilities 806 may comprise performance estimates for stopping, braking, acceleration, and turning radius, and autonomous and / or non-autonomous states and / or one or more capabilities. The capability estimates may be based on stored estimates, which in one embodiment may be loaded into memory. These estimates may be based on empirical performance figures for a particular vehicle or for an average across one or more vehicles, and / or one or more models for a given performance figure. When performance estimates for multiple models are averaged or otherwise combined, they may be selected based on similar or common characteristics. For example, vehicles with similar or the same weight and the same or similar drivetrain may share performance estimates for driving performance related estimates such as braking / stopping distance, turning radius, and acceleration performance. Vehicle performance estimates may also be obtained over the wireless network from a vehicle data server on the network, for example, using the external V2X input(s) 808. This is particularly useful for obtaining information about vehicles that do not have wireless capabilities and cannot provide vehicle information directly. In one embodiment, vehicle capabilities 806 may also be affected by vehicle component conditions such as tire wear, tire brand capabilities, brake pad wear, brake brand and capabilities, and engine condition. In one embodiment, vehicle capabilities 806 may also be affected by overall vehicle conditions such as speed, direction of travel, and by external factors such as road surface, road conditions (wet, dry, slippery / traction), weather (windy, rain, snow, black ice, slippery roads, etc.). In many cases, external factors such as wear or other system degradation, and weather, road surface, road conditions, etc. may be utilized to reduce, confirm, or improve performance estimates. In some embodiments, actual measured vehicle performance, such as measured vehicle stopping distance and / or acceleration time per distance, may be measured and / or estimated based on actual vehicle driving related performance. In one embodiment, if measurements do not match, more recently measured performance may be weighted more heavily or prioritized over older measurements.Similarly, in one embodiment, measurements obtained under similar conditions, such as the same type of weather or the same type of road surface as that currently being detected by the vehicle, such as via vehicle exterior sensors 802 and / or vehicle interior sensors 804, may be weighted more heavily and / or prioritized in determining capability.

[0072]

[0078] The V2X vehicle sensing, prediction, and planning execution 812 handles the receipt and processing of information from blocks 802, 804, 806, 808, and 810 via an external object sensing and classification block 814, utilizing in part a sensor fusion and object classification block 816 to correlate, corroborate, and / or combine data from input blocks 802, 804, 806, 808, and 810. The external object sensing and classification block 814 determines what objects are present and determines the object's type (car, truck, bicycle, motorcycle, pedestrian, animal, etc.) and / or its status relative to the vehicle, such as its movement state, proximity, direction of travel, and / or location relative to the vehicle, its size, threat level, and vulnerability priority (e.g., pedestrians have a higher vulnerability priority than street litter). In one embodiment, block 814 may utilize GNSS measurement messages from other vehicles to determine a relative positioning relative to the other vehicles. The output from this block 814 may be provided to a prediction and planning block 818, which determines the detected objects and vehicles and their associated trajectories via block 820, and determines a vehicle maneuver and path plan in block 822, the output of which is utilized in a vehicle maneuver execution block 826, either directly or via a V2X vehicle-to-vehicle negotiation block 824, which will integrate and consider maneuver plans, locations, and conditions received from other vehicles. V2X vehicle-to-vehicle negotiation takes into account the state of neighboring vehicles and allows negotiation and cooperation between neighboring or otherwise affected vehicles based on various conditions such as vehicle priority, vehicle capabilities (such as being able to stop, slow down, or speed up to avoid a collision), and in some embodiments, weather conditions (rain, fog, snow, wind), road conditions (dry, wet, icy, slippery), etc. These include, for example, negotiation of the timing and order of traversing an intersection between vehicles approaching an intersection, negotiation of lane changes between adjacent vehicles, negotiation of parking spaces, access to directional movement on a single lane road, or negotiation of passing another vehicle.Vehicle-to-vehicle negotiations may also include time-based and / or distance-based factors such as reservation time, destination distance, and estimated route time to reach the destination, and in some embodiments, the type of reservation and the importance of the reservation.

[0073]

[0079] FIG. 9 is a perspective view of an exemplary vehicle 900 according to one embodiment capable of communicating with other vehicles and / or V2X entities in the above-described embodiments. Here, some of the components described in connection with FIG. 4 and the previous embodiment are shown. As illustrated and described above, the vehicle 900 may have a camera(s) such as a rearview mirror mounted camera 906, a front fender mounted camera (not shown), a side mirror mounted camera (not shown), and a rear camera (not shown, typically on the trunk, hatch, or rear bumper). The vehicle 900 may also have a LIDAR 904 for detecting objects and measuring distances to those objects; the LIDAR 904 is often roof mounted, but if there are multiple LIDAR units 904, they may be oriented around the front, rear, and sides of the vehicle. The vehicle 900 may have various other location related systems such as a GNSS receiver 480 (typically located in a shark fin unit at the rear of the roof as shown), various wireless communication interfaces (WAN, WLAN, V2X, etc., typically but not necessarily located in the shark fin) 902, a RADAR 908 (typically in the front bumper), and a SONAR 910 (if present, typically located on both sides of the vehicle). There may also be various wheel sensors 912 and drive train sensors such as tire pressure sensors, accelerometers, gyros, and wheel rotation detection and / or counters. In one embodiment, distance measurements and relative locations determined via various sensors such as LIDAR, RADAR, cameras, GNSS, and SONAR may be combined with information regarding the size and shape information of the automobile and the location of the sensors to determine distances and relative locations between surfaces of different vehicles, whereby the distance or vector from a sensor to another vehicle or between two different sensors (such as two GNSS receivers) is incrementally increased to account for the location of the sensors on each vehicle. Therefore, the precise GNSS distance and vector between the two GNSS receivers needs to be corrected based on the relative locations of the various vehicle surfaces to the GNSS receivers.For example, in determining the distance between the front bumper of the trailing vehicle and the rear bumper of the leading vehicle, the distance needs to be adjusted based on the distance between the GNSS receiver of the trailing vehicle and the front bumper, and the distance between the GNSS receiver of the leading vehicle and the rear bumper of the leading vehicle. For example, the distance between the rear bumper of the leading vehicle and the front bumper of the trailing vehicle is the relative distance between the two GNSS receivers minus the distance from the GNSS receiver of the trailing vehicle to the front bumper minus the distance from the GNSS receiver of the leading vehicle to the rear bumper. It is understood that this list is not intended to be limiting, and that FIG. 9 is intended to provide example locations of various sensors in one embodiment of a vehicle equipped with a V2X device 400.

[0074]

[0080] With reference to the accompanying figures, components that may include memory may include non-transitory machine-readable media. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any storage medium that participates in providing data that causes a machine to operate in a specific manner. In the embodiments provided above, various machine-readable media may participate in providing instructions / code to a processing unit and / or other device(s) for execution. Additionally or alternatively, machine-readable media may be used to store and / or transport such instructions / code. In many implementations, computer-readable media are physical and / or tangible storage media. Such media may take many forms, including but not limited to non-volatile media, volatile media, and transmission media. Common forms of computer readable media include, for example, magnetic and / or optical media, any other physical medium having a pattern of holes, RAM, Programmable ROM (PROM), Erasable Programmable ROM (EPROM), FLASH®-EPROM, any other memory chip or cartridge, a carrier wave as described below, or any other medium from which a computer can read instructions and / or code.

[0075]

[0081] The methods, systems, and devices described herein are examples. Various embodiments may omit, substitute, or add various procedures or components, as appropriate. For example, features described in connection with a particular embodiment may be combined in various other embodiments. Different aspects and elements of the embodiments may be combined in a similar manner. Various components of the diagrams provided herein may be embodied in hardware and / or software. Also, because technology evolves, many of the elements are examples that do not limit the scope of the disclosure to those particular examples.

[0076]

[0082] It has proven convenient at times, primarily for reasons of common usage, to refer to such signals as bits, information, values, elements, symbols, characters, variables, terms, numbers, or numerals, or the like. It should be understood, however, that all of these or similar terms are to be associated with appropriate physical quantities and are merely convenient labels. Unless otherwise indicated, and as is apparent from the above description, throughout this specification, descriptions utilizing terms such as, for example, "processing," "calculating," "calculating," "determining," "ascertaining," "identifying," "associating," "measuring," or "performing" are understood to refer to actions or processes of a particular apparatus, such as a special-purpose computer or similar special-purpose electronic computing device. Thus, in the context of this specification, a special-purpose computer or similar special-purpose electronic computing device is capable of manipulating or transforming signals that are typically represented as physical electronic, electrical, or magnetic quantities in memories, registers, or other information storage, transmission, or display devices of the special-purpose computer or similar special-purpose electronic computing device.

[0077]

[0083] As used herein, the terms "and" and "or" may include various meanings that are also expected to depend at least in part on the context in which such terms are used. Typically, "or," when used to link a list such as A, B, or C, is intended to mean A, B, and C, which are used herein in an inclusive sense, and A, B, or C, which are used herein in an exclusive sense. Furthermore, the term "one or more" as used herein may be used to describe any feature, structure, or characteristic in the singular, or may be used to describe any combination of multiple features, structures, or characteristics. However, it should be noted that this is merely an illustrative example, and claimed subject matter is not limited to this example. Furthermore, the term "at least one of," when used to link a list such as A, B, or C, may be interpreted to mean any combination of A, B, and / or C, such as, for example, A, AB, AA, AAB, AABBCCC, etc.

[0078]

[0084] Although several embodiments have been described, various modifications, alternative configurations, and equivalents may be used without departing from the gist of the present disclosure. For example, the above elements are merely components of a larger system, where other rules may take precedence over or otherwise modify the application of the various embodiments. Also, some steps may be performed before, during, or after the above elements are considered. Thus, the above description does not limit the scope of the present disclosure. The invention as described in the claims of the original application is set forth below. [C1] 1. A method for vehicle steering coordination, comprising: determining, at a first vehicle, a maneuver for the first vehicle to execute; determining a priority level corresponding to the maneuver; and wirelessly transmitting, from the first vehicle, a request to execute the maneuver, wherein the request comprises: The operation, said priority level; and a time window for performing said maneuver; Provided with information indicating A method comprising: [C2] The method described in [C1], wherein the first request is transmitted wirelessly in accordance with a vehicle-to-everything (V2X) communication standard. [C3] The method of [C1], wherein the priority level is based on a reason for the maneuver, a vehicle type of the first vehicle, or both. [C4] receiving an acceptance message from a second vehicle or a roadside unit (RSU) at the first vehicle; executing the maneuver with the first vehicle in response to receiving the acceptance message; The method according to [C1], further comprising: [C5] 1. A method for vehicle steering coordination, comprising: wirelessly receiving a first request to execute a maneuver from a first vehicle, wherein the first request comprises information indicative of the maneuver, a priority level, and a time window for executing the maneuver; determining whether to grant the first request based at least in part on the priority level of the first request; wirelessly sending a response indicating whether the first request was granted; and A method comprising: [C6] The method of [C5], wherein receiving the first request, determining whether to grant the first request, and wirelessly sending the response are performed by a second vehicle. [C7] The method of [C6], wherein the second vehicle determines whether to grant the first request further based on a priority level of a second request received by the second vehicle from a third vehicle. [C8] determining whether to grant the first request comprises determining to deny the first request based on a determination that the priority level of the second request is higher than the priority level of the first request; the response comprises information indicating a denial of the first request. The method described in [C7]. [C9] determining whether to grant the first request comprises determining to accept the first request based on a determination that the priority level of the second request is lower than the priority level of the first request; the response comprises information indicating acceptance of the first request. The method described in [C7]. [C10] A device comprising a communication interface, a memory, and one or more processing units, the one or more processing units being communicatively coupled to the communication interface and the memory and configured to cause the device to execute a method according to any one of [C1] to [C9]. [C11] A device comprising means for carrying out the method according to any one of [C1] to [C9]. [C12] A non-transitory computer-readable medium having embedded instructions which, when executed by one or more processing units, cause the one or more processing units to perform a method according to any one of [C1] to [C9].

Claims

1. 1. A method for vehicle steering coordination, comprising: determining, at a first vehicle, a maneuver for the first vehicle to execute; determining a priority level corresponding to the maneuver; and wirelessly transmitting, from the first vehicle, a request to execute the maneuver, wherein the request comprises: The operation, said priority level; and a time window for performing said maneuver; Provided with information indicating A method comprising:

2. 2. The method of claim 1, wherein the request is transmitted wirelessly in accordance with a vehicle-to-everything (V2X) communications standard.

3. The method of claim 1 , wherein the priority level is based on a reason for the maneuver, a vehicle type of the first vehicle, or both.

4. receiving an acceptance message from a second vehicle or roadside unit (RSU) at the first vehicle, the second vehicle being determined to be affected by the maneuver based on a location and a speed of the second vehicle; executing the maneuver with the first vehicle in response to receiving the acceptance message; The method of claim 1 further comprising:

5. 1. A method for vehicle steering coordination, comprising: wirelessly receiving a first request to execute a maneuver from a first vehicle, wherein the first request comprises information indicative of the maneuver, a priority level, and a time window for executing the maneuver; determining whether to grant the first request based at least in part on the priority level of the first request; wirelessly sending a response indicating whether the first request was granted; and A method comprising:

6. receiving the first request, determining whether to grant the first request, and wirelessly sending the response are performed by a second vehicle; the second vehicle is a vehicle determined to be affected by the maneuver based on a location and a speed of the second vehicle. The method according to claim 5.

7. the second vehicle determining whether to grant the first request further based on a priority level of a second request received by the second vehicle from a third vehicle; the second request comprises information indicating a second maneuver to be performed by the third vehicle, a priority level corresponding to the second maneuver, and a time window for performing the second maneuver; the second vehicle is a vehicle determined to be affected by the second maneuver based on a location and a speed of the second vehicle; The method according to claim 6.

8. determining whether to grant the first request comprises determining to deny the first request based on a determination that the priority level of the second request is higher than the priority level of the first request; the response comprises information indicating a denial of the first request. The method according to claim 7.

9. determining whether to grant the first request comprises determining to accept the first request based on a determination that the priority level of the second request is lower than the priority level of the first request; the response comprises information indicating acceptance of the first request. The method according to claim 7.

10. A device comprising a communication interface, a memory and one or more processing units, the one or more processing units being communicatively coupled to the communication interface and the memory and configured to cause the device to perform a method according to any one of claims 1 to 9.

11. A device comprising means for carrying out the method according to any one of claims 1 to 9.

12. A non-transitory computer readable medium having embedded instructions that, when executed by one or more processing units, cause the one or more processing units to perform the method of any one of claims 1 to 9.

Citation Information

Patent Citations

  • Passage control system, point control device used for the same, and passage control method

    JP2012150630A

  • Control system and semiconductor device

    JP2016031586A

  • Driving support device of vehicle

    JP2016143137A

  • Vehicle control device

    JP2019199169A