Patent 09 / Intelligent Hashing Hub
01 / 11 US10999352B1
↑↓ navigate  ·  all patents →
Siten Sanghvi  ·  Granted May 4, 2021

Any protocol in.
Best route out.
Every byte verified.

An AI-driven hub that ingests data over any network protocol, uses machine learning to select the optimal destination server, translates to the right output protocol — and hashes every packet to guarantee end-to-end integrity.

US10999352B1Patent
Jan 7, 2020Filed
16 monthsTime to grant
Multiple ClaimsScope
0 CitationsForward citations
SCROLL TO EXPLORE
Visual patent explainer
02 / The Problem

Protocols fragment. Routing is blind. Data arrives unverified.

Enterprise data flows across dozens of incompatible network protocols. Routing decisions are static — pre-configured, not real-time. And nothing in the standard file-transfer pipeline verifies whether data arrived intact.

Protocol lock-inEach system speaks its own language — translation is manual and error-prone
Static routingRoutes are set in advance; failing servers receive traffic until an admin intervenes
No integrity layerData corruption in transit goes undetected without explicit hashing at the hub
03 / The Invention

Five processors. One intelligent hub.

The intelligent hashing hub places five specialized processing layers between any sender and any destination — handling protocol translation, AI-driven routing, priority ranking, and cryptographic integrity verification in a single appliance.

Transceiver — Any Protocol In, Any Protocol Out

Receives incoming data using any transmission protocol, splits it into groups, and sends those groups out using a second protocol selected by the intelligence engine.

Interrogator — Profile Every Packet

Identifies the incoming protocol, sender identity, and intended recipient before any routing decision is made. This profile drives priority assignment and server selection.

Intelligence Engine + Hashing Processor — Route Smart, Verify Everything

ML selects the best destination server in real time. The hashing processor runs a cryptographic digest on the data before transmission — and again on delivery — to detect any corruption or tampering in transit.
04 / Architecture

Hub in the middle.
Intelligence everywhere.

The hub sits between any number of data senders and destination servers. It handles everything — protocol detection, routing, translation, and hashing — invisibly, without the sender ever knowing where data ends up or what protocol carries it.

Data flow — US10999352B1
Sender A
Protocol 1
Sender B
Protocol 2
Intelligent Hashing Hub
Interrogate · Route · Translate · Hash
Server A
Protocol 3
Server B
Protocol 4
Server C
Protocol 5
05 / The Hash Processor

Every byte.
Fingerprinted.

The hashing processor computes a cryptographic digest of each data payload before routing it. The same hash is verified at the destination — any mismatch means the data was altered, corrupted, or tampered with in transit.

This closes the integrity gap that exists in standard protocol-conversion pipelines, where data arrives looking complete but may have been silently modified between protocol layers.

Hash verification — US10999352B1
06 / AI Routing Engine

Best server.
Real-time.
Every time.

The intelligence engine doesn't use a static routing table. It ranks available destination servers in real time using machine learning — evaluating capacity, bandwidth, latency, and security level — and sends each data group to the current winner.

Historical performance data from each server continuously refines the model, so routing decisions improve with every transfer.

Server selection — US10999352B1
07 / Protocol Translation

Senders never know
what's on the
other side.

The data translation processor converts incoming data from its original protocol to whatever protocol the selected destination server uses. Crucially, the sender never receives information about the output protocol or which server was chosen — a deliberate privacy and security design.

This network obfuscation prevents reverse-engineering of the destination topology and reduces the attack surface from compromised senders.

Protocol conversion flow
📥
Receive
Incoming data arrives in Protocol A (e.g., FTP, HTTP, SFTP — any standard)
🔍
Interrogate
Hub profiles sender, recipient, protocol — invisible to originator
⚙️
Translate
Data translated to Protocol B as selected by the intelligence engine
📤
Deliver
Routed to destination — sender has no visibility into the delivery path
08 / Priority Assignment

Not all data is
equally urgent.

The intelligence engine assigns a priority tier to each incoming data group by analyzing the sender's identity, the recipient's profile, and the time of receipt. High-priority data gets first access to the best-ranked server.

One priority signal is whether the incoming data is likely already publicly available at receipt — data that matches public sources can be deprioritized without integrity risk, freeing bandwidth for genuinely new or sensitive transfers.

Priority factors
Sender ID
Trust level
Recipient
Profile
Time
of receipt
Priority Tier Assigned
High · Medium · Low · Deferred
Best server
routed first
09 / Applications

Where intelligent
routing changes
the equation.

Any environment where data crosses protocol boundaries, routing must adapt in real time, or data integrity is non-negotiable — the intelligent hashing hub adds value without changing sender or receiver systems.

Use cases — US10999352B1
Express
Protocol-Agnostic Data Ingestion Enterprise systems sending data over heterogeneous protocols (FTP, HTTP, SFTP) can route to a common destination without any protocol-specific gateway per sender.
Express
AI-Optimized Server Load Distribution Instead of round-robin, traffic flows to whichever server currently offers the best combination of available capacity, latency, and security posture.
Inferred
Multi-Cloud Data Pipeline Data originating from on-prem systems can be routed across cloud providers based on real-time capacity and cost signals — invisibly, with integrity guaranteed at every hop.
Inferred
Financial Data Integrity Assurance High-value transaction records that traverse multiple systems can be hash-verified at the hub, catching silent corruption before it reaches downstream ledgers or reporting systems.
10 / Citations

No Forward Citations Yet

As of June 2026, no patents have formally cited US10999352B1 in their prior art. The hashing hub architecture — particularly its combination of AI routing and per-packet integrity verification — remains an uncrowded space.

Citation data verified via Google Patents (June 2026). Forward citations will be added here as the patent matures and the technology propagates through the field.
Citation landscape — US10999352B1
Related Patent
US10701135B1
Sibling patent — Protocol-Agnostic File Transfer Hub
Same inventors · Same priority date · 2 forward citations
FILED SAME DAY · COMPLEMENTARY SCOPE
11 / Timeline

Patent Lifecycle

Jan 7, 2020
Filed
Application US16/736,658 filed
16 months
May 4, 2021
Granted
US10999352B1 granted — published with grant (B1)
~19 years
Jan 7, 2040
Expires
Est. expiration (subject to maintenance fees)
End / Patent 09