WO2017127072A1

WO2017127072A1 - Biometric authentication to a vehicle access system

Info

Publication number: WO2017127072A1
Application number: PCT/US2016/014142
Authority: WO
Inventors: Owen Carpenter
Original assignee: Ford Global Technologies, Llc
Priority date: 2016-01-20
Filing date: 2016-01-20
Publication date: 2017-07-27

Abstract

A vehicle access system is provided. The vehicle access system may include a vehicle access server which stores information regarding a plurality of motorized vehicles, which stores information regarding a driver, and which stores information regarding which of the plurality of vehicles the driver is permitted to operate. The system includes an authentication device which includes a computer processor and a biometric sensor which senses a biometric measurement of a person wearing the device. The authentication device is validated based on validation of biometric measurement of a person wearing the authentication device. A driver is permitted to access and operate any authorized vehicles via the authentication device after validation of the authentication device.

Description

BIOMETRIC AUTHENTICATION TO A VEHICLE ACCESS SYSTEM

BACKGROUND

FIELD OF THE INVENTION

[001] This invention relates to vehicular systems and more particularly to systems and methods for facilitating driver access to one or more vehicles.

SUMMARY OF THE INVENTION

[002] It is desirable to provide greater control over vehicle access. Modern vehicles may be benefitted by providing improved vehicle access systems which allow drivers to more easily access vehicles while also providing additional security to the vehicles. A vehicle access system may allow drivers to authenticate once daily and then obtain managed access to one or multiple vehicles throughout the day.

BRIEF DESCRIPTION OF THE DRAWINGS

[003] In order that the advantages of the invention will be readily understood, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered limiting of its scope, the invention will be described and explained with additional specificity and detail through use of the accompanying drawings, in which:

[004] FIG. 1 is a schematic diagram of an example vehicle access system. [005] FIG. 2 is a schematic diagram of an example wearable authentication

[006] FIG. 3 is a schematic diagram of an example vehicle access server.

[007] FIG. 4 is a schematic diagram of an example client computer.

[008] FIG. 5 is a flowchart illustrating example vehicle access procedures.

DETAILED DESCRIPTION

[009] It will be readily understood that the components of the present invention, as generally described and illustrated in the Figures herein, could be arranged and designed in a wide variety of different configurations. Thus, the following more detailed description of the embodiments of the invention, as represented in the Figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of certain examples of presently contemplated embodiments in accordance with the invention. The presently described embodiments will be best understood by reference to the drawings, wherein like parts are designated by like numerals throughout.

[0010] Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of various examples of the present invention. Also, common but well-understood elements that are useful or necessary in a

commercially feasible embodiment are often not depicted in order to facilitate a less obstructed view of these various embodiments of the present invention. [0011] Reference throughout this specification to "one embodiment", "an embodiment", "one example" or "an example" means that a particular feature, structure or characteristic described in connection with the embodiment or example is included in at least one embodiment of the present invention. Thus, appearances of the phrases "in one embodiment", "in an embodiment", "one example" or "an example" in various places throughout this specification are not necessarily all referring to the same embodiment or example. Furthermore, the particular features, structures or characteristics may be combined in any suitable combinations and/or sub-combinations in one or more embodiments or examples. . In addition, it is appreciated that the figures provided herewith are for explanation purposes to persons ordinarily skilled in the art and that the drawings are not necessarily drawn to scale.

[0012] FIG. 1 shows an example vehicle access system. Many vehicles 10 experience high use during a day. Additionally, many drivers may use a large number of different vehicles during a day. As an example, a delivery driver may access an assigned vehicle dozens of times during a day and may access multiple different vehicles during a day as they complete their assigned deliveries. An automobile salesman or automobile lot attendant may access many different vehicles during a day. Ride sharing vehicles may be accessed by multiple different drivers during a day and a driver participating in ride sharing may access multiple different vehicles during a day. In each of these situations, conventional vehicle security and access provided by vehicle keys adds inconvenience and reduces vehicle security. A driver who accesses their vehicle frequently during a day must store vehicle keys and retrieve these vehicle keys in order to access and operate the vehicle. A driver who may access multiple vehicles must keep multiple different vehicle keys and must determine which key corresponds to which vehicle in order to operate that vehicle. Vehicle security is compromised as increasing numbers of vehicle keys creates increased risk of misplaced, stolen, or improperly copied and distributed keys and vehicle access is obtained once a copy of a key is obtained.

