IP Library Granted Patent US 12,355,898
Granted Patent B2
US 12,355,898 · App. 18/348,630 · Granted Jul 8, 2025

System and method for secure Internet communications

Inventors: Jose Manuel Rivera (Burke, VA); Michael Lasky (Silver Spring, MD); Andrew Bruce (Glen Rock, PA)
Assignee: TripleCyber Corp.
H04L9/3263H04L9/30H04L9/50
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,355,898
App. No.
18/348,630
Granted
Jul 8, 2025
Kind
B2
Abstract

This invention is directed toward a method for facilitating secure communications on the Internet that allows individual actors to be registered, their identities to be confirmed at an acceptable level of confidence, and their association with, and/or ownership of, certain user identifiers (such as email addresses, phone numbers, domain names, application usernames, and the like), to be verified. The invention also enables Internet actors to communicate securely and to encrypt or sign digital messages and/or documents between each other while maintaining sole possession and control of their private cryptographic keys. To ensure that the integrity of user information has not been compromised, the invention includes embodiments that periodically backup crucial data in a publicly accessible blockchain format that can be independently verified and is difficult to alter.

Claims (54)

1. A method for facilitating secure electronic communications, comprising:

(A) registering a plurality of users in a database management system (DBMS) residing on a centrally controlled computing server accessible via the Internet, the registering step comprising for each such user:

receiving a public key component of a public/private key pair, the public key having an assigned security level to facilitate customization of secure communications, the assigned security level having a setting selected from two or more security options,

receiving an electronic address of the user,

receiving a name of the user and a residence address of the user,

obtaining, from a trusted external name-address information source, a trusted user name associated with the user and a trusted residence address associated with the user,

responsive to obtaining the trusted user name and the trusted residence address, validating the electronic address of the user for secure communications, including:

verifying the assigned security level, and

comparing the name of the user and the residence address of the user received from the user with corresponding user name and address information received from the trusted external name-address information source, and when there is a match, accepting the user for subsequent communications at an increased security level, and

storing, in a record in the DBMS, the electronic address of the user, the name of the user, the residence address of the user, the public key, the assigned or increased security level of the public key, and a result of the secure communications validation;

(B) receiving, at the DBMS a request to communicate directly with the electronic address of the user; and

(C) in response to the request:

(1) locating, within the DBMS, a matching record containing the electronic address of the user,

(2) extracting, from the matching record, the public key, and

(3) transmitting the extracted public key to support the request.

2. The method of claim 1 , wherein validating the electronic address of the user for secure communications further comprises:

verifying the electronic address of the user by sending a prepared Universal Resource Locator (URL) to the electronic address of the user and receiving a notification that the prepared URL was accessed within a specified period of time.

3. The method of claim 1 , wherein the electronic address of the user comprises an email address.

4. The method of claim 1 , wherein the electronic address of the user comprises a phone number.

5. The method of claim 1 , further comprising:

exporting one or more portions of the DBMS to a cryptographic chain comprising a plurality of chained records, each chained record comprising data extracted from one of the records in the DBMS;

transmitting a copy of the cryptographic chain to an immutable, append-only storage via a secure connection; and

providing public access to the transmitted cryptographic chain in the storage.

6. A system to facilitate secure electronic communications, comprising:

a registration module to register one or more users in a database management system (DBMS), the DBMS residing on a centrally controlled computing server accessible via the Internet, for each such user the registration module configured to:

receive a public key component of public/private key pair, the public key having an assigned security level to facilitate customization of secure communications, the assigned security level having a setting selected from one of two or more security options,

receive an electronic address of the user, and

receive a name of the user and a residence address of the user,

obtain, from a trusted external name-address information source, a trusted user name associated with the user and a trusted residence address associated with the user,

a verification module configured to:

verify the electronic address of the user for secure communications, including verification of the assigned security level, and

compare the name of the user and the residence address of the user received from the user with corresponding user name and address information received from the trusted external name-address information source, and when there is a match, accept the user for subsequent communications at an increased security level,

the registration module configured to create and store a registered user record, the record including the electronic address of the user, the name of the user, the residence address of the user, the public key, the assigned security level of the public key, and a result of secure communication verification,

a public key services module configured to process a request to communicate directly with the electronic address of the user; and

in response to the request:

identify, within the DBMS, a matching record containing the electronic address of the user,

extract, from the matching record, the public key, and

transmit the extracted public key to support the request.

7. The system of claim 6 , wherein the electronic address of the user comprises an email address.

8. The system of claim 6 , wherein the electronic address of the user comprises a phone number.

9. The system of claim 6 , further comprising a cryptographic chain services module configured to:

export one or more portions of the DBMS to a cryptographic chain comprising a plurality of chained records, each chained record comprising data extracted from one of the records in the DBMS;

transmit a copy of the cryptographic chain to an immutable, append-only storage via a secure connection; and

