ABSTRACT
Abstract
A vehicle management system can include self-driving vehicles. Before entering a self-driving vehicle, a rider can use a remote computing device to select a pick-up location at which a self-driving vehicle will later pick up the rider. Detecting that the remote computing device is unable to communicate with the vehicle management system can trigger several responses configured to minimize the risk of a self-driving vehicle failing to pick up the rider.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 16/367,076; filed Mar. 27, 2019; and entitled SELF-DRIVING VEHICLE SYSTEMS AND METHODS.
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 16/205,013; filed Nov. 29, 2018; and entitled SELF-DRIVING VEHICLE SYSTEMS AND METHODS.
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 16/166,057; filed Oct. 19, 2018; and entitled SELF-DRIVING VEHICLE SYSTEMS AND METHODS.
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 16/128,334; filed Sep. 11, 2018; and entitled SELF-DRIVING VEHICLE ACTIONS IN RESPONSE TO A LOW BATTERY.
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 16/049,275; filed Jul. 30, 2018; and entitled SELF-DRIVING VEHICLE SYSTEMS AND METHODS.
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 15/863,903; filed Jan. 6, 2018; and entitled SELF-DRIVING VEHICLE SYSTEMS AND METHODS.
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 15/589,619; filed May 8, 2017; and entitled SELF-DRIVING VEHICLE SYSTEMS AND METHODS.
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 15/181,413; filed Jun. 14, 2016; and entitled SELF-DRIVING VEHICLE SYSTEMS AND METHODS.
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 15/099,565; filed Apr. 14, 2016; and entitled SELF-DRIVING VEHICLE SYSTEMS AND METHODS.
BACKGROUND
Field
Various embodiments disclosed herein relate to vehicles. Certain embodiments relate to self-driving motorized vehicles.
Description of Related Art
Vehicles typically require a driver. These vehicles often can only perform actions when directly instructed by the driver. However, self-driving vehicles are not reliant upon drivers and can perform actions based upon external events. As such, self-driving vehicles can save time and dramatically increase convenience in roadway travel. As a result, there is a need for systems and methods that enable self-driving vehicles to perform actions based upon external events.
SUMMARY
Self-driving vehicles will save tens of thousands of lives per year. The majority of vehicle-related deaths are caused by driver error. Tests have shown that self-driving vehicles nearly eliminate self-inflicted accidents (although they are not immune to accidents caused by human drivers of other vehicles). Self-driving vehicles have unlimited attention spans and can process complex sensor data nearly instantaneously. The ability of self-driving vehicles to save lives is so impressive that society has a moral imperative to develop self-driving technology such that it can be widely adopted.
Self-driving vehicles also have the ability to dramatically save time and improve convenience in roadway travel. Specifically, self-driving vehicles have unlimited potential to learn and predict human behavior and perform actions accordingly. Many embodiments described herein enable a self-driving vehicle to monitor human activity and predict when and where the human will be located and whether the human needs a ride from the self-driving vehicle. Self-driving vehicles will be able to perform such tasks with incredible efficacy and accuracy that will allow self-driving vehicles to proliferate at a much faster rate than would otherwise be the case.
Some embodiments comprise using a vehicle management system to operate a self-driving vehicle, wherein the vehicle management system is configured to be communicatively coupled with a remote computing device configured to operate software adapted to enable a user to control behaviors of the self-driving vehicle. Methods may include coupling communicatively, by the vehicle management system, the remote computing device to the self-driving vehicle, and then determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system; identifying, by the vehicle management system, a pick-up location of the user; and sending, by the vehicle management system, the self-driving vehicle to the pick-up location in response to determining that the remote computing device is no longer communicatively coupled to the vehicle management system.
Embodiments may also comprise sending, by the vehicle management system, the self-driving vehicle to the pick-up location in response to an estimated pick-up time. Additionally, methods may include determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system by sending a wireless communication to the remote computing device and then determining that the remote computing device did not respond to the wireless communication.
In some embodiments, methods comprise determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system by determining that a battery of the remote computing device is depleted below a predetermined threshold. Even still, embodiments may include determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system in response to determining that the vehicle management system has not received a first wireless communication from the remote computing device for a predetermined amount of time. In some embodiments, the predetermined amount of time is greater than thirty seconds and less than thirty minutes.
According to some embodiments, after sending the self-driving vehicle to the pick-up location, methods include instructing, by the vehicle management system, the self-driving vehicle to find a parking location in response to determining, by the vehicle management system, that communicative coupling between the vehicle management system and the remote computing device has been restored. As well, in some embodiments, methods include sending a second wireless communication from the vehicle management system to the remote computing device in response to determining that the remote computing device is no longer communicatively coupled to the vehicle management system. The second wireless communication may be configured to elicit a reply wireless communication from the remote computing device to the vehicle management system when the remote computing device regains cellular communication abilities.
Some embodiments comprise sending a second wireless communication from the vehicle management system to the remote computing device in response to determining that the remote computing device is no longer communicatively coupled to the vehicle management system, wherein the second wireless communication is configured to elicit a reply wireless communication from the remote computing device to the vehicle management system when the remote computing device regains cellular communication abilities, and then instructing, by the vehicle management system, the self-driving vehicle to find a parking location in response to receiving the reply wireless communication. The parking location may be located remotely relative to the pick-up location. Additionally, the pick-up location may be within fifty yards of a drop-off location where the self-driving vehicle last dropped off the user.
Some embodiments comprise receiving, by the vehicle management system, the pick-up location from the remote computing device prior to determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system. In some embodiments, methods include determining, by the vehicle management system, the pick-up location by analyzing location data of the remote computing device in a period within thirty minutes of when the vehicle management system determines that the remote computing device is no longer communicatively coupled to the vehicle management system.
Some embodiments comprise determining, by the vehicle management system, a pick-up time based on the location data of the remote computing device during the period. Methods also include sending, by the vehicle management system, the self-driving vehicle to the pick-up location at a time determined, by the vehicle management system, based on analyzing past amounts of time from past drop-offs to past pick-ups.
Some embodiments comprise sending, by the vehicle management system, the self-driving vehicle to the pick-up location at a time determined, by the vehicle management system, based on analyzing past amounts of time from past drop-offs to past pick-ups at past drop-off locations within fifty yards of a most recent drop-off location. Methods may even include analyzing location data of the remote computing device after a most recent drop-off of the user, and then sending, by the vehicle management system, the self-driving vehicle to the pick-up location at a time determined, by the vehicle management system, based on analyzing the location data.
In some embodiments, after sending the self-driving vehicle to the pick-up location, methods include determining that the user is not located at the pick-up location, and instructing, by the vehicle management system, the self-driving vehicle to move away from the pick-up location and to return to the pick-up location after a first period of time. Methods also include determining that the user is not located at the pick-up location after the first period of time, and instructing, by the vehicle management system, the self-driving vehicle to move away from the pick-up location and to return to the pick-up location after a second period of time, and determining that the user is not located at the pick-up location after the second period of time, and instructing, by the vehicle management system, the self-driving vehicle to move away from the pick-up location and to return to the pick-up location after a third period of time, wherein the third period is greater than the second period, and the second period is greater than the first period.
Some embodiments comprise analyzing, by the vehicle management system, a schedule of the user to estimate at least one of the pick-up location and a pick-up time. Methods also include determining that the user is not located at the pick-up location, and instructing, by the vehicle management system, the self-driving vehicle to move to a predetermined parking location that is located remotely relative to the pick-up location and a most-recent drop-off location.
Some embodiments comprise receiving, by the vehicle management system, from the remote computing device the predetermined parking location prior to determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system. The predetermined parking location may be a residence of the user.
Some embodiments comprise sending, by the vehicle management system, a notification to an emergency contact in response to determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system. The notification may comprise at least one of a most recent drop-off location of the user and location information of the self-driving vehicle.
Some embodiments comprise receiving from the emergency contact, by the vehicle management system, at least one of a pick-up time and the pick-up location for the user in response to sending the notification. Even still, methods include sending the notification in response to determining, by the vehicle management system, that the user is not located at the pick-up location.
Some embodiments comprise using a vehicle management system to operate a self-driving vehicle, wherein the vehicle management system is configured to be communicatively coupled with a remote computing device configured to operate software adapted to enable a user to control behaviors of the self-driving vehicle. Methods include coupling communicatively, by the vehicle management system, the remote computing device to the self-driving vehicle, and then determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system; identifying, by the vehicle management system, a pick-up location of the user; and sending, by the vehicle management system, the self-driving vehicle to a first location that is within a direct wireless communication range of a smart key from a most-recent drop-off location in response to determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system.
Some embodiments comprise receiving, by the vehicle management system, an indication that an antenna of the self-driving vehicle detected a first wireless communication from the smart key, and then sending, by the vehicle management system, the self-driving vehicle to the pick-up location in response to receiving the indication. Methods also include identifying, by the vehicle management system, the pick-up location by analyzing a directionality of the first wireless communication from the smart key.
Some embodiments comprise using a vehicle management system to operate a self-driving vehicle, wherein the vehicle management system is configured to be communicatively coupled with a remote computing device configured to operate software adapted to enable a user to control behaviors of the self-driving vehicle. Methods include coupling communicatively, by the vehicle management system, the remote computing device to the self-driving vehicle; detecting, by the remote computing device, a battery charge indication below a predetermined threshold; notifying, by the remote computing device, the user to select a pick-up time in response to detecting the battery charge indication below the predetermined threshold; and sending, by the vehicle management system, the self-driving vehicle to a pick-up location in response to the pick-up time selected by the user.
Some embodiments comprise determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system, and then sending, by the vehicle management system, the self-driving vehicle to the pick-up location in response to determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system. Additionally, methods include determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system in response to determining that the vehicle management system has not received a first wireless communication from the remote computing device for a predetermined amount of time.
Some embodiments comprise methods of using a vehicle management system to operate a self-driving vehicle. The vehicle management system can be configured to be communicatively coupled with a remote computing device. The remote computing device can be configured to enable a user to control behaviors of the self-driving vehicle. The remote computing device can comprise a battery configured to provide electrical power to the remote computing device. The battery can comprise one or more cells.
Several embodiments comprise coupling communicatively the remote computing device to the vehicle management system; and detecting, by the remote computing device, a first battery charge indication of the battery. The remote computing device can be configured to detect when the first battery charge indication is below a first predetermined threshold. The system can take various actions in response to detecting that the battery life is low (e.g., to reduce the risk of the user needing to communicate with the self-driving vehicle, but being unable to communicate with the self-driving vehicle).
Some embodiments comprise determining, by the remote computing device, that the first battery charge indication is below a first predetermined threshold; prompting, b
CROSS-REFERENCE TO RELATED APPLICATIONS
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 16/367,076; filed Mar. 27, 2019; and entitled SELF-DRIVING VEHICLE SYSTEMS AND METHODS.
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 16/205,013; filed Nov. 29, 2018; and entitled SELF-DRIVING VEHICLE SYSTEMS AND METHODS.
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 16/166,057; filed Oct. 19, 2018; and entitled SELF-DRIVING VEHICLE SYSTEMS AND METHODS.
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 16/128,334; filed Sep. 11, 2018; and entitled SELF-DRIVING VEHICLE ACTIONS IN RESPONSE TO A LOW BATTERY.
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 16/049,275; filed Jul. 30, 2018; and entitled SELF-DRIVING VEHICLE SYSTEMS AND METHODS.
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 15/863,903; filed Jan. 6, 2018; and entitled SELF-DRIVING VEHICLE SYSTEMS AND METHODS.
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 15/589,619; filed May 8, 2017; and entitled SELF-DRIVING VEHICLE SYSTEMS AND METHODS.
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 15/181,413; filed Jun. 14, 2016; and entitled SELF-DRIVING VEHICLE SYSTEMS AND METHODS.
The entire contents of the following application are incorporated by reference herein: U.S. patent application Ser. No. 15/099,565; filed Apr. 14, 2016; and entitled SELF-DRIVING VEHICLE SYSTEMS AND METHODS.
BACKGROUND
Field
Various embodiments disclosed herein relate to vehicles. Certain embodiments relate to self-driving motorized vehicles.
Description of Related Art
Vehicles typically require a driver. These vehicles often can only perform actions when directly instructed by the driver. However, self-driving vehicles are not reliant upon drivers and can perform actions based upon external events. As such, self-driving vehicles can save time and dramatically increase convenience in roadway travel. As a result, there is a need for systems and methods that enable self-driving vehicles to perform actions based upon external events.
SUMMARY
Self-driving vehicles will save tens of thousands of lives per year. The majority of vehicle-related deaths are caused by driver error. Tests have shown that self-driving vehicles nearly eliminate self-inflicted accidents (although they are not immune to accidents caused by human drivers of other vehicles). Self-driving vehicles have unlimited attention spans and can process complex sensor data nearly instantaneously. The ability of self-driving vehicles to save lives is so impressive that society has a moral imperative to develop self-driving technology such that it can be widely adopted.
Self-driving vehicles also have the ability to dramatically save time and improve convenience in roadway travel. Specifically, self-driving vehicles have unlimited potential to learn and predict human behavior and perform actions accordingly. Many embodiments described herein enable a self-driving vehicle to monitor human activity and predict when and where the human will be located and whether the human needs a ride from the self-driving vehicle. Self-driving vehicles will be able to perform such tasks with incredible efficacy and accuracy that will allow self-driving vehicles to proliferate at a much faster rate than would otherwise be the case.
Some embodiments comprise using a vehicle management system to operate a self-driving vehicle, wherein the vehicle management system is configured to be communicatively coupled with a remote computing device configured to operate software adapted to enable a user to control behaviors of the self-driving vehicle. Methods may include coupling communicatively, by the vehicle management system, the remote computing device to the self-driving vehicle, and then determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system; identifying, by the vehicle management system, a pick-up location of the user; and sending, by the vehicle management system, the self-driving vehicle to the pick-up location in response to determining that the remote computing device is no longer communicatively coupled to the vehicle management system.
Embodiments may also comprise sending, by the vehicle management system, the self-driving vehicle to the pick-up location in response to an estimated pick-up time. Additionally, methods may include determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system by sending a wireless communication to the remote computing device and then determining that the remote computing device did not respond to the wireless communication.
In some embodiments, methods comprise determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system by determining that a battery of the remote computing device is depleted below a predetermined threshold. Even still, embodiments may include determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system in response to determining that the vehicle management system has not received a first wireless communication from the remote computing device for a predetermined amount of time. In some embodiments, the predetermined amount of time is greater than thirty seconds and less than thirty minutes.
According to some embodiments, after sending the self-driving vehicle to the pick-up location, methods include instructing, by the vehicle management system, the self-driving vehicle to find a parking location in response to determining, by the vehicle management system, that communicative coupling between the vehicle management system and the remote computing device has been restored. As well, in some embodiments, methods include sending a second wireless communication from the vehicle management system to the remote computing device in response to determining that the remote computing device is no longer communicatively coupled to the vehicle management system. The second wireless communication may be configured to elicit a reply wireless communication from the remote computing device to the vehicle management system when the remote computing device regains cellular communication abilities.
Some embodiments comprise sending a second wireless communication from the vehicle management system to the remote computing device in response to determining that the remote computing device is no longer communicatively coupled to the vehicle management system, wherein the second wireless communication is configured to elicit a reply wireless communication from the remote computing device to the vehicle management system when the remote computing device regains cellular communication abilities, and then instructing, by the vehicle management system, the self-driving vehicle to find a parking location in response to receiving the reply wireless communication. The parking location may be located remotely relative to the pick-up location. Additionally, the pick-up location may be within fifty yards of a drop-off location where the self-driving vehicle last dropped off the user.
Some embodiments comprise receiving, by the vehicle management system, the pick-up location from the remote computing device prior to determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system. In some embodiments, methods include determining, by the vehicle management system, the pick-up location by analyzing location data of the remote computing device in a period within thirty minutes of when the vehicle management system determines that the remote computing device is no longer communicatively coupled to the vehicle management system.
Some embodiments comprise determining, by the vehicle management system, a pick-up time based on the location data of the remote computing device during the period. Methods also include sending, by the vehicle management system, the self-driving vehicle to the pick-up location at a time determined, by the vehicle management system, based on analyzing past amounts of time from past drop-offs to past pick-ups.
Some embodiments comprise sending, by the vehicle management system, the self-driving vehicle to the pick-up location at a time determined, by the vehicle management system, based on analyzing past amounts of time from past drop-offs to past pick-ups at past drop-off locations within fifty yards of a most recent drop-off location. Methods may even include analyzing location data of the remote computing device after a most recent drop-off of the user, and then sending, by the vehicle management system, the self-driving vehicle to the pick-up location at a time determined, by the vehicle management system, based on analyzing the location data.
In some embodiments, after sending the self-driving vehicle to the pick-up location, methods include determining that the user is not located at the pick-up location, and instructing, by the vehicle management system, the self-driving vehicle to move away from the pick-up location and to return to the pick-up location after a first period of time. Methods also include determining that the user is not located at the pick-up location after the first period of time, and instructing, by the vehicle management system, the self-driving vehicle to move away from the pick-up location and to return to the pick-up location after a second period of time, and determining that the user is not located at the pick-up location after the second period of time, and instructing, by the vehicle management system, the self-driving vehicle to move away from the pick-up location and to return to the pick-up location after a third period of time, wherein the third period is greater than the second period, and the second period is greater than the first period.
Some embodiments comprise analyzing, by the vehicle management system, a schedule of the user to estimate at least one of the pick-up location and a pick-up time. Methods also include determining that the user is not located at the pick-up location, and instructing, by the vehicle management system, the self-driving vehicle to move to a predetermined parking location that is located remotely relative to the pick-up location and a most-recent drop-off location.
Some embodiments comprise receiving, by the vehicle management system, from the remote computing device the predetermined parking location prior to determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system. The predetermined parking location may be a residence of the user.
Some embodiments comprise sending, by the vehicle management system, a notification to an emergency contact in response to determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system. The notification may comprise at least one of a most recent drop-off location of the user and location information of the self-driving vehicle.
Some embodiments comprise receiving from the emergency contact, by the vehicle management system, at least one of a pick-up time and the pick-up location for the user in response to sending the notification. Even still, methods include sending the notification in response to determining, by the vehicle management system, that the user is not located at the pick-up location.
Some embodiments comprise using a vehicle management system to operate a self-driving vehicle, wherein the vehicle management system is configured to be communicatively coupled with a remote computing device configured to operate software adapted to enable a user to control behaviors of the self-driving vehicle. Methods include coupling communicatively, by the vehicle management system, the remote computing device to the self-driving vehicle, and then determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system; identifying, by the vehicle management system, a pick-up location of the user; and sending, by the vehicle management system, the self-driving vehicle to a first location that is within a direct wireless communication range of a smart key from a most-recent drop-off location in response to determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system.
Some embodiments comprise receiving, by the vehicle management system, an indication that an antenna of the self-driving vehicle detected a first wireless communication from the smart key, and then sending, by the vehicle management system, the self-driving vehicle to the pick-up location in response to receiving the indication. Methods also include identifying, by the vehicle management system, the pick-up location by analyzing a directionality of the first wireless communication from the smart key.
Some embodiments comprise using a vehicle management system to operate a self-driving vehicle, wherein the vehicle management system is configured to be communicatively coupled with a remote computing device configured to operate software adapted to enable a user to control behaviors of the self-driving vehicle. Methods include coupling communicatively, by the vehicle management system, the remote computing device to the self-driving vehicle; detecting, by the remote computing device, a battery charge indication below a predetermined threshold; notifying, by the remote computing device, the user to select a pick-up time in response to detecting the battery charge indication below the predetermined threshold; and sending, by the vehicle management system, the self-driving vehicle to a pick-up location in response to the pick-up time selected by the user.
Some embodiments comprise determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system, and then sending, by the vehicle management system, the self-driving vehicle to the pick-up location in response to determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system. Additionally, methods include determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system in response to determining that the vehicle management system has not received a first wireless communication from the remote computing device for a predetermined amount of time.
Some embodiments comprise methods of using a vehicle management system to operate a self-driving vehicle. The vehicle management system can be configured to be communicatively coupled with a remote computing device. The remote computing device can be configured to enable a user to control behaviors of the self-driving vehicle. The remote computing device can comprise a battery configured to provide electrical power to the remote computing device. The battery can comprise one or more cells.
Several embodiments comprise coupling communicatively the remote computing device to the vehicle management system; and detecting, by the remote computing device, a first battery charge indication of the battery. The remote computing device can be configured to detect when the first battery charge indication is below a first predetermined threshold. The system can take various actions in response to detecting that the battery life is low (e.g., to reduce the risk of the user needing to communicate with the self-driving vehicle, but being unable to communicate with the self-driving vehicle).
Some embodiments comprise determining, by the remote computing device, that the first battery charge indication is below a first predetermined threshold; prompting, by the remote computing device, the user to select a pick-up time in response to determining that the first battery charge indication is below the first predetermined threshold; and sending, by the remote computing device, the pick-up time selected by the user to the vehicle management system. The remote computing device can send information to the vehicle management system through direct wireless communication methods and/or through indirect wireless communication methods (e.g., using other communication systems such as cellular communication networks, satellite communication networks, radio communication networks, and any other communication devices and technologies).
Some embodiments comprise prompting, by the remote computing device, the user to select a pick-up location in response to determining, by the remote computing device, that a second battery charge indication is below a second predetermined threshold. Some embodiments comprise sending, by the remote computing device, the pick-up location selected by the user to the vehicle management system.
Some embodiments comprise determining, by the remote computing device, that a third battery charge indication is below a third predetermined threshold. (The third predetermined threshold is less than the first predetermined threshold.) Some embodiments comprise reminding, by the remote computing device, the user regarding the pick-up time in response to determining that the third battery charge indication is below the third predetermined threshold.
Some embodiments comprise estimating, by at least one of the remote computing device and the vehicle management system, that a battery power supply of the remote computing device will be depleted before the pick-up time, and then in response to the estimating, reminding, by the remote computing device, the user regarding the pick-up time prior to depleting the battery power supply.
Some embodiments comprise receiving, by the remote computing device, a first pick-up time; estimating, by at least one of the remote computing device and the vehicle management system, that a battery power supply of the remote computing device will be depleted before the first pick-up time; and then in response to the estimating, prompting, by the remote computing device, the user to select a second pick-up time configured to supersede the first pick-up time. Embodiments can comprise sending, by the remote computing device, the second pick-up time to the vehicle management system.
Some embodiments comprise sending, by the remote computing device, the second pick-up time to the vehicle management system such that the second pick-up time supersedes the first pick-up time.
Some embodiments comprise receiving, by the remote computing device, a first pick-up time; estimating, by the remote computing device, that a battery power supply of the remote computing device will be depleted before the first pick-up time; and then in response to the estimating, prompting, by the remote computing device, the user to select a back-up pick-up location. Some embodiments comprise sending, by the remote computing device, the back-up pick-up location to the vehicle management system such that the vehicle management system is configured to send the self-driving vehicle to the back-up pick-up location in response to the vehicle management system being unable to communicate with the remote computing device.
Some embodiments comprise determining, by the remote computing device, that the first battery charge indication is below a first predetermined threshold; and entering, by the remote computing device, a low battery mode in response to determining that the first battery charge indication is below the first predetermined threshold and in response to determining, by the remote computing device, that the vehicle management system is in a pick-up expected mode.
In several embodiments, entering the low battery mode comprises disabling a radio-frequency signal transmission system of the remote computing device.
In several embodiments, entering the low battery mode comprises disabling at least one feature of the remote computing device to reduce power consumption of the remote computing device.
In several embodiments, the vehicle management system is configured to be in the pick-up expected mode from a first time when the self-driving vehicle drops off the user until a second time when the self-driving vehicle picks up the user.
In several embodiments, the vehicle management system is configured to be in the pick-up expected mode from a first time when the vehicle management system drops off the user (e.g., with a first self-driving vehicle) until a second time when the vehicle management system picks up the user (e.g., with the first self-driving vehicle or with a different self-driving vehicle).
In several embodiments, the pick-up expected mode comprises a mode in which at least one of the user is located remotely relative to the self-driving vehicle yet the self-driving vehicle anticipates picking up the user, the vehicle management system is waiting for an instruction from the remote computing device to pick up the user, and a pick-up time selected by the user is less than twelve hours away.
Some embodiments comprise receiving, by the remote computing device, a pick-up time; sending, by the remote computing device, the pick-up time to the vehicle management system; and exiting, by the remote computing device, the low battery mode in response to receiving the pick-up time.
Some embodiments comprise receiving, by the remote computing device, a pick-up location; sending, by the remote computing device, the pick-up location to the vehicle management system; and exiting, by the remote computing device, the low battery mode in response to receiving the pick-up location.
Some embodiments comprise receiving, by the remote computing device, at least one of a pick-up time and a pick-up location; sending, by the remote computing device, at least one of the pick-up time and the pick-up location to the vehicle management system; and exiting, by the remote computing device, the low battery mode in response to sending at least one of the pick-up time and the pick-up location.
Some embodiments comprise shutting down the remote computing device in response to determining, by the remote computing device, that a second battery charge indication is below a second predetermined threshold and in response to determining, by the remote computing device, that the vehicle management system is in the pick-up expected mode. The second predetermined threshold can be lower than the first predetermined threshold.
Some embodiments comprise determining, by the remote computing device, that the first battery charge indication is below a first predetermined threshold; and prompting, by the remote computing device, the user to select a back-up contact in response to determining that the first battery charge indication is below the first predetermined threshold. Some embodiments comprise sending, by the remote computing device, the back-up contact selected by the user to the vehicle management system.
Some embodiments comprise sending, by the vehicle management system, a wireless communication to the back-up contact in response to determining, by the vehicle management system, that the vehicle management system is no longer able to communicate with the remote computing device. The wireless communication can comprise location information regarding the user. The wireless communication can be configured to prompt the back-up contact to take action to aid the user. The wireless communication can prompt the back-up contact to select a pick-up time and pick-up location for the user. The wireless communication can prompt the back-up contact to select where the vehicle should go (e.g., the back-up contact can instruct the vehicle to move to a waiting location, a home base, and/or to the user's home).
Some embodiments comprise granting control, by at least one of the remote computing device and the vehicle management system, of the self-driving vehicle to the back-up contact in response to receiving, by the remote computing device, the back-up contact from the user. In several embodiments, granting control enables the back-up contact to choose a destination for the self-driving vehicle.
Some embodiments comprise granting control, by at least one of the remote computing device and the vehicle management system, of the self-driving vehicle to the back-up contact in response to receiving, by the remote computing device, the back-up contact from the user and in response to determining, by the vehicle management system, that the vehicle management system is no longer able to communicate with the remote computing device.
Some embodiments comprise determining, by the remote computing device, that the first battery charge indication is below a first predetermined threshold; determining, by the remote computing device, that a back-up contact is located within 50 yards of the user; and prompting, by the remote computing device, the user to select the back-up contact to at least one of receive a notification regarding the self-driving vehicle and control at least one movement of the self-driving vehicle. Prompting the user can be in response to determining that the first battery charge indication is below the first predetermined threshold.
BRIEF DESCRIPTION OF THE DRAWINGS
These and other features, aspects, and advantages are described below with reference to the drawings, which are intended to illustrate, but not to limit, the invention. In the drawings, like reference characters denote corresponding features consistently throughout similar embodiments.
FIG. 1 illustrates a diagrammatic view of a self-driving vehicle, according to some embodiments.
FIG. 2 illustrates a diagrammatic view of a self-driving vehicle, according to some embodiments.
FIG. 3 illustrates a diagrammatic view of a method of using a self-driving vehicle, according to some embodiments.
FIG. 4 illustrates a diagrammatic view of another method of using a self-driving vehicle, according to some embodiments.
FIG. 5 illustrates a diagrammatic view of another method of using a self-driving vehicle, according to some embodiments.
FIG. 6 illustrates a diagrammatic view of another method of using a self-driving vehicle, according to some embodiments.
FIG. 7 illustrates a diagrammatic view of another method of using a self-driving vehicle, according to some embodiments.
FIG. 8 illustrates a diagrammatic view of another method of using a self-driving vehicle, according to some embodiments.
FIG. 9 illustrates a diagrammatic view of another method of using a self-driving vehicle, according to some embodiments.
FIG. 10 illustrates a diagrammatic view of another method of using a self-driving vehicle, according to some embodiments.
FIG. 11 illustrates a diagrammatic view of another method of using a self-driving vehicle, according to some embodiments.
FIG. 12 illustrates a diagrammatic view of another method of using a self-driving vehicle, according to some embodiments.
FIG. 13 illustrates a diagrammatic view of another method of using a self-driving vehicle, according to some embodiments.
FIG. 14 illustrates a diagrammatic view of another method of using a self-driving vehicle, according to some embodiments.
FIGS. 15 - 20 illustrate diagrammatic views of methods of using a self-driving vehicle, according to some embodiments.
FIG. 21 illustrates a perspective view of a top side, a front side and a passenger side of a vehicle guidance system coupled to a vehicle, according to some embodiments.
FIG. 22 illustrates a perspective view of the top side, a backside side and a driver side of the vehicle guidance system coupled to the vehicle, according to some embodiments.
FIG. 23 illustrates a diagrammatic view of a first time after a rider was dropped off at a drop-off location, according to some embodiments.
FIG. 24 illustrates a diagrammatic view of a second time after the rider was dropped off at the drop-off location, according to some embodiments.
DETAILED DESCRIPTION
Although certain embodiments and examples are disclosed below, inventive subject matter extends beyond the specifically disclosed embodiments to other alternative embodiments and/or uses, and to modifications and equivalents thereof. Thus, the scope of the claims appended hereto is not limited by any of the particular embodiments described below. For example, in any method or process disclosed herein, the acts or operations of the method or process may be performed in any suitable sequence and are not necessarily limited to any particular disclosed sequence. Various operations may be described as multiple discrete operations in turn, in a manner that may be helpful in understanding certain embodiments; however, the order of description should not be construed to imply that these operations are order dependent. Additionally, the structures, systems, and/or devices described herein may be embodied as integrated components or as separate components.
For purposes of comparing various embodiments, certain aspects and advantages of these embodiments are described. Not necessarily all such aspects or advantages are achieved by any particular embodiment. Thus, for example, various embodiments may be carried out in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other aspects or advantages as may also be taught or suggested herein.
Self-driving vehicles will provide significant savings to the economy and society at-large. For example, self-driving vehicles will not only greatly reduce roadway congestion, thus making transportation more efficient and less costly, but self-driving vehicles will also learn and adapt to human behavior, thus providing an unimaginable level of convenience in today's world of transportation. The ability of self-driving vehicles to positively impact the economy and public is so impressive that society has a moral imperative to develop self-driving technology such that it can be widely adopted.
Self-driving vehicles have unlimited potential to learn and predict human behavior and perform actions accordingly. Many embodiments described herein enable a self-driving vehicle to monitor human activity and predict when and where the human will be located and whether the human needs a ride from the self-driving vehicle. Self-driving vehicles will be able to perform such tasks with incredible efficacy and accuracy, which will allow self-driving vehicles to proliferate much faster than would otherwise be the case.
Self-driving cars are sometimes referred to as autonomous cars, autonomous vehicles, driverless cars, and driverless vehicles. Various levels of âself-drivingâ behaviors are possible to sense surrounding environments and navigate appropriately (e.g., without hitting objects, in a time-efficient manner).
FIG. 1 illustrates a diagrammatic view of a self-driving vehicle 2 and a vehicle management system 4 . In some embodiments, the system 4 comprises the vehicle 2 . In this regard, the system 4 can comprise a plurality of vehicles (e.g. self-driving vehicles and non-self-driving vehicles) that are communicatively coupled to the system 4 . In some embodiments, the vehicle 2 comprises the system 4 . In this regard, the system 4 can be implemented as an on-board system located within the vehicle 2 . In such embodiments, the system 4 can still be communicatively coupled to other vehicles (e.g. self-driving vehicles and non-self-driving vehicles).
With continued reference to FIG. 1 , the system 4 can receive a notification 6 a . In some embodiments, the system 4 can send a first wireless communication 15 a to the vehicle 2 in response to the system 4 receiving the notification 6 a . The first wireless communication 15 a can thereby prompt the vehicle 2 to move towards the person 1 . It should be noted that any of the transmission steps described in this disclosure, such as sending, receiving, and the like, can be executed directly and/or indirectly.
As shown in FIG. 2 , the notification 6 a can be any type of notification that indicates that a person, such as the person 1 or another person, needs a ride from the vehicle 2 . In some embodiments, the notification 6 a comprises a checkout notification 6 b , such as a notification that the person has purchased an item or service from a store. Accordingly, in some embodiments, the vehicle management system 4 receives the checkout notification 6 b in response to the person 1 purchasing the item or service at the store.
According to FIGS. 2 and 3 , the vehicle 2 and/or system 4 may perform actions in response to the system 4 receiving an indication of the notification 6 a . For example, in response to receiving the notification 6 a , such as the checkout notification 6 b , the system 4 may send a second wireless communication 15 b to the remote computing device 12 . The second wireless communication 15 b may prompt the remote computing device 12 to ask the person 1 whether the person 1 wants the vehicle 2 to move towards the person 1 . In this regard, the system 4 can respond to the notification by sending an indication to the remote computing device 12 to determine whether the person 1 wants the vehicle 2 to move towards the person 1 (e.g. pick up the person 1 ). Because the vehicle 2 and/or system 4 can receive wireless communications while the vehicle 2 is in a parked state or a driving state, such as when the vehicle 2 is in a holding pattern (e.g. driving around the parking lot waiting for the person 1 to be picked up), the system 4 may receive the second wireless communication 15 c . In some embodiments, the second wireless communication 15 c may instruct the vehicle 2 to move to a parked state, enter the holding pattern, continue the holding pattern, or move towards a pickup location to retrieve the person 1 .
As shown in FIG. 2 , the notification 6 a can comprise various types of notifications and events, such as a first event 6 c associated with the person 1 . In some embodiments, the first event 6 c may comprise a text message or email sent by the remote computing device 12 , a post on a social network communicatively coupled to the remote computing device 12 , such as status or âcheck inâ posted on a social network (e.g. Facebook®, Twitter®, and the like). The first event 6 c may also include other external events, such as a severe weather alert. For example, the system 4 may be configured to determine if severe weather is about to occur. In response to this determination, the vehicle 2 can move towards the person 1 to pick up the person 1 and take them out of harm's way.
The system 4 can also be configured to determine the occurrence of many other events, such as whether an event or appointment that the person is attending has concluded or is about to conclude whereby the event has a known ending time. For example, the system 4 can determine that the person 1 is attending a movie and the movie has ended or is about to end within a predetermined amount of time, such as within 5 minutes.
The system 4 can also be configured to determine whether an event or appointment that the person is attending has concluded or is about to conclude whereby the event has an unknown ending time. Described differently, many appointments and events, such as sporting events, can last for unknown amounts of time. For example, a baseball game may have a tie score whereby the game is extended into extra innings. In this regard, the system 4 can determine that the person 1 is not only attending the baseball game, but the system can determine, via a third party database, whether the game has been extended to extra innings. The system 4 may continue to monitor the progress of the baseball game and once the game is over, the vehicle 2 may be dispatched to retrieve the person 1 . The system 4 may further be configured with advanced features, or analytics, to determine the conclusion of the event based upon statistical probabilities. For example, the system 4 may be monitoring the progress of the baseball game and the system 4 may determine that the home team has scored 7 runs in the bottom of the 12 th inning and that the home team now leads by a score of 8-1. The system 4 may implement statistical analysis and determine that the other team has a very low statistical chance of scoring 7 or more runs during the top of the 13 th inning. In response to this determination, the vehicle 2 may move towards the person 1 based upon the assumption that the game will end after the top of the 13 th inning. It should be appreciated that these are just a few of the many examples of how statistical analysis and analytics can be used to predict the end of events with unknown ending times. Accordingly, in response to this analysis, the vehicle 2 and system 4 can respond by performing any appropriate action, as described in this disclosure.
The notification 6 a can also include various notifications, such as a second checkout notification 6 f The second checkout notification 6 f can indicate that the person 1 has purchased a second item from the same store, or even a different store. This type of notification can indicate that the person 1 is still shopping and may not want to be picked up just yet. Alternatively, this type of notification can indicate that the person 1 has concluded her shopping and is ready to be picked up. The system 4 can learn the person's behavior patterns and respond to future occurrences in accordance with these patterns, which can indicate the person's desires.
In some embodiments, the system 4 receives the checkout notification 6 b in response to the person 1 purchasing the item with a credit card. In response to the checkout notification, the vehicle 2 can thereby move towards the <figure-callout id="1" label="person" filenames="US11789460-20231017-D0
CLAIMS
Claims ( 20 )
What is claimed is:
1. A non-transitory computer readable media, executable by a vehicle management processor, of a vehicle management system comprising a self-driving vehicle fleet including a plurality of self-driving vehicles, to communicatively couple the vehicle management system to a remote computing device; and the non-transitory computer readable media being configured to direct a first self-driving vehicle from the self-driving vehicle fleet, to drop-off a rider at a drop-off location.
2. The non-transitory computer readable media as recited in claim 1 , wherein the non-transitory computer readable media is further configured to instruct the first self-driving vehicle to go to a predetermined pick-up location of the rider in response to determining, by the vehicle management system, that the remote computing device is no longer communicatively coupled to the vehicle management system.
3. The non-transitory computer readable media as recited in claim 2 , wherein the non-transitory computer readable media is further configured to determine that the communicative coupling between the vehicle management system and the remote computing device has been restored, and in response to determining that the communicative coupling has been restored, the non-transitory computer readable media is further configured to instruct the first self-driving vehicle to move away from a first area within a predetermined distance of the predetermined pick-up location.
4. The non-transitory computer readable media as recited in claim 1 , wherein the non-transitory computer readable media is further configured to determine whether the remote computing device is communicatively coupled to the vehicle management system by sending a first wireless communication to the remote computing device and thereby determine that the remote computing device did not respond to the first wireless communication.
5. The non-transitory computer readable media as recited in claim 1 , wherein the non-transitory computer readable media is further configured to determine whether the remote computing device is communicatively coupled to the vehicle management system by determining that the vehicle management system has not received a first wireless communication from the remote computing device within a predetermined amount of time.
6. The non-transitory computer readable media as recited in claim 1 , wherein the non-transitory computer readable media is further configured to determine whether the remote computing device is communicatively coupled to the vehicle management system by determining that a battery of the remote computing device is below a predetermined threshold.
7. The non-transitory computer readable media as recited in claim 1 , wherein the non-transitory computer readable media is further configured to receive a first indication that the remote computing device is communicatively disabled; and instruct the first self-driving vehicle to drive to a first area within a predetermined distance of the drop-off location to pick up the rider in response to receiving the first indication.
8. The non-transitory computer readable media as recited in claim 1 , wherein the non-transitory computer readable media is further configured to receive first location data indicative of a first pick-up location; receive a first indication that the remote computing device is communicatively disabled; instruct the first self-driving vehicle to drive to a first area within a predetermined distance of the first pick-up location in response to receiving the first indication that the remote computing device is communicatively disabled.
9. A non-transitory computer readable media, executable by a vehicle management processor, of a vehicle management system, to select a predetermined pick-up location of a rider in response to a determination, by the vehicle management processor, that a remote computing device is no longer communicatively coupled to the vehicle management system, the non-transitory computer readable media being configured to cause the vehicle management system to cause a self-driving vehicle to drive proximate to the predetermined pick-up location in connection with the determination.
10. The non-transitory computer readable media as recited in claim 9 , wherein the non-transitory computer readable media is further configured to cause the vehicle management processor to cause the self-driving vehicle to drive to a first area within 250 feet of a predetermined drop-off location in response to the determination, by the vehicle management processor, that the remote computing device is no longer communicatively coupled to the vehicle management system.
11. The non-transitory computer readable media as recited in claim 10 , wherein the non-transitory computer readable media is further configured to cause the vehicle management processor to cause the vehicle management system to send a wireless communication to the remote computing device in connection with the determination that the remote computing device is not communicatively coupled to the vehicle management system.
12. The non-transitory computer readable media as recited in claim 11 , wherein the non-transitory computer readable media is further configured to determine whether the remote computing device is responsive to the wireless communication within a predetermined amount of time.
13. The non-transitory computer readable media as recited in claim 12 , wherein the predetermined amount of time is greater than thirty seconds and less than sixty minutes.
14. The non-transitory computer readable media as recited in claim 9 , wherein the determination is made in connection with detection that a battery of the remote computing device is depleted.
15. The non-transitory computer readable media as recited in claim 9 , wherein the non-transitory computer readable media is further configured to cause the vehicle management processor to cause the self-driving vehicle to drive to a first area within 250 feet of the predetermined pick-up location in response to the determination, by the vehicle management processor, that the remote computing device is no longer communicatively coupled to the vehicle management system and to cause instructions to be issued by the vehicle management system to the self-driving vehicle to move away from the first area in response to determining that a rider is not located in the first area and further causing instructions to be issued to at least a first portion of a self-driving vehicle fleet to return to the first area, after a first period of time, in an attempt to pick up a rider.
16. The non-transitory computer readable media as recited in claim 15 , wherein the non-transitory computer readable media is further configured to cause the vehicle management processor, to issue instructions to cause the first portion of the self-driving vehicle fleet to move away from the first area; and
instruct, at least a second portion of the self-driving vehicle fleet, to return to the first area after a second period of time that is greater than the first period of time in an attempt to pick up the rider.
17. The non-transitory computer readable media as recited in claim 16 , wherein the non-transitory computer readable media is further configured to cause the vehicle management processor, to issue instructions, by the vehicle management system, to at least a third portion of the self-driving vehicle fleet to return to the first area after a third period of time that is greater than the second period of time in an attempt to pick up the rider.
18. A non-transitory computer readable media, executable by a processor, of a remote computing device, configured to cause the processor to allow selection, on the remote computing device, of a rider pick-up location and a rider drop-off location in connection with a vehicle management system transmitting the rider pick-up location and the rider drop-off location to a self-driving vehicle.
19. The non-transitory computer readable media as recited in claim 18 , wherein the non-transitory computer readable media is further configured to receive a first wireless communication from a vehicle management system comprising a self-driving vehicle fleet including a plurality of self-driving vehicles.
20. The non-transitory computer readable media as recited in claim 19 , wherein the non-transitory computer readable media is further configured to send a first reply wireless communication to the vehicle management system.
US17/368,654
2018-01-06
2021-07-06
Self-driving vehicle systems and methods
Active
2038-05-01
US11789460B2
( en )
Priority Applications (3)
Application Number
Priority Date
Filing Date
Title
US17/368,654
US11789460B2
( en )
2018-01-06
2021-07-06
Self-driving vehicle systems and methods
US18/307,519
US12147229B2
( en )
2019-11-08
2023-04-26
Self-driving vehicle systems and methods
US18/916,263
US20250036121A1
( en )
2019-11-08
2024-10-15
Self-driving vehicle systems and methods
Applications Claiming Priority (7)
Application Number
Priority Date
Filing Date
Title
US15/863,903
US10255648B2
( en )
2016-04-14
2018-01-06
Self-driving vehicle systems and methods
US16/049,275
US10274950B1
( en )
2018-01-06
2018-07-30
Self-driving vehicle systems and methods
US16/128,334
US10299216B1
( en )
2018-01-06
2018-09-11
Self-driving vehicle actions in response to a low battery
US16/166,057
US10268192B1
( en )
2018-01-06
2018-10-19
Self-driving vehicle systems and methods
US16/205,013
US10303181B1
( en )
2018-11-29
2018-11-29
Self-driving vehicle systems and methods
US16/367,076
US11073838B2
( en )
2018-01-06
2019-03-27
Self-driving vehicle systems and methods
US17/368,654
US11789460B2
( en )
2018-01-06
2021-07-06
Self-driving vehicle systems and methods
Related Parent Applications (3)
Application Number
Title
Priority Date
Filing Date
US16/367,076
Continuation
US11073838B2
( en )
2018-01-06
2019-03-27
Self-driving vehicle systems and methods
US16/678,751
Continuation
US11221622B2
( en )
2018-10-01
2019-11-08
Self-driving vehicle systems and methods
US16/678,660
Continuation
US11221621B2
( en )
2018-10-01
2019-11-08
Self-driving vehicle systems and methods
Related Child Applications (2)
Application Number
Title
Priority Date
Filing Date
US16/678,660
Continuation-In-Part
US11221621B2
( en )
2018-10-01
2019-11-08
Self-driving vehicle systems and methods
US18/307,519
Continuation-In-Part
US12147229B2
( en )
2019-11-08
2023-04-26
Self-driving vehicle systems and methods
Publications (2)
Publication Number
Publication Date
US20210333801A1
US20210333801A1 ( en )
2021-10-28
US11789460B2
true
US11789460B2 ( en )
2023-10-17
Family
ID=67212856
Family Applications (2)
Application Number
Title
Priority Date
Filing Date
US16/367,076
Active
2038-10-15
US11073838B2
( en )
2018-01-06
2019-03-27
Self-driving vehicle systems and methods
US17/368,654
Active
2038-05-01
US11789460B2
( en )
2018-01-06
2021-07-06
Self-driving vehicle systems and methods
Family Applications Before (1)
Application Number
Title
Priority Date
Filing Date
US16/367,076
Active
2038-10-15
US11073838B2
( en )
2018-01-06
2019-03-27
Self-driving vehicle systems and methods
Country Status (1)
Country
Link
US
( 2 )
US11073838B2
( en )
Families Citing this family (20)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
JP6967417B2
( en )
*
2017-10-03
2021-11-17
æ ªå¼ä¼ç¤¾ ããã¯ã¦ã§ã¢
Route generator and program
US11073838B2
( en )
*
2018-01-06
2021-07-27
Drivent Llc
Self-driving vehicle systems and methods
US11235778B2
( en )
*
2018-01-24
2022-02-01
Clearpath Robotics Inc.
Systems and methods for maintaining vehicle state information
US11221622B2
( en )
2019-03-21
2022-01-11
Drivent Llc
Self-driving vehicle systems and methods
US10832569B2
( en )
2019-04-02
2020-11-10
Drivent Llc
Vehicle detection systems
US11644833B2
( en )
2018-10-01
2023-05-09
Drivent Llc
Self-driving vehicle systems and methods
KR102692325B1
( en )
*
2019-06-17
2024-08-08
íëìë차주ìíì¬
Apparatus for controlling remote parking out mode of vehicle and method thereof
US12147229B2
( en )
2019-11-08
2024-11-19
Drivent Llc
Self-driving vehicle systems and methods
JP7359710B2
( en )
*
2020-02-03
2023-10-11
ãã¨ã¿èªåè»æ ªå¼ä¼ç¤¾
Vehicle management system
US10972893B1
( en )
*
2020-02-06
2021-04-06
Qualcomm Incorporated
Cellular vehicle to everything assisted next generation emergency call
US20210300334A1
( en )
2020-03-26
2021-09-30
Toyota Motor North America, Inc.
Transport relocation
US11551534B2
( en )
*
2020-04-17
2023-01-10
Oshkosh Corporation
Thermal management controls
US11538291B2
( en )
2020-04-17
2022-12-27
Oshkosh Corporation
Thermal management sensors
CN112785866B
( en )
*
2020-12-28
2022-03-08
å京éªèç§ææéå ¬å¸
Vehicle position reporting method and device, shared vehicle and storage medium
JP7468404B2
( en )
*
2021-02-25
2024-04-16
ãã¨ã¿èªåè»æ ªå¼ä¼ç¤¾
Autonomous vehicles, autonomous vehicle dispatch systems and mobile terminals
JP7351320B2
( en )
*
2021-03-09
2023-09-27
ãã¨ã¿èªåè»æ ªå¼ä¼ç¤¾
Vehicle control system and vehicle control method
JP7476843B2
( en )
2021-04-15
2024-05-01
ãã¨ã¿èªåè»æ ªå¼ä¼ç¤¾
Information processing device, method, and program
US11845347B2
( en )
2021-05-12
2023-12-19
David Alan Copeland
Precision charging control of an untethered vehicle with a modular vehicle charging roadway
JP7237121B1
( en )
*
2021-08-26
2023-03-10
ä¸è±é»æ©æ ªå¼ä¼ç¤¾
Positioning device
CN119179320B
( en )
*
2024-10-25
2025-02-25
ä¸æ±½ç 汽车æ£éªä¸å¿ï¼å¤©æ´¥ï¼æéå ¬å¸
Remote control parking test device and method
Citations (268)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US4212069A
( en )
1976-08-31
1980-07-08
Baumann Dwight M
Paratransit fare computation and dispatching method
US5769471A
( en )
1995-09-04
1998-06-23
Aisin Seiki Kabushiki Kaisha
Apparatus for unlocking a door lock for a vehicle
US5798695A
( en )
1997-04-02
1998-08-25
Northrop Grumman Corporation
Impaired operator detection and warning system employing analysis of operator control actions
US5871063A
( en )
1997-01-22
1999-02-16
Automotive Systems Laboratory, Inc.
Seat belt latch sensor system
US5945919A
( en )
1996-05-30
1999-08-31
Trimble Navigation Limited
Dispatcher free vehicle allocation system
US5960523A
( en )
1998-08-25
1999-10-05
Breed Automotive Technology, Inc.
Seat belt buckle sensor
US5986420A
( en )
1996-11-11
1999-11-16
Toyota Shatai Kabushiki Kaisha
Apparatus for automatically opening and closing pop-up door of a vehicle
US6011478A
( en )
1997-05-08
2000-01-04
Nittan Company, Limited
Smoke sensor and monitor control system
US6081088A
( en )
1997-12-26
2000-06-27
Asmo Co., Ltd.
Automatic opening/closing apparatus
US20020077876A1
( en )
2000-12-18
2002-06-20
O'meara Cian E.
Allocation of location-based orders to mobile agents
US20020121291A1
( en )
*
2001-03-03
2002-09-05
Daum Wolfgang R.A.
Method and device to clean the interior room of a car
US6530251B1
( en )
1999-11-18
2003-03-11
Strattec Security Corporation
Modular vehicle door lock and latch system and method
US20030195696A1
( en )
1993-05-18
2003-10-16
Jones M. Kelly
Notification systems and methods with notifications based upon prior stop locations
US20030214585A1
( en )
2002-01-09
2003-11-20
Bakewell Charles Adams
Mobile enforcement platform with aimable violation identification and documentation system for multiple traffic violation types across all lanes in moving traffic, generating composite display images and data to support citation generation, homeland security, and monitoring
US20040068354A1
( en )
1998-04-27
2004-04-08
Tabe Joseph A.
Smart seatbelt control system
US20040076280A1
( en )
2002-07-17
2004-04-22
Omron Corporation
Operation service information mediation system
US20040203600A1
( en )
2000-10-10
2004-10-14
Mccorkle John W.
System and method for providing device authentication in a wireless network
US20040219933A1
( en )
2003-02-07
2004-11-04
Johnathan David Faith
Transportation ordering system
KR20050017888A
( en )
2003-08-11
2005-02-23
íëìë차주ìíì¬
Penalty system for unfastening seatbelt and method for controlling the same
US20050156726A1
( en )
2004-01-20
2005-07-21
Faurecia Automotive Seating Canada Limited
Vehicle seatbelt usage sensing apparatus and method for generating and transmitting a seatbelt warning signal
US7093515B2
( en )
2002-10-09
2006-08-22
Nissan Motor Co., Ltd.
Accelerator pedal device for a vehicle
US20070096447A1
( en )
2003-10-07
2007-05-03
Tabe Joseph A
Smart seatbelt control system
US20070132567A1
( en )
2000-03-02
2007-06-14
Donnelly Corporation
Video mirror system suitable for use in a vehicle
US20070198144A1
( en )
2005-10-21
2007-08-23
Norris William R
Networked multi-role robotic vehicle
US7298250B2
( en )
2003-08-29
2007-11-20
Mitsubishi Jidosha Kogyo Kabushiki Kaisha
Seatbelt reminder system
US20080030906A1
( en )
2005-03-01
2008-02-07
Fujitsu Limited
Magnetoresistive effect element and magnetic memory device
US20080144944A1
( en )
1992-05-05
2008-06-19
Automotive Technologies International, Inc.
Neural Network Systems for Vehicles
US20080195428A1
( en )
2007-02-12
2008-08-14
O'sullivan Sean
Shared transport system and service network
US7413357B2
( en )
2005-06-13
2008-08-19
Silverstate Safety Image
Concealed camera
US20090132128A1
( en )
2007-11-20
2009-05-21
Tk Holdings Inc.
Occupant monitoring and restraint status system
US20090140886A1
( en )
2007-12-03
2009-06-04
International Truck Intellectual Property Company, Llc
Multiple geofence system for vehicles
US20090287367A1
( en )
2008-05-16
2009-11-19
Gm Global Technology Operations, Inc.
Method and apparatus for driver control of a limited-ability autonomous vehicle
US20090289443A1
( en )
2008-05-23
2009-11-26
Okezie Pathfins C
Vehicle safety apparatus and method
US7698078B2
( en )
2007-06-15
2010-04-13
Tesla Motors, Inc.
Electric vehicle communication interface
US20100169199A1
( en )
2008-12-31
2010-07-01
Fuller Max L
Method for In-Cab Driver Operation
US7777619B2
( en )
2007-04-11
2010-08-17
Ford Global Technologies, Llc
System and method for implementing active safety counter measures for an impaired driver
US20110059341A1
( en )
2008-06-12
2011-03-10
Junichi Matsumoto
Electric vehicle
US20110098017A1
( en )
2007-06-27
2011-04-28
Ford Global Technologies, Llc
Method And System For Emergency Notification
US7999701B1
( en )
*
2008-06-26
2011-08-16
Bin Xu
Transportation notification system
US20110267186A1
( en )
2010-04-29
2011-11-03
Ford Global Technologies, Llc
Occupant Detection
US8055534B2
( en )
2008-12-22
2011-11-08
International Business Machines Corporation
Variable rate travel fee based upon vehicle occupancy
US8078359B2
( en )
2009-10-05
2011-12-13
Tesla Motors, Inc.
User configurable vehicle user interface
US20120009845A1
( en )
2010-07-07
2012-01-12
Juniper Holding Corp.
Configurable location-aware toy capable of communicating with like toys and associated system infrastructure for communicating with such toys
US8150611B2
( en )
2008-09-30
2012-04-03
International Business Machines Corporation
System and methods for providing predictive traffic information
US20120083960A1
( en )
2010-10-05
2012-04-05
Google Inc.
System and method for predicting behaviors of detected objects
US8180379B2
( en )
2007-06-28
2012-05-15
Apple Inc.
Synchronizing mobile and vehicle devices
US20120158251A1
( en )
2007-05-01
2012-06-21
Ronald Van Houtan
Enhanced seat belt/accelerator behavioral system
US8285571B2
( en )
2009-02-18
2012-10-09
Toyota Motor Engineering & Manufacturing North America (Tema)
Rideshare system and associated methodology
US20120290950A1
( en )
2011-05-12
2012-11-15
Jeffrey A. Rapaport
Social-topical adaptive networking (stan) system allowing for group based contextual transaction offers and acceptances and hot topic watchdogging
US8325025B2
( en )
2008-12-12
2012-12-04
Gordon*Howard Associates, Inc.
Automated geo-fence boundary configuration and activation
US20130085817A1
( en )
2011-09-29
2013-04-04
Michael Collins Pinkus
Discount offer system and method for use with for hire vehicles
US8433934B1
( en )
2012-06-28
2013-04-30
Google Inc.
Saving battery on wireless connections on mobile devices using internal motion detection
US20130132140A1
( en )
2009-12-04
2013-05-23
Uber Technologies, Inc.
Determining a location related to on-demand services through use of portable computing devices
US8452771B2
( en )
2011-01-03
2013-05-28
Honda Motor Co., Ltd.
Method for differentiating traffic data obtained from probe vehicles
US20130138460A1
( en )
2011-11-29
2013-05-30
Hartford Fire Insurance Company
System and method for administering a telematics-enabled test drive dealer program
US20130197674A1
( en )
2012-01-30
2013-08-01
Apple Inc.
Automatic configuration of self-configurable environments
US20130214919A1
( en )
2012-02-20
2013-08-22
Fred Bassali
Seatbelt usage logging and alerting system
US20130231824A1
( en )
2012-03-05
2013-09-05
Florida A&M University
Artificial Intelligence Valet Systems and Methods
US20130246301A1
( en )
2009-12-04
2013-09-19
Uber Technologies, Inc.
Providing user feedback for transport services through use of mobile devices
US20130335213A1
( en )
2011-02-16
2013-12-19
Toyota Motor Engineering & Manufacturing North America, Inc.
Lane departure warning/assistance method and system having a threshold adjusted based on driver impairment determination using pupil size and driving patterns
KR20140033673A
( en )
2012-09-10
2014-03-19
ì¼ì±ì ì주ìíì¬
System and method for processing information of vehicle
US8686844B1
( en )
2011-06-29
2014-04-01
Intellectual Ventures Fund 79 Llc
Methods, devices, and mediums associated with risk management of vehicle operation
US8700251B1
( en )
2012-04-13
2014-04-15
Google Inc.
System and method for automatically detecting key behaviors by vehicles
US20140129132A1
( en )
2011-07-05
2014-05-08
Toyota Jidosha Kabushiki Kaisha
Recommendation information provision system
US20140129951A1
( en )
2012-11-08
2014-05-08
Uber Technologies, Inc.
Providing on-demand services through use of portable computing devices
US20140172727A1
( en )
2005-12-23
2014-06-19
Raj V. Abhyanker
Short-term automobile rentals in a geo-spatial environment
US8764657B2
( en )
2010-03-24
2014-07-01
Abbott Diabetes Care Inc.
Medical device inserters and processes of inserting and using medical devices
US20140207541A1
( en )
2012-08-06
2014-07-24
Cloudparc, Inc.
Controlling Use of Parking Spaces Using Cameras
US20140207307A1
( en )
2013-01-21
2014-07-24
Volvo Car Corporation
Vehicle driver assist arrangement
US8818608B2
( en )
2012-11-30
2014-08-26
Google Inc.
Engaging and disengaging for autonomous driving
US20140253314A1
( en )
2012-09-24
2014-09-11
Amy Rambadt
Child safety seat mobile alarm and method therefor
US8849494B1
( en )
2013-03-15
2014-09-30
Google Inc.
Data selection by an autonomous vehicle for trajectory modification
US20140316616A1
( en )
2013-03-11
2014-10-23
Airphrame, Inc.
Unmanned aerial vehicle and methods for controlling same
US20140320281A1
( en )
2013-04-23
2014-10-30
Canary Connect, Inc.
System and methods for designating and notifying secondary users for location-based monitoring
US20140336935A1
( en )
2013-05-07
2014-11-13
Google Inc.
Methods and Systems for Detecting Weather Conditions Using Vehicle Onboard Sensors
US20140350855A1
( en )
2012-02-28
2014-11-27
Google Inc.
Systems and Methods for Providing Navigational Assistance to Reserved Parking Locations
US20150012833A1
( en )
2013-07-02
2015-01-08
Fortis Riders Corporation
Mobile application using gestures to facilitate communication
US8948993B2
( en )
2013-03-08
2015-02-03
Richard Schulman
Method and system for controlling the behavior of an occupant of a vehicle
US8949016B1
( en )
2012-09-28
2015-02-03
Google Inc.
Systems and methods for determining whether a driving environment has changed
US8954217B1
( en )
2012-04-11
2015-02-10
Google Inc.
Determining when to drive autonomously
US8954252B1
( en )
2012-09-27
2015-02-10
Google Inc.
Pedestrian notifications
US20150046080A1
( en )
2011-04-19
2015-02-12
Kees Wesselius
Vehicle request management system having a central server
US20150066284A1
( en )
2013-09-05
2015-03-05
Ford Global Technologies, Llc
Autonomous vehicle control for impaired driver
US20150088421A1
( en )
2013-09-26
2015-03-26
Google Inc.
Controlling Navigation Software on a Portable Device from the Head Unit of a Vehicle
US8996224B1
( en )
2013-03-15
2015-03-31
Google Inc.
Detecting that an autonomous vehicle is in a stuck condition
US9008890B1
( en )
2013-03-15
2015-04-14
Google Inc.
Augmented trajectories for autonomous vehicles
US9019107B2
( en )
2013-06-19
2015-04-28
GM Global Technology Operations LLC
Methods and apparatus for detection and reporting of vehicle operator impairment
US20150120504A1
( en )
2013-10-25
2015-04-30
Michael Todasco
Systems and methods for completion of item delivery and transactions using a mobile beacon
US9026300B2
( en )
2012-11-06
2015-05-05
Google Inc.
Methods and systems to aid autonomous vehicles driving through a lane merge
US20150148077A1
( en )
2013-11-25
2015-05-28
Agco Corporation
Dynamic cooperative geofence
US20150149283A1
( en )