Remote user verification system and method for access-controlled embedded devices

Abstract

Regulated embedded devices, such as electronic nicotine delivery system (ENDS) products are often targeted by unauthorized users. For instance, minors may attempt to gain access to ENDS products. The disclosure herein provides an authentication and control mechanism for checking the identity of an attempted user. For instance, the mechanism may collect images or other sensor data from an attempted user and compare sensed data such as a photograph of the user to other data such as a photograph of a government-issued identification document, in order to determine whether the attempted user should be granted access to the device. The device may be selectively activated or inhibited in response to the determining.

Description

REMOTE USER VERIFICATION SYSTEM AND METHOD FOR ACCESS- CONTROLLED EMBEDDED DEVICESCross-Reference to Related Application

[0001] This application is based upon and claims priority to U.S. Provisional Patent Application No. 63 / 540,293 entitled “REMOTE USER VERIFICATION SYSTEM AND METHOD FOR ACCESS-CONTROLLED EMBEDDED DEVICES” and filed on September 25, 2023, the entire content of which is incorporated herein by reference.Field

[0002] The present invention is directed to access control, and more specifically, the present disclosure is directed to remote user verification for access-controlled embedded devices.Background

[0003] Access-controlled embedded devices may require certain user verification procedures prior to granting of access to the device to a user. For instance, a dispenser of a controlled substance that should be dispensed for only an authorized user is a regulated embedded device that may be desired to be access-controlled. Similarly, electronic nicotine delivery system (ENDS) devices may be desired to be access-controlled. These are often targeted by unauthorized users, such as minors, for misuse. Current mitigation techniques focus on identify verification at a point of sale. However, devices purchased online may not have a point-of-sale opportunity for inspection of a user’s identification documents and further, typical inspection performed at a point-of-sale terminal may be inadequate to identify some fake identification documents. Thus there remains a need for remote user verification for access-controlled embedded devices.1SUBSTITUTE SHEET (RULE 26)Summary

[0004] A system for remote user verification is provided. The system may include an access- controlled embedded device with a processor, a memory, and a transceiver connectable to a smartphone. The system may include an application running on a smartphone, the application connectable to the processor via the transceiver, wherein the application connects to at least one sensor of the smartphone to receive identity characteristics of a user from the at least one sensor. The system may include a verification server configured to receive from the application, data representative of the identity characteristics and to determine an authorization status of the user. The application is connectable via the smartphone to the verification server. The verification server transmits an authorization status message to the application corresponding to the authorization status. The application transmits to the access- controlled embedded device via the transceiver an instruction to authorize operation of the access-controlled embedded device, in response to the authorization status message including an indication that access is granted.

[0005] The system may include other features too. The identity characteristics may include an image of the user and an image of a government-issued identification document. The server may set the authorization status message to include the indication that the access is granted in response to the image of the user and the image of the government-issued identification document illustrating depictions of a same person and the image of the government-issued identification document illustrating a birth date of the user prior to a first age limit.

[0006] The verification server may store a private signing key. The memory of the access- controlled embedded device may store a verification key. The server may sign the authorization status message with the private signing key. The access-controlled embedded2SUBSTITUTE SHEET (RULE 26)device may verify an authenticity of the authorization status message by applying the verification key to the signed authorization status message.

[0007] The identity characteristics may further include a video of the user. The server may determine whether the user is a live person or a printed visual representation of a person in response to analyzing the video. In various embodiments, the server accesses a list of authorized users and the authorization status message including the indication that access is granted is transmitted in response to the government-issued identification document having one or more field corresponding to an authorized user. The access-controlled embedded device may be an electronic nicotine delivery system (ENDS). The application may be a browser-based application.

[0008] An access-controlled embedded device is provided. The device may include a processor, a transceiver connectable to a smartphone, and a memory to store a verification key. The processor may connect to an application on a smartphone via the transceiver. The processor may selectively deactivate or activate the access-controlled embedded device in response to receipt of an authorization status message that is signed by a signing key that corresponds to the verification key and that also includes an indication that access is granted.

[0009] In various embodiments, other aspects may be provided. A server may be connectable to the smartphone and may provide the authorization status message to the smartphone for transmission to the transceiver. The server may analyze data corresponding to an image of a user and an image of identity documents of the user and determine whether the identity documents are valid. The server may determine whether an age of the user provided in the identity documents exceeds a first threshold, and in response the server may set the authorization status message to include the indication that access is granted.

[0010] In various embodiments, the server signs the authorization status message with the signing key. In various embodiments, the server includes a signed authentication token that is3SUBSTITUTE SHEET (RULE 26)signed with the signing key in the authorization status message. In various embodiments, the signing key is a private key of an asymmetric key pair and the verification key is a public key of the asymmetric key pair. The access-controlled embedded device may be an electronic nicotine delivery system (ENDS).

