WO2015042650A1

WO2015042650A1 - Frameworks, methodologies, systems and components configured to enable vehicle sharing

Info

Publication number: WO2015042650A1
Application number: PCT/AU2014/000943
Authority: WO
Inventors: William Davies; David TRUMBULL; Tony SIMOPOULOS
Original assignee: Car Next Door Australia Pty Ltd; Metavera Solutions, Inc
Priority date: 2013-09-26
Filing date: 2014-09-26
Publication date: 2015-04-02
Also published as: AU2014328469A1

Abstract

Described herein are frameworks, methodologies, systems and components configured to enable vehicle sharing. For example, embodiments include computer implemented frameworks, devices present in such frameworks, and methods implemented in those devices, which enable the provision of vehicle sharing services to users. In overview, various embodiments considered herein make use of electronic lockboxes, which are externally mountable to vehicles. Each lockbox includes a lockable compartment that is able to be accesses subject to authentication of an access code. In some embodiments the lockbox is configured such that the authentication is affected by a time-driven algorithm. In this manner, a given access code is only able to be successfully authenticated during a specific time period. In other embodiments the lockbox is configured to communicate with a remote server device, such that the authentication requirements (for example acceptable access code) are able to be controlled remotely.

Description

FRAMEWORKS, METHODOLOGIES, SYSTEMS AND COMPONENTS CONFIGURED TO ENABLE VEHICLE

SHARING

FIELD OF THE INVENTION

[0001 ] The present invention relates to frameworks, methodologies, systems and components configured to enable vehicle sharing. For example, embodiments include computer implemented frameworks, devices present in such frameworks, and methods implemented in those devices, which enable the provision of vehicle sharing services to users. Some embodiments include physical devices that, whilst disconnected from the computer implemented framework, are used in the context of such the framework thereby to enable vehicle sharing. While some embodiments will be described herein with particular reference to that application, it will be appreciated that the invention is not limited to such a field of use, and is applicable in broader contexts.

BACKGROUND

[0002] Any discussion of the background art throughout the specification should in no way be considered as an admission that such art is widely known or forms part of common general knowledge in the field.

[0003] Vehicle sharing is a practice whereby multiple users have access to a pool of available vehicles, for example cars, typically managed by a central system that charges a fee for car use. It is known to use various technological measures to configure a vehicle to participate in a vehicle sharing arrangement, for example by installing security and/or other devices into a car. Known measures are typically complex, requiring installation by a qualified person, such as an auto-electrician. This involves a cost and hassle which is viewed negatively by persons considering submitting a vehicle for use in such a vehicle sharing arrangement.

SUMMARY OF THE INVENTION

[0004] It is an object of the present invention to overcome or ameliorate at least one of the disadvantages of the prior art, or to provide a useful alternative. [0005] One embodiment provides a computer implemented method for enabling vehicle sharing, the method including:

(i) maintaining access to a vehicle database, wherein the vehicle database associates, by one-to-one relationships a plurality of vehicles to a plurality of lockbox Unique Identifiers (UID)s, wherein each lockbox UID corresponds to a specific physical lockbox device including a lockable compartment that is accessible subject to authentication of an inputted access code, wherein the authentication is affected by on a time-driven algorithm;

(ii) providing a bookings engine that enables a user, via a remote client device, to identify a vehicle in the vehicle database and defining booking parameters;

(iii) operating an access code determination module that, for a given booking, is responsive to the lockbox UID associated with the identified vehicle, thereby to determine a booking access code, wherein the determined booking access code is suitable for authentication during a specified time period; and

(iv) providing to the user a notification indicative of the booking access code. [0006] One embodiment provides a method wherein:

[0007] the authentication is affected by on a time-driven algorithm; [0008] the booking parameters include a pickup time; and

[0009] the access code determination module that is operated such that, for a given booking, is responsive to the pickup time and the lockbox UID associated with the identified vehicle, thereby to determine a booking access code, wherein the determined booking access code is suitable for authentication by the specific physical lockbox corresponding to the lockbox UID only during a time period defined by reference to the pickup time.

[0010] One embodiment provides a method wherein the time period defined by reference to the pickup time includes a predefined window preceding and following the pickup time. [001 1 ] One embodiment provides a method wherein the vehicle database additionally maintains, for a given vehicle, data indicative of a vehicle location.

[0012] One embodiment provides a method wherein the data indicative of vehicle location is determined based on a GPS device carried by the vehicle.

[0013] One embodiment provides a method including operating the access code determination module such that the determined booking access code corresponds to a code that is transmitted to the lockbox via a wireless communication.

[0014] One embodiment provides a method for enabling vehicle sharing, the method including:

[0015] providing an interface thereby to enable a user to complete a registration process thereby to register a vehicle for vehicle sharing;

[0016] based on the registration process, defining an entry representing the vehicle in a vehicle database; and

[0017] associating, in the vehicle database, the vehicle with a lockbox UID, wherein the lockbox UID corresponds to a specific physical lockbox device including a lockable compartment that is accessible subject to authentication of an inputted access code, wherein a given code is successfully authenticated only during a defined time period.

[0018] One embodiment provides a method wherein the authentication is affected by a time-driven algorithm.

[0019] One embodiment provides a method wherein the lockbox UID is inputted by the user.

