Movatterモバイル変換


[0]ホーム

URL:


US12045761B2 - Systems and methods for delivering items to moving vehicles - Google Patents

Systems and methods for delivering items to moving vehicles
Download PDF

Info

Publication number
US12045761B2
US12045761B2US16/580,339US201916580339AUS12045761B2US 12045761 B2US12045761 B2US 12045761B2US 201916580339 AUS201916580339 AUS 201916580339AUS 12045761 B2US12045761 B2US 12045761B2
Authority
US
United States
Prior art keywords
vehicle
zone
item
controller
location
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US16/580,339
Other versions
US20210090018A1 (en
Inventor
Seyhan Uçar
Baik Hoh
Kentaro Oguchi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Toyota Motor Corp
Original Assignee
Toyota Motor Engineering and Manufacturing North America Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Toyota Motor Engineering and Manufacturing North America IncfiledCriticalToyota Motor Engineering and Manufacturing North America Inc
Priority to US16/580,339priorityCriticalpatent/US12045761B2/en
Assigned to TOYOTA MOTOR ENGINEERING & MANUFACTURING NORTH AMERICA, INC.reassignmentTOYOTA MOTOR ENGINEERING & MANUFACTURING NORTH AMERICA, INC.ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS).Assignors: OGUCHI, KENTARO, HOH, BAIK, UÇAR, SEYHAN
Publication of US20210090018A1publicationCriticalpatent/US20210090018A1/en
Application grantedgrantedCritical
Publication of US12045761B2publicationCriticalpatent/US12045761B2/en
Assigned to TOYOTA JIDOSHA KABUSHIKI KAISHAreassignmentTOYOTA JIDOSHA KABUSHIKI KAISHAASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS).Assignors: TOYOTA MOTOR ENGINEERING & MANUFACTURING NORTH AMERICA, INC.
Activelegal-statusCriticalCurrent
Adjusted expirationlegal-statusCritical

Links

Images

Classifications

Definitions

Landscapes

Abstract

A controller for delivering an item is provided. The controller includes one or more processors, one or more memory modules, and machine readable instructions stored in the one or more memory modules. The controller is configured to determine a location or a traveling schedule of a first vehicle and a location of a second device, determine a zone where the first vehicle and the second device are expected to be proximate each other based on traffic information, the location or the traveling schedule of the first vehicle, and the location of the second device, instruct the first vehicle to move to the zone, and instruct the second device to transfer an item to the first vehicle in response to determining that the first vehicle and the second device are proximate each other at the zone.

Description

