WO2016054700A1

WO2016054700A1 - Online booking system

Info

Publication number: WO2016054700A1
Application number: PCT/AU2015/050621
Authority: WO
Inventors: Russell HOWARTH
Original assignee: Ot Ip Pty Ltd
Priority date: 2014-10-10
Filing date: 2015-10-12
Publication date: 2016-04-14

Abstract

A vehicle booking system and method is provided that may enable vehicles to be more efficiently utilised. The method includes: receiving, on a data interface and from a customer, a booking request including a pickup location; selecting a vehicle of a plurality of vehicles and booking the selected vehicle. The vehicle may be selected according to the pickup location and at least one travel metric, wherein the at least one travel metric includes a component relating to an existing engagement of the vehicle. Alternatively, the vehicle may be selected according to at least one travel metric including a route information component.

Description

ONLINE BOOKING SYSTEM

TECHNICAL FIELD

[0001] The present invention relates to online booking of transport services. BACKGROUND ART

[0002] In large cities, 'hailing' passing taxis is generally the preferred method of obtaining transport. In particular, the passenger waits on or near the sidewalk, and signals to passing taxis by whistling, waving a hand or the like. Hailing taxis is generally efficient in large, dense cities when there is a high demand, as one taxi journey is generally followed by another shortly thereafter.

[0003] However, in smaller cities, or in cities where the demand of taxis is lower, hailing of taxis is generally not very efficient. In particular, the passenger may have to wait a significant amount of time before the arrival of a taxi, and taxis generally waste fuel and time driving around looking for passengers.

[0004] Telephone and online booking of taxis has therefore become more popular. In particular, the passenger will order a taxi by phone, or on a computing device. Typically, the closest available taxi is assigned to the passenger.

[0005] A problem with telephone and online booking systems of the prior art is that taxi utilisation is poor. For example, taxis generally drive long distances between journeys, which results in high fuel consumption, which is turn is costly and bad for the environment.

[0006] As such, there is a need for an improved online booking system.

[0007] It will be clearly understood that, if a prior art publication is referred to herein, this reference does not constitute an admission that the publication forms part of the common general knowledge in the art in Australia or in any other country.

SUMMARY OF INVENTION

[0008] The present invention is directed to online booking systems and methods, which may at least partially overcome at least one of the abovementioned disadvantages or provide the consumer with a useful or commercial choice. [0009] With the foregoing in view, the present invention in one form, resides broadly in a vehicle booking method including:

receiving, on a data interface and from a customer, a booking request including a pickup location;

selecting a vehicle of a plurality of vehicles, wherein the vehicle is selected according to the pickup location and at least one travel metric, and wherein the at least one travel metric includes a component relating to an existing engagement of the vehicle; and

booking the selected vehicle.

[0010] Advantageously, the present invention may provide increased efficiency as vehicles may be more efficiently utilised because the vehicle selected according to the metric is booked. For example, costs in relation to fuel, maintenance and the like may be reduced. Such reduction in fuel consumption also leads to environmental benefits, through a potential reduction in carbon related emissions, but also resulting in less congestion on the roads.

[0011] Furthermore, the present invention may provide an increase in network capability, which results in the ability to handle more clients. In turn, vehicles may arrive at customers more quickly.

[0012] The method may further comprise determining the at least one travel metric.

Determining the at least one travel metric may comprise: determining a first travel metric component in relation to the existing engagement; and determining a second travel metric component in relation to the pickup location.

[0013] According to certain embodiments, the pickup location is automatically determined based upon a location of the customer. The pickup location may be determined at least in part according to a Global Positioning System (GPS) sensor of a portable device of the user.

[0014] Alternatively, the pickup location may be manually entered by the customer, or selected from a profile of the customer (e.g. a home or work address).

[0015] A travel metric may be performed for each of the plurality of vehicles, selecting the vehicle of a plurality of vehicles comprises selecting the vehicle according to the highest or lowest travel metric.

[0016] Alternatively, the pickup location is automatically determined based upon a location input by the customer. The location may be stored in a profile of the customer. [0017] The at least one travel metric may include at least one of a travel time, a travel distance, an estimated fuel consumption, an unpaid travel measure, and a proximity measure. The at least one travel metric may comprise a measure of how close the vehicle is to the pickup location.

[0018] The at least one travel metric may be weighted. The travel metric may be weighted based upon a status if the respective vehicle, a time of day, or based upon a demand. As such, selection criteria based upon the at least one travel metric may be dynamically updated.