[0020] One embodiment provides a method wherein the lockbox UID corresponds to a lockbox that is designated for delivery to the user.

[0021 ] One embodiment provides a method enabling vehicle sharing, the method including: [0022] maintaining access to a vehicle database, wherein the vehicle database stores data indicative of a plurality of registered vehicles, including, for each vehicle:

[0023] (i) vehicle booking data; and

[0024] (ii) a vehicle home location;

[0025] for each vehicle, monitoring a current vehicle location; and

[0026] executing a protocol thereby to take a predefined action, in respect of a given vehicle, based on observance of a prescribed relationship between the vehicle booking data, vehicle home location, and current vehicle location.

[0027] One embodiment provides a method wherein executing the protocol includes providing a notification to a user associated with an upcoming booking in the case that the vehicle is not at the home location at a time preceding a commencement time defined for the upcoming booking.

[0028] One embodiment provides a method wherein executing the protocol includes providing a notification to a user associated with a vehicle in the case that the vehicle leaves the vehicle home location in absence of a booking.

[0029] One embodiment provides a method wherein executing the protocol includes, in the case that a vehicle leaves the vehicle home location in absence of a booking, preventing the placing of bookings in respect of that vehicle.

[0030] One embodiment provides a method wherein executing the protocol includes allowing the placing of bookings in respect of that vehicle upon observing its return to the home location.

[0031 ] One embodiment provides a method including:

[0032] (i) maintaining access to a vehicle database, wherein the vehicle database associates, by one-to-one relationships a plurality of vehicles to a plurality of lockbox UIDs, wherein each lockbox UID corresponds to a specific physical lockbox device including a lockable compartment that is accessible subject to authentication of an inputted access code, wherein the authentication is affected by on a time-driven algorithm;

[0033] (ii) providing a bookings engine that enables a user, via a remote client device, to identify a vehicle in the vehicle database and defining booking parameters;

[0034] (iii) operating an access code determination module that, for a given booking, is responsive to the lockbox UID associated with the identified vehicle, thereby to determine a booking access code, wherein the determined booking access code is suitable for authentication during a specified time period; and

[0035] (iv) providing to the user a notification indicative of the booking access code.

[0036] One embodiment provides a method wherein:

[0037] the authentication is affected by on a time-driven algorithm;

[0038] the booking parameters include a pickup time; and

[0039] the access code determination module that is operated such that, for a given booking, is responsive to the pickup time and the lockbox UID associated with the identified vehicle, thereby to determine a booking access code, wherein the determined booking access code is suitable for authentication by the specific physical lockbox corresponding to the lockbox UID only during a time period defined by reference to the pickup time.

[0040] One embodiment provides a method for enabling vehicle sharing, the method including:

[0041 ] maintaining access to a vehicle database, wherein the vehicle database stores data indicative of a plurality of registered vehicles, including, for each vehicle, booking data, wherein the booking data include, for a given booking:

[0042] (i) a user associated with the booking; and

[0043] (ii) a commencement time for the booking; [0044] for each vehicle, monitoring a current vehicle location; and

[0045] in the case that a user is associated with a booking for a vehicle, the booking having a commencement time within a prescribed period of a current time, providing to the user data indicative of the current vehicle location.

[0046] One embodiment provides a computer program product for performing a method as described herein.

[0047] One embodiment provides a non-transitive carrier medium for carrying computer executable code that, when executed on a processor, causes the processor to perform a method as described herein.

[0048] One embodiment provides a system configured for performing a method as described herein.

[0049] Reference throughout this specification to "one embodiment", "some embodiments" 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, appearances of the phrases "in one embodiment", "in some embodiments" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment, but may. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner, as would be apparent to one of ordinary skill in the art from this disclosure, in one or more embodiments.

[0050] As used herein, unless otherwise specified the use of the ordinal adjectives "first", "second", "third", etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

[0051 ] In the claims below and the description herein, any one of the terms comprising, comprised of or which comprises is an open term that means including at least the elements/features that follow, but not excluding others. Thus, the term comprising, when used in the claims, should not be interpreted as being limitative to the means or elements or steps listed thereafter. For example, the scope of the expression a device comprising A and B should not be limited to devices consisting only of elements A and B. Any one of the terms including or which includes or that includes as used herein is also an open term that also means including at least the elements/features that follow the term, but not excluding others. Thus, including is synonymous with and means comprising.

[0052] As used herein, the term "exemplary" is used in the sense of providing examples, as opposed to indicating quality. That is, an "exemplary embodiment" is an embodiment provided as an example, as opposed to necessarily being an embodiment of exemplary quality.

BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings in which:

[0054] FIG. 1 schematically illustrates a framework according to one embodiment.

[0055] FIG. 2A illustrates a vehicle registration method according to one embodiment.

[0056] FIG. 2B illustrates a booking method according to one embodiment.

[0057] FIG. 3 illustrates a client-server framework leveraged by various embodiments.

[0058] FIG.4A illustrates a lockbox and mounting member according to one embodiment, shown with locking loop detached.

[0059] FIG. 4B provides a perspective of view the lockbox supported by a mounting member.

[0060] FIG. 4C provides a perspective view of the lockbox supported by a mounting member, shown mounted to a car window.