TECHNICAL FIELD
The present specification generally relates to systems and methods for delivering an item to a moving vehicle and, more specifically, to systems and methods for delivering an item to a moving vehicle by determining a zone where the moving vehicle and a device including the item are expected to be proximate to each other.
BACKGROUND
Items may need to be transferred from a device (e.g., a vehicle or a container) to a vehicle, such as when a customer orders an item and would like to have the item placed in her vehicle from a delivery vehicle or a delivery container.
Accordingly, a need exists for systems for delivering an item to a vehicle.
SUMMARY
In one embodiment, a controller for delivering an item is provided. The controller includes one or more processors, one or more memory modules, and machine readable instructions stored in the one or more memory modules. The controller is configured to determine a location or a traveling schedule of a first vehicle and a location of a second device, determine a zone where the first vehicle and the second device are expected to be proximate each other based on traffic information, the location or the traveling schedule of the first vehicle, and the location of the second device, instruct the first vehicle to move to the zone, and instruct the second device to transfer an item to the first vehicle in response to determining that the first vehicle and the second device are proximate each other at the zone.
In another embodiment, a method for delivering an item is provided. The method includes determining a location or a traveling schedule of a first vehicle and a location of a second device, determining a zone where the first vehicle and the second device are expected to be proximate each other based on traffic information, the location or the traveling schedule of the first vehicle, and the location of the second device, instructing the first vehicle to move to the zone, and instructing the second device to transfer an item to the first vehicle in response to determining that the first vehicle and the second device are proximate each other at the zone.
In yet another embodiment, a system includes a first vehicle, a second device, and a server communicatively coupled to the first vehicle and the second device. The server is configured to determine a zone where the first vehicle and the second device are expected to be proximate each other based on traffic information, a location or a traveling schedule of the first vehicle, and a location of the second device, instruct the first vehicle to move to the zone, and instruct the second device to transfer an item to the first vehicle in response to determining that the first vehicle and the second device are proximate each other at the zone.
These and additional features provided by the embodiments of the present disclosure will be more fully understood in view of the following detailed description, in conjunction with the drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
The embodiments set forth in the drawings are illustrative and exemplary in nature and not intended to limit the disclosure. The following detailed description of the illustrative embodiments can be understood when read in conjunction with the following drawings, where like structure is indicated with like reference numerals and in which:
FIG.1A depicts a system for delivering an item to a moving vehicle, according to one or more embodiments shown and described herein;
FIG.1B depicts transferring the item from a second vehicle to a first vehicle, according to one or more embodiments shown and described herein;
FIG.2 depicts schematic diagrams of the system for delivering an item, according to one or more embodiments shown and described herein;
FIG.3 is a flowchart for delivering an item to a moving vehicle, according to one or more embodiments shown and described herein;
FIG.4 depicts an exemplary scenario where a first vehicle and a second vehicle meet at another zone after failing to deliver an item at an original zone, according to one or more embodiments shown and described herein;
FIG.5 depicts a system for delivering an item to a moving vehicle, according to another embodiment shown and described herein;
FIG.6 depicts a system for delivering an item to a moving vehicle, according to another embodiment shown and described herein; and
FIG.7 depicts a system for delivering an item to a moving vehicle, according to another embodiment shown and described herein.
DETAILED DESCRIPTION
The embodiments disclosed herein include systems and methods for delivering an item to a moving vehicle using another vehicle, such as an unmanned aerial vehicle. Referring generally toFIGS.1A and3, a method for delivering an item to a vehicle using another vehicle, such as an unmanned aerial vehicle is provided. A system determines a location or a traveling schedule of afirst vehicle110 and a location of a second device (e.g., asecond vehicle120 or astationary container710 inFIG.7). The system determines a zone where thefirst vehicle110 and the second device are expected to be proximate each other based on traffic information, the location or the traveling schedule of the first vehicle, and the location of the second device. For example, the system determines that thefirst vehicle110 and the second vehicle are expected to be proximate each other at azone140. The system instructs thefirst vehicle110 to move to thezone140 and instructs thesecond vehicle120 to transfer an item to thefirst vehicle110 in response to determining that thefirst vehicle110 and thesecond vehicle120 are proximate each other at the zone.
The systems and methods according to the present disclosure provide the secure, convenient, and customized delivery of an item to a trusted entity. Specifically, the system of the present disclosure helps a customer to order an item online and pick up the item at a preferred time while commuting on a road. Whenever a customer orders an item, the customer may select a delivery location, a range, and an estimated pick-up time based on her scheduling, e.g., commuting schedule. Based on customer preferences, the estimated location range and pick-up time are selected, and the system organizes delivering an item based on the estimated location range and pick-up time without violation of customer schedule and/or plan. Additionally, according to the present disclosure, an unmanned aerial vehicle may be operated to fly for a short time or distance and within line of sight view of a human operator, which may be compatible with FAA regulations.
FIG.1A depicts a system for delivering an item to a moving vehicle, according to one or more embodiments shown and described herein. In embodiments, thesystem100 includes afirst vehicle110, asecond vehicle120, and aserver160. The details of thefirst vehicle110, thesecond vehicle120, and theserver160 will be described below with reference toFIG.2.
Thefirst vehicle110 and thesecond vehicle120 may be an automobile or any other passenger or non-passenger vehicle such as, for example, a terrestrial, aquatic, and/or airborne vehicle including, but not limited, a bus, a train, a scooter, and a bicycle. In some embodiments, thevehicle110 and thesecond vehicle120 may be an autonomous vehicle that navigates its environment with limited human input or without human input. Each of thefirst vehicle110 and thesecond vehicle120 may transmit its current location and/or a planned route to theserver160. Theserver160 may be a remote server or an edge server such as a road side unit.
In embodiments, thesecond vehicle120 may carry an unmannedaerial vehicle130. For example, the unmannedaerial vehicle130 may be carried in a container of thesecond vehicle120, such as a trunk. As another example, the unmannedaerial vehicle130 may dock onto the top of thesecond vehicle120. In some embodiments, the unmannedaerial vehicle130 may independently follow thesecond vehicle120.
In embodiments, a user may order an item (e.g., by placing an online order) and set a pick-up region and/or time based on her schedule and/or a commute plan. For example, as shown inFIG.1A, a pick-up region150 may be set by the user. The pick-up time may be set at 6:00 pm. As another example, the pick-up time may be set as a range, e.g., between 6:30 pm and 6:40 pm. In response to the order by the user, theserver160 may instruct thesecond vehicle120 to carry theitem132 to the pick-up region150 according to the pick-up time. In embodiments, thefirst vehicle110 may be related to the user ordering the item. For example, the user may be the driver or passenger of thefirst vehicle110. As another example, thefirst vehicle110 may be the vehicle of a person designated by the user ordering the item (e.g., a spouse, family, relative, and the like) to pick up the item.
Theserver160 may determine a zone where thefirst vehicle110 and thesecond vehicle120 are expected to be proximate each other based on traffic information, the location or the traveling schedule of thefirst vehicle110, and/or the location of thesecond vehicle120. The zone may include at least one of a parking lot, a rest area, an intersection, a short-term pull over area, and a low speed limit zone where thefirst vehicle110 and thesecond vehicle120 are expected to be proximate each other. By referring toFIG.1A, theserver160 may determine that thefirst vehicle110 and thesecond vehicle120 are expected to proximate each other at azone140 based on traffic information, the location or the traveling schedule of thefirst vehicle110, and/or the location of thesecond vehicle120. For example, thefirst vehicle110 may be at location L1 and thesecond vehicle120 may be at location L2. Theserver160 may determine that both thefirst vehicle110 and thesecond vehicle120 may arrive at thezone140 approximately at the same time by taking into consideration various factors including the speeds of thefirst vehicle110 and thesecond vehicle120, traffic flow on roads within the pick-upregion150, traffic light information, and the like. Additionally, theserver160 may determine that both thefirst vehicle110 and thesecond vehicle120 may stop or move less than a threshold speed (e.g., 5 miles per hour, 10 miles per hour, etc.) at thezone140 due to the light of atraffic light142 being red or traffic congestion near thezone140.
In some embodiments, theserver160 may provide information about expected delivery time and suggest a departure time of thefirst vehicle110 to thefirst vehicle110. For example, thefirst vehicle110 may commute between home and office. Theserver160 may send to the device of the driver or passenger of the first vehicle110 a message, e.g., “If you leave work at 6:30 pm, you will receive the item you ordered at7:10 at zone A.” In this regard, the driver or the passenger of thefirst vehicle110 may re-schedule his or her plan according to the suggestion from theserver160.
Once theserver160 determines thezone140, theserver160 may transmit routing instructions to thefirst vehicle110 and thesecond vehicle120. In embodiments, theserver160 may instruct thefirst vehicle110 to reroute in order to arrive at thezone140. For example, the original route of thefirst vehicle110 may be a route following adirectional arrow112. Theserver160 may instruct thefirst vehicle110 to change the original route to a route that following adirectional arrow114 such that thefirst vehicle110 may arrive at thezone140 at the same time as thesecond vehicle120 due to, e.g., thetraffic light142. In embodiments, when thefirst vehicle110 and thesecond vehicle120 are proximate each other at thezone140, thesecond vehicle120 may initiate transferring theitem132 from thesecond vehicle120 to thefirst vehicle110.
FIG.1B depicts transferring an item from thesecond vehicle120 to thefirst vehicle110, according to one or more embodiments shown and described herein. As shown inFIG.1B, thefirst vehicle110 and thesecond vehicle120 are at thezone140 and stop or move less than a threshold speed due to, for example, the red light of thetraffic light142 or traffic congestion. In embodiments, theserver160 may instruct thesecond vehicle120 and/or the unmannedaerial vehicle130 to transfer theitem132 to thefirst vehicle110 when it is determined that thefirst vehicle110 and thesecond vehicle120 are proximate each other at thezone140. Theserver160 may determine whether thefirst vehicle110 is an intended recipient of theitem132 and authenticate thefirst vehicle110 before instructing thesecond vehicle120 to transfer theitem132 based on identification information about the first vehicle110 (e.g., a VIN number, a color and model of a vehicle, and the like). In some embodiments, thesecond vehicle120 or the unmannedaerial vehicle130 may authenticate thefirst vehicle110 based on identification information about thefirst vehicle110 received from theserver160.
In response to the instruction from theserver160, thesecond vehicle120 may initiate transferring theitem132 to thefirst vehicle110. For example, thesecond vehicle120 may open a trunk or a sunroof of thesecond vehicle120 and allow the unmannedaerial vehicle130 to transfer theitem132 from thesecond vehicle120 to thefirst vehicle110. Because the unmannedaerial vehicle130 files a relatively short distance for the delivery of an item, the present disclosure addresses conventional problems of deliveries by unmanned aerial vehicle such as insufficient flying range due to limited batteries, and limited flying due to Federal Aviation Administration regulations (e.g., restricted zones, line-of-sight of human operator restrictions, see-and-avoid requirements, etc.)
In some embodiment, thesecond vehicle120 may include a robot arm that may be extended outside of thesecond vehicle120. The robot arm may grab theitem132 and extend theitem132 toward thefirst vehicle110 such that the driver or the passenger of thefirst vehicle110 may receive theitem132.
WhileFIG.1B depicts transferring an item from thesecond vehicle120 to thefirst vehicle110 on a road, items can be transferred at different locations. For example, thefirst vehicle110 may park at a short term parking spot (e.g., parking lot, meter parking, at the like), and thesecond vehicle120 may come to the parking location of thefirst vehicle110 and transfer the item using the unmanned aerial vehicle.
FIG.2 depicts schematic diagrams of the system for delivering an item, according to one or more embodiments shown and described herein.
Thefirst vehicle110 includes one ormore processors201, one ormore memory modules202, anetwork interface hardware203, asatellite antenna204, and one ormore vehicle sensors205.
Each of the one ormore processors201 of thefirst vehicle110 may be any device capable of executing machine readable instructions. Accordingly, each of the one ormore processors201 may be a controller, an integrated circuit, a microchip, a computer, or any other computing device. Each of the one ormore processors201 is communicatively coupled to the other components of thefirst vehicle110 by acommunication path207. Accordingly, thecommunication path207 may communicatively couple any number of processors with one another, and allow the components coupled to thecommunication path207 to operate in a distributed computing environment. Specifically, each of the components may operate as a node that may send and/or receive data.
Each of the one ormore memory modules202 of thefirst vehicle110 is coupled to thecommunication path207 and communicatively coupled to the one ormore processors201. Each of the one ormore memory modules202 may comprise RAM, ROM, flash memories, hard drives, or any device capable of storing machine readable instructions such that the machine readable instructions can be accessed and executed by the one ormore processors201. The machine readable instructions may comprise logic or algorithm(s) written in any programming language of any generation (e.g., 1GL, 2GL, 3GL, 4GL, or 5GL) such as, for example, machine language that may be directly executed by the one ormore processors201, or assembly language, object-oriented programming (OOP), scripting languages, microcode, etc., that may be compiled or assembled into machine readable instructions and stored in the one ormore memory modules202. Alternatively, the machine readable instructions may be written in a hardware description language (HDL), such as logic implemented via either a field-programmable gate array (FPGA) configuration or an application-specific integrated circuit (ASIC), or their equivalents. Accordingly, the functionality described herein may be implemented in any conventional computer programming language, as pre-programmed hardware elements, or as a combination of hardware and software components. The one ormore memory modules202 may include driving history of thefirst vehicle110 including, for example, previous routes, destinations, and the like.
Still referring toFIG.2, thenetwork interface hardware203 is coupled to thecommunication path207 and communicatively coupled to the one ormore processors201. Thenetwork interface hardware203 may be any device capable of transmitting and/or receiving data via a network. Accordingly, thenetwork interface hardware203 can include a communication transceiver for sending and/or receiving any wired or wireless communication. For example, thenetwork interface hardware203 may include an antenna, a modem, LAN port, Wi-Fi card, WiMax card, mobile communications hardware, near-field communication hardware, satellite communication hardware and/or any wired or wireless hardware for communicating with other networks and/or devices. In some embodiments, thenetwork interface hardware203 includes hardware configured to operate in accordance with the Bluetooth wireless communication protocol. In other embodiments, thenetwork interface hardware203 includes hardware configured to operate in accordance with a wireless communication protocol other than Bluetooth. Thenetwork interface hardware203 of thefirst vehicle110 may communicate with theserver160, thesecond vehicle120, or the unmannedaerial vehicle130.
Still referring toFIG.2, asatellite antenna204 is coupled to thecommunication path207 such that thecommunication path207 communicatively couples thesatellite antenna204 to other modules of thefirst vehicle110. Thesatellite antenna204 is configured to receive signals from global positioning system satellites. Specifically, in one embodiment, thesatellite antenna204 includes one or more conductive elements that interact with electromagnetic signals transmitted by global positioning system satellites. The received signal is transformed into a data signal indicative of the location (e.g., latitude, longitude, and altitude) of thesatellite antenna204 or an object positioned near thesatellite antenna204, by the one ormore processors201. The one ormore memory modules202 may include instructions for transmitting the location received by thesatellite antenna204 to theserver160.
Thefirst vehicle110 comprises one ormore vehicle sensors205. Each of the one ormore vehicle sensors205 is coupled to thecommunication path207 and communicatively coupled to the one ormore processors201. The one ormore vehicle sensors205 may include one or more motion sensors for detecting and measuring motion and changes in motion of the vehicle. The motion sensors may include inertial measurement units. Each of the one or more motion sensors may include one or more accelerometers and one or more gyroscopes. Each of the one or more motion sensors transforms sensed physical movement of the vehicle into a signal indicative of an orientation, a rotation, a velocity, or an acceleration of the vehicle.
The unmannedaerial vehicle130 includes one ormore processors211, one ormore memory modules212, anetwork interface hardware213, asatellite antenna214, and one ormore cameras215. Each of the one ormore processors211 of the unmannedaerial vehicle130 may be any device capable of executing machine readable instructions. Accordingly, each of the one ormore processors211 may be a controller, an integrated circuit, a microchip, a computer, or any other computing device. Each of the one ormore processors211 is communicatively coupled to the other components of the unmannedaerial vehicle130 by thecommunication path216.
Each of the one ormore memory modules212 of the unmannedaerial vehicle130 is coupled to thecommunication path216 and communicatively coupled to the one ormore processors211. Each of the one ormore memory modules212 may comprise RAM, ROM, flash memories, hard drives, or any device capable of storing machine readable instructions such that the machine readable instructions can be accessed and executed by the one ormore processors211. The one ormore memory modules212 may include information about a vehicle related to the order of an item. For example, information about the owner of thefirst vehicle110 who ordered an item, and the information about thefirst vehicle110 such as a vehicle model, color, and the like may be transmitted to and stored in the one ormore memory modules212.
Still referring toFIG.2, thenetwork interface hardware213 is coupled to thecommunication path216 and communicatively coupled to the one ormore processors211. Thenetwork interface hardware213 may be any device capable of transmitting and/or receiving data via a network, similar to thenetwork interface hardware213. Thenetwork interface hardware213 of the unmannedaerial vehicle130 may communicate with theserver160, thefirst vehicle110, or thesecond vehicle120.
Still referring toFIG.2, asatellite antenna214 is coupled to thecommunication path216 such that thecommunication path216 communicatively couples thesatellite antenna214 to other modules of the unmannedaerial vehicle130. Thesatellite antenna214 is configured to receive signals from global positioning system satellites similar to thesatellite antenna204.
Still referring toFIG.2, one ormore cameras215 are coupled to thecommunication path216 such that thecommunication path216 communicatively couples the one ormore cameras215 to other modules of the unmannedaerial vehicle130. Each of the one ormore cameras215 may be any device having an array of sensing devices (e.g., pixels) capable of detecting radiation in an ultraviolet wavelength band, a visible light wavelength band, or an infrared wavelength band. Each of the one ormore cameras215 may have any resolution. The one ormore cameras215 may include an omni-directional camera, or a panoramic camera. In some embodiments, one or more optical components, such as a mirror, fish-eye lens, or any other type of lens may be optically coupled to at least one of the one ormore cameras215. The one ormore cameras215 may be used to capture an image of vehicles nearby, e.g., thefirst vehicle110.
Still referring toFIG.2, thecommunication path216 may be formed from any medium that is capable of transmitting a signal such as, for example, conductive wires, conductive traces, optical waveguides, or the like, similarly to thecommunication path207. Moreover, thecommunication path216 may be formed from a combination of mediums capable of transmitting signals.
Now referring to thesecond vehicle120, thesecond vehicle120 includes one ormore processors221, one ormore memory modules222, asatellite antenna223, anetwork interface hardware224, and one ormore vehicle sensors225. The one ormore processors221 may be processors similar to the one ormore processors201 described above. The one ormore memory modules222 may be memories similar to the one ormore memory modules202 described above. Thesatellite antenna223 may be a satellite antenna similar to thesatellite antenna204 described above. Thenetwork interface hardware224 may be an interface hardware similar to thenetwork interface hardware203 described above. The one ormore vehicle sensors225 may be vehicle sensors similar to the one ormore vehicle sensors205 described above. Thecommunication path226 may be a communication path similar to thecommunication path207 described above.
The one ormore memory modules222 of thesecond vehicle120 include apath planner module272, and anentity manager module274. Each of thepath planner module272, and theentity manager module274 may be a program module in the form of operating systems, application program modules, and other program modules stored in one ormore memory modules222. In some embodiments, the program module may be stored in a remote storage device that may communicate with theserver160. Such a program module may include, but is not limited to, routines, subroutines, programs, objects, components, data structures, and the like for performing specific tasks or executing specific data types as will be described below.
Thepath planner module272 is configured to monitor mobility information of entities such as thefirst vehicle110 and thesecond vehicle120 and maintain the destination and route information of the entities. Thepath planner module272 is also configured to inform theentity manager module274 about instructions received from theserver160. Thepath planner module272 verifies the instructions received from theserver160 based on the origin and destination of thefirst vehicle110 or thesecond vehicle120.
Theentity manager module274 is configured to perform coordination with the unmannedaerial vehicle130 and theserver160. Theentity manager module274 may inform theserver160 about mobility or route information and state of delivery. Theentity manager module274 may coordinate communication with one or more item delivery unmanned aerial vehicles. Theentity manager module274 is configured to open or close the container of thesecond vehicle120. For example, theentity manager module274 opens or closes the trunk or sunroof of thesecond vehicle120 or a delivery pod.
Now referring to theserver160, theserver160 includes one ormore processors241, one ormore memory modules245, anetwork interface hardware242, and acommunication path243. The one ormore processors241 may be processors similar to the one ormore processors201 described above. The one ormore memory modules245 may be memories similar to the one ormore memory modules202 described above. Thenetwork interface hardware242 may be an interface hardware similar to thenetwork interface hardware203 described above. Thecommunication path243 may be a communication path similar to thecommunication path207 described above. The one ormore processors241 in combination of one ormore memory modules245 may operate as an electronic control unit for theserver160.
The one ormore memory modules245 of theserver160 includes adelivery manager module250 and anentity manager module260. Thedelivery manager module250 includes adelivery oracle module252 and a delivery planner module254. Theentity manager module260 includes an entityroute planner module262 and an entityinformation manager module264. Each of thedelivery manager module250, thedelivery oracle module252, the delivery planner module254, theentity manager module260, the entityroute planner module262, and the entityinformation manager module264 may be a program module in the form of operating systems, application program modules, and other program modules stored in one ormore memory modules245. In some embodiments, the program module may be stored in a remote storage device that may communicate with theserver160. Such a program module may include, but is not limited to, routines, subroutines, programs, objects, components, data structures, and the like for performing specific tasks or executing specific data types as will be described below.
Thedelivery oracle module252 is configured to determine a meeting time and a zone for thefirst vehicle110 and thesecond vehicle120. Thedelivery oracle module252 may receive mobility information of thefirst vehicle110 and thesecond vehicle120, and compute a time and a zone for a delivery of theitem132 based on actual and/or predicted traffic and road conditions. Thedelivery oracle module252 may inform the delivery planner module254 and the entityroute planner module262 about the time and the zone for the delivery.
The delivery planner module254 is configured to plan the delivery of the item. The delivery planner module254 may optimize on-road item delivery. For example, based on potential meeting time and location pairs received from thedelivery oracle module252, the delivery planner module254 may maximize the delivery by the unmannedaerial vehicle130 and minimize travelling time of thefirst vehicle110 and thesecond vehicle120.
The entityroute planner module262 is configured to plan the route of thefirst vehicle110 based on various factors including, but not limited to, available or predicted traffic information, minimum travelling time, preferences of a driver, and the like. The route may include thezone140 such that thefirst vehicle110 may stop or move less than a threshold value at thezone140 and receive theitem132 from thesecond vehicle120. The entityroute planner module262 is also configured to plan the route of thesecond vehicle120 based on the various factors. The route of thesecond vehicle120 may also include thezone140 such that thefirst vehicle110 and the second vehicle arrive at thezone140 at the same time and perform the delivery of theitem132 by, e.g., the unmannedaerial vehicle130.
The entityinformation manager module264 is configured to receive information about entities such as thefirst vehicle110 and thesecond vehicle120 and the state of item delivery. The information about entities may include, but is not limited to, mobility of the entities, handshaking credential for secure item delivery, and the like. The state of item delivery may include a state where the unmannedaerial vehicle130 is on the way to a meeting location, e.g., thezone140, a state where the unmannedaerial vehicle130 opens the second vehicle and delivers theitem132 to thefirst vehicle110, and a state where the unmannedaerial vehicle130 completed the delivery of the item to thefirst vehicle110. The entityinformation manager module264 may inform thedelivery oracle module252 and the delivery planner module254 about mobility information of entities and state of package delivery.
FIG.3 is a flowchart for delivering an item to a moving vehicle, according to one or more embodiments shown and described herein.
Inblock310, theserver160 determines a location or a traveling schedule of thefirst vehicle110 and a location of a second device (e.g., thesecond vehicle120 or thestationary container710 inFIG.7). Thefirst vehicle110 may transmit the location and the traveling schedule to theserver160 and thesecond vehicle120 may transmit its location to theserver160.
Inblock320, theserver160 determines a zone where thefirst vehicle110 and the second device are expected to be proximate each other based on traffic information, the location or the traveling schedule of the first vehicle, and the location of thesecond vehicle120. For example, by referring toFIG.1, theserver160 may determine that thefirst vehicle110 and thesecond vehicle120 are expected to be proximate each other at thezone140 based on location L1 of thefirst vehicle110, location L2 of thesecond vehicle120, and traffic information including traffic flow information and information about thetraffic light142.
Inblock330, theserver160 instructs thefirst vehicle110 to move to thezone140. For example, theserver160 may transmit a routing instruction to thefirst vehicle110 including the information about thezone140.
Inblock340, theserver160 instructs the second device to transfer an item to the first vehicle in response to determining that thefirst vehicle110 and the second device are proximate each other at the zone. In embodiments, when thefirst vehicle110 and thesecond vehicle120 arrive at thezone140, theserver160 may instruct thesecond vehicle120 to transfer theitem132 to thefirst vehicle110. Thesecond vehicle120 may open its trunk or sunroof and the unmannedaerial vehicle130 may transfer theitem132 from thesecond vehicle120 to thefirst vehicle110 by flying a relatively short distance. In embodiments, theserver160 may determine that thefirst vehicle110 and thesecond vehicle120 are proximate each other by receiving messages from thefirst vehicle110 and thesecond vehicle120 indicating respective positions of thefirst vehicle110 and thesecond vehicle120, and determining that the positions are within a threshold distance from one another and are in the zone. In embodiments, theserver160 may determine that thefirst vehicle110 and thesecond vehicle120 are proximate each other by receiving messages from thefirst vehicle110 and thesecond vehicle120 indicating respective positions of thefirst vehicle110 and thesecond vehicle120, and determining that the positions are within the zone. In embodiments, theserver160 may determine that thefirst vehicle110 and thesecond vehicle120 are proximate each other by receiving messages from thefirst vehicle110 and thesecond vehicle120 indicating respective positions of thefirst vehicle110 and thesecond vehicle120, and determining that the positions are within a threshold distance of the zone.
In some embodiments, theserver160 may determine whether thefirst vehicle110 and thesecond vehicle120 stop at thezone140 or move less than a threshold speed based on mobility data received from thefirst vehicle110 and thesecond vehicle120. If it is determined that thefirst vehicle110 and thesecond vehicle120 stop at thezone140 or move slower than a threshold speed, theserver160 may instruct thesecond vehicle120 to transfer theitem132 to thefirst vehicle110. If it is determined that thefirst vehicle110 and thesecond vehicle120 do not stop at thezone140 or move faster than a threshold speed, theserver160 may instruct thesecond vehicle120 to defer the delivery of theitem132.
Inblock350, theserver160 may determine whether the item is transferred to thefirst vehicle110 at the zone. In embodiments, thesecond vehicle120 may transmit the status of the delivery of the item to theserver160. If the status indicates that theitem132 is transferred to thefirst vehicle110, theserver160 may update the status of the delivery as completed.
If the status indicates that theitem132 has not been transferred to thefirst vehicle110 after thefirst vehicle110 departs the zone140 (NO at block350), theserver160 may determine another zone where thefirst vehicle110 and thesecond vehicle120 are expected to be proximate each other based on traffic information, the location or the traveling schedule of thefirst vehicle110, and the location of thesecond vehicle120 atblock360. By referring toFIG.4, thefirst vehicle110 and thesecond vehicle120 are expected to be proximate each other at thezone140 and stop at thezone140. However, due to the change of a traffic light, e.g., from red to green, thefirst vehicle110 may pass thezone140 without stopping at thezone140. In this example, thesecond vehicle120 may not be able to deliver theitem132 using the unmannedaerial vehicle130 flying a short distance. Then, theserver160 may determine anotherzone440 where thefirst vehicle110 and thesecond vehicle120 are expected to be proximate each other based on traffic information, the location or the traveling schedule of thefirst vehicle110, and the location of thesecond vehicle120.
Referring back toFIG.3, inblock370, theserver160 instructs thefirst vehicle110 to move to another zone. For example, referring toFIG.4, theserver160 may transmit a routing instruction to thefirst vehicle110 to follow aroute422 that leads to thezone440. Theserver160 may also transmit a routing instruction to thesecond vehicle120 to follow aroute420 that leads to thezone440.
Referring back toFIG.3, inblock380, theserver160 instructs thesecond vehicle120 to transfer the item to thefirst vehicle110 in response to determining that thefirst vehicle110 and the second device are proximate each other at thezone440.
If the status indicates that theitem132 has been transferred to thefirst vehicle110 after thefirst vehicle110 departs the zone140 (YES at block350), theserver160 may determine that delivery has been completed atblock390.
FIG.5 depicts a system for delivering an item to a moving vehicle, according to another embodiment shown and described herein. In embodiments, thesystem500 includes thefirst vehicle110, thesecond vehicle120, athird vehicle520, astore510 and aserver160. Thethird vehicle520 may be a vehicle similar to thesecond vehicle120. InFIG.5, the ordereditem132 is not available in delivery vehicles within or proximate to the pick-upregion150. Thestore510 storing theitem132 may transfer theitem132 to thethird vehicle520 using the unmannedaerial vehicle130. Thethird vehicle520 drives to azone530 where thethird vehicle520 and thesecond vehicle120 are proximate each other. Then, the unmannedaerial vehicle130 may transfer theitem132 from thethird vehicle520 to thesecond vehicle120 in a similar way as the unmannedaerial vehicle130 transfers the item from thesecond vehicle120 to thefirst vehicle110 as discussed above with reference toFIG.1B. After the transfer of the item from thethird vehicle520 to thesecond vehicle120, the unmannedaerial vehicle130 may be carried in thesecond vehicle120 or follow thesecond vehicle120. Then, thefirst vehicle110 and thesecond vehicle120 meet at thezone140 and the unmannedaerial vehicle130 transfers theitem132 from thesecond vehicle120 to thefirst vehicle110.
FIG.6 depicts a system for delivering an item to a moving vehicle, according to another embodiment shown and described herein. In embodiment, thesystem600 includes afirst vehicle110, aserver160, astore610, and an unmannedaerial vehicle620.
Thefirst vehicle110 may transmit the location and route of thefirst vehicle110 to theserver160. For example, thefirst vehicle110 may transmit aroute640 as its intended route to theserver160. Thestore610 includes a geo-fence area612. In embodiments, once thefirst vehicle110 comes within the geo-fence area612, the store610 (e.g., by way of a server associated with the store610) may take control over thefirst vehicle110 and operate thefirst vehicle110 to follow theroute642. In some embodiments, once thefirst vehicle110 comes within the geo-fence area612, theserver160 may transmit a routing instruction to thefirst vehicle110 to follow theroute642 instead of theroute640.
When thefirst vehicle110 arrives at azone650, thestore610 may dispatch the unmannedaerial vehicle620 to transfer theitem630 to thefirst vehicle110. In this example, the unmannedaerial vehicle620 only needs to fly a relatively short distance. Once the delivery is completed, the unmannedaerial vehicle620 may return and stay at thestore610. In some embodiments, right before the first vehicle arrives at azone650, the store610 (e.g., by way of a server associated with the store610) may dispatch the unmannedaerial vehicle620 such that the unmannedaerial vehicle620 and thevehicle110 meet at thezone650 at the same time.
FIG.7 depicts a system for delivering an item to a moving vehicle, according to another embodiment shown and described herein. In embodiment, thesystem700 includes afirst vehicle110, aserver160, astore610, an unmannedaerial vehicle620, and astationary container710.
Thefirst vehicle110 may transmit the location and route of thefirst vehicle110 to theserver160. For example, thefirst vehicle110 may transmit aroute724 as its intended route to theserver160. Thestore610 includes a geo-fence area612. In embodiments, once thefirst vehicle110 comes within the geo-fence area612, thestore610 may take control over thefirst vehicle110 and operate thevehicle110 to follow theroute722. In some embodiments, once thefirst vehicle110 comes within the geo-fence area612, theserver160 may transmit a routing instruction to thefirst vehicle110 to follow theroute722 instead of theroute724.
When thefirst vehicle110 arrives at azone730, thestationary container710 containing theitem630 may open its container such that thefirst vehicle110 may pick up theitem630. In embodiments, the unmannedaerial vehicle620 may deliver theitem630 from thestore610 to thestationary container710 in advance of the first vehicle arriving thezone730. For example, when theitem110 is ordered by the driver or passenger of thefirst vehicle110, the unmannedaerial vehicle620 may transfer theitem630 form thestore610 to thestationary container710. As another example, when it is determined that thefirst vehicle110 enters the geo-fence area612, the unmannedaerial vehicle620 may transfer theitem630 form thestore610 to thestationary container710.
Thesystem700 may include additional stationary containers, e.g., astationary container720. If thefirst vehicle110 fails to receive theitem630 at thezone730, thefirst vehicle110 may be provided another opportunity to receive the item from thestationary container720 at azone740. In this example, the unmannedaerial vehicle620 may transfer the same item to both thestationary containers710 and720. In another example, the unmannedaerial vehicle620 may transfer the item in thestationary container710 to thestationary container720.
It should be understood that embodiments described herein are directed to methods and systems for delivering an item. The method includes determining a location or a traveling schedule of a first vehicle and a location of a second device, determining a zone where the first vehicle and the second device are expected to be proximate each other based on traffic information, the location or the traveling schedule of the first vehicle, and the location of the second device, instructing the first vehicle to move to the zone, and instructing the second device to transfer an item to the first vehicle in response to determining that the first vehicle and the second device are proximate each other at the zone.
According to the present disclosure, an item is delivered to a trusted entity (e.g., a vehicle) while the entity is on-road. A system of the present disclosure seeks to accommodate customer preferences and aims to conveniently deliver items based on a customer's schedule. The system first tries to perform on-road drone package delivery near a store. If this logistics is not possible and/or creates an unwanted congestion, then the system instructs two entities (e.g., a drone-hosted delivery entity and customer selected trusted entity) to reroute such that they meet with each other and stay stationary enough based on dynamic, static and/or predetermined metrics such as available/predicted traffic information and/or road conditions for on-road drone package delivery. When the entities meet with each other, an unmanned aerial vehicle delivers the item from a delivery entity to a customer entity. The system may utilize short-range communication to verify and authenticate between the delivery and customer entities.
The systems and methods according to the present disclosure provide the secure, convenient, and customized delivery of an item to a trusted entity. Specifically, the system of the present disclosure helps a customer to order an item online and pick up the item at a preferred time while commuting on road. Whenever a customer orders an item, the customer may select a delivery location, a range and an estimated pick-up time based on her schedule, e.g., commuting schedule. Based on customer preferences, the estimated location range and pick-up time are elected, and the system organizes delivering an item based on the estimated location range and pick-up time according to the customer's schedule and/or plan. Additionally, according to the present disclosure, an unmanned aerial vehicle operates to fly for a short time and/or distance and to fly within the line of sight view of a human operator.
It is noted that the terms “substantially” and “about” may be utilized herein to represent the inherent degree of uncertainty that may be attributed to any quantitative comparison, value, measurement, or other representation. These terms are also utilized herein to represent the degree by which a quantitative representation may vary from a stated reference without resulting in a change in the basic function of the subject matter at issue.
While particular embodiments have been illustrated and described herein, it should be understood that various other changes and modifications may be made without departing from the spirit and scope of the claimed subject matter. Moreover, although various aspects of the claimed subject matter have been described herein, such aspects need not be utilized in combination. It is therefore intended that the appended claims cover all such changes and modifications that are within the scope of the claimed subject matter.

