THEREFOR

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This patent application claims the benefit of Canadian Patent Application No. 3,022,109 filed on October 25, 2018, which is incorporated herein by reference in its entirety.

FIELD OF THE DISCLOSURE

[0002] The present disclosure relates to digital certificate enrolment and management, and, in particular, to a digital certificate enrolment system and method, and challenge password management system and method therefor.

BACKGROUND

[0003] Digital certificates are commonly employed to securely identify an entity such as an end user or device, for instance to authenticate end users and encrypt/decrypt messages. Typically, a user will request a certificate from a Certification Authority (CA), which will issue an encrypted digital certificate containing the applicant’s public key and a variety of other user identification information.

[0004] In Active Directory-integrated public key infrastructures (PKIs), specifically for Enterprise CAs, user certificates can be automatically issued for domain users. However when using a non-Active Directory-integrated PKI, e.g. within the context of a standalone CA, certificate enrollment requests generally need to be authorized. A one-time password (OTP) is a common way of authorizing certificate enrolment, however, this typically requires user intervention, which can cause delay and/or user inconvenience.

[0005] This background information is provided to reveal information believed by the applicant to be of possible relevance. No admission is necessarily intended, nor should be construed, that any of the preceding information constitutes prior art or forms part of the general common knowledge in the relevant art. SUMMARY

[0006] The following presents a simplified summary of the general inventive concept(s) described herein to provide a basic understanding of some aspects of the disclosure. This summary is not an extensive overview of the disclosure. It is not intended to restrict key or critical elements of embodiments of the disclosure or to delineate their scope beyond that which is explicitly or implicitly described by the following description and claims.

[0007] A need exists for digital certificate enrolment systems and methods, and challenge password management systems and methods therefor, that overcome some of the drawbacks of known techniques, or at least, provides a useful alternative thereto. Some aspects of this disclosure provide examples of such processes, systems and methods.

[0008] In accordance with one aspect, there is provided a digital certificate enrolment front-end process digitally executable by one or more digital data processors for enrolling a digital certificate for a network entity with a corresponding certification authority (CA), the process comprising: requesting a challenge password on behalf of the network entity; providing the network entity secure access to said challenge password; obtaining a signed certification request from the network entity encompassing said challenge password; issuing a certificate enrolment request encompassing said challenge password on behalf of the network entity so to invoke issuance of the digital user certificate from the CA; and relaying the digital certificate to the network entity.

[0009] In one embodiment, prior to said requesting, the process further comprises receiving a preliminary certification request generated by the network entity; said providing comprises appending said challenge password to said preliminary certification request to create a digital digest representative thereof, and securely forwarding said digital digest to the network entity; and said obtaining comprises obtaining a digital signature from the network entity upon processing thereby of said digital digest to construct said signed certification request.

[0010] In one embodiment, the digital digest comprises a secure cryptographic hash.

[0011] In one embodiment, requesting a challenge password comprises processing a pre- emptive request received via an authorized administrative interface to pre-emptively obtain and securely store said challenge password; and said providing comprises, upon initiation of a digital certificate enrolment process for the network device, providing the network device secure access to said challenge password to locally generate said signed certificate request encompassing said challenge password.

[0012] In one embodiment, the challenge password comprises a one-time password (OTP).

[0013] In one embodiment, the certificate enrolment request comprises a simple certificate enrolment protocol (SCEP) request.

[0014] In one embodiment, the certification request comprises a certificate signing request (CSR).

[0015] In one embodiment, the digital certificate is to be associated with a designated entity, the process further comprising: digitally associating a digital identity of the designated entity with said challenge password; and only issuing said certificate enrolment request encompassing said challenge password upon verifying that a given entity identified by said signed certification request corresponds with said digital identity.

[0016] In one embodiment, the designated entity comprises an end user and wherein said digital identity comprises a digital end user identity.

[0017] In one embodiment, the designated entity comprises a network application instance and wherein said digital identity comprises a digital application instance identity.

[0018] In one embodiment, the designated entity comprises a target resource, wherein the digital certificate is to be used to digitally gain authorized access to the target resource, and wherein said digital identity comprises a digital target resource identity.

[0019] In one embodiment, the digital certificate is to be digitally associated with an authorized end user and a target resource to which the authorized end user is to be provided authenticated access using the digital certificate via the network device, the process further comprising: digitally associating a digital end user identity and a digital target resource identity corresponding with the authorized end user and the target resource, respectively, with said challenge password; and only issuing said certificate enrolment request encompassing said challenge password upon verifying that said signed certification request identifies said digital end user identity and said target resource identity.

[0020] In one embodiment, the target resource comprises or is associated with an instance of a network application, and wherein said digital target resource identity comprises a digital network application instance identity.

[0021] In one embodiment, the challenge password is requested from a registration authority (RA) having digital access to said certification authority and wherein said certificate enrolment request is issued to said RA.

[0022] In accordance with another aspect, there is provided a non-transitory computer-readable medium comprising statements and instructions stored thereon to be executed by one or more processors to implement a certificate enrolment front-end process to enroll a digital certificate for a network entity with a corresponding certification authority (CA) by executing the process as defined above.

[0023] In accordance with another aspect, there is provided a network device comprising a non- transitory computer-readable medium as defined above, or operable to execute the process as defined above.

[0024] In accordance with another aspect, there is provided a digital certificate enrolment system to enroll a digital certificate with a digital certification authority for a network entity, the system comprising; a digital certificate enrolment engine operable to interface with the digital certification authority and having a front-end interface operable to: request a challenge password on behalf of the network entity; provide the network entity secure access to said challenge password; obtain a signed certification request from the network entity encompassing said challenge password; issue a certificate enrolment request encompassing said challenge password on behalf of the network entity so to invoke issuance of the digital certificate from the certification authority; and relay the digital certificate to the network entity.

[0025] In one embodiment, the front-end interface is further operable to, prior to requesting said challenge password, receive a preliminary certification request generated by the network entity, wherein said front-end interface is further operable to append said challenge password to said preliminary certification request to create a digital digest representative thereof, and securely forward said digital digest to the network entity to obtain a digital signature from the network entity upon processing thereby of said digital digest to construct said signed certification request.

[0026] In one embodiment, the digital digest comprises a secure cryptographic hash.

[0027] In one embodiment, the front-end interface further comprises secure network access to a server directory and a network administrator interface, and is further operable to process a pre- emptive request received via said network administrator interface to pre-emptively obtain and securely store said challenge password on said server directory; wherein, upon initiation of a digital certificate enrolment process for the network entity, said front-end interface provides the network entity authenticated access to said challenge password to locally generate said signed certificate request encompassing said challenge password.

[0028] In one embodiment, the system further comprises the digital certification authority, and wherein said digital certification authority comprises a standalone digital certification authority.

[0029] In one embodiment, the system further comprises an enterprise management device operating an enterprise management application having communicative access to the network entity and said front-end interface to intermediate certificate enrolment for the network device.

[0030] In one embodiment, the challenge password comprises a one-time password (OTP).

[0031] In one embodiment, the certificate enrolment request comprises a simple certificate enrolment protocol (SCEP) request.

[0032] In one embodiment, the certification request comprises a certificate signing request (CSR).

[0033] In one embodiment, the digital certificate is to be associated with a designated entity, and wherein said front-end interface is further operable to: digitally associate a digital identity of the designated entity with said challenge password; and prior to issuing said certificate enrolment request, verify that said challenge password to be encompassed therein corresponds with said digital identity.

[0034] In one embodiment, the designated entity comprises an end user of the network device and wherein said digital identity comprises a digital end user identity.

[0035] In one embodiment, the designated entity comprises a network application instance and wherein said digital identity comprises a digital application instance identity.

[0036] In one embodiment, the designated entity comprises a target resource, wherein the digital certificate is to be used to digitally gain authorized access to the target resource using the network device, and wherein said digital identity comprises a digital target resource identity.

[0037] In one embodiment, the digital certificate is to be digitally associated with an authorized end user and a target resource to which the authorized end user is to be provided authenticated access using the digital certificate via the network device, said front-end interface being further operable to digitally associate a digital end user identity and digital target resource identity with said challenge password; and prior to issuing said certificate enrolment request, verifying that said challenge password to be encompassed therein corresponds with said digital end user identity and said digital target resource identity.

[0038] In one embodiment, the target resource comprises or is associated with an instance of a network application, and wherein said digital target resource identity comprises a digital network application instance identity.

[0039] In accordance with another aspect, there is provided a digital certificate enrolment front- end process digitally executable by one or more digital data processors for enrolling a digital certificate with a corresponding certification authority (CA), wherein the digital certificate is to be associated with a designated entity, the process comprising: digitally associating a digital identity of the designated entity with a challenge password to be used for enrolling the digital certificate for the designated entity; obtaining a request for the digital certificate issued from a given network device and encompassing said challenge password, wherein said request identifies a given entity to be associated with the digital certificate and; verifying that said given entity identified by said request corresponds with said digital identity digitally associated with said challenge password; and upon said given entity corresponding with said digital entity, issuing a certificate enrolment request encompassing said challenge password on behalf of the given network device so to invoke issuance of the digital certificate for the designated entity from the CA to the given network device.

[0040] In one embodiment, the designated entity comprises at least one of an end user or a network application instance.

[0041] In one embodiment, the designated entity comprises a target resource, wherein the digital certificate is to be used to digitally gain authorized access to the target resource, and wherein said digital identity comprises a digital target resource identity.

[0042] In one embodiment, the digital certificate is to be digitally associated with an authorized end user and a target resource to which the authorized end user is to be provided authenticated access using the digital certificate via the given network device, and wherein digital identity comprises a digital authorized end user identity and digital target resource identity.

[0043] In one embodiment, the target resource is operatively associated with a network application instance, and wherein said digital target resource identity comprises a digital network application instance identity.

[0044] In accordance with another aspect, there is provided a non-transitory computer-readable medium comprising statements and instructions stored thereon to be executed by one or more processors to implement a certificate enrolment policy enforcement process by executing the process as defined above.

[0045] Other aspects, features and/or advantages will become more apparent upon reading of the following non-restrictive description of specific embodiments thereof, given by way of example only with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES

[0046] Several embodiments of the present disclosure will be provided, by way of examples only, with reference to the appended drawings, wherein: [0047] FIGURE 1 is a component diagram for an environment in which embodiments of the disclosure may be practiced;

[0048] FIGURE 2 is a diagram of an exemplary client computer that may be included in a system in accordance with at least one of the various embodiments;

[0049] FIGURE 3 is a diagram of an exemplary network computer that may be included in a system in accordance with at least one of the various embodiments;

[0050] FIGURE 4A and FIGURE 4B are schematic physical and logical diagrams, respectively, of a wearable user authentication / access authorization device, in accordance with at least one of the various embodiments;

[0051] FIGURE 5A is a logical schematic diagram of a biometric device showing sensors for fingerprint scanning and electrocardiogram signal capturing in accordance with at least one of the various embodiments;

[0052] FIGURE 5B is a logical schematic diagram of a biometric device showing another arrangement of sensors for fingerprint scanning and electrocardiogram signal capturing in accordance with at least one of the various embodiments;

[0053] FIGURE 5C is a logical schematic diagram of a biometric device showing a top view of the embodiment of Figure 5B for fingerprint scanning and electrocardiogram signal capturing;

[0054] FIGURE 6 is a high level system diagram illustrating interactions between various user authentication devices (UAD) and a customer client machine operating an enterprise management application for managing user presence authentication and/or access authorizations to various customer resources based, at least in part, on digital certificates issued by an external certification authority via enterprise network device enrolment and front-end enrolment services, in accordance with one embodiment;

[0055] Figure 7 is a diagram of communication sequences between various components of the system illustrated in Figure 6 to implement digital certificate enrolment, in accordance with one embodiment; [0056] Figure 8 is a diagram of communication sequences between various components of the system illustrated in Figure 6 to implement digital certificate enrolment, in accordance with one embodiment; and

[0057] Figure 9 is a diagram of illustrative communication sequences for different processes involved in the implementation of one-time password requests and enforcement policies for digital certificate enrolment, in accordance with one embodiment.

[0058] Elements in the several figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be emphasized relative to other elements for facilitating understanding of the various presently disclosed embodiments. Also, common, but well-understood elements that are useful or necessary in commercially feasible embodiments are often not depicted in order to facilitate a less obstructed view of these various embodiments of the present disclosure.

DETAILED DESCRIPTION

[0059] Various implementations and aspects of the specification will be described with reference to details discussed below. The following description and drawings are illustrative of the specification and are not to be construed as limiting the specification. Numerous specific details are described to provide a thorough understanding of various implementations of the present specification. However, in certain instances, well-known or conventional details are not described in order to provide a concise discussion of implementations of the present specification.

