COMPUTERIZED SYSTEM AND METHOD FOR WEARABLE IDENTITY MANAGEMENT

Disclosed are systems and methods that provide a novel cross-session authentication framework that enables secure local and/or network sessions to be effectuated via biometric tracking via a wearable device (e.g., smart ring). In some implementations, when a user wearing a smart ring is authenticated with a first secure resource (e.g., a computer system such as a smart phone application associated with the smart ring), such authentication can be maintained and leveraged to access other resources that are separately being securely held. The smart ring, when properly worn, can monitor biometrics (e.g., vital signs) of a user, and based therefrom, determine if and/or when the smart ring is removed/manipulated from the user's finder. Until the smart ring is removed, the smart ring's confirmation of being worn by the user can be leveraged as an identification token that can enable the user access to other securely held information.

FIELD OF THE DISCLOSURE

The present disclosure is generally related to identity monitoring and management, and more particularly, to a decision intelligence (DI)-based computerized framework for automatically and dynamically managing the identity and authenticated activities of a user via a wearable device associated with the user.

BACKGROUND

Currently, mechanisms for accessing securely held resources are limited to user provided input, which can include, for example, a username/password, PINs, facial recognition, fingerprints, and the like. Indeed, at most, two-factor authentication (2FA) or multi-factor authentication (MFA) can involve a combination of authentication types which can provide added layers of protection.

SUMMARY OF THE DISCLOSURE

However, such techniques are still susceptible to malicious activity. That is, for example, passwords can be hacked, facial recognition systems can be spoofed, and regardless of the number of MFA layers, each layer can be readily exposed via a data breach.

To that end, according to some embodiments, as discussed herein, the disclosed systems and methods provide a cross-session authentication framework that enables secure local and/or network sessions to be effectuated via biometric tracking via a wearable device. According to some embodiments, when a user wearing a smart ring is authenticated with a first secure resource (e.g., a computer system such as a smart phone application associated with the smart ring, for example), such authentication can be maintained and leveraged to access other (or third party) resources that are separately being securely held. According to some embodiments, a smart ring, when properly worn, can monitor biometrics (e.g., vital signs) of a user, and based therefrom, determine if and/or when the smart ring is removed from the user's finder (e.g., or manipulated out of place from being worn correctly). Until the smart ring is removed (and/or according to other related criteria, for example, a time period, type of gesture, requested resource, type of user, and the like), the smart ring's confirmation of being worn by the user can be leveraged as an identification token that can enable the user access to other securely held information.

According to some embodiments, as discussed herein, the disclosed framework can operate by enabling a user to leverage authentication with a first secure system to access other securely held systems. In some embodiments, upon a user accessing a first system, a user's device (e.g., smart ring) is provided a secure session token, which can be stored in association with the device (e.g., in storage on the device and/or in a network accessible repository). In some embodiments, the token is capable of being provided to other securely held systems while the device is determined to have maintained association with the user. For example, upon receiving the token, the token remains valid as long as the user's smart ring remains worn by the user (e.g., on the same finger and hand as was established upon receiving the token). Thus, this effectively acts as an “open” session for the user device, for which confirmation of the user's identity can be proactively provided when requesting access to such systems.

According to some embodiments, a method is disclosed for a DI-based computerized framework for automatically and dynamically managing the identity and authenticated activities of a user via a wearable device associated with the user. In accordance with some embodiments, the present disclosure provides a non-transitory computer-readable storage medium for carrying out the above-mentioned technical steps of the framework's functionality. The non-transitory computer-readable storage medium has tangibly stored thereon, or tangibly encoded thereon, computer readable instructions that when executed by a device cause at least one processor to perform a method for automatically and dynamically managing the identity and authenticated activities of a user via a wearable device associated with the user.

In accordance with one or more embodiments, a system is provided that includes one or more processors and/or computing devices configured to provide functionality in accordance with such embodiments. In accordance with one or more embodiments, functionality is embodied in steps of a method performed by at least one computing device. In accordance with one or more embodiments, program code (or program logic) executed by a processor(s) of a computing device to implement functionality in accordance with one or more such embodiments is embodied in, by and/or on a non-transitory computer-readable medium.

