IP Library Granted Patent US 12,572,629
Granted Patent B2
US 12,572,629 · App. 18/416,222 · Granted Mar 10, 2026

Secure messaging service with digital rights management using blockchain technology

Inventor: Robert Bernardi (McLean, VA)
Assignee: Myseum, Inc.
G06F21/105G06F21/10G06F21/6263H04L9/085H04L51/10H04L51/18H04L63/123
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,572,629
App. No.
18/416,222
Granted
Mar 10, 2026
Kind
B2
Abstract

The invention described herein is directed to a secure text messaging and object sharing mobile application connected to a DRM cloud service that provides encryption, digital rights management (DRM) of the text and of the attachments, blockchain transactions, the capability of attaching documents, photos and so forth, the capability of interfacing with a user's contacts application, and that operates in both Android and iOS environments.

Claims (37)

1 . A method for implementing a secure messaging service with digital rights management (DRM) between a DRM Cloud Server and a set of user computing devices, the method comprising:

receiving, at a Digital Rights Management (DRM) Cloud Server from a first user computing device associated with a first user, a DRM restriction assigned to an electronic messaging object,

wherein the DRM restriction is selected in a DRM Messaging application installed on the first user computing device, and

wherein the first user computing device is configured to transmit encrypted communications to the DRM Cloud Server;

rendering, by the DRM Cloud Server, the electronic messaging object to produce an HTML file of the electronic messaging object, the HTML file saved to a storage location associated with the first user;

transmitting, by the DRM Cloud Server to a second user computing device, a URL link of the HTML file of the electronic messaging object,

wherein the DRM Messaging application is installed on the second user computing device, and

wherein the URL link is displayed within the DRM Messaging application of the second user computing device;

in response to the second user activating the URL link, enabling display, by the DRM Cloud Server from the second user computing device, the HTML file of the electronic messaging object in a browser associated with the DRM Messaging application of the second user computing device; and

monitoring the first user computing device and the second user computing device for a DRM restriction violation assigned to the electronic messaging object; and

when the DRM restriction is violated, enforcing the DRM restriction on the second user computer device by disabling, by the DRM Cloud Server, the URL link to the HTML file.

2 . The method of claim 1 , wherein the electronic messaging object is a DRM-modified electronic messaging object (DRM-MEMO), and wherein the electronic messaging object is selected from a text message, a document, a photo, a video file, and an audio file.

3 . The method of claim 1 , wherein the DRM restriction is selected from copy, save, print, forward, expire, revoke upon violation, disappear, edit, and modify.

4 . The method of claim 1 , wherein the encrypted communications transmitted from the first user computing device to the DRM Cloud Server uses split-key encryption.

5 . The method of claim 1 , wherein the DRM restriction is assigned to the electronic messaging object using XrML to insert a restrictive header into metadata of the electronic messaging object.

6 . The method of claim 1 , wherein the DRM Cloud Server stores the electronic messaging object on a decentralized cloud platform having a blockchain network auditing module and blockchain identity and security module.

7 . The method of claim 6 , wherein the DRM Cloud Server has a blockchain crypto payments module.

8 . The method of claim 1 , wherein the DRM Messaging application installed on the first user computing device comprises a DRM Menu, and wherein the DRM Menu comprises a timed expire option to disable the URL link to the HTML file after a period selected from ranges of 1-30 days, 1-24 hours, and 1-60 minutes.

9 . The method of claim 1 , wherein the first user computing device and the second user computing device are mobile telephones, and wherein the DRM Messaging application is configured as a mobile telephone application.

10 . The method of claim 1 , wherein the electronic messaging object is a specific file type with a specific DRM permission selected from the group consisting of:

a marketing file and a (TCPA) compliant DRM, a commercial message and a CAN-SPAM Act compliant DRM, a financial record and a (GLBA) compliant DRM, a credit record and a (FCRA) compliant DRM, a health record and a (HIPAA) compliant DRM, a student record and a (FERPA) compliant DRM, a DMV record and a (DPPA) compliant DRM, a child's information and a (COPPA) compliant DRM, an online transaction file and a (VPPA) compliant DRM, a subscriber record and a (CCPA) compliant DRM, a personal information file and a (CCPA) compliant DRM, a file stored on a computer and a (CFAA) compliant DRM, a communication file and an (ECPA) compliant DRM, an identification file and a SOX compliant DRM, and a DoD or DFAR related file and a DFAR compliant DRM.