[0060] Various apparatuses and processes will be described below to provide examples of implementations of the system disclosed herein. No implementation described below limits any claimed implementation and any claimed implementations may cover processes or apparatuses that differ from those described below. The claimed implementations are not limited to apparatuses or processes having all of the features of any one apparatus or process described below or to features common to multiple or all of the apparatuses or processes described below. It is possible that an apparatus or process described below is not an implementation of any claimed subject matter. [0061] Furthermore, numerous specific details are set forth in order to provide a thorough understanding of the implementations described herein. However, it will be understood by those skilled in the relevant arts that the implementations described herein may be practiced without these specific details. In other instances, well-known methods, procedures and components have not been described in detail so as not to obscure the implementations described herein.

[0062] In this specification, elements may be described as“configured to” perform one or more functions or“configured for” such functions. In general, an element that is configured to perform or configured for performing a function is enabled to perform the function, or is suitable for performing the function, or is adapted to perform the function, or is operable to perform the function, or is otherwise capable of performing the function.

[0063] It is understood that for the purpose of this specification, language of“at least one of X, Y, and Z” and“one or more of X, Y and Z” may be construed as X only, Y only, Z only, or any combination of two or more items X, Y, and Z (e.g., XYZ, XY, YZ, ZZ, and the like). Similar logic may be applied for two or more items in any occurrence of“at least one ...” and“one or more...” language.

[0064] Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs.

[0065] Throughout the specification and claims, the following terms take the meanings explicitly associated herein, unless the context clearly dictates otherwise. The phrase“in one of the embodiments” or“in at least one of the various embodiments” as used herein does not necessarily refer to the same embodiment, though it may. Furthermore, the phrase“in another embodiment” or“in some embodiments” as used herein does not necessarily refer to a different embodiment, although it may. Thus, as described below, various embodiments may be readily combined, without departing from the scope or spirit of the innovations disclosed herein.

[0066] In addition, as used herein, the term“or” is an inclusive“or” operator, and is equivalent to the term“and/or,” unless the context clearly dictates otherwise. The term“based on” is not exclusive and allows for being based on additional factors not described, unless the context clearly dictates otherwise. In addition, throughout the specification, the meaning of "a," "an," and "the" include plural references. The meaning of "in" includes "in" and "on."

[0067] As used in the specification and claims, the singular forms“a”,“an” and“the” include plural references unless the context clearly dictates otherwise.

[0068] The term“comprising” as used herein will be understood to mean that the list following is non-exhaustive and may or may not include any other additional suitable items, for example one or more further feature(s), component(s) and/or element(s) as appropriate.

[0069] The terms“physiological,”“physiological data,” or“physiological signal” as used herein are understood to mean any signal that can be obtained via a sensor or device when operatively interfacing with a user to confirm a live user presence. Non-limiting examples of physiological signals are heart rate, galvanic skin response, temperature, electrocardiogram (ECG), photoplethysmogram (PPG), electromyogram, electroencephalogram, transient otoacoustic emissions, phonocardiogram, perspiration, or a combination thereof. A live user presence can also be confirmed using any combination of the above or other physiological parameters, as can other physiological signals and/or sensors be considered alone or in combination to produce this result.

[0070] The terms“biometric,”“biometric data,” or“biometric signal” as used herein are understood to mean any signal that can be obtained from a user that can uniquely identify the user, including, but not limited to, one or more unique physiological signals or signatures that can be processed to uniquely identifier the user. Non-limiting examples of biometric signals are gait, heart rate, galvanic skin response, temperature, fingerprint, voice or voiceprint, body electrical characteristic, body thermal characteristic, iris pattern, vein pattern, eye vein pattern, facial or other anatomical structure, electrocardiogram (ECG), photoplethysmogram (PPG), electromyogram, electroencephalogram, transient otoacoustic emissions, phonocardiogram, DNA, one or more chemical markers, one or more biochemical markers, skin-color variation or discolouration, perspiration, or a combination thereof. A unique identity of a user can also be obtained by observing patterns or combinations of one or more biometric characteristic. For example a person may have a unique heart rate at a particular temperature and with a particular amount of sweat. In this way, two or more biometric observations can be combined or fused to obtain a multi-modal unique biometric profile. This is especially useful in situations wherein one particular biometric is not sufficient as a standalone identifier. In one example, perspiration and gait can be combined or fused to provide a unique biometric profile for a user. Information from sources that are standalone identifiers can also be combined in order to increase accuracy and/or security. In another example, a multi-modal biometric system may fuse fingerprints with iris and face characteristics.

[0071] The terms“access point” and“resource” are used interchangeably herein refers to any logical or physical gateway, device, or application that requires authentication, such as for security or personalization purposes, and is otherwise locked or inaccessible to the user. Some non-limiting examples of physical access points are electronically locked doors, parking transceivers, smart environment technologies, vehicle doors and transit systems. Some non limiting examples of logical access points are password, PIN, passcode or otherwise digitally protected electronic devices (e.g. smartphone, desktop computer, laptop, tablet, workstation, onboard vehicular device, etc.) or accounts, proof of payment systems, point of sale stations, automated bank teller machines, library checkout systems, and hotel and airport check-in stations. Further, access points may be considered a generic term for applications, computers, terminals, devices, or the like, that are enabled to communicate using the protocols described herein. For example, a wireless access point may be operatively associated with a network application to identify, monitor or track an authenticated user presence without necessarily invoking a further action in response to such recognized user presence. Namely, while some embodiments may encompass an access point for the purposes of authenticating a user presence in order to grant the user authenticated access to a particular resource, user presence authentication may not be limited to such applications, but may also include embodiments where a user’s authenticated presence is recognized, monitored and/or tracked for other purposes, such as for advertising, analyzing user traffic an/or usage of designated physical spaces, law enforcement, etc. For simplicity, the terms “access point” and “resource” will be used interchangeably herein to refer not only to the computational device or application (e.g. physical hardware, firmware and/or software application) being accessed and operated to implement or provide for user presence authentication and/or access authorizations, but also any one or more resources that are operatively associated therewith, whereby a resources may include, but is not limited to: a physical space, room, zone or area contained or otherwise restricted by an electronically controlled gateway, door, gate or entryway; physical or computational workstation, device, equipment and/or tool for manufacturing, testing, verification, simulation, development, research, experimentation, development, assembly, etc.; physical or digital library, directory, repository and/or other classified or restricted information repository; and/or the like.

[0072] The term“access control signal” as used herein refers to the signal sent by an access control device to a physical or logical access point that may enable the user to unlock or access the access point. The control signal may be a binary encoded sequence or user identifier transmitted wired or wirelessly using but not limited to Bluetooth, near field communication, ultra-wide band, RFID, or Wi-Fi. The control signal is generally a non-biometric signal, however it can also be a biometric signal if the access control at the access point requires it depending on the application and/or context at hand.

[0073] The term“finger” as used herein refers to any digit attached to a hand or foot, including a thumb or a toe.

[0074] The term "encryption" as used herein is understood to refer to actions that change (information) from one form to another especially to hide its meaning. Further, in some embodiments, encryption as used herein may include employing pseudorandom transformations that produce pseudorandom outputs in the sense that a cipher text may be distinguishable from a completely random sequence of bits of the same length without revealing anything about the plaintext. For example, consider adding one or more zeros at the end of every encryption output. In at least one of the various embodiments, encryption may include applying pseudo-random function information, where the key of the pseudorandom function may be stored locally on a mobile device.

[0075] The terms "authorized authentication device" and“user authentication device” as used herein refer to devices and/or access points that may be arranged to include specialized applications for enrolling/registering a mobile device with a user. Authorized authentication devices (AADs) may be arranged to store keys, encrypted biometric user profiles, or the like. In some embodiments, implementation of at least some of the AAD functionality may be incorporated and/or otherwise embedded within the functions of a portable device, such as embedded within a wearable authentication/user access authorization device or the like, and/or distributed between such portable/wearable devices and/or one or more network-accessible servers, client computers, access points or the like. In some of the examples provided herein, a user authentication device or“UAD” is defined as a portable or wearable device operable to execute onboard user authentication procedures to thereby activate the UAD to broadcast or otherwise communicate or distribute an authenticated user status or identity for implementing/processing authenticated user presence or access privileges with one or more access points/resources.

[0076] The following briefly describes various embodiments in order to provide a basic understanding of some aspects of the herein described technology. This brief description is not intended as an extensive overview. It is not intended to identify key or critical elements, or to delineate or otherwise narrow the scope. Its purpose is merely to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

[0077] Briefly stated, various embodiments are directed towards communicating using a mobile device, such as a mobile or wearable user authentication and user presence and/or access authorization device in a secured environment. Co-pending Canadian Patent Application No. 2,992,333 for a User Access Authorization System and Method, and Physiological User Sensor and Authentication Device Therefor, and U.S. Patent No. 9,197,414 for a Cryptographic Protocol for Portable Devices, the entire contents of each of which are hereby incorporated herein by reference, provide illustrative environments and contexts for implementation of the herein described embodiments.

[0078] In some of the herein-described embodiments, some of the challenges and/or inconveniences associated with the use of challenge passwords, such as one-time passwords (OTPs), to authorize digital certificate enrolment are mitigated, for example, by providing measures to bypass user action in this respect and/or to enforce certain password security enhancement policies. For instance, in some embodiments, an enrolment front-end service (e.g. server, application, engine, etc., generically and interchangeably referenced herein as a front-end interface, engine and/or process) is provided, for example, within the context of an external certification authority (e.g. a non-Active Directory-integrated public key infrastructure (non AD- integrated PKI) or standalone CA operable to manage, intermediate and/or otherwise facilitate certificate enrolment and/or policy enforcement/enhancement for various customer end users/entities (e.g. users, applications, etc.), such as, during enterprise setup for a particular client system, device or user, and/or for the purposes of certificate renewals, revocations, re- initializations, etc.

[0079] For example, in one particular embodiment, an external enterprise security services system is implemented for the purposes of providing customer security services in which multiple user authentication devices can be used to routinely authenticate authorized end users and manage user access privileges accordingly. For example, and with reference to the illustrative embodiment of Figure 6, a set of end users are provided with a corresponding set of portable (wearable) user authentication devices (UAD) 602 to be used to authenticate each end user (e.g. via PIN, password, onboard biometric authentication, etc.) for the purposes of communicating an authenticated user identity, for example, in authenticating a user presence and, in some further examples, gaining user access to one or more customer resources 604 accordingly. Various measures to ensure secure user authentication, live user presence, prevent fraud, collusion or the like are illustratively described below, as are other complementary/alternative means for securely authenticating the user via onboard and/or communicatively accessible authentication and status broadcast resources.

[0080] Following from the onboard authentication examples further described below, once a UAD is active, it may be used to securely authenticate the user, for example, to gain authenticated access to certain authorized resources 604 whose access is at least in part operatively controlled by a security-enabled (network) application 605 operating locally or distributively to communicate with nearby UADs 602 via a related access point or like communication path. For example, a given UAD 602 may be logically linked to a particular user to perform onboard user authentication to activate the UAD 602 and thus actively or selectively broadcast a user-authenticated status or authenticated user identity. For example, an actively authenticated or pre-authorized UAD may transact with one or more instances of a security enabled (network) application 605 that can be operated to recognize, monitor and/or track an authenticated user presence, for example, to grant authenticated user access to one or more corresponding resources 604 operatively associated therewith. For example, the network application 605 may be operated to securely identify the authenticated user (e.g. using one or more (mutual) user/device/application authentication procedures) in providing authenticated access to the corresponding resource if so authorized. For simplicity, the following examples will relate to a system for granting authenticated user access privileges to authenticated users based on successful user identification, authentication and communications relating thereto between a given UAD and network application (instance).

[0081] Accordingly, and as will be detailed below with reference to certain illustrative embodiments, each end user (User A, B, and C) may be attributed one or more customer access privileges (e.g. to Resource X, Y and/or Z) to be implemented via their respective UAD 602. To do so, respective digital certificates may be issued to accommodate such diversified access privileges; namely User A may seek to enrol a user-specific certificate to access Resource X (e.g. certificate(A,X) 620)), User B may seek to enrol respective user-specific certificates to respectively access each of Resources Y and Z (but not X), and User C may seek to enrol respective user-specific certificates for each resource along with possibly a higher level authorization certificate to access the enterprise management application 606. Each certificate can then be used to successfully negotiate access to its corresponding resource via the resource’s respective SEA instances 605 (or EMA 606). While this illustrative example contemplates user and target resource-specific certificates, similar considerations may apply to the enrolment of certificates to be associated with different entities, be they end users, network devices, applications and/or instances thereof, associated resources, or the like.

[0082] As noted above, in the illustrated embodiment, end user certificate enrolment is implemented via an external (standalone) CA 616, for example, to reduce customer impact and touch points in outsourcing managements of such security resources (which external CA can be used to provide certificate enrolment, and other security management services, to various customers interfacing therewith). In this embodiment, an enterprise management application 606 operates on a customer/client machine (e.g. local network infrastructure) 608 that interfaces with an enterprise server 610 operated by the external security services provider to process certificate enrolment requests, optionally among other UAD enterprise setup procedures.

[0083] To mitigate inconveniences common in the implementation of OTP steps common for certificate enrolment procedures using a standalone/external CA, and in accordance with some embodiments, a front-end certificate enrolment service, illustrated herein as a front-end Web enrolment service (WES) 612, is illustratively implemented by the enterprise server 610.

