US2019266518A1PendingUtilityA1
Dispatch system and method of dispatching vehicles
Individually held — no corporate assignee on recordPriority: Aug 5, 2014Filed: May 7, 2019Published: Aug 29, 2019
Est. expiryAug 5, 2034(~8 yrs left)· nominal 20-yr term from priority
H04W 4/021G01C 21/3438H04W 4/023G06Q 10/02G06Q 10/063114G01C 21/3697H04W 4/46H04W 4/024G01C 21/3415G06Q 50/30G06Q 50/40
57
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
Provided are a fully automated dispatch system and method of dispatching vehicles that requires no direct communication between a dispatch person and the driver or passenger.
Claims
exact text as granted — not AI-modifiedWe claim:
1 . A method of dispatching vehicles for hire comprising:
providing a system comprising at least one cloud-based server comprising a non-volatile memory; logging onto the system by a booker; entering passenger information into the non-volatile memory by the booker; entering a pickup location and a drop-off location into the system by the booker; searching for a vehicle in the system by the booker; selecting a vehicle by the booker; determining by the system a best driver for a passenger; logging onto the system by the driver; entering driver information into a database stored in the non-volatile memory; automatically validating driver information by the system, and if the driver's information is validated, providing logon information for a driver app to the driver; running the driver app by the driver on a driver user interface device; automatically validating passenger information by the system, and if the passengers information is validated, providing logon information for a passenger app to the passenger; running the passenger app by the passenger on a passenger user interface device; validating by the system that the passenger app is running on the passenger user interface device; inputting an internet protocol (IP) address of the passenger user interface device to the non-volatile memory; using the IP address by the system to determine a location of the passenger user interface device; validating by the system that the driver app is running on the driver user interface device; determining by the system at least one route for the driver between the pickup location and drop-off location, and providing the at least one route to the driver app for the driver to view on the driver user interface device; picking up the passenger at the pickup location by the driver; determining in real time a real time location of the driver user interface device using a global positioning system (GPS) and if the GPS is not on determining in real time the location of the driver user interface device using triangulation; determining in real time a real time location of the passenger user interface device using the GPS and if the GPS is not on determining in real time the location of the passenger user interface device using triangulation; determining proximity of the passenger to the driver by the system based on the real time locations of the driver user interface device and the passenger user interface device; confirming by the system that the driver and passenger are in the same location during a ride based on the real time locations of the driver user interface device and the passenger user interface device; using a function on the driver user interface device by the driver that meets hands-free requirements to communicate with the system to enter information to the system during driving of the passenger by the driver; and confirming by the system that the driver and the passenger are not in same location after the driver leaves the passenger at the drop-off location based on the real time locations of the driver user interface device and the passenger user interface device, wherein the method is conducted without the use of a dispatch person communicating directly with the driver or passenger.
2 . The method according to claim 1 , wherein the booker is an account holder registered with the system.
3 . The method according to claim 1 , further comprising the system alerting the account holder if a requirement is not met, the requirement being at least one selected from the group of security requirements, ride management permissions, passenger requirements, booker requirements, and account holder requirements.
4 . The method according to claim 1 , wherein the passenger validation comprising address validation by geo location information.
5 . The method according to claim 1 , further comprising determining by the system a price for dispatching a vehicle to transport the passenger from the pickup location to the drop-off location, the price based at least one of the price of alternative transportation, time of day, seasonal demand, day of week, passenger ride history, passenger preferences, account preferences, vehicle type, competitor pricing, and local events.
6 . The method according to claim 1 , wherein the system determines the best driver by weighing at least one of the following factors vehicle type, driver profile, languages spoken, country of origin, passenger capacity, luggage capacity, vehicle features, profitability, driver ranking based on reviews from passengers, location proximity to passenger, client preference, trip information, passenger preference, company preference, accountholder preference, and/or booker preference.
7 . The method according to claim 1 , wherein if the best driver rejects the ride, the second best driver is offered the ride, and repeating the steps of determining the next best driver until a driver accepts the ride.
8 . The method according to claim 1 , wherein the system determines the proximity of the passenger to the driver by the driver user interface device and passenger user interface device communicating with each other and or the system.
9 . The method according to claim 8 , wherein the driver user interface device and the passenger user interface device communicate by an ultra low frequency signal and microphones.
10 . The method according to claim 1 , wherein if the driver cannot fulfill the ride, the system determines the next best driver.
11 . The method according to claim 1 , wherein the system determines a best route and sends the best route to the driver app.
12 . The method according to claim 11 , wherein the system determines the best route based on at least one of weather, construction, traffic accidents, detours, flight delays, and events.
13 . The method according to claim 1 , wherein the system determines when the driver deviates from the route and alerts the driver of the deviation.
14 . The method according to claim 1 , wherein the system determines an estimated time of arrival to the pickup location based on vehicle location and speed limits from the driver location to pickup location, and sends the estimated time of arrival to the passenger app.
15 . The method according to claim 1 , further comprising the system confirming passenger flight information and adjusting drop-off and/or pickup times based on the passenger flight information.
16 . The method according to claim 1 , further comprising the driver entering changes into the system during the ride by a hand-free method.
17 . The method according to claim 16 , wherein the change comprises at least one of additional stops, delays, passenger requests, environmental, and accidents.
18 . The method according to claim 1 , further comprising the system sending a settlement to the driver and/or passenger when the driver is at the drop-off location.
19 . The method according to claim 1 , further comprising the system sending a message to the driver app to enter a review of the passenger.
20 . The method according to claim 19 , further comprising the driver entering a passenger review into the passenger app, and the passenger review being stored in the database.
21 . The method according to claim 1 , further comprising the system sending a message to the passenger app to enter a review of the driver.
22 . A system for dispatching vehicles comprising:
a cloud based server connected to a network, the cloud based server being in communication with or comprising at least one non-volatile memory; a driver user interface device in communication with the cloud based server via the network; a passenger user interface device in communication with the cloud based server via the network; a dispatch computer and/or dispatch user interface device in communication with the cloud based server; a driver app software module stored in the non-volatile memory, the driver app allowing a hand-fee communication between the driver and the system during driving a vehicle, and for allowing the driver to query where the passenger user interface device is located; a passenger app software module stored in the non-volatile memory, the passenger app allowing the passenger to query where the driver user interface device is located; a database stored in the non-volatile memory, the database comprising an account holder records database; registration software stored in the non-volatile memory, the registration software allowing a user to register with the system and become an account holder; booking software stored in the non-volatile memory, the booking software allowing an account holder to search for and select a vehicle, and to book a ride; vehicle price software stored in the non-volatile memory, the vehicle price software determining a price for the vehicle selected; validation software stored in the non-volatile memory, the validation software validating that the driver app and passenger app are running on the driver user interface device and passenger user interface device during a ride; internet protocol (IP) address software stored in the non-volatile memory, the IP address software inputting the IP address of the passenger user interface device to the non-volatile memory and using the IP address to determine a location of the passenger user interface device; real time location software stored in the non-volatile memory, the real time location software determining in real time a real time location of the driver user interface device using a global positioning system (GPS) and if the GPS is not on determining in real time the location of the driver user interface device using triangulation, and determining in real time a real time location of the passenger user interface device using the GPS and if the GPS is not on determining in real time the location of the passenger user interface device using triangulation; proximity software stored in the non-volatile memory, the proximity software determining the proximity of the driver user interface device to the passenger user interface device and to determine when the driver and passenger are in the same location based on the real time locations of the driver user interface device and the passenger user interface device; best driver software stored in the non-volatile memory, the best driver software determining the best driver for the passenger, and if the driver rejects the ride determining the next best driver until a driver accepts the ride; driver location software located in the non-volatile memory, the driver location software monitoring the location of the driver before and during the ride, and providing the passenger app with the location of the driver based on the real time locations of the driver user interface device and the passenger user interface device; and route software stored in the non-volatile memory, the route software determining the best route for the driver and sending the best route to the driver app, and sending an alert to the driver if the driver deviates from the route during the ride based on the real time locations of the driver user interface device and the passenger user interface device.Join the waitlist — get patent alerts
Track US2019266518A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.