DETAILED DESCRIPTION

For purposes of this disclosure, a “wireless network” should be understood to couple client devices with a network. A wireless network may employ stand-alone ad-hoc networks, mesh networks, Wireless LAN (WLAN) networks, cellular networks, or the like. A wireless network may further employ a plurality of network access technologies, including Wi-Fi, Long Term Evolution (LTE), WLAN, Wireless Router mesh, or 2nd, 3rd, 4thor 5thgeneration (2G, 3G, 4G or 5G) cellular technology, mobile edge computing (MEC), Bluetooth, 802.11b/g/n, or the like. Network access technologies may enable wide area coverage for devices, such as client devices with varying degrees of mobility, for example.

In short, a wireless network may include virtually any type of wireless communication mechanism by which signals may be communicated between devices, such as a client device or a computing device, between or within a network, or the like.

A client device may vary in terms of capabilities or features. Claimed subject matter is intended to cover a wide range of potential variations, such as a web-enabled client device or previously mentioned devices may include a high-resolution screen (HD or4K for example), one or more physical or virtual keyboards, mass storage, one or more accelerometers, one or more gyroscopes, global positioning system (GPS) or other location-identifying type capability, or a display with a high degree of functionality, such as a touch-sensitive color 2D or 3D display, for example.

Certain embodiments and principles will be discussed in more detail with reference to the figures. With reference toFIG.1, system100is depicted which includes user equipment (UE)102(e.g., a client device, as mentioned above and discussed below in relation toFIG.6), network104, cloud system106, database108, computer system110and authentication engine200. It should be understood that while system100is depicted as including such components, it should not be construed as limiting, as one of ordinary skill in the art would readily understand that varying numbers of UEs, cloud systems, databases, computer systems and/or networks can be utilized; however, for purposes of explanation, system100is discussed in relation to the example depiction inFIG.1.

According to some embodiments, UE102can be any type of device, such as, but not limited to, a mobile phone, tablet, laptop, sensor, Internet of Things (IoT) device, autonomous machine, and any other device equipped with a cellular or wireless or wired transceiver. For example, UE102can be a smart ring, which as discussed below in more detail, can enable the identification and/or collection of vitals of the wearing user. In some embodiments, such vitals can correspond to, but not be limited to, heart rate, heart rate variability (HRV), blood oxygen levels, blood pressure, hydration temperature, pulse, motion, sleep, and/or any other type of biometric for a person, or some combination thereof.

In some embodiments, peripheral device (not shown) can be connected to UE102, and can be any type of peripheral device, such as, but not limited to, a wearable device (e.g., smart ring or smart watch), printer, speaker, sensor, and the like. In some embodiments, peripheral device can be any type of device that is connectable to UE102via any type of known or to be known pairing mechanism, including, but not limited to, WiFi, Bluetooth™, Bluetooth Low Energy (BLE), NFC, and the like. For example, the peripheral device can be a smart ring that connectively pairs with UE102, which can be a user's smart phone.

According to some embodiments, UE102can correspond to an access point (AP) device, which is a device that creates a wireless local area network (WLAN) for the location. According to some embodiments, an AP device can be, but is not limited to, a router, switch, hub and/or any other type of network hardware that can project a WiFi signal to a designated area. For example, an AP device can be a Plume Pod™, and the like. In some embodiments, UE102may be an AP device for which another smart device connects thereto.

According to some embodiments, computer system110can be any type of secure local and/or network device, location, application, account, portal, resource, and the like, upon which authentication is required for a device and/or user to access the securely held information. For example, computer system100can be, but is not limited to, a web-portal, website, application, account, datastore, repository, cloud, peer device, platform, exchange, and the like, or some combination thereof.

In some embodiments, network104can be any type of network, such as, but not limited to, a wireless network, cellular network, the Internet, and the like (as discussed above). Network104facilitates connectivity of the components of system100, as illustrated inFIG.1.

