Device, user or server registration and authentication
Through two-way verification of transducers and authentication servers that integrate biometric data in the device, the complexity of multi-device type management and authentication is solved, and seamless authentication and security improvement is achieved.
Patent Information
- Application Number
- CN201980069582.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-11-01
- Filing Date
- 2019-10-18
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2039-10-18
AI Technical Summary
The existing technology is difficult to effectively manage and verify more and more device types, resulting in users facing complex authentication problems when accessing different devices, and password management of different devices increases user frustration.
By integrating biometric data into the device, users' biometric data is generated and bidirectional verification is carried out with the authentication server, seamless authentication is achieved to ensure the verification of user identity and device identity, allowing or denying users access to device functions.
Improves user experience, enhances security, reduces the possibility of spoofing and simulated attacks, and achieves seamless user and device verification independently of user input through seamless authentication and strict registration or verification rules.
Smart Images

Figure CN112913187B_ABST
Abstract
Description
Background Art
[0001] User and device authentication is becoming increasingly challenging. Part of the challenge is that there are more and more devices of an ever-increasing number of device types. It is becoming increasingly difficult to keep track of all the devices, the users who have access to them, and to keep the devices secure from exploitation. Additionally, users are becoming increasingly frustrated with the myriad of authentication schemes required to access different devices. While such password variations are recommended for security reasons, users using different passwords for different devices can exacerbate this frustration. Summary of the invention
[0002] The present disclosure provides a device, system, method and machine-readable medium for device, user or authentication server authentication. The device may include a memory, a processing circuit coupled to the memory, the processing circuit including a transducer for generating biometric data of a user of the device, and the processing circuit for performing operations including generating biometric data of the user by the transducer in response to detecting that the user performs a non-authentication operation with the device. These operations may also include providing biometric data to an authentication server for user verification, wherein the authentication server is registered with the device and authenticated by the device, and the device is registered with the authentication server and authenticated by the authentication server. The operation may also include granting the user access to the functionality of the device in response to a result communication from the authentication server indicating that the user authentication is passed. The operation may also include denying the user access to the functionality of the device in response to a result communication from the authentication server indicating that the user authentication failed.
[0003] A method may include registering a device with an authentication server, including receiving or generating a device identification. The method may also include registering an authentication server with the device, including receiving or generating an authentication server identification. The method may also include registering a user with the authentication server, including receiving or generating a user identification. The method may also include, in response to the device detecting that a user has used the device to perform a specified action, verifying at least two of the following identities through communication between the device and the authentication server: (i) the device identification, (ii) the authentication server identification, (iii) the corresponding user identification, and (iv) the corresponding user identification associated with the device identification. The method may also include, in response to any of the at least two identities failing to verify, denying the user action on the functionality of the device. The method may also include, in response to all of the at least two identities being verified, granting the user access to the functionality of the device.
[0004] A non-transitory machine-readable medium may include instructions that, when executed by a device, cause the device to perform operations, the operations comprising: registering the device with an authentication server, including receiving or generating a device identification; registering the authentication server with the device, including receiving or generating an authentication server identification. The operations may also include registering one or more users with the authentication server, including receiving or generating user identifications. The operations may also include verifying each of the following by communicating with the authentication server: (i) the device identification, (ii) the authentication server identification, (iii) the user identification, and (iv) the corresponding user identification is associated with the device identification. The operations may also include, in response to any one of (i) to (iv) failing to verify, denying the user access to the functionality of the device. The operations may also include allowing the user access to the functionality of the device in response to all of (i) to (iv) being verified.
[0005] The system may include a device including a memory and a device processing circuit, the device processing circuit including a transducer coupled to the memory for generating biometric data of a user of the device, the device processing circuit performing a first operation, the first operation including generating, by the transducer, the biometric data of the user in response to detecting that the user performs a non-authentication operation with the device. The operations may also include providing the biometric data to an authentication server for user verification, wherein the authentication server is registered with and authenticated by the device, and the device is registered with and authenticated by the authentication server. The operations may also include granting the user access to the functionality of the device in response to a result communication from the authentication server indicating that the user authentication passed. The operations may also include denying the user access to the functionality of the device in response to a result communication from the authentication server indicating that the user authentication failed. The authentication server may include a memory and an authentication server processing circuit, the memory including authentication data stored thereon, the authentication server processing circuit for performing a second operation, the second operation including comparing the biometric data with second biometric data in the authentication data. Operation of the authentication server processing circuitry may also include providing a result communication indicating (i) authentication passed if (a) the biometric data matches the second biometric data and (b) the user is associated with the device in the authentication data, or (ii) authentication failed if (c) the biometric data does not match the second biometric data or (d) the user is not associated with the device in the authentication data.
[0006] The present disclosure also provides a device or system configured to perform an operation. The present disclosure also provides at least one machine-readable medium, the machine-readable medium including instructions, which are configured to the machine to perform the operation when executed by the machine. The present disclosure also provides a method for performing an operation. The present disclosure also provides an apparatus for performing an operation.
[0007] Various embodiments of the present disclosure have various advantages. For example, according to various embodiments, the user experience can be enhanced by seamless authentication. Another advantage can include enhancing security by user, device or server registration or verification without user input. Another advantage can include enhancing security by strictly following registration or verification rules. Another advantage can include verifying user identity independent of user input or user expected user verification. Such embodiments can help reduce attacks of spoofing or other simulated types. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] The drawings show generally by way of example, but not limitation, of the various embodiments discussed in this document.
[0009] Figure 1 A communication diagram showing an embodiment of communication between items of a seamless authentication system by way of example.
[0010] Figure 2 A communication diagram showing another embodiment of the communication between items of the seamless authentication system by way of example.
[0011] Figure 3 A diagram of an embodiment of a system for indirect user, device, or server authentication and verification is shown by way of example.
[0012] Figure 4 A diagram of an implementation of a seamless authentication method is shown by way of example.
[0013] Figure 5 A diagram of another embodiment of a method for seamless authentication is shown by way of example.
[0014] Figure 6 A block diagram of an example of a device on which any of the one or more processes (eg, methods) discussed herein may be performed is shown by way of example. DETAILED DESCRIPTION
[0015] Reference will now be made in detail to certain embodiments of the presently disclosed subject matter, examples of which are partially illustrated in the accompanying drawings. Although the presently disclosed subject matter will be described in conjunction with the enumerated claims, it should be understood that the exemplary subject matter is not intended to limit the claims to the presently disclosed subject matter.
[0016] Throughout this document, values expressed in a range format should be interpreted in a flexible manner to include not only the values explicitly listed as the limits of the range but also all individual values or subranges contained within the range, as if each value and subrange were explicitly listed. For example, the range "about 0.1% to about 5%" or "about 0.1% to 5%" should be interpreted as including not only about 0.1% to about 5%, but also individual values (e.g., 1%, 2%, 3%, and 4%) and subranges (e.g., 0.1% to 0.5%, 1.1% to 2.2%, 3.3% to 4.4%) within the indicated range. Unless otherwise specified, the expression "about X to Y" has the same meaning as "about X to about Y". Similarly, unless otherwise specified, the expression "about X, Y, or about Z" has the same meaning as "about X, about Y, or about Z".
[0017] In this document, unless the context clearly indicates otherwise, the terms "a", "an", or "the" are used to include one or more than one. Unless otherwise indicated, the term "or" is used to refer to a non-exclusive "or". The expression "at least one of A and B" has the same meaning as "A, B, or A and B". In addition, it should be understood that the words or terms used herein and not otherwise defined are for descriptive purposes only and are not limiting. Any use of section headings is intended to facilitate understanding of the document and should not be construed as limiting; information related to a section heading may appear within or outside the section.
[0018] In the methods described herein, except where a time or sequence of operations is explicitly enumerated, various actions may be performed in any order without departing from the principles of the invention. In addition, specified actions may be performed simultaneously unless explicit claim language implies that they are performed separately. For example, a claimed action of performing X and a claimed action of performing Y may be performed simultaneously in a single operation, and the resulting process will fall within the literal scope of the claimed process.
[0019] As used herein, the term "about" can allow for a certain degree of variability in values or ranges, such as within 10%, within 5%, or within 1% of the value or range limit, and includes the values or ranges that are exactly stated. As used herein, the term "substantially" or "substantially" refers to a large portion or majority, such as at least about 50%, 60%, 70%, 80%, 90%, 95%, 96%, 97%, 98%, 99%, 99.5%, 99.9%, 99.99%, or at least about 99.999% or more, or 100%.
[0020] Various embodiments of the present disclosure provide for secure implementations of mutual authentication server to local device identity authentication. Embodiments may also provide for user authentication to an authentication server or local device. Embodiments may include one or more of the following features: (i) user registration with an authentication server or device, (ii) user authentication with an authentication server or device (e.g., using biometric data), (iii) device authentication of the authentication server identity, (iv) authentication server authentication of the device identity, (v) association of a user with a device at an authentication server, and (vi) identification of a user's intent to use or interact with a device to trigger biometric data collection or user authentication.
[0021] The embodiment provides secure authentication of assets / devices in the cloud. The embodiment can maintain the integrity and security of the assets. The embodiment may include devices / assets for seamlessly authenticating users and reducing the chance of impersonation ("spoofing"). Currently, devices (e.g., IoT devices or other Internet-connected devices) cannot seamlessly and uniquely identify users. In this article, seamless means that the user does not know that the identification process is happening. For example, phone facial recognition authentication is not seamless. This is because the user needs to position their face in the field of view of the phone camera to perform authentication. Seamless authentication may include devices that perform identification in the natural use of the device. For example, consider a helmet with goggles. The helmet is worn on the head during natural use. Seamless authentication with the helmet may include facial recognition identification. In another example, consider a smart watch. For natural use, the smart watch is located on the user's wrist. Seamless authentication with the smart watch may include verifying one or more unique biometric characteristics of the skin or body under the smart watch, such as by using a wrist print. In another example, consider a smart phone. For natural use, the smart phone is located in the user's hand. Seamless authentication with the smart phone may include verifying one or more unique biometric characteristics of the palm, fingers, or other parts of the user's hand.
[0022] Embodiments allow a user to seamlessly interact with a device while maintaining secure access to the device. The device can mutually authenticate with a cloud (e.g., an authentication server in the cloud). Thus, embodiments can provide seamless device authentication that allows a user to interact in an approved (permission-based) manner to authenticate the device and the user's identity, such as in a "two-way authentication," sometimes referred to as a "handshake."
[0023] Consider an example where a user has an IoT device such as a smartwatch. The user may register the smartwatch with the cloud, and the cloud may register the smartwatch at the same time or at a different time. The user may authenticate to the cloud so that the user is associated with the device. Subsequent attempts to connect the device to the cloud may include mutual verification of each (cloud and device) identity. After the connection is established between the device and the cloud, the user may authenticate the cloud (where the device acts as a conduit) or the device. After the user is authenticated, the device then proceeds to, for example, collect data (e.g., the user's biometric data). The data may be sent to the cloud for processing. After the initial registration, the entire authentication process may be transparent to the user. Then, when an unauthorized user (a user who has not registered to use the device or for whom the cloud does not have biometric data) attempts to use the device (e.g., a smartwatch), the authentication will fail. Therefore, since the user authentication fails at the cloud, the device will not allow data collection and / or processing to continue.
[0024] Further details of the embodiments will now be described with reference to the accompanying drawings.
[0025] Figure 1 A communication diagram of an embodiment of communication between items of a seamless authentication system 100 is shown by way of example. The seamless authentication system 100 as shown includes a user 102, a device 104, and an authentication server 106. The user 102 includes anyone who can use the device 104.
[0026] Device 104 may include a computing device (e.g., a phone, a laptop, a tablet, a desktop computer, a smart watch, a fitness tracker, etc.), an e-reader, a helmet, an appliance (e.g., a stove, a refrigerator, a coffee maker, a microwave oven, a television, a washing machine, a dryer, a dishwasher, etc.), a security device (e.g., a camera, a microphone, a sensor (such as a motion detection sensor, a glass break sensor, a window or door open sensor, a smoke detector, a heat detector, a water detector, etc.), a vehicle (e.g., a manned or unmanned car, truck, boat, airplane, etc.), a health monitor (e.g., a blood glucose, pulse oximeter, an oxygen tank, a blood pressure, a heart rate, a heartbeat monitor, a pacemaker, etc.), or other device that can be used by user 102 and communicate with authentication server 106.
[0027] Device 104 as shown includes processing circuit 101 and memory 105. Processing circuit 101 as shown includes transducer 103 and communication circuit 111. Device 104 may communicate with authentication server 106 such as through communication circuit 111. Communication may be wired or wireless. Communication may be performed on the same or different networks. Communication may be performed through the Internet. Communication circuit 111 may include one or more of wired communication circuit or wireless communication circuit. Examples of wired communication circuits include circuits that comply with Ethernet, Recommended Standard 232 (RS-232), RS-485, Universal Asynchronous Receiver / Transmitter (UART), Universal Synchronous / Asynchronous Receiver / Transmitter (USART), Universal Serial Bus (USB), FireWire or other wired communication protocols. Examples of wireless communication circuits include receiving radio components, transmitting radio components, transceiver radio components, etc. Radio components may include circuits that comply with Bluetooth, Zigbee, Wireless Fidelity (WiFi), Long Term Evolution (LTE), Institute of Electrical and Electronics Engineers (IEEE) 802.11 or other wireless communication protocols.
[0028] Device 104 may acquire biometric data using transducer 103. Transducer 103 converts changes in physical properties that can be quantified into electrical signals. For example, the physical properties may include one or more of pressure, color, brightness, temperature, chemical composition (e.g., salinity, odor, oxygen, water, pH, etc.), contour, shape, resistivity or conductivity, combinations thereof, etc. Transducer 103 may sometimes be referred to as a sensor. Examples of transducer 103 include pressure sensors, optical transducers, salinity, water, oxygen or other chemical sensors, thermometers, etc.
[0029] Memory 105 may include data to be used in a registration or verification process (jointly referred to as an authentication process). For example, memory 105 may include one or more of the following: (i) an authentication server identity provided or generated based on data provided in server registration communication 110; (ii) a user identity provided or generated based on data provided in user registration communication 112; (iii) biometric data of user 102 from user registration communication 112, such as biometric data from processing circuit 101 or directly from transducer 103; and (iv) an encryption key or decryption key to be used to communicate with authentication server 106; or other authentication data.
[0030] Authentication server 106 manages access to device 104 by user 102. Authentication server 106 may include processing circuitry 109 that facilitates authentication of user 102 attempting to access device 104. Authentication server 106 may be part of a dedicated computer (a computer dedicated to managing access to device 104), a switch (e.g., an Ethernet switch), an access point or network access server, or other device. Processing circuitry 109 determines whether a person (or something) is who they claim to be. Techniques for such determinations are discussed elsewhere herein.
[0031] The processing circuits 101, 109 may additionally or alternatively include one or more electrical or electronic components configured to form a circuit. The electrical or electronic components may include one or more resistors, transistors, capacitors, diodes, inductors, power sources (e.g., voltage or current sources, such as batteries or power lines connected to a power source), regulators (voltage regulators or current regulators), modulators, demodulators, analog-to-digital converters, digital-to-analog converters, processors (e.g., central processing units (CPUs), graphics processing units (GPUs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), logic gates (e.g., AND, OR, XOR, negation or buffer gates), multiplexers, switches, radio components (e.g., receiving radio components, transmitting radio components or transceiver radio components), communication ports (e.g., Ethernet ports, USB ports, FireWire ports, UART ports, USART ports, etc.), etc. The processing circuits 101, 109 may be configured to execute instructions stored on the memory 105, 113 or other memory, which cause the processing circuits 101, 109 to perform operations of the device 104 or the authentication server 106, respectively.
[0032] Authentication server 106 is shown to also include memory 113. Memory 113 may include authentication data 107. Authentication data 107 may include data to be used in a user, device, or authentication server authentication process (such as a handshake). Authentication data 107 may include a user identity or biometric data of user 102, such as may be provided or generated based on data provided in user registration communication 114. Authentication data 107 may include a device identity, such as may be provided or generated based on data provided in device registration communication 108. Authentication data may include an authentication server identity, such as may be provided or generated based on data provided in server registration communication 110.
[0033] The device 104 may register with the authentication server 106 via a device registration communication 108. The device registration communication 108 may include authentication data to be used in the authentication process. The authentication data may include one or more characteristics of the device 104, which may be unique (e.g., in aggregate) to the device 104. The one or more characteristics may include one or more of a serial number, a model number, a device type, a device version number, an operating system, an operating system version, a device color, a manufacturing date, a media access control (MAC), a combination thereof, and the like. The authentication data may include non-device-based data that may be used for authentication. For example, the authentication data may include a certificate, an encryption key, a random number, other quantities, a string, a combination thereof, and the like. In some embodiments, the authentication data may include a combination of characteristics and non-device-based data.
[0034] The authentication server 106 may register with the device 104 via the authentication server registration communication 110. The device registration communication 108 may include authentication data to be used in the authentication process with the device 104. The authentication data from the server may include one or more characteristics of the authentication server 106, which may be unique (e.g., in aggregate) to the authentication server 106. The one or more characteristics of the authentication server 106 may include one or more of a serial number, a model, a device type, a device version number, an operating system, an operating system version, a device color, a manufacturing date, a media access control (MAC), a combination thereof, and the like. The authentication data may include non-device-based data that can be used for authentication. For example, the authentication data may include a certificate, an encryption key, a random number, other quantities, a string, a combination thereof, and the like. In some embodiments, the authentication data may include a combination of characteristics and non-device-based data. The device registration communication 108 and the server registration communication 110 are used to exchange data that can be used for the device 104 to authenticate the server 106 and for the authentication server 106 to authenticate the device 104.
[0035] The user 102 may optionally register with the device 104 via a user registration communication 112. The registration communication 112 may include a request to allow the user to access at least some functionality of the device 104. In some embodiments, the user registration communication 112 may include a user interacting directly with the device 104. In some other embodiments, the user registration communication 112 may come from a user interacting with a different device. In some embodiments, the user registration communication 112 may include one or more of a user name, a password, a passcode, biometric data, or other data unique to the user 102 (unique from the perspective of the device 104). In some embodiments, the user registration communication 112 includes biometric data that may be collected by the device 104 during natural operation of the device 104.
[0036] Biometric data may include data collected by device 104 when a user performs an operation that is not an authentication operation. Biometric data is data from body measurements. Biometric data relates to one or more physiological characteristics (as opposed to behavioral characteristics) of user 102. Biometric data may include facial characteristics, skin characteristics (e.g., color, such as color under specified lighting, texture, hair color, salinity, temperature, skin prints, such as fingerprints, etc.), vein or artery prints, deoxyribonucleic acid (DNA), wrist or palm prints, the geometry of a part of the body, iris prints, retinal prints, smells or fragrances, chemical composition, or other biometric data.
[0037] Examples of authentication operations include a user entering a password, username, passcode, etc. through a user interface. Other examples of authentication operations include a user positioning a camera of device 104 so that their face is in the camera's field of view so that the device can verify their facial identification, or a user placing their finger in a designated location on device 104 so that device 104 can verify their fingerprint. These operations are not required for normal operation of the phone and require user 102 to perform actions beyond their desired operation of the phone.
[0038] Examples of non-authentication operations include: picking up device 104 if device 104 is a phone, reader, tablet, inventory management device, or other handheld device; lowering the goggles of device 104 if device 104 is a helmet; wearing device 104 on their wrist if device 104 is a watch or fitness tracker; wearing device 104 on their chest, ankle, or wrist if device 104 is a fitness tracker; opening the door of device 104 if device 104 is a refrigerator, microwave, oven, vehicle, etc.; grabbing the remote control of device 104 if device 104 is a television, drone, or other remotely controlled device; lifting the lid of device 104 if device 104 is a laptop, etc.
[0039] The user 102 may register with the authentication server 106 via a user registration communication 114. The user registration communication 114 may include a request to associate user access with the device 104. In some embodiments, the user registration communication 114 may include a user interacting directly with the device 104. In some other embodiments, the user registration communication 114 may come from a user interacting with a different device. In some embodiments, the user registration communication 114 may include one or more of a user name, a password, a passcode, biometric data, or other data that may be used to uniquely identify the user 102. In some embodiments, the user registration communication 114 includes biometric data that may be collected by the device 104 during the natural operation of the user 102 operating the device 104.
[0040] At operation 116, the authentication server 106 may associate the user 102 with the device 104. Associating the user 102 with the device 104 may include setting one or more bits in a memory accessible by the authentication server 106 to indicate that the user 102 has sufficient permissions to access at least some functionality of the device 104. The registration process ends at operation 116, and the verification process begins at operation 118, where the user 102 performs non-authentication operations with the device 104. The separation between the registration and verification processes is indicated by the dashed line 133. The non-authentication operations 118 were previously discussed with respect to the user registration communication 112.
[0041] During the performance of the non-authentication operation 118, at operation 120, the device 104 may collect biometric data of the user 102. The biometric data collected at operation 120 may include data provided in the user registration communication 112, 114. Operation 120 allows the device 104 to perform user authentication without the user 102 being aware of the authentication. This is sometimes referred to herein as "seamless".
[0042] The device 104 may provide a device verification communication 122 to the authentication server 106. The device verification communication 122 may include device data, such as data provided in the device registration communication 108 or data derived from data in the device registration communication 108. For example, the data in the device verification communication 122 may include data from the device registration communication 108 that is concatenated, combined via some mathematical technique, encrypted via an encryption key, such as may be derived from the data or shared with the authentication server 106, and the like.
[0043] Authentication server 106 may provide server authentication communication 124 to device 104. Authentication server authentication communication 124 may include authentication server data, such as data provided in server registration communication 110 or data derived from data in server registration communication 110. For example, the data in server authentication communication 124 may include data from server registration communication 110 that is concatenated, combined via some mathematical technique, encrypted via an encryption key, such as may be derived from the data or shared with device 104, and the like.
[0044] Device authentication communication 122 and server authentication communication 124 may sometimes be referred to as a "two-way handshake". Communications 122, 124 are used to mutually authenticate device 104 and server 106. The two-way handshake may include encrypted communication of device data or server data. The two-way handshake may include the derivation of encryption keys or decryption keys, such as may be based on data provided in registration communications 108, 110.
[0045] The device 104 or the authentication server 106 may provide a result communication 126 indicating whether the two-way handshake was successful or failed. Although the device verification communication 122, the server verification communication 124, and the result communication 126 are shown as occurring after operations 118 and 120, some embodiments may include the device verification communication 122, the server verification communication 124, and the result communication 126 before operation 118.
[0046] User authentication communications 128 may be provided from device 104 to server 106. User authentication communications 128 may include biometric data collected by device 104. The biometric data may include the biometric data collected at operation 120. User authentication communications 128 may be used to verify that user 102 has sufficient authority to access at least some functionality of device 104.
[0047] Authentication server 106 may compare the biometric data from user verification communication 128 with the biometric data of the user in authentication data 107. If authentication data 107 includes biometric data that is sufficiently similar to the biometric data in user verification communication 128, and user 102 is associated with device 104, such as at operation 116, authentication may be successful. In such examples, authentication server 106 may indicate to device 104 via result communication 130 that the authentication has been successful. If the biometric data is not close enough to the biometric data in authentication data 107, or device 104 is not associated with user 102 in authentication data 107, authentication server 106 may indicate to device 104 via result communication 130 that the authentication has failed. In this case, device 104 may refrain from allowing user 102 to access its functionality. In some embodiments, device 104 may issue result communication 132 to user 102 indicating whether the authentication was successful or failed. Result communication 132 may be a visual, audible, vibrational, tactile, or other signal that conveys whether the authentication was successful or failed.
[0048] Figure 2 A communication diagram of another embodiment of other communications between items of seamless authentication system 200 is shown by way of example. System 200 includes the same items as system 100. The difference between systems 100 and 200 is that in system 200, device 104 and authentication server 106 perform a verification process handshake before the user performs a non-authentication operation with the device at operation 118. The registration process of system 200 may be the same as the registration process of system 100.
[0049] More specifically, the handshake including device authentication communication 122, server authentication communication 124, and result communication 126 occurs before operation 118. This allows user 102 to operate device 104 with less functionality lag, at least because user 102 does not have to wait for the handshake operation to pass after performing operation 118.
[0050] As in system 100, device 104 may provide device verification communications 122 to authentication server 106. Device verification communications 122 may include device data, such as data provided in device registration communications 108 or data derived from data in device registration communications 108. For example, data in device verification communications 122 may include data from device registration communications 108 that is concatenated, combined via some mathematical technique, encrypted via an encryption key, such as may be derived from the data or shared with authentication server 106, and the like.
[0051] Authentication server 106 may provide server authentication communication 124 to device 104. Authentication server authentication communication 124 may include authentication server data, such as data provided in server registration communication 110 or data derived from data in server registration communication 110. For example, the data in server authentication communication 124 may include data from server registration communication 110 that is concatenated, combined via some mathematical technique, encrypted via an encryption key, such as may be derived from the data or shared with device 104, and the like.
[0052] Device authentication communication 122 and server authentication communication 124 may sometimes be referred to as a "two-way handshake". Communications 122, 124 are used to mutually authenticate device 104 and server 106. The two-way handshake may include encrypted communication of device data or server data. The two-way handshake may include the derivation of encryption keys or decryption keys, such as may be based on data provided in registration communications 108, 110.
[0053] The device 104 or the authentication server 106 may provide a result communication 126 indicating whether the two-way handshake was successful or failed. Although the device verification communication 122, the server verification communication 124, and the result communication 126 are shown as occurring after operations 118 and 120, some embodiments may include the device verification communication 122, the server verification communication 124, and the result communication 126 before operation 118.
[0054] Similar to system 100, during the performance of non-authentication operation 118, device 104 may collect biometric data of user 102 at operation 120. The biometric data collected at operation 120 may include data provided in user registration communications 112, 114. Operation 120 allows device 104 to perform user authentication without user 102 being aware of the authentication. This is sometimes referred to herein as "seamless".
[0055] User authentication communications 128 may be provided from device 104 to server 106. User authentication communications 128 may include biometric data collected by device 104. The biometric data may include the biometric data collected at operation 120. User authentication communications 128 may be used to verify that user 102 has sufficient authority to access at least some functionality of device 104.
[0056] Authentication server 106 may compare the biometric data from user verification communication 128 with the biometric data of the user in authentication data 107. If authentication data 107 includes biometric data that is sufficiently similar to the biometric data in user verification communication 128, and user 102 is associated with device 104, such as at operation 116, authentication may be successful. In such examples, authentication server 106 may indicate to device 104 via result communication 130 that the authentication has been successful. If the biometric data is not close enough to the biometric data in authentication data 107, or device 104 is not associated with user 102 in authentication data 107, authentication server 106 may indicate to device 104 via result communication 130 that the authentication has failed. In this case, device 104 may refrain from allowing user 102 to access its functionality. In some embodiments, device 104 may issue result communication 132 to user 102 indicating whether the authentication was successful or failed. Result communication 132 may be a visual, audible, vibrational, tactile, or other signal that conveys whether the authentication was successful or failed.
[0057] Figure 3 A schematic diagram of an embodiment of a system 300 for indirect user 102, device 104A, 104B, or authentication server 106 registration and verification is shown by way of example. Devices 104A, 104B illustrate specific instances of device 104. The suffix means that device 104A is different from device 104B and its components are similar to the same numbered components without the suffix.
[0058] Using system 300, user 102 may register with authentication server 106, such as by having device 104A issue a user registration communication similar to user registration communication 114. Registration communication 114 may be used to associate user 102 with device 104B in authentication data 107. User 102 may then use device 104B. Device 104B may interact with authentication server 106 to perform a registration or authentication process, such as regarding Figure 1-2 and Figure 4-5 Discussed.
[0059] Figure 4A diagram of an embodiment of a method 400 for seamless authentication is shown by way of example. The method 400 as shown includes, at operation 402, generating biometric data by the device in response to a non-authentication operation performed by a user using the device; at operation 404, providing the generated biometric data to an authentication server; and at operation 406, allowing or denying the user access to the functionality of the device. Operation 402 may be performed by a transducer of the device. Non-authentication operations may include operations performed by the user that are not used for user authentication with the device, such as the user picking up the device, placing the device on their wrist, etc. Non-authentication operations may include operations that occur in normal use of the device, such as those just mentioned.
[0060] Method 400 may include, wherein the authentication server is registered with the device and authenticated by the device, and the device is registered with the authentication server and authenticated by the authentication server. Operation 406 may include allowing the user to access the functionality of the device, and may occur in response to a result communication from the authentication server indicating that the user was authenticated. Operation 406 may include denying the user access to the functionality of the device, and may occur in response to a result communication from the authentication server indicating that the user was authenticated. The result communication provided at operation 406 may indicate whether the biometric data matches the biometric data of the authentication server and whether the user is associated with the device (in the authentication server).
[0061] The method 400 may also include providing a device registration communication to the authentication server to register the device with the authentication server, the device registration communication including data to be used in the two-way authentication process. The method 400 may also include receiving an authentication server registration communication from the authentication server, the authentication server registration communication including authentication server data to be used in the two-way authentication process. The two-way authentication process may include verifying that the authentication server data matches the authentication server data in the memory.
[0062] The method 400 may also include associating the authentication server identifier with the authentication server address. The authentication server identifier may include authentication server data or be derived from authentication server data. The method may also include providing a user registration communication to the authentication server, the user registration communication including user registration data for generating a unique user identifier.
[0063] Figure 5A diagram of an embodiment of a method 500 for seamless authentication is shown by way of example. The method 500 as shown includes registering a device with an authentication server at operation 502; registering the authentication server with the device at operation 504; registering a user with the authentication server at operation 506; performing authentication of the user, the device, and the authentication server at operation 508; and allowing or denying access to functionality of the device (based on the results of the authentication at operation 506) at operation 510. Operation 502 may include receiving or generating a device identification. Operation 504 may include receiving or generating an authentication server identification. Operation 506 may include receiving or generating a user identification.
[0064] Operation 508 may be performed in response to the device detecting that the user has performed a specified action using the device. Operation 508 may include verifying, through communication between the device and an authentication server, at least two of the following identities: (i) a device identification, (ii) an authentication server identification, (iii) a corresponding user identification, and (iv) the corresponding user identification associated with the device identification. Operation 510 may include denying the user action on the functionality of the device in response to any of the at least two identities failing to verify. Operation 510 may include granting the user access to the functionality of the device in response to all of the at least two identities being verified.
[0065] Operation 504 may include receiving a unique authentication server identifier from an authentication server and associating the authentication server identifier with an authentication server address. Operation 506 may include providing, by the device, biometric data of the user to the authentication server. The biometric data may indicate facial features, wrist prints, or palm prints of the user. The biometric data may be captured by the device. The biometric data may be captured by another device and provided to the authentication server. The specified action may include performing a device operation required for a non-authentication operation using the device, and capturing biometric data during the performance of the operation. The specified action may include closing a visor of the device, picking up the device, or positioning the device on the wrist of the user.
[0066] Figure 6 A block diagram of an example of a device 600 is shown by way of example, on which any of the one or more processes (eg, methods) discussed herein may be performed. The device 600 (eg, a machine) may be operable to perform Figure 1-5In some embodiments, the device 104, 104A-104B, the authentication server 106, the processing circuit 101, 103A-103B, 109, the communication circuit 111, 111A-111B may include one or more of the components of the device 600. In some examples, the device 600 may operate as a standalone device or may be connected (e.g., networked) to one or more components, such as the device 104A-104B or the authentication server 106. The processing circuit 101, 103A-103B or the communication circuit 111, 111A-111B may include one or more of the items of the device 600, or the device 600 may implement at least a portion of a middleware, cloud, distributed, or other solution to perform one or more of the methods discussed herein.
[0067] As described herein, embodiments may include logic or several components, modules or mechanisms, or may be operated on. A module is a tangible entity (e.g., hardware) that is capable of performing a specified operation when in operation. A module includes hardware. In one example, the hardware may be specifically configured to perform a specific operation (e.g., hardwired). In one example, the hardware may include a configurable execution unit (e.g., a transistor, a logic gate (e.g., combinational and / or state logic) or other circuit, etc.) and a computer-readable medium containing instructions, wherein the instructions configure the execution unit to perform a specific operation when in operation. Configuration may occur under the guidance of the execution unit or a loading mechanism. Therefore, when the device is in operation, the execution unit may be communicatively coupled to the computer-readable medium. In this example, the execution unit may be a user of more than one module. For example, under operation, the execution unit may be configured by a first instruction set to implement a first module at a point in time, and reconfigured by a second instruction set to implement a second module.
[0068] The device (e.g., computer system) 600 may include a hardware processor 602 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, a processing circuit (e.g., logic gates, multiplexers, state machines, gate arrays such as programmable gate arrays, arithmetic logic units (ALUs), etc., or any combination thereof), a main memory 604, and a static memory 606, some or all of which may communicate with each other via an interlocking device (e.g., a bus) 608. The device 600 may also include a display unit 610, an input device 612 (e.g., an alphanumeric keyboard), and a user interface (UI) Navigation device 614 (e.g., mouse). In one example, display unit 610, input device 612, and UI navigation device 614 may be a touch screen display. Device 600 may further include a storage device (e.g., drive unit) 616, a signal generating device 618 (e.g., speaker), and a network interface device 620. Device 600 may include an output controller 628, such as a serial (e.g., universal serial bus (USB), parallel or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., printer, card reader, etc.).
[0069] The storage device 616 may include a machine-readable medium 622 on which is stored one or more sets of data structures or instructions 624 (e.g., software) embodying or utilized by any one or more of the techniques or functionality described herein. The instructions 624 may also reside, completely or at least partially, within the main memory 604, within the static memory 606, or within the hardware processor 602 during execution of the instructions 624 by the device 600. In one example, one or any combination of the hardware processor 602, the main memory 604, the static memory 606, or the storage device 616 may constitute a machine-readable medium.
[0070] Although the machine-readable medium 622 is shown as a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database and / or associated caches and servers) configured to store one or more instructions 624. The term "machine-readable medium" may include any tangible medium capable of storing, encoding, or carrying instructions for execution by the device 600 and causing the device 600 to perform any one or more of the techniques (e.g., processes) of the present disclosure, or any tangible medium capable of storing, encoding, or carrying data structures used by or associated with such instructions. Thus, the term "machine-readable medium" should be considered to include, but is not limited to, solid-state memory and optical and magnetic media. Specific examples of machine-readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The machine-readable medium itself does not include signals.
[0071] The instructions 624 may also be transmitted or received over the communication network 626 using a transmission medium via the network interface device 620 using any of a number of transmission protocols (e.g., frame relay, Internet Protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), a mobile telephone network (e.g., a cellular network), a plain old telephone (POTS) network, and a wireless data network (e.g., a wireless network known as a wireless network). The Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of standards, known as ), IEEE 802.16 family of standards), IEEE 802.15.4 family of standards, peer-to-peer (P2P) networks, and the like. In one example, the network interface device 620 may include one or more physical jacks (e.g., Ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the communication network 626. In one example, the network interface device 620 may include multiple antennas for wireless communication using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technology. The term "transmission medium" should be deemed to include any intangible medium capable of storing, encoding, or carrying instructions for execution by the device 600, and includes digital or analog communication signals or other intangible media to facilitate the communication of such software.
[0072] Although the terms and expressions employed are used as terms of description rather than limitation, and it is not intended that the use of such terms and expressions exclude any equivalents of the features shown and described or portions thereof, it is recognized that various modifications within the scope of the embodiments of the present invention are possible. Therefore, although the present disclosure has been specifically disclosed through specific embodiments and optional features, modifications and variations of the concepts disclosed herein may be deduced by those of ordinary skill in the art, and such modifications and variations are within the scope of the embodiments of the present disclosure.
[0073] Additional Implementation
[0074] The present invention provides the following exemplary embodiments, the numbering of which should not be construed as designating importance:
[0075] Embodiment 1 includes a device comprising a memory, a processing circuit coupled to the memory, the processing circuit comprising a transducer for generating biometric data of a user of the device, the processing circuit performing operations comprising: generating biometric data of the user by the transducer in response to detecting that the user performs a non-authentication operation with the device, providing the biometric data to an authentication server for user verification, wherein the authentication server is registered with and verified by the device, and the device is registered with and verified by the authentication server, allowing the user access to functionality of the device in response to a result communication from the authentication server indicating that the user verification is passed, and denying the user access to functionality of the device in response to a result communication from the authentication server indicating that the user verification has failed.
[0076] In embodiment 2, embodiment 1 also includes wherein the result communication indicates whether the biometric data matches the biometric data of the authentication server and whether the user is associated with the device.
[0077] In embodiment 3, at least one of embodiments 1-2 further includes, wherein the operations further include providing a device registration communication to the authentication server to register the device with the authentication server, the device registration communication including data to be used in a two-way authentication process.
[0078] In embodiment 4, embodiment 3 also includes, wherein the operations further include receiving an authentication server registration communication from the authentication server, the authentication server registration communication including authentication server data to be used in the mutual authentication process.
[0079] In embodiment 5, embodiment 4 also includes, wherein the two-way authentication process includes verifying that the authentication server data matches the authentication server data in the memory.
[0080] In embodiment 6, at least one of embodiments 4-5 also includes, wherein the operation further includes associating the authentication server identifier with the authentication server address.
[0081] In embodiment 7, embodiment 6 also includes, wherein the authentication server identifier includes authentication server data or is derived from authentication server data.
[0082] In embodiment 8, at least one of embodiments 1-7 further includes, wherein the operations further include providing a user registration communication to an authentication server, the user registration communication including user registration data for generating a unique user identification.
[0083] Embodiment 9 includes a method performed by operation of the device of any one of embodiments 1-8.
[0084] Embodiment 10 includes a machine-readable medium (eg, a non-transitory machine-readable medium) including instructions that, when executed by a machine, cause the machine to perform the operations of the method of Embodiment 9.
[0085] Embodiment 11 includes an apparatus for performing the method of embodiment 9.
[0086] Embodiment 12 includes a method comprising registering a device with an authentication server, including receiving or generating a device identification; registering an authentication server with the device, including receiving or generating an authentication server identification and storing the authentication server identification in a memory of the device; registering a user with the authentication server, including receiving or generating a user identification including biometric data; in response to detecting that a user has performed a specified action using the device, verifying at least two of the following identities through communication between the device and the authentication server: (i) a device identification, (ii) an authentication server identification, (iii) a corresponding user identification, and (iv) a corresponding user identification associated with the device identification; in response to any one of the at least two identities failing to be verified, denying the user action on the functionality of the device; and in response to all of the at least two identities being verified, allowing the user access to the functionality of the device.
[0087] In Embodiment 13, Embodiment 12 may further include, wherein registering the device with the authentication server includes receiving a unique authentication server identifier from the authentication server and associating the authentication server identifier with an authentication server address.
[0088] In Embodiment 14, at least one of Embodiments 12-13 also includes, wherein registering the user with the authentication server includes providing, by the device, biometric data of the user to the authentication server.
[0089] In embodiment 15, embodiment 14 also includes, wherein the biometric data indicates a facial feature, a wrist print, or a palm print of the user.
[0090] In Example 16, at least one of Examples 14-15 further includes, wherein the biometric data is captured by the device.
[0091] In Example 17, at least one of Examples 14-16 also includes, wherein the biometric data is captured by another device and provided to the authentication server.
[0092] In Embodiment 18, at least one of Embodiments 12-17 also includes, wherein the specified action includes using the device to perform an operation with the device required for a non-authentication operation, and capturing biometric data during the performance of the operation.
[0093] In Example 19, Example 18 also includes, wherein the specified action includes closing a visor of the device, picking up the device, or positioning the device on a user's wrist.
[0094] Embodiment 20 includes a device configured to perform the method of any of Embodiments 12-19.
[0095] Embodiment 21 includes a machine-readable medium (eg, a non-transitory machine-readable medium) including instructions that, when executed by a machine, cause the machine to perform the operations of the method of at least one of Embodiments 12-20.
[0096] Embodiment 22 includes an apparatus for performing the method of at least one of Embodiments 12-21.
[0097] Embodiment 23 comprises a non-transitory machine-readable medium comprising instructions which, when executed by a device, cause the device to perform operations comprising: registering the device with an authentication server, comprising receiving or generating a device identification; registering the authentication server with the device, comprising receiving or generating an authentication server identification; registering one or more users with the authentication server, comprising receiving or generating user identifications, verifying each of the following by communicating with the authentication server: (i) a device identification, (ii) an authentication server identification, (iii) a user identification, and (iv) the corresponding user identification being associated with the device identification; in response to any one of (i) to (iv) failing to be verified, denying the user action on the functionality of the device; and in response to all of (i) to (iv) being verified, allowing the user to access the functionality of the device.
[0098] In Embodiment 24, Embodiment 23 also includes, wherein registering the device with the authentication server includes receiving a unique authentication server identifier from the authentication server and associating the authentication server identifier with an authentication server address.
[0099] In Example 25, at least one of Examples 23-24 also includes, wherein registering the user with the authentication server includes providing the user's biometric data to the authentication server by the device.
[0100] In Embodiment 26, Embodiment 25 also includes, wherein the biometric data indicates a facial feature, a wrist print, or a palm print of the user.
[0101] In Example 27, at least one of Examples 25-26 further includes, wherein the biometric data is captured by the device.
[0102] In Example 28, at least one of Examples 25-27 further includes, wherein the biometric data is captured by another device and provided to the authentication server.
[0103] In Example 29, at least one of Examples 23-28 also includes, wherein the specified action includes using the device to perform an operation with the device required for a non-authentication operation, and capturing biometric data during the performance of the operation.
[0104] In Example 30, Example 29 includes, wherein the specified action includes closing a visor of the device, picking up the device, or positioning the device on a user's wrist.
[0105] Embodiment 31 includes a device configured to perform the operations of any of Embodiments 23-30.
[0106] Embodiment 32 comprises a method comprising performing the operations of at least one of Embodiments 23-30.
[0107] Embodiment 33 includes means for performing the operations of at least one of Embodiments 23-30.
[0108] Embodiment 34 includes a system comprising: a device, the device including a memory; a device processing circuit, the device processing circuit including a transducer for generating biometric data of a user of the device, the device processing circuit performing a first operation, the first operation including: generating biometric data of the user by the transducer in response to detecting that the user performs a non-authentication operation with the device, providing the biometric data to an authentication server for user verification, wherein the authentication server is registered with the device and is verified by the device, and the device is registered with the authentication server and is verified by the authentication server, allowing the user to access functionality of the device in response to a result communication from the authentication server indicating that the user verification is successful, and in response to an indication from the authentication server that the user has been verified, The authentication server includes: a memory including authentication data stored thereon; and an authentication server processing circuit for performing a second operation, the second operation including: comparing the biometric data with second biometric data in the authentication data and providing a result communication indicating (i) the authentication is successful if (a) the biometric data matches the second biometric data and (b) the user is associated with the device in the authentication data, or (ii) the authentication is unsuccessful if (c) the biometric data does not match the second biometric data or (d) the user is not associated with the device in the authentication data.
[0109] In Embodiment 35, Embodiment 34 also includes, wherein the first operation further includes providing a device registration communication to the authentication server to register the device with the authentication server, the device registration communication including data to be used in a two-way authentication process.
[0110] In Embodiment 36, Embodiment 35 also includes, wherein the first operation further includes receiving an authentication server registration communication from the authentication server, the authentication server registration communication including authentication server data to be used in the mutual authentication process.
[0111] In Example 37, Example 36 also includes, wherein the two-way authentication process includes verifying that the authentication server data matches the authentication server data in the memory.
[0112] In Example 38, Example 37 also includes, wherein the first operation also includes associating the authentication server identifier with the authentication server address.
[0113] In Example 39, Example 38 also includes, wherein the authentication server identifier includes authentication server data or is derived from authentication server data.
[0114] In Embodiment 40, at least one of Embodiments 34-39 further includes, wherein the operation further includes providing a user registration communication to an authentication server, the user registration communication including user registration data for generating a unique user identification.
[0115] Embodiment 41 includes at least one machine-readable medium (eg, a non-transitory machine-readable medium) including instructions that, when executed by a machine, cause the machine to perform operations of a device of the system of at least one of Embodiments 34-39.
[0116] Embodiment 42 includes means for performing the operations of one or more of the devices of the system of at least one of Embodiments 34-39.
Claims
1. A device for an authentication process, the device comprising: Memory; A processing circuit coupled to the memory, the processing circuit including a transducer to generate biometric data of a user of the device, the processing circuit performing operations including the steps of: registering the device with an authentication server, including receiving or generating a device identification and providing the device identification to the authentication server; registering the authentication server with the device, including receiving or generating an authentication server identifier and storing the authentication server identifier in a memory of the device; registering a user with the authentication server, including receiving or generating a user identification including the biometric data, and storing the user identification in a memory of the authentication server; associating the user with the device at the authentication server; In response to detecting that the user has performed a specified action using the device, verifying, through communication between the device and the authentication server, at least two of the following identities: (i) the device identification, (ii) the authentication server identification, (iii) a corresponding user identification, and (iv) the corresponding user identification at the authentication server is associated with the device identification, wherein the specified action includes an operation of the device required to perform a non-authentication operation using the device, and the biometric data is captured during the performance of the operation; In response to any one of the at least two identities failing to authenticate, denying a user action on functionality of the device; and In response to all of the at least two identities being authenticated, the user is allowed access to the functionality of the device.
2. The device according to claim 1, wherein Registering the device with the authentication server includes receiving a unique authentication server identifier from the authentication server and associating the authentication server identifier with an authentication server address.
3. The device according to any one of claims 1 to 2, wherein: The registering the user with the authentication server includes: providing the biometric data of the user to the authentication server by the device.
4. The device according to claim 3, wherein The biometric data indicates a facial feature, a wrist print, or a palm print of the user.
5. The device according to claim 3, wherein The biometric data is captured by the transducer.
6. The device according to claim 1, wherein The specified action includes closing a visor of the device, picking up the device, or placing the device on the user's wrist.
7. A method for an authentication process, the method comprising: Registering a device with an authentication server, including receiving or generating a device identification and providing the device identification to the authentication server; registering the authentication server with the device, including receiving or generating an authentication server identifier and storing the authentication server identifier in a memory of the device; Registering a user with the authentication server includes receiving or generating a user identifier and storing the user identifier in a memory of the authentication server; associating the user with the device at the authentication server; In response to detecting by the device that the user has performed a specified action using the device, verifying, through communication between the device and the authentication server, at least two of the following identities: (i) the device identification, (ii) the authentication server identification, (iii) a corresponding user identification, and (iv) the corresponding user identification at the authentication server is associated with the device identification, wherein the specified action includes an operation of the device required to perform a non-authentication operation using the device, and the biometric data is captured during the performance of the operation; In response to any one of the at least two identities failing to authenticate, denying a user action on functionality of the device; and In response to all of the at least two identities being authenticated, the user is allowed access to the functionality of the device.
8. The method according to claim 7, wherein: Registering the device with the authentication server includes receiving a unique authentication server identifier from the authentication server and associating the authentication server identifier with an authentication server address.
9. The method according to any one of claims 7 to 8, wherein: The registering the user with the authentication server includes: providing the biometric data of the user to the authentication server by the device.
10. The method according to claim 9, wherein: The biometric data indicates a facial feature, a wrist print, or a palm print of the user.
11. The method according to claim 9, wherein: The biometric data is captured by the device.
12. The method according to claim 9, wherein: The biometric data is captured by another device and provided to the authentication server.
13. The method according to claim 7, wherein: The specified action includes closing a visor of the device, picking up the device, or placing the device on the user's wrist.
