IP Library Granted Patent US 12,634,145
Granted Patent B2
US 12,634,145 · App. 18/402,526 · Granted May 19, 2026

Cryptographic trust system for electronic communications integrity using tuple spaces and messaging user agents

Inventors: Thomas Gray (Mansfield, CA); Logendra Naidoo (Ottawa, CA)
Assignee: Mitel Networks Corporation
H04L9/3242H04L9/3247
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,634,145
App. No.
18/402,526
Granted
May 19, 2026
Kind
B2
Abstract

An electronic communication system for certification of an electronic communication includes: (1) a cryptographic trust server (CTS); (2) a common memory to store electronic communications; (3) a tuple server configured to generate tuple spaces; (4) a first user device; and (5) a first messaging user agent (MUA) associated with the first user device. The first MUA is configured to generate an MUA cryptographic hash for a first electronic communication, and the MUA places the first electronic communication with the cryptographic hash in the common memory, optionally with an iterative communication thread of prior electronic communications. The first MUA places an alert and the location of the first electronic communication in a tuple space provided by the tuple server. The alert notifies the CTS to access the common memory to review and verify or not verify the MUA cryptographic hash and optionally verify or not verify a CTS hash of the iterative communication thread.

Claims (39)

1 . An electronic communication system configured to certify an iterative electronic communication thread, wherein the system comprises:

a cryptographic trust server (CTS) configured to validate the iterative electronic communication thread;

a tuple server configured to generate tuple spaces that are in communication with the CTS;

a common memory in communication with the CTS, the common memory being configured to store electronic communications;

a first user device associated with a first user, wherein the first user device is configured to facilitate the creation of a first electronic communication by the first user; and

a first messaging user agent (MUA) associated with and in communication with (a) the first user device, (b) a first tuple space generated by the tuple server, and (c) the common memory, wherein the first MUA is configured to (d) generate an MUA cryptographic hash for the first electronic communication utilizing a private key of the first MUA, (e) transmit the iterative electronic communication thread including the first electronic communication with the MUA cryptographic hash to the common memory, and (f) place in the first tuple space (i) an MUA alert indicating that the iterative electronic communication including the first electronic communication has been added to the common memory, and (ii) the location in the common memory where the first electronic communication is located;

wherein the CTS, in response to the MUA alert, is configured to access the common memory and either (a) verifies the authenticity of (i) a CTS hash that the CTS previously placed on the iterative electronic communication thread prior to the first electronic communication being added, and (ii) the MUA cryptographic hash for the first electronic communication, and (iii) places a new CTS hash on the iterative electronic communication thread including the first electronic communication, or (b) does not verify the authenticity of (i) the CTS hash that the CTS previously placed on the iterative electronic communication thread prior to the first electronic communication being added, or (ii) the MUA cryptographic hash for the first electronic communication, and (iii) does not place the new CTS hash on the iterative electronic communication thread including the first electronic communication; and

if the authenticity of the iterative electronic communication thread including the first electronic communication is verified, the CTS is further configured to (a) place a first CTS alert in the tuple space to indicate same to the first MUA, or (b) place a second CTS alert in a second tuple space to indicate same to a second MUA.

2 . The electronic communication system of claim 1 , wherein the first MUA digitally signs the first electronic communication if it is verified by the CTS.

3 . The electronic communication system of claim 1 , wherein the MUA is further configured to transmit to the tuple space a thread identifier and the location in the common memory of each contribution to the iterative electronic communication thread, and the CTS either (a) verifies the authenticity of each contribution in the iterative electronic communication thread, places the CTS hash on the iterative electronic communication thread, and permits it to be received and opened by another user device, or (b) does not verify the authenticity of the iterative electronic communication thread, does not place the CTS hash on the iterative electronic communication thread, and does not permit it to be received and opened by another user device.

4 . The electronic communication system of claim 1 , wherein if the CTS places the first CTS alert in the tuple space, the first MUA receives the CTS hash and is configured to permit the iterative electronic communication thread including the first electronic communication to be (a) sent to, and (b) opened by another user device.

5 . The electronic communication system of claim 1 , wherein the iterative electronic communication thread including the first electronic communication is sent to a second user device in communication with the second MUA, the tuple server generates a second tuple space, the CTS places the second CTS alert in the second tuple space, and the second MUA receives the second CTS alert and permits the second user device to receive and open the iterative electronic communication thread including the first electronic communication.

6 . The electronic communication system of claim 1 , wherein the first MUA is further configured to place a digital signature on the first electronic communication if the MUA cryptographic hash is verified by the CTS.

