Prepositioning Empty Vehicles Based on Predicted Future Demand

1 - 71 . (canceled)

72 . An automated ridesharing dispatch system, comprising memory configured to store historical data associated with past demand for ridesharing vehicles in a geographical area;

a communications interface;

at least one processor configured to access the memory and to:

use the historical data to predict imminent demand of ridesharing requests including predicting general zones in the geographical area associated with imminent demand;

select a holding zone for prepositioning empty ridesharing vehicles in order to expedite satisfaction of the predicted imminent demand; and

send, via the communications interface, to a mobile communications device in a specific ridesharing vehicle, instructions directing the specific ridesharing vehicle to the holding zone.

73 . The system of claim 72 , wherein the specific ridesharing vehicle is directed to the holding zone to maintain a presence in the holding zone despite other ridesharing demand in the geographical area.

74 . The system of claim 72 , wherein the at least one processor is further configured to access in the memory historical data collected about pick-up locations, days, and times of prior ride requests.

75 . The system of claim 74 , wherein the at least one processor is further configured to access in the memory historical data collected about weather conditions associated with the prior ride requests.

76 . The system of claim 72 , wherein the at least one processor is further configured to select the holding zone from a plurality of pre-identified holding zones stored in the memory, wherein the holding zone includes at least one of a specific location and a neighborhood.

77 . The system of claim 72 , wherein the at least one processor is further configured to select a holding zone for the specific ridesharing vehicle using real-time data.

78 . The system of claim 72 , wherein the at least one processor is further configured to select a holding zone for the specific ridesharing vehicle using data about passenger-capacity of the specific ridesharing vehicle.

79 . The system of claim 72 , wherein the at least one processor is further configured to select a holding zone for the specific ridesharing vehicle using data about a shift of a driver of the specific ridesharing vehicle.

80 . The system of claim 72 , wherein the at least one processor is further configured to identify a plurality of holding zones and to direct a plurality of empty ridesharing vehicles to the plurality of holding zones.

81 . The system of claim 72 , wherein the at least one processor is further configured to identify a plurality of holding zones and to direct, based on the predicted general zones in the geographical area, a single empty ridesharing vehicle to a first holding zone and at least two empty ridesharing vehicles to a second holding zone.

82 . The system of claim 72 , wherein the at least one processor is further configured to determine a drop-off location for a last passenger riding the specific ridesharing vehicle based on the selected holding zone and desired destination of the passenger.

83 . The system of claim 72 , wherein the at least one processor is further configured to receive a rideshare request from a mobile communications device of a user in a vicinity of a selected holding zone, and to send a message to an empty rideshare vehicle in the selected holding zone to pick-up the user, including routing instructions to a pick-up location in a vicinity of the selected holding zone.

84 . The system of claim 72 , wherein the at least one processor is further configured to receive a rideshare request from a mobile communications device of a user in a vicinity of the specific ridesharing vehicle driving toward the selected holding zone, and to send a message to another rideshare vehicle farther away from the user to pick up the user.

85 . The system of claim 72 , wherein the at least one processor is further configured to receive a rideshare request, from a mobile communications device of a user in a vicinity of the specific ridesharing vehicle driving toward the selected holding zone, and to send a message to the specific ridesharing vehicle to pick up the user when the desired destination of the user is in proximity to the selected holding zone.

86 . The system of claim 72 , wherein at least some of the ridesharing vehicles are electrically-powered vehicles, and the holding zone includes a location where the ridesharing vehicle can charge while waiting for a user assignment.

87 . The system of claim 72 , wherein at least some of the ridesharing vehicles are manually-drivable ridesharing vehicles, and the holding zone includes a location where the ridesharing vehicles can park while waiting for a user assignment.

88 . The system of claim 72 , wherein at least some of the ridesharing vehicles are autonomous, and the holding zone includes a route along which the autonomous vehicle is directed to drive while awaiting a pick-up assignment.

89 . A non-transitory computer-readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform a method for managing a fleet of ridesharing vehicles, the method comprising:

storing historical data associated with past demand for ridesharing vehicles in a geographical area;

using the historical data to predict imminent demand of ridesharing requests including predicting general zones in the geographical area associated with imminent demand;

selecting a holding zone for prepositioning empty ridesharing vehicles in order to expedite satisfaction of the predicted imminent demand; and

sending to a mobile communications device in a specific ridesharing vehicle, instructions directing the specific ridesharing vehicle to the holding zone.

90 . The non-transitory computer-readable storage medium according to claim 89 , wherein the specific ridesharing vehicle is directed to the holding zone to maintain a presence in the holding zone despite other ridesharing demand in the geographical area.

91 . The non-transitory computer-readable storage medium according to claim 89 , wherein selecting the holding zone includes making a selection from a list of holding zone options stored in memory.

92 . The non-transitory computer-readable storage medium according to claim 89 , wherein the method further comprises:

identifying a plurality of holding zones; and

directing, based on the predicted general zones in the geographical area, a single empty ridesharing vehicle to a first holding zone and at least two empty ridesharing vehicles to a second holding zone.

93 . An automated ridesharing dispatch system, comprising:

memory configured to store historical data associated with past demand for ridesharing vehicles in a geographical area;

a communications interface configured to receive location information from a plurality of communication devices associated with a plurality of ridesharing vehicles;

at least one processor configured to access the memory and to:

assign, to ridesharing vehicles already transporting users, additional users for simultaneous transportation in the ridesharing vehicles;

track assignments of each specific ridesharing vehicle to identify that a first ridesharing vehicle and a second ridesharing vehicle are about to be without passengers and without future assignments;

direct the first ridesharing vehicle to a first holding zone based on a current location of the first vehicle and a predicted imminent demand proximate the first holding zone; and

direct the second ridesharing vehicle to a second holding zone other than the first holding zone based on a current location of the second vehicle and a predicted imminent demand proximate to the second holding zone.

94 . The system of claim 93 , wherein at least one processor is further configured to direct the second ridesharing vehicle to a second holding zone when the first holding zone is at full capacity.

95 - 184 . (canceled)