11 . The method of claim 1 , further comprising:

removing the electronic messaging object from the second user computing device.

12 . A system for implementing a secure messaging service with digital rights management (DRM) comprising:

a DRM Cloud Server comprising:

a memory having a URL link associated therewith,

a DRM rendering module configured to render an HTML file of an electronic messaging object, wherein the HTML file is stored in the memory associated with the DRM Cloud Server,

a TCP-IP link messaging module configured to forward the URL link to one of a set of user computing devices, and

a server-side DRM Enforcement module configured to send an enforcement command to one of the set of user computing devices and disable access to the URL link by individual ones of the set of user computing devices in response to receiving an alert that one or more DRM permissions assigned to an electronic message object has been violated; and

the set of user computing devices, individual ones of the set of user computing devices comprising:

a DRM Mobile Messaging Application saved to memory of individual ones of the set of user computing devices having program instructions executable on a processor configured to: initiate assignment of DRM permissions on an electronic messaging object to generate the electronic messaging object,

send, by a TCP-IP communication module, the electronic messaging object, and

a device-side DRM Enforcement module configured to:

process the one or more DRM permissions on the HTML file,

send an alert, encrypted in transit to the DRM Cloud Server when violation of the DRM permissions is detected, and

in response to receiving the alert specifying that at least one DRM permission of the one or more DRM permissions is violated, enforce the DRM permission assigned to the electronic messaging object by disabling, by the DRM Cloud Server, the URL Link to the HTML file; and

a browser associated with the DRM Mobile Messaging Application to request access to the HTML file.