Claims (18)

What is claimed is:
1. A system comprising:
a controller programmed to:
determine at least one of a location and a traveling schedule of a first vehicle and a location of a second device, wherein the second device is a vehicle;
determine a zone where the first vehicle and the second device are expected to be proximate each other based on traffic information, at least one of the location and the traveling schedule of the first vehicle, and the location of the second device;
instruct the first vehicle to move to the zone;
determine whether the first vehicle and the second device move less than a threshold speed based on mobility data received from the first vehicle and the second device;
instruct an unmanned aerial vehicle to transfer an item from the second device to the first vehicle in response to determining that the first vehicle and the second device are proximate each other at the zone and the first vehicle and the second device move slower than the threshold speed;
instruct the unmanned aerial vehicle to defer to transfer the item from the second device to the first vehicle in response to determining that the first vehicle and the second device move faster than the threshold speed;
receive a route of the first vehicle;
determine whether the first vehicle is within a geo-fence of a store;
control movement of the first vehicle in response to determination that the first vehicle is within the geo-fence of the store; and
operate the first vehicle to follow the route of the first vehicle.
2. The system ofclaim 1, wherein:
the second device includes the item, and
the controller is further programmed to:
instruct the second device to move to the zone.
3. The system ofclaim 1, wherein:
the controller is further programmed to:
obtain a trajectory of the first vehicle; and
instruct a store to deliver the item to the second device before the first vehicle arrives at the zone based on the trajectory.
4. The system ofclaim 1, wherein:
the controller is further programmed to:
authenticate the first vehicle in response to determining that the first vehicle and the second device are proximate each other at the zone.
5. The system ofclaim 1, wherein the traffic information includes at least one of a traffic condition, a chronic congested area, and traffic light information at intersections.
6. The system ofclaim 1, wherein the controller is further programmed to:
determine the zone where the first vehicle and the second device are expected to be proximate each other based on one or more locations where the first vehicle is expected to stop or move less than a predetermined speed.
7. The system ofclaim 1, wherein the zone includes at least one of a parking lot, a rest area, an intersection, a short-term pull over area, and a low speed limit zone.
8. The system ofclaim 1, wherein the controller is further programmed to:
determine the zone where the first vehicle and the second device are expected to move less than a threshold speed or stop for a predetermined time based on traffic information.
9. The system ofclaim 1, wherein the controller is further programmed to:
instruct the second device to open a trunk or a sunroof of the second device in response to determining that the first vehicle and the second device are proximate each other at the zone.
10. The system ofclaim 1, wherein the controller is further programmed to:
receive a route of the first vehicle;
determine whether the route of the first vehicle overlaps with the zone;
update the route of the first vehicle such that the route overlaps with the zone in response to determination that the route of the first vehicle does not overlap with the zone; and
instruct the first vehicle to follow the updated route.
11. The system ofclaim 1, wherein the controller is further programmed to:
determine whether the item is in the second device after the first vehicle departs from the zone; and
instruct the first vehicle to move to a predetermined location in response to determination that the item is in the second device after the first vehicle departs from the zone.
12. The system ofclaim 1, wherein the controller is further programmed to:
determine whether the item is in the second device after the first vehicle departs from the zone;
determine another zone where the first vehicle and the second device are expected to be proximate each other based on traffic information, the location or the traveling schedule of the first vehicle, and the location of the second device;
instruct the first vehicle to move to the another zone in response to determination that the item is in the second device after the first vehicle departs from the zone; and
instruct the second device to transfer the item to the first vehicle in response to determining that the first vehicle and the second device are proximate each other at the another zone.
13. The system ofclaim 1, wherein the controller is further programmed to:
receive an order for the item from a terminal of a user; and
obtain a commute path or a trajectory of the first vehicle, wherein the first vehicle is a vehicle authorized by the user.
14. The system ofclaim 1, wherein the controller is further programmed to:
obtain a commute path or a trajectory of the first vehicle; obtain a trajectory or a location of the second device; and
determine the zone where the first vehicle and the second device are expected to be proximate each other further based on the commute path or the trajectory of the first vehicle and the trajectory or the location of the second device.
15. The system ofclaim 1, wherein the controller is further programmed to:
instruct the unmanned aerial vehicle to transfer the item from a store to a third vehicle;
instruct the third vehicle to drive to a zone where the third vehicle and the second device are proximate each other;
instruct the unmanned aerial vehicle to transfer the item from the third vehicle to the second device;
instruct the unmanned aerial vehicle to be carried in the second device or follow the second device; and
instruct the unmanned aerial vehicle to transfer the item from the second device to the first vehicle at a zone where the first vehicle and the second device are proximate each other.
16. A method for delivering an item, the method comprising:
determining, by a controller, at least one of a location and a traveling schedule of a first vehicle and a location of a second device, wherein the second device is a vehicle;
determining, by the controller, a zone where the first vehicle and the second device are expected to be proximate each other based on traffic information, at least one of the location and the traveling schedule of the first vehicle, and the location of the second device;
instructing, by the controller, the first vehicle to move to the zone;
determining, by the controller, whether the first vehicle and the second device move less than a threshold speed based on mobility data received from the first vehicle and the second device;
instructing, by the controller, an unmanned aerial vehicle to transfer an item from the second device to the first vehicle in response to determining that the first vehicle and the second device are proximate each other at the zone and the first vehicle and the second device move slower than the threshold speed;
instructing, by the controller, the unmanned aerial vehicle to defer to transfer the item from the second device to the first vehicle in response to determining that the first vehicle and the second device move faster than the threshold speed;
receiving, by the controller, a route of the first vehicle;
determining, by the controller, whether the first vehicle is within a geo-fence of a store;
controlling, by the controller, movement of the first vehicle in response to determination that the first vehicle is within the geo-fence of the store; and
operating, by the controller, the first vehicle to follow the route of the first vehicle.
17. The method ofclaim 16, further comprising:
receiving, by the controller, a route of the first vehicle;
determining, by the controller, whether the route of the first vehicle overlaps with the zone;
updating, by the controller, the route of the first vehicle such that the route overlaps with the zone in response to determination that the route of the first vehicle does not overlap with the zone; and
instructing, by the controller, the first vehicle to follow the updated route.
18. A system comprising:
a first vehicle;
a second device, wherein the second device is a vehicle; and
a server communicatively coupled to the first vehicle and the second device and configured to:
determine a zone where the first vehicle and the second device are expected to be proximate each other based on traffic information, at least one of a location and a traveling schedule of the first vehicle, and a location of the second device;
instruct the first vehicle to move to the zone;
determine whether the first vehicle and the second device move less than a threshold speed based on mobility data received from the first vehicle and the second device;
instruct an unmanned aerial vehicle to transfer an item from the second device to the first vehicle in response to determining that the first vehicle and the second device are proximate each other at the zone and the first vehicle and the second device move slower than the threshold speed;
instruct the unmanned aerial vehicle to defer to transfer the item from the second device to the first vehicle in response to determining that the first vehicle and the second device move faster than the threshold speed;
receive a route of the first vehicle;
determine whether the first vehicle is within a geo-fence of a store;
control movement of the first vehicle in response to determination that the first vehicle is within the geo-fence of the store; and
operate the first vehicle to follow the route of the first vehicle.
US16/580,3392019-09-242019-09-24Systems and methods for delivering items to moving vehiclesActive2041-10-12US12045761B2 (en)

