Patent Application
20070271034
The invention will be better understood from the following detailed description with reference to the drawings, in which:
The present invention and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. It should be noted that the features illustrated in the drawings are not necessarily drawn to scale. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the present invention. The examples used herein are intended merely to facilitate an understanding of ways in which the invention may be practiced and to further enable those of skill in the art to practice the invention. Accordingly, the examples should not be construed as limiting the scope of the invention.
This invention comprises an adaptive route planning system where the GPS system monitors driving and builds a database of the actual historical time to traverse any road segment and the time of day and day of the week when the trip was made. After a sufficient amount of data is collected, the GPS system can use this database to calculate the best route for a trip based on actual travel times over a road segment. The system could also transfer trip data to a computer allowing data from many different drivers to be aggregated (potentially in real-time). Individual drivers could share data to build up a useful database faster. Or a company could collect and aggregate data from many drivers in a particular locale to build a valuable database that could be sold.
Typically, the route segments that are identified in item 100 are those that are identified by the GPS route creation function which is a process that is well-known to those ordinarily skill in the art and is not discussed in detail herein (see U.S. Patent Publication 2006/0031566, for example). What comprises a route segment can vary from system to system (depending upon designers requirements) or even from user to user (if users are provided various options). For example, some embodiments herein can classify a route segment according to a predetermined distance (e.g., every 5 kilometers) or a predetermined time (e.g., every 10 minutes). Alternatively, a route segment can be identified as a portion of a route occurring between two connecting points, such as between successive turns, which would essentially define each individual street, road, highway, etc. as a route segment. Thus, as one example, each time a user was directed to turn onto a different street, highway, etc., a new route segment would begin. One ordinarily skill in the art would understand that route segments can be defined in many different ways and the invention is not limited to the specific examples presented herein.
In item 102, the method records an actual historical time of travel for at least one route segment as users of the GPS based navigation system travel. The actual historical time of travel comprises the amount of time taken by a user of the GPS based navigation system to go from a beginning of the route segment to an end of the route segment. Thus, for example, each time a user of the GPS system travels with the GPS system turned on, each segment of the route is timed to provide the actual historical time of travel for that route segment. If the route segment is traveled often at the same time of day, the actual historical times of travel can be statistically analyzed to provide mean, median, and other useful information for the database. Thus, for example, in one embodiment, the database would maintain an average historical time of travel for a given route segment.
With embodiments herein, the day, date, and time that the route segment was recorded is also noted in item 104. That is, item 104 records the day of the year (allowing holidays to be noted), day of the month, day of the week (weekend versus weekday) and other information to be recorded. Further, in item 104 the “time” can comprise as granular a measure as is desired by the designer or a user (depending upon the options given to the designer and user). Thus, the time of day can be simply classified as daytime versus nighttime. Alternatively, time of day can be classified as rush-hour versus non rush-hour. Similarly, the time of day can be broken down into multiple hour units, single hour units or fractional hour units. The decision of how to classify “time” depends upon the amount of information that will be collected in the database, the storage abilities of the database and the processing capability of the GPS system. Maintaining more information in a higher granular format may provide more exact results; however, this may also tax the resources of the GPS system unnecessarily. Therefore, the embodiments herein provide the designer/user with various options depending upon the specific application of the GPS system. Again, one ordinarily skill to the art would understand that the definitions of “route segments” “date/day” as well as “time” are not limited to the examples discuss herein, and the invention is equally applicable to all uses of such terminology.
Then, the actual historical time of travel and the date/day and time for the route segment can be stored in a database in item 106.
Once sufficient information is established in the database, the user can supply and the system can receive, as input, a beginning and an end of a desired route (e.g. a new route) in item 108. Typically, the GPS system knows its current location and the users are required to enter a new end location for a new desired route to be calculated, as is well-known by those ordinarily skill in the art. The then current day and time is also supplied or known by the GPS based navigation system in item 110.
From the historical records within the database of the different actual travel times for the different route segments, the method can then calculate a plurality of potential travel routes between the beginning and end of the desired route (each of the potential travel routes comprises the route segments stored in the database) in item 112. Subsequently, the method calculates an estimated travel time for each of the different potential travel routes using the actual historical time of travel of the route segments for the current day and time in item 114. The calculating of the estimated travel time comprises adding stored actual travel times for all route segments within each of the potential travel routes.
The amount of information required from the database for items 112 and 114 can be adjusted by the designer or user. For example, designer/user settings may require that all route segments have an actual historical time of travel recording for the current day and time before an estimate of the entire route can be made. Alternative embodiments can allow some of the route segments to not have an actual historical time of travel. For example, in one embodiment it may be required that a predetermined percentage of the length of the entire route has an actual historical time of travel (and that predetermined percentage can be less than 100 percent). In addition, other alternative embodiments of the invention can substitute actual historical travel times for other similar route segments (or for the same route segment for a different day or different time) to be used in place of route segments for which there is no actual historical travel time. Once again, one ordinarily skill in the art would understand that the invention is not limited to these specific examples of how the travel time for the entire route is estimated, but instead, many other similar options can be provided to allow the travel time for the entire route to the estimated (without knowing the actual historical time of travel for each route segment included within the completed route).
Then the method can identify a travel route that has a shortest estimated travel time for the current day and time to allow the user to know the fastest route that will be available for the current day and time in item 116.
Thus, as shown above, this invention comprises an adaptive route planning system where the GPS system monitors driving and builds a database of the actual historical time to traverse any road segment and the time of day and day of the week when the trip was made. After a sufficient amount of data is collected, the GPS system can use this database to calculate the best route for a trip based on actual travel times over a road segment. The system could also transfer trip data to a computer allowing data from many different drivers to be aggregated potentially in real-time.
While the invention has been described in terms of preferred embodiments, those skilled in the art will recognize that the invention can be practiced with modification within the spirit and scope of the appended claims.
