IP Library Granted Patent US 12,603,780
Granted Patent B2
US 12,603,780 · App. 18/782,801 · Granted Apr 14, 2026

System and method for managing an operating system using tokenized identity

Inventors: Amod Ashok Dange (Mountain View, CA); Yash Mody (Mumbai, IN)
Assignee: Amod Ashok Dange
H04L9/3213H04L9/0866H04L9/0869H04L9/30H04L9/3231H04L9/3247H04L63/0861G06F21/32H04L63/0281H04L63/0823H04L63/102
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,603,780
App. No.
18/782,801
Granted
Apr 14, 2026
Kind
B2
Abstract

A System for managing an operating system using tokenized identity. The system maintains a token repository storing user tokens, Unique-Numbers, and Public-Keys. The system registers users by processing biometric samples to compute a Secret-Key, generating a Unique-Number, and computing a Public-Key. The Public-Key (P 1 ) is stored in the token repository, on the provisioned virtual remote device, and on a thin client application on a personal local device. The Unique-Number is stored on the provisioned virtual remote device and in the token repository. Further, the system receives session signing requests from a proxy-user management application integrated with various device Operating Systems via thin client sessions. The system authenticates users through a two-step process using real-time biometric samples, and comparing computed Real-Time-Unique-Numbers with stored Unique-Numbers. Upon authentication, the system fetches user tokens, identifies corresponding proxy-user management application instances, captures user approval, and affixes biometrically authenticated signatures in session logs.

Claims (123)

1 . A System for managing an Operating System using tokenized identity, the system comprising:

a processor and a memory coupled to the processor, wherein the processor is configured to execute instructions stored in the memory for:

a) maintaining a token repository, wherein the token repository is configured to maintain a user token, a Unique-Number, and a Public-Key corresponding to each user from a set of users;

b) registering a user by,

receiving a set of biometric samples of the user corresponding to one or more biometric factors,

processing the set of biometric samples to compute a Secret-Key (S 1 ) corresponding to the user,

generating a Unique-Number (N 1 ) using a random number generation algorithm,

applying a Function (F 1 ) to the Secret-Key (S 1 ) and the Unique-Number (N 1 ) to compute a Public-Key (P 1 ),

storing the Unique-Number (N 1 ) on a provisioned virtual remote device and in a token repository, wherein the provisioned virtual remote device is a virtual machine corresponding to the user, wherein the provisioned virtual remote device is hosted over a remote server, wherein the token repository is hosted over a centralized server and

storing the Public-Key (P 1 ) in the token repository, on the provisioned virtual remote device, and on a thin client application on a personal local device,

receiving a user input on the thin client application corresponding to one or more immutable attributes of the user,

generating an immutable attribute token for each immutable attribute, and

storing the immutable attribute tokens along with the Public-Key (P 1 ) in the token repository;

c) transmitting to a user, a session signing request from a proxy-user management application, wherein the proxy-user management application is integrated with a device Operating System (OS), wherein the session signing request corresponds to a user-authenticated session, on the device Operating System (OS), wherein the session signing request is received via a thin client session running on a client device;

d) initiating a first authentication process for authenticating the user via the thin client session by,

receiving a biometric sample captured from the user in real-time,

processing the biometric sample to generate a Secret-Key (S 2 ),

when using a thin client application on a personal local device,

selecting the Public-Key (P 1 ) from the thin client application,

fetching the corresponding Public-Key (P 1 ) from the token repository,

computing a Real-Time-Unique-Number (N 2 ) using the Public-Key (P 1 ), the Secret-Key (S 2 ) and the Function (F 1 ), and

authenticating the user based on comparison of the Real-Time-Unique-Number (N 2 ) with the Unique-Number (N 1 ) stored in the token repository,

when using a thin client application on a non-personal local device,

receiving a user input corresponding to the one or more immutable attributes of the user,

generating a token corresponding to each of the one or more immutable attributes,

querying the token repository for one or more tokens,

fetching the public-keys (P 1 -Pn) corresponding to the one or more tokens,