[0011] A method of activating an access-controlled embedded device by a user is provided. The method may include receiving, by a server, an activation request sent to the server by an application on a smartphone, wherein the activation request includes identity characteristics of a user. The method may include verifying, by the server, an authorization status of the user in response to the identity characteristics. The method may include transmitting, by the server, an authorization status message to the application in response to the verifying. The method may include wherein the authorization status message includes an indication that access of the user to the access-controlled embedded device is (i) granted or (ii) denied.

[0012] One or more further aspects may be provided. For instance, in various embodiments the method includes transmitting, by the application on the smartphone, and via a radio transceiver of the smartphone, at least a portion of the authorization status message to the access-controlled embedded device.

[0013] The method may include wherein the identity characteristics include an image of the user and an image of a government-issued identification document. Verifying the authorization status of the user may include comparing the image of the user to the image of the government-issued identification document and determining that the government-issued identification document and the image of the user illustrate a same person. The verifying may include determining that the government-issued identification document illustrates an age that is greater than a first minimum age.

[0014] In various embodiments, the server signs at least a portion of the authorization status message with a private signing key. The access-controlled controlled embedded device stores4SUBSTITUTE SHEET (RULE 26)a verification key. The access-controlled embedded device verifies an origin of the authorization status message by applying the verification key to the signed authorization status message. The access-controlled embedded device may be an electronic nicotine delivery system (ENDS).5SUBSTITUTE SHEET (RULE 26)Brief Description of Figures

[0015] A more complete understanding of the present invention may be derived by referring to the detailed description and claims when considered in connection with the Figures, where like reference numbers refer to similar elements throughout the Figures, and:

[0016] FIG. 1A is a diagram of a system for remote user verification for access-controlled embedded devices, in accordance with various embodiments;

[0017] FIG. IB is a diagram of an access-controlled embedded device, in accordance with various embodiments; and

[0018] FIG. 2 is a diagram of an example method of remote user verification, in accordance with various embodiments; and

[0019] FIG. 3 is a diagram of an example method of activating an access-controlled embedded device, in accordance with various embodiments.6SUBSTITUTE SHEET (RULE 26)Detailed Description

[0020] The following description is of various exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the present disclosure in any way. Rather, the following description is intended to provide a convenient illustration for implementing various embodiments including the best mode. As will become apparent, various changes may be made in the function and arrangement of the elements described in these embodiments without departing from the scope of the appended claims.

[0021] Access-controlled embedded devices, such as electronic nicotine delivery system (ENDS) products or dispensers of controlled substances are often targeted by unauthorized users. For instance, minors may attempt to gain access to ENDS products. Current mitigation techniques focus on identify verification at a point of sale. However, devices purchased online may not have a point-of-sale opportunity for inspection of a user’s identification documents and further, typical inspection performed at a point-of-sale terminal may be inadequate to identify some fake identification documents. Thus there remains a need for remote user verification for access-controlled embedded devices.

[0022] This disclosure provides for a novel user verification system and method using a smartphone application or a web application running on a browser that supports Web Bluetooth. Browsers supporting Web Bluetooth allow web applications running on such browsers to connect to nearby Bluetooth devices. The user utilizes the application to verify his or her identity via a remotely disposed server. After the identity of the user has been verified as corresponding to an individual having appropriate credentials to use the access- controlled embedded device (such as being above an age limit), the application utilizes a Bluetooth connection to the access-controlled embedded device to activate the device for use.

[0023] The method includes providing identity characteristics to the system via the application. The identity characteristics may include credentials, identity information, scans7SUBSTITUTE SHEET (RULE 26)or photographs of documents, and images and / or videos. On successful verification, the application may connect to the device (e.g., the access-controlled embedded device) over Bluetooth or Bluetooth Low Energy (BLE) and activate the device.

[0024] As mentioned, the system may utilize a smartphone application or a web application. An application running on the phone, such as a smartphone application may provide for user verification and for device control over a wireless connection such as Bluetooth Low Energy (BLE) or Bluetooth Classic. In various embodiments, rather than providing for a smartphone application, a web browser application communicating with a remote server may be utilized. The web browser application may run on the smartphone on a web browser that supports Bluetooth or Bluetooth Low Energy and provides wireless remote control for the server to control the device over Bluetooth, such as by using the Web Bluetooth specification.

