Route selection

• US 8,768,623 B2
• Filed: 10/17/2011
• Issued: 07/01/2014
• Est. Priority Date: 10/17/2011
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Krzanowski, Roman, Parsons, Yvonne Cuilian Fang
• Primary Examiner(s): Tarcza, Thomas
• Assistant Examiner(s): Lee, Tyler J
• Application Number:
  US13/274,405
• Publication Number:
  US 20130096826A1
• Time in Patent Office: 988 Days
• Field of Search: 701400-410, 701/487, 701/532, 701/533, 701/123, 340988-996
• US Class Current: 701/533
• CPC Class Codes: G01C 21/34 Route searching; Route guidance
• CPC Class Codes: G01C 21/3407 specially adapted for specific applications
• CPC Class Codes: G01C 21/3492 employing speed data or traffic data, e.g. real-time or historical traffic control systems for road vehicles involving transmission of navigation instructions to the vehicle G08G1/0968
• CPC Class Codes: G01C 21/3617 using user history, behaviour, conditions or preferences, e.g. predicted or inferred from previous use or current movement
• CPC Class Codes: G01C 21/3626 Details of the output of route guidance instructions traffic control systems for road vehicles involving transmission of navigation instructions to the vehicle G08G1/0968
• CPC Class Codes: G01C 21/3661 Guidance output on an external device, e.g. car radio

Abstract

A request is received to compute a route from a start point to an end point. The route is computed using map data that includes a plurality of map elements, and route data that includes rules associated with the map elements, each of the rules being triggered by a condition flag that specifies a condition according to which the rule should be applied. The route data is based inputs related to driver experience in a geographic area associated with the route, and the inputs are based on stored data and not real-time or near-real-time data.

Claims

1. A method, comprising:

receiving, in a computing device having a processor and a memory, a request to compute a route from a start point to an end point; and

computing the route using map data that includes a plurality of map elements, and route data that includes rules associated with the map elements, each of the rules being triggered by a condition flag that specifies a condition according to which the rule should be applied,

specifying a rule that includes avoidance of a map element based at least in part on user inputs related to driver knowledge provided in advance of occurrence of the condition and

wherein the route data is based at least in part on user inputs related to driver experience in a geographic area associated with the route, and further wherein the user inputs are based on stored data and not real-time or near-real-time traffic data.

2. The method of claim 1, wherein the condition flag includes at least one of a time, a date, a weather condition, and an event.

3. The method of claim 1, wherein the rules include at least one of a rule to avoid a map element and a rule to use a map element.

4. The method of claim 1, wherein the map elements include at least one of a road, a street, a highway, an intersection, a bridge, and a building.

14. The method of claim 1, wherein the user inputs related to driver experience are inputted via a graphical user interface by a driver having knowledge and experience specific to at least one of the map elements.

15. The method of claim 14, wherein the user inputs associate at least one of the map elements with the condition flag.

16. The method of claim 15, wherein the rules are associated, in response to the user inputs related to driver experience, with the at least one map element and the condition flag.

17. The method of claim 1, wherein the route data is not based on traffic data and further wherein the route data reflects driver experiences collected over a period of time, the period of time including at least one of the most recent days and the most recent weeks.

18. The method of claim 1, further comprising collecting the route data by surveying at least one driver in the geographic area.

19. The method of claim 1, wherein the condition is a venue event.

20. The method of claim 1, further comprising collecting the route data by presenting the map elements to a user and allowing the user to specify the rules for the map elements.

21. The method of claim 20, wherein the rules that the user can specify include at least one of the following:

avoid during a specific time, avoid during certain weather condition and avoid during specific event.

5. A non-transitory computer-readable medium tangibly embodying computer-executable instructions, including instructions for:

receiving a request to compute a route from a start point to an end point;

computing the route using map data that includes a plurality of map elements, and route data that includes rules associated with the map elements, each of the rules being triggered by a condition flag that specifies a condition according to which the rule should be applied; and

specifying a precedence of at least one rule based on user inputs independent of real-time traffic data,

wherein the route data is based at least in part on user inputs related to driver experience in a geographic area associated with the route, and further wherein the user inputs are based on stored data and not real-time or near-real-time traffic data.

6. The medium of claim 5, the instructions further comprising instructions for collecting the route data via a webpage with a form.

7. The medium of claim 5, wherein the condition flag includes at least one of a time, a date, a weather condition, and an event.

8. The medium of claim 5, wherein the rules include at least one of a rule to avoid a map element and a rule to use a map element.

9. The medium of claim 5, wherein the map elements include at least one of a road, a street, a highway, an intersection, a bridge, and a building.

10. A system, comprising:

a computing device, including a processor and a memory, configured to;

receive a request to compute a route from a start point to an end point;

correlate a scheduled event at a venue with a map element to be avoided; and

compute the route using map data that includes a plurality of map elements, and route data that includes rules associated with the map elements, each of the rules being triggered by a condition flag that specifies a condition according to which the rule should be applied, at least one rule being triggered by the scheduled event to avoid the map element associated with the scheduled event;

wherein the route data is based at least in part on user inputs related to driver experience in a geographic area associated with the route associated with the scheduled event, and further wherein the user inputs are based on stored data and not real-time or near-real-time traffic data.

11. The device of claim 10, further configured to collect the route data via a graphical user interface.

12. The device of claim 10, further configured to collect the route data by analyzing data downloaded from one or more client devices.

13. The device of claim 10, wherein the map elements include at least one of a road, a street, a highway, an intersection, a bridge, and a building.

22. The system of claim 10, wherein the inputs related to driver experience in the geographic area are based at least in part on at least one interview or survey with a driver in the geographic area.