GB2551794A

GB2551794A - Authentication method & apparatus

Info

Publication number: GB2551794A
Application number: GB1611407.6A
Authority: GB
Inventors: Davis Louis-James
Original assignee: Vst Enterprises Ltd
Current assignee: Vst Enterprises Ltd
Priority date: 2016-06-30
Filing date: 2016-06-30
Publication date: 2018-01-03
Also published as: WO2018002621A1; GB201611407D0

Abstract

A method of authenticating a user to determine if they have permission to use a device comprises the steps of: storing at a server a unique code string identifying the device, and a user credential; generating a first data string by machine reading a code symbol on the device representing the unique code string; generating a second data string by machine reading biometric data credentials from the user; transmitting the first and second data strings to the server; establishing the identity of the device for which permission is sought from the first data string; establishing whether the user has permission to use the device from the second data string; generating an authorisation code at the server if the user is authenticated as having permission, and transmitting the authorisation code to the device to activate it for use by the user. The machine reader may be a mobile phone. The unique codes may be created by a random number generator and encoded by an encryption algorithm into a code symbol. The code symbol may be a light pattern, a sound sequence or a visual symbol. The device may be a vehicle, which is only operable after receipt of the authorisation code.

Description

(54) Title of the Invention: Authentication method & apparatus Abstract Title: Method of authenticating a user (57) A method of authenticating a user to determine if they have permission to use a device comprises the steps of: storing at a server a unique code string identifying the device, and a user credential; generating a first data string by machine reading a code symbol on the device representing the unique code string; generating a second data string by machine reading biometric data credentials from the user; transmitting the first and second data strings to the server; establishing the identity of the device for which permission is sought from the first data string; establishing whether the user has permission to use the device from the second data string; generating an authorisation code at the server if the user is authenticated as having permission, and transmitting the authorisation code to the device to activate it for use by the user. The machine reader may be a mobile phone. The unique codes may be created by a random number generator and encoded by an encryption algorithm into a code symbol. The code symbol may be a light pattern, a sound sequence or a visual symbol. The device may be a vehicle, which is only operable after receipt of the authorisation code.

At least one drawing originally filed was informal and the print reproduced here is taken from a later filed formal copy.

1/5

08 17

Fig. 1

2/5

08 17

3/5

08 17

ο co

CM

Fig. 3

4/5

Fig. 4

5/5

08 17

Fig. 5

AUTHENTICATION METHOD & APPARATUS

The present invention relates to a method and apparatus for authentication.

Typically, authentication for access to a particular situation, such as the use of a computer, phone or service (such as social media sites, for example) is conducted by the use of a user name and a password. The username is usually not secret, though it will inevitably assist the security of access if the username is kept secret. The password is, however, habitually kept secret. Such authentication methods do not per se, however, provide any further capacity to control or audit access.

The present invention provides an alternative.

Embodiments of the present invention will now be described, by way of example, and with reference to the accompanying drawings, in which:

Fig. 1 illustrates the generation of a code symbol; and

Figs. 2 to 5 illustrate a scenario of authentication according to an embodiment of the present invention;

Description of embodiments of the present invention will be most suitably made by reference to a sequence of drawings illustrating a scenario. Referring to Fig. 1, one element or ‘tool’ of relevance to embodiments of the present invention is a code format which provides sufficient address space to enable, for all practical purposes, an unlimited number of different codes to be generated. One embodiment of such a code format is based upon a 14 character hexadecimal number H_n. This provides an address space with around 2χ 10¹⁸ different numbers. Codes are generated using a random number generator 500. Once the number H_n has been generated, it is then encoded by a processor 502 running a dedicated algorithm into an indicium 504. Encoding the number H_n into an indicium serves a number of purposes. First, where the encoding algorithm is not made public, it performs an encryption function, since the value H_n of the number cannot be parsed from the indicium without the algorithm. Secondly, encoding a number into an indicium then provides a means by which the number may more readily and robustly be machine readable or assimilable, to enable rapid transfer between parties and transmitted across networks. The indicium may take any form that enables encryption and representation of a code number of the requisite format and so may be a light pattern (varying, over time, for example), a sound sequence or a visual symbol. In the present embodiment a visual symbol V is adopted in which the presence of black marks upon the white pathways represent the values of the 14 characters in the code H_n. The code H_n may be retrieved from the symbol 504 by scanning the symbol 504 with a scanning device 506 that then sends digitised data to the processor 502 which runs the algorithm then to generate the number H_n from that scanned data.

Embodiments of the invention are thus predicated firstly upon the premise that the visual representation of the code string H_n provides robust encryption; and secondly upon the presence and probity of a Trusted Administrator for the code. The Trusted Administrator will store values against the code H_n that permit it to provide trusted authority for the performance of an activity based upon the provision to the Trusted Authority of a code H_n and, for example, suitable credentials.