Priority Applications (1)

Application NumberPriority DateFiling DateTitle
US16/580,339US12045761B2 (en)2019-09-242019-09-24Systems and methods for delivering items to moving vehicles

Applications Claiming Priority (1)

Application NumberPriority DateFiling DateTitle
US16/580,339US12045761B2 (en)2019-09-242019-09-24Systems and methods for delivering items to moving vehicles

Publications (2)

Publication NumberPublication Date
US20210090018A1 US20210090018A1 (en)2021-03-25
US12045761B2true US12045761B2 (en)2024-07-23

Family

ID=74882155

Family Applications (1)

Application NumberTitlePriority DateFiling Date
US16/580,339Active2041-10-12US12045761B2 (en)2019-09-242019-09-24Systems and methods for delivering items to moving vehicles

Country Status (1)

CountryLink
US (1)US12045761B2 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
US20210174689A1 (en)*2019-12-042021-06-10Bae Systems Information And Electronic Systems Integration Inc.Situational awareness ground transmitter
JP2021163160A (en)*2020-03-312021-10-11本田技研工業株式会社Information providing device, information providing system, information providing method, and program
KR20240053821A (en)*2022-10-182024-04-25현대자동차주식회사Method and Apparatus for Providing Information on Management of Vehicle

Citations (16)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
US20150242811A1 (en)*2012-12-212015-08-27United Parcel Service Of America, Inc.Delivery of an item to a vehicle
US20150370251A1 (en)2014-06-202015-12-24Hti, Ip, L.L.C.Method and system for drone deliveries to vehicles in route
DE102015005892B3 (en)2015-05-082016-09-15Audi Ag Method of transferring at least one item
US9659502B1 (en)2015-12-182017-05-23International Business Machines CorporationDrone range extension via host vehicles
US9731821B2 (en)2014-09-102017-08-15International Business Machines CorporationPackage transport by unmanned aerial vehicles
US20180082356A1 (en)*2016-09-212018-03-22Wal-Mart Stores, Inc.Systems and methods for determining customer availability for customer pick up of orders
WO2018065977A1 (en)2016-10-072018-04-12Shmuel Ur Innovation Ltd.Drone based delivery system using vehicles
US20180137454A1 (en)2016-11-162018-05-17Staples, Inc.Autonomous Multimodal Logistics
US9981745B2 (en)2016-04-292018-05-29United Parcel Service Of America, Inc.Unmanned aerial vehicle including a removable parcel carrier
WO2018169695A1 (en)2017-03-162018-09-20Amazon Technologies, Inc.Mobile fulfillment centers with intermodal carriers and unmanned aerial vehicles
US20190043001A1 (en)2017-08-022019-02-07Microsoft Technology Licensing, LlcSystems and methods for scheduling en route product delivery
US20190043370A1 (en)*2017-08-022019-02-07Microsoft Technology Licensing, LlcEn route product delivery by unmanned aerial vehicles
US10467579B1 (en)*2015-03-202019-11-05Square, Inc.Systems, method, and computer-readable media for estimating timing for delivery orders
US20200286034A1 (en)*2017-09-252020-09-10Shmuel Ur Innovation LtdDrone based delivery system using vehicles
US20200349511A1 (en)*2019-05-042020-11-05United States Postal ServiceSystems and methods of local area optimization for routing and delivery of items
US20210166192A1 (en)*2018-04-162021-06-03Ford Global Technologies, LlcItem shipment for passengers