[0084] The WES is provided in this example to interface with the enterprise server’s network device enrolment service 614 (and downstream enterprise certification authority (CA) 616) and optional enterprise server directory 618, on the one side, and the customer-operated enterprise management application 606 on the other in circumventing user actions typically required to implement OTP verifications for certificate enrolment authorization. In some embodiments, an enterprise server administrator can initiate certain preparatory transactions to be later engaged by enterprise management application 606 with the enterprise server 610, for instance to invoke, via an authorized administrative interface, an automated OPT distribution before a certificate enrolment procedure is initiated for a given LAD 602, whereas in other embodiments, certificate enrolment procedures may be initiated for a given UAD 602 without pre-emptive action from such administrator.

[0085] In yet further embodiments, optional automated OTP policy enhancements may also be automatically invoked and implemented by the front-end enrolment service, as will be described in further detail below, for example, to enhance security provisions associated with such enrolments.

[0086] As will be appreciated by the skilled artisan, while the embodiment shown in Figure 6 provides one example of a local client and external server architecture to implement the functions and features described herein with respect to certificate enrolment, OTP management and optional OTP policy augmentation and enforcement, other system architectures and configurations may also or alternatively be considered to achieve similar results, and that, without departing from the general scope and nature of the present disclosure.

[0087] With added reference to Figure 7, and in accordance with one illustrative embodiment, a user certificate enrolment procedure, in this example effectively implemented without pre emptive OTP distribution, will now be described. In this example, certificate enrolment is initiated at step 702 upon initiating UAD enterprise setup and user authentication via the enterprise management application (EMA). In doing so, the UAD and EMA will proceed through mutual authentication at step 704, followed by the EMA generating a certificate signing request (CSR) at step 706. The UAD will locally generate a key pair at step 708 and send the CSR without OTP at step 710 to the EMA. The EMA and the enterprise server’s enrolment Web service (EWS) will establish a TLS connection with server authentication at 712, establish client authentication using the user’s authentication device credentials at 714 and forward the CSR without OTP at 716. The EWS will internally enforce applicable security policies (e.g. subjects in CSR and www client authentication must match) at 718, and, upon successful enforcement, request a OTP from the network device enrolment service (NDES) at 720 on behalf of the user. The OTP will be returned to the EWS at 722, which will append the OTP to the CSR and calculate a hash accordingly at 724. At 726, the EWS will request from the EMA that the CSR hash be signed, which request will be forwarded to the ETAD at 728. The CSR signature will be returned to the EMA at 730, which will be forwarded thereby at 732 to the EWS, which will itself at 734 construct the CSR and Simple Certificate Enrolment Protocol (SCEP) request to ultimately forward the SCEP request to the NDES at 736. The certificate request will finally be relayed to the enterprise certification authority (CA) at 738, which will return a user certificate at 740 to the NDES, which will itself forward the user certificate to the EWS at 742, to be forwarded at 744 to the EMA, and finally forwarded thereby to the UAD at 746 which stores the user certificate at 748. Enterprise setup can be pursued thereafter, and the user certificate employed as needed in subsequent user authentication/authorization procedures.

[0088] Using this illustrative approach, the front-end enrolment service authenticates the end entity (e.g. a user, an application) using existing credentials (e.g. UAD user / machine credentials). It then requests an OTP on behalf of the entity. It adds the OTP to the CSR and provides a digest of the updated CSR to the entity for re-signing. The OTP is never exposed to the end entity and the private key associated with the certificate is never exposed outside of the end entity.

[0089] With reference now to Figure 8, and in accordance with another illustrative embodiment, a user certificate enrolment procedure, in this example pre-emptively prepared by an enterprise administrator to enable automated OTP distribution, will now be described. In this example, the administrator will first request at 850, a OTP for a given user or users from the EWS. At 852, the OTP request is forwarded by the EWS to the NDES, which returns the requested OTP at 854. The OTP is then stored in an enterprise directory at 856, which completes the pre-emptive OTP administration procedure at 858.

[0090] Much as above, user certificate enrolment is then initiated at step 802 upon initiating UAD enterprise setup and user authentication via the enterprise management application (EMA). In doing so, the UAD and EMA will again proceed through mutual authentication at step 804 (e.g. establish secure authenticated access, for example, via Active Directory (AD)), followed by the EMA requesting the OTP corresponding to this particular user at 860 from the enterprise directory. The OTP is returned by the directory to the EMA at 862. Once returned, the EMA will generate a certificate signing request (CSR) at step 806 to the UAD, which will locally generate a key pair at step 808 and send the CSR, this time with OTP, at step 810. The EMA and the enterprise server’s enrolment Web service (EWS) will establish a TLS connection with server authentication at 812, establish client authentication using the user’s authentication device credentials at 814 and forward the CSR with OTP at 816. The EWS will internally enforce applicable security policies (e.g. subjects in CSR and www client authentication must match) at 818 and 819, and, upon successful enforcement, construct the simple certificate enrolment protocol (SCEP) request at 834 to ultimately forward the SCEP request (CSR with OTP) to the NDES at 836. The certificate request will finally be relayed to the enterprise certification authority (CA) at 838, which will return a user certificate at 840 to the NDES, which will itself forward the user certificate to the EWS at 842 in the form of a SCEP response, to be forwarded at 844 to the EMA in the form of a user certificate enrolment response, and finally forwarded thereby to the UAD at 846 which stores the user certificate at 848. The OTP can then be deleted from the directory at 864 and confirmed thereby at 866. Enterprise setup can be pursued thereafter, and the user certificate employed as needed in subsequent user authentication/authorization procedures.

[0091] Using this approach, the front-end enrollment service provides an interface for an administrative user to request OTPs on behalf of specific end-entities (users / machines). The OTPs are stored in a back-end database (e.g. enterprise directory). When the end entity authenticates with the enrollment service and submits a certificate request, the OTP is retrieved from the database and provided to the enrollment service. Enrollment service includes the OTP and asks the end-entity to re-sign the CSR as in the previous option. [0092] In each case, the ability to satisfy the need for authenticating / authorizing certificate enrollment is provided without the need for user intervention for distributing / entering OTP. Furthermore, the OTP value is never exposed to the end user / end entity hence reducing the opportunity for abusing OTP.

[0093] As referenced above, in some embodiments, such as that illustrated in Figures 7 and 8, the EWS may be operated to enforce certain OTP policies when processing a particular certificate request. As will be noted below, while OTP policy implementation and enforcement may be considered within the exemplary embodiments of Figures 7 and 8, such policy implementation and enforcement considerations may also, or alternatively be considered independently within the context of other certificate enrolment procedures.

[0094] For example, certificate enrollment protocols like PKCS10 and SCEP generally make use of a challenge Password for authorizing certificate enrollment. A given registration authority (RA) may enforce certain policies on the challenge Password, e.g. the challenge Password may be for one-time use only (e.g. OTP), and may expire after a certain period of time. However, in some scenarios, the policy enforced by the RA may not be adequate for the security requirements of the system in question, for example when the registration authority is based on a commercial off the shelf product.

[0095] With reference to Figure 9, and in accordance with one embodiment, a certificate enrolment challenge password (e.g. OTP) policy augmentation method and system may be implemented to enhance security considerations surrounding certificate enrolment and related OTPs issued therefor. For example, in the illustrated embodiment of Figure 9, a certificate enrolment service 912 (e.g. a RA front-end or the EWS of Figures 6, 7 or 8), may be implemented to interface with a registration authority 914 (e.g. network device enrolment service of Figures 6, 7 or 8) to process OTP requests and policies, and certificate requests related thereto and directed to a target certification authority (CA) 916 accessible to the RA. As detailed below, policy augmentations may include, but are not limited to, restricting successful OTP processing to a target end user (e.g. end user A, B or C in Figure 6) and/or subject (e.g. resource X, Y or Z in Figure 6) for which a related digital certificate is to be issued and subsequently used for user identification, authentication and/or access authorization procedures. As noted above, other target or designated entity types may be considered herein without departing from the general scope and nature of the present disclosure, such as different end users, devices, applications or the like and that, in various combinations as may be relevant or applicable to the application and environment at hand.

[0096] In the illustrated example, different scenarios are illustrated, namely a OTP request sequence (shown in solid lines), an unauthorized certificate request sequence based on the issued OTP and applied policy augmentations (shown in dash-dot lines), and an authorized certificate request sequence based on the issued OTP and applied policy augmentations (shown in dotted lines). In the first sequence, at 1002, User A requests a OTP for Subject (e.g. Resource) X from the enrolment service 912. For example, User A may be represented by an end user identity, whereas Subject X may be represented by a target network-enabled resource identity to which the end user wishes to gain authenticated user access, thus the end user being the source of the enrolment request whereas the target resource is the subject. The enrolment service 912 at 1004 requests the OTP from the RA 914 and receives the OTP therefrom at 1006. The enrolment service 912 then, at 1008, stores the OTP, along with certain policy augmentations that may be applied thereto beyond the standard one-time use and possible lifetime policies; in this case, policies are augmented to both identify the intended user for whom the OTP has been issued and the intended subject for which it was issued. For example, these policies may be stored together with a hash of the OTP (e.g. annotated as OTR(A,C)). The OTP is then delivered to User A at 1010

[0097] In the examples provided above and further below, a user within this context may include, but is not limited to, an authorized end user for whom authenticated user access may be authorized for certain system resources, which resources may be the subject of the digital certificate being requested. As detailed below, resources may include different forms of physical, logical, computational and/or like resources within a given environment for which particular user access restrictions and/or authorizations may be required and applied in accordance with different user/management preferences, profiles and/or criteria. In some embodiments, a OTP request subject may thus define the particular access resource selected for this user, whereby distinct certificate enrolment requests, and related OTP processes, may be applied for each given user and for each resource to which each such given user is to be provided authenticated authorized user access. That being said, the embodiments herein described are not to be limited to such examples, whereby a particular user defined for a particular OTP request and subsequent certificate may rather, or additionally include a client application, device or the like, whereas a particular subject may include different resources, applications, devices or the like as may be applicable within the particular context at hand.

[0098] Continuing with the example of Figure 9, when a Request for certificate enrolment is received from User A for Subject X at 1012, the enrolment service 912 will generally authenticate User A, extract the OTP and enforce the policies at 1014 before the certificate request can be authorized to proceed. In this case, provided that this is the first time the OTP is used and the request is made within the lifetime of the OTP, since the authenticated request came from User A and is for Subject X, the request is authorized by the enrolment service 912 and proceeds at 1016 to the RA 914 and ultimately at 1018 with the CA 916 to return the requested certificate (e.g. Cert(A,X)) to User A at 1020 for Subject X.

[0099] On the other hand, should a request for certificate come from User B using the OTP previously issued to User A for Subject X, shown as step 1022, the enrolment service 912 will automatically identify a mismatch at 1024 between the originating user defined by the augmented OTP policies, and reject the certificate request at 1026. A similar scenario may be applied where User A wrongly uses the issued OTP for an unauthorized subject (e.g. Subject Y).

[00100] In response to an unauthorized attempt to use an issued OTP, this OTP may be automatically discarded or marked as expired so to avoid further misuse, requiring that User A again request a new OTP for Subject X and try again, as appropriate.

[00101] As noted above, the OTP policy augmentation procedures described herein may be applied to different embodiments where a RA front-end is deployed to apply and enforce OTP policy augmentations, as can they be applied within the context of the systems and procedures described above with respect of Figures 6 to 8. For example, an enrolment front-end service, such as described above, may be implemented to interface with a registration authority, such as an off the shelf network device enrolment service, to not only mitigate OTP processing inconveniences, but also, or alternatively, to implement OTP policy augmentations to increase certificate enrolment security. [00102] Detailed below are some exemplary operating environments to implement the systems and procedures noted above. It will be appreciated that while the following description provides some examples, the above-described embodiments are not so limited and may be applied to other operating environments without departing from the general scope and nature of the present disclosure. For instance, the above and following examples describe the provision and enrolment of digital user certificates to be used in association with various user authentication devices and/or resources. While this provides one particular use of the herein described embodiments, similar notions may be applied to other fields making use of user digital certificates and OTP authorization procedures, and that, without departing from the general scope and nature of the present disclosure.

[00103] Furthermore, it will be appreciated that the certificate enrolment and OTP provisions described herein may be implemented at various stages or in different contexts depending on the application at hand. For example, in the illustrated embodiments, certificate enrolment may be required or otherwise implemented when a new entity is to be registered/setup with the system. For example, a user certificate may be created when a new user enrols a new authentication device within the context of the portable user authentication device described below. Similarly, an application certificate may be generated every time a new application (e.g. a new instance of enterprise management application 606, or security-enabled application 605 of Figure 6) seeks to register itself with the system (e.g. enterprise server 610), for example. On the other hand, a new user or application certificate may be required where a previous certificate expires (e.g. in time- limited certificate enrolments) and/or when a previous certificate is revoked (e.g. within the context of a security breach, certificate abuse or misuse, etc.), provided previously certified entities are still valid and a system administrator confirms that they are to remain enrolled within the system). These and other such considerations are considered to fall within the general scope and nature of the present disclosure, as will be appreciated by the skilled artisan.

