Patent Application
20180137594
This disclosure relates in general to the field of mobile applications and, more particularly, to a system and method for reserving drivers for a transportation service and navigating drivers to service transportation requests.
A transportation service may utilize a plurality of drivers that fulfill passenger requests for transportation. A transportation service may provide one or more mobile applications that facilitate the efficient pairing of passengers and drivers. The transportation service may receive a transportation request and select a driver to fulfill the request based on information associated with the transportation request and information associated with the driver.
To provide a more complete understanding of the present disclosure and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying figures, wherein like reference numerals represent like parts, in which:
In one embodiment, a method comprises determining, based on one or more metrics indicative of passenger demand and driver supply, to send a first idle mode offer to a first driver, the first idle mode offer specifying compensation to be provided to the first driver for maintaining availability to service a transportation request for the transportation service; sending the first idle mode offer to the first driver; sending a transportation request to the first driver while the first driver is maintaining availability in accordance with the first idle mode offer; and providing an indication of a compensation amount to be awarded to the first driver in accordance with the first idle mode offer, the compensation amount based on a time that the first idle mode offer was accepted by the first driver and a time at which the transportation request was sent to the first driver.
Various embodiments of the present disclosure may enhance the experience of passengers and drivers associated with a transportation service by offering drivers incentives to remain available to service transportation requests from the transportation service. It is fairly common for drivers to be affiliated with (i.e., service transportation requests received from) multiple transportation services, any of which could send a transportation request to the driver at a particular moment. In various embodiments, a transportation service reserves drivers to accept transportation requests from the transportation service (and to forego transportation requests from other transportation services) by sending the driver an idle mode offer specifying a compensation amount to incentivize the driver to remain idle (i.e., to not accept transportation requests from another transportation service) for a specified period of time or until the transportation service is able to send a transportation request to the driver. For example, the idle mode offer may specify that the driver is to receive a certain amount of money per minute that the driver remains available to take a transportation request from the transportation service. Various embodiments may provide technical advantages such as improving the speed at which a transportation request may be sent to a driver (e.g., due to the increased availability of drivers), reducing processing and communication resources expended during a search for an available driver, and other technical advantages.
Computing devices 104 and 108 may include any electronic computing device operable to receive, transmit, process, and store any appropriate data. In various embodiments, computing devices 104 and 108 may be mobile devices or stationary devices. As examples, mobile devices may include laptop computers, tablet computers, smartphones, personal digital assistants, smartwatches, computers integrated with a vehicle, computers integrated with clothing, and other devices capable of connecting (e.g., wirelessly) to one or more networks 120 while stationary devices may include desktop computers, televisions, or other devices that are not easily portable. Devices 104 and 108 may include a set of programs such as operating systems (e.g., Microsoft Windows, Linux, Android, Mac OSX, Apple iOS, UNIX, or other operating system), applications, plug-ins, applets, virtual machines, machine images, drivers, executable files, and other software-based programs capable of being run, executed, or otherwise used by the respective devices. Each computing device can include at least one graphical display and user interface allowing a user to view and interact with applications and other programs of the computing device. In a particular embodiment, computing device 108 may be a hardened device that is configured to only run a driver application using a specialized operating system (e.g., a modified version of Android). In one embodiment, a transportation service may issue or otherwise facilitate the provision of hardened devices to its drivers, but restrict the functionality of the devices to the driver application (i.e., the devices may be locked down so as not to allow the installation of additional applications or may only allow preapproved applications to be installed).
In various embodiments, a driver computing device 108 may be integrated within and/or communicate with a self-driven vehicle (e.g., a vehicle that has the capability of driving without physical steering guidance from a human being) and may influence the movement of the vehicle by providing route information (e.g., passenger pick-up and destination locations driver destination locations, navigational directions, etc.) to the self-driven vehicle. Accordingly, as used herein “driver” may refer to a human being that may physically drive or otherwise control movement of a vehicle or to the vehicle itself (e.g., in the case of a self-driven vehicle) or component thereof (e.g., computing device application 108 or logic thereof).
In particular embodiments, a passenger application runs on passenger computing devices 104. The application may allow a user to enter various account information (e.g., in connection with a registration with the transportation service) to be utilized by a transportation service. For example, the account information may include a user name and password (or other login credentials), contact information of the user (e.g., phone number, home address), payment information (e.g., credit card numbers or bank account numbers and associated information), or car preference information (e.g., what models or color of car the user prefers).
The application may allow a user to request a ride from the transportation service. In various embodiments, the application may establish a pick-up location automatically or based on user input (e.g., locations may include the current location of the computing device 104 as determined by a global positioning system (GPS) of the computing device or a different user-specified location). In certain embodiments, the user may specify a destination location as well. The locations may be specified in any suitable format, such as GPS coordinates, street address, establishment name (e.g., LaGuardia Airport, Central Park, etc.), or other suitable format. At any time (e.g., before the ride, during the ride, or after the ride is complete) the user may specify a method of payment to be used for the ride. The user may also specify whether the request is for immediate pick-up or for a specified time in the future. In various embodiments, the user may specify pick-up by a vehicle that has particular merchandise available for use by the user, such as a specified type of battery charger, bottle of water or other food or beverage, umbrella, or other suitable merchandise. The user may also specify criteria for the driver, such as a minimum performance rating, such that drivers having performance ratings below the minimum performance rating will not be considered during selection of the driver.
The user may use the application to order a ride based on the specified information. The request for the ride is generated based on the information and transmitted to backend system 116. Backend system 116 will facilitate the selection of a driver. In some embodiments, backend system 116 may select a driver based on any suitable factors, such as the information contained in the request from the passenger, the proximity of the driver to the passenger, or other suitable factors. In other embodiments, backend system 116 may select a plurality of drivers that could fulfill the ride request, send information associated with the drivers to the passenger, and allow the passenger to select the driver to be used via the application on the passenger computing device 104. Any suitable information about the potential driver(s) may be sent to the computing device 104 either before or after the selection of the driver by the passenger, such as a location of a driver, an estimated pick-up time, a type of car used by a driver, the merchandise available in the car, driver ratings or comments from other passengers about the driver, or other suitable information.
Once a driver has been selected and has accepted the request to provide a ride, the application may notify the user of the selected driver and provide real-time updates of the driver's location (e.g., with respect to the passenger's location) and estimated pick-up time. The application may also provide contact information for the driver and/or the ability to contact the driver through the application (e.g., via a phone call or text). Once the ride has begun, the application may display any suitable information, such as the current location of the computing device 104 and the route to be taken. Upon completion of the ride, the application may provide the passenger the ability to rate the driver or provide comments about the driver.
In particular embodiments, a driver application runs on driver computing devices 108. The application may allow a driver to enter various account information to be utilized by a transportation service. For example, the account information may include a user name and password (or other login credentials), contact information of the driver (e.g., phone number, home address), information used to collect payment (e.g., bank account information), vehicle information (e.g., what model or color of car the driver utilizes), merchandise offered by the driver, or other suitable information.
In various embodiments, the application may allow a driver to specify his availability to transport passengers for the transportation service. In some embodiments, the driver may select between multiple levels of availability. In one example, the driver may be “available,” meaning that the driver is willing to receive and consider any transportation requests that the transportation service sends the driver; the driver may be “unavailable,” meaning that the driver is not willing to receive any transportation requests (e.g., this state may be explicitly indicated by the driver inputting this state into his computing device or may be detected, e.g., through a deduction that the driver's device is not logged into the transportation service through the driver application), or the driver may be “inactive,” meaning that the driver only desires to receive particular requests meeting certain exception criteria. In another example, the driver may be “idle.” The idle status may be similar to the available status, but while the driver is idle the driver may maintain availability to accept a ride from the transportation service in exchange for compensation from the transportation service for the time spent in the idle status. In various embodiments, compensation accumulated while a driver has a status of idle (i.e., while the driver is in an idle mode) may vest upon the occurrence of one or more events (e.g., the acceptance of a ride from the transportation service while the driver is in idle mode, the completion of a ride received by the driver from the transportation service, the end of a time duration of the idle mode offer, or other suitable event).
The application may periodically transmit the current location of the computing device 108 as determined by a GPS of the computing device 108 to the backend system 116. When a driver is selected to provide (or is identified as a suitable candidate for) a ride, backend system 116 may send a notification to the driver application. In some embodiments, the driver may have a limited amount of time to select whether the driver accepts the ride. In other embodiments, the application may be configured by the driver to automatically accept the ride or to automatically accept the ride if certain criteria are met (e.g., fare minimum, direction of travel, minimum passenger rating, etc.).
Once a pairing of the driver and the passenger is confirmed by backend system 116, the application may navigate the driver to the passenger. The application may also provide contact information for the passenger and/or the ability to contact the passenger through the application (e.g., via a phone call, email, instant message, or text). The application may also navigate the driver to the passenger's destination once the ride begins. Upon completion of the ride, the application may provide the driver the ability to rate the passenger or provide comments about the passenger.
System 100 may include one or more application servers 112 coupled to the computing devices through one or more networks 120. The passenger application and driver application may be supported with, downloaded from, served by, or otherwise provided through an application server 112 or other suitable means. In some instances, the applications can be downloaded from an application storefront onto a particular computing device using storefronts such as Google Android Market, Apple App Store, Palm Software Store and App Catalog, RIM App World, etc., or other sources. In various embodiments, the passenger application and driver application may be installed on their respective devices in any suitable manner and at any suitable time. As one example, a passenger application may be installed on a computing device as part of a suite of applications that are pre-installed prior to provision of the computing device to a consumer. As another example, a driver application may be installed on a computing device by a transportation service (or an entity that provisions computing devices for the transportation service) prior to the issuance of the device to a driver that is employed or otherwise associated with the transportation service.
As described above, applications utilized by computing devices 104 and 108 can make use of a backend system 116. Backend system 116 may comprise any suitable servers or other computing devices that facilitate the provision of a transportation service as described herein. For example, backend system 116 may receive a request from a passenger and facilitate the assignment of a driver to fulfill the request. Backend system 116 is described in more detail in connection with
In general, servers and other computing devices of backend system 116 or application server 112 may include electronic computing devices operable to receive, transmit, process, store, or manage data and information associated with system 100. As used in this document, the term computing device, is intended to encompass any suitable processing device. For example, portions of backend system 116 (including backend server 302) or application server 112 may be implemented using servers (including server pools) or other computers. Further, any, all, or some of the computing devices may be adapted to execute any operating system, including Linux, UNIX, Windows Server, etc., as well as virtual machines adapted to virtualize execution of a particular operating system, including customized and proprietary operating systems.
Further, servers and other computing devices of system 100 can each include one or more processors, computer-readable memory, and one or more interfaces, among other features and hardware. Servers can include any suitable software component or module, or computing device(s) capable of hosting and/or serving a software application or services (e.g., services of application server 112 or backend system 116), including distributed, enterprise, or cloud-based software applications, data, and services. For instance, servers can be configured to host, serve, or otherwise manage data sets, or applications interfacing, coordinating with, or dependent on or used by other services, including transportation service applications and software tools. In some instances, a server, system, subsystem, or computing device can be implemented as some combination of devices that can be hosted on a common computing system, server, server pool, or cloud computing environment and share computing resources, including shared memory, processors, and interfaces.
In various embodiments, backend system 116 or any components thereof may be deployed using a cloud service such as Amazon Web Services, Microsoft Azure, or Google Cloud Platform. For example, the functionality of the backend system 116 may be provided by virtual machine servers that are deployed for the purpose of providing such functionality or may be provided by a service that runs on an existing platform.
System 100 also includes various networks 120 used to communicate data between the computing devices 104 and 108, the backend system 116, and the application server 112. The networks 120 described herein may be any suitable network or combination of one or more networks operating using one or more suitable networking protocols. A network may represent a series of points, nodes, or network elements and interconnected communication paths for receiving and transmitting packets of information. For example, a network may include one or more routers, switches, firewalls, security appliances, antivirus servers, or other useful network elements. A network may provide a communicative interface between sources and/or hosts, and may comprise any public or private network, such as a local area network (LAN), wireless local area network (WLAN), metropolitan area network (MAN), Intranet, Extranet, Internet, wide area network (WAN), virtual private network (VPN), cellular network (implementing GSM, CDMA, 3G, 4G, LTE, etc.), or any other appropriate architecture or system that facilitates communications in a network environment depending on the network topology. A network can comprise any number of hardware or software elements coupled to (and in communication with) each other through a communications medium. In some embodiments, a network may simply comprise a transmission medium such as a cable (e.g., an Ethernet cable), air, or other transmission medium.
In the embodiment depicted, computing devices 104 and 108 each include a computer system to facilitate performance of their respective operations. In particular embodiments, a computer system may include a processor, storage, and one or more communication interfaces, among other components. As an example, computing devices 104 and 108 each include one or more processors 202 and 204, memory elements 206 and 208, and communication interfaces 214 and 216, among other hardware and software. These components may work together in order to provide functionality described herein.
A processor 202 or 204 may be a microprocessor, controller, or any other suitable computing device, resource, or combination of hardware, stored software and/or encoded logic operable to provide, either alone or in conjunction with other components of computing devices 104 and 108, the functionality of these computing devices. In particular embodiments, computing devices 104 and 108 may utilize multiple processors to perform the functions described herein.
A processor can execute any type of instructions to achieve the operations detailed in this Specification. In one example, the processor could transform an element or an article (e.g., data) from one state or thing to another state or thing. In another example, the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by the processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array (FPGA), an erasable programmable read only memory (EPROM), an electrically erasable programmable ROM (EEPROM)) or an application specific integrated circuit (ASIC) that includes digital logic, software, code, electronic instructions, or any suitable combination thereof.
Memory 206 and 208 may comprise any form of non-volatile or volatile memory including, without limitation, random access memory (RAM), read-only memory (ROM), magnetic media (e.g., one or more disk or tape drives), optical media, solid state memory (e.g., flash memory), removable media, or any other suitable local or remote memory component or components. Memory 206 and 208 may store any suitable data or information utilized by computing devices 104 and 108, including software embedded in a computer readable medium, and/or encoded logic incorporated in hardware or otherwise stored (e.g., firmware). Memory 206 and 208 may also store the results and/or intermediate results of the various calculations and determinations performed by processors 202 and 204.
Communication interfaces 214 and 216 may be used for the communication of signaling and/or data between computing devices 104 and 108 and one or more networks (e.g., 120g) and/or network nodes (e.g., backend system 116 and application server 112) coupled to a network or other communication channel. For example, communication interfaces 214 and 216 may be used to send and receive network traffic such as data packets. Each communication interface 214 and 216 may send and receive data and/or signals according to a distinct standard such as an LTE, IEEE 802.11, IEEE 802.3, or other suitable standard. In various embodiments, any of the data described herein as being communicated between elements of system 100 may be data generated using voice commands from a user or data generated independently of voice commands (e.g., data may be generated by a processor in response to the processor receiving data from another element or from an input device such as a touch screen). Communication interfaces 214 and 216 may include antennae and other hardware for transmitting and receiving radio signals to and from other devices in connection with a wireless communication session over one or more networks 120.
GPS units 210 and 212 may include any suitable hardware and/or software for detecting a location of their respective computing devices 104 and 108. For example, a GPS unit may comprise a system that receives information from GPS satellites, wireless or cellular base stations, and/or other suitable source and calculates a location based on this information (or receives a calculated position from a remote source). In one embodiment, the GPS unit is embodied in a GPS chip.
Application logic 218 may include logic providing, at least in part, the functionality of the passenger application described herein. Similarly, application logic 220 may include logic providing, at least in part, the functionality of the driver application described herein. In a particular embodiment, the logic of devices 104 and 108 may include software that is executed by processor 202 and 204. However, “logic” as used herein, may include but not be limited to hardware, firmware, software and/or combinations of each to perform a function(s) or an action(s), and/or to cause a function or action from another logic, method, and/or system. In various embodiments, logic may include a software controlled microprocessor, discrete logic (e.g., an application specific integrated circuit (ASIC)), a programmed logic device (e.g., a field programmable gate array (FPGA)), a memory device containing instructions, combinations of logic devices, or the like. Logic may include one or more gates, combinations of gates, or other circuit components. Logic may also be fully embodied as software.
In a particular embodiment, a user may supply login credentials for a social network system (e.g., FACEBOOK) or other social media system (e.g., TWITTER) to the transportation service through application logic 218. The transportation service (e.g., through backend server) may then access the user's account on the social network system or other social media system and access information associated with the user's account. As another example, passenger application logic 218 may access the user's social media account directly and integrate information from the account with other functionality of the passenger application logic.
Social network application logic 222 may provide a user interface to allow a passenger to interact with (e.g., enter and transmit information to and view information received from) a social network system. A social network system may store a record (i.e., a user profile) for each user of the system. The user profile may include any suitable information about the user, such as contact information, employment information, demographic information, personal interests, user-generated content, or other suitable information. The social network system may also store a record of the user's relationship with other users of the social network system. For example, such information may be stored as a social graph, wherein users (e.g., individuals, groups, business entities, organizations, etc.) may be represented as nodes in the graph and the nodes may be connected based on relationships between the users. A social network system may provide various services (e.g., photo sharing, wall posts, messaging, games, or advertisements) facilitating interaction between the users.
In a particular embodiment, the social network system allows users to create events, invite others to events, and to indicate attendance at such events. An event may comprise a gathering of a plurality of people for any suitable purpose. Examples of events include concerts, sporting events (e.g., baseball, football, soccer, basketball, hockey, boxing, or other sports), parades, airplane arrivals, community gatherings, or other suitable gatherings. A record for an event stored by the social network system may include any suitable information, such as the name of the event, the type of event, the time and date of the event, the location of the event, a record of users that were invited to the event as well as an indication of whether the users have accepted, declined, or not yet responded to the invitation, or other suitable information about the event.
In various embodiments, the social network system may interact with passenger application logic 218 and/or backend server 302 to enhance the functionality of these components. As an example, events created in the social network system may be provided to the backend server 302 through an API or other interface to a data store of the social network system. In one embodiment, the social network system may allow backend server 302 to access events independent of a user login associated with a passenger or driver. For example, the social network system may have an arrangement with the transportation service to provide events created in the social network system to the transportation service. In another embodiment, backend server 302 may access the events visible by the transportation service's administrators, passengers, and/or drivers via their respective login credentials to the social network system.
In various embodiments, the social network system may provide any of the functionality listed above with respect to passenger application logic 218 in allowing a user to request a ride from an event and may relay received requests for rides to backend server 302 along with any suitable identifying information about the user to facilitate pickup by a driver. In one embodiment, information associated with requesting a ride from the event may be provided on an event page (e.g., a page that displays the details of the event) viewed by the user using social network application logic 222, a network browser, or other means. The information associated with requesting a ride may include instructions to or an interface (e.g., a link) to request a ride through the social network system, instructions to or a link to download passenger application logic 218 in order to request a ride, an advertisement about the transportation service along with an indication that the transportation service may provide a ride from the event, a coupon for a discounted ride from the event, or other suitable information facilitating the request of a ride from a user (who may or may not already be a customer of the transportation service). In another embodiment, information associated with requesting a ride may be sent to the user by the social network system through the social network application logic 222 (e.g., via a push notification) or other means (e.g., email, text messaging). In various embodiments, the information associated with requesting a ride from the event is provided to the user in response to a determination that the user is at the event.
Email application logic 224 may provide an interface for the passenger to read, draft, and/or manage emails. Email application logic 224 may comprise a traditional email client (e.g., Microsoft Outlook or a native iOS or Android mail application) or a web-based email application (e.g., a web browser or other application operable to access Outlook.com, Gmail, Yahoo! Mail, or other web-based email service).
Calendar application logic 226 may provide an interface for the passenger to read, draft, and/or manage calendar appointments and related tasks. Calendar application logic 226 may comprise a traditional calendar client (e.g., Microsoft Outlook or a native iOS or Android calendar application) or a web-based calendar application (e.g., a web browser or other application operable to access Outlook.com, Google Calendar, or other web-based calendar service).
Search engine application logic 228 may provide an interface for the passenger to perform Internet keyword searches. In various embodiments, logic 228 is operable to receive input forming a keyword search. In some embodiments, logic 228 may also perform the keyword search by transmitting the search to one or more servers operable to perform the search and provide search results back to logic 228. In other embodiments, logic 228 may communicate the input to another application to perform the keyword search. In various embodiments, logic 228 may present the search results to the passenger via any suitable interface (e.g., a visual or audio interface). In various embodiments, logic 228 may comprise a web browser or other application.
Device assistant logic 230 may comprise logic to enhance the functionality of other applications of passenger computing device 104. In particular embodiments, device assistant logic 230 may comprise an intelligent personal assistant, such as Siri, Cortana, Google Now, or similar assistant. In various embodiment, device assistant logic 230 may monitor activity of the passenger computing device 104, including an operating system or one or more applications of passenger computing device 104. For example, device assistant logic 230 may access emails, instant messages, or text messages sent by, received by, or accessible by email application logic 224 or other logic of passenger computing device 104. As another example, device assistant logic 230 may access calendar appointments available through calendar application logic 226 (which may be stored in a calendar file stored by passenger computing device 104 or on a remote server). As another example, device assistant logic 230 may access search queries made through search engine application logic 228. As another example, device assistant logic 230 may access transportation requests made through passenger application logic 218 or detect when passenger application logic 218 is opened. As another example, device assistant logic 230 may access the location of passenger computing device 104 using data determined by global positioning system 210.
In various embodiments, device assistant logic 230 may enhance the user experience of the passenger by answering questions from the passenger, making recommendations to the passenger, and performing other actions, such as drafting emails, texts, or calendar appointments. In addition to answering questions explicitly asked by the passenger, device assistant logic 230 may proactively obtain information and present the information to the passenger. In various embodiments, the proactive presentation of information is based upon previous user activity with respect to passenger computing device 104. For example, device assistant logic 230 may present or direct the presentation of (e.g., within a web browser) the status of a flight reservation or other travel reservation that the passenger booked or accessed using a web browser of the passenger computing device 104 or for which a confirmation email was received via email application logic 224. As other examples, device assistant logic 230 may direct the presentation of hotel or restaurant reservations, weather information, sporting event information, package tracking information, local movie times, stock prices, news events, or other information based on the passenger's location, emails, calendar appointments, search or browsing history, or other activity.
Device assistant logic 230 may also use information obtained from the operating system or applications of passenger computing device 104 to enhance the user experience of the passenger with respect to the transportation service. For example, information obtained by the device assistant logic 230 may be used to identify events that the passenger may be attending. In various embodiments, device assistant logic 230 may communicate device activity information (which may include at least a subset of the gathered information or other information obtained by processing at least a subset of the gathered information) directly to a server of backend system 116 controlled by the transportation service. In other embodiments, device assistant logic 230 may communicate activity information to a third party server controlled by, for example, the provider of the device assistant logic (e.g., Google, Apple, Microsoft, etc.), which may then communicate the device activity information (or a subset thereof) to a server of backend system 116 controlled by the transportation service. In yet other embodiments, device assistant logic 230 may communicate device activity information with passenger application logic 218 which may then communicate device activity information (or a subset thereof) to the backend system 116.
In various embodiments of the present disclosure, in addition to any combination of the features described above with respect to the driver application, driver application logic 220 may provide additional features for the driver application to enhance the functionality of the transportation service. For example, driver application logic 220 may receive idle mode offers from backend system 116 and cause display of the offer to a driver. Driver application logic 220 may also be operable to accept input from the driver regarding whether the driver accepts the offer. Driver application logic 220 may also display information associated with the idle mode offer, such as the time duration of the offer and/or how much time remains for the offer, prospective compensation associated with the offer, accumulated prospective compensation associated with the offer, earned compensation associated with the offer, other information associated with the offer described herein, or any other suitable information associated with the offer.
In the embodiment depicted, backend server 302 includes a computer system to facilitate performance of its operations. As an example, backend server 302 includes one or more processors 308, memory elements 310, and communication interfaces 312, among other hardware and software. These components may work together in order to provide backend server functionality described herein. Processor 308 may have any suitable characteristics of the processors 202 and 204 described above. In particular embodiments, backend server 302 may utilize multiple processors to perform the functions described herein. In various embodiments, reference to a processor may refer to multiple discrete processors communicatively coupled together.
Similarly, memory 310 may have any suitable characteristics of memories 206 and 208 described above. Memory 310 may store any suitable data or information utilized by backend server 302, including software embedded in a computer readable medium, and/or encoded logic incorporated in hardware or otherwise stored (e.g., firmware). Memory 310 may also store the results and/or intermediate results of the various calculations and determinations performed by processor 308.
Communication interface 312 may also have any suitable characteristics of communication interfaces 214 and 216 described above. Communication interfaces 312 may be used for the communication of signaling and/or data between backend server 302 and one or more networks (e.g., networks 120) and/or network nodes (e.g., computing devices 104 and 108, data store 304, third party services 306, and application server 112) coupled to a network or other communication channel.
Business logic 314 may have any suitable characteristics of application logic 218 and 220 described above. Business logic 314 may include logic providing, at least in part, the functionality of the backend server described herein. In a particular embodiment, business logic 314 may include software that is executed by processor 308. However, in other embodiments, business logic 314 may take other forms such as those described above with respect to application logic 218 and 220.
Backend server 302 may communicate with data store 304 to initiate storage and retrieval of data related to the transportation service. Data store 304, may store any suitable data associated with the transportation service in any suitable format(s). For example, data store 304 may include one or more database management systems (DBMS), such as SQL Server, Oracle, Sybase, IBM DB2, or NoSQL data bases (e.g., Redis and MongoDB).
In the embodiment depicted, data store 304 includes passenger account data 316, driver account data 318, transportation request data 320, driver availability data 322, navigational data 324, and historical request data 326. The various data may be updated at any suitable intervals.
Passenger account data 316 may include any suitable information associated with passenger accounts, such as contact information (e.g., real names and addresses), user names and passwords (or other authentication information), payment information (e.g., credit card or bank account numbers and associated information), passenger preferences (e.g., preferred type or color of car), ratings the passenger has given drivers, ratings the passenger has received from drivers, or other information associated with passenger profiles.
Driver account data 318 may include any suitable information associated with driver accounts, such as contact information (e.g., real names and addresses), user names and passwords (or other authentication information), payment collection information (e.g., bank account information), vehicle information (e.g., models and colors of cars the drivers utilize, maximum capacity of the cars of the drivers), merchandise offered by the drivers, whether the drivers are available to transport passengers, whether the drivers have opted for automatic acceptance of transportation requests (whereby the backend server 302 may assign a transportation request to the driver without waiting for the driver to indicate acceptance of a request), or other suitable information.
Transportation request data 320 may comprise pending requests (i.e., requests that have not yet been fulfilled) received from passengers. Each request may include any suitable information, such as any combination of one or more of an identification of the passenger making the request, the time the request was made, the current location of the passenger, the desired pick-up location, the desired pick-up time, the estimated time remaining until a driver can pick up the passenger, the actual pick-up time, the desired destination location of the passenger (which the passenger may or may not provide at the time the request is made), the expected arrival time at the destination location, the type of vehicle requested, estimated fare for the trip, current accumulated fare for the trip, estimated time and mileage remaining in the trip, other information specified by the user (e.g., requested merchandise, requested minimum rating of driver), whether a driver has been assigned to a request, and which driver has been assigned to a request. For each transportation, an appropriate fare may be assigned according to a distance-weighted continuous pricing function as disclosed herein.
Driver availability data 322 may comprise information associated with drivers that are available to transport passengers. In some embodiments, driver availability data 322 may also comprise information associated with drivers that are not available to transport passengers (e.g., because they are off-duty or currently transporting a passenger). An entry in the driver availability data 322 may include an identification of a driver and any suitable associated information, such as one or more of a current location of the driver, whether the driver is available to transport passengers, whether the driver is currently transporting a passenger, a destination location of a current trip of the driver, an estimate of how long it will be before the driver finishes his current trip, whether the driver has opted for automatic acceptance of transportation requests, or other suitable information.
In various embodiments, driver availability data 322 may include information indicating whether an idle mode offer has recently been sent to a driver, whether the driver is currently in an idle mode, how much time remains on an idle mode offer accepted by a driver, whether an idle mode offer is scheduled to be sent to a driver, when an idle mode offer is to be sent to a driver (if an idle mode offer is scheduled), and/or other information associated with an idle mode offer sent or to be sent to a driver.
Navigational data 324 may comprise information supporting navigation functions provided by the passenger applications and driver passenger applications. For example, navigational data 324 may comprise map data that may be sent to passenger computing devices 104 and driver computing devices 108 to allow the devices to display maps and associated indicators (e.g., location of passenger(s), location of driver(s), desired routes, etc.). In some embodiments, the navigational data may also comprise information indicative of the amount of time required to travel between various locations. In some embodiments, navigational data 324 may comprise historic and/or real time data about the flow of traffic in particular areas enabling backend server 302 to calculate an estimated time required to travel from one location to another.
Historical request data 326 may comprise information about completed requests. In some embodiments, historical request data 326 may also include information about canceled requests. The information for each request may include any combination of the information listed above with respect to requests stored in the transportation request data 320 as well as any combination of additional data such as the time at which the destination location was reached, the total time of the trip, the total fare, a rating given by the passenger to the driver or by the driver to the passenger for the trip, or other suitable information associated with the trip.
Historical idle offer data 328 may comprise information about idle offers sent to drivers and associated data. For example, historical idle offer data 328 may include a plurality of entries comprising data associated with idle offers sent to drivers. An entry may include any suitable information associated with an idle offer. For example, an entry may indicate which driver an idle offer was sent to, compensation specified by the idle offer, a duration of the idle offer, whether the idle offer was accepted, an amount of time the driver remained in idle mode after accepting the idle offer, whether the driver accepted a ride from the transportation service while in idle mode, whether the driver voluntarily left idle mode, and/or other suitable information associated with an idle offer.
Event data 330 may comprise information about upcoming events, currently occurring events, and recently ended events (e.g., before information about the events is transferred to historical event data 332). An event may comprise a gathering of a plurality of people for any suitable purpose. Examples of events include concerts, sporting events (e.g., baseball, football, soccer, basketball, hockey, boxing, or other sports), parades, airplane arrivals, community gatherings, or other suitable gatherings. Events identified by the backend server 302 may be events in which a plurality of passengers are likely to request transportation from the transportation service to the event or from the event or events that otherwise may affect the flow of traffic or the availability of drivers.
An entry in event data 330 may include any suitable information about an event, such as a title of the event, a location of the event (which may be expressed in any suitable manner, such as GPS or other coordinates, an address, or a name of the venue at which the event is held), an estimated start time of the event, an estimated end time of the event, passenger pickup locations associated with the event (e.g., one or more ideal locations for drivers to pick up passengers that attended the event), an estimation of the number of people attending the event, an indication of the type of the event (e.g., a baseball game, a concert, an airplane arrival), an event information source associated with the event (e.g., a web address or other identifier of an information source from which current information about the event may be obtained), or other suitable information associated with the event. An entry in event data 330 may include a tracking of and/or an estimate of passenger requests for transportation from passengers that will be or are attending the event. For example, an entry may include an estimation of the aggregate number of passenger requests that will be and/or have been received from passengers at the event and/or a predicted timeline of how many requests have been and/or will be received as a function of time relative to the completion of the event (e.g., an average number of requests per minute received prior to and after the end of the event). In some embodiments, an indication of each passenger request made in association with the event may be stored. Whether a passenger request is associated with the event may be determined in any suitable manner, such as by filtering requests based on a temporal and geographical proximity with the event.
In various embodiments, backend server 302 may classify an event based on the information received from one or more event information sources to facilitate comparison with historical events stored in historical event data 332. The classification may be based on the source of the event information, key words included in the event information, manual entry of the classification, or other suitable information. As just one example, particular events obtained from a basketball team's website may be classified as basketball games for the particular team. Backend server may analyze historical events with similar classifications in order to determine patterns in start times, end times, and/or the number (and timing of) passenger requests associated with the events in order to more accurately predict the same for upcoming or ongoing events.
In various embodiments, backend server 302 may determine or estimate a start time and/or a completion time for the event. In particular embodiments, backend server 302 may identify the start time or completion time from information provided by an event information source (e.g., the start time, end time, or the duration of the event may be specified by the event information source). In some embodiments, the start time or end time of an event may be estimated based on start times or end times associated with past events of the same type stored in historical event data 332. In some embodiments, backend server 302 may update the estimated end time of an event one or more times during the event (e.g., periodically during the event). For example, backend server 302 may connect to the event information source to determine how much time is left until the event is over. As various examples, sports websites may include information indicating how far a game has progressed or an airport website may indicate an expected arrival time for a particular flight.
Historical event data 332 may include information about past events that may be used by backend server to determine the number of passenger requests and/or estimated start times or completion times for events stored in event data 330. An entry in historical event data 332 for a past event may include any suitable information, such as that described above in connection with an entry in event data 330.
In various embodiments, backend server 302 may connect to event information sources through one or more networks to discover events and/or obtain updated information about events. An event information source may include any source containing information about an event. For example, an event information source may be a server hosting a webpage containing event information, a server providing an API through which backend server 302 may request event information from the server, a server providing access to a file (e.g., a calendar file such as an iCalendar or vCalendar file) containing information about one or more events, a computing device which may be used by an administrator to manually enter event information, information obtained from a passenger or driver computing device, or other suitable source. In an embodiment, an event information source includes a social network system. In some embodiments, event information may be uploaded directly to backend server 302 via a flash drive or other means. In one embodiment, backend server 302 may access various websites and parse the data included in the websites to obtain the event information. The event information obtained from one or more event information sources may include any suitable information about an event, such as any of the information stored in event data 330.
In various embodiments, performance evaluation criteria data 334 of data store 304 may specify information describing a performance evaluation scheme for a plurality of drivers of the transportation service that is implemented at least in part by backend server 302. The performance evaluation criteria data 334 may be provided to backend server 302 by any suitable entity, such as an administrator of the transportation service. The performance evaluation criteria data 334 may be updated at any suitable time and may be used to generate performance scores for the drivers.
In various embodiments, the performance evaluation criteria may indicate one or more periods that each specify a time duration over which the drivers are to be evaluated. For example, the performance evaluation period may be a day, a week, a month, a quarter of a year, or other suitable period. A performance evaluation period may be specified using a start time and/or date and an end time and/or date or a duration. Each performance evaluation period may be associated with a set of performance metric data, which may be the same for all performance evaluation periods or may vary from performance evaluation period to performance evaluation period.
The performance metrics may include any suitable indications of the performance of the drivers. Example performance metrics may include revenue brought in through servicing transportation requests and/or fulfilling idle mode offers, distance traveled transporting passengers, time spent transporting passengers, an amount of time worked by the driver (e.g., time spent with an available status (i.e., a status indicating availability to accept transportation requests) and/or transporting passengers), feedback scores received from passengers, safety record (e.g., a measure of traffic accidents experienced or traffic tickets received), a percentage of received transportation requests that are accepted and serviced, or other suitable performance metrics.
In various embodiments, a single performance metric (e.g., revenue or an amount of time worked), is used to judge the performance of individual drivers. In other embodiments, multiple performance metrics (including any suitable combination of two or more performance metrics described herein or other performance metrics) are used to judge performance.
The performance evaluation criteria data may specify how the performance metrics are to be applied to each driver to generate performance scores for the driver. If a single performance metric is used, a single performance score is calculated. The performance score may be the raw data from the corresponding metric or it may be another value representing a level of performance with respect to the metric. For example, if the performance metric is revenue and the performance score is the raw data, the performance score of an individual driver with respect to the revenue performance metric is the amount of revenue generated by a driver over the performance evaluation period. As another example, if the performance score is another value representing a level of performance with respect to the metric, the raw data may be converted to a value on a performance scale (e.g., a number from 0 to 10). Any suitable scale and conversion methodology may be specified by the performance evaluation criteria data.
When multiple performance metrics are used, the scores associated with each performance metric may be combined to yield a cumulative performance score (if only one performance metric is used, the corresponding performance score is used as the cumulative score for the user). The scores may be combined in any suitable manner. For example, the scores may be added together. As another example, the scores may be averaged. In some embodiments, the performance evaluation criteria data may specify relative weights for each performance metric, such that more important metrics such as revenue may be factored more heavily in the judgment of performance of a driver or group of drivers. Accordingly, in such embodiments, a weighted average (or other calculation taking into accounts the weights of the various performance metrics) of various scores may be calculated to yield a cumulative performance score for a driver.
In various embodiments, a performance score generated from application of any one of the performance metrics may be adjusted based on any suitable criteria, such as a characteristic associated with a driver, to generate an adjusted score for the driver. Any suitable criteria may be used to adjust a performance score, such as a home location of a driver (i.e., the city in which a driver is based), the length of time a driver has been driving for the transportation service, the type of car of the driver, any of the performance metrics described above (e.g., a score representing the revenue generated by a driver may be adjusted based on customer feedback received for the driver or the percentage of rides the driver accepted), or other suitable criteria. After the performance score for the performance metric is adjusted, the adjusted performance score may be used in the calculation of the cumulative performance score for the driver. Alternatively, a cumulative score may be calculated and the cumulative score itself may be adjusted based on any suitable adjustment criteria. A performance score may be adjusted in any suitable manner. In one embodiment, an adjustment multiplier is associated with the adjustment criteria and when the adjustment criteria applies to a particular driver, the adjustment multiplier will be multiplied by the relevant performance score to yield an adjusted performance score. Any other suitable methodology for adjusting performance scores may be used.
In various embodiments, backend server 302 may access third party services 306 through business logic 328 to access data 330. Third party services 306 may represent any suitable number of devices operated by any suitable number of third parties that are distinct from an entity that operates the backend system 116 and/or data store 304. For example, in some embodiments the navigational data may be obtained from a third party service 306 rather than data store 304, or additional third party navigational data such as map data or historical and/or current traffic flow information may be used to supplement navigational data 324. As another example, third party services 306 may authenticate users on behalf of the backend server 302 (e.g., through an account of the user with the third party). Business logic 328 may comprise any suitable logic operable to receive requests for data from backend system 116 and/or computing devices 104 and 108 and provide responses to the requests.
Backend server 302 may be in communication with each passenger computing device 104 and each driver computing device 108 that is utilizing the transportation service at a particular time. Backend server may store information received from the computing devices 104 and 108 in data store 304. Backend server 302 may also receive and respond to requests made by computing devices 104 and 108 by processing information retrieved from data store 304.
When a passenger opens the passenger application, the backend server 302 may log the passenger in based on a comparison of authentication information provided by the passenger computing device 104 with authentication information stored in passenger account data 316. The passenger may then request a ride. The request is received by the backend server 302 and stored in transportation request data 320. Backend server 302 may access driver availability data 322 to determine one or more drivers that would be suitable to fulfill the request from the passenger. In one embodiment, backend server 302 selects a particular driver (e.g., based on the driver's locality with respect to the passenger's pick-up location) and sends information associated with the request to the driver. The driver indicates whether he accepts or rejects the request via his computing device 108. If the driver rejects the request, backend server 302 selects a different driver and the process is repeated until the backend server 302 receives an accepted request from a driver. In another embodiment, backend server 302 may select a plurality of drivers that may fulfill a transportation request and allow the passenger to select one of the drivers. The backend server 302 may proceed to notify the driver of the request in a similar manner to that described above. In yet another embodiment, backend server 302 may select a plurality of drivers that may fulfill a transportation request and notify each driver of the transportation request. The backend server 302 may then allocate the request to one of the drivers based on any suitable criteria. For example, the driver who is the first to accept the request may be assigned to the request. As another example, if multiple drivers accept the request within a given timeframe, the request may be assigned to the most suitable driver (e.g., the driver that is closest to the pick-up location or a driver that has a car that meets preferred characteristics of the transportation request).
Once the request has been accepted by a driver, the backend server 302 notifies the passenger that a driver has accepted his request and provides any suitable information associated with the driver (e.g., driver's current location, model and color of vehicle, estimated time of arrival, etc.) to the passenger.
The backend server 302 may provide navigation information (e.g., the passenger's current location or other pickup location and directions to the current location or other pickup location) to the driver computing device 108 to direct the driver to the passenger's pickup location and subsequently to direct the driver to the passenger's destination location. The backend server 302 may also provide real-time updates associated with the trip to both the passenger and the driver.
Once the passenger's destination location has been reached, the backend server 302 may facilitate payment of the fare for the trip using payment information stored in passenger account data 316 and/or driver account data 318 (or information supplied by the passenger at the time of the transaction). The backend server 302 may also receive ratings associated with the trip for the passenger and driver and store these ratings in data store 304.
In particular embodiments, the zones may be dynamic. That is, the delineation of the zones may be changed by the transportation service over time based on conditions within the zones. For example, if a particular zone sees a drastic reduction in traffic, the zone may be deleted from the zones tracked by the transportation service. As another example, if a particular spot within a zone sees an increase in traffic, one or more new zones may be created or the boundaries of the zone may be modified to account for this increase.
In various embodiments, backend server 302 may determine one or more surge pricing parameters for the zones 404. For example, the backend server 302 may determine one or more surge pricing parameters on a per-zone basis. In some embodiments, the one or more surge pricing parameters are communicated to the passenger computing device for presentation to the passenger when the passenger requests a ride. A surge pricing parameter may be, for example, an absolute price for a transportation request taking surge factors into account, a surge cap specifying the amount of price for a ride that is subject to surge pricing, or it may be a multiplier of a baseline or default rate normally charged for rides originating from the pickup location, which in some embodiments may be a regional baseline applicable to a large region (e.g., the baseline for Kansas City, Mo. may be different from the baseline for New York, N.Y., which may be different from the baseline for Los Angeles, Calif.). If the surge pricing parameter is a multiplier, it may be expressed in a form such as 1.05× (for a zone with near-baseline demand), 1.3× (for a zone with slightly elevated demand), 3.2× (for a zone with very high demand), or 0.85× (for a discounted zone, such as a zone that is a target of a promotion, or a zone that is in low demand). The surge multiplier may be based on any suitable information, such as supply and demand (e.g., the number of drivers in the zone and/or nearby zones and the rate of passenger requests in the zone and/or nearby zones), and/or other relevant factors such as time of day, traffic conditions, weather conditions, road conditions, or other factors. In various embodiments, any of the factors described below in conjunction with estimating a supply of passenger requests and a baseline driver supply may be used to calculate a surge pricing parameter for a zone. In various embodiments, when the surge multiplier is updated, if the amount of demand exceeds the amount of supply (or the demand to supply ratio has increased relative to the last calculated demand to supply ratio), then the surge multiplier for the zone may increase. Conversely, if the amount of supply exceeds the amount of demand (or the demand to supply ratio has decreased relative to the last calculated demand to supply ratio), the surge multiplier may decrease.
In various embodiments of the present disclosure, a surge cap is associated with a zone. The surge cap limits the amount of rides from the zone that are subject to surge pricing, resulting in a fairer price to the passenger. Until the surge cap is reached, surge pricing applies to the fare, but once the surge cap is reached, default rates are replied for the remainder of the trip. Such embodiments may provide passengers taking short trips with the standard surge pricing (since a surge cap may be set high enough that short rides are unlikely to meet the surge cap), but place a ceiling on the surge surcharge that a passenger is to pay for a longer trip.
The surge cap presented to the user may take any suitable form, but in any event represents a maximum amount of a fare for the transportation request that is subject to a surge pricing surcharge. For example, the surge cap may represent a maximum amount of the total fare that may be calculated by applying the surge multiplier (or multiple surge multipliers). For example, if a surge multiplier for a transportation request is 3.0× and the surge cap is $30, then the fare will accumulate at a rate of 3× the normal rate until the accumulated fare reaches $30, at which point the fare will accumulate at the default rate. As another example, the surge cap may represent a maximum amount of a surcharge due to surge pricing. For example, if a surge multiplier is 3.0× and the surge cap is $20, then the fare will accumulate at a rate of 3× the normal rate until the surcharge due to the surge pricing reaches $20, at which point the fare will accumulate at the default rate. In this example, the surcharge due to the surge pricing is 2.0× the normal fare (since the surge multiplier is 3.0×), and thus this surge cap is equivalent to the surge cap of the previous example in which the surge cap was $30 but was applied to the total fare (and not just to the amount representing the surcharge).
In various embodiments, the surge cap is determined by the backend server 302 based on one or more surge multipliers associated with one or more different zones surrounding the pickup location. In a particular embodiment, each zone of multiple different zones is associated with its own surge multiplier. As an example, if only a portion of the route for a transportation request travels through a zone with a high surge multiplier, then the surge cap may be lower for that route than for a route of similar distance that has a larger portion of the route in one or more zones with high surge multipliers.
In particular embodiments, idle mode offers may be managed on a per-zone basis. Thus, for each zone, backend system 116 may determine whether idle mode offers are to be sent to drivers located within the zone, how many idle mode offers should be sent, when to send idle mode offers, and the values of other idle mode offer parameters (e.g., compensation details) associated with idle mode offers.
At 502, passenger demand for a zone is estimated. In various embodiments, backend server 302 may estimate the number of passenger requests as a function of time or at a particular point in time. For example, backend server 302 may estimate the average number of requests that will be received per interval of time (e.g., per minute). As another example, backend server 302 may estimate the number of requests that are expected within a five minute interval, a fifteen minute interval, or other time interval.
The passenger demand may be estimated relative to any suitable time. For example, the passenger demand may be estimated for the next five minutes. As another example, the passenger demand may be estimated for a time interval beginning ten minutes in the future and ending fifteen minutes in the future.
The passenger demand of a zone may be estimated at any suitable interval. For example, the estimation of the passenger demand may be updated periodically (e.g., every 2 minutes, every 5 minutes, or at any other period interval) or in response to an event (such as a rapid change in the rate at which transportation requests are being received).
The estimation of demand may be based on the number of pending transportation requests (i.e., transportation requests that have been received but not assigned to a driver and/or transportation requests that are currently being serviced) originating from the zone (and/or neighboring zones), the number of transportation requests received over a particular time interval (e.g., over a recent time interval such as the last 10 minutes) with a pickup location in the zone (and/or neighboring zones), the number of transportation requests expected to be received for a particular time interval (with pickup locations in the zone and/or neighboring zones), and/or other suitable information. In various embodiments, the number of transportation requests expected to be received may be based on data stored in historical request data 326 (e.g., the number of requests historically received during a time period that is similar to the time period for which the estimate is being made). As just one example, the number of transportation requests expected to be received on a Wednesday morning at 7:30 AM-7:45 AM may be based on the number of transportation requests received over the same time period on one or more previous Wednesdays.
In various embodiments, the number of historical passenger requests over a timeframe may be adjusted by a factor indicative of the number of recent requests. For example, continuing the example above, the number of requests received from 7:15 AM-7:30 AM on the Wednesday morning relative to historical requests received at a similar time on one or more previous Wednesdays may be ascertained and used to adjust the number of historical requests in order to estimate an expected number of requests to be received that Wednesday morning from 7:30 AM-7:45 AM. For example, if the transportation service is receiving a number of requests that morning that is 1.2× higher than usual, an estimate that is based on historical requests may be adjusted upwards by a factor of 1.2×. Other embodiments may adjust a number derived from historical requests in any suitable manner based on current demand to estimate a number of passenger requests to be received over a particular time period.
In various embodiments, the estimated passenger demand for a zone may be based on one or more events in the zone or a nearby zone. The number of expected passenger requests may be determined in any suitable manner. For example, backend server 302 may determine an expected number of passengers for a particular time period based on any suitable factors such as the expected total attendance at the event (e.g., as indicated by an event information source or as derived from similar past events stored in historical event data 332), the percentage of the population (e.g., in a particular region including the location of the event) that utilize the transportation service, a number of passengers detected as attending the event (e.g., based on GPS coordinates received from passenger mobile devices), the location of the event (some locations may result in a higher rate of transportation requests than others), the time of the event, past passenger requests from similar events (e.g., as stored in historical request data 326 and/or historical event data 332), data representing the timing of requests associated with past events (e.g., as stored in historical request data 326, historical event data 332, and/or other data), and/or other suitable factors. In one embodiment, the expected total attendance at the event may be based on a number of users of a social network that have indicated an intent to attend the event. As just one example, the number of transportation requests received may spike within a first zone prior to the beginning of a nearby event (e.g., in a second zone) and may spike within the second zone at the end of the event.
In various embodiments, the number of historical requests over a timeframe may be adjusted by a factor indicative of the number of recent requests. For example, data associated with one or more previous football games may indicate that 20 requests are likely to be received from a zone during a first 5 minute period before a football game is to start on a given day and 30 requests are likely to be received from the zone during a second 5 minute period before the football game. However, if a time period corresponding (i.e., the same number of minutes before the start of the game) to the first 5 minute period yields only 10 passenger requests, then the estimate for the second 5 minute period may be adjusted downward (e.g., to 15 passenger requests or other number). Any suitable number of historical time periods may be compared with recent time periods during the estimation of passenger demand.
In various embodiments, the passenger demand for a future time period may be estimated based on a combination of one or more events, historical passenger request data, and current passenger request data. For example, the expected number of passenger requests based on historical passenger request data for a particular time period may be determined, the increase in requests expected to be generated due to one or more events may be added, and the result may be adjusted by the current rate of passenger requests relative to expected requests (which could also be based on historical passenger request data and/or event data).
At 504, a baseline driver supply for the zone is estimated. In various embodiments, the baseline driver supply estimate may indicate the number of drivers that are expected to accept (or be available to accept) transportation requests over a particular time period or particular point in time. For example, backend server 302 may estimate the number of drivers that are expected to be available at 6:15 PM on a particular date, the number of drivers that will accept transportation requests from 6:30 PM-6:45 PM on a particular date, or the number of drivers to be available and/or accept transportation requests over the next five minutes. As another example, backend server 302 may estimate (or determine) that 8 drivers are currently waiting for transportation requests in a particular zone. In various embodiments, a time or time period for which the baseline driver supply is calculated may be equal to or at least overlap with a time period or time for which passenger demand is estimated. In various embodiments, the estimated baseline driver supply may be comparable against the estimated passenger demand (e.g., in order to determine whether the estimated baseline driver supply is sufficient to meet the estimated passenger demand).
The baseline driver supply may be estimated relative to any suitable time. For example, the baseline driver supply may be estimated for the next five minutes. As another example, the baseline driver supply may be estimated for a time interval beginning ten minutes in the future and ending fifteen minutes in the future.
The baseline driver supply of a zone may be estimated at any suitable interval. For example, the estimation of the baseline driver supply may be updated periodically (e.g., every 2 minutes, every 5 minutes, or at any other period interval) or in response to an event (such as a rapid change in driver availability or the rate at which transportation requests are being received).
The baseline driver supply may be estimated based on historical and/or current data accessible by backend server 302 about the number of drivers located (or expected to be located) in the zone or otherwise available to fulfill transportation requests with pickup locations within the zone (e.g., the indication of supply may be based on the number of drivers in neighboring zones and/or within a certain distance or driving time of one or more locations of the zone) or other suitable information. For example, the baseline driver supply may be based on the current number or drivers located in the zone that are available to transport passengers (which could include drivers that are currently waiting due to having accepted an idle mode offer and drivers that are waiting for a transportation request independent of an idle mode offer). As another example, the baseline driver supply may be based on the current number or drivers located at locations that are within a threshold distance from the zone that are available to transport passengers (which could include drivers that are currently waiting due to having accepted an idle mode offer and drivers that are waiting for a transportation request independent of an idle mode offer). As another example, the baseline driver supply may be based on the historical number of drivers that are available at a particular time or time period (e.g., the amount of drivers that are usually available on a particular time and/or the number of drivers that are usually available to transport passengers in connection with a particular type of event) and/or the number of drivers that have accepted rides over one or more particular time periods. As another example, the baseline driver supply may be based on a number of drivers that are expected to finish transporting passenger(s) to the particular zone (or nearby locations) during (or before) the relevant time period (thus becoming available to transport passengers from the particular zone). In various embodiments, historical data may be adjusted by current conditions (e.g., the number of drivers available or the rate of servicing of transportation requests) when used to estimate a baseline driver supply.
The baseline driver supply for a zone may also be based on the likelihood of one or more drivers being busy at a particular time due to accepting a ride from a different transportation service, accepting a ride originating in another zone, or otherwise becoming unavailable to transport passengers during the relevant time period. For example, backend server 302 may access historical data tracking the availability of drivers to determine a likelihood of one or more drivers becoming unavailable. As one example, backend server 302 may determine that over a five minute period, any given driver has a 25% chance of becoming unavailable by the end of the period. In various embodiments, the likelihood of one or more drivers becoming unavailable may be based on historical data measuring availability during the relevant time period (e.g., day and time or a time period following an event). Thus an estimate of a baseline driver supply may factor in the likelihood of available drivers becoming unavailable during the relevant time period.
At 506, idle mode offer parameters are determined for the zone. In various embodiments, the idle mode offer parameters are based on one or more metrics indicative of passenger demand and driver supply. For example, the idle mode offer parameters may be based on an estimated passenger demand and an estimated baseline driver supply. As another example, the idle mode offer parameters may be based on the number of passenger requests that are currently waiting to be assigned drivers. As another example, the idle mode offer parameters may be based on one or more waiting times/estimated times of arrivals (ETAs) of a driver for a transportation request (e.g., the magnitude of the waiting time may quantify the extent to which passenger demand exceeds driver supply). As yet another example, the idle mode offer parameters may be based on one or more surge pricing parameters associated with the zone and/or neighboring zones. In various embodiments, the idle mode offer parameters may be determined based on multiple metrics indicative of passenger demand and driver supply. As just one example, the number of idle mode offers may be based on the estimated passenger demand and estimated baseline driver supply while the amount of compensation offered by the idle mode offers may be based on a surge pricing parameter (e.g., a surge multiplier) of a zone.
When the backend server 302 detects that passenger demand exceeds or is going to exceed baseline driver supply, the backend server 302 may decide to send one or more idle mode offers. The number of idle mode offers sent may depend on the magnitude of the disparity between the passenger demand and the driver supply (e.g., more offers are sent if the disparity is larger).
As one example, the backend server 302 may determine whether the estimated passenger demand exceeds the estimated driver supply for the next X minutes (where X is any suitable number) and send idle mode offers if the demand is expected to exceed the supply. As another example, the backend server 302 may determine whether the estimated passenger demand exceeds the estimated driver supply for a time period beginning in the future (e.g., 10 minutes from the time the determination is made) and send (or schedule the sending of) idle mode offers if the demand is expected to exceed the supply during this time period. As another example, backend server 302 may determine whether a surge pricing parameter is above a certain threshold and may send one or more idle mode offers based on the value of the surge pricing parameter. As another example, backend server may send one or more idle mode offers if the number of passenger requests that are currently waiting to be assigned drivers is greater than a particular threshold. As another example, the backend server 302 may send one or more idle offers if the waiting time/ETA of a driver for a transportation request (or a metric based on multiple waiting times/ETAs for multiple rides) exceeds a threshold. For each of these, the number of idle mode offers sent (or scheduled to be sent) may be based on the extent to which the demand exceeds (or is expected to exceed) the supply (e.g, various threshold levels may correspond to various numbers of idle mode offers or the magnitude of the metric indicating supply and demand may be converted and then rounded to determine a number of idle mode offers).
In various embodiments, passenger requests may be estimated as a function of time and the number of idle mode offers and the times at which the offers are sent may be selected based on the difference between the expected passenger requests and the baseline driver supply as a function of time. For example, it is common for attendees of a sporting event to leave the event early to avoid crowds. Thus, backend server 302 may offer idle mode offers at periodic intervals leading up to the estimated end time of the event with progressively more idle mode offers being made towards the end time of the event to increase the supply of drivers available when the event finishes.
In addition to determining how many idle mode offers to send, backend server 302 may determine various parameters for the idle mode offers. Any of the parameters may be based on any suitable factors, such as one or more metrics indicative of passenger demand and driver supply, the estimated passenger supply, the estimated baseline driver supply, historical idle mode offers, historical driver availability data, or other suitable information (e.g., any of the information stored by data store 304). Similar to the determination of the number of offers made, any of the parameters values may be based on the extent to which passenger demand exceeds driver supply (e.g., parameter values that would result in a higher acceptance of idle mode offers may be used when the demand greatly exceeds the supply while less aggressive values may be used when the demand and supply are more closely matched).
For example, backend server 302 may determine the durations of the idle mode offers, which may be the same for each offer (or each set of offers that are sent at the same time) or may vary from offer to offer. The duration of an idle mode offer may specify a maximum length of time over which the driver is to be compensated for remaining idle. For example, the idle mode offer may specify that the driver is to receive compensation for every minute up to the duration of the idle mode offer that the driver remains available to service a ride from the transportation service.
As another example, backend server 302 may determine an amount of compensation for the idle mode offer. In a particular embodiment, the amount of compensation is an amount per time interval (e.g., $0.60 per minute, $2.00 per 5 minutes, etc.). In another embodiment, the amount of compensation could be a flat amount. In a particular embodiment, an amount of compensation is a portion of the rate that would be charged for a standard ride (e.g., 30% of the average rate per minute). In a particular embodiment, the amount of compensation is determined based on the surge price multiplier (e.g., the compensation may be the standard rate/minute for a ride times the surge multiplier times a discount factor).
As another example, backend server 302 may determine which drivers will be the recipients of the idle mode offers. In particular embodiments, when determining which drivers will be the recipients of the idle mode offers for a particular zone, the backend server 302 may limit the sending of offers to drivers located in the zone, drivers within a particular range of the zone, and/or drivers that are predicted to be located in the zone or within a particular range of the zone at the time the offer is to be sent (e.g., based on an analysis of a ride the driver is currently servicing) or the offer is to begin (e.g., an offer could be sent before the offer begins such as when a particular driver is nearing the end of a transportation request). The backend server 302 may also limit the sending of idle mode offers to drivers that are currently available or are expected to be available at the time the offer is to be sent. In particular embodiments, drivers may be selected for idle mode offers based on historical idle offer data 328 indicating how likely the driver is to accept the idle mode offer and/or fulfill the terms of the idle mode offer (e.g., remain idle until a transportation request from the transportation service is sent to the driver or the length of the idle mode offer has expired). In various embodiments, drivers may be selected for idle mode offers based on performance scores of the drivers. In a particular embodiment, the availability data associated with various users may be used to determine whether to send idle mode offers to the users. For example, if a particular driver displays a pattern of availability indicating that the driver is not associated with other transportation services, the backend server 302 may choose not to send an idle mode offer to the driver since the driver may not need to be incentivized to remain available for the transportation service.
In a particular embodiment, if a driver rejects an idle mode offer, the driver is not offered another idle mode offer for a particular period of time. The period of time may be uniform across all drivers or may be variable for each driver and based on any suitable factors, such as the number of idle mode offers rejected by the driver, the percentage of idle mode offers rejected by the driver, a performance score of the driver, other suitable factors, or any combination thereof.
As another example, backend server 302 may determine what times the offers are to be sent. In various embodiments, multiple offers may be sent at the same time. In other embodiments, offers may be staggered in time based on the one or more metrics of driver supply and passenger demand.
Idle mode parameters may be determined at any suitable intervals or in response to any suitable triggers. For example, idle mode parameters may be determined periodically (e.g., every 2 minutes, every 5 minutes, or at any other period interval) or in response to a trigger (such as a rapid change in demand or supply or when a metric crosses a threshold).
At 508, idle mode offers are sent to one or more drivers. In various embodiments, characteristics associated with an idle mode offer may be similar to characteristics associated with a standard transportation request. For example, an incoming idle mode offer may cause driver computing device 108 to play the same sound as an incoming transportation request. As another example, a driver may have the same amount of time to accept an idle mode offer as an incoming transportation request. In other embodiments, the characteristics may be different from characteristics associated with a standard transportation request. For example, a driver may receive additional time to respond to an incoming idle mode offer. In various embodiments, the idle mode offer may specify any or all of the idle mode offer parameters discussed above.
At 510, backend server 302 waits for responses to idle mode offers. An acceptance to an idle mode offer may be sent to the backend server 302 by a driver computing device 108. Similarly, a rejection to an idle mode offer may be sent to the backend server 302 by a driver computing device 108. In various embodiments, a rejection to an idle mode offer may be inferred if an acceptance is not received within a predetermined period of time.
At 512, backend server determines whether to send additional offers to drivers. In various embodiments, this determination may be based on how many of the offers sent at 508 were accepted. For example, the number of additional offers sent may be equal to the number of offers that were rejected. As another example, the number of additional offers sent may be different from the number of offers that were rejected (e.g., if the offers were rejected by drivers that were considered to be likely to accept the offers but new offers are to be sent to drivers that are not considered to be likely to accept the offers then additional new idle mode offers may be sent). The determination of how many offers to send and who to send the offers to may use any of the factors described above with respect to operations 502, 504, and 506.
In a particular embodiment, based on the rate of idle mode offer acceptance, the average compensation of the new idle mode offers sent may be adjusted upwards or downwards from the average compensation of the previously sent idle mode offers. For example, if the acceptance rate of idle mode offers is lower than expected, the compensation of the new idle mode offers may be adjusted upwards to incentivize acceptance of the offers. As another example, if the acceptance rate of idle mode offers is higher than expected, then the compensation specified in future idle mode offers may be adjusted downward.
At 514, the accepted idle mode offers are tracked. Backend server 302 may keep track of which drivers have accepted idle mode offers and the time at which the idle mode offers were accepted. Backend server 302 may also track the availability of the drivers that have accepted idle mode offers to determine whether the drivers are complying with the terms of the idle mode offers. Backend server 302 may also determine whether the drivers that have accepted idle mode offers accepted a transportation request during fulfillment of the idle mode offer (i.e., while the drivers were remaining idle waiting for a transportation request) and what time the transportation requests were accepted. Tracking by the backend server 302 may allow the backend server to determine accumulated prospective compensation for the drivers and whether the accumulated prospective compensation is vested (i.e., to be paid to the drivers). At 516, backend server 302 arranges for compensation for idle mode offers in which the accumulated prospective compensation is vested (e.g., upon acceptance of a transportation request by the driver or upon the expiration of the duration of the idle mode offer). Compensation may be arranged in any suitable manner, such as by storing an indication of the amount earned through the idle mode offer. In various embodiments, compensation may be arranged using the same methods used to arrange for compensation for the fulfillment of a standard transportation request.
Some of the operations illustrated in
At 602, an idle mode offer is received (e.g., from a backend server 302). At 604, a determination is made as to whether the offer is accepted. For example, driver computing device 108 may detect user input that accepts the offer or user input that rejects the offer. As another example, driver computing device 108 may detect that a time limit associated with acceptance of the offer has expired and infer that the offer is rejected. As another example, driver computing device 108 may receive a notification from backend server 302 that the offer has expired. If the idle mode is not accepted, then no idle mode compensation is received by the driver at 606.
If the idle mode offer is accepted at 604, then prospective idle mode compensation begins accumulating at 608. In one embodiment, the driver computing device 108 may start its own timer upon acceptance of the idle mode offer and calculate the accumulated prospective idle mode compensation based on the amount of time that has expired since the offer was accepted and the compensation specified by the offer. In another embodiment, the driver computing device 108 may receive periodic updates from the backend server 302 regarding how much prospective idle mode compensation has accumulated. The accumulated prospective idle mode compensation may be displayed to the driver via the driver computing device 108. In various embodiments, the amount of time remaining in the duration of the idle mode offer is also displayed by the driver computing device 108.
At 610, if the time waited by the driver in idle mode is greater than the duration of the idle mode offer, then the accumulated prospective idle mode compensation is received by the driver at 616. If the time waited is not greater than the duration of the idle mode offer, then the prospective idle mode compensation continues accumulating at 608.
At 612, if no transportation request is received, the prospective idle mode compensation continues accumulating at 608. If a transportation request is received, then a determination of whether the transportation request is accepted by the driver is determined at 614. If the driver does not accept the transportation request, then the driver does not receive the accumulated prospective idle mode compensation at 606. Conversely, if the driver accepts the transportation request, then the accumulated prospective idle mode compensation is received by the driver at 616.
Some of the operations illustrated in
It is important to note that the operations in
In various embodiments, if a driver has accepted an idle mode offer and subsequently fails to accept a transportation request from the transportation service or explicitly exits idle mode, the driver may lose any accumulated idle mode compensation associated with the idle mode offer. In particular embodiments, after a driver has accepted an idle mode offer, the driver is allowed to drive to any location during the idle mode offer duration without losing the idle mode compensation. In other embodiments, after a driver has accepted an idle mode offer, the driver may be restricted to a certain area (e.g., a zone or a threshold distance from a zone) in order to receive the idle mode compensation (such a restriction may be specified in the idle mode offer sent to the driver). In various embodiments, when a transportation request following an acceptance of an idle mode offer ends, the driver is no longer in idle mode until the driver is offered an additional idle mode offer. In particular embodiments, an additional idle mode offer may be sent to a driver in idle mode prior to the expiration of the duration of an idle mode offer that has been accepted by the driver, thus potentially extending the period in which the driver remains idle. This additional idle mode offer may have any suitable parameters which may be the same as or different from the parameters of the idle mode offer that was already accepted by the driver. If a transportation request is received prior to the expiration of the first idle mode offer, then the second idle mode offer may be canceled.
In various embodiments, transportation requests may be sent to drivers based at least in part on whether they are currently in idle mode. For example, if backend server 302 determines that the need for retaining drivers in idle mode has diminished relative to earlier predictions, the backend server 302 may route transportation requests to drivers in idle mode in order to reduce the number of drivers in idle mode. Conversely, if the need for retaining drivers in idle mode is still high, the backend server 302 may router transportation requests to drivers that are not in idle mode in order to maintain a surplus of drivers in idle mode to meet expected demand.
The functionality described herein may be performed by any suitable component(s) of the system. For example, certain functionality described herein as being performed by backend server 302, may, in various embodiments, be performed by any combination of one or more passenger computing devices 104 or driver computing devices 108 where appropriate. Similarly, certain functionality described herein as being performed by a passenger computing device 104 or a driver computing device 108 may, in various embodiments, be performed by backend server 302 where appropriate.
Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it is intended that the present disclosure encompass all such changes, substitutions, variations, alterations, and modifications as falling within the scope of the appended claims. In order to assist the United States Patent and Trademark Office (USPTO) and, additionally, any readers of any patent issued on this application in interpreting the claims appended hereto, Applicant wishes to note that the Applicant: (a) does not intend any of the appended claims to invoke subsection (f) of 35 U.S.C. section 112 as it exists on the date of the filing hereof unless the words “means for” or “step for” are specifically used in the particular claims; and (b) does not intend, by any statement in the specification, to limit this disclosure in any way that is not otherwise reflected in the appended claims.
