Intersection-based off-board vehicle path generation

By deploying remote stations at intersections and using camera devices and sensor data to generate and update vehicle paths, the problem of inaccurate vehicle path prediction in the prior art is solved, accurate prediction and real-time update of vehicle paths are achieved, and intersections are improved safety and collision risk detection.

CN118985015APending Publication Date: 2024-11-19DENSO CORP
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
CN202380031614.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-31
Filing Date
2023-03-22
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

The prior art is difficult to accurately predict the path of a vehicle passing through an intersection, especially after the vehicle is parked, the traditional path prediction algorithm is inaccurate and the map message does not contain vehicle path information within the intersection, making it difficult to remind the driver of potential vehicles and pedestrians. risk of collision between the two.

Method used

By deploying remote stations at intersections, using camera devices and sensor data, the baseline static paths and dynamic paths of vehicles are generated and updated, and map messages are updated in real time based on road blocking information and vehicle motion data, and accurate vehicle path information is provided to provide accurate vehicle path information to Supports collision warning system.

Benefits of technology

Accurate prediction and real-time update of the paths of vehicles passing through intersections are achieved, the safety of intersections is improved, and the detection and early warning capabilities of vehicle-peer collision risks are enhanced.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118985015A_ABST
    Figure CN118985015A_ABST
Patent Text Reader

Abstract

A remote station includes a transceiver, a memory, and a control module. The memory is configured to store (i) a baseline static path of a vehicle moving through an intersection, and (ii) map data. The control module is configured to: obtain road congestion information; determining whether the road congestion information affects one or more of the baseline static paths of the vehicle through the intersection based on the baseline static paths and the map data, and updating the one or more baseline static paths based on the road congestion information; and broadcasting, via the transceiver, a map message indicating the updated one or more baseline static paths.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Non-Provisional Application No. 17 / 710,067, filed on March 31, 2022, the entire disclosure of which is incorporated herein by reference. Technical Field

[0003] The present disclosure relates to vehicle path tracking and broadcast systems. Background Art

[0004] The background description provided here is for the purpose of generally presenting the context of the present disclosure. It is neither explicitly nor implicitly admitted that the work of the presently named inventors, to the extent described in this background section, and aspects of the description that may not have been prior art at the time of filing, are prior art to the present disclosure.

[0005] Vehicle-to-everything (V2X) systems enable vehicle-to-vehicle (V2V) communications and vehicle-to-infrastructure (V2I) communications. In a V2X system, map messages including data indicating a vehicle's path on a road and between intersections may be transmitted. Map messages may be sent from a roadside unit (RSU) and received at a vehicle. Vehicles may utilize map data for positioning and navigation purposes and / or to avoid collisions with other vehicles and / or objects. Summary of the invention

[0006] This section provides a general summary of the disclosure, and is not a comprehensive disclosure of its full scope or all of its features.

[0007] A remote station is disclosed, which includes a transceiver, a memory, and a control module. The memory is configured to store (i) a baseline static path of a vehicle moving through an intersection and (ii) map data. The control module is configured to: obtain road blockage information; determine whether the road blockage information affects one or more baseline static paths of the vehicle through the intersection based on the baseline static path and the map data, and update the one or more baseline static paths based on the road blockage information; and broadcast a map message indicating the updated one or more baseline static paths via the transceiver.

[0008] In other features, the baseline static path is a predicted vehicle path from an entry lane to the intersection through the intersection to an exit lane from the intersection. In other features, the baseline static path includes two-dimensional or three-dimensional path information. In other features, the control module is configured to determine at a predetermined frequency whether the road obstruction information affects any of the baseline static paths.

[0009] In other features, the control module is configured to: determine a dynamic path based on at least one of a camera, other sensor data, or a basic safety message; compare the dynamic path to a baseline static path; and update the baseline static path based on the comparison between the dynamic path and the baseline static path. In other features, the dynamic path is an actual vehicle path from an entry lane to the intersection through the intersection to an exit lane from the intersection.

[0010] In other features, the road obstruction information includes at least one of lane closure information or road closure information. In other features, the road obstruction information includes accident information. In other features, the road obstruction information includes road maintenance information. In other features, the remote station is implemented as an intersection camera device, a traffic light, an RSU, a cloud-based server, a backend server, or an edge computing device.

[0011] In other features, the control module is configured to: connect to one or more intersection cameras; track the movement of vehicles through the intersection based on signals from the one or more intersection cameras; and update the baseline static path based on the tracked movement of the vehicle.

[0012] In other features, the transceiver communicates with one or more intersection cameras via an Ethernet connection, a Long Term Evolution connection, a fifth generation (5G) connection, or a Wireless Fidelity (Wi-Fi) connection.

[0013] In other features, the remote station further includes a camera configured to capture images of the intersection.The control module is configured to track movement of the vehicle through the intersection based on the captured images and update the baseline static path based on the tracked movement of the vehicle.

[0014] In other features, the control module is configured to: (i) connect to a cloud-based server, an edge computing device, or a backend server and collect captured images from one or more cameras at an intersection that tracks vehicles passing through the intersection; and (ii) update the baseline static path based on the movement of the tracked vehicles.

[0015] In other features, the control module is configured to: (i) receive captured images from a camera having a field of view covering at least a portion of an intersection; (ii) convert positions of objects in the intersection into three-dimensional global positioning system coordinates based on the captured images; and (iii) update the baseline static path based on the three-dimensional global positioning system coordinates.

[0016] In other features, the control module is configured to: tag data of the vehicle and track the path of the vehicle from an entry lane through an intersection to an exit lane; determine the speed and yaw rate of the vehicle through the intersection; calculate a three-dimensional vehicle position in the intersection and in multiple frames based on the tracked path of the vehicle and the speed and yaw rate of the vehicle; and update the baseline static path based on the three-dimensional vehicle position. In other features, the control module is configured to: receive basic safety messages from one or more vehicles; and update the baseline static path based on the basic safety messages.

[0017] In other features, the control module is configured to: receive data from one or more cameras having a field of view covering at least a portion of an intersection; fuse the data received from the one or more cameras with data in a basic safety message to provide an aggregate data set; and update a baseline static path based on the aggregate data set, including storing at least one of a node list or a curvature radius of a path for one or more vehicles through the intersection.

[0018] In other features, a remote station is disclosed that includes a transceiver, a memory, and a control module. The memory is configured to store a baseline static path and a dynamic path of a vehicle through an intersection, wherein the baseline static path refers to at least one of a previously predetermined path, an average path, or a historical path, and wherein the dynamic path refers to a currently detected path. The control module is configured to: (i) compare the dynamic path to the baseline static path; (ii) determine whether there is statistical significance between the dynamic path and the baseline static path; (iii) in response to the presence of statistical significance between the dynamic path and the baseline static path, broadcast a first map message indicating the dynamic path via the transceiver; and (iv) in response to the absence of statistical significance between the dynamic path and the baseline static path, broadcast a second map message indicating the baseline static path via the transceiver.

[0019] In other features, the control module is configured to average the trajectory of the vehicle to create a set of nodes or a turning radius to determine one of the dynamic paths. In other features, there is statistical significance between the dynamic path and the baseline static path when the difference between the dynamic path and the baseline static path is greater than a predetermined amount. In other features, there is statistical significance between the dynamic path and the baseline static path when at least a portion of the dynamic path deviates from the baseline static path by more than a predetermined amount. In other features, there is statistical significance between the dynamic path and the baseline static path when the average difference between the nodes of one of the dynamic paths and the nodes of one of the baseline static paths exceeds a predetermined amount. In other features, there is statistical significance between the dynamic path and the baseline static path when a predetermined percentage of the difference between the nodes of one of the dynamic paths and the nodes of one of the baseline static paths is greater than a predetermined percentage.

[0020] In other features, the control module is configured to adjust a window duration for tracking the vehicle to determine the dynamic path. In other features, the control module is configured to adjust a frequency at which the vehicle's trajectories are averaged to determine the average dynamic path, and broadcast the map message to include the average dynamic path when a difference between the average dynamic path and at least one of the baseline static paths is statistically significant.

[0021] In other features, the map message includes intersection box path data indicating a vehicle position in an intersection. In other features, the map message is a vehicle-to-everything type of map message.

[0022] In other features, the control module is configured to: obtain map data and road blockage information; determine whether the road blockage information affects one or more of the baseline static paths of the vehicle through the intersection based on the baseline static paths and the map data, and update the one or more baseline static paths based on the road blockage information; and broadcast a third map message indicating the updated one or more baseline static paths via the transceiver.

[0023] In other features, a remote station is disclosed that includes a transceiver, a memory, and a control module. The memory is configured to store first path data of a vehicle through an intersection. The control module is configured to: (i) receive at least one of road obstruction information or current vehicle path information; (ii) update the first path data based on at least one of the road obstruction information or the current vehicle path information; and (iii) broadcast a first map message including the updated first path data via the transceiver, the map message including a first data element, wherein the first data element defines a vehicle path through the intersection.

[0024] In other features, the map message is a vehicle-to-everything type map message. In other features, the first data element includes at least one of: (i) a radius of curvature of a path through the intersection, (ii) a node list of locations of the path through the intersection, (iii) latitude and longitude coordinates of a point along the path through the intersection.

[0025] In other features, the map message includes a generic lane frame including the second data element and connected to frames including a connection frame, and one of the connection frames includes an intersection path frame.

[0026] In other features, the second data element includes two or more of: (i) a frame identifier, (ii) a name, (iii) a lane attribute, (iv) an entry path, (v) an exit path, (vi) a maneuver, or (vii) a node list. In other features, the map message has a tree structure that includes: (i) a general lane frame at a first level of the tree structure, (ii) a second data element and a connection to frame at a second level of the tree structure, (iii) a connection frame at a third level of the tree structure, (iv) an intersection path frame at a fourth level of the tree structure, and (v) a first data element at a fifth level of the tree structure.

[0027] In other features, the first route data includes a baseline static route. The control module is configured to: (i) receive road blockage information; and (ii) update the first route data based on the road blockage information.

[0028] In other features, the road obstruction information includes at least one of lane closure information, road closure information, accident information, or road maintenance information.

[0029] In other features, the first path data includes a baseline static path and a dynamic path. The control module is configured to: (i) compare current vehicle path information to the baseline static path; (ii) determine whether there is a statistical significance between the current vehicle path information and the baseline static path; (iii) in response to the statistical significance between the current vehicle path information and the baseline static path, broadcast a first map message indicating the current vehicle path information via the transceiver; (iv) in response to the absence of statistical significance between the current vehicle path information and the baseline static path, broadcast a second map message indicating the baseline static path via the transceiver.

[0030] In other features, a remote station is provided, which includes a transceiver, a memory, and a control module. The memory is configured to store first path data of a vehicle through an intersection. The control module is configured to: (i) receive at least one of road obstruction information or current vehicle path information; (ii) update the first path data based on at least one of the road obstruction information or the current vehicle path information; and (iii) broadcast a map message including the updated first path data via the transceiver, wherein the map message includes: (i) a connection frame including an intersection path frame identifier connector to an intersection path frame in the map message, and (ii) an intersection path frame including a first data element, the first data element defining a vehicle path through the intersection.