Assignments (6)
CHANGE OF NAME Recorded Dec 11, 2025
From: DATCHAT, INC.
To: MYSEUM, INC.
Reel/Frame 073934/0481 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 18, 2024
From: BERNARDI, ROBERT
To: AVILA TECHNOLOGY, LLC
Reel/Frame 066168/0544 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 18, 2024
From: AVILA TECHNOLOGY, LLC
To: AVILA SECURITY CORPORATION
Reel/Frame 066168/0633 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 18, 2024
From: AVILA TECHNOLOGY, LLC
To: AVILA SECURITY CORPORATION
Reel/Frame 066168/0656 →
MERGER Recorded Jan 18, 2024
From: AVILA SECURITY CORPORATION
To: DATCHAT PATENTS II, LLC
Reel/Frame 066168/0756 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 18, 2024
From: DATCHAT PATENTS II, LLC
To: DATCHAT, INC.
Reel/Frame 066168/0836 →
Continuity (5)
Continuation 17528178 · Nov 16, 2021
Continuation 17197114 · Mar 10, 2021
Continuation 17064559 · Oct 6, 2020
Continuation In Part 16845082 · Apr 10, 2020
Related Publication 20240419766A1 · Dec 19, 2024
References Cited (172)
US 7337146B2 · Heelan · 2008 [cited by applicant]
US 7415439B2 · Kontio · 2008 [cited by applicant]
US 7593991B2 · Friedman · 2009 [cited by applicant]
US 7765404B2 · Lamberg · 2010 [cited by applicant]
US 8090662B2 · Pence · 2012 [cited by applicant]
US 8286255B2 · Grant · 2012 [cited by applicant]
US 8488786B2 · Ferrazzini · 2013 [cited by applicant]
US 8619993B2 · Verma · 2013 [cited by applicant]
US 8635645B2 · Krishnamoorthi · 2014 [cited by applicant]
US 8660539B2 · Khambete · 2014 [cited by applicant]
US 8688583B2 · Boccon-Gibod · 2014 [cited by applicant]
US 8701145B1 · Berger · 2014 [cited by applicant]
US 8726406B2 · Catrein · 2014 [cited by applicant]
US 8806208B2 · Cheng · 2014 [cited by applicant]
US 8831228B1 · Agrawal · 2014 [cited by applicant]
US 9113497B2 · Smith, II · 2015 [cited by applicant]
US 9177112B2 · Bjorkengren · 2015 [cited by applicant]
US 9244916B2 · Berger · 2016 [cited by applicant]
US 9313458B2 · Helms · 2016 [cited by applicant]
US 9363133B2 · Yoakum · 2016 [cited by applicant]
US 9374369B2 · Mahaffey · 2016 [cited by applicant]
US 9374685B1 · Jakatdar · 2016 [cited by applicant]
US 9396325B2 · Kendall · 2016 [cited by applicant]
US 9426133B2 · Boccon-Gibod · 2016 [cited by applicant]
US 9473485B2 · Kendall · 2016 [cited by applicant]
US 9491496B2 · Patadia · 2016 [cited by applicant]
US 9531744B2 · Bettini · 2016 [cited by applicant]
US 9577989B2 · Ackerly · 2017 [cited by applicant]
US 9578021B2 · Ackerly · 2017 [cited by applicant]
US 9582668B2 · Bettini · 2017 [cited by applicant]
US 9621840B2 · Berger · 2017 [cited by applicant]
US 9626667B2 · Boccon-Gibod · 2017 [cited by applicant]
US 9628841B2 · Cho · 2017 [cited by applicant]
US 9635004B2 · Giladi · 2017 [cited by applicant]
US 9679332B2 · Kim · 2017 [cited by applicant]
US 9715814B2 · Sattari · 2017 [cited by applicant]
US 9847975B2 · Medvinsky · 2017 [cited by applicant]
US 9847979B2 · Peterka · 2017 [cited by applicant]
US 9864405B2 · Trachtenberg · 2018 [cited by applicant]
US 9900306B2 · Handal · 2018 [cited by applicant]
US 9923844B1 · Kret · 2018 [cited by applicant]
US 9934600B2 · Sarafa · 2018 [cited by applicant]
US 9948580B2 · Reed · 2018 [cited by applicant]
US 9948588B2 · O'Connor · 2018 [cited by applicant]
US 9965628B2 · Ford · 2018 [cited by applicant]
US 9967553B1 · Kim-Whitty · 2018 [cited by applicant]
US 9972239B2 · Trachtenberg · 2018 [cited by applicant]
US 9979702B2 · Nugent · 2018 [cited by applicant]
US 9979707B2 · Miller · 2018 [cited by applicant]
US 10015169B2 · Kennedy · 2018 [cited by applicant]
US 10110960B2 · Roberts · 2018 [cited by applicant]
US 10123065B2 · Lyons · 2018 [cited by applicant]
US 10210341B2 · Roth · 2019 [cited by applicant]
US 10319022B2 · Clayton · 2019 [cited by applicant]
US 10332478B2 · Trachtenberg · 2019 [cited by applicant]
US 10387857B2 · Kim · 2019 [cited by applicant]
US 10429801B2 · Billings · 2019 [cited by applicant]
US 10504418B2 · Trachtenberg · 2019 [cited by applicant]
US 10536422B1 · Rao · 2020 [cited by applicant]
US 10539806B2 · Kim-Whitty · 2020 [cited by applicant]
US 10565621B2 · Dewitt · 2020 [cited by applicant]
US 10601794B2 · Srinivasan · 2020 [cited by applicant]
US 10608974B2 · Longdale · 2020 [cited by examiner]
US 10693872B1 · Larson · 2020 [cited by applicant]
US 10742732B1 · Lindeman · 2020 [cited by applicant]
US 10873852B1 · Bernardi · 2020 [cited by applicant]
US 10958629B2 · Hybertson · 2021 [cited by applicant]
US 11003802B2 · Auh · 2021 [cited by examiner]
US 11019261B2 · Chase · 2021 [cited by applicant]
US 11023973B2 · Køber · 2021 [cited by applicant]
US 11100197B1 · Bernardi · 2021 [cited by applicant]
US 11151229B1 · Bernardi · 2021 [cited by applicant]
US 11176226B2 · Bernardi · 2021 [cited by applicant]
US 11822626B2 · Bernardi · 2023 [cited by applicant]
US 11914684B2 · Bernardi · 2024 [cited by examiner]
US 20030078890A1 · Schmidt · 2003 [cited by applicant]
US 20030131353A1 · Blom · 2003 [cited by applicant]
US 20030236892A1 · Coulombe · 2003 [cited by applicant]
US 20040101141A1 · Alve · 2004 [cited by applicant]
US 20040158741A1 · Schneider · 2004 [cited by applicant]
US 20050008163A1 · Leser · 2005 [cited by applicant]
US 20060031351A1 · Marston · 2006 [cited by applicant]
US 20060161666A1 · Cohen · 2006 [cited by applicant]
US 20060176902A1 · Bellordre · 2006 [cited by applicant]
US 20070079381A1 · Hartung · 2007 [cited by applicant]
US 20070104181A1 · Lee · 2007 [cited by applicant]
US 20070204064A1 · Mail · 2007 [cited by applicant]
US 20070204078A1 · Boccon-Gibod · 2007 [cited by applicant]
US 20070217595A1 · Lee · 2007 [cited by applicant]
US 20080086779A1 · Blake · 2008 [cited by applicant]
US 20080098212A1 · Helms · 2008 [cited by applicant]
US 20080189213A1 · Blake · 2008 [cited by applicant]
US 20090037388A1 · Cooper · 2009 [cited by applicant]
US 20090052863A1 · Parmar · 2009 [cited by applicant]
US 20090167531A1 · Ferguson · 2009 [cited by applicant]
US 20110071891A1 · Gavita · 2011 [cited by applicant]
US 20110072267A1 · Johansson · 2011 [cited by applicant]
US 20120066495A1 · Hao · 2012 [cited by applicant]
US 20120095749A1 · Capretta · 2012 [cited by applicant]
US 20120131120A1 · Maghraby · 2012 [cited by applicant]
US 20120240240A1 · Naslund · 2012 [cited by applicant]
US 20120303490A1 · Hill · 2012 [cited by applicant]
US 20130054965A1 · Catrein · 2013 [cited by applicant]
US 20130173378A1 · Scholes · 2013 [cited by applicant]
US 20130179949A1 · Shapiro · 2013 [cited by applicant]
US 20130227636A1 · Bettini · 2013 [cited by applicant]
US 20130227683A1 · Bettini · 2013 [cited by applicant]
US 20130347094A1 · Bettini · 2013 [cited by applicant]
US 20140040622A1 · Richard · 2014 [cited by applicant]
US 20140161356A1 · Tesch · 2014 [cited by applicant]
US 20140161423A1 · Tesch · 2014 [cited by applicant]
US 20140163956A1 · Tesch · 2014 [cited by applicant]
US 20140163957A1 · Tesch · 2014 [cited by applicant]
US 20140163980A1 · Tesch · 2014 [cited by applicant]
US 20140164371A1 · Tesch · 2014 [cited by applicant]
US 20140164506A1 · Tesch · 2014 [cited by applicant]
US 20140222963A1 · Gangadharan · 2014 [cited by applicant]
US 20140279475A1 · Castrechini · 2014 [cited by applicant]
US 20140310527A1 · Veugen · 2014 [cited by applicant]
US 20140355955A1 · Berger · 2014 [cited by applicant]
US 20150007264A1 · Maldaner · 2015 [cited by applicant]
US 20150074715A1 · Berger · 2015 [cited by applicant]
US 20150095645A1 · Eldar · 2015 [cited by examiner]
US 20150143455A1 · Bettini · 2015 [cited by applicant]
US 20150227722A1 · Cholas · 2015 [cited by applicant]
US 20150236905A1 · Bellan · 2015 [cited by applicant]
US 20150242747A1 · Packes · 2015 [cited by applicant]
US 20150269366A1 · Bells · 2015 [cited by applicant]
US 20150310188A1 · Ford · 2015 [cited by examiner]
US 20150350712A1 · Sarosi · 2015 [cited by applicant]
US 20160007074A1 · Marsh · 2016 [cited by applicant]
US 20160142381A1 · Shiraishi · 2016 [cited by applicant]
US 20160149970A1 · Jacquemot · 2016 [cited by applicant]
US 20160365973A1 · Van Deventer · 2016 [cited by applicant]
US 20170041296A1 · Ford · 2017 [cited by applicant]
US 20170099293A1 · Tan · 2017 [cited by applicant]
US 20170132630A1 · Castinado · 2017 [cited by applicant]
US 20170243028A1 · Lafever · 2017 [cited by applicant]
US 20170295475A1 · Patel · 2017 [cited by applicant]
US 20170374311A1 · Trachtenberg · 2017 [cited by applicant]
US 20180114205A1 · Thomas · 2018 [cited by applicant]
US 20190035008A1 · Venters, III · 2019 [cited by applicant]
US 20190158544A1 · Ohneck · 2019 [cited by applicant]
US 20190173854A1 · Beck · 2019 [cited by applicant]
US 20190213304A1 · Webb · 2019 [cited by applicant]
US 20190335133A1 · Sharif-Ahmadi · 2019 [cited by applicant]
US 20190386969A1 · Verzun · 2019 [cited by applicant]
US 20190387191A1 · Sharif-Ahmadi · 2019 [cited by applicant]
US 20200065853A1 · Cvinar · 2020 [cited by applicant]
US 20200092270A1 · Ackerly · 2020 [cited by applicant]
US 20200126594A1 · Berger · 2020 [cited by applicant]
US 20200142750A1 · Kaplan · 2020 [cited by applicant]
US 20200245048A1 · Chase · 2020 [cited by applicant]
US 20200266976A1 · Roth · 2020 [cited by applicant]
US 20200374113A1 · Noam · 2020 [cited by applicant]
US 20210135845A1 · Adibi · 2021 [cited by applicant]
US 20220179925A1 · Krajicek · 2022 [cited by applicant]
US 20230086191A1 · Jakobsson · 2023 [cited by examiner]
Cohen (A Legal Guide To Privacy and Data Security 2019, 2019, 178 pages) (Year: 2019). [cited by examiner]
Davies et al. “Evaluating Two Approaches for Browser-Based Real-Time Multimedia Communication”, MoMM2012, Dec. 3-5, 2012 (Year: 2012), 9 pages. [cited by applicant]
Faklaris, C., et al., “Oh Snap! The State of Electronic Discovery Amid the Rise of Snapchat, WhatsApp, Kik, and Other Mobile Messaging Apps”, The Computer & Internet Lawyer, vol. 33, No. 10, Oct. 2016 (Year: 2016), pp. … [cited by applicant]
Goulao, Antonio, et al., “Sharelff: A Sticky Policy Middleware for Self-Destructing Messages in Android Applications”, 2016 IEEE 35th Symposium on Reliable Distributed Systems (SRDS), (Year: 2016), pp. 11-20. [cited by applicant]
Katalov, V., “iMessage Security, Encryption and Attachments”, IcomSoft blog, Nov. 15, 2018 (Year: 2018), pp. 1-11. [cited by applicant]
Lea, K., “Does Someone Know When You Save Their Chat on Snapchat?”, Quora.com, Apr. 2019 (Year: 2019), pp. 1-3. [cited by applicant]
Li et al., “Block-Secure: Blockchain Based Scheme for Secure P2W Cloud Storage”, Information Sciences, Elsevier Inc., (Year: 2018), pp. 219-231. [cited by applicant]
Locklizard, “Safeguard Enterprise PDF Security Product Manual for Windows”, Version 5, Revision 1.36, 2018 (Year: 2018), 265 pages. [cited by applicant]
Rescorla, E. K., “RFC 9999”, Stream: Internet Engineering Task Force (IETF), Category: Standards Track, Aug. 2019 (Year: 2019), ISSN: 2070-1721, 41 pages. [cited by applicant]
Rinaldi, “Peer to Peer Digital Rights Management Using Blockchain”, University of the Pacific, Thesis, 2018 (Year: 2018), 68 pages. [cited by applicant]
Sergiienko, “WebRTC Blueprints”, Packt Publishing, 2014 (Year: 2014), 176 pages. [cited by applicant]
Sredojev et al., “WebRTC Technology Overview and Signaling Solution Design and Implementation”, MIPRO 2015, May 25-29, 2015 (Year: 2015), 4 pages. [cited by applicant]
GSM Association, “WebRTC to Complement IP Communication Services”, Version 1.0, Feb. 20, 2016 (Year: 2016), 33 pages. [cited by applicant]
Menegay, Peter, et al., “Secure Communications Using Blockchain Technology”, IEEE, 2018, (Year: 2018), pp. 599-604. [cited by applicant]