Local Data Publisher Architecture for Synchronized Data Distribution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

High-volume data communication across geographically dispersed recipients in electronic communications networks is inefficient, particularly for high-bandwidth and low-latency data, leading to increased costs and complexity due to varying network latencies and the need for customized data distribution.

Innovation Solution

A data distribution architecture that incorporates real-time customization and synchronization mechanisms, ensuring all recipients receive data in the same relational order, regardless of transmission delays, by using local data publishers that apply customization information to update control databases and maintain synchronized data streams.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Area of stationary object

If data is distributed to geographically dispersed recipients across wide area networks, then data reaches more recipients, but transmission latency increases and data relationships become unsynchronized

Engineering Contradiction:
Improvegeographic coverageVSAvoidtransmission latency
Core Design Contradiction:
Area of stationary objectVSLoss of time

Solution Approach 1:

The system segments data distribution by creating multiple publication points (local data publishers) geographically distributed across different locations. Each publisher independently receives and publishes data locally, allowing recipients in different geographic regions to access data through their nearest publisher rather than relying on long-distance network transmission from a single central source.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary action by pre-synchronizing data relationships and control information at each local data publisher before recipients need the data. Control databases are updated in advance with synchronization information, so when recipients request data, the relational integrity is already established locally without requiring real-time coordination across wide area networks.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If data is customized for different recipients, then data relevance improves, but system complexity increases

Engineering Contradiction:
Improvedata customizationVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system applies local quality by implementing customization at the local data publisher level rather than centrally. Each publisher maintains its own control database with recipient-specific customization information, allowing data to be tailored to local recipient needs while keeping the overall system architecture simple and decentralized.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

Local data publishers operate autonomously, self-managing their control databases and customization logic without requiring complex centralized coordination. Each publisher independently handles data customization for its local recipients based on pre-configured parameters, reducing the need for complex inter-publisher communication and control mechanisms.

Inventive Principle:
Principle #25Self-service

3Quantity of substance

If high-volume data is transmitted across wide area networks, then data availability improves, but costs increase

Engineering Contradiction:
Improvedata volumeVSAvoidtransmission cost
Core Design Contradiction:
Quantity of substanceVSLoss of energy

Solution Approach 1:

The system segments high-volume data distribution into multiple independent local streams from different geographic publishers. Instead of transmitting all data across wide area networks to a single central point, data is divided and distributed through multiple regional paths, reducing the total volume transmitted over expensive long-distance network infrastructure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system creates local copies of data and control information at each publisher's control database. Rather than repeatedly transmitting the same high-volume data across wide area networks to multiple recipients, each local publisher maintains synchronized copies locally, allowing recipients to access data from their nearest publisher with minimal network transmission.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12555164B2Data distribution architecture
Publication Date: 2026.02.17 CHICAGO MERCANTILE EXCHANGE INC
  • US12555164B2 patent drawing
  • US12555164B2 patent drawing
  • US12555164B2 patent drawing

AI summary

Disclosed are a system and method, also referred to herein as an architecture, for efficiently communicating a high volume of data from a server over an electronic communications network to geographically disperse recipients, where one or more of those recipients may receive a customized version of that data, e.g., content, timing and/or form. As the data is generated, timing information and/or changes to information regarding customizations is incorporated forming a data stream which is communicated to local data publishers (“LDP's”). Upon receipt, the LDP's extract the data, customization, or timing information and act accordingly when transmitting the received data to the recipients. Customization is applied to update local control databases which specify the customizations for subsequently received data before transmission. By acting on the messages in real time, e.g., as they are received, the LDP's, even if they don't receive the messages at the same time, then perform the same functions in the same relative order relative to the data stream.