According to some embodiments, cloud system106may be any type of cloud operating platform and/or network based system upon which applications, operations, and/or other forms of network resources may be located. For example, system106may be a service provider and/or network provider from where services and/or applications may be accessed, sourced or executed from. For example, system106can represent the cloud-based architecture associated with a smart home or network provider, which has associated network resources hosted on the internet or private network (e.g., network104), which enables (via engine200) the identity and authentication management discussed herein.

In some embodiments, cloud system106may include a server(s) and/or a database of information which is accessible over network104. In some embodiments, a database108of cloud system106may store a dataset of data and metadata associated with local and/or network information related to a user(s) of the components of system100and/or each of the components of system100(e.g., UE102, and the services and applications provided by cloud system106and/or authentication engine200).

In some embodiments, for example, cloud system106can provide a private/proprietary management platform, whereby engine200, discussed infra, corresponds to the novel functionality system106enables, hosts and provides to a network104and other devices/platforms operating thereon.

Turning toFIGS.4and5, in some embodiments, the exemplary computer-based systems/platforms, the exemplary computer-based devices, and/or the exemplary computer-based components of the present disclosure may be specifically configured to operate in a cloud computing/architecture106such as, but not limiting to: infrastructure as a service (IaaS)510, platform as a service (PaaS)508, and/or software as a service (SaaS)506using a web browser, mobile app, thin client, terminal emulator or other endpoint504.FIGS.4and5illustrate schematics of non-limiting implementations of the cloud computing/architecture(s) in which the exemplary computer-based systems for administrative customizations and control of network-hosted application program interfaces (APIs) of the present disclosure may be specifically configured to operate.

Turning back toFIG.1, according to some embodiments, database108may correspond to a data storage for a platform (e.g., a network hosted platform, such as cloud system106, as discussed supra) or a plurality of platforms. Database108may receive storage instructions/requests from, for example, engine200(and associated microservices), which may be in any type of known or to be known format, such as, for example, standard query language (SQL). According to some embodiments, database108may correspond to any type of known or to be known storage, for example, a memory or memory stack of a device, a distributed ledger of a distributed network (e.g., blockchain, for example), a look-up table (LUT), and/or any other type of secure data repository

Authentication engine200, as discussed above and further below in more detail, can include components for the disclosed functionality. According to some embodiments, authentication engine200may be a special purpose machine or processor, and can be hosted by a device on network104, within cloud system106and/or on UE102. In some embodiments, engine200may be hosted by a server and/or set of servers associated with cloud system106.

According to some embodiments, as discussed in more detail below, authentication engine200may be configured to implement and/or control a plurality of services and/or microservices, where each of the plurality of services/microservices are configured to execute a plurality of workflows associated with performing the disclosed security management. Non-limiting embodiments of such workflows are provided below in relation to at leastFIG.3.

According to some embodiments, as discussed above, authentication engine200may function as an application provided by cloud system106. In some embodiments, engine200may function as an application installed on a server(s), network location and/or other type of network resource associated with system106. In some embodiments, engine200may function as an application installed and/or executing on UE102. In some embodiments, such application may be a web-based application accessed by UE102and/or other devices over network104from cloud system106. In some embodiments, engine200may be configured and/or installed as an augmenting script, program or application (e.g., a plug-in or extension) to another application or program provided by cloud system106and/or executing on UE102.

As illustrated inFIG.2, according to some embodiments, authentication engine200includes identification module202, analysis module204, determination module206and access module208. It should be understood that the engine(s) and modules discussed herein are non-exhaustive, as additional or fewer engines and/or modules (or sub-modules) may be applicable to the embodiments of the systems and methods discussed. More detail of the operations, configurations and functionalities of engine200and each of its modules, and their role within embodiments of the present disclosure will be discussed below.

Turning toFIG.3, Process300provides non-limiting example embodiments for the disclosed security management framework. According to some embodiments, Process300provides non-limiting embodiments for a cross-session authentication framework that enables secure local and/or network sessions to be effectuated via biometric tracking via a wearable device (e.g., smart ring).