[0031] In other features, the map message is a vehicle-to-everything type map message. In other features, the first data element includes at least one of: (i) a radius of curvature of a path through the intersection; (ii) a node list of locations of the path through the intersection; (iii) latitude and longitude coordinates of a point along the path through the intersection.

[0032] In other features, the map message includes a generic lane frame, the generic lane frame including the second data element and a connection to a frame, the connection to the frame including a connection frame, and one of the connection frames includes an intersection path frame identifier connector. In other features, the intersection path frame identifier connector refers to an intersection path frame, the intersection path frame is one of a plurality of frames of the generic lane frame.

[0033] In other features, the map message has a tree structure that includes: (i) a general lane frame at a first level of the tree structure, (ii) a second data element, a connection frame and an intersection path frame at a second level of the tree structure, (iii) a connection frame at a third level of the tree structure, and (iv) an intersection path frame identifier and a first data element separated from the intersection path frame identifier at a fourth level of the tree structure.

[0034] In other features, the second plurality of data elements includes two or more of: (i) a frame identifier, (ii) a name, (iii) a lane attribute, (iv) an entry path, (v) an exit path, (vi) a maneuver, or (vii) a node list. In other features, the first path data includes a baseline static path. The control module is configured to: (i) receive road blockage information; and (ii) update the first path data based on the road blockage information. In other features, the road blockage information includes at least one of lane closure information, road closure information, accident information, or road maintenance information.

[0035] In other features, the first path data includes a baseline static path and a dynamic path. The control module is configured to: (i) compare current vehicle path information to the baseline static path; (ii) determine whether there is a statistical significance between the current vehicle path information and the baseline static path; (iii) in response to the statistical significance between the current vehicle path information and the baseline static path, broadcast a first map message indicating the current vehicle path information via the transceiver; (iv) in response to the absence of statistical significance between the current vehicle path information and the baseline static path, broadcast a second map message indicating the baseline static path via the transceiver.

[0036] In other features, a path prediction system is disclosed that includes a transceiver, a memory, and a control module. The transceiver is configured to receive a map message at a host vehicle, the map message including path information of the vehicle through an intersection. The memory is configured to store map data including global navigation satellite system information. The control module is configured to: (i) determine whether the host vehicle is approaching, at, or in an intersection based on the map data, (ii) in response to determining that the host vehicle is approaching, at, or in an intersection, predict a path of the host vehicle through the intersection based on the path information, and (iii) perform at least one collision warning operation based on the predicted path of the host vehicle.

[0037] In other features, the control module is configured to predict a path of the host vehicle based on at least one of: a node list or a curvature radius of the vehicle path through the intersection and a latitude and longitude of a center point of the curvature radius. The map message includes at least one of the node list or the curvature radius of the vehicle path through the intersection.

[0038] In other features, the control module is configured to predict the path independently of the speed of the host vehicle and the yaw rate of the host vehicle. In other features, the control module is configured to (i) obtain at least one of a vehicle speed or a yaw rate of a vehicle in the intersection, and (ii) predict the path of the host vehicle based on at least one of the vehicle speed or the yaw rate of the host vehicle in the intersection.

[0039] In other features, the control module is configured to perform at least one of a forward collision warning operation or a pedestrian collision warning operation based on the predicted path of the host vehicle. In other features, the control module is configured to determine a location of the host vehicle based on global navigation satellite system information, generate a basic safety message indicating the location of the host vehicle, and send the basic safety message.

[0040] In other features, the control module is configured to: (i) determine whether map data for the host vehicle includes at least one of a list of nodes or a radius of curvature for a vehicle path through an intersection; and (ii) in response to the map data including at least one of a list of nodes or a radius of curvature for a vehicle path through an intersection, use the map data to predict a path of the host vehicle.

[0041] In other features, the control module is configured to: in response to the map data not including at least one of a node list or a radius of curvature for a vehicle path through an intersection, predict a path of the host vehicle based on at least one of a speed or a yaw rate of the host vehicle.

[0042] In other features, the control module is configured to generate the basic safety message based on the predicted path of the host vehicle in response to the map data including at least one of a node list or a radius of curvature of a vehicle path through an intersection.

[0043] In other features, the control module is configured to: (i) determine whether the host vehicle has left the intersection; and (ii) in response to the host vehicle having left the intersection, transition from predicting a path of the host vehicle based on map data to predicting a path of the host vehicle based on at least one of a speed or a yaw rate of the host vehicle. In other features, the map message is received from a roadside unit that is monitoring the intersection.

[0044] In other features, a path prediction system is disclosed, which includes a transceiver, a memory, and a control module. The transceiver is configured to receive a map message at a host vehicle, the map message including path information of the vehicle through an intersection. The memory is configured to store map data including global navigation satellite system information. The control module is configured to: (i) determine whether the host vehicle is approaching, at, or in an intersection based on the map data; (ii) in response to determining that the host vehicle is approaching, at, or in an intersection, predict the path of the host vehicle through the intersection based on the path information; and (iii) determine the location of the host vehicle based on the predicted path of the host vehicle, generate a basic safety message indicating the location of the host vehicle, and send the basic safety message.

[0045] In other features, the control module is configured to predict a path of the host vehicle based on at least one of a node list or a radius of curvature of the vehicle path through the intersection. The map message includes at least one of the node list or the radius of curvature of the vehicle path through the intersection.

[0046] In other features, the control module is configured to predict the path independently of the speed of the host vehicle and the yaw rate of the host vehicle. In other features, the control module is configured to: (i) obtain at least one of a vehicle speed or a yaw rate of a vehicle in the intersection; and (ii) predict the path of the host vehicle based on at least one of the vehicle speed or the yaw rate of the host vehicle in the intersection.

[0047] In other features, the control module is configured to perform at least one of a forward collision warning operation or a pedestrian collision warning operation based on the predicted path of the host vehicle. In other features, the control module is configured to: (i) determine whether map data for the host vehicle includes at least one of a node list or a radius of curvature for a vehicle path through an intersection; and (ii) in response to the map data including at least one of a node list or a radius of curvature for a vehicle path through an intersection, use the map data to predict the path of the host vehicle. In other features, the control module is configured to: in response to the map data not including at least one of a node list or a radius of curvature for a vehicle path through an intersection, predict the path of the host vehicle based on at least one of a speed or a yaw rate of the host vehicle.

[0048] In other features, the control module is configured to: (i) determine whether the host vehicle has left the intersection; and (ii) in response to the host vehicle having left the intersection, transition from predicting a path of the host vehicle based on map data to predicting a path of the host vehicle based on at least one of a speed or a yaw rate of the host vehicle. In other features, the map message is received from a roadside unit that is monitoring the intersection.

[0049] In other features, a pedestrian collision warning system is disclosed, the pedestrian collision warning system comprising a transceiver, a memory, and a control module. The transceiver is configured to receive a personal safety message and a map message at a host vehicle. The memory is configured to store map data. The control module is configured to: (i) determine a possible conflict box in which the host vehicle and the pedestrian are predicted to be simultaneously located according to the path of the host vehicle based on the personal safety message and the map message; (ii) determine a most likely path for the host vehicle to pass through the intersection from possible paths through the intersection based on the map data and the map message; (iii) determine whether the host vehicle and the pedestrian will be simultaneously located in one of the possible conflict boxes based on the most likely path of the host vehicle and the possible conflict box; and (iv) in response to determining that the host vehicle and the pedestrian will be simultaneously located in one of the possible conflict boxes, warn at least one of the occupants of the host vehicle or the pedestrian of a potential collision via a vulnerable road user device.

[0050] In other features, the personal safety message is received from a roadside unit that is separate from a host vehicle, the roadside unit being separate from a pedestrian collision warning system implemented at the host vehicle. In other features, the personal safety message is received from a vulnerable road user device that is separate from the host vehicle, the vulnerable road user device being separate from the pedestrian collision warning system implemented at the host vehicle. In other features, the map message is received from a roadside unit that is monitoring an intersection. In other features, the map message is received from a cloud-based server.

[0051] In other features, the control module is configured to: (i) determine whether the host vehicle is moving; and (ii) when the host vehicle is not moving, determine a possible conflict box in which the host vehicle and the pedestrian are predicted to be simultaneously located based on the path of the host vehicle. In other features, the control module is configured to: (i) determine whether the host vehicle begins to move; and (ii) in response to the host vehicle beginning to move, determine the most likely path for the host vehicle to pass through the intersection, and determine whether the host vehicle and the pedestrian will be simultaneously located in one of the possible conflict boxes.

[0052] In other features, the control module is configured to: (i) determine whether the host vehicle begins to move; and (ii) in response to the host vehicle beginning to move, determine a most likely path for the host vehicle to pass through the intersection, and determine whether the host vehicle and the pedestrian will be in one of the possible conflict boxes at the same time. In other features, the control module is configured to: (i) determine whether the host vehicle is approaching the intersection; and (ii) in response to the host vehicle being approaching the intersection, determine the possible conflict box.

[0053] In other features, a pedestrian collision warning method is disclosed, the method comprising: receiving a personal safety message and a map message at a host vehicle; obtaining map data from a memory; determining, based on the personal safety message and the map message, a possible conflict box in which the host vehicle and the pedestrian are predicted to be simultaneously located according to a path of the host vehicle; determining, based on the map data and the map message, a most likely path for the host vehicle to pass through an intersection from possible paths through the intersection; determining, based on the most likely path of the host vehicle and the possible conflict boxes, whether the host vehicle and the pedestrian will be simultaneously located in one of the possible conflict boxes; and in response to determining that the host vehicle and the pedestrian will be simultaneously located in one of the possible conflict boxes, warning at least one of an occupant of the host vehicle or a pedestrian of a potential collision via a vulnerable road user device.

[0054] In other features, the personal safety message is received from a roadside unit that is separate from the host vehicle, the roadside unit being separate from a pedestrian collision warning system implemented at the host vehicle. In other features, the personal safety message is received from a vulnerable road user device that is separate from the host vehicle, the vulnerable road user device being separate from a pedestrian collision warning system implemented at the host vehicle.

[0055] In other features, the map message is received from a roadside unit that is monitoring the intersection. In other features, the map message is received from a cloud-based server. In other features, the pedestrian collision warning method further includes: determining whether the host vehicle is moving; and when the host vehicle is not moving, determining a possible collision box in which the host vehicle and the pedestrian are predicted to be simultaneously located based on the path of the host vehicle.

[0056] In other features, the pedestrian collision warning method further includes: determining whether the host vehicle begins to move; and in response to the host vehicle beginning to move, determining the most likely path of the host vehicle through the intersection, and determining whether the host vehicle and the pedestrian will be in one of the possible conflict boxes at the same time. In other features, the pedestrian collision warning method further includes: determining whether the host vehicle begins to move; and in response to the host vehicle beginning to move, determining the most likely path of the host vehicle through the intersection, and determining whether the host vehicle and the pedestrian will be in one of the possible conflict boxes at the same time. In other features, the pedestrian collision warning method further includes: determining whether the host vehicle is approaching the intersection; and in response to the host vehicle being approaching the intersection, determining the possible conflict box.

