WO2007038839A1

WO2007038839A1 - Vehicle rental system and method

Info

Publication number: WO2007038839A1
Application number: PCT/AU2006/001457
Authority: WO
Inventors: William Thomas Cowie
Original assignee: Move Yourself Trailer Hire Pty Ltd
Priority date: 2005-10-06
Filing date: 2006-10-06
Publication date: 2007-04-12
Also published as: GB2445890A; GB2445890A8; GB0807256D0

Abstract

A system (100) and method for processing a transaction between a user (106) and a rental vehicle provider is disclosed. The system (100) includes an input device (104), a communication device (202) and a processor (206). The input device (104) accepts rental data including vehicle identification data for a selected rental vehicle (102), and user data. The communication device (202) wirelessly communicates with a vehicle data unit (112) of the rental vehicle (102) identified by the vehicle identification data to obtain vehicle data therefrom. The processor (206) processes the user data and the vehicle data to produce an agreement for acceptance by the user (106) so that the agreement includes information derived from the user data and the vehicle data.

Description

VEHICLE RENTAL SYSTEM AND METHOD

This application claims priority from Australian Provisional Patent Application No. 2005905506 filed on 6 October 2005, the contents of which are to be taken as incorporated herein by this reference.

FIELD OF INVENTION

The present invention relates to a vehicle rental system and method. In a typical application the system may be used in a rental vehicle depot to facilitate automatic handling of the rental of a vehicle from a selection of rental motor vehicles. Although the invention will largely be described herein with reference to this use, it will be appreciated that the invention is not limited to use in this field.

BACKGROUND TO THE INVENTION Vehicle rental services are often relied upon by travelers requiring transportation when visiting destinations where they do not have access to their own vehicle or another form of suitable transportation.

Renting a vehicle from a rental depot typically initially involves a user reserving a rental vehicle using a reservation system which accepts rental data, such as, the type of vehicle required, the depot from which the vehicle is to be collected and returned, the start date and duration of the rental period and user data.

Once the rental data has been provided to the reservation system the user then enters into an agreement with the rental vehicle provider that requires the user to collect the rental vehicle from the collection depot at the collection date specified by the user. Accordingly, on the day of collection the user arrives at the collection depot ready to collect the rental vehicle.

Unfortunately, after having arrived at the collection depot to collect the rental vehicle, the user is often asked to complete further rental documents so as to finalise the rental agreement prior to the rental vehicle being released to the user. Completion of the further documentation typically involves additional activities such as the rental agent confirming the user's identification information