Referring to Fig. 2 one such scenario will now be described with reference to a heavy plant machine 200. Such machines are frequently left on site overnight because it is financially impractical not to do so. The machine 200 has a unique code H_n. H_n is encoded into a visual symbol 202 which is located upon the dashboard of the machine 200. The ignition of the machine, schematically illustrated by key 210, is configured to required the provision of an authorisation code AuthCode received, for example, over the mobile telephone network via a GPRS module 220 and then converted into a suitable data format via a processor 230 predicated upon the presence of a Trusted Administrator of code.

Referring additionally to Fig. 3, the authorisation code is held on a server 300 which is accessible via the URL http://www.administrationoftrustedcode.fake. The server holds a database of interrelational tables, some of which are schematically illustrated in Fig. 4. A first table, T1, holds code values of H_n against a UserlD, in this example XYZXYZ. The UserlD may be related to the owner or operator of the machine 200, for example, so that it may be that although several different machines each have a unique code H_n they are all mapped to a single UserlD on the trusted server 300. A second table T2 maps a given UserlD - here XYZXYZ - to credentials. In the illustrated example the UserlD XYZXYZ maps to the credential #*“**; it may also map to other credentials. In the present example, the credential ****** is derived from biometric data ***** such as a thumbprint, which is then stored in T2 after salting and hashing to protect against compromise of the security of the server 300 as ******

Referring to Fig. 3, when a user wishes to use the machine 200, the user first scans the code symbol 202 using a mobile telephone 250. The telephone may simply digitise the symbol 202 or translate it into an encrypted version of the code number H_n. In the former scenario the digitised symbol is returned to the server 300 as a data string and translated into H_n on the server 300; in the latter scenario an encrypted version of H_n is transmitted by the phone 250 to the server 300. The phone is then used to acquire the biometric data forming the authentication credentials. In the present embodiment the thumbprint 260 is scanned using the phone 250 and then digitised by it into the data ***** is then encrypted to the string {*****}. The digitised thumbprint {*****} and code number H_n are then sent to the server 300, forming an authorisation request for use of the machine 200 and, therefore the return of AuthCode to enable the machine ignition 210 to operate. In the present example they are sent together but can be sent separately with a suitable associating label enabling them to be paired at the server 300.

The server 300 then uses the table T1 to retrieve the UserlD XYZXYZ corresponding to the code H_n; and table T2 to map UserlD XYZXYZ to the Credentials which will trigger the issue of the authorisation code AuthCode to enable the machine 200 ignition 210. The encrypted biometric data {*****} is then decrypted and used, together with the salted and hashed stored biometric data ******* to establish the authenticity of the request for the issue of the authorisation code.

Referring to Fig. 5, upon establishing that the authorisation request is authentic, the server 300 then issues AuthCode to the machine via the mobile telephone network which, upon processing by the processor 220, causes the ignition 210 to become live and therefore actuable.

In a first modification, actuation of the ignition 210 is limited to a period of time after receipt of AuthCode, say 30 seconds. Alternatively or additionally, the AuthCode may merely be conditional that the ignition can occur upon the provision of some further data, such as the biometric data 260 used to require the authorisation code.

In yet a further modification, instead of biometric data for the provision of the Credentials, a further code H_n+i which identifies an authorised user, together with geolocation data may be used to trigger the release of AuthCode. Where geolocation data is used, this will typically be a data log of recent geolocation data received in connection with transactions conducted in connection with the code H_n+i. Thus, if it becomes unlikely that, having regard to recent transactions, the user of code H_n+1 could occupy the geolocation of the machine 200 at the time the authorisation request is sent, it will be refused.

In yet a further embodiment, biometric data is stored associated with the code H_n+1 and both are sent as part of the authorisation request, which is issued upon both the biometric data and H_n+1relating to each other and the UserlD of H_n+1 having the necessary validation permissions for ignition of the machine 200.

Claims

1. A method of authenticating a user for the provision of permission to user an artefact comprising the steps of:

5 storing, at a server:

a) , a unique code string identifying the artefact, and

b) . a user credential for the performance of the act in relation to the artefact;

machine reading a code symbol displayed on the artefact and which represents the unique code string to generate a first data string;

10 generating a second data string by machine reading biometric data credentials from the user;

transmitting the first and second data strings to the server;

establishing, on the basis of the first data string, the identity of the artefact in connection with which the permission is sought;

15 establishing, on the basis of the second data string, whether the biometric data credentials authenticate the user as having the permission;

in the event that the user is authenticated as having the permission, generating an authorisation code and transmitting the authorisation code to the artefact to activate the artefact for use by the user.

Intellectual

Property

Office

Application No: GB1611407.6 Examiner: Mr Robert Alexander