[0057] Further areas of applicability will become apparent from the description provided herein.The description and specific examples in this summary are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] The accompanying drawings, which are incorporated into and constitute a part of the specification, illustrate various systems, methods and other embodiments of the present disclosure. It will be understood that the element boundaries (e.g., boxes, box groups or other shapes) shown in the figures represent one embodiment of the boundaries. In some embodiments, the elements may not be drawn to scale.

[0059] [ Figure 1 ] Figure 1 is a functional block diagram of an exemplary intersection-based vehicle path monitoring and response system (IVPMRS) according to the present disclosure.

[0060] [ Figure 2 ] Figure 2 yes Figure 1 Functional block diagram of a part of the IVPMRS.

[0061] [ Figure 3 ] Figure 3 According to the present disclosure, a method including an intersection path prediction module is provided. Figure 1 Functional block diagram of an example vehicle of the IVPMRS.

[0062] [ Figure 4 ] Figure 4 According to the content of this disclosure Figure 1Functional block diagram of an example remote station of the IVPMRS.

[0063] [ Figure 5 ] Figure 5 is a top view of an example intersection according to the present disclosure, illustrating an example set of nodes for possible paths for a vehicle through the intersection from a single turn lane to two exit lanes.

[0064] [ Figure 6 ] Figure 6 is a top view of an example intersection according to the present disclosure, illustrating an example set of nodes for possible paths for a vehicle through the intersection from two turn lanes to two exit lanes.

[0065] [ Figure 7 ] Figure 7 is a top view of an example intersection showing an example set of nodes for possible paths for a vehicle through the intersection from two turn lanes to a single exit lane due to lane obstruction in accordance with the present disclosure.

[0066] [ Figure 8 ] Figure 8 An example method for a remote station to update a baseline static path according to the present disclosure is shown.

[0067] [ Fig. 9 ] Fig. 9 is a top view of an example intersection showing a roadside unit (RSU) monitoring the path of a vehicle from a single turn lane through the intersection to two exit lanes in accordance with the present disclosure.

[0068] [ Fig.10 ] Fig.10 is a top view of an example intersection showing RSUs at nodes monitoring different paths of vehicles through the intersection from a single turn lane to two exit lanes in accordance with the present disclosure.

[0069] [ Fig.11 ] Fig.11 is a top view of an example intersection according to the present disclosure showing similar example static and dynamic paths of vehicles through the intersection from two turn lanes to two exit lanes.

[0070] [ Fig.12 ] Fig.12 is a top view of an example intersection according to the present disclosure showing different example static and dynamic paths of vehicles through the intersection from two turn lanes to two exit lanes.

[0071] [ Fig.13 ] Fig.13 An example method of determining whether to broadcast a static path or a dynamic path according to the present disclosure is shown.

[0072] [ Fig.14 ] Fig.14 is a top view of an example intersection showing example nodes of a vehicle's path through the intersection from two turn lanes to two exit lanes including example radii of curvature in accordance with the present disclosure.

[0073] [ Fig.15 ] Fig.15 is a block diagram of an example representation of a tree structure of a map message according to the present disclosure.

[0074] [ Fig.16 ] Fig.16 is a block diagram of an example representation of a tree structure of a map message including level jumpers in the form of intersection box path frame identifiers in accordance with the present disclosure.

[0075] [ Fig.17 ] Fig.17 is a top view of an example intersection according to the present disclosure, illustrating an example predicted first node of a vehicle determined based on available intersection path information from a map message and an example predicted second node of the vehicle determined without intersection path information provided via a map message.

[0076] [ Fig.18 ] Fig.18 A method of providing intersection-based path prediction and providing collision warning and basic safety message transmission based on the path prediction according to the present disclosure is shown.

[0077] [ Fig.19 ] Fig.19 is a top view of an example intersection according to the contents of the present disclosure, which shows an example first predicted path based on map message intersection path information provided via a map message, an example second predicted path based on vehicle speed and yaw rate, an example actual vehicle path, and an example corresponding curvature radius.

[0078] [ Fig. 20 ] Fig. 20 is a top view of an example intersection showing predicted paths of vehicles and conflict boxes in accordance with the present disclosure.

[0079] [ Fig.21 ] Fig.21 An example method for performing pedestrian collision warning based on intersection path information of a map message according to the present disclosure is shown.

[0080] Corresponding reference numerals indicate corresponding parts throughout the several views of the drawings. DETAILED DESCRIPTION

[0081] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0082] A large proportion (e.g. 40%) of traffic accidents occur in intersections. V2X communications can be used to improve the safety of intersections and include V2I and V2V applications, such as red light running warning (RLVW) applications and intersection mobility assistance (IMA) applications. V2X communications are also used to detect collision threats to vulnerable road users (VRUs) such as pedestrians, cyclists, etc. It can be difficult to alert drivers to a potential collision between a VRU in a crosswalk and a vehicle because conventional collision warning systems cannot accurately predict the path of a vehicle through an intersection, especially after stopping. This is due to two main factors. The first factor involves conventional vehicle path prediction algorithms, which are typically inaccurate unless the vehicle's turning radius is constant. The second factor is that map messages traditionally do not include information about potential vehicle paths within an intersection.

[0083] The example set forth herein includes a system for accurately predicting the path of a vehicle through an intersection. An intersection refers to an area (or frame) between an entrance lane and an exit lane, and typically includes one or more traffic lights. Traffic from different directions enters and leaves an intersection. An entrance lane extends to (or leads to) an intersection, and an exit lane extends (or leaves an intersection) from an intersection. An intersection is a point of intersection where two or more roads meet, fork, meet or cross at the same height. The example of a typical intersection includes an area where two orthogonal roads intersect. In this example, the geographic area where two roads intersect is referred to as an intersection frame, and may include a crosswalk. The peripheral edge of the frame may be at least partially defined by a white stop line, and a vehicle should stop behind the white stop line when waiting for a green light indicating that the vehicle is allowed to pass through an intersection. Figures 5 to 7 , Figures 9 to 12 , Fig.14 , Fig.17 , Fig.19 and Fig. 20 Examples of intersections, crosswalks, and white stop lines are shown.

[0084] These examples also include generating and sending map messages that include vehicle path information, and performing various operations based on the vehicle path information. The vehicle path information includes a baseline static path (also referred to as a static path) and a dynamic path of the vehicle. The static path of a vehicle through an intersection refers to a predicted or ideal vehicle path based on predetermined and / or historical vehicle paths through the intersection and map information that defines the intersection. The static path extends from an entry lane to the intersection to an exit lane leaving the intersection. The dynamic path refers to the current actual path of the vehicle moving through the intersection. The dynamic path also refers to a path extending from an entry lane to the intersection to an exit lane leaving the intersection. The static path and dynamic path information may include two-dimensional (2D) and / or three-dimensional (3D) path information.

[0085] Example embodiments will now be described more fully with reference to the accompanying drawings.

[0086] Figure 1 An IVPMRS 100 is shown, which may include a connected vehicle 102, a non-connected vehicle 104, a distributed network 106, a cloud-based (or back-end) server 108, an RSU 110, and a VRU device 112. Each of the connected vehicles 102 is configured to connect to and communicate with other network devices in the IVPMRS 100. Each of the non-connected vehicles 104 is not configured to connect to and communicate with other network devices. Each of the connected vehicles 102 may include a control module 120, which includes a path prediction module 122, a pedestrian collision warning (PCW) module 124, and a vehicle forward collision warning (FCW) module 126. The path prediction module 122 can predict the path of the connected vehicle 102 through the intersection, the path of other nearby vehicles through the intersection, and / or the path of an object (e.g., VRU) through the intersection. These predictions may be based on map messages received from: (i) one or more remote stations, such as one or more of the cloud-based servers 108, the RSUs 110, and / or other remote stations disclosed herein, and / or (ii) messages broadcast by other connected vehicles 102 or VRU devices 112. A remote station may refer to a device that is separate from the connected vehicle 102, communicates with the connected vehicle 102, broadcasts messages to the connected vehicle 102, and / or receives information from the connected vehicle 102. The modules 124, 126 and / or other collision warning modules of the connected vehicle 102 may perform collision warning operations to prevent collisions between the connected vehicle 102 and objects, such as pedestrians, VRUs, vehicles, and / or other objects including the vehicles 102, 104.

[0087] The cloud-based server 108, RSU 110 and / or other remote stations can generate a map message including map information and intersection path information. Other remote stations may include backend servers, edge computing devices, and / or roadside or overhead equipment (e.g., cameras, traffic lights, RSUs, etc.). The intersection path information may include a static path, which includes: nodes of the vehicle's position along the path between the entrance lane and the exit lane; a linear trajectory between the entrance lane and the exit lane; and / or a rotation center with a radius of curvature of a curved trajectory of a path from a turn lane to an exit lane. A turn lane may be referred to as an entrance lane, and other non-turn entrance lanes may also be referred to as an entrance lane. Turn lanes may include left-turn lanes and right-turn lanes. The path through an intersection may be linear, non-linear, and / or curved.

[0088] In the example shown, the cloud-based server 108 and the RSU 110 may include respective control modules (e.g., control modules 130, 132) including intersection path modules (e.g., intersection path modules 134, 136) and V2X map message modules (e.g., V2X map message modules 138, 140). The intersection path module is configured to track, store and / or predict the paths of connected vehicles and non-connected vehicles and / or other objects (e.g., VRUs) through intersections. This may be based on past / historical paths of vehicles and objects through intersections, road congestion information, map information, the number and type of entry and exit lanes, etc. The road congestion information may include accident information, road maintenance information, traffic congestion information, road closure information, lane closure information, etc. The road congestion information may indicate which lanes are closed, which lanes are open, and / or which lanes are temporarily blocked and / or include non-moving traffic. The V2X map message module may generate a map message including the path information, which may be broadcast to the connected vehicles 102 and / or VRU devices 112. The V2X communications mentioned herein include the transmission of map messages and other messages such as basic safety messages and personal safety messages. These messages can be transmitted in the 5.9 Gigahertz (GHz) frequency band.

[0089] The VRU device 112 can be respectively in the VRU ( Figure 1106). The VRU device 112 may include a mobile phone, a tablet computer, a wearable network device (e.g., a smart watch), etc. The VRU may include pedestrians, cyclists, etc. The VRU device 112 may communicate with the connected vehicle 102, the cloud-based server 108, and / or the RSU 110 and / or receive messages from the connected vehicle 102, the cloud-based server 108, and / or the RSU 110. Such communication and reception of messages may be direct or indirect via the distributed network 106. Similarly, the connected vehicle 102 may communicate with the cloud-based server 108, the RSU 110, and / or the VRU device 112 and / or receive messages from the cloud-based server 108, the RSU 110, and / or the VRU device 112. Such communication and reception of messages may be direct or indirect via the distributed network 106.

[0090] Figure 2 An RSU 202, a connected vehicle 204, and a VRU device 206 are shown, which may be Figure 1 The RSU 202 may include a control module 210, a transceiver 212, and a memory 214, the memory 214 storing an intersection path application 216 and a V2X message application 218. The connected vehicle 204 includes a control module 220, a transceiver 222, and a memory 224, the memory 224 storing a path prediction application 226, a PCW application 228, a basic safety message (BSM) application 230, and a FCW application 232. The VRU device 206 may include a control module 240, a transceiver 242, and a memory 244, the memory 244 storing a PSM application 246 and a collision warning application 248.

