Real-Time Live Event Data Aggregation via WebSocket Push
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for broadcasting live event data to mobile devices often result in significant latency, with delays ranging from seconds to minutes, due to the need for data to be added to a database, written to files, and propagated to servers before clients can receive it.
Innovation Solution
The use of topic queues and open duplex communication connections, such as websocket connections, to quickly process and push live event data from message queue servers to client devices, reducing latency to milliseconds.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional database and file propagation methods are used to broadcast live event data, then data can be stored and transmitted through standard processes, but latency increases to seconds or minutes
Solution Approach 1:
The patent extracts the data from conventional storage mediums (databases and files) and transmits it directly through websocket connections. By removing the intermediate steps of database insertion and file writing, the system achieves real-time transmission with latency reduced to milliseconds while maintaining data reliability through the persistent websocket connection.
Solution Approach 2:
The patent introduces a websocket server as an intermediary between the data source and client devices. This mediator maintains persistent connections with clients and pushes data in real-time, eliminating the need for clients to repeatedly request updates and reducing overall system latency while ensuring reliable data delivery.
2Speed
If real-time data pushing is implemented to reduce latency, then data delivery speed increases to milliseconds, but system complexity increases due to websocket connections and topic queues
Solution Approach 1:
The websocket server acts as a mediator that simplifies the architecture by centralizing connection management and data push operations. Instead of implementing complex peer-to-peer real-time communication between multiple components, the mediator handles all real-time data pushing through maintained connections, reducing overall system complexity while achieving millisecond-level delivery speed.
Solution Approach 2:
The system establishes persistent websocket connections in advance before data needs to be transmitted. By pre-establishing these communication channels and maintaining them open, the system eliminates connection establishment overhead at the time of data transmission, achieving fast data delivery without requiring complex on-demand connection management.
3Loss of time
If persistent connections are maintained for real-time data pushing, then data can be delivered instantly to clients, but server resources and connection management complexity increase
Solution Approach 1:
The websocket server maintains persistent connections with clients who have expressed interest in receiving real-time data updates. Rather than establishing connections with all possible clients or continuously polling for data, the server selectively maintains connections only where needed, reducing unnecessary resource consumption while still achieving instant data delivery to subscribed clients.
Data Source
AI summary
A system to aggregate and broadcast live event data in real-time includes an aggregator host server having one or more processor circuits; and an aggregator component executing on a processor circuit to: receive a plurality of data payloads, from topic entries associated with a plurality of subscribed topics associated with a live event, from a message queue server; aggregate the plurality of data payloads into a new aggregated topic entry; and publish the new aggregated topic entry to an aggregated topic at the message queue server, when the aggregator component has a publisher role.