(for example, the user's licence information) and entering particular information for the rental vehicle (for example, make and model) into the rental agreement. As would be expected, such further activities frequently result in delaying the release of the rental vehicle to the user and may lead to user dissatisfaction, particularly during periods of peak rental activity and/or where the user requires the rental vehicle promptly. In addition, in circumstances where the user, or indeed the rental agent, is subject to increased stress, there is an increased likelihood that errors will be made during the completion of the rental agreement.

Similarly, on return of the rental vehicle to the vehicle depot, the user may again find themselves in a situation requiring rapid handling of the return processing. In addition to the inconveniences presented to a user, the fleet management practices of the rental provider may delay the processing, or inadvertently affect the accuracy of, a rental agreement between the user and the rental provider. For example, existing rental pool management systems typically rely on readings of vehicle status information (such as an odometer reading) taken during an inspection of the vehicle prior to a user taking rent of a rental vehicle (or on return of a rental vehicle). Unfortunately, obtaining such status information tends to delay processing of a rental transaction, particularly during bust periods. In addition, inaccuracies in the rental agreement may lead to a dispute between the user and the rental provider in relation to, for example, the costs incurred for the rent of the vehicle, or the state of the vehicle at the time that the rental period commenced.

In view of the above, a vehicle rental system and method is needed that reduces the time taken to release, or return, a rental vehicle to a user. It would also be useful if such a system and method were provided that led to a reduced likelihood of errors in the rental agreement.

SUMMARY OF THE INVENTION

In broad terms, the present invention provides a system and method that automatically processes user data obtained from a user and vehicle data obtained from a vehicle so as to produce an agreement for acceptance by the user to complete, on acceptance of the agreement, a rental transaction. Producing an agreement in this way is expected to lead to improvements in the accuracy of information contained in the rental agreement and may lead to a reduced processing time. In one form of the present invention, there is provided a system for processing a transaction between a user and a rental vehicle provider, including: (a) input device for accepting rental data, the rental data including vehicle identification data for a rental vehicle and user data for the user; (b) a communications device for wirelessly communicating with a vehicle data unit of the rental vehicle identified by the vehicle identification data so to obtain vehicle data therefrom; and

(c) a processor for processing the user data and the vehicle data to produce an agreement for acceptance by the user; wherein the agreement includes information derived from the user data and the vehicle data.

In another form of the present invention there is provided method of processing a transaction between a user and a rental vehicle provider, including:

(a) an input device accepting rental data, the rental data including vehicle identification data for a selected rental vehicle and user data;

(b) a communication device wirelessly communicating with a vehicle data unit of the rental vehicle identified by the vehicle identification data to obtain vehicle data therefrom; and

(c) a processor processing the user data and the vehicle data to produce an agreement for acceptance by the user; wherein the agreement includes information derived from the user data and the vehicle data.

The transaction may be a rental transaction wherein on acceptance of the agreement by the user the selected rental vehicle is released to the user. Alternatively, the rental vehicle transaction may include a return transaction wherein on acceptance of the agreement by the user the selected rental vehicle is released from the user to the rental provider so as to return that vehicle to the rental provider.

Accordingly, the present invention involves the use of a system and a method which utlilises a processor capable of processing data obtained from one or more input devices and one or more vehicle data units of respective rental vehicles so as to produce the agreement. Thus, the agreement is transaction dependent in that the actual agreement will depend on whether the transaction is a rental transaction (in which case, the agreement may include a rental contract) - A - or a return transaction (in which case, the agreement may include a rental docket).

The method and system may be deployed as a standalone computer system that provides suitable processing capability, computer program code and data structures. In an embodiment, one such standalone computer system may be of a type that is typically referred to as a "kiosk". However, in a particularly preferred form of the present invention the system is designed as a network of computers configured to interoperate over a communications network, such as a wide area communications network (for example, a mobile network or the Internet.) Further benefits are expected to be provided by a networked form of the invention in that such an embodiment may allow for interoperation between geographically distributed rental depots.

Thus, according to another form of the present invention there is provided a system for processing a transaction between a user and a rental vehicle provider, including:

(a) plural rental vehicle depots, each depot having access to a pool of rental vehicles;

(b) at each depot, a terminal including:

(i) input device for accepting rental data, the rental data including vehicle identification data for a rental vehicle and user data;

(ii) a communications device for communicating the vehicle identification data into a first communications network;

(c) a hub, communicatively coupled with the terminals via the first communications network, including: (i) a receiver for receiving vehicle identification data from a terminal via the first communications network; and

(ii) a controller for activating wireless communication with a vehicle data unit of the rental vehicle identified by the vehicle identification data to retrieve vehicle data therefrom; wherein either the hub, or the terminal, includes a processor for processing the vehicle data and the user data to provide, at the terminal, an agreement for acceptance by the user, the agreement including information derived from the user data and the vehicle data. The present invention also provides a method of processing a transaction between a user and a rental vehicle provider, including: a rental depot terminal accepting rental data, the rental data including vehicle identification data for a rental vehicle and user data; a hub, communicatively coupled with the terminal, receiving the vehicle identification data from the rental depot terminal via the first communications network; the hub processing the vehicle identification data and activating wireless communication with a vehicle data unit of the rental vehicle identified by the vehicle identification data to obtain vehicle data therefrom and thereafter activating communication of that data to the terminal via the first, or another, communications network; and processing the vehicle data and the user data to provide, at the terminal, an agreement for acceptance by the user, the agreement including information derived from the user data and the vehicle data.

The present invention also provides a programmed device for processing a rental transaction between a user and a rental vehicle provider, the device including: a processor; a memory; an input device; a wireless communication device; and a set of program instructions resident in the memory and executable by the processor to: accept rental data into the input device, the rental data including vehicle identification data for a selected rental vehicle and user data; activate the wireless communications device for wirelessly communicating with a vehicle data unit of a rental vehicle identified by the vehicle identification data to obtain vehicle data therefrom; and process the user data and the vehicle data to produce an agreement for acceptance by the user; wherein the agreement includes information derived from the user data and the vehicle data.

The present invention also provides a computer readable media containing a set of program instructions in the form of a computer program, the computer program executable by a processor of a device that also includes a memory, an input device, and a wireless communication device, so that on execution of the program the processor: accepts rental data into the input device, the rental data including vehicle identification data for a selected rental vehicle and user data; activates the wireless communications device for wirelessly communicating with a vehicle data unit of a rental vehicle identified by the vehicle identification data to obtain vehicle data therefrom; and processes the user data and the vehicle data to produce an agreement for acceptance by the user; wherein the agreement includes information derived from the user data and the vehicle data.

Thus, in one preferred arrangement, the system and method employs a terminal in networked communication with a hub that itself is capable of initiating data communication with a rental vehicle selected by the user to obtain vehicle data therefrom. In such an arrangement, the terminal constitutes that part of the system designed to accept user data from the user whereas the hub constitutes that part of the system for initiating communication with the vehicle data unit a selected rental vehicle so as to obtain vehicle data therefrom. In arrangements that include a hub, the processing may be shared between the terminal and the hub, or it may be performed by either singularly. Thus, the nature of the interaction between the terminal and the hub may vary. Thus, although in one arrangement the terminal accepts user data from the user and the hub obtains vehicle data from the selected vehicle for communication to the terminal, in another embodiment the terminal may accept user data from the user and also obtains vehicle data from the vehicle data unit of selected vehicle.

As indicated above, the system and method of the invention is ideally suited to operate in a networked environment. In this arrangement, the terminal, the hub and the vehicle data units are communicatively coupled via one or more communication networks to allow for the exchange and processing of user data and vehicle data on demand so as to produce the agreement.

This present invention provides significant advantages over traditional rental systems and methods. One advantage of processing data obtained from the user and the rental vehicle is that the information is more likely to be up to date and thus, accurate.

BRIEF DESCRIPTION OF THE DRAWINGS

Additional aspects, features and advantages of the present invention will be more readily apparent from the following detailed description which presents, by way of non-limiting example only, preferred and other embodiments of the invention, with reference to the accompanying drawings, in which:

Fig.1 illustrates a block diagram of system according to an embodiment of the present invention for handling rental of a vehicle to a user; Fig.1 A illustrates an example of an agreement produced by an embodiment of the present invention;

Fig.2 illustrates a block diagram of a terminal suitable for use with an embodiment of the present invention; Fig.2A is a flow diagram of a method embodiment of the present invention;

Fig.3 illustrates a block diagram of different communication channels that may be used in an embodiment of the present invention;

Fig.4 illustrates a block diagram of an automated rental system according to a second embodiment of the present invention; Fig.5 illustrates a block diagram of an automated rental system according to an third embodiment of the present invention; and

Fig.6A illustrates a lower level block diagram of a system of the type illustrated in Fig.4;

Fig.6B illustrates a lower level block diagram of a system of the type illustrated in Fig.4.

DETAILED DESCRIPTION OF AN EMBODIMENT

Fig.1 shows an embodiment of a system 100 for processing a rental vehicle transaction between a user 106 and a rental vehicle provider (not shown). The illustrated system 100 includes a terminal 104 that is operable by a user 106 to facilitate rental and/or return of a rental vehicle 102 in the form of a rental motor vehicle 102.

In a typical application, the system 100 processes transactions that involves a rental, and/or a return of, a vehicle from a rental vehicle depot having an associated pool 108 of rental motor vehicles 102. However, it is to be appreciated that the scope of the term "rental vehicles" is not to be so limited.

Indeed, the term "rental vehicles", as used throughout this specification, is intended to include any vehicle that is operable to convey people or objects.

Accordingly, the term "rental vehicles" is intended to include within its scope a range of different vehicles such as cycles, trailers, camper-trailers, caravans, motorcycles, cars, trucks and vans, recreational vehicles (such as jet-skis), boats, fork-lifts, cranes and the like.

In addition, and again in the context of this description, references to the term "user" throughout this specification are to be understood to be references to a person who is taking a rental of, or returning, a rental vehicle. Thus, the user 106 is typically a person who requires, or has required, the use of a rental vehicle 102. In this respect, whilst the system 100 and the terminal 104 will be described in the following description as being "operable by a user" it will be appreciated that this need not always be the case. Indeed, it is envisaged that in some situations the system 100 or the terminal 104 may be operated by another person, such as a representative of a rental depot, such as a rental agent, to process the transaction.

In the present case, the terminal 104 is operable by a user to initiate data communication over a wireless communications channel 1 10 with a vehicle data unit 1 12 of a rental vehicle 102. The wireless communications channel 1 10 may include a bi-directional communications channel that supports direct data communication between the terminal 104 and the vehicle data unit 1 12, or it may provide for networked data communication via a communication network. In an embodiment that includes a wireless communications channel 1 10 that supports direct data communication, the wireless communications channel may include, for example, a Bluetooth channel, a Wi-Fi (for example, IEEE802.1 1 ) channel or an infra-red (IR) channel. On the other hand, a bidirectional communications channel that supports networked data communication via a communication network may utilise, for example, a private wireless network. Further examples of suitable networked communications channels will be described in more detail later.

In using the term "vehicle data unit" we mean any unit that permanently or temporarily stores data indicative of vehicle data of a type that is required for processing a transaction involving the rental and/or return of a rental vehicle. By way of example, the vehicle data may be indicative of, but need not be limited to:

(a) vehicle odometer information;

(b) vehicle fuel level information;

(c) vehicle location information; (d) vehicle make and/or model information;

(e) vehicle registration information; and

(f) vehicle status information (including vehicle servicing and maintenance) information). As will be appreciated, the type of vehicle data may vary according to, or be specific for, the type of vehicle to which the vehicle data unit is fitted. By way of example, where the vehicle is a trailer, the vehicle data may be indicative of: (a) trailer weight; (b) trailer size;

