Server Policy Handler for Asynchronous Data Synchronization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current server systems are unable to efficiently handle concurrent requests for both live and historical data from clients, particularly in scenarios where data streams are received asynchronously, and they struggle to synchronize data according to client-specified rates and timestamps, lacking scalability and distributability across different hardware.

Innovation Solution

A server system with a policy request handler that merges asynchronous data streams into time-ordered data points and forms policy-based data frames, allowing for synchronized data delivery based on client-defined policies, using a server controller to manage data distribution across multiple servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If current server systems handle concurrent requests for live and historical data, then data delivery capability is improved, but synchronization accuracy according to client-specified rates and timestamps deteriorates

Engineering Contradiction:

Improveconcurrent request handling capabilityVSAvoidsynchronization accuracy

Core Design Contradiction:

ProductivityVSMeasurement precision

Solution Approach 1:

The system segments data streams into separate live data streams and historical data streams, processing them through different pathways. Live data is processed through a live data server with real-time synchronization, while historical data is processed through a historical data server with timestamp-based ordering. This segmentation allows concurrent processing without synchronization conflicts.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary component that receives data from multiple sources and applies client-specified policies for synchronization. This intermediary layer buffers and reorders data packets according to timestamps and client-requested rates, ensuring accurate synchronization even when handling multiple concurrent requests.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If data streams are received asynchronously at different data rates, then data collection flexibility is improved, but timestamp preservation and synchronization capability deteriorates

Engineering Contradiction:

Improveasynchronous data stream acceptanceVSAvoidtimestamp preservation accuracy

Core Design Contradiction:

Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The system performs preliminary actions by assigning unique timestamps to data packets at the source before transmission. These timestamps are preserved through buffering and reordering mechanisms, ensuring that even when data arrives asynchronously at different rates, the original temporal relationships are maintained for accurate reconstruction.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements dynamic buffering and reordering mechanisms that adapt to varying data arrival rates. The system dynamically adjusts buffer sizes and reordering algorithms based on the asynchronous arrival patterns of different data streams, maintaining timestamp accuracy without requiring fixed-rate input.

Inventive Principle:

Principle #15Dynamics

3Device complexity

If servers synchronize data based on internal clocks, then data processing simplicity is improved, but ability to preserve original data timestamps and client-specified rates deteriorates

Engineering Contradiction:

Improvesynchronization mechanism simplicityVSAvoidoriginal timestamp preservation

Core Design Contradiction:

Device complexityVSMeasurement precision

Solution Approach 1:

Instead of modifying original timestamps during synchronization, the system creates copies of timestamp information and stores them alongside data packets. This copying approach preserves the original timestamps intact while allowing the system to apply its own synchronization logic based on client specifications without corrupting the source data.

Inventive Principle:

Principle #26Copying

4Device complexity

If server systems are designed for single-hardware deployment, then system simplicity is improved, but scalability and distributability across multiple hardware pieces deteriorates

Engineering Contradiction:

Improvesystem architecture simplicityVSAvoidscalability and distributability

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent designs universal data structures and communication protocols that function identically whether deployed on a single hardware system or distributed across multiple hardware pieces. The same timestamp-based synchronization mechanism and data formatting work across single-server and multi-server deployments, enabling seamless scalability without architecture redesign.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentEP2827559B1Server system for providing current data and past data to clients

Publication Date: 2020.10.21 THE BOEING CO

Figure 1
Figure 2
Figure 3

AI summary

A method and apparatus for handling a server request received at a data server. The data server comprises a policy request handler. The policy request handler is activated within the data server in response to the server request being received at the data server. The policy request handler is configured to receive a plurality of asynchronous data streams. The policy request handler is further configured to merge data points in the plurality of asynchronous data streams together to form time-ordered data points. The policy request handler is further configured to form policy-based data according to a server policy identified in the server request using the time-ordered data points.