Occulsion aware planning and control
US-2019384302-A1 · Dec 19, 2019 · US
US11585669B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11585669-B2 |
| Application number | US-202017007565-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 31, 2020 |
| Priority date | Aug 31, 2020 |
| Publication date | Feb 21, 2023 |
| Grant date | Feb 21, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In some examples, a system may determine a plurality of routes between a source location and a destination location. Further, the system may segment each route of the plurality of routes into multiple road segments. The system may determine a first field of view (FOV) for each road segment. In addition, the system may receive vehicle sensor configuration information for vehicle sensors on board a vehicle. The system may determine a second FOV for the vehicle sensors. Additionally, the system may select a route for the vehicle based at least on comparing the second FOV with the first FOV for a plurality of the road segments.
Opening claim text (preview).
What is claimed: 1. A system comprising: one or more processors; and one or more non-transitory computer-readable media including executable instructions, which, when executed by the one or more processors, configure the one or more processors to perform operations comprising: determining a plurality of routes between a source location and a destination location; segmenting each route of the plurality of routes into multiple road segments; receiving, from a database, a respective first field of view (FOV) for each respective road segment of the multiple road segments of the plurality of routes, each respective first FOV corresponding to a zone of the respective road segment that has been specified for monitoring by vehicles during traversal of the road segment and based on at least one of a safety requirement or an automated driving requirement; receiving vehicle sensor configuration information for vehicle sensors on board a vehicle; determining a second FOV indicating a zone of sensor coverage around the vehicle provided by the vehicle sensors; comparing the second FOV with the respective first FOVs received from the database for the respective road segments of the multiple road segments to determine a first subset of the routes, wherein the first subset of the routes indicates a higher FOV coverage of the first FOV by the vehicle sensors, indicative of at least one of route safety or a capability of being traversed by automated driving; determining a predicted fuel consumption for the vehicle for the plurality of the routes; determining predicted vehicle dynamics for the vehicle for the plurality of the routes, wherein determining the predicted vehicle dynamics includes determining, based at least in part on a road geometry for individual routes of the plurality of routes, at least one of a predicted vehicle jerk, roll, pitch, or yaw; and selecting a route for the vehicle from the first subset based at least on the higher FOV coverage, the predicted fuel consumption and the predicted vehicle dynamics. 2. The system as recited in claim 1 , wherein a respective first FOV for a respective road segment includes one or more zones of the respective road segment selected for monitoring with the vehicle sensors to at least one of avoid collisions or perform automated driving. 3. The system as recited in claim 1 , the operation of comparing the second FOV with the respective first FOVs for the multiple road segments to determine a first subset of the routes further comprises: determining an amount of overlap of the second FOV with the respective first FOV for each road segment; and determining a cumulative amount of overlap for a respective route based on aggregating the amounts of overlap for the road segments included in the respective route. 4. The system as recited in claim 1 , the operations further comprising: receiving the vehicle sensor configuration information for the vehicle sensors on board the vehicle in a communication received from the vehicle; and determining the second FOV for the vehicle sensors based at least on the received vehicle sensor configuration information indicating a type of the vehicle sensors. 5. The system as recited in claim 1 , the operations further comprising: determining a speed profile for individual segments of the multiple segments, the speed profile indicating a predicted speed of the vehicle for traversing the individual segments; and determining the predicted vehicle dynamics and predicted fuel consumption based partially on the predicted speed. 6. The system as recited in claim 1 , the operation of selecting the route for the vehicle from the first subset based at least on the FOV coverage, the predicted fuel consumption and the predicted vehicle dynamics further comprising: selecting the route by considering user defined criteria including at least one of an FOV overlap threshold, an efficiency threshold, or a comfort threshold. 7. A method comprising: determining, by one or more processors, a plurality of routes between a source location and a destination location; segmenting each route of the plurality of routes into multiple road segments; receiving, from a database, a respective first field of view (FOV) for each respective road segment of the multiple road segments of the plurality of routes, each respective first FOV corresponding to a zone of the respective road segment that has been specified for monitoring by vehicles during traversal of the road segment and based on at least one of a safety requirement or an automated driving requirement; receiving vehicle sensor configuration information for vehicle sensors on board a vehicle; determining a second FOV indicating a zone of sensor coverage around the vehicle provided by the vehicle sensors; and selecting a route for the vehicle, from the plurality of routes, and based at least on comparing the second FOV with the respective first FOVs received from the database for the respective road segments of the multiple road segments of the plurality of routes. 8. The method as recited in claim 7 , wherein a respective first FOV for a respective road segment includes one or more zones of the respective road segment selected for monitoring with the vehicle sensors to at least one of avoid collisions or perform automated driving. 9. The method as recited in claim 7 , wherein comparing the second FOV with the respective first FOVs for the multiple road segments further comprises: determining an amount of overlap of the second FOV with the respective first FOV for each road segment; and determining a cumulative amount of overlap for a respective route based on aggregating the amounts of overlap for each of the road segments included in the respective route. 10. The method as recited in claim 7 , further comprising: receiving vehicle information indicating at least a powertrain configuration of the vehicle; determining a predicted fuel consumption for the vehicle for the plurality of the routes based at least in part on the received powertrain configuration; and selecting the route based partially on considering the predicted fuel consumption. 11. The method as recited in claim 7 , further comprising: receiving vehicle information indicating the configuration of the vehicle, wherein the information indicating the configuration of the vehicle includes at least one of powertrain information or chassis information for the vehicle; determining predicted vehicle dynamics for the vehicle for the plurality of the routes based at least partially on the received information indicating the configuration of the vehicle, wherein determining the predicted vehicle dynamics includes determining, based at least in part on a road geometry for individual routes of the plurality of routes, at least one of a predicted vehicle jerk, roll, pitch, or yaw; and selecting the route based partially on considering the predicted vehicle dynamics. 12. The method as recited in claim 7 , further comprising determining that the selected route conforms to a time threshold and an FOV coverage threshold prior to selecting the route for the vehicle. 13. The method as recited in claim 7 , further comprising: receiving the one or more current conditions over a network from one or more computing devices, the one or more current conditions including at least one of: weather conditions, or traffic conditions; and selecting a different route for the vehicle based on receiving the one or more current conditions. 14. A system comprising: one or more processor configured by executable instructions to perform operations comprising: determining a plurali
Preferred or disfavoured areas, e.g. dangerous zones, toll or emission zones, intersections, manoeuvre types or segments such as motorways, toll roads or ferries · CPC title
Fuel consumption; Energy use; Emission aspects · CPC title
Details of route searching algorithms, e.g. Dijkstra, A*, arc-flags or using precalculated routes · CPC title
Input other than that of destination using image analysis, e.g. detection of road signs, lanes, buildings, real preceding vehicles using a camera · CPC title
Speed control (B60W30/16 takes precedence) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.