ILLUSTRATIVE OPERATING ENVIRONMENT

[00104] FIGURE 1 shows components, in accordance with one illustrative embodiment, of an environment in which embodiments of the invention may be practiced. Not all of the components may be required to practice different embodiments of the invention, and variations in the arrangement and type of the components may be made without departing from the general spirit or scope of the present disclosure. As shown, system 100 of FIGURE 1 includes local area networks (LANs)/ wide area networks (WANs) - (network) 110, wireless network 108, client computers 102-105, authentication / access authorization device 106 (generally referred to herein as authentication device 106, which may include, but is not limited to, a mobile, wireless, portable, wearable device and/or the like, for example), authentication / access authorization server computer 116 (generally referred to herein as authentication server 116), or the like.

[00105] At least one embodiment of client computers 102-105 is described in more detail below in conjunction with FIGURE 2. In one embodiment, at least some of client computers 102-105 may operate over one or more wired and/or wireless networks, such as networks 108, and/or 110. Generally, client computers 102-105 may include virtually any computer capable of communicating over a network to send and receive information, perform various online activities, offline actions, or the like. In one embodiment, one or more of client computers 102- 105 may be configured to operate within a business or other entity to perform a variety of services for the business or other entity. For example, client computers 102-105 may be configured to operate as a server, client application, media player, mobile telephone, game console, desktop computer, access point, or the like. However, client computers 102-105 are not constrained to these services and may also be employed, for example, as for end-user computing in other embodiments. It should be recognized that more or less client computers (as shown in FIGURE 1) may be included within a system such as described herein, and embodiments are therefore not constrained by the number or type of client computers employed.

[00106] Computers that may operate as client computer 102 may include computers that typically connect using a wired or wireless communications medium such as personal computers, multiprocessor systems, microprocessor-based or programmable electronic devices, network PCs, or the like. In some embodiments, client computers 102-105 may include virtually any portable computer capable of connecting to another computer and receiving information such as, laptop computer 103, mobile computer 104, tablet computers 105, or the like. However, portable computers are not so limited and may also include other portable computers such as cellular telephones, display pagers, radio frequency (RF) devices, infrared (IR) devices, Personal Digital Assistants (PDAs), handheld computers, wearable computers, integrated devices combining one or more of the preceding computers, or the like. As such, client computers 102-105 typically range widely in terms of capabilities and features. Moreover, client computers 102-105 may access various computing applications, including a browser, or other web-based application.

[00107] A web-enabled client computer may include a browser application that is configured to receive and to send web pages, web-based messages, and the like. The browser application may be configured to receive and display graphics, text, multimedia, and the like, employing virtually any web-based language, including a wireless application protocol messages (WAP), and the like. In one embodiment, the browser application is enabled to employ Handheld Device Markup Language (HDML), Wireless Markup Language (WML), WMLScript, JavaScript, Standard Generalized Markup Language (SGML), HyperText Markup Language (HTML), extensible Markup Language (XML), JavaScript Object Notation (JSON), or the like, to display and send a message. In one embodiment, a user of the client computer may employ the browser application to perform various activities over a network (online). However, another application may also be used to perform various online activities.

[00108] One embodiment of Client computers 102-105 are described in more detail below in conjunction with FIGURE 2. Briefly, however, Client computers 102-105 also may include at least one other client application that is configured to receive and/or send content between another computer. The client application may include a capability to send and/or receive content, or the like. The client application may further provide information that identifies itself, including a type, capability, name, and the like. In one embodiment, client computers 102-105 may uniquely identify themselves through any of a variety of mechanisms, including an Internet Protocol (IP) address, a phone number, Mobile Identification Number (MIN), an electronic serial number (ESN), or other device identifier. Such information may be provided in a network packet, or the like, sent between other client computers, server computer 116, device 106, or other computers.

[00109] Client computers 102-105 may further be configured to include a client application that enables an end-user to log into an end-user account that may be managed by another computer, such as server computer 116, or the like. Such an end-user account, in one non-limiting example, may be configured to enable the end-user to manage one or more online activities, including in one non-limiting example, project management, system administration, configuration management, search activities, social networking activities, browse various websites, communicate with other users, or the like.

[00110] One embodiment of device 106 is described in more detail below in conjunction with FIGURE 4. Briefly, however, device 106 can be any device that can be worn or otherwise carried by a user and is capable of obtaining authentication data to invoke an authentication process, in this illustrated example, via server 116. As introduced above and as will be detailed below in accordance with some embodiments, authentication data may include manually entered data and/or biometric data acquired or otherwise input by the user to seek authentication and, in some implementations, certain access authorizations.

[00111] As noted above, some embodiments of device 106 will further include one or more physiological sensors and/or proximity detection mechanisms to provide secondary authentication and/or authorization measures to gain and/or maintain authentication/authorization in use.

[00112] Non-limiting examples of suitable wearable authentication devices may include, but are not limited to, a wristband, wristwatch, bracelet, necklace, ring, belt, glasses, clothing, hat, anklet, headband, chest harness, patch, skin probe or earring(s), to name a few, or any other wearable item that is capable of obtaining a biometric signal. The device 106 can also be incorporated into clothing. In another embodiment, the device 106 may comprise more than one biometric and/or physiological sensors, to be used alone and/or in combination, to carry out user authentication and/or liver user presence confirmation. Device 106 may be arranged to communicate with one or more of client computer 102-105 over a network, such as wireless network 108. Further, device 106 may be arranged to communicate with access points, enabling user access to secure locations and secured electronic devices as well as customization of a user experience.

[00113] As will be appreciated by the skilled artisan, some of the features and/or functions noted above with respect to client computers 102-105 may be interchangeably applied to the functions and features of the herein described embodiments of portable device 106. For instance, while client computers are distinctly illustrated herein in one particular embodiment, some embodiments may further or alternatively contemplate portable and/or wearable client computers, as can other embodiments be considered to implement the features and functions of there herein described embodiments.

[00114] Wireless network 108 is configured to couple client computers 102-105 and/or authentication device 106 with network 110. Wireless network 108 may include any of a variety of wireless sub-networks that may further overlay stand-alone ad-hoc networks, and the like, to provide an infrastructure-oriented connection for client computers 102-105 and/or authentication device 106. Such sub-networks may include mesh networks, Bluetooth, Wireless LAN (WLAN) networks, cellular networks, and the like. In one embodiment, the system may include more than one wireless network.

[00115] Wireless network 108 may further include an autonomous system of terminals, gateways, routers, and the like connected by wireless radio links, and the like. These connectors may be configured to move freely and randomly and organize themselves arbitrarily, such that the topology of wireless network 108 may change rapidly.

[00116] Wireless network 108 may further employ a plurality of access technologies including 2nd (2G), 3rd (3G), 4th (4G) 5th (5G) generation radio access for cellular systems, WLAN, Bluetooth, Wireless Router (WR) mesh, and the like. Access technologies such as 2G, 3G, 4G, 5G, and future access networks may enable wide area coverage for mobile computers, such as client computers 102-105, and authentication device 106 with various degrees of mobility. In one non-limiting example, wireless network 108 may enable a radio connection through a radio network access such as Global System for Mobil communication (GSM), General Packet Radio Services (GPRS), Enhanced Data GSM Environment (EDGE), code division multiple access (CDMA), time division multiple access (TDMA), Wideband Code Division Multiple Access (WCDMA), High Speed Downlink Packet Access (HSDPA), Long Term Evolution (LTE), and the like. In essence, wireless network 108 may include virtually any wireless communication mechanism by which information may travel between client computers 102-105, authentication device 106, and another computer, network, a cloud-based network, a cloud instance, or the like.

[00117] Network 110 is configured to couple network computers with other computers, including, authentication server computer 116, client computers 102-105, authentication device 106 through wireless network 108, or the like. Network 110 is enabled to employ any form of computer readable media for communicating information from one electronic device to another. Also, network 110 can include the Internet in addition to local area networks (LANs), wide area networks (WANs), direct connections, such as through a universal serial bus (USB) port, other forms of computer-readable media, or any combination thereof. On an interconnected set of LANs, including those based on differing architectures and protocols, a router acts as a link between LANs, enabling messages to be sent from one to another. In addition, communication links within LANs typically include twisted wire pair or coaxial cable, while communication links between networks may utilize analog telephone lines, full or fractional dedicated digital lines including Tl , T2, T3, and T4, and/or other carrier mechanisms including, for example, E- carriers, Integrated Services Digital Networks (ISDNs), Digital Subscriber Lines (DSLs), wireless links including satellite links, or other communications links known to those skilled in the art. Moreover, communication links may further employ any of a variety of digital signaling technologies, including without limit, for example, DS-0, DS-l, DS-2, DS-3, DS-4, OC-3, OC- 12, OC-48, or the like. Furthermore, remote computers and other related electronic devices could be remotely connected to either LANs or WANs via a modem and temporary telephone link. In one embodiment, network 110 may be configured to transport information of an Internet Protocol (IP).

[00118] Additionally, communication media typically embodies computer readable instructions, data structures, program modules, or other transport mechanism and includes any information delivery media. By way of example, communication media includes wired media such as twisted pair, coaxial cable, fiber optics, wave guides, and other wired media and wireless media such as acoustic, RF, infrared, and other wireless media.

[00119] One embodiment of authentication server computer 116 is described in more detail below in conjunction with FIGURE 3. Briefly, however, authentication server computer 116 includes virtually any network computer capable of performing actions for storing, authenticating, processing of biometric information, users, access points, or the like.

[00120] Although FIGURE 1 illustrates authentication server computer 116 as a single computer, the innovations and/or embodiments are not so limited. For example, one or more functions of authentication server computer 116 may be distributed across one or more distinct network computers. Moreover, authentication server computer 116 is not limited to a particular configuration such as the one shown in FIGURE 1. Thus, in one embodiment, authentication server computer 116 may be implemented using a plurality of network computers and/or client computer. In other embodiments, development computer may operate as a plurality of network computers within a cluster architecture, a peer-to-peer architecture, cloud or virtualized architecture, or the like. Further, in at least one of the various embodiments, authentication server computer 116 may be implemented using one or more cloud instances in one or more cloud networks.

[00121] Described herein, in accordance with some embodiments, is a system, method and device that authenticates a user while confirming that the user being authenticated is a genuine living human being. This system may also, or alternatively, seek to confirm a live user presence during authenticated/authorized usage, confirm proximity of such user to a given access point or associated resource during use (i.e. within a designated authorization zone, area or distance threshold), and/or evaluate other secondary user authorization parameters. In the herein illustrated embodiment, the system is centred around a wearable authentication device that authenticates the wearer based on available authentication data, which may include biometric data, while confirming, based on an acquired physiological signal, that the wearer is in fact a living human being. Some embodiments further allow for confirmation that the same user (i.e. the wearer) is both the source of the physiological signal and the authentication data, for instance, within the context of biometric authentication. In yet other embodiments, such live user presence, proximity and/or other related provisions may not be implemented, for instance, in reduced security environments and/or to reduce or limit complexity of the implemented authentication devices/systems.

[00122] In one embodiment, once authenticated, the wearable authentication device synchronizes with a pre-initialized authorized registration application to authorize the wearable authentication device to wirelessly communicate a preauthenticated user identity to other devices and systems. In another embodiment, once authenticated, the wearable authentication device activates and privately broadcasts the user’s identification to other devices and systems. In yet other embodiments, authentication and/or physiological data is communicated or otherwise transferred to a trusted computation device, such as authentication server 116, for remote processing, thereby reducing a computational load on the wearable device. This enables logical and physical access by the user at one or more access points as a result of a single user authorization.

[00123] In contrast, traditional access systems, including biometric access systems, may be subject to hacking and/or misuse. For example, hackers may lift a fingerprint and create a fingerprint mold, which can be applied to a fingerprint sensor, in order to gain access. Hackers may also take a picture of a fingerprint, and hold it in front of a scanner. Similarly, a user of an authentication device that authenticates once, and then pre-authorizes access for a defined period of time, may be worn by a person without authorization while a person with authorization authenticates the device. Other drawbacks naturally exist, such as maintaining authorized access activations when a user removes the authentication device and/or leaves or moves away from the restricted access area or resource. Such possibilities may be unacceptable to security conscious institutions, resulting in additional layers of security being added, e.g. re-occurring user authentication, or using out of band mechanisms.