[0025] Turning now to FIGs. 1A-B, in an example system for remote user verification for access-controlled embedded devices (system 2), a user 4 may desire to access a device 6. The device 6 may be an access-controlled device. The access-controlled device 6 may have a processor 60, and may be an embedded device, thus being a device 6 with embedded processing functionality. Moreover, the embedded device 6 may be access-controlled, meaning systems and methods for access control of devices 6 are implemented thereon. The device 6 may be a nicotine delivery device. For instance, the device 6 may be an aspect of an electronic nicotine delivery system (ENDS). The device 6 may have a processor 60. The processor 60 may be any computing device, such as an embedded processor or microcontroller. The device 6 may have a memory 62. The memory 62 may be any electronic memory connectable to the processor 60 and providing working memory and / or storage memory. The memory 62 may store electronic keys, such as one or more key of one or more public-private key pair. The memory 62 may store a corresponding verification key (public key) associated with a private signing key (which may be retained by a server 10 such as a8SUBSTITUTE SHEET (RULE 26)verification server). The transceiver 64 may be an electronic communication device connected to the processor 60 to enable the processor 60 to communicate with other devices. For instance, the transceiver 64 may be a radio transceiver, such as a Bluetooth transceiver, and may be operatively connectable to a phone 5 of the user 4 to enable the processor 60 to communicate with the phone 5 of the user 4.

[0026] The system 2 may include an application 8. The application 8 may be associated with verifying an identity characteristic of a user 4 having custody of the device 6 to determine that the user is an authorized user. For instance, the application 8 may run on a phone 5. The user 4 may use the phone 5 enter identity characteristics. Identity characteristics include data or images or biometric data which can be used to verify an identity of the user 4 to establish that the user 4 has an identity characteristic that makes the user 4 authorized to use the access-controlled embedded device 6. For instance, an identity characteristic may be an age, as established by identity documents, or may be biometric data of the user 4 to determine that the user 4 is present in proximity to the smartphone 5, alive, and corresponds to a real person represented in identity documents. An identity characteristic may be a feature associated with making a positive determination of an identity of the user 4 or may be a physical characteristic of the user 4 that qualifies that user 4 for access. For instance, a purported person having physical features associated with a two-dimensional flat printed image of a human head may fail to have qualifying physical characteristics because that purported person is actually a non-living printout placed in front of a camera to pretend to be a real living person. The phone 5 may contain data corresponding to a unique identifier attributable to an identity of the user 4.

[0027] The smartphone 5 may run the one or more application 8, which may be a smartphone application, or a web application running in a browser session. The application 8 may have access to sensors of the smartphone 5 or may provide data entry fields so that a user 4 may9SUBSTITUTE SHEET (RULE 26)provide data adequate to complete the remote user verification so that an identity may be attributed to the user 4. The device 6 may connect to the application 8 running on the phone 5 and the application 8 may selectively enable or disable use of the device 6 based on verification of an authorized user 4.

[0028] The system 2 may include a server 10. The server 10 may have one or more verification component to verify authenticity of the identity and / or unique identifier attributable to the identity and / or identity characteristics of the user 4. In various embodiments, the server 10 contains a private signing key associated with the verification key (public key) in the memory 62 of the device 6. Stated differently, the server 10 may possess an authentication key (e.g., the private signing key) whose corresponding verification key is on the device 6. The keys maybe a symmetric key pair. The keys may be an asymmetric key pair.

[0029] Thus, with reference to the combination of FIGs. 1A and IB, a system 2 may include an access-controlled embedded device 6. The access-controlled embedded device 6 may require activation before a first use. The embedded device 6 may be equipped with a processor 60, a memory 62, and a transceiver 64 such as a Bluetooth transceiver. The Bluetooth transceiver may support Bluetooth Low Energy (BLE) and / or Classic Bluetooth. The system 2 may include an application 8. The application 8 may be running on a phone 5 or other device. The application 8 may be for user verification and device control. The application 8 may be a native smartphone application. The application 8 may be a web application running on a browser of a phone 5 supporting Web Bluetooth. The system 2 may include a server 10. The server 10 may be a verification server. The server 10 may store a private signing key. A corresponding verification key that corresponds to the private signing key may be stored on the device 6.10SUBSTITUTE SHEET (RULE 26)

[0030] In various embodiments, an authorized user 4 is known to the server 10 by a set of identity characteristics. The identity characteristics may include personal identifiers such as name, date of birth, and / or taxpayer identification number (TIN). In various embodiments, the identity characteristics may include whether the user 4 is or is not of an age above a threshold age. For instance, the authorized user 4 may be any user 4 whose age is above a certain age threshold. As mentioned, the identity characteristics may be entered into the application 8. In further instances, the identity characteristics may be computed from data entered into the application 8, whether manually or via sensors of the phone 5.