According to some embodiments, while the discussion herein may focus upon a smart ring being UE102, for purposes of discussing Process300, it should not be construed as limiting, as one of skill in the art would recognize that any type of wearable device that captures and monitors biometrics of a user can be implemented without departing from the scope of the instant disclosure.

According to some embodiments, Steps302-304and314-318can be performed by access module208of authentication engine200; Steps306-308can be performed by identification module202; Step310can be performed by analysis module204; and Step312can be performed by determination module206.

According to some embodiments, Process300begins with Step302where authentication for a first secure session with a first system is performed. According to some embodiments, as discussed above, the first secure session can correspond to a user logging into their account (or registering for an account, according to some embodiments) for any type of known or to be known computer system (e.g., computer system110, cloud system106, and the like). For example, in Step302, engine200can provide login credentials to a first system that can verify the user's identity, thereby enabling the user (and the device the user is using) access to the first system. In some embodiments, for example, a user, via their smart phone, can login to an application running on their smart phone via providing a face identifier (ID).

In Step304, in response to the authentication in Step302, engine200can provide a session token to a user's UE. The session token can be utilized, as discussed herein, to initiate and/or maintain an authentication state. For example, as discussed above, the UE can be a smart ring; as such, in some embodiments, the smart ring can receive a session that includes information related to an identity of the user. In some embodiments, the session can correspond to information related to, but not limited to, a time period, type of activity, type of encryption, type of content, a type of UE, a location, and the like, or some combination thereof.

In some embodiments, the session token can be stored in memory of the UE (e.g., RAM of the smart ring). In some embodiments, the session token, which can be encrypted, can be stored in database108, as depicted in relation toFIG.1, for example, In some embodiments, the key can be subject to any type of symmetric and asymmetric encryption, which can be, but is not limited to, master key encryption (MEK), key encryption key (KEK), content encryption (CEK), and the like.

In Step306, engine200can monitor and collect data associated with the physical contact of the UE with the user. For example, engine200can collect and track biometric data related to the smart ring on the user's finger, which can also indicate where on the user's finger the ring is located (upon the performance of Step302), which finger, and which position/rotation/angle the ring is at such time proximate to Step302. Accordingly, as discussed above, Step306can involve tracking whether the user is wearing the smart ring, whether and when they have removed it, and/or if the smart ring has been put back on the user's finger properly.

In some embodiments, Step306can involve the collection of data about the user (e.g., referred to as user data). According to some embodiments, the user data can be collected continuously and/or according to a predetermined period of time or interval. In some embodiments, user data may be collected based on detected events (e.g., the authentication of the first secure session, as discussed supra). As discussed above, the user data can provide biometrics or vitals for the user, which can include information related to, but are not limited to, heart rate, heart rate variation (HRV), blood oxygen levels, blood pressure, body temperature, hydration temperature, pulse, motion, and the like, or some combination thereof.

In some embodiments, the collected user data in Step306can be stored in database108in association with an ID of a user, an ID of the first secure session, ID of the location and/or an ID of an account of the user/location, and the like.

In Step308, engine200can receive a request from the user to access a second secure system to establish a second secure session. Such request can include, but not limited to, traversing to another website or portal or network resource (different from the first system), attempting to login to another application or system, and the like, or some combination thereof.

For example, in Step302, the user successfully logged into a first application on their smartphone, as discussed above. In Step308, the user can open another application (e.g., a mail application, for example), for which the application can require identity verification before the user can access their mail account. In another non-limiting example, as discussed above respective toFIG.1, the second secure system can be an IoT device, which can be accessible given the active session token.