[0013] A driver 14 may wear a wearable authentication device 18 that allows the driver to access and drive one or more vehicles 10. The authentication device 18 may authenticate the user through a biometric measurement such as the driver's electrocardiogram. The wearable authentication device 18 may be a wristband or bracelet and the driver 14 may wear the device on their wrist. A driver 14 may perform a required authentication procedure which may then be valid until the authentication device 18 is removed from the driver. The driver 14 may then remain authenticated until the device is removed and may obtain access to permitted vehicles until the device 18 is removed or otherwise becomes unauthenticated. This allows the driver 14 to authenticate once per day instead of every time they need access to a vehicle. The authentication device 18 may communicate with enabled vehicles 10 through Bluetooth communication, for example.

[0014] Vehicle access may be managed through a cloud vehicle access system. The cloud vehicle access system may include a vehicle access server 22. The server 22 may hold a list of all users who possess authentication devices 18 and a list of vehicles 10 which are enabled to work with the authentication devices 18. The server 22 includes data regarding which vehicles each driver 14 has access to. The cloud vehicle access system greatly simplifies the process of accessing different vehicles because data regarding all of the vehicles a user has access to is organized in one place. If a user authenticates them self in the morning, they instantly have access to all vehicles available to them without additional authentication. A driver 14 can access and drive a first vehicle 10A and then access and drive another authorized vehicle 10B without having to re- authenticate. This is a great time saver for users who need to use multiple vehicles for work or need to access the same vehicle multiple times per day.

[0015] The cloud vehicle access system may allow access to the vehicle access server 22 via another computer 26. This may allow persons to manage the driver lists and the authorized vehicle lists on the server 22. In this manner, a manager of a vehicle ride share company may manage a list of drivers who are members of the ride share and have access to ride share vehicles. The manager may manage a list of ride share vehicles and may assign vehicles of a particular type, location, etc. to individual ride share drivers as desired. In this manner, the vehicle access server 22 may include a database which allows for management of associated groups of vehicles and drivers.

[0016] When a driver 14 desires to access and drive a particular vehicle 10, the driver may approach the vehicle. Upon the driver approaching the vehicle to a required distance, pressing an unlock button on the vehicle, etc. the vehicle may receive an authentication device identification number from the authentication device 18. The vehicle 10 may then communicate a vehicle identification number and the authentication device identification number to the vehicle access server 22, such as by cellular or satellite network and via the internet 24, and the vehicle access server 22 may respond to the vehicle 10 allowing or denying driver access to the vehicle. A driver who has access to a vehicle 10 may thus approach, enter, and drive an authorized vehicle. [0017] The vehicle 10 may include an access control computer 30. The access control computer 30 may communicate with the wearable authentication device 18 and may facilitate use of the vehicle 10 by the driver 14. Accordingly, the access control computer 30 may include a communication module such as a Bluetooth communication transmitter/receiver which allows the access control computer 30 to communicate with the authentication device 18 as is indicated at 34. The access control computer includes the necessary hardware and software to implement the described functionality, and as such typically includes a processor, memory, a storage device, etc. The access control computer stores information such as a vehicle identification code which may be the VIN number of the vehicle 10. The access control computer stores software/firmware which provides computer instructions for processing data and for communicating with the authentication device 18 and other parts of the vehicle. The access control computer 30 includes input and output hardware which allows it to communicate with other parts of the vehicle 10.