[0019] The existing engagement may include travel from a first location to a second location. The first location may be a current location of the vehicle, and the second location may be a destination of the vehicle in relation to the existing engagement. The travel metric may include a component relating to the current location and the second location. The travel metric may include a component relating to the second location to the pickup location.

[0020] The existing engagement may include a plurality of existing engagements. In such case, the travel metric may include component relating to each of the plurality of existing engagements.

[0021] The plurality of vehicles may include taxis, shared vehicles, private vehicles and limousines, charter boats, minibuses, and aircraft.

[0022] Determining the at least one travel metric may comprise:

estimating a travel time of the vehicle to a destination of the existing journey; and estimating a travel time from the destination of the existing journey to the pickup location.

[0023] The method may further comprise sending a booking request to the vehicle, and receiving a confirmation from the vehicle. The confirmation may be sent from a vehicle device with which a driver of the vehicle interacts.

[0024] The at least one travel metric may include a route information component. The route information of the route information component can include one way streets, speed limits, traffic congestion, estimated drop off and pick up time, and weather conditions. The route information may be static, semi- static or dynamic.

[0025] In another form, the invention resides broadly in a vehicle booking system including:

a processor;

a data interface coupled to the processor; and

a memory coupled to the processor, the memory including instruction code executable by the processor for:

receiving, on the data interface and from a customer, a booking request including a pickup location;

booking the selected vehicle.

[0026] The system may further include a customer device. The customer device may include a Global Positioning System (GPS) sensor. The pickup location may be automatically determined based upon the GPS sensor.

[0027] The system may further include vehicle devices in each of the vehicles. The vehicle devices may include GPS sensors.

[0028] In another form, the invention resides broadly in a vehicle booking method including:

selecting a vehicle of a plurality of vehicles, wherein the vehicle is selected according to the pickup location and at least one travel metric, and wherein the at least one travel metric includes a route information component; and

booking the selected vehicle.

[0029] The route information can include one way streets, speed limits, traffic congestion, estimated drop off and pick up time, and weather conditions. The route information may be static, semi-static or dynamic.

[0030] Any of the features described herein can be combined in any combination with any one or more of the other features described herein within the scope of the invention.

[0031] The reference to any prior art in this specification is not, and should not be taken as an acknowledgement or any form of suggestion that the prior art forms part of the common general knowledge.

BRIEF DESCRIPTION OF DRAWINGS

[0032] Various embodiments of the invention will be described with reference to the following drawings, in which:

[0033] Figure 1 illustrates a transport booking system 100, for booking transport in vehicles, according to an embodiment of the present invention;

[0034] Figure. 2 illustrates a flow chart of a method of the system of FIG. 1, according to an embodiment of the present invention;

[0035] Figure 3 illustrates a method of determining a travel metric for a vehicle of the system of FIG. 1, according to an embodiment of the present invention;

[0036] Figure 4 illustrates a scenario on a map, where the prior art is compared with embodiments of the present invention;

[0037] Figure 5 illustrates a schematic of a management server of the system of FIG. 1, according to an embodiment of the present invention; and

[0038] Figure 6 diagrammatically illustrates a method of determining a closest vehicle on a map 600, according to an embodiment of the present invention.

[0039] Preferred features, embodiments and variations of the invention may be discerned from the following Detailed Description which provides sufficient information for those skilled in the art to perform the invention. The Detailed Description is not to be regarded as limiting the scope of the preceding Summary of the Invention in any way.

DESCRIPTION OF EMBODIMENTS

[0040] Figure 1 illustrates a transport booking system 100, for booking transport in vehicles, such as shared vehicles, private vehicles and limousines, taxis, charter boats, minibuses, and aircraft, according to an embodiment of the present invention.

[0041] The system 100 provides increased efficiency as vehicles may be more efficiently utilised. This may in turn reduce costs in relation to fuel, maintenance and the like may, which may also lead to environmental benefits, through a potential reduction in carbon related emissions, but also resulting in less congestion on the roads.

[0042] The transport booking system 100 includes a management server 105, which is coupled to a plurality of vehicles 110 by a communications network 115, such as the internet. The management server 105 provides efficient coordination of bookings of the vehicles 110.

[0043] An end user 120 is able to connect to the management server 105 by an app on a mobile communication device 125, which in turn communicates with the management server 105 by the communications network 115.

[0044] In use, the end user 120 will request a vehicle using the mobile communication device 125, and the request is forwarded to the management server 105. The request includes a pickup location, which may, for example, be determined according to a global positioning system sensor of the mobile communication device 125, or using an address selected by the end user 120.