In yet another example, the second secure system can be a third party system, such as, for example, a payment system and/or other type of system for which authentication to account credentials of the user can be provided via the session token's presence in association with the user's wearable device (e.g., the ring is maintained on the user's finger, for example).

Accordingly, in Step310, based on the request (from Step308), engine200can analyze the collected data (from Step308). In some embodiments, the collected data analysis, as discussed above, can be directed to whether the user is still wearing the smart ring, whether the smart ring was removed but is now being worn again (e.g., at a time proximate or associated with a time of the second request of Step308), if the ring is being worn improperly, and the like. As discussed herein, the session token (from Step304) is tied to the user maintaining the smart ring being worn to ensure that, for example, another user has not put on the user's ring. Thus, the analysis of Step310can serve as a backstop to guaranteeing that the identity of the user requesting access to the second system corresponds to the same user that was authenticated in Step302.

For example, Step310can involve checking whether the person is still wearing their ring. For example, in the event of a robbery, the person can remove the ring thereby disabling access to their linked accounts.

According to some embodiments, engine200can implement any type of known or to be known computational analysis technique, algorithm, mechanism or technology to analyze the collected user data from Step306.

In some embodiments, engine200may include a specific trained artificial intelligence/machine learning model (AI/ML), a particular machine learning model architecture, a particular machine learning model type (e.g., convolutional neural network (CNN), recurrent neural network (RNN), autoencoder, support vector machine (SVM), and the like), or any other suitable definition of a machine learning model or any suitable combination thereof.

In some embodiments, engine200may be configured to utilize one or more AI/ML techniques chosen from, but not limited to, computer vision, feature vector analysis, decision trees, boosting, support-vector machines, neural networks, nearest neighbor algorithms, Naive Bayes, bagging, random forests, logistic regression, and the like.

In some embodiments and, optionally, in combination of any embodiment described above or below, a neural network technique may be one of, without limitation, feedforward neural network, radial basis function network, recurrent neural network, convolutional network (e.g., U-net) or other suitable network. In some embodiments and, optionally, in combination of any embodiment described above or below, an implementation of Neural Network may be executed as follows:a. define Neural Network architecture/model,b. transfer the input data to the neural network model,c. train the model incrementally,d. determine the accuracy for a specific number of timesteps,e. apply the trained model to process the newly-received input data,f. optionally and in parallel, continue to train the trained model with a predetermined periodicity.

In Step312, based on the analysis from Step308, engine200can determine whether to authenticate the user (e.g., reply with an “auth” or “no_auth” message). According to some embodiments, the determination can leverage the information for the request from the second system in correlation with the biometrics data to determine that i) the smart ring is still being properly worn by the user (from Step302), ii) was removed, but was put back on before the request for the second system, or iii) was not being worn at the time of the second request.

In some embodiments, should the smart ring have been removed between Steps302and308(e.g., despite it being put back on before the request of Step308), engine200may require a new session token, as upon removal of the ring, and an absence (for at least a predetermined period of time) of collected biometric data, may cause the session token (from Step304) to be rendered invalid (and in some embodiments, removed from storage). Thus, in some embodiments, if the session token is rendered invalid, Step308may function in a similar manner as Step302where a new session can be created for subsequent system access operations.

Accordingly, when the user is not authenticated for automatic access to the second system (e.g., the session token is not valid because the smart ring is not currently being worn at the time of the second request or it had been removed prior to the performance of Step308), Process300can proceed from Step312to Step314. In Step314, the authentication request is denied, and a notification can be communicated to a device of the user (e.g., no_auth message).

In some embodiments, the notification can be sent to one or more devices of the user. For example, if the user requested access on their smart phone, a notification can be displayed on the smart phone indicating the denial of access, which can include an option to login via other procedures. In some embodiments, a notification can also or alternatively be sent to the smart ring of the user, which can provide a haptic or audible output indicating the denial.

Accordingly, any type of known or to be known notification can be utilized, which include, but is not limited to, audio, video, text, haptic and the like, output effects that can alert the user to a denial of an access request.

In some embodiments, when the user is authenticated to access the second system (e.g., the smart ring is currently being worn at the time of the second request), Process300can proceed from Step312to Step316. In Step316, the session token (from Step304) can be provided to the second system, which functions as a confirmation of the identity of the user requesting access to the second system. In some embodiments, the session token can be updated to include information related to and/or reference a secure session with the second system.