[0018] The access control computer 30 may communicate with an engine control computer 38, a vehicle antenna 42, and other parts of the vehicle 10 such as door locks 46. As part of vehicle security, the engine control computer 38 may prevent the engine from running unless an authorization signal is provided to the engine control computer 38 from the access control computer 30. Once the engine control computer 38 has received an authorization signal from the access control computer 30, the engine may receive a start signal from a vehicle start switch/button to allow the driver 14 to start and operate the vehicle engine. [0019] The access control computer 30 may use a vehicle antenna 42 to communicate with the vehicle access server 22. As an example, the vehicle antenna 42 may use a cellular network to communicate with the vehicle access server 22 via the internet 24. Known communications equipment such as routers, switches, etc. may be used in this process. The access control computer 30 may receive a communication from the authentication device 18 including an identification code associated with the individual authentication device 18. The access control computer 30 may, via the vehicle antenna 42, send a communication to the vehicle access server 22 which includes the vehicle identification code and the authentication device identification code and which polls the vehicle access server 22 to determine if the driver associated with the authentication device 18 is permitted to operate the vehicle in question. The vehicle access server 22 may send a reply to the access control computer 30 indicating whether or not the driver 14 is permitted to operate the vehicle. If the driver 14 associated with the authentication device 18 is permitted to operate the vehicle 10, the access control computer 30 sends a signal to the engine control computer 38 (or another equivalent vehicle computer) authorizing operation of the vehicle 10. In some vehicles, functions associated with the access control computer 30 and the engine control computer 38 as well as other vehicle functions may be distributed across different vehicle control computers or modules or may be combined together into a combined control computer or module as is desirable.

[0020] It will be appreciated that, while various electronic components of the vehicle 10 such as computers, control modules, sensors, etc. are illustrated as separate components, various features may be implemented by a single computer or module. Similarly, the functionality described with respect to a single computer, module, sensor, etc. may be distributed across multiple separate components as is convenient for the manufacture of vehicles.

[0021] FIG. 2 shows a drawing of an example wearable authentication device 18. The authentication device 18 may include a computer processor 50, a battery 54, a biometric sensor 58, and a communications module 62. The battery 54 provides power to the authentication device 18. The computer processor 50 may include a processor, memory, and data storage. The computer processor 50 may store instructions and information which allows the authentication device 18 to communicate with the vehicle access server 22 to authenticate the driver 14 and to communicate with the vehicle 10 to allow the driver to access the vehicle 10. The computer processor 30 communicates with the biometric sensor 58 to receive biometric data from the driver 10. The communications module 62 may be a Bluetooth or cellular communications module and may communicate with the vehicle 10 and with the vehicle access server 22. The authentication device 18 may include a display device 64 such as an LCD screen which provides status indications and information to the driver 14. The authentication device 18 may include a sensor or other component to determine if the authentication device has been removed from a driver. For example, the authentication device 18 may be worn as a bracelet or watch by the driver 14. The computer processor 50 may include a resistance/continuity sensor and may be connected to wires 66 and contacts 70 which form part of a latch/connector 72 used to wear the authentication device 18 and create a continuous circuit around the circumference of the watch/bracelet when the authentication device 18 is fastened together as worn by the user. The computer processor 50 can detect a break in the continuity through the wires 66 and contacts 70 and may identify a break in continuity as removal of the authentication device and require re- authentication of the device 18 if the continuity is broken.

[0022] FIG. 3 shows a drawing of an example vehicle access server 22. As discussed, the vehicle access server 22 may be configured to perform one or more functions associated with managing driver access to individual vehicles. The vehicle access server 22 may include a processing device 74, a memory device 78, a communication device 82, and a user interface 86.

[0023] The processing device 74 can include memory, e.g., read only memory (ROM) and random access memory (RAM), storing processor-executable instructions and one or more processors that execute the processor-executable instructions. In embodiments where the processing device 74 includes two or more processors, the processors can operate in a parallel or distributed manner. In an example, the processing device 74 may execute a vehicle access module 90.

[0024] The communication device 82 is a device that allows the vehicle access server 22 to communicate with another device, such as one or more vehicles 10 and a computer 26. The communication device 82 can include one or more wireless transceivers for performing wireless communication and/or one or more communication ports for performing wired communication. While not shown, it is understood that the vehicle access server 22 and the communication device 82 may utilize the services of various known networking devices such as modems, routers, switches, cellular networks, etc. [0025] The memory device 78 is a device that stores data generated by or received by the vehicle access server 22. The memory device 78 can include, but is not limited to a hard disc drive, an optical disc drive, and/or a flash memory drive. Further, the memory device 78 may be distributed and located at multiple locations. The memory device 78 is accessible to the processing device 74. The memory device 78 stores information for implementing the present invention and may store a vehicle database 94, a driver database 98, and a client database 102 as well as any other databases and information useful for implementing the present system.

