Patent Grant
11188955
Embodiments described herein pertain generally to a system and method for providing on-demand services through use of portable computing devices.
Current on-demand services, such as fleet management systems employed for Taxi and limousine fleets, typically utilize onboard metering devices, radios, and cell phones to dispatch drivers and monitor fares. Such systems typically are not communicative to customers that are waiting for pickup. Furthermore, little information is tracked about individual fares. Moreover, conventional approaches rely on the customer making payment directly to the driver by credit card or cash.
Embodiments described herein provide an interactive environment for enabling a user to request on-demand services using a computing device. In particular, some embodiments described herein enable mobile computing devices, such as smart phones and geo-aware cellular telephony devices, to be used in connection with an on-demand service that enables the user to request services, such as a delivery service or transport service, using a simplified user interface schematic. Functionality, such as communicating the location of the user, the location of available service providers, the types of service available, the estimated fees and other information, can be aggregated and provided to the user in an efficient and user-friendly manner.
In one embodiment, a computing device can operate an application for requesting on-demand services. The application can provide user interface features that provide a user of the application with information for enabling the user to request a particular type of service. For example, the user can be provided a mechanism for selecting services and service types, as well as displaying information that may affect the decision of the user in making such selections.
According to some embodiments, the information and service options made available to the user can be region-specific. For example, different on-demand services and information about different services can be provided to the user based on the region that the user is located in. Thus, the service options made available to the user, as well as the information provided to the user regarding the service options can be made region specific.
In some embodiments, different user interface features can be provided, at least in part, by an application or program that is stored and operated on the user's computing device. The application can be configured to communicate with an on-demand service system that arranges services between users and service providers (e.g., drivers for transport, ice cream delivery providers, personal telegram service providers, etc.). For example, a user can request food to be delivered to his or her office, and the on-demand service system can determine available food providers that satisfy the user's request and arrange for a food provider to perform the service. The user is enabled, via the user interface features, to make different selections for viewing specified information and for requesting different on-demand service options based on the user selections.
According to an embodiment, a location of the computing device can be determined so that user interface features for requesting an on-demand service can be presented, on a display of the computing device, based on the device's real-time location. A multistate selection feature can be provided to enable a user to select a particular type of service. In one implementation, the multistate selection feature identifies a plurality of service options for an on-demand service (e.g., types of vehicles that can provide a transport service for the user, types of food trucks, delivery methods, etc.), based on a region where the user is located (e.g. the device's real-time location).
In one embodiment, a summary user interface can be presented on the display in response to the user selecting one of the plurality of the service options, such as a vehicle type for a delivery or transport, or type of food service. The summary user interface can include region-specific information about the on-demand service that is particular to and based on the selected service option. For example, for an on-demand food service, the summary user interface can include region-specific information about the closest food service providers, types of foods available in the region, average prices for the foods, the inventory available, etc. In another example, the region-specific information can include an estimated time of arrival to the user's current location, the average price, the amount of space/capacity of the vehicle, etc. The provided information can assist the user in making a better informed decision in requesting the on-demand service. In some implementations, the user can interact with the multistate selection feature by selecting different service types or service options to cause the contents within the summary user interface to dynamically change accordingly.
Still further, in some embodiments, once the user requests the on-demand service based on the selected service option, a confirmation user interface feature can be displayed to present additional features and information that the user can verify before confirming the request. When the user confirms the request (e.g., places an order), the computing device can provide the service request to the on-demand service system with necessary user data so that the on-demand service system can arrange the service between the user and an available service provider. The user can provide additional information on the confirmation user interface feature, such as, for example, special notes for the service provider or a promotional code before confirming the request.
As described herein, a “user,” or a “customer” refer to individuals that are requesting or ordering an on-demand service. Also as described herein, a “provider,” or a “service provider” refer to individuals or entities that can provide the requested service. As an example, a user can request an on-demand service (e.g., car/Taxi service, food delivery, messenger service, telegram service, or provide a product) using the system, and a service provider can communicate with the system and/or the user to arrange to perform the service. In addition, as described herein, “customer devices” and “provider devices” refer to computing devices that can correspond to desktop computers, cellular or smartphones, personal digital assistants (PDAs), laptop computers, tablet devices, television (IP Television), etc., that can provide network connectivity and processing resources for enabling a user to communicate with a system over a network. A provider device can also correspond to taxi meters or other metering devices.
One or more embodiments described herein provide that methods, techniques, and actions performed by a computing device are performed programmatically, or as a computer-implemented method. Programmatically, as used herein, means through the use of code or computer-executable instructions. These instructions can be stored in one or more memory resources of the computing device. A programmatically performed step may or may not be automatic.
One or more embodiments described herein can be implemented using programmatic modules, engines, or components. A programmatic module, engine, or component can include a program, a sub-routine, a portion of a program, or a software component or a hardware component capable of performing one or more stated tasks or functions. As used herein, a module or component can exist on a hardware component independently of other modules or components. Alternatively, a module or component can be a shared element or process of other modules, programs or machines.
Some embodiments described herein can generally require the use of computing devices, including processing and memory resources. For example, one or more embodiments described herein may be implemented, in whole or in part, on computing devices such as servers, desktop computers, cellular or smartphones, personal digital assistants (e.g., PDAs), laptop computers, printers, digital picture frames, network equipments (e.g., routers) and tablet devices. Memory, processing, and network resources may all be used in connection with the establishment, use, or performance of any embodiment described herein (including with the performance of any method or with the implementation of any system).
Furthermore, one or more embodiments described herein may be implemented through the use of instructions that are executable by one or more processors. These instructions may be carried on a computer-readable medium. Machines shown or described with figures below provide examples of processing resources and computer-readable mediums on which instructions for implementing embodiments of the invention can be carried and/or executed. In particular, the numerous machines shown with embodiments of the invention include processor(s) and various forms of memory for holding data and instructions. Examples of computer-readable mediums include permanent memory storage devices, such as hard drives on personal computers or servers. Other examples of computer storage mediums include portable storage units, such as CD or DVD units, flash memory (such as carried on smartphones, multifunctional devices or tablets), and magnetic memory. Computers, terminals, network enabled devices (e.g., mobile devices, such as cell phones) are all examples of machines and devices that utilize processors, memory, and instructions stored on computer-readable mediums. Additionally, embodiments may be implemented in the form of computer-programs, or a computer usable carrier medium capable of carrying such a program.
System Description
As an alternative or addition, some or all of the components of system 100 can be implemented on one or more computing devices, such as on one or more servers or other mobile computing devices. System 100 can also be implemented through other computer systems in alternative architectures (e.g., peer-to-peer networks, etc.). Accordingly, system 100 can use data provided by an on-demand service system, data provided by other components of the mobile computing device, and information provided by a user in order to present user interface features and functionality for enabling the user to request an on-demand service. The user interface features can be specific to the location or region that the computing device is located in, so that region-specific information can be provided to the user. System 100 can also adjust the user interface features, including the content displayed as part of the user interface features, based on other user selections.
In some implementations, system 100 includes an on-demand service application 110, a map component 140, a map database 143, and a location determination 145. The components of system 100 can combine to provide user interface features that are specific to user selections, user locality, and/or real-time conditions to enable a user to request on-demand services. The on-demand service application 110 can correspond to a program that is downloaded onto a smartphone, portable computer device (e.g., tablet or other ego-aware device). In one implementation, a user can download and install the on-demand service application 110 on his or her computing device and register the computing device 180 with an on-demand service system of the entity.
The on-demand service application 110 can include an application manager 115, a user interface (UI) component 120, and a service interface 125. The service interface 125 can be used to handle communications exchanged between the on-demand service application 110 and the on-demand service system 170 (e.g., over a network). For example, the service interface 125 can use one or more network resources of the device 180 for exchanging communications over a wireless network. The network resources can include, for example, a cellular data/voice interface to enable the device to receive and send network communications over a cellular transport. As an alternative or variation, the network resources can include a wireless network interface for connecting to access points (e.g., Wireless Fidelity 802.11(g) or 802.11(n)) or for using other types of wireless mediums (e.g., WiMax)
The application manager 115 can receive user input 111, location information 147, and other information (such as user information 151 and/or historical information 153) to configure content that is to be provided by the UI component 120. For example, the UI component 120 can cause various user interface features 121 to be output to a display of the computing device 180. Some of the user interface features 121 can be region-specific (e.g., based on the current location of the computing device) to display information that is particular to the region. The user interface features 121 can also provide dynamically adjusted content based on user selections provided via the user input 111.
For example, the UI component 120 uses a UI framework that can be configured with various content, such as UI content 175 provided by the on-demand service system 170 and content as a result of user input. The UI component 120 can also configure the UI framework with location information 147 and map content 141. In this manner, a map of a region in which the user is currently located in can be displayed as part of a user interface feature 121. In some examples, the map component 140 can provide the map content 141 using map data stored in one or more map databases 143. Based on the locale of the user and the user selection(s) made for requesting an on-demand service, such as a type of food or a type of vehicle that the user would like to be transported in, the application manager 115 can cause region-specific and user-selection-specific UI content 175 to be presented with or as part of a user interface 121.
In some implementations, the user interfaces 121 can be configured by the application manager 115 to display information about on-demand services that are available for the user-specific region. On-demand services can include food services (e.g., users can order food, request mobile food providers such as food trucks, request dessert providers such as ice cream trucks), delivery services, transport services, telegram or entertainment services (e.g., users can request mariachi bands, singing quartets), or other services that the user can request via the on-demand service system. Based on the user's region, different services and service options can be available for the user.
For example, for an on-demand transport service, Taxicab vehicles may be available in one city, and unavailable in another. Similarly, a hybrid vehicle may be available in one city, and unavailable in another. In another example, for an entertainment service, an on-demand Mariachi band may be available in one country or region, and may not be available in other countries. In various examples described, the user interfaces 121, which displays information about services available for a user, as well as features to enable the user to request services, can be configured with network user interface content (e.g., provided by the on-demand service system 170) to reflect the services available to the user based on the user's geographic region. The user is enabled to interact with the different displayed user interface features 121, via the user input 111, to make selections and input preferences when requesting an on-demand service from the on-demand service system 170.
When the on-demand service application 110 is operated by the user, the various user interfaces 121 can be rendered to the user based on the user inputs 111 and/or information received from the on-demand service system 170. These user interfaces include, for example, a home page user interface (e.g., an initial page or launch page), a multistate selection feature, a summary user interface, a location suggestion user interface, a location search user interface, a confirmation user interface, or a combination of any of the features described. For example, the UI component 120 can cause a home page user interface 121 to be displayed that identifies the service(s) that the user can request using the on-demand service application 110. The home page user interface 121 can also provide only certain service selection options or types that are available in the user's region. In this manner, based on the current location of the computing device, the on-demand service application 110 can cause location-specific user interfaces 121 and content to be presented to the user.
In many instances, a geographic region that is specific to the user can be based on the user's current location (e.g., the current location of the computing device 180) or the user's requested service location (e.g., the pickup location for a transport service, or a delivery location for a food service). For example, in some cases, the current location can be different from the requested service location, so that the user can manually select a particular pickup location or delivery location that is different from the current location of the computing device 180. The user's current location or service performance location can be determined by the location determination 145.
The location determination 145 can determine the location of the computing device in different ways. In one example, the location determination 145 can receive global positioning system (GPS) data 161 from location-based/geo-aware resources 160 of the computing device 180. In addition, the location determination 145 can also receive GPS data 161 from other applications or programs that operate on the computing device 180. For example, system 100 can communicate with one or more other applications using one or more application program interfaces (APIs). The on-demand service application 110 can use the location information 147 to cause the UI component 120 to configure the UI framework based on the location information 147. In addition, the on-demand service application 110 can provide the user's location data 119 to the on-demand service system 170.
As an addition or alternative, the on-demand service application 110 can determine the user's current location or pickup location (i) by using location data 177 provided by the on-demand service system 170, (ii) by using user location input provided by the user (via a user input 111), and/or (iii) by using user info 151 and/or historical info 153 stored in one or more user databases 150.
For example, the on-demand service system 170 can cross-reference the location data 119 (received from the on-demand service application 110) with the other sources or databases (e.g., third party servers and systems) that maintain location information to obtain granular/specific data about the particular identified location. In some cases, by cross-referencing the data, the on-demand service system 170 can identify particular stores, restaurants, apartment complexes, venues, street addresses, etc., that are proximate to and/or located at the identified location, and provide this information as location data 177 to the on-demand service application 110. The application manager 115 can cause the UI component 120 to provide the specific location information as part of the user interface 121 so that the user can select a particular store or venue as the current location or the service performance location (e.g., a pick up location or delivery location).
The on-demand service application 110 can also receive user location input provided by the user to determine the current location or service location of the user. In one example, the on-demand service application 110 can cause the UI component 120 to present a location search user interface on the display. The user can input a search term to identify stores, restaurants, venues, addresses, etc., that the user wishes to request the on-demand service. The on-demand service application 110 can perform the search by querying one or more external sources to provide the search results to the user. In some variations, the user can manually provide user location input by entering an address (e.g., with a number, street, city, state) or by manipulating and moving a service location graphic/icon on a map that is displayed as part of a user interface 121. In response to the user selection, the on-demand service application 110 can provide the location data 119 to the on-demand service system 170.
In another variation, the on-demand service application 110 can retrieve and use user information 151 and/or historical information 153 that are stored in a user database 150. The user database 150 can include records of the user's previous on-demand service requests as well as user preferences. In some implementations, the user database 150 can be stored remotely at the on-demand service system 170 and user information can be retrieved from the on-demand service system 170. The on-demand service application 110 can use the data stored in the user database 150 to identify previous service locations for the user (e.g., a BBQ sandwiches food ordering application 110 can access the user database 150 for records of when the user ordered food and where the food was delivered to). Based, in part, on the current location of the computing device 180, the on-demand service application 110 can use the user information 151, such as the user's home address, the user's place of business, the user's preferences, etc., and historical information 153, such as the frequency and recency of previous locations that the user requested services at, to provide recent and/or recommended points of interest to the user. When the user selects one of the entries of a recommended point of interest as a current location and/or pickup location, the on-demand service application 110 can provide the location data 119 to the on-demand service system 170.
Based on the user's current location or service location, the application manager 115 can cause region-specific user interface features 121 to be outputted by the UI component 120. A region that is specific to the user includes the current location (or service location) in which on-demand services can be provided to the user. The region can be a city or metropolitan area in which the computing device 180 is currently located in, can be an area having a predetermined distance radius from current location (e.g., six miles), or can be an area that is specifically partitioned from other areas. Based on the user's region, the application manager 115 can cause region-specific information about the on-demand service to be provided on one or more user interface features 121.
Region-specific information about the on-demand service can be provided, in part, by the on-demand service system 170. As discussed, the on-demand service application 110 can provide location information to the on-demand service system 170 so that the on-demand service system 170 can arrange for a service to be provided to a user (e.g., arrange a transport service or an entertainment provider service). Based on the user-specified region, the on-demand service system 170 can provide information about available service providers (e.g., drivers, or mariachi bands) that can perform the on-demand service in that region.
For example, for a transport service, a transport on-demand service system 170 can maintain information about the number of available vehicles, the number of available drivers, which drivers are currently performing a transport service, which drivers are ready to pick up users, the current location of the vehicles, the direction and destination of the vehicles in motion, etc., in order to properly arrange the transport service between users and drivers. In another example, for a food service, a food on-demand service system 170 can maintain information about the different food trucks that are available, where the food trucks are, how long a food truck will be at a particular location, what type of foods are being served, etc. Because services can vary between regions, such as cities, the application manager 115 can cause only information pertinent to the user's specific region to be provided as part of the user interface 121.
Using the information maintained about the services and the service providers, the on-demand service system 170 can provide relevant information to the on-demand service application 110. Service information 171 can correspond to information about the particular on-demand service that can be arranged by the on-demand service system 170 (e.g., food services, delivery services, transport services, telegram or entertainment services). Service information 171 can include information about costs for the service, available service options (e.g., types of food available, types of entertainment, delivery options), or other details (e.g., available times, specials, etc.). Provider information 173 can correspond to information about the available service providers themselves, such as profile information about the providers, the current location or movement of the delivery vehicles, transport vehicles, food trucks, etc., or the types of vehicles.
Referring back to the example of an on-demand transport service, if the user requests pickup in San Francisco, Calif., the on-demand service system 170 would look for available drivers within a particular distance or particular pickup time from the user (e.g., the system would not consider drivers in Los Angeles, Calif.). The on-demand service system 170 can transmit relevant service information 171 (e.g., cost for the service, promotions in the area) and relevant provider information 173 (e.g., driver information, vehicle information) to the on-demand service application 110 so that the on-demand service application 110 can cause region-specific information to be presented to the user. For any type of on-demand service, the on-demand service system 170 can transmit service information 171 and/or service provider information 173 to the on-demand service application 110.
As an example, a region-specific user interface feature 121 can include a multistate selection panel. The multistate selection panel can include a multistate selection feature that can be manipulated and moved by the user (e.g., by interacting with an input mechanism or a touch-sensitive display screen) in order to select one or more service options to request the on-demand service. Based on the user's determined region, the multistate selection panel can identify and display only certain options that are available for providing the on-demand service in that region. For an on-demand transport service, for example, if limousines or SUVs are unavailable in a particular region, such as San Francisco, but Taxis, Sedans, and hybrid vehicles are available, the multistate selection panel can enable only the available vehicle types to be displayed and/or selected by the user. The indicators for the unavailable types of vehicles, such as limousines and SUVs, for example, can be blocked out, hidden, or displayed in a different manner than indicators for vehicle types that are available in that region.
Similarly, in an example for on-demand dessert, the multistate selection panel can provide different dessert types that are available for selection by a user in the region. If ice cream is unavailable for a particular region, while tarts, cookies, or cheesecakes are available for a user to request, the multistate selection panel can enable only tarts, cookies, or cheesecakes to be selected by the user in requesting the on-demand dessert service.
When the user interacts with the multistate selection feature, additional information corresponding to the selected service option can be provided in a region-specific user interface feature 121. In one implementation, the user interface feature 121 can correspond to a summary panel that displays region-specific information about the selected service option. For example, for an on-demand food or dessert service, once a user makes a selection of a type of service (e.g., a type of food or a certain food truck, etc.), the summary panel can display information about the closest available food provider, the average cost for an order, menu details, service provider profile information, or other information that the user can quickly view to make an informed decision.
In another example, for an on-demand transport service, the summary panel can provide region-specific information, such as the estimated time of arrival for pickup (based on the user's current location or pickup location and the current locations of the available vehicles of the selected type), the average fare based on the region (e.g., the average estimated fare can be region-specific because some regions can be more expensive than other regions and/or some vehicle types can be more expensive than other vehicle types), and the capacity of the vehicle (how many riders can fit in the vehicle). In one variation, the summary panel can be provided concurrently with the multistate selection panel so that when the user manipulates the multistate selection feature to select different service options, the content within the summary panel can be dynamically adjusted by the on-demand service application 110 to provide updated information corresponding to the selected option.
Once the user makes a selection by providing a user input 111, the application manager 115 can cause the UI component 120 to provide user interface features 121 that are based on the selected service option. The user can then make a request for the on-demand service based on the selection. In one example, when the user makes a request, a confirmation user interface feature 121 can be provided by the on-demand service application 110. From this user interface feature, the user can view the details of the request, such as what account or credit card to charge (and can edit or choose a different payment method), provide specific requests to the driver, enter a promotional code for a discount, calculate the price, cancel the request, or confirm the request. As an alternative, the request can be automatically confirmed without displaying a confirmation user interface feature 121.
After the user confirms the request for the on-demand service, the on-demand service application 110 can provide the service request 117 to the on-demand service system 170 via the service interface 125. In some examples, the service request 117 can include the service location specified by the user (e.g., the location where the user would like the service to be performed or provided), the user's account information, the selected service option, any specific notes or requests to the service provider, and/or other information provided by the user. Based on the received service request 117, the on-demand service system 170 can arrange the service between the user and an available service provider that is qualified and capable of providing the on-demand service. The on-demand service system 170 can provide additional provider information 173 to the on-demand service application 110, such as the particular service provider who will be fulfilling the service, the service provider's ratings, etc., so that this information can be provided to the user on a user interface 121.
Methodology
The on-demand service application can automatically determine the current location of the computing device (step 210). According to different implementations, the current location of the computing device (or the selected service location for the on-demand service) can be determined based on location data provided by a geo-aware resource, such as a GPS component of the computing device (sub-step 212), based on user input to search and/or select particular locations (sub-step 214), and/or based on historical data of previous pickup locations of the user (sub-step 216). Using the current location or the service location of the user, a region or area (that includes the current location or the service location) in which the on-demand services are to be performed can be determined by the on-demand service application and/or the on-demand service system. In this manner, the on-demand service system can identify available service providers (e.g., drivers, food trucks, dessert providers, mariachi bands) in the region that can perform the on-demand service.
Based on the determined region and/or the determined current location or service location, a multistate selection feature for selecting one or more of a plurality of service options can be presented on a display of the computing device (step 220). The multistate selection feature can identify, and enable a user to select one of various service options available for a particular on-demand service. For example, the multistate selection feature can identify the specific available vehicle types (e.g., Sedan, Taxi, SUV, hybrid vehicle, electric vehicle, limousine, etc.) that the user can request for an on-demand transport service. The multistate selection feature identifies only those vehicle types that are available in that region to provide the on-demand transport service, so that vehicle types that are unavailable cannot be selected by the user. For example, in one region, such as a particular city, only Sedans and Taxis may be available, whereas in another city, Sedans, Taxis, and SUVs may be available for transport.
The user is enabled to interact with the multistate selection feature in order to make a selection of one or more of the plurality of service options (step 230). In one example, the multistate selection feature that is displayed to the user can be a slider panel with a selectable icon that can slide along a track. In other variations, the multistate selection feature can include features to toggle on or off each of the different available service options in that region. For example, on a mobile computing device with a touch-sensitive display, the user can tap on the different service options to cause the selectable icon to move to the selected option, or hold and drag the selectable icon between the different service options along a track or path. In some instances, when the user moves the selectable icon between the different service options, an indication can be displayed to provide feedback to the user (e.g., when the SUV vehicle type is selected for a transport application, the selectable icon can display an image of an SUV rather than an image of a Sedan or other previously selected vehicle type).
Once the user makes a selection of a service option, the application displays user interface features that are region-specific and selection-specific. In one implementation, a region-specific summary user interface is presented based on the selected service option of the user (step 240). The summary user interface can be region-specific because different regions can have different pricing structures based on usage of the service in the city, the amount of available service providers and/or users, the overall cost of living, etc. The summary user interface can provide a variety of region-specific and selection-specific content to the user so that the user can specify the transport service he or she prefers.
Again, referring to the on-demand transport service example, the summary user interface can identify the estimated time of arrival of the driver (having the selected vehicle type) to the user's current location or service location (e.g., pickup location). The summary user interface can also display the region-specific average fare for the vehicle of the selected type (e.g., the average fare can be an estimated fare based on the locations of the available vehicles and the location of the user), and identify the maximum capacity (number of people the vehicle can drive at once) for the selected vehicle type.
In some implementations, the summary user interface can also be displayed concurrently with the multistate selection feature so that when the user changes the selected service option to select a different service option, the summary user interface can dynamically alter the content based on the adjusted selections. In this manner, the user can easily view the differences (e.g., differences in cost, vehicle size, estimated time for performing the service, estimated time of arrival, types of foods available, etc.) between the service options to make a better judgment on what on-demand service options to request.
When a user initiates and operates the on-demand service application on his or her computing device, for example, a home page user interface can be provided to the user. The user can interact with features on the home page user interface in order to request a service. In some implementations, the home page user interface can include a multistate selection feature 320, as illustrated in
In some cases, based on the user's region, different service options can be provided with the multistate selection feature 320. For example, if the on-demand service application corresponds to a food delivery service, the service options provided with the multistate selection feature 320 can correspond to types of foods that are available in the user's region. The multistate selection feature 320 can be presented on the display to include only service options that are available so that options that are unavailable in that locale are not displayed or are displayed in a different fashion to be distinguishable to the user (e.g., a different color, shading, text type, etc.). In another example, the multistate selection feature 320 can prevent the user from making a selection of a service option that is unavailable if the user attempts to select a stop that corresponds to an unavailable service option. Once the user makes a selection, a summary panel can be provided to the user to display additional detail about the user's selection.
For example, for an on-demand entertainment application, the user can select a mariachi band via the multistate selection feature 320 (e.g., instead of a string quartet or jingle singing group, etc., that is available in the region). The summary panel 360 can include specific information about available mariachi bands in the user's region. The summary panel 360 can provide the average, actual, or estimated cost for the mariachi band in section 361, the number of band members available in section 363, or the earliest the band can perform the service in section 375, or other information, etc., to quickly provide the user with sufficient details in placing the order. In this manner, functionality, such as communicating a variety of information to the user, can be aggregated and provided to the user in an efficient and user-friendly manner.
In
The home page user interface 300a can also include a multistate selection feature 320. The multistate selection feature 320 can include a slider feature 322 that can be manipulated by the user to be moved along a track 321. The multistate selection feature 320 can identify a plurality of service types that are available for providing, for instance, a transport service for the user based on the user's current location (or pickup location). Depending on the user's location, available service providers can be determined for a particular region that includes the user's current location or pickup location. For example, the region can be a city, such as San Francisco, Calif., and the multistate selection feature 320 can identify vehicle types that are available for providing the transport service within the general vicinity or area of San Francisco, Calif.
In the example provided, the multistate selection feature 320 is region-specific so that only the vehicles that are specifically available in San Francisco, Calif. can be selected by the user. The available vehicle types in
In some variations, when the user manipulates the slider feature 322 by moving it between the different selection points along the track 321, the identifier 325 of the selected vehicle type can also be changed to identify the selection. For example, the identifier “Sedan” is elevated as compared to the other identifiers to indicate the selection of “Sedan” type vehicles. In other examples, the selected identifier can be altered in size, color, font, etc., to easily indicate to the user of the selection. As an addition, the graphic 323 provided within the slider feature 322 can dynamically change in order to correspond to the selection (e.g., a graphic of a vehicle that corresponds to a selected vehicle type, a graphic of food type, a graphic of an entertainment selection, etc.).
In one implementation, the slider feature 322 can initially be positioned at a default vehicle type or a default vehicle type that is selected and programmed by the user. In other variations, the slider feature 322 can be initially positioned at a vehicle type that has most frequently been used by the user to request the transport service, or can initially be positioned at a vehicle type that was previously used by the user to request a transport service.
The home page user interface 300a can also include a map that illustrates at least a portion of the region in which the user's current location or pickup location is located in. The map can include a graphic pin 313 that indicates the user's current location or pickup location. In some implementations, the home page user interface 300a can also include a feature (proximate to or as part of the graphic pin 313) that indicates an estimated time of arrival 330 of an available service provider having a vehicle of the selected type, and a request selection feature 340 to enable the user to request the transport service using the selected vehicle type. The estimated time of arrival 330 can dynamically be altered in response to the user changing the selection by moving the slider feature 322 along the track 321.
In some examples, the on-demand service application that operates on the user's computing device can communicate with the on-demand service system to receive real-time information about service providers in the determined region of the user. The on-demand service system can continually (periodically) receive data from the computing devices of the service providers (e.g., such as GPS data, driver and vehicle information) in order to determine the current location of the service providers, the speed and direction in which the service provider is moving, whether a service provider is currently providing a transport service (e.g., is currently occupied), etc., and other service provider information. The on-demand service application can receive information about one or more service providers in the vicinity of the user's current location or pickup location in order to provide real-time information to the user.
For example, based on the selected vehicle type and determined region, one or more graphic vehicle indicators 315 (if any) can be dynamically provided on the map to indicate to the user the current/real-time locations and movements of the service providers having the selected vehicle type. The graphic vehicle indicators 315 can indicate to the user that the driver is currently available to service the user and is within the region or portion of the region in which the user's current location or pickup location is located in. In the example illustrated in
In one implementation, one or more graphic vehicle indicators 315 can move on the map corresponding to the real-time and real-life movements of the service providers' vehicles relative to the user's current location or pickup location. The movements of the graphic vehicle indicators 315 can be determined using provider data (e.g., via provider information 173 transmitted by the transport service system in
In one example, the transport service system can also use one or more databases of streets and roads for maps (e.g., including external databases maintained by third parties or other map sources) to determine how the graphic vehicle indicators 315 can be oriented and moved on a map that is presented to the user (e.g., as part of the home page user interface 300a). The one or more databases can include geocoding information that make up individual streets and roads. By taking the GPS points or coordinates of available vehicles (from the service providers' devices) and drawing lines between the points, the GPS points and lines can be aligned with the geocoding information from the databases. In this manner, real-time vehicle movements and locations can be correlated to maps of streets and roads so that the graphic vehicle indicators 315 can be displayed to the user. In addition, by map-fitting the GPS points with the known geolocations of streets, the transport service system can correct for inconsistencies and smooth out lines between GPS points so that the corresponding graphic vehicle indicators 315 can be accurately displayed on a map to the user on the user's computing device (e.g., on user interface 300a).
The graphic vehicle indicators 315 can then be oriented and aligned in the appropriate directions on the appropriate streets so that the user can easily determine the locations and directions of movement of nearby service provider vehicles, and determine what side of the street the service provider vehicles are on.
In some implementations, when the user makes a selection of a vehicle type using the multistate selection feature 320, a summary user interface 350a can be presented to the user. As illustrated in
The summary panel 360 can include a variety of information related to a transport service that is specific to the locality (e.g., the region) of the user and the selected vehicle type. The summary panel 360 can include an estimated time of arrival (ETA) section 361, an average fare section 363, and a maximum capacity section 365, that each include dynamically provided content that is location-specific (e.g., region-specific) and vehicle-specific. Each of the sections can also include a graphic to represent the corresponding content (e.g., a watch or clock, a receipt or ticket, person). Because the available service providers continue to drive around the region, pick up other customers, make traffic stops, etc., the information provided within the sections 361, 363, 365 can also be dynamically adjusted based on the real-time conditions of the service providers (e.g., the estimated time of arrival can be decreased or increased, or the average estimated fare can be adjusted).
In addition, the location-specific information is based on the selected vehicle type, when the user changes the selection of a vehicle type, the information provided within the sections 361, 363, 365 can be dynamically adjusted. For example, when the summary panel 360 is presented concurrently with the multistate selection feature 320 on the summary user interface 350a, the user can also move the slider feature 322 to select different vehicle types and cause the content within the sections 361, 363, 365 to change accordingly. The maximum capacity of an SUV or Van can be more than four, for example, compared to a Sedan, which can be three, and the closest SUV or Van can be much further away than a Sedan, which can cause the estimated time of arrival to be altered. In another example, a Sedan can be cheaper than an SUV in the user's current region, so that the average estimated fare can be dynamically decreased in cost.
The user can also select a completion feature 367 when he or she has finished viewing the information corresponding to the selected vehicle type. Selecting the completion feature 367 can close the summary user interface 350a to remove the summary panel 360. In other examples, selecting other portions of the summary user interface 350a (e.g., selecting on a region of the semi-transparent shading 370) can cause the summary user interface 350a to be closed (e.g., no longer presented to the user). When the user is done selecting the vehicle type, other user interface features can be provided to enable the user to request the transport service.
The transport application can also provide transport specific information to the user using languages, symbols, and/or prices based on the user's location. For example, the different vehicle types displayed in the multistate selection feature 320 can be identified in French, German, Spanish, etc., based on the country the user operates the transportation application in (e.g., instead of “Sedan” or “Any”). A user can choose to have information provided by the transport application in a particular language (e.g., select a language for the application), such as when first installing the transport application or by selecting a language when first registering the user's device, etc. The user is also free to change languages upon his or her preference.
In another example, the content within the sections 361, 363, 365 of the summary user interface 350a can also be provided in a language selected by the user and/or based on the user's location. If the user was currently in London, England, for example, the average fare section 363 would display the average cost for the selected vehicle type in pounds (GBP) instead of dollars (USD). This enables the transport application to provide text information in a language selected by the user, while at the same time, tailor the content based on the user's location. For example, the user can prefer to operate the transport application in French, while living in London, England. The text information can be provided by the transport application in French, yet continue to provide content based on standards used in England (e.g., provide average fare information in pounds).
As an addition or alternative, the home page user interface 380 of
The home page user interface 380 (and other user interfaces for other on-demand services as described in
When user selects the price adjustment feature 381, informational content about the adjusted pricing can be presented to the user. For example, the user can be notified of the price adjustment, how much the price is being adjusted, why the price is being adjusted, etc., to provide the user with full disclosure before the user agrees to request the service at that price. In some variations, a price adjustment icon 383 can be provided with one or more vehicle types in a user's region to inform the user which particular vehicles are subject to the price adjustment. Dynamic price adjustment is described in U.S. Provisional Patent Application No. 61/612,471, filed Mar. 19, 2012 (the aforementioned application being incorporated by reference in its entirety).
The home page user interface 380 can also include a promotional selection feature 391. The promotional selection feature 391 can be selected by a user to view dynamically provided promotional content that the user can view and request when requesting the transport service. Promotional content is further described with
The user interface 395 can be presented with an expanded map 396 that has been expanded to fit the size of a display screen of the computing device in response to a user selection. The user selection can correspond to, for example, the user interacting with (e.g., tapping, tapping and holding, or double tapping, etc.) a portion of a map of a previously displayed user interface. For example, if the user interface 380 of
The user interface 395 can also include a reduce feature 397 that can be selectable in order to return the map to a previous size and re-display the previously displayed user interface feature. In some cases, the graphic transition can show the transition of the expanded map 396 reducing in size from the larger size to a smaller size, such as the map in
The location suggestion user interface 400 enables a user to select particular locations, such as stores, restaurants, parks, venues, etc., that can be precisely and easily identified by a service provider when the user requests to have the on-demand service be performed or fulfilled. For example, the user can select the location at which the user would like his or her food to be delivered at (e.g., the user's office or home, or a friend's apartment, etc.) or the location where the mariachi band should play at (e.g., at a bar or restaurant). In another example, referring back to
In some implementations, other suggested entries 440 can be provided based on historical/previous pickup locations of the user and/or based on user-specific data. Based on the current location of the computing device, the on-demand service application can access user information that includes previously requested services and/or personal user information (e.g., the user's home address, the user's place of business, the user's preferences) to provide one or more user-based location entries 420, 440. Historical information, such as the frequency or recency of previous service locations that the user requested service to be performed at, can be used to provide recent and/or recommended points of interest to the user.
In this manner, the on-demand service application can predict what particular service locations the user would like to select. The one or more suggested entries 440 can be displayed based on a combination of the user's current location (e.g., the nearness of service locations) and the recency of previous service locations and/or the total frequency of particular service locations. In some examples, the suggested locations can also be ranked based on the scores of the suggested locations determined using a recency, frequency, or nearness algorithm. The user can also select the search field 410 in order to search for other locations or venues that are not listed in the suggestions 420, 430. A cancellation feature 415 can be selected by the user to close the location suggestion user interface 400 and request service at the location already determined and identified on a location identifier (such as the pickup location identifier 310 of
The location search user interface 450 of
A confirmation user interface 500 can provide a variety of information that the user can confirm before the on-demand service system arranges the on-demand service for the user. Referring back to the transport service example, the confirmation user interface 500 can include a pickup location marker 520 and a pickup location panel 510 that identifies the selected vehicle type (e.g., Sedan) as a graphic and/or text, and the pickup location (e.g., automatically determined from the current user location or determined from user selections). The confirmation user interface 500 can also include additional features, such as markers 530 (a marker identifying the destination, if selected by a user via a user interface, or a marker identifying the current location of the driver that is to provide the transport service). As another example, if the user is requesting an ice cream truck, the confirmation user interface 500 can include a service destination marker, a current ice cream truck location marker, and other additional information.
The confirmation user interface 500 can also provide the user's financial account information 540 (e.g., a bank routing and/or account number, a credit card number, etc.) that is used to pay for the requested on-demand service. The user can have the option to use a different account to pay for the service if he or she prefers. In some variations, the confirmation user interface 500 can also provide selectable features 550, 560, 570 for calculating the price or fare, providing a specific note or additional information to the driver, and for entering a promotional code to receive discounts or other promotional services.
Once the user views the information provided, the user can select the confirmation feature 580 to confirm the requested on-demand service. The on-demand service system can then receive appropriate information from the on-demand service application, charge the account, communicate with available service providers in the vicinity of the user's service location, arrange the on-demand service between the user and a driver, and/or provide a transaction confirmation or receipt to the user. If the information provided on the confirmation user interface 500 is incorrect, or the user wishes to cancel the request for whatever reason, the user can simply select the “cancel” feature to change the service options and/or the service location.
The confirmation user interface 590 can also enable a user to correct or alter a pick up location or drop off location without having to backtrack or return to previously displayed user interfaces (e.g., user interfaces for requesting a service or for searching for a location). The user can, for example, interact with the service location identifier and/or the displayed map in order to change a service location. A user can also interact directly with the displayed map of the confirmation user interface 590 in order to dynamically adjust the displayed portion of the map (e.g., pan, zoom in, zoom out). The user can zoom in/out and/or pan the map in one or more directions, for example, to see the closest available service provider(s) or the overall geography (streets, freeways, locations of interest, etc.) of the region. In this manner, the confirmation user interface 590 can dynamically display different portions of the map based on user preference.
In some implementations, the confirmation user interface 590 can include a confirmation feature 595 that dynamically alters its text (e.g., its content within the selectable feature) based on the user selections for the service. For example, instead of the text “confirm” within the confirmation feature 580, the confirmation feature 595 can specify “request black car” or “request sedan,” etc., based on the user selected request. Despite the different variations or layouts, the confirmation user interfaces 500, 590 can display information about the user's requested service in a clear and informative manner on a single panel.
The detailed information provided in the fare information panel 600 can identify an estimated or anticipated fare for the service, or can identify the actual fare that a service provider abides by. The detailed information can be adjusted depending the user's location (e.g., the user's current location, the pickup location and/or destination location, etc.) and the user's selected service option. For example, for a transport service or a delivery service, the determined fares 610, 620, 630 can be adjusted depending on the type of vehicle the user has selected (e.g., via the multistate selection panel). In other examples, the threshold levels for the fares can be adjusted depending on the user's location or the service option (e.g., instead of 11 mph, increased to 13 mph).
In
Once the subsequent user interface feature 730, such as a promotional user interface, is provided, the user can view the information displayed and navigate back to the previous (or different) user interface (e.g., back to a home page user interface or confirmation user interface, etc.).
As an addition or alternative, the graphical transitions described with respect to
Still further, a graphical transition can include a visual expansion (from a first size to a second larger size, for example) of a feature on a user interface and/or a visual reduction of a feature. Referring to
Hardware Diagrams
The processor 810 is configured with software and/or other logic to perform one or more processes, steps and other functions described with implementations, such as described by
The location data 865 can also be provided to the on-demand service system using the communication sub-systems 840. The communication sub-systems 840 can enable the computing device 800 to communicate with other servers and computing devices, for example, over a network (e.g., wirelessly or using a wire). The location data 865 can be communicated to the on-demand service system so that when the user requests the on-demand service, the system can arrange the service between the user and an available service provider. The communication sub-systems 840 can also receive provider information 845 (such as location and/or movement information of drivers in real-time) from the on-demand service system and transmit the provider information 845 to the processor 810 for displaying driver data on one or more user interfaces 815.
The processor 810 can cause user interface features to be presented on the display 830 by executing instructions and/or applications that are stored in the memory resources 820. In some examples, user interfaces 815, such as user interfaces described with respect to
It is contemplated for embodiments described herein to extend to individual elements and concepts described herein, independently of other concepts, ideas or system, as well as for embodiments to include combinations of elements recited anywhere in this application. Although embodiments are described in detail herein with reference to the accompanying drawings, it is to be understood that the invention is not limited to those precise embodiments. As such, many modifications and variations will be apparent to practitioners skilled in this art. Accordingly, it is intended that the scope of the invention be defined by the following claims and their equivalents. Furthermore, it is contemplated that a particular feature described either individually or as part of an embodiment can be combined with other individually described features, or parts of other embodiments, even if the other features and embodiments make no mentioned of the particular feature. Thus, the absence of describing combinations should not preclude the inventor from claiming rights to such combinations.
This application is a continuation of U.S. patent application Ser. No. 15/457,948, filed Mar. 13, 2017, which is a continuation of U.S. patent application Ser. No. 14/924,705, filed Oct. 27, 2015, now U.S. Pat. No. 10,417,673, which is a continuation of U.S. patent application Ser. No. 13/672,634, filed Nov. 8, 2012, now U.S. Pat. No. 9,230,292, which is a continuation-in-part of U.S. patent application Ser. No. 12/961,493, filed Dec. 6, 2010, which claims benefit of priority to Provisional U.S. Patent Application No. 61/266,996, filed Dec. 4, 2009; the aforementioned priority applications being incorporated by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3953720 | Kelch | Apr 1976 | A |
| 5043736 | Darnell | Aug 1991 | A |
| 5168451 | Bolger | Dec 1992 | A |
| 5293642 | Lo | Mar 1994 | A |
| 5862244 | Kleiner et al. | Jan 1999 | A |
| 5930474 | Dunworth et al. | Jul 1999 | A |
| 6057831 | Harms | May 2000 | A |
| 6339745 | Novik | Jan 2002 | B1 |
| 6356838 | Paul | Mar 2002 | B1 |
| 6417856 | Tamura | Jul 2002 | B1 |
| 6446004 | Cao | Sep 2002 | B1 |
| 6456207 | Yen | Sep 2002 | B1 |
| 6456852 | Bar | Sep 2002 | B2 |
| 6516056 | Justice et al. | Feb 2003 | B1 |
| 6519463 | Tendler | Feb 2003 | B2 |
| 6522342 | Gagnon | Feb 2003 | B1 |
| 6591253 | Dinkin | Jul 2003 | B1 |
| 6697730 | Dickerson | Feb 2004 | B2 |
| 6756913 | Ayed | Jun 2004 | B1 |
| 6804658 | Lim et al. | Oct 2004 | B2 |
| 6925381 | Adamczyk | Aug 2005 | B2 |
| 7064681 | Horstmeyer | Jun 2006 | B2 |
| 7089110 | Pechatnikov et al. | Aug 2006 | B2 |
| 7113110 | Horstmeyer | Sep 2006 | B2 |
| 7119716 | Horstmeyer | Oct 2006 | B2 |
| 7191057 | Adamcyzk | Mar 2007 | B2 |
| 7315780 | Sugahara et al. | Jan 2008 | B2 |
| 7319414 | Horstmeyer | Jan 2008 | B2 |
| 7394386 | Nowlan | Jul 2008 | B2 |
| 7395140 | Christie | Jul 2008 | B2 |
| 7412042 | Henry | Aug 2008 | B2 |
| 7412715 | Kim | Aug 2008 | B2 |
| 7434177 | Ording et al. | Oct 2008 | B1 |
| 7479899 | Horstmeyer | Jan 2009 | B2 |
| 7479900 | Horstmeyer | Jan 2009 | B2 |
| 7479901 | Horstmeyer | Jan 2009 | B2 |
| 7487467 | Kawahara et al. | Feb 2009 | B1 |
| 7504966 | Horstmeyer | Mar 2009 | B2 |
| 7528742 | Horstmeyer | May 2009 | B2 |
| 7538691 | Horstmeyer | May 2009 | B2 |
| 7482952 | Horstmeyer | Jun 2009 | B2 |
| 7552063 | McEachern | Jun 2009 | B1 |
| 7561069 | Horstmeyer | Jul 2009 | B2 |
| 7673251 | Wibisono | Mar 2010 | B1 |
| 7756615 | Barfoot | Jul 2010 | B2 |
| 7756633 | Huang | Jul 2010 | B2 |
| 7864935 | Elliott | Jan 2011 | B2 |
| 7869945 | Huang | Jan 2011 | B2 |
| 7876239 | Horstmeyer | Jan 2011 | B2 |
| 7970533 | Huang | Jun 2011 | B2 |
| 7974779 | Huang | Jul 2011 | B2 |
| 8036824 | Huang | Oct 2011 | B2 |
| 8068037 | Horstmeyer | Nov 2011 | B2 |
| 8086400 | Huang | Dec 2011 | B2 |
| 8099085 | Lowry | Jan 2012 | B2 |
| 8131307 | Lubeck et al. | Mar 2012 | B2 |
| 8140256 | dos-Santos | Mar 2012 | B1 |
| 8224571 | Huang | Jul 2012 | B2 |
| 8232899 | Horstmeyer | Jul 2012 | B2 |
| 8242935 | Horstmeyer | Aug 2012 | B2 |
| 8271316 | Blackshaw et al. | Sep 2012 | B2 |
| 8284076 | Horstmeyer | Oct 2012 | B1 |
| 8362927 | Horstmeyer | Jan 2013 | B2 |
| 8368562 | Horstmeyer | Feb 2013 | B2 |
| 8374627 | Howard et al. | Feb 2013 | B2 |
| 8386593 | Gao | Feb 2013 | B1 |
| 8531317 | Horstmeyer | Sep 2013 | B2 |
| 8554608 | O'Conner | Oct 2013 | B1 |
| 8564459 | Horstmeyer | Oct 2013 | B2 |
| 8775938 | Rosser | Jul 2014 | B2 |
| 20020034292 | Tuoriniemi et al. | Mar 2002 | A1 |
| 20020077905 | Arndt | Jun 2002 | A1 |
| 20020095326 | Katz | Jul 2002 | A1 |
| 20020138338 | Trauth et al. | Sep 2002 | A1 |
| 20020194129 | Furuya et al. | Dec 2002 | A1 |
| 20030040944 | Hileman | Feb 2003 | A1 |
| 20030043206 | Duarte | Mar 2003 | A1 |
| 20030087648 | Mezhvinsky et al. | May 2003 | A1 |
| 20030137435 | Haddad | Jul 2003 | A1 |
| 20040049424 | Murray | Mar 2004 | A1 |
| 20040054428 | Sheha et al. | Mar 2004 | A1 |
| 20040070602 | Kobuya | Apr 2004 | A1 |
| 20040093280 | Yamaguchi | May 2004 | A1 |
| 20040100479 | Nakano et al. | May 2004 | A1 |
| 20040106399 | Ki | Jun 2004 | A1 |
| 20040112959 | Jun | Jun 2004 | A1 |
| 20040155907 | Yamaguchi | Aug 2004 | A1 |
| 20040158483 | LeCouturier | Aug 2004 | A1 |
| 20040185842 | Spaur et al. | Sep 2004 | A1 |
| 20040219933 | Faith | Nov 2004 | A1 |
| 20040243430 | Horstmeyer | Dec 2004 | A1 |
| 20040249818 | Isaac | Dec 2004 | A1 |
| 20040254717 | Sugahara et al. | Dec 2004 | A1 |
| 20040254811 | Horstmeyer | Dec 2004 | A1 |
| 20040260470 | Rast | Dec 2004 | A1 |
| 20050091596 | Anthony et al. | Apr 2005 | A1 |
| 20050149382 | Fenner et al. | Jul 2005 | A1 |
| 20050227704 | Ferra et al. | Oct 2005 | A1 |
| 20050240512 | Quintero | Oct 2005 | A1 |
| 20050251333 | Adamzyk | Nov 2005 | A1 |
| 20050278063 | Hersh et al. | Dec 2005 | A1 |
| 20050278114 | Ahmad | Dec 2005 | A1 |
| 20060034201 | Umeda et al. | Feb 2006 | A1 |
| 20060048076 | Vronay et al. | Mar 2006 | A1 |
| 20060059023 | Mashinsky | Mar 2006 | A1 |
| 20060094447 | Zellner | May 2006 | A1 |
| 20060135134 | Mezhvinsky et al. | Jun 2006 | A1 |
| 20060136254 | Greenstein | Jun 2006 | A1 |
| 20060149681 | Meisner | Jul 2006 | A1 |
| 20060155460 | Raney | Jul 2006 | A1 |
| 20060161346 | Murakami et al. | Jul 2006 | A1 |
| 20060178949 | McGrath | Aug 2006 | A1 |
| 20060200306 | Adamcyzk | Sep 2006 | A1 |
| 20060200396 | Satterfield | Sep 2006 | A1 |
| 20060217885 | Crady et al. | Sep 2006 | A1 |
| 20060229778 | Obradovich et al. | Oct 2006 | A1 |
| 20060268100 | Karukka et al. | Nov 2006 | A1 |
| 20060271867 | Wang et al. | Nov 2006 | A1 |
| 20070073477 | Krumm et al. | Mar 2007 | A1 |
| 20070103342 | Milleville | May 2007 | A1 |
| 20070176796 | Bliss et al. | Aug 2007 | A1 |
| 20070197229 | Kalliola | Aug 2007 | A1 |
| 20070198276 | Hinrichs et al. | Aug 2007 | A1 |
| 20080005695 | Ozzie | Jan 2008 | A1 |
| 20080070593 | Hill | Mar 2008 | A1 |
| 20080076451 | Sheha | Mar 2008 | A1 |
| 20080114629 | Pavlov | May 2008 | A1 |
| 20080125967 | Sprigg | May 2008 | A1 |
| 20080172173 | Chang et al. | Jul 2008 | A1 |
| 20080178116 | Kim | Jul 2008 | A1 |
| 20080189207 | Wurster | Aug 2008 | A1 |
| 20080195428 | O'Sullivan | Aug 2008 | A1 |
| 20080270019 | Anderson | Oct 2008 | A1 |
| 20080270204 | Poykko | Oct 2008 | A1 |
| 20080277183 | Huang | Nov 2008 | A1 |
| 20080288880 | Reponen et al. | Nov 2008 | A1 |
| 20080307512 | Tandon | Dec 2008 | A1 |
| 20090030885 | DePasquale et al. | Jan 2009 | A1 |
| 20090037101 | Koike | Feb 2009 | A1 |
| 20090049119 | Marcinkiewicz et al. | Feb 2009 | A1 |
| 20090083111 | Carr | Mar 2009 | A1 |
| 20090099971 | Salemme et al. | Apr 2009 | A1 |
| 20090106124 | Yang | Apr 2009 | A1 |
| 20090125228 | Dicke | May 2009 | A1 |
| 20090156241 | Staffaroni et al. | Jun 2009 | A1 |
| 20090171529 | Hayatoma | Jul 2009 | A1 |
| 20090171576 | Kim et al. | Jul 2009 | A1 |
| 20090172599 | Nezu | Jul 2009 | A1 |
| 20090176508 | Lubeck et al. | Jul 2009 | A1 |
| 20090177384 | Walder | Jul 2009 | A1 |
| 20090177385 | Matas et al. | Jul 2009 | A1 |
| 20090177502 | Doinoff et al. | Jul 2009 | A1 |
| 20090192851 | Bishop | Jul 2009 | A1 |
| 20090204920 | Beverley et al. | Aug 2009 | A1 |
| 20090216600 | Hill | Aug 2009 | A1 |
| 20090222284 | McEachern | Sep 2009 | A1 |
| 20090254270 | Yu | Oct 2009 | A1 |
| 20090282353 | Halbherr et al. | Nov 2009 | A1 |
| 20090313077 | Wheeler | Dec 2009 | A1 |
| 20090326991 | Wei | Dec 2009 | A1 |
| 20100017275 | Carlson | Jan 2010 | A1 |
| 20100023246 | Zhao | Jan 2010 | A1 |
| 20100035596 | Nachman et al. | Feb 2010 | A1 |
| 20100070334 | Monteverde | Mar 2010 | A1 |
| 20100076988 | Kenedy et al. | Mar 2010 | A1 |
| 20100088026 | Manolescu | Apr 2010 | A1 |
| 20100115455 | Kim | May 2010 | A1 |
| 20100121689 | Wallace | May 2010 | A1 |
| 20100153292 | Zheng et al. | Jun 2010 | A1 |
| 20100182265 | Kim | Jul 2010 | A1 |
| 20100198453 | Dorogusker et al. | Aug 2010 | A1 |
| 20100199213 | Suzuki | Aug 2010 | A1 |
| 20100211340 | Lowenthal | Aug 2010 | A1 |
| 20100235085 | Kikuchi | Sep 2010 | A1 |
| 20100243724 | Golla | Sep 2010 | A1 |
| 20100228415 | Paul | Nov 2010 | A1 |
| 20100299436 | Khalid | Nov 2010 | A1 |
| 20110010300 | Audet | Jan 2011 | A1 |
| 20110050588 | Li | Mar 2011 | A1 |
| 20110052110 | Kim | Mar 2011 | A1 |
| 20110060480 | Mottla et al. | Mar 2011 | A1 |
| 20110069017 | Victor | Mar 2011 | A1 |
| 20110099040 | Felt et al. | Apr 2011 | A1 |
| 20110060600 | Fox et al. | May 2011 | A1 |
| 20110112952 | Annunziata | May 2011 | A1 |
| 20110137696 | Meyer et al. | Jun 2011 | A1 |
| 20110137699 | Ronen et al. | Jun 2011 | A1 |
| 20110153192 | Lin | Jun 2011 | A1 |
| 20110153453 | Gameelah | Jun 2011 | A1 |
| 20110153495 | Dixon | Jun 2011 | A1 |
| 20110177845 | Fasold | Jul 2011 | A1 |
| 20110197131 | Duffin et al. | Aug 2011 | A1 |
| 20110208732 | Melton et al. | Aug 2011 | A1 |
| 20110218992 | Waldman et al. | Sep 2011 | A1 |
| 20110221765 | Nason et al. | Sep 2011 | A1 |
| 20110238690 | Arrasvuori | Sep 2011 | A1 |
| 20110283223 | Vaittinen | Nov 2011 | A1 |
| 20110307282 | Camp | Dec 2011 | A1 |
| 20110313880 | Paul et al. | Dec 2011 | A1 |
| 20120041675 | Juliver | Feb 2012 | A1 |
| 20120084676 | de Paz | Apr 2012 | A1 |
| 20120130627 | Islam et al. | May 2012 | A1 |
| 20120179764 | Erdal | Jul 2012 | A1 |
| 20120203599 | Choi | Aug 2012 | A1 |
| 20120225671 | Lubeck et al. | Sep 2012 | A1 |
| 20120226390 | Adams | Sep 2012 | A1 |
| 20120232943 | Myr | Sep 2012 | A1 |
| 20120239452 | Trivedi et al. | Sep 2012 | A1 |
| 20120313965 | Mochizuki et al. | Dec 2012 | A1 |
| 20120323642 | Camp | Dec 2012 | A1 |
| 20120327009 | Fleizach | Dec 2012 | A1 |
| 20120330778 | Eastham | Dec 2012 | A1 |
| 20130024249 | Zohar et al. | Jan 2013 | A1 |
| 20130041720 | Spires | Feb 2013 | A1 |
| 20130050131 | Lee | Feb 2013 | A1 |
| 20130132140 | Amin | May 2013 | A1 |
| 20130132246 | Amin | May 2013 | A1 |
| 20130132887 | Amin et al. | May 2013 | A1 |
| 20130162627 | Gabara | Jun 2013 | A1 |
| 20130191141 | Chun | Jul 2013 | A1 |
| 20130204676 | Hindi et al. | Aug 2013 | A1 |
| 20130268406 | Radhakrishnan et al. | Oct 2013 | A1 |
| 20130290040 | Perry | Oct 2013 | A1 |
| 20140026065 | Wang | Jan 2014 | A1 |
| 20140036076 | Nerayoff | Feb 2014 | A1 |
| 20140047346 | Karamchedu | Feb 2014 | A1 |
| 20140051465 | Ruys et al. | Feb 2014 | A1 |
| 20140067491 | James | Mar 2014 | A1 |
| 20140129135 | Holden et al. | May 2014 | A1 |
| 20140129302 | Amin | May 2014 | A1 |
| 20140172727 | Abhyanker | Jun 2014 | A1 |
| 20140180732 | Rotchin | Jun 2014 | A1 |
| 20140180733 | Rotchin | Jun 2014 | A1 |
| 20150012341 | Amin | Jan 2015 | A1 |
| 20150046080 | Wesselius et al. | Feb 2015 | A1 |
| 20160021154 | Schoeffler | Jan 2016 | A1 |
| 20170186056 | Amin | Jun 2017 | A1 |
| 20180211194 | Camp | Jul 2018 | A1 |
| 20190220778 | Camp | Jul 2019 | A1 |
| 20200088540 | Nainwal | Mar 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 102402852 | Apr 2012 | CN |
| 102496265 | Jun 2012 | CN |
| 102682593 | Sep 2012 | CN |
| 2367979 | Apr 2002 | GB |
| 2001188996 | Jul 2001 | JP |
| 2002024659 | Jan 2002 | JP |
| 10-2005-0015772 | Feb 2005 | KR |
| 10-2009-0109044 | Oct 2009 | KR |
| 10-1006599 | Jan 2011 | KR |
| WO9944186 | Sep 1999 | WO |
| WO 2002006994 | Jan 2002 | WO |
| WO2010056923 | Nov 2009 | WO |
| WO 2011014076 | Mar 2011 | WO |
| Entry |
|---|
| International Search Report and Written Opinion, International Application No. PCT/US2010/059152, dated Mar. 28, 2011, pp. 1-11. |
| Examination Report for Australian Application No. 2010325793, dated Jun. 21, 2013. |
| Search Report dated Oct. 1, 2013, for related EP Application No. 10835261.8. |
| Alfred Round et al. “Future Ride: Adapting New Technologies to Paratransit in the United States”, Working Paper, UCTC No. 306, University of California Transportation Center, 51 pages. |
| International Search Report and Written Opinion, International Application No. PCT/US2013/68025, dated Apr. 15, 2014, pp. 12. |
| Shigematsu et al. “AVM System”, Fujistu Ten Technical Journal No. 33, 27:34, (2009). |
| Uber iPhone app update 1.0.48, Jun. 27, 2011, http:/blog.uber.com/2011/06/27/uber-iphone-app-update 1-0-48. |
| International Search Report and Written Opinion, International Application No. PCT/US2015/056703 dated Feb. 2, 2016. |
| Chinese Search Report dated Jun. 22, 2016 in CN 2013800627666. |
| Kikuchi, et al., “Advanced Traveler Aid Systems for Public Transportation”, US Department of Transportation, Sep. 1994. |
| Fu, et al., “On-Line and Off-Line Routing and Scheduling of Dial-a-Ride Paratransit Vehicles”, Computer-Aided Civil and Infrastructure Engineering 14 (1999). |
| Edward W. Walbridge, “Real-Time Ridesharing Using Wireless Pocket Phones To Access The Ride Matching Computer”, 1995 IEEE. |
| EESR in EP 10835261.8 dated Oct. 10, 2016. |
| 2nd Office Action in CN 201380062766.6 dated Jan. 3, 2017. |
| Examination Report No. 2 for Australian Application No. 2015202596 dated May 22, 2017. |
| Examination Report No. 1 for Australian Application No. 2016210772 dated Nov. 14, 2017. |
| Office Action in European Application No. 13853639.6 dated Jun. 11, 2018. |
| Examination Report No. 2 for Australian Application No. 2016210722 dated Jul. 27, 2018. |
| Walsh, HTML5 Link Prefetching, Jul. 7, 2010, https://davidwalsh.name/html5-prefetch. |
| Gill et al., AMP: Adaptive Multi-stream Prefetching in a Shared Cache, Dec. 19, 2006, https://www.usenix.org/ legacy/events/fast07/tech/full_papers/gill/gill_html/ amp-html.html. |
| Gill et al., AMP: Adaptive Multi-stream Prefetching in a Shared Cache—Introduction, Dec. 19, 2006, https://www.usenix.org/ legacy/events/fast07/tech/fuIl_papers/gill/gill_html/node1.html. |
| EESR in EP 19165275.9 dated Apr. 18, 2019. |
| Examination Report No. 1 for Australian Application No. 2019268109 dated Nov. 4, 2020. |
| Mukai, Dynamic Location Management for On-Demand Car Sharing System, 2005, In: Khosia R., Howlett R.J., Jain L.C. (eds) Knowledge-Based Intelligent Information and Engineering Systems, KES 2005. Lecture Notes in Computer Science, vol. 3681. Springer, Berlin, Heidelberg, pp. 768-744 (2005). |
| Number | Date | Country | |
|---|---|---|---|
| 20200342505 A1 | Oct 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15457948 | Mar 2017 | US |
| Child | 16927771 | US | |
| Parent | 14924705 | Oct 2015 | US |
| Child | 15457948 | US | |
| Parent | 13672634 | Nov 2012 | US |
| Child | 14924705 | US |
