IP Library › Granted Patent US 12,443,968
Granted Patent B2
US 12,443,968 · App. 18/161,086 · Granted Oct 14, 2025

System and methods for universal identification and passport management

Inventors: Steve Doumar (Fort Lauderdale, FL); David Teodosio (Guilford, CT)
Assignee: TAPTEXT LLC
G06Q30/0207G06F16/9554G06F16/9558G06F21/32G06F21/6245G06K7/1417G06K19/06037G06N20/00G06Q10/06315G06Q30/016G06Q30/0201H04M3/523H04M3/527H04M3/53308H04M3/53333G06F2221/2139G06Q30/0267
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,443,968
App. No.
18/161,086
Filed
Jan 29, 2023
Granted
Oct 14, 2025
Kind
B2
Examiner
ELAHEE, MD S
Art Unit
2694
USPC
379/88.22
Abstract

A system and method for universal identification and passport management using a phone identifier and text redirect for user identification. The first step is engagement by a mobile phone with a call-to-action embedded in various media that triggers a text message to auto-populate on the mobile phone. The auto-populated message comprises information about the user and a unique identifier. The second step is for the user to tap to send the auto-populated message to the universal identification and passport manager, thus initiating the identification of the user. The manager works with an identity verifier and privileges handler to identify the user, grant the user access to a third-party client system, and perform other actions based on the unique identifier and stored authentication instructions.

Claims (75)

1. A system for universal identification and passport management, comprising:

a computing device comprising a memory, a processor, and a non-volatile data storage device;

a first database stored on the non-volatile data storage device, the first database comprising a second plurality of user data, wherein the second plurality of user data includes a plurality of user privileges data and a plurality of user identity profiles comprising a plurality of user data, wherein the plurality of user data includes at least each user's phone number and device international mobile equipment identity (IMEI);

a second database stored on the non-volatile data storage device, the second database comprising a plurality of client instructions for authenticating a user computing device on a third-party client system, each client instruction of the plurality of client instructions comprising a scheme for generating placement of call-to-action elements and a verification procedure;

a positioning manager comprising a first plurality of programming instructions stored in the memory which, when operating on the processor, causes the computing device to:

retrieve from the second database a client instruction for authenticating a user computing device;

generate a call-to-action element comprising coding instructions configured to generate a pre-filled short message service (SMS) or multi-media message service (MMS) message comprising a destination, an identifier, and an IMEI on user computing devices, such that interaction with the call-to-action element on a user computing device causes the user computing device to propagate the pre-filled SMS or MMS message; and

place the call-to-action element according to the scheme specified in the client instructions; and

an identification and passport manager comprising a second plurality of programming instructions stored in the memory which, when operating on the processor, causes the computing device to:

receive the SMS or MMS message from the user computing device via the destination;

capture a phone number from which the SMS or MMS message was sent;

retrieve from the second database a client instruction for authenticating the user computing device using the identifier; and

execute the client instruction, wherein the client instruction causes the computing device to:

query the first database using the phone number and IMEI of the user computing device;

verify, using the query results, that a user identity profile associated with the phone number and IMEI satisfies the verification procedure of the client instruction; and

send a notification to the third-party client system.

2. The system of claim 1 , wherein the identification and passport manager is further configured to:

on a first identification to the third-party client system, issue new privileges according to a new user procedure of the client instruction;

send user data from the user identity profile to the third-party client system;

update user privileges to the third-party client system; and

store the updated user privileges in the user identity profile.

3. The system of claim 1 , wherein:

the system further comprises a session manager comprising a third plurality of programming instructions store in the memory which, when operating on the processor, causes the computing device to:

generate an authenticated session between the third-party client system and user computing device;

monitor and log user activity during the authenticated session; and

terminate the session.

4. The system of claim 1 , wherein the call-to-action element comprises an interactable button or link, an NFC beacon, or a scannable QR code.

5. The system of claim 1 , wherein the SMS or MMS message further comprises user consent to receive communications from the third-party client system.

6. The system of claim 1 , wherein the identification and passport manager is further configured to send a notification to the user computing device.

7. The system of claim 2 , wherein the identification and passport manager may further increase, decrease, or remove user privileges to the third-party client system.

8. The system of claim 3 , wherein the session manager is further configured to:

send a SMS or MMS message to the user computing device comprising a request to extend or terminate the session or a warning of session expiration; and

receive a response to the SMS or MMS message to the user computing device from the user computing device via the destination;

update user privileges to the third-party client system;

store the updated user privileges in the user identity profile; and

send a notification to the third-party client system.

9. The system of claim 1 , wherein the notification to the third-party client system further comprises a photograph.

10. The system of claim 6 , wherein the identification and passport manager further comprises instructions to perform facial recognition on the photograph.

11. A method for universal identification and passport management, comprising the steps of:

creating a first database on the non-volatile data storage device of a computing device, the computing device comprising a memory, a processor, and the non-volatile data storage device, the first database comprising a second plurality of user data, wherein the second plurality of user data includes a plurality of user privileges data and a plurality of user identity profiles comprising a plurality of user data, wherein the plurality of user data includes at least each user's phone number and device international mobile equipment identity (IMEI);

creating a second database on the non-volatile data storage device of a computing device, the computing device comprising a memory, a processor, and the non-volatile data storage device, the second database comprising a plurality of client instructions for authenticating a user computing device on a third-party client system, each client instruction of the plurality of client instructions comprising a scheme for generating placement of call-to-action elements and a verification procedure;

using a positioning manager operating on the computing device to perform the steps of:

retrieving from the second database a client instruction for authenticating a user computing device;

generating a call-to-action element comprising coding instructions configured to generate a pre-filled short message service (SMS) or multi-media message service (MMS) message comprising a destination, an identifier, and an IMEI on user computing devices, such that interaction with the call-to-action element on a user computing device causes the user computing device to propagate the pre-filled SMS or MMS message;

placing the call-to-action element according to the scheme specified in the client instructions;

using an identification and passport manager operating on the computing device to perform the steps of:

retrieving from the second database a client instruction for authenticating a user computing device;

receiving the SMS or MMS message from the user computing device via the destination;

capturing a phone number from which the SMS or MMS message was sent;

retrieving from the second database a client instruction for authenticating the user computing device using the identifier;

executing the client instruction, wherein the client instruction causes the computing device to:

querying the first database using the phone number and IMEI of the user computing device;

verifying, using the query results, that a user identity profile associated with the phone number and IMEI satisfies the verification procedure of the client instruction; and

sending a notification to the third-party client system.

12. The method of claim 11 , wherein the identification and passport manager is further configured to perform the steps of:

on a first identification to the third-party client system, issuing new privileges according to a new user procedure of the client instruction;

sending user data from the user identity profile to the third-party client system;

updating user privileges to the third-party client system; and

storing the updated user privileges in the user identity profile.

13. The method of claim 11 , wherein the method further comprises the step of using a session manager operating on the computing device to perform the steps of:

generating an authenticated session between the third-party client system and user computing device;

monitoring and logging user activity during the authenticated session; and

terminating the session.

14. The method of claim 11 , wherein the call-to-action element comprises an interactable button or link, an NFC beacon, or a scannable QR code.

15. The method of claim 11 , wherein the SMS or MMS message further comprises user consent to receive communications from the third-party client system.

16. The method of claim 11 , wherein the identification and passport manager further performs the step of sending a notification to the user computing device.

17. The method of claim 11 , wherein the method further comprises the step of using the identification and passport manager to perform the steps of increasing, decreasing, or removing user privileges to the third-party client system.

18. The method of claim 13 , wherein the method further comprises the step of using a session manager operating on the computing device to perform the steps of:

sending a SMS or MMS message to the user computing device comprising a request to extend or terminate the session or a warning of session expiration; and

receiving a response to the SMS or MMS message to the user computing device from the user computing device via the destination;

updating user privileges to the third-party client system;

storing the updated user privileges in the user identity profile; and

sending a notification to the third-party client system.

19. The method of claim 11 , wherein the notification to the third-party client system further comprises a photograph.

20. The method of claim 19 , wherein the method further comprises the step of using the identification and passport manager to perform the step of performing facial recognition on the photograph.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 11, 2024
From: DOUMAR, STEVE; TEODOSIO, DAVID
To: TAPTEXT LLC
Reel/Frame 066720/0639 →
Continuity (38)
Continuation In Part 17942227 · Sep 12, 2022
Continuation In Part 17943118 · Sep 12, 2022
Continuation In Part 17875402 · Jul 27, 2022
Continuation In Part 17409841 · Aug 24, 2021
Continuation In Part 17360731 · Jun 28, 2021
Continuation In Part 17351321 · Jun 18, 2021
Continuation 17349659 · Jun 16, 2021
Continuation 17349659 · Jun 16, 2021
Continuation 17348660 · Jun 15, 2021
Continuation 17344695 · Jun 10, 2021
Continuation 17229251 · Apr 13, 2021
Continuation In Part 17229251 · Apr 13, 2021
Continuation In Part 17209474 · Mar 23, 2021
Continuation In Part 17208059 · Mar 22, 2021
Continuation In Part 17191977 · Mar 4, 2021
Continuation In Part 17190260 · Mar 2, 2021
Continuation In Part 17153426 · Jan 20, 2021
Continuation In Part 17085931 · Oct 30, 2020
Continuation In Part 16693275 · Nov 23, 2019
Provisional Application 63411163 · Sep 29, 2022
Provisional Application 63350415 · Jun 9, 2022
Provisional Application 63319314 · Mar 12, 2022
Provisional Application 63211496 · Jun 16, 2021
Provisional Application 63166391 · Mar 26, 2021
Provisional Application 63154357 · Feb 26, 2021
Provisional Application 63040610 · Jun 18, 2020
Provisional Application 63025287 · May 15, 2020
Provisional Application 63022190 · May 8, 2020
Provisional Application 62994219 · Mar 24, 2020
Provisional Application 62965626 · Jan 24, 2020
Provisional Application 62963568 · Jan 21, 2020
Provisional Application 62963379 · Jan 20, 2020
Provisional Application 62963368 · Jan 20, 2020
Provisional Application 62940607 · Nov 26, 2019
Provisional Application 62904568 · Sep 23, 2019
Provisional Application 62883360 · Aug 6, 2019
Provisional Application 62879862 · Jul 29, 2019
Related Publication 20230368233A1 · Nov 16, 2023
References Cited (37)
US 8380230B2 · Christianson · 2013 [cited by examiner]
US 8620365B2 · Hunziker · 2013 [cited by applicant]
US 8783571B2 · Sakahashi et al. · 2014 [cited by applicant]
US 8950685B1 · Lin et al. · 2015 [cited by applicant]
US 9223885B2 · Marsico · 2015 [cited by applicant]
US 9237424B2 · Nelkenbaum · 2016 [cited by applicant]
US 10031643B2 · Chien · 2018 [cited by examiner]
US 10361870B2 · Chow et al. · 2019 [cited by applicant]
US 10645037B2 · Schmid et al. · 2020 [cited by applicant]
US 11062038B2 · Murphy et al. · 2021 [cited by applicant]
US 11201737B1 · Will et al. · 2021 [cited by applicant]
US 11205105B1 · Devlin et al. · 2021 [cited by applicant]
US 11210648B2 · Ortiz et al. · 2021 [cited by applicant]
US 11368454B2 · Whaley et al. · 2022 [cited by applicant]
US 20100094703A1 · Bramley · 2010 [cited by examiner]
US 20120226743A1 · Smargon · 2012 [cited by applicant]
US 20120278142A1 · Li · 2012 [cited by applicant]
US 20130144738A1 · Qawami et al. · 2013 [cited by applicant]
US 20150039409A1 · Marsico et al. · 2015 [cited by applicant]
US 20170214522A1 · Code et al. · 2017 [cited by applicant]
US 20170244555A1 · Beiter et al. · 2017 [cited by applicant]
US 20180060914A1 · Conrad et al. · 2018 [cited by applicant]
US 20190354665A1 · Haslam et al. · 2019 [cited by applicant]
US 20200045020A1 · Soundararajan et al. · 2020 [cited by applicant]
US 20200184085A1 · Korten et al. · 2020 [cited by applicant]
US 20200186338A1 · Andon et al. · 2020 [cited by applicant]
US 20200242105A1 · Rich et al. · 2020 [cited by applicant]
US 20210092135A1 · Strogov et al. · 2021 [cited by applicant]
US 20210256070A1 · Tran et al. · 2021 [cited by applicant]
US 20210306460A1 · Doumar et al. · 2021 [cited by applicant]
US 20210319116A1 · Jarvis · 2021 [cited by applicant]
US 20210398095A1 · Mallett et al. · 2021 [cited by applicant]
US 20220201476A1 · Naujok et al. · 2022 [cited by applicant]
US 20220201477A1 · Rolfe · 2022 [cited by applicant]
US 20220311611A1 · Gaur et al. · 2022 [cited by applicant]
EP 3316549A1 · 2018 [cited by applicant]
Wang et al. Non-fungible token (NFT): Overview, evaluation, opportunities and challenges. arXiv preprint arXiv:2105.07447.Oct. 25, 2021. [retrieved on Jul. 3, 2023] Retrieved from the Internet < URL: https://arxiv.org/p… [cited by applicant]