Systems and methods for biometric authentication and generalised authentication protocols
The described system enhances biometric authentication by generating validation tokens and performing supplementary authentication based on configurable security information, addressing security and usability issues in existing systems, and enabling secure, low-friction access across multiple sectors.
Patent Information
- Application Number
- PCT/EP2026/064134
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-14
- Filing Date
- 2026-05-13
- Publication Date
- 2026-11-19
AI Technical Summary
Existing biometric authentication systems lack robustness, security, and usability, necessitating improved methods for user authentication that enhance security while maintaining user convenience.
A processing system that obtains face data, generates a validation token upon successful match, performs supplementary authentication based on configurable security information, and permits access only upon successful validation of user identifiers, utilizing tokenization to replace sensitive biometric data and enabling offline or online operations.
Provides secure, low-friction user authentication with enhanced security and usability by leveraging configurable security protocols and tokenization, applicable across various sectors and environments.
Smart Images

Figure EP2026064134_19112026_PF_FP_ABST
Abstract
Description
[0001] SYSTEMS AND METHODS FOR BIOMETRIC AUTHENTICATION AND GENERALISED AUTHENTICATION PROTOCOLS
[0002] FIELD OF THE INVENTION
[0003] The present disclosure relates to systems and methods for biometric authentication. In particular the present disclosure relates to biometric authentication using face data. In addition, the present disclosure relates to generalised authentication protocols operable across multiple authentication input modalities and across a plurality of deployment sectors.
[0004] BACKGROUND
[0005] The background description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description which may not otherwise qualify as prior art at the time of filing, are neither expressly or impliedly admitted as prior against the present disclosure.
[0006] It is known to use devices that gather biometric data from users for comparison with
[0007] stored biometric data for enabling user authentication. Various techniques exist for user authentication using biometric data. There is a need to provide user authentication with improved robustness, security and usability. Moreover, there is a need to provide streamlined user authentication with enhanced security. It is in this context that the present disclosure arises.
[0008] SUMMARY OF THE INVENTION
[0009] According to an aspect of the disclosure, a processing system comprising processing circuitry is configured to:
[0010] obtain face data for a user;
[0011] generate a validation token in response to a successful match based on the face data and a stored biometric token;
[0012] perform validation of the validation token;
[0013] determine whether to perform supplementary authentication processing in dependence on configurable security information, the configurable security information comprising one or more conditions for triggering the supplementary authentication processing;
[0014] wherein in response to determining that supplementary authentication processing is to be performed, the processing system is configured to:
[0015] obtain at least one user identifier associated with the user;
[0016] perform validation of the at least one user identifier; and
[0017] permit access for a resource conditional on successful validation of the at least one user identifier.
[0018] H 16964 WOThe configurable security information may comprise at least one of: first configurable security information comprising one or more scenario-related conditions; and second configurable security information comprising one or more validation-outcome related conditions for at least one of face data validation and validation-token validation.
[0019] One or more of the scenario-related conditions may specify one or more predetermined scenarios for which supplementary authentication processing is to be performed. One or more of the scenario-related conditions may specify at least one of: a time period; a geographical area and / or location associated with the user and / or a terminal device; a type of commercial sector associated with the resource, a type of information to be accessed; a type associated with the resource; and an amount associated with a financial transaction.
[0020] One or more of the validation-outcome related conditions specify at least one of: whether obtained face data results in a successful match for a stored biometric token; and whether a validation token results in successful validation.
[0021] The configurable security information may comprise a plurality of supplementary authentication processing routines, and the processing system may be configured to select a respective one of the plurality of supplementary authentication processing routines in dependence on one or more triggered conditions.
[0022] The configurable security information may comprise associations between one or more of the one or more conditions and one or more of the plurality of supplementary authentication processing routines.
[0023] The configurable security information may comprise a decision tree for selecting one or more user identifiers to be obtained for the user for the supplementary authentication processing, and optionally an order for obtaining and validating the one or more user identifiers.
[0024] The configurable security information may comprise at least one condition defined in advance by the user. The configurable security information may further comprise at least one supplementary authentication processing routine defined in advance by the user.
[0025] The configurable security information may comprise a plurality of respective authentication processing levels, each respective authentication processing level may comprise one or more conditions, and wherein the configurable security information may define the plurality of respective authentication processing levels to have a hierarchical ordering so that the plurality of respective authentication processing levels are evaluated in hierarchical order.
[0026] H 16964 WOThe processing system may be configured to: determine a highest-ordered respective authentication processing level comprising one or more triggered conditions; and perform supplementary authentication processing in dependence on the highest-ordered respective authentication processing level comprising one or more triggered conditions.
[0027] The processing system may be configured to: detect at least one device identification parameter wirelessly communicated by a registered user device associated with the user; and perform validation of the least one device identification parameter wirelessly communicated by the registered user device.
[0028] The processing system may be configured to activate an image sensor to capture the face data for the user in response to successful validation of the at least one device identification parameter wirelessly communicated by the registered user device.
[0029] The processing system may be configured to obtain the at least one device identification parameter wirelessly communicated by the registered user device for use as at least one user identifier for the supplementary authentication processing.
[0030] The configurable security information may comprise a first-ordered level of the plurality of respective authentication processing level, in which the first-ordered level may comprise one or more conditions which when triggered require the at least one device identification parameter wirelessly communicated by the user device to be validated.
[0031] The processing system may be configured to operate in an offline mode, and the system may comprise: a terminal device comprising an image sensor to capture the face data for the user; and a user device associated with the user, wherein the user device comprises secure token storage circuitry to store one or more preloaded biometric tokens and communication circuitry configured to communicate a preloaded biometric token to the terminal device for temporary storage at the terminal device. The terminal device may be configured to permit access for the resource without accessing one or more other devices.
[0032] The terminal device may be configured to: obtain the face data for the user; generate the validation token in response to a successful match based on the face data and the preloaded biometric token communicated by the user device; and perform validation of the validation token.
[0033] The preloaded biometric tokens may be time-limited tokens which are updated periodically.
[0034] The processing system may be configured to operate in an online mode, and the system may comprise a terminal device and one or more servers, the terminal device comprising first
[0035] H 16964 WOprocessing circuitry to: obtain the face data for the user; generate an encryption result in dependence on the face data; and communicate the encryption result to the one or more servers, wherein the one or more servers comprise second processing circuitry to: generate the validation token in response to the successful match based on the face data and the stored biometric token; and perform validation of the validation token; wherein at least one of the first processing circuitry and the second processing circuitry is configured to: determine whether to perform the supplementary authentication processing in dependence on the configurable security information; wherein in response to determining that supplementary authentication processing is to be performed, at least one of the first processing circuitry and the second processing circuitry is configured to: obtain at least one user identifier associated with the user; perform validation of the at least one user identifier; and permit use of a resource conditional on successful validation of the at least one user identifier.
[0036] According to another aspect of the disclosure, a computer-implemented method comprises:
[0037] obtaining face data for a user;
[0038] generating a validation token in response to a successful match based on the face data and a stored biometric token;
[0039] performing validation of the validation token;
[0040] determining whether to perform supplementary authentication processing in dependence on configurable security information, the configurable security information comprising one or more conditions for triggering the supplementary authentication processing;
[0041] in response to determining that supplementary authentication processing is to be performed:
[0042] obtaining at least one user identification parameter associated with the user; performing validation of the at least one user identification parameter; and permitting access for a resource conditional on successful validation of the at least one user identification parameter.
[0043] According to another aspect of the disclosure, a computer program comprises instructions which, when executed by a processing system, cause the processing system to perform the above method.
[0044] According to another aspect of the disclosure, a processing system comprising processing circuitry, wherein the processing system is configured to:
[0045] obtain at least one authentication input for a user;
[0046] perform validation of the at least one authentication input against a corresponding reference, the reference being accessible to the processing system at the time of validation;
[0047] H 16964 WOdetermine whether to perform supplementary authentication processing in dependence on configurable security information, the configurable security information comprising one or more conditions for triggering the supplementary authentication processing;
[0048] wherein in response to determining that supplementary authentication processing is to be performed, the processing system is configured to:
[0049] obtain at least one user identifier associated with the user;
[0050] perform validation of the at least one user identifier; and
[0051] permit access for a resource conditional on successful validation of the at least one user identifier.
[0052] The validation may comprise generating a non-reversible representation of the authentication input for comparison with a corresponding non-reversible reference.
[0053] In other words, non-reversible in this context means such that the original authentication input cannot feasibly be recovered from the representation, by any method satisfying applicable local and international data protection regulations governing the processing, storage, and transmission of authentication data.
[0054] According to another aspect of the disclosure, a processing system comprising processing circuitry, wherein the processing system is configured to:
[0055] obtain at least one authentication input for a user;
[0056] presence detection; motion detection; ambient sensor input; and a time-based trigger; or any other authentication input from which a user may be identified or a session may be initiated; perform validation of the at least one authentication input against a corresponding reference;
[0057] determine whether to perform supplementary authentication processing in dependence on configurable security information, the configurable security information comprising one or more conditions for triggering the supplementary authentication processing;
[0058] wherein in response to determining that supplementary authentication processing is to be performed, the processing system is configured to:
[0059] obtain at least one user identifier associated with the user;
[0060] perform validation of the at least one user identifier; and
[0061] permit access for a resource conditional on successful validation of the at least one user identifier.
[0062] The at least one authentication input may comprise one or more of, by way of example only and not as a limitation: face data; voice input; iris scan; fingerprint; gesture input; a device identification parameter wirelessly communicated by a registered user device associated with the user; a geolocation parameter.
[0063] H 16964 WOAccording to another aspect of the disclosure, a processing system comprising processing circuitry, wherein the processing system is configured to:
[0064] obtain at least one authentication input for a user;
[0065] perform validation of the at least one authentication input against a corresponding reference;
[0066] evaluate configurable security information, the configurable security information comprising a plurality of authentication processing levels arranged in hierarchical order, the plurality of authentication processing levels comprising a duress detection level, the duress detection level comprising one or more conditions for detecting duress on the basis of any signal accessible to the processing system, including one or more user properties, environmental properties, behavioural properties, or contextual properties;
[0067] determine a highest-ordered authentication processing level comprising one or more triggered conditions;
[0068] in response to triggering of the duress detection level, cause the processing system to enter a limited access mode for one or more resource types; and
[0069] permit access for a resource conditional on the outcome of the highest-ordered authentication processing level.
[0070] The processing system of the previous aspects may be configured to be operable in an online mode in which validation of the authentication input is performed using one or more remote processing resources, and to be operable in an offline mode in which validation of the authentication input is performed locally without requiring access to one or more remote processing resources, using a reference accessible to the local processing environment, wherein the configurable security information operates identically in both modes. A reference to being accessible to the local processing environment may be a reference preloaded from a user device associated with the user.
[0071] The at least one authentication input may comprise a plurality of authentication inputs, and wherein the validation may be performed against one or more references corresponding to the plurality of authentication inputs.
[0072] According to another aspect of the disclosure, we provide a processing system comprising processing circuitry, wherein the processing system is configured to:
[0073] obtain at least one authentication input for a user via a browser-accessible interface; perform validation of the at least one authentication input against a corresponding reference;
[0074] determine whether to perform supplementary authentication processing in dependence on configurable security information; and
[0075] H 16964 WOpermit access for a resource conditional on the validation outcome, the access being permitted within a single session.
[0076] Obtaining authentication input via a browser-accessible interface may mean that the input is obtained without requiring a registered user device associated with the user or an installed application
[0077] According to another aspect of the disclosure, we provide a processing system comprising processing circuitry, wherein the processing system is configured to:
[0078] obtain at least one authentication input for a user;
[0079] determine whether the authentication input corresponds to a live user, by any process achieving the determination;
[0080] determine an age classification for the user, by any process achieving the determination; generate a token encoding the age classification; and
[0081] permit access for a resource conditional on the token satisfying one or more age-related conditions associated with the resource.
[0082] According to another aspect of the disclosure, we provide a processing system comprising processing circuitry, wherein the processing system is configured to:
[0083] detect a trigger event comprising one or more of: a scannable optical marker interaction, a user input, and an ambient sensor input;
[0084] in response to the trigger event, obtain at least one authentication input for a user; generate a reference for the user associated with a future session identifier;
[0085] on a subsequent interaction by the user, recognise the user via the at least one authentication input, reactivate the future session identifier, and permit access for a resource associated with the future session identifier.
[0086] A scannable optical marker interaction may include a QR code interaction.
[0087] The processing system may be configured to establish a persistent session for a user across a plurality of access points associated with a defined role, and wherein triggering of the duress detection level causes modification of access permissions for one or more of the plurality of access points.
[0088] According to another aspect of the disclosure, we provide a processing system configured to: detect a plurality of device identification parameters wirelessly communicated by a plurality of registered user devices within a defined proximity;
[0089] determine a lead device from the plurality of registered user devices in dependence on one or more parameters associated with the registered user devices;
[0090] H 16964 WOestablish a session associated with the lead device and one or more secondary devices.
[0091] The one or more parameters associated with the registered user devices may include signal parameters, location parameters, user-elected priority, and / or contextual parameters.
[0092] In response to successful validation of the authentication input and the at least one user identifier, the processing system may be configured to trigger one or more interface logic events at one or more output devices within a defined proximity of the user, the one or more interface logic events being determined in dependence on the validation outcome and the proximity of the user.
[0093] According to another aspect of the disclosure, we provide a processing system comprising processing circuitry, wherein the processing system is configured to:
[0094] obtain aggregate presence data for a defined zone, the aggregate presence data including but not limited to a plurality of device identification parameters wirelessly communicated by a plurality of registered user devices within the defined zone;
[0095] determine a density metric for the defined zone in dependence on the aggregate presence data;
[0096] evaluate the density metric against one or more routing conditions; and
[0097] in response to the density metric satisfying one or more routing conditions, transmit one or more routing instructions to one or more output devices.
[0098] The at least one authentication input may comprise a device identification parameter wirelessly communicated by a registered user device entering a defined zone, and wherein the processing system may be configured to activate a session for the user within the defined zone in response to successful validation of the authentication input, the session activating one or more services associated with the defined zone without requiring application software to be installed on the registered user device.
[0099] According to another aspect of the disclosure, we provide a processing system comprising processing circuitry, wherein the processing system is configured to:
[0100] monitor a plurality of density metrics across a plurality of defined zones in dependence on aggregate presence data, including but not limited to device identification parameters wirelessly communicated by a plurality of registered user devices;
[0101] evaluate the plurality of density metrics against one or more emergency conditions; and in response to the one or more emergency conditions being satisfied, transmit zonespecific instructions to one or more output devices to route users between zones, the zone-specific instructions being updated in dependence on changes in the density metrics.
[0102] H 16964 WOAccording to another aspect of the disclosure, we provide a processing system comprising processing circuitry, wherein the processing system is configured to:
[0103] obtain one or more product identification parameters from one or more products by a product identification mechanism;
[0104] obtain at least one authentication input for a user;
[0105] perform validation of the at least one authentication input and the one or more product identification parameters; and
[0106] in response to successful validation, authorise a transaction associated with the one or more products and permit physical egress.
[0107] The product identification mechanism may include one of a short-range wireless communication from one or more product tags, optical recognition, weight-based detection, or any other suitable product identification method as is known in the art.
[0108] The authorisation of the transaction associated with the one or more product and permission of physical egress may be performed without requiring manual interaction.
[0109] According to another aspect of the disclosure, we provide a processing system comprising processing circuitry, wherein the processing system is configured to:
[0110] generate a reference for a user, the reference being accessible to processing systems associated with a plurality of venues operated by distinct operators;
[0111] at a first venue, perform validation of at least one authentication input for the user against the reference and activate a session for the user at the first venue;
[0112] at one or more further venues, perform validation of at least one authentication input for the user against the same reference and activate a session for the user at each of the one or more further venues, without requiring re-registration at any further venue.
[0113] The generation of a reference for a user may be made by any mechanism providing such accessibility, including but not limited to a centralised registry, a federated identity protocol, a distributed ledger, or a peer-to-peer reference exchange.
[0114] The processing system may be configured to:
[0115] map a plurality of defined zones associated with a sequence of locations the user is anticipated to or does traverse;
[0116] at each of the plurality of defined zones, perform validation of the at least one authentication input and activate one or more context-aware services associated with that zone in dependence on the zone identity and the user's position within the sequence.
[0117] H 16964 WOThe plurality of zones associated with the sequence of locations may be provided by reference to a travel itinerary, an event-day sequence, an appointment sequence, or a user-defined zone sequence.
[0118] The processing system may be further configured to:
[0119] establish a notification subscription associated with the user at a point of initial registration, the notification subscription being established via an interface accessible to the user device without requiring installation of a native application on a user device associated with the user;
[0120] at each of the plurality of defined zones, in response to successful validation of the at least one authentication input, automatically deliver one or more zone-specific notifications to the user device via the notification subscription, the content of the one or more zone-specific notifications being determined in dependence on the zone identity and the user's position within the sequence;
[0121] wherein the notification subscription, once established, remains active and operable across the plurality of defined zones without requiring the user to re-subscribe, to re-authenticate the subscription, or to install any application at any subsequent zone in the sequence.
[0122] The notification subscription may be established via a browser-accessible interface or a progressive web application interface.
[0123] The automated delivery of notifications may be by any delivery mechanism including but not limited to direct transmission, relay through one or more intermediate nodes, or retrieval triggered by the validation event.
[0124] According to another aspect of the disclosure, we provide a computer-implemented method comprising:
[0125] obtaining at least one authentication input for a user;
[0126] performing validation of the at least one authentication input against a corresponding reference;
[0127] determining whether to perform supplementary authentication processing in dependence on configurable security information, the configurable security information comprising one or more conditions for triggering the supplementary authentication processing;
[0128] in response to determining that supplementary authentication processing is to be performed:
[0129] obtaining at least one user identifier associated with the user;
[0130] performing validation of the at least one user identifier; and
[0131] permitting access for a resource conditional on successful validation of the at least one user identifier.
[0132] H 16964 WOAccording to another aspect of the disclosure, we provide computer software which, when executed by a processing system, causes the processing system to carry out the above method.
[0133] According to another aspect of the disclosure, we provide a processing system comprising processing circuitry, wherein the processing system is configured to:
[0134] obtain at least one authentication input for a user;
[0135] perform a validation operation on the at least one authentication input;
[0136] determine whether to perform supplementary authentication processing in dependence on configurable security information, the configurable security information comprising one or more conditions for triggering the supplementary authentication processing, the one or more conditions being evaluable against the validation outcome regardless of the process used to produce the validation outcome;
[0137] wherein in response to determining that supplementary authentication processing is to be performed, the processing system is configured to:
[0138] obtain at least one user identifier associated with the user;
[0139] perform a validation operation on the at least one user identifier by any process operable to produce a validation outcome; and
[0140] permit access for a resource conditional on the validation outcome of the at least one user identifier.
[0141] The validation operation on the at least one authentication input may be by any process operable to produce a validation outcome, including but not limited to:
[0142] comparison against a corresponding reference;
[0143] generation of a non-reversible representation of the authentication input for comparison with a corresponding non-reversible reference;
[0144] evaluation of the authentication input against one or more behavioural properties, environmental properties, or contextual properties;
[0145] computation of one or more confidence metrics for the authentication input; evaluation of the authentication input by one or more distributed processes operating across a plurality of processing resources; or
[0146] any other process operable to produce a validation outcome from the authentication input;
[0147] Various aspect and features of the present disclosure are defined in the appended claims and within the text of the accompanying description.
[0148] BRIEF DESCRIPTION OF THE FIGURES
[0149] In order that the present disclosure may be more readily understood, embodiments thereof will now be described, by way of example only, with reference to the accompanying drawings, in which:
[0150] H 16964 WOFigure 1 is a schematic diagram illustrating an example processing system;
[0151] Figure 2 is a schematic diagram illustrating a terminal device;
[0152] Figure 3 is a schematic diagram illustrating a first processing device;
[0153] Figures 4 and 5 are schematic flowcharts illustrating methods for user authentication using face data;
[0154] Figures 6a, 6b and 6c are schematic flowcharts illustrating methods for user authentication using configurable security information;
[0155] Figure 7 is a schematic flowchart illustrating a method for user authentication using configurable security information comprising three authentication processing levels;
[0156] Figure 8 is a schematic diagram illustrating a system comprising a user device and a terminal device;
[0157] Figure 9 is a schematic flowchart illustrating a generalised authorisation protocol applicable to one or more authentication inputs;
[0158] Figure 10 is a schematic diagram illustrating a processing system operable to obtain authentication input from one or more of a plurality of authentication input modalities;
[0159] Figure 11 is a schematic flowchart illustrating a method for user authentication using configurable security information comprising a plurality of authentication processing levels including a duress detection level;
[0160] Figure 12 is a schematic diagram illustrating cross-venue session activation using a reference accessible to processing systems associated with a plurality of venues;
[0161] Figure 13 is a schematic diagram illustrating multi-zone session activation across a sequence of defined zones associated with a user;
[0162] Figure 14 is a schematic diagram illustrating aggregate presence routing using a plurality of device identification parameters across one or more defined zones; and
[0163] Figure 15 is a schematic diagram illustrating product identification with authentication-conditional egress at an exit point.
[0164] DETAILED DESCRIPTION OF THE DISCLOSURE
[0165] Figure 1 schematically illustrates an example processing system for user authentication. The example processing system comprises a terminal device 101, a first processing device 102 (also referred to as a biometric authentication device 102), and a second processing device 103 (also referred to as a validation-token validation device 103). The terminal device 101 , the first processing device 102, and the second processing device 103 are each operable to communicate via one or more communications networks indicated by the arrowed lines in Figure 1. The dashed arrowed line indicates that in some cases the second processing device 103 may optionally communicate information to the terminal device 101 without communication via the first processing device 102. For example, the second processing device 103 may communicate a validation
[0166] H 16964 WOoutcome to the terminal device using a communications path that may or may not include the first processing device 102. The devices 101, 102 and 103 may communicate using one or more of a local area network (LAN), a wide area network (WAN) (e.g., the Internet, etc.), a mobile communications network or other suitable networks.
[0167] The terminal device 101 is a client-side device that is accessible by users for attempting user authentication. The terminal device 101 may be provided at various locations / environments for allowing authentication of one or more users (e.g. retail environments, access for buildings and events and so on). Successful user authentication may permit access for one or more resources for potentially wide-ranging applications. In some examples, the first processing device 102 and the second processing device 103 may be client-side devices. In other examples, the first processing device 102 and the second processing device 103 may each be server-side devices. In some examples, the first processing device 102 may be a first server device, and the second processing device 103 may be a second server device.
[0168] The techniques of the present disclosure are applicable for authenticating a user based on at least face data using biometric tokenisation. Authentication using face data can provide a low-friction and secure user authentication process. For example, a user can simply arrange their face within a field-of-view of an image capture device (e.g. an image sensor built in or connected to a terminal device) for attempting user authentication. In some examples, the techniques of the present disclosure may be used for secure payment (e.g. transaction authorisation, identity-validated request) processing using face data for authentication. A user may complete a financial transaction (e.g. in a shop or other similar venue) using face data alone. In other examples, face data and one or more other user identifiers may also be used. The techniques of the present disclosure will firstly be introduced using examples in which face data alone may be used for permitting access to a resource (e.g. completing a financial transaction), and techniques using supplementary authentication processing involving one or more other user identifiers will be discussed later.
[0169] Although the techniques are described primarily by reference to face data as the authentication input, it will be appreciated that the principles of the present disclosure are applicable to any suitable authentication input. References to face data throughout the description may be substituted, by way of example only and not as a limitation, with one or more of: voice input, iris scan, fingerprint, gesture input, a device identification parameter wirelessly communicated by a registered user device, a geolocation parameter, presence or motion detection, ambient sensor input, a time-based trigger, or any other authentication input from which a user may be identified or a session may be initiated. The configurable security information, supplementary authentication processing, hierarchical authentication levels, decision-tree pathway selection, and dual-mode (online and offline) operation described herein operate identically regardless of the type of authentication input used.
[0170] H 16964 WOThe techniques of the present disclosure are sector-agnostic and may be deployed across any context in which authentication-conditional resource access is required. By way of example only and not as a limitation, examples include: civic identity registration, age verification, voting, physical and digital lock control, insurance claim processing, content access, venue pre-check and access, vehicle fuelling, wellness service access, healthcare diagnostics, fitness access, transport, charitable donations, subscription management, queue management, analytics, automotive ignition, electric vehicle charging, motorsport operations, personal safety with duress detection, banking and financial transactions, fastfood and retail ordering, pharmacy retail, education and campus access, health insurance, aviation crew identity, retail checkout, events and concerts, and child safety. In each context, the processing system is configured with sector-specific configurable security information, the underlying authentication architecture being applicable across all such contexts.
[0171] The techniques of the present disclosure will generally be described in relation to a processing system comprising the terminal device 101 , the first processing device (also referred to as a biometric authentication device), and the second processing device 103 (also referred to as a validator device, which may in some cases be one or more backend servers). However, in some cases the functionality described in relation to the first processing device 102, and the second processing device 103 may be implemented as a single device (e.g. a single server may perform the functionality of the first and second processing devices). The techniques of the present disclosure allow for online biometric authentication (i.e. using one or more online devices such as servers) and also allow for offline biometric authentication without accessing one or more online devices. Moreover, in some cases references to a processing system may refer to the terminal device 101 on its own (or more generally one or more client-side devices). Techniques for offline biometric authentication are discussed in more detail later.
[0172] Referring to Figure 2, the terminal device 101 comprises processing circuitry 1011 (e.g. one or more CPUs and / or GPUs or similar) for processing instructions, and a memory 1012 for storing the instructions to be processed. The memory 1012 may take any suitable form. For example, the memory 1012 may comprise a combination of non-volatile memory (e.g. SSD) and volatile memory (e.g. RAM) for temporary storage of data. In particular, in the techniques of the present disclosure, the terminal device 101 can be operable to obtain face data for a user (using an image sensorthat may be part of the terminal device, connected to the terminal device, or at least in communication with the terminal device) and the face data can be temporarily stored using volatile memory and processed by the processing circuitry 1011.
[0173] The terminal device 101 also comprises communication circuitry 1013 for communication with one or more other devices. The communication circuitry 1013 may be configured to communicate
[0174] H 16964 WOusing, by way of example only and not as a limitation, one or more of a wired communication (e.g. USB, Ethernet) and / or wireless communication (e.g. Bluetooth®, Wi-Fi®, LTE and so on), or any other communication protocol satisfying the relevant communication requirement. The terminal device 101 may also comprise an image sensor 1014 and / or a connection port (e.g. USB port) for achieving a wired connection with an image capture device comprising the image sensor 1014. Image data captured by the image sensor 1014 can thus be obtained for processing by the processing circuitry 1011. The image sensor 1014 can be used to capture a live image comprising at least some (or all) of a user's face. The image sensor 1014 may comprise one or more of: one or more visible image sensors operable to detect visible light; one or more infrared image sensors operable to detect infrared light; and one or more image sensors each operable to detect both visible light and infrared light (e.g. one or more RGB-lr sensors). By way of example only and not as a limitation, CMOS image sensors and / or CCD image sensors may be used, or any other image sensor technology capable of capturing the relevant image data. In some examples, the image senor may be so-called RGB colour sensor. The image sensor(s) can be arranged so that the field-of-view (FOV) includes a region expected to be occupied by a user. More generally, the processing circuitry 1011 is operable to obtain face data from the image sensor 1014 for processing according to the techniques to be discussed below.
[0175] The terminal device 101 may also comprise a user interface 1015 (e.g. in the form of a touch panel display or the like) for outputting information to a user and / or receiving input from a user. For example, the user interface 1015 may be used to output information for confirming success or failure of user authentication, and optionally for outputting information requesting one or more inputs from the user for cases in which one or more user identifiers may be requested as part of user authentication processing. Alternatively or in addition, the terminal device may comprise or be coupled to one or more audio output units for outputting information to a user. For example, the terminal device 101 may be used at an event (e.g. sporting event) and used for permitting access (e.g. by permitting opening of an access gate or similar) and an audio output unit may be provided for outputting information for confirming success or failure of authentication, and optionally for outputting information requesting one or more inputs (e.g. a voice input and / or gesture input which may be used for supplementary authentication processing). More generally, the terminal device 101 may comprise one or more interfaces for outputting information to users and receiving inputs from users.
[0176] Referring to Figure 3, the first processing device 102 (also referred to as a biometric authentication device) comprises processing circuitry 1021 (e.g. one or more CPUs and / or GPUs or similar) for processing instructions, and a memory 1022 for storing the instructions to be processed. The memory 1022 may take any suitable form and may comprise a combination of non-volatile memory and volatile memory. The first processing device 102 comprises communication circuitry 1023 for communication with one or more other devices. The communication circuitry 1023 may be
[0177] H 16964 WOconfigured to communicate using, by way of example only and not as a limitation, one or more of a wired communication (e.g. USB, Ethernet) and / or wireless communication (e.g. Bluetooth®, WiFi®, LTE and so on), or any other communication protocol satisfying the relevant communication requirement. In a similar manner, the second processing device 103 may also comprise the elements discussed in relation to Figure 3. Hence, the second processing device 103 may also comprise processing circuitry, memory, and communication circuitry.
[0178] The techniques of the present disclosure use tokenisation to replace sensitive biometric data. The use of biometric data and tokenisation can provide an efficient and secure user authentication process. In particular the techniques of the present disclosure use tokenisation to replace sensitive face data for users. As part of an initial registration procedure, a user provides one or more biometric samples (e.g. images including face data) which are processed to generate a biometric template for the user. One or more algorithms may be used to extract key features from the biometric data, such as points on a face, for creating a unique biometric template for the user. A cryptographic function is then used to process the unique biometric template to generate a biometric token which can be stored for use when authenticating the user. The cryptographic function takes an input comprising a unique biometric template for a given user and generates an output comprising a biometric token. The cryptographic function may use, by way of example only and not as a limitation, one or more asymmetric encryption methods and / or one or more symmetric encryption methods such as but not limited to the Advanced Encryption standard "AES" (e.g. AES-256), or any other encryption method satisfying the cryptographic property required for the relevant embodiment. Various symmetric and asymmetric encryption techniques are known in the art and will therefore not be described in detail.
[0179] In the techniques of the present disclosure, a cryptographic function may use a non-reversible token algorithm so as to generate a token intended to be non-reversible (i.e. from which the original template data cannot feasibly be recovered). The biometric token can then be stored and referenced for user authentication processing. In this way, sensitive biometric data (e.g. face data) for a given user can be replaced with a stored token for that given user. Subsequently, when the same user attempts authentication, biometric data is captured for the user and evaluated against the stored token resulting in a match. In particular, the captured biometric data can be processed to obtain an encryption result (an encrypted biometric vector) which can be compared with a stored token. The user can be authenticated responsive to whether the encryption result matches the stored token.
[0180] Hence more generally, a method for registering a user may comprise: obtaining biometric face samples; generating a unique biometric template based on at least some of the biometric face samples; processing the unique biometric template using a cryptographic function to generate a biometric token for the user; and storing the biometric token to storage circuitry (e.g. memory
[0181] H 16964 WO1022). A plurality of users may each be registered according to the technique discussed above such that a different respective biometric token is generated and stored for each of the plurality of users. Hence, a token store may be obtained comprising a plurality of biometric tokens each corresponding to a different respective user. As part of the registration process, various sensitive information (e.g. bank card details, user IDs, bank account numbers and so on) can be linked with user profiles so that in response to matching the captured face data with a matching biometric token, a validation token can be generated for the user which comprises tokenised sensitive information which can be validated for permitting access for a resource (e.g. completing an action such as a transaction).
[0182] Figure 4 schematically illustrates a method 400 for user authentication based on face data. The method 400 comprises:
[0183] obtaining (at a step 410) face data for a user;
[0184] generating (at a step 420) a validation token in response to a successful match based on the face data and a stored biometric token;
[0185] performing (at a step 430) validation of the validation token; and
[0186] permitting (at a step 440) access for a resource conditional on the validation of the validation token.
[0187] Figure 4 represents a method in which a user is authenticated in response to a successful match using captured face data for the user and a stored biometric token for the user, and validation of the validation token is used for permitting access to a resource. In some examples, face-based authentication on its own may be sufficient for permitting access for a resource. Authentication using face data and biometric tokenisation provides a secure and streamlined (low friction) user authentication technique. For example, a user can be authenticated and access a resource with the user only being required to position their face (some or all of the face) within a field-of-view of an image capture device.
[0188] Figure 5 schematically illustrates a more detailed example for user authentication based on face data. The method 500 comprises:
[0189] obtaining (at a step 510) face data for a user;
[0190] processing (at a step 520) the face data using an encryption function to generate an encryption result comprising encrypted face data, and transmitting the encryption result via a first communications network;
[0191] receiving (at a step 530) the encryption result;
[0192] determining (at a step 540) whether there is a successful match for the encryption result and a stored biometric token;
[0193] H 16964 WOgenerating (at a step 550) a validation token in response to a successful match based on the face data and the stored biometric token, and transmitting the validation token via a second communications network;
[0194] receiving (at a step 560) the validation token;
[0195] performing (at a step 570) validation of the validation token, and transmitting a validation result; and
[0196] permitting (at a step 570) access for a resource conditional on successful validation of the validation token.
[0197] In Figure 5, the dashed boxes 101, 102 and 103 represent examples of the different processing devices that may be responsible for the different steps. Generally speaking, the terminal device may be responsible for obtaining face data and generating an encryption result using the face data, the first processing device 102 may be responsible for performing authentication of face data and generating a validation token, and the second processing device 103 may be responsible for performing validation of the validation token. In some examples, the functionality of the first processing device 102 and the second processing device 103 may be performed by a same processing device.
[0198] Still referring to Figure 5, the first processing device 102 is operable to receive the transmitted encryption result for a current user’s face data, at the step 530. The first processing device 102 is operable to access storage circuitry comprising one or more stored biometric tokens for one or more previously registered (e.g. on-boarded) users. The biometric authentication device 102 may comprise the memory 1022 for storing one or more biometric tokens. Alternatively or in addition, the biometric authentication device 102 may be operable to access a separate datastore (e.g. database storing one or more biometric tokens). Hence, the biometric authentication device 102 can be operable to receive the encryption result, determine (at the step 540) whether there is a successful match with a stored biometric token, and if so generate a validation token. A threshold condition such as a threshold match score (e.g. defined as a percentage or other similar value) may be used such that the biometric authentication device 102 determines a successful match with a stored biometric token when the degree of match exceeds the threshold condition. For example, a threshold condition may specify a threshold match score in the range 95% to 98% such that a match score that is greater than or equal to the threshold match score corresponds to a successful match.
[0199] Still referring to Figure 5, the second processing device 103 is operable to receive the validation token, at the step 560. Generally speaking, the validation token comprises a tokenisation of sensitive information which has previously been registered by a user. The validation token may comprise metadata to be used by the second processing device 103 (e.g. one or more backend servers) for validation. For example, the validation token may comprise information such as
[0200] H 16964 WOpayment (e.g. transaction authorisation, identity-validated request) details for a financial transaction and / or other suitable applications.
[0201] More generally, the second processing device 103 is operable to validate the validation token against stored information accessible to the second processing device 103. The second processing device 103 may be a backend server associated with an organisation such as bank, card issuer, or similar. The backend server may communicate with one or more other backend servers for performing validation of the validation token.
[0202] The second processing device 103 is thus operable to perform validation for the validation token. At the step 570, the second processing device 103 is operable to communicate a validation result to at least the terminal device 101 (e.g. as shown by the dashed arrow in Figure 1). The validation result indicates whether the validation token has been successfully validated. In response to receiving the validation result, the terminal device 101 may output (e.g. display) an indicator to indicate to the user that the use of the resource(s) has been permitted. At the step 580, the method comprises permitting access for a resource conditional on the validation result.
[0203] In some examples, the first processing device 102 may access a first token store storing biometric tokens for thereby determining whether the encryption result successfully matches a stored biometric token. The first processing device 102 may then access a second token store storing second tokens associated with the biometric tokens, in which the second token store stores tokens including information (e.g. payment (e.g. transaction authorisation, identity-validated request) information) to be used for validation for thereby permitting access for (e.g. use of) a resource. Alternatively, a same token store may store the biometric tokens and the second tokens. Hence, tokens including details (e.g. transaction details) for validation and biometric tokens may be stored in a same or separate information store. Alternatively, in some cases a stored biometric token may also compromise the information (e.g. payment (e.g. transaction authorisation, identity-validated request) information) to be used for validation. More generally, in response to a successful match for the face data and a stored biometric token, a validation token is generated which comprises information to be used for validation.
[0204] In some embodiments of the disclosure, the validation token may be generated with an associated lifetime (e.g. a time-to-live “TTL”). The associated lifetime defines a time that the validation token is valid for use. In some examples the information associated with the validation token may specify an issue time and an expiry time. Alternatively or in addition, the validation token may be generated with a limit on a number of uses. In some examples, the validation token may be a single-use token. Hence, the steps 420 / 550 in Figures 4 and 5 may comprise generating the validation token with an associated lifetime (e.g. in units of time) and / or associated limit on a number of uses. In
[0205] H 16964 WOsome examples, the validation token may be generated with a lifetime (e.g. time-to-live “TTL”) in the range 30 - 60 seconds. The validation token may be revocable.
[0206] A validation token may be used for various applications including but not limited to: banking, loyalty identification, ticketing, access control (e.g. digital access control, and / or physical access control for a building, event and so on), user identification for purposes such as civic voting, starting a vehicle and so on. In some examples, a validation token may be a payment (e.g. transaction authorisation, identity-validated request) token (i.e. a tokenisation of payment (e.g. transaction authorisation, identity-validated request) details) that is to be validated by one or more servers for permitting a transaction. A validation token may include details for a bank card, loyalty card, smart card, driving licence, or passport among others. In some embodiments of the disclosure a validation token may comprise a timestamp, session ID, and merchant ID.
[0207] In some embodiments of the disclosure, a validation token may comprise a match score indicative of a degree of match between the biometric token and the face data. As explained above, a threshold condition may be used so that when the face data and the biometric token are matched above the threshold condition, a validation token (e.g. short-lived validation token) is generated. A validation token may comprise a match score that was obtained for the comparison of the face data and the biometric token. The match score may be considered as part of the processing for validation of the validation token. For example, for certain applications (e.g. highly sensitive applications) a higher threshold condition for the match score may be used for the validation stage. Alternatively or in addition, in some embodiments of the disclosure a validation token may comprise a liveness score. As explained below, a liveness algorithm may be used, and a liveness score may be associated with the validation token. A validation token generally comprises information (e.g. a payload) to be used for validation without including biometric data for the user. For example, a token payload in the case of a transaction may comprise the following fields: userjd; match score; sessionjd; merchantjd; iat (issued at time); and exp (expiration time). In some embodiments of the disclosure, a validation token may use, by way of example only and not as a limitation, the JSON Web Token (JWT) format, or any other token format satisfying the relevant payload and validation requirements. Hence, a validation token may comprise or consist of a JWT or any other equivalent token format. In some embodiments of the disclosure, a validation token may be compatible with various APIs, including but not limited to Stripe, Adyen, Apple Wallet, or any other API capable of processing the validation token. A validation token may thus trigger a payment (e.g. transaction authorisation, identity-validated request) intent without disclosing identity or biometric source. A validation token may be used to access (e.g. unlock), by way of example only and not as a limitation, Apple Wallet passes, loyalty IDs, tickets, ID documents, or any other digital asset or credential capable of being unlocked or accessed via the validation token.
[0208] H 16964 WOAt the steps 430 and 570, performance of validation for the validation token may result in a pass or failed validation. A validation token may be unsuccessfully validated due to one or more of: unsuccessful payload validation; exceeding a number of uses for the validation token; exceeding an expiry time for the token; a match score below a threshold match score used for validation; a liveness score (and / or classification) below a threshold liveness score (and / or classification) used for validation. For example, a validation token may have expired and / or already been used thereby resulting in failed validation.
[0209] The above techniques refer to user-authentication which may be performed using just face data from the user. In some embodiments of the disclosure, supplementary authentication processing techniques may be used to enhance security and / or improve usability.
[0210] In some embodiments of the disclosure, the validation operation performed on an authentication input may be performed by any process operable to produce a validation outcome from the authentication input. Such processes include, by way of example only and not as a limitation: comparison of the authentication input against a corresponding stored reference; generation of a non-reversible representation of the authentication input for comparison with a corresponding non-reversible reference, including by tokenisation as described elsewhere in this disclosure; evaluation of the authentication input against one or more behavioural properties, environmental properties, or contextual properties as described in relation to the duress detection level; computation of one or more confidence metrics for the authentication input by one or more processes operating on the authentication input; evaluation of the authentication input by one or more distributed processes operating across a plurality of processing resources; or any other process operable to produce a validation outcome that may be evaluated by the configurable security information. The configurable security information, supplementary authentication processing, hierarchical authentication processing levels, decision-tree pathway selection, and dual-mode (online and offline) operation described elsewhere in this disclosure operate identically regardless of the process used to produce the validation outcome. The validation outcome may comprise, by way of example only and not as a limitation, a discrete pass or fail result, a continuous confidence metric, a multi-valued classification, or any other outcome capable of being evaluated by the configurable security information.
[0211] Figure 6a schematically illustrates a method 600 in accordance with embodiments of the disclosure. The method 600 comprises:
[0212] obtaining (at a step 610) face data for a user;
[0213] generating (at a step 620) a validation token in response to a successful match based on the face data and a stored biometric token;
[0214] performing (at a step 630) validation of the validation token;
[0215] H 16964 WOdetermining (at a step 640) whether to perform supplementary authentication processing in dependence on configurable security information, and if so performing the supplementary authentication processing; and
[0216] permitting (at a step 650) access for a resource conditional on successful validation by the supplementary authentication processing. In response to unsuccessful validation by the supplementary authentication processing, the method 600 ends without permitting use of the resource, or the method 600 may return to the step 610 so as to repeat the method by asking the user to reattempt authentication.
[0217] The method 600 may comprise performing supplementary authentication processing for cases in which at least one of the step 620 and the step 630 results in failed validation. In particular, the configurable security information may comprise one or more conditions which are triggered in response to failure for at least one of the face-data authentication and validation-token validation. Accordingly, in some cases, even though the validation token is not successfully validated, the supplementary authentication processing may be performed and use of the resource may still be permitted conditional on the result of the supplementary authentication processing.
[0218] The method 600 may comprise performing supplementary authentication processing for cases in which the steps 620 and 630 result in successful validation for the validation token. Even though the validation token is successfully validated, the method 600 may comprise performing supplementary authentication processing. This can contribute to improving security. The configurable security information may comprise one or more conditions which are triggered in response to one or more scenarios. Hence, the supplementary authentication processing may be selectively triggered responsive to one or more scenarios (e.g. user properties, real-world environment properties, resource properties (e.g. a type for the resource(s) to be accessed, a quantity for a transaction), and / or current conditions such as time of day). This is discussed in more detail later.
[0219] The method 600 may be performed by a processing system such as the processing system described in relation to Figure 1. Figure 6b is a schematic flowchart illustrating steps performed between step 640 and step 650. Referring to Figure 6b, the method further comprises:
[0220] determining (at the step 640) whether to perform supplementary authentication processing in dependence on configurable security information, the configurable security information comprising one or more conditions for triggering the supplementary authentication processing; in response to determining that supplementary authentication processing is to be performed (shown as Y at the step 641), the method further comprises:
[0221] obtaining (at a step 642) at least one user identifier associated with the user; performing (at a step 643) validation of the at least one user identifier; and
[0222] H 16964 WOpermitting (at the step 650) access for a resource conditional on successful validation of the at least one user identifier.
[0223] As shown in Figure 6b, in response to determining that supplementary authentication processing is not to be performed (shown as N at the step 641), the method may proceed directly to the step 650 to permit access for the resource. Figure 6b represents a specific example in which the configurable security information comprises one or more conditions which are triggered in response to failure for at least one of the step 620 and the step 630. Accordingly, when at least one of facedata authentication and validation-token validation fails (i.e. at the steps 620 / 630), one or more of the conditions will be triggered for causing supplementary authentication processing. Conversely, when face-data authentication and validation-token validation are successful (and no other conditions are tiggered, if present), the method can proceed to step 650 to permit access for the resource. Optionally, the one or more conditions used at the step 641 may also comprise one or more scenario-based conditions, and therefore even though the validation token may be successfully validated, the method 600 may comprise performing supplementary authentication processing.
[0224] Figure 6c schematically illustrates an example in which the configurable security information comprises one or more scenario-based conditions and does not comprise one or more conditions which are triggered in response to failure at the step 620 and / or the step 630. As shown in Figure 6c, in response to one or more scenario-based conditions being triggered, the method determines that supplementary authentication processing is to be performed (shown as Y at the step 641), and the method proceeds to obtain one or more user identifiers (other than face data) and perform validation(s) thereof. Accordingly, the data flow in this case may proceed according to the steps 641 , 642, 643. In response to determining that supplementary authentication processing is not to be performed (shown as N at the step 641), and the validation token was not successfully validated at the step 630 (shown as N at the step 644), the method proceeds to the step 645 and ends without performing supplementary authentication processing and without permitting use of the resource. Alternatively, the method may automatically return to the step 610 and the method may repeat Moreover, the method may proceed by requesting the user to reattempt authentication beginning with capturing the user’s face and the method steps may be repeated. In response to determining that supplementary authentication processing is not to be performed (shown as N at the step 641), and the validation token was successfully validated at the step 630 (shown as Y at the step 644), the method can proceed to step 650 to permit access for the resource. Hence, Figure 6c represent an example in which the one or more conditions used for determining whether to perform supplementary authentication processing comprise one or more scenario-based conditions, and in response to none of the one or more scenario-based conditions being triggered, the step 644 may be used to check the validation results for the steps 620 and 630 to select whether to proceed with permitting use or denying use of the resource.
[0225] H 16964 WOMore generally, Figures 6a, 6b and 6c illustrate methods in which user authentication is performed based on matching a stored biometric token and captured face data, a validation process is performed for a generated validation token, and configurable security information is referenced to determine whether to perform supplementary authentication processing prior to permitting access for a resource. Processing for determining whether to perform supplementary authentication processing may start at any time prior to the step of permitting access for the resource. In some examples, processing for determining whether to perform supplementary authentication processing may start prior to any of the steps 610-630. Hence, it may be determined that supplementary authentication processing is to be performed prior to the step of performing validation of the validation token and potentially prior to validating face data with a biometric token. In some cases, determining whether to perform supplementary authentication processing may comprise detecting whether one or more scenario related conditions are present which may feasibly be detected prior to the steps 610-630 and / or during the processing operations for the steps 610-630. Hence in some examples operations for supplementary authentication processing may be performed in parallel with other operations.
[0226] Referring to Figure 1 , configurable security information may be accessed by one or more of the devices 101, 102 and / or 103 for determining whether to perform supplementary authentication processing. In response to determining that supplementary authentication processing is to be performed, supplementary authentication processing may be performed by one or more of the devices 101, 102 and / or 103. For example, the terminal device may access (e.g. store) configurable security information and may determine that supplementary authentication processing is to be performed, and supplementary authentication processing may be performed by the terminal device 101 and / or the first processing device 102 and / or the second processing device 103. Alternatively or in addition, the first processing device 102 may access (e.g. store) configurable security information and may determine that supplementary authentication processing is to be performed, and supplementary authentication processing may be performed by the first processing device 102 and / or the terminal device 101 and / or the second processing device 103.
[0227] Some embodiments of the disclosure allow for online biometric authentication. In some embodiments of the disclosure a processing system is configured to operate in an online mode to perform offline biometric authentication. As explained above, the system in Figure 1 may be used for performing any of the methods described above. The terminal device 101 may be a point-of-sale (POS) terminal device (e.g. located in a retail environment). The devices 102 and 103 may be one or more servers. The terminal device 101 may comprise first processing circuitry to:
[0228] obtain face data for a user;
[0229] generate an encryption result in dependence on the face data; and
[0230] H 16964 WOcommunicate the encryption result to the one or more servers, wherein the one or more servers may comprise second processing circuitry to:
[0231] generate a validation token in response to a successful match based on the face data and a stored biometric token; and
[0232] perform validation of the validation token;
[0233] wherein at least one of the first processing circuitry and the second processing circuitry may be configured to:
[0234] determine whether to perform supplementary authentication processing in dependence on configurable security information;
[0235] wherein in response to determining that supplementary authentication processing is to be performed, at least one of the first processing circuitry and the second processing circuitry may be configured to:
[0236] obtain at least one user identifier associated with the user;
[0237] perform validation of the at least one user identifier; and
[0238] permit use of a resource conditional on successful validation of the at least one user identifier.
[0239] This represents an example of an online mode for user authentication. The techniques of the present disclosure can be performed using a combination of processing devices (e.g. 101, 102, 103) and references to processing circuitry may refer to distributed arrangements where processing is performed across a plurality of respective devices operable to communicate via one or more communications networks. For an offline mode (discussed later) the techniques may be performed locally using one or more local devices. In some cases, offline functionality may be performed solely by a terminal device.
[0240] In the techniques of the present disclosure, in response to determining that supplementary authentication processing is to be performed, at least one user identifier (other than face data) is to be obtained and successfully validated in order to permit access for the resource. In some embodiments of the disclosure, the at least one user identifier may be obtained without any interaction by the user. In particular, in some embodiments of the disclosure the terminal device may perform scanning (using short-range wireless communication technology) to detect a device identification parameter (e.g. a device ID previously registered by the user) communicated by a registered user device associated with the user. In this way, both face data and a wirelessly communicated device identification parameter (e.g. a BLE signal) may be used for authentication of the user. Authentication using face data and a device identification parameter can provide secure and streamlined (low friction) user authentication technique. In particular, form the user’s perspective, the user may position their face within a camera FOV and both face data and a passively obtained (i.e. without physical interaction by the user) device identification parameter may be used for authentication.
[0241] H 16964 WOThe above discussion refers to an example using a device identification parameter as at least one user identifier for the supplementary authentication processing. The user identifier may be any suitable unique user identifier. In some embodiments of the disclosure, the supplementary authentication processing may comprise obtaining one or more user identifiers for the user, which may comprise at least one of: a voice input, gesture input, fingerprint, iris scan, manually entered user identification number (e.g. a personal identification number “PIN”), and a device ID communicated by a registered user device (e.g. a BLE handshake). More generally, in the techniques to be discussed below face data may be used as a primary user identifier, and supplementary authentication processing may be performed which includes performing validation of one or more secondary user identifiers. For example, the combination of face data and a device identifier can allow a seamless user experience. The combination face data and a voice input (e.g. matching voice to a reference) can also provide a relatively fast and easy user experience.
[0242] The configurable security information comprises one or more conditions for triggering the supplementary authentication processing. The conditions may be defined in advance by a programmer. The conditions may or may not be capable of being modified by a user (e.g. as part of an onboarding / enrolling process). Hence, in some cases the configurable security information may comprise one or more programmed conditions (also referred to as predetermined conditions) and / or one or more user-defined conditions. For example, a user may provide inputs (e.g. when setting up a user profile or user account) to modify an already existing condition and / or create a new condition. The configurable security information thus defines one or more conditions, and in response to at least one of the one or more conditions being triggered, supplementary authentication processing is automatically performed.
[0243] In some embodiments of the disclosure, the configurable security information may comprise first configurable security information comprising one or more scenario-related conditions. The first configurable security information may comprise one or more conditions which are tiggered in response to one or more scenarios. Alternatively or in addition, the configurable security information may comprise second configurable security information comprising one or more validation-outcome related conditions for at least one of face data validation and validation-token validation. The second configurable security information may comprise one or more conditions which are tiggered in response to outcomes for the face data validation (i.e. outcomes for one or both of the steps 620 and 630). Hence, in some embodiments of the disclosure one or more conditions can be scenario-based and / or one or more conditions can be validation-outcome based.
[0244] A scenario-related condition refers to a condition which can be triggered irrespective of the outcomes of the steps 620 / 630 (and therefore potentially before completion of those steps).
[0245] Moreover, whether a scenario-related condition is triggered may be dependent on one or more
[0246] H 16964 WOproperties associated with the current user, one or more real-world environment properties, and / or one or more properties associated with the resource to be used (e.g. a type of data to be accessed). This is contrast to a validation-outcome related condition which is responsive to the outcomes of the step 620 and / or the step 630.
[0247] In some embodiments of the disclosure, the first configurable security information may comprise one or more scenario-related conditions specifying one or more predetermined scenarios for which supplementary authentication processing is to be performed. One or more of the scenario-related conditions may be triggered in response to: one or more user-related properties being present for the current user; one or more real-world environment properties being present for the user’s surrounding real-world environment; and / or one or more resource-related properties being present for the resource for which access is being attempted. In some cases, a respective condition may define a combination of a user-related property and a resource-related property, such that the respective condition may only be triggered responsive to both the user-related property and the resource-related property being simultaneously present.
[0248] In some embodiments of the disclosure, one or more of the scenario-related conditions may specify at least one of: a current time of day; a current geographical area and / or location associated with the user and / or the terminal device; a type of commercial sector associated with the resource, a type of information to be accessed; a type associated with the resource; and an amount associated with a financial transaction. For example, a scenario-related condition may specify a current time of day by specifying a time range such as 10pm to 4am. Therefore, when a user attempts to use the resource at a time of day within this time range, supplementary authentication processing can be triggered. A scenario related condition may specify a current geographical area and / or location by specifying a name of a street, neighbourhood, district, suburb, town, city, state, province and / or country. Alternatively or in addition, a current geographical area and / or location may be specified using a postcode (ZIP code) and / or GPS coordinates. Therefore, when a user attempts to use the resource when currently located within the specified geographical area and / or location (or within a predetermined distance e.g. X miles, of the specified geographical area and / or location), supplementary authentication processing can be triggered. Alternatively or in addition, a type of commercial sector associated with the resource may be specified. For example, one or more of banking, government, or vehicle access (as suitable examples among others) may be specified. Alternatively or in addition, a type of information to be accessed may be specified and / or a type associated with the resource to be used may be specified. For example, banking information, government information, vehicle information, sporting event information and so on may be specified. Alternatively or in addition, in the case of financial transactions, an amount may be specified (e.g. in units of currency) such that, when a current transaction involves an amount that is at least equal to the specified amount, supplementary authentication processing can be triggered.
[0249] H 16964 WOIn some embodiments of the disclosure, one or more of the validation-outcome related conditions may specify at least one of: whether obtained face data results in a successful match for a stored biometric token; and whether a validation token results in successful validation. Specifically, the one or more validation-outcome related conditions may be triggered in response to a failure for one or more of the face-data authentication and the validation-token validation.
[0250] In some embodiments of the disclosure, the configurable security information may comprise a plurality of supplementary authentication processing routines. The processing system may be configured to select a respective one of the plurality of supplementary authentication processing routines in dependence on one or more triggered conditions. The plurality of supplementary authentication processing routines may each use at least one different type of user-identifier. For example, a first supplementary authentication processing routine may require successful validation of a first type of user-identifier (e.g. a manually entered identification code, such as a PIN), and a second supplementary authentication processing routine may require successful validation of a second type of user-identifier (e.g. a voice input or a fingerprint) different from the first useridentifier.
[0251] In some embodiments of the disclosure, the configurable security information may comprise associations between one or more of the one or more conditions and one or more of the plurality of supplementary authentication processing routines. The configurable security information may comprise a mapping between conditions and supplementary authentication processing routines. The table below shows an example in which condition 1 is mapped to supplementary authentication processing routine A, condition 2 is mapped to supplementary authentication processing routine B, condition 3 is mapped to supplementary authentication processing routine C, and condition 4 is mapped to supplementary authentication processing routine D. The conditions 1-4 may each be different and the supplementary authentication processing routines A-D may each be different.
[0252] Condition Routine
[0253] 1 A
[0254] 2 B
[0255] 3 C
[0256] 4 D
[0257]
[0258] For example, condition 1 may specify a banking scenario, and routine A may require successful validation of a first type of user-identifier (e.g. a device identification parameter, as discussed previously). Condition 2 may specify a time period (e.g. a day of the week and / or a time of day), and routine B may require successful validation of a second type of user-identifier. In a case where both condition 1 and condition 2 may be simultaneously triggered, the processing circuitry may
[0259] H 16964 WOselect (e.g. randomly) one routine to be used from the routines A and B. Alternatively, conditions may be ordered such that a higher-ordered condition takes priority over a lower-ordered condition and the routine associated with the higher-ordered condition is selected as the selected supplementary authentication processing routine. The table represents one example of associations between conditions and routines.
[0260] In some embodiments of the disclosure, the configurable security information may comprise a decision tree for selecting one or more user identifiers to be obtained for the user, and optionally an order for obtaining and validating the one or more user identifiers. In the case of configurable security information comprising a plurality of respective conditions, all of the conditions, or a subset of the conditions, or none of the conditions may be triggered for a given authentication attempt by a user, and this information can be input to a decision tree comprising a root node as a starting point. The root node is connected to internal nodes and branches representing different possible outcomes corresponding to different user-identifiers to be validated. Hence more generally, information indicating which of the conditions are triggered (and potentially also indicating which of the conditions have not been triggered) can be input to a decision tree for determining one or more properties for the supplementary authentication processing (i.e. which user identifiers to request and optionally an order for obtaining and validating the one or more user identifiers).
[0261] In some embodiments of the disclosure, the configurable security information may comprise at least one condition defined in advance by the user. A user may create a condition such as at a time when registering with a service so that security can potentially be enhanced when one or more conditions are present and / or one or more preferred types of user-identifier can be specified by the user for supplementary authentication processing. In some cases, at least one condition defined in advance by a user may be automatically associated with a default supplementary authentication processing routine. Optionally, the configurable security information may further comprise at least one supplementary authentication processing routine defined in advance by the user. A user may create a supplementary authentication processing routine by specifying a type of user-identifier and optionally an order for requesting different types of user-identifier.
[0262] Multi-level examples
[0263] In some embodiments of the disclosure, the configurable security information may comprise a plurality of respective authentication processing levels. Each respective authentication processing level may comprise one or more conditions. The configurable security information may define the plurality of respective authentication processing levels to have a hierarchical ordering so that the plurality of respective authentication processing levels are evaluated in hierarchical order. More generally, the configurable security information may define a multi-levelled supplementary authentication structure.
[0264] H 16964 WOFigure 7 is a schematic flowchart illustrating evaluating respective authentication processing levels in hierarchical order. Figure 7 illustrates an example using three respective authentication processing levels. It will be appreciated that the principles described in relation to Figure 7 may be performed for an arrangement using N respective authentication processing levels, where N may be any value greater than 2, or a value in the range 2-10, or in the range 2-5. In some examples, the configurable security information may define four respective authentication processing levels. Hence, face data can be used as a primary authenticator and the configurable security information may define N respective authentication processing levels which are evaluated in order.
[0265] Figure 7 is a schematic flowchart illustrating steps that may be performed between the step 640 and the step 650. Referring to Figure 7, the method further comprises:
[0266] determining (at the step 641-1) whether one or more conditions for a first authentication processing level are triggered, and if so performing (at the step 701-1) first supplementary authentication processing, and permitting (at the step 650) access for a resource conditional on successful validation by the step 701-1 ;
[0267] determining (at the step 641-2) whether one or more conditions for a second authentication processing level are triggered, and if so performing (at the step 701-2) second supplementary authentication processing, and permitting (at the step 650) access for the resource conditional on successful validation by the step 701-2; and
[0268] determining (at the step 641-3) whether one or more conditions for a third authentication processing level are triggered, and if so performing (at the step 701-3) third supplementary authentication processing, and permitting (at the step 650) access for the resource conditional on successful validation by the step 701-3.
[0269] In Figure 7, the three levels are evaluated in hierarchical order. The levels have one or more different conditions and the levels each have a different supplementary authentication processing routine. For example, the first supplementary authentication processing at the step 701-1 , the second supplementary authentication at the step 701-2 and the third supplementary authentication processing at the step 701-3 may each require successful validation of at least one different type of user identifier. The configurable security information can be modified (e.g. by a programmer) to modify the respective levels, and in particular the conditions and the supplementary authentication processing routines used for the different levels. For example, updates may be issued to the devices 101, 102 and 103 for modifying one or more of the respective levels. Over-the-air updates may be issued to the terminal device 101 for updating configurable security information.
[0270] In some embodiments of the disclosure, the first authentication processing level (i.e. level 1) may use first supplementary authentication processing that requires successful validation of a device identification parameter wirelessly communicated by a registered user device. The second
[0271] H 16964 WOauthentication processing level (i.e. level 2) may use second supplementary authentication processing that requires successful validation of one or more user identifiers comprising one or more of voice input, a passcode, gesture input, and iris scan. The third authentication processing level (i.e. level 3) may use third supplementary authentication processing that requires successful validation of one or more user identifiers comprising one or more of voice input, a passcode, gesture input, and iris scan. Level 2 and level 3 may in some cases require a same type of user identifier to be validated, but may use different conditions. In some cases, a user-identifier associated with lower friction (i.e. less interaction by the user) may be used for level 2 and another user-identifier associated with higher friction (i.e. more interaction by the user) may be used for level 3. For example, one or more of a voice input and a gesture input may be used for level 2, and one or more of a fingerprint scan and a manually entered passcode may be used for level 3. In some embodiments of the disclosure, one or more scenario related conditions may be used for the second authentication processing level (i.e. level 2 in Figure 7), and one or more failure-based conditions may be used for the third authentication processing level (i.e. level 3 in Figure 7).
[0272] More generally, Figure 7 represents an example in which a plurality of respective authentication processing levels are evaluated in hierarchical order to determine a highest-ordered respective authentication processing level comprising one or more triggered conditions. Supplementary authentication processing is then performed in dependence on the highest ordered respective authentication processing level comprising the one or more triggered conditions.
[0273] In some embodiments of the disclosure, the configurable security information may define four respective authentication processing levels. A first level may perform supplementary authentication based on a device identification parameter from a registered user device associated with a user. A second level may perform supplementary authentication based on one or more user identifiers other than face data (e.g. passcode, fingerprint, gesture, voice, iris). A third level may be a duress detection level that can detect duress for a user (e.g. based on user properties and / or environmental properties) and automatically prohibit access for some resource types (e.g. banking), and optionally may also perform supplementary authentication processing based on one or more user identifiers other than face data (e.g. passcode, fingerprint, gesture, voice, iris). A fourth level may perform supplementary authentication based on one or more user identifiers other than face data (e.g. passcode, fingerprint, gesture, voice, iris). The respective levels may each use one or more different conditions so that the levels are triggered in response to different events (e.g. scenarios and / or outcomes of validation for the face data and the validation token). For example, the second level may correspond to the first configurable security information comprising one or more scenario-related conditions, and the fourth level may correspond to the second configurable security information comprising one or more validation-outcome related conditions.
[0274] H 16964 WOA first level of the authentication processing levels may comprise one or more conditions and an associated first supplementary authentication processing routine. The first supplementary authentication processing routine may require a parameter obtained from a registered user device to be successfully validated. The one or more conditions may specify a scenario such as one or more of banking and aviation access, for example. Hence, the first supplementary authentication processing routine may require presence of a registered user-device which transmits a device identification parameter for being validated for access for these scenarios. The registered userdevice may be a mobile device such as a smartphone or smartwatch, and the device identification parameter may be transmitted using a short-range wireless communication. The registered userdevice may transmit the device identification parameter using a personal area network (PAN) wirelessly connecting the registered user device and the terminal device 101. By way of example only and not as a limitation, one or more of Bluetooth®, Near Field Communication (NFC) and Ultra-wideband (UWB) communication may be used, or any other wireless communication protocol satisfying the relevant communication requirement.
[0275] A second level of the authentication processing levels may comprise one or more conditions and an associated second supplementary authentication processing routine. The second supplementary authentication processing routine may require successful validation of at least one of a passcode (e.g. PIN number), voice, gesture, iris scan. A passcode may be entered by the user using a keypad (e.g. physical or touchscreen). A voice may be detected using one or more audio sensors (e.g. microphones) to detect the user’s voice. A gesture may be detected using the image sensor 1014. The user may perform a gesture using one or more of: a hand, a finger, an arm, a head. The one or more conditions may specify a scenario such as one or more types of sector (such as government access, vehicle access and so on), a geographic location, a time period (e.g. a time of day, such as a range of time defined based on a 24-hour clock), a type of data associated with an accessed resource (e.g. whether the data is classified), and / or a session type (e.g. whether the session has a high value transaction).
[0276] A third level of the authentication processing levels may comprise one or more conditions and optionally an associated third supplementary authentication processing routine. The one or more conditions may specify one or more user properties and / or real-world environment properties indicative of duress. For example, one or more image sensors and / or audio sensors at the terminal device may monitor the user for detecting such properties. The one or more conditions may specify one or more user properties such as a voice tone, one or more spoken words and / or phrases, one or more physical gestures, and / or presence (or proximity) of one or more other nearby people. One or more image sensors and / or one or more audio sensors may be used to capture images of the user and / or detect audio (e.g. speech, background noise). These inputs can be compared with the one or more conditions. In some examples theses inputs may be analysed to assess the status and / or a behavioural context for the user. By way of example only and not as a limitation, Al-based
[0277] H 16964 WOclassification techniques may be used to provide a duress classification and / or a behavioural classification for the user, or any other classification technique capable of providing the relevant classification. Accordingly, the third level may use any of the inputs discussed above for flagging duress and / or behavioural aspects, and when triggered the processing system may enter a limited access mode for limiting access to only one or more types of resource. For example access for one or more types of resource (such as banking) may not be permitted for the limited access mode.
[0278] The duress detection level (i.e. duress classification or behavioural classification) operates as a native authentication processing level within the configurable security information framework, evaluated within the same hierarchical ordering as the other levels and triggered by configurable conditions specifying any signal accessible to the processing system indicative of duress. By way of example only and not as a limitation, such signals may include user properties, environmental properties, behavioural properties, or contextual properties. The duress detection level is not a separate or standalone security mechanism; it is architecturally identical to the other authentication processing levels and uses the same condition-evaluation, routine-selection, and access-gating logic described elsewhere in this disclosure.
[0279] A fourth level of the authentication processing levels may comprise one or more conditions and an associated fourth supplementary authentication processing routine. The fourth supplementary authentication processing routine may require successful validation of at least one of a passcode (e.g. PIN number), voice, gesture, iris. The one or more conditions may comprise one or more validation-outcome related conditions for at least one of face data validation and validation-token validation. Moreover, the one or more conditions may comprise one or more failure-based and / or contextual override conditions. Generally speaking, the fourth level may use one or more of the conditions that are reactive to events during the attempted authentication (such as facial authentication failure, validation token failure).
[0280] In some embodiments of the disclosure, a liveness detection algorithm may be used. An image captured by the image sensor 1014 may be processed by the terminal device 101 using a liveness detection algorithm to detect whether the captured image corresponds to a real user. This can guard against attempts by unauthorised users to gain access by using illicit techniques (e.g. photos or displayed images). The liveness detection algorithm may use features such as blinks, face movement eye movement, depth checks, skin tone, and shadows for liveness detection.
[0281] Registered user device examples
[0282] In some embodiments of the disclosure, a registered user device associated with a user may be configured to wirelessly communicate a device identification parameter. The processing system may be configured to detect the at least one device identification parameter wirelessly
[0283] H 16964 WOcommunicated by the registered user device and perform validation of the least one device identification parameter wirelessly communicated by the registered user device. The registered user device may wireless communicate the device identification parameter using a short-range wireless communication including but not limited to Bluetooth® (e.g. Bluetooth Low Energy "BLE"), NFC and / or RFID, or any other short-range wireless communication protocol satisfying the relevant communication requirement. In some embodiments of the disclosure, a short-range wireless communication with a range greater than 1 metre (e.g. in the range 1 to 10 metres) may be used such that the user may only need to position themselves proximate to the terminal device 101 for allowing the terminal device 101 to automatically detect the device identification parameter. The terminal device 101 may performing scanning (e.g. a passive BLE scan) to detect a BLE packet comprising the device identification parameter. Accordingly, when the user approaches the terminal device 101 , the terminal device 101 is able to automatically detect the device identification parameter, without needing physical interaction from the user. For example, smartphone device in a user’s pocket (or smartwatch device) may passively transmit the device identification parameter to the terminal device 101. This can contribute to allowing a seamless interaction for the user.
[0284] In addition to face data, the processing system may be triggered by detection of one or more of, by way of example only and not as a limitation: a device identification parameter wirelessly communicated by a registered user device, a geolocation parameter indicating the user is within a defined geographical area, presence or motion of the user detected by one or more sensors, an ambient sensor input, a time-based trigger, a user input provided to the terminal device, or any other trigger from which a session may be initiated. The trigger initiates the authentication chain, which proceeds with validation of the obtained authentication input and, where required, supplementary authentication processing in dependence on the configurable security information.
[0285] In some embodiments of the disclosure, the processing system may be configured to activate the image sensor 1014 to capture the face data for the user in response to successful validation of the at least one device identification parameter wirelessly communicated by the user device.
[0286] Therefore, the terminal device 101 may automatically activate the image sensor 1014 to capture one or more images comprising the user in response to the user moving within range of the terminal device 101. Hence, referring to Figures 4, 5, 6a, 6b and 6c, the methods therein may start with detecting a device identification parameter for a registered user device and activating the image sensor in response thereto so as to capture face data for a user having the registered user device. In other examples, presence and / or motion of the user, and / or a user input provided to the terminal device 101, and / or time-based triggers / ambient sensor logic may be used to activate the image sensor 1014. However, in some cases detection of the device identification parameter may be used to passively (i.e. without interaction by the user) activate the image sensor thereby achieving a seamless interaction for the user and providing authentication with enhanced security.
[0287] H 16964 WOIn some embodiments of the disclosure the processing system may be configured to: obtain the at least one device identification parameter wirelessly communicated by the user device for use as at least one user identifier for the supplementary authentication processing; and perform validation of the at least one device identification parameter. The device identification parameter may be used for the supplementary authentication processing so that “just look” user authentication can be combined with supplementary authentication processing using a passively detected device identification parameter. The device identification parameter may be a registered device ID which can be validated e.g. by the first processing device 102. For example, the first processing device 102 may access storage circuitry (e.g. memory 1022) storing one or more registered device IDs and may perform device ID matching. In some embodiments of the disclosure, tokenisation may be used to replace a device ID with a token (also referred to as a device token). The device token may be a one-time device token. References to a device identification parameter may refer to a device token wirelessly communicated by the user device.
[0288] Accordingly a method for authentication using a device identification parameter may comprise: obtaining a device identification parameter (e.g. device token) from a registered user device associated with a user;
[0289] obtaining face data for the user;
[0290] in response to a first successful match based on the face data and a stored biometric token and a second successful match based on the device identification parameter and a stored device identification parameter (e.g. stored device token), generating a validation token;
[0291] performing validation of the validation token; and
[0292] permitting access for a resource conditional on the validation of the validation token.
[0293] This represents an example using both face data and a device identification parameter from a registered user device for permitting access for a resource. The terminal device 101 may receive both face data and a device token and if both the face scan data and the device token successfully match with a stored biometric token and a stored device token, respectively, then the validation token can be generated. Therefore, in some examples, face based authentication and registered-device based authentication may be sufficient for permitting use of a resource. In some examples, registered-device based authentication may be mandatory. In other examples, registered-device based authentication may be performed as part of the supplementary authentication processing. This is discussed below. In some examples, the face data matching and device token matching may be performed at the first processing device 102. Moreover, the terminal device 101 may communicate the device token and the encryption result for the face data to the first processing device 102 for validation processing thereat. In other examples, the validation processing for the device token and the encryption result for the face data may be performed locally at the terminal device (e.g. in the case of an offline mode).
[0294] H 16964 WOAnother method for authentication using a device identification parameter may comprise: obtaining a device identification parameter (e.g. device token) from a registered user device associated with a user;
[0295] activating an image sensor in response to a successful match based on the device identification parameter and a stored device identification parameter;
[0296] capturing face data for the user using the image sensor;
[0297] generating a validation token in response to a successful match based on the face data and a stored biometric token;
[0298] performing validation of the validation token; and
[0299] permitting access for a resource conditional on the validation of the validation token.
[0300] Therefore, in some examples, registered-device based authentication may be used to activate the image sensor, and face based authentication using face data captured using the image sensor may be used to generate the validation token.
[0301] Another method for authentication using a device identification parameter may comprise:
[0302] obtaining face data for a user;
[0303] generating a validation token in response to a successful match based on the face data and a stored biometric token;
[0304] performing validation of the validation token;
[0305] determining whether to perform supplementary authentication processing in dependence on configurable security information, and if so performing the supplementary authentication processing, the supplementary authentication processing comprising:
[0306] obtaining a device identification parameter (e.g. device token) from a registered user device associated with a user for use as at least one user identifier associated with the user; and
[0307] performing validation of the at least one user identifier; and
[0308] permitting access for a resource conditional on successful validation by the supplementary authentication processing.
[0309] In the above example, the device identification parameter may be obtained in response to determining that supplementary authentication processing is to be performed. The device identification parameter (e.g. device token) may serve to acts as a user identifier since the device token is tied to the registered user device associated with the user. For example, the first-ordered authentication processing level in Figure 7 (i.e. level 1) may require device token validation for the supplementary authentication processing.
[0310] Hence more generally, in some embodiments of the disclosure the configurable security information may comprise a first-ordered level of the plurality of respective authentication
[0311] H 16964 WOprocessing levels, the first-ordered level comprising one or more conditions which when triggered require at least one device identification parameter wirelessly communicated by the user device to be validated.
[0312] It will be appreciated that any of the above-mentioned methods for authentication using the device identification parameter may be suitably combined.
[0313] Offline mode examples
[0314] Some embodiments of the disclosure may allow offline biometric authentication without accessing one or more servers (e.g. without internet connectivity). In some embodiments of the disclosure a processing system is configured to operate in an offline mode to perform offline biometric authentication.
[0315] Figure 8 schematically illustrates example processing system for offline biometric authentication. The processing system comprises the terminal device 101 comprising an image sensor to capture the face data for the user, and a user device 100a associated with a user. In some examples, the user device 100a may be a registered user device (as already discussed above) and may also be operable to communicate a device identification parameter for use according to the techniques discussed above. The user device may be any suitable mobile device such as a smartphone or smartwatch, for example.
[0316] In some embodiments of the disclosure, the user device may comprise secure token storage circuitry 800 to store one or more preloaded biometric tokens. The secure token storage circuitry 800 may be partitioned so that a first secure token storage 810 stores one or more preloaded biometric tokens and a second secure token storage 820 stores one or more pre-authorised payment (e.g. transaction authorisation, identity-validated request) tokens. In some cases, the secure token storage circuitry 800 may not store pre-authorised payment (e.g. transaction authorisation, identity-validated request) tokens, and this may optionally be included for use with payment (e.g. transaction authorisation, identity-validated request)-based use cases.
[0317] The user device 100a comprises communication circuitry configured to communicate a preloaded biometric token to the terminal device for temporary storage at the terminal device 101. The user device 100a and the terminal device 101 may communicate using any of the wireless communication technologies discussed above (e.g. a short-range wireless communication such as Bluetooth®, e.g. BLE). The terminal device 101 may temporarily store the preloaded biometric token in memory (e.g. RAM) for a maximum period specified by the token (e.g. in the range 30 - 60 seconds). The terminal device 101 can be configured to: obtain the face data for the user; generate a validation token in response to a successful match based on the face data and the preloaded
[0318] H 16964 WObiometric token communicated by the user device; and perform validation of the validation token. The operations at the terminal device 101 can therefore successfully authenticate the user (without accessing online services) and permit access for a local resource. For example, the terminal device 101 may be positioned at a gate or similar entry for an event and may permit access using the gate / entry. In some embodiments of the disclosure, the terminal device 101 may be connected to a vehicle, and may permit access for the vehicle, such as unlocking a car’s central locking system and / or activating an ignition.
[0319] Pre-authorised payment (e.g. transaction authorisation, identity-validated request) tokens may be communicated to the terminal device 101 and validated locally. The pre-authorised payment (e.g. transaction authorisation, identity-validated request) tokens may have been pre-authorised by an entity (bank, card holder or similar) with an upper limit for a transaction amount. Therefore, the terminal device 101 may be able to process payment (e.g. transaction authorisation, identity-validated requests when offline and store a log for one or more offline transactions. During an online period, the terminal device 101 may communicate with one or more online devices for completion of offline transactions.
[0320] The secure token storage circuitry 800 may store preloaded tokens (preloaded biometric tokens and optionally pre-authorised payment (e.g. transaction authorisation, identity-validated request) tokens) which may have an associated lifetime (e.g. in units of time) and / or associated limit on a number of uses. In some examples, the pre-loaded tokens may be generated with a lifetime (e.g. time-to-live "TTL") in the range 1-3 days. The pre-loaded tokens may be revocable and / or single use. In some examples, the user device 100a may store a predetermined number of pre-loaded tokens. The number of pre-loaded tokens that can be stored at any given time may be capped (e.g. to a value in the range 3 to 10). Pre-loaded tokens may be automatically updated at periodic intervals at times when the user device has access to one or more online servers. For example, pre-loaded tokens may expire or may be revoked every Y days (Y may be a value in the range 1 to 5) and replaced with new pre-loaded tokens.
[0321] Generalised authorisation
[0322]
[0323] Figure 9 schematically illustrates a method 900 for user authentication using a generalised authorisation protocol applicable to one or more authentication inputs. The method 900 comprises:
[0324] obtaining (at a step 910) at least one authentication input for a user;
[0325] performing (at a step 920) validation of the at least one authentication input against a corresponding reference, the reference being accessible to the processing system at the time of validation;
[0326] H 16964 WOdetermining (at a step 930) whether to perform supplementary authentication processing in dependence on configurable security information, the configurable security information comprising one or more conditions for triggering the supplementary authentication processing;
[0327] in response to determining that supplementary authentication processing is to be performed (shown as Y at the step 940), the method comprises:
[0328] obtaining (at a step 950) at least one user identifier associated with the user; performing (at a step 960) validation of the at least one user identifier; and permitting (at a step 970) access for a resource conditional on successful validation of the at least one user identifier.
[0329] In response to determining that supplementary authentication processing is not to be performed (shown as N at the step 940), the method may proceed directly to the step 970 to permit access for the resource conditional on successful validation of the authentication input.
[0330] The method 900 represented by Figure 9 generalises the method described in relation to Figures 4, 5, 6a, 6b and 6c by abstracting the authentication input from face data specifically to any suitable authentication input. The configurable security information, supplementary authentication processing, and access-gating logic operate identically regardless of the type of authentication input used.
[0331] Figure 10 schematically illustrates an example processing system 1000 operable to obtain authentication input from one or more of a plurality of authentication input modalities. The processing system 1000 comprises a terminal device 101 in communication with one or more input modalities including, by way of example only and not as a limitation: an image sensor for face data capture; an audio sensor for voice input capture; an iris scanner; a fingerprint scanner; a gesture detection sensor; communication circuitry for receiving a device identification parameter wirelessly communicated by a registered user device; a geolocation receiver; a presence detection sensor; a motion detection sensor; an ambient sensor; and a time-based trigger source. The terminal device 101 is configured to obtain at least one authentication input from one or more of the plurality of input modalities and to proceed with validation according to the method 900 of Figure 9.
[0332] Figure 11 schematically illustrates a method for user authentication using configurable security information comprising a plurality of authentication processing levels including a duress detection level. Figure 11 represents an extension of Figure 7 in which the duress detection level is depicted as a native authentication processing level within the hierarchical framework. Referring to Figure 11, the method comprises evaluating, in hierarchical order, a plurality of authentication processing levels comprising at least: a first level operable on a device identification parameter wirelessly communicated by a registered user device; a second level operable on one or more user identifiers other than face data; a duress detection level operable on any signal accessible to the processing
[0333] H 16964 WOsystem indicative of duress, including but not limited to user properties, environmental properties, behavioural properties, or contextual properties; and a fourth level operable on validation-outcome related conditions. In response to triggering of the duress detection level, the processing system enters a limited access mode for one or more resource types. The duress detection level uses the same condition-evaluation, routine-selection, and access-gating logic as the other authentication processing levels.
[0334] Figure 12 schematically illustrates an example system for cross-venue session activation using a reference accessible to processing systems associated with a plurality of venues operated by distinct operators. Referring to Figure 12, the system comprises a reference accessible to the processing systems by any mechanism providing such accessibility, including but not limited to a centralised registry, a federated identity protocol, a distributed ledger, or a peer-to-peer reference exchange. A user registers once by providing at least one authentication input, and on subsequent interactions at any of the plurality of venues, the user is recognised against the same reference and a session is activated at that venue without requiring re-registration.
[0335] Figure 13 schematically illustrates an example system for multi-zone session activation across a sequence of defined zones associated with a user. Referring to Figure 13, the processing system maps a plurality of defined zones associated with a sequence of locations the user is anticipated to or does traverse, including but not limited to a travel itinerary, an event-day sequence, an appointment sequence, or a user-defined zone sequence. At each of the plurality of defined zones, the processing system performs validation of at least one authentication input for the user and activates one or more context-aware services associated with that zone in dependence on the zone identity and the user's position within the sequence.
[0336] In some embodiments of the disclosure, the processing system may be configured to deliver zonespecific information to the user device via a notification subscription established at a point of initial registration. The notification subscription may be established via any interface accessible to the user device without requiring installation of a native application on the user device, including by way of example only and not as a limitation a browser-accessible interface, a progressive web application interface, or any other delivery interface achieving the property of subscription establishment without native application installation. At each of the plurality of defined zones in the sequence, in response to successful validation of the authentication input at that zone, the processing system may be configured to automatically deliver one or more zone-specific notifications to the user device via the notification subscription, by any delivery mechanism, including but not limited to direct transmission, relay through one or more intermediate nodes, or retrieval triggered by the validation event, the content of the one or more zone-specific notifications being determined in dependence on the zone identity and the user's position within the sequence. The notification subscription, once established, remains active and operable across the plurality of
[0337] H 16964 WOdefined zones, such that the user is not required to re-subscribe, to re-authenticate the subscription, to install any application, or to perform any further interaction in order to receive zonespecific notifications at any subsequent zone in the sequence. The point of initial registration may comprise, by way of example only and not as a limitation, a trigger event as described elsewhere in this disclosure, including but not limited to a scannable optical marker interaction, a user input, or an ambient sensor input.
[0338] Figure 14 schematically illustrates an example system for aggregate presence routing using a plurality of device identification parameters across one or more defined zones. Referring to Figure 14, the processing system obtains aggregate presence data for a defined zone, the aggregate presence data including but not limited to a plurality of device identification parameters wirelessly communicated by a plurality of registered user devices within the defined zone. The processing system determines a density metric for the defined zone in dependence on the aggregate presence data, evaluates the density metric against one or more routing conditions, and in response to the density metric satisfying one or more routing conditions, transmits one or more routing instructions to one or more output devices. The same architecture may be applied across a plurality of defined zones for emergency evacuation and routing applications.
[0339] Figure 15 schematically illustrates an example system for product identification with authenticationconditional egress at an exit point. Referring to Figure 15, the processing system obtains one or more product identification parameters from one or more products by any product identification mechanism, including but not limited to short-range wireless communication from one or more product tags, optical recognition, weight-based detection, or any other product identification method. The processing system obtains at least one authentication input for a user, performs validation of the at least one authentication input and the one or more product identification parameters, and in response to successful validation, authorises a transaction associated with the one or more products and permits physical egress without requiring manual interaction.
[0340] The invention may also broadly consist in the parts, elements, steps, examples and / or features referred to or indicated in the specification individually or collectively in any and all combinations of two or more said parts, elements, steps, examples and / or features. In particular, one or more features in any of the embodiments described herein may be combined with one or more features from any other embodiment(s) described herein.
[0341] Although certain example embodiments of the invention have been described, the scope of the appended claims is not intended to be limited solely to these embodiments. The claims are to be construed literally, purposively, and / or to encompass equivalents.
[0342] H 16964 WOWhen used in this specification and claims, the terms "comprises" and "comprising" and variations thereof mean that the specified features, steps or integers are included. The terms are not to be interpreted to exclude the presence of other features, steps or components.
[0343] It will be appreciated that example embodiments can be implemented by computer software operating on a general purpose a computing system. In these examples, computer software, which when executed by a computer, causes the computer to carry out any of the methods discussed above is considered as an embodiment of the present disclosure. Similarly, embodiments of the disclosure are provided by a non-transitory, machine-readable storage medium which stores such computer software.
[0344] It will also be apparent that numerous modifications and variations of the present disclosure are possible in light of the above teachings. It is therefore to be understood that within the scope of the appended claims, the disclosure may be practised otherwise than as specifically described herein.
[0345] H 16964 WO
Claims
43CLAIMS1. A processing system comprising processing circuitry, wherein the processing system is configured to:obtain face data for a user;generate a validation token in response to a successful match based on the face data and a stored biometric token;perform validation of the validation token;determine whether to perform supplementary authentication processing in dependence on configurable security information, the configurable security information comprising one or more conditions for triggering the supplementary authentication processing;wherein in response to determining that supplementary authentication processing is to be performed, the processing system is configured to:obtain at least one user identifier associated with the user;perform validation of the at least one user identifier; andpermit access for a resource conditional on successful validation of the at least one user identifier.
2. The processing system according to claim 1 , wherein the configurable security information comprises at least one of:first configurable security information comprising one or more scenario-related conditions; andsecond configurable security information comprising one or more validation-outcome related conditions for at least one of face data validation and validation-token validation.
3. The processing system according to claim 2, wherein one or more of the scenario-related conditions specify one or more predetermined scenarios for which supplementary authentication processing is to be performed.
4. The processing system according to claim 3, wherein one or more of the scenario-related conditions specify at least one of: a time period; a geographical area and / or location associated with the user and / or a terminal device; a type of commercial sector associated with the resource, a type of information to be accessed; a type associated with the resource; and an amount associated with a financial transaction.
5. The processing system according to any one of claims 2 to 4, wherein one or more of the validation-outcome related conditions specify at least one of:whether obtained face data results in a successful match for a stored biometric token; and whether a validation token results in successful validation.H 16964 WO446. The processing system according to any preceding claim, wherein the configurable security information comprises a plurality of supplementary authentication processing routines, and wherein the processing system is configured to select a respective one of the plurality of supplementary authentication processing routines in dependence on one or more triggered conditions.
7. The processing system according to claim 6, wherein the configurable security information comprises associations between one or more of the one or more conditions and one or more of the plurality of supplementary authentication processing routines.
8. The processing system according to claim 6 or claim 7, wherein the configurable security information comprises a decision tree for selecting one or more user identifiers to be obtained for the user for the supplementary authentication processing, and optionally an order for obtaining and validating the one or more user identifiers.
9. The processing system according to any preceding claim, wherein the configurable security information comprises at least one condition defined in advance by the user.
10. The processing system according to claim 9, wherein the configurable security information further comprises at least one supplementary authentication processing routine defined in advance by the user.
11. The processing system according to any preceding claim, wherein the configurable security information comprises a plurality of respective authentication processing levels, each respective authentication processing level comprising one or more conditions, and wherein the configurable security information defines the plurality of respective authentication processing levels to have a hierarchical ordering so that the plurality of respective authentication processing levels are evaluated in hierarchical order.
12. The processing system according to claim 11 , wherein the processing system is configured to:determine a highest-ordered respective authentication processing level comprising one or more triggered conditions; andperform supplementary authentication processing in dependence on the highest-ordered respective authentication processing level comprising one or more triggered conditions.
13. The processing system according to any preceding claim, wherein the processing system is configured to:H 16964 WO45detect at least one device identification parameter wirelessly communicated by a registered user device associated with the user; andperform validation of the least one device identification parameter wirelessly communicated by the registered user device.
14. The processing system according to claim 13, wherein the processing system is configured to activate an image sensor to capture the face data for the user in response to successful validation of the at least one device identification parameter wirelessly communicated by the registered user device.
15. The processing system according to claim 13 or claim 14, wherein the processing system is configured to obtain the at least one device identification parameter wirelessly communicated by the registered user device for use as at least one user identifier for the supplementary authentication processing.
16. The processing system according to claim 15 when dependent on claim 11 or claim 12, wherein the configurable security information comprises a first-ordered level of the plurality of respective authentication processing level, the first-ordered level comprising one or more conditions which when triggered require the at least one device identification parameter wirelessly communicated by the user device to be validated.
17. The processing system according to any preceding claim, wherein the processing system is configured to operate in an offline mode, wherein the system comprises:a terminal device comprising an image sensor to capture the face data for the user; and a user device associated with the user, wherein the user device comprises secure token storage circuitry to store one or more preloaded biometric tokens and communication circuitry configured to communicate a preloaded biometric token to the terminal device for temporary storage at the terminal device.
18. The processing system according to claim 17, wherein the terminal device is configured to:obtain the face data for the user;generate the validation token in response to a successful match based on the face data and the preloaded biometric token communicated by the user device; and perform validation of the validation token.
19. The processing system according to claim 17 or claim 18, wherein the preloaded biometric tokens are time-limited tokens which are updated periodically.H 16964 WO20. The processing system according to any one of claims 17 to 19, wherein the terminal device is configured to permit access for the resource without accessing one or more other devices.
21. The processing system according to any preceding claim, wherein the processing system is configured to operate in an online mode, wherein the system comprises a terminal device and one or more servers, the terminal device comprising first processing circuitry to:obtain the face data for the user;generate an encryption result in dependence on the face data; andcommunicate the encryption result to the one or more servers, wherein the one or more servers comprise second processing circuitry to:generate the validation token in response to the successful match based on the face data and the stored biometric token; andperform validation of the validation token;wherein at least one of the first processing circuitry and the second processing circuitry is configured to:determine whether to perform the supplementary authentication processing in dependence on the configurable security information;wherein in response to determining that supplementary authentication processing is to be performed, at least one of the first processing circuitry and the second processing circuitry is configured to:obtain at least one user identifier associated with the user;perform validation of the at least one user identifier; andpermit use of a resource conditional on successful validation of the at least one user identifier.
22. A computer-implemented method comprising:obtaining face data for a user;generating a validation token in response to a successful match based on the face data and a stored biometric token;performing validation of the validation token;determining whether to perform supplementary authentication processing in dependence on configurable security information, the configurable security information comprising one or more conditions for triggering the supplementary authentication processing;in response to determining that supplementary authentication processing is to be performed:obtaining at least one user identification parameter associated with the user; performing validation of the at least one user identification parameter; andH 16964 WOpermitting access for a resource conditional on successful validation of the at least one user identification parameter.
23. Computer software which, when executed by a processing system, causes the processing system to carry out the method of claim 22.
24. A processing system comprising processing circuitry, wherein the processing system is configured to:obtain at least one authentication input for a user;perform validation of the at least one authentication input against a corresponding reference, the reference being accessible to the processing system at the time of validation;determine whether to perform supplementary authentication processing in dependence on configurable security information, the configurable security information comprising one or more conditions for triggering the supplementary authentication processing;wherein in response to determining that supplementary authentication processing is to be performed, the processing system is configured to:obtain at least one user identifier associated with the user;perform validation of the at least one user identifier; andpermit access for a resource conditional on successful validation of the at least one user identifier.
25. A processing system comprising processing circuitry, wherein the processing system is configured to:obtain at least one authentication input for a user;presence detection; motion detection; ambient sensor input; and a time-based trigger; or any other authentication input from which a user may be identified or a session may be initiated;perform validation of the at least one authentication input against a corresponding reference;determine whether to perform supplementary authentication processing in dependence on configurable security information, the configurable security information comprising one or more conditions for triggering the supplementary authentication processing;wherein in response to determining that supplementary authentication processing is to be performed, the processing system is configured to:obtain at least one user identifier associated with the user;perform validation of the at least one user identifier; andpermit access for a resource conditional on successful validation of the at least one user identifier.H 16964 WO4826. A processing system comprising processing circuitry, wherein the processing system is configured to:obtain at least one authentication input for a user;perform validation of the at least one authentication input against a corresponding reference;evaluate configurable security information, the configurable security information comprising a plurality of authentication processing levels arranged in hierarchical order, the plurality of authentication processing levels comprising a duress detection level, the duress detection level comprising one or more conditions for detecting duress on the basis of any signal accessible to the processing system, including one or more user properties, environmental properties, behavioural properties, or contextual properties;determine a highest-ordered authentication processing level comprising one or more triggered conditions;in response to triggering of the duress detection level, cause the processing system to enter a limited access mode for one or more resource types; andpermit access for a resource conditional on the outcome of the highest-ordered authentication processing level.
27. The processing system according to claim 24, wherein the validation comprises generating a non-reversible representation of the authentication input for comparison with a corresponding non-reversible reference.
28. The processing system according to any one of claims 24 to 27, wherein the processing system is configured to be operable in an online mode in which validation of the authentication input is performed using one or more remote processing resources, and to be operable in an offline mode in which validation of the authentication input is performed locally without requiring access to one or more remote processing resources, using a reference accessible to the local processing environment, wherein the configurable security information operates identically in both modes.
29. The processing system according to any one of claims 24 to 28, wherein the at least one authentication input comprises a plurality of authentication inputs, and wherein the validation is performed against one or more references corresponding to the plurality of authentication inputs.
30. A processing system comprising processing circuitry, wherein the processing system is configured to:obtain at least one authentication input for a user via a browser-accessible interface; perform validation of the at least one authentication input against a corresponding reference;H 16964 WO49determine whether to perform supplementary authentication processing in dependence on configurable security information; andpermit access for a resource conditional on the validation outcome, the access being permitted within a single session.
31. A processing system comprising processing circuitry, wherein the processing system is configured to:obtain at least one authentication input for a user;determine whether the authentication input corresponds to a live user, by any process achieving the determination;determine an age classification for the user, by any process achieving the determination; generate a token encoding the age classification; andpermit access for a resource conditional on the token satisfying one or more age-related conditions associated with the resource.
32. A processing system comprising processing circuitry, wherein the processing system is configured to:detect a trigger event comprising one or more of: a scannable optical marker interaction, a user input, and an ambient sensor input;in response to the trigger event, obtain at least one authentication input for a user; generate a reference for the user associated with a future session identifier;on a subsequent interaction by the user, recognise the user via the at least one authentication input, reactivate the future session identifier, and permit access for a resource associated with the future session identifier.
33. The processing system according to claim 26, wherein the processing system is configured to establish a persistent session for a user across a plurality of access points associated with a defined role, and wherein triggering of the duress detection level causes modification of access permissions for one or more of the plurality of access points.
34. The processing system according to claim 25, wherein the processing system is configured to:detect a plurality of device identification parameters wirelessly communicated by a plurality of registered user devices within a defined proximity;determine a lead device from the plurality of registered user devices in dependence on one or more parameters associated with the registered user devices;establish a session associated with the lead device and one or more secondary devices.H 16964 WO5035. The processing system according to claim 25, wherein in response to successful validation of the authentication input and the at least one user identifier, the processing system is configured to trigger one or more interface logic events at one or more output devices within a defined proximity of the user, the one or more interface logic events being determined in dependence on the validation outcome and the proximity of the user.
36. A processing system comprising processing circuitry, wherein the processing system is configured to:obtain aggregate presence data for a defined zone, the aggregate presence data including but not limited to a plurality of device identification parameters wirelessly communicated by a plurality of registered user devices within the defined zone;determine a density metric for the defined zone in dependence on the aggregate presence data;evaluate the density metric against one or more routing conditions; andin response to the density metric satisfying one or more routing conditions, transmit one or more routing instructions to one or more output devices.
37. The processing system according to claim 25, wherein the at least one authentication input comprises a device identification parameter wirelessly communicated by a registered user device entering a defined zone, and wherein the processing system is configured to activate a session for the user within the defined zone in response to successful validation of the authentication input, the session activating one or more services associated with the defined zone without requiring application software to be installed on the registered user device.
38. A processing system comprising processing circuitry, wherein the processing system is configured to:monitor a plurality of density metrics across a plurality of defined zones in dependence on aggregate presence data, including but not limited to device identification parameters wirelessly communicated by a plurality of registered user devices;evaluate the plurality of density metrics against one or more emergency conditions; and in response to the one or more emergency conditions being satisfied, transmit zonespecific instructions to one or more output devices to route users between zones, the zone-specific instructions being updated in dependence on changes in the density metrics.
39. A processing system comprising processing circuitry, wherein the processing system is configured to:obtain one or more product identification parameters from one or more products by a product identification mechanism;obtain at least one authentication input for a user;H 16964 WO51perform validation of the at least one authentication input and the one or more product identification parameters; andin response to successful validation, authorise a transaction associated with the one or more products and permit physical egress without requiring manual interaction.
40. A processing system comprising processing circuitry, wherein the processing system is configured to:generate a reference for a user, the reference being accessible to processing systems associated with a plurality of venues operated by distinct operators;at a first venue, perform validation of at least one authentication input for the user against the reference and activate a session for the user at the first venue;at one or more further venues, perform validation of at least one authentication input for the user against the same reference and activate a session for the user at each of the one or more further venues, without requiring re-registration at any further venue.
41. The processing system according to any one of claims 25 to 40, wherein the processing system is configured to:map a plurality of defined zones associated with a sequence of locations the user is anticipated to or does traverse;at each of the plurality of defined zones, perform validation of the at least one authentication input and activate one or more context-aware services associated with that zone in dependence on the zone identity and the user's position within the sequence.
42. The processing system according to claim 41 , wherein the processing system is further configured to:establish a notification subscription associated with the user at a point of initial registration, the notification subscription being established via an interface accessible to the user device without requiring installation of a native application on a user device associated with the user;at each of the plurality of defined zones, in response to successful validation of the at least one authentication input, automatically deliver one or more zone-specific notifications to the user device via the notification subscription, the content of the one or more zone-specific notifications being determined in dependence on the zone identity and the user's position within the sequence;wherein the notification subscription, once established, remains active and operable across the plurality of defined zones without requiring the user to re-subscribe, to re-authenticate the subscription, or to install any application at any subsequent zone in the sequence.
43. A computer-implemented method comprising:obtaining at least one authentication input for a user;H 16964 WO52performing validation of the at least one authentication input against a corresponding reference;determining whether to perform supplementary authentication processing in dependence on configurable security information, the configurable security information comprising one or more conditions for triggering the supplementary authentication processing;in response to determining that supplementary authentication processing is to be performed:obtaining at least one user identifier associated with the user;performing validation of the at least one user identifier; andpermitting access for a resource conditional on successful validation of the at least one user identifier.
44. Computer software which, when executed by a processing system, causes the processing system to carry out the method of claim 43.
45. A processing system comprising processing circuitry, wherein the processing system is configured to:obtain at least one authentication input for a user;perform a validation operation on the at least one authentication input;determine whether to perform supplementary authentication processing in dependence on configurable security information, the configurable security information comprising one or more conditions for triggering the supplementary authentication processing, the one or more conditions being evaluable against the validation outcome regardless of the process used to produce the validation outcome;wherein in response to determining that supplementary authentication processing is to be performed, the processing system is configured to:obtain at least one user identifier associated with the user;perform a validation operation on the at least one user identifier by any process operable to produce a validation outcome; andpermit access for a resource conditional on the validation outcome of the at least one user identifier.H 16964 WO