[0026] The vehicle database 94 can store information associated with vehicles 10. The vehicle database 94 may, for each vehicle, store information such as a vehicle identification code, vehicle VIN number, and vehicle manufacturer information. The vehicle database may also store communication information for each vehicle such as a communications network used to contact the vehicle, a vehicle number or code used to initiate communications with the vehicle, vehicle communications protocols, etc. The vehicle database 94 may also store information relevant to the content of a message sent to the vehicle. For example, the vehicle database may store the format and content of a message which may be sent to a vehicle access control computer 30 to allow a driver 14 to access and drive a vehicle 10 or alternatively to prevent a driver 14 from accessing and driving the vehicle 10. The vehicle access server 22 may obtain and store vehicle information from a vehicle manufacturer so that a customer using the vehicle access system does not need to provide such information. Certain procedures may be implemented to streamline the collection and use of this data. For example, if a vehicle is identified by using the VIN number as the vehicle identification code, a separate code does not need to be created and the identification code will be unique among all vehicle manufacturers. In such a situation, a vehicle VIN number will identify the vehicle manufacturer and a given vehicle manufacturer may use a predetermined communications network and signaling/messaging protocol with their vehicles. In this situation, the vehicle access server may store a database of information for each vehicle manufacturer and, upon receipt of a vehicle VIN number, may have all information necessary for communications with the vehicle.

[0027] The driver database 98 may store information associated with each driver 14. The driver database may store contact information for the driver and sufficient personal information to create a user account for the driver. The driver database may store information linking the driver 14 to a particular assigned authentication device 18, such as an identification code associated with the authentication device 18. The driver database 98 may store biometric information for the driver which is sufficient to determine if a person wearing/using the authentication device is in fact the driver 14 associated with the authentication device. As an example, the driver database 98 may store characteristic waveform information for the heartbeat generated electrical impulses for the driver 14 who is associated with a particular authentication device. From this biometric information, the vehicle access server 22 may identify a driver 14 who is using an authentication device 18 and then determine which vehicles the driver 14 is permitted to access and whether or not the driver is permitted to access a particular vehicle 10.

[0028] The client database 102 may store information associated with a particular client who uses the vehicle access system. The client may be an individual driver 14 who owns multiple vehicles 10 and desires easier access to the vehicles. The client may be a business such as an automobile dealership or a business with delivery vehicles that operates multiple vehicles 10 and may employ multiple drivers 14. The client may be a vehicle sharing business which owns multiple vehicles 10 and sells driving access to multiple drivers 14. Many clients may thus have multiple drivers and/or multiple vehicles and desire to provide easier access to and greater control over the vehicles. The client database may associate a particular client with vehicles which are owned by/controlled by that client and with drivers which are associated with that client. The client database 102 may include data fields which allow designation of vehicles for certain drivers, drivers for certain vehicles, time and location restrictions, etc. As such, the client database may allow a client to designate, for each driver associated with the client, which vehicles may be driven by that driver and any limitations such as when those vehicles may be driven by that driver.

[0029] A vehicle dealership client may thus designate that salesmen or lot attendants may drive any vehicles owned by the dealership during regular business hours. A ride sharing business client may designate as drivers paying customers of the business and may designate which vehicles may be driven by each driver. For example, certain drivers may be allowed to drive cars or compact vehicles while other drivers may be allowed to drive SUV's or trucks or all vehicles. These drivers may be limited on which vehicles they may drive based on their membership within the client company. A client with delivery vehicles may designate that delivery drivers may use delivery vehicles during business hours.

[0030] In this manner, a client may access the vehicle access server 22 and enter information for data fields in the client database 102 to create a listing of vehicles, drivers, and permissions for vehicles and drivers. The client may control access to the vehicles through the vehicle access server 22 rather than through control of copies of physical keys. In some situations, a driver may pertain to multiple clients. For example, a driver 14 may work at a vehicle dealership as a salesman. The vehicle dealership may provide vehicle access to the driver 14 through an authentication device 18. The driver 14 may also desire to use the authentication device to control access to personal vehicles, and thus may be an independent client of the vehicle access server 22. The same authentication device 18 may identify the driver 14 to the vehicle access server 22 and allow the driver 14 to access vehicles 10. The vehicle access server 22 may allow the driver 14 to access personal vehicles at all times and allow the driver to access dealership vehicles during business hours.

