US20110313804A1 - System and method for arranging transport amongst parties through use of mobile devices - Google Patents
System and method for arranging transport amongst parties through use of mobile devices Download PDFInfo
- Publication number
- US20110313804A1 US20110313804A1 US12/961,493 US96149310A US2011313804A1 US 20110313804 A1 US20110313804 A1 US 20110313804A1 US 96149310 A US96149310 A US 96149310A US 2011313804 A1 US2011313804 A1 US 2011313804A1
- Authority
- US
- United States
- Prior art keywords
- customer
- transport
- driver
- request
- geographic location
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title claims abstract description 43
- 230000004044 response Effects 0.000 claims description 14
- 238000012546 transfer Methods 0.000 claims description 12
- 230000001413 cellular effect Effects 0.000 claims description 11
- 238000013507 mapping Methods 0.000 claims description 4
- 230000002250 progressing effect Effects 0.000 claims description 2
- 230000007423 decrease Effects 0.000 claims 1
- 230000032258 transport Effects 0.000 description 224
- 238000004891 communication Methods 0.000 description 23
- 230000008569 process Effects 0.000 description 14
- 238000012544 monitoring process Methods 0.000 description 8
- 230000009471 action Effects 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 238000004458 analytical method Methods 0.000 description 4
- 238000013459 approach Methods 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 4
- 244000107946 Spondias cytherea Species 0.000 description 3
- 230000008901 benefit Effects 0.000 description 3
- 238000004422 calculation algorithm Methods 0.000 description 3
- 238000012790 confirmation Methods 0.000 description 3
- 238000001514 detection method Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 2
- 238000011156 evaluation Methods 0.000 description 2
- 230000033001 locomotion Effects 0.000 description 2
- RZVAJINKPMORJF-UHFFFAOYSA-N Acetaminophen Chemical compound CC(=O)NC1=CC=C(O)C=C1 RZVAJINKPMORJF-UHFFFAOYSA-N 0.000 description 1
- 230000004656 cell transport Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000011176 pooling Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 230000029305 taxis Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/02—Reservations, e.g. for tickets, services or events
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/02—Reservations, e.g. for tickets, services or events
- G06Q10/025—Coordination of plural reservations, e.g. plural trip segments, transportation combined with accommodation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0201—Market modelling; Market analysis; Collecting market data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0201—Market modelling; Market analysis; Collecting market data
- G06Q30/0202—Market predictions or forecasting for commercial activities
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0283—Price estimation or determination
- G06Q30/0284—Time or distance, e.g. usage of parking meters or taximeters
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
-
- G06Q50/40—
Definitions
- Embodiments described herein pertain generally to a system and method for arranging transport amongst parties through use of mobile devices that are carried by the respective parties.
- FIG. 1 illustrates a system for enabling transport to be arranged between parties that are at different geographic locations, according to one or more embodiments.
- FIG. 2 illustrates a mobile computing device that can be used by either customers or respondents, in implementing a system such as described with FIG. 1 .
- FIG. 3 illustrates components for implementing a service, such as described with other embodiments.
- FIG. 4 illustrates a process for programmatically transferring funds from a customer to a relevant transport party as a mechanism for compensating the transport party, according to an embodiment.
- FIG. 5 illustrates a process for enabling fee splitting amongst multiple customers that share a transport, according to one or more embodiments.
- FIG. 6 illustrates a method for processing data determined from monitoring transport amongst parties located at different locations, according to one or more embodiments.
- FIG. 7A through FIG. 7F illustrate examples of a series of user-interfaces that are displayed to a customer as transportation is requested and provided, according to an embodiment.
- FIG. 8A through FIG. 8F illustrate examples of a series of user-interfaces that are displayed to the driver/respondent when accepting and providing transport to a customer, according to an embodiment.
- a system and method are described for enabling transportation to be arranged for individuals carrying mobile devices (e.g. handsets).
- a customer can transmit a request for transport from a given customer geographic location.
- a service may handle the request by selecting a party to provide transport to the customer.
- the pairing of the party to the customer requesting the transport is performed programmatically and/or automatically, based on parameters such as the location of the driver (or a vehicle of the transport party).
- Some embodiments provide that a location of the customer is communicated to a service and/or driver using programmatic resources of the customer's handset.
- individual drivers may be selected as respondents to a customer request, whom in turn have the option to accept the assignment.
- information about the driver e.g. the location of the driver when the fare was accepted, a picture of the driver, his rating etc.
- the driver may also be provided information about the customer (e.g. the picture of the customer, the customer's rating, the customer's precise location).
- some embodiments provide that the customer is provided updates as to the location of the vehicle of the driver en route to the customer.
- the updates may be provided in real-time or near-real time, to reflect the progression of the driver towards the customer.
- embodiments recognize that transport services often have vehicles that have down-time because they are between fares.
- limousine or black cabs
- embodiments provided herein enable the operators of the vehicles to field transport requests from, for example, their handsets.
- the handsets may correspond to, for example, (i) cellular telephony or data devices (e.g. APPLE IPHONE) that run a program that is part of a transport platform, and/or (ii) roaming devices that can connect to access points (e.g. hot spot) or operate under other wireless networks (e.g. WiMax).
- access points e.g. hot spot
- WiMax wireless networks
- the drivers/respondents When the drivers/respondents are free (e.g. between fares), they can operate the program on their devices to field transport requests.
- Customers may run a program of the same platform on similar handsets or devices, in order to make requests for transport from their respective location.
- a service (such as provided online, through use of a server) may select a respondent/driver (or transport), and perform some intermediary functions (such as make payment).
- Various parts of the transport transaction in which a customer is picked up and transported to a desired location, are handled programmatically, through computing resources of the platform.
- embodiments employ such programmatic components in order to facilitate the ability of customers to request transport, as well as to facilitate transport providing parties and customers to meet at the pickup site and to conduct their business.
- the geographic location of the respective parties is determined programmatically using geo-aware resources. This information is communicated to the other party without need for manual involvement by the party operating the handset.
- the customer makes the request for transport, his location at the time of making the request can automatically be included in the request.
- the respondent/driver accepts the fare and starts to travel to the customer, his location and other relevant information (such as continuously updated estimated time of arrival) can be automatically communicated to the customer.
- the fare for the transport is determined automatically, using a program platform that is shared by the devices of both customer and driver. Moreover, the customer's funds may be automatically accessed and transferred to the driver/respondent. Thus, the driver is provided an incentive in participating in the platform, by being assured that funds for services will be received.
- each party is able to provide a rating or feedback of the other party for the transaction.
- they can record a rating that affects the reputation of the other party in using the service. In this way, both parties can be motivated to perform and behave well, thereby increasing the quality of the experience to both customer and driver.
- embodiments enable a system such as described to be implemented using commercially available handsets and devices.
- devices that may be operated by customers or respondents (e.g. drivers) include multifunctional cellular telephony devices (e.g. APPLE IPHONE, devices that operate the Android operating system), and wireless network enabled devices such as laptops, netbooks or tables (e.g. iPAD).
- APPLE IPHONE multifunctional cellular telephony devices
- wireless network enabled devices such as laptops, netbooks or tables
- iPAD wireless network enabled devices
- Customer's who wish to use a transport service such as described need to only download or otherwise run a program on a suitable handset.
- drivers who wish to participate need only to run a corresponding program on a similar handset.
- 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 means through the use of code, or computer-executable instructions. A programmatically performed step may or may not be automatic.
- a programmatic module or component may include a program, a subroutine, a portion of a program, or a software component or a hardware component capable of performing one or more stated tasks or functions.
- 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.
- 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.
- 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 many cell phones and personal digital assistants (PDAs)), and magnetic memory.
- Computers, terminals, network enabled devices e.g.
- mobile devices such as cell phones
- processors such as RAM
- memory such as RAM
- instructions stored on computer-readable mediums
- embodiments may be implemented in the form of computer-programs, or a computer usable carrier medium capable of carrying such a program.
- FIG. 1 illustrates a system for enabling transport to be arranged between parties that are at different geographic locations, according to some embodiments.
- a customer 110 also referred as to a customer
- a transport service 120 locates a respondent 130 (also referred to as ‘respondent’ or ‘driver’) from a pool of possible respondents, in order to drive the customer 110 to a desired destination.
- respondent 130 also referred to as ‘respondent’ or ‘driver’
- the customer 110 operates a handset 105 to generate a request for transport 112 .
- the handset 105 may include roaming network capabilities (e.g. network interface for cellular network, Wireless Fidelity 802.11 (a), (g) (n), or WiMax etc.), along with geo-aware resources (e.g. GPS).
- the network functionality enables the handset 105 to transmit request 112 and communicate further with service 120 or respondents 130 .
- the geo-aware resources enable the handset to automatically include geographic identification information 124 that identifies the geographic location of the customer 110 when making the request 112 .
- the handset 105 may also be configured to include identification information that identifies the customer 110 to either the service 120 or to the respondent 130 .
- the identification information 124 includes, for example, a name, account number, a rating, and/or picture of the customer making the request 112 .
- a destination address may also be included or provided with the identification information 124 .
- the service 120 processes the request 112 in order to select candidate respondents that can provide the requested transport.
- the service 120 is able to use identification information 124 to identify an account or profile of the user.
- the account or profile of the user may include or identify (i) funds for payment for transport services, (ii) rating information that identifies a reputation or class of user of the customer 110 .
- Other information that may optionally be associated or maintained with the user account/profile includes, for example, an image of the customer, preferences of the user (e.g. type of vehicle the user prefers), the rating of the user (which may be provided by drivers that have previously interacted with), and historical information such as previous drivers that have provided transport to the user.
- Such preferences, rating information, historical information and other profile information can be used to select drivers for the user at a given instance. For example, for a given fare request, the service may first attempt to locate a driver that the user has previously used (and perhaps provided a good rating for).
- account/profile information may be stored with the user, and communicated as part of the user's request.
- Service 120 uses information contained in the customer request 112 to select candidate respondents 132 based on one or more criteria.
- the criteria may include (i) proximity of the individual candidate respondents to the customer 110 , (ii) a class or rating of the candidate respondent 132 , based on reputation and/or level/quality of service (such as provided by rating/feedback of past instances), (iii) availability of the candidate respondents 132 .
- the criteria may also include user-specified preferences, including specific identification by the user of a particular driver, or previous drivers that have serviced the user and whom have received good feedback from the user.
- an embodiment provides that the service 120 implements a pairing process upon receipt of the request 112 .
- the service 120 performs the pairing process by (i) using the one or more criteria to select a first candidate respondent; (ii) sending an invitation 114 to the first candidate, and giving the first candidate a short duration to accept the invitation; (iii) if the first candidate respondent declines or fails to accept the invitation, selecting a second candidate respondent using the one or more criteria; (iv) sending the invitation 114 to the second candidate, and giving the second candidate a short duration to accept.
- the pairing process may be repeated (n times) until a respondent 130 from the candidate pool 132 communicates back an acceptance 115 to the invitation 114 .
- another embodiment provides for selecting drivers by contacting a set of two or more drivers at once, based on criteria such as described above.
- the particular driver that ultimately is selected may correspond to, for example, the first driver in the set to respond and accept the invitation.
- the service 120 may specify, to the selected respondent 130 , information about the customer 110 that includes: (i) the reputation of the customer (e.g. the user's feedback as provided by other drivers), (ii) the expected fare of the transport for that customer (which may include determining and communicating the customer's destination), and/or (iii) the geographic location of the customer.
- the customer's picture or other identification information may also be communicated to the accepting respondent.
- the respondent 130 is able to identify the customer 110 from sight when he arrives to pickup the customer.
- the pool of respondents 132 are equipped with devices that can communicate with geo-aware mobile devices (e.g. handsets) of the customers.
- the pool of respondents 132 may include portable/mobile and personal handsets 135 , such as cellular voice/data devices with geo-aware resources that the respondents can carry with them into and out of their vehicles.
- the handsets 135 of the candidate respondents share a platform (e.g. application level) with the handsets 105 used by the customers. The shared platform enables each party to exchange communications across a shared functionality and user-interface.
- the progress communications 126 may be generated automatically, using program instructions that cause the handset to utilize its geo-aware resources to automatically generate location information of the respondent 130 as it progresses en route to the location of customer 110 .
- the progress communications 126 are communicated to the customer 110 using network communications.
- the progress communications 126 may be communicated directly from the respondent 130 to the customer 110 , or via the service 120 .
- the customer 110 and the respondent 130 are each facilitated in that identification information for each party has been communicated to the other. This identification information may include the picture of the other party.
- one or both devices can be used to perform fare monitoring functions.
- the fare monitoring functions enable the calculation of the fee that the customer will have to pay when he is driven to his desired destination.
- the fee determination is based on the distance or route travelled and/or the time that the customer 110 is in the vehicle.
- the fee determination may also be determined based on a formula or factor that is specific to a particular transport party (e.g. the transport) company or service. Stop and wait times may be calculated, either by monitoring the GPS information communicated from the metering device, or from use of accelerometers that are sometimes included in the hardware of the handset. Numerous other parameters may be used to determine the fee for the fare, as described with embodiments and variations of FIG. 3-5 .
- payment is automatic.
- the customer 110 may store or associate an online fund account with his device 105 .
- the driver or alternatively the transport party
- service 120 (or the devices as configured) can trigger transfer of out of the customer's account.
- the funds are transferred from the customer's account to an account of the service, which then transfers funds to compensate the respondent party that provided transport.
- the distribution of the funds from the customer may be distributed to the service 120 , as well as a transport party transport that can correspond to either the driver, or a business entity that provides the driver (e.g. fleet operator).
- the fee transferred from the service to the transport is based on the fee charged to the customer, but may include reductions for use of the service.
- Various payment schemes may be used to compensate the transport party, such as paying the transport party a percentage of the fare, or compensating the transport party based on various parameters that include quality of service, desirability of fare, or even hourly.
- the service can trigger at least a portion of the funds to be transferred from the customer's account directly to the transport party (e.g. fleet operator or driver).
- the fund transfer can be accomplished by moving funds from the customer's online financial account to that of the service and/or respondent 130 (e.g. a commercial account for the fleet manager or company).
- fund transfer communication 142 is directed to the respondent 130 to confirm that payment has been made.
- the fund transfer communication 142 may be made in response to the respondent/driver (and/or the customer 110 ) signaling via the respective handset that the fare is over.
- some or all of the actual funds may be distributed to an account associated with either the driver or the transport party (e.g. the entity that employs the driver).
- an embodiment enables one or both parties to provide feedback about the other.
- the customer 110 may provide a rating or feedback 144 to service 120 , to rate, for example, the customer's experience with the particular driver.
- the driver can provide a rating or feedback 146 for the customer 110 .
- the service 120 may associate profiles or accounts with each of the customer 110 and respondent 130 (or respondent party), and the rating/feedbacks 144 , 146 may affect the overall rating of the customer/respondent.
- the reputation of the customer 110 or the driver 130 may be influenced by the feedback provided by the other party.
- a service such as described by FIG. 1 can be implemented using handsets or other portable computing devices, in a manner that overlays or compliments existing dispatching/metering equipment used by conventional services for limousines and taxicabs.
- limousine drivers can carry commercially available handsets (e.g. APPLE IPHONE) that are configured to implement a system such as shown in FIG. 1 , in order to field pickup requests from customers using handsets (also configured as described above and elsewhere in the application), while at the same time using conventional fleet/taxi dispatch and metering equipment for carrying out fares that are made through conventional channels.
- APPLE IPHONE commercially available handsets
- FIG. 1 an embodiment such as described with FIG. 1 and elsewhere can provide an alternative but complimentary mechanism by which fleet drivers can be assigned fares.
- the drivers may utilize conventional meters to determine fares that are initiated through conventional channels, and use the suitably configured mobile device or service to determine the fares when providing transport via the service such as described by FIG. 1 . It is possible for different fare calculation formulas and rules to be used to determine fares with conventional meters as opposed to those determined through the use of handsets or devices (as described above).
- embodiments such as described by FIG. 1 may be implemented to utilize drivers regardless of the specific hardware or equipment implemented by fleet companies.
- embodiments such as described need not be limited by disparities in the dispatch system or equipment used amongst different fleets or transport companies that service a common geographic region. Rather, drivers from different fleet networks can be made part of the same service through use of a suitably configured commercially available handset.
- FIG. 2 illustrates a mobile computing device that can be used by either customers or respondents, in implementing a system such as described with FIG. 1 .
- mobile computing device 210 may be illustrative of the customer handset 105 (see FIG. 1 ) or the respondent handset 135 ( FIG. 1 ). Accordingly, the mobile device 210 may correspond to any one of the following: multi-functional cellular telephony/data device, wireless tablet device, netbook, laptop, or GPS computing device.
- Computing device 210 includes GPS component 204 , network resources 206 , processor 212 , and memory resources 214 .
- Other components that may be included with the computing device 210 include, for example, sensors such as accelerometer 230 .
- the network resources 206 includes one or more modules for enabling wireless connectivity.
- the wireless modules may include radios or modems, as well as software or logic for enabling network ports and interfaces through use of the radios.
- 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, including communications to service 120 (see FIG. 1 ) and/or to the other party.
- the device may transmit, for example, device identification (e.g.
- the network resources 206 includes 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).
- access points e.g. Wireless Fidelity 802.11(g) or 802.11(n)
- WiMax wireless mediums
- device 210 uses the geo-aware resources, shown in form of Global Positioning System (GPS) component 204 , as well as network resources 206 to communicate with the service 120 or the respondents 130 ( FIG. 1 ) over cellular or other roaming networks.
- the device 210 can use the processor(s) 212 and memory resources 214 execute a program (or corresponding) functionality for either a customer or driver/respondent.
- the same type of mobile computing device 210 may be used for handsets 105 of customers and respondents 130 , but the programming functionality on the handsets may vary for the respective parties.
- the processors 212 execute programming instructions 211 in order to auto-locate and transmit geo-location information to the service 120 or to the device of the other party in the transaction.
- This functionality (as provided by programming instructions 211 ) enables geo-aware communications 209 to be transmitted from the device.
- the geo-aware communications 209 may correspond to the customer's request for transport 112 ( FIG. 1 ), in which geographic information 122 is automatically included with the request 112 .
- This functionality also allows for geo-aware communications 209 from the driver respondent 130 , which automatically communicate its geographic information of the driver in progress communications 126 ( FIG. 1 ) to the customer 110 .
- the programming instructions 211 exist in the form of an application that communicates with a transport service such as described with an embodiment of FIG. 3 .
- the application may execute to utilize various resources of the device, such as the geo-aware resources or accelerometer (as described below), to generate requests that automatically include information for transport requests, such as customer identification and geographic location.
- the device 210 also includes geo-presentation resources 213 , to enable mapping or similar presentations using geographic identification information. For example, maps can be stored and/or retrieved on the device to present the position of either party at a given moment.
- the on-device GPS unit 204 may provide GPS coordinates 205 to the processor, which then uses the geo-presentation resources 213 to present ‘real-time’ maps of the user's position.
- the processor 212 may also receive GPS coordinates 215 from over a network (via the network interface 206 ) and use geo-presentation resources 213 and the received GPS coordinates 215 to present the location of the other party at a given instance.
- device 210 includes an accelerometer 230 that provides accelerometer information 232 to the processor 212 .
- the accelerometer information 232 can be used by the processor 212 to determine metering information, particularly with regard to stop or waiting time. More specifically, an embodiment provides that the processor 212 uses the GPS data 205 and the accelerometer information 232 to determine (i) position information, such as pickup and drop-off locations and route information or distance traveled, and (ii) stop/wait time.
- position information such as pickup and drop-off locations and route information or distance traveled
- stop/wait time stop/wait time.
- the processor 212 may perform the metering function to validate or confirm the fare. The driver/respondent may also use the information to determine the fare.
- FIG. 3 illustrates components for implementing a service, such as described with other embodiments.
- a transport service e.g. service 120 of ( FIG. 1 ) is implemented on server (or servers) 300 to arrange transport for customers by pairing drivers to customers.
- Server 300 may include customer interface 310 , dispatcher 320 , account interface 340 , and respondent interface 330 .
- the customer interface 310 may be used to handle customer communications 302
- respondent interface 330 is used to handle respondent communications 332 .
- the overall service provided on the server 300 includes a dispatcher (sub) component 320 which pairs a driver (or transport party) with a customer in response to a customer request.
- the server 300 also includes tracking components 360 , 370 which track (or monitor position and status) of the customer and the driver when the fare request is initiated (e.g. when the driver is en route to the customer) and when the fare is ongoing (driver is delivering customer to destination).
- a presentation component 352 , 354 may be provided to generate a graphic user interface for each of the customer and the driver prior to and after pickup.
- Payment component 380 may be included to handle automatic payment for the fare by the customer.
- dispatch component 320 implements a selection process that results in a driver being paired to a customer, who has made a request for transport.
- the customer request is generated programmatically, such as by way of the customer operating a user interface of a handset to make the request.
- customer interface 310 receives the transport request 312 from a given customer, and uses the dispatcher 320 to select a respondent for invitation 314 .
- the transport request 312 may communicate a pickup location of the customer.
- the pickup location can be included in the transport request 312 manually (e.g. the user specifies an address for the pickup operating a handset), or automatically (e.g. based on the users known position via the GPS information communicated from his handset).
- position data 311 can be procured programmatically and automatically from the customer when the service is in use, based on the GPS information of the user's device.
- Similar position data 313 may be maintained for the driver when he is available for customer pickup, as well as when he is engaged to pick up and deliver a customer to a destination location. Once the transport is initiated, the position data 311 , 313 may be used to determine a route taken, or intermediate positions between the pickup and drop-off locations.
- the dispatch component 320 responds to the transport request 312 from the customer.
- the dispatch component 320 may identify relevant parameters, such as the pickup location (or the location of the customer), as well as profile information about the customer (e.g. customer rating, customer preferences etc.).
- the dispatch component 320 may also identify the customer, and obtain profile information 353 from the profile database 350 .
- server 300 (as part of service 120 FIG. 1 ) maintains profile information about each of the participants of the service.
- the profile information may be maintained in a profile store 350 . Examples of information that may be maintained in the profile store 350 include overall rating/feedback of either party, commentary feedback (such as complaints), name or identity information, credit card information, logs of transactions (showing, for example, the average fare requested by a customer).
- the profile information 353 may be stored in a database or similar data structure, and dispatch component 320 may query 351 the database for information about the customer, based on the identity identified from the request 312 or other customer communication 302 .
- dispatch 320 includes information to identify the pickup location in the invitation 314 that is communicated to the one or more drivers.
- multiple invitations 314 may be used to progressively select a driver respondent for the customer, using criteria that includes (i) proximity of the customer to the candidate respondent, (ii) rating or class association of the driver and/or the customer, (iii) user preference for a particular driver, driver or vehicle class, or other characteristic of the driver or transport; and/or (iv) alternative business logic (e.g. driver bidding process for the fare).
- the server 300 may require use of geographic information resource (GIR) 326 that identifies, for example, proximity by distance or time of individual drivers to the requesting customer.
- GIR geographic information resource
- the geographic information may also be used to identify the geographic location of individual parties based on their communicated GPS information.
- the geographic information resource may include maps or codes that enable locating parties from their GPS coordinates, as well as information needed for calculating time/distance separating the two parties.
- the dispatch component 320 may also identify profile information 353 about the individual drivers by, for example, querying 351 the database 350 .
- dispatch component 320 sends out multiple invites 314 to multiple drivers, in response to transport request 312 communicated via customer device interface 310 (which may receive the customer communication 302 ).
- the invitations 314 may be sent in parallel (e.g. concurrently), or in series (sent to one driver, who can then accept or not, then sent to another driver).
- Each of the initially selected drivers is a candidate, selected based on parameters such as proximity, rating, preference etc.
- the candidate driver that is selected to handle the transport may communicate response 316 , via the driver device interface 330 (which receives the driver communication 332 ).
- Dispatch 320 may then communicate (i) a notification 331 that informs the customer of the driver selection (including optionally, information about the driver, such as his picture, vehicle identification, rating, and current position); and (ii) updates 333 that convey information about the position of the driver en route to the pickup location and/or estimated time of arrival.
- a notification 331 that informs the customer of the driver selection (including optionally, information about the driver, such as his picture, vehicle identification, rating, and current position); and (ii) updates 333 that convey information about the position of the driver en route to the pickup location and/or estimated time of arrival.
- position data 311 , 313 is obtained from the handsets of each of the customer and driver (via the respective device interfaces 310 , 330 ).
- a customer tracking component 360 uses the position data 311 to track the customer by position and time.
- the driver tracking could component 370 uses the position data 313 to track the driver by position and time.
- the GIR 326 can be used to place the user's position data 311 and the drivers position data 313 in context to mapping information and other geographic resources.
- the server 300 implements presentation component 352 , 354 for the customer and the driver.
- the respective customer and driver tracking components 360 , 370 communicate the position information of customer and driver to the presentation component 352 , 354 for output to the user.
- the output of the respective presentation components 352 , 354 may be a geographic output, such as one that would combine the position data 311 , 313 of each of the customer and driver with mapping information.
- the geographic output 317 , 319 is communicated to the customer and driver devices via the device interface 310 and 330 , respectively.
- both customer and driver are able to view the progress of the fare after pickup.
- the server 300 includes logic for facilitating payment between customer(s) and the relevant transport party for a particular fare.
- payment of the customers transport is performed automatically, or substantially automatically (i.e. with minimal user input, such as confirmation by the user that the fare is to be paid), in response to completion of the transport.
- the completion of the transport can be detected automatically, based on, for example, the position data 311 of the customer relative to the position data 313 of the driver. For example, if the customer leaves the transport vehicle and does not return to the vehicle after a set duration, a determination may be made that the transport has been completed. This determination may be made by, for example, customer and/or driver tracking component 360 , 370 .
- some embodiments provide that one or both parties to the transport can signify that the transport has been completed with some action, such as providing input via the handset.
- some action such as providing input via the handset.
- the customer can enter rating information for the driver, which then can be interpreted as signifying the completion of the transport.
- the payment component 380 may receive payment location parameters 381 from one or both of the customer/driver tracking components 360 , 370 .
- the location payment parameters 381 may include (i) the pickup location of the customer, (ii) the drop-off location of the customer, (iii) the route or intermediate position of the vehicle between the customer pickup and drop-off locations, and/or (iv) the duration of the transport.
- Other location payment parameters may also be used by the payment component 380 , such as whether toll fees were incurred (which can be determined from position data 311 , 313 cross-referenced with information provided by GIR 326 ), and the type of the vehicle used (e.g. can be determined by the profile information 350 of the driver).
- Other parameters may also be used, including parameters on predicted or actual market demand, vehicle availability, time of day, rating of driver, type of vehicle, and quality of service (see description provided by FIG. 4 ).
- the payment component 380 may implement one or more algorithms to determine the fare for the transport, based on the location payment parameters 381 and/or other parameters or conditions (e.g. market demand, time of day etc.). Additional descriptions of how payment algorithms can be implemented are described with FIG. 4 and FIG. 5 .
- the payment component 380 may communicate an instruct 383 to account interface 340 .
- the instruct 383 identifies the amount of the transport, the customer (or customers) that are to provide the amount, and the transport party that is to be credited for the fare.
- the account interface 340 may be used to process and transfer funds from an online account of the customer to an online account of the transport service (provided by the server 300 ).
- the transport service may utilize one or more methodologies to compensate the relevant transport party.
- the relevant transport party can correspond to a business entity (e.g. company) that operates the vehicle, or which employs the driver.
- the relevant transport party may correspond to the driver, who can, in some variations of embodiments described, receive funds from the service.
- the transport service may for example, compensate the transport party by (i) distributing a portion (e.g.
- the transport party corresponds to an entity that operates one or more vehicles (e.g. fleet), and is separate entity from the driver.
- implementations provide that the transport party is compensated with one payment (for driver or operating entity) or multiple payments (separate payments for driver and operating entity).
- the transport service may delineate a tip portion of the payment of the customer, and compensate the driver separately for the tip portion.
- account interface 340 is capable of interfacing with online transactional accounts on behalf of either the customer 310 or the transport party/respondent.
- the server 300 may maintain credit card information for customers and use that information to pay the transport party/driver.
- server 300 automatically, without approval from the customer, pays the respondent. In this way, the respondents are encouraged to accept the transport requests, in that payment for services is assured.
- the customer may have the option to tip. Whether the customer tips or not may reflect back on the customer by the respondent's rating/feedback.
- Some embodiments enable the participants of the transport service to provide feedback about one another based on their respective experiences. As mentioned elsewhere, one embodiment provides that each participant (customer and driver) can provide feedback that includes a rating or other quantative metric. Additionally, a user can provide qualitative statements, such as sentences or paragraph-formed commentary about his experience with the driver.
- a rating interface 384 , 388 may be provided for each of the customer and the driver.
- the rating interface 384 of the customer enables the customer to record feedback 385 about a driver, or more generally, about the transport party (e.g. driver or the taxi or limousine company that provided the transport).
- the rating interface 388 enables the driver to record feedback about the customer 389 .
- the rating information of each participant may be recorded as part of that user's profile information, and thus stored in the profile store 350 .
- each feedback results in a respective driver rating update 387 (provided by the customer) or customer rating update 391 (provided from the driver).
- the rating interface 384 , 388 is provided in part as a webpage or webform that the user can interact with to record information about the other participant in the transaction. Still further, the rating interface may be presented to the user upon completion of the transport, such as pushed (or accessible) to the user's handset (via web browser or app). Numerous alternatives and variations are possible in regard to enabling the participant (customer or driver) to enter rating and other feedback.
- the transport service may prompt the customer to answer a series of yes or no questions as a means of evaluating the performance of a particular driver.
- the questions may ask, for example, whether the driver was courteous, whether the driver opened the door or assisted the customer in entering the vehicle, the manner in which the driver drove the vehicle, and the driver's response time.
- the user's questionnaire feedback may be recorded for the particular driver and/or the company or operator that provided the driver.
- the rating information can have a variety of uses. Rating information can influence, for example, the ability of a customer to pick up a driver when the pool of drivers is limited. A customer's rating may be based on factors such as whether the customer provided a decent tip, and was courteous. A “good tipper” can be identified from the rating information, and when the good tipper needs transport, available drivers are more likely to accept his fare. On the driver side, the rating information associated with a driver may reflect the driver's courtesy, driving manner etc.
- the transport service 300 may prioritize (or emphasize) selection of drivers with good ratings. For example, the invite 314 may first be sent to proximate drivers with highest ratings, then proximate drivers with middle tier ratings. Still further, some embodiments provide the user with the ability to reject the driver based on, for example, the driver's rating information.
- the rating information may be used as a parameter in selecting one driver to be paired to a customer.
- customers may first be paired with drivers with similar ratings.
- a transport service such as described with FIG. 1 or FIG. 3 may collect and utilize information determined from customers and drivers for a variety of purposes.
- the location of potential customers may be determined based on location information transmitted from suitably configured customer handsets.
- service 120 FIG. 1
- the conglomeration may be identified as a social event or hot-spot in the city at the given time interval.
- This information can then be shared with other customers, or with a portion of the population that may want to know where, for example, the ‘night life’ in the city is in a given evening.
- Drivers and fleet operators including conventional transport providers who may not use handsets) may be informed of the location where customer pickups may readily be available.
- Other types of information that may be collected, disseminated or otherwise used includes (i) popular pickup locations (e.g. to assist transport providers as to locations to patrol or be near for pickups), (ii) popular destinations, (iii) estimated travel times through to a given destination, or through a particular part of a city (e.g. to estimate traffic).
- popular pickup locations e.g. to assist transport providers as to locations to patrol or be near for pickups
- popular destinations e.g. to estimate travel times through to a given destination, or through a particular part of a city (e.g. to estimate traffic).
- information pertaining to the various transports that are transacted through the transport service are recorded for a given duration of time.
- the recorded information may identify customer pickup locations, customer drop-off locations, time of transport, duration of transport, and/or routes taken.
- the recorded information is stored in a log 394 .
- the information may be recorded from, for example, dispatch 320 (identify customer pickup locations), the customer tracker 360 and driver tracker 370 (record pickup and drop-off locations, routes taken, duration), and/or the payment component 380 (record fares paid, tips paid etc.).
- An analysis component 390 may analyze information from the log 394 to identify information for users (customers and drivers) of the transport service, as well as to direct users who may research based on information recorded by the transport service.
- the analysis component 390 may provide output to users on, for example, a website.
- the information from the log includes historical and/or real-time information that is published to third-parties and/or a population.
- the publication may be in the form of communications sent directly to third-parties, such as vehicle transport providers.
- the information may be published on, for example, a website or made available to users that operate a mobile application.
- parties such as customers, the information may identify the location of transport vehicles, as well as popular spots in a given geographic region.
- the information may predict likely areas where there are likely to be fares, thus facilitating the vehicle transport services and providers in positioning vehicles and drivers to reduce response times to customer transport requests.
- web users can utilize the site to identify traffic spots or best routes by identifying routes taken by drivers of the transport service, as well as their actual transport time (versus expected or average).
- common pickup locations may be analyzed by time, date or event to facilitate taxi services in knowing where to locate themselves in their off time. Similar information can identify information relevant to other business or social settings of a city. For example, hotel occupancy can be estimated by identifying the number of drop-offs at hotels.
- Historical information may also be utilized to predict likely transport request times and locations. For example, the most common pickup times in a given region of a city at a particular time of year can be determined.
- FIG. 4 illustrates a process for programmatically transferring funds from a customer to a relevant transport party as a mechanism for compensating the transport party, according to an embodiment.
- a method such as described by FIG. 4 may be implemented using components such as described with FIG. 3 . Accordingly, reference is made to components of FIG. 3 for purpose of illustrating suitable components for performing a step or sub step being described.
- Customers may subscribe to participate in a transport service such as described with FIG. 3 .
- their participation may include (i) establishing an account with funds, and (ii) registering and/or enabling a device to utilize the service of server 300 .
- their participation may involve (i) establishing an account to receive funds, and (ii) registering and or enabling a device to utilize the service of server 300 .
- the devices used by the participants correspond to handsets that run applications (“app”) for participating in the transport service described.
- apps applications
- Other types of devices may also be used, such as laptops, tablets, computers, or other GPS enabled devices that have network connectivity. It should also be noted that embodiments contemplate use of more primitive devices, such as those that only enable cellular telephony communications and/or SMS.
- the accounts include funds that can be used for transfer to a driver.
- the customer may make payments through a specific transport service account that is managed by the transport service entity. The payments may be made, for example, in advance, periodically, or when prompted (such as by the transport service in response to the customer receiving the transport).
- the transport service (such as implemented on the server(s) 300 ) may have authority to automate transfer of funds from an account of the customer that is not under the control of the transport service (e.g. checking account, credit card account, PAYPAL account).
- the relevant transport party that is to receive compensation from the fare can, depending on the implementation and the payment methodology, correspond to (i) the fleet or vehicle operator (e.g. limousine company or entity), and/or (ii) the driver.
- the transport party may establish or associate an account to receive funds from the transport service and/or account of the customer.
- Each account may also be associated with profile information of the respective participant, including the identity of the participant.
- the transport service determines when the customer is being provided transport by driver ( 420 ). This determination may be made based on factors that include the customer requesting pickup, and a transport service selecting a particular driver. However, embodiments further recognize that not all transport requests may end up as fares. Thus, embodiments include the ability to auto detect when the customer and driver have actually initiated the transport ( 422 ). Such detection can be implemented in one of many possible ways. For example, the position of the transport providing vehicle and customer can be compared over duration of time while the two are moving, and if they are at the same position, the significance is that they are determined to be in the same vehicle. As an alternative or addition, accelerometers incorporated into the handsets of the customer and/or driver may detect linear motion, such as provided by motion of a vehicle. This information can also be used to detect a fare pickup, or to confirm as such. As an alternative or addition, customer input ( 424 ) or driver input ( 426 ) may be used to determine when the fare has started.
- one or more embodiments detect the completion of the transport ( 430 ). Similar to pick up, this determination may be made automatically ( 432 ), or by way of input from either the customer ( 434 ) or the driver ( 436 ). Automatic detection of the transport completion can be made by comparing relative position data 311 , 313 (e.g. as determined from GPS of devices) of the customer and transport vehicle, respectively. For example, if the position data 311 , 313 indicates that the customer and transport vehicle have separated in position, and a designated duration of time has passed by which the customer does not return to proximity of the transport vehicle, then a determination may be made that the fare is complete.
- relative position data 311 , 313 e.g. as determined from GPS of devices
- a wireless signal e.g. Bluetooth detection and/or pairing
- the two devices may be in very close proximity to each other (e.g. front seat and backseat of vehicle).
- the completion of the transport may correspond to such wireless signal indicating the two devices have separated.
- manual input may also be used, such as by the customer ( 434 ) or the transport party ( 436 ).
- the transport party 436
- one party may have lost battery life, in which case manual input from the other party is needed to signify end of transport.
- the location payment parameters for the fare are determined ( 440 ).
- the location payment parameters can include, but are not limited to, the customer pickup location ( 442 ), the customer drop-off location ( 444 ), route information (or intermediate positions between the pickup and drop-off locations) ( 446 ), and/or the duration of the transport ( 448 ).
- Other location parameters can include the type of vehicle used (e.g. sedan versus stretch limo), presence of tolls or other costs, and even the transport route that is used.
- the alternative parameters include market condition parameters ( 452 ).
- Market condition parameters may correspond to metrics that estimate or predict availability and demand for transport at a particular duration corresponding to when the customer requests transport.
- the demand may be based on (i) determining the pool of candidate parties or respondents that are in service in the particular duration, and (ii) determining the number of drivers that are engaged by customers at the given duration. For example, during peak hours, the number of transport providing vehicles may be a maximum. Rates for transport services may be higher or at peak than low demand hours.
- the fare value may weight or prioritize demand for transport independently. For example, when demand is at peak, rates for transport services may be higher.
- Demand can be determined from real-time information maintained by the transport serve.
- the log 394 may at a given instance identify the number of available vehicles, and the number of transports that are engaged or in service.
- the demand may be predicted from historical analysis, such as estimations of demand during particular hours of weekdays, weekends, or holidays.
- Desirability parameters may be used to determine the fare value ( 454 ). Desirability parameters may correspond to the type of vehicle or transport provided. For example, the luxury limousines may result in a higher fare value than non-luxury sedans. The desirability of the transport may also include parameter such as whether ride sharing is permitted, whether on-board entertainment or amenities or provided etc. Desirability parameters may also correspond to rating parameters of the transporting party (either the company or driver). Such rating parameters may designate higher ratings for transport providing parties (or drivers) that have higher ratings. The fare value may also be affected by the customer rating. For example, customers may have higher ratings or class designations (e.g. VIPs), and with such designation, the fare for that customer may be reduced.
- VIPs class designations
- some embodiments may base the fare value on transport evaluation parameters.
- the transport service may evaluate the quality and kind of the transport that the customer received from the driver. The evaluation may be based on criteria such as (i) the response time of the driver to arrive at the pickup location, (ii) the transport time, (iii) whether the driver elected the fastest or best route to the drop-off location. Other considerations include whether amenities were provided to the customer (or whether the customer actual used the amenities), as well as feedback by the customer as to specifics of the transport (e.g. the driver was courteous, opened the door, the car was clean, the driver obeyed driving laws etc.).
- Other parameters may also be used to determine the fare value.
- Such other parameters may include bids that the transport service receives from the transport providing parties for fares at select locations, times or for particular drivers or vehicles.
- the fare for the transport is calculated and transferred from customer to driver ( 460 ).
- the fare is calculated and accessed from the customer account, in response to a determination that the transport is complete.
- the transfer of the fare may be performed substantially automatically, such as by way of prompting the customer and/or driver to perform some action or otherwise provide confirmation upon determining that the transport has been completed.
- the transport service collects the funds and distributes funds to the pertinent transport parties periodically, or responsively, after one or more fares are collected.
- the sum total of the fares that are distributed to the transport party may represent a portion of the total received.
- the funds (or portion thereof) collected from the customer can be transferred directly to the transport party.
- the transport party may correspond to the operator or company that provides the drivers.
- the drivers may be compensated by separate arrangements with the operator or company that provides the transport (e.g. their employers).
- some funds may be distributed from the transport service to the drivers separate from the companies that employ the drivers (e.g. the tip portion). Numerous variations are possible for distributing funds collected from customers, depending on considerations for distributing collected funds from the customer.
- the parameters used to determine the fare value may include numerous variations.
- the fare value may be based on the route of the transport, as defined by the customer pickup location, the customer drop-off location and intermediate points there between.
- the general geographic locality where the transport service operates e.g. a city
- the fare value from one fenced region to another may be pre-determined.
- only the pickup and drop-off locations may be used to determine the fare value.
- other parameters set by market conditions, desirability of other parameters may influence the fare value (e.g. adjust it up or down), or even provide the primary factor for determining the fare value.
- FIG. 5 illustrates a process for enabling fee splitting amongst multiple customers that share a transport, according to one or more embodiments.
- fee splitting in transport situations e.g. limos, taxis
- the time it takes for customers to work out a fee arrangement is inefficient.
- conventional approaches have an underlining assumption that parties sharing rides know one another, and thus are comfortable discussing fee arrangement.
- an embodiment of FIG. 5 enables transport to be arranged for multiple parties in a manner previously described by other embodiments.
- the transport service can be used to determine the fee portion of each party sharing the transport, and further prompt or automate the transfer of funds from each party without requiring the individuals to agree or discuss the arrangement.
- the fee payment arrangement can be implemented with minimal involvement from the parties. It is also easier for a transport party to provide a vehicle to pickup more than one party for transport, even if the parties are not acquaintances, as the fee splitting is not an issue that needs to be resolved by the individuals.
- the transport service determines that a particular transport is shared by more than one customer ( 510 ).
- the determination can be made in various ways.
- the transport service can be configured to detect when individuals that are participants of the service enter a vehicle that is also operating under the service. For example, such individuals may have handsets that each runs an application which communicates with the server 300 . The presence of each individual in the same vehicle may be determined in a manner described with, for example, FIG. 4 (e.g. see 410 ). When multiple individuals are in one of the transport vehicles, the transport service may assume the fee splitting arrangement is to take place.
- the assumption may be a parameter that is weighted against other parameters, such as whether the individuals entered the vehicle at the same time, whether they have shared rides in the past or whether they are dropped off at the same location.
- the fee splitting may be implemented after individuals in the transport perform a designated action. This designated action can correspond to the individuals responding to a prompt delivered to their respective handsets.
- the users may “bump” devices. Bumping can trigger an accelerometer to register the event, and the event can signify some action like fee splitting. Numerous actions can be performed to enable the transport service to infer fee splitting is in place.
- the payment parameters for the fare of each customer can be determined ( 520 ).
- the payment parameters may be customer-specific ( 524 ) and/or collective ( 528 ) for the fare, depending on the algorithm that is implemented.
- Customer-specific payment parameters include (i) pickup-location of each customer (if different), (ii) drop-off location of each customer (if different), and/or (iii) ride duration of each customer between their respective pickup and drop-off locations.
- Collective ride parameters include the starting point (first pickup) of the transport and the finishing point (the last drop-off), as well as the total distance and/or time of the transport from start to finish.
- the portion of the fee is calculated for each customer based on the determined payment parameters ( 530 ).
- the particular payment parameters, weighting and/or other factors used in determining the proportioning amongst the customers can be a matter of implementation.
- the fare portion attributable to each customer is then withdrawn from each user's associated online account and transferred to an account of the transport service, or the transport party (depending on the implementation).
- the payment transfer may be performed automatically, substantially automatically (e.g. prompt user to confirm payment) or manually.
- the user may have to pay cash or by credit.
- FIG. 6 illustrates a method for processing data determined from monitoring transport amongst parties located at different locations, according to one or more embodiments.
- a method such as described by FIG. 6 may be implemented using components such as described with FIG. 3 . Accordingly, reference is made to components of FIG. 3 for purpose of illustrating suitable components for performing a step or sub step being described.
- Embodiments recognize that utilizing mobile devices with geo-aware resources and communicative capabilities to arrange transports enable significant data collection and usages.
- a transport service such as described with FIG. 3 may arrange transport for multiple vehicle transport services, such as different limousine operates in a designated city. In doing so, instances of customer pickups and drop-offs may be recorded, including recording the pickup locations ( 610 ) and drop-offs ( 620 ).
- the information may be recorded in the log 394 . In some embodiments, the information may be recorded in real-time, although the information may stored for use as historical data.
- Other information may also be recorded from, for example, by monitoring vehicles available for transport, and/or transports in progress ( 630 ). For example, the location of available vehicles may be determined, as well as the duration of transport between locations.
- the recorded information is processed ( 640 ).
- the information current information at a given instance is extracted from the log and processed in accordance with a particular application.
- One applications includes presenting geographic information about popular customer pickup and/or drop-off locations. For example, a map may be generated that identifies the location of or popular recent customer pickups, recent or popular customer drop-offs, current location of available transport vehicles, predicted response times, and predicted areas of traffic congestion.
- historical information from the log 394 may be used to predict demands for transport during given time spans (e.g. weeknights, weekends, between 2-4 pm on Thursdays etc.).
- the historical information may include customer pickup locations, pickup times, customer drop-off locations and/or drop-off times. This information may be processed to determine predicted demands for transport at given locations and times.
- the processed information is then communicated or published to third-parties ( 650 ).
- the transport service may publish the processed information on, for example, a website that is available to customers and transport provides.
- the information may be published through applications that execute on user devices.
- the information may be generated in the form of reports that are emailed or otherwise communicated to parties (e.g. transport providing parties) directly. Numerous other variations are possible.
- FIG. 7A through FIG. 7F illustrate examples of a series of user-interfaces that are displayed to the customer from the time he requests transport to the time he arrives at his destination.
- a system such as described with FIG. 1 and/or FIG. 3 may be implemented on handsets operated by customers and respondents. The customer may operate a program on the handset to select transport.
- FIG. 7A shows a presentation and interface, depicting an embodiment in which the customer is shown his location and a soft button or icon (any mechanical or programmatic input may be used) to initiate the transport request.
- the presentation and interface may be generated on the customer device by an application, such as mobile app that is configured to communicate with a transport service.
- the presentation and interface may be made through, for example, a browser of the device, which connects to a specific website or network location to generate the presentation (or execute an application for generating the interface).
- an embodiment provides that the customer need only trigger the soft-feature (or other input mechanism).
- the application or programming
- the application automatically determines the information that is to be provided with the request, such as the location of the customer (as determined from the GPS resources of the device), the identity of the customer (as stored for use with the application), and other information (e.g. such as picture of the customer).
- the customer does not need to enter the address, but can compose and send the request for transport, along with information to identify the geographic location of the customer, with a simple soft-press or icon selection.
- FIG. 7B through FIG. 7D progress panels are displayed to the customer.
- the progress panel informs the customer that a driver is being selected (e.g. by process such as described with an embodiment of FIG. 1 ).
- a feature 712 is provided to enable the customer to cancel the pickup.
- FIG. 7C shows the geographic location 722 and estimated time of arrival 724 of the driver. The panel may be updated as the driver makes its way to the customer, to show how the driver is progressing towards the customer.
- FIG. 7D information about the selected driver/respondent is shown to the user. This may include an image 732 of the driver's face, as well as the rating information 734 associated with the driver.
- FIG. 7E shows an interface for when the trip is in progress (after-pickup).
- the location of the vehicle in transit may be shown on a map.
- the customer is provided an interface that includes (i) a feature 742 displaying the fare price (see e.g. FIG. 4 and FIG. 5 ), and (ii) an input interface 744 to rate the driver.
- FIG. 8A through FIG. 8F illustrate examples of a series of user-interfaces that are displayed to the driver/respondent, from the time the request for transport is made from the customer.
- the transport request is received by the respondent.
- Information contained when the driver receives/accepts the transport request include (i) identification of the customer 802 , (ii) rating information associated with the customer 804 , and (iii) location of the customer 806 (which can be displayed as a map).
- the driver/respondent is provided the interface to start the monitoring function of his handset.
- the driver/respondent is able to operate a soft button 812 to trigger when to start monitoring and when it is to finish.
- FIG. 8F when the fare is finished, the fare amount 822 is displayed to the driver and confirmation may be provided as to the fare amount. The driver is also given the opportunity to provide rating/feedback 832 of the customer.
Abstract
Description
- This application claims benefit of priority to Provisional U.S. Patent Application No. 61/266,996, filed Dec. 4, 2009; the aforementioned application being incorporated by reference in its entirety.
- Embodiments described herein pertain generally to a system and method for arranging transport amongst parties through use of mobile devices that are carried by the respective parties.
- Current fleet management systems employed for taxi and limousine fleet 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.
-
FIG. 1 illustrates a system for enabling transport to be arranged between parties that are at different geographic locations, according to one or more embodiments. -
FIG. 2 illustrates a mobile computing device that can be used by either customers or respondents, in implementing a system such as described withFIG. 1 . -
FIG. 3 illustrates components for implementing a service, such as described with other embodiments. -
FIG. 4 illustrates a process for programmatically transferring funds from a customer to a relevant transport party as a mechanism for compensating the transport party, according to an embodiment. -
FIG. 5 illustrates a process for enabling fee splitting amongst multiple customers that share a transport, according to one or more embodiments. -
FIG. 6 illustrates a method for processing data determined from monitoring transport amongst parties located at different locations, according to one or more embodiments. -
FIG. 7A throughFIG. 7F illustrate examples of a series of user-interfaces that are displayed to a customer as transportation is requested and provided, according to an embodiment. -
FIG. 8A throughFIG. 8F illustrate examples of a series of user-interfaces that are displayed to the driver/respondent when accepting and providing transport to a customer, according to an embodiment. - A system and method are described for enabling transportation to be arranged for individuals carrying mobile devices (e.g. handsets). In some embodiments, a customer can transmit a request for transport from a given customer geographic location. A service may handle the request by selecting a party to provide transport to the customer. According to some embodiments, the pairing of the party to the customer requesting the transport is performed programmatically and/or automatically, based on parameters such as the location of the driver (or a vehicle of the transport party).
- Some embodiments provide that a location of the customer is communicated to a service and/or driver using programmatic resources of the customer's handset.
- According to embodiments, individual drivers may be selected as respondents to a customer request, whom in turn have the option to accept the assignment. Once a driver (or alternatively, transport party) is selected and has accepted the assignment, information about the driver (e.g. the location of the driver when the fare was accepted, a picture of the driver, his rating etc.) may be communicated to a device of the customer (e.g. to the customer's handset). The driver may also be provided information about the customer (e.g. the picture of the customer, the customer's rating, the customer's precise location).
- Additionally, some embodiments provide that the customer is provided updates as to the location of the vehicle of the driver en route to the customer. The updates may be provided in real-time or near-real time, to reflect the progression of the driver towards the customer.
- Among other benefits, embodiments recognize that transport services often have vehicles that have down-time because they are between fares. In particular, limousine (or black cabs) spend much of their operational time being idle, as conventional dispatching services for such drivers often significantly underutilize the individual drivers. In contrast to conventional approaches, embodiments provided herein enable the operators of the vehicles to field transport requests from, for example, their handsets. The handsets (or other mobile devices) may correspond to, for example, (i) cellular telephony or data devices (e.g. APPLE IPHONE) that run a program that is part of a transport platform, and/or (ii) roaming devices that can connect to access points (e.g. hot spot) or operate under other wireless networks (e.g. WiMax). When the drivers/respondents are free (e.g. between fares), they can operate the program on their devices to field transport requests. Customers may run a program of the same platform on similar handsets or devices, in order to make requests for transport from their respective location. A service (such as provided online, through use of a server) may select a respondent/driver (or transport), and perform some intermediary functions (such as make payment). Various parts of the transport transaction, in which a customer is picked up and transported to a desired location, are handled programmatically, through computing resources of the platform. As explained in more detail, embodiments employ such programmatic components in order to facilitate the ability of customers to request transport, as well as to facilitate transport providing parties and customers to meet at the pickup site and to conduct their business.
- Among other features, at least some embodiments provide that the geographic location of the respective parties is determined programmatically using geo-aware resources. This information is communicated to the other party without need for manual involvement by the party operating the handset. Thus, for example, when the customer makes the request for transport, his location at the time of making the request can automatically be included in the request. Further, when the respondent/driver accepts the fare and starts to travel to the customer, his location and other relevant information (such as continuously updated estimated time of arrival) can be automatically communicated to the customer.
- According to some embodiments, the fare for the transport is determined automatically, using a program platform that is shared by the devices of both customer and driver. Moreover, the customer's funds may be automatically accessed and transferred to the driver/respondent. Thus, the driver is provided an incentive in participating in the platform, by being assured that funds for services will be received.
- Still further, embodiments provide that each party is able to provide a rating or feedback of the other party for the transaction. Thus, if either party has a particularly good or bad experience with the other party, they can record a rating that affects the reputation of the other party in using the service. In this way, both parties can be motivated to perform and behave well, thereby increasing the quality of the experience to both customer and driver.
- Still further, embodiments enable a system such as described to be implemented using commercially available handsets and devices. Examples of devices that may be operated by customers or respondents (e.g. drivers) include multifunctional cellular telephony devices (e.g. APPLE IPHONE, devices that operate the Android operating system), and wireless network enabled devices such as laptops, netbooks or tables (e.g. iPAD). As such, specialized devices or components are not needed. Customer's who wish to use a transport service such as described need to only download or otherwise run a program on a suitable handset. Likewise, drivers who wish to participate need only to run a corresponding program on a similar handset.
- 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 means through the use of code, or computer-executable instructions. A programmatically performed step may or may not be automatic.
- One or more embodiments described herein may be implemented using programmatic modules or components. A programmatic module or component may include a program, a subroutine, 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.
- 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 many cell phones and personal digital assistants (PDAs)), 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.
-
FIG. 1 illustrates a system for enabling transport to be arranged between parties that are at different geographic locations, according to some embodiments. In an embodiment, a customer 110 (also referred as to a customer) is able to make a request to receive metered automobile transport services using a computing device. Atransport service 120 locates a respondent 130 (also referred to as ‘respondent’ or ‘driver’) from a pool of possible respondents, in order to drive the customer 110 to a desired destination. - According to some embodiments, the customer 110 operates a
handset 105 to generate a request fortransport 112. As described inFIG. 2 , thehandset 105 may include roaming network capabilities (e.g. network interface for cellular network, Wireless Fidelity 802.11 (a), (g) (n), or WiMax etc.), along with geo-aware resources (e.g. GPS). The network functionality enables thehandset 105 to transmitrequest 112 and communicate further withservice 120 orrespondents 130. The geo-aware resources enable the handset to automatically includegeographic identification information 124 that identifies the geographic location of the customer 110 when making therequest 112. Thehandset 105 may also be configured to include identification information that identifies the customer 110 to either theservice 120 or to therespondent 130. Theidentification information 124 includes, for example, a name, account number, a rating, and/or picture of the customer making therequest 112. A destination address may also be included or provided with theidentification information 124. - According to an embodiment, the
service 120 processes therequest 112 in order to select candidate respondents that can provide the requested transport. Theservice 120 is able to useidentification information 124 to identify an account or profile of the user. The account or profile of the user may include or identify (i) funds for payment for transport services, (ii) rating information that identifies a reputation or class of user of the customer 110. Other information that may optionally be associated or maintained with the user account/profile includes, for example, an image of the customer, preferences of the user (e.g. type of vehicle the user prefers), the rating of the user (which may be provided by drivers that have previously interacted with), and historical information such as previous drivers that have provided transport to the user. Such preferences, rating information, historical information and other profile information can be used to select drivers for the user at a given instance. For example, for a given fare request, the service may first attempt to locate a driver that the user has previously used (and perhaps provided a good rating for). - As an alternative or addition, some or all of the account/profile information may be stored with the user, and communicated as part of the user's request.
-
Service 120 uses information contained in thecustomer request 112 to selectcandidate respondents 132 based on one or more criteria. The criteria may include (i) proximity of the individual candidate respondents to the customer 110, (ii) a class or rating of thecandidate respondent 132, based on reputation and/or level/quality of service (such as provided by rating/feedback of past instances), (iii) availability of thecandidate respondents 132. As mentioned, the criteria may also include user-specified preferences, including specific identification by the user of a particular driver, or previous drivers that have serviced the user and whom have received good feedback from the user. In order to arrange transport to the customer, an embodiment provides that theservice 120 implements a pairing process upon receipt of therequest 112. Theservice 120 performs the pairing process by (i) using the one or more criteria to select a first candidate respondent; (ii) sending aninvitation 114 to the first candidate, and giving the first candidate a short duration to accept the invitation; (iii) if the first candidate respondent declines or fails to accept the invitation, selecting a second candidate respondent using the one or more criteria; (iv) sending theinvitation 114 to the second candidate, and giving the second candidate a short duration to accept. The pairing process may be repeated (n times) until a respondent 130 from thecandidate pool 132 communicates back anacceptance 115 to theinvitation 114. - As an alternative to a single pairing process, another embodiment provides for selecting drivers by contacting a set of two or more drivers at once, based on criteria such as described above. The particular driver that ultimately is selected may correspond to, for example, the first driver in the set to respond and accept the invitation.
- Either as part of the
invitation 114, or in a follow on communication (followingacceptance 115 of the invitation), theservice 120 may specify, to the selectedrespondent 130, information about the customer 110 that includes: (i) the reputation of the customer (e.g. the user's feedback as provided by other drivers), (ii) the expected fare of the transport for that customer (which may include determining and communicating the customer's destination), and/or (iii) the geographic location of the customer. The customer's picture or other identification information may also be communicated to the accepting respondent. Thus, for example, therespondent 130 is able to identify the customer 110 from sight when he arrives to pickup the customer. - According to embodiments, the pool of
respondents 132 are equipped with devices that can communicate with geo-aware mobile devices (e.g. handsets) of the customers. In particular, the pool ofrespondents 132 may include portable/mobile andpersonal handsets 135, such as cellular voice/data devices with geo-aware resources that the respondents can carry with them into and out of their vehicles. In one embodiment, thehandsets 135 of the candidate respondents share a platform (e.g. application level) with thehandsets 105 used by the customers. The shared platform enables each party to exchange communications across a shared functionality and user-interface. - Once the respondent 130 starts traveling to the customer 110, a series of
progress communication 126 are communicated to the customer 110. Theprogress communications 126 may be generated automatically, using program instructions that cause the handset to utilize its geo-aware resources to automatically generate location information of the respondent 130 as it progresses en route to the location of customer 110. Theprogress communications 126 are communicated to the customer 110 using network communications. Theprogress communications 126 may be communicated directly from the respondent 130 to the customer 110, or via theservice 120. On pickup, the customer 110 and the respondent 130 are each facilitated in that identification information for each party has been communicated to the other. This identification information may include the picture of the other party. - According to an embodiment, once the respondent 130 picks up the customer 110, one or both devices can be used to perform fare monitoring functions. The fare monitoring functions enable the calculation of the fee that the customer will have to pay when he is driven to his desired destination. In an embodiment, the fee determination is based on the distance or route travelled and/or the time that the customer 110 is in the vehicle. The fee determination may also be determined based on a formula or factor that is specific to a particular transport party (e.g. the transport) company or service. Stop and wait times may be calculated, either by monitoring the GPS information communicated from the metering device, or from use of accelerometers that are sometimes included in the hardware of the handset. Numerous other parameters may be used to determine the fee for the fare, as described with embodiments and variations of
FIG. 3-5 . - In an embodiment, payment is automatic. The customer 110 may store or associate an online fund account with his
device 105. Likewise, the driver (or alternatively the transport party) has an associated account for receiving funds. Once the customer 110 is driven to his desired destination, service 120 (or the devices as configured) can trigger transfer of out of the customer's account. In one embodiment, the funds are transferred from the customer's account to an account of the service, which then transfers funds to compensate the respondent party that provided transport. The distribution of the funds from the customer may be distributed to theservice 120, as well as a transport party transport that can correspond to either the driver, or a business entity that provides the driver (e.g. fleet operator). The fee transferred from the service to the transport is based on the fee charged to the customer, but may include reductions for use of the service. Various payment schemes may be used to compensate the transport party, such as paying the transport party a percentage of the fare, or compensating the transport party based on various parameters that include quality of service, desirability of fare, or even hourly. As a variation or alternative, the service can trigger at least a portion of the funds to be transferred from the customer's account directly to the transport party (e.g. fleet operator or driver). Thus, the fund transfer can be accomplished by moving funds from the customer's online financial account to that of the service and/or respondent 130 (e.g. a commercial account for the fleet manager or company). In an embodiment,fund transfer communication 142 is directed to the respondent 130 to confirm that payment has been made. Thefund transfer communication 142 may be made in response to the respondent/driver (and/or the customer 110) signaling via the respective handset that the fare is over. As mentioned with other embodiments, some or all of the actual funds may be distributed to an account associated with either the driver or the transport party (e.g. the entity that employs the driver). - After the customer 110 is driven to the desired destination, an embodiment enables one or both parties to provide feedback about the other. The customer 110 may provide a rating or
feedback 144 toservice 120, to rate, for example, the customer's experience with the particular driver. Likewise, the driver can provide a rating orfeedback 146 for the customer 110. Theservice 120 may associate profiles or accounts with each of the customer 110 and respondent 130 (or respondent party), and the rating/feedbacks driver 130 may be influenced by the feedback provided by the other party. - According to some embodiments, a service such as described by
FIG. 1 can be implemented using handsets or other portable computing devices, in a manner that overlays or compliments existing dispatching/metering equipment used by conventional services for limousines and taxicabs. For example, limousine drivers can carry commercially available handsets (e.g. APPLE IPHONE) that are configured to implement a system such as shown inFIG. 1 , in order to field pickup requests from customers using handsets (also configured as described above and elsewhere in the application), while at the same time using conventional fleet/taxi dispatch and metering equipment for carrying out fares that are made through conventional channels. Thus, an embodiment such as described withFIG. 1 and elsewhere can provide an alternative but complimentary mechanism by which fleet drivers can be assigned fares. In some embodiments, the drivers may utilize conventional meters to determine fares that are initiated through conventional channels, and use the suitably configured mobile device or service to determine the fares when providing transport via the service such as described byFIG. 1 . It is possible for different fare calculation formulas and rules to be used to determine fares with conventional meters as opposed to those determined through the use of handsets or devices (as described above). - Moreover, embodiments such as described by
FIG. 1 may be implemented to utilize drivers regardless of the specific hardware or equipment implemented by fleet companies. Thus, embodiments such as described need not be limited by disparities in the dispatch system or equipment used amongst different fleets or transport companies that service a common geographic region. Rather, drivers from different fleet networks can be made part of the same service through use of a suitably configured commercially available handset. -
FIG. 2 illustrates a mobile computing device that can be used by either customers or respondents, in implementing a system such as described withFIG. 1 . Accordingly,mobile computing device 210 may be illustrative of the customer handset 105 (seeFIG. 1 ) or the respondent handset 135 (FIG. 1 ). Accordingly, themobile device 210 may correspond to any one of the following: multi-functional cellular telephony/data device, wireless tablet device, netbook, laptop, or GPS computing device. -
Computing device 210 includesGPS component 204,network resources 206,processor 212, andmemory resources 214. Other components that may be included with thecomputing device 210 include, for example, sensors such asaccelerometer 230. In one implementation, thenetwork resources 206 includes one or more modules for enabling wireless connectivity. The wireless modules may include radios or modems, as well as software or logic for enabling network ports and interfaces through use of the radios. 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, including communications to service 120 (seeFIG. 1 ) and/or to the other party. In implementing one or more embodiments, the device may transmit, for example, device identification (e.g. cellular number) and geo-aware communications (as described below). As an alternative or variation, thenetwork resources 206 includes 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). - In an embodiment,
device 210 uses the geo-aware resources, shown in form of Global Positioning System (GPS)component 204, as well asnetwork resources 206 to communicate with theservice 120 or the respondents 130 (FIG. 1 ) over cellular or other roaming networks. Thedevice 210 can use the processor(s) 212 andmemory resources 214 execute a program (or corresponding) functionality for either a customer or driver/respondent. In some embodiments, the same type ofmobile computing device 210 may be used forhandsets 105 of customers andrespondents 130, but the programming functionality on the handsets may vary for the respective parties. - In one embodiment, the
processors 212 executeprogramming instructions 211 in order to auto-locate and transmit geo-location information to theservice 120 or to the device of the other party in the transaction. This functionality (as provided by programming instructions 211) enables geo-aware communications 209 to be transmitted from the device. The geo-aware communications 209 may correspond to the customer's request for transport 112 (FIG. 1 ), in whichgeographic information 122 is automatically included with therequest 112. This functionality also allows for geo-aware communications 209 from thedriver respondent 130, which automatically communicate its geographic information of the driver in progress communications 126 (FIG. 1 ) to the customer 110. In some embodiments, theprogramming instructions 211 exist in the form of an application that communicates with a transport service such as described with an embodiment ofFIG. 3 . The application may execute to utilize various resources of the device, such as the geo-aware resources or accelerometer (as described below), to generate requests that automatically include information for transport requests, such as customer identification and geographic location. - The
device 210 also includes geo-presentation resources 213, to enable mapping or similar presentations using geographic identification information. For example, maps can be stored and/or retrieved on the device to present the position of either party at a given moment. The on-device GPS unit 204 may provide GPS coordinates 205 to the processor, which then uses the geo-presentation resources 213 to present ‘real-time’ maps of the user's position. Theprocessor 212 may also receive GPS coordinates 215 from over a network (via the network interface 206) and use geo-presentation resources 213 and the received GPS coordinates 215 to present the location of the other party at a given instance. - According to an embodiment,
device 210 includes anaccelerometer 230 that providesaccelerometer information 232 to theprocessor 212. Theaccelerometer information 232 can be used by theprocessor 212 to determine metering information, particularly with regard to stop or waiting time. More specifically, an embodiment provides that theprocessor 212 uses theGPS data 205 and theaccelerometer information 232 to determine (i) position information, such as pickup and drop-off locations and route information or distance traveled, and (ii) stop/wait time. When used by the customer, theprocessor 212 may perform the metering function to validate or confirm the fare. The driver/respondent may also use the information to determine the fare. -
FIG. 3 illustrates components for implementing a service, such as described with other embodiments. In an embodiment, a transport service (e.g. service 120 of (FIG. 1 ) is implemented on server (or servers) 300 to arrange transport for customers by pairing drivers to customers.Server 300 may include customer interface 310,dispatcher 320, account interface 340, andrespondent interface 330. The customer interface 310 may be used to handlecustomer communications 302, whilerespondent interface 330 is used to handlerespondent communications 332. The overall service provided on theserver 300 includes a dispatcher (sub)component 320 which pairs a driver (or transport party) with a customer in response to a customer request. Theserver 300 also includes trackingcomponents presentation component Payment component 380 may be included to handle automatic payment for the fare by the customer. These components are described in greater detail below. - Dispatch, Driver Selection and Pickup
- According to embodiments,
dispatch component 320 implements a selection process that results in a driver being paired to a customer, who has made a request for transport. In an embodiment such as shown, the customer request is generated programmatically, such as by way of the customer operating a user interface of a handset to make the request. - On the
server 300, customer interface 310 receives thetransport request 312 from a given customer, and uses thedispatcher 320 to select a respondent forinvitation 314. Thetransport request 312 may communicate a pickup location of the customer. The pickup location can be included in thetransport request 312 manually (e.g. the user specifies an address for the pickup operating a handset), or automatically (e.g. based on the users known position via the GPS information communicated from his handset). As discussed below,position data 311 can be procured programmatically and automatically from the customer when the service is in use, based on the GPS information of the user's device.Similar position data 313 may be maintained for the driver when he is available for customer pickup, as well as when he is engaged to pick up and deliver a customer to a destination location. Once the transport is initiated, theposition data - The
dispatch component 320 responds to thetransport request 312 from the customer. In responding, thedispatch component 320 may identify relevant parameters, such as the pickup location (or the location of the customer), as well as profile information about the customer (e.g. customer rating, customer preferences etc.). In response to receiving therequest 312, thedispatch component 320 may also identify the customer, and obtainprofile information 353 from theprofile database 350. More specifically, as mentioned in some embodiments, server 300 (as part ofservice 120FIG. 1 ) maintains profile information about each of the participants of the service. The profile information may be maintained in aprofile store 350. Examples of information that may be maintained in theprofile store 350 include overall rating/feedback of either party, commentary feedback (such as complaints), name or identity information, credit card information, logs of transactions (showing, for example, the average fare requested by a customer). - Thus, the
profile information 353 may be stored in a database or similar data structure, anddispatch component 320 may query 351 the database for information about the customer, based on the identity identified from therequest 312 orother customer communication 302. - In selecting the driver for a given customer, dispatch 320 includes information to identify the pickup location in the
invitation 314 that is communicated to the one or more drivers. As discussed previously,multiple invitations 314 may be used to progressively select a driver respondent for the customer, using criteria that includes (i) proximity of the customer to the candidate respondent, (ii) rating or class association of the driver and/or the customer, (iii) user preference for a particular driver, driver or vehicle class, or other characteristic of the driver or transport; and/or (iv) alternative business logic (e.g. driver bidding process for the fare). In order to handle transport requests and make invitations, theserver 300 may require use of geographic information resource (GIR) 326 that identifies, for example, proximity by distance or time of individual drivers to the requesting customer. The geographic information may also be used to identify the geographic location of individual parties based on their communicated GPS information. The geographic information resource may include maps or codes that enable locating parties from their GPS coordinates, as well as information needed for calculating time/distance separating the two parties. Thedispatch component 320 may also identifyprofile information 353 about the individual drivers by, for example, querying 351 thedatabase 350. - In one embodiment,
dispatch component 320 sends outmultiple invites 314 to multiple drivers, in response totransport request 312 communicated via customer device interface 310 (which may receive the customer communication 302). Theinvitations 314 may be sent in parallel (e.g. concurrently), or in series (sent to one driver, who can then accept or not, then sent to another driver). Each of the initially selected drivers is a candidate, selected based on parameters such as proximity, rating, preference etc. The candidate driver that is selected to handle the transport may communicateresponse 316, via the driver device interface 330 (which receives the driver communication 332).Dispatch 320 may then communicate (i) anotification 331 that informs the customer of the driver selection (including optionally, information about the driver, such as his picture, vehicle identification, rating, and current position); and (ii) updates 333 that convey information about the position of the driver en route to the pickup location and/or estimated time of arrival. - Customer Pickup
- According to embodiments, once the customer is picked up,
position data customer tracking component 360 uses theposition data 311 to track the customer by position and time. Similarly, the driver tracking couldcomponent 370 uses theposition data 313 to track the driver by position and time. TheGIR 326 can be used to place the user'sposition data 311 and the drivers positiondata 313 in context to mapping information and other geographic resources. Theserver 300 implementspresentation component driver tracking components presentation component respective presentation components position data geographic output device interface 310 and 330, respectively. Thus, under one implementation, both customer and driver are able to view the progress of the fare after pickup. - Payment
- The
server 300 includes logic for facilitating payment between customer(s) and the relevant transport party for a particular fare. According to some embodiments, payment of the customers transport is performed automatically, or substantially automatically (i.e. with minimal user input, such as confirmation by the user that the fare is to be paid), in response to completion of the transport. Still further, some embodiments provide that the completion of the transport can be detected automatically, based on, for example, theposition data 311 of the customer relative to theposition data 313 of the driver. For example, if the customer leaves the transport vehicle and does not return to the vehicle after a set duration, a determination may be made that the transport has been completed. This determination may be made by, for example, customer and/ordriver tracking component - As an alternative or addition, some embodiments provide that one or both parties to the transport can signify that the transport has been completed with some action, such as providing input via the handset. As another example, the customer can enter rating information for the driver, which then can be interpreted as signifying the completion of the transport.
- The
payment component 380 may receivepayment location parameters 381 from one or both of the customer/driver tracking components location payment parameters 381 may include (i) the pickup location of the customer, (ii) the drop-off location of the customer, (iii) the route or intermediate position of the vehicle between the customer pickup and drop-off locations, and/or (iv) the duration of the transport. Other location payment parameters may also be used by thepayment component 380, such as whether toll fees were incurred (which can be determined fromposition data profile information 350 of the driver). Other parameters may also be used, including parameters on predicted or actual market demand, vehicle availability, time of day, rating of driver, type of vehicle, and quality of service (see description provided byFIG. 4 ). - The
payment component 380 may implement one or more algorithms to determine the fare for the transport, based on thelocation payment parameters 381 and/or other parameters or conditions (e.g. market demand, time of day etc.). Additional descriptions of how payment algorithms can be implemented are described withFIG. 4 andFIG. 5 . - Once the fare for the transport is determined, the
payment component 380 may communicate an instruct 383 to account interface 340. The instruct 383 identifies the amount of the transport, the customer (or customers) that are to provide the amount, and the transport party that is to be credited for the fare. - In one implementation, the account interface 340 may be used to process and transfer funds from an online account of the customer to an online account of the transport service (provided by the server 300). In turn, the transport service may utilize one or more methodologies to compensate the relevant transport party. The relevant transport party can correspond to a business entity (e.g. company) that operates the vehicle, or which employs the driver. Alternatively, the relevant transport party may correspond to the driver, who can, in some variations of embodiments described, receive funds from the service. The transport service, may for example, compensate the transport party by (i) distributing a portion (e.g. 50%) of the compensation to the transport party; (ii) pooling funds from multiple transports of the transport party, then transferring the funds (which can represent a portion of the total funds received) to the transport party; (ii) compensating the transport party based on an alternative metric such as flat fee or hourly rate. Embodiments further recognize that many situations, the transport party corresponds to an entity that operates one or more vehicles (e.g. fleet), and is separate entity from the driver. In such embodiments, implementations provide that the transport party is compensated with one payment (for driver or operating entity) or multiple payments (separate payments for driver and operating entity). In still another variation, the transport service may delineate a tip portion of the payment of the customer, and compensate the driver separately for the tip portion.
- Accordingly, account interface 340 is capable of interfacing with online transactional accounts on behalf of either the customer 310 or the transport party/respondent. As an alternative, the
server 300 may maintain credit card information for customers and use that information to pay the transport party/driver. - According to some embodiments, when the fare is complete,
server 300 automatically, without approval from the customer, pays the respondent. In this way, the respondents are encouraged to accept the transport requests, in that payment for services is assured. The customer may have the option to tip. Whether the customer tips or not may reflect back on the customer by the respondent's rating/feedback. - Feedback
- Some embodiments enable the participants of the transport service to provide feedback about one another based on their respective experiences. As mentioned elsewhere, one embodiment provides that each participant (customer and driver) can provide feedback that includes a rating or other quantative metric. Additionally, a user can provide qualitative statements, such as sentences or paragraph-formed commentary about his experience with the driver.
- With reference to
FIG. 3 , arating interface rating interface 384 of the customer enables the customer to recordfeedback 385 about a driver, or more generally, about the transport party (e.g. driver or the taxi or limousine company that provided the transport). Likewise, therating interface 388 enables the driver to record feedback about the customer 389. The rating information of each participant may be recorded as part of that user's profile information, and thus stored in theprofile store 350. Thus, each feedback results in a respective driver rating update 387 (provided by the customer) or customer rating update 391 (provided from the driver). - In some embodiments, the
rating interface - Other forms of feedback may also be collected in addition to, for example, overall ratings. For example, the transport service may prompt the customer to answer a series of yes or no questions as a means of evaluating the performance of a particular driver. The questions may ask, for example, whether the driver was courteous, whether the driver opened the door or assisted the customer in entering the vehicle, the manner in which the driver drove the vehicle, and the driver's response time. The user's questionnaire feedback may be recorded for the particular driver and/or the company or operator that provided the driver.
- Once entered, the rating information can have a variety of uses. Rating information can influence, for example, the ability of a customer to pick up a driver when the pool of drivers is limited. A customer's rating may be based on factors such as whether the customer provided a decent tip, and was courteous. A “good tipper” can be identified from the rating information, and when the good tipper needs transport, available drivers are more likely to accept his fare. On the driver side, the rating information associated with a driver may reflect the driver's courtesy, driving manner etc. The
transport service 300 may prioritize (or emphasize) selection of drivers with good ratings. For example, theinvite 314 may first be sent to proximate drivers with highest ratings, then proximate drivers with middle tier ratings. Still further, some embodiments provide the user with the ability to reject the driver based on, for example, the driver's rating information. - As still another variation, the rating information may be used as a parameter in selecting one driver to be paired to a customer. In such an embodiment, customers may first be paired with drivers with similar ratings.
- Log and Data Usage
- Still further, embodiments enable collection and dissemination of data that can promote or facilitate transport services for both customers and drivers. A transport service such as described with
FIG. 1 orFIG. 3 may collect and utilize information determined from customers and drivers for a variety of purposes. Among the types of information that can be collected, the location of potential customers may be determined based on location information transmitted from suitably configured customer handsets. For example, service 120 (FIG. 1 ) may identify a location (e.g. city block, street address) of a conglomeration of customer handsets during a given time interval. Numerous inferences may then be made about the conglomeration. For example, the conglomeration may be identified as a social event or hot-spot in the city at the given time interval. This information can then be shared with other customers, or with a portion of the population that may want to know where, for example, the ‘night life’ in the city is in a given evening. Drivers and fleet operators (including conventional transport providers who may not use handsets) may be informed of the location where customer pickups may readily be available. - Other types of information that may be collected, disseminated or otherwise used includes (i) popular pickup locations (e.g. to assist transport providers as to locations to patrol or be near for pickups), (ii) popular destinations, (iii) estimated travel times through to a given destination, or through a particular part of a city (e.g. to estimate traffic). Thus, the collection and dissemination/use of this and other information may be collected to provide additional services, or to enhance transport providers in providing service.
- With reference to
FIG. 3 , information pertaining to the various transports that are transacted through the transport service are recorded for a given duration of time. The recorded information may identify customer pickup locations, customer drop-off locations, time of transport, duration of transport, and/or routes taken. In the example shown, the recorded information is stored in alog 394. The information may be recorded from, for example, dispatch 320 (identify customer pickup locations), thecustomer tracker 360 and driver tracker 370 (record pickup and drop-off locations, routes taken, duration), and/or the payment component 380 (record fares paid, tips paid etc.). - From the recorded information, various kinds of analysis can be performed. An
analysis component 390 may analyze information from thelog 394 to identify information for users (customers and drivers) of the transport service, as well as to direct users who may research based on information recorded by the transport service. Theanalysis component 390 may provide output to users on, for example, a website. - According to some embodiments such as described with
FIG. 6 , the information from the log includes historical and/or real-time information that is published to third-parties and/or a population. For example, the publication may be in the form of communications sent directly to third-parties, such as vehicle transport providers. Alternatively, the information may be published on, for example, a website or made available to users that operate a mobile application. For parties such as customers, the information may identify the location of transport vehicles, as well as popular spots in a given geographic region. For vehicle transport services and providers, the information may predict likely areas where there are likely to be fares, thus facilitating the vehicle transport services and providers in positioning vehicles and drivers to reduce response times to customer transport requests. - As another example, web users can utilize the site to identify traffic spots or best routes by identifying routes taken by drivers of the transport service, as well as their actual transport time (versus expected or average).
- Numerous other applications for such data exist. For example, common pickup locations may be analyzed by time, date or event to facilitate taxi services in knowing where to locate themselves in their off time. Similar information can identify information relevant to other business or social settings of a city. For example, hotel occupancy can be estimated by identifying the number of drop-offs at hotels.
- Historical information may also be utilized to predict likely transport request times and locations. For example, the most common pickup times in a given region of a city at a particular time of year can be determined.
- Payment Methodology
-
FIG. 4 illustrates a process for programmatically transferring funds from a customer to a relevant transport party as a mechanism for compensating the transport party, according to an embodiment. A method such as described byFIG. 4 may be implemented using components such as described withFIG. 3 . Accordingly, reference is made to components ofFIG. 3 for purpose of illustrating suitable components for performing a step or sub step being described. - Customers may subscribe to participate in a transport service such as described with
FIG. 3 . For customers, their participation may include (i) establishing an account with funds, and (ii) registering and/or enabling a device to utilize the service ofserver 300. For drivers, their participation may involve (i) establishing an account to receive funds, and (ii) registering and or enabling a device to utilize the service ofserver 300. In one embodiment, the devices used by the participants correspond to handsets that run applications (“app”) for participating in the transport service described. Other types of devices may also be used, such as laptops, tablets, computers, or other GPS enabled devices that have network connectivity. It should also be noted that embodiments contemplate use of more primitive devices, such as those that only enable cellular telephony communications and/or SMS. - In this environment, participants (customers and transport providing parties) are associated with accounts (410). In the case of the customers, the accounts include funds that can be used for transfer to a driver. For example, the customer may make payments through a specific transport service account that is managed by the transport service entity. The payments may be made, for example, in advance, periodically, or when prompted (such as by the transport service in response to the customer receiving the transport). The transport service (such as implemented on the server(s) 300) may have authority to automate transfer of funds from an account of the customer that is not under the control of the transport service (e.g. checking account, credit card account, PAYPAL account).
- As provided with other embodiments, the relevant transport party that is to receive compensation from the fare (directly from the service) can, depending on the implementation and the payment methodology, correspond to (i) the fleet or vehicle operator (e.g. limousine company or entity), and/or (ii) the driver. The transport party may establish or associate an account to receive funds from the transport service and/or account of the customer. Each account may also be associated with profile information of the respective participant, including the identity of the participant.
- The transport service determines when the customer is being provided transport by driver (420). This determination may be made based on factors that include the customer requesting pickup, and a transport service selecting a particular driver. However, embodiments further recognize that not all transport requests may end up as fares. Thus, embodiments include the ability to auto detect when the customer and driver have actually initiated the transport (422). Such detection can be implemented in one of many possible ways. For example, the position of the transport providing vehicle and customer can be compared over duration of time while the two are moving, and if they are at the same position, the significance is that they are determined to be in the same vehicle. As an alternative or addition, accelerometers incorporated into the handsets of the customer and/or driver may detect linear motion, such as provided by motion of a vehicle. This information can also be used to detect a fare pickup, or to confirm as such. As an alternative or addition, customer input (424) or driver input (426) may be used to determine when the fare has started.
- In addition to detecting the pickup, one or more embodiments detect the completion of the transport (430). Similar to pick up, this determination may be made automatically (432), or by way of input from either the customer (434) or the driver (436). Automatic detection of the transport completion can be made by comparing
relative position data 311, 313 (e.g. as determined from GPS of devices) of the customer and transport vehicle, respectively. For example, if theposition data - As still another variation, once the fare pickup is detected as being present, a wireless signal (e.g. Bluetooth detection and/or pairing) may be used to determine that the two devices are in very close proximity to each other (e.g. front seat and backseat of vehicle). The completion of the transport may correspond to such wireless signal indicating the two devices have separated.
- As mentioned with pickup, manual input may also be used, such as by the customer (434) or the transport party (436). For example, one party may have lost battery life, in which case manual input from the other party is needed to signify end of transport.
- Once the transport is complete, the location payment parameters for the fare are determined (440). The location payment parameters can include, but are not limited to, the customer pickup location (442), the customer drop-off location (444), route information (or intermediate positions between the pickup and drop-off locations) (446), and/or the duration of the transport (448). Other location parameters can include the type of vehicle used (e.g. sedan versus stretch limo), presence of tolls or other costs, and even the transport route that is used.
- As an addition or alternative to use of location payment parameters, some embodiments determine the fare price using alternative parameters (450). The alternative parameters include market condition parameters (452). Market condition parameters may correspond to metrics that estimate or predict availability and demand for transport at a particular duration corresponding to when the customer requests transport. In one implementation, the demand may be based on (i) determining the pool of candidate parties or respondents that are in service in the particular duration, and (ii) determining the number of drivers that are engaged by customers at the given duration. For example, during peak hours, the number of transport providing vehicles may be a maximum. Rates for transport services may be higher or at peak than low demand hours. Still further, the fare value may weight or prioritize demand for transport independently. For example, when demand is at peak, rates for transport services may be higher.
- Demand can be determined from real-time information maintained by the transport serve. For example, the
log 394 may at a given instance identify the number of available vehicles, and the number of transports that are engaged or in service. As an alternative or addition, the demand may be predicted from historical analysis, such as estimations of demand during particular hours of weekdays, weekends, or holidays. - As a variation or alternative to market parameters, desirability parameters may be used to determine the fare value (454). Desirability parameters may correspond to the type of vehicle or transport provided. For example, the luxury limousines may result in a higher fare value than non-luxury sedans. The desirability of the transport may also include parameter such as whether ride sharing is permitted, whether on-board entertainment or amenities or provided etc. Desirability parameters may also correspond to rating parameters of the transporting party (either the company or driver). Such rating parameters may designate higher ratings for transport providing parties (or drivers) that have higher ratings. The fare value may also be affected by the customer rating. For example, customers may have higher ratings or class designations (e.g. VIPs), and with such designation, the fare for that customer may be reduced.
- As another variation, some embodiments may base the fare value on transport evaluation parameters. The transport service may evaluate the quality and kind of the transport that the customer received from the driver. The evaluation may be based on criteria such as (i) the response time of the driver to arrive at the pickup location, (ii) the transport time, (iii) whether the driver elected the fastest or best route to the drop-off location. Other considerations include whether amenities were provided to the customer (or whether the customer actual used the amenities), as well as feedback by the customer as to specifics of the transport (e.g. the driver was courteous, opened the door, the car was clean, the driver obeyed driving laws etc.).
- Other parameters may also be used to determine the fare value. Such other parameters may include bids that the transport service receives from the transport providing parties for fares at select locations, times or for particular drivers or vehicles.
- From the payment parameters, the fare for the transport is calculated and transferred from customer to driver (460). In one embodiment, the fare is calculated and accessed from the customer account, in response to a determination that the transport is complete. Alternatively, the transfer of the fare may be performed substantially automatically, such as by way of prompting the customer and/or driver to perform some action or otherwise provide confirmation upon determining that the transport has been completed.
- As mentioned with other embodiments, various methodologies may be used to distribute funds from the customer to the various entities that are involved in providing the transport to the customer. In one embodiment, the transport service collects the funds and distributes funds to the pertinent transport parties periodically, or responsively, after one or more fares are collected. The sum total of the fares that are distributed to the transport party may represent a portion of the total received. As an alternative, the funds (or portion thereof) collected from the customer can be transferred directly to the transport party. In the context provided, the transport party may correspond to the operator or company that provides the drivers. Thus, the drivers may be compensated by separate arrangements with the operator or company that provides the transport (e.g. their employers). Still as another variation, some funds may be distributed from the transport service to the drivers separate from the companies that employ the drivers (e.g. the tip portion). Numerous variations are possible for distributing funds collected from customers, depending on considerations for distributing collected funds from the customer.
- With reference to embodiments described above, the parameters used to determine the fare value may include numerous variations. In one embodiment, the fare value may be based on the route of the transport, as defined by the customer pickup location, the customer drop-off location and intermediate points there between. In another embodiment, the general geographic locality where the transport service operates (e.g. a city) may be ‘fenced’ geographically into multiple pre-defined regions. The fare value from one fenced region to another may be pre-determined. Thus, only the pickup and drop-off locations may be used to determine the fare value. In addition to location parameters, other parameters set by market conditions, desirability of other parameters may influence the fare value (e.g. adjust it up or down), or even provide the primary factor for determining the fare value.
-
FIG. 5 illustrates a process for enabling fee splitting amongst multiple customers that share a transport, according to one or more embodiments. Conventionally, fee splitting in transport situations (e.g. limos, taxis) is informal and dictated by agreement amongst the customers. The time it takes for customers to work out a fee arrangement is inefficient. Furthermore, conventional approaches have an underlining assumption that parties sharing rides know one another, and thus are comfortable discussing fee arrangement. In contrast to such approaches, an embodiment ofFIG. 5 enables transport to be arranged for multiple parties in a manner previously described by other embodiments. Additionally, the transport service can be used to determine the fee portion of each party sharing the transport, and further prompt or automate the transfer of funds from each party without requiring the individuals to agree or discuss the arrangement. Among other benefits, the fee payment arrangement can be implemented with minimal involvement from the parties. It is also easier for a transport party to provide a vehicle to pickup more than one party for transport, even if the parties are not acquaintances, as the fee splitting is not an issue that needs to be resolved by the individuals. - With reference to an embodiment of
FIG. 5 , the transport service determines that a particular transport is shared by more than one customer (510). The determination can be made in various ways. First, the transport service can be configured to detect when individuals that are participants of the service enter a vehicle that is also operating under the service. For example, such individuals may have handsets that each runs an application which communicates with theserver 300. The presence of each individual in the same vehicle may be determined in a manner described with, for example,FIG. 4 (e.g. see 410). When multiple individuals are in one of the transport vehicles, the transport service may assume the fee splitting arrangement is to take place. - Alternatively, the assumption may be a parameter that is weighted against other parameters, such as whether the individuals entered the vehicle at the same time, whether they have shared rides in the past or whether they are dropped off at the same location. As another variation or alternative, the fee splitting may be implemented after individuals in the transport perform a designated action. This designated action can correspond to the individuals responding to a prompt delivered to their respective handsets. As an alternative, the users may “bump” devices. Bumping can trigger an accelerometer to register the event, and the event can signify some action like fee splitting. Numerous actions can be performed to enable the transport service to infer fee splitting is in place.
- Once the transport is partially complete (some but not all of the customers are dropped off) or fully complete (all of the customers are dropped off), the payment parameters for the fare of each customer can be determined (520). The payment parameters may be customer-specific (524) and/or collective (528) for the fare, depending on the algorithm that is implemented. Customer-specific payment parameters include (i) pickup-location of each customer (if different), (ii) drop-off location of each customer (if different), and/or (iii) ride duration of each customer between their respective pickup and drop-off locations. Collective ride parameters include the starting point (first pickup) of the transport and the finishing point (the last drop-off), as well as the total distance and/or time of the transport from start to finish.
- The portion of the fee is calculated for each customer based on the determined payment parameters (530). The particular payment parameters, weighting and/or other factors used in determining the proportioning amongst the customers can be a matter of implementation.
- According to some embodiments, the fare portion attributable to each customer is then withdrawn from each user's associated online account and transferred to an account of the transport service, or the transport party (depending on the implementation). The payment transfer may be performed automatically, substantially automatically (e.g. prompt user to confirm payment) or manually. For example, in some cases, the user may have to pay cash or by credit.
-
FIG. 6 illustrates a method for processing data determined from monitoring transport amongst parties located at different locations, according to one or more embodiments. A method such as described byFIG. 6 may be implemented using components such as described withFIG. 3 . Accordingly, reference is made to components ofFIG. 3 for purpose of illustrating suitable components for performing a step or sub step being described. - Embodiments recognize that utilizing mobile devices with geo-aware resources and communicative capabilities to arrange transports enable significant data collection and usages. A transport service such as described with
FIG. 3 may arrange transport for multiple vehicle transport services, such as different limousine operates in a designated city. In doing so, instances of customer pickups and drop-offs may be recorded, including recording the pickup locations (610) and drop-offs (620). The information may be recorded in thelog 394. In some embodiments, the information may be recorded in real-time, although the information may stored for use as historical data. - Other information may also be recorded from, for example, by monitoring vehicles available for transport, and/or transports in progress (630). For example, the location of available vehicles may be determined, as well as the duration of transport between locations.
- The recorded information is processed (640). In real-time applications, the information current information at a given instance is extracted from the log and processed in accordance with a particular application. One applications includes presenting geographic information about popular customer pickup and/or drop-off locations. For example, a map may be generated that identifies the location of or popular recent customer pickups, recent or popular customer drop-offs, current location of available transport vehicles, predicted response times, and predicted areas of traffic congestion.
- As another application, historical information from the
log 394 may be used to predict demands for transport during given time spans (e.g. weeknights, weekends, between 2-4 pm on Thursdays etc.). The historical information may include customer pickup locations, pickup times, customer drop-off locations and/or drop-off times. This information may be processed to determine predicted demands for transport at given locations and times. - The processed information is then communicated or published to third-parties (650). For example, the transport service may publish the processed information on, for example, a website that is available to customers and transport provides. Alternatively, the information may be published through applications that execute on user devices. As still another example, the information may be generated in the form of reports that are emailed or otherwise communicated to parties (e.g. transport providing parties) directly. Numerous other variations are possible.
-
FIG. 7A throughFIG. 7F illustrate examples of a series of user-interfaces that are displayed to the customer from the time he requests transport to the time he arrives at his destination. As mentioned, a system such as described withFIG. 1 and/orFIG. 3 may be implemented on handsets operated by customers and respondents. The customer may operate a program on the handset to select transport.FIG. 7A shows a presentation and interface, depicting an embodiment in which the customer is shown his location and a soft button or icon (any mechanical or programmatic input may be used) to initiate the transport request. The presentation and interface may be generated on the customer device by an application, such as mobile app that is configured to communicate with a transport service. Alternatively, the presentation and interface may be made through, for example, a browser of the device, which connects to a specific website or network location to generate the presentation (or execute an application for generating the interface). In making the request, an embodiment provides that the customer need only trigger the soft-feature (or other input mechanism). Once the soft-feature is triggered, the application (or programming) automatically determines the information that is to be provided with the request, such as the location of the customer (as determined from the GPS resources of the device), the identity of the customer (as stored for use with the application), and other information (e.g. such as picture of the customer). Thus, the customer does not need to enter the address, but can compose and send the request for transport, along with information to identify the geographic location of the customer, with a simple soft-press or icon selection. - In
FIG. 7B throughFIG. 7D , progress panels are displayed to the customer. InFIG. 7B , the progress panel informs the customer that a driver is being selected (e.g. by process such as described with an embodiment ofFIG. 1 ). Afeature 712 is provided to enable the customer to cancel the pickup.FIG. 7C shows thegeographic location 722 and estimated time ofarrival 724 of the driver. The panel may be updated as the driver makes its way to the customer, to show how the driver is progressing towards the customer. InFIG. 7D , information about the selected driver/respondent is shown to the user. This may include animage 732 of the driver's face, as well as therating information 734 associated with the driver.FIG. 7E shows an interface for when the trip is in progress (after-pickup). As a variation, the location of the vehicle in transit may be shown on a map. InFIG. 7F , the customer is provided an interface that includes (i) afeature 742 displaying the fare price (see e.g.FIG. 4 andFIG. 5 ), and (ii) aninput interface 744 to rate the driver. -
FIG. 8A throughFIG. 8F illustrate examples of a series of user-interfaces that are displayed to the driver/respondent, from the time the request for transport is made from the customer. InFIG. 8A andFIG. 8B , the transport request is received by the respondent. Information contained when the driver receives/accepts the transport request include (i) identification of thecustomer 802, (ii) rating information associated with thecustomer 804, and (iii) location of the customer 806 (which can be displayed as a map). - In
FIG. 8C throughFIG. 8E , the driver/respondent is provided the interface to start the monitoring function of his handset. In one implementation, the driver/respondent is able to operate asoft button 812 to trigger when to start monitoring and when it is to finish. InFIG. 8F , when the fare is finished, thefare amount 822 is displayed to the driver and confirmation may be provided as to the fare amount. The driver is also given the opportunity to provide rating/feedback 832 of the customer. - Although illustrative embodiments have been described in detail herein with reference to the accompanying drawings, variations to specific embodiments and details are encompassed by this disclosure. It is intended that the scope of the invention is 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. Thus, absence of describing combinations should not preclude the inventor(s) from claiming rights to such combinations.
Claims (25)
Priority Applications (8)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/961,493 US20110313804A1 (en) | 2009-12-04 | 2010-12-06 | System and method for arranging transport amongst parties through use of mobile devices |
US13/672,655 US20130132246A1 (en) | 2010-12-06 | 2012-11-08 | Providing a summary or receipt for on-demand services through use of portable computing devices |
US13/672,661 US20130132887A1 (en) | 2010-12-06 | 2012-11-08 | Transitioning user interface features for on-demand services through use of portable computing devices |
US13/672,658 US20130132140A1 (en) | 2009-12-04 | 2012-11-08 | Determining a location related to on-demand services through use of portable computing devices |
US13/837,592 US20130246301A1 (en) | 2009-12-04 | 2013-03-15 | Providing user feedback for transport services through use of mobile devices |
US15/457,948 US20170186056A1 (en) | 2009-12-04 | 2017-03-13 | Providing on-demand services through use of portable computing devices |
US15/645,874 US20170316359A1 (en) | 2009-12-04 | 2017-07-10 | Determining a Location Related to On-Demand Services Through Use of Portable Computing Devices |
US16/927,771 US11188955B2 (en) | 2009-12-04 | 2020-07-13 | Providing on-demand services through use of portable computing devices |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US26699609P | 2009-12-04 | 2009-12-04 | |
US12/961,493 US20110313804A1 (en) | 2009-12-04 | 2010-12-06 | System and method for arranging transport amongst parties through use of mobile devices |
Related Child Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/672,655 Continuation-In-Part US20130132246A1 (en) | 2010-12-06 | 2012-11-08 | Providing a summary or receipt for on-demand services through use of portable computing devices |
US13/672,634 Continuation-In-Part US9230292B2 (en) | 2009-12-04 | 2012-11-08 | Providing on-demand services through use of portable computing devices |
US13/672,661 Continuation-In-Part US20130132887A1 (en) | 2010-12-06 | 2012-11-08 | Transitioning user interface features for on-demand services through use of portable computing devices |
US13/672,658 Continuation US20130132140A1 (en) | 2009-12-04 | 2012-11-08 | Determining a location related to on-demand services through use of portable computing devices |
US13/837,592 Continuation-In-Part US20130246301A1 (en) | 2009-12-04 | 2013-03-15 | Providing user feedback for transport services through use of mobile devices |
Publications (1)
Publication Number | Publication Date |
---|---|
US20110313804A1 true US20110313804A1 (en) | 2011-12-22 |
Family
ID=44115341
Family Applications (9)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/928,254 Active US9959512B2 (en) | 2009-12-04 | 2010-12-06 | System and method for operating a service to arrange transport amongst parties through use of mobile devices |
US12/961,493 Abandoned US20110313804A1 (en) | 2009-12-04 | 2010-12-06 | System and method for arranging transport amongst parties through use of mobile devices |
US12/928,253 Abandoned US20110307282A1 (en) | 2009-12-04 | 2010-12-06 | System and method for operating a service to arrange transport between a customer and a transport party |
US13/596,497 Abandoned US20120323642A1 (en) | 2009-12-04 | 2012-08-28 | System and method for operating a service to arrange transport amongst parties through use of mobile devices |
US13/672,658 Abandoned US20130132140A1 (en) | 2009-12-04 | 2012-11-08 | Determining a location related to on-demand services through use of portable computing devices |
US15/645,874 Abandoned US20170316359A1 (en) | 2009-12-04 | 2017-07-10 | Determining a Location Related to On-Demand Services Through Use of Portable Computing Devices |
US15/933,975 Active 2032-08-30 US11068811B2 (en) | 2009-12-04 | 2018-03-23 | System and method for operating a service to arrange transport amongst parties through use of mobile devices |
US16/247,246 Abandoned US20190220788A1 (en) | 2009-12-04 | 2019-01-14 | System and method for operating a service to arrange transport amongst parties through use of mobile devices |
US17/357,375 Pending US20210319380A1 (en) | 2009-12-04 | 2021-06-24 | System and method for facilitating a transport service for drivers and users of a geographic region |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/928,254 Active US9959512B2 (en) | 2009-12-04 | 2010-12-06 | System and method for operating a service to arrange transport amongst parties through use of mobile devices |
Family Applications After (7)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/928,253 Abandoned US20110307282A1 (en) | 2009-12-04 | 2010-12-06 | System and method for operating a service to arrange transport between a customer and a transport party |
US13/596,497 Abandoned US20120323642A1 (en) | 2009-12-04 | 2012-08-28 | System and method for operating a service to arrange transport amongst parties through use of mobile devices |
US13/672,658 Abandoned US20130132140A1 (en) | 2009-12-04 | 2012-11-08 | Determining a location related to on-demand services through use of portable computing devices |
US15/645,874 Abandoned US20170316359A1 (en) | 2009-12-04 | 2017-07-10 | Determining a Location Related to On-Demand Services Through Use of Portable Computing Devices |
US15/933,975 Active 2032-08-30 US11068811B2 (en) | 2009-12-04 | 2018-03-23 | System and method for operating a service to arrange transport amongst parties through use of mobile devices |
US16/247,246 Abandoned US20190220788A1 (en) | 2009-12-04 | 2019-01-14 | System and method for operating a service to arrange transport amongst parties through use of mobile devices |
US17/357,375 Pending US20210319380A1 (en) | 2009-12-04 | 2021-06-24 | System and method for facilitating a transport service for drivers and users of a geographic region |
Country Status (5)
Country | Link |
---|---|
US (9) | US9959512B2 (en) |
EP (2) | EP2507753A4 (en) |
AU (1) | AU2010325793B2 (en) |
CA (1) | CA2782611C (en) |
WO (1) | WO2011069170A1 (en) |
Cited By (81)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120232943A1 (en) * | 2011-03-09 | 2012-09-13 | Makor Issues And Rights Ltd. | Automatic optimal taxicab mobile location based dispatching system |
US20130085817A1 (en) * | 2011-09-29 | 2013-04-04 | Michael Collins Pinkus | Discount offer system and method for use with for hire vehicles |
US20130090957A1 (en) * | 2011-10-05 | 2013-04-11 | Robert Popkey | Waiting line transaction management system and method |
US8473326B1 (en) * | 2011-03-23 | 2013-06-25 | Amazon Technologies, Inc. | Courier management |
US20130185208A1 (en) * | 2012-01-18 | 2013-07-18 | Square, Inc. | Handling transaction and trip data |
US20130317945A1 (en) * | 2011-02-18 | 2013-11-28 | Doleweerd Consulting Inc. | Browser based mapping region builder |
US20130339168A1 (en) * | 2012-06-07 | 2013-12-19 | Keith T. White | Systems and Methods for Facilitating Transactions Between a Seeker and a Proffered Provider of an Urgent Goods or Service |
US20140040079A1 (en) * | 2012-05-04 | 2014-02-06 | Shahar Smirin | Mechanisms for ordering transportation vehicles |
US20140046789A1 (en) * | 2012-08-09 | 2014-02-13 | Ebay, Inc. | Fast Transactions |
US20140051465A1 (en) * | 2011-04-19 | 2014-02-20 | Godert Otto Anthony Ruys | Vehicle request device |
US20140058880A1 (en) * | 2012-06-12 | 2014-02-27 | Corey G. Konaxis | Retail fitting room/fitting room attendant system and method |
US20140123306A1 (en) * | 2012-10-30 | 2014-05-01 | Elwha Llc | Methods and systems for managing data |
US20140279713A1 (en) * | 2013-03-14 | 2014-09-18 | Bank Of America Corporation | Automated payment for a rental period based on determining the location of a renter's mobile communication device |
US20150095197A1 (en) * | 2013-09-30 | 2015-04-02 | David Edward Eramian | Systems and methods for minimizing travel costs for use of transportation providers by a user |
US20150095122A1 (en) * | 2013-09-30 | 2015-04-02 | David Edward Eramian | Systems and methods for determining pro rata shares of a monetary cost during a ride sharing situation |
EP2860673A1 (en) | 2013-10-14 | 2015-04-15 | Chaillie, Patrick | Server and method for matching a demand request for a transport capacity with supply requests |
CN104620277A (en) * | 2012-08-24 | 2015-05-13 | 三星电子株式会社 | Method and mobile terminal for providing transport service information, method and server for managing transport service, and method and vehicle for providing transport service |
US9053478B2 (en) | 2011-05-03 | 2015-06-09 | Verifone, Inc. | Mobile commerce system |
US9157748B2 (en) | 2012-07-31 | 2015-10-13 | Flatiron Apps LLC | System and method for hailing taxicabs |
US20150348221A1 (en) * | 2014-06-02 | 2015-12-03 | Uber Technologies, Inc. | Maintaining data for use with a transport service during connectivity loss between systems |
TWI512668B (en) * | 2013-05-06 | 2015-12-11 | Univ Nat Taiwan | Intelligent cross direction and real-time vehicle dispatching system |
WO2015200225A1 (en) * | 2014-06-20 | 2015-12-30 | OneWhistle, Inc. | Location-based service provisioning |
WO2016007857A1 (en) * | 2014-07-11 | 2016-01-14 | Sunil Paul | Systems and methods for providing transportation discounts in shared rides |
US20160019473A1 (en) * | 2014-07-18 | 2016-01-21 | Otitopic Inc. | Arranging transport amongst parties through use of mobile devices |
US20160034855A1 (en) * | 2014-07-30 | 2016-02-04 | Lenovo (Singapore) Pte. Ltd. | Location sharing for events |
US20160078516A1 (en) * | 2014-09-17 | 2016-03-17 | Umm Al-Qura University | Wasul transport application |
WO2016111898A1 (en) * | 2015-01-06 | 2016-07-14 | Instalabor, Llc | Labor marketplace exchange computing systems and methods |
US20160247109A1 (en) * | 2015-02-24 | 2016-08-25 | Addison Lee Limited | Systems and Methods for Vehicle Resource Management |
US9432804B2 (en) | 2014-07-10 | 2016-08-30 | Bank Of America Corporation | Processing of pre-staged transactions |
WO2016135645A1 (en) * | 2015-02-24 | 2016-09-01 | Addison Lee Limited | Systems and methods for allocating networked vehicle resources in priority environments |
US9471759B2 (en) | 2014-07-10 | 2016-10-18 | Bank Of America Corporation | Enabling device functionality based on indoor positioning system detection of physical customer presence |
US9499128B2 (en) | 2013-03-14 | 2016-11-22 | The Crawford Group, Inc. | Mobile device-enhanced user selection of specific rental vehicles for a rental vehicle reservation |
US9635545B2 (en) | 2010-07-21 | 2017-04-25 | Sensoriant, Inc. | System and method for controlling mobile services using sensor information |
US9659316B2 (en) | 2014-07-10 | 2017-05-23 | Bank Of America Corporation | Providing navigation functionality in a retail location using local positioning technology |
US9681254B2 (en) | 2010-07-21 | 2017-06-13 | Sensoriant, Inc. | System and method for control and management of resources for consumers of information |
US9691092B2 (en) | 2014-07-10 | 2017-06-27 | Bank Of America Corporation | Predicting and responding to customer needs using local positioning technology |
CN106908077A (en) * | 2015-12-23 | 2017-06-30 | 滴滴(中国)科技有限公司 | Route of user display methods and device based on map |
US9699599B2 (en) | 2014-07-10 | 2017-07-04 | Bank Of America Corporation | Tracking associate locations |
US9715707B2 (en) | 2010-07-21 | 2017-07-25 | Sensoriant, Inc. | System and method for control and management of resources for consumers of information |
US9734643B2 (en) | 2014-07-10 | 2017-08-15 | Bank Of America Corporation | Accessing secure areas based on identification via personal device |
US9741023B2 (en) | 2012-02-28 | 2017-08-22 | Emerson Electric Co. | HVAC system remote monitoring and diagnosis |
US9749206B2 (en) | 2012-10-30 | 2017-08-29 | Elwha Llc | Methods and systems for monitoring and/or managing device data |
US9785920B2 (en) | 2012-01-18 | 2017-10-10 | Square, Inc. | Acquisition of card information to enhance user experience |
US9824504B2 (en) | 2012-01-18 | 2017-11-21 | Square, Inc. | Mobile card processing using multiple wireless devices |
US9886458B2 (en) | 2012-11-26 | 2018-02-06 | Elwha Llc | Methods and systems for managing one or more services and/or device data |
US9902343B2 (en) | 2013-07-31 | 2018-02-27 | Driverdo Llc | Digital vehicle tag and method of integration in vehicle allocation system |
CN107766997A (en) * | 2016-08-15 | 2018-03-06 | 滴滴(中国)科技有限公司 | A kind of method and device of order push |
US20180130160A1 (en) * | 2016-11-08 | 2018-05-10 | Peter Alexander | Systems, Devices, and/or Methods for Managing Transportation |
US20180137487A1 (en) * | 2016-11-11 | 2018-05-17 | Kevin Sunlin Wang | System and method for geo-aware transportation billing verification |
CN108205407A (en) * | 2016-12-20 | 2018-06-26 | 夏普株式会社 | Display device, display methods and storage medium |
US10028081B2 (en) | 2014-07-10 | 2018-07-17 | Bank Of America Corporation | User authentication |
US20180233045A1 (en) * | 2017-02-10 | 2018-08-16 | Vikram Kumar | End-trip detection system |
US10055804B2 (en) | 2011-09-20 | 2018-08-21 | Metrobee, Llc | Roaming transport distribution management system |
US10074130B2 (en) | 2014-07-10 | 2018-09-11 | Bank Of America Corporation | Generating customer alerts based on indoor positioning system detection of physical customer presence |
US10085121B1 (en) | 2017-09-15 | 2018-09-25 | Uber Technologies, Inc. | Lost device detection using geospatial location data |
US10091325B2 (en) | 2012-10-30 | 2018-10-02 | Elwha Llc | Methods and systems for data services |
US10108952B2 (en) | 2014-07-10 | 2018-10-23 | Bank Of America Corporation | Customer identification |
US10171569B2 (en) | 2016-12-02 | 2019-01-01 | Uber Technologies, Inc. | Transmission of data to multiple computing devices according to a transmission schedule |
US10176891B1 (en) | 2015-02-06 | 2019-01-08 | Brain Trust Innovations I, Llc | System, RFID chip, server and method for capturing vehicle data |
US10176443B2 (en) * | 2016-08-09 | 2019-01-08 | Conduent Business Services, Llc | Method and system for dispatching of vehicles in a public transportation network |
US10181104B2 (en) | 2013-07-31 | 2019-01-15 | Driverdo Llc | Allocation system and method of deploying resources |
US10200371B2 (en) | 2015-11-09 | 2019-02-05 | Silvercar, Inc. | Vehicle access systems and methods |
US10216957B2 (en) | 2012-11-26 | 2019-02-26 | Elwha Llc | Methods and systems for managing data and/or services for devices |
US10332050B2 (en) | 2014-07-10 | 2019-06-25 | Bank Of America Corporation | Identifying personnel-staffing adjustments based on indoor positioning system detection of physical customer presence |
US10360733B2 (en) | 2017-06-20 | 2019-07-23 | Bank Of America Corporation | System controlled augmented resource facility |
US10390289B2 (en) | 2014-07-11 | 2019-08-20 | Sensoriant, Inc. | Systems and methods for mediating representations allowing control of devices located in an environment having broadcasting devices |
US10438146B2 (en) | 2011-09-20 | 2019-10-08 | Metrobee, Llc | Roaming transport distribution management system |
US10552895B2 (en) * | 2016-08-11 | 2020-02-04 | Service Trading Company, Inc. | Computer system and stored program for certifying contractors |
US10574662B2 (en) | 2017-06-20 | 2020-02-25 | Bank Of America Corporation | System for authentication of a user based on multi-factor passively acquired data |
US10614473B2 (en) | 2014-07-11 | 2020-04-07 | Sensoriant, Inc. | System and method for mediating representations with respect to user preferences |
WO2020110144A1 (en) * | 2018-12-01 | 2020-06-04 | ANI Technologies Private Limited | Allocation of vehicles for inter-city rides |
US10677604B1 (en) * | 2015-07-20 | 2020-06-09 | Via Transportation, Inc. | Continuously updatable computer-generated routes with continuously configurable virtual bus stops for passenger ride-sharing of a fleet of ride-sharing vehicles and computer transportation systems and computer-implemented methods for use thereof |
US10701165B2 (en) | 2015-09-23 | 2020-06-30 | Sensoriant, Inc. | Method and system for using device states and user preferences to create user-friendly environments |
US10834538B1 (en) | 2020-02-12 | 2020-11-10 | International Business Machines Corporation | Locating a mobile device and notifying a user of the mobile device location |
US10887724B2 (en) * | 2019-05-01 | 2021-01-05 | International Business Machines Corporation | Locating a mobile device and notifying a user of the mobile device location |
US11017650B2 (en) | 2011-06-22 | 2021-05-25 | Thinkware Corporation | Safety service system and method thereof |
US11132626B2 (en) | 2016-11-30 | 2021-09-28 | Addison Lee Limited | Systems and methods for vehicle resource management |
US11244756B1 (en) * | 2017-10-20 | 2022-02-08 | Teletracking Technologies, Inc. | Integrated system and method for receiving and processing real-time digital data concerning transportation and service monitoring scheduling |
US11395093B2 (en) | 2013-10-02 | 2022-07-19 | Federico Fraccaroli | Method, system and apparatus for location-based machine-assisted interactions |
US11694250B2 (en) * | 2015-01-06 | 2023-07-04 | GigSmart, Inc. | Labor marketplace exchange and methods thereof |
US11954717B2 (en) | 2021-10-14 | 2024-04-09 | GigSmart, Inc. | Labor marketplace exchange computing systems and methods |
Families Citing this family (395)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7412842B2 (en) | 2004-04-27 | 2008-08-19 | Emerson Climate Technologies, Inc. | Compressor diagnostic and protection system |
US7275377B2 (en) | 2004-08-11 | 2007-10-02 | Lawrence Kates | Method and apparatus for monitoring refrigerant-cycle systems |
US10687166B2 (en) | 2004-09-30 | 2020-06-16 | Uber Technologies, Inc. | Obtaining user assistance |
US10514816B2 (en) | 2004-12-01 | 2019-12-24 | Uber Technologies, Inc. | Enhanced user assistance |
US10445799B2 (en) | 2004-09-30 | 2019-10-15 | Uber Technologies, Inc. | Supply-chain side assistance |
US8358976B2 (en) | 2006-03-24 | 2013-01-22 | The Invention Science Fund I, Llc | Wireless device with an aggregate user interface for controlling other devices |
US9369082B2 (en) * | 2007-02-15 | 2016-06-14 | Haihui Huang | Solar power mobile charging station |
US9140728B2 (en) | 2007-11-02 | 2015-09-22 | Emerson Climate Technologies, Inc. | Compressor sensor module |
TWI401610B (en) * | 2009-07-03 | 2013-07-11 | Shih Pi Ta Technology Ltd | Dispatching system for car assignment apparatus and method thereof |
WO2011047042A2 (en) | 2009-10-13 | 2011-04-21 | Square, Inc. | Systems and methods for dynamic receipt generation with environmental information |
US9996831B2 (en) * | 2009-11-25 | 2018-06-12 | Cubic Corporation | Mobile wireless payment and access |
WO2011069170A1 (en) | 2009-12-04 | 2011-06-09 | Uber, Inc. | System and method for arranging transport amongst parties through use of mobile devices |
US9230292B2 (en) * | 2012-11-08 | 2016-01-05 | Uber Technologies, Inc. | Providing on-demand services through use of portable computing devices |
TW201218117A (en) * | 2010-10-29 | 2012-05-01 | Hon Hai Prec Ind Co Ltd | System and method for arranging taxies |
US8635556B2 (en) * | 2010-11-30 | 2014-01-21 | Alcatel Lucent | Human readable iconic display server |
US8630897B1 (en) * | 2011-01-11 | 2014-01-14 | Google Inc. | Transportation-aware physical advertising conversions |
AU2012223466B2 (en) | 2011-02-28 | 2015-08-13 | Emerson Electric Co. | Residential solutions HVAC monitoring and diagnosis |
US8942991B2 (en) * | 2011-05-12 | 2015-01-27 | Accenture Global Services Limited | Agent-side traveler application for mobile computing devices |
US20120330719A1 (en) * | 2011-05-27 | 2012-12-27 | Ashutosh Malaviya | Enhanced systems, processes, and user interfaces for scoring assets associated with a population of data |
US20130031001A1 (en) * | 2011-07-26 | 2013-01-31 | Stephen Patrick Frechette | Method and System for the Location-Based Discovery and Validated Payment of a Service Provider |
US20130060721A1 (en) | 2011-09-02 | 2013-03-07 | Frias Transportation Infrastructure, Llc | Systems and methods for pairing of for-hire vehicle meters and medallions |
KR101907002B1 (en) * | 2011-09-29 | 2018-10-12 | 삼성전자주식회사 | Apparatus and method for creating and searching location-tagged contents in computing device |
DE202012100620U1 (en) | 2011-11-22 | 2012-06-13 | Square, Inc. | System for processing cardless payment transactions |
US20130179205A1 (en) * | 2012-01-10 | 2013-07-11 | Eduard SLININ | Systems and methods for optimizing transportation resources |
US8964338B2 (en) | 2012-01-11 | 2015-02-24 | Emerson Climate Technologies, Inc. | System and method for compressor motor protection |
SG11201404408VA (en) * | 2012-02-01 | 2014-08-28 | Mapas Inteligentes Llc | Geocoding points of interest and service route delivery and audit field performance and sales method and apparatus |
US9373112B1 (en) | 2012-03-16 | 2016-06-21 | Square, Inc. | Ranking of merchants for cardless payment transactions |
US20130246207A1 (en) | 2012-03-19 | 2013-09-19 | Uber Technologies, Inc. | System and method for dynamically adjusting prices for services |
JP6035842B2 (en) * | 2012-04-25 | 2016-11-30 | ソニー株式会社 | Imaging apparatus, imaging processing method, image processing apparatus, and imaging processing system |
WO2013159973A1 (en) * | 2012-04-27 | 2013-10-31 | Fleetmatics Irl Limited | System and method for managing vehicle dispatch and fleet workflow |
US9406084B2 (en) * | 2012-05-23 | 2016-08-02 | Specialty's Café & Bakery, Inc. | Methods for submitting a food order remotely |
US9066206B2 (en) | 2012-07-03 | 2015-06-23 | Uber Technologies, Inc. | System and method for providing dynamic supply positioning for on-demand services |
US20140052582A1 (en) * | 2012-08-15 | 2014-02-20 | Fadl-Alla Abdel Karim | Online system for person to person transaction |
US20140067488A1 (en) * | 2012-08-30 | 2014-03-06 | Frias Transportation Infrastructure Llc | Mobile for-hire-vehicle hailing system and method |
US20200211142A1 (en) * | 2012-08-30 | 2020-07-02 | Ivsc Ip Llc | For-hire-vehicle management systems and methods |
US9310439B2 (en) | 2012-09-25 | 2016-04-12 | Emerson Climate Technologies, Inc. | Compressor having a control and diagnostic module |
US9152971B2 (en) * | 2012-09-26 | 2015-10-06 | Paypal, Inc. | Dynamic mobile seller routing |
US9665858B1 (en) | 2012-10-11 | 2017-05-30 | Square, Inc. | Cardless payment transactions with multiple users |
AU2013332252A1 (en) * | 2012-10-18 | 2015-03-26 | Muzeek Pty Ltd | System, process and method of booking musicians and artists |
USD738901S1 (en) * | 2012-11-08 | 2015-09-15 | Uber Technologies, Inc. | Computing device display screen with graphical user interface |
US9671233B2 (en) | 2012-11-08 | 2017-06-06 | Uber Technologies, Inc. | Dynamically providing position information of a transit object to a computing device |
USD734349S1 (en) * | 2012-11-08 | 2015-07-14 | Uber Technologies, Inc. | Computing device with computer-generated information panel interface |
AU2013351922B2 (en) | 2012-11-30 | 2017-10-26 | Taxiprop Pty Ltd | Taximeter, system and method for a taxi |
US20140164280A1 (en) * | 2012-12-11 | 2014-06-12 | Vitalii Stepanenko | Shipping address determination based on device location |
CN103047981B (en) * | 2012-12-22 | 2017-03-15 | 江苏车视杰电子有限公司 | Electronic installation and its navigation locating method and system |
GB201300006D0 (en) * | 2013-01-01 | 2013-02-13 | Tomtom Dev Germany Gmbh | Vehicle management system |
US20140214715A1 (en) * | 2013-01-30 | 2014-07-31 | Command Alkon Incorporated | Scheduling system and method for distribution of perishable loads of pre-mixed concrete to multiple sites |
US20140244330A1 (en) * | 2013-02-22 | 2014-08-28 | Innovations 10.01, Llc | System and method for assessing and managing a facility |
US9940616B1 (en) | 2013-03-14 | 2018-04-10 | Square, Inc. | Verifying proximity during payment transactions |
US9704146B1 (en) | 2013-03-14 | 2017-07-11 | Square, Inc. | Generating an online storefront |
US10467554B2 (en) | 2013-03-14 | 2019-11-05 | Lyft, Inc. | System for connecting a driver and a rider |
US20140279220A1 (en) * | 2013-03-14 | 2014-09-18 | Eric Weiner | Systems and methods for mobile retail environment |
US20140278838A1 (en) * | 2013-03-14 | 2014-09-18 | Uber Technologies, Inc. | Determining an amount for a toll based on location data points provided by a computing device |
US9638436B2 (en) | 2013-03-15 | 2017-05-02 | Emerson Electric Co. | HVAC system remote monitoring and diagnosis |
US20170286884A1 (en) | 2013-03-15 | 2017-10-05 | Via Transportation, Inc. | System and Method for Transportation |
US9803902B2 (en) | 2013-03-15 | 2017-10-31 | Emerson Climate Technologies, Inc. | System for refrigerant charge verification using two condenser coil temperatures |
US20140279081A1 (en) * | 2013-03-15 | 2014-09-18 | Qualcomm Incorporated | Mobile devices, methods and computer systems for ensuring that a pickup order is freshly prepared when a consumer arrives to pick it up |
US9551504B2 (en) | 2013-03-15 | 2017-01-24 | Emerson Electric Co. | HVAC system remote monitoring and diagnosis |
CA2908362C (en) | 2013-04-05 | 2018-01-16 | Fadi M. Alsaleem | Heat-pump system with refrigerant charge diagnostics |
US9824410B1 (en) | 2013-04-29 | 2017-11-21 | Grubhub Holdings Inc. | System, method and apparatus for assessing the accuracy of estimated food delivery time |
WO2014190023A2 (en) * | 2013-05-21 | 2014-11-27 | Cubic Corporation | Multi-modal journey planning and payment |
US10192220B2 (en) | 2013-06-25 | 2019-01-29 | Square, Inc. | Integrated online and offline inventory management |
JP5959745B2 (en) * | 2013-06-28 | 2016-08-02 | 楽天株式会社 | Advertisement system, advertisement processing device |
SG11201510767XA (en) * | 2013-07-03 | 2016-01-28 | Uber Technologies Inc | System and method for splitting a fee for an on-demand service |
US20150039366A1 (en) * | 2013-07-31 | 2015-02-05 | Mashhur Zarif Haque | Mobile application for automobile business to manage driver-based transporting of vehicles |
GB201314091D0 (en) * | 2013-08-07 | 2013-09-18 | Smart Ship Holdings Ltd | Ordering products/services |
US20150046206A1 (en) * | 2013-08-12 | 2015-02-12 | Jordan Kelley | Method, Apparatus, and System for Managing Work Flow |
CN105431882A (en) * | 2013-09-13 | 2016-03-23 | 英特尔公司 | Context-aware distributive taxi cab dispatching |
US9697531B1 (en) | 2013-09-20 | 2017-07-04 | Square, Inc. | Dynamic pricing for physical stores |
AU2014331620B2 (en) | 2013-10-04 | 2017-03-16 | Uber Technologies, Inc. | Determining location information using a location data point provided by a computing device |
US11151658B1 (en) | 2013-10-22 | 2021-10-19 | Gigawarp Technologies LLC | Dynamic location tracking assignment and management of insurance claims |
US10417635B1 (en) | 2013-10-22 | 2019-09-17 | Square, Inc. | Authorizing a purchase transaction using a mobile device |
US8892462B1 (en) | 2013-10-22 | 2014-11-18 | Square, Inc. | Proxy card payment with digital receipt delivery |
US9721314B2 (en) | 2013-10-28 | 2017-08-01 | Square, Inc. | Apportioning shared financial expenses |
US10319013B2 (en) | 2013-10-28 | 2019-06-11 | Square, Inc. | Electronic ordering system |
US20150134439A1 (en) | 2013-11-08 | 2015-05-14 | Square, Inc. | Interactive digital receipt |
US20150178714A1 (en) * | 2013-11-26 | 2015-06-25 | Transcast, Inc. | Method for providing connectivity from a transport vehicle |
US20150149286A1 (en) * | 2013-11-26 | 2015-05-28 | II Benjamin Alexander Brown | Mobile provider advertising and scheduling platform |
US20150170116A1 (en) * | 2013-11-26 | 2015-06-18 | Transcast, Inc. | Online self contained portable interactive transactional system |
IL235911B (en) | 2013-11-26 | 2018-04-30 | Gt Gettaxi Ltd | System and method for ordering a transportation vehicle using a near-field communication device |
US9344849B2 (en) | 2013-11-27 | 2016-05-17 | Alan Michael Snyder | Methods and systems for locating persons and places with mobile devices |
US10057719B2 (en) | 2013-11-27 | 2018-08-21 | Alan Snyder | Methods and systems for locating persons and places with mobile devices |
US20150154810A1 (en) * | 2013-12-04 | 2015-06-04 | Kar Leong Tew | Virtual transportation stands |
US10380564B1 (en) | 2013-12-05 | 2019-08-13 | Square, Inc. | Merchant performed banking-type transactions |
AU2014362392A1 (en) * | 2013-12-11 | 2016-06-23 | Uber Technologies, Inc. | Intelligent queuing for user selection in providing on-demand services |
CA3194882A1 (en) * | 2013-12-11 | 2015-06-18 | Uber Technologies, Inc. | Optimizing selection of drivers for transport requests |
US20150178312A1 (en) * | 2013-12-20 | 2015-06-25 | Lsi Corporation | Attribute-based assistance request system for sequentially contacting nearby contacts without having them divulge their presence or location |
US9875469B1 (en) | 2013-12-24 | 2018-01-23 | Square, Inc. | Bill splitting |
US10810682B2 (en) | 2013-12-26 | 2020-10-20 | Square, Inc. | Automatic triggering of receipt delivery |
US9984574B2 (en) | 2014-01-21 | 2018-05-29 | Tribal Rides, Inc. | Method and system for anticipatory deployment of autonomously controlled vehicles |
US20150206267A1 (en) * | 2014-01-22 | 2015-07-23 | Jahan Khanna | Systems and methods for providing a transportation marketplace |
USD773484S1 (en) * | 2014-01-24 | 2016-12-06 | Tencent Technology (Shenzhen) Company Limited | Display screen with graphical user interface |
USD769888S1 (en) * | 2014-01-24 | 2016-10-25 | Tencent Technology (Shenzhen) Company Limited | Display screen portion with graphical user interface |
USD768642S1 (en) * | 2014-01-24 | 2016-10-11 | Tencent Technology (Shenzhen) Company Limited | Display screen portion with animated graphical user interface |
US9965783B2 (en) * | 2014-02-07 | 2018-05-08 | Uber Technologies, Inc. | User controlled media for use with on-demand transport services |
US20150235304A1 (en) * | 2014-02-14 | 2015-08-20 | Melissa M. Vincent | Method and system for global shopping and delivery |
US10692038B2 (en) * | 2014-02-17 | 2020-06-23 | Bruce E. Stuckman | Delivery data server and methods for use therewith |
US10198731B1 (en) | 2014-02-18 | 2019-02-05 | Square, Inc. | Performing actions based on the location of mobile device during a card swipe |
US8965791B1 (en) | 2014-03-10 | 2015-02-24 | Square, Inc. | Quick legend receipt system |
US20150262089A1 (en) * | 2014-03-12 | 2015-09-17 | Reso Holdings, Inc. | System and method for one-click booking of a service event for a user |
WO2015138013A1 (en) | 2014-03-13 | 2015-09-17 | Uber Technologies, Inc. | Configurable push notifications for a transport service |
US9960986B2 (en) * | 2014-03-19 | 2018-05-01 | Uber Technologies, Inc. | Providing notifications to devices based on real-time conditions related to an on-demand service |
US10692064B2 (en) | 2014-03-19 | 2020-06-23 | Square, Inc. | Merchant platform |
US9767471B1 (en) | 2014-03-24 | 2017-09-19 | Square, Inc. | Determining recommendations from buyer information |
US9619792B1 (en) | 2014-03-25 | 2017-04-11 | Square, Inc. | Associating an account with a card based on a photo |
US9888087B2 (en) | 2014-03-31 | 2018-02-06 | Uber Technologies, Inc. | Adjusting attributes for an on-demand service system based on real-time information |
TW201541393A (en) * | 2014-04-21 | 2015-11-01 | Wei-Yen Yeh | Taxi management equipment and taxi management system |
JP6423520B2 (en) * | 2014-04-24 | 2018-11-14 | ベイジン ディディ インフィニティ テクノロジー アンド ディベロップメント カンパニー リミティッド | System and method for managing service supply status |
USD770487S1 (en) * | 2014-04-30 | 2016-11-01 | Tencent Technology (Shenzhen) Company Limited | Display screen or portion thereof with graphical user interface |
USD770488S1 (en) * | 2014-04-30 | 2016-11-01 | Tencent Technology (Shenzhen) Company Limited | Portion of a display screen with graphical user interface |
US10458801B2 (en) | 2014-05-06 | 2019-10-29 | Uber Technologies, Inc. | Systems and methods for travel planning that calls for at least one transportation vehicle unit |
US11100434B2 (en) | 2014-05-06 | 2021-08-24 | Uber Technologies, Inc. | Real-time carpooling coordinating system and methods |
US9569767B1 (en) | 2014-05-06 | 2017-02-14 | Square, Inc. | Fraud protection based on presence indication |
US9552559B2 (en) | 2014-05-06 | 2017-01-24 | Elwha Llc | System and methods for verifying that one or more directives that direct transport of a second end user does not conflict with one or more obligations to transport a first end user |
US9483744B2 (en) | 2014-05-06 | 2016-11-01 | Elwha Llc | Real-time carpooling coordinating systems and methods |
US10026083B1 (en) | 2014-05-11 | 2018-07-17 | Square, Inc. | Tab for a venue |
US9536271B2 (en) | 2014-05-16 | 2017-01-03 | Uber Technologies, Inc. | User-configurable indication device for use with an on-demand transport service |
US20150332223A1 (en) | 2014-05-19 | 2015-11-19 | Square, Inc. | Transaction information collection for mobile payment experience |
US9631933B1 (en) | 2014-05-23 | 2017-04-25 | Google Inc. | Specifying unavailable locations for autonomous vehicles |
US9436182B2 (en) | 2014-05-23 | 2016-09-06 | Google Inc. | Autonomous vehicles |
US10467896B2 (en) | 2014-05-29 | 2019-11-05 | Rideshare Displays, Inc. | Vehicle identification system and method |
US9892637B2 (en) | 2014-05-29 | 2018-02-13 | Rideshare Displays, Inc. | Vehicle identification system |
WO2015200328A1 (en) * | 2014-06-23 | 2015-12-30 | Dabble Apps, LLC | Ridesharing system and method |
US9531885B2 (en) | 2014-06-24 | 2016-12-27 | Level 3 Communications, Llc | Apparatus, system, and method for visualizing telecommunications resources |
JPWO2015198593A1 (en) * | 2014-06-25 | 2017-04-20 | 日本電気株式会社 | Information processing apparatus, processing method and recording medium storing the program |
JP6168636B2 (en) * | 2014-06-30 | 2017-07-26 | みこらった株式会社 | Mobile calling system, calling apparatus, and wireless communication apparatus |
CA2956063A1 (en) | 2014-07-22 | 2016-01-28 | Lyft, Inc. | Ride chaining |
CA2956631C (en) | 2014-07-30 | 2022-04-12 | Uber Technologies, Inc. | Arranging a transport service for multiple users |
CA2957054A1 (en) * | 2014-08-04 | 2016-02-11 | Uber Technologies, Inc. | Determining and providing predetermined location data points to service providers |
CN104794553B (en) * | 2014-08-12 | 2018-07-10 | 北京东方车云信息技术有限公司 | Worksheet processing system and method based on taxi operation region familiarity during network is hired a car |
US9766618B2 (en) * | 2014-08-14 | 2017-09-19 | International Business Machines Corporation | Generating work product plans specifying proportions of constituents to be used in forming a work product |
JP6432205B2 (en) * | 2014-08-15 | 2018-12-05 | 富士通株式会社 | Reservation management method, reservation management program, and reservation management apparatus |
EP3183707A4 (en) | 2014-08-21 | 2018-02-28 | Uber Technologies Inc. | Arranging a transport service for a user based on the estimated time of arrival of the user |
US20160055743A1 (en) * | 2014-08-23 | 2016-02-25 | Sunder Rathnavelu Raj | Congo: System and Method of Transportation Using Carrier Vehicles and Personal Transport Vehicles |
US20160071050A1 (en) * | 2014-09-04 | 2016-03-10 | Evan John Kaye | Delivery Channel Management |
BR112017003958A2 (en) | 2014-09-05 | 2017-12-19 | Uber Technologies Inc | providing route information to devices during a shared transport service |
US10949888B1 (en) | 2014-09-10 | 2021-03-16 | Square, Inc. | Geographically targeted, time-based promotions |
US10528901B2 (en) * | 2014-09-17 | 2020-01-07 | Uber Technologies, Inc. | Managing service provider accounts based on completion of tasks |
CN105430031B (en) * | 2014-09-17 | 2018-08-24 | 口碑控股有限公司 | A kind of share-car information transmitting methods and device |
US9626639B2 (en) | 2014-09-26 | 2017-04-18 | Shyp, Inc. | Image processing and item transport |
US11151634B2 (en) | 2014-09-30 | 2021-10-19 | Square, Inc. | Persistent virtual shopping cart |
US10101164B2 (en) | 2014-10-16 | 2018-10-16 | Aayush Thakur | Route optimization system and methods of use thereof |
US10140623B1 (en) | 2014-10-27 | 2018-11-27 | Square, Inc. | Detection and explanation of lifts in merchant data |
US10909563B1 (en) | 2014-10-30 | 2021-02-02 | Square, Inc. | Generation and tracking of referrals in receipts |
CN204242224U (en) * | 2014-11-21 | 2015-04-01 | 北京东方车云信息技术有限公司 | The system of passenger getting on/off is judged in network is hired a car |
US10194485B2 (en) | 2014-12-18 | 2019-01-29 | Motorola Solutions, Inc. | Method and apparatus for automated dispatch of mobile devices in a communication system |
WO2016113602A1 (en) * | 2015-01-12 | 2016-07-21 | Yogesh Chunilal Rathod | Real-time presenting on-demand service providers and users or customers and facilitating them |
CN104715286B (en) * | 2015-04-08 | 2018-07-13 | 北京嘀嘀无限科技发展有限公司 | The method and apparatus for determining order starting point |
SG11201705930PA (en) * | 2015-01-20 | 2017-08-30 | Beijing Didi Infinity Tech And Dev Co Ltd | Systems and methods for providing information for an on-demand service |
GB2550523A (en) | 2015-02-02 | 2017-11-22 | Beijing Didi Infinity Tech And Dev Co Ltd | Methods and systems for order processing |
US9852551B2 (en) | 2015-02-05 | 2017-12-26 | Uber Technologies, Inc. | Programmatically determining location information in connection with a transport service |
US10282684B2 (en) | 2015-02-26 | 2019-05-07 | Uber Technologies, Inc. | Performing selective operations based on mobile device locations |
JP2016161989A (en) | 2015-02-26 | 2016-09-05 | Line株式会社 | Calculation server, communication terminal, and communication terminal program |
CN104657883A (en) * | 2015-03-02 | 2015-05-27 | 北京嘀嘀无限科技发展有限公司 | Order based pairing method and pairing equipment |
US9990621B1 (en) | 2015-03-20 | 2018-06-05 | Square, Inc. | Merchant application programming interface for splitting bills |
US20160283994A1 (en) * | 2015-03-25 | 2016-09-29 | International Business Machines Corporation | Trust calculator for peer-to-peer transactions |
US20160300318A1 (en) * | 2015-04-13 | 2016-10-13 | Uber Technologies, Inc. | Fare determination system for on-demand transport arrangement service |
USD780206S1 (en) * | 2015-04-13 | 2017-02-28 | Gt Gettaxi Limited | Display screen or portion thereof with graphical user interface |
AU2016249122A1 (en) * | 2015-04-15 | 2017-11-02 | Uber Technologies, Inc. | Programmatically providing information in connection with location-based services to service providers |
US9774693B2 (en) * | 2015-04-29 | 2017-09-26 | Facebook, Inc. | Methods and systems for viewing user feedback |
US11017369B1 (en) | 2015-04-29 | 2021-05-25 | Square, Inc. | Cloud-based inventory and discount pricing management system |
US9721251B1 (en) | 2015-05-01 | 2017-08-01 | Square, Inc. | Intelligent capture in mixed fulfillment transactions |
US10009306B2 (en) | 2015-05-15 | 2018-06-26 | Uber Technologies, Inc. | Methods to mitigate communication delays between systems in connection with a transport service |
US10026062B1 (en) | 2015-06-04 | 2018-07-17 | Square, Inc. | Apparatuses, methods, and systems for generating interactive digital receipts |
US9904900B2 (en) | 2015-06-11 | 2018-02-27 | Bao Tran | Systems and methods for on-demand transportation |
US10360521B2 (en) * | 2015-06-12 | 2019-07-23 | Sap Se | Dynamic location recommendation for public service vehicles |
US10984498B2 (en) * | 2015-06-15 | 2021-04-20 | International Business Machines Corporation | Managing transportation deployment using customer activity |
US11107009B2 (en) | 2015-06-15 | 2021-08-31 | International Business Machines Corporation | Managing user transportation needs without user intervention |
US9762601B2 (en) | 2015-06-17 | 2017-09-12 | Uber Technologies, Inc. | Trip anomaly detection system |
US9733096B2 (en) * | 2015-06-22 | 2017-08-15 | Waymo Llc | Determining pickup and destination locations for autonomous vehicles |
RU2609082C2 (en) * | 2015-06-30 | 2017-01-30 | Общество С Ограниченной Ответственностью "Яндекс" | Method and system for determining address corresponding to most probable physical position of electronic device associated with user |
US10212536B2 (en) | 2015-07-10 | 2019-02-19 | Uber Technologies, Inc. | Selecting a messaging protocol for transmitting data in connection with a location-based service |
US10949796B1 (en) | 2015-07-15 | 2021-03-16 | Square, Inc. | Coordination of inventory ordering across merchants |
US10909486B1 (en) | 2015-07-15 | 2021-02-02 | Square, Inc. | Inventory processing using merchant-based distributed warehousing |
US10067988B2 (en) | 2015-07-21 | 2018-09-04 | Uber Technologies, Inc. | User-based content filtering and ranking to facilitate on-demand services |
US10657486B1 (en) | 2015-07-29 | 2020-05-19 | DoorDash, Inc. | Containers for crowdsourced delivery |
BR112017027933A2 (en) | 2015-07-29 | 2018-08-28 | Beijing Didi Infinity Technology And Development Co., Ltd. | method and system for determining the transportation service charge |
US20170034085A1 (en) * | 2015-07-30 | 2017-02-02 | Uber Technologies, Inc. | Messaging integration in connection with a transportation arrangement service |
US20170039621A1 (en) * | 2015-08-04 | 2017-02-09 | Glen Russell Harding | Multi-Agent System for GPS Web Services |
US10215574B2 (en) * | 2015-08-06 | 2019-02-26 | Uber Technologies, Inc. | Facilitating rider pick-up for a transport service |
US10121119B2 (en) | 2015-08-27 | 2018-11-06 | Indooratlas Oy | Order management |
US10013697B1 (en) * | 2015-09-02 | 2018-07-03 | State Farm Mutual Automobile Insurance Company | Systems and methods for managing and processing vehicle operator accounts based on vehicle operation data |
US9749812B1 (en) | 2015-09-03 | 2017-08-29 | State Farm Mutual Automobile Insurance Company | Tow and emergency roadside assistance locating and tracking mobile application |
US10055995B2 (en) | 2015-10-06 | 2018-08-21 | Gt Gettaxi Limited | System for preemptively navigating drivers to an event created through a social network system |
US9754338B2 (en) | 2015-10-09 | 2017-09-05 | Gt Gettaxi Limited | System to facilitate a correct identification of a service provider |
US10157436B2 (en) | 2015-10-09 | 2018-12-18 | Gt Gettaxi Limited | System for navigating vehicles associated with a delivery service |
CN106600083B (en) * | 2015-10-14 | 2021-06-01 | 腾讯科技(深圳)有限公司 | Management method and equipment for driver order taking |
US20170109704A1 (en) * | 2015-10-19 | 2017-04-20 | Recycle Track Systems Inc. | System and method for scheduling and facilitating waste removal |
US20170116563A1 (en) * | 2015-10-27 | 2017-04-27 | Peter Fong | System and Method for Arranging Duty with Transport Among Parties |
WO2017075437A1 (en) | 2015-10-30 | 2017-05-04 | Zemcar, Inc. | Rules based driver selection |
US10467561B2 (en) * | 2015-11-05 | 2019-11-05 | Gt Gettaxi Limited | System for identifying events and preemptively navigating drivers to transport passengers from the events |
US9939279B2 (en) | 2015-11-16 | 2018-04-10 | Uber Technologies, Inc. | Method and system for shared transport |
US9771018B2 (en) | 2015-12-03 | 2017-09-26 | Opus Inspection, Inc. | System and method for identification of transport vehicles and drivers |
AU2016368552B2 (en) * | 2015-12-08 | 2019-09-12 | Aurora Operations, Inc. | Optimizing communication for automated vehicles |
US9432929B1 (en) | 2015-12-08 | 2016-08-30 | Uber Technologies, Inc. | Communication configuration system for a fleet of automated vehicles |
US10243604B2 (en) | 2015-12-08 | 2019-03-26 | Uber Technologies, Inc. | Autonomous vehicle mesh networking configuration |
US10685416B2 (en) * | 2015-12-10 | 2020-06-16 | Uber Technologies, Inc. | Suggested pickup location for ride services |
US10635994B2 (en) * | 2015-12-11 | 2020-04-28 | Lyft, Inc. | System for navigating driver to passenger for ride authorized by another user of transportation service |
WO2017106497A1 (en) * | 2015-12-17 | 2017-06-22 | Counterfy Llc | Displayed identifier for a ridesharing service |
MY196941A (en) * | 2015-12-22 | 2023-05-11 | Beijing Didi Infinity Technology & Dev Co Ltd | Systems and methods for updating sequence of services |
CN106919994B (en) * | 2015-12-24 | 2021-03-16 | 北京嘀嘀无限科技发展有限公司 | Order pushing method and device |
US11205240B2 (en) | 2015-12-30 | 2021-12-21 | Waymo Llc | Autonomous vehicle services |
US11508026B2 (en) | 2015-12-31 | 2022-11-22 | Lyft, Inc. | System for navigating transportation service providers to fulfill transportation requests authorized by an organization |
US10794713B2 (en) | 2015-12-31 | 2020-10-06 | Lyft, Inc. | System for navigating drivers to passengers based on start times of events |
SG10201600024TA (en) | 2016-01-04 | 2017-08-30 | Grabtaxi Holdings Pte Ltd | System and Method for Multiple-Round Driver Selection |
US11049059B2 (en) * | 2016-02-03 | 2021-06-29 | Operr Technologies, Inc | Method and system for on-demand customized services |
US10282681B2 (en) | 2016-02-03 | 2019-05-07 | Operr Technologies, Inc. | System and method for customizable prescheduled dispatching for transportation services |
US10417605B1 (en) | 2016-02-29 | 2019-09-17 | Square, Inc. | Courier notifications regarding missing items |
US10366460B2 (en) | 2016-03-01 | 2019-07-30 | International Business Machines Corporation | Optimized route sharing |
CN107153882B (en) * | 2016-03-03 | 2021-10-15 | 北京嘀嘀无限科技发展有限公司 | Method and system for predicting passenger taxi taking time distribution interval |
WO2017155518A1 (en) * | 2016-03-08 | 2017-09-14 | Visa International Service Association | Point of sale device with additional service capabilities |
US10410200B2 (en) | 2016-03-15 | 2019-09-10 | Square, Inc. | Cloud-based generation of receipts using transaction information |
US10628811B2 (en) | 2016-03-15 | 2020-04-21 | Square, Inc. | System-based detection of card sharing and fraud |
US10242574B2 (en) | 2016-03-21 | 2019-03-26 | Uber Technologies, Inc. | Network computer system to address service providers to contacts |
US10636019B1 (en) | 2016-03-31 | 2020-04-28 | Square, Inc. | Interactive gratuity platform |
CA3015542A1 (en) * | 2016-04-01 | 2017-10-05 | Walmart Apollo, Llc | Store item delivery systems and methods |
US9429947B1 (en) | 2016-04-14 | 2016-08-30 | Eric John Wengreen | Self-driving vehicle systems and methods |
US10255648B2 (en) * | 2016-04-14 | 2019-04-09 | Eric John Wengreen | Self-driving vehicle systems and methods |
US10685391B2 (en) * | 2016-05-24 | 2020-06-16 | International Business Machines Corporation | Directing movement of a self-driving vehicle based on sales activity |
JP6477601B2 (en) * | 2016-05-31 | 2019-03-06 | トヨタ自動車株式会社 | Information processing system |
US10168164B2 (en) * | 2016-06-11 | 2019-01-01 | Apple Inc. | Integrating ride hailing services into a navigation application |
US10672198B2 (en) * | 2016-06-14 | 2020-06-02 | Uber Technologies, Inc. | Trip termination determination for on-demand transport |
US10929866B1 (en) | 2016-06-27 | 2021-02-23 | Square, Inc. | Frictionless entry into combined merchant loyalty program |
US10621515B2 (en) * | 2016-06-30 | 2020-04-14 | At&T Intellectual Property I, L.P. | Optimized traffic management via an electronic driving pass |
US10129221B1 (en) | 2016-07-05 | 2018-11-13 | Uber Technologies, Inc. | Transport facilitation system implementing dual content encryption |
JP6834075B2 (en) * | 2016-08-12 | 2021-02-24 | 株式会社日本総合研究所 | Request device and its request method |
US11182709B2 (en) | 2016-08-16 | 2021-11-23 | Teleport Mobility, Inc. | Interactive real time system and real time method of use thereof in conveyance industry segments |
US11087252B2 (en) | 2016-08-16 | 2021-08-10 | Teleport Mobility, Inc. | Interactive real time system and real time method of use thereof in conveyance industry segments |
US11176500B2 (en) | 2016-08-16 | 2021-11-16 | Teleport Mobility, Inc. | Interactive real time system and real time method of use thereof in conveyance industry segments |
US10607192B2 (en) | 2016-08-25 | 2020-03-31 | Ford Global Technologies, Llc | Methods and apparatus for autonomous vehicle scheduling |
US10460411B2 (en) | 2016-08-30 | 2019-10-29 | Uber Technologies, Inc. | Real-time resource management for on-demand services |
US10878025B1 (en) * | 2016-09-12 | 2020-12-29 | Omnyx, LLC | Field of view navigation tracking |
AU2017331458A1 (en) * | 2016-09-23 | 2019-04-18 | Operr Technologies, Inc. | System and method for customizable prescheduled dispatching for transportation services |
US10417727B2 (en) | 2016-09-26 | 2019-09-17 | Uber Technologies, Inc. | Network system to determine accelerators for selection of a service |
US20180088749A1 (en) * | 2016-09-26 | 2018-03-29 | Uber Technologies, Inc. | Customized content generation for a user interface for a network service |
US10477504B2 (en) * | 2016-09-26 | 2019-11-12 | Uber Technologies, Inc. | Network service over limited network connectivity |
US10002140B2 (en) | 2016-09-26 | 2018-06-19 | Uber Technologies, Inc. | Geographical location search using multiple data sources |
US9813510B1 (en) | 2016-09-26 | 2017-11-07 | Uber Technologies, Inc. | Network system to compute and transmit data based on predictive information |
US10425490B2 (en) * | 2016-09-26 | 2019-09-24 | Uber Technologies, Inc. | Service information and configuration user interface |
US9791291B1 (en) * | 2016-09-26 | 2017-10-17 | Uber Technologies, Inc. | Modifying map configurations based on established location points |
US10565279B2 (en) * | 2016-10-05 | 2020-02-18 | Uber Technologies, Inc. | Contextual search for location services |
US20180101878A1 (en) * | 2016-10-11 | 2018-04-12 | Gt Gettaxi Limited | System for navigating drivers to passengers based on arrival times and surge pricing information |
US10325442B2 (en) | 2016-10-12 | 2019-06-18 | Uber Technologies, Inc. | Facilitating direct rider driver pairing for mass egress areas |
US10417589B2 (en) * | 2016-11-01 | 2019-09-17 | Uber Technologies, Inc. | Pre-selection of drivers in a passenger transport system |
US11288716B1 (en) * | 2016-11-04 | 2022-03-29 | Jpmorgan Chase Bank, N.A. | Systems and methods for digital wallet transit payments |
USD868895S1 (en) | 2016-11-14 | 2019-12-03 | Lyft, Inc. | Electronic device with front and rear displays |
US20180144440A1 (en) * | 2016-11-23 | 2018-05-24 | Microsoft Technology Licensing, Llc | Providing Map Context |
US10963887B1 (en) | 2016-11-30 | 2021-03-30 | Square, Inc. | Utilizing proxy contact information for merchant communications |
US20180163991A1 (en) * | 2016-12-13 | 2018-06-14 | Haier Us Appliance Solutions, Inc. | Water Heater Appliance |
US10740822B1 (en) | 2016-12-19 | 2020-08-11 | Square, Inc. | Using data analysis to connect merchants |
US10641612B2 (en) * | 2016-12-19 | 2020-05-05 | Alpine Electronics, Inc. | Method and apparatus for correcting current position in navigation system via human-machine interface |
JP6841647B2 (en) * | 2016-12-20 | 2021-03-10 | シャープ株式会社 | Display device, display method and program |
SG11201805482PA (en) * | 2016-12-21 | 2018-07-30 | Meru Cab Company Private Ltd | System, method, and computer-readable medium for providing optimal dynamic content of a service to a user |
US11880788B1 (en) | 2016-12-23 | 2024-01-23 | Block, Inc. | Methods and systems for managing retail experience |
USD848463S1 (en) * | 2016-12-30 | 2019-05-14 | Lyft, Inc. | Display screen or portion thereof with graphical user interface |
US11574262B2 (en) | 2016-12-30 | 2023-02-07 | Lyft, Inc. | Location accuracy using local device communications |
USD848462S1 (en) * | 2016-12-30 | 2019-05-14 | Lyft, Inc. | Display screen or portion thereof with graphical user interface |
USD862506S1 (en) * | 2016-12-30 | 2019-10-08 | Lyft, Inc. | Display screen or portion thereof with graphical user interface |
US10554783B2 (en) * | 2016-12-30 | 2020-02-04 | Lyft, Inc. | Navigation using proximity information |
US10190886B2 (en) | 2017-01-04 | 2019-01-29 | Uber Technologies, Inc. | Network system to determine a route based on timing data |
US10355788B2 (en) | 2017-01-06 | 2019-07-16 | Uber Technologies, Inc. | Method and system for ultrasonic proximity service |
US10522043B2 (en) * | 2017-01-09 | 2019-12-31 | Satori Worldwide, Llc | Systems and methods for managing assets in a geographical location |
US10890457B2 (en) | 2017-01-13 | 2021-01-12 | Uber Technologies, Inc. | Method and system for repositioning a service location |
US20180211541A1 (en) | 2017-01-25 | 2018-07-26 | Via Transportation, Inc. | Prepositioning Empty Vehicles Based on Predicted Future Demand |
US9898791B1 (en) | 2017-02-14 | 2018-02-20 | Uber Technologies, Inc. | Network system to filter requests by destination and deadline |
US10371542B2 (en) | 2017-02-17 | 2019-08-06 | Uber Technologies, Inc. | System and methods for performing multivariate optimizations based on location data |
US20180242375A1 (en) * | 2017-02-17 | 2018-08-23 | Uber Technologies, Inc. | System and method to perform safety operations in association with a network service |
CA3055038A1 (en) * | 2017-02-20 | 2018-08-23 | Uber Technologies, Inc. | Service request matching based on provider compliance state |
US10293818B2 (en) | 2017-03-07 | 2019-05-21 | Uber Technologies, Inc. | Teleassistance data prioritization for self-driving vehicles |
US10803418B2 (en) | 2017-03-09 | 2020-10-13 | Square, Inc. | Provisioning temporary functionality to user devices |
US20180270605A1 (en) * | 2017-03-20 | 2018-09-20 | Satori Worldwide, Llc | System and method for providing location data over a messaging system |
US10445950B1 (en) | 2017-03-27 | 2019-10-15 | Uber Technologies, Inc. | Vehicle monitoring system |
US10402771B1 (en) | 2017-03-27 | 2019-09-03 | Uber Technologies, Inc. | System and method for evaluating drivers using sensor data from mobile computing devices |
US11023873B1 (en) | 2017-03-31 | 2021-06-01 | Square, Inc. | Resources for peer-to-peer messaging |
US11087412B1 (en) | 2017-03-31 | 2021-08-10 | Square, Inc. | Intelligent compensation management |
US10146769B2 (en) * | 2017-04-03 | 2018-12-04 | Uber Technologies, Inc. | Determining safety risk using natural language processing |
US9769616B1 (en) | 2017-04-04 | 2017-09-19 | Lyft, Inc. | Geohash-related location predictions |
US11416792B2 (en) | 2017-04-19 | 2022-08-16 | Uber Technologies, Inc. | Network system capable of grouping multiple service requests |
US10679312B2 (en) * | 2017-04-25 | 2020-06-09 | Lyft Inc. | Dynamic autonomous vehicle servicing and management |
US11087287B2 (en) | 2017-04-28 | 2021-08-10 | Uber Technologies, Inc. | System and method for generating event invitations to specified recipients |
US20180315088A1 (en) * | 2017-04-28 | 2018-11-01 | Uber Technologies, Inc. | Recommendation engine for generating context-specific recommendations |
US10495472B2 (en) | 2017-05-10 | 2019-12-03 | Lyft, Inc. | Dynamic geolocation optimization of pickup locations using location scores |
US10839695B2 (en) | 2017-05-11 | 2020-11-17 | Uber Technologies, Inc. | Network computer system to position service providers using provisioning level determinations |
SG11201707747WA (en) | 2017-05-12 | 2018-12-28 | Grabtaxi Holdings Pte Ltd | Optimal Allocation of Dynamically Batched Service Providers and Service Requesters |
US10701759B2 (en) | 2017-05-19 | 2020-06-30 | Uber Techologies, Inc. | Predictive location selection transportation optimization system |
US10628903B2 (en) | 2017-05-22 | 2020-04-21 | Uber Technologies, Inc. | Network computer system to implement counter values for arranging services |
US11295337B1 (en) | 2017-05-31 | 2022-04-05 | Block, Inc. | Transaction-based promotion campaign |
US11042901B1 (en) | 2017-05-31 | 2021-06-22 | Square, Inc. | Multi-channel distribution of digital items |
CA3029568A1 (en) * | 2017-06-01 | 2018-12-06 | Beijing Didi Infinity Technology And Development Co., Ltd. | Methods and systems for providing transportation service |
CN109086902B (en) * | 2017-06-14 | 2021-04-02 | 北京嘀嘀无限科技发展有限公司 | Processing method, processing apparatus, server, computer device, and storage medium |
US10515342B1 (en) | 2017-06-22 | 2019-12-24 | Square, Inc. | Referral candidate identification |
US10453056B2 (en) * | 2017-06-29 | 2019-10-22 | Square, Inc. | Secure account creation |
US10860968B1 (en) | 2017-06-29 | 2020-12-08 | DoorDash, Inc. | System management based on device information |
US20190019244A1 (en) * | 2017-07-17 | 2019-01-17 | Fawad Bangash | System and method to provide competitive bidding transportation services to a variety of customers |
US10697784B1 (en) * | 2017-07-19 | 2020-06-30 | BlueOwl, LLC | System and methods for assessment of rideshare trip |
CN107403062B (en) | 2017-07-25 | 2021-03-26 | 上海联影医疗科技股份有限公司 | Information processing method and device and electronic terminal |
EP3659078B1 (en) | 2017-07-26 | 2023-08-30 | Via Transportation, Inc. | Systems and methods for managing and routing ridesharing vehicles |
CA3071144A1 (en) * | 2017-08-01 | 2019-02-07 | Alexis DaCosta | An interactive real time system and real time method of use thereof in conveyance industry segments |
JP6274545B1 (en) * | 2017-08-10 | 2018-02-07 | フューネラル サービス ワーカーズ アカデミー,インク.Funeral service workers academy,Inc. | Mausoleum sleeping car dispatch server |
US10721327B2 (en) | 2017-08-11 | 2020-07-21 | Uber Technologies, Inc. | Dynamic scheduling system for planned service requests |
US10586222B1 (en) | 2017-08-24 | 2020-03-10 | Square, Inc. | Server-based order persistence and/or fulfillment |
US10990948B1 (en) | 2017-08-24 | 2021-04-27 | Square, Inc. | Server-based order persistence and/or fulfillment |
US10692374B2 (en) | 2017-08-25 | 2020-06-23 | Denise Lisa Salvucci | Automotive vehicle parking systems, methods, and apparatus |
US10508925B2 (en) | 2017-08-31 | 2019-12-17 | Uber Technologies, Inc. | Pickup location selection and augmented reality navigation |
US11257123B1 (en) | 2017-08-31 | 2022-02-22 | Square, Inc. | Pre-authorization techniques for transactions |
US10725473B2 (en) * | 2017-09-01 | 2020-07-28 | Uatc, Llc | Systems and methods for changing a destination of an autonomous vehicle in real-time |
AU2018326801B2 (en) | 2017-09-01 | 2023-07-13 | Put Corp. | Computerized applications for coordinating delivery data with mobile computing devices |
US11067410B2 (en) | 2017-09-07 | 2021-07-20 | Uber Technologies, Inc. | First-person perspective view |
US10567520B2 (en) | 2017-10-10 | 2020-02-18 | Uber Technologies, Inc. | Multi-user requests for service and optimizations thereof |
DE102017218854A1 (en) * | 2017-10-23 | 2019-04-25 | Audi Ag | Method for operating a motor vehicle and motor vehicle |
US11436554B2 (en) | 2017-11-02 | 2022-09-06 | Uber Technologies, Inc. | Network computer system to implement predictive time-based determinations for fulfilling delivery orders |
US10731998B2 (en) | 2017-11-05 | 2020-08-04 | Uber Technologies, Inc. | Network computer system to arrange pooled transport services |
US10706487B1 (en) | 2017-11-11 | 2020-07-07 | Lyft, Inc. | Dynamically generating and updating multipliers for a transportation matching system using machine learning |
WO2019113426A1 (en) * | 2017-12-08 | 2019-06-13 | Uber Technologies, Inc. | Coordinating transport through a common rendezvous location |
US10349223B1 (en) | 2017-12-14 | 2019-07-09 | Lyft, Inc. | Initiating transportation requests |
US10365783B2 (en) | 2017-12-29 | 2019-07-30 | Lyft, Inc. | Optimizing transportation networks through dynamic user interfaces |
US10264389B1 (en) * | 2017-12-31 | 2019-04-16 | Lyft, Inc. | Optimizing pickup locations for transportation requests based on context information |
US11073838B2 (en) | 2018-01-06 | 2021-07-27 | Drivent Llc | Self-driving vehicle systems and methods |
US10274950B1 (en) | 2018-01-06 | 2019-04-30 | Drivent Technologies Inc. | Self-driving vehicle systems and methods |
US10303181B1 (en) | 2018-11-29 | 2019-05-28 | Eric John Wengreen | Self-driving vehicle systems and methods |
US10299216B1 (en) | 2018-01-06 | 2019-05-21 | Eric John Wengreen | Self-driving vehicle actions in response to a low battery |
WO2019136341A1 (en) | 2018-01-08 | 2019-07-11 | Via Transportation, Inc. | Systems and methods for managing and scheduling ridesharing vehicles |
US20190279279A1 (en) * | 2018-02-13 | 2019-09-12 | Nishant Tomar | Systems and methods for identifying and hiring service providers |
US11308536B1 (en) * | 2018-03-19 | 2022-04-19 | DoorDash, Inc. | Managing item options for distribution efficiency |
JP7037762B2 (en) * | 2018-03-22 | 2022-03-17 | トヨタ自動車株式会社 | Information processing equipment and programs |
EP3776395A1 (en) | 2018-04-09 | 2021-02-17 | Via Transportation, Inc. | Systems and methods for planning transportation routes |
US20190320043A1 (en) * | 2018-04-13 | 2019-10-17 | Uber Technologies, Inc. | Network computer system to generate synthetic messages based on service-specific information |
DE112018007321T5 (en) * | 2018-04-18 | 2020-12-03 | Ford Global Technologies, Llc | DYNAMIC PROMOTIONAL PROMOTIONS BASED ON VEHICLE LOCATION AND ROUTING |
USD918930S1 (en) * | 2018-06-06 | 2021-05-11 | Lyft, Inc. | Display screen or portion thereof with a graphical user interface |
WO2020008282A1 (en) * | 2018-06-12 | 2020-01-09 | Volvo Car Corporation | Vehicle reservation systems with predictive adjustments |
US20210209525A1 (en) * | 2018-06-12 | 2021-07-08 | Volvo Car Corporation | Prediction-based vehicle reservation systems |
US10466057B1 (en) | 2018-07-30 | 2019-11-05 | Wesley Edward Schwie | Self-driving vehicle systems and methods |
US11861579B1 (en) | 2018-07-31 | 2024-01-02 | Block, Inc. | Intelligent inventory system |
US20200043073A1 (en) * | 2018-08-03 | 2020-02-06 | International Business Machines Corporation | Geolocation-capable physical-location recommendation engine |
USD950587S1 (en) | 2018-08-31 | 2022-05-03 | Zoox, Inc. | Display screen or portion thereof having a graphical user interface |
US11449917B2 (en) | 2018-09-05 | 2022-09-20 | Uber Technologies, Inc. | Network computing system for providing interactive menus and group recommendations |
US11769352B2 (en) * | 2018-09-06 | 2023-09-26 | Embraer S.A. | Smart and shared services platform |
US10552773B1 (en) | 2018-09-07 | 2020-02-04 | Lyft, Inc. | Efficiency of a transportation matching system using geocoded provider models |
US10223844B1 (en) | 2018-09-18 | 2019-03-05 | Wesley Edward Schwie | Self-driving vehicle systems and methods |
US10289922B1 (en) | 2018-09-18 | 2019-05-14 | Eric John Wengreen | System for managing lost, mislaid, or abandoned property in a self-driving vehicle |
US10493952B1 (en) | 2019-03-21 | 2019-12-03 | Drivent Llc | Self-driving vehicle systems and methods |
US10479319B1 (en) | 2019-03-21 | 2019-11-19 | Drivent Llc | Self-driving vehicle systems and methods |
US10471804B1 (en) | 2018-09-18 | 2019-11-12 | Drivent Llc | Self-driving vehicle systems and methods |
US10282625B1 (en) | 2018-10-01 | 2019-05-07 | Eric John Wengreen | Self-driving vehicle systems and methods |
US10900792B2 (en) | 2018-10-22 | 2021-01-26 | Drivent Llc | Self-driving vehicle systems and methods |
US11221622B2 (en) | 2019-03-21 | 2022-01-11 | Drivent Llc | Self-driving vehicle systems and methods |
US10794714B2 (en) | 2018-10-01 | 2020-10-06 | Drivent Llc | Self-driving vehicle systems and methods |
US11644833B2 (en) | 2018-10-01 | 2023-05-09 | Drivent Llc | Self-driving vehicle systems and methods |
US10832569B2 (en) | 2019-04-02 | 2020-11-10 | Drivent Llc | Vehicle detection systems |
US11210721B1 (en) | 2018-10-15 | 2021-12-28 | Square, Inc. | Converting items into vectors to determine optimized locations |
US10240938B1 (en) | 2018-10-22 | 2019-03-26 | Drivent Technologies Inc. | Self-driving vehicle systems and methods |
US11423340B2 (en) | 2018-10-29 | 2022-08-23 | Uber Technologies, Inc. | On-demand transport selection process facilitating third-party autonomous vehicles |
US10286908B1 (en) | 2018-11-01 | 2019-05-14 | Eric John Wengreen | Self-driving vehicle systems and methods |
US10474154B1 (en) | 2018-11-01 | 2019-11-12 | Drivent Llc | Self-driving vehicle systems and methods |
US11397911B2 (en) | 2018-11-15 | 2022-07-26 | Uber Technologies, Inc. | Network computer system to make effort-based determinations for delivery orders |
US10740615B2 (en) | 2018-11-20 | 2020-08-11 | Uber Technologies, Inc. | Mutual augmented reality experience for users in a network system |
US10867291B1 (en) | 2018-11-28 | 2020-12-15 | Square, Inc. | Remote association of permissions for performing an action |
US11537953B2 (en) * | 2018-11-29 | 2022-12-27 | Here Global B.V. | Method and apparatus for proactive booking of a shared vehicle |
US10878394B1 (en) | 2018-11-29 | 2020-12-29 | Square, Inc. | Intelligent inventory recommendations |
US11308476B1 (en) * | 2018-12-28 | 2022-04-19 | United Services Automobile Association (Usaa) | Proximity peer to peer mobile navigation system and method |
US11416850B1 (en) | 2018-12-28 | 2022-08-16 | United Services Automobile Association (Usaa) | Peer to peer navigation system and method |
US11047700B2 (en) | 2019-02-01 | 2021-06-29 | Uber Technologies, Inc. | Navigation and routing based on image data |
US10744976B1 (en) | 2019-02-04 | 2020-08-18 | Drivent Llc | Self-driving vehicle systems and methods |
US10377342B1 (en) | 2019-02-04 | 2019-08-13 | Drivent Technologies Inc. | Self-driving vehicle systems and methods |
US10640082B1 (en) * | 2019-02-11 | 2020-05-05 | Gm Cruise Holdings Llc | Child rider features for an autonomous vehicle |
US10575123B1 (en) | 2019-02-14 | 2020-02-25 | Uber Technologies, Inc. | Contextual notifications for a network-based service |
US10535201B1 (en) | 2019-02-15 | 2020-01-14 | Capital One Services, Llc | Utilizing machine learning to generate augmented reality vehicle information for a scale model of a vehicle |
US11493345B1 (en) * | 2019-02-15 | 2022-11-08 | State Farm Mutual Automobile Insurance Company | Systems and methods for dynamically generating optimal routes for vehicle delivery management |
US11910452B2 (en) | 2019-05-28 | 2024-02-20 | Lyft, Inc. | Automatically connecting wireless computing devices based on recurring wireless signal detections |
US11650064B2 (en) * | 2019-06-11 | 2023-05-16 | Ford Global Technologies, Llc | Systems and methods for fuel purchase decision assistance |
US20210004728A1 (en) * | 2019-07-05 | 2021-01-07 | Lyft, Inc. | Determining arrival of transportation providers to pickup locations utilizing a hiking distance predictor model |
US11887102B1 (en) | 2019-07-31 | 2024-01-30 | Block, Inc. | Temporary virtual payment card |
US11216770B2 (en) * | 2019-09-13 | 2022-01-04 | Uber Technologies, Inc. | Optimizing service requests in transport supply-constrained sub-regions |
US11681420B2 (en) * | 2019-12-13 | 2023-06-20 | Lyft, Inc. | Panel-snapping interface for responsive display of maps |
FR3106231B1 (en) * | 2020-01-14 | 2022-01-14 | Vulog | Method and system for displaying on a digital map, the geographical position of vehicles available for reservation |
US11570276B2 (en) | 2020-01-17 | 2023-01-31 | Uber Technologies, Inc. | Forecasting requests based on context data for a network-based service |
US11494517B2 (en) | 2020-02-12 | 2022-11-08 | Uber Technologies, Inc. | Computer system and device for controlling use of secure media recordings |
US11669786B2 (en) | 2020-02-14 | 2023-06-06 | Uber Technologies, Inc. | On-demand transport services |
US20210295224A1 (en) * | 2020-03-23 | 2021-09-23 | Lyft, Inc. | Utilizing a requestor device forecasting model with forward and backward looking queue filters to pre-dispatch provider devices |
US11830302B2 (en) | 2020-03-24 | 2023-11-28 | Uatc, Llc | Computer system for utilizing ultrasonic signals to implement operations for autonomous vehicles |
US11887386B1 (en) | 2020-03-30 | 2024-01-30 | Lyft, Inc. | Utilizing an intelligent in-cabin media capture device in conjunction with a transportation matching system |
US20210304078A1 (en) * | 2020-03-30 | 2021-09-30 | Lyft, Inc. | Utilizing contemporaneous transportation data from a transportation matching system to surface trending destinations in user interfaces |
USD997988S1 (en) | 2020-03-30 | 2023-09-05 | Lyft, Inc. | Transportation communication device |
DE102020205263A1 (en) | 2020-04-24 | 2021-10-28 | Volkswagen Aktiengesellschaft | Method for the electronic administration and checking of the availability of a service, as well as computer program product and electronic administration system |
JP7327282B2 (en) * | 2020-05-29 | 2023-08-16 | トヨタ自動車株式会社 | SERVER DEVICE, PROGRAM, AND OPERATION METHOD OF SERVER DEVICE |
US20210383296A1 (en) * | 2020-06-05 | 2021-12-09 | Lyft, Inc. | Systems and methods for enhanced transportation dispatch |
USD980247S1 (en) * | 2020-06-18 | 2023-03-07 | Zoox, Inc. | Display screen or portion thereof having an animated graphical user interface |
US20220005086A1 (en) * | 2020-07-06 | 2022-01-06 | ANI Technologies Private Limited | Performance assessment of drivers |
US20220122212A1 (en) * | 2020-10-21 | 2022-04-21 | Sameh Mosa Kryakos | Rideshare management method, device and mobile application with selectable driver programs |
US11638125B2 (en) * | 2021-01-15 | 2023-04-25 | Oshkosh Corporation | System and method for automatic generation of work site equipment groupings |
US20220327565A1 (en) * | 2021-04-07 | 2022-10-13 | Suol Innovations Ltd. | Method and system for improving predictions of demand for ride hailing services |
JP7447859B2 (en) * | 2021-04-13 | 2024-03-12 | トヨタ自動車株式会社 | Information processing device and information processing method |
US20230012948A1 (en) * | 2021-07-14 | 2023-01-19 | Hafez Omar Nesnas | Enhanced security ride services subscription delivery system |
US11429910B1 (en) | 2021-08-05 | 2022-08-30 | Transit Labs Inc. | Dynamic scheduling of driver breaks in a ride-sharing service |
US11488187B1 (en) * | 2022-04-11 | 2022-11-01 | Santa Israel Ltd. | Managing operations of mobile retail units |
Citations (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6356838B1 (en) * | 2000-07-25 | 2002-03-12 | Sunil Paul | System and method for determining an efficient transportation route |
US6519463B2 (en) * | 1996-02-28 | 2003-02-11 | Tendler Cellular, Inc. | Location based service request system |
US20040158483A1 (en) * | 2003-02-10 | 2004-08-12 | Lecouturier Jacques M. | Business and technological method for a flexible automobile sharing transit on demand |
US20050227704A1 (en) * | 2004-03-26 | 2005-10-13 | Joseph Ferra | Facilitating entering location data |
US20060034201A1 (en) * | 2004-07-28 | 2006-02-16 | Nobutoshi Umeda | Taxi dispatching system and dispatching method |
US20060059023A1 (en) * | 2002-08-02 | 2006-03-16 | Alex Mashinsky | Method system and apparatus for providing transportation services |
US20060094447A1 (en) * | 2000-12-19 | 2006-05-04 | Bellsouth Intellectual Property Corporation | System and method for using location information to execute an action |
US7064681B2 (en) * | 2003-05-28 | 2006-06-20 | Legalview Assets, Limited | Response systems and methods for notification systems |
US20060136254A1 (en) * | 2004-11-24 | 2006-06-22 | Mark Greenstein | System and method for dispatching transportation to persons who want transportation |
US20060155460A1 (en) * | 2005-01-08 | 2006-07-13 | Stephen Raney | Method for GPS carpool rendezvous tracking and personal safety verification |
US20060200306A1 (en) * | 2003-06-24 | 2006-09-07 | Maria Adamcyzk | Methods, systems and computer program products for ride matching based on current location information |
US20070103342A1 (en) * | 2005-07-06 | 2007-05-10 | Milleville Dan P | Dynamic Modification And Communication Of Routes For Transportation Vehicles |
US20070198276A1 (en) * | 2003-09-19 | 2007-08-23 | Andreas Hinrichs | System for procuring services |
US20080114629A1 (en) * | 2006-11-09 | 2008-05-15 | Yahoo! Inc. | System for matching users and transportation providers |
US20080125967A1 (en) * | 2006-11-24 | 2008-05-29 | Sprigg Stephen A | System and method for sending destination locations to navigation devices |
US20080189207A1 (en) * | 2007-02-02 | 2008-08-07 | Mach 9 Travel, Llc | System and Method of Transferring Reservations for Transportation Services |
US7412042B2 (en) * | 2003-02-14 | 2008-08-12 | Grape Technology Group, Inc. | Technique for providing information assistance including a concierge-type service |
US20080195428A1 (en) * | 2007-02-12 | 2008-08-14 | O'sullivan Sean | Shared transport system and service network |
US20080270019A1 (en) * | 2006-12-29 | 2008-10-30 | High Regard Software, Inc. | Systems and methods for enhancing private transportation |
US20090083111A1 (en) * | 2007-09-21 | 2009-03-26 | Bob Carr | Systems and Methods for Coordinating Transportation Between Riders and Volunteer Drivers |
US20090125228A1 (en) * | 2007-11-09 | 2009-05-14 | Research In Motion Limited | System and method for providing dynamic route information to users of wireless communications devices |
US20090156241A1 (en) * | 2007-12-14 | 2009-06-18 | Promptu Systems Corporation | Automatic Service Vehicle Hailing and Dispatch System and Method |
US20090177502A1 (en) * | 2008-01-08 | 2009-07-09 | Nick Doinoff | System for matching drivers with customers seeking to hire a driver |
US20090176508A1 (en) * | 2008-01-03 | 2009-07-09 | Lubeck Olaf M | Method for requesting transportation services |
US7561069B2 (en) * | 2003-11-12 | 2009-07-14 | Legalview Assets, Limited | Notification systems and methods enabling a response to change particulars of delivery or pickup |
US20090192851A1 (en) * | 2008-01-25 | 2009-07-30 | Bishop Paul L | Location-Based Transportation Management |
US20090216600A1 (en) * | 2008-02-27 | 2009-08-27 | Montiss Llc | Systems and methods for arranging a transport transaction |
US20090313077A1 (en) * | 2008-06-17 | 2009-12-17 | Wheeler Iv George Y | Consumer initiated, service provider direct dispatching system |
US20090326991A1 (en) * | 2008-06-27 | 2009-12-31 | E-Lantis Corporation | Gps and wireless integrated fleet management system and method |
US7756633B2 (en) * | 2007-05-11 | 2010-07-13 | Palo Alto Research Center Incorporated | System and method for security enhanced rideshare |
US8099085B2 (en) * | 2007-01-16 | 2012-01-17 | At&T Intellectual Property I, Lp | Method and system for communicating with users of wireless devices when approaching a predetermined destination |
US20120130627A1 (en) * | 2010-11-23 | 2012-05-24 | Islam Mohammad R | Taxi dispatch system |
Family Cites Families (182)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US2009101A (en) | 1932-08-19 | 1935-07-23 | Bendix Aviat Corp | Brake |
DE2332361C3 (en) * | 1973-06-26 | 1980-08-28 | Kienzle Apparate Gmbh, 7730 Villingen-Schwenningen | Electronic taximeter for line taxi system |
US5168451A (en) | 1987-10-21 | 1992-12-01 | Bolger John G | User responsive transit system |
US5043736B1 (en) | 1990-07-27 | 1994-09-06 | Cae Link Corp | Cellular position location system |
US5293642A (en) | 1990-12-19 | 1994-03-08 | Northern Telecom Limited | Method of locating a mobile station |
US5862244A (en) | 1995-07-13 | 1999-01-19 | Motorola, Inc. | Satellite traffic reporting system and methods |
US5930474A (en) | 1996-01-31 | 1999-07-27 | Z Land Llc | Internet organizer for accessing geographically and topically based information |
US6057831A (en) | 1996-08-14 | 2000-05-02 | Samsung Electronics Co., Ltd. | TV graphical user interface having cursor position indicator |
US6456852B2 (en) | 1997-01-08 | 2002-09-24 | Trafficmaster Usa, Inc. | Internet distributed real-time wireless location database |
IL123420A0 (en) | 1998-02-24 | 1998-09-24 | Jaffe Shai | Request dispatch system |
JP3046578B2 (en) | 1998-06-11 | 2000-05-29 | 株式会社ナムコ | Image generation device and information storage medium |
US6339745B1 (en) | 1998-10-13 | 2002-01-15 | Integrated Systems Research Corporation | System and method for fleet tracking |
US7412715B2 (en) | 1998-10-28 | 2008-08-12 | Samsung Electronics Co., Ltd. | Method and apparatus for displaying channel information and selecting channel on digital television |
US6754485B1 (en) | 1998-12-23 | 2004-06-22 | American Calcar Inc. | Technique for effectively providing maintenance and information to vehicles |
US6522342B1 (en) | 1999-01-27 | 2003-02-18 | Hughes Electronics Corporation | Graphical tuning bar for a multi-program data stream |
US20020194129A1 (en) * | 1999-04-08 | 2002-12-19 | Hitachi, Ltd. | IC card reader/writer |
JP2001084240A (en) * | 1999-09-13 | 2001-03-30 | Riosu Corp:Kk | System and method for predicting vehicle demand |
US6756913B1 (en) | 1999-11-01 | 2004-06-29 | Mourad Ben Ayed | System for automatically dispatching taxis to client locations |
US6591253B1 (en) | 1999-12-17 | 2003-07-08 | International Business Machines Corporation | Method and system for real time pricing of fine-grained resource purchases |
US8271316B2 (en) | 1999-12-17 | 2012-09-18 | Buzzmetrics Ltd | Consumer to business data capturing system |
US7434177B1 (en) | 1999-12-20 | 2008-10-07 | Apple Inc. | User interface for providing consolidation and access |
JP2001188996A (en) * | 2000-01-05 | 2001-07-10 | Nippon Kouatsu Electric Co | Taxi service management system |
US6516056B1 (en) * | 2000-01-07 | 2003-02-04 | Vesta Corporation | Fraud prevention system and method |
US20100005396A1 (en) | 2000-02-18 | 2010-01-07 | Nason D David | Method and system for controlling a comlementary user interface on a display surface |
US6697730B2 (en) | 2000-04-04 | 2004-02-24 | Georgia Tech Research Corp. | Communications and computing based urban transit system |
WO2001086492A1 (en) | 2000-05-05 | 2001-11-15 | Abm Industries Pty. Ltd. | End user to mobile service provider message exchange system based on proximity |
JP2002024659A (en) | 2000-07-06 | 2002-01-25 | Hitachi Ltd | Taxi dispatch reserving system |
AU2001276937A1 (en) | 2000-07-14 | 2002-01-30 | Sunil Paul | System and method for determining an efficient transportation route |
KR20000063909A (en) * | 2000-08-10 | 2000-11-06 | 기준성 | System For Processing Transportation Information Using Communication Network And Method Thereof |
WO2002015086A1 (en) | 2000-08-11 | 2002-02-21 | Tvx Internet Services, Inc. | Integrated system for differentiation and positioning of a commercial offering |
US20020034292A1 (en) * | 2000-08-22 | 2002-03-21 | Tuoriniemi Veijo M. | System and a method to match demand and supply based on geographical location derived from a positioning system |
GB2367979A (en) * | 2000-10-06 | 2002-04-17 | Wapacab Com Ltd | Mobile Service Request System |
US7552063B1 (en) | 2000-11-03 | 2009-06-23 | Quality Data Management, Inc. | Physician office viewpoint survey system and method |
US20090106124A1 (en) | 2000-12-08 | 2009-04-23 | Ping Yang | Method and apparatus for ordering and delivering of meals |
US20020095326A1 (en) | 2001-01-16 | 2002-07-18 | Interactive Voice Data Systems, Inc. | Automated and remotely operated vehicle dispatching, scheduling and tracking system |
US6456207B1 (en) * | 2001-02-20 | 2002-09-24 | John Yen | Intelligent taxi total service system |
US6446004B1 (en) | 2001-02-28 | 2002-09-03 | International Business Machines Corporation | System and method for implementing proximity or location driven activities |
US20020138338A1 (en) | 2001-03-23 | 2002-09-26 | Trauth Gregory L. | Customer complaint alert system and method |
US7542993B2 (en) | 2001-05-10 | 2009-06-02 | Equifax, Inc. | Systems and methods for notifying a consumer of changes made to a credit report |
US7082365B2 (en) | 2001-08-16 | 2006-07-25 | Networks In Motion, Inc. | Point of interest spatial rating search method and system |
US20030040944A1 (en) | 2001-08-22 | 2003-02-27 | Hileman Ryan M. | On-demand transportation system |
US7093201B2 (en) | 2001-09-06 | 2006-08-15 | Danger, Inc. | Loop menu navigation apparatus and method |
US7315780B2 (en) | 2001-09-20 | 2008-01-01 | Matsushita Electric Industrial Co., Ltd. | Guide system, guide apparatus, and radio apparatus which communicates with guide apparatus |
GB0126809D0 (en) | 2001-11-07 | 2002-01-02 | Isaac Stephen J | A car-sharing system |
GB2382203A (en) | 2001-11-20 | 2003-05-21 | Hewlett Packard Co | Alerting users to impending events |
US6973384B2 (en) | 2001-12-06 | 2005-12-06 | Bellsouth Intellectual Property Corporation | Automated location-intelligent traffic notification service systems and methods |
US6804658B2 (en) | 2001-12-14 | 2004-10-12 | Delta Air Lines, Inc. | Method and system for origin-destination passenger demand forecast inference |
ES2355076T3 (en) | 2002-03-01 | 2011-03-22 | Telecommunication Systems, Inc. | PROCEDURE AND APPLIANCE FOR SENDING, RECOVERING AND PLANNING RELEVANT INFORMATION FOR THE LOCATION. |
EP2463627B1 (en) | 2002-04-30 | 2017-07-19 | Intel Corporation | Navigation system using corridor maps |
TWI238348B (en) | 2002-05-13 | 2005-08-21 | Kyocera Corp | Portable information terminal, display control device, display control method, and recording media |
AU2003243646A1 (en) | 2002-06-21 | 2004-01-06 | Nuride, Inc. | System and method for facilitating ridesharing |
US7466811B2 (en) | 2002-06-21 | 2008-12-16 | Verizon Business Global Llc | Method and system for automatic update of a location profile |
CN100335808C (en) | 2002-07-26 | 2007-09-05 | 利滕斯汽车公司 | Overrunning alternator decoupler pulley with bare wire spring and grease lubrication |
JP4300767B2 (en) | 2002-08-05 | 2009-07-22 | ソニー株式会社 | Guide system, content server, portable device, information processing method, information processing program, and storage medium |
JP2004157698A (en) | 2002-11-06 | 2004-06-03 | Nec Corp | Taxi service system, mobile terminal and taxi service method and program used for them |
KR20040050957A (en) * | 2002-12-11 | 2004-06-18 | 씨엔씨엔터프라이즈 주식회사 | Terminal for collecting taxi fare and providing additional services |
ATE492085T1 (en) * | 2003-01-28 | 2011-01-15 | Cellport Systems Inc | A SYSTEM AND METHOD FOR CONTROLLING APPLICATIONS' ACCESS TO PROTECTED RESOURCES WITHIN A SECURE VEHICLE TELEMATICS SYSTEM |
GB0302886D0 (en) * | 2003-02-07 | 2003-03-12 | Faith Jonathan D | Transportation ordering system |
JP2004295159A (en) | 2003-02-07 | 2004-10-21 | Sony Corp | Icon display system and method, electronic equipment, and computer program |
US20040260470A1 (en) | 2003-06-14 | 2004-12-23 | Rast Rodger H. | Conveyance scheduling and logistics system |
US7676534B2 (en) | 2003-06-27 | 2010-03-09 | Tohru Nishioka | Coordinate mutual converting module |
KR20050015772A (en) * | 2003-08-07 | 2005-02-21 | 현대자동차주식회사 | System for settling taxi fare and method for controlling the same |
US6990637B2 (en) | 2003-10-23 | 2006-01-24 | Microsoft Corporation | Graphical user interface for 3-dimensional view of a data collection based on an attribute of the data |
US20050149382A1 (en) | 2003-12-24 | 2005-07-07 | Fenner John D. | Method for administering a survey, collecting, analyzing and presenting customer satisfaction feedback |
US7672677B2 (en) | 2004-01-16 | 2010-03-02 | Compasscom Software Corporation | Method and system to transfer and to display location information about an object |
US20050240512A1 (en) | 2004-02-18 | 2005-10-27 | Nacenters, Inc. | Method and system for identifying auction items in a graphical location |
US7395140B2 (en) | 2004-02-27 | 2008-07-01 | Union Switch & Signal, Inc. | Geographic information system and method for monitoring dynamic train positions |
US7385529B2 (en) * | 2004-06-14 | 2008-06-10 | Fittipaldi Logistics, Inc. | Dynamic and predictive information system and method for shipping assets and transport |
US20050278114A1 (en) | 2004-06-15 | 2005-12-15 | Ahmad Ahmad M | Method and system for selecting destinations |
US8028250B2 (en) | 2004-08-31 | 2011-09-27 | Microsoft Corporation | User interface having a carousel view for representing structured data |
US20060149681A1 (en) | 2004-12-04 | 2006-07-06 | Meisner Philip H | Method and system for the process of music creation, development, and distribution |
US20110208732A1 (en) | 2010-02-24 | 2011-08-25 | Apple Inc. | Systems and methods for organizing data items |
US20060178949A1 (en) | 2005-02-07 | 2006-08-10 | Mcgrath Paul T | Integrated system and method for inducing, brokering and managing alternative transportation modes for commuters and generating commute statistics |
US7394386B2 (en) | 2005-03-03 | 2008-07-01 | Motorola, Inc. | Location signaling for transport system |
US8370054B2 (en) * | 2005-03-24 | 2013-02-05 | Google Inc. | User location driven identification of service vehicles |
CA2607123A1 (en) | 2005-05-02 | 2006-12-07 | Ecolane Finland Oy | Method and arrangement for arranging practical aspects of a demand responsive transport system |
US20060271867A1 (en) | 2005-05-27 | 2006-11-30 | Wang Kong Q | Mobile communications terminal and method therefore |
US7797641B2 (en) | 2005-05-27 | 2010-09-14 | Nokia Corporation | Mobile communications terminal and method therefore |
US7487467B1 (en) | 2005-06-23 | 2009-02-03 | Sun Microsystems, Inc. | Visual representation and other effects for application management on a device with a small screen |
AU2005203074A1 (en) | 2005-07-14 | 2007-02-01 | Canon Information Systems Research Australia Pty Ltd | Image browser |
WO2007012198A1 (en) | 2005-07-26 | 2007-02-01 | Macdonald, Dettwiler & Associates Inc. | Guidance, navigation, and control system for a vehicle |
US8024112B2 (en) | 2005-09-29 | 2011-09-20 | Microsoft Corporation | Methods for predicting destinations from partial trajectories employing open-and closed-world modeling methods |
WO2007056450A2 (en) | 2005-11-07 | 2007-05-18 | Google Inc. | Local search and mapping for mobile devices |
US20070130153A1 (en) | 2005-12-02 | 2007-06-07 | Palm, Inc. | Techniques to communicate and process location information from communications networks on a mobile computing device |
US20140172727A1 (en) | 2005-12-23 | 2014-06-19 | Raj V. Abhyanker | Short-term automobile rentals in a geo-spatial environment |
US7667646B2 (en) | 2006-02-21 | 2010-02-23 | Nokia Corporation | System and methods for direction finding using a handheld device |
EP1990789A1 (en) | 2006-02-27 | 2008-11-12 | Navitime Japan Co., Ltd. | Map display system, method of inputting conditions for searching for poi, method of displaying guidance to poi, and terminal device |
US8989778B2 (en) | 2006-06-01 | 2015-03-24 | Green Dot Corporation | Secure and private location sharing for location-aware mobile communication devices |
US8626136B2 (en) | 2006-06-29 | 2014-01-07 | Microsoft Corporation | Architecture for user- and context-specific prefetching and caching of information on portable devices |
US8140256B1 (en) | 2006-08-16 | 2012-03-20 | University Of South Florida | Dynamic ride matching system |
US8832575B2 (en) | 2006-09-26 | 2014-09-09 | Core Wireless Licensing S.A.R.L | Speed dependent displaying of information items in a graphical user interface |
US7673251B1 (en) | 2006-10-02 | 2010-03-02 | Adobe Systems, Incorporated | Panel presentation |
US7751971B2 (en) | 2007-01-17 | 2010-07-06 | Microsoft Corporation | Location mapping for key-point based services |
KR101496451B1 (en) | 2007-01-19 | 2015-03-05 | 엘지전자 주식회사 | Terminal and Method for Scroll Bar Using the Same |
US20080307512A1 (en) | 2007-05-26 | 2008-12-11 | Pankaj Tandon | Property Centric Real Estate Maps with Personalized Points of Interest |
US8315795B2 (en) | 2007-05-30 | 2012-11-20 | Navitime Japan Co., Ltd. | Map display system, map display, and map display method |
US20090030885A1 (en) | 2007-07-26 | 2009-01-29 | Ridecharge | Method and system for on-demand and scheduled services relating to travel and transportation |
JPWO2009016693A1 (en) | 2007-07-27 | 2010-10-07 | 株式会社ナビタイムジャパン | Map display system, map display device, and map display method |
US9009210B2 (en) * | 2007-08-15 | 2015-04-14 | Sony Corporation | Distribution of multimedia files using a transportation provider wireless device |
US20090099971A1 (en) * | 2007-10-10 | 2009-04-16 | Oneway Llc. | Methods and systems for marketing distressed inventory |
US8775938B2 (en) | 2007-10-19 | 2014-07-08 | Microsoft Corporation | Presentation of user interface content via media player |
JP2009154647A (en) | 2007-12-26 | 2009-07-16 | Aisin Aw Co Ltd | Multi-screen display and program of the same |
JP5034931B2 (en) | 2007-12-26 | 2012-09-26 | ソニー株式会社 | Display device, program, and recording medium |
KR20090071076A (en) | 2007-12-27 | 2009-07-01 | 엘지전자 주식회사 | Navigation apparatus and method for providing information of poi(position of interest) |
US8355862B2 (en) | 2008-01-06 | 2013-01-15 | Apple Inc. | Graphical user interface for presenting location information |
EP2078928A1 (en) | 2008-01-09 | 2009-07-15 | Wayfinder Systems AB | Method and device for presenting information associated to geographical data |
US20090254270A1 (en) * | 2008-04-02 | 2009-10-08 | O2Micro, Inc. | System and method for tracking a path of a vehicle |
KR101033006B1 (en) | 2008-04-14 | 2011-05-09 | 주식회사 한국스마트카드 | Business Taxi card service system |
US8856671B2 (en) | 2008-05-11 | 2014-10-07 | Navteq B.V. | Route selection by drag and drop |
US9596359B2 (en) | 2008-06-26 | 2017-03-14 | Visa International Service Association | Mobile communication device configured for transit application |
US8386593B1 (en) | 2008-07-17 | 2013-02-26 | NetBrain Technologies Inc. | Computer aided network engineering system, apparatus, and method |
US20110137699A1 (en) | 2008-08-05 | 2011-06-09 | Ronen Ben-Ari | Method and system for cab management |
US20100070334A1 (en) | 2008-09-08 | 2010-03-18 | Dante Monteverde | Method and system for location-based mobile device predictive services |
US20100076988A1 (en) | 2008-09-10 | 2010-03-25 | Expanse Networks, Inc. | Masked Data Service Profiling |
US9159238B2 (en) | 2008-10-02 | 2015-10-13 | Microsoft Technology Licensing, LLP | Location-aware selection of public transportation |
KR20100050103A (en) | 2008-11-05 | 2010-05-13 | 엘지전자 주식회사 | Method of controlling 3 dimension individual object on map and mobile terminal using the same |
US20100121689A1 (en) | 2008-11-12 | 2010-05-13 | Wallace Collin D | System and method for wireless ordering in a venue |
US8771066B2 (en) | 2008-11-13 | 2014-07-08 | Wms Gaming, Inc. | Configuring and controlling wagering game presentations |
US20100153292A1 (en) | 2008-12-11 | 2010-06-17 | Microsoft Corporation | Making Friend and Location Recommendations Based on Location Similarities |
KR101569776B1 (en) | 2009-01-09 | 2015-11-19 | 삼성전자주식회사 | Foldable Display Device And Operation Method thereof |
US8364389B2 (en) | 2009-02-02 | 2013-01-29 | Apple Inc. | Systems and methods for integrating a portable electronic device with a bicycle |
US8935112B2 (en) | 2009-02-17 | 2015-01-13 | Chargepoint, Inc. | System and method for managing electric vehicles |
US20100228415A1 (en) | 2009-03-05 | 2010-09-09 | Sunil Paul | System and method for reducing the cost of efficient vehicles |
US20100243724A1 (en) | 2009-03-30 | 2010-09-30 | Solomon K Golla | Payment Apparatus for a Personal Transportation System |
US9241062B2 (en) | 2009-05-20 | 2016-01-19 | Citrix Systems, Inc. | Methods and systems for using external display devices with a mobile computing device |
US20120327009A1 (en) | 2009-06-07 | 2012-12-27 | Apple Inc. | Devices, methods, and graphical user interfaces for accessibility using a touch-sensitive surface |
SG176725A1 (en) | 2009-06-08 | 2012-01-30 | Zipcar Inc | Mobile device application for communicating with vehicles |
CA2708444C (en) * | 2009-07-09 | 2017-09-26 | Mathieu Audet | Method for communicating and repartitioning vehicles |
NO331246B1 (en) | 2009-07-31 | 2011-11-07 | Trond Paulsen | Taxi booking method and system |
US20120131170A1 (en) * | 2009-08-21 | 2012-05-24 | William John Spat | System and method for fulfilling requests using a mobile device |
US8363020B2 (en) | 2009-08-27 | 2013-01-29 | Symbol Technologies, Inc. | Methods and apparatus for pressure-based manipulation of content on a touch screen |
KR101068542B1 (en) | 2009-08-31 | 2011-09-28 | 주식회사 뉴로스 | Journal foil air bearing |
US20110060600A1 (en) * | 2009-09-10 | 2011-03-10 | Transittix, Llc | Systems and Methods For Tracking the Transportation of Passengers |
EP3855297A3 (en) | 2009-09-22 | 2021-10-27 | Apple Inc. | Device method and graphical user interface for manipulating user interface objects |
US10325316B2 (en) | 2009-10-02 | 2019-06-18 | Trade Capture, Otc Corp. | Method and apparatus of displaying market depth and other information on a mobile phone, handheld device or computer system |
US9595300B2 (en) | 2009-10-21 | 2017-03-14 | Media Ip, Llc | Contextual chapter navigation |
US10002198B2 (en) * | 2009-10-28 | 2018-06-19 | Verizon Patent And Licensing Inc. | Mobile taxi dispatch system |
WO2011066327A1 (en) | 2009-11-25 | 2011-06-03 | Cubic Corporation | Mobile wireless payment and access |
US9230292B2 (en) | 2012-11-08 | 2016-01-05 | Uber Technologies, Inc. | Providing on-demand services through use of portable computing devices |
WO2011069170A1 (en) | 2009-12-04 | 2011-06-09 | Uber, Inc. | System and method for arranging transport amongst parties through use of mobile devices |
CA2696345C (en) | 2009-12-04 | 2016-12-20 | 3Pd Inc. | Automated survey system |
US20110153453A1 (en) | 2009-12-18 | 2011-06-23 | Gameelah Ghafoor | Transport allocation and payment system, method and software |
US8483962B2 (en) | 2009-12-21 | 2013-07-09 | Entertainment Machine Operator | Method for providing route information and the system thereof |
US8699991B2 (en) | 2010-01-20 | 2014-04-15 | Nokia Corporation | Method and apparatus for customizing map presentations based on mode of transport |
US8838586B2 (en) | 2010-03-05 | 2014-09-16 | Apple Inc. | Relevancy ranking for map-related search |
US8725706B2 (en) | 2010-03-26 | 2014-05-13 | Nokia Corporation | Method and apparatus for multi-item searching |
EP2556335A2 (en) | 2010-04-08 | 2013-02-13 | Way Better Ltd. | Public transport optimization |
US8554608B1 (en) | 2010-04-17 | 2013-10-08 | James O'Connor | Driver controlled automated taxi service and devices |
US9582166B2 (en) | 2010-05-16 | 2017-02-28 | Nokia Technologies Oy | Method and apparatus for rendering user interface for location-based service having main view portion and preview portion |
US20110313880A1 (en) * | 2010-05-24 | 2011-12-22 | Sunil Paul | System and method for selecting transportation resources |
US20120041675A1 (en) | 2010-08-10 | 2012-02-16 | Steven Juliver | Method and System for Coordinating Transportation Service |
KR101006599B1 (en) | 2010-08-10 | 2011-01-07 | 에스케이네트웍스 주식회사 | Total cars management service system for companies and institutes and cars management method therefor |
CN102402852A (en) | 2010-09-19 | 2012-04-04 | 浙江易商科技有限公司 | Taxi interaction lattice application system combined with electronic map |
US9241000B2 (en) | 2010-09-22 | 2016-01-19 | Abdullah Celik Erdal | Trusted social network |
WO2012044713A1 (en) | 2010-10-01 | 2012-04-05 | Imerj LLC | Drag/flick gestures in user interface |
US8275508B1 (en) | 2011-03-03 | 2012-09-25 | Telogis, Inc. | History timeline display for vehicle fleet management |
US20130132246A1 (en) | 2010-12-06 | 2013-05-23 | Uber Technologies, Inc. | Providing a summary or receipt for on-demand services through use of portable computing devices |
US20130132887A1 (en) | 2010-12-06 | 2013-05-23 | Uber Technologies, Inc. | Transitioning user interface features for on-demand services through use of portable computing devices |
KR20120090445A (en) | 2011-02-08 | 2012-08-17 | 삼성전자주식회사 | Method and apparatus for providing safety taxi service |
US8442848B2 (en) | 2011-03-09 | 2013-05-14 | David Myr | Automatic optimal taxicab mobile location based dispatching system |
US20120239452A1 (en) | 2011-03-17 | 2012-09-20 | Aarjav Trivedi | Fleet Management Systems and Processes |
GB201106555D0 (en) | 2011-04-19 | 2011-06-01 | Tomtom Int Bv | Taxi dispatching system |
US20120330778A1 (en) | 2011-05-23 | 2012-12-27 | Garrett Eastham | Product comparison and feature discovery |
JP5747673B2 (en) | 2011-06-10 | 2015-07-15 | ソニー株式会社 | Information processing apparatus, information processing method, and program |
US20130041720A1 (en) | 2011-08-12 | 2013-02-14 | Collin Richard SPIRES | System and method for real-time satisfaction survey feedback |
US20130050131A1 (en) | 2011-08-23 | 2013-02-28 | Garmin Switzerland Gmbh | Hover based navigation user interface control |
CN102496265B (en) | 2011-11-29 | 2013-12-11 | 杭州妙影微电子有限公司 | Taxi calling and carpooling method based on mobile terminal and system thereof |
US8836698B2 (en) | 2011-12-26 | 2014-09-16 | TrackThings LLC | Method and apparatus for identifying a 3-D object from a 2-D display of a portable unit |
US8660861B2 (en) | 2012-01-24 | 2014-02-25 | Fmr Llc | Allocation of financial incentives for employee wellness programs |
US20130204676A1 (en) | 2012-01-26 | 2013-08-08 | Flywheel Software, Inc. | Method and system for dynamically categorizing service providers |
US20130246207A1 (en) * | 2012-03-19 | 2013-09-19 | Uber Technologies, Inc. | System and method for dynamically adjusting prices for services |
US20130282602A1 (en) | 2012-04-18 | 2013-10-24 | Yingjie Wang | TaxiZag |
US20130290040A1 (en) | 2012-04-25 | 2013-10-31 | Alexander Perry | Method and System for Arranging Taxi and Transportation Services |
CN102682593B (en) | 2012-05-04 | 2014-07-16 | 舒方硕 | Intelligent system and method for managing and scheduling taxis |
US20140047346A1 (en) | 2012-08-13 | 2014-02-13 | TollShare, Inc. | User interface elements for transportation sharing |
US20140067491A1 (en) | 2012-08-30 | 2014-03-06 | Frias Transportation Infrastructure Llc | Transportation control and regulation system and method for for-hire vehicles |
US9671233B2 (en) | 2012-11-08 | 2017-06-06 | Uber Technologies, Inc. | Dynamically providing position information of a transit object to a computing device |
US20140129302A1 (en) | 2012-11-08 | 2014-05-08 | Uber Technologies, Inc. | Providing a confirmation interface for on-demand services through use of portable computing devices |
US20140180732A1 (en) | 2012-12-21 | 2014-06-26 | Blackjet, Inc. | System And Method For Arranging Aggregated Unscheduled Transport Service |
US20140180733A1 (en) | 2012-12-21 | 2014-06-26 | Blackjet, Inc. | System And Method For Arranging Aggregated Unscheduled Transport Service |
SG11201510767XA (en) | 2013-07-03 | 2016-01-28 | Uber Technologies Inc | System and method for splitting a fee for an on-demand service |
WO2018066074A1 (en) | 2016-10-04 | 2018-04-12 | 三菱電機株式会社 | Information processing device, information processing method, and information processing program |
-
2010
- 2010-12-06 WO PCT/US2010/059152 patent/WO2011069170A1/en active Application Filing
- 2010-12-06 AU AU2010325793A patent/AU2010325793B2/en active Active
- 2010-12-06 US US12/928,254 patent/US9959512B2/en active Active
- 2010-12-06 EP EP10835261.8A patent/EP2507753A4/en not_active Ceased
- 2010-12-06 EP EP19165275.9A patent/EP3522081A1/en not_active Withdrawn
- 2010-12-06 CA CA2782611A patent/CA2782611C/en active Active
- 2010-12-06 US US12/961,493 patent/US20110313804A1/en not_active Abandoned
- 2010-12-06 US US12/928,253 patent/US20110307282A1/en not_active Abandoned
-
2012
- 2012-08-28 US US13/596,497 patent/US20120323642A1/en not_active Abandoned
- 2012-11-08 US US13/672,658 patent/US20130132140A1/en not_active Abandoned
-
2017
- 2017-07-10 US US15/645,874 patent/US20170316359A1/en not_active Abandoned
-
2018
- 2018-03-23 US US15/933,975 patent/US11068811B2/en active Active
-
2019
- 2019-01-14 US US16/247,246 patent/US20190220788A1/en not_active Abandoned
-
2021
- 2021-06-24 US US17/357,375 patent/US20210319380A1/en active Pending
Patent Citations (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6519463B2 (en) * | 1996-02-28 | 2003-02-11 | Tendler Cellular, Inc. | Location based service request system |
US6356838B1 (en) * | 2000-07-25 | 2002-03-12 | Sunil Paul | System and method for determining an efficient transportation route |
US20060094447A1 (en) * | 2000-12-19 | 2006-05-04 | Bellsouth Intellectual Property Corporation | System and method for using location information to execute an action |
US20060059023A1 (en) * | 2002-08-02 | 2006-03-16 | Alex Mashinsky | Method system and apparatus for providing transportation services |
US20040158483A1 (en) * | 2003-02-10 | 2004-08-12 | Lecouturier Jacques M. | Business and technological method for a flexible automobile sharing transit on demand |
US7412042B2 (en) * | 2003-02-14 | 2008-08-12 | Grape Technology Group, Inc. | Technique for providing information assistance including a concierge-type service |
US7064681B2 (en) * | 2003-05-28 | 2006-06-20 | Legalview Assets, Limited | Response systems and methods for notification systems |
US20060200306A1 (en) * | 2003-06-24 | 2006-09-07 | Maria Adamcyzk | Methods, systems and computer program products for ride matching based on current location information |
US20070198276A1 (en) * | 2003-09-19 | 2007-08-23 | Andreas Hinrichs | System for procuring services |
US7561069B2 (en) * | 2003-11-12 | 2009-07-14 | Legalview Assets, Limited | Notification systems and methods enabling a response to change particulars of delivery or pickup |
US20050227704A1 (en) * | 2004-03-26 | 2005-10-13 | Joseph Ferra | Facilitating entering location data |
US20060034201A1 (en) * | 2004-07-28 | 2006-02-16 | Nobutoshi Umeda | Taxi dispatching system and dispatching method |
US20060136254A1 (en) * | 2004-11-24 | 2006-06-22 | Mark Greenstein | System and method for dispatching transportation to persons who want transportation |
US20060155460A1 (en) * | 2005-01-08 | 2006-07-13 | Stephen Raney | Method for GPS carpool rendezvous tracking and personal safety verification |
US20070103342A1 (en) * | 2005-07-06 | 2007-05-10 | Milleville Dan P | Dynamic Modification And Communication Of Routes For Transportation Vehicles |
US20080114629A1 (en) * | 2006-11-09 | 2008-05-15 | Yahoo! Inc. | System for matching users and transportation providers |
US20080125967A1 (en) * | 2006-11-24 | 2008-05-29 | Sprigg Stephen A | System and method for sending destination locations to navigation devices |
US20080270019A1 (en) * | 2006-12-29 | 2008-10-30 | High Regard Software, Inc. | Systems and methods for enhancing private transportation |
US8099085B2 (en) * | 2007-01-16 | 2012-01-17 | At&T Intellectual Property I, Lp | Method and system for communicating with users of wireless devices when approaching a predetermined destination |
US20080189207A1 (en) * | 2007-02-02 | 2008-08-07 | Mach 9 Travel, Llc | System and Method of Transferring Reservations for Transportation Services |
US20080195428A1 (en) * | 2007-02-12 | 2008-08-14 | O'sullivan Sean | Shared transport system and service network |
US7756633B2 (en) * | 2007-05-11 | 2010-07-13 | Palo Alto Research Center Incorporated | System and method for security enhanced rideshare |
US20090083111A1 (en) * | 2007-09-21 | 2009-03-26 | Bob Carr | Systems and Methods for Coordinating Transportation Between Riders and Volunteer Drivers |
US20090125228A1 (en) * | 2007-11-09 | 2009-05-14 | Research In Motion Limited | System and method for providing dynamic route information to users of wireless communications devices |
US20090156241A1 (en) * | 2007-12-14 | 2009-06-18 | Promptu Systems Corporation | Automatic Service Vehicle Hailing and Dispatch System and Method |
US20090176508A1 (en) * | 2008-01-03 | 2009-07-09 | Lubeck Olaf M | Method for requesting transportation services |
US20090177502A1 (en) * | 2008-01-08 | 2009-07-09 | Nick Doinoff | System for matching drivers with customers seeking to hire a driver |
US20090192851A1 (en) * | 2008-01-25 | 2009-07-30 | Bishop Paul L | Location-Based Transportation Management |
US20090216600A1 (en) * | 2008-02-27 | 2009-08-27 | Montiss Llc | Systems and methods for arranging a transport transaction |
US20090313077A1 (en) * | 2008-06-17 | 2009-12-17 | Wheeler Iv George Y | Consumer initiated, service provider direct dispatching system |
US20090326991A1 (en) * | 2008-06-27 | 2009-12-31 | E-Lantis Corporation | Gps and wireless integrated fleet management system and method |
US20120130627A1 (en) * | 2010-11-23 | 2012-05-24 | Islam Mohammad R | Taxi dispatch system |
Cited By (155)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9949060B2 (en) | 2010-07-21 | 2018-04-17 | Sensoriant, Inc. | System allowing or disallowing access to resources based on sensor and state information |
US10405157B2 (en) | 2010-07-21 | 2019-09-03 | Sensoriant, Inc. | System and method for provisioning user computing devices based on sensor and state information |
US10104518B2 (en) | 2010-07-21 | 2018-10-16 | Sensoriant, Inc. | System and method for provisioning user computing devices based on sensor and state information |
US9635545B2 (en) | 2010-07-21 | 2017-04-25 | Sensoriant, Inc. | System and method for controlling mobile services using sensor information |
US9681254B2 (en) | 2010-07-21 | 2017-06-13 | Sensoriant, Inc. | System and method for control and management of resources for consumers of information |
US9686630B2 (en) | 2010-07-21 | 2017-06-20 | Sensoriant, Inc. | System and method for control and management of resources for consumers of information |
US9930522B2 (en) | 2010-07-21 | 2018-03-27 | Sensoriant, Inc. | System and method for controlling mobile services using sensor information |
US9715707B2 (en) | 2010-07-21 | 2017-07-25 | Sensoriant, Inc. | System and method for control and management of resources for consumers of information |
US9913071B2 (en) | 2010-07-21 | 2018-03-06 | Sensoriant, Inc. | Controlling functions of a user device utilizing an environment map |
US10602314B2 (en) | 2010-07-21 | 2020-03-24 | Sensoriant, Inc. | System and method for controlling mobile services using sensor information |
US9763023B2 (en) | 2010-07-21 | 2017-09-12 | Sensoriant, Inc. | System and method for control and management of resources for consumers of information |
US9913069B2 (en) | 2010-07-21 | 2018-03-06 | Sensoriant, Inc. | System and method for provisioning user computing devices based on sensor and state information |
US11140516B2 (en) | 2010-07-21 | 2021-10-05 | Sensoriant, Inc. | System and method for controlling mobile services using sensor information |
US9913070B2 (en) | 2010-07-21 | 2018-03-06 | Sensoriant, Inc. | Allowing or disallowing access to resources based on sensor and state information |
US9730232B2 (en) | 2010-07-21 | 2017-08-08 | Sensoriant, Inc. | System and method for control and management of resources for consumers of information |
US20130317945A1 (en) * | 2011-02-18 | 2013-11-28 | Doleweerd Consulting Inc. | Browser based mapping region builder |
US8442848B2 (en) * | 2011-03-09 | 2013-05-14 | David Myr | Automatic optimal taxicab mobile location based dispatching system |
US20120232943A1 (en) * | 2011-03-09 | 2012-09-13 | Makor Issues And Rights Ltd. | Automatic optimal taxicab mobile location based dispatching system |
US8473326B1 (en) * | 2011-03-23 | 2013-06-25 | Amazon Technologies, Inc. | Courier management |
US9618353B2 (en) * | 2011-04-19 | 2017-04-11 | Tomtom International B.V. | Vehicle request device |
US20140051465A1 (en) * | 2011-04-19 | 2014-02-20 | Godert Otto Anthony Ruys | Vehicle request device |
US10068222B2 (en) | 2011-05-03 | 2018-09-04 | Verifone, Inc. | Mobile commerce system |
US9053478B2 (en) | 2011-05-03 | 2015-06-09 | Verifone, Inc. | Mobile commerce system |
US11532222B2 (en) | 2011-06-22 | 2022-12-20 | Thinkware Corporation | Safety service system and method thereof |
US11017650B2 (en) | 2011-06-22 | 2021-05-25 | Thinkware Corporation | Safety service system and method thereof |
US11217078B2 (en) | 2011-06-22 | 2022-01-04 | Thinkware Corporation | Safety service system and method thereof |
US11436907B2 (en) | 2011-06-22 | 2022-09-06 | Thinkware Corporation | Safety service system and method thereof |
US10438146B2 (en) | 2011-09-20 | 2019-10-08 | Metrobee, Llc | Roaming transport distribution management system |
US10055804B2 (en) | 2011-09-20 | 2018-08-21 | Metrobee, Llc | Roaming transport distribution management system |
US20130085817A1 (en) * | 2011-09-29 | 2013-04-04 | Michael Collins Pinkus | Discount offer system and method for use with for hire vehicles |
US20130090957A1 (en) * | 2011-10-05 | 2013-04-11 | Robert Popkey | Waiting line transaction management system and method |
US9785920B2 (en) | 2012-01-18 | 2017-10-10 | Square, Inc. | Acquisition of card information to enhance user experience |
US9824504B2 (en) | 2012-01-18 | 2017-11-21 | Square, Inc. | Mobile card processing using multiple wireless devices |
US11257048B2 (en) | 2012-01-18 | 2022-02-22 | Square, Inc. | Securing transactions between mobile computing devices |
US20130185208A1 (en) * | 2012-01-18 | 2013-07-18 | Square, Inc. | Handling transaction and trip data |
US10373126B2 (en) | 2012-02-28 | 2019-08-06 | Emerson Electric Co. | HVAC system remote monitoring and diagnosis |
US9741023B2 (en) | 2012-02-28 | 2017-08-22 | Emerson Electric Co. | HVAC system remote monitoring and diagnosis |
US10755373B2 (en) | 2012-05-04 | 2020-08-25 | Gt Gettaxi Limited | Method, device, and medium for searching and routing geographically-positioned entities via a graphical user interface |
US9477983B2 (en) * | 2012-05-04 | 2016-10-25 | Gt Gettaxi Limited | Mechanisms for ordering transportation vehicles |
US20140040079A1 (en) * | 2012-05-04 | 2014-02-06 | Shahar Smirin | Mechanisms for ordering transportation vehicles |
US20130339168A1 (en) * | 2012-06-07 | 2013-12-19 | Keith T. White | Systems and Methods for Facilitating Transactions Between a Seeker and a Proffered Provider of an Urgent Goods or Service |
US20130339176A1 (en) * | 2012-06-07 | 2013-12-19 | Keith T. White | Systems and Methods for Matching a Seeker with a Proffered Provider of an Urgent Goods or Service |
US20130346251A1 (en) * | 2012-06-07 | 2013-12-26 | Keith T. White | Systems and Methods for Screening and Proffering Providers of an Urgent Goods or Service |
US20140058880A1 (en) * | 2012-06-12 | 2014-02-27 | Corey G. Konaxis | Retail fitting room/fitting room attendant system and method |
US9934691B2 (en) | 2012-07-31 | 2018-04-03 | Flatiron Apps LLC | System and method for hailing vehicles |
US9488494B2 (en) | 2012-07-31 | 2016-11-08 | Flatiron Apps LLC | System and method for hailing vehicles |
US9157748B2 (en) | 2012-07-31 | 2015-10-13 | Flatiron Apps LLC | System and method for hailing taxicabs |
US20140046789A1 (en) * | 2012-08-09 | 2014-02-13 | Ebay, Inc. | Fast Transactions |
CN104620277A (en) * | 2012-08-24 | 2015-05-13 | 三星电子株式会社 | Method and mobile terminal for providing transport service information, method and server for managing transport service, and method and vehicle for providing transport service |
US10380668B2 (en) * | 2012-08-24 | 2019-08-13 | Samsung Electronics Co., Ltd. | Method, medium, and system for managing a vehicle transport service |
US20140123306A1 (en) * | 2012-10-30 | 2014-05-01 | Elwha Llc | Methods and systems for managing data |
US9749206B2 (en) | 2012-10-30 | 2017-08-29 | Elwha Llc | Methods and systems for monitoring and/or managing device data |
US9948492B2 (en) | 2012-10-30 | 2018-04-17 | Elwha Llc | Methods and systems for managing data |
US10361900B2 (en) * | 2012-10-30 | 2019-07-23 | Elwha Llc | Methods and systems for managing data |
US10091325B2 (en) | 2012-10-30 | 2018-10-02 | Elwha Llc | Methods and systems for data services |
US9736004B2 (en) | 2012-10-31 | 2017-08-15 | Elwha Llc | Methods and systems for managing device data |
US10069703B2 (en) | 2012-10-31 | 2018-09-04 | Elwha Llc | Methods and systems for monitoring and/or managing device data |
US9886458B2 (en) | 2012-11-26 | 2018-02-06 | Elwha Llc | Methods and systems for managing one or more services and/or device data |
US10216957B2 (en) | 2012-11-26 | 2019-02-26 | Elwha Llc | Methods and systems for managing data and/or services for devices |
US9499128B2 (en) | 2013-03-14 | 2016-11-22 | The Crawford Group, Inc. | Mobile device-enhanced user selection of specific rental vehicles for a rental vehicle reservation |
US10059304B2 (en) | 2013-03-14 | 2018-08-28 | Enterprise Holdings, Inc. | Method and apparatus for driver's license analysis to support rental vehicle transactions |
US11833997B2 (en) | 2013-03-14 | 2023-12-05 | The Crawford Group, Inc. | Mobile device-enhanced pickups for rental vehicle transactions |
US11697393B2 (en) | 2013-03-14 | 2023-07-11 | The Crawford Group, Inc. | Mobile device-enhanced rental vehicle returns |
US10899315B2 (en) | 2013-03-14 | 2021-01-26 | The Crawford Group, Inc. | Mobile device-enhanced user selection of specific rental vehicles for a rental vehicle reservation |
US10850705B2 (en) | 2013-03-14 | 2020-12-01 | The Crawford Group, Inc. | Smart key emulation for vehicles |
US9701281B2 (en) | 2013-03-14 | 2017-07-11 | The Crawford Group, Inc. | Smart key emulation for vehicles |
US20140279713A1 (en) * | 2013-03-14 | 2014-09-18 | Bank Of America Corporation | Automated payment for a rental period based on determining the location of a renter's mobile communication device |
US10308219B2 (en) | 2013-03-14 | 2019-06-04 | The Crawford Group, Inc. | Smart key emulation for vehicles |
US10549721B2 (en) | 2013-03-14 | 2020-02-04 | The Crawford Group, Inc. | Mobile device-enhanced rental vehicle returns |
TWI512668B (en) * | 2013-05-06 | 2015-12-11 | Univ Nat Taiwan | Intelligent cross direction and real-time vehicle dispatching system |
US10181104B2 (en) | 2013-07-31 | 2019-01-15 | Driverdo Llc | Allocation system and method of deploying resources |
US9902343B2 (en) | 2013-07-31 | 2018-02-27 | Driverdo Llc | Digital vehicle tag and method of integration in vehicle allocation system |
US20150095197A1 (en) * | 2013-09-30 | 2015-04-02 | David Edward Eramian | Systems and methods for minimizing travel costs for use of transportation providers by a user |
US20150095122A1 (en) * | 2013-09-30 | 2015-04-02 | David Edward Eramian | Systems and methods for determining pro rata shares of a monetary cost during a ride sharing situation |
US11395093B2 (en) | 2013-10-02 | 2022-07-19 | Federico Fraccaroli | Method, system and apparatus for location-based machine-assisted interactions |
EP2860673A1 (en) | 2013-10-14 | 2015-04-15 | Chaillie, Patrick | Server and method for matching a demand request for a transport capacity with supply requests |
AU2018206844B2 (en) * | 2014-06-02 | 2020-01-16 | Uber Technologies, Inc. | Maintaining data for use with a transport service during connectivity loss between systems |
US20150348221A1 (en) * | 2014-06-02 | 2015-12-03 | Uber Technologies, Inc. | Maintaining data for use with a transport service during connectivity loss between systems |
US10424036B2 (en) * | 2014-06-02 | 2019-09-24 | Uber Technologies, Inc. | Maintaining data for use with a transport service during connectivity loss between systems |
WO2015200225A1 (en) * | 2014-06-20 | 2015-12-30 | OneWhistle, Inc. | Location-based service provisioning |
US9432804B2 (en) | 2014-07-10 | 2016-08-30 | Bank Of America Corporation | Processing of pre-staged transactions |
US9734643B2 (en) | 2014-07-10 | 2017-08-15 | Bank Of America Corporation | Accessing secure areas based on identification via personal device |
US10108952B2 (en) | 2014-07-10 | 2018-10-23 | Bank Of America Corporation | Customer identification |
US10074130B2 (en) | 2014-07-10 | 2018-09-11 | Bank Of America Corporation | Generating customer alerts based on indoor positioning system detection of physical customer presence |
US9471759B2 (en) | 2014-07-10 | 2016-10-18 | Bank Of America Corporation | Enabling device functionality based on indoor positioning system detection of physical customer presence |
US9754295B2 (en) | 2014-07-10 | 2017-09-05 | Bank Of America Corporation | Providing navigation functionality in a retail location using local positioning technology |
US9659316B2 (en) | 2014-07-10 | 2017-05-23 | Bank Of America Corporation | Providing navigation functionality in a retail location using local positioning technology |
US10028081B2 (en) | 2014-07-10 | 2018-07-17 | Bank Of America Corporation | User authentication |
US10332050B2 (en) | 2014-07-10 | 2019-06-25 | Bank Of America Corporation | Identifying personnel-staffing adjustments based on indoor positioning system detection of physical customer presence |
US9699599B2 (en) | 2014-07-10 | 2017-07-04 | Bank Of America Corporation | Tracking associate locations |
US9691092B2 (en) | 2014-07-10 | 2017-06-27 | Bank Of America Corporation | Predicting and responding to customer needs using local positioning technology |
WO2016007857A1 (en) * | 2014-07-11 | 2016-01-14 | Sunil Paul | Systems and methods for providing transportation discounts in shared rides |
US10614473B2 (en) | 2014-07-11 | 2020-04-07 | Sensoriant, Inc. | System and method for mediating representations with respect to user preferences |
US10390289B2 (en) | 2014-07-11 | 2019-08-20 | Sensoriant, Inc. | Systems and methods for mediating representations allowing control of devices located in an environment having broadcasting devices |
US20160019473A1 (en) * | 2014-07-18 | 2016-01-21 | Otitopic Inc. | Arranging transport amongst parties through use of mobile devices |
US20160034855A1 (en) * | 2014-07-30 | 2016-02-04 | Lenovo (Singapore) Pte. Ltd. | Location sharing for events |
US20160078516A1 (en) * | 2014-09-17 | 2016-03-17 | Umm Al-Qura University | Wasul transport application |
US10592952B2 (en) * | 2015-01-06 | 2020-03-17 | GigSmart, Inc. | Labor marketplace exchange computing systems and methods |
US11694250B2 (en) * | 2015-01-06 | 2023-07-04 | GigSmart, Inc. | Labor marketplace exchange and methods thereof |
US11157982B2 (en) * | 2015-01-06 | 2021-10-26 | GigSmart, Inc. | Labor marketplace exchange computing systems and methods |
WO2016111898A1 (en) * | 2015-01-06 | 2016-07-14 | Instalabor, Llc | Labor marketplace exchange computing systems and methods |
US20160335694A1 (en) * | 2015-01-06 | 2016-11-17 | Instalabor, Llc | Labor marketplace exchange computing systems and methods |
US10482377B1 (en) | 2015-02-06 | 2019-11-19 | Brain Trust Innovations I, Llc | System, RFID chip, server and method for capturing vehicle data |
US10628739B1 (en) | 2015-02-06 | 2020-04-21 | Brain Trust Innovations I, Llc | System, RFID chip, server and method for capturing vehicle data |
US10176891B1 (en) | 2015-02-06 | 2019-01-08 | Brain Trust Innovations I, Llc | System, RFID chip, server and method for capturing vehicle data |
US11756660B1 (en) | 2015-02-06 | 2023-09-12 | Brain Trust Innovations I, Llc | System, RFID chip, server and method for capturing vehicle data |
US10540623B2 (en) * | 2015-02-24 | 2020-01-21 | Addison Lee Limited | Systems and methods for vehicle resource management |
US11416795B2 (en) * | 2015-02-24 | 2022-08-16 | Addison Lee Limited | Systems and methods for vehicle resource management |
US20160247109A1 (en) * | 2015-02-24 | 2016-08-25 | Addison Lee Limited | Systems and Methods for Vehicle Resource Management |
WO2016135645A1 (en) * | 2015-02-24 | 2016-09-01 | Addison Lee Limited | Systems and methods for allocating networked vehicle resources in priority environments |
WO2016135652A1 (en) * | 2015-02-24 | 2016-09-01 | Addison Lee Limited | Systems and methods for vehicle resource management |
US11062415B2 (en) | 2015-02-24 | 2021-07-13 | Addison Lee Limited | Systems and methods for allocating networked vehicle resources in priority environments |
US9805431B2 (en) | 2015-02-24 | 2017-10-31 | Addison Lee Limited | Systems and methods for allocating networked vehicle resources in priority environments |
US10217069B2 (en) * | 2015-02-24 | 2019-02-26 | Addison Lee Limited | Systems and methods for vehicle resource management |
US10677604B1 (en) * | 2015-07-20 | 2020-06-09 | Via Transportation, Inc. | Continuously updatable computer-generated routes with continuously configurable virtual bus stops for passenger ride-sharing of a fleet of ride-sharing vehicles and computer transportation systems and computer-implemented methods for use thereof |
US11178240B2 (en) | 2015-09-23 | 2021-11-16 | Sensoriant, Inc. | Method and system for using device states and user preferences to create user-friendly environments |
US10701165B2 (en) | 2015-09-23 | 2020-06-30 | Sensoriant, Inc. | Method and system for using device states and user preferences to create user-friendly environments |
US11424921B2 (en) | 2015-11-09 | 2022-08-23 | Dealerware, Llc | Vehicle access systems and methods |
US11451384B2 (en) | 2015-11-09 | 2022-09-20 | Dealerware, Llc | Vehicle access systems and methods |
US11463246B2 (en) | 2015-11-09 | 2022-10-04 | Dealerware, Llc | Vehicle access systems and methods |
US10218702B2 (en) | 2015-11-09 | 2019-02-26 | Silvercar, Inc. | Vehicle access systems and methods |
US10412088B2 (en) | 2015-11-09 | 2019-09-10 | Silvercar, Inc. | Vehicle access systems and methods |
US10200371B2 (en) | 2015-11-09 | 2019-02-05 | Silvercar, Inc. | Vehicle access systems and methods |
US10277597B2 (en) | 2015-11-09 | 2019-04-30 | Silvercar, Inc. | Vehicle access systems and methods |
US10924271B2 (en) | 2015-11-09 | 2021-02-16 | Silvercar, Inc. | Vehicle access systems and methods |
CN106908077A (en) * | 2015-12-23 | 2017-06-30 | 滴滴(中国)科技有限公司 | Route of user display methods and device based on map |
US10176443B2 (en) * | 2016-08-09 | 2019-01-08 | Conduent Business Services, Llc | Method and system for dispatching of vehicles in a public transportation network |
US10552895B2 (en) * | 2016-08-11 | 2020-02-04 | Service Trading Company, Inc. | Computer system and stored program for certifying contractors |
CN107766997A (en) * | 2016-08-15 | 2018-03-06 | 滴滴(中国)科技有限公司 | A kind of method and device of order push |
US20180130160A1 (en) * | 2016-11-08 | 2018-05-10 | Peter Alexander | Systems, Devices, and/or Methods for Managing Transportation |
US11042856B2 (en) * | 2016-11-11 | 2021-06-22 | Operr Technologies, Inc | System and method for geo-aware transportation billing verification |
US20190188666A1 (en) * | 2016-11-11 | 2019-06-20 | Kevin Sunlin Wang | System and method for geo-aware transportation billing verification |
US10504079B2 (en) * | 2016-11-11 | 2019-12-10 | Operr Technologies, Inc. | System and method for geo-aware transportation billing verification |
US20180137487A1 (en) * | 2016-11-11 | 2018-05-17 | Kevin Sunlin Wang | System and method for geo-aware transportation billing verification |
US11132626B2 (en) | 2016-11-30 | 2021-09-28 | Addison Lee Limited | Systems and methods for vehicle resource management |
US10587679B2 (en) | 2016-12-02 | 2020-03-10 | Uber Technologies, Inc. | Multi-mode message transmission for a network-based service |
US10171569B2 (en) | 2016-12-02 | 2019-01-01 | Uber Technologies, Inc. | Transmission of data to multiple computing devices according to a transmission schedule |
US11665226B2 (en) | 2016-12-02 | 2023-05-30 | Uber Technologies, Inc. | Multi-mode message transmission for a network-based service |
US11252225B2 (en) * | 2016-12-02 | 2022-02-15 | Uber Technologies, Inc. | Multi-mode message transmission for a network-based service |
CN108205407A (en) * | 2016-12-20 | 2018-06-26 | 夏普株式会社 | Display device, display methods and storage medium |
US20180233045A1 (en) * | 2017-02-10 | 2018-08-16 | Vikram Kumar | End-trip detection system |
US11171963B2 (en) | 2017-06-20 | 2021-11-09 | Bank Of America Corporation | System for authentication of a user based on multi-factor passively acquired data |
US10574662B2 (en) | 2017-06-20 | 2020-02-25 | Bank Of America Corporation | System for authentication of a user based on multi-factor passively acquired data |
US10360733B2 (en) | 2017-06-20 | 2019-07-23 | Bank Of America Corporation | System controlled augmented resource facility |
WO2019053556A1 (en) * | 2017-09-15 | 2019-03-21 | Uber Technologies, Inc. | Lost device detection using geospatial location data |
US10674321B2 (en) | 2017-09-15 | 2020-06-02 | Uber Technologies, Inc. | Lost device detection using geospatial location data |
AU2018333084B2 (en) * | 2017-09-15 | 2023-10-26 | Uber Technologies, Inc. | Lost device detection using geospatial location data |
US11284219B2 (en) | 2017-09-15 | 2022-03-22 | Uber Technologies, Inc. | Lost device detection using geospatial location data |
US10085121B1 (en) | 2017-09-15 | 2018-09-25 | Uber Technologies, Inc. | Lost device detection using geospatial location data |
US10382899B2 (en) | 2017-09-15 | 2019-08-13 | Uber Technologies, Inc. | Lost device detection using geospatial location data |
US11244756B1 (en) * | 2017-10-20 | 2022-02-08 | Teletracking Technologies, Inc. | Integrated system and method for receiving and processing real-time digital data concerning transportation and service monitoring scheduling |
WO2020110144A1 (en) * | 2018-12-01 | 2020-06-04 | ANI Technologies Private Limited | Allocation of vehicles for inter-city rides |
US10887724B2 (en) * | 2019-05-01 | 2021-01-05 | International Business Machines Corporation | Locating a mobile device and notifying a user of the mobile device location |
US10834538B1 (en) | 2020-02-12 | 2020-11-10 | International Business Machines Corporation | Locating a mobile device and notifying a user of the mobile device location |
US11954717B2 (en) | 2021-10-14 | 2024-04-09 | GigSmart, Inc. | Labor marketplace exchange computing systems and methods |
Also Published As
Publication number | Publication date |
---|---|
US20170316359A1 (en) | 2017-11-02 |
US20180211194A1 (en) | 2018-07-26 |
US20190220788A1 (en) | 2019-07-18 |
US20130132140A1 (en) | 2013-05-23 |
AU2010325793B2 (en) | 2015-03-12 |
AU2010325793A1 (en) | 2012-07-19 |
US20110301985A1 (en) | 2011-12-08 |
US20120323642A1 (en) | 2012-12-20 |
EP3522081A1 (en) | 2019-08-07 |
US11068811B2 (en) | 2021-07-20 |
US9959512B2 (en) | 2018-05-01 |
WO2011069170A1 (en) | 2011-06-09 |
CA2782611A1 (en) | 2011-06-09 |
EP2507753A1 (en) | 2012-10-10 |
EP2507753A4 (en) | 2013-10-30 |
CA2782611C (en) | 2018-07-10 |
US20110307282A1 (en) | 2011-12-15 |
US20210319380A1 (en) | 2021-10-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20210319380A1 (en) | System and method for facilitating a transport service for drivers and users of a geographic region | |
US20130246301A1 (en) | Providing user feedback for transport services through use of mobile devices | |
JP6062641B2 (en) | Taxi operation system and server device | |
US8688532B2 (en) | Real-time ride share system | |
US20170286884A1 (en) | System and Method for Transportation | |
KR20150048632A (en) | Real-time local offer targeting and delivery system | |
US20060136254A1 (en) | System and method for dispatching transportation to persons who want transportation | |
US20180066947A1 (en) | Providing Alternative Routing Options To A Rider Of A Transportation Management System | |
US20150032485A1 (en) | Digital method For Providing Transportation Services | |
WO2004013733A2 (en) | Method, system and apparatus for providing transportation services | |
CN110969425A (en) | Payment card for multi-branch itineraries | |
WO2018217161A1 (en) | Systems and methods for managing shuttle services and deriving of shuttle service routes and services | |
WO2009058117A1 (en) | Method and system for providing transportation service | |
KR20160120898A (en) | Rental system of car using partnership method | |
KR20130142213A (en) | Proxy driving system using smart phone and method for managing the same | |
KR20160120901A (en) | Forecast and selection system for variable path of transporting vehicle | |
KR20170023058A (en) | Rental system of car using partnership method | |
WO2020142706A1 (en) | Market Layer Price Queue Map Routing in Transportation Capacity and Space | |
AU2017203891B2 (en) | System and method for arranging transport amongst parties through use of mobile devices | |
JP2002140402A (en) | Method for providing vehicle pool service and system for the same and device for the same | |
KR20180029990A (en) | Rental system of car using partnership method | |
US20170039504A1 (en) | Systems and methods to administer a dispatch platform affiliate program | |
AU2016277703A1 (en) | System and Method for Arranging Transport Amongst Parties Through Use of Predominantly Mobile Devices | |
CN111417973A (en) | Method and system for determining payment method for paying online-to-offline services | |
KR20170042203A (en) | Intermediation service system of reverse offering driving by driver and operating method thereof |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: UBER, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CAMP, GARRETT;SALAZAR, OSCAR;KALANICK, TRAVIS;SIGNING DATES FROM 20110427 TO 20110531;REEL/FRAME:026412/0238 |
|
AS | Assignment |
Owner name: UBER TECHNOLOGIES, INC., CALIFORNIA Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE'S NAME PREVIOUSLY RECORDED ON REEL 026412 FRAME 0238. ASSIGNOR(S) HEREBY CONFIRMS THE CHANGE OF NAME FROM UBERCAB, INC. TO UBER TECHNOLOGIES, INC.;ASSIGNOR:UBERCAB, INC.;REEL/FRAME:027504/0351 Effective date: 20110209 |
|
AS | Assignment |
Owner name: UBERCAB, INC., CALIFORNIA Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE'S NAME PREVIOUSLY RECORDED ON REEL 026412 FRAME 0238. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNEE'S CORRECT NAME AS UBERCAB, INC.;ASSIGNORS:CAMP, GARRETT;SALAZAR, OSCAR;KALANICK, TRAVIS;SIGNING DATES FROM 20120702 TO 20120724;REEL/FRAME:028712/0596 |
|
AS | Assignment |
Owner name: GOLDMAN SACHS LENDING PARTNERS LLC, NEW YORK Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:UBER TECHNOLOGIES, INC.;REEL/FRAME:030787/0373 Effective date: 20130710 |
|
AS | Assignment |
Owner name: UBER TECHNOLOGIES, INC., CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:GOLDMAN SACHS LENDING PARTNERS LLC;REEL/FRAME:033054/0697 Effective date: 20130926 |
|
AS | Assignment |
Owner name: UBER TECHNOLOGIES, INC., CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:UBERCAB, INC.;REEL/FRAME:035796/0195 Effective date: 20110209 |
|
AS | Assignment |
Owner name: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRATIVE AGENT, MARYLAND Free format text: PATENT SECURITY AGREEMENT (TERM LOAN);ASSIGNOR:UBER TECHNOLOGIES, INC.;REEL/FRAME:039341/0008 Effective date: 20160713 Owner name: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRATIVE AGENT, MARYLAND Free format text: PATENT SECURITY AGREEMENT (REVOLVER);ASSIGNOR:UBER TECHNOLOGIES, INC.;REEL/FRAME:039341/0064 Effective date: 20160713 Owner name: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRA Free format text: PATENT SECURITY AGREEMENT (REVOLVER);ASSIGNOR:UBER TECHNOLOGIES, INC.;REEL/FRAME:039341/0064 Effective date: 20160713 Owner name: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRA Free format text: PATENT SECURITY AGREEMENT (TERM LOAN);ASSIGNOR:UBER TECHNOLOGIES, INC.;REEL/FRAME:039341/0008 Effective date: 20160713 |
|
AS | Assignment |
Owner name: CORTLAND CAPITAL MARKET SERVICES LLC, AS ADMINISTRATIVE AGENT, ILLINOIS Free format text: SECURITY INTEREST;ASSIGNOR:UBER TECHNOLOGIES, INC.;REEL/FRAME:045853/0418 Effective date: 20180404 Owner name: CORTLAND CAPITAL MARKET SERVICES LLC, AS ADMINISTR Free format text: SECURITY INTEREST;ASSIGNOR:UBER TECHNOLOGIES, INC.;REEL/FRAME:045853/0418 Effective date: 20180404 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: CORTLAND CAPITAL MARKET SERVICES LLC, AS ADMINISTR Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY NUMBER PREVIOUSLY RECORDED AT REEL: 45853 FRAME: 418. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:UBER TECHNOLOGIES, INC.;REEL/FRAME:049259/0064 Effective date: 20180404 Owner name: CORTLAND CAPITAL MARKET SERVICES LLC, AS ADMINISTRATIVE AGENT, ILLINOIS Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY NUMBER PREVIOUSLY RECORDED AT REEL: 45853 FRAME: 418. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:UBER TECHNOLOGIES, INC.;REEL/FRAME:049259/0064 Effective date: 20180404 |
|
AS | Assignment |
Owner name: UBER TECHNOLOGIES, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKET SERVICES LLC, AS ADMINISTRATIVE AGENT;REEL/FRAME:055547/0404 Effective date: 20210225 |