[0031] The system 2 may have features to facilitate users to log in onto the application 8. The application 8 may then access and / or interact with the server 10. The server 10 may create a unique identifier for each user 4 logging in to the system 2 on the application 8 and the server 10 may mark each user 4 as being either verified or unverified. The application 8 may grant access to the device 6 to users that are verified and may deny access to the device 6 to users that are unverified. The application 8 may also grant differing access to differing features of the device 6 based on other data in other fields marked by the server 10.

[0032] The server 10 may operate to consider new users to be unverified until the new users pass the verification process. The server 10 may grant new users one or more attempts to pass the verification process. The server 10 may inform the application 8 upon login of the user 4 whether the user 4 is verified or not and whether the user 4 is allowed to use any remaining attempts to pass the verification process if the user 4 is unverified. Furthermore, the application 8 may be configured to initiate the user verification process of an unverified user 4 who is allowed at least one remaining verification attempt. In various embodiments, the user verification process includes sending a verification link or code to a user’s phone number and / or email that the user 4 clicks on or enters into an application 8.11SUBSTITUTE SHEET (RULE 26)

[0033] The application 8 may perform a variety of features during the user verification process. For instance, the application 8 may require the user 4 to scan a front and / or back of a state-issued identification document such as a driver’s license or identity card. The application 8 may require the user 4 to record multiple successive photographs of the user 4 (e.g., selfie photographs) or a short video of the user 4 (e.g., selfie video).

[0034] The application 8 may request a user’s taxpayer identification number or part thereof (for example, a last four digits of a social security number). The application 8 may request the user’s email and / or mobile phone number. In various embodiments, the application 8 sends this collected data to the server 10. The data may be sent over a secure-TLS channel. The server 10 may then complete the user verification process.

[0035] The user verification process may include various aspects. For instance, the user verification process may include extracting, by the server 10 or the application 8, the values of fields (ID fields) shown in an image of a state-issued identification document. For instance, various data fields are printed on a driver’s license. The values in each of the data fields, such as name, birth date, age, address, and the like may be extracted. The process may include decoding a barcode in the state-issued identification document if present. The process may include comparing the information in the ID fields to the information decoded from the barcode. In this manner, some invalid or fake identification documents may be discovered and verification my be denied to that user 4. Moreover, the process may include checking an authenticity of the state-issued identification. For instance, the checking the authenticity may include detecting of whether a photo on the identification has been changed or altered. The checking the authenticity may include detecting of whether text on the identification ahs been changed or altered.

[0036] The user verification process may include matching information on the state-issued identification against a predefined list of authorized users. For instance, the list may be12SUBSTITUTE SHEET (RULE 26)known to the server 10 by a set of personal identifiers such as name, date of birth, and / or tax payer identification number (TIN). The process may match name, date of birth, address, and / or ID number or TIN number to one or more corresponding field in the list. The process may comprise verifying that the date of birth of the user 4 corresponds to an age that is older than an age threshold. The user verification process may include verifying that the information on the state-issued identification document such as name, date of birth, address, and / or identification number such as a TIN correctly matches public records. For instance, the server 10 may compare these items to credit bureau data.

[0037] In various instances, the user verification process may include extracting liveness features from multiple successive selfie photos or a short video to detect a user’s liveness and physical presence in front of the camera. Moreover, the user verification process may include matching photos or the short video of the user 4 to a photograph on a state-issued identification document. Yet furthermore, the process may include calculating an age estimate based on characteristics of the user 4 shown in one or more photograph or short video of the user 4.

[0038] In various embodiments, the server 10 will require additional enhanced review of the user’s identity characteristics. For instance, the server 10 may require additional enhanced review of the user’s state-issued identification. The server 10 may require additional enhanced review of the user’s identity characteristics such as a photograph (e.g., selfie photograph) or short video of the user 4. The enhanced review may include a manual review by a human reviewer. The additional enhanced review may be triggered if the user’s age estimate corresponds to a younger person than expected from the date of birth provided or on the state-issued identification document. For instance, an image may be analyzed to estimate an estimated user age. The additional enhanced review may include further review if a match between the photograph on the state-issued identification inadequately corresponds to a13SUBSTITUTE SHEET (RULE 26)photograph or short video of the user 4. The server 10 also may evaluate whether a user 4 has more than one account with different identifiers such as different identity characteristics. For instance, the server 10 may verify that a new user’s information does not match any previously registered user information (email, phone number, ID information, user photo or short video) that was already registered.