Patent Citations (17)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
US20150242811A1 (en)*2012-12-212015-08-27United Parcel Service Of America, Inc.Delivery of an item to a vehicle
US20150370251A1 (en)2014-06-202015-12-24Hti, Ip, L.L.C.Method and system for drone deliveries to vehicles in route
US9494937B2 (en)*2014-06-202016-11-15Verizon Telematics Inc.Method and system for drone deliveries to vehicles in route
US9731821B2 (en)2014-09-102017-08-15International Business Machines CorporationPackage transport by unmanned aerial vehicles
US10467579B1 (en)*2015-03-202019-11-05Square, Inc.Systems, method, and computer-readable media for estimating timing for delivery orders
DE102015005892B3 (en)2015-05-082016-09-15Audi Ag Method of transferring at least one item
US9659502B1 (en)2015-12-182017-05-23International Business Machines CorporationDrone range extension via host vehicles
US9981745B2 (en)2016-04-292018-05-29United Parcel Service Of America, Inc.Unmanned aerial vehicle including a removable parcel carrier
US20180082356A1 (en)*2016-09-212018-03-22Wal-Mart Stores, Inc.Systems and methods for determining customer availability for customer pick up of orders
WO2018065977A1 (en)2016-10-072018-04-12Shmuel Ur Innovation Ltd.Drone based delivery system using vehicles
US20180137454A1 (en)2016-11-162018-05-17Staples, Inc.Autonomous Multimodal Logistics
WO2018169695A1 (en)2017-03-162018-09-20Amazon Technologies, Inc.Mobile fulfillment centers with intermodal carriers and unmanned aerial vehicles
US20190043001A1 (en)2017-08-022019-02-07Microsoft Technology Licensing, LlcSystems and methods for scheduling en route product delivery
US20190043370A1 (en)*2017-08-022019-02-07Microsoft Technology Licensing, LlcEn route product delivery by unmanned aerial vehicles
US20200286034A1 (en)*2017-09-252020-09-10Shmuel Ur Innovation LtdDrone based delivery system using vehicles
US20210166192A1 (en)*2018-04-162021-06-03Ford Global Technologies, LlcItem shipment for passengers
US20200349511A1 (en)*2019-05-042020-11-05United States Postal ServiceSystems and methods of local area optimization for routing and delivery of items

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
Amy Frearson, "BMW Concept Car Could Receive Drone Deliveries On The Move", Jan. 6, 2017, URL: https://www.dezeen.com/2017/01/06/bmw-5-series-sedan-concept-car-ces-consumerelectronics-show-2017-drone-deliveries/.
Ghazzai, et al., "On the Placement of UAV Docking Stations for Future Intelligent Transportation Systems", IEEE Vehicular Technology Conference (VTC Spring), 2017.
Ryan Randazzo, "Waymo's driverless cars on the road: Cautious, clunky, impressive," AZCentral.com, https://www.azcentral.com/story/money/business/tech/2018/12/05/phoenix-waymo-vans-how-self-driving-cars-operate-roads/2082664002/, Dec. 5, 2018 (Year: 2018).*