DETAILED DESCRIPTION

[0061 ] Described herein are frameworks, methodologies, systems and components configured to enable vehicle sharing. For example, embodiments include computer implemented frameworks, devices present in such frameworks, and methods implemented in those devices, which enable the provision of vehicle sharing services to users. In overview, various embodiments considered herein make use of electronic lockboxes, which are externally mountable to vehicles. Each lockbox includes a lockable compartment that is able to be accesses subject to authentication of an access code. In some embodiments the lockbox is configured such that the authentication is affected by a time-driven algorithm. In this manner, a given access code is only able to be successfully authenticated during a specific time period. In other embodiments the lockbox is configured to communicate with a remote server device, such that the authentication requirements (for example acceptable access code) are able to be controlled remotely.

Exemplary Booking Process

[0062] One embodiment provides a computer implemented method for enabling vehicle sharing. For example, this method is performed at a server (or across multiple server devices) thereby to enable management of bookings placed by users via respective client devices (which may include smartphones, PCs, and the like). The method includes maintaining access to a vehicle database, wherein the vehicle database associates, by one-to-one relationships a plurality of vehicles to a plurality of lockbox UIDs, wherein each lockbox UID corresponds to a specific physical lockbox device including a lockable compartment that is accessible subject to authentication of an inputted access code.

[0063] The lockbox is configured such that a given access code is able to be successfully authenticated only during a defined time period. That is, a code that is successfully authenticated during a first time period is not successfully authenticated during a second time period. There are a number of technological approaches for achieving this objective, including, but not limited to the following:

• Option A: Use of a lockbox that implements a time-based authentication algorithm.

That is, whether or not an inputted access code is successfully authenticated depends on a time at which the code is inputted. A software process may be executed on a PC or the like thereby to, with knowledge of the lockbox UID and/or lockbox unique authentication parameters, determined access codes that will be successfully authenticated at defined time. • Option B: Use of a lockbox that is configured to communicate with a remote server device (for example via a cellular network or the like) such that the authentication requirements (for example acceptable access code) are able to be controlled remotely. For example, in one embodiment a remote server is used to change authentication requirements on an as-required basis (for example changing the required access code at the completion of each vehicle booking).

• Option C: Use of a lockbox that is configured to communicate with a remote server device, such that the unlocking is controlled remotely. For example, a user sends a SMS to a predefined contact address and, subject to authentication, the lockbox is unlocked via a wireless signal initiated by the server device.

[0064] Embodiments discussed below focus on Option A, wherein the authentication is affected by on a time-driven algorithm. However, it should be appreciated that the other options above, or other options, may be used in further embodiments.

[0065] The method additionally includes providing a bookings engine that enables a user, via a remote client device, to identify a vehicle in the vehicle database and defining booking parameters, wherein the booking parameters include a pickup time. An access code determination module operates to, for a given booking, based on the pickup time and the lockbox UID associated with the identified vehicle, to determine a booking access code. The determined booking access code is suitable for authentication by the specific physical lockbox corresponding to the lockbox UID only during a time period defined by reference to the pickup time. A notification indicative of the booking access code is provided to the user.

Exemplary Car Registration Process

[0066] One embodiment provides a computer implemented method for enabling vehicle sharing. Again, this method is preferably performed at a server (or across multiple server devices) thereby to enable management of bookings placed by users via respective client devices (which may include smartphones, PCs, and the like). The method includes providing an interface thereby to enable a user to complete a registration process, and by such a process to register a vehicle for vehicle sharing (for example by submitting various details of personal information, and details of the vehicle). Based on the registration process, an entry representing the vehicle is defined in a vehicle database. The method also includes associating, in the vehicle database, the vehicle with a lockbox UID, wherein the lockbox UID corresponds to a specific physical lockbox device including a lockable compartment that is accessible subject to authentication of an inputted access code, wherein the authentication is affected by on a time-driven algorithm. In some cases the lockbox UID is inputted by the user (for example where the user first acquires a lockbox, and then registers) and in other cases the lockbox UID corresponds to a lockbox that is designated for delivery to the user (for example where the user first registers, and then has a lockbox sent to their location).

Exemplary Framework

[0067] FIG. 1 illustrates an exemplary framework according to one embodiment. This framework centres on a vehicle sharing management server 100. Although illustrated as a single component, it will be appreciated that the functionalities of server 100 may be provided by a plurality of separate (and optionally distributing) computing components. In broad terms, server 100 is configured to provide a vehicle sharing arrangement, whereby a plurality of vehicle-owner users register vehicles for sharing, and a plurality of vehicle- booking users register themselves thereby to gain access to bookings for the registered vehicles.

[0068] In the context of FIG. 1 , users (both vehicle-owner users and vehicle-booking users) interact with server 100 via respective client devices, illustrates in terms of an exemplary client device 130 and a plurality of further exemplary client devices 130'. Client devices may take the form of substantially any computing devices, including but not limited to PCs, notebooks, tables, smartphones, gaming consoles, kiosks, and so on. The manner of interaction may be via a web-browser arrangement, or via proprietary applications ("apps"). For example, client device 130 includes a microprocessor 131 configured to enable execution of computer executable code (software instructions) maintained on a memory module 132. A communications module 133 (for example a WiFi, Ethernet, cellular, or other communications module) enables communication between device 130 and server 100 via the Internet. For example, the software instructions may include a web browser module that enables rendering of a user interface provided by server 100. Alternately, the software instructions may include an app that inherently provides a user interface configured to provide access to functionalities of server 100. Inputs/outputs 134 enable a user to interact with device 130 (for example via buttons, a touchscreen, microphone, and so on), and a display screen 135 displays a rendering of the user interface.