computing a Real-Time-Unique-Number (N 2 ) for each Public-Key (P 1 -Pn), the Secret-Key (S 2 ) and the Function (F 1 ), identifying a target Real-Time-Unique-Number (N 2 t ),

wherein the target Real-Time-Unique-Number (N 2 t ) matches the Unique-Number (N 1 ) stored in the token repository, and

authenticating the user based on comparison of the target Real-Time-Unique-Numbers (N 2 t ) with the Unique-Number (N 1 ) stored in the token repository;

e) fetching from the token repository, a user token (T 1 ) corresponding to the Unique-Number (N 1 );

f) Identifying from a set of proxy-user management application instances, a proxy-user management application instance corresponding to the user token (T 1 );

g) displaying a request to sign the proxy-user management application session and the corresponding device OS session;

h) capturing the user's approval to affix the user's biometrically authenticated signature to the session;

i) initiating a second authentication process; and

j) recording the user's biometrically authenticated signature in the proxy-user management application session log.

2 . The system of claim 1 , wherein the proxy-user management application is a device operating system, wherein the device operating system corresponds to a computer OS, an Artificial Intelligence (AI) Agent OS, or a Robot OS,

wherein the user is logged into computer, wherein the user's biometrically authenticated signature in the proxy-user management application session log corresponds to the user's authorization for the computer operation session,

wherein the AI Agent represents the user when interacting with others, wherein the user's biometrically authenticated signature in the proxy-user management application session log corresponds to the user's authorization for the AI Agent operation session, and

wherein the Robot represents the user, when interacting with others, wherein the user's biometrically authenticated signature in the proxy-user management application session log corresponds to the user's authorization for the Robot operation session.

3 . The system of claim 1 , wherein the session signing request is triggered by the proxy-user management application session based on a set of predefined rules.

4 . The system of claim 1 , wherein the session signing request is generated upon receiving a user command to launch the proxy-user management application session.

5 . The system of claim 4 , wherein the proxy-user management application session is configured to record the user's biometrically authenticated signature, wherein the user's biometrically authenticated signature represents a promise to abide by the terms and conditions specified in respect of the proxy-user management application session.

6 . The system of claim 1 , wherein the second authentication process is triggered upon capturing the user's approval through the user interface, wherein the second authentication process is the same as the first authentication process.

7 . The system of claim 1 , wherein when the user is accessing the system via a thin client on the user's personal device, fetching the Public-Key (P 1 ) corresponding to the user from the token repository.

8 . A method for managing an Operating System using tokenized identity, the method comprising steps of:

a) maintaining a token repository, wherein the token repository is configured to maintain a user token, a Unique-Number, and a Public-Key corresponding to each user from a set of users;

b) registering a user by,

receiving a set of biometric samples of the user corresponding to one or more biometric factors,

processing the set of biometric samples to compute a Secret-Key (S 1 ) corresponding to the user,

generating a Unique-Number (N 1 ) using a random number generation algorithm,

applying a Function (F 1 ) to the Secret-Key (S 1 ) and the Unique-Number (N 1 ) to compute a Public-Key (P 1 ),

storing the Unique-Number (N 1 ) on a provisioned virtual remote device and in a token repository, wherein the provisioned virtual remote device is a virtual machine corresponding to the user, wherein the provisioned virtual remote device is hosted over a remote server, wherein the token repository is hosted over a centralized server and

storing the Public-Key (P 1 ) in the token repository, on the provisioned virtual remote device, and on a thin client application on a personal local device,

receiving a user input on the thin client application corresponding to one or more immutable attributes of the user,

generating an immutable attribute token for each immutable attribute, and

storing the immutable attribute tokens along with the Public-Key (P 1 ) in the token repository;

c) transmitting to a user, a session signing request from a proxy-user management application, wherein the proxy-user management application is integrated with a device Operating System (OS), wherein the session signing request corresponds to a user-authenticated session, on the device Operating System (OS), wherein the session signing request is received via a thin client session running on a client device;

d) initiating a first authentication process for authenticating the user via the thin client session by,