[0031] Referring now to FIG. 4, a schematic showing example components of the client computer 26 is illustrated. The computer 26 may include a processing device 106, a memory device 110, a communication device 114, and a user interface 118. The computer 26 can include other components and some of the components may not be required in every example.

[0032] The processing device 106 can include memory, e.g., read only memory (ROM) and random access memory (RAM), storing processor-executable instructions and one or more processors that execute the processor-executable instructions. In embodiments where the processing device 106 includes two or more processors, the processors can operate in a parallel or distributed manner. The processing device 106 can execute an operating system of the computer 26. In the illustrative example, the processing device 106 also executes a vehicle management module 122. [0033] The user interface 118 is a device that allows a user, a responsible agent of the client, in particular, to interact with the computer 26 and thereby interact with the vehicle management server 22. While one user interface 118 is shown, the term "user interface" can include, but is not limited to devices such as a monitor, a touch screen, a physical keyboard, a mouse, a microphone, and/or a speaker. The communication device 114 is a device that allows the computer 26 to communicate with another device, e.g., the server 22. The communication device 114 can include one or more wireless transceivers for performing wireless communication and/or one or more communication ports for performing wired communication. The communication device typically allows the computer 26 to communicate with the vehicle access server 22 via the internet 24. As such, the communication device may include a modem or networking device, and may work in combination with other communications equipment such as routers or switches to communicate with the vehicle access server 22. The memory device 110 is a device that stores data generated by or received by the computer 26. The memory device 110 can include, but is not limited to, a hard disc drive, an optical disc drive, and/or a flash memory drive. Computer software may be stored on the memory device 110 and the vehicle management module 122 and its associated data may be stored on the memory device 110.

[0034] The vehicle management module 122 allows a user, a responsible person/agent of the client in particular, to efficiently manage different drivers 14 and vehicles 10 associated with that client. In one example, the vehicle access server 22 may provide a secure/authenticated webpage login where a client may access the server 22 via the computer 26 and vehicle management module 122. The vehicle management module 122 may provide a software framework through which the computer 26 may receive information from the server 22 and provide information to the server 22. The vehicle management module 122 may receive information about associated drivers 14 and vehicles 10 and which drivers 14 are authorized to use client vehicles 14, add or remove drivers 14 or vehicles 10, add, remove, or modify driving authorization for specific vehicles or specific drivers, and transmit information regarding drivers 14, vehicles 10, and driver/vehicle driving authorization to the server 22.

[0035] FIG. 5 illustrates an example flowchart for operating a vehicle 10 with a wearable authentication device 18. A driver 14 may first authenticate 126 an authentication device 18. The driver may typically wear the device, such as by placing a watch or bracelet style of wearable authentication device on their wrist. The wearable authentication device 18 may close a circuit which encircles the wearers wrist when it is latched closed. The processor 50 of the wearable authentication device 18 may recognize that the authentication device is properly carried by the driver 14. The wearable authentication device 18 may then authenticate the driver 14. The authentication device processor 50 may, via the sensor 58, sense a biometric measurement from the driver 14 such as by detecting and recording the electrocardiogram signal when in contact with the driver's skin. The driver 14 may be authenticated by comparing the sensed biometric data with known/stored biometric data associated with the driver. The authentication device 18 may transmit biometric information to the server 22 and the server may compare the sensed biometric information with known biometric information and verify that the authentication device 18 is worn by the driver 14. The server 22 may transmit a signal to the authentication device to indicate that the driver has been authenticated. The authentication device 18 may transmit biometric data to the server 22 and authenticate the driver 14 when the driver first approaches a vehicle 10. The vehicle 10, access control computer 30, and vehicle antenna 42 and communications network may be used to transmit data between the server 22 and the authentication device 18. In some situations, a WIFI network or cellular network may be used to directly transmit data between the authentication device 18 and the server 22.

[0036] Once authenticated, the authentication device 18 is used to provide vehicle access to the driver 14. The driver 14 may approach 130 a vehicle 10 to access the vehicle. The vehicle access control computer 30 may sense the proximity of the authentication device 18 and information regarding the authentication device 18 may be transmitted 134 to the vehicle. The transmitted information may include an authentication device ID code, an authentication status, etc. The vehicle may transmit 138 information to the vehicle access server 22. This information may include the authentication device ID, authentication status, and the vehicle identification code or VIN.