[0069] FIG. 1 illustrates two exemplary vehicle component kits 140a and 140b, along with a plurality of further vehicle component kits 140'. It is not mandatory that both kits 140a and 140b be present; these represent optional alternate lockbox hardware configurations.

[0070] Vehicle component kit 140a includes a lockbox device 150a, which is able to be externally mounted to a vehicle, and a separate GPS device 156, which is in use mounted internally of the vehicle.

[0071 ] Lockbox device 150a includes mounting hardware 151 . Preferably mounting hardware 151 includes a brace, for example a window-mountable brace, which enables convenient mounting of the lockbox to the vehicle in a manner that enable external access. This includes external access to a lockable compartment 152, which is of sufficient size to contain a car key (or car key with keychain and car remote). The lockable compartment is able to be maintained in an unlocked (whereby it is able to opened by a user) or a locked configuration (whereby it is only able to be opened subject to authentication of an inputted access code. A user inputs an access code via a lock interface 153, which may include (for instance) a set of alphanumeric or numeric buttons, which are depressed in series to input an access code. A lock logic unit 154 (which includes a microprocessor and memory) is responsible for authentication of an inputted code, thereby to determine whether or not to progress the lockbox from the locked configuration to the unlocked configuration.

[0072] Lock logic unit 154 implements a time-driven authentication algorithm. That is, whether or not a particular inputted code is successfully authenticated is dependent on the time at which the access code in inputted. For example, the authentication algorithm processes an inputted code based on a time reading from a local clock (time and date based, or counter based) and a unique secure authentication key (unique to the lockbox, and associated with a device UID), thereby to determine whether the inputted access code is to be successfully authenticated. This algorithm preferably operates in a manner such that it is not a unique access code that is operable at any given point in time. By way of illustration: • A first access code might be successfully authenticated only between 1 PM and 3PM on a given day.

• A second access code might be successfully authenticated between 12PM and 4PM on that same day.

[0073] In this manner, the lockbox is unlockable based on a plurality of overlapping- time-dependent access codes.

[0074] Vehicle component kit 140b is generally the same as kit 140a, however its lockbox 140b includes an integrated GPS device 157 (in place of a separate GPS device 156).

[0075] Although GPS technology is specifically disclosed herein, alternate technologies may be used for enabling server 100 to determine a location of a vehicle, and the inventive concepts are by no means intended to be necessarily limited to use of GPS. In some embodiments reverse geographic coding is implemented to determine an address of a vehicle from the latitude longitude of the vehicle's GPS. This may be provided to borrowers and owners so they can find a give vehicle, and/or superimposed on a map. In some embodiments, server 100 is configured to provide users with access to location data for vehicles they have booked preceding a booking. For example, one embodiments includes storing, for a given booking: (i) a user associated with the booking; and (ii) a commencement time for the booking. In the case that a user is associated with a booking for a vehicle, the booking having a commencement time within a prescribed period of a current time, that user is provided with access to data indicative of the current vehicle location. For example, the user is provided with a map location for the vehicle, so they can observe whether it is in the prescribed pickup location, or en route to that location (or otherwise located).

[0076] Server 100 includes user interface modules 101 , which may interact with client devices 130 and 130' by way of a web browser arrangement or proprietary app arrangement (as discussed by reference to FIG. 3). User interface modules 101 include a user registration module that enables a user registration process, a vehicle registration module that enables a vehicle registration process (see FIG. 2A) and a booking interface module that enables bookings of vehicles by users (see FIG. 2B). [0077] A bookings engine 107 is responsible for managing vehicle bookings. In this regard, bookings engine 107 maintains access to user data 108 (which includes details for registered vehicle-booking users), vehicle data 109 (which includes details for registered vehicles, their lockbox UIDs, and locations) and bookings data 1 10 (which includes vehicle availability, and booking status information). Based on this data, a vehicle- booking user is able to place a booking by way of booking interface module 104 and bookings engine 107.

[0078] Based on a pickup time defined for a given booking, and the UID of the relevant lockbox, a code determination module is operated to determine an access code for the booking. The access code is communicated to the vehicle-booking user, for example via a SMS or other electronic message communicated via a notifications module 105. More specifically, code determination module 106 is configured to receive input indicative of a time range (defined in terms of time and date) and a lockbox UID. Based on this input, module 107 executes a code determination procedure, which outputs a code that is configured to be successfully authenticated by the relevant lockbox during the time range (based on knowledge of the manner of operation of the unique secure authentication keys of the plurality of lockboxes).

[0079] In overview, in one embodiment the framework of FIG. 1 is used as follows:

• Vehicle-owner users register via server 100, and are issued with a lockbox which they attach to the car window through use of the bracket, and the key is able to be stored safely within the lockbox with the car.

• A vehicle-booking user makes a booking via server 100 (or via other means, such as a phone-in service).

• Prior the booking time (for example 15 minutes prior), notifications module 105 sends the vehicle-booking user an access code to open the lockbox (as determined by module 106), as well as the current address of the vehicle (known that from the GPS tracking device).

• The vehicle-booking user goes to the vehicle, enters the access code, and the lockbox is unlocked. They remove the key, unlock the car, wind the window down and remove the lockbox and bracket from the window and put it in the car. • The vehicle-booking user uses the car as someone usually would. The GPS tracking device optionally measures the distance travelled for billing and/or other purposes.

• The vehicle-booking user returns vehicle (for example to an agreed location specified at the time of making the booking) at the end of the booking, and "ends' the booking using internet, smart phone, SMS or by other such means.

• When the booking is ended, another access code is sent to the user, thereby to enable the key to be replaced in the lockbox. The vehicle-booking user reattaches lockbox to car window, winds up window to lock it into place, then locks the car, and finally puts the key into the lockbox and locks it.

[0080] It will be appreciated that, from an implementation perspective, alternate approaches may be used via the framework of FIG. 1.

[0081 ] In some cases users are provided with functionality to request from server 100 a further lockbox code during a window of time following a completed booking, for example to enable a borrower to recover items inadvertently left in a vehicle, or in some cases to allow for late returns.

Exemplary Vehicle Registration Method

[0082] FIG. 2A illustrates a computer implemented method 200 for enabling vehicle sharing according to one embodiment. The method includes providing an interface thereby to enable a user to complete a registration process thereby to register a vehicle for vehicle sharing, including receiving vehicle registration data at 201 . The vehicle registration data may include owner details, license plate and registration details, vehicle details (make, year, condition), home location details, user specified conditions and availability parameters, and so on. An entry is then defined in a vehicle database at 202. The entry is associated with a specific lockbox UID at 203, such that server 100 is able torn via module 106, determine appropriate access codes for a lockbox based on booking pickup times and the like, being a lockbox wherein access code authentication is affected by on a time-driven algorithm. In some cases the lockbox UID is inputted by the user (for example where the user first acquires a lockbox, and then registers) and in other cases the lockbox UID corresponds to a lockbox that is designated for delivery to the user (for example where the user first registers, and then has a lockbox sent to their location). In some cases the entry is additionally associated with a GPS device UID, thereby to enable vehicle tracking.

[0083] At 204, a vehicle is made live for the purposes of the booking engine. This may be subject to input provided by the vehicle-owner user indicating that the lockbox and GPS are mounted and activated. This enables vehicle bookings at 205.

Exemplary Booking Method

[0084] FIG. 2B illustrates an exemplary booking method 220 according to one embodiment. This method assumes that access is maintained to a vehicle database, wherein the vehicle database associates, by one-to-one relationships a plurality of vehicles to a plurality of lockbox UIDs, wherein each lockbox UID corresponds to a specific physical lockbox device including a lockable compartment that is accessible subject to authentication of an inputted access code, wherein the authentication is affected by on a time-driven algorithm;

[0085] A user accesses a bookings engine at 221 . This bookings engine enables a user, via a remote client device, to search available vehicles registered for sharing at 222, and selects a desired vehicle at 223. At 224 the booking is finalised for the identified vehicle by inputting defining booking parameters (including a pickup time), agreeing to a payment regime, and so on

[0086] Functional block 225 represents a process including operating an access code determination module that, for a given booking, is responsive to the pickup time and the lockbox UID associated with the identified vehicle, thereby to determine a booking access code. The determined booking access code is suitable for authentication by the specific physical lockbox corresponding to the lockbox UID only during a time period defined by reference to the pickup time. The user is provided a notification indicative of the booking access code (for example via SMS or email) at a predefined time, as represented by functional block 226.

Exemplary Lockbox and Mount

[0087] FIG.4A illustrates a lockbox 400 according to one embodiment, shown with locking loop 401 detached. A mounting bracket 402 is also illustrated. In FIG. 4B these are shown in an assembled locked configuration. In FIG. 4C, lockbox 400 is supported by a mounting member 402 on a car window 403.

[0088] In some embodiments, the lockbox is in use partially covered by a protective sheath, thereby to protect it from weather and the like.

[0089] The mounting member includes an a-frame portion configured to be hung over a car door window, such that the mounting member is secured in place upon closure of the window. In some cases, a cable lock (or other securing member) may be attached to the mounting member thereby to securely attach the mounting member to the interior of the vehicle (hence to prevent the lockbox from being removed from the vehicle). In one example, a laptop-style cable lock is used, but that should not be regarded as necessarily limiting.

[0090] In some cases alternate lockbox arrangements are used. For example, a lockbox doesn't always have to mounted to a vehicle; it can be on the doorknob or on the owners fence, etc. In such cases the system is configured to provide directions to the lockbox to tell borrowers exactly where it is.

Home Locations

[0091 ] Each vehicle is preferably associated with one or more "home locations", which define locations from which the vehicle is available to be collected (and returned). For example, a user may define a first home location at their place of residence, and a second home location at their workplace. The vehicle may be made available for booking form each of those based on a defined schedule (for example the workplace home location during business house, and the residence home location during evenings and/or weekends). A user is enabled to define home locations, and schedules for those home locations (in terms of availability for a vehicle to be booked).

[0092] A home location is preferably defined by way of a zone, noting that a vehicle may be parked on a public street, and not necessarily always in the precise same location. Monitoring of Vehicle Locations

[0093] Some embodiments provide computer implemented methods that are implemented via server 100 (or other servers that provide car sharing platforms), making use of vehicle position tracking data (for example derived from GPS tracking devices 156 and/or 157).

[0094] One class of such computer implemented methods include maintaining access to a vehicle database, wherein the vehicle database stores data indicative of a plurality of registered vehicles, including. This include vehicle booking data (for example user IDs for users who have made bookings, booking commencement and completion times, pickup locations, and so on) and one or more vehicle home locations (for example a "home location" is a geographic region in which the car typically resides, and is available for pickup). The methods include, for each vehicle, monitoring a current vehicle location. A protocol is executed thereby to take a predefined action, in respect of a given vehicle, based on observance of a prescribed relationship between the vehicle booking data, vehicle home location, and current vehicle location. Several examples are discussed below.

[0095] In some cases executing the protocol includes providing a notification to a user associated with an upcoming booking in the case that the vehicle is not at the home location at a time preceding a commencement time defined for the upcoming booking. For example, this time might be 30 minutes or one hour preceding the commencement time (in other examples it is a shorter or longer lead time). This allows the booking user some warning that the car might in fact not be available to take in accordance with a given booking.

[0096] In some cases executing the protocol includes providing a notification to a user associated with a vehicle (i.e. a vehicle owner user) in the case that the vehicle leaves the vehicle home location in absence of a booking. For example, a vehicle owner user might be required/expected to book out their own vehicle for personal use, thereby to prevent other users from making bookings. Such notifications this may warn the vehicle owner user that they are taking their own vehicle without such a booking, and additionally provide warnings of upcoming third party bookings of their vehicle (thereby to inform the vehicle owner user of a time by which they should return the car to the home location). [0097] In some cases the protocol includes, in the case that a vehicle leaves the vehicle home location in absence of a booking, preventing the placing of bookings in respect of that vehicle. This may further include allowing the placing of bookings in respect of that vehicle upon observing its return to the home location. In essence this allows for an inferred booking to be made on behalf of a vehicle owner user in the event that they use their own vehicle without a booking. Server 100 in some embodiments provides additional functionalities for streamline vehicle owner bookings of their own vehicles.

[0098] Monitoring of vehicle location may also be used thereby to automatically confirm whether a vehicle is returned at completion of a booking. For example, vehicle return may be inferred from observing a vehicle being stationary in its home location for greater than a threshold time period (for example 15 minutes).

Exemplary Client-Server Framework

[0099] In some embodiments, methods and functionalities considered herein are implemented by way of a server, as illustrated in FIG. 3. In overview, a web server 302 provides a web interface 303. This web interface is accessed by the parties by way of client terminals 304. In overview, users access interface 303 over the Internet by way of client terminals 304, which in various embodiments include the likes of personal computers, PDAs, cellular telephones, gaming consoles, and other Internet enabled devices.

[00100] Server 303 includes a processor 305 coupled to a memory module 306 and a communications interface 307, such as an Internet connection, modem, Ethernet port, wireless network card, serial port, or the like. In other embodiments distributed resources are used. For example, in one embodiment server 302 includes a plurality of distributed servers having respective storage, processing and communications resources. Memory module 306 includes software instructions 308, which are executable on processor 305.

[00101] Server 302 is coupled to a database 310. In further embodiments the database leverages memory module 306.

[00102] In some embodiments web interface 303 includes a website. The term "website" should be read broadly to cover substantially any source of information accessible over the Internet or another communications network (such as WAN, LAN or WLAN) via a browser application running on a client terminal. In some embodiments, a website is a source of information made available by a server and accessible over the Internet by a web-browser application running on a client terminal. The web-browser application downloads code, such as HTML code, from the server. This code is executable through the web-browser on the client terminal for providing a graphical and often interactive representation of the website on the client terminal. By way of the web- browser application, a user of the client terminal is able to navigate between and throughout various web pages provided by the website, and access various functionalities that are provided.

[00103] Although some embodiments make use of a website/browser-based implementation, in other embodiments proprietary software methods are implemented as an alternative. For example, in such embodiments client terminals 304 maintain software instructions for a computer program product that essentially provides access to a portal via which framework 100 is accessed (for instance via an iPhone app or the like).

[00104] In general terms, each terminal 304 includes a processor 31 1 coupled to a memory module 313 and a communications interface 312, such as an internet connection, modem, Ethernet port, serial port, or the like. Memory module 313 includes software instructions 314, which are executable on processor 31 1. These software instructions allow terminal 304 to execute a software application, such as a proprietary application or web browser application and thereby render on-screen a user interface and allow communication with server 302. This user interface allows for the creation, viewing and administration of profiles, access to the internal communications interface, and various other functionalities.

Conclusions and Interpretation

[00105] Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions utilizing terms such as "processing," "computing," "calculating," "determining", analyzing" or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities into other data similarly represented as physical quantities. [00106] In a similar manner, the term "processor" may refer to any device or portion of a device that processes electronic data, e.g., from registers and/or memory to transform that electronic data into other electronic data that, e.g., may be stored in registers and/or memory. A "computer" or a "computing machine" or a "computing platform" may include one or more processors.

[00107] The methodologies described herein are, in one embodiment, performable by one or more processors that accept computer-readable (also called machine-readable) code containing a set of instructions that when executed by one or more of the processors carry out at least one of the methods described herein. Any processor capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken are included. Thus, one example is a typical processing system that includes one or more processors. Each processor may include one or more of a CPU, a graphics processing unit, and a programmable DSP unit. The processing system further may include a memory subsystem including main RAM and/or a static RAM, and/or ROM. A bus subsystem may be included for communicating between the components. The processing system further may be a distributed processing system with processors coupled by a network. If the processing system requires a display, such a display may be included, e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT) display. If manual data entry is required, the processing system also includes an input device such as one or more of an alphanumeric input unit such as a keyboard, a pointing control device such as a mouse, and so forth. The term memory unit as used herein, if clear from the context and unless explicitly stated otherwise, also encompasses a storage system such as a disk drive unit. The processing system in some configurations may include a sound output device, and a network interface device. The memory subsystem thus includes a computer-readable carrier medium that carries computer-readable code (e.g., software) including a set of instructions to cause performing, when executed by one or more processors, one of more of the methods described herein. Note that when the method includes several elements, e.g., several steps, no ordering of such elements is implied, unless specifically stated. The software may reside in the hard disk, or may also reside, completely or at least partially, within the RAM and/or within the processor during execution thereof by the computer system. Thus, the memory and the processor also constitute computer-readable carrier medium carrying computer-readable code.