[0045] The management server 105 then selects a vehicle 110 of the plurality of vehicles for the booking, including among those vehicles 110 that have an existing engagement (e.g. a transport assignment) that is currently in progress. In particular, the vehicle 110 is selected according to the pickup location and at least one travel metric, wherein the at least one travel metric includes a component relating to an existing engagement of the vehicle.

[0046] The management server 105 may determine a travel time for each vehicle of the vehicles 110, from their current location to the pickup location, including consideration of any existing arrangements that the vehicle has. A 'closest' vehicle 110 can then selected and booked.

[0047] In the case where a vehicle 110 does not have any existing arrangements, the management server 105 may determine an arrival time of the vehicle at the pickup location in case the vehicle 110 would immediately travel from its current location to the pickup location. This may be determined using a map system, including details of relevant roads, distances and speed limits.

[0048] In the case where the vehicle 110 does have an existing arrangement, the management server 105 may determine an arrival time of the vehicle at the pickup location by first determining a time for the vehicle 110 to finalise its existing arrangement, and then determining a travel time from the location where existing arrangement was finalised to the pickup location.

[0049] As an illustrative example, a vehicle 110 may be partway through an existing journey. The management server 105 may determine an arrival time of the vehicle 110 at the pickup location by determining an arrival time of the vehicle 110 at a destination of the existing journey, and subsequently determining a travel time from the destination of the existing journey to the pickup location.

[0050] According to certain embodiments, the management server 105 selects a vehicle 110 by applying weights to the travel times. . For example, currently available vehicles 110 may be given a lower weight (i.e. an advantage) than vehicles with an existing arrangement, to ensure that work is evenly distributed among vehicles.

[0051] The travel metric may also include weights to favourite drivers of the end user 120, such that the favourite drivers are given preference over other drivers.

[0052] The vehicle 110 may be selected based upon a lowest or highest travel metric, potentially weighted, depending on requirements of the system.

[0053] The above description primarily relates discussed selecting a vehicle based upon available time. However, other factors can be used to choose vehicle, including unoccupied travel of the vehicle, travelled distance, fuel consumption, or a weighted combination thereof.

[0054] Furthermore, such selection criteria (e.g. weights) can be changed based upon a time of day, or demand. For example, during high demand, it may be desirable to give a high weight to reducing unoccupied travel of the vehicle, thus enabling the vehicles 110 to be utilised as much as possible. During low demand times, it may be desirable to give high weight to reducing distance travelled, thus ensuring that fuel consumption remains low.

[0055] The vehicles 110 may be associated with a portable computing device (not shown), such as a smartphone, in communication with the management server 105. As such, a location of a vehicle 110 may be determined or estimated according to a location of the portable computing device. Alternatively, a device may be permanently or semi-permanently attached to the vehicle for providing information to the management server 105, such as a location of the vehicle. [0056] Figure 2 illustrates a flow chart of a method 200 of the system 100, according to an embodiment of the present invention.

[0057] At step 205, a booking request is received from the customer 120 using the mobile communication device 125. As discussed above, the request includes a pickup location, which may be explicitly provided by the customer 120, or determined by the mobile communication device 125. The customer 120 may make the request by an app residing on the mobile communication device 125.

[0058] At step 210, the 'closest' vehicle 110 to the customer is determined. In this case, the term 'closest' can be determined according to one of several travel metrics in relation to the pickup location. For example, the closest vehicle may be determined according to metrics including a point-to-point distance (i.e. as the crow flies), an estimated travel distance (i.e. taking into consideration roads), an estimated travel time, an estimated fuel consumption, an unpaid travel distance or time, a proximity, or a combination thereof.

[0059] The plurality of vehicles 110 includes vehicles 110 that have existing engagements (such as existing journeys/bookings in the case of taxis), and in such case, the travel metric takes into account the existing engagements. In particular, a travel metric is first determined in relation to the existing engagement, and then determined in relation to the pickup location.

[0060] At step 215, a request is sent to the closest vehicle. The closest vehicle may then accept the request, and provide confirmation of same, which is received by the management server 105 at step 220.

[0061] At step 225, a confirmation is provided to the customer in relation to the booking request. The confirmation may include an estimate arrival time, details of the vehicle or driver, or any other information that may be of interest to the customer.