[0091] Applications 216, 218, 226, 228, 230, 232, 246, 248 may be executed by control modules 210, 220, 240. Intersection path application 216 is implemented to track, store, and predict paths of connected and non-connected vehicles and / or other objects through intersections. Path prediction application 226 is implemented to predict the path of connected vehicle 204 through intersections, the paths of other nearby vehicles through intersections, and / or the paths of objects (e.g., VRUs) through intersections. V2X message application 218 is implemented as a map message including path information that can be broadcast to connected vehicles 204 and / or VRU devices 206.

[0092] The applications 228, 232 are implemented to perform collision warning operations to prevent collisions between the connected vehicle 102 and objects such as pedestrians, VRUs, vehicles, and / or other objects. The BSM application 230 is implemented to generate and broadcast BSM messages indicating, for example, the speed, heading, and position of the connected vehicle 204. The PSM application 246 is implemented to generate and broadcast PSM messages indicating, for example, the speed, heading, and position of the VRU device 206 and / or corresponding VRUs. The collision warning application 248 can perform collision warning operations to prevent collisions between the VRUs of the VRU device 206 and objects such as vehicles, pedestrians, VRUs, and / or other objects.

[0093] Figure 3 Shows that it can replace Figure 1 One of the connected vehicles 102 of the IVPMRS 100 is a vehicle 300. The vehicle 300 may be a fully or partially autonomous vehicle and includes a sensor system 302, a map module 304, and a vehicle control module 305, which may include a path prediction module 306, a collision warning module 307, an actuator module 308, and a parameter adjustment module 309. The sensor system 302 provides information about the vehicle 300, such as speed and yaw rate.

[0094] The path prediction module 306 can be used with Figure 1 and Figure 2 The path prediction modules 122 and 226 are similarly executed and can be implemented Figure 2 Path prediction application 226. Path prediction module 306 is configured to determine a trajectory that vehicle 300 will follow through the intersection and that is within the geometric constraints of the intersection and / or entry and exit lanes leading to and leaving the intersection. The path prediction performed by path prediction module 306 may not ensure that the trajectory is collision-free. Other collision avoidance modules use path prediction to predict the likelihood of a collision or whether the corresponding host vehicle is within specified lane parameters and / or meets one or more other parameters. Collision warning module 307 may be used with Figure 1 The collision warning modules 124, 126 are similarly executed and can be implemented Figure 2 Collision warning applications 228, 232. When the vehicle 300 is an autonomous or partially autonomous vehicle, the actuator module 308 can be configured to control the operation of the vehicle or a portion thereof to follow the planned trajectory of the vehicle 300. When the vehicle 300 is a non-autonomous vehicle (or a vehicle completely controlled by the driver), the actuator module 308 or other modules can provide instructions to the driver to follow the planned trajectory. The planned trajectory can be determined by one or more modules in modules 305 to 307.

[0095] Sensor system 302 provides dynamic information, such as the speed and yaw rate of the host vehicle. This information is provided to modules 305 to 307. The map generated, obtained and / or monitored by map module 304 contains the geometry and features of the surrounding area in a format that allows modules 305 to 308 to determine where there are available (permissible and feasible) driving areas and lanes. Available driving areas and lanes can be inside and outside intersections, emergency driving areas, impassable areas, and other semantic categories of the local road configuration.

[0096] Actuator module 308 may take the plan generated by modules 305-307 and convert the plan into wheel, brake, and accelerator commands to affect the speed, acceleration, and heading of host vehicle 300. Map and object (or obstacle) information may be used to determine an optimal trajectory for host vehicle 300 that satisfies target conditions (e.g., exiting an entry lane into an intersection, following a particular path through the intersection, and entering a particular exit lane from the intersection).

[0097] The vehicle 300 also includes an infotainment module 312 and other control modules 314 (e.g., a body control module). The modules 305 to 309, 312, and / or 314 can communicate with each other via a vehicle interface 316, such as a controller area network (CAN) bus, a local interconnect network (LIN), a clock extension peripheral interface (CXPI) bus, and / or other vehicle interfaces. In an embodiment, the sensor signal is received from the sensor system 302 at the vehicle control module 305 via the CAN bus.

[0098] The vehicle control module 305 can control the operation of the vehicle system and can include modules 305, 306, 308, 309, and other modules. The vehicle control module 305 can also include one or more processors configured to execute instructions stored in a non-transitory computer-readable medium such as memory 322, which can include read-only memory (ROM) and / or random access memory (RAM).

[0099] The vehicle 300 may also include: a display 330; an audio system 331; and one or more transceivers 332 including an antenna module 334. The RF antenna module 334 may include and / or be connected to an RF circuit 336. The map module 304 may communicate with a telematics module 338, a global positioning system (GPS) receiver 340, and a sensor 342. The one or more transceivers 332 may include a telematics module 338. The vehicle control module 305 and / or the telematics module 338 are configured to receive GPS data and associate the GPS location data of the vehicle 300 with a geographic map location.

[0100] The RF circuit 336 can be used to communicate with mobile devices, central offices, other vehicles, land base stations, cloud-based networks, etc., including Bluetooth (registered trademark), wireless fidelity (Wi-Fi) or Wi-Fi direct connection and / or other RF signal transmission that meet various wireless communication protocols. The RF circuit 336 may include a radio, a transmitter, a receiver, etc. for transmitting and receiving RF signals. The telematics module 338 can be implemented by a global navigation satellite system (e.g., GPS), an inertial navigation system, a global mobile communication system (GSM), and / or other positioning systems. The telematics module 338 can provide map information, which includes road and object information, such as: the vehicle's location, speed, acceleration, heading; the location of objects; the distance between objects; the distance between the current location and the intermediate and / or target destination; and so on. This information can be provided to the map module 304.

[0101] Sensors 342 may include sensors for path prediction and planning and actuator operation. Sensors may include a vehicle speed sensor 343, a yaw rate sensor 344, and other sensors 345, such as cameras, object detection sensors, temperature sensors, accelerometers, etc. GPS receiver 340 may provide vehicle speed and / or direction (or heading) and / or global clock timing information of vehicle 300.

[0102] The memory 322 may store various sensor data, parameter data, size status, trajectory planning information, and other information. As an example, the memory 322 may store sensor and parameter data 350, PCW application 352, BSM application 354, FCW application 356, path prediction application 358, timing information 360, connection information 362, and other applications 364. The connection information 362 may refer to information for connecting to other vehicles, mobile access devices, cloud-based servers, back-end servers, remote stations, etc. The timing information 360 may relate to the time when the vehicle 300 is at a specific location, the time to arrive at a predicted destination (or node), etc. The transition may be based on time, based on the distance traveled, and / or other conditions.

[0103] Applications 352, 354, 356, 358, 364 can be implemented by modules 305 to 309, 312, 314 and 338 and / or transceiver 332. Other applications 364 may include, for example, planning applications and actuator applications. The planning application can be executed by the planning module to plan the trajectory of the vehicle 300. The actuator application can be executed by the actuator module 308 to implement the trajectory plan selected by the planning module. The planning module can determine the target path for the vehicle 300 to follow. The target path can be adjusted based on the changing environment. For example, the vehicle 300 may approach or encounter one or more objects such as fixed objects, pedestrians and / or other vehicles, and update the target path. If the vehicle 300 is an autonomous vehicle, the vehicle 300 can follow the updated target path to avoid collisions. The parameter adjustment module 309 can be used to adjust the parameters of the vehicle 300.

[0104] Although the memory 322 and the vehicle control module 305 are shown as separate devices, the memory 322 and the vehicle control module 305 may be implemented as a single device.

[0105] The vehicle control module 305 can control the operation of the engine or motor 370, converter / generator 372, transmission 374, window / door system 380, lighting system 382, ​​seat system 384, mirror system 386, braking system 388, electric motor 390 and / or steering system 392 according to parameters set by modules 305 to 309, 334 and / or 338.

[0106] The vehicle control module 305 can receive power from a power source 394, which can be provided to an engine or motor 370, a converter / generator 372, a transmission 374, a window / door system 380, a lighting system 382, ​​a seat system 384, a mirror system 386, a brake system 388, an electric motor 390, and / or a steering system 392, among others. As a result of the plan, some operations may include starting fuel and spark for the engine or motor 370, starting the electric motor 390, powering any of the systems mentioned herein, and / or performing other operations further described herein. In one embodiment, the vehicle 300 does not include an engine and / or a transmission, and the electric motor 390 is used for vehicle propulsion and / or drive purposes.

[0107] The engine or motor 370 , converter / generator 372 , transmission 374 , window / door system 380 , lighting system 382 , seat system 384 , mirror system 386 , brake system 388 , motor 390 , and / or steering system 392 may include actuators controlled by the vehicle control module 305 to, for example, adjust fuel, spark, airflow, steering wheel angle, throttle position, pedal position, door locks, window position, seat angle, etc. This control may be based on the output of the sensors 342 , the map module 304 , the GPS receiver 340 , and the above data and information stored in the memory 322 .

[0108] Figure 4 A remote station 400 is shown, which may replace Figure 1 The cloud-based server 108, one of the RSUs 110 and / or other remote stations and / or Figure 1 The cloud-based server 108, one of the RSUs 110, and / or other remote stations may operate similarly, and / or at Figure 1 The remote station 400 may be implemented as a backend server, a cloud-based server, a central office monitoring station, an RSU, a roadside camera (or other sensing device or system), a traffic light, an edge computing device, or other remotely located station separated from the vehicle. The remote station 400 may include a control module 402, a transceiver 404, and a memory 406, which may store an intersection path application 408 and a V2X map message application 410. Applications 408 and 410 may be used with Figure 2 The applications 216, 218 of the remote station 400 are similarly configured. When the remote station 400 is implemented as an RSU, it may include a camera 412 for capturing images of the intersection. The camera 412 may be replaced by or used in combination with one or more other sensors (e.g., a lidar sensor or a radar sensor). This applies to other intersection camera devices mentioned herein.

[0109] Intersection path information generation

[0110] The following Figures 5 to 13 Relates to the generation of valid intersection path information associated with a vehicle's path through an intersection (or intersection box). An intersection box may refer to a box defined at least in part by, for example, white stop lines printed across an entry lane to an intersection. The white stop lines may define at least a portion of an outer edge of the intersection box. The valid intersection path information may be based on intersection lane and road geometry and other existing map information.

[0111] Figure 5An intersection 500 is shown showing a node set of possible paths for a vehicle through the intersection 500 from a single left turn lane 506 to two exit lanes 507, shown by dashed arrows. The intersection 500 includes a stop line 502. Conventional static map information only includes vehicle path information for lanes leading to the stop line 502, such as provided by the solid arrows shown, and path information associated with lanes leaving the intersection 500. The solid arrow pointing to the intersection 500 is on the entrance lane. The solid arrow leaving the intersection 500 is on the exit lane. The solid arrow has an associated node set.