[00108] Furthermore, a computer-readable carrier medium may form, or be included in a computer program product. [00109] In alternative embodiments, the one or more processors operate as a standalone device or may be connected, e.g., networked to other processor(s), in a networked deployment, the one or more processors may operate in the capacity of a server or a user machine in server-user network environment, or as a peer machine in a peer-to-peer or distributed network environment. The one or more processors may form a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.

[001 10] Note that while diagrams only show a single processor and a single memory that carries the computer-readable code, those in the art will understand that many of the components described above are included, but not explicitly shown or described in order not to obscure the inventive aspect. For example, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

[001 1 1] Thus, one embodiment of each of the methods described herein is in the form of a computer-readable carrier medium carrying a set of instructions, e.g., a computer program that is for execution on one or more processors, e.g., one or more processors that are part of web server arrangement. Thus, as will be appreciated by those skilled in the art, embodiments of the present invention may be embodied as a method, an apparatus such as a special purpose apparatus, an apparatus such as a data processing system, or a computer-readable carrier medium, e.g., a computer program product. The computer-readable carrier medium carries computer readable code including a set of instructions that when executed on one or more processors cause the processor or processors to implement a method. Accordingly, aspects of the present invention may take the form of a method, an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of carrier medium (e.g., a computer program product on a computer-readable storage medium) carrying computer-readable program code embodied in the medium.

