Autonomous vehicles may be configured to be driven in a manual mode (where the operator exercises a high degree of control over the movement of the vehicle) or in an autonomous mode (where the vehicle essentially drives itself). These vehicles use various computing systems to aid in the transport of passengers from one location to another. Some autonomous vehicles may require some initial input or continuous input from an operator, such as a pilot, driver, or passenger. Other systems, for example autopilot systems, may be used only when the system has been engaged, which permits the operator to switch from a manual mode to an autonomous mode and to modes that lie somewhere in between.
A vehicle with autonomous driving capability is configured to receive signal inputs from the sensors that monitor the vehicle operations, surrounding objects and road conditions in order to identify safety hazards and generate countermeasures to deal with various driving situations. The autonomous vehicle may also collect and record data from various information sources such as cellular network, satellites as well as user inputs such as users' identification, destinations and routes of navigation requests and vehicle operation preferences.
In one aspect, a method of determining a route for a vehicle is provided. It includes receiving data from a sensor affixed to a vehicle that senses, at one point in time, the environment surrounding the vehicle. It also includes accessing data stored in a memory that was previously sensed by a sensor affixed to the vehicle at an earlier point in time. A destination is determined from the received and accessed data and is identified to a user of the vehicle, such as by suggesting the destination.
In another aspect, a system includes a processor as well as a memory containing instructions. The processor is processor capable of executing instructions and is affixed to an autonomous vehicle. The memory contains instructions and data that are accessible by the processor. The data includes the output of a sensor affixed to the vehicle that was obtained by the vehicle both during the current trip and a trip earlier than the current trip. The instructions include: receiving a destination entered by a user determining an action to be performed by the vehicle (where the action is determined based on sensors that identify the location of a vehicle and sensors that do not identify the location of a vehicle) and recommending the action to the user.
In still another aspect, a method of recommending an action is provided. The method includes receiving the output of a first sensor affixed to a first vehicle, such that the output was captured during a first time frame. The first vehicle also receives the output of a second sensor affixed to a second vehicle, where that output was captured during a second time frame occurring after the first time frame. A processor affixed to the first vehicle determines a recommendation to be provided to the user based on the output of the first and second sensors. The recommendation relates to automatically navigating the first vehicle. The recommendation is provided to the user and the first vehicle performs the recommendation depending on whether the user provided an indication that the recommendation was accepted.
In one aspect, a system and method is provided wherein an autonomous vehicle makes recommendations to a user based on the conditions detected by the car's sensors. The recommendation may be based on both previous and currently sensed conditions, such as recommending a destination based on the location of prior long stops by the vehicle as well as the sensed weather conditions. The sensor data may be provided by other vehicles with sensors, and the recommendations may be communicated to other vehicles.
Although certain aspects of the invention are particularly useful in connection with specific types of vehicles, vehicle 101 may be any type of vehicle. Possible vehicles include, by way of example only, cars, trucks, motorcycles, busses, boats, airplanes, helicopters, lawnmowers, recreational vehicles, amusement park vehicles, trams, golf carts, trains and trolleys.
Vehicle 101 may include an autonomous vehicle computer system 130 that is in communication with sensors 140, navigation control 150, user input 160, user indicators 170 and external communication component 180.
Computer system 130 may comprise a computer containing a processor 131, memory 132 and other components typically present in general purpose computers.
The memory 132 stores information accessible by processor 131, including instructions 133 and data 134 that may be executed or otherwise used by the processor 131. The memory 132 may be of any type capable of storing information accessible by the processor, including a computer-readable medium, or other medium that stores data that may be read with the aid of an electronic device, such as a hard-drive, memory card, ROM, RAM, DVD or other optical disks, as well as other write-capable and read-only memories. Systems and methods may include different combinations of the foregoing, whereby different portions of the instructions and data are stored on different types of media.
The instructions 133 may be any set of instructions to be executed directly (such as machine code) or indirectly (such as scripts) by the processor. For example, the instructions may be stored as computer code on a computer-readable medium. In that regard, the terms “instructions” and “programs” may be used interchangeably herein. The instructions may be stored in object code format for direct processing by the processor, or in any other computer language including scripts or collections of independent source code modules that are interpreted on demand. Functions, methods and routines of the instructions are explained in more detail below.
The data 134 may be retrieved, stored or modified by processor 131 in accordance with the instructions 133. For instance, although the system and method is not limited by any particular data structure, the data may be stored in computer registers, in a relational database as a table having a plurality of different fields and records, XML documents or flat files. The data may also be formatted in any computer-readable format. By further way of example only, image data may be stored as bitmaps comprised of grids of pixels that are stored in accordance with formats that are compressed or uncompressed, lossless (e.g., BMP) or lossy (e.g., JPEG), and bitmap or vector-based (e.g., SVG), as well as computer instructions for drawing graphics. The data may comprise any information sufficient to identify the relevant information, such as numbers, descriptive text, proprietary codes, references to data stored in other areas of the same memory or different memories (including other network locations) or information that is used by a function to calculate the relevant data.
The processor 131 may be any conventional processor, such as processors from Intel Corporation or Advanced Micro Devices. Alternatively, the processor may be a dedicated device such as an ASIC. Although
Sensors
As shown in
Geographic location component 210 is used to determine the geographic location and orientation of the vehicle 101. For example, component 210 may include a GPS receiver 211 to determine the vehicle's latitude, longitude and/or altitude. Although references herein to the location of the vehicle will often refer to a location in latitude/longitude/altitude coordinates, the data representing the location of the vehicle may also be relative to other reference systems, such as the vehicle's distance from objects. Some reference systems may be subject to less noise than others.
The geographic location component may also include an inertial guidance system 212, which may in turn include an accelerometer 213 and gyroscope 214. The inertial guidance system 212 may determine the current orientation of the device and changes of speed in any direction. For example, the inertial guidance system 212 may detect when the vehicle is turning. It may also estimate the current location of the car relative to a starting location based on changes in speed and direction.
Other devices may also be used to determine the location of the vehicle 101. For example, if the external object detector 220 identifies an object and its location relative to the vehicle, and if processor 131 can access pre-existing data that identifies the geographic location of the object, then processor 131 can identify the geographic location of the vehicle. The system may also triangulate its location based on cell phone tower transmissions or the presence of smaller wireless networks. The processor may combine the information from the various components and detectors, or select the most accurate source, and determine the geographic location of the vehicle accordingly.
The vehicle may include an external object detection system 220 for detecting objects external to the vehicle such as other vehicles, obstacles in the roadway, traffic signals, signs, trees, etc. The detection system 220 may include a laser 221, radar 222, cameras 223, sonar 224 or and other detection devices.
Vehicle 101 may include a laser 221 mounted on the roof or other convenient location. In one aspect, the laser may measure the distance between the vehicle and object surfaces facing the vehicle by spinning on its axis and changing its pitch. The laser may also be used to identify changes in surface texture or reflectivity. Thus, the laser may be configured to detect lane lines by distinguishing between the amount of light reflected by a painted lane line relative to unpainted dark pavement.
Sensors 140 may further include various radar detection units 222, such as those used for adaptive cruise control systems. The radar detection units may be located on the front and back of the car as well as on either side of the front bumper. In addition to using radar to determine the relative location of external objects, other types of radar may be used for other purposes as well, such as conventional speed detection. Short wave radar may be used to determine the depth of snow on the road and to determine location and condition of the road surface.
One of the sensors may also include one or more cameras 223. If multiple cameras are used and the distances from each other are known, the parallax from the different images may be used to compute the distance to various objects which are captured by the cameras. Content may also be extracted from the images. For example, the vehicle may automatically slow down if its current speed is 50 mph and it detects, by using its cameras and using optical-character recognition, that it will shortly pass a sign indicating that the speed limit is 35 mph. Yet further, pattern matching and other feature detection algorithms may be used to determine the type of the object.
Ambient sensors 240 may determine environmental aspects that do not specifically relate to external object detection, such as air quality sensors for detecting the surrounding air's temperature, humidity, or particulates.
Sensors 140 may also include sensors for determining the state of the user, such as the driver and other passengers in a car. For example, passenger sensors 250 may include a video camera that is used to determine whether the driver is asleep. Other sensors may determine the state of the interior of the car such as interior temperature, humidity, seat and mirror positions, weight measurements and distributions of the occupants (driver and passengers).
Although not shown in
The sensors may output their determinations to computer system 130. The system and method permits various data configurations between the computer system and the sensors. The sensors may provide the data in relatively raw low-level form or independently process the sensed information and provide relatively high-level data. Many of these sensors provide data that is processed by the computer in real-time, that is, the sensors may continuously update their output and continuously or as-demanded provide that updated output to the computer system 130. Thus, some of the sensors may instantaneously provide information that can be directly processed by the processor of the central control, such as a self-contained speed radar detector. Other sensors may require the processor to process data received from the sensor over a range of time, e.g., determining the speed of an object by comparing changes in its position based on the output of laser 221.
The vehicle further includes navigation controls 150, at least some of which operate at the direction of processor 131. For example, a car's navigation controls may include steering, brakes, fuel throttle (e.g., accelerator), turn signals, and other systems that control the movement and speed of vehicle 101. In addition, when engaged, computer 110 may control some or all of these functions of vehicle 101 and thus be fully or partially autonomous. In that regard, central control 130 may maneuver the car in response to information from the sensors, such as using the external object detector 220 to avoid hitting external objects and using the data provided by geographic location component 210 to avoid objects. The vehicle may also have various user input devices for activating or deactivating one or more autonomous driving modes. In some aspects, the driver may take control of the vehicle from the computer system by turning the steering wheel, pressing the acceleration or deceleration pedals.
As shown in
The vehicle may also include a variety of devices for communicating information to a user. For instance, the interior of vehicle 101 may include an electronic display 325 (e.g., a monitor having a screen, a small LCD touch-screen or any other electrical device that is operable to display information). It may further include a status indicating apparatus, such as status bar 330, to indicate the current status of vehicle 101. In the example of
Among other things, display 325 may display other information relating to the overall status of the vehicle, particular sensors, or computer system 130. The display 325 may include computer generated images of the vehicle's surroundings including, for example, the status of the computer, the vehicle itself, roadways, intersections, as well as other objects and information. Computer system 330 may further use visual or audible cues to indicate whether the computer system is obtaining valid data from the various sensors, whether the computer is partially or completely controlling the direction or speed of the car or both, whether there are any errors, etc.
As shown in
In addition to the operations illustrated in
The above and following data propagation, collection, processing and recommendations may be controlled under vehicle users' permissions. The users may allow, disallow, or control the level of data sharing with other vehicles and third parties.
Based on data collected locally and from other vehicles, the computer system on vehicle 101 may process the data and make various kinds of recommendations to the user and recommendations to third parties. Recommendations may be made based on data collected solely from and processed by the user's vehicle.
In one aspect, the system and method makes recommendations based both on data that was previously collected by the sensors and, at the time of the recommendation, is currently being collected by the sensors.
POI based on what has been visited in the past
For example, computer system 131 may provide the user with a recommended point of interest (POI) to visit. At the user's request, processor 131 may select the destination by consulting the data it received from geographic location component 210 the last time the vehicle was in the current geographic area. Processor 131 may then compare its current location with how long vehicle 101 has stayed at a particular POI, such as a restaurant. Depending on the average amount of time that the user stayed at a particular place, and based further on the vehicle's current position, processor 131 may then recommend a specific restaurant or other POI. By way of example, if the vehicle is currently near a POI that the user has previously stayed at for 30 minutes or more, the vehicle may identify the recommended destination and ask the user if they would like to be brought to the POI.
The recommended action may be performed automatically. Continuing the foregoing example, vehicle 101 may automatically bring the user to the recommended destination if the user indicates to the vehicle that he or she accepts the recommendation.
Prior to receiving a recommendation, the user may enter destination information into computer system 130, and the vehicle may suggest a route based on the current location provided by the geographic location component and map data that is available to the computer system. The user's designated destination may be used when making the recommendation, e.g., recommending POI near the destination.
In addition to recommending points of interest depending on information received from the sensors, the vehicle may also recommend locations to avoid. For instance, the data collected by vehicle 302 may indicate a pattern of avoiding certain commercial districts during a specific time of day. As such, the computer system may recommend that the user avoid certain routes or areas during that time based on the starting and destination address entered by the user in a navigation request.
The system and method may base its recommendation on prior sensor data may have been captured a significant amount of time before the current sensor data. For example, the system and method may rely on data that was collected well prior to the currently sensed data while travelling along the then-current route. It may evaluate data that was taken at least a specific time period in advance, e.g., at least one day before the moment the latest sensor data was captured. It may also evaluate data that was collected while the vehicle was travelling along a different route. The prior data may also have occurred while the vehicle was travelling the same route but on an earlier different trip (e.g., the car took the same streets between the same origination and destination earlier in the day).
Recommendations may be made based on data collected from other vehicles as well as the data collected locally from the vehicle. By way of example,
The information transmitted between vehicles may include the data output from the sensors to the computer system 131 or may comprise more processed information. By way of example, vehicle 402 may transmit relatively raw sensor data such as the signals acquired by laser 221. Alternatively, if vehicle 402 identified a particular object based on the laser data, the vehicle may transmit the type of detected object and its location relative to vehicle 401 after the computer system 131 identifies the object.
The vehicle may generate a recommendation based on information provided by both the other vehicle and the current vehicle. For example, processor of vehicle 401 may consider its previously sensed data (e.g., the average times that vehicle 401 has spent at different restaurants), its currently sensed data (e.g., its current location) and the currently sensed data from another vehicle (e.g., the amount of snow at the location of vehicle 402) when generating a recommendation (e.g., going to a different restaurant than the one requested by the user if the weather conditions are bad at the location near the requested restaurant). In that regard, the recommended action may be determined based on the sensors (e.g., GPS receivers) that identify the current and past location of the car, as well as sensors that do not identify the location of the car (e.g., road conditions).
The vehicle may also rely on data previously sensed by another vehicle. For instance, vehicle 402 may also transmit the amount of snow it encountered at previous locations, some of which may be visited or will soon be visited by vehicle 401.
An autonomous vehicle may also generate recommendations based on the data obtained from multiple vehicles. For example, vehicle 401 may also receive and use the current conditions at vehicle 403 in order to provide a recommendation to the user of vehicle 401.
In addition to directly communicating with other vehicles, the vehicle may obtain sensor data from other vehicles via the use of intermediate transmitters and receivers that are stationary. For instance, the vehicle may access a database containing sensor data obtained from other vehicles. As shown in
In addition to transmitting sensor data to other vehicles, a vehicle may also transmit recommendations. For example, vehicle 401 may recommend to vehicle 402 that it take a different course if it appears that vehicle 402 is headed to an unsafe location. If vehicle 401 is in communication with vehicle 404, vehicle 401 may transmit the same recommendation 445 to vehicle 404. It may also transmit the sensor data 441 from vehicle 402 to vehicle 404, effectively functioning as an intermediary for the sensor data from vehicle 402. In that regard, sensor data may be gathered and recommendations generated and transmitted between vehicles without the use of stationary base stations. The vehicles may also transfer information to each other via a stationary wireless network, particularly if the distance between the vehicles makes it difficult to establish a direct connection. In that regard, vehicle 401 may transmit its sensor data 447 and recommendations 446 to vehicle 405 by wireless connecting to Internet 495 via wireless carrier 460.
The system and method may provide routing-related recommendations based on other data as well. For example, by accruing sensor data over a time period, the computer system on vehicle 101 may derive the traffic densities, cross-roads, pedestrian distributions, busy corners and various other features for a particular neighborhood or a geographic boundary. Based on such data, as well as the user's past driving routes, the system may make various recommendations of nearby POIs or recommend certain routes to avoid. The recommendations may relate to alternative routes, i.e., presenting different combinations of streets to get to a specific destination.
Vehicle 401 may use the data to determine how to maneuver the vehicle (e.g., slowing down based on turns or traffic jams detected by other vehicles, taking an alternative route, or taking an evasive action to avoid an object such as a deer).
A vehicle may also choose to use data from other sources for its recommendations if the source is considered trustworthy. For example, different vehicles may be associated with different vendors, and a first vehicle might only trust the data sent from a second vehicle if the second vehicle cryptographically signed the data, and if the first vehicle can verify the signature. Moreover, the vehicle may perform different maneuvers based on different levels of trust. For instance, information from vehicles from unknown vendors may only be used for slowing the user's vehicle down but information from trusted vendor vehicles may be used for slowing the user's vehicle down and changing lanes. If received data has some indicia that implies that the source is counterfeit or otherwise not trustworthy, the data might not be used at all or only used to add weight to a factor that is consistent with already-sensed data.
The vehicles may exchange other information that does not correspond with the information obtained by the sensors and use such information when generating a recommendation. By way of example, vehicles 402 and 403 may transmit their user profile along with their sensor data 441 and 442, respectively. Vehicle 401 may compare that user profile with its own user's profile when basing a recommendation on data provided by vehicle 402. In that regard, if vehicle 401 is generating a route recommendation based on the routes travelled by vehicles 402 and 403, vehicle 401 may allocate additional weight to the route travelled by the vehicle with the most similar user profile. It may also allocate more weight to information received from vehicles of a similar type regardless of the profile of the user.
The user profile information may comprise any information that is related to the user. For example, in response to a prompt from the computer 130, the user may be asked to enter user identification (e.g., the driver's name or a reference number) and/or other user attribute data such as gender and age. The profile information may also include various user preferences such as preference for vehicle operation (e.g., warning when vehicles in adjacent lanes move within a predetermined safety distance), preference for vehicle interior conditions (e.g., seat positions or vehicle temperatures), and route or navigation preference (e.g., a preferred route to a specific destination during a specific time, and making one or more specific stops along the route), etc. This information may be used by vehicle 101 without regard to other vehicles, e.g., the computer system 130 may ascribe more weight to weather conditions when a user has indicated a relatively low tolerance for driving in less than optimal conditions.
The autonomous vehicle may make unsolicited recommendations in addition to responding to requests from the user. For example, if the data from vehicle 402 indicates that the road conditions near an intended destination POI are unsafe, vehicle 401 may—without prompting—display a message to the user recommending a different POI.
The recommendations may also be made to various interested third parties, for example, business (restaurants, shops, etc.) owners and market survey providers. These third parties may also be provided with options to subscribe to receiving recommendations from various autonomous vehicles. In that regard, the recommendations may be provided to data repository 470, which in turn provides the recommendations to the third parties. Third parties may also be provided with the raw data collected by the sensors (with the user's permission, as noted above).
In one aspect, third parties may locate businesses based on the aggregation of the raw data. For example, a fueling station operator may, based on the number of vehicles driven within a particular geographic region and the fuel levels of these vehicles, make decisions as to whether to build a gas station in the region.
In another aspect, autonomous vehicle service providers may adjust pricing to use the autonomous vehicle based on these data. Governments may also make various public service deployment decisions (e.g., road or neighborhood development, expenditure or infrastructure allocations) based on the sensor data. The information may also be used by service providers, such as map providers, to update their databases and make any changes available to other autonomous vehicles, for example, by transmitting the information automatically or by making available downloadable updates.
The recommendations may be provided to the user in variety of ways. For example, the recommendation may be shown on display 325 as shown in
The information from the sensors may be used to change the current path and speed of the vehicle. The data from the sensors permits the central control 130 to determine whether the vehicle's then-current direction or speed should be modified in response to the sensed environment. By way of example, if the vehicle is operating in a completely autonomous mode, computer system 130 may cause the vehicle to accelerate (e.g., by increasing fuel or other energy provided to the engine), decelerate (e.g., by decreasing the fuel supplied to the engine or by applying brakes) and change direction (e.g., by turning the front two wheels). For instance, if the computer determines that an object is obstructing the intended path of the vehicle, it may slow down and maneuver the vehicle around the obstruction.
The vehicle may continuously use the sensor data to identify objects, such as traffic signals, people, other vehicles, and other objects, in order to maneuver the vehicle to the destination and reduce the likelihood of a collision. The vehicle may use the map data to determine where traffic signals or other objects should appear and take actions, for example, by signally turns or changing lanes.
In addition to processing data provided by the various sensors, the computer may rely on environmental data that was obtained at a previous point in time and is expected to persist regardless of the vehicle's presence in the environment. For example, data 134 may include detailed map information, e.g., highly detailed maps identifying the shape and elevation of roadways, lane lines, intersections, crosswalks, speed limits, traffic signals, buildings, signs, real time traffic information, or other such objects and information. Each of these objects such as lane lines or intersections may be associated with a geographic location which is highly accurate, for example, to 15 cm or even 1 cm. The map information may also include, for example, explicit speed limit information associated with various roadway segments. The speed limit data may be entered manually or scanned from previously taken images of a speed limit sign using, for example, optical-character recognition. The map information may include three-dimensional terrain maps incorporating one or more of objects listed above. For example, the vehicle may determine that another car is expected to turn based on real-time data (e.g., using its sensors to determine the current GPS position of another car) and other data (e.g., comparing the GPS position with previously-stored lane-specific map data to determine whether the other car is within a turn lane).
It will be further understood that the sample values, types and configurations of data described and shown in the figures are for the purposes of illustration only. In that regard, systems and methods in accordance with aspects of the invention may include various types of sensors, communication devices, user interfaces, vehicle control systems, data values, data types and configurations. The systems and methods may be provided and received at different times (e.g., via different servers or databases) and by different entities (e.g., some values may be pre-suggested or provided from different sources).
As these and other variations and combinations of the features discussed above can be utilized without departing from the systems and methods as defined by the claims, the foregoing description of exemplary embodiments should be taken by way of illustration rather than by way of limitation of the invention as defined by the claims. It will also be understood that the provision of examples of the invention (as well as clauses phrased as “such as,” “e.g.”, “including” and the like) should not be interpreted as limiting the invention to the specific examples; rather, the examples are intended to illustrate only some of many possible aspects. Unless expressly stated to the contrary, every feature in a given embodiment, alternative or example may be used in any other embodiment, alternative or example herein.
The present application is a continuation of U.S. patent application Ser. No. 15/488,836, filed on Apr. 17, 2017, which is a continuation of U.S. patent application Ser. No. 14/727,273, filed on Jun. 1, 2015, which is a continuation of U.S. patent application Ser. No. 13/252,568, filed on Oct. 4, 2011, which claims the benefit of the filing dates of U.S. Provisional Application No. 61/390,094, entitled “AUTONOMOUS VEHICLES,” filed Oct. 5, 2010, and U.S. Provisional Application No. 61/391,271, entitled “AUTONOMOUS VEHICLES,” filed Oct. 8, 2010, the entire disclosures of which are hereby incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
1924984 | Fageol | Aug 1933 | A |
3186508 | Lamont | Jun 1965 | A |
3324805 | Mulch | Jun 1967 | A |
3411139 | Lynch et al. | Nov 1968 | A |
3596728 | Neville | Aug 1971 | A |
4372414 | Anderson | Feb 1983 | A |
4387783 | Carman | Jun 1983 | A |
4656834 | Elpern | Apr 1987 | A |
4924795 | Ottemann | May 1990 | A |
4970653 | Kenue | Nov 1990 | A |
4982072 | Takigami | Jan 1991 | A |
5187666 | Watanabe | Feb 1993 | A |
5415468 | Latarnik | May 1995 | A |
5448487 | Arai | Sep 1995 | A |
5470134 | Toepfer et al. | Nov 1995 | A |
5521579 | Bernhard | May 1996 | A |
5684696 | Rao et al. | Nov 1997 | A |
5774069 | Tanaka et al. | Jun 1998 | A |
5790403 | Nakayama | Aug 1998 | A |
5906645 | Kagawa et al. | May 1999 | A |
5913376 | Takei | Jul 1999 | A |
5954781 | Slepian et al. | Sep 1999 | A |
6055042 | Sarangapani | Apr 2000 | A |
6064926 | Sarangapani et al. | May 2000 | A |
6070682 | Isogai et al. | Jun 2000 | A |
6151539 | Bergholz et al. | Nov 2000 | A |
6195610 | Kaneko | Feb 2001 | B1 |
6226570 | Hahn | May 2001 | B1 |
6321147 | Takeda et al. | Nov 2001 | B1 |
6332354 | Lalor et al. | Dec 2001 | B1 |
6343247 | Jitsukata et al. | Jan 2002 | B2 |
6385539 | Wilson et al. | May 2002 | B1 |
6414635 | Stewart et al. | Jul 2002 | B1 |
6438472 | Tano et al. | Aug 2002 | B1 |
6438491 | Farmer | Aug 2002 | B1 |
6453056 | Laumeyer et al. | Sep 2002 | B2 |
6470874 | Mertes | Oct 2002 | B1 |
6504259 | Kuroda | Jan 2003 | B1 |
6516262 | Takenaga et al. | Feb 2003 | B2 |
6560529 | Janssen | May 2003 | B1 |
6591172 | Oda et al. | Jul 2003 | B2 |
6606557 | Kotzin | Aug 2003 | B2 |
6643576 | O Connor et al. | Nov 2003 | B1 |
6832156 | Farmer | Dec 2004 | B2 |
6836719 | Andersson et al. | Dec 2004 | B2 |
6847869 | Dewberry et al. | Jan 2005 | B2 |
6859009 | Jablin | Feb 2005 | B2 |
6862524 | Nagda | Mar 2005 | B1 |
6876908 | Cramer et al. | Apr 2005 | B2 |
6934613 | Yun | Aug 2005 | B2 |
6963657 | Nishigaki et al. | Nov 2005 | B1 |
7011186 | Frentz et al. | Mar 2006 | B2 |
7031829 | Nisiyama | Apr 2006 | B2 |
7085633 | Nishira et al. | Aug 2006 | B2 |
7102496 | Ernst, Jr. et al. | Sep 2006 | B1 |
7177760 | Kudo | Feb 2007 | B2 |
7194347 | Harumoto et al. | Mar 2007 | B2 |
7207304 | Lwatsuki | Apr 2007 | B2 |
7233861 | Van Buer et al. | Jun 2007 | B2 |
7327242 | Holloway et al. | Feb 2008 | B2 |
7340332 | Underdahl | Mar 2008 | B2 |
7346439 | Bodin | Mar 2008 | B2 |
7373237 | Wagner et al. | May 2008 | B2 |
7394046 | Olsson et al. | Jul 2008 | B2 |
7486802 | Hougen | Feb 2009 | B2 |
7499774 | Barrett et al. | Mar 2009 | B2 |
7499776 | Allard et al. | Mar 2009 | B2 |
7499804 | Svendsen et al. | Mar 2009 | B2 |
7515101 | Bhogal et al. | Apr 2009 | B1 |
7565241 | Tauchi | Jul 2009 | B2 |
7579942 | Kalik | Aug 2009 | B2 |
7656280 | Hines et al. | Feb 2010 | B2 |
7694555 | Howell et al. | Apr 2010 | B2 |
7778759 | Tange et al. | Aug 2010 | B2 |
7818124 | Herbst et al. | Oct 2010 | B2 |
7835859 | Bill | Nov 2010 | B2 |
7865277 | Larson et al. | Jan 2011 | B1 |
7894951 | Norris et al. | Feb 2011 | B2 |
7908040 | Howard et al. | Mar 2011 | B2 |
7956730 | White et al. | Jun 2011 | B2 |
7979175 | Allard et al. | Jul 2011 | B2 |
8024102 | Swoboda et al. | Sep 2011 | B2 |
8050863 | Trepagnier et al. | Nov 2011 | B2 |
8078349 | Prada Gomez et al. | Dec 2011 | B1 |
8095313 | Blackburn | Jan 2012 | B1 |
8099213 | Zhang et al. | Jan 2012 | B2 |
8126642 | Trepagnier et al. | Feb 2012 | B2 |
8190322 | Lin et al. | May 2012 | B2 |
8194927 | Zhang et al. | Jun 2012 | B2 |
8195341 | Huang et al. | Jun 2012 | B2 |
8244408 | Lee et al. | Aug 2012 | B2 |
8244458 | Blackburn | Aug 2012 | B1 |
8260515 | Huang et al. | Sep 2012 | B2 |
8280601 | Huang et al. | Oct 2012 | B2 |
8280623 | Trepagnier et al. | Oct 2012 | B2 |
8311274 | Bergmann et al. | Nov 2012 | B2 |
8352111 | Mudalige | Jan 2013 | B2 |
8352112 | Mudalige | Jan 2013 | B2 |
8368558 | Salowitz | Feb 2013 | B2 |
8412449 | Trepagnier et al. | Apr 2013 | B2 |
8452506 | Groult | May 2013 | B2 |
8457827 | Ferguson | Jun 2013 | B1 |
8634980 | Urmson et al. | Jan 2014 | B1 |
8694236 | Takagi | Apr 2014 | B2 |
8706394 | Trepagnier et al. | Apr 2014 | B2 |
8718861 | Montemerlo et al. | May 2014 | B1 |
8724093 | Sakai et al. | May 2014 | B2 |
8775063 | Zeng | Jul 2014 | B2 |
8831813 | Ferguson et al. | Sep 2014 | B1 |
8855860 | Isaji et al. | Oct 2014 | B2 |
8874267 | Dolgov et al. | Oct 2014 | B1 |
8880270 | Ferguson et al. | Nov 2014 | B1 |
8918277 | Niem et al. | Dec 2014 | B2 |
8929604 | Platonov et al. | Jan 2015 | B2 |
8948954 | Ferguson | Feb 2015 | B1 |
8949016 | Ferguson et al. | Feb 2015 | B1 |
8970397 | Nitanda et al. | Mar 2015 | B2 |
8972093 | Joshi | Mar 2015 | B2 |
9008369 | Schofield et al. | Apr 2015 | B2 |
9062979 | Ferguson et al. | Jun 2015 | B1 |
9063548 | Ferguson | Jun 2015 | B1 |
9081383 | Montemerlo et al. | Jul 2015 | B1 |
9182759 | Wimmer et al. | Nov 2015 | B2 |
9248834 | Ferguson et al. | Feb 2016 | B1 |
9669827 | Ferguson et al. | Jun 2017 | B1 |
9811085 | Hayes | Nov 2017 | B1 |
9914452 | Ferguson et al. | Mar 2018 | B1 |
20010024095 | Fitzgibbon et al. | Sep 2001 | A1 |
20010037927 | Nagler | Nov 2001 | A1 |
20020188499 | Jenkins | Dec 2002 | A1 |
20030014302 | Jablin | Jan 2003 | A1 |
20030016804 | Sheha | Jan 2003 | A1 |
20030037977 | Tatara et al. | Feb 2003 | A1 |
20030055554 | Shioda | Mar 2003 | A1 |
20030093209 | Andersson et al. | May 2003 | A1 |
20030125963 | Haken | Jul 2003 | A1 |
20040243292 | Roy | Dec 2004 | A1 |
20050012589 | Kokubu | Jan 2005 | A1 |
20050099146 | Nishikawa et al. | May 2005 | A1 |
20050125154 | Kawasaki | Jun 2005 | A1 |
20050131645 | Panopoulos | Jun 2005 | A1 |
20050149251 | Donath et al. | Jul 2005 | A1 |
20050216184 | Ehlers | Sep 2005 | A1 |
20050273251 | Nix | Dec 2005 | A1 |
20060037573 | Lwatsuki | Feb 2006 | A1 |
20060082437 | Yuhara | Apr 2006 | A1 |
20060089764 | Filippov et al. | Apr 2006 | A1 |
20060089765 | Pack et al. | Apr 2006 | A1 |
20060089800 | Svendsen et al. | Apr 2006 | A1 |
20060116801 | Shirley et al. | Jun 2006 | A1 |
20060173841 | Bill et al. | Aug 2006 | A1 |
20060178240 | Hansel | Aug 2006 | A1 |
20060276942 | Anderson | Dec 2006 | A1 |
20070010942 | Bill | Jan 2007 | A1 |
20070024501 | Yeh | Feb 2007 | A1 |
20070112477 | Van Zanten et al. | May 2007 | A1 |
20070142992 | Gronau et al. | Jun 2007 | A1 |
20070149214 | Walsh | Jun 2007 | A1 |
20070165910 | Nagaoka et al. | Jul 2007 | A1 |
20070193798 | Allard et al. | Aug 2007 | A1 |
20070203617 | Haug | Aug 2007 | A1 |
20070225909 | Sakano | Sep 2007 | A1 |
20070239331 | Kaplan | Oct 2007 | A1 |
20070247281 | Shimomura | Oct 2007 | A1 |
20070279250 | Kume et al. | Dec 2007 | A1 |
20080021628 | Tryon | Jan 2008 | A1 |
20080033615 | Khajepour et al. | Feb 2008 | A1 |
20080039991 | May et al. | Feb 2008 | A1 |
20080040039 | Takagi | Feb 2008 | A1 |
20080056535 | Bergmann et al. | Mar 2008 | A1 |
20080059015 | Whittaker et al. | Mar 2008 | A1 |
20080059048 | Kessler | Mar 2008 | A1 |
20080084283 | Kalik | Apr 2008 | A1 |
20080089556 | Salgian et al. | Apr 2008 | A1 |
20080120025 | Naitou et al. | May 2008 | A1 |
20080120171 | Ikeuchi et al. | May 2008 | A1 |
20080147253 | Breed | Jun 2008 | A1 |
20080161987 | Breed | Jul 2008 | A1 |
20080167771 | Whittaker et al. | Jul 2008 | A1 |
20080183512 | Benzinger | Jul 2008 | A1 |
20080188246 | Sheha | Aug 2008 | A1 |
20080195268 | Sapilewski et al. | Aug 2008 | A1 |
20080277183 | Huang | Nov 2008 | A1 |
20080303696 | Aso et al. | Dec 2008 | A1 |
20080306969 | Mehta et al. | Dec 2008 | A1 |
20090005959 | Bargman et al. | Jan 2009 | A1 |
20090010494 | Bechtel et al. | Jan 2009 | A1 |
20090074249 | Moed et al. | Mar 2009 | A1 |
20090082879 | Dooley et al. | Mar 2009 | A1 |
20090115594 | Han | May 2009 | A1 |
20090150489 | Davis | Jun 2009 | A1 |
20090164071 | Takeda | Jun 2009 | A1 |
20090198400 | Allard et al. | Aug 2009 | A1 |
20090248231 | Tsuyoshi | Oct 2009 | A1 |
20090276154 | Subramanian | Nov 2009 | A1 |
20090287367 | Salinger | Nov 2009 | A1 |
20090287368 | Bonne | Nov 2009 | A1 |
20090306834 | Hjelm et al. | Dec 2009 | A1 |
20090313077 | Wheeler, IV | Dec 2009 | A1 |
20090313095 | Hurpin | Dec 2009 | A1 |
20090319096 | Offer et al. | Dec 2009 | A1 |
20090319112 | Fregene et al. | Dec 2009 | A1 |
20090322872 | Muehlmann et al. | Dec 2009 | A1 |
20090326799 | Crook | Dec 2009 | A1 |
20100010699 | Taguchi et al. | Jan 2010 | A1 |
20100014714 | Zhang et al. | Jan 2010 | A1 |
20100017056 | Asakura | Jan 2010 | A1 |
20100042282 | Taguchi | Feb 2010 | A1 |
20100052945 | Breed | Mar 2010 | A1 |
20100066587 | Yamauchi et al. | Mar 2010 | A1 |
20100076640 | Maekawa et al. | Mar 2010 | A1 |
20100079590 | Kuehnle et al. | Apr 2010 | A1 |
20100179715 | Puddy | Jul 2010 | A1 |
20100179720 | Lin et al. | Jul 2010 | A1 |
20100191433 | Groult | Jul 2010 | A1 |
20100198491 | Mays | Aug 2010 | A1 |
20100205132 | Taguchi et al. | Aug 2010 | A1 |
20100207787 | Catten et al. | Aug 2010 | A1 |
20100228419 | Lee et al. | Sep 2010 | A1 |
20100241297 | Aoki | Sep 2010 | A1 |
20100253542 | Seder et al. | Oct 2010 | A1 |
20100256836 | Mudalige | Oct 2010 | A1 |
20100265354 | Kameyama | Oct 2010 | A1 |
20110010131 | Miyajima et al. | Jan 2011 | A1 |
20110040481 | Trombley et al. | Feb 2011 | A1 |
20110071718 | Norris et al. | Mar 2011 | A1 |
20110099040 | Felt et al. | Apr 2011 | A1 |
20110137520 | Rector et al. | Jun 2011 | A1 |
20110150348 | Anderson | Jun 2011 | A1 |
20110206273 | Plagemann et al. | Aug 2011 | A1 |
20110210866 | David et al. | Sep 2011 | A1 |
20110213511 | Msconti et al. | Sep 2011 | A1 |
20110239146 | Dutta | Sep 2011 | A1 |
20110246156 | Zecha et al. | Oct 2011 | A1 |
20110254655 | Maalouf | Oct 2011 | A1 |
20110264317 | Druenert et al. | Oct 2011 | A1 |
20120053775 | Nettleton et al. | Mar 2012 | A1 |
20120069185 | Stein | Mar 2012 | A1 |
20120078723 | Stewart | Mar 2012 | A1 |
20120083960 | Zhu et al. | Apr 2012 | A1 |
20120114178 | Platonov et al. | May 2012 | A1 |
20120157052 | Quade | Jun 2012 | A1 |
20120271483 | Samukawa et al. | Oct 2012 | A1 |
20120277947 | Boehringer et al. | Nov 2012 | A1 |
20120283912 | Lee et al. | Nov 2012 | A1 |
20120314070 | Zhang | Dec 2012 | A1 |
20130035821 | Bonne et al. | Feb 2013 | A1 |
20130054049 | Uno | Feb 2013 | A1 |
20130054106 | Schmudderich et al. | Feb 2013 | A1 |
20130054128 | Moshchuk et al. | Feb 2013 | A1 |
20130061181 | Arrasvuori | Mar 2013 | A1 |
20130144520 | Ricci | Jun 2013 | A1 |
20130166206 | Nagase | Jun 2013 | A1 |
20130179382 | Fritsh et al. | Jul 2013 | A1 |
20130282277 | Rubin et al. | Oct 2013 | A1 |
20130321400 | Van Os et al. | Dec 2013 | A1 |
20130321422 | Pahwa et al. | Dec 2013 | A1 |
20140067187 | Ferguson et al. | Mar 2014 | A1 |
20140088855 | Ferguson et al. | Mar 2014 | A1 |
20140117933 | Nyu | May 2014 | A1 |
20140139369 | Baba | May 2014 | A1 |
20140156164 | Schuberth et al. | Jun 2014 | A1 |
20140180543 | Ueda et al. | Jun 2014 | A1 |
20140195138 | Stelzig et al. | Jul 2014 | A1 |
20140214255 | Dolgov et al. | Jul 2014 | A1 |
20140309870 | Ricci | Oct 2014 | A1 |
20140350836 | Stettner et al. | Nov 2014 | A1 |
20140369168 | Max et al. | Dec 2014 | A1 |
20150112571 | Schmudderich | Apr 2015 | A1 |
20150153735 | Clarke et al. | Jun 2015 | A1 |
20150177007 | Su et al. | Jun 2015 | A1 |
20150198951 | Thor et al. | Jul 2015 | A1 |
20150203107 | Lippman et al. | Jul 2015 | A1 |
20150293216 | O'Dea et al. | Oct 2015 | A1 |
20150302751 | Strauss | Oct 2015 | A1 |
20160086285 | Jordan Peters et al. | Mar 2016 | A1 |
20160170998 | Frank | Jun 2016 | A1 |
20160171620 | Bogovich et al. | Jun 2016 | A1 |
20160327947 | Ishikawa | Nov 2016 | A1 |
20160334230 | Ross | Nov 2016 | A1 |
20160334797 | Ross | Nov 2016 | A1 |
20170098176 | Hirose | Apr 2017 | A1 |
20170337571 | Bansal | Nov 2017 | A1 |
20170370735 | Salowitz | Dec 2017 | A1 |
20180189918 | Lu | Jul 2018 | A1 |
20180238705 | O'Herlihy | Aug 2018 | A1 |
Number | Date | Country |
---|---|---|
101073018 | Nov 2007 | CN |
101364111 | Feb 2009 | CN |
101522493 | Sep 2009 | CN |
10052816 | May 2002 | DE |
10218010 | Nov 2003 | DE |
10336986 | Mar 2005 | DE |
102008014771 | Sep 2009 | DE |
102009010006 | Oct 2009 | DE |
102008023380 | Nov 2009 | DE |
0884666 | Dec 1998 | EP |
2042405 | Apr 2009 | EP |
2060455 | May 2009 | EP |
2216225 | Aug 2010 | EP |
2692064 | Dec 1993 | FR |
H05246635 | Sep 1993 | JP |
H08110998 | Apr 1996 | JP |
09160643 | Jun 1997 | JP |
H09-161196 | Jun 1997 | JP |
H09166209 | Jun 1997 | JP |
09-066853 | Nov 1997 | JP |
11-39598 | Feb 1999 | JP |
11282530 | Oct 1999 | JP |
2000149188 | May 2000 | JP |
2000305625 | Nov 2000 | JP |
2000-38008 | Dec 2000 | JP |
2001101599 | Apr 2001 | JP |
2002236993 | Aug 2002 | JP |
2002251690 | Sep 2002 | JP |
2003081039 | Mar 2003 | JP |
2003162799 | Jun 2003 | JP |
2003-205804 | Jul 2003 | JP |
2004-206510 | Jul 2004 | JP |
2004-326730 | Nov 2004 | JP |
2004345862 | Dec 2004 | JP |
2005062912 | Mar 2005 | JP |
2005067483 | Mar 2005 | JP |
2005071114 | Mar 2005 | JP |
2005297621 | Oct 2005 | JP |
2005339181 | Dec 2005 | JP |
2006264530 | Oct 2006 | JP |
2006322752 | Nov 2006 | JP |
2007001475 | Jan 2007 | JP |
2007-022135 | Feb 2007 | JP |
2000-193471 | Jul 2007 | JP |
2007331458 | Dec 2007 | JP |
2008087545 | Apr 2008 | JP |
2008117082 | May 2008 | JP |
2008152655 | Jul 2008 | JP |
2008170404 | Jul 2008 | JP |
2008213581 | Sep 2008 | JP |
2008257652 | Oct 2008 | JP |
2008290680 | Dec 2008 | JP |
2009026321 | Feb 2009 | JP |
2009053925 | Mar 2009 | JP |
2009075638 | Apr 2009 | JP |
2010128637 | Jun 2010 | JP |
2010-173530 | Aug 2010 | JP |
2010182207 | Aug 2010 | JP |
2010191803 | Sep 2010 | JP |
20030062535 | Jul 2003 | KR |
0070941 | Nov 2000 | WO |
2001088827 | Nov 2001 | WO |
WO 0188827 | Nov 2001 | WO |
2005013235 | Feb 2005 | WO |
2007145564 | Dec 2007 | WO |
2009028558 | Mar 2009 | WO |
2009155228 | Dec 2009 | WO |
2011021046 | Feb 2011 | WO |
Entry |
---|
“Fact Sheet: Beyond Traffic Signals: A Paradigm Shift Intersection Control for Autonomous Vehicles”, [online]_3 Retrieved Apr. 27, 2011], Retrieved from the internet: htlp://www_fhwa.dot.gov/advancedresearch/pubs/10023/index_cfm>, 3 pages. |
Carl Crane, et al. Team Gator Nation's Autonomous Vehicle Development for the 2007 DARPA Urban Challenge, Dec. 2007, 27 pages. |
Chinese Office Action for Application No. 201180057942.8 dated Jun. 3, 2015. |
Chinese Office Action for Application No. 201180057954.0 dated Apr. 29, 2015. |
Eric Guizzo, How's Google's Self-Driving Car Works, IEEE. Org, IEEE, Oct. 18, 2011, pp. 1/31/-31/31. |
European Search Report for Application No. EP18211931 dated Jun. 25, 2019. |
Extended European Search Report for EP Patent Application No. 11831503.5, dated Dec. 3, 2015. |
Extended European Search Report for European Patent Application No. 11831362.6, dated Mar. 14, 2017. 11 pages. |
Google Cars Drive Themselves, in Traffic [online], [Retrieved Aug. 19, 2011] Retrieved from the internet: <http://www_nytimes.com/2010/10/1 O/science/10google_html>, 4 pages. |
International Search Report and the Written Opinion for Application No. PCT/US 2011/054154, dated Apr. 24, 2012. |
International Search Report and the Written Opinion for Application No. PCT/US 2011/054896, dated Apr. 25, 2012. |
International Search Report and Written Opinion for Application No. PCT/US2013/061604 dated Jul. 3, 2014. |
International Search Report and Written Opinion for Application No. PCT/US2011/054899 dated May 4, 2012. |
Jaffe, “The First Look at How Google's Self-Driving Car Handles City Streets”, The Atlantic City Lab, Apr. 28, 2014. |
Japanese Office Action for Application No. 2013-532908 dated Sep. 8, 2015. |
Martin Schonhof, Martin Treiber, Arne Kesting, and Dirk Helbing, Autonomous Detection and Anticipation of Jam Fronts From Messages Propagated by Intervehicle Communication, 2007, pp. 3-12. |
Matthew McNaughton, Motion Planning for Autonomous Driving with a Conformal Spatiotempral Lattice, Internation Conference on Robotics and Automation, May 9-13, pp. 4889-4895. |
Notice of Preliminary Rejection for Korean Patent Application No. 10-2013-7011657 dated Feb. 1, 2016. |
Notice of Reasons for Rejection for Japanese Patent Application No. 2013-532909, dated Nov. 25, 2015. |
Notice of Reasons for Rejection for Japanese Patent Application No. 2013-532909, dated May 26, 2016. |
Partial European Search Report for Application No. EP18211931 dated Feb. 27, 2019. |
Supplementary Partial European Search Report for European Patent Application No. 11831505.0, dated Dec. 20, 2016. |
Tiwari et al. “Survival analysis: Pedestrian risk exposure at signalized intersections.” Trans Research Part F: Traffic Psych and Behav, Pergamon, Amsterdam, NL, vol. 10, No. 2, Dec. 2, 2006 (Dec. 12, 2006),p. 77-89, XP005802066. |
TomTom GO user manual. Oct. 1, 2007 (Oct. 1, 2007). XP055123040. Retrieved from the Internet: <http://˜ownload.tomtom.com/open/manuals/device/refman/TomTom-GO-en-GB.pdf> _ 100 pages. |
Vincenzo DiLecce and Marco Calabrese, Experimental System to Support Real-Time Driving Pattern Recognition, 2008, pp. 1192-1199. |
Extended European Search Report for EP Application No. 18211931.3 dated Jun. 25, 2019, 14 pages. |
Number | Date | Country | |
---|---|---|---|
61391271 | Oct 2010 | US | |
61390094 | Oct 2010 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15488836 | Apr 2017 | US |
Child | 16441699 | US | |
Parent | 14727273 | Jun 2015 | US |
Child | 15488836 | US | |
Parent | 13252568 | Oct 2011 | US |
Child | 14727273 | US |