[0037] The vehicle access server 22 may determine 142 if the authentication status of the wearable authentication device 18 is valid. The server 22 may determine if the driver 14 has authenticated with the authentication device 18 today (or in another predetermined period of time), if the authentication has been invalidated such as by removing the authentication device, etc. If the vehicle access server 22 determines 142 that the authentication is not valid, the authentication device 18 may attempt to re- authenticate 126 with the server 22. If the vehicle access server 22 determines 142 that the authentication is valid, the server 22 may then proceed to determine 146 if the driver 14 is authorized to access the particular vehicle 10 which has been approached 130 by the driver 14. Accordingly, the vehicle access server 22 may search the client database(s) 102 (or the driver database 98 or vehicle database 94, depending on the data structure within the server 22) to determine if the driver 14 has been granted permission to drive the vehicle 10 and whether or not any current restrictions apply to the driver 14.

[0038] By way of example, the driver 14 may have approached a personal vehicle and may be granted access to drive the vehicle. The driver 14 may have approached a work delivery vehicle and may be granted access to the vehicle. The driver 14 may have approached a work vehicle and may be denied access to the vehicle because it is not currently within operating hours of the business. The driver may approach a ride share vehicle and may be granted access to the vehicle as the driver is a member in good standing of the ride share company. The driver may approach a ride share vehicle and may be denied access to the vehicle as the driver has not paid to drive the type of vehicle which was approached. Similar to these examples, the vehicle access server 22 may determine 146 if the driver 14 is authorized to access and drive the vehicle 10. If the server 22 determines that the driver 14 is not authorized to drive the vehicle 10, the vehicle access server 22 may deny 150 access to the vehicle 10. If the server 22 determines that the driver 14 is authorized to drive the vehicle 10, the vehicle access server 22 may allow 154 access to the vehicle.

[0039] The vehicle access server 22 may then transmit 158 information to the vehicle 10. This information may be transmitted to the vehicle access control computer 30 via the vehicle antenna 42 and the communications network used by the vehicle 10. The vehicle 10 may transmit 162 information to the wearable authentication device 18. For example, the vehicle 10 may transmit a request status indicator signal which indicates to the authentication device 18 whether or not the driver 14 is permitted to access the vehicle 10. If desired, the authentication device 18 may include a display device 64 such as an LCD screen or LED indicator which may provide a status indication to the driver 14. For example, the authentication device 18 may use a red indicator light to indicate to the driver 14 that he is not permitted to access the vehicle 10 and may use a green indicator light to indicate to the driver 14 that he is permitted to access the vehicle 10. The authentication device 18 may use an audible sound signal or a vibration signal to indicate to the driver 14 whether or not he is permitted to access the vehicle 10. The authentication device 18 may include an LCD screen 64 and may provide the driver 14 with status indication via the screen. For example, the LCD screen may indicate to the driver 14 whether or not he has authenticated and whether or not he is permitted to access the vehicle 10.

[0040] If the driver 14 is permitted to access and drive the vehicle 10, the vehicle access control computer 30 may transmit 166 a signal to the vehicle engine control computer 38 or another vehicle computer to indicate that the vehicle may be operated. Such a signal may be used to manage the operational status and security of the vehicle by deactivating operation of the vehicle engine and vehicle electric locks unless an unlock or access signal is sent to the computer modules controlling operation of these vehicle components. The vehicle access control computer 30 transmitting 166 an access signal to the vehicle computer or vehicle engine control computer 38 may then permit the driver 14 to operate 170 the vehicle. The driver may be permitted to unlock the vehicle 10 (through an unlock button on the authentication device 18 or through an unlock button on the vehicle door handle, etc.), start the vehicle 10, and operate the vehicle 10. Following operation 170 of the vehicle 10, the driver may afterwards approach 130 the same vehicle 10 or another vehicle 10B and, if permitted, operate that vehicle.

[0041] The flowchart in FIG. 5 illustrates the architecture, functionality, and operation of a possible implementation of an example vehicle access system. In this regard, each block in the flowchart may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). Each block in the flowchart may represent a series of instructions or steps taken by a module or component of the system. It will also be noted that each block of the flowchart illustration, and combinations of blocks in the flowchart illustration, may be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