[001 12] The software may further be transmitted or received over a network via a network interface device. While the carrier medium is shown in an exemplary embodiment to be a single medium, the term "carrier medium" should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term "carrier medium" shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by one or more of the processors and that cause the one or more processors to perform any one or more of the methodologies of the present invention. A carrier medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical, magnetic disks, and magneto-optical disks. Volatile media includes dynamic memory, such as main memory. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise a bus subsystem. Transmission media also may also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications. For example, the term "carrier medium" shall accordingly be taken to included, but not be limited to, solid-state memories, a computer product embodied in optical and magnetic media; a medium bearing a propagated signal detectable by at least one processor of one or more processors and representing a set of instructions that, when executed, implement a method; and a transmission medium in a network bearing a propagated signal detectable by at least one processor of the one or more processors and representing the set of instructions.

[001 13] It will be understood that the steps of methods discussed are performed in one embodiment by an appropriate processor (or processors) of a processing (i.e., computer) system executing instructions (computer-readable code) stored in storage. It will also be understood that the invention is not limited to any particular implementation or programming technique and that the invention may be implemented using any appropriate techniques for implementing the functionality described herein. The invention is not limited to any particular programming language or operating system.

[001 14] It should be appreciated that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, FIG., or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

[001 15] Furthermore, while some embodiments described herein include some but not other features included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention, and form different embodiments, as would be understood by those skilled in the art. For example, in the following claims, any of the claimed embodiments can be used in any combination.