[0112] Conventional static map information does not include any vehicle path information for vehicle paths within the intersection 500. The intersection path module disclosed herein can generate static path information for vehicle paths through the intersection. The static path information may include node information, such as longitude and latitude points (or X, Y coordinates) along the vehicle path, as shown in node box (or node) 510. Node 510 is associated with a pair of available paths, and there are other nodes for other available paths through the intersection 500. Each available path through the intersection 500 can have a corresponding node set (or node list).

[0113] Intersection path information may be obtained using a variety of techniques, such as: collecting information from manual mapping performed by surveyors; monitoring vehicle paths via intersection cameras that capture images of the intersection to track the paths of vehicles through intersection 500; collecting information from connected vehicles indicating the locations of connected vehicles; collecting information from a map database; and collecting information from portable and / or handheld sensors to track the locations of vehicles passing through intersection 500. A set of intersection nodes may be generated, stored, and / or averaged for use in predicting the paths of vehicles through intersection 500. Path information may include information about available and allowable (or valid) paths for a vehicle. Path information may not include unavailable and / or invalid paths for a vehicle. Figure 5 , examples of two available and valid paths are shown for the left turn lane 506 .

[0114] Figure 6 An intersection 600 is shown, which shows a node set of available and effective paths (referred to as possible paths) for a vehicle to pass through the intersection 600 from two left turn lanes 602 to two exit lanes 604, respectively. Possible paths, which may be referred to as static paths, are shown by dashed arrows with corresponding nodes 606. In the example shown, the static paths are ideal curved paths that may each have a specific radius of curvature. Although in Figure 6 Only two possible paths are shown, but static path information for each possible path through intersection 600 may be tracked, determined, and stored. Figure 6is an example when there is no lane obstruction. Each static path has a corresponding node list including node coordinates, which can be stored in a memory and / or broadcast to the vehicle from a remote station (eg, any of the remote stations mentioned herein).

[0115] Figure 7 An intersection 700 is shown, which shows a set of nodes showing possible paths for a vehicle from two left turn lanes 702 through the intersection 700 to a single exit lane 704 due to lane obstruction. The intersection 700 may be a Figure 6 706 is the same intersection as intersection 600 of FIG. 708. In this example, one exit lane is closed. Exit lane 706 is blocked, as indicated by 'X' 708, which may indicate an accident in exit lane 706, debris, lane 706 having a closure bracket and / or roadblock, or other road obstruction. Planned lane closures and obstructions are taken into account when determining and updating static path information for the vehicle path through the intersection and the node list including node 710. Road obstruction information may be received at the vehicle from a central office, backend server, reporting agent, edge computing device, RSU, or other remote station. When the closure of exit lane 706 ends, the static path information may be restored to be similar to that for Figure 6 Provides static path information for static path information.

[0116] although Figure 8 , Fig.13 , Fig.18 and Fig.21 The following methods are shown as separate methods, but two or more of the methods and / or operations from different methods may be combined and performed as part of a single method.

[0117] Figure 8 A method for updating a baseline static path is shown. The method can be implemented by any of the remote stations disclosed herein. The method can be performed iteratively and periodically and starts at 800.