Also Published As

Publication numberPublication date
US20210090018A1 (en)2021-03-25

Similar Documents

PublicationPublication DateTitle
US11513537B2 (en)Managing drones in vehicular system
US10545500B2 (en)Model for determining drop-off spot at delivery location
US11474515B2 (en)Method and control apparatus for an autonomous and/or semiautonomous transport vehicle
US11378980B2 (en)Cellular device location discovery systems and methods for autonomous vehicles
US11970190B2 (en)Autonomous vehicle stations
US12045761B2 (en)Systems and methods for delivering items to moving vehicles
US11397913B2 (en)Systems and methods for automated multimodal delivery
CN108931971A (en)For unpiloted mobile terminal, vehicle, server and Unmanned Systems
US11367357B2 (en)Traffic control apparatus, traffic control system, traffic control method, and non-transitory computer recording medium
US10755582B2 (en)Drone physical and data interface for enhanced distance coverage
CN111103893A (en)System and method for transferring control of an unmanned aerial vehicle
US20190258270A1 (en)Traveling control system for autonomous traveling vehicles, server apparatus, and autonomous traveling vehicle
US12014630B2 (en)Systems and methods for assisting a maneuver of a moving object
JP2020149640A (en) Flight system and landing control method
US20220041146A1 (en)Systems and Methods for Emergency Braking in Autonomous Vehicles
US11964672B2 (en)Passenger transportation system, method of passenger transportation, and vehicle controller
EP3755971B1 (en)Remote operation extending an existing route to a destination
US20230290257A1 (en)Vehicle controller
JPWO2019171749A1 (en) Traffic control system
US20230384797A1 (en)System and method for inbound and outbound autonomous vehicle operations
JP2021168022A (en)Automatic control system, automatic control method, and automatic control device
WO2023229731A1 (en)System and method for inbound and outbound autonomous vehicle operations
WO2024142373A1 (en)Intuitive display of traveling route of unmanned traveling vehicle
CN119160103A (en) Control device and control method

