Subscription Data Messaging for Real-Time Trading Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing subscription management systems face significant processing burdens, bandwidth usage, and memory consumption due to the need for real-time dissemination of large volumes of trading information, particularly in financial instrument trading, leading to inefficiencies and high resource utilization.

Innovation Solution

A subscription management system utilizing a user interface (UI) message framework that minimizes transmission size and frequency by using JSON messages with byte arrays and numeric values, generating thread-safe messages based on change rates of subscribed subjects, and transmitting only updated data as needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If real-time data dissemination is implemented for all subscribed subjects, then data freshness and reliability are improved, but network bandwidth consumption and processing resources increase significantly

Engineering Contradiction:
Improvedata freshnessVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system segments data transmission by separating static data (displayed once) from dynamic data (updated in real-time). The UI message structure divides subject data into initial display data and subsequent update data, allowing selective transmission based on change detection. This segmentation enables real-time updates only when necessary, reducing bandwidth consumption while maintaining data freshness for critical subjects.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements feedback mechanisms where clients send unsubscribe requests when no longer needing specific subject data, and the server responds by removing those subscriptions. Change detection feedback allows the system to identify when data has been modified and trigger updates only for affected subjects. This feedback loop ensures reliable data delivery while minimizing unnecessary transmissions.

Inventive Principle:
Principle #23Feedback

2Loss of information

If comprehensive real-time updates are provided for all subscription subjects, then information completeness is improved, but processing resources and memory usage increase

Engineering Contradiction:
Improveinformation completenessVSAvoidprocessing resources
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system extracts and transmits only the necessary data elements required for the client subscription, removing redundant information from the transmission stream. By filtering data based on subscription preferences and change detection, the system maintains information completeness for subscribed subjects while significantly reducing processing resources compared to comprehensive updates of all available data.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies partial action by providing real-time updates only for subjects that have changed or are specifically subscribed to, rather than continuously updating all possible subjects. The UI message framework transmits minimal necessary data (byte arrays with numeric values) rather than complete data structures, reducing processing overhead while maintaining sufficient information for client display.

Inventive Principle:
Principle #16Partial or excessive action

3Speed

If frequent data transmissions are performed to ensure real-time updates, then data timeliness is improved, but network bandwidth and transmission overhead increase

Engineering Contradiction:
Improvedata update speedVSAvoidtransmission volume
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The system implements periodic action through change-rate-based update mechanisms where data is transmitted at appropriate intervals or only when changes occur. The UI message framework supports different update frequencies for different subjects based on their volatility and subscription requirements, enabling timely updates without constant transmission. This periodic approach maintains data timeliness while significantly reducing transmission volume compared to continuous updates.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system uses efficient data representation by copying only essential data elements into compact UI messages with byte arrays and numeric values. This copying approach transmits minimal necessary information rather than complete data structures, reducing transmission overhead while maintaining data timeliness for real-time display requirements.

Inventive Principle:
Principle #26Copying

4Measurement precision

If detailed data processing is performed for each subscription item, then data accuracy is improved, but processing time and computational resources increase

Engineering Contradiction:
Improvedata accuracyVSAvoidprocessing speed
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The system changes data representation parameters by converting complex data structures into compact byte arrays with numeric values for transmission. This parameter transformation maintains data accuracy through precise serialization while significantly reducing processing time for transmission and display. The UI message framework optimizes data formatting to balance accuracy requirements with processing efficiency.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12470640B2Method, apparatus and system for subscription management
Publication Date: 2025.11.11 BGC PARTNERS LP
  • US12470640B2 patent drawing
  • US12470640B2 patent drawing
  • US12470640B2 patent drawing

AI summary

Subscription management system and method provides real time subscription data dissemination to multiple computer devices of respective clients based on client subscriptions, using a UI message framework that decreases size and frequency of transmission of UI messages to service the subscriptions.