(c) trailer carrying capacity;

(d) trailer towing requirements;

(e) trailer registration status information;

(f) trailer location; (g) trailer colour; and

(h) trailer electrical requirements (such as power connector type).

In the present case, the vehicle data unit 1 12 includes a GPRS based communications module (such as a "Patriot 4" GPRS module) that interfaces with suitable sensors. In the illustrated embodiment, the vehicle data unit 1 12 monitors various vehicle components (and/or sensors) to collect, from those components (and/or sensors), vehicle data for storage. In this respect, it will be appreciated that the vehicle data unit 1 12 may collect vehicle data on an "as required" basis for temporary storage (for example, in a buffer memory) prior to communicating vehicle data represented by at least some of that data to the terminal 104 or, alternatively, it may collect such data in memory and update that data in realtime, perhaps in response to detecting changes in the data, for later communication to the terminal 104.

Ideally, the vehicle data unit 1 12 will be fixedly connected to a respective rental vehicle 102. In using the term "fixedly connected" we mean that the vehicle data unit 1 12 will normally be mechanically secured to the rental vehicle using a suitable mounting arrangement. Ideally, the vehicle data unit 1 12 will be secured using a mounting arrangement that permits the vehicle data unit 1 12 to be accessible for (or detachable from the vehicle) servicing, repair, replacement or the like.

In terms of the electrical connection of the vehicle data unit 1 12 to a rental vehicle 102, it is preferred that the electrical connection includes an electrical connection to one or more busses (for example, a CANbus vehicle data bus and a +12VDC power bus) of the vehicle 102 so as to provide connectivity to the components from which the vehicle data unit 1 12 collects data as well as connectivity to an electrical power source (for example, a battery). However, the electrical connection scheme may be varied and may include any suitable connection scheme. One suitable scheme may be a point to point wiring scheme). For example, another suitable scheme may include hard-wiring the vehicle data unit 1 12 to an electrical bus of the vehicle that provides electrical power and, separately, wirelessly connectivity with the components (and/or sensors) from which the vehicle data unit 1 12 collects data. Irrespective of the type of connection scheme that is used, the vehicle data unit 1 12 will be able to collect the required data from one or more of the vehicle components (or sensors).

The vehicle data unit 1 12 may be any suitable device. However, in the present case the vehicle data unit 1 12 includes an engine management system (EMS) including suitable hardware and software to support wireless communications over the wireless communication channel 1 10.

In terms of engine management systems that do not provide support for wireless communications, but that are nevertheless able to collect the required data, it is expected that modification of such engine management systems to provide support for wireless communication would be well within the capabilities of a competent communications engineer.

In addition to providing a data storage function, the vehicle data unit 1 12 also provides a data processing capability. Thus, in the illustrated embodiment, the vehicle data unit 1 12 includes a processing unit. In the present case, the processing unit provides the vehicle data unit 1 12 with the capability to assemble a message containing vehicle data in a format that is suitable for communicating, over the wireless communications channel 1 10, to the terminal 104 or another device in networked communication with the terminal 104. Different forms of suitable wireless communication channels 1 10, and different types of suitable networked communication schemes will be described in more detail later. With reference to Fig.2, there is shown a block diagram of an embodiment of a terminal 104 for processing a transaction involving the rental of a rental vehicle 102 (ref. Fig.1 ) to a user 106 (ref. Fig.1 ).

In the present case the terminal 104 is a free-standing unit (such as a kiosk). In other embodiments the terminal 104 may be a mobile device (such as a personal digital assistant equipped with suitable software). One suitable standalone mobile device is an 02 XDAIIi equipped with suitable computer software. As will be appreciated, the terminal 104 may be a standalone computer terminal configured to operate independently of other processing devices, or it may be a "dumb" terminal (for example, a "thin client") that merely accepts data from a user, and possibly the vehicle data unit of a rental vehicle, and that is in networked communication with a remote processing device (such as a hub) that provides the requisite processing and communications capability.

With reference now to Fig.2 and Fig.2A, the terminal 104.2 includes an input device 200 for accepting, at step 224 (ref. Fig.2A) rental information, a wireless communication device 202 (shown as transceiver 204) for wirelessly communicating, at step 226, with a vehicle data unit 1 12 (ref. Fig.1 ) of a rental vehicle 102 and a processor 206 for processing, at step 228, the rental information to provide, at step 230, an agreement for acceptance by the user 106 (ref. Fig.1 ).

Because the terminal 104 shown in Fig.2 is a "standalone" type terminal, the processor 206 provides the requisite processing capability to process the rental vehicle rental transaction. However, it will be appreciated that this not need be the case. Indeed, in another embodiment the processing capability may be provided by a remote processing unit in networked communication with the terminal 104.