[0039] Upon completion of the user verification process, the server 10 may determine that the user 4 is successfully verified upon an applicable subset of aforementioned checks being successful. In response to successful verification, the server 10 records an indication that the user 4 is a verified user in an electronic memory. Otherwise, the user 4 remains unverified.

[0040] The server 10 provides an indication to the application 8 on the smartphone 5 of the user 4 that the verification was successful or unsuccessful. In response to the verification being successful, the server 10 may send an activation command to the application 8. The application 8 may communicate with the device 6 such as via a Bluetooth connection and provide an activation command. The activation command may include an authentication token (for example, a message authentication code (MAC) or a digital signature) that is generated using the server authentication key. The command may also include an identifier of the device 6, such as a Bluetooth address, and / or a one-time challenge created by the device 6.

[0041] In various instances, upon receipt of the activation command, the device 6 verifies the activation command using the verification key stored on the device 6 and unlocks itself upon successful verification.

[0042] Revalidation and other variations in behavior also invoke aspects of a user verification process. For instance, if a verified user 4 logs in on the application 8 (for example on a new phone 5), the server 10 is configured to request user revalidation by recording multiple successive selfie photographs of the user 4, detecting liveness, and matching the selfie14SUBSTITUTE SHEET (RULE 26)photographs with previously-provided selfie photographs provided previously by the user 4 during an earlier user verification. Moreover, user revalidation may be repeated at time intervals, or at random times, or upon certain user actions following activation, such as upon detection of excessive usage of the device 6 in excess of what would be expected for a single person.

[0043] Moreover, the server 10 may track a number of devices 6 activated by a single user 4 and the activation times. The server 10 may block further activation requests of a user 4 if the total number of devices 6 activated by the user 4 exceeds a predefined threshold, or if the number of devices 6 activated by the user 4 in a given time period such as a year or a month, exceeds a predefined threshold.

[0044] Referring now to FIG. 2, but with periodic reference to aspects of FIGs. 1A-1B, a method 100 of remote user verification is provided. The method 100 may include creating, by an application 8 on a smartphone 5, an account (block 102). For example, creating the account may include one or more steps that utilize an input device or a sensor of the phone 5 to input identity characteristics of a user 4. For instance, the phone 5 may be used to take a photograph of the user 4 (block 104), take a video of the user 4 (block 106), take a photograph of a state-issued identity document of the user 4 (block 108), and / or receive data entry via a keyboard or other entry function of the phone 5 as entered by the user 4 (block 110).

[0045] The application 8 may store the data entered in connection with the creating the account (block 122). In various embodiments, the data is stored locally in a memory of the phone 5. In further embodiments, the data is stored in a memory associated with the server 10.

[0046] The method may include a user verification aspect (block 142). The user verification aspect may include analyzing, by the server 10, the data from block 122 and determining15SUBSTITUTE SHEET (RULE 26)whether to grant access (block 162) for a user 4 to the device 6 or deny access (block 182) by the user 4 to the device 6 or require a return to block 102 for reentry of some or all of the identity characteristics previously entered in block 102.

[0047] The user verification aspect (block 142) may have further aspects. For instance, the server 10 may review data (block 144) corresponding to the data stored for review in block 122. The reviewing the data may include parsing out data associated with verifying an age of the user 4. For instance, the server 10 may verify the age of the user 4 (block 146) to determine that the user 4 is older than an age limit associated with the device 6. In response to an appropriate age being verified, the server 10 may grant access (block 162) for the user 4 to the device 6. Alternatively, in response to an appropriate age being not verified, the server 10 may deny access (block 182) of the user 4 to the device 6. In response to there being a deficiency with the data, the server 10 may send a message to the application 8 on the phone 5 requesting reentry of one or more identity characteristic, returning to block 102. Moreover, in response to there being a possible deficiency with the data, but the deficiency being capable of being resolved through elevated review, the server 10 may perform an elevated review of the data (block 148). In various instances, an elevated review includes additional age verification checks, such as more extensive application of machine learning, Al, external databases, or human review (block 162). This elevated review may verify correspondence between a selfie and an image on a state-issued identification document having an age indication corresponding to an access grant. In response to the elevated review indicating that access should be denied to the user 4, such as for having insufficient age, the server 10 will deny access (block 182). Finally, in response to there being a deficiency with the data, the server 10 may send a message to the application 8 on the phone 5 requesting reentry of one or more identity characteristic, returning to block 102.16SUBSTITUTE SHEET (RULE 26)

[0048] In various embodiments, granting access (block 162) includes sending by the server 10 a message to the application 8. The message utilizes an aspect of the phone 5, such as a Bluetooth transceiver, to send a message to the device 6 causing the device 6 to unlock for use. In various instances, granting access may involve one or more exchange of shared secret or keys, to verify the provenance and validity of messages.

