IP Library Granted Patent US 11,822,626
Granted Patent B2
US 11,822,626 · App. 17/408,495 · Granted Nov 21, 2023

Secure web RTC real time communications service for audio and video streaming communications

Inventor: Robert Bernardi (McLean, VA)
Assignee: DatChat, Inc.
G06F21/105G06F21/6263H04L9/085H04L51/10H04L51/18H04L63/123G06F21/10
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 11,822,626
App. No.
17/408,495
Granted
Nov 21, 2023
Kind
B2
Abstract

Secure Real Time Communications Service (SRTCS) for audio and video streaming communications and content sharing that securely connects multiple users using a “push-button” WebRTC chat app connection over a Peer-to-Peer (P2P) network. SRTCS uniquely combines advanced security technologies to provide user based permissions control when communicating and sharing rich media content with other users including End-to-End Encryption (E2EE), Hash Technology (DHT), and Digital Rights Protection (DRM). SRTCS has also designed a unique cloud based streamed video storage and sharing platform service for consumers and business video storage and sharing applications.

Claims (26)

1. A method comprising:

sending, by a first Web Real-Time Communication (WebRTC) chat application on a first communication device, a first telephone number of the first communication device, a private device Internet Protocol (IP) address of the first communication device, and a JavaScript Object Notation (JSON) Short Message Service (SMS) message comprising a second telephone number of a second communication device and an invitation to join a chat session, the chat session being transmitted via a WebRTC-Gateway Server, and the WebRTC-Gateway Server configured to mediate media communications and exchange JSON messages and Real-time Transport Protocol (RTP)/RTP Control Protocol (RTCP) messages with the second communication device;

connecting a private blockchain module to the WebRTC-Gateway Server to enable the WebRTC-Gateway Server to establish a permission-based access control layer that governs network access by the first communication device and the second communication device, the private blockchain module generating an immutable record of WebRTC connection transactions between the first communication device and the second communication device, and the private blockchain module storing the second telephone number of the second communication device;

sending, in a second WebRTC chat application on the second communication device, a JSON SMS message reply containing an answer to the invitation and a private IP address of the second communication device to the WebRTC-Gateway Server;

establishing a communication between the WebRTC-Gateway Server and a signaling server, the signaling server configured to provide communication discovery and media format negotiation between the first communication device and the second communication device;

establishing an encrypted WebRTC connection between the first WebRTC chat application on the first communication device and the second WebRTC chat application on the second communication device;

deploying an advanced security technology module to provide user-based permission control when communicating and sharing content; and

connecting a Distributed Ledger Technology (DLT) module to the WebRTC-Gateway Server, recording WebRTC audio and video transactions, and storing the WebRTC audio and video transactions and user personally identifiable information (PII) in distributed blocks of the private blockchain module.

2. The method of claim 1 , wherein the first WebRTC chat application on the first communication device comprises video chat and voice chat.

3. The method of claim 2 , further comprising:

storing a second chat session transmitted via the first WebRTC chat application on the first communication device, the second chat session being stored at a cloud storage server connected to the first communication device.

4. The method of claim 3 , wherein the cloud storage server uses a Distributed Hash Table, and wherein the first telephone number of the first communication device is a key mapped to a second value associated with the second chat session.

5. The method of claim 4 , further comprising:

assigning, through of the WebRTC chat application on the first communication device, a digital rights management (DRM) permission to the second chat session, wherein the DRM permission is selected from the group consisting of: record, not record, store, screen share, revoke, expire, offline view, blacklist, copy, forward, screen capture, rights violation, and cancel/disappear, and wherein DRM permission is provided by a DRM module to apply user permissions relating to video/audio streaming on a peer-to-peer (P2P) network connection.

6. The method of claim 5 , further comprising:

rendering, in a rendering module of the cloud storage server, an HTML file of the second chat session, the HTML file stored in the cloud storage server and associated with a uniform resource locator (URL).

7. The method of claim 6 , further comprising:

enforcing the DRM permission of the second chat session,

the cloud storage server in encrypted communication with the second communication device, the second communication device having the second WebRTC chat application operatively connected to a WebRTC browser of the second communication device, wherein the WebRTC browser is configured to enable access, using the URL, the HTML file of the second chat session saved in the cloud storage server, wherein the second chat session is rendered on the cloud storage server,

the first WebRTC chat application enforces the DRM permission of the second chat session using a DRM enforcement module in the first WebRTC chat application, and the DRM enforcement module configured to send an enforcement command when a DRM permission violation is detected, and

the DRM enforcement module configured to revoke an encryption key that encrypts an electronic signal between the first WebRTC chat application and the WebRTC browser, wherein the electronic signal is between a codec associated with the WebRTC browser and a playback component of the second communication device.

8. The method of claim 3 , wherein the private blockchain module is configured to enable controls for verifying user identity, authentication, a digital hash, Group Node Coupling, PII security, content linking, content searching, and content addressing for the cloud storage server.

9. The method of claim 3 , wherein the first WebRTC chat application comprises a hardware security module in communication with the cloud storage server to provide encryption for audio and video streams, and wherein the first WebRTC chat application provides a secret video chat module to prevent video recording/playback using an encrypted key with expiration and revocation controls.

10. The method of claim 1 , wherein the first WebRTC chat application comprises a key management module in communication with the WebRTC-Gateway Server and the signaling server, wherein the key management module is configured to provide homomorphic encryption of a communication between the WebRTC-Gateway Server and the signaling server, and wherein the homomorphic encryption allowing the signaling server to extract the private IP address of the second communication device without decrypting JSON SMS message content.

11. The method of claim 1 , wherein the first WebRTC chat application has an insertable streams module to provide end-to-end encryption, wherein insertable streams transmitted through the insertable streams module iterate on frames to transform an encoded frame to an asynchronous insertable stream.

12. The method of claim 1 , wherein the first communication device is selected from a mobile communication device, a desktop computer communication device, and a tablet communication device.

Assignments (5)
CHANGE OF NAME Recorded Dec 11, 2025
From: DATCHAT, INC.
To: MYSEUM, INC.
Reel/Frame 073934/0481 →
MERGER Recorded Dec 6, 2022
From: AVILA SECURITY CORPORATION
To: DATCHAT PATENTS II, LLC
Reel/Frame 061989/0201 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 6, 2022
From: DATCHAT PATENTS II, LLC
To: DATCHAT, INC.
Reel/Frame 061989/0255 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 19, 2022
From: AVILA TECHNOLOGY, LLC
To: AVILA SECURITY CORPORATION
Reel/Frame 059053/0761 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 18, 2022
From: BERNARDI, ROBERT
To: AVILA TECHNOLOGY, LLC
Reel/Frame 059053/0720 →
Continuity (6)
Continuation 17246593 · May 1, 2021
Continuation 17197114 · Mar 10, 2021
Continuation 17064559 · Oct 6, 2020
Continuation In Part 16845082 · Apr 10, 2020
Related Publication 20220107994A1 · Apr 7, 2022
Related Publication 20230205850A9 · Jun 29, 2023
Cited By (2)
US 12,524,507 US 12,572,629