receiving a biometric sample captured from the user in real-time,

processing the biometric sample to generate a Secret-Key (S 2 ),

when using a thin client application on a personal local device,

selecting the Public-Key (P 1 ) from the thin client application,

fetching the corresponding Public-Key (P 1 ) from the token repository,

computing a Real-Time-Unique-Number (N 2 ) using the Public-Key (P 1 ), the Secret-Key (S 2 ) and the Function (F 1 ), and

authenticating the user based on comparison of the Real-Time-Unique-Number (N 2 ) with the Unique-Number (N 1 ) stored in the token repository,

when using a thin client application on a non-personal local device,

receiving a user input corresponding to the one or more immutable attributes of the user,

generating a token corresponding to each of the one or more immutable attributes,

querying the token repository for one or more tokens;

fetching the public-keys (P 1 -Pn) corresponding to the one or more tokens,

computing a Real-Time-Unique-Number (N 2 ) for each Public-Key (P 1 -Pn), the Secret-Key (S 2 ) and the Function (F 1 ),

identifying a target Real-Time-Unique-Number (N 2 t ), wherein the target Real-Time-Unique-Number (N 2 t ) matches the Unique-Number (N 1 ) stored in the token repository, and

authenticating the user based on comparison of the target Real-Time-Unique-Numbers (N 2 t ) with the Unique-Number (N 1 ) stored in the token repository;

e) fetching from the token repository, a user token (T 1 ) corresponding to the Unique-Number (N 1 );

f) identifying from a set of proxy-user management application instances, a proxy-user management application instance corresponding to the user token (T 1 );

g) displaying a request to sign the proxy-user management application session and the corresponding device OS session;

h) capturing the user's approval to affix the user's biometrically authenticated signature to the session;

i) initiating a second authentication process; and

j) recording the user's biometrically authenticated signature in the proxy-user management application session log.

9 . The method of claim 8 , wherein the proxy-user management application is a device operating system, wherein the device operating system corresponds to a computer OS, an Artificial Intelligence (AI) Agent OS, or a Robot OS,

wherein the user is logged into a computer, wherein the user's biometrically authenticated signature in the proxy-user management application session log corresponds to the user's authorization for the computer operation session,

wherein the AI Agent represents the user when interacting with others, wherein the user's biometrically authenticated signature in the proxy-user management application session log corresponds to the user's authorization for the AI Agent operation session,

wherein the Robot represents the user, when interacting with others, wherein the user's biometrically authenticated signature in the proxy-user management application session log corresponds to the user's authorization for the Robot operation session.

10 . The method of claim 8 , wherein the session signing request is triggered by the proxy-user management application session based on a set of predefined rules.

11 . The method of claim 10 , wherein the proxy-user management application session is configured to record the user's biometrically authenticated signature, wherein the user's biometrically authenticated signature represents an agreement to abide by the terms and conditions specified in respect of the proxy-user management application session.

12 . The method of claim 8 , wherein the session signing request is generated upon receiving a user command to launch the proxy-user management application session.

13 . The method of claim 8 , wherein the second authentication process is triggered upon capturing the user's approval through the user interface, wherein the second authentication process is the same as the first authentication process.

14 . A non-transitory computer-readable storage medium storing a computer program product comprising computer-executable instructions for managing an Operating System using tokenized identity, which when executed by one or more processors, cause the one or more processors to:

a) maintain a token repository, wherein the token repository is configured to maintain a user token, a Unique-Number, and a Public-Key corresponding to each user from a set of users;

b) registering a user by,

receiving a set of biometric samples of the user corresponding to one or more biometric factors,

processing the set of biometric samples to compute a Secret-Key (S 1 ) corresponding to the user,

generating a Unique-Number (N 1 ) using a random number generation algorithm,

applying a Function (F 1 ) to the Secret-Key (S 1 ) and the Unique-Number (N 1 ) to compute a Public-Key (P 1 ),

storing the Unique-Number (N 1 ) on a provisioned virtual remote device and in a token repository, wherein the provisioned virtual remote device is a virtual machine corresponding to the user, wherein the provisioned virtual remote device is hosted over a remote server, wherein the token repository is hosted over a centralized server, and

storing the Public-Key (P 1 ) in the token repository, on the provisioned virtual remote device, and on a thin client application on a personal local device,

receiving a user input on the thin client application corresponding to one or more immutable attributes of the user,

generating an immutable attribute token for each immutable attribute, and

storing the immutable attribute tokens along with the Public-Key (P 1 ) in the token repository;

c) transmitting to a user, a session signing request from a proxy-user management application, wherein the proxy-user management application is integrated with a device Operating System (OS), wherein the session signing request corresponds to a user-authenticated session, on the device Operating System (OS), wherein the session signing request is received via a thin client session running on a client device;

d) initiating a first authentication process for authenticating the user via the thin client session by,

receiving a biometric sample captured from the user in real-time,

processing the biometric sample to generate a Secret-Key (S 2 ),

when using a thin client application on a personal local device,

selecting the Public-Key (P 1 ) from the thin client application;

fetching the corresponding Public-Key (P 1 ) from the token repository,

computing a Real-Time-Unique-Number (N 2 ) using the Public-Key (P 1 ), the Secret-Key (S 2 ) and the Function (F 1 ), and

authenticating the user based on comparison of the Real-Time-Unique-Number (N 2 ) with the Unique-Number (N 1 ) stored in the token repository,

when using a thin client application on a non-personal local device,

receiving a user input corresponding to the one or more immutable attributes of the user,

generating a token corresponding to each of the one or more immutable attributes,

querying the token repository for one or more tokens,

fetching the public-keys (P 1 -Pn) corresponding to the one or more tokens,

computing a Real-Time-Unique-Number (N 2 ) for each Public-Key (P 1 -Pn), the Secret-Key (S 2 ) and the Function (F 1 ),

identifying a target Real-Time-Unique-Number (N 2 t ), wherein the target Real-Time-Unique-Number (N 2 t ) matches the Unique-Number (N 1 ) stored in the token repository, and

authenticating the user based on comparison of the target Real-Time-Unique-Numbers (N 2 t ) with the Unique-Number (N 1 ) stored in the token repository,

e) fetching from the token repository, a user token (T 1 ) corresponding to the Unique-Number (N 1 );

f) identifying from a set of proxy-user management application instances, a proxy-user management application instance corresponding to the user token (T 1 );

g) displaying a request to sign the proxy-user management application session and the corresponding device OS session;

h) capturing the user's approval to affix the user's biometrically authenticated signature to the session;

i) initiating a second authentication process; and

j) recording the user's biometrically authenticated signature in the proxy-user management application session log.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 24, 2024
From: MODY, YASH
To: DANGE, AMOD ASHOK
Reel/Frame 068072/0200 →
Continuity (6)
Continuation In Part 17481468 · Sep 22, 2021
Continuation In Part 17018273 · Sep 11, 2020
Provisional Application 63029717 · May 26, 2020
Provisional Application 62954591 · Dec 29, 2019
Provisional Application 62906080 · Sep 25, 2019
Related Publication 20240380598A1 · Nov 14, 2024
References Cited (56)
US 6401206B1 · Khan et al. · 2002 [cited by applicant]
US 7013290B2 · Ananian · 2006 [cited by applicant]
US 7039805B1 · Messing · 2006 [cited by examiner]
US 7093131B1 · Kobayashi · 2006 [cited by examiner]
US 7340438B2 · Nordman et al. · 2008 [cited by applicant]
US 7496191B1 · Crews et al. · 2009 [cited by applicant]
US 7769633B2 · Jokinen et al. · 2010 [cited by applicant]
US 8170615B2 · Vanska et al. · 2012 [cited by applicant]
US 9633269B2 · Gu et al. · 2017 [cited by applicant]
US 10136191B1 · Lewis et al. · 2018 [cited by applicant]
US 10489826B2 · Matthews et al. · 2019 [cited by applicant]
US 10530577B1 · Pazhoor et al. · 2020 [cited by applicant]
US 11252479B2 · Lewis et al. · 2022 [cited by applicant]
US 20020023220A1 · Kaplan · 2002 [cited by examiner]
US 20030028451A1 · Ananian · 2003 [cited by examiner]
US 20030135740A1 · Talmor · 2003 [cited by examiner]
US 20060085844A1 · Buer · 2006 [cited by examiner]
US 20070271463A1 · Ginter · 2007 [cited by examiner]
US 20080072068A1 · Wang et al. · 2008 [cited by applicant]
US 20090271634A1 · Boult et al. · 2009 [cited by applicant]
US 20120033807A1 · Asim · 2012 [cited by examiner]
US 20140006290A1 · Hozanne · 2014 [cited by examiner]
US 20150006895A1 · Irvine · 2015 [cited by examiner]
US 20150046699A1 · Benteo · 2015 [cited by examiner]
US 20150095999A1 · Toth · 2015 [cited by examiner]
US 20150134552A1 · Engels · 2015 [cited by examiner]
US 20150269389A1 · Lee · 2015 [cited by examiner]
US 20150280921A1 · Geoffrey · 2015 [cited by examiner]
US 20160050213A1 · Storr · 2016 [cited by examiner]
US 20160219046A1 · Ballard et al. · 2016 [cited by applicant]
US 20170141920A1 · Herder, III · 2017 [cited by examiner]
US 20170372059A1 · Sindia et al. · 2017 [cited by applicant]
US 20180173871A1 · Toth · 2018 [cited by applicant]
US 20180307859A1 · LaFever et al. · 2018 [cited by applicant]
US 20190097812A1 · Toth · 2019 [cited by examiner]
US 20190182176A1 · Niewczas · 2019 [cited by applicant]
US 20190306151A1 · Hamel et al. · 2019 [cited by applicant]
US 20200204545A1 · Pacella et al. · 2020 [cited by applicant]
US 20200266989A1 · KrcMaricic-Barackov et al. · 2020 [cited by applicant]
US 20200296093A1 · Hoyos · 2020 [cited by applicant]
US 20210058246A1 · Stolbikov · 2021 [cited by examiner]
US 20210091937A1 · Dange et al. · 2021 [cited by applicant]
US 20220004613A1 · Dange et al. · 2022 [cited by applicant]
US 20220004619A1 · Dange et al. · 2022 [cited by applicant]
US 20220004661A1 · Dange et al. · 2022 [cited by applicant]
US 20220006815A1 · Dange et al. · 2022 [cited by applicant]
US 20220038291A1 · Hong · 2022 [cited by examiner]
JP 4675660B2 · 2006 [cited by applicant]
JP 2014127164A · 2014 [cited by applicant]
Sy et al. “Generation of Cryptographic Keys from Personal Biometrics: An Illustration Based on Fingerprints.” dated Nov. 28, 2021, pp. 1-35. [cited by applicant]
Hochrieser, “Online Dating Can Benefit From Identity Verification And Biometric Authentication In 2019”, Information Security Buzz, dated Jul. 18, 2019 pp. 1-5. [cited by applicant]
Arsenova, “Face Liveness Detection For Safe Biometric Authentication And Face Recognition”, dated Jan. 27, 2020, pp. 1-10. [cited by applicant]
M. Kapko et al., “What is Windows Hello? Microsoft's biometrics security system explained” dated Jan. 12, 2021, pp. 1-5. [cited by applicant]
Mjaaland et al., “Biocryptics: Towards Robust Biometric Public/Private Key Generation”, The Norwegian Information Security Conference (NISK) dated 2009, pp. 27-42. [cited by applicant]
Chandra et al., “Generate an Encryption Key by using Biometric Cryptosystems to secure transferring of Data over a Network”, IOSR Journal of Computer Engineering (IOSR-JCE), vol. 12, Issue 1, dated May-Jun. 2013), pp. 1… [cited by applicant]
Office Action dated Nov. 19, 2026, issued in U.S. Appl. No. 18/783,017 (21 pages). [cited by applicant]