[001 16] Furthermore, some of the embodiments are described herein as a method or combination of elements of a method that can be implemented by a processor of a computer system or by other means of carrying out the function. Thus, a processor with the necessary instructions for carrying out such a method or element of a method forms a means for carrying out the method or element of a method. Furthermore, an element described herein of an apparatus embodiment is an example of a means for carrying out the function performed by the element for the purpose of carrying out the invention.

[001 17] In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In other instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

[001 18] Similarly, it is to be noticed that the term coupled, when used in the claims, should not be interpreted as being limited to direct connections only. The terms "coupled" and "connected," along with their derivatives, may be used. It should be understood that these terms are not intended as synonyms for each other. Thus, the scope of the expression a device A coupled to a device B should not be limited to devices or systems wherein an output of device A is directly connected to an input of device B. It means that there exists a path between an output of A and an input of B which may be a path including other devices or means. "Coupled" may mean that two or more elements are either in direct physical or electrical contact, or that two or more elements are not in direct contact with each other but yet still co-operate or interact with each other.

[001 19] Thus, while there has been described what are believed to be the preferred embodiments of the invention, those skilled in the art will recognize that other and further modifications may be made thereto without departing from the spirit of the invention, and it is intended to claim all such changes and modifications as falling within the scope of the invention. For example, any formulas given above are merely representative of procedures that may be used. Functionality may be added or deleted from the block diagrams and operations may be interchanged among functional blocks. Steps may be added or deleted to methods described within the scope of the present invention.