7 . The electronic communication system of claim 1 that further comprises a second client device configured to receive the iterative electronic communication thread including the first electronic communication, wherein the second client device is in communication with the second MUA, wherein the second MUA is configured to query the CTS before permitting the second client device to receive the iterative electronic communication thread including the first electronic communication by placing a second MUA alert in the second tuple space to cause the CTS to authenticate the MUA cryptographic hash and the CTS hash.

8 . The electronic communication system of claim 7 , wherein the second MUA is further configured to add a start marker and an end marker to the first electronic communication.

9 . The electronic communication system of claim 1 , wherein the iterative electronic communication thread is an email thread, and the system further includes an email server in communication with the first client device.

10 . The electronic communication system of claim 1 , wherein the first MUA is a plugin of the first client device.

11 . A computer method of certifying electronic communications within an iterative electronic communication thread, wherein the method comprises the steps of:

using a first user device associated with a first user, creating a first electronic communication;

generating a first tuple space using a tuple server;

using a first MUA in communication with the first user device and in communication with the first tuple space, generating an MUA cryptographic hash for the first electronic communication using a private key of the first MUA, and placing the iterative electronic communication thread including the first electronic communication with the cryptographic hash into a common memory, and placing an alert in the first tuple space, wherein the alert notifies a CTS of the presence of the first electronic communication in the common memory; and

in response to the alert, the CTS verifying the authenticity of (i) a CTS hash placed on the iterative electronic communication thread prior to the first electronic communication being added, and (ii) the MUA cryptographic hash for the first electronic communication, and (iii) placing a new CTS hash on the iterative electronic communication thread including the first electronic communication or not verifying (i) the CTS hash previously placed on the iterative electronic communication thread prior to the first electronic communication being added, or (ii) the MUA cryptographic hash for the first electronic communication, and (iii) not placing the new CTS hash on the iterative electronic communication thread including the first electronic communication.

12 . The computer method of claim 11 that further comprises the step of the first MUA placing in the first tuple space the location of the first electronic communication in the common memory.

13 . The computer method of certifying electronic communications within an iterative electronic communication thread of claim 12 , wherein the CTS either (a) verifies the authenticity of the MUA cryptographic hash, places a CTS hash on the first electronic communication and permits the first electronic communication to be received and opened by another user device, or (b) does not verify the authenticity of the MUA cryptographic hash, does not place the CTS hash on the first electronic communication, and does not permit it to be received and opened by another user device.

14 . The computer method of certifying electronic communications within an iterative electronic communication thread of claim 12 that further includes the steps of the CTS (a) verifying the authenticity of each contribution in the iterative electronic communication thread by reviewing a first CTS hash and the MUA cryptographic hash, and placing a second CTS hash on the iterative electronic communication thread including the first electronic communication, and permitting it to be received and opened by another user device, or (b) not verifying the authenticity of each contribution in the iterative electronic communication thread including the first electronic communication, not placing the second CTS hash on the iterative electronic communication thread including the first electronic communication, and not permitting it to be received and opened by another user device.

15 . The computer method of certifying electronic communications within an iterative electronic communication thread of claim 12 that further includes the step of one or more of the first MUA and the CTS alerting one or more of the first user device, another MUA, another user device, and a system administrator if an electronic communication is not authenticated by the CTS.

16 . The computer method of certifying electronic communications within an iterative electronic communication thread of claim 12 that further includes the step of the first MUA adding a thread identifier and a location within the common memory for each electronic communication within the iterative electronic communication thread into the first tuple space to assist the CTS in verifying the authenticity of each electronic communication within the iterative electronic communication thread.

17 . The computer method of certifying electronic communications within an iterative electronic communication thread of claim 15 that further includes the step of storing in the common memory the first electronic communication thread MUA cryptographic hash.

18 . A method of certifying iterative electronic communications in an iterative electronic communication thread that comprises the steps of:

a first MUA identifying a first electronic communication created by a first user device, wherein the first electronic communication is added to the iterative electronic communication thread;

the first MUA placing an MUA cryptographic hash on the first electronic communication and placing the iterative electronic communication thread including the first electronic communication into a common memory;

the first MUA placing an alert in a first tuple space generated by a tuple server, wherein the first tuple space is in communication with a CTS, wherein the CTS reviews the MUA cryptographic hash in the common memory;

the CTS either verifying or rejecting the first electronic communication based on the information in the MUA cryptographic hash and communicating the verification or rejection to the first MUA via the first tuple space; and

the MUA transmitting the iterative electronic communication thread including the first electronic communication if the first electronic communication is verified by the CTS and blocking transmission if the first electronic communication is rejected by the CTS.

19 . The computer method of certifying iterative electronic communications in an iterative electronic communication thread of claim 18 that further comprises the steps of:

