Patent ID: 12249337

DETAILED DESCRIPTION

So that the manner in which the features and advantages of the embodiments of the systems and methods disclosed herein, as well as others that will become apparent, may be understood in more detail, a more particular description of embodiments of systems and methods briefly summarized above may be had by reference to the following detailed description of embodiments thereof, in which one or more are further illustrated in the appended drawings, which form a part of this specification. It is to be noted, however, that the drawings illustrate only various embodiments of the systems and methods disclosed herein and are therefore not to be considered limiting of the scope of the systems and methods disclosed herein as it may include other effective embodiments as well.

The present disclosure is generally directed to systems and methods for using or utilizing a bone conduction signal for continuous and/or active device authentication of a user non-intrusively. Such a system and method may include a computing device in signal communication with the wearable device. The computing device may include a waveform generator and/or instructions to generate a signal. The signal may include different messages or portions, such as a pilot portion, to indicate authenticity of a user (for example, based on a signature specific to a user's bone conduction pathway), and a token portion, to indicate authenticity of the signal (for example, to prevent authentication of tampered with or otherwise altered signals). The waveform generator and/or instructions may be configured to encrypt the message using one or more different encryption algorithms or instructions. For example, the computing device (such as, the waveform generator and/or instructions) may utilize a Rivest-Shamir-Adleman (RSA) algorithm to encrypt the signal. In other words, the computing device may encrypt the message using a public key and may decrypt a later received signal, as will be described below, using a privately shared key. In another embodiment, the wearable device may decrypt the message with the privately shared key. In yet another embodiment, other encryption algorithms or systems may be utilized, such as using a one-time key, a Diffie-Hellman key exchange, and/or other encryption algorithm or system as will be understood by one skilled in the art.

After the computing device encrypts the message, the message may be sent to the wearable device and/or a transmitter of the wearable device. The transmitter may include a speaker, bone conduction speaker, and/or other transmitter configured to transmit a signal as a bone conduction signal. The transmitter may be configured to transmit the encrypted signal as a bone conduction signal. The bone conduction signal may be transmitted as an inaudible message, an unnoticeable message, or a just noticeable message. For example, the bone conduction signal may be transmitted at a frequency inaudible to humans, such as ultra-low and/or ultra-high frequencies (such as, from about 16 kHz to about 48 kHz, from about 20 Hz to about 200 Hz, or at about ultrasound frequencies). In another embodiment, the bone conduction signal may be transmitted as a short-period acoustic signal patch to audible frequencies to achieve the non-intrusiveness. For example, time-frequency patterns with limited duration and bandwidth (such as, a short-duration-narrow-bandwidth time-frequency pattern), or smaller signals masked by a larger amplitude signal, even at audible frequencies (such as, via a psychoacoustic masking effect), may be utilized. Further, the transmitter may vary the frequency of the bone conduction signal each time an authentication request is received. In other words, each time the transmitter receives an encrypted signal, the transmitter may choose a different frequency from the last frequency used. Further still, the wearable device may include a plurality of transmitters. In such an embodiment, the each of the plurality of transmitters may choose different frequencies at which to transmit the bone conduction signal.

The wearable device may also include a receiver or a plurality of receivers. Each receiver may be located at an opposite end of a bone conduction pathway (for example, the receiver is positioned near a contralateral ear, while the transmitter is positioned near an ipsilateral ear) and/or proximal to the transmitter. Once the transmitter transmits the bone conduction signal, the bone conduction signal may travel along a bone conduction pathway specific to the user. The receiver may receive the signal. As a bone conduction signals travels along a bone conduction signal pathway, the bone conduction signal may pick up or include noise (for example, from movement of the user and/or ambient sound occurring nearby or proximal the user). The receiver or other circuitry of the wearable device may remove or cancel such noise (for example, by removing frequencies outside of the frequency chosen by the transmitter). The receiver may then transmit the bone conduction signal to the computing device. In an embodiment, the receiver and/or the wearable device may, prior to transmission to the computing device, decrypt the bone conduction signal.

The computing device may further be configured to or include circuitry configured to decrypt the bone conduction signal. The computing device may process the bone conduction signal (for example, filtering, segmenting, and/or normalizing the bone conduction signal). The processed bone conduction signal may then be decrypted, if not decrypted by the receiver or wearable device. The computing device may then analyze the bone conduction signal to generate or separate the pilot portion and token portion from the bone conduction signal. The token portion may be utilized to ensure that the message is authentic, while the pilot portion and/or the bone conduction signal itself may be utilized to determine that the user is authentic. Upon authentication of the bone conduction signal and the user, the computing device may transmit a signal to the wearable device indicating the authentication and, thus, allowing the user to utilize or to continue to utilize the wearable device.

In an embodiment, authentication may occur continuously, substantially continuously, and/or periodically (for example, after a preselected period of time). The authentication may occur during use of the wearable device. Additionally, authentication may be prompted by the user and/or the wearable device, for example, when a user initially wears the wearable device. In another embodiment, a user, upon initializing a wearable device, may provide various bone conduction signal samples to produce a bone conduction signal signature. Such an initialization may occur automatically and/or without user intervention, thus allowing a user to continue to use a wearable or mobile device without interruption or interference.

The wearable device, as described herein, may include earbuds, augmented reality (AR)/virtual reality (VR) devices, and/or other devices able to access a metaverse (for example, an immersive virtual reality platform). The systems and methods described herein may enable users to access specified user profiles, based on authentication. For example, two or more users sharing a wearable device may access corresponding personal settings upon wearing the wearable device (such as, based on the non-intrusive authentication). Thus, as different users wear the wearable device, the wearable device may display the wearer's personal settings and provide a seamless, personalized experience based on continuous and non-intrusive authentication. Further, if the wearable device is stolen or used by an unauthorized user, personal or private information may be protected, as the unauthorized user may not be able to access the personal settings of the other users.

Further, the authentication operation may tie or associate a user with a virtual character in the metaverse. Thus, a user may access their character from any wearable device. Additionally, even if a character is replicable, the user's identity is preserved for sensitive and personal application/data (for example, account information; and/or financial information, such as for online shopping/trading; among other sensitive and personal application/data, as will be understood by one skilled in the art). Further still, the systems and methods described herein may be utilized to continuously provide authentication for users in a classroom, teaching, and/or testing setting. Thus, each user's identity is authenticated continuously, without disrupting any of the users in such a setting, ensuring all participants are accounted.

As noted, authentication may occur continuously and/or actively. The computing device and/or the wearable device may prompt authentication of the user without any user interaction and/or intrusion at various intervals or periods or substantially continuously. The computing device may further use the continuous authentication operations to update a user's bone conduction signal signature.

FIG.1A,FIG.1B,FIG.1C, andFIG.1Dare block diagrams of systems to authenticate a user, according to an embodiment of the present disclosure. The system100ofFIG.1Amay illustrate, at a high level, the interaction between the wearable device106and a computing device102to automatically and/or substantially continuously authenticate a user to utilize the wearable device106without user interaction and/or intrusion (for example, to authenticate a user to enable the user to perform one or more functions, including, but not limited to, operating a drone, playing music or videos, accessing user data or information, and/or performing smart home functions, among other operations or functions). The system100may include a wearable device106and a computing device102. The term “computing device” is used herein to refer to any one or all of servers, virtual computing device or environment, desktop computers, personal data assistants (PDAs), laptop computers, tablet computers, smart books, palm-top computers, personal computers, smartphones, wearable devices (such as headsets, earbuds, smartwatches, or the like), and similar electronic devices equipped with at least a processor and any other physical components necessarily to perform the various operations described herein. Devices such as smartphones, laptop computers, tablet computers, and wearable devices are generally collectively referred to as mobile devices. In an embodiment, rather than a wearable device106, the computing device102may connect to a mobile device for authentication purposes.

The term “server” or “server device” is used to refer to any computing device capable of functioning as a server, such as a master exchange server, web server, mail server, document server, or any other type of server. A server may be a dedicated computing device or a server module (for example, an application) hosted by a computing device that causes the computing device to operate as a server. A server module (for example, a server application) may be a full function server module, or a light or secondary server module (for example, light or secondary server application) that is configured to provide synchronization services among the dynamic databases on computing devices. A light server or secondary server may be a slimmed-down version of server type functionality that can be implemented on a computing device, such as a smart phone, thereby enabling it to function as an Internet server (for example, an enterprise e-mail server) only to the extent necessary to provide the functionality described herein.

As used herein, a “non-transitory machine-readable storage medium” may be any electronic, magnetic, optical, or other physical storage apparatus to contain or store information such as executable instructions, data, and the like. For example, any machine-readable storage medium described herein may be any of random access memory (RAM), volatile memory, non-volatile memory, flash memory, a storage drive (such as, hard drive), a solid state drive, any type of storage disc, and the like, or a combination thereof. The memory may store or include instructions executable by the processor.

As used herein, a “processor” or “processing circuitry” may include, for example one processor or multiple processors included in a single device or distributed across multiple computing devices. The processor (such as, processor circuitry124shown inFIG.1D) may be at least one of a central processing unit (CPU), a semiconductor-based microprocessor, a graphics processing unit (GPU), a field-programmable gate array (FPGA) to retrieve and execute instructions, a real time processor (RTP), other electronic circuitry suitable for the retrieval and execution instructions stored on a machine-readable storage medium, or a combination thereof.

The computing device102may include a processor and memory. The computing device102may further include instructions (for example, instructions stored in memory and executable by the processor), circuitry, and/or engines. In an embodiment, the computing device102may include a waveform generator104, a decryption engine112, and an authentication engine114. Further, the computing device may be in signal communication with the wearable device106or another computing device and/or mobile device. The wearable device106(or other computing device and/or mobile device) may include one or more transmitters108and one or more receiver110. Further, the wearable device106(or other computing device and/or mobile device) may include communications circuitry116.

In an embodiment, the waveform generator104of the computing device102may be configured to generate a message. The message may comprise a pilot portion and a token portion. The pilot portion may comprise symbols. The pilot portion may include known sequences used to measure the bone conduction signal and/or a sequence submitted by a user during an initiation. Further, the pilot portion may be randomly chosen from a given set (for example, the set comprising data and/or symbols corresponding to an initial input, initialization, and/or additional inputs verified and/or confirmed as being from a corresponding user). The token portion may include data corresponding to one or more of a user ID, a time stamp, or a random selection of bits.

The waveform generator104may further be configured to encrypt the message. In an embodiment, the waveform generator104may encrypt the token portion or the pilot portion, rather the entire message (for example, the pilot portion and the token portion). The waveform generator104may use a number of different encryption algorithms, for example a RSA algorithm, Diffie-Helman algorithm, or other encryption algorithms, as will be understood by one skilled in the art. Since the computing device may encrypt and then decrypt the message (such as, after the message is received back from the wearable device), a single key may be used. However, as noted, other algorithms may be utilized such as RSA (for example, the computing device102may access a public key for encryption and include or store a private key to decrypt the message or portion of the message). Once the message or portion of the message is encrypted, the waveform generator104may be configured to transmit the encrypted message to the wearable device106.

The wearable device106may be configured to receive the encrypted message at the transmitter108and/or the communications circuitry116of the wearable device106. The wearable device106may include, as noted, one or more transmitters. The transmitter108may transmit the encrypted message as an inaudible, substantially inaudible, unnoticeable, or just noticeable (or some combination thereof) bone conduction signal. In other words, the encrypted message may be transmitted via the transmitter108without interaction from the user and/or interruption of use of the wearable device106. The bone conduction message may be transmitted at a low frequency and/or a high frequency. The frequency of the transmitted message may vary each time an operation is undertaken. The frequency may be at about 16 kHz to about 48 kHz, about 48 kHz, about 20 Hz to about 200 Hz, and/or at an ultrasound frequency. The frequency of transmission may be determined based on user comfort and experience (for example, limited, minute, and/or no use interruption). As noted, the bone conduction signal may be transmitted as a short-period acoustic signal patch to audible frequencies to achieve the non-intrusiveness. For example, time-frequency patterns with limited duration and bandwidth (such as, a short-duration-narrow-bandwidth time-frequency pattern), or smaller signals masked by a larger amplitude signal, even at audible frequencies (such as, via a psychoacoustic masking effect), may be utilized. In an embodiment, the transmitter108may include speakers, in-ear speakers, bone conduction speakers, and/or a speaker capable of fitting within a user's ear or ear canal and configured to transmit the bone conduction signal. In another embodiment, if the wearable device includes at least two transmitters, then each transmitter may transmit the bone conduction signal at different or the same frequencies. Further, for subsequent authentication processes, each transmitter may be configured to transmit the bone conduction signal at a frequency different from the previously utilized frequency.

The wearable device106may include one or more receivers (for example, receiver110). The receiver110may be configured to receive an inaudible, substantially inaudible, unnoticeable, or just noticeable (or some combination thereof) bone conduction signal119. The bone conduction signal119may be received via direct and/or crosstalk bone conduction channels (for example, within a user's ear canal and/or through a user's bone conduction pathway). The receiver110may be configured to remove noise (for example, noise based on user movement, such as footsteps, arm movement, jaw movement, neck movement, dental articulation, and/or any other movement by the user; noise based on user communication, speech, and/or respiration; and/or noise based on ambient sound of a user's environment such as speech by others, music, and/or background noise; among other noise, as will be understood by one skilled in the art) from a received bone conduction signal119. The noise may be reduced, canceled, or removed based on different frequencies outside of the expected or actual frequency the bone conduction signal119is transmitted at. The bone conduction signal119may then be transmitted (for example, via the receiver110, via the transmitter108, and/or other communications circuitry) to the computing device102. The computing device102may be configured to receive the bone conduction signal from the receiver110. In an embodiment, the receiver110may be an in-ear microphone or in-ear bone conduction microphone.

In an embodiment, prior to transmitting the bone conduction signal119via the transmitter108to the receiver110, the wearable device106may ensure or check that the wearable device105is properly worn by a user. In another embodiment, the wearable device106may determine whether the receiver110and the transmitter108are properly worn prior to transmission of the bone conduction signal119. In an embodiment, the transmitter108and/or the receiver110may be active components. In other words, the transmitter108may actively search and/or scan for new bone conduction signals to transmit. Further, the receiver110may actively listen and/or scan for the transmitted bone conduction signal from the transmitter108.

As noted, the computing device102may include a decryption engine112. The decryption engine112may receive the bone conduction signal. In an embodiment, the wearable device106may include encryption/decryption circuitry. In such examples, the wearable device106may decrypt (for example, using a private key known by the computing device102and the wearable device106) the receive bone conduction signal prior to transmission via the transmitter108to the receiver110. The wearable device106may then encrypt (for example, via a public key accessible by the wearable device106) the denoised bone conduction signal from the receiver110prior to transmission to the computing device102.

Upon reception of the bone conduction signal by the computing device102, the decryption engine112may be configured to process the bone conduction signal. Processing the bone conduction signal may include filtering the bone conduction signal (for example, passing the bone conduction signal through a low-pass filter to remove noise generated by human motion and/or a Wiener filter to remove noise), segmenting the bone conduction signal (for example, removing non-relevant portions of the received bone conduction signal, and/or normalizing or synchronizing the bone conduction signal. Normalizing or synchronizing may include adjusting the signal based on a time delay between the received bone conduction signal and the transmitted bone conduction signal. The decryption engine112may, after processing the bone conduction signal, decrypt the bone conduction signal. Decryption may include, as noted, a RSA algorithm or other encryption/decryption algorithm or instructions. For example, the decryption engine112may obtain from memory of the computing device102or may include a private key. The private key may be shared between the wearable device106and the computing device102upon initialization. Further, each other wearable device may share a different private key with the computing device102. The decryption engine112may use the private key to decrypt the encrypted bone conduction signal.

The computing device102may include an authentication engine114. The authentication engine114may be configured to analyze the decrypted bone conduction signal. Such analysis may include extracting features from the bone conduction signal (for example, via neural network or other trained machine learning model), embedding the extracting features in a vector or bone conduction signal vector, generating a score by applying the vector to a classifier or other machine learning module, and comparing the score to a threshold score to indicate whether the user is authentic or not. In other words, the score may indicate whether the bone conduction signal is from a known user, an initialized user, or the user associated with the bone conduction signal. The authentication engine114, in another embodiment, may compare the bone conduction signal and/or the pilot portion of the bone conduction signal to known values (for example, one or more known initialization values from a user) to determine whether the user is authentic or is verified. The authentication engine114may further verify the bone conduction signal authenticity (for example, not a fake or spoofed bone conduction signal) using the token portion included in the bone conductions signal, for example, by comparing the token portion to a user identification (ID), a device ID, a timestamp, or random bits originally generated by the computing device102and/or waveform generator104.

Turning toFIG.1B, the wearable device106may include at least two transmitters120A,120B and at least two receivers118A,118B. The bone conduction signal may be transmitted by one or more of the two transmitters120A,120B. Further, each of the two transmitters120A,120B, may utilize different frequencies to transmit the bone conduction signals. The two receivers118A,118B may receive the bone conduction signal from one or more of the two transmitters120A,120B (for example, directly or via a cross-talk pathway). In such examples, the computing device102may indicate, via a signal included with the encrypted message, which of the at least two transmitters120A,120B to transmit from and which of the at least two receivers118A,118B to receive the corresponding bone conduction signals. Further, the computing device102may indicate or specify that the two receivers118A,118B may receive the bone conduction signal via direct or crosstalk bone conduction signals or, in other words, which of the two transmitters120A,120B to receive the bone conduction signal from. The two receivers118A,118B may determine which bone conduction signal is from which of the two transmitters120A,120B based on one or more of time received or an indicator included in the bone conduction signal. Further, the two transmitters120A,120B chosen and the two receivers118A,118B chosen may be different for each subsequent authentication process. As authentication may occur continuously or substantially continuously, various different and random combinations may be utilized to further enhance security and prevent fake users and/or spoofing.

Turning toFIG.1C, the wearable device106may include an authentication circuitry122. The authentication circuitry122may be configured to receive user authentication from the computing device102. In another embodiment, the authentication circuitry122may be configured to receive a request for authentication from the user (for example, via a physical, textual, or verbal response). In another embodiment, the authentication circuitry122may include a key. The key (for example, a private key) may be used to decrypt the bone conduction message. In another embodiment, the authentication circuitry122may be configured to encrypt the bone conduction signal. In another example, the key may be securely exchanged with the computing device102(for example, via a Diffie-Hellman exchange).

After authentication of a user, the user may be able to utilize the wearable device106, access a specified set of data, and/or utilize a corresponding or associate mobile device (for example, the mobile device including or in communication with the wearable device106). Such operations described above may be performed on a continuous basis, a substantially continuous basis, and/or after a specified or preselected time period has lapsed. Such a basis (for example, continuous or periodic) may be based on or defined by use of the wearable device106by the user. In other words, authentication operations may continue while the wearable device106is in use.

In another embodiment, the score generated that indicates user authenticity may further indicate partial authentication. In such an embodiment, partial authentication may be defined by a score in a specified range. The user may be able to utilize basic functionality of the wearable device106until the user is authenticated or indicates authenticity in another way (for example, via two-factor authentication via another form of communication).

In another embodiment, the computing device106may utilize characteristic of a received bone conduction signal from the wearable device to determine user authenticity. For example, the computing device106may extract features (such as, via a neural network or other machine learning model) from the bone conduction signal itself. The computing device106may then add the extracted features to an embeddings or vector. The computing device106may compare or generate a score for the embeddings or vectors using a known bone conduction signal from the user, which may be indicated by the pilot portion of the message. As noted herein, if the score exceeds a threshold, then the computing device106may authenticate the user.

Turning toFIG.1D, the system101or apparatus may include processing circuitry124, memory126, communications circuitry134, waveform generator circuitry128, decryption circuitry136, and authentication circuitry132, each of which will be described in greater detail below. While the various components are illustrated inFIG.1Das being connected with processing circuitry124, it will be understood that the system101or apparatus may further comprise a bus (not expressly shown inFIG.1D) for passing information amongst any combination of the various components of the system101or apparatus. The system101or apparatus further may include programming or instructions configured to execute various operations described herein, such as those described above in connection withFIGS.1A through1Band below in connection withFIGS.2through6B.

The processing circuitry124(and/or co-processor or any other processor assisting or otherwise associated therewith) may be in communication with the memory126via a bus for passing information amongst components of the system101or apparatus. The processing circuitry124may be embodied in a number of different ways and may, for example, include one or more processing devices configured to perform independently. Furthermore, the processing circuitry124may include one or more processors configured in tandem via a bus to enable independent execution of software instructions, pipelining, and/or multithreading. The use of the term “processor” may be understood to include a single core processor, a multi-core processor, multiple processors of the system101or apparatus, remote or “cloud” processors, or any combination thereof.

The processing circuitry124may be configured to execute software instructions stored in the memory126or otherwise accessible to the processing circuitry124. In some cases, the processing circuitry124may be configured to execute hard-coded functionality. As such, whether configured by hardware or software methods, or by a combination of hardware with software, the processing circuitry124represents an entity or device (for example, an element that can be physically embodied in circuitry) capable of performing operations according to various embodiments of the present disclosure while configured accordingly. Alternatively, as another example, when the processing circuitry124is embodied as an executor of software instructions, the software instructions may specifically configure the processing circuitry124to perform the algorithms and/or operations described herein when the software instructions are executed.

The memory126may be a non-transitory machine readable storage medium and may include, for example, one or more volatile and/or non-volatile memories. In other words, for example, the memory126may be an electronic storage device (for example, a computer readable storage medium). The memory126may be configured to store information, data, content, applications, software instructions, or the like, for enabling the apparatus to carry out various functions in accordance with example embodiments contemplated herein.

The communications circuitry134or communications interface may include at least one device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and/or transmit data from/to a network and/or any other device, wearable device, mobile device, circuitry, or module in communication with the system101or apparatus. In this regard, the communications circuitry134may include, for example, a network interface for enabling communications with a wired or wireless communication network. For example, the communications circuitry134may include one or more network interface cards, antennas, buses, switches, routers, modems, and supporting hardware and/or software, or any other device suitable for enabling communications via a network. Furthermore, the communications circuitry134may include the processing circuitry124for causing transmission of such signals to a network or for handling receipt of signals received from a network.

The system101or apparatus generally will include a waveform generator circuitry128, configured to generate a message, encrypt the message, and transmit the message to a wearable device. The waveform generator circuitry128may generate a message based on data corresponding to a user to be authenticated. The data may include previously stored data relating to initiation of the wearable device by the user. The data may also include a user ID, a device ID, a timestamp, and/or a random number of bits. The waveform generator circuitry128may be configured to encrypt the message. Such an encryption may be performed by encryption/decryption instructions or algorithms in the waveform generator circuitry128and/or stored in memory126. The waveform generator circuitry128may utilize a public key or a one-time key to encrypt the message. The waveform generator circuitry128may also transmit the encrypted message to the wearable device (for example, via the communications circuitry134).

The system101or apparatus may include a decryption circuitry130configured to decrypt a received bone conduction signal (for example, received from a wearable device) and/or process the received bone conduction signal. The decryption circuitry130may include or may access in memory126a private key or the one-time generated key to decrypt the encrypted bone conduction signal. Further, the decryption circuitry130may process the decrypted bone conduction signal. The processing may include filtering the bone conduction signal (for example, passing the bone conduction signal through a low-pass filter to remove noise generated by human motion and/or a Wiener filter to remove noise), segmenting the bone conduction signal (for example, removing non-relevant portions of the received bone conduction signal, and/or normalizing the bone conduction signal. Normalization may include adjusting the decrypted bone conduction signal based on a timestamp included in the bone conduction signal. The bone conduction signal may be processed further using various other techniques as will be understood by one skilled in the art.

The system101or apparatus may include a authentication circuitry132configured to authenticate and verify the bone conduction signal and send the authentication to a wearable device. The authentication circuitry132may, to begin authentication and verification, analyze the bone conduction signal. Such analysis may include extracting features from the bone conduction signal or a portion of the bone conduction signal via a model or classifier (for example, such as a trained neural network). The extracted features may then be embedded in a vector and the vector may be applied to another model or classifier to generate a score. The score may indicate user authenticity. Further, the score may indicate some level of authenticity below full authentication (for example, based on selected score range). Finally, after decryption, the authentication circuitry132may verify portions of the bone conduction signal based on user and/or device data. The authentication circuitry132may further be configured to transmit a user authentication signal to a wearable device.

FIG.2is a graphical representation200of user authentication over time204, according to an embodiment of the present disclosure. The graph may include a S axis202representing a time when various signals are received. For example, at “1”206, a new probe or bone conduction signal (for example, new probe212,214, and216) may be received at a wearable device. A computing device may perform authentication and send the results to the wearable device by time “T1”208. If authentication is received, then the user may continue to use the wearable device. However, if no response or authentication is received (for example, see no response218) at time “T2”, then the wearable device may provide partial access220to the wearable device (for example, use or access of limited data, and/or use of standard applications, among other limited uses and/or access). If no response is received at “T2”, the wearable device may prevent user access or use. As indicated in the graphical representation200, the authentication operation may be continuous or substantially continuous.

FIG.3is a block diagram of a system to authenticate a user336, according to an embodiment of the present disclosure. As an authentication process begins, s waveform generator302of an authentication server332may generate an inaudible or unnoticeable (or substantially inaudible or unnoticeable) probe signal at304. The waveform generator302may send the probe signal at306to an augmented reality (AR) or virtual reality (VR) device316or other computing device. A bone conduction speaker310of the AR/VR device316may play the probe signal at308. The probe signal may pass through an bone conduction pathway to pick up an ear biometric318at312and received and recorded at314by an in-ear mic315. The recorded response signal may be transmitted to the authentication server332at320. The authentication server332may then verify the bear biometric318and a token at322. Such verification may begin with feature extraction. Extracted features may then be compared to ear biometric templates at a verifier328(for example, the acquired ear biometric318may be compared to initial ear biometrics from a user336). If no ear biometric templates are stored, the authentication server332may enter an initialization phase and record the acquired biometric. Further, the authentication server332may request additional ear biometrics. If the ear biometric is updated and is different than the ear biometric template (for example, different, but not different enough to cause rejection of authentication), the authentication server332may save the ear biometric as a new template. In an example, as a user336changes over time (for example, gains or loses weight and/or changes physically in some other way), that user's336ear biometric may change.

If the ear biometric318is accepted, then the authentication server332may send an acceptance (or in some embodiments, a rejection) to the user336of the AR/VR device316. The authentication operation may occur at various times, such as time334A,334B, and up to334N. For each operation, the user's336ear biometric may be update or saved. In another embodiment, the authentication operation may be prompted by the user336. In an embodiment, the user336and/or the authentication server332may set the frequency of each authentication operation. Further, the authentication operation may be non-intrusive and active. The authentication server332may actively read a user's bilateral ear channel (for example, by transmitting, via a user device, a bone conduction signal to a receiver of the user device and receiving, from the receiver, the bone conduction signal at the authentication server332without user interaction and/or initiation). Further, the authentication server332may continuously request authentication and, based on any incremental changes to a bone conduction signal transmitted through the user's bilateral ear channel, may update the user's bone conduction signal signature (for example, a signature specific to a user's bone conduction pathway and/or various bone conduction signal samples utilized to produce a bone conduction signal signature).

During such operations the user336may not know or be aware that such an operation is occurring. In such embodiments, the probe signal may be played by the bone conduction speaker310as an inaudible signal (for example, at a frequency inaudible to humans), substantially inaudible signal, unnoticeable signal, or just unnoticeable signal (or some combination thereof). In another embodiment, the user336may disable authentication operations (for example, authentication no longer occurs unless prompted by the user336). In yet another embodiment, operation of the AR/VR device316may be automatically cause an authentication operation to occur (for example, authentication operations occur while the AR/VR device316is in use).

FIG.4is a graphical representation400of data insertion in subcarriers, according to an embodiment of the present disclosure. In an embodiment, pilot data404may be generated (for example, as symbols402) at a fixed length for each authentication operation. The pilot data404may be loaded along the direction of the growing subcarrier index. The pilot data404may fill an entire subcarrier index or bandwidth. Further, other data bits408may be modulated onto the remaining subcarrier indices. Modulation may include differential phase key shifting. The symbols may then be converted by inverse Fourier Transform (IFFT)410into the time domain waveform412. Thus, a message generated by a waveform generator may be processed such that the message may be sent or transmitted as a bone conduction signal.

FIG.5is a flow diagram of continuous, active, and/or non-intrusive user authentication, according to an embodiment of the present disclosure. It also will be understood that any of the FIGS. described herein may implement the method500, in particularFIGS.1A-1D and3. The method500may be included in one or more programs, protocols, or instructions loaded into memory of a computing device. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described blocks may be combined in any order and/or in parallel to implement the disclosed methods

At block502, a system may determine whether a wearable or mobile device is in use. The system may determine that the wearable or mobile device is in use via reception of a signal indicating use of the wearable or mobile device. Further, a user may indicate that the wearable or mobile device is in use. In yet another embodiment, while the wearable or mobile device is in use, the operations described in relation to method500may be continuously, substantially continuously, or periodically performed.

If the wearable or mobile device is in use, at block504, the system may generate a signal. The system may include a waveform generator. The waveform generator may choose pilot data from a set of previously stored data relating or corresponding to the user. The waveform generator may add the pilot data to a subcarrier index. The waveform generator may also choose token data. The token data may include a user ID, a device ID, a timestamp, or randomly generated bits. The token data may also be added to a subcarrier index.

After the signal is generated, at block506, the signal may be encrypted. The system may utilize one or more different encryption algorithms to encrypt the signal. For example, the system may retrieve a public key and encrypt the signal using the public key. The system may further generate a key and utilize the generated key to encrypt the signal. At block508, the encrypted signal may be modulated as communication symbols (for example, the random bits may be converted or modulated to communication symbols transferable as a bone conduction or audio signal).

At block510, the modulated encrypted signal may be sent or transmitted to one or more transmitters of the wearable or mobile device. The one or more transmitters may include bone conduction speakers configured to transmit the modulated encrypted signal as an inaudible signal, substantially inaudible signal, unnoticeable signal, or just unnoticeable signal (or some combination thereof). The one or more transmitters may be active components. The one or more transmitters may actively search and/or scan for the modulated encrypted signal and, upon reception of the modulated encrypted signal, automatically transmit the modulated encrypted. The one or more transmitters may be positioned within a user's ear canal. The one or more transmitters may transmit the bone conduction signal along a user's bone conduction pathway (for example, directly or via a cross-talk pathway) to one or more receivers. The one or more receivers may actively search, listen, and/or scan for the bone conduction signal and, upon reception of the bone conduction signal, automatically process the bone conduction signal and then send the processed bone conduction signal to the system. The one or more receivers may then transmit the bone conduction signal back to the system. Prior to such a transmission, the one or more receivers may denoise the bone conduction signal (for example, remove noise associated with user movement and/or ambient noise) and/or remove interference in the bone conduction signal. Thus, at block512, the system may receive a denoised bone conduction signal from the one or more receivers.

At block514, the system may demodulate the denoised bone conduction signal. The system may then, at block516, decrypt the demodulated bone conduction signal. The type of decryption utilized may be based on the type of encryption utilized. For example, if a public key was used to encrypt the signal, a private key may be utilized to decrypt the bone conduction signal. In another example, if a one-time key is utilized, then the one-time key may be used for decryption.

At block518, the system may verify the authenticity of a bone conduction signal based on the token portion of the bone conduction signal. If the token portion of the bone conduction matches the token portion of the original signal, then the system may verify that the bone conduction signal is authentic. At block520, if the system determines that the bone conduction signal is authentic, then the system may authenticate the user based on the bone conduction signal. In an embodiment, the system may utilize the pilot portion of the bone conduction signal to authenticate the user. In another embodiment, the system may utilize a combination of the pilot portion of the signal and characteristics of the received bone conduction signal. In such examples, if the characteristic of the received bone conduction signal match the pilot portion or other data stored in the system, then the system may authenticate the user. The system may transmit the authentication to the wearable or mobile device, thus enabling a user to continue to utilize the wearable or mobile device.

As noted, the method500may be iterated while the wearable or mobile device is in use and/or at various time intervals.

FIG.6AandFIG.6Bare flow diagram of continuous, active, and/or non-intrusive user authentication, according to an embodiment of the present disclosure. It also will be understood that any of the Figs. described herein may implement the method600, in particularFIGS.1A-1D and3. The method600may be included in one or more programs, protocols, or instructions loaded into memory of a computing device. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described blocks may be combined in any order and/or in parallel to implement the disclosed methods

At block602, a system may determine whether a wearable or mobile device is in use. The system may determine that the wearable or mobile device is in use via reception of a signal indicating use of the wearable or mobile device. Further, a user may indicate that the wearable or mobile device is in use. In yet another embodiment, while the wearable or mobile device is in use, the operations described in relation to method600may be continuously, substantially continuously, or periodically performed.

At block604, the system may determine whether a preselected time interval or period has lapsed. If the time period or interval has not lapsed, then system may determine whether the wearable or mobile device is still in use. Further, at block606, the system may determine or check whether a user authentication request was received. If the time period or interval has lapsed or if user authentication has been requested, then the system, at block608, may generate a signal. The system may include a waveform generator. The waveform generator may choose pilot data from a set of previously stored data relating or corresponding to the user. The waveform generator may add the pilot data to a subcarrier index. The waveform generator may also choose token data. The token data may include a user ID, a device ID, a timestamp, or randomly generated bits. The token data may also be added to a subcarrier index.

After signal generation, at block610, the signal may be encrypted. The system may utilize one or more different encryption algorithms to encrypt the signal. For example, the system may retrieve a public key and encrypt the signal using the public key. The system may further generate a key and utilize the generated key to encrypt the signal. At block612, the encrypted signal may be modulated as communication symbols (for example, the random bits may be converted or modulated to communication symbols transferable as a bone conduction or audio signal).

In an embodiment, the modulated encrypted signal may be sent or transmitted to one or more transmitters of the wearable or mobile device. The one or more transmitters may include bone conduction speakers configured to transmit the modulated encrypted signal as an inaudible signal, substantially inaudible signal, unnoticeable signal, or just unnoticeable signal (or some combination thereof). The one or more transmitters may be positioned within a user's ear canal. The one or more transmitters may transmit the bone conduction signal along a user's bone conduction pathway (for example, directly or via a cross-talk pathway) to one or more receivers. Thus, At block614, the system and/or wearable or mobile device may determine whether the modulated encrypted signal has been received at the wearable or mobile device. Further, the wearable or mobile device may determine whether the one or more transmitters of the wearable or mobile device are properly positioned or positioned within a user's ear canal. Further still, the wearable or mobile device may determine whether the one or more receivers of the wearable or mobile device are properly positioned or positioned within a user's ear canal.

At block616, the one or more transmitters may transmit the modulated encrypted signal as bone conduction signal. The bone conduction signal, as noted, may be recorded by the one or more receivers. In other words, at block618, the one or more receivers may receive the bone conduction signal. Further, at block620, the one or more receivers (or, in another embodiment, the system) may denoise the bone conduction signal. At block622, the system may receive the denoised bone conduction signal. At block624, the system may demodulate the denoised bone conduction signal.

At block626, the system may decrypt the demodulated bone conduction signal. The type of decryption utilized may be based on the type of encryption utilized. For example, if a public key was used to encrypt the signal, a private key may be utilized to decrypt the bone conduction signal. In another example, if a one-time key is utilized, then the one-time key may be used for decryption.

At block628, the system may verify the authenticity of a bone conduction signal based on the token portion of the bone conduction signal. If the token portion of the bone conduction matches the token portion of the original signal, then the system may verify that the bone conduction signal is authentic.

At block630, the system may extract features from the received bone conduction signal and/or the pilot portion of the signal. Feature extraction may be performed via a convolutional neural network (CNN), another neural network, or other trained machine learning model or classifier. The CNN may leverage an image-classification method to extract image-like feature maps from using a time-frequency analysis. At block630, the extracted features may be added or embedded in a bone conduction embedding or vector. At block634, the system may generate or produce a score based on the bone conduction embedding or vector. The score may be generated or produced based on application of the bone conduction embedding or vector to a classifier or model.

At block636, the system may determine if the score exceeds a threshold. If the score exceeds a threshold, then, at block638, the system may transmit user authentication to the wearable or mobile device. If the score does not exceed the threshold, then, at block640, the system may transmit a signal to the wearable or mobile device to deny access to the current user. At block642, the system may generate a notification to the user indicating a potential security threat. Such a notification may be transmitted via a secondary communication associated with the user (for example, a phone number, and/or email, among other secondary communications).

In some embodiments, some of the operations above may be modified or further amplified. Furthermore, in some embodiments, additional optional operations may be included. Modifications, amplifications, or additions to the operations above may be performed in any order and in any combination.

This application is related to U.S. Provisional Application No. 63/268,999, filed Mar. 8, 2022, titled “SYSTEMS AND APPARATUS FOR MULTIFACTOR AUTHENTICATION USING BONE CONDUCTION AND AUDIO SIGNALS,” U.S. Provisional Application No. 63/269,001, filed Mar. 8, 2022, titled “METHOD FOR MULTIFACTOR AUTHENTICATION USING BONE CONDUCTION AND AUDIO SIGNALS,” and U.S. Provisional Application No. 63/380,229, filed Oct. 19, 2022, titled “SYSTEMS AND METHODS FOR CONTINUOUS, ACTIVE, AND NON-INTRUSIVE USER AUTHENTICATION,” the disclosures of which are incorporated herein by reference in their entirety.

In the drawings and specification, several embodiments of systems and methods to provide two-way authentication for a user via a smart device or device and a wearable device have been disclosed, and although specific terms are employed, the terms are used in a descriptive sense only and not for purposes of limitation. Embodiments of systems and methods have been described in considerable detail with specific reference to the illustrated embodiments. However, it will be apparent that various modifications and changes can be made within the spirit and scope of the embodiments of systems and methods as described in the foregoing specification, and such modifications and changes are to be considered equivalents and part of this disclosure.