[00124] The herein-described embodiments provide a compelling security solution to at least some of these typical drawbacks by significantly reducing if not eliminating concerns about hacking and misuse of an authentication/authorization device. For example, in one illustrative embodiment where a biometric authentication sensor, such as a fingerprint reader, shares a contact point with a complementary physiological sensor, such as an ECG, even if a hacker were to lift a fingerprint, create a fingerprint mold, and attach or otherwise embed the fingerprint mold onto a glove while touching biometric authentication sensor, an analysis of the physiological sensor would determine that the user is not a live, in-the-flesh, human being, and so the authentication device would not authenticate the user. Furthermore, following from the same illustrative example, misuse of the authentication device, e.g. authenticating a device worn by another individual, is also prevented, as the physiological sensor could be configured to fail to take a reading unless the device was both worn and authenticated by the same user (e.g. an electrocardiogram or galvanic skin response does not exist across two people). Accordingly the authentication device would not authenticate, even if the biometric feature (e.g. a fingerprint) is a match. In addition, at least some of the presently described embodiments allow for faster access control since the user does not require authentication every time she needs to access a physical or logical system. As noted above, other features, advantages and benefits of the herein described embodiments, such as live user confirmation during and/or post-authentication, user proximity metrics, and/or other such features and advantages, will be readily apparent to the skilled artisan from the present disclosure.

ILLUSTRATIVE CLIENT COMPUTER

[00125] FIGURE 2 shows one embodiment of client computer 200 that may be included in a system in accordance with at least one of the various embodiments. Client computer 200 may include many more or less components than those shown in FIGURE 2. However, the components shown are sufficient to disclose an illustrative embodiment for practicing different embodiments of the present invention. Client computer 200 may represent, for example, one embodiment of at least one of client computers 102-105 of FIGURE 1.

[00126] As shown in the figure, client computer 200 includes a processor 202 in communication with a mass memory 226 via a bus 234. In some embodiments, processor 202 may include one or more central processing units (CPU). Client computer 200 also includes a power supply 228, one or more network interfaces 236, an audio interface 238, a display 240, a keypad 242, an illuminator 244, a video interface 246, an input/output interface 248, a haptic interface 250, and a global positioning system (GPS) receiver 232.

[00127] Power supply 228 provides power to client computer 200. A rechargeable or non- rechargeable battery may be used to provide power. The power may also be provided by an external power source, such as an alternating current (AC) adapter or a powered docking cradle that supplements and/or recharges a battery, or directly powering the unit.

[00128] Client computer 200 may optionally communicate with a base station (not shown), or directly with another computer. Network interface 236 includes circuitry for coupling client computer 200 to one or more networks, and is constructed for use with one or more communication protocols and technologies including, but not limited to, GSM, CDMA, TDMA, GPRS, EDGE, WCDMA, HSDPA, LTE, user datagram protocol (UDP), transmission control protocol/Internet protocol (TCP/IP), short message service (SMS), WAP, ultra-wide band (UWB), IEEE 802.16 Worldwide Interoperability for Microwave Access (WiMax), session initiated protocol/real-time transport protocol (SIP/RTP), or any of a variety of other wireless communication protocols. Network interface 236 is sometimes known as a transceiver, transceiving device, or network interface card (NIC).

[00129] Audio interface 238 is arranged to produce and receive audio signals such as the sound of a human voice. For example, audio interface 238 may be coupled to a speaker and microphone (not shown) to enable telecommunication with others and/or generate an audio acknowledgement for some action.

[00130] Display 240 may be a liquid crystal display (LCD), gas plasma, light emitting diode (LED), organic LED, AMOLED, PMOLED, or any other type of display used with a computer. Display 240 may also include a touch sensitive screen arranged to receive input from an object such as a stylus or a digit from a human hand.

[00131] Keypad 242 may comprise any input device arranged to receive input from a user. For example, keypad 242 may include a push button numeric dial, or a keyboard. Keypad 242 may also include command buttons that are associated with selecting and sending images.

[00132] Illuminator 244 may provide a status indication and/or provide light. Illuminator 244 may remain active for specific periods of time or in response to events. For example, when illuminator 244 is active, it may backlight the buttons on keypad 242 and stay on while the client computer is powered. Also, illuminator 244 may backlight these buttons in various patterns when particular actions are performed, such as dialing another client computer. Illuminator 244 may also cause light sources positioned within a transparent or translucent case of the client computer to illuminate in response to actions.

[00133] Video interface 246 is arranged to capture video images, such as a still photo, a video segment, an infrared video, or the like. For example, video interface 246 may be coupled to a digital video camera, a web-camera, or the like. Video interface 246 may comprise a lens, an image sensor, and other electronics. Image sensors may include a complementary metal-oxide- semiconductor (CMOS) integrated circuit, charge-coupled device (CCD), or any other integrated circuit for sensing light. [00134] Client computer 200 also comprises input/output interface 248 for communicating with external devices, such as a headset, or other input or output devices not shown in FIGURE 2. Input/output interface 248 can utilize one or more communication technologies, such as USB, infrared, Bluetooth™, ultrasound, Wi-Fi, ultra-wideband, or the like.

[00135] Haptic interface 250 is arranged to provide tactile feedback to a user of the client computer. For example, the haptic interface 250 may be employed to vibrate client computer 200 in a particular way when another user of a computer is calling. In some embodiments, haptic interface 250 may be optional.

[00136] Client computer 200 may also include GPS transceiver 232 to determine the physical coordinates of client computer 200 on the surface of the Earth. GPS transceiver 232, in some embodiments, may be optional. GPS transceiver 232 typically outputs a location as latitude and longitude values. However, GPS transceiver 232 can also employ other geo-positioning mechanisms, including, but not limited to, tri angulation, assisted GPS (AGPS), Enhanced Observed Time Difference (E-OTD), Cell Identifier (Cl), Service Area Identifier (SAI), Enhanced Timing Advance (ETA), Base Station Subsystem (BSS), or the like, to further determine the physical location of client computer 200 on the surface of the Earth. It is understood that under different conditions, GPS transceiver 232 can determine a physical location within millimeters for client computer 200; and in other cases, the determined physical location may be less precise, such as within a meter or significantly greater distances. In one embodiment, however, client computer 200 may through other components, provide other information that may be employed to determine a physical location of the computer, including for example, a Media Access Control (MAC) address, IP address, or the like.

[00137] Mass memory 226 includes a Random Access Memory (RAM) 204, a Read-only Memory (ROM) 222, and other storage means. Mass memory 226 illustrates an example of computer readable storage media (devices) for storage of information such as computer readable instructions, data structures, program modules or other data. Mass memory 226 stores a basic input/output system (BIOS) 224, or the like, for controlling low-level operation of client computer 200. The mass memory also stores an operating system 206 for controlling the operation of client computer 200. It will be appreciated that this component may include a general-purpose operating system such as a version of UNIX, or LINUX™, or a specialized client communication operating system such as Microsoft Corporation’s Windows Mobile™, Apple Corporation’s iOS™, Google Corporation’s Android™, or the like. The operating system may include, or interface with a Java virtual machine module that enables control of hardware components and/or operating system operations via Java application programs.

[00138] Mass memory 226 further includes one or more data storage 208, which can be utilized by client computer 200 to store, among other things, applications 214 and/or other data. For example, data storage 208 may also be employed to store information that describes various capabilities of client computer 200. The information may then be provided to another computer based on any of a variety of events, including being sent as part of a header during a communication, sent upon request, or the like. Data storage 208 may also be employed to store social networking information including address books, buddy lists, aliases, user profile information, user credentials, or the like. Further, data storage 208 may also store messages, web page content, or any of a variety of user generated content.

[00139] At least a portion of the information stored in data storage 208 may also be stored on another component of client computer 200, including, but not limited to processor readable storage media 230, a disk drive or other computer readable storage devices (not shown) within client computer 200. Further, at least a portion of data storage 208 may be used to store user (e.g. authentication, authorization and/or biometric) profile information 210 for one or more users and/or one or more authentication devices.

[00140] Processor readable storage media 230 may include volatile, non-transitive, non- transitory, nonvolatile, removable, and non-removable media implemented in any method or technology for storage of information, such as computer- or processor-readable instructions, data structures, program modules, or other data. Examples of computer readable storage media include RAM, ROM, Electrically Erasable Programmable Read-only Memory (EEPROM), flash memory or other memory technology, Compact Disc Read-only Memory (CD-ROM), digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other physical medium which can be used to store the desired information and which can be accessed by a computer. Processor readable storage media 230 may also be referred to herein as computer readable storage media and/or computer readable storage device.

[00141] Applications 214 may include computer executable instructions which, when executed by client computer 200, transmit, receive, and/or otherwise process network data. Network data may include, but is not limited to, messages (e.g. SMS, Multimedia Message Service (MMS), instant message (IM), email, and/or other messages), audio, video, and enable telecommunication with another user of another client computer. Applications 214 may include, for example, user (e.g. biometric) authentication application 216, enrollment application 218, other applications 220, or the like.

[00142] Other applications 220 may include a web browser. The web browser may include virtually any application configured to receive and display graphics, text, multimedia, messages, and the like, employing virtually any web based language. In one embodiment, the browser application is enabled to employ HDML, WML, WMLScript, JavaScript, SGML, HTML, XML, and the like, to display and send a message. However, any of a variety of other web-based programming languages may be employed. In one embodiment, the browser may enable a user of client computer 200 to communicate with another network computer, such as authentication server computer 116 as shown in FIGURE 1.

[00143] Other applications 220 may additionally include, but are not limited to, calendars, search programs, email clients, IM applications, SMS applications, voice over Internet Protocol (VOIP) applications, contact managers, task managers, transcoders, database programs, word processing programs, software development tools, security applications, spreadsheet programs, games, search programs, and so forth.

ILLUSTRATIVE NETWORK COMPUTER

[00144] FIGURE 3 shows one embodiment of a network computer 300, according to one embodiment of the invention. Network computer 300 may include many more or less components than those shown. The components shown, however, are sufficient to disclose an illustrative embodiment for practicing the invention. Network computer 300 may be configured to operate as a server, client, peer, a host, cloud instance, or any other computer. Network computer 300 may represent, for example authentication server computer 116, and/or other network computers.

[00145] Network computer 300 includes processor 302, processor readable storage media 328, network interface unit 330, an input/output interface 332, hard disk drive 334, video display adapter 336, and memory 326, all in communication with each other via bus 338. In some embodiments, processor 302 may include one or more central processing units.

[00146] As illustrated in FIGURE 3, network computer 300 also can communicate with the Internet, or other communication networks, via network interface unit 330, which is constructed for use with various communication protocols including the TCP/IP protocol. Network interface unit 330 is sometimes known as a transceiver, transceiving device, or network interface card (NIC).

[00147] Network computer 300 also comprises input/output interface 332 for communicating with external devices, such as a keyboard, or other input or output devices not shown in FIGURE 3. Input/output interface 332 can utilize one or more communication technologies, such as USB, infrared, NFC, Bluetooth, or the like.

[00148] Memory 326 generally includes RAM 304, ROM 322 and one or more permanent mass storage devices, such as hard disk drive 334, tape drive, optical drive, and/or floppy disk drive. Memory 326 stores operating system 306 for controlling the operation of network computer 300. Any general-purpose operating system may be employed. Basic input/output system (BIOS) 324 is also provided for controlling the low-level operation of network computer 300.

[00149] Although illustrated separately, memory 326 may include processor readable storage media 328. Processor readable storage media 328 may be referred to and/or include computer readable media, computer readable storage media, and/or processor readable storage device. Processor readable storage media 328 may include volatile, nonvolatile, non-transitory, non transitive, removable, and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. Examples of processor readable storage media include RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other media which can be used to store the desired information and which can be accessed by a computer.

[00150] Memory 326 further includes one or more data storage 308, which can be utilized by network computer 300 to store, among other things, applications 314 and/or other data. For example, data storage 308 may also be employed to store information that describes various capabilities of network computer 300. The information may then be provided to another computer based on any of a variety of events, including being sent as part of a header during a communication, sent upon request, or the like. Data storage 308 may also be employed to store messages, web page content, or the like. At least a portion of the information may also be stored on another component of network computer 300, including, but not limited to processor readable storage media 328, hard disk drive 334, or other computer readable storage medias (not shown) within network computer 300.

[00151] Data storage 308 may include a database, text, spreadsheet, folder, file, or the like, that may be configured to maintain and store user account identifiers, user profiles, email addresses, IM addresses, and/or other network addresses; or the like. Data storage 308 may further include program code, data, algorithms, and the like, for use by a processor, such as processor 302 to execute and perform actions. In one embodiment, at least some of data store 308 might also be stored on another component of network computer 300, including, but not limited to processor- readable storage media 328, hard disk drive 334, or the like.

[00152] Data storage 308 may include user (e.g. authentication, authorization and/or biometric) profile information 312. In at least one of the various embodiments, user profile information 312 may include information, such as, one or more files, that include authentication (e.g. biometric) data for one or more users, or the like, used for authentications of wearable authentication devices. Also, in at least one of the various embodiments, data storage 308 may include authentication information 313 that may include information about users, access points, access control lists, or the like.

[00153] Applications 314 may include computer executable instructions, which may be loaded into mass memory and run on operating system 306. Examples of application programs may include transcoders, schedulers, calendars, database programs, word processing programs, Hypertext Transfer Protocol (HTTP) programs, customizable user interface programs, IPSec applications, encryption programs, security programs, SMS message servers, GM message servers, email servers, account managers, and so forth. Applications 314 may also include, enrollment application 320 for enrolling and/or activating authentication devices. Application mat also include registration application 321 for authenticating users by employing biometric information, authentication devices, additional conditions, or the like.