[0049] In various embodiments, denying access (block 182) includes sending by the server 10 a message to the application 8. In other embodiments, the device 6 defaults to a locked state and no message is needed, because the device 6 will not unlock without the message of the preceding paragraph. In various instances, denying access may involve one or more exchange of shared secret or keys, to verify the provenance and validity of messages.

[0050] Thus, and with reference to FIG. 3, a method 300 of activating an access-controlled embedded device by a user may include remote user verification 100 (FIG. 2). The method may specifically include steps receiving, by a server, an activation request sent to the server by an application on a smartphone, wherein the activation request includes identity characteristics of a user (block 302). The method may include verifying, by the server, an authorization status of the user in response to the identity characteristics (block 304). The method may include transmitting, by the server, an authorization status message to the application in response to the verifying (block 306). The authorization status message may include an indication that access of the user to the access-controlled embedded device is (i) granted or (ii) denied. The method may also include transmitting, by the application on the smartphone, and via a radio transceiver of the smartphone, at least a portion of the authorization status message to the access-controlled embedded device (block 308).

[0051] The method 300 may include one or more additional feature, some of which have been discussed already in connection to other aspects of this disclosure but are helpfully repeated below. For instance, the identity characteristics may include an image of the user17SUBSTITUTE SHEET (RULE 26)and an image of a government-issued identification document. In some embodiments, verifying the authorization status of the user comprises comparing the image of the user to the image of the government-issued identification document and determining that the government-issued identification document and the image of the user illustrate a same person. The verifying may also include determining that the government-issued identification document illustrates an age that is greater than a first minimum age.

[0052] The method may also include wherein the server signs at least a portion of the authorization status message with a private signing key. The access-controlled controlled embedded device stores a verification key. The access-controlled embedded device verifies an origin of the authorization status message by applying the verification key to the signed authorization status message. In various embodiments, the access-controlled embedded device comprises an electronic nicotine delivery system (ENDS).

[0053] Turning now to the entire collection of FIGs. 1A-3, it is convenient to discuss various example implementations of the aforementioned systems and methods. In various embodiments, a system 2 for remote user verification is provided. The system 2 may include an access-controlled embedded device 6 with a processor 60, a memory 62, and a transceiver 64 connectable to a smartphone 5. The system 2 may include an application 8 running on a smartphone 5, the application 8 connectable to the processor 60 via the transceiver 64, wherein the application 8 connects to at least one sensor of the smartphone 5 to receive identity characteristics of a user 4 from the at least one sensor. The system 2 may include a verification server 10 configured to receive from the application 8, data representative of the identity characteristics and to determine an authorization status of the user 4. The application 8 is connectable via the smartphone 5 to the verification server 10. The verification server 10 transmits an authorization status message to the application 8 corresponding to the authorization status. The application 8 transmits to the access-controlled embedded device 618SUBSTITUTE SHEET (RULE 26)via the transceiver 64 an instruction to authorize operation of the access-controlled embedded device 6, in response to the authorization status message including an indication that access is granted.

[0054] The system 2 may include other features too. The identity characteristics may include an image of the user 4 and an image of a government-issued identification document. The server 10 may set the authorization status message to include the indication that the access is granted in response to the image of the user 4 and the image of the government-issued identification document illustrating depictions of a same person and the image of the government-issued identification document illustrating a birth date of the user 4 prior to a first age limit.

[0055] The verification server 10 may store a private signing key. The memory 62 of the access-controlled embedded device 6 may store a verification key. The server 10 may sign the authorization status message with the private signing key. The access-controlled embedded device 6 may verify an authenticity of the authorization status message by applying the verification key to the signed authorization status message.

[0056] The identity characteristics may further include a video of the user 4. The server 10 may determine whether the user 4 is a live person or a printed visual representation of a person in response to analyzing the video. In various embodiments, the server 10 accesses a list of authorized users and the authorization status message including the indication that access is granted is transmitted in response to the government-issued identification document having one or more field corresponding to an authorized user 4. The access-controlled embedded device 6 may be an electronic nicotine delivery system (ENDS). The application 8 may be a browser-based application.

[0057] An access-controlled embedded device 6 is provided. The device 6 may include a processor 60, a transceiver 64 connectable to a smartphone 5, and a memory 62 to store a19SUBSTITUTE SHEET (RULE 26)verification key. The processor 60 may connect to an application 8 on a smartphone 5 via the transceiver 64. The processor 60 may selectively deactivate or activate the access-controlled embedded device 6 in response to receipt of an authorization status message that is signed by a signing key that corresponds to the verification key and that also includes an indication that access is granted.