[0062] The method 200 enables more efficient vehicle usage, as the closest vehicle (regardless of whether it currently has an engagement or not, is selected. As discussed above, this may have various advantages including reduced fuel and maintenance costs, but also faster pickups for customers.

[0063] Figure 3 illustrates a method 300 of determining a travel metric for a vehicle 110 according to an embodiment of the present invention. The method 300 may be performed for each of the plurality of vehicles 110 to determine the 'closest' vehicle to the pickup location. [0064] At step 305, the method 300 is initialised by setting the travel metric ('metric') and a counter variable ('η') to zero, and setting a location variable ('loc') to the current location of the vehicle 110.

[0065] At step 310 it is determined if the counter variable ('η') is greater than or equal to the number of bookings of the vehicle. In particular, the method 300 loops over all bookings and adds a value associated with each of the bookings to the travel metric ('metric') in step 305.

[0066] In particular, a 'distance' between the location variable ('loc') and the pickup of the booking (booking [n] .pickup) is determined using a distance function ('dist'). Such distance may represent a travel metric describing a distance to the booking, i.e. the distance between the current location ('loc') and the pickup associated with the booking. This distance is then added to the travel metric ('metric').

[0067] A 'distance' between the pickup of the booking (booking[n]. pickup) and the destination of the booking (booking[n].dest) is determined using a distance function ('dist'). Such distance may represent a travel metric describing a distance associated with the booking, such as a distance of the journey. This distance is then added to the travel metric ('metric').

[0068] Finally, the location variable ('loc') is updated to the destination of the booking, and the counter variable ('η') is incremented.

[0069] When the method 300 has looped over all bookings (i.e. n >= num bookings), the 'distance' between the location variable ('loc') and the pickup ('pickup') is determined and added to the travel metric ('metric').

[0070] The method 300 enables use of vehicles that are presently engaged, but will shortly become available. In particular, the method 300 enables a determination of how close a vehicle is to a pickup, even if it must fulfil other obligations first.

[0071] Figure 4 illustrates a scenario on a map 400, where the prior art is compared with embodiments of the present invention.

[0072] A first vehicle 405 is currently engaged in a journey to a first destination 410. A second vehicle 415 is currently available for a booking.

[0073] At a first time instant, before the first vehicle 405 completes the journey, a first customer 420 makes a booking request associated with a first pickup location. At a second time instant, after the first vehicle 405 completes the journey, a second customer 425 makes a booking request associated with a second pickup location.

[0074] According to the prior art, the second vehicle 415 will be allocated to the first customer 420 as the first vehicle 405 is already engaged in a journey. The first vehicle 405 will then be allocated to the second customer 425. As such, the second vehicle 415 and the first vehicle 405 cross the map 400 to get to the first customer 420 and the second customer 425 respectively.

[0075] According to embodiments of the present invention, the 'closest' vehicle to the first customer 420 is determined. In this case, the first vehicle 405 is closer to the first customer 420, even considering the existing journey.

[0076] A first travel metric may be determined for the first vehicle 405 from its current location to the first destination 410, and from the first destination to the first customer 420, as discussed above in the context of FIG. 3. A second travel metric may be determined for the second vehicle 405 from its current location to the customer 420. The 'closest' vehicle may be determined by comparing the first travel metric to the second travel metric.

[0077] As such, according to embodiments of the present invention, the first vehicle 405 and the second vehicle 415 are able to pick up passengers, while minimising unnecessary travel. This can result in both the first and second customer 420, 425 get picked up earlier, but also both vehicles 405, 415 being engaged earlier, and thus becoming available again sooner, which enables more efficient utilisation of vehicles and driver time.

[0078] Figure 5 illustrates a schematic of the management server 105, according to an embodiment of the present invention.

[0079] The management server 105 includes a processor 505, a memory 510 coupled to the processor 505, and a data interface 515 coupled to the processor 505. The memory includes instruction code executable by the processor for performing the method 200 of FIG. 2 or the method 300 of FIG. 3.

[0080] In particular, the instruction code may include instructions for operating a web server, user authentication, and other associated features of a transport booking system. [0081] Figure 6 diagrammatically illustrates a method of determining a closest vehicle on a map 600, according to an embodiment of the present invention.

[0082] The map 600 illustrates a first vehicle 605, a second vehicle 610, a pickup point 615, and a plurality of roads 620 on which the first vehicle 605 and the second vehicle 610 may travel. The roads 620 include one way roads 620a, as indicated by one way arrows.

[0083] As can be seen on the map 600, the first vehicle 605 is clearly closer to the pickup point 615 than the second vehicle 610. However, if the one way roads 620a are taken into consideration, the second vehicle 610 is able to arrive at the pickup point 615 before the first taxi 605, if they were to both leave at the same time.

[0084] Similarly, the method can me modified to take into consideration route information such as speed limits, traffic congestions (estimated or actual), estimated drop off and pick up time delays (in case of existing engagements), and weather conditions. The route information may be static, semi-static or dynamic.

[0085] According to certain embodiments, the travel metric of the method 100 takes into consideration the route information.

[0086] According to certain embodiments, the transport booking system enables an end user to provide an incentive, such as a payment, to more quickly obtain a vehicle - i.e. jump the queue. In such case, the system may determine a closest vehicle regardless of any future bookings, and allocate the closest vehicle to the end user. The future bookings of the closest vehicle may then be shuffled to a later time, or the system may reallocate the bookings to other vehicles.

[0087] In the present specification and claims (if any), the word 'comprising' and its derivatives including 'comprises' and 'comprise' include each of the stated integers but does not exclude the inclusion of one or more further integers.

[0088] Reference throughout this specification to 'one embodiment' or 'an embodiment' means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearance of the phrases 'in one embodiment' or 'in an embodiment' in various places throughout this specification are not necessarily all referring to the same embodiment.

Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more combinations.

[0089] In compliance with the statute, the invention has been described in language more or less specific to structural or methodical features. It is to be understood that the invention is not limited to specific features shown or described since the means herein described comprises preferred forms of putting the invention into effect. The invention is, therefore, claimed in any of its forms or modifications within the proper scope of the appended claims (if any) appropriately interpreted by those skilled in the art.

Claims

1. A vehicle booking method including:

booking the selected vehicle.

2. The method of claim 1, further comprising determining the at least one travel metric.

3. The method of claim 2, further comprising determining a first travel metric component in relation to the existing engagement; and determining a second travel metric component in relation to the pickup location, wherein the at least one travel metric includes the first travel metric component and the second travel metric component.

6. The method of claim 2, wherein a travel metric is determined for each of the plurality of vehicles, and wherein selecting the vehicle of the plurality of vehicles comprises selecting the vehicle according to the highest or lowest travel metric.

7. The method of claim 2, wherein the at least one travel metric includes at least one of a travel time, a travel distance, an estimated fuel consumption, an unpaid travel measure, and a proximity measure.

8. The method of claim 2, wherein the travel metric is weighted based upon a status of the vehicle, a time of day, or based upon a demand.

9. The method of claim 3, wherein the existing engagement includes travel from a first location to a second location.

10. The method of claim 9, wherein the first location is a current location of the vehicle, and the second location is a destination of the vehicle in relation to the existing engagement.

11. The method of claim 3, wherein the existing engagement includes a plurality of existing engagements, and wherein the travel metric includes components relating to each of the existing engagements.

15. The method of claim 3, wherein determining the at least one travel metric comprises: estimating a travel time of the vehicle to a destination of the existing engagement; and estimating a travel time from the destination of the existing engagement to the pickup location.

16. The method of claim 1, wherein the pickup location is automatically determined based upon a location of the customer.

17. The method of claim 16, wherein the pickup location is determined at least in part according to a Global Positioning System (GPS) sensor of a portable device of the user.

18. The method of claim 1, wherein the plurality of vehicles includes at least one of taxis, shared vehicles, private vehicles and limousines, charter boats, minibuses, and aircraft.

19. The method of claim 1, further comprising sending a booking request to the vehicle, and receiving a confirmation from the vehicle, wherein the confirmation is sent from a vehicle device with which a driver of the vehicle interacts.

20. The method of claim 1, wherein the at least one travel metric includes a route information component comprising at least one of: one way streets, speed limits, traffic congestion, estimated drop off and pick up time, and weather conditions.

21. A vehicle booking system including:

a processor;

a data interface coupled to the processor; and

booking the selected vehicle.

22. The system of claim 21, further including a customer device, from which the booking request is provided.

23. The system of claim 22, wherein the customer device includes a Global Positioning System (GPS) sensor, and wherein the pickup location is automatically determined according to the GPS sensor.

24. The system of claim 21, further including vehicle devices in each of the vehicles, wherein the vehicle devices include GPS sensors for determining locations of the vehicles.

25. A vehicle booking method including:

booking the selected vehicle.

26. The method of claim 25, wherein the route information includes at least one of: one way streets, speed limits, traffic congestion, estimated drop off and pick up time, and weather conditions.