[00154] Website server 318 may represent any of a variety of information and services that are configured to provide content, including messages, over a network to another computer. Thus, website server 318 can include, for example, a web server, a File Transfer Protocol (FTP) server, a database server, a content server, email server, or the like. Website server 318 may provide the content including messages over the network using any of a variety of formats including, but not limited to WAP, HDML, WML, SGML, HTML, XML, Compact HTML (cHTML), Extensible HTML (xHTML), or the like.

ILLUSTRATIVE AUTHENTICATION DEVICE

[00155] In at least one of the various embodiments, a wearable authentication device, such as, authentication device 106 may be any device that may be employed, typically, worn or held, by a user and is capable of receiving authentication data as input, such as for example, offering a user input interface for the manual input of authentication data (username, password, code, PIN, etc.) and/or being operable to obtain a biometric signal or like input. Non-limiting examples of wearable authentication devices are a wristband, wristwatch, bracelet, necklace, ring, belt, glasses, clothing, hat, anklet, headband, chest harness or earring(s), or, in the context of a biometric device, any other item that is capable of obtaining a biometric signal. The wearable authentication device can also be incorporated into clothing. In another embodiment, the wearable authentication device may comprise multiple input interfaces so to access distinct authentication inputs (e.g. combined manual and biometric inputs, multiple biometric inputs, etc.).

[00156] While wearable authentication devices are contemplated in the illustrated embodiments, for at least one of the various embodiments, authentication devices within the scope of these innovations are not limited exclusively to wearable devices. In at least one of the various embodiments, authentication devices in non-wearable form factors may be considered to be within the scope of the innovations described herein. For example, a fixed authentication device embedded in a chair, desk, handle bar, or the like, or combination thereof. Likewise, authentication devices that may be held rather than worn are also contemplated to be within the scope of the innovations described herein. However, in the interest of clarity and brevity most of the discussion and examples presented herein are described in terms of wearable authentication devices. One of ordinary skill in the art will appreciate the other authentication device form factors are within the scope of these innovations and are envisaged.

[00157] In at least one of the various embodiments, a user of a wearable authentication device may be authenticated with one or more biometric technologies or sensors that may capture biometric signals and/or data that represent biometric features that may be employed to uniquely identify the user. The uniqueness of a biometric feature may be directly related to the underlying inter-individual differences in a population. Some non-limiting examples of biometric data that may be employed to uniquely identify a user are gait, heart rate, galvanic skin response, temperature, fingerprint, voice or voiceprint, body electrical characteristic, body thermal characteristic, iris pattern, vein pattern, eye vein pattern, facial or other anatomical structure, electrocardiogram, photoplethysmogram, electromyogram, electroencephalogram, transient otoacoustic emissions, phonocardiogram, DNA, one or more chemical markers, one or more biochemical markers, skin-color variation or discoloration, or perspiration. In at least one of the various embodiments, authentication is performed by the authentication device. However, additionally or alternatively, authentication may be performed by an authorized registration application.

[00158] In at least one of the various embodiments, a physiological feature is also captured, not to identify a user (although this is also contemplated, with various degrees of weight given based on the uniqueness of the physiological signal for use as a secondary biometric feature type), but to determine whether the authentication data was received from a genuine living human being, and/or to determine whether the genuine living human from whom the authentication data was captured is wearing the authentication device. [00159] For example, in some embodiments, an authentication process invoked by or via the device will be satisfied upon confirming authentication of the input authentication data and concurrent live user presence via the device’s physiological feature. Such liver user presence confirmation may further or alternatively persist during use to confirm live user presence in maintaining user authorizations and otherwise revoke such authorizations if the physiological input is lost (e.g. if the device is removed from the user, or, vice-versa).

[00160] In some embodiments, as noted above, the user authentication interface and physiological sensor will be configured so to concurrently with the user during authentication, for example, where authentication data input requires user contact (e.g. fingerprint and/or data input) and where such contact invariably results in user contact with a complementary physiological sensor (e.g. probe, interface and/or contact thereof). It will, however, be appreciated that such concurrent user contact need not necessarily proceed through a common interface but rather, may require authentication and physiological interfaces to be closely disposed or arranged to facilitate concurrent or sequential contact. In some embodiments, a physiological signal may further require two concurrent physical contact points by a same genuine user, for example in the context of a ECG, which can be achieved in some embodiments, through a finger input interface and wrist interface in a wristband or likewise configured device.

[00161] For example, because an electrocardiogram requires two points of contact across the heart to be detected, an electrocardiogram (ECG) is used in at least one of the various embodiments to validate that a fingerprint (e.g. authenticating biometric data) is being captured by a wearer of an authentication device (e.g. as opposed to a fingerprint from a person standing next to the wearer). The ECG may also be used to defeat a replay attack by validating that the fingerprint is captured from a genuine living person, as opposed to a fingerprint mold intended to fool the authentication device. Both validations are accomplished by positioning one of the ECG sensors proximate to (e.g. adjacent to, on top of, around the bezel of, as part of, etc.) the fingerprint sensor, such that, in one embodiment, both biometric and physiological features are captured concurrently, from the same finger. Additionally or alternatively, authentication and physiological features may be captured sequentially, such that within a defined period of time chosen to prevent another person from substituting their finger, or in parallel. Additionally or alternatively, authentication and physiological features may be captured within a defined period of time such that the wearable authentication device has not detected the removal of the finger between captures. It will be appreciated that while biometric authentication is considered in the above-noted examples, other authentication mechanisms may also be considered to concurrently or sequentially benefit from physiological user presence confirmation. For instance, a user input interface for receiving as input manually entered authentication data (e.g. touch sensitive screen or interface) may double as or be juxtaposed to a physiological probe so to provide a similar effect.

[00162] Following from the above example, in one or more of the various embodiments, a second ECG sensor is positioned so as to contact the wrist of the wearer. In this way, an ECG signal is enabled to travel from the heart, through one arm, through one of the ECG sensors, out the other ECG sensor, through the other arm, and back to the heart. Without this electrical connection - e.g. if another person is providing the fingerprint or manual input, such that the ECG does not flow through the fmgerpath of the user touching the authentication interface - the authentication device will determine that the authentication data is not being provided by the wearer of the authentication device. Similarly, if the electrical connection is distorted or in any way modified by the use of a fingerprint mold, for example, the ECG sensor will determine that the fingerprint is not being provided by the wearer of the authentication device.

[00163] Throughout this disclosure, and particularly with reference to the illustrative example presented above, for clarity and brevity, authentication features are predominantly discussed as biometric features, and more predominantly fingerprints, and physiological features are predominantly discussed as ECGs, but other types of authentication, and particularly biometric features may be considered, such as but not limited to finger-veins and galvanic skin responses, to name a few. For instance, in the context of the illustrative example provided above, biometric authentication feature may be any feature that is captured based on contact with the user, whereas a physiological feature may be any feature that can be captured, at least in part, using the same body part as is used to capture the biometric feature, and which can determine if the wearable authentication device is worn by the owner of that same body part. While fingerprint and ECG are discussed in greater detail below as options for providing authentication and liver user presence confirmation, such examples should not be considered to limit the general scope and nature of the present disclosure, but rather, merely serve as one example consistent with various embodiments of the present disclosure.

[00164] In at least one of the various embodiments, the wearable authentication device may include an onboard power source to enable the authentication device to perform the required functions, such as obtaining the authentication and/or physiological signals, transmitting and receiving these and related control signals, and in some embodiments, maintaining a detector for detecting the removal of the wearable authentication device, for example, such as an electronic continuity detector. Any power source known to the skilled person is acceptable, with non limiting examples being battery, photovoltaic, kinetic, or microgenerator, thermal, piezo-electric generator, inductive charging, and wireless power transfer.

[00165] The wearable authentication device includes one or more radios/transceivers for transmitting and receiving communications. The one or more radios/transceivers may transmit and receive communications from systems installed at access points, e.g. transmitting authorization to gain access to one or more access points.

[00166] In one example, the wearable authentication device may incorporate a wireless connectivity module such as Bluetooth 4.0 Low Energy (BLE), Near-Field Communications (NFC), Wi-Fi, or other wireless technology capable of transmitting and receiving functions. In one embodiment, a BLE radio may be used because it may consume significantly less power when communicating in short bursts. In this way, a battery or other power source used to power the wearable authentication device may have an extended life, in some cases on the order of multiple weeks.

[00167] In at least one of the various embodiments, the radios and/or transceivers may be used to transmit data during initialization and authentication, identify the user, and to establish a unique user profile associated with the user and the wearable authentication device. The same or other the radios and/or transceivers included in a wearable authentication device may also transmit and receive motion data, time of flight, signal strength, and proximity data in order to be aware of local access points. In at least one of the various embodiments, the radios and/or transceivers may also be used to receive a positive authentication message that puts the wearable device into an authenticated state, as well as to prompt the user of notification events. [00168] In at least one of the various embodiments, the wearable authentication device may be arranged to include proximity sensors for sensing an access point (physical or logical), or an authorized application. In one embodiments, a feature of the Bluetooth 4.0 standard which may be used by radios and/or transceivers included in the authentication device. Also, in at least one of the various embodiments, the wearable authentication device may be configured to transmit a beacon signal along with the transmitting signal strength. Accordingly, the receiving device may use this information, along with the received signal strength, to estimate the proximity of the wearable authentication device. Non-limiting exemplary uses of the proximity data may include: only unlocking a device when the proximity is within a specified range, i.e., a door lock is only unlocked when the authorized user is within a certain distance, such as 50 cm; a“digital leash” which warns the user when a paired device is no longer within a certain proximity; revoke authorized access to a given resource upon the device moving beyond a designated authorization distance, zone or area, or the like.

[00169] In at least one of the various embodiments, in addition to being used to confirm that the person providing the fingerprint is wearing the wearable authentication device, as described above in one example, the wearable authentication device may utilize ECG biometric authentication as a secondary, confirmatory form of biometric authentication in addition to the primary authentication mechanism, e.g. fingerprint, finger-vein, etc. In at least one of the various embodiments, ECG biometric authentication technology may use unique features of a user’s electrocardiogram (ECG) to create a highly personalized biometric signature for that individual. Like other biometric characteristics, the ECG is universal, unique for every individual, and permanent over time. An ECG may be recorded for every living user, with no exclusion criteria. In addition, studies have shown that even though aspects of the ECG signal may get distorted with time and aging, the overall diacritical characteristics are observable. In the case of ECG, the uniqueness of the biometric feature is a result of several parameters of the cardiac function that control the waveforms. Electrophysiological variations of the myocardium such as the heart mass orientation and exact position, or the timing of depolarization and repolarization add to the idiosyncratic properties of every person's ECG waveforms.

[00170] In at least one of the various embodiments, one or more well-known ECG biometrics algorithms may analyze the overall pattern of the signal waveform rather than specific characteristics of the heart-beats and are therefore referred to as“fiducial -independent”. One of the core algorithms is referred to as the AC/LDA (Autocorrelation / Linear Discriminant Analysis) and has become a standard for the comparison of fiducial dependent and independent algorithms.

[00171] In at least one of the various embodiments, a number of mechanisms for initiation of ECG capture and authentication may be used. For example, the authentication device may be arranged to automatically sense when a top electrode is touched, such as using an embedded “lead on/off’ detection system, optionally with notification of the lead status to the user. Additionally or alternatively, ECG capture is initiated in response to capturing primary authentication data , such as a fingerprint.

[00172] In at least one of the various embodiments, when biometric authentication is initiated through fingerprint, one or more images of a finger are captured and stored in a biometric profile 210. In one or more of the various embodiments, when authentication is performed by the registration application, the one or more images of the finger are transmitted to the registration application for processing and stored in biometric profile information 312. Similarly, once ECG capture and liveness validation are initiated, the single-channel filtered ECG data may be processed by the wearable authentication device and/or transmitted to the registration application for processing. In another embodiment, the images of the finger and ECG capture and liveness validation are processed and stored on the device.

[00173] Losing a function within the registration application, biometric/user enrollment may be initiated, wherein the user touches the wearable authentication device, and then a biometric feature (e.g. a fingerprint, finger-vein) and an ECG are captured and processed by the wearable authentication device, and/or are transmitted to the registration application. This process may take as little as about 1 second and up to a few seconds, a minute, or a few minutes depending on the level of interaction with the user with the wearable authentication device and the type of authentication signals being obtained.

[00174] In at least one of the various embodiments, the user (e.g. biometric) profile may be created in a number of different ways. In one way, the biometric signal may be transmitted to a cloud service, where the processing is performed on the cloud servers to generate the biometric profile. Alternatively, the biometric signal may be processed on the registration application to generate the biometric profile.