In some embodiments, Step316can involve the device of the user communicating an “auth” message to the second system (e.g., without communicating the session token). Such message can provide an indication that access is granted via the device of the user. In some embodiments, such message can include, but is not limited to, credentials that enable the second session to be access via approved credentials associated with the user and/or device.

Thus, in Step318, the provided session token (and/or auth message, in some embodiments, as discussed above) can enable the establishment of a secure second session for the user which enables them to access the electronic resources and information hosted by the second system.

Accordingly, after Step314and/or Step318, engine200may then continue monitoring the user. In some embodiments, the monitoring can continue running in the backend, while certain modules of engine200execute to optimize authentication of the user's identity, as discussed above.

By way of a non-limiting example, a user requests access to a first application on their laptop. As in Step302, the user enters their username/password, then via 2FA, enters the code from their smartphone SMS application, and is authenticated for the first application. As in Step304, a session token is transmitted to the user's smart ring which provides validated identity information for the user.

The user then, on their smart phone, opens a second application, and requests access. As discussed above, since the user is determined to have not removed their smart ring from the time of accessing the first application (or removed it, but then put it on prior to requesting access to the second application), the user is granted access to the second application. Such access is facilitated via the session token and/or auth message being provided to the second application as a form of identity verification.

Thus, as discussed above, the disclosed systems and methods can provide a cross-application, cross-session and cross-device authentication system that enables users to login and establish secure computer sessions based on security identification information stored and provided from the user's smart ring, which is based on and tied to continued biometric readings ensuring the ring maintains it correlation with the proper wearer.