[0042] It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figure. In certain embodiments, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Alternatively, certain steps or functions may be omitted if not needed.

[0043] The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative, and not restrictive. The scope of the invention is, therefore, indicated by the appended claims, rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1. A vehicle access control system comprising:

a vehicle access server with data identifying a plurality of vehicles which a driver is permitted to drive; and

an authentication device assigned to and worn by a driver and validated by the vehicle access server that a person wearing the device is the driver, and which communicates with a vehicle access control computer to allow a validated driver to operate any of the plurality of vehicles after validation.

2. The system of claim 1, wherein the authentication device includes a computer processor and a biometric sensor, wherein the authentication device senses biometric information about a person wearing the authentication device, and wherein the biometric information is analyzed to determine if the person wearing the device is the driver.

3. The system of claim 1, wherein the biometric information is an electrocardiogram.

4. The system of claim 1, wherein the authentication device detects removal of the authentication device from the driver and wherein the validation is invalidated if the authentication device is removed from the driver.

5. The system of claim 1, wherein the authentication device remains validated with the vehicle access server until removed from the driver.

6. The system of claim 1, wherein the authentication device communicates wirelessly with the vehicle access control computer.

7. The system of claim 1, wherein the vehicle access control computer communicates wirelessly with the vehicle access server.

8. The system of claim 1, wherein the plurality of vehicles are associated with a client, and wherein a client may access the vehicle access server via a client computer to manage access to the plurality of vehicles by assigning vehicle driving privileges for particular vehicles and particular drivers.

9. The system of claim 1, wherein the vehicle access server stores information for a plurality of vehicles associated with a client, and wherein a driver associated with the client may be assigned driving privileges for one or more vehicles of the plurality of vehicles in the vehicle access server.

10. The system of claim 1, wherein the vehicle access control computer is configured to send a signal to an engine control computer to allow operation of the vehicle engine if the authentication device is worn by a driver who is permitted to operate the vehicle in the vehicle access server data.

11. A vehicle access control system comprising:

a plurality of motorized vehicles associated with a client, each of the plurality of motorized vehicles having an access control computer;

an authentication device which includes a computer processor and a biometric sensor which senses a biometric measurement of a person;

a vehicle access server which stores information regarding the plurality of motorized vehicles, which stores information regarding a driver, and which stores information regarding authorized vehicles which are selected from the plurality of vehicles and which the driver is permitted to operate;

wherein the authentication device is validated based on biometric measurement if a person with the authentication device is the driver; and

wherein the driver is permitted to access and operate any of the authorized vehicles via the authentication device after validation of the authentication device.

12. The system of claim 11, wherein the vehicle access server receives sensed biometric information from the authentication device, wherein the vehicle access server validates the biometric information against stored information regarding the driver, and wherein the authentication device is validated if the biometric information from the authentication device matches stored information regarding the driver.

13. The system of claim 11, wherein the authentication device is worn by the driver.

14. The system of claim 13, wherein the authentication device detects removal of the authentication device from the driver and wherein validation of the authentication device is invalidated if the authentication device is removed from the driver.

15. The system of claim 11, wherein the biometric measurement is an electrocardiogram signal.

16. The system of claim 11, wherein the authentication device remains validated until removed from the driver.

17. The system of claim 11, wherein the authentication device communicates wirelessly with the vehicle access control computer.

18. The system of claim 11, wherein the vehicle access control computer communicates wirelessly with the vehicle access server.

19. The system of claim 11, wherein the client may access the vehicle access server to manage access to the plurality of vehicles by assigning vehicle driving privileges for particular vehicles and particular drivers.

20. A method for controlling access to vehicles comprising:

storing, in a vehicle access server, data regarding a plurality of motorized vehicles associated with a client;

storing, in a vehicle access server, data regarding a driver associated with the client;

storing, in a vehicle access server, data regarding authorized vehicles which are vehicles selected from the plurality of vehicles and which are vehicles that the driver is permitted to operate;

validating, by the vehicle access server, that an authentication device which includes a computer processor and a biometric sensor which senses a biometric measurement of a person is worn by the driver based on biometric measurement from the authentication device; and

the vehicle access server permitting the driver to access and operate any of the authorized vehicles via the authentication device after validation of the authentication device.