[0058] In various embodiments, other aspects may be provided. A server 10 may be connectable to the smartphone 5 and may provide the authorization status message to the smartphone 5 for transmission to the transceiver 64. The server 10 may analyze data corresponding to an image of a user 4 and an image of identity documents of the user 4 and determine whether the identity documents are valid. The server 10 may determine whether an age of the user 4 provided in the identity documents exceeds a first threshold, and in response the server 10 may set the authorization status message to include the indication that access is granted.

[0059] In various embodiments, the server 10 signs the authorization status message with the signing key. In various embodiments, the server 10 includes a signed authentication token that is signed with the signing key in the authorization status message. In various embodiments, the signing key is a private key of an asymmetric key pair and the verification key is a public key of the asymmetric key pair. The access-controlled embedded device 6 may be an electronic nicotine delivery system (ENDS).

[0060] A method of activating an access-controlled embedded device 6 by a user 4 is provided. The method may include receiving, by a server 10, an activation request sent to the server 10 by an application 8 on a smartphone 5, wherein the activation request includes identity characteristics of a user 4. The method may include verifying, by the server 10, an authorization status of the user 4 in response to the identity characteristics. The method may include transmitting, by the server 10, an authorization status message to the application 8 in20SUBSTITUTE SHEET (RULE 26)response to the verifying. The method may include wherein the authorization status message includes an indication that access of the user 4 to the access-controlled embedded device 6 is (i) granted or (ii) denied.

[0061] One or more further aspects may be provided. For instance, in various embodiments the method includes transmitting, by the application 8 on the smartphone 5, and via a radio transceiver 64 of the smartphone 5, at least a portion of the authorization status message to the access-controlled embedded device 6.

[0062] The method may include wherein the identity characteristics include an image of the user 4 and an image of a government-issued identification document. Verifying the authorization status of the user 4 may include comparing the image of the user 4 to the image of the government-issued identification document and determining that the government- issued identification document and the image of the user 4 illustrate a same person. The verifying may include determining that the government-issued identification document illustrates an age that is greater than a first minimum age.

[0063] In various embodiments, the server 10 signs at least a portion of the authorization status message with a private signing key. The access-controlled controlled embedded device 6 stores a verification key. The access-controlled embedded device 6 verifies an origin of the authorization status message by applying the verification key to the signed authorization status message. The access-controlled embedded device 6 may be an electronic nicotine delivery system (ENDS).

[0064] The present disclosure has been described with reference to various embodiments. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the present disclosure. For example, features of different embodiments may be combined. Accordingly, the specification is to be21SUBSTITUTE SHEET (RULE 26)regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of the present disclosure.

[0065] For the sake of brevity, conventional techniques for manufacturing and construction may not be described in detail herein. Furthermore, the connecting lines shown in various figures contained herein are intended to represent exemplary functional relationships and / or physical couplings between various elements. It should be noted that many alternative or additional functional relationships or physical connections may be present in a practical method of construction. As used herein, mechanical communication means any joint, connection, bond, or arrangement whereby an article is held, retained, or fixed in relatively static spatial relationship to another article. As used herein, electronic communication means any wired, wireless, analog, digital, or other mechanism whereby information is communicated between machines, circuits, or devices.

[0066] Benefits, other advantages, and solutions to problems have been described herein with regard to various embodiments. However, the benefits, advantages, solutions to problems, and any elements that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as critical, required, or essential features or elements of the invention. Moreover, where a phrase similar to “at least one of A, B, and C” or “at least one of A, B, or C” is used in the claims or specification, it is intended that the phrase be interpreted to mean that A alone may be present in an embodiment, B alone may be present in an embodiment, C alone may be present in an embodiment, or that any combination of the elements A, B and C may be present in a single embodiment; for example, A and B, A and C, B and C, or A and B and C.

[0067] As used herein, the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. As used herein, the terms “for example,” “for instance,” “such as,” or “including” are meant to introduce examples that further clarify more22SUBSTITUTE SHEET (RULE 26)general subject matter. Unless otherwise specified, these examples are embodiments of the present disclosure, and are not meant to be limiting in any fashion.

[0068] 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. No claim element herein is to be construed under the provisions of 35 U.S.C. 112(f) unless the element is expressly recited using the phrase “means for.” As used herein, the terms “comprises,” “comprising,” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.23SUBSTITUTE SHEET (RULE 26)

Claims

ClaimsWHAT IS CLAIMED IS:

1. A system for remote user verification comprising: an access-controlled embedded device comprising a processor, a memory, and a transceiver connectable to a smartphone; an application running on a smartphone, the application connectable to the processor via the transceiver, wherein the application connects to at least one sensor of the smartphone to receive identity characteristics of a user from the at least one sensor; a verification server configured to receive from the application, data representative of the identity characteristics and to determine an authorization status of the user, wherein the application is connectable via the smartphone to the verification server and, wherein the verification server transmits an authorization status message to the application corresponding to the authorization status, and wherein the application transmits to the access-controlled embedded device via the transceiver an instruction to authorize operation of the access-controlled embedded device, in response to the authorization status message including an indication that access is granted.

2. The system according to claim 1, wherein the identity characteristics include an image of the user and an image of a government-issued identification document.

3. The system according to claim 2, wherein the server sets the authorization status message to include the indication that the access is granted in response to the image of the user and the image of the government-issued identification document illustrating depictions of a same24SUBSTITUTE SHEET (RULE 26)person and the image of the government-issued identification document illustrating a birth date of the user prior to a first age limit.

4. The system according to claim 3, wherein the verification server stores a private signing key, wherein the memory of the access-controlled embedded device stores a verification key, wherein the server signs the authorization status message with the private signing key, and wherein the access-controlled embedded device verifies an authenticity of the authorization status message by applying the verification key to the signed authorization status message.

5. The system according to claim 4, wherein the identity characteristics further include a video of the user, and wherein the server determines whether the user is a live person or a printed visual representation of a person in response to analyzing the video.

6. The system according to claim 1, wherein the server accesses a list of authorized users and the authorization status message including the indication that access is granted is transmitted in response to the government-issued identification document having one or more field corresponding to an authorized user.

7. The system according to claim 1, wherein the access-controlled embedded device comprises an electronic nicotine delivery system (ENDS).

8. The system according to claim 1, wherein the application is a browser-based application.

9. An access-controlled embedded device comprising: a processor,25SUBSTITUTE SHEET (RULE 26)a transceiver connectable to a smartphone; and a memory to store a verification key, wherein the processor connects to an application on a smartphone via the transceiver, and wherein the processor selectively deactivates or activates the access-controlled embedded device in response to receipt of an authorization status message that is signed by a signing key that corresponds to the verification key and that also includes an indication that access is granted.

10. The access-controlled embedded device according to claim 9, wherein a server is connectable to the smartphone and provides the authorization status message to the smartphone for transmission to the transceiver.

11. The access-controlled embedded device according to claim 10, wherein the server analyzes data corresponding to an image of a user and an image of identity documents of the user and determines whether the identity documents are valid and determines whether an age of the user provided in the identity documents exceeds a first threshold, and in response the server sets the authorization status message to include the indication that access is granted.

12. The access-controlled embedded device according to claim 11, wherein the server signs the authorization status message with the signing key.

13. The access-controlled embedded device according to claim 11, wherein the server includes a signed authentication token that is signed with the signing key in the authorization status message.26SUBSTITUTE SHEET (RULE 26)14. The access-controlled embedded device according to claim 11, wherein the signing key comprises a private key of an asymmetric key pair and the verification key comprises a public key of the asymmetric key pair.

15. The access-controlled embedded device according to claim 9, wherein the access- controlled embedded device comprises an electronic nicotine delivery system (ENDS).

16. A method of activating an access-controlled embedded device by a user, the method comprising: receiving, by a server, an activation request sent to the server by an application on a smartphone, wherein the activation request includes identity characteristics of a user; verifying, by the server, an authorization status of the user in response to the identity characteristics; and transmitting, by the server, an authorization status message to the application in response to the verifying, wherein the authorization status message includes an indication that access of the user to the access-controlled embedded device is (i) granted or (ii) denied.

17. The method according to claim 16, further comprising transmitting, by the application on the smartphone, and via a radio transceiver of the smartphone, at least a portion of the authorization status message to the access-controlled embedded device.27SUBSTITUTE SHEET (RULE 26)18. The method according to claim 16, wherein the identity characteristics comprise an image of the user and an image of a government-issued identification document, wherein verifying the authorization status of the user comprises comparing the image of the user to the image of the government-issued identification document and determining that the government-issued identification document and the image of the user illustrate a same person and determining that the government-issued identification document illustrates an age that is greater than a first minimum age.

19. The method according to claim 16, wherein the server signs at least a portion of the authorization status message with a private signing key, and wherein the access-controlled controlled embedded device stores a verification key, and wherein the access-controlled embedded device verifies an origin of the authorization status message by applying the verification key to the signed authorization status message.

20. The method according to claim 16, wherein the access-controlled embedded device comprises an electronic nicotine delivery system (ENDS).28SUBSTITUTE SHEET (RULE 26)

Images