[00175] In at least one of the various embodiments, once the biometric profile is created, it may be associated with a user and stored within a cloud service. Also, in at least one of the various embodiments, the biometric profile may be transmitted to the registration application or stored locally just on the device. In at least one of the various embodiments, the biometric profile may be stored on a wearable authentication device that is arranged to include the processing power required to authenticate the user. In another alternative, the processing for the creation of the biometric profile may be performed on the registration application or in the wearable authentication device itself.

[00176] In at least one of the various embodiments, the wearable authentication device may include one or more of: a CPU or system on a chip (SOC) which acts as the controller, a wireless transceiver, an antenna, audible and haptic feedback, and a user interface. The controller may be operative for controlling the overall operation of the wearable authentication device. The controller functionality may be implemented within, for example, one or more digital processing devices within the wearable authentication device. The wireless transceiver is operative for supporting wireless communication between the wearable authentication device and one or more other wireless entities including the AAD and wireless access points. In one embodiment, separate transceivers are provided within the wearable authentication device to support wireless communication between the wearable authentication device and other systems or devices. The wireless transceiver may also be coupled to one or more antennas to facilitate the transmission and reception of wireless signals. Any type of antenna(s) may be used including, for example, a dipole antenna, a patch antenna, a helical antenna, an antenna array, trace antenna, and/or others, including combinations of the above.

[00177] In at least one of the various embodiments, a user interface may be operative for providing an interface between a user and the wearable authentication device. The user interface of a authentication device may include structures such as, for example, a keyboard, a liquid crystal display (LCD), light emitting diode (LED), active-matrix organic light-emitting diode (AMOLED), passive-matrix organic light-emitting diode (PMOLED), capacitive touch screen, a speaker, a microphone, mouse, stylus, one or more physical or electronic buttons, and/or any other form of device or structure that enables a user to input information or commands to the wearable authentication device or receive information or a notification from the device.

[00178] In one embodiment, the controller may first determine if the wearable authentication device (and, therefore, the user) is within a predetermined distance or proximity to an access point. In one example, if the wearable authentication device is within proximity of an access point and the wearable authentication device transmits a control signal to the access point indicating that the user has been authenticated, the receiver at the access point may automatically enable access to the user. If the wearable authentication device later goes outside the predetermined distance from the access point, the access point may be locked. In one example, if the access point is a security protected desktop computer and the preauthorized user wearing their preauthorized wearable authentication device temporarily leaves her desk to go to lunch, the computer will automatically lock so that no one else may use it in the user's absence. Similarly, if the access point is a smartphone and the smartphone is inadvertently left somewhere by the user, or is stolen, the smartphone will automatically lock up and thus be unusable by an unauthorized party in possession thereof. When the user wearing the preauthorized wearable authentication device again comes within a predetermined distance of the smartphone, the smartphone will simply be unlocked without having to repeat the automatic log in procedure, assuming that the wearable authentication device remains preauthorized.

[00179] In at least one of the various embodiments, the wearable authentication device, no matter which type of authentication data is used for authentication, should be able to maintain contact with the user (e.g. via onboard physiological sensor) such that in the case that the wearable device is removed from the user, the wearable device will require re-initialization prior to authorizing access control. The purpose of maintaining contact of the wearable authentication device with the user is to ensure that an authorized authentication device cannot be transferred to a different user without requiring reauthorization. Accordingly, although skin or body contact is not required at all times while the wearable device is in its authenticated state, the wearable device should be on the user in such a way that removal of the wearable will put the wearable device back to its unauthenticated state. In the unauthenticated state, the wearable authentication device is not enabled to transmit a control signal to an access point. The security of at least some of the herein described embodiments depends on ensuring that removal of the wearable device from the user is reliably detected. Accordingly, the wearable authentication device may be arranged such that removal from the user’s body may be easily detected.

[00180] In one particular embodiment, as a complement to or in the absence of a physiological sensor, the wearable device may comprise a sensored adjustable and/or openable clasp to assist the user with putting on and removing the wearable device while monitoring removal of the device form the user in authenticated use. For example, removal of the wearable device may be sensed by the wearable authentication device, for example, by opening the clasp, or again by cutting the band, or generally severing an electrical conduit such as an electronic continuity detector. One exemplary electronic continuity detector that may be used to detect device removal comprises a simple circuit within the wearable device that runs around the entire wrist and is broken when the clasp is opened or the band is cut. Other types of device removal detection may be used, for example, including disruption in skin contact detection by way of conductivity, heat flux, galvanic skin response or motion, or periodic or continuous biometric signal detection. Yet other non-limiting examples of device removal detection embodiments may include pulse detection, skin temperature detection, ambient temperature detection, blood flow detection, pressure detection, ambient light detection, electromagnetic field detection, respiration detection, heart rate detection, electrocardiogram detection, photoplethysmogram detection, electromyogram detection, electroencephalogram detection, near infra-red detection, skin-color detection, close magnetic contact detection, and mechanical switch detection.

[00181] In at least one of the various embodiments, additional sensors may be incorporated into the device to obtain additional biometric or environmental readings. Some non-limiting examples of an additional sensor are motion sensor, proximity sensor, barometric sensor, pressure sensor, thermometer, microphone, near infrared sensor, light sensor, GPS sensor, capacitive sensor, gyroscope, manometer, camera, humidity sensor, hall sensor, galvanic skin sensor, photoplethysmogram sensor, electroencephalogram sensor, electromyogram sensor, blood flow sensor, bioimpedance sensor, otoacoustic emission sensor, optical sensor, altimeter sensor or UV light sensor. These additional sensors may provide one or more contextual signals such as the location of the wearable device and/or proximity to trusted environments. [00182] In at least one of the various embodiments, a wearable authentication device may comprise one or more motion sensors that may be used for a variety of purposes, including but not limited to, user input (e.g., tap detection), activity tracking (e.g., pedometer, sports, fitness, etc.), gesture recognition, or the like. In one embodiment, a wearable authentication device may incorporate a six-axis motion sensor using an integrated accelerometer and gyroscope or a 9-axis motion sensor using integrated accelerometer, gyroscope, and magnetometer application-specific integrated circuit (ASIC). Embedded motion sensors may also be utilized for simple gesture recognition to indicate user intent, such as for example gestures may be used to distinguish between user intents to unlocking different locks on an automobile, such as, the driver door, passenger door, the trunk, or the like. In this way, computational requirements on the wearable authentication device may be kept at a minimum.

[00183] In at least one of the various embodiments, the wearable authentication device may be arranged to include notification devices and procedures to alert the user of one or more notification events. Some non-limiting examples of these include one or more notification LEDs and/or a vibration motor. A notification event may be an event detected by the wearable authentication device that the user should be aware of. These events may include: when the wearable device has been put into an authenticated state; when the wearable authentication device is communicating with other devices; when the wearable device is sensing motion; and/or when some event has occurred on a paired device, such as receiving an email or text. A paired device may be any device or system that interacts with the wearable authentication device.

[00184] In at least one of the various embodiments, the wearable device may also comprise other components such as a display screen, input devices (such as, for example, button, switch, keypad or touchscreen), timepiece/timers, tracking or global positioning (GPS) detector activity, or physiology or emotion tracking. In at least one of the various embodiments, authentication device may be arranged to indicate proximity to other devices. In at least one of the various embodiments, wearable authentication devices may be arranged to include additional electronics for storing data for access and use not related to the presently described security system. [00185] FIGURE 4A and FIGURE 4B are schematic physical and logical diagrams, respectively, of a wearable user authentication / access authorization device, in accordance with at least one of the various embodiments.

[00186] FIGURE 4A illustrates authentication device 400 that is arranged as a wearable wristband/bracelet. In at least one of the various embodiments, wristband 402 may be arranged to include various hardware components, probes, sensors, and software for capturing authentication (e.g. biometric) and/or physiological signals from its wearer; making a determination whether authentication data was captured from a live person wearing the wearable wristband/bracelet based on a captured physiological feature; communication with a registration application or access point; authentication of a wearer, or the like, as discussed above. Further, in at least one of the various embodiments, wristband 402 may include an adjustable clasp mechanism, such as, clasp 404, for detecting if a wearer removes wristband 402 from his or her wrist. For example, in at least one of the various embodiments, if an authentication device detects that the clasp is opened, it may automatically de-authenticate itself.

[00187] FIGURE 4B schematically illustrates some of the various components that may be comprised in an authentication device in accordance with at least one of the various embodiments. In at least one of the various embodiments, wristband 402 may include one or more presence sensors, such as, presence sensor 406, presence sensors may be arranged to determine if authentication device 402 is in the presence of a wearer, registration application, access point, or the like, or combination thereof. Also, in at least one of the various embodiments, authentication device 402 may include one or more radios or transceivers, such as, high bandwidth radio 410 and low bandwidth radio 412. These radios may enable a authentication device to communicate with other computer or devices, such as, access points, authentication servers, or the like, or combination thereof.

[00188] In at least one of the various embodiments, clasp sensor 408, may be arranged to determine if the clasp, or other securing mechanism, is opened or closed. In at least one of the various embodiments, an opened clasp may indicate that the authentication device may be separated from its authenticated user. Accordingly, for example, the authentication device may be arranged to automatically reset or otherwise de-authenticate itself if clasp sensor 408 indicates that the authentication device is removed from the wearer. Further, removal of the wearable device may be sensed by the wearable authentication device for example, by opening the clasp, cutting the band, or generally severing an electrical conduit such as an electronic continuity detector. One exemplary electronic continuity detector that may be used to detect device removal comprises of a simple circuit within the wearable device that runs around the entire wrist and is broken when the clasp is opened or the band is cut. Other types of device removal detection may be used, for example, including disruption in physiological signal such as skin contact detection by way of conductivity, heat flux, galvanic skin response or motion, or periodic or continuous biometric signal detection. Yet other non-limiting examples of device removal detection embodiments include physiological tests such as pulse detection, skin temperature detection, blood flow detection, pressure detection, electromagnetic field detection, respiration detection, heart rate detection, electrocardiogram detection, photoplethysmogram detection, electromyogram detection, electroencephalogram detection, near infra-red detection, skin-color detection, close magnetic contact detection, and/or non-physiological tests such as mechanical switch detection, ambient temperature detection, ambient light detection, etc..

[00189] In at least one of the various embodiments, as discussed above, authentication device 402 may be arranged to communicate with various devices, such as, access points, authentication servers and cloud services, or the like, or combination thereof. In at least one of the various embodiments, high bandwidth radio 410 may include radios for communication using high bandwidth mechanisms such as Wi-Fi, or the like. Low bandwidth radio 412 may represent components for communicating using low-power, shorter range radio systems such as, Bluetooth, Bluetooth Low Energy, NFC, RFID, or the like, or combination thereof. Further, in at least one of the various embodiments, these radios may be coupled to one or more antennas to facilitate the transmission and reception of wireless signals. Any type of antenna(s) may be used including, for example, a dipole antenna, a patch antenna, a helical antenna, an antenna array, trace antenna, and/or others, including combinations of the above.

[00190] In at least one of the various embodiments, RAM 414 may be non-volatile and/or volatile random access memory for storing information for operation of authentication device 402. In at least one of the various embodiments, all or portions of the contents of RAM 414 may be erased if the authentication device is removed of its wearer. Likewise, in at least one of the various embodiments, ROM 416 may contain data and/or instructions for the operation of the authentication device. In at least one of the various embodiments, ROM 416 may be“flashable,” enabling it to be updated with system updates provided by a registration application or a biometric server service.

[00191] In at least one of the various embodiments, secure memory 418 may be a hardened tamper resistant memory device that is resistant to physical tampering. In at least one of the various embodiments, sensitive information such as cryptographic keys, biometric profiles derived from captured biometric features, and the like may be stored in secure memory 418.

[00192] In at least one of the various embodiments, authentication device 402 may be arranged to include CPU or System-on-a-Chip (SOC) for controller the operations of the authentication device. The performance capability of CPU/SOC 420 may vary depending on how much processing authentication device 402 is intended to perform.

[00193] In at least one of the various embodiments, GPS transceiver 422 may represent the radios, hardware, and instructions (e.g., software) for receiving geo-location. GPS transceiver 422 may determine the physical coordinates of authentication device 402 on the surface of the Earth. GPS transceiver 422 typically outputs a location as latitude and longitude values. However, GPS transceiver 422 may also employ other geo-positioning mechanisms, including, but not limited to, triangulation, assisted GPS (AGPS), Enhanced Observed Time Difference (E- OTD), Cell Identifier (Cl), Service Area Identifier (SAI), Enhanced Timing Advance (ETA), Base Station Subsystem (BSS), or the like, to further determine the physical location of authentication device 402 on the surface of the Earth. It is understood that under different conditions, GPS transceiver 422 may determine a physical location within millimeters for authentication device 402; and in other cases, the determined physical location may be less precise, such as within a meter or significantly greater distances.