As is shown in Fig.2, the processor 206 includes a programmed memory 208 containing a set of programmed instructions 210, a processing unit 212 and a communications controller 214. In the present case, the processor 206 also includes a display 216, a printer interface 218 and a power source 220. The function of the display 216, the printer interface 218 and the power source 220 will be described in more detail later.

The input device 200 may include any suitable device for accepting rental information. In the present case the input device includes a touch-panel 222 and an image capture device 224 (such as a Web Cam). It will of course be appreciated that other types of conventional input devices may be used, including, for example, a track ball, a mouse, a keyboard and the like.

In the present case, the touch-panel 222 is operatively associated with a graphical user interface (GUI) provided on the display 216. The GUI displays an image containing a keypad, buttons, tick boxes and the like that are each "activatable" using the touch-panel 222 to permit the user to enter rental information into the terminal 104.

In the present case, the rental information includes vehicle identification data for a particular rental vehicle 102 (ref. Fig1 ) and user data.

The vehicle identification data includes information that is usable by the system 100 to identify a particular rental vehicle 102 (ref. Fig1 ) from a pool 108 (ref. Fig1 ) of available rental vehicles. By way of example, the vehicle identification data may include coded data that is indicative of a vehicle type (for example, a sedan, a station wagon or a four wheel drive), a vehicle model (for example, Holden) or a vehicle category (for example, a small vehicle or a four- cylinder vehicle). Alternatively, the vehicle identification data may include information that is usable by the system 100 to specify characteristics of a particular identified rental vehicle 102 (such as a trailer). In the present case, the vehicle identification data includes a code that uniquely identifies a selected rental vehicle 102 (ref. Fig1 ) from the pool 108 (ref. Fig1 ) of available rental vehicles. The code may include a numerical code (for example, "103"), an alphabetic code (for example. "AED", or an alphanumeric code (for example, AED103), such as a vehicle registration number. In the illustrated embodiment, the user 106 enters a code for a user- selected rental vehicle 102 into the terminal 104. Entry of the code into the terminal 104 entails the user 106 "pressing" keypad "keys" displayed on the display 216 until the terminal 104 has accepted the code from the user 106. "Presses" of the keypad keys are detected by the processing unit 212 in response to processing data provided thereto by the touch panel 222.

The user data includes information that is provided by the user and may be indicative of, for example:

(a) rental period information;

(b) user identification information; (c) return depot information;

(d) payment method information;

(e) return date information; and

(f) user specified vehicle requirements (such as load weight). Th Θ user data may be obtained as responses from the user 106 to a set of structured questions.

Thus, the user data includes information that is usable by the system 100 to identify the user 106 taking rent of the vehicle 102 as well as other rental information, such as the duration of the rent, the start date of the rent, and possibly the return depot. In addition, the user data may also include other data for characterising the user 106, such as data that confirms whether the user 106 wears corrective lenses, whether the user 106 is of legal age to take rent of the vehicle, and the language understood by the user 106. The user identification information may include information such as the user's name, address, photographic image, date of birth, driver's licence number, nationality or biometric information (such as fingerprint or retina scan).

The user data is entered into the terminal 104 using any suitable input device 200, with the actual input device depending on the type of user data is provided. For example, where the user data is provided in an electronic data file stored on a data storage card (for example, an SD memory card), the input device 200 may include a memory card reader. Alternatively, where the electronic data file is stored on a wireless device, the input device 200 may include a compatible wireless receiver. Alternatively, the user data may be entered into the terminal 104 using a keypad arrangement of the type described previously for entering vehicle data. It will be appreciated that the above examples of suitable input devices 200 for accepting user data are intended as non-limiting examples.

In the illustrated embodiment, and as already described, the input device 200 includes the touch panel 222 and the image capturing device 224. The image capturing device 224 is configured to capture an image of the user 106 or of an identification card (for example, a driver's licence) of the user 106. In the present case, the image capturing device 224 is a digital camera (for example, a "web cam") configured to capture an image of the user's 106 driver's licence in the form an image file (for example, a jpeg image file) for storage in memory 208. A process that involves capturing an image of the user's driver's licence to thereby obtain some of the user data is expected to offer advantages over prior systems in that it is expected to reduce the likelihood of typographical errors being made during data entry. It is also anticipated that such a process will reduce the time taken to obtain some of the user data from the user.

After having captured the image in an image file, the processing unit 212 uses a process, such as an optical character recognition (OCR) process, to process the resultant image file so as to extract, from the image, text portions that are representative of specific user data (for example, the user's name). It is not essential that OCR processing be performed since the image file will provide a recording of an image of the user data as contained on the driver's licence. Nevertheless, it is preferred that OCR processing be performed since it may allow for storage of user data in a form, such as a database, that is searchable.

After having accepted the rental information, the processing unit 212 of the processor 206 then activates the communications controller 214 to control the transceiver 204 to wirelessly communicate with a vehicle data unit 1 12 of the rental vehicle 102 identified by the vehicle identification information. In this example, since the vehicle identification data includes a code that uniquely identifies a selected rental vehicle 102, the communications controller 214 controls the transceiver 204 to broadcast a radio frequency (RF) signal, via the wireless communications channel 1 10, containing a unique address derived from the code and that is recognisable by the vehicle data unit 1 10 of the selected rented vehicle 102 as a request for that the vehicle data unit 1 12 of that rental vehicle 102 to provide vehicle data for that rental vehicle 102. However, where the vehicle identification data does not identify a specific vehicle, but instead identifies a type of rental vehicle, the processor 206 processes the vehicle identification data rental to derive a unique address of a rental vehicle 102 that corresponds with the rental vehicle type identified by the vehicle identification information.

Having received and decoded the signal broadcasted by the terminal 104, the vehicle data unit 1 12 of the selected rental vehicle 102 then communicates, again using an RF signal, the vehicle data to the terminal 104 via the wireless communications channel 1 10.

On receipt of the RF signal by the transceiver 204, the processor 206 processes the user data and the vehicle data (as contained in the second signal) to provide an agreement for acceptance by the user. In the present case, the processing of the user data and the vehicle data produces an agreement containing user data, including user data in the form of an image of the driver's licence and vehicle data. The agreement also includes the term and conditions of the rent. The agreement may be produced in any suitable form. One suitable form may include a graphical image of the agreement on the display 216. However, in the present case, the agreement is provided as a paper-copy that is generated using a printer in data communication with the printer interface 218.

One example of a suitable agreement 1 14 is illustrated in Fig.1 A. As shown, the agreement 1 14 includes user data 1 16-1 , 1 16-2, 1 16-3 provided by the user 106 (ref. Fig.1 ) and vehicle data 1 18 (shown as an odometer reading) obtained from the vehicle data unit 1 12 (ref. Fig.1 ) for a selected rental vehicle.

In the illustrated example, the user data 1 16-1 includes a scanned image of the user's 106 driver's licence, the user data 1 16-2 includes rental period information, and the user data 1 16-3 includes the user's telephone contact details.

Having provided the agreement to the user 106, and in order for the selected rental vehicle 102 to be released to the user 106, the user 106 must then accept the agreement. In this respect, in using the term "accept the agreement" we mean that the user must agree to be party to the agreement. The user 106 may acknowledge their acceptance of the agreement using any suitable device. In the present case, and with reference again Fig.2, the user 106 accepts the agreement by activating an "accept" button on the display 216 using the touch-panel 222.

Once the user has accepted the agreement, the selected rental vehicle 102 is released to the user 106. The release of the selected vehicle 102 to the user 106 may involve a rental agent confirming the user's acceptance of the agreement and handing the keys to the selected rental vehicle 102 to the user 106. In the illustrated embodiment, the releasing of the selected vehicle 102 also includes the terminal 104 broadcasting a signal addressed to the selected rental vehicle 102 to unlock that vehicle 102 by activating the central locking system onboard the vehicle 102. In this respect, such a signal may be broadcast to a lock controller (not shown) on board the selected vehicle 102 via the wireless communications channel 1 10, or it may be broadcast by another suitable communication channel. As described previously, the terminal 104 illustrated in Fig. 1 is operable by a user 106 to initiate data communication with a vehicle data unit 1 12 of a selected rental vehicle 102 over a wireless communications channel 1 10. Any suitable wireless communications channel may be used. As is illustrated in Fig.3, one suitable wireless communications channel 1 10 includes a channel that is provided by a communications network 300. In some embodiments the characteristics of the wireless communications channel 1 10 will vary according to the capability of communications network 300 providing that channel 1 10. For example, in embodiments in which the communications network 300 is a wide area communications network, such as a public land mobile network (PLMN), the wireless communications channel 1 10 may support GSM services, a GPRS services, a 3G service, or CDMA services.

In the present case, two channels are depicted in the example illustrated in Fig.3. Channel 1 10-A (shown surrounded with a solid line) is a PLMN channel providing GPRS services permitting packet based data communication between the terminal 104 and the vehicle data unit 1 12. For communicating via such a channel 1 10-A, both the terminal 104 and the vehicle data unit 1 12 include transceivers that are compatible with a PLMN GPRS service. Of course, other types of wireless communications channels may also be used. By way of example, a second wireless communications channel 1 10-B (shown surrounded with a dashed line) includes an wired connection 302 (such as an Ethernet connection) connecting the terminal 104 to a packet switched network 304 (such as the Internet) which in turn connects the terminal 104 to the vehicle data unit 1 12 via the PLMN network. Fig.4 depicts a system 400 in accordance with another embodiment that includes a terminal 104 that is in networked communications with one or more remote processing units, shown here as a hub 402.

The hub 402 depicted in Fig.4 provides the processing capacity for processing a transaction of the vehicle rental or return. An embodiment that includes a hub 402 is expected to provide additional benefits as it may provide an arrangement that supports multiple terminals 104 and thus multiple depots. In use, such a system may improve the ability to control the movements and/or distribution of rental vehicles between different depots so that, for example, adjustments in the number of rental vehicles located at each of the depots can be made in accordance with demand.

In addition, in a networked embodiment in which a hub 402 is communicatively coupled to multiple terminals 104 for respective vehicle depots, the hub 402 may be able to process depot status information for plural of the rental depots and use that information to influence the production of the agreement. For example, a networked embodiment of a system according to an embodiment of the present invention may include means for identifying a rental provider preferred return depot (based on status information for the rental depots) to which the selected vehicle is to be returned at the end of the rental period and include, in the agreement, an incentive offer for the user to return the selected vehicle to that depot. By way of example, an incentive may include a reduction in the cost of the rental. Such an embodiment may assist in the management of the distribution of rental vehicles across the rental depots. In addition, a system that includes a hub 402 may permit a centralised storage in a centralised database of user data and vehicle data for future retrieval. The storage of user data for future retrieval is expected to be particularly beneficial for rental processes for repeat users. Advantageously, an embodiment that includes a centralised database may provide further capabilities, including, but not limited to:

(1.) Centralised storage of a copy of the agreement.

(2.) Centralised storage of vehicle data including, when a vehicle was last serviced, what was replaced, how long since the bearings were checked and the like. Storage of servicing history may enable rapid verification of when a vehicle was inspected last and what was actually done to it.

Such information may also assist in ensuring that vehicle servicing runs more efficiently.

As shown in Fig.4, in addition to the hub 402 the illustrated system 400 also includes a communications channel 1 10-A (which, in the present case includes the Internet 304) providing connectivity between the terminal 104 and the hub 402 and, separately, connectivity between the hub 402 and the vehicle data unit 1 12. It will be appreciated that although the system 400 has been illustrated with a communications channel 1 10-A that includes a packet switched network 304 (such as the Internet), it is not essential that a packet-based communications channel be used, as any suitable communications channel 1 10 may be used. For example, in another embodiment another communications channel 1 10-B may be provided by a private wireless network, that includes a communications path between the hub 402 and the vehicle data unit 1 12, or indeed, or the terminal 104, the hub 402 and the and the vehicle data unit 1 12.

In one embodiment that includes a hub 402, the terminal 104 communicates accepted vehicle identification data to the hub 402 via a first communications network 404 (that is, the network including the packet switched network 304 and the hub 402). In such embodiments, the hub 402 includes a receiver for receiving the vehicle identification data via the first communications network 404 and a processor (hereinafter referred to as the "hub processor").

The hub processor (not shown) processes received vehicle identification data and activates wireless communication with the vehicle data unit 1 12 of the rental vehicle 102 identified by the vehicle identification data so as to obtain vehicle data there from via a second communications network 406 (that is, the network that connects the hub 402 and the vehicle data unit 1 12). Thereafter, the hub 402 communicates the obtained vehicle data to the terminal 104 via the first communications network 404) and the terminal 104 processes the received vehicle data to provide an agreement for acceptance by the user 106. Alternatively, the vehicle data unit 112 may communicate the obtained vehicle data to the terminal 104 directly (in other words, by bypassing the hub 402, or by bypassing the hub and the packet switched network 304)) using, for example, an alternative communications channel (such as 1 10-B shown dashed). In any event, upon acceptance of the agreement by the user 106 the selected rental vehicle 102 is released to the user 106.

As will be appreciated, there are numerous types and arrangements of network architectures and communications networks that would permit suitable connectivity between a terminal 104, a hub 402 and a vehicle data unit 1 12. Thus, it is not intended that the present invention be limited to the afore-described arrangements. By way of example, Fig.5 illustrates other examples of network connectivity schemes that may be suitable in other embodiments. In this respect, the following examples are provided to describe a typical rental process that may be performed with an embodiment of the system as illustrated in Fig.5. Example 1 : Rental Processing Sequence via Wireless Communications Channel

(1.) The user 106 selects a rental vehicle 102 from a pool 108 of available rental vehicles at the depot; (2.) The terminal 104 accepts rental information from the user, including vehicle identification data for a rental vehicle 102 and user data including an image of the user's drivers licence;

(3.) The terminal 104 wirelessly communicates, using wireless communications channel "A", with the vehicle data unit 1 12 of the rental vehicle 102 identified by the vehicle identification information;

(4.) The terminal 104 obtains from the vehicle data unit 1 12 (via wireless communications channel "A") vehicle data including vehicle kilometre information, vehicle fuel level information, and possibly other information, from the vehicle data unit 1 12; (5.) A processor on-board the terminal 104 processes the user data and the vehicle data to providing an agreement for acceptance by the user, the agreement including a image of the user's drivers licence and at least some of the vehicle data;

(6.) On acceptance of the agreement by the user, the selected vehicle 102 is released to the user 106.

Example 2: Rental Processing Sequence via Wireless Communications Channel "B"

(1.) The user 106 selects a rental vehicle 102 from a pool 108 of available rental vehicles at the depot.

(2.) The user 106 enters the vehicle identification data (for example, an "ID" number) for the selected vehicle 102 into the terminal 104. (3.) The terminal 104 accepts the vehicle identification data and connects to the hub 402 via a first communications network 500 (including the Internet 304) to communicate the vehicle identification data and the user data to the hub 402. (4.) The hub 402 then indexes a vehicle database containing availability information for the vehicle so as to check that the selected vehicle 102 is available. If the selected vehicle is available then the rental process continues and the hub 402 communicates with the terminal 104 to instruct the terminal 104 to request further rental information from the user 106. If the selected vehicle is unavailable, the user 106 is requested by the terminal 104 to contact a booking office to complete the hire. (5.) The user 106 enters into the terminal 104, other rental information including the rental period and user information including the user's driver's licence for image capture by the image capturing device 224. Once the user 106 has provided their licence, the image capturing device 224 captures an image of the licence. The entered information is then communicated to the hub 402.

(6.) Responsive to the receipt of the entered information, the hub 402 wirelessly communicates with the vehicle data unit 1 12 via a second communications network 502 (including the packet switched network 304) to obtain vehicle data, including the current co-ordinates of the vehicle based on its GPS location, vehicle odometer information and possibly other information. The hub 402 then processes the entered information and the obtained vehicle data to produce an agreement containing the information derived from the user information and the vehicle information.

(7.) After completion of (6.), the hub 402 communicates the agreement to the terminal via channel B and request that the terminal 104 print the agreement for acceptance by the user.

(8.) The user 106 then accepts or declines the agreement.

(9.) If the user accepts the agreement, a rental agent then confirms the details on the agreement match the user's 106 details. If anything is not correct then the rental agent may modify the agreement accordingly.

(10.) Following confirmation of the agreement details by the rental agent, the terminal 104 requests that the selected vehicle 102 be released. The terminal 104 then initiates a signal for unlocking the selected vehicle 102 and turning off a vehicle immobiliser. The keys to the selected vehicle 102 are then provided to the user 106.

Irrespective of which connectivity arrangement is selected, the providing of the agreement involves processing information that has been obtained from both the user 106 and the vehicle data unit 1 12. Providing an agreement in this way means that the accuracy of the information is less susceptible to errors, particularly in embodiments that obtain the user data from, or as, an image of the user's drivers licence.

The use of the system 100 (ref. Fig.1 ) for processing a transaction that involves returning a rental vehicle 102 to a rental vehicle provider is analogous to that described for processing rental of a rental vehicle 102. However, it will be appreciated that the rental data processed by the system 100 will vary.

By way of example, a system 100 for processing a rental vehicle return by a user 106 will accept vehicle identification data for a rental vehicle 102 being returned by the user 106 and use that data to wirelessly communicate with a vehicle data unit 1 12 of the rental vehicle identified 102 by the vehicle identification data 1 12 so as to obtain vehicle data therefrom. In addition, the processor 206 will process the vehicle data for the returned vehicle 102 to provide an agreement containing rental information for confirmation by the user. Upon confirmation of the report information by the user the returned vehicle 102 is released from the user.

Moreover, a system for processing a vehicle return transaction may also provide other functionality, including, for example, application software for requesting that user to pay an amount for the length of time that the vehicle was out on hire and perhaps modified in accordance with rental period parameters, for example, if the vehicle is returned late/early, or if a greater than allowed distance has been covered. For example, the system may automatically calculate a "late" fee according to the length of the period for which return of the vehicle was overdue. In addition, if the user reports that the vehicle is damaged an embodiment of the system will automatically bring that damage to the attention of management for further investigation.

It will thus be recognised that the present invention provides a system and method for processing rental and/or return of rental vehicles that is able to provide an agreement by processing data obtained from the user and the rental vehicle being rented, or returned by the user. Thus, it is envisaged that the present invention will provide efficient rental and return processing that provides improved accuracy in the information included in the agreement (such as a rental contract). Indeed, it is envisaged that a system, or method, according to an embodiment of the invention will at least reduce the time taken to release, or return, a rental vehicle to a user. Again, it is also envisaged that such a terminal, or system, will led to a reduced likelihood of errors in the agreement.

With general reference to Fig.5, the following example is provided to assist the reader in a typical application of an embodiment of a system for processing a rental vehicle return transaction that involves returning an automobile.

Example 3: Rental Return Transaction Processing

(1.) User 106 parks the vehicle 102 in a particular park of a return depot;

(2.) User 106 then enters the vehicle identification data into the terminal. (3.) The terminal 104 prompts the user 106 to enter user data, including damage information.

(4.) The terminal 104 communicates with the hub 402 which, in turn, communicates with the vehicle data unit 1 12 of the vehicle 1 12 to retrieve vehicle data in the form of location data (for example, GPS coordinates), odometer data, and possibly other data (for example, fuel level).

(5.) If, based on the vehicle location data the vehicle 102 has not been returned to the correct park, the hub 402 instructs the terminal 104 to prompt the user 106 to move the vehicle 102 to the correct park or advise an agent of the rental provider. (6.) If the vehicle 102 has been returned to the correct park then the hub 402 instructs the terminal 104 to produce an agreement for acceptance by the user (for example, a return docket) - that agreement identifies any extra charges that may be required for either time or distance used and for acceptance by the user 106. (7.) On acceptance of the agreement, the user 106 releases the vehicle 102 to an agent (not shown) of the rental provider by providing the vehicle keys back to the agent, or confirming that the user has left the key in the ignition of the vehicle, or deposited the key in a suitable location. Then the system communicates with the vehicle data unit 1 12 to immobilise the vehicle and lock the vehicle doors, and close the windows.

Fig.6A and Fig.6B illustrate lower level block diagrams depicting example communications interfaces between the hub 402 and plural terminals 106. As shown the communications interface may include a wired interface (ref. Fig.6A), or a wireless interface (ref. Fig.6B), or a combination of both. In addition, Fig.6A and FigθB each show a system that includes a hub 402 suitable for use with a system according to one form of the present invention. As is shown, the illustrated hub 402 includes a router 602, a network switch 604, a web server 606, a database server 608 and a fax server 610. In Fig.6A, the router 602 is a communication device providing connectivity between the hub 402 and the packet switched network 304. In the depicted example, the router 602 is a Cisco 1700 series router that includes program software to provide a firewall to reduce susceptibility to tampering from outside sources. In Fig.6B, the router 602 is a Cisco 1700 series router that connects to a private wireless network via a suitable communications device, such as a gateway.

The network switch 604, is of a conventional variety and, as such, provides a connectivity backbone between the devices of the hub 402. In the illustrated embodiment the web server 606 includes a server running on a suitable server platform (in the present case, "Windows Server 2000") and, in the present case, stores instructions and functions required by the terminal 104 (and a booking office) necessary to control the flow of data between the terminals 104, the hub 402, and the rental vehicles 1 12. Moreover, in the illustrated embodiment the web server 606 is uniquely communicatively coupled to the database server 608 to provide an extra level of data security. In addition, the web server 606 also controls the vehicle data units 1 12 (refer Fig.5) installed on the rental cars 102 (refer Fig.5).

In the illustrated embodiment, the database server 608 stores data for the terminals and the booking office. In the present case, the database server 608 is a Linux server. In addition to storing the required data, the database server 608 also provides data back up devices to secure backup of data in case of accidental loss.

Finally, the fax server 610 provides a backup method of communicating with the rental depot terminals. Thus, it is not essential that a fax server 610 be provided.

The present invention has been described with reference to a preferred embodiment and number of specific alternative embodiments. However, it will be appreciated by those skilled in the relevant fields that a number of other embodiments, differing from those specifically described, will also fall within the spirit and scope of the present invention. Accordingly, it will be understood that the invention is not intended to be limited to the specific embodiments described in the present specification.

Claims

CLAIMS:

1 . A system for processing a transaction between a user and a rental vehicle provider, including: (a) an input device for accepting rental data, the rental data including vehicle identification data for a selected rental vehicle and user data; (b) a wireless communications device for wirelessly communicating with a vehicle data unit of the rental vehicle identified by the vehicle identification data to obtain vehicle data therefrom; and (c) a processor for processing the user data and the vehicle data to produce an agreement for acceptance by the user; wherein the agreement includes information derived from the user data and the vehicle data.

2. A system according to claim 1 wherein the transaction is a vehicle rental transaction and wherein on acceptance of the agreement by the user the selected vehicle is released to the user.

3. A system according to claim 1 wherein the transaction is a vehicle return transaction and wherein on acceptance of the agreement by the user the selected vehicle is released from the user to the provider.

4. A system according to any one of clams 1 to 3 wherein the user data includes user identification information and wherein the input device includes a device for directly obtaining that information from an item containing that information.

5. A system according to claim 4 wherein the item is a driver's licence of the user and wherein the device for directly obtaining user data includes a device for reading or graphically recording the user's driver's license information.

6. A system according to claims 4 or 5 wherein the obtained license information includes an image of at least a portion of the user's driver's licence.

7. A system according to claim 6 wherein the portion includes an image of the user.

8. A system according to claim 6 or 7 wherein the providing of the agreement includes providing an agreement containing the at least a portion of image of the user's driver's licence.

9. A system according to any one of claims 1 to 8 wherein the vehicle data includes one or more of: (a) vehicle odometer information;

(b) vehicle fuel level information;

(c) vehicle location information;

(d) vehicle make and/or model information;

(e) vehicle registration information; and (f) vehicle status information.

10. A system according to any one of claims 1 to 8 wherein the vehicle is a trailer and wherein the vehicle data includes one or more of:

(a) trailer weight; (b) trailer size;

(c) trailer carrying capacity;

(d) trailer towing requirements;

(e) trailer registration status information;

(f) trailer location; (g) trailer colour; and

(h) trailer electrical requirements.

1 1 . A system according to any one of claims 1 to 10 wherein the user data includes one or more: (a) rental period information;

(b) user identification information;

(c) return depot information;

(d) payment method information; and

(e) return date information.

12. A system according to any one of claims 1 to 11 wherein the system further includes an output device for outputting the agreement.

13. A system according to any one of claims 4 to 12, when appended to claim 2, further including a communications device for communicating with a hub to obtain from the hub information identifying a rental provider preferred return depot for receiving the selected vehicle at the end of the rental period, and wherein the agreement identifies the preferred return depot and includes an incentive offer for the user to return the selected vehicle to that depot.

14. A system according to any one of claims 4 to 13 when appended to claim 2, further including a transmitter for communicating a signal to the selected vehicle to unlock that vehicle and wherein the releasing of the selected vehicle to the user includes the rental terminal communicating that signal to the vehicle.

15. A system according to claim 3, or any one of claims 4 to 1 1 when appended to claim 3, further including a signaling device for communicating a signal to the identified vehicle to lock that vehicle and wherein the releasing of the selected vehicle from the user includes the rental terminal communicating that signal to the vehicle.

16. A system according to claim 3, or any one of claims 4 to 1 1 when appended to claim 3, wherein the user data includes damage data for the returned vehicle, the damage data identifying whether the returned vehicle was damaged during the rental period and wherein the processing, by the processor, of the vehicle data to produce an agreement for acceptance by the user further includes processing the damage information for the returned vehicle.

17. A system according to claim 3, or any one of claims 4 to 1 1 when appended to claim 3, wherein the vehicle data includes data identifying actual location of the vehicle within a return depot, and wherein the system further includes a comparator for comparing the actual location with a desired location and, in the event that the actual location is different to the desired location, communicating to the user a message to move the vehicle to the desired location.

18. A method of processing a transaction between a user and a rental vehicle provider, including: an input device accepting rental data, the rental data including vehicle identification data for a selected rental vehicle and user data; a wireless communications device wirelessly communicating with a vehicle data unit of the selected rental vehicle to obtain vehicle data therefrom; and a processor processing the user data and the vehicle data to produce an agreement for acceptance by the user; wherein the agreement includes information derived from the user data and the vehicle data.

19. A method according to claim 18 wherein the transaction is a vehicle rental transaction and wherein on acceptance of the agreement by the user the selected vehicle is released to the user.

20. A method according to claim 18 wherein the transaction is a vehicle return transaction and wherein on acceptance of the agreement by the user the selected vehicle is released from the user to the provider.

21 . A method according to any one of clams 18 to 20 wherein the user data includes user identification information and wherein the input device includes a device for directly obtaining that information from an item containing that information.

22. A method according to claim 21 wherein the item is a driver's licence of the user and wherein the device for directly obtaining user data includes a device for reading or graphically recording the user's driver's license information.

23. A system according to claims 21 or 22 wherein the obtained license information includes an image of at least a portion of the user's driver's licence.

24. A method according to claim 23 wherein the portion includes an image of the user.

25. A method according to claim 23 or 24 wherein the providing of the agreement includes providing an agreement containing the at least a portion of image of the user's driver's licence.

26. A method according to any one of claims 18 to 25 wherein the vehicle data includes one or more of: (a) vehicle odometer information;

(b) vehicle fuel level information;

(c) vehicle location information;

(d) vehicle make and/or model information;

(e) vehicle registration information; and (f) vehicle status information.

27. A method according to any one of claims 18 to 25 wherein the vehicle is a trailer and wherein the vehicle data includes one or more of:

(a) trailer weight; (b) trailer size;

(c) trailer carrying capacity;

(d) trailer towing requirements;

(e) trailer registration status information;

(f) trailer location; (g) trailer colour; and

(h) trailer electrical requirements.

28. A method according to any one of claims 18 to 27 wherein the user data includes one or more: (a) rental period information;

(b) user identification information;

(c) return depot information;

(d) payment method information; and

(e) return date information.

29. A system for processing a transaction between a user and a rental vehicle provider, including:

(a) plural rental vehicle depots, each depot having access to a pool of rental vehicles including a vehicle data unit;

(b) at each depot, a terminal including:

(i) an input device for accepting rental data, the rental data including vehicle identification data for a rental vehicle and user data; (ii) a transmitter for communicating the vehicle identification data into a first communications network;

(c) a hub, communicatively coupled with the terminals via the first communications network, including:

(i) a receiver for receiving vehicle identification data from a terminal via the first communications network; and (ii) a communications device for activating wireless communication with a vehicle data unit of the rental vehicle identified by the received vehicle identification data to retrieve vehicle data therefrom; wherein either the hub, or the terminal, includes a processor for processing the vehicle data and the user data to provide, at the terminal, an agreement for acceptance by the user, the agreement including information derived from the user data and the vehicle data.

30. A system according to claim 29 wherein the transaction is a vehicle rental transaction and wherein on acceptance of the agreement by the user the selected vehicle is released to the user.

31 . A system according to claim 19 wherein the transaction includes a vehicle return transaction and wherein on acceptance of the agreement by the user the selected vehicle is released from the user to the provider.

32. A system according to claim 30 or 31 wherein the first communications network is a wide area communications network.

33. A system according to claim 32 wherein the wide area communications network is a mobile wireless network.

34. A system according to claim 32 wherein the wide area communications network is a private wireless network.

35. A programmed device for processing a rental transaction between a user and a rental vehicle provider, the device including: a processor; a memory; an input device; a wireless communications device; and a set of program instructions resident in the memory and executable by the processor to: accept rental data into the input device, the rental data including vehicle identification data for a selected rental vehicle and user data; activate the communications device for wirelessly communicating with a vehicle data unit of a rental vehicle identified by the vehicle identification data to obtain vehicle data therefrom; and process the user data and the vehicle data to produce an agreement for acceptance by the user; wherein the agreement includes information derived from the user data and the vehicle data.

36. A computer readable media containing a set of program instructions in the form of a computer program, the computer program executable by a processor of a device that also includes a memory, an input device, and a communications device, so that on execution of the program the processor: accepts rental data into the input device, the rental data including vehicle identification data for a selected rental vehicle and user data; activates the communications device for wirelessly communicating with a vehicle data unit of a rental vehicle identified by the vehicle identification data to obtain vehicle data therefrom; and processes the user data and the vehicle data to produce an agreement for acceptance by the user; wherein the agreement includes information derived from the user data and the vehicle data.

37. A computer software program executable by a processor of a device that also includes a memory, an input device, and a communications device, so that on execution of the program the processor: accepts rental data into the input device, the rental data including vehicle identification data for a selected rental vehicle and user data; activates the communications device for wirelessly communicating with a vehicle data unit of a rental vehicle identified by the vehicle identification data to obtain vehicle data therefrom; and processes the user data and the vehicle data to produce an agreement for acceptance by the user; wherein the agreement includes information derived from the user data and the vehicle data.

38. A system for processing a rental vehicle transaction between a user and a rental vehicle provider substantially as hereinbefore described with reference to any one of the accompanying drawings.

39. A method of processing a rental vehicle transaction between a user and a rental vehicle provider substantially as hereinbefore described with reference to any one of the accompanying drawings.