Legal Events

DateCodeTitleDescription
ASAssignment

Owner name:TOYOTA MOTOR ENGINEERING & MANUFACTURING NORTH AMERICA, INC., TEXAS

Free format text:ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:UCAR, SEYHAN;HOH, BAIK;OGUCHI, KENTARO;SIGNING DATES FROM 20190809 TO 20190923;REEL/FRAME:050472/0649

FEPPFee payment procedure

Free format text:ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STPPInformation on status: patent application and granting procedure in general

Free format text:DOCKETED NEW CASE - READY FOR EXAMINATION

STPPInformation on status: patent application and granting procedure in general

Free format text:NON FINAL ACTION MAILED

STPPInformation on status: patent application and granting procedure in general

Free format text:RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPPInformation on status: patent application and granting procedure in general

Free format text:FINAL REJECTION MAILED

STPPInformation on status: patent application and granting procedure in general

Free format text:RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER

STPPInformation on status: patent application and granting procedure in general

Free format text:ADVISORY ACTION MAILED

STPPInformation on status: patent application and granting procedure in general

Free format text:NON FINAL ACTION MAILED

STPPInformation on status: patent application and granting procedure in general

Free format text:RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPPInformation on status: patent application and granting procedure in general

Free format text:FINAL REJECTION MAILED

STPPInformation on status: patent application and granting procedure in general

Free format text:RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER

STPPInformation on status: patent application and granting procedure in general

Free format text:ADVISORY ACTION MAILED

STPPInformation on status: patent application and granting procedure in general

Free format text:NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

ZAAANotice of allowance and fees due

Free format text:ORIGINAL CODE: NOA

ZAABNotice of allowance mailed

Free format text:ORIGINAL CODE: MN/=.

STPPInformation on status: patent application and granting procedure in general

Free format text:NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

ZAAANotice of allowance and fees due

Free format text:ORIGINAL CODE: NOA

STPPInformation on status: patent application and granting procedure in general

Free format text:PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCFInformation on status: patent grant

Free format text:PATENTED CASE

ASAssignment

Owner name:TOYOTA JIDOSHA KABUSHIKI KAISHA, JAPAN

Free format text:ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TOYOTA MOTOR ENGINEERING & MANUFACTURING NORTH AMERICA, INC.;REEL/FRAME:068507/0228

Effective date:20240814

CCCertificate of correction

[8]ページ先頭

©2009-2025 Movatter.jp