[00194] In at least one of the various embodiments, additional sensors 424 represent one or more sensor systems including, additional sensors such as accelerometers, motion sensors, proximity sensors, barometric sensors, pressure sensors, thermometers, microphones, near infrared sensors, light sensors, capacitive sensors, gyroscopes, manometers, cameras, humidity sensors, hall sensors, galvanic skin sensors, photoplethysmogram sensors, electroencephalogram sensors, electromyogram sensors, blood flow sensors, bioimpedance sensors, otoacoustic emission sensors, optical sensors, altimeter sensors, UV light sensors, or the like.

[00195] In at least one of the various embodiments, as discussed above, authentication device 402 may be arranged to include a variety of biometric and/or physiological sensors and probes for detecting, sensing, and/or sampling a variety of biometric and/or physiological signals from the wearer. ECG sensors 426 represent one or more sensors for detecting, sensing, and/or sampling ECG information as described above. Fingerprint sensor 427, depicted adjacent to ECG sensor 426 to indicate a physical proximity on the physical device, represents a sensor for scanning fingerprints, as described above. Likewise, biometric sensors 428 represent one or more sensors for detecting, sensing, and/or sampling other biometric information as described above. In some embodiments, sensors may be comprised of one or more probes, contacts, or the like. In some embodiments, one or more probes or contacts, represented by probes 436, may be used for to collect signals for more than one sensor.

[00196] In at least one of the various embodiments, ECG sensor 426 may be adjacent to, surrounding, internal to, integrated with, and/or otherwise close enough to fingerprint sensor 427 that a user may easily place a finger on probes for both sensors at the same time. In another of the various embodiments, probes for ECG sensor 426 may be located next to / integrated with one or more probes for fingerprint sensor 427 such that it is difficult if not impossible to selectively activate one sensor but not the other, and such that it is difficult if not impossible for two fingers, each from different people, to individually be captured by the different sensors.

[00197] In one or more of the various embodiments, one or more probes or other components may be shared by two or more sensors. For example, in some embodiments, a sensor for detecting body temperature, heart rate, ECGs, or the like, may be arranged to share the same probe.

[00198] In at least one of the various embodiments, biometric sensor 402 may be arranged to include a variety of components for interacting with the wearer. Vibration motor 430 may enable the authentication device to vibrate to notify the wearer of various changes in state, or the like (as discussed above). Likewise, user interface 432 may comprise elements that enable a user to provide input to the authentication device or for receiving output from the authentication device as discussed above, including biometric data that may be employed to uniquely identify a user, such as gait, heart rate, galvanic skin response, temperature, fingerprint, voice or voiceprint, body electrical characteristic, body thermal characteristic, iris pattern, vein pattern, eye vein pattern, facial or other anatomical structure, electrocardiogram, photoplethysmogram, electromyogram, electroencephalogram, transient otoacoustic emissions, phonocardiogram, DNA, one or more chemical markers, one or more biochemical markers, skin-color variation or discolouration, perspiration, or the like. Also, in at least one of the various embodiments, user interface 432 may include a key pad, buttons, LED’s microphone (for voice commands), or the like, or combination thereof.

[00199] Also, in at least one of the various embodiments, power source 434 may be arranged to provide power of operating authentication device 402. Power source 434 may include various batteries, storage cells, power adapters, chargers, or the like, as well as, power sources such as, photovoltaic, kinetic, or microgenerator, thermal, piezo-electric generator, inductive charging, and wireless power transfer or the like, or combination thereof.

[00200] One or ordinary skill in the art will appreciate that authentication device 402 is a non limiting example of an authentication device that is in accordance at least one of the various embodiments. Even though authentication device 402 represents a wristband wearable authentication device, authentication devices within the scope of these innovation may be arranged in other form factors, such as those discussed above.

[00201] Further, in at least one of the various embodiments, some or all of components described in FIGURE 4B and/or elsewhere in this paper may be implemented in hardware, including, dedicated (custom) hardware, ASICs, FPGAs, or the like. Likewise, these components or portions thereof may be implemented in whole or in part using software.

[00202] FIGURE 5A illustrates a logical schematic of authentication device 500 showing sensors for fingerprint scanning and ECG signal capturing in accordance with at least one of the various embodiments. In at least one of the various embodiments, authentication device section 502 represents a side cross-section that highlights one arrangement for capturing fingerprints and ECG signals. In at least one of the various embodiments, fingerprint sensors in a authentication device may be arranged to receive signals from one or more probes, such as probe 504. Probe 504 may be a camera, scanner, or other device or component capable of capturing an signals that correspond to a fingerprint. ECG sensors may be arranged to uses probes, such as probe 506 and probe 508 that may be probe contacts (e.g., electrodes, conductive contacts, or the like) arranged to capture ECG signals upon direct contact of a user’s skin. In at least one of the various embodiments, probe 504 and probe 506 are arranged to enable the user to touch with a finger of his or her opposite hand (the hand not wearing the authentication device). In at least one of the various embodiments, probe 508 is arranged to contact the skin of the user’s wrist that is wearing the authentication device. Accordingly, a circuit may be made from one hand to the other, enabling ECG signals to be captured through the probes and provided to one or more sensors, concurrent with a fingerprint of the same finger being captured. Note, one of ordinary skill in the art will appreciate that other probes or sensor arrangements may be employed. Further, more or fewer probes or sensors may be arranged in different positions - however, the arrangement disclosed in FIGURE 5B is at least sufficient for practicing the innovations described herein.

[00203] FIGETRE 5B illustrates a logical schematic of authentication device 510 showing another arrangement of probes for fingerprint scanning and ECG signal capturing in accordance with at least one of the various embodiments. In at least one of the various embodiments, authentication device section 512 represents a side cross-section that highlights one arrangement for capturing fingerprints and ECG signals. In at least one of the various embodiments, a fingerprint sensor, such as, fingerprint sensor 427, may be arranged to receive signals from one or more probes, such as probe 514 which may be a camera, scanner, or other device capable of capturing an image of a fingerprint. Probe 516 represents a contact (e.g., conductive metal ring or bezel) arranged to capture ECG signals upon direct contact of a user’s skin. In some embodiments, probe 516 may be positioned to contact a user’s finger while that finger is in contact with probe 514.

[00204] In at least one of the various embodiments, because probe 514 and probe 516 are arranged to enable the user to simultaneously contact both probes with the same finger of his or her opposite hand (the hand not wearing the authentication device). Accordingly, while the user’s fingertip is in contact with both probes at the same time, probe 514 captures the user’s fingerprint information and probe 516 acts as an conductive contact. [00205] In at least one of the various embodiments, probe 518 is arranged to contact the skin of the user’s wrist that is wearing the authentication device. Accordingly, a circuit may be made from one hand to the other, enabling ECG signals to be captured through the probes and provided to an ECG sensor, such as, ECG sensor 426, concurrent with a fingerprint of the same finger being captured. Note, one of ordinary skill in the art will appreciate that other sensor arrangements may be employed. Further, more or fewer sensors may be arranged in different positions - however, the arrangement disclosed in FIGURE 5B is at least sufficient for practicing the innovations described herein.

[00206] FIGETRE 5C illustrates a logical schematic of authentication device 510 showing a top view of the arrangement of sensors for fingerprint scanning and ECG signal capturing in accordance with at least one of the various embodiments. In at least one of the various embodiments, authentication device section 512 represents a top view of device 510 that highlights one arrangement for capturing fingerprints and ECG signals. In at least one of the various embodiments, a fingerprint sensor, such as, fingerprint sensor 427, may be arranged to receive signals from one or more probes, such as, probe 514. The one or more probes may include a camera, scanner, or other device capable of capturing an image of a fingerprint. Probe 516 represents a conductive contact (e.g., conductive metal ring or bezel) arranged to capture ECG signals upon direct contact of a user’s skin. In some embodiments, probe 516 may be positioned to contact a user’s finger while that finger is in contact with probe 514.

[00207] In at least one of the various embodiments, because probe 514 and probe 516 are arranged to enable the user to simultaneously contact both probes with the same finger of his or her opposite hand (the hand not wearing the authentication device). Accordingly, while the user’s fingertip is in contact with both probes at the same time, probe 514 captures the user’s fingerprint information and probe 516 acts as an conductive contact.

[00208] In at least one of the various embodiments, probe 518 (not visible in FIGURE 5C) is arranged to contact the skin of the user’s wrist that is wearing the authentication device. Accordingly, a circuit may be made from one hand to the other, enabling ECG signals to be captured through the probes, concurrent with a fingerprint of the same finger being captured. Note, one of ordinary skill in the art will appreciate that other sensor or probe arrangements may be employed. Further, more or fewer probes or sensors may be arranged in different positions - however, the arrangement disclosed in FIGURE 5C is at least sufficient for practicing the innovations described herein.

[00209] Again, one or ordinary skill in the art will appreciate that authentication devices 502/512 are non-limiting examples of authentication devices that are in accordance at least some of the various embodiments. Even though authentication devices 502/512 represent wristband wearable authentication devices, authentication devices within the scope of these innovation may be arranged in other form factors, such as those discussed above.

[00210] Further, in at least one of the various embodiments, some or all of components described in FIGURE 4B and/or elsewhere in this paper as it relates to the embodiments shown in FIGURES 5A-5C may also be implemented in hardware, including, dedicated (custom) hardware, ASICs, FPGAs, or the like. Likewise, these components or portions thereof may be implemented in whole or in part using software, firmware and/or combinations thereof.

[00211] A general operation and implementation of the herein described embodiments, namely of their various functions, features and processes, are further described in co-pending Canadian Patent Application No. 2,992,333, the entire contents of which are hereby again incorporated herein by reference. The person of ordinary skill in the art will appreciate that these and other features and/or functions may be considered herein, without departing from the general scope and nature of the present disclosure.

[00212] As noted above, in at least one of the various embodiments, a wearable device may be arranged to omit features and components related to biometric sensors, biometric signals, or the like. In such embodiments, the preauthorization and/or authentication of the device may be based on non-biometric security factors. However, in the interest of brevity, the term biometric device is used throughout this description even though some wearable devices may be arranged to omit biometric features for authentication and/or preauthorization.

[00213] It will be understood that each block of the flowchart illustration, and combinations of blocks in the flowchart illustration, may be implemented by computer program instructions. These program instructions may be provided to a processor to produce a machine, such that the instructions, which execute on the processor, create means for implementing the actions specified in the flowchart block or blocks. The computer program instructions may be executed by a processor to cause a series of operational steps to be performed by the processor to produce a computer-implemented process such that the instructions, which execute on the processor to provide steps for implementing the actions specified in the flowchart block or blocks. The computer program instructions may also cause at least some of the operational steps shown in the blocks of the flowchart to be performed in parallel. These program instructions may be stored on some type of machine readable storage media, such as processor readable non-transitive storage media, or the like. Moreover, some of the steps may also be performed across more than one processor, such as might arise in a multi-processor computer system. In addition, one or more blocks or combinations of blocks in the flowchart illustration may also be performed concurrently with other blocks or combinations of blocks, or even in a different sequence than illustrated without departing from the general scope or spirit of the present disclosure.

[00214] Accordingly, blocks of the flowchart illustration support combinations of means for performing the specified actions, combinations of steps for performing the specified actions and program instruction means for performing the specified actions. It will also be understood that each block of the flowchart illustration, and combinations of blocks in the flowchart illustration, may be implemented by special purpose hardware-based systems, which perform the specified actions or steps, or combinations of special purpose hardware and computer instructions. The foregoing example should not be construed as limiting and/or exhaustive, but rather, an illustrative use case to show an implementation of at least one of the various embodiments of the invention.

[00215] While the present disclosure describes various embodiments for illustrative purposes, such description is not intended to be limited to such embodiments. On the contrary, the applicant's teachings described and illustrated herein encompass various alternatives, modifications, and equivalents, without departing from the embodiments, the general scope of which is defined in the appended claims. Except to the extent necessary or inherent in the processes themselves, no particular order to steps or stages of methods or processes described in this disclosure is intended or implied. In many cases the order of process steps may be varied without changing the purpose, effect, or import of the methods described. [00216] Information as herein shown and described in detail is fully capable of attaining the above-described object of the present disclosure, the presently preferred embodiment of the present disclosure, and is, thus, representative of the subject matter which is broadly contemplated by the present disclosure. The scope of the present disclosure fully encompasses other embodiments which may become apparent to those skilled in the art, and is to be limited, accordingly, by nothing other than the appended claims, wherein any reference to an element being made in the singular is not intended to mean "one and only one" unless explicitly so stated, but rather "one or more." All structural and functional equivalents to the elements of the above-described preferred embodiment and additional embodiments as regarded by those of ordinary skill in the art are hereby expressly incorporated by reference and are intended to be encompassed by the present claims. Moreover, no requirement exists for a system or method to address each and every problem sought to be resolved by the present disclosure, for such to be encompassed by the present claims. Furthermore, no element, component, or method step in the present disclosure is intended to be dedicated to the public regardless of whether the element, component, or method step is explicitly recited in the claims. However, that various changes and modifications in form, material, work-piece, and fabrication material detail may be made, without departing from the spirit and scope of the present disclosure, as set forth in the appended claims, as may be apparent to those of ordinary skill in the art, are also encompassed by the disclosure.