[0118] At 802, a control module (eg, Figure 1 , Figure 2 and Figure 4The control module 130, 132, 210, 402 of one of the control modules can determine and / or obtain the baseline static path of the intersection. This can include generating a static path based on the road geometry in the intersection. At 803, the control module obtains road blocking information, which can include any road blocking information in the road blocking information mentioned herein, including road and / or lane blocking and / or closure. The road blocking information can also indicate roads and / or lanes that are no longer closed and / or blocked and are therefore open. The road blocking information can include accident information, road and / or lane maintenance information, etc. This can be obtained by accessing the memory of the server and / or local station of the control module and / or obtained from the remote station and / or server.

[0119] At 804, the control module compares the blockage information, including road closures and blockages, to the baseline static path. The comparison and / or the remainder of the method may be performed at a fixed, configurable, and / or predetermined frequency (e.g., once a day). At 806, the control module determines, based on the comparison, whether the road blockage information warrants following a path different from the static path. If so, operation 808 is performed, otherwise operation 810 is performed. At 808, the control module updates the static path based on the road blockage information to generate an updated baseline static path. This may be done as desired. As an example, Figure 6 The static path shown can be Figure 7 At 810, the control module prohibits updating the static path. The method can end at 812.

[0120] Fig. 9 An intersection 900 is shown showing an RSU 902 monitoring a path 903 of a vehicle from a single turn lane 904 through the intersection 900 to two exit lanes 906. The RSU 902 may be implemented as any of the RSUs mentioned herein and is connected to an intersection camera 910 having a field of view (FOV) 912 and capturing images of the intersection 900. The RSU 902 may also be connected to a backend server 914. The RSU 902 and the backend server 914 may share information such as road obstruction information, static paths through the intersection, images collected by the intersection camera 910, etc. The RSU 902 may be implemented as part of the intersection camera 910 and / or one of the traffic lights 916.

[0121] The RSU 902 may: dynamically update static path information and provide the updated static path information to a backend server; collect images and / or track vehicle movement through an intersection and / or provide images and / or tracked vehicle data to a backend server, which may then update the static path information; and / or generate dynamic path information and provide the dynamic path information to the backend server. The RSU 902 may be connected to the camera device 910 and the backend server 914 via an Ethernet connection, a long term evolution (LTE) connection, a fifth generation (5G) mobile network connection, a wireless fidelity (Wi-Fi) connection, or other wired and / or wireless connection and / or a combination thereof.

[0122] Although a single camera and two traffic lights are shown, any number of cameras and traffic lights may be implemented at the intersection. The number and location of the cameras are arranged so that all inbound lanes, outbound lanes, and the entire intersection are covered by the FOV of the cameras. Each lane and each portion of the intersection is visible in the FOV of at least one of the cameras to track vehicles moving toward or away from that lane and through the intersection.

[0123] The control module of RSU 902 and / or the control module of backend server 914 can store the transfer function of each camera in the camera for converting the object position in the image captured by the camera into 3D global positioning system (GPS) coordinates. Two-dimensional (2D) points can be converted into 3D points. The transfer function can be based on the focal length of the camera and the camera projection. The GPS coordinates are then used to update the static path information and / or to provide dynamic path information. Transfer functions can be generated for any object in the intersection, including, for example, pedestrians and cyclists on crosswalks. This is done to track the movement of objects. A node list can be generated for each object.

[0124] Fig.10 An intersection 1000 is shown showing an RSU 1002 monitoring nodes 1004 of different paths of vehicles from a single turn lane 1008 through the intersection 1000 to two exit lanes 1010. The RSU 1002 is connected to a camera 1012 and a backend server 1014. The RSU 1002 may be implemented as any of the RSUs mentioned herein, and is connected to an intersection camera 1012 having a FOV 1016 and capturing images of the intersection 1000 at a suitable frame rate.

[0125] The RSU 1002 may: dynamically update static path information and provide the updated static path information to a backend server; collect images and / or track vehicle movement through an intersection and / or provide images and / or tracked vehicle data to a backend server, which may then update the static path information; and / or generate dynamic path information and provide the dynamic path information to a backend server.

[0126] In one embodiment, the control module of the RSU 1002 marks each vehicle in the FOV 1016. In other words, the control module provides an identifier for each vehicle, and tracks the movement of each vehicle in the vehicle and records the movement, which is identified by the tag. This may include the control module marking the data of each vehicle in the vehicle. The marked data includes the path of the tracked vehicle from the entrance lane through the intersection to the exit lane. The control module can determine the speed and yaw rate of the vehicle through the intersection. The speed and yaw rate can be determined based on the image data, the GPS data received from the vehicle, and / or the speed and yaw rate information broadcast from the vehicle via the BSM. When the vehicle drives through the intersection 1000, the control module can calculate the speed and yaw rate. The control module can calculate the three-dimensional position of the vehicle in the image and the intersection 1000 based on the path of the tracked vehicle and the speed and yaw rate information. The control module can then update the baseline static path based on the three-dimensional vehicle position.

[0127] Although the control module for RSU 1002 is described Fig.10 , but the operations of the control module of RSU 1002 can be implemented by the control module of the camera device 1012, the backend server 1014 and / or other remote stations such as edge computing devices. The monitored vehicle can be a connected vehicle or a non-connected vehicle. The edge computing device can be a multi-access edge computing device located near the intersection 1000.

[0128] If the vehicle is a connected vehicle and transmits a BSM, the BSM data of the BSM signal may be received by the RSU 1002 and / or the backend server 1014 and used in conjunction with or in place of image data collected by the camera 1012 and / or any other intersection camera of the intersection 1000. The BSM and camera data may be fused together based on, for example, the timestamp of the BSM data and the timestamp of the camera data. By fusing the BSM data and the camera data together and / or using both the BSM data and the camera data, a better estimate of the vehicle's position may be determined and predicted.

[0129] In one embodiment, and for each possible and allowed path for a vehicle through the intersection 1000, the control module of the RSU 1002 and / or the backend server 1014 averages the position data (e.g., BSM-based position data and / or camera-based position data) to provide an estimate and / or prediction of the vehicle's position. The position data of multiple vehicles is averaged for each possible and allowed path. The positions of vehicles moving from the same entry lane to the same exit lane are averaged. Vehicles may take slightly different paths. More specifically, the coordinates of corresponding nodes are averaged. For example, a list of a predetermined number (e.g., 5 to 50) of nodes may be provided for each vehicle moving from the same specific entry lane to the same specific exit lane. The nodes of a predetermined number of vehicles (e.g., 10) may be averaged. The averaging may be performed at a predetermined frequency (e.g., once every 15 minutes). The first node in the list is averaged, the second node in the list is averaged, and so on. This may be performed for each of the points in the list, and this may be performed to provide a node list of the resulting averaged nodes. The radii of curvature of the paths of vehicles moving from the same entry lane to the same exit lane may also be averaged.

[0130] In an embodiment, the position data is averaged at a fixed, configurable and / or predetermined frequency (e.g., 1 to 50 times per day). The averaged position data may be referred to as dynamic path data for the dynamic path of the vehicle. The averaged position data or dynamic path data may include a node list and / or a radius of curvature for the dynamic path. A node list and / or a radius of curvature may be provided for each path. In another embodiment, a time-based moving window is used to update the average path data. Both the time window and the frequency of the update may be fixed, configurable and predetermined. By using a moving window, the oldest position data is removed and the newly collected position data is used together with the previously collected position data.

[0131] The control module of the RSU 1002 may broadcast a map message including static path information and / or dynamic path information at a predetermined frequency (e.g., 10 Hz). The map message may be broadcast continuously or periodically. The RSU 1002 may broadcast only the map message, or may alternatively establish a link with a nearby vehicle and then send the map message and / or corresponding information.

[0132] Fig.11An intersection 1100 is shown, which shows similar static and dynamic paths of vehicles through the intersection from two turning lanes 1102, 1104 to two exit lanes 1106, 1108. An RSU 1112 connected to a camera 1114 and a backend server 1116 monitors the movement of vehicles through the intersection 1100. The static paths are solid lines 1120, 1122, and the dynamic paths are dashed lines 1124, 1126. The RSU 1112 can determine the static paths 1120, 1122 and the dynamic paths 1124, 1126 and broadcast this information to the vehicles. The static paths and / or dynamic paths may not be circular and / or completely curved, but may include curved, linear and / or semi-linear segments. These segments are connected in series, and each path in the path is provided by a corresponding set of connected segments. The static paths and / or dynamic paths may include points where linear, semi-linear and / or curved segments intersect. A dynamic path may completely match, partially match, be similar in shape, or be different in shape from a corresponding static path.

[0133] Fig.12 An example is shown where the dynamic path is substantially different from the static path due to the use of a different exit lane. Fig.12 An intersection 1200 is shown showing different static and dynamic paths of vehicles through the intersection 1200 from two turn lanes 1202, 1204 to two exit lanes 1206, 1208. An RSU 1212 connected to a camera 1214 and a backend server 1216 monitors the movement of vehicles through the intersection 1200. The dynamic paths are solid lines 1220, 1222, and the static paths are dashed lines 1224, 1226. The RSU 1212 can determine the dynamic paths 1220, 1222 and the static paths 1224, 1226 and broadcast this information to the vehicles.

[0134] Fig.13 A method for determining whether to broadcast a static path or a dynamic path is shown. Fig.13 The method may start at 1300. At 1302, a control module, such as an RSU, may determine a baseline static path for a vehicle through an intersection. This may include historical static path information of an average path of vehicles previously moved through the intersection.

[0135] At 1304, the control module may determine a dynamic path for vehicles currently moving through the intersection. The dynamic path may be generated based on tracked vehicle movement through the intersection using (i) images captured from a camera system, (ii) other intersection sensor data, and / or (iii) location data included in a BSM broadcast received from a vehicle in the intersection. The control module may average the trajectories of different vehicles to create a node set and / or calculate and average the turning radius of the trajectories. The window duration and frequency of the trajectory averaging may be configurable parameters that are remotely adjusted by, for example, a backend server.

[0136] At 1306, the control module may compare the dynamic path and / or an average thereof to the baseline static path to determine a difference between the baseline static path and the dynamic path. Intersection box path data may be generated based on the comparison, which may be broadcast to nearby vehicles as part of a V2X map message. The intersection box path data may include the dynamic vehicle path data provided at 1310 or the baseline static vehicle path data provided at 1312.

[0137] At 1308, the control module can determine whether there is a statistically significant difference between the baseline static path and the dynamic path. One or more different statistically significant difference algorithms and / or methods can be used to determine whether there is a statistically significant difference. For example, when the difference between the dynamic path and the baseline static path is greater than a predetermined amount, the control module can determine that there is statistical significance between the dynamic path and the baseline static path. As another example, when at least a portion of the dynamic path deviates from the baseline static path by more than a predetermined amount, the control module can determine that there is statistical significance between the dynamic path and the baseline static path.

[0138] As yet another example, the control module may determine that there is statistical significance between the dynamic path and the baseline static path when the average difference between the nodes of one of the dynamic paths and the nodes of one of the baseline static paths exceeds a predetermined amount. As yet another example, the control module may determine that there is statistical significance between the dynamic path and the baseline static path when a predetermined percentage of the difference between the nodes of one of the dynamic paths and the nodes of one of the baseline static paths is greater than a predetermined percentage (e.g., 10%).

[0139] The control module can be configured to adjust the duration of the window used to track the vehicle to determine the dynamic path. The control module can be configured to adjust the frequency with which the vehicle's trajectory is averaged to determine when there is a difference between (i) the average dynamic path and / or (ii) the average dynamic path and the static path. The more the dynamic path deviates from the static path, the more likely it is that there is a statistically significant difference.

[0140] When there is a statistically significant difference, operation 1310 may be performed, otherwise operation 1312 may be performed.

[0141] At 1310, the control module may use and broadcast the dynamic path data. The dynamic path data may be used to estimate and predict the position of the vehicle. The estimated and predicted position may be broadcast to the vehicle along with the dynamic path data or as an alternative to the dynamic path data.

[0142] At 1312, the control module may use and broadcast the baseline static path data. The static path data may be used to estimate and predict the position of the vehicle. The estimated and predicted position may be broadcast to the vehicle along with the baseline static path data or as an alternative to the baseline static path data.

[0143] If operation 1310 is performed, the baseline static path data may need to be updated. Operation 1314 may be performed after operation 1310 to update the baseline static path data based on the dynamic path data. The control module may replace the baseline static path data with the dynamic path data or average the baseline static path data with the dynamic path data. The dynamic path data may be averaged with an average of the baseline static path data or with a last predetermined window of static path data. The method may end at 1316.

[0144] Some intersections may have only baseline static path information, but no dynamic path information. Other intersections may have both baseline static path information and dynamic path information.

[0145] Map message generation

[0146] The following Figures 14 to 16 Relates to the generation and use of map messages that include valid intersection routing information in addition to other information traditionally included in a map message. Valid intersection routing information may include available and allowed routing information. Examples of conventional map message content are mentioned below. This may include updating static routing data with information defining planned lane closures and other road obstructions.

[0147] Fig.14An intersection 1400 is shown, which shows nodes 1402, 1404 of a path of a vehicle including an example radius of curvature R from two turning lanes 1406, 1408 through the intersection 1400 to two exit lanes 1410, 1412. The control module of the RSU can use road geometry information to determine an available turning path through the intersection 1400. The turning path can be determined based on the stored position of the vehicle in the intersection moving from the entrance lane 1406, 1408 to the exit lane 1410, 1412. The path can be generated based on the radius of curvature of the node and / or the line (or path) connecting the node. The control module can average the trajectory of the vehicle to create a node set or a turning radius to determine each of the dynamic paths. The control module is configured to adjust the window duration for tracking the vehicle to determine the dynamic path. The node and / or radius can be included in a map message, which is broadcast and / or transmitted to the vehicle and / or VRU device from the RSU or other station. The map message may include intersection box path data indicating the position of the vehicle in the intersection. The map message may be a V2X type map message.

[0148] Fig.15 A representation of a tree structure of a map message 1500 is shown. The tree structure comprises levels, wherein each level comprises one or more data elements and / or one or more frames. Each frame is connected to the next level, which comprises one or more data elements and / or one or more frames.

[0149] In the example shown, map message 1500 includes 5 levels of information, but may include any number of levels of information. The first level includes frames 1502, which refer to frames 1504 and data elements 1506 in the second level. Although not shown, each of frames 1504 refers to one or more data elements and / or one or more frames. As shown, one of frames 1504 (referred to as a "connected to" frame) can refer to another frame 1508 in the next level. Connected to a frame can include information about entry and exit lanes and corresponding attributes of each lane (e.g., certain types of traffic signals). One of frames 1508 can refer to frame 1510 and data element 1512. Frame 1510 can refer to data element 1514.

[0150] As an example, frame 1502 can be a general frame. Frame 1504 can include a lane attribute frame, a manipulation frame, a node list frame, a connection frame, an overlay frame and / or a region frame. Data element 1506 can include a lane identifier, a name, an entrance and passage identifier, and / or an exit and passage identifier. Connecting to a frame can refer to frame 1508, which can be referred to as a "connection" frame. Data element 1512 can include a connection lane data element, a remote intersection data element, a signal group data element, a user category data element and / or a connection identifier.

[0151] Frame 1510 may be an intersection box path frame that references intersection path information, such as the radius, center point latitude, center point longitude, and node list of the vehicle path. The center point latitude and center point longitude refer to the coordinates of the center point of a circle having the radius of the vehicle path. The intersection box path information is added to the map message to indicate the vehicle position within the corresponding intersection, which the vehicle can use to determine the vehicle's position and for other purposes, as further described below.

[0152] As Fig.15 The alternative option is Fig.16 A representation of a tree structure of a map message 1600 including level jumps (or links between levels) in the form of intersection box path frame identifiers (IDs) is shown. The tree structure includes levels, where each level includes one or more data elements and / or one or more frames. Each frame is connected to the next level, which includes one or more data elements and / or one or more frames.

[0153] In the example shown, map message 1600 includes 5 levels of information, but may include any number of levels of information. The first level includes frames 1602, which refer to frames 1604 and data elements 1606 in the second level. Although not shown, each of frames 1604 refers to one or more data elements and / or one or more frames. As shown, one of frames 1604 may refer to another frame 1608, and another of frames 1604 may refer to a frame 1610 in the next level. One of frames 1608 may refer to data element 1612 in level 4. Frame 1608 may be referred to as a "connection" or "path" frame. Frame 1610 may be referred to as a "connection" frame.

[0154] One of the frames 1610 can refer to frame 1614 and data element 1616. Frame 1614 refers to data element 1618. One of the data elements 1618 is a level jump from level 5 to level 2 and from one of the data elements 1618 (called "intersection box path identifier") to one of the frames 1604 (called "intersection box path frame"). The jump is shown by the dotted arrow 1620. Data element 1612 may include intersection path information, such as an intersection box path ID, a radius of the vehicle path, a center point latitude, a center point longitude, and a node list. The center point latitude and the center point longitude refer to the coordinates of the center point of a circle with a radius of the vehicle path. The intersection box path information is added to the map message to indicate the vehicle position within the corresponding intersection, which the vehicle can use to determine the vehicle's position and for other purposes, as further described below.

[0155] Figure 15 to Figure 16 The tree structure of the map messages 1500, 1600 can be used to quickly access intersection frame path information while traversing a minimum number of levels and accessing and / or consulting a minimum number of frames and data elements. The map messages 1500, 1600 can indicate which exit lanes are available for each entrance lane of the intersection for the vehicle in the entrance lane. The map messages 1500, 1600 can indicate which traffic signal is applicable to the vehicle when the vehicle is in the entrance lane. For example, whether a left turn traffic signal, a right turn traffic signal, or a straight traffic signal is applicable to the entrance lane.

[0156] Map messages 1500, 1600 may be generated by a remote station and broadcast and / or sent to a vehicle. The vehicle may then use the map and / or intersection box path information to determine the location of the vehicle, where the vehicle is located in a lane, which lane the vehicle is in, and the like. This information may then be used to determine whether one or more of the vehicles is about to, for example, run a red light, collide with another vehicle, follow an invalid path through an intersection, or perform some other incorrect maneuver. The control module of the corresponding vehicle may detect that the vehicle is about to run a red light based on: the time until the light will change from red to green; the vehicle location; the vehicle speed; and the vehicle heading information.

[0157] Path prediction enhancement

[0158] The following Figure 17 to Figure 18Relates to improved path prediction algorithms that utilize valid intersection path information when appropriate and under certain conditions. This may include using images captured by intersection cameras (and / or other sensor data) and / or basic safety messages generated by connected vehicles as described above to generate dynamic vehicle path data for vehicles passing through an intersection. A prerequisite for enhanced path prediction is the receipt of a map message and the existence of an intersection including an available path through it.

[0159] Fig.17 A top view of an example intersection 1700 is shown showing a predicted first node 1702 for a vehicle based on available intersection path information from a map message and a predicted second node 1704 for the vehicle without intersection path information provided via a map message.

[0160] Path prediction algorithms without intersection path information may require yaw rate, vehicle speed, and Global Navigation Satellite System (GNSS) inputs to predict the path of the vehicle. The yaw rate and speed of a vehicle are typically not constant, especially when the vehicle is turning a corner or moving after the vehicle has stopped. For this reason, path predictions based on yaw rate, vehicle speed, and GNSS data may be inaccurate, especially when making sharp turns and / or moving from a stationary position. As disclosed herein, static and dynamic path information may be provided in a map message to improve path prediction. Path predictions may be based on static and / or dynamic path information and / or based on yaw rate, vehicle speed, and GNSS data. Static and dynamic path information are high probability indicators of the vehicle's path and, therefore, may be weighted more heavily than yaw rate, vehicle speed, and GNSS data when weighting parameters based on which the vehicle's path is predicted. In Fig.17 In the example of FIG. 1 , due to prediction inaccuracies associated with using yaw rate, vehicle speed, and GNSS data, second node (or path prediction point) 1704 results in a predicted path that does not point to exit lane 1720. This is different from first node (or path point) 1702 that leads to exit lane 1720.

[0161] In an embodiment, when the GNSS position data indicates that the vehicle is traveling along a node path indicated by a map message, a control module of the vehicle uses the map message data for path prediction operations, rather than relying on yaw rate and vehicle speed. With respect to path prediction, CAN data, which may include yaw rate data and vehicle speed data, may be ignored when approaching an intersection and activated and / or relied upon after leaving the intersection.

[0162] Fig.18 It is a method to provide intersection-based path prediction and provide collision warning and basic safety message transmission based on path prediction. It can be performed iteratively Fig.18 The method may begin at 1800. At 1802, a control module (e.g., Figures 1 to 3 The control module 120, 220, 307 of one of the above) can be used to receive a map message from a remote station, such as any remote station mentioned herein, including Figures 1 to 4 Cloud-based server 108, RSU 110, RSU 202, remote station 400.

[0163] At 1804, the control module may determine whether the host vehicle is at and / or approaching an intersection. If so, operations 1806 and 1808 are performed, otherwise operation 1812 is performed. In one embodiment, operations 1806 and 1808 are performed sequentially, so that one of operations 1806 and 1808 is performed before the other of operations 1806 and 1808. At 1806, the control module uses the intersection box data including the node list and / or curvature radius of the vehicle path through the intersection for path prediction and / or collision warning.

[0164] The location of the host vehicle may be determined based on other information such as vehicle speed, yaw rate of the vehicle, GNSS (or GPS) data, etc. Using map message information including a list of nodes and / or a radius of curvature of the vehicle's path provides a substantially better prediction of the host vehicle's path than using the host vehicle's speed and yaw rate alone for path prediction purposes. A control module may receive GNSS data and determine when the host vehicle is at or near a node of a static or dynamic node set of a map message. As an example, the GNSS location may be correct and the host vehicle may not be at the center of the path. Correlation with the node indicates that the host vehicle is traveling on a similar path.

[0165] Node locations on static or dynamic paths and / or predicted path information are broadcast over the air in basic safety messages to other vehicles to prevent collisions. Path data can be sent to other vehicles in map messages to prevent collisions. Collision warnings can include forward collision warnings, pedestrian collision warnings, and / or other collision warnings (e.g., side collision warnings). Collision warning operations are performed based on the predicted path of the host vehicle determined by the control module.

[0166] At 1808, the control module generates a BSM using the intersection box data including a node list and / or a radius of curvature of the vehicle path through the intersection. The control module determines the most likely path of the host vehicle based on the node list and / or the radius of curvature and generates a BSM indicating the predicted path of the host vehicle. The determination may also be based on other information, such as vehicle speed, yaw rate of the vehicle, GNSS (or GPS) data, etc. The BSM may be transmitted from the host vehicle to (i) nearby connected vehicles and (ii) VRU devices to indicate the predicted path of the host vehicle and support collision avoidance applications.

[0167] At 1810, the control module determines whether the host vehicle has left the intersection. If so, operation 1812 may be performed, otherwise operations 1806, 1808 may be repeated. At 1812, the control module uses vehicle data (which may be CAN data including the vehicle's yaw rate and velocity) for path prediction purposes. This may not include using the node list and / or curvature radius from the map message. Operation 1802 may be performed after operation 1812.

[0168] Pedestrian Collision Warning Enhanced

[0169] The following Figures 19 to 21 PCW enhancement involving the use of path prediction provided as described above. This provides more accurate detection and avoidance of VRU collision threats.

[0170] Fig.19 An intersection 1900 is shown showing a first predicted path 1902 based on map message intersection path information, a second predicted path based on vehicle speed and yaw rate, a third actual vehicle path 1906, and an example corresponding radius of curvature R. The first predicted path 1902 has a node 1910. The second node path has a corresponding point 1912.

[0171] When the host vehicle starts from a complete stop, such as in a left turn lane before making a left turn, the accuracy of the speed and yaw rate is insufficient to accurately predict the path of the host vehicle through the intersection. Using map message information that includes a node list and / or a radius of curvature of the vehicle's path through the intersection provides a high probability path that the host vehicle will follow, such as path 1902. This high probability path can be used when predicting the path of the host vehicle. If the vehicle speed and yaw rate are used alone, the control module of the host vehicle can predict that the host vehicle follows a second path shown by point 1912. A radius can be provided when the path is circular, semi-circular, and / or arc-shaped. The use of map message information including an intersection data set containing a node list and / or a radius improves the accuracy of path prediction. Path predictions can be made faster and used for collision warning purposes, such as for determining pedestrian conflict boxes. Pedestrian conflict boxes refer to areas where the host vehicle and pedestrians may be located at the same time. Some example pedestrian conflict boxes are shown in FIG. Fig. 20 Shown in.

[0172] Fig. 20 An intersection 2000 is shown showing predicted paths 2002, 2004 of vehicles and a conflict box 2006. The intersection may include an RSU 2010 connected to a camera 2012 and a backend server 2014. In this example, the illustrated vehicle may move through the intersection 2000 along the path 2002 from a left turn lane 2016 to an exit lane 2018, or along the path 2004 from a left turn lane 2016 to an exit lane 2020. The conflict box 2006 may be referred to as a pedestrian conflict box. The conflict box 2006 refers to an area where a vehicle and a pedestrian (e.g., pedestrian 222) may be located at the same time and therefore a potential collision may occur.

[0173] Fig.21 A method for performing a pedestrian collision warning at a vehicle based on intersection path information of a map message received at the vehicle is shown. The following operations may be performed iteratively. The method may start at 2100. At 2102, a control module of the vehicle may receive a signal from a remote station (e.g., Fig. 20 RSU 2010) receives map messages including intersection box data.

[0174] At 2104, the control module may receive a personal safety message (PSM) from an RSU or VRU device. When a VRU device is carried by a VRU, the PSM may indicate the motion state of the VRU. This may include the speed, position, and / or heading of the VRU. As an example, the VRU device may be carried by a VRU such as Fig. 20A portable device held or worn by a pedestrian walking across a crosswalk at an intersection is shown. Example portable devices are mobile phones, laptops, tablets, smart watches, etc. The RSU can receive a PSM from a VRU device and forward the PSM to the RSU. The PSM can also be generated by the RSU, where the detection of the VRU is done by a camera or other sensing device connected to the RSU.

[0175] At 2108, the control module may calculate possible conflict boxes (eg, Fig. 20 When the vehicle stops and / or starts moving and may need time to stabilize, it may be difficult to measure the speed and yaw rate, and therefore it may be difficult to determine the position of the vehicle and predict the conflict box based solely on the vehicle speed and yaw rate.

[0176] At 2110, the control module may determine whether the vehicle is moving. If so, operation 2112 is performed, otherwise operation 2016 is performed. At 2112, the control module may receive GNSS (or GPS) data and CAN data including the speed and yaw rate of the vehicle.

[0177] At 2114, the control module may use GNSS data to associate the intersection box path from the map message with a map of the area. At 2116, the control module may determine the most likely trajectory of the vehicle based on the association results. At 2118, the control module may identify the primary conflict box among the possible conflict boxes. This is based on the collected and / or calculated data. The primary conflict box is the conflict box with the highest probability of a collision. This is based on the known speed, position, heading and / or predicted trajectory of the vehicle and the VRU and VRU equipment.

[0178] At 2120, the control module may predict whether the VRU and the vehicle will be in the same conflict box (ie, in the same geographic area at the same time). If so, operation 2122 may be performed, otherwise operation 2102 may be performed.

[0179] At 2122, the control module may perform countermeasures to avoid the collision. This may include generating an alert message inside and / or outside the vehicle. The control module may control the operation of the vehicle to adjust the speed, acceleration, and / or deceleration of the vehicle to avoid the collision. The control module may send a signal to the VRU device so that the VRU device may perform countermeasures including warning the VRU. The VRU may then take action to avoid the collision.

[0180] Figure 8 , Fig.13 , Fig.18 and Fig.21The above operations are intended as illustrative examples. Depending on the application, the operations may be performed sequentially, synchronously, simultaneously, continuously, during overlapping time periods, or in a different order. In addition, depending on the order of events and / or implementation, any of the operations may not be performed or may be skipped.

[0181] Although the above reference Figures 1 to 21 Various features and embodiments are described, but Figures 1 to 21 Any or all of the embodiments may be combined and implemented as a single embodiment.

[0182] The foregoing description is essentially only illustrative, and is by no means intended to limit the present disclosure, its application or use. The broad teachings of the present disclosure can be implemented in various forms. Therefore, although the present disclosure includes specific examples, the true scope of the present disclosure should not be limited thereto, because other modifications will become apparent after studying the drawings, the specification and the appended claims. It should be understood that, without changing the principle of the present disclosure, one or more steps in the method can be performed in different orders (or simultaneously). In addition, although each embodiment is described as having certain features above, any one or more of those features described in any embodiment of the present disclosure can be implemented and / or combined with it in the features of any other embodiment, even if the combination is not clearly described. In other words, the described embodiments are not mutually exclusive, and the mutual replacement of one or more embodiments is retained within the scope of the present disclosure.

[0183] Various terms are used to describe the spatial and functional relationships between elements (e.g., between modules, circuit elements, semiconductor layers, etc.), including "connected," "engaged," "coupled," "adjacent," "next to," "on top," "above," "below," and "arranged." Unless explicitly described as "directly," when describing the relationship between a first element and a second element in the above disclosure, the relationship can be a direct relationship in which there are no other intervening elements between the first element and the second element, but can also be an indirect relationship in which there are one or more intervening elements (spatially or functionally) between the first element and the second element. As used herein, the phrase at least one of A, B, and C should be interpreted to mean a logical (A or B or C) using a non-exclusive logical OR, and should not be interpreted to mean "at least one of A, at least one of B, and at least one of C."

[0184] In the drawings, the direction of the arrows, as indicated by the arrows, generally shows the flow of information (e.g., data or instructions) that is important to the illustration. For example, when element A and element B exchange various information but the information transmitted from element A to element B is relevant to the illustration, the arrow may point from element A to element B. This unidirectional arrow does not imply that no other information is transmitted from element B to element A. In addition, for information sent from element A to element B, element B may send a request for the information to element A or send a confirmation of receipt of the information.

[0185] In this application, the term "module" or the term "controller" may be replaced with the term "circuit" in the case of including the following definitions. The term "module" may refer to, be part of, or include: an application-specific integrated circuit (ASIC); a digital, analog, or mixed analog / digital discrete circuit; a digital, analog, or mixed analog / digital integrated circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor circuit (shared, dedicated, or grouped) that executes code; a memory circuit (shared, dedicated, or grouped) that stores code executed by the processor circuit; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system on a chip.

[0186] Module can include one or more interface circuits.In some examples, interface circuit can include the wired or wireless interface that is connected to local area network (LAN), Internet, wide area network (WAN) or its combination.The function of any given module of the present disclosure can be distributed in multiple modules connected via interface circuit.For example, multiple modules can allow load balancing.In other examples, server (also referred to as remote or cloud) module can realize some functions on behalf of client module.

[0187] The term code as used above may include software, firmware and / or microcode, and may refer to a program, a routine, a function, a class, a data structure and / or an object. The term shared processor circuit includes a single processor circuit that executes some or all of the code from multiple modules. The term grouped processor circuit includes a processor circuit that is combined with another processor circuit to execute some or all of the code from one or more modules. References to multiple processor circuits include multiple processor circuits on discrete chips, multiple processor circuits on a single chip, multiple cores of a single processor circuit, multiple threads of a single processor circuit, or a combination of the above. The term shared memory circuit includes a single memory circuit that stores some or all of the code from multiple modules. The term grouped memory circuit includes a memory circuit that is combined with another memory to store some or all of the code from one or more modules.

[0188] The term memory circuit is a subset of the term computer-readable medium. The term computer-readable medium as used herein does not include transient electrical signals or transient electromagnetic signals propagated through a medium (e.g., on a carrier wave); thus the term computer-readable medium may be considered to be tangible and non-transient. Non-limiting examples of non-transient tangible computer-readable media are non-volatile memory circuits (e.g., flash memory circuits, erasable programmable read-only memory circuits, or mask read-only memory circuits), volatile memory circuits (e.g., static random access memory circuits or dynamic random access memory circuits), magnetic storage media (e.g., analog or digital tape or hard drive), and optical storage media (e.g., CD, DVD, or Blu-ray disc).

[0189] The apparatus and methods described in this application may be implemented in part or in whole by a special purpose computer created by configuring a general purpose computer to perform one or more specific functions embodied in a computer program. The above functional blocks, flow chart components and other elements serve as software instructions, which can be compiled into a computer program by the routine work of an experienced technician or programmer.

[0190] The computer program includes processor executable instructions stored on at least one non-transitory, tangible computer readable medium. The computer program may also include or rely on stored data. The computer program may include a basic input / output system (BIOS) that interacts with the hardware of the special-purpose computer, device drivers that interact with specific devices of the special-purpose computer, one or more operating systems, user applications, background services, background applications, etc.

[0191] A computer program may include: (i) a descriptive text to be parsed, such as HTML (Hypertext Markup Language), XML (Extensible Markup Language), or JSON (JavaScript Object Notation); (ii) assembly code; (iii) object code generated by a compiler from a source code; (iv) source code executed by an interpreter; (v) source code compiled and executed by a real-time compiler; etc. By way of example only, source code may be written using syntax from languages ​​including: C, C++, C#, Objective C, Swift, Haskell, Go, SQL, R, Lisp, Java (registered trademark), Fortran, Perl, Pascal, Curl, OCaml, Javascript (registered trademark), HTML5 (Hypertext Markup Language 5th Revision), Ada, ASP (Active Server Pages), PHP (PHP: Hypertext Preprocessor), Scala, Eiffel, Smalltalk, Erlang, Ruby, Flash (registered trademark), Visual Basic (registered trademark), Lua, MATLAB, SIMULINK, and Python (registered trademark).

Claims

1. A remote station, comprising: Transceiver; a memory configured to store (i) a baseline static path of a vehicle moving through an intersection and (ii) map data; as well as A control module configured to: Get road congestion information, determining whether the road blockage information affects one or more of the baseline static paths for the vehicle to pass through the intersection based on the baseline static paths and the map data, and updating the one or more baseline static paths based on the road blockage information, and A map message indicating the updated one or more baseline static paths is broadcasted via the transceiver.

2. The remote station according to claim 1, wherein: The baseline static path is a predicted vehicle path through the intersection from an entry lane to the intersection to an exit lane from the intersection.

3. A remote station according to claim 1 or 2, wherein: The baseline static path includes two-dimensional or three-dimensional path information.

4. A remote station according to any one of claims 1 to 3, wherein: The control module is configured to determine, at a predetermined frequency, whether the road obstruction information affects any of the baseline static paths.

5. A remote station according to any one of claims 1 to 4, wherein: The control module is configured to: determining a dynamic path based on at least one of a camera, other sensor data, or a primary safety message; comparing the dynamic path to the baseline static path; as well as The baseline static path is updated based on a comparison result between the dynamic path and the baseline static path.

6. The remote station of claim 5, wherein: The dynamic path is the actual vehicle path through the intersection from an entry lane to the intersection to an exit lane from the intersection.

7. A remote station according to any one of claims 1 to 6, wherein: The road obstruction information includes at least one of lane closure information or road closure information.

8. A remote station according to any one of claims 1 to 7, wherein: The road congestion information includes accident information.

9. A remote station according to any one of claims 1 to 8, wherein: The road congestion information includes road maintenance information.

10. A remote station according to any one of claims 1 to 9, wherein: The remote station is implemented as an intersection camera, a traffic light, an RSU, a cloud-based server, a backend server, or an edge computing device.

11. A remote station according to any one of claims 1 to 10, wherein: The control module is configured to: connected to one or more intersection camera devices; tracking movement of vehicles through the intersection based on signals from the one or more intersection cameras; as well as The baseline static path is updated based on the tracked movement of the vehicle.

12. The remote station of claim 11, wherein: The transceiver communicates with the one or more intersection cameras via an Ethernet connection, a Long Term Evolution connection, a Fifth Generation (5G) connection, or a Wireless Fidelity (Wi-Fi) connection.

13. The remote station according to any one of claims 1 to 12, further comprising a camera configured to capture an image of the intersection, in, The control module is configured to: tracking the movement of vehicles through the intersection based on the captured images, and The baseline static path is updated based on the tracked movement of the vehicle.

14. A remote station according to any one of claims 1 to 13, wherein: The control module is configured to: (i) connect to a cloud-based server, an edge computing device, or a backend server and collect captured images from one or more camera devices at the intersection, the one or more camera devices tracking vehicles passing through the intersection; and (ii) updating the baseline static path based on the tracked movement of the vehicle.

15. A remote station according to any one of claims 1 to 14, wherein: The control module is configured to: (i) receive captured images from a camera having a field of view covering at least a portion of the intersection; (ii) convert positions of objects in the intersection into three-dimensional global positioning system coordinates based on the captured images; and (iii) update the baseline static path based on the three-dimensional global positioning system coordinates.

16. A remote station according to any one of claims 1 to 15, wherein: The control module is configured to: tagging data of the vehicle and tracking a path of the vehicle through the intersection from an entry lane to an exit lane; determining a speed and a yaw rate of the vehicle passing through the intersection; calculating a three-dimensional vehicle position in the intersection and in a plurality of frames based on the tracked path of the vehicle and the speed and yaw rate of the vehicle; as well as The baseline static path is updated based on the three-dimensional vehicle position.

17. A remote station according to any one of claims 1 to 16, wherein: The control module is configured to: receiving a basic safety message from one or more vehicles; and The baseline static path is updated based on the basic security message.

18. The remote station of claim 17, wherein: The control module is configured to: receiving data from one or more camera devices having a field of view covering at least a portion of the intersection; fusing data received from the one or more cameras with data in the primary safety message to provide an aggregate data set; as well as The baseline static path is updated based on the aggregate data set, including storing at least one of a node list or a radius of curvature of a path of the one or more vehicles through the intersection.

19. A remote station comprising: Transceiver; a memory configured to store a baseline static path and a dynamic path for a vehicle to pass through an intersection, wherein the baseline static path refers to at least one of a previously predetermined path, an average path, or a historical path, and wherein the dynamic path refers to a currently detected path; and A control module configured to: (i) compare the dynamic path to the baseline static path; (ii) determine whether there is a statistical significance between the dynamic path and the baseline static path; (iii) in response to the statistical significance between the dynamic path and the baseline static path, broadcast a first map message indicating the dynamic path via the transceiver; and (iv) in response to the absence of statistical significance between the dynamic path and the baseline static path, broadcast a second map message indicating the baseline static path via the transceiver.

20. The remote station of claim 19, wherein: The control module is configured to average the trajectories of the vehicles to create a set of nodes or a turning radius to determine one of the dynamic paths.

21. A remote station according to claim 19 or 20, wherein: There is statistical significance between the dynamic path and the baseline static path when the difference between the dynamic path and the baseline static path is greater than a predetermined amount.

22. A remote station according to any one of claims 19 to 21, wherein: There is a statistical significance between the dynamic path and the baseline static path if at least a portion of the dynamic path deviates from the baseline static path by more than a predetermined amount.

23. A remote station according to any one of claims 19 to 22, wherein: If a mean difference between nodes of one of the dynamic paths and nodes of one of the baseline static paths exceeds a predetermined amount, there is a statistical significance between the dynamic path and the baseline static path.

24. A remote station according to any one of claims 19 to 23, wherein: There is statistical significance between the dynamic path and the baseline static path when a predetermined percentage of differences between nodes of one of the dynamic paths and nodes of one of the baseline static paths is greater than a predetermined percentage.

25. A remote station according to any one of claims 19 to 24, wherein: The control module is configured to adjust a window duration for tracking the vehicle to determine the dynamic path.

26. A remote station according to any one of claims 19 to 25, wherein: The control module is configured to adjust the frequency at which trajectories of the vehicle are averaged to determine an average dynamic path, and to broadcast the map message to include the average dynamic path when a difference between the average dynamic path and at least one of the baseline static paths is statistically significant.

27. A remote station according to any one of claims 19 to 26, wherein: The map message includes intersection box path data indicating the position of the vehicle in the intersection.

28. A remote station according to any one of claims 19 to 27, wherein: The map message is a vehicle-to-everything type map message.

29. A remote station according to any one of claims 19 to 28, wherein: The control module is configured to: Obtain map data and road congestion information; determining whether the road blockage information affects one or more of the baseline static paths for the vehicle to pass through the intersection based on the baseline static paths and the map data, and updating the one or more baseline static paths based on the road blockage information; as well as A third map message indicating the updated one or more baseline static paths is broadcasted via the transceiver.

Citation Information

Cited By

  • Method for VRU to predict movement path in wireless communication system supporting sidelink, and device for same

    US12493098B2

  • Method for VRU to predict movement path in wireless communication system supporting sidelink, and device for same

    US20230087496A1