receiving, on a second user device in communication with a second MUA, the iterative electronic communication thread including the first electronic communication;

the second MUA transmitting the iterative electronic communication thread including the first electronic communication to the common memory, and placing a second alert in a second tuple space generated by the tuple server, wherein the second alert notifies the CTS to review the MUA cryptographic hash of the first electronic communication; and

the CTS examining and (a) verifying the authenticity of the MUA cryptographic hash and permitting the first electronic communication to be opened by the second user device, or (b) not verifying the authenticity of the MUA cryptographic hash, and not permitting the first electronic communication to be opened by the second user device.

20 . The computer method of certifying iterative electronic communications in an iterative electronic communication thread of claim 18 that further includes the steps of the CTS (a) verifying the authenticity of each contribution to the iterative electronic communication thread including the first electronic communication, placing a CTS hash on the iterative electronic communication thread including the first electronic communication, and permitting the iterative electronic communication thread including the first electronic communication, to be received and opened by another user device, or (b) not verifying the authenticity of the iterative electronic communication thread including the first electronic communication, not placing the CTS hash on the iterative electronic communication thread including the first electronic communication, and not permitting the iterative electronic communication thread including the first electronic communication, to be received and opened by another user device.

Assignments (5)
SECURITY INTEREST Recorded Jun 30, 2025
From: MLN US HOLDCO LLC; MITEL (DELAWARE), INC.; MITEL NETWORKS CORPORATION; MITEL NETWORKS, INC.
To: U.S. PCI SERVICES, LLC
Reel/Frame 071758/0843 →
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2025
From: ACQUIOM AGENCY SERVICES LLC
To: MITEL (DELAWARE), INC.; MITEL NETWORKS, INC.; MITEL NETWORKS CORPORATION
Reel/Frame 071730/0632 →
SECURITY INTEREST Recorded Jun 20, 2025
From: MITEL (DELAWARE), INC.; MITEL NETWORKS CORPORATION; MITEL NETWORKS, INC.
To: ACQUIOM AGENCY SERVICES LLC
Reel/Frame 071676/0815 →
SECURITY INTEREST Recorded Mar 12, 2025
From: MITEL (DELAWARE), INC.; MITEL NETWORKS CORPORATION; MITEL NETWORKS, INC.
To: ACQUIOM AGENCY SERVICES LLC
Reel/Frame 070689/0857 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 2, 2024
From: GRAY, THOMAS; NAIDOO, LOGENDRA
To: MITEL NETWORKS CORPORATION
Reel/Frame 065998/0164 →
Continuity (1)
Related Publication 20250219842A1 · Jul 3, 2025
References Cited (28)
US 8571993B2 · Kocher et al. · 2013 [cited by applicant]
US 8578169B2 · Adams et al. · 2013 [cited by applicant]
US 10044662B1 · Mesters et al. · 2018 [cited by applicant]
US 10305833B1 · Dennis · 2019 [cited by applicant]
US 10505736B1 · Meixler · 2019 [cited by examiner]
US 10574453B2 · Notani · 2020 [cited by applicant]
US 10911386B1 · Beckman · 2021 [cited by examiner]
US 10986169B2 · Ziebell · 2021 [cited by examiner]
US 11895151B1 · Castro · 2024 [cited by examiner]
US 20050198511A1 · Tomkow · 2005 [cited by examiner]
US 20060200523A1 · Tokuda · 2006 [cited by examiner]
US 20120066498A1 · Engert · 2012 [cited by examiner]
US 20160366091A1 · Baldwin · 2016 [cited by examiner]
US 20160380942A1 · Salpe · 2016 [cited by examiner]
US 20170134323A1 · Alexander et al. · 2017 [cited by applicant]
US 20180152461A1 · Albisu · 2018 [cited by examiner]
US 20180219810A1 · Santos Ramirez · 2018 [cited by examiner]
US 20190312831A1 · Gupta · 2019 [cited by examiner]
US 20190349426A1 · Smith et al. · 2019 [cited by applicant]
US 20210029170A1 · Gupta · 2021 [cited by examiner]
US 20210149720A1 · Mehta · 2021 [cited by examiner]
US 20220100498A1 · Guim Bernat · 2022 [cited by examiner]
US 20220198049A1 · Dumas · 2022 [cited by examiner]
US 20240320338A1 · Chhetri · 2024 [cited by examiner]
US 20240422141A1 · Shade · 2024 [cited by examiner]
WO 2017027648A1 · 2017 [cited by applicant]
WO 2020176975A1 · 2020 [cited by applicant]
De, Nikhilesh, “Salesforce Wins Patent Trackling Email Spam With Blockchain”, Website https://www.coindesk.com; Business; Nov. 7, 2018. [cited by applicant]