Real-Time Data Delivery Engine for Web Browsers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems fail to provide continuous real-time process data over the web due to the stateless nature of web architecture, leading to missing data points and security concerns when accessing large volumes of critical data across multiple users.
Innovation Solution
A system comprising a web server, data store, and data retrieval engine that authenticates users and tracks data values sent to each user, ensuring only new data is provided, maintaining real-time data integrity and security through a data retrieval engine that manages data streams and user queues.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If web browsers use standard HTTP stateless architecture to access real-time data, then ease of operation and accessibility are improved, but data completeness and reliability deteriorate due to missing data points
Solution Approach 1:
The patent introduces a server-side session management system that acts as an intermediary between the stateless HTTP protocol and the stateful process control data stream. This mediator maintains session state, tracks data points sent to each user, and ensures continuous data delivery despite the stateless nature of web browsers, thereby resolving the contradiction between web accessibility and data completeness.
Solution Approach 2:
The system implements feedback mechanisms where the server tracks which data points have been sent to each user session and uses this information to determine what new data to send in subsequent responses. This feedback loop ensures that no data points are missed even though the browser makes periodic requests, maintaining reliability while preserving web accessibility.
2Reliability
If data refresh rate is increased to reduce data loss, then data completeness is improved, but network bandwidth consumption and server load increase
Solution Approach 1:
Instead of sending all data points at every refresh interval, the system sends only the partial data that is new since the last request. The server tracks the last sent data point for each session and only transmits subsequent new data points, reducing unnecessary network traffic while ensuring no data is missed.
Solution Approach 2:
The server performs preliminary tracking of data points in memory before they need to be sent to clients. By maintaining session state and tracking which data points have been transmitted, the system prepares the information needed to send only new data in subsequent responses, reducing network bandwidth consumption while maintaining data completeness.
3Adaptability or versatility
If multiple users access real-time data simultaneously through web browsers, then system versatility and ease of operation are improved, but security management and data integrity become more complex
Solution Approach 1:
The patent implements a universal session management system that handles authentication, authorization, and data tracking for multiple users through a common architecture. This multi-functional system manages security credentials, maintains individual session states, and controls data access for each user uniformly, enabling multi-user support without proportionally increasing security management complexity.
Solution Approach 2:
The system segments user sessions into independent tracking contexts, where each user's data transmission state is maintained separately. This segmentation allows multiple users to access the system simultaneously with individual security credentials and data tracking, managing complexity by isolating each user's session state while providing unified multi-user support.
Data Source
AI summary
A data retrieval engine accesses data streams (“tags”) from data sources. Each data stream preferably includes a plurality of values for a tag and a time each value was recorded. A user accesses the web server to request real-time performance data for a plurality of the tags. After authenticating the user, the data retrieval engine sends values for tags the user is authorized to view to the web server, for delivery to the browser. The data retrieval engine tracks which values were sent to the web server for each user and when. When the data retrieval engine receives a request for a specific user, only data not previously provided to the web server for that user is provided for the current request. In this manner, the user does not miss any events, and is provided substantially in real time with a complete set of data for requested tags.