Claims

CLAIMS:

1. A computer implemented method for enabling vehicle sharing, the method including:

(i) maintaining access to a vehicle database, wherein the vehicle database associates, by one-to-one relationships a plurality of vehicles to a plurality of lockbox UIDs, wherein each lockbox UID corresponds to a specific physical lockbox device including a lockable compartment that is accessible subject to authentication of an inputted access code, wherein the authentication is affected by on a time-driven algorithm;

(iv) providing to the user a notification indicative of the booking access code.

2. A method according to claim 1 wherein: the authentication is affected by on a time-driven algorithm; the booking parameters include a pickup time; and the access code determination module that is operated such that, for a given booking, is responsive to the pickup time and the lockbox UID associated with the identified vehicle, thereby to determine a booking access code, wherein the determined booking access code is suitable for authentication by the specific physical lockbox corresponding to the lockbox UID only during a time period defined by reference to the pickup time.

3. A method according to claim 2 wherein the time period defined by reference to the pickup time includes a predefined window preceding and following the pickup time.

4. A method according to claim 1 wherein the vehicle database additionally maintains, for a given vehicle, data indicative of a vehicle location.

5. A method according to claim 3 wherein the data indicative of vehicle location is determined based on a GPS device carried by the vehicle.

6. A method according to claim 1 including operating the access code determination module such that the determined booking access code corresponds to a code that is transmitted to the lockbox via a wireless communication.

7. A computer implemented method for enabling vehicle sharing, the method including: providing an interface thereby to enable a user to complete a registration process thereby to register a vehicle for vehicle sharing; based on the registration process, defining an entry representing the vehicle in a vehicle database; and associating, in the vehicle database, the vehicle with a lockbox UID, wherein the lockbox UID corresponds to a specific physical lockbox device including a lockable compartment that is accessible subject to authentication of an inputted access code, wherein a given code is successfully authenticated only during a defined time period.

8. A method according to claim 7 wherein the authentication is affected by a time- driven algorithm.

9. A method according to claim 7 wherein the lockbox UID is inputted by the user.

10. A method according to claim 7 wherein the lockbox UID corresponds to a lockbox that is designated for delivery to the user.

1 1 . A computer implemented method for enabling vehicle sharing, the method including: maintaining access to a vehicle database, wherein the vehicle database stores data indicative of a plurality of registered vehicles, including, for each vehicle:

(i) vehicle booking data; and

(ii) a vehicle home location; for each vehicle, monitoring a current vehicle location; and executing a protocol thereby to take a predefined action, in respect of a given vehicle, based on observance of a prescribed relationship between the vehicle booking data, vehicle home location, and current vehicle location.

12. A method according to claim 1 1 wherein executing the protocol includes providing a notification to a user associated with an upcoming booking in the case that the vehicle is not at the home location at a time preceding a commencement time defined for the upcoming booking.

13. A method according to claim 1 1 wherein executing the protocol includes providing a notification to a user associated with a vehicle in the case that the vehicle leaves the vehicle home location in absence of a booking.

14. A method according to claim 1 1 wherein executing the protocol includes, in the case that a vehicle leaves the vehicle home location in absence of a booking, preventing the placing of bookings in respect of that vehicle.

15. A method according to claim 14 wherein executing the protocol includes allowing the placing of bookings in respect of that vehicle upon observing its return to the home location.

16. A method according to claim 1 1 including:

17. A method according to claim 16 wherein: the authentication is affected by on a time-driven algorithm; the booking parameters include a pickup time; and the access code determination module that is operated such that, for a given booking, is responsive to the pickup time and the lockbox UID associated with the identified vehicle, thereby to determine a booking access code, wherein the determined booking access code is suitable for authentication by the specific physical lockbox corresponding to the lockbox UID only during a time period defined by reference to the pickup time.

18. A computer implemented method for enabling vehicle sharing, the method including: maintaining access to a vehicle database, wherein the vehicle database stores data indicative of a plurality of registered vehicles, including, for each vehicle, booking data, wherein the booking data include, for a given booking:

(i) a user associated with the booking; and

(ii) a commencement time for the booking; for each vehicle, monitoring a current vehicle location; and in the case that a user is associated with a booking for a vehicle, the booking having a commencement time within a prescribed period of a current time, providing to the user data indicative of the current vehicle location.

19. A computer system configured to perform a method according to any one of claims 1 to 18.

20. A computer program configured to perform a method according to any one of claims 1 to 18.

21 . A non-transitive carrier medium carrying computer executable code that, when executed on a processor, causes the processor to perform a method according to any one of claims 1 to 18.