According to some embodiments, a user and/or location can have a dedicated engine200model so that the authentication protocols discussed herein can be specific to the events and patterns learned and detected for the user and/or at that location. In some embodiments, the model can be specific for a user or set of users (e.g., users that live at a certain location (e.g., a house). For example, parental controls can be provided via a parent's valid session token (e.g., a child's request for content can be contingent upon the parent's smart ring being actively worn for a parent-session).

FIG.6is a schematic diagram illustrating a client device showing an example embodiment of a client device that may be used within the present disclosure. Client device600may include many more or less components than those shown inFIG.6. However, the components shown are sufficient to disclose an illustrative embodiment for implementing the present disclosure. Client device600may represent, for example, UE102discussed above at least in relation toFIG.1.

As shown in the figure, in some embodiments, Client device600includes a processing unit (CPU)622in communication with a mass memory630via a bus624. Client device600also includes a power supply626, one or more network interfaces650, an audio interface652, a display654, a keypad656, an illuminator658, an input/output interface660, a haptic interface662, an optional global positioning systems (GPS) receiver664and a camera(s) or other optical, thermal or electromagnetic sensors666. Device600can include one camera/sensor666, or a plurality of cameras/sensors666, as understood by those of skill in the art. Power supply626provides power to Client device600.

Client device600may optionally communicate with a base station (not shown), or directly with another computing device. In some embodiments, network interface650is sometimes known as a transceiver, transceiving device, or network interface card (NIC).

Audio interface652is arranged to produce and receive audio signals such as the sound of a human voice in some embodiments. Display654may be a liquid crystal display (LCD), gas plasma, light emitting diode (LED), or any other type of display used with a computing device. Display654may also include a touch sensitive screen arranged to receive input from an object such as a stylus or a digit from a human hand.

Keypad656may include any input device arranged to receive input from a user. Illuminator658may provide a status indication and/or provide light.

Client device600also includes input/output interface660for communicating with external. Input/output interface660can utilize one or more communication technologies, such as USB, infrared, Bluetooth™, or the like in some embodiments. Haptic interface662is arranged to provide tactile feedback to a user of the client device.

Optional GPS transceiver664can determine the physical coordinates of Client device600on the surface of the Earth, which typically outputs a location as latitude and longitude values. GPS transceiver664can also employ other geo-positioning mechanisms, including, but not limited to, triangulation, assisted GPS (AGPS), E-OTD, CI, SAI, ETA, BSS or the like, to further determine the physical location of client device600on the surface of the Earth. In one embodiment, however, Client device may through other components, provide other information that may be employed to determine a physical location of the device, including for example, a MAC address, Internet Protocol (IP) address, or the like.

Mass memory630includes a RAM632, a ROM634, and other storage means. Mass memory630illustrates another example of computer storage media for storage of information such as computer readable instructions, data structures, program modules or other data. Mass memory630stores a basic input/output system (“BIOS”)640for controlling low-level operation of Client device600. The mass memory also stores an operating system641for controlling the operation of Client device600.

Memory630further includes one or more data stores, which can be utilized by Client device600to store, among other things, applications642and/or other information or data. For example, data stores may be employed to store information that describes various capabilities of Client device600. The information may then be provided to another device based on any of a variety of events, including being sent as part of a header (e.g., index file of the HLS stream) during a communication, sent upon request, or the like. At least a portion of the capability information may also be stored on a disk drive or other storage medium (not shown) within Client device600.

Applications642may include computer executable instructions which, when executed by Client device600, transmit, receive, and/or otherwise process audio, video, images, and enable telecommunication with a server and/or another user of another client device. Applications642may further include a client that is configured to send, to receive, and/or to otherwise process gaming, goods/services and/or other forms of data, messages and content hosted and provided by the platform associated with engine200and its affiliates.

According to some embodiments, certain aspects of the instant disclosure can be embodied via functionality discussed herein, as disclosed supra. According to some embodiments, some non-limiting aspects can include, but are not limited to the below method aspects, which can additionally be embodied as system, apparatus and/or device functionality:

Aspect 1. A method comprising:providing a session token to a device of a user, the session token corresponding to an authenticated session of the user with a first system;collecting biometric data related to the user, the biometric data providing an indication of a manner in which the user is wearing the device;communicating a request for access to a second system;analyzing the collected biometric data based on the request;determining, based on the analysis, whether to authenticate the user for the second system;electronically communicating information to the device based on the determination.
Aspect 2. The method of Aspect 1, wherein the communicated information comprises an indication of an access denial.
Aspect 3. The method of Aspect 2, further comprising:determining, based on the analysis, that the manner in which the user is wearing the device is not consistent with a manner corresponding to the authentication of the session with the first system.
Aspect 4. The method of Aspect 1, further comprising:determining, based on the analysis, that the manner in which the user is wearing the device is consistent with a manner corresponding to the authentication of the session with the first system; andcommunicating, via the device, the session token to the second system.
Aspect 5. The method of Aspect 4, further comprising:authenticating the user on the second system via the communicated session token.
Aspect 6. The method of Aspect 4, wherein the communicated information comprises an indication of access to the second system.
Aspect 7. The method of Aspect 1, further comprising:monitoring, via the device, the biometric data; andanalyzing the biometric data to determine events corresponding to manners in which the user maintains a status of wearing the device, wherein the monitoring and analysis of the biometric data is based on the collection of the biometric data.
Aspect 8. The method of Aspect 1, further comprising:providing login credentials to the first system;receiving, in response to the provided login credentials, an indication of authentication with the first system, the authentication comprising access to an account with the first system; andcommunicating the session token to the device.
Aspect 9. The method of Aspect 1, wherein the session token is stored in association with the device.
Aspect 10. The method of Aspect 1, wherein the device is a smart ring.

For the purposes of this disclosure the term “user”, “subscriber” “consumer” or “customer” should be understood to refer to a user of an application or applications as described herein and/or a consumer of data supplied by a data provider. By way of example, and not limitation, the term “user” or “subscriber” can refer to a person who receives data provided by the data or service provider over the Internet in a browser session, or can refer to an automated software application which receives the data and stores or processes the data. Those skilled in the art will recognize that the methods and systems of the present disclosure may be implemented in many manners and as such are not to be limited by the foregoing exemplary embodiments and examples. In other words, functional elements being performed by single or multiple components, in various combinations of hardware and software or firmware, and individual functions, may be distributed among software applications at either the client level or server level or both. In this regard, any number of the features of the different embodiments described herein may be combined into single or multiple embodiments, and alternate embodiments having fewer than, or more than, all of the features described herein are possible.