provide public access to the transmitted cryptographic chain in the storage.

10. The system of claim 6 , wherein the trusted external name-address information source is used to verifiably link the name of the user and the residence address of the user with the electronic address of the user.

11. The system of claim 6 , wherein the trusted external name-address information source is a government database.

12. The system of claim 6 , wherein the verification module is further configured to access two or more trusted external name-address information sources to obtain the trusted user name associated with the user and the trusted residence address associated with the user.

13. The system of claim 12 , wherein the verification module is further configured to access the two or more trusted external name-address information sources in a sequential fashion based on results obtained and a specific security level being sought by the user.

14. The system of claim 6 , wherein the trusted external name-address information source is a trusted third-party source different from the DBMS and the user.

15. The method of claim 1 , wherein the trusted external name-address information source is used to verifiably link the name of the user and the residence address of the user with the electronic address of the user.

16. The method of claim 1 , wherein the trusted external name-address information source is a government database.

17. The method of claim 1 , wherein obtaining the trusted user name associated with the user and the trusted residence address associated with the user includes accessing two or more trusted external name-address information sources.

18. The method of claim 17 , wherein accessing the two or more trusted external name-address information sources includes accessing each of the trusted name-address sources in a sequential fashion based on results obtained and a specific security level being sought by the user.

19. The method of claim 1 , wherein the trusted external name-address information source is a trusted third-party source different from the DBMS and the user.

Continuity (3)
Continuation 17729177 · Apr 26, 2022
Provisional Application 63181297 · Apr 29, 2021
Related Publication 20230362018A1 · Nov 9, 2023
References Cited (34)
US 9419951B1 · Felsher et al. · 2016 [cited by applicant]
US 10749676B2 · Simons · 2020 [cited by applicant]
US 10972274B2 · Redpath et al. · 2021 [cited by applicant]
US 10972475B1 · Zaki et al. · 2021 [cited by applicant]
US 20060112280A1 · Cohen et al. · 2006 [cited by applicant]
US 20060282528A1 · Madams et al. · 2006 [cited by applicant]
US 20090288150A1 · Toomim et al. · 2009 [cited by applicant]
US 20170346851A1 · Drake · 2017 [cited by applicant]
US 20180227293A1 · Uhr · 2018 [cited by examiner]
US 20190130384A1 · Shauh · 2019 [cited by examiner]
US 20190158481A1 · Ronda et al. · 2019 [cited by applicant]
US 20200005290A1 · Madisetti et al. · 2020 [cited by applicant]
US 20200044823A1 · Savir et al. · 2020 [cited by applicant]
US 20200073657A1 · Robison et al. · 2020 [cited by applicant]
US 20200136803A1 · Prasad · 2020 [cited by examiner]
US 20200220729A1 · Hudson et al. · 2020 [cited by applicant]
US 20200220730A1 · Hudson et al. · 2020 [cited by applicant]
US 20200334771A1 · Li · 2020 [cited by applicant]
US 20210117385A1 · Haldar et al. · 2021 [cited by applicant]
US 20210241256A1 · Caldwell · 2021 [cited by examiner]
US 20210342850A1 · Kumar · 2021 [cited by applicant]
JP 2003244120A · 2003 [cited by applicant]
JP 2008234143A · 2008 [cited by applicant]
JP 2011095824A · 2011 [cited by applicant]
WO 2021074719A1 · 2021 [cited by applicant]
Wazid, M., Das, A.K., Odelu, V., Kumar, N., Conti, M. and Jo, M., 2017. Design of secure user authenticated key management protocol for generic IoT networks. IEEE Internet of Things Journal, 5(1), pp. 269-282. (Year: 20… [cited by examiner]
Lux, Z.A., Thatmann, D., Zickau, S. and Beierle, F., Sep. 2020, Distributed-ledger-based authentication with decentralized identifiers and verifiable credentials. In 2020 2nd Conference on Blockchain Research & Applicat… [cited by examiner]
Notice of Reasons for Refusal JP2023-566546, Oct. 22, 2024. [cited by applicant]
Office Action U.S. Appl. No. 17/729,177, Dec. 2, 2022. [cited by applicant]
PCT Search Report, PCT/US22/26665, Aug. 26, 2022. [cited by applicant]
PCT Written Opinion, PCT/US22/26665, Aug. 26, 2022. [cited by applicant]
Antonopoulos, P., et al., Jun. 2021. SQL ledger: Crypographically verifiable data in azure SQL database. In Proceedings of the 2021 international conference on management of data (pp. 2437-2449). (Year: 2021). [cited by applicant]
Zhaofeng, M. et al., 2019. Blockchain-enabled decentralized trust management and secure usage control of IoT big data. IEEE Internet of Things Journal, 7(5), pp. 4000-4015. (Year: 2019). [cited by applicant]
Office Action U.S. Appl. No. 17/729,177, Jul. 21, 2022. [cited by applicant]