Verification Device for Distributed Data Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed data processing systems, identifier errors can lead to malfunctions, and detecting these errors is challenging due to inconsistencies between identifiers used by different devices.

Innovation Solution

A method and system that involve a client device requesting attribute values from multiple data sources, sending these responses to a server, which then forwards relevant information to a verification device. The verification device performs a consistency evaluation on the identifiers, comparing them to previously stored combinations to determine if the identifiers are consistent and correct.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a distributed data processing system uses multiple devices to supply attribute values, then the system can perform complex operations and improve functionality, but identifier errors and inconsistencies between devices can cause malfunctions and reduce reliability

Engineering Contradiction:
Improvesystem functionalityVSAvoidoperation reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

A verification device is introduced as an intermediary component between the server and data sources. This verification device receives identifiers from multiple data sources, performs consistency evaluation by comparing them against stored combinations, and returns verification results to the server. The verification device acts as a mediator that detects identifier errors without requiring the server to directly verify each identifier, thus maintaining system functionality while improving reliability through centralized verification.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the server verifies identifier consistency by comparing identifiers from multiple data sources, then identifier errors can be detected and reliability improved, but the verification process increases system complexity and processing time

Engineering Contradiction:
Improveidentifier accuracyVSAvoidverification system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The verification function is segmented and extracted into a separate verification device that operates independently from the server. The verification device maintains its own storage for identifier combinations and performs verification operations locally. This segmentation reduces the processing burden on the server and allows the verification logic to be optimized separately, thereby improving identifier accuracy without proportionally increasing overall system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The verification device implements a feedback mechanism where verification results are returned to the server, which then uses this information to determine whether to execute the task. This feedback loop enables the system to detect and respond to identifier errors efficiently. The feedback mechanism allows for continuous verification without requiring complex real-time analysis, as the verification device pre-computes and stores identifier combinations for comparison.

Inventive Principle:
Principle #23Feedback

3Reliability

If the system performs consistency evaluation on identifiers from multiple data sources, then wrong identifiers can be detected and prevented from causing malfunctions, but the process requires additional processing steps and time

Engineering Contradiction:
Improvedata correctnessVSAvoidverification time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The verification device performs preliminary verification actions by pre-storing identifier combinations from data sources in its memory before the actual task execution. When a verification request is received, the device compares the received identifiers against these pre-stored combinations rather than performing complex real-time verification. This preliminary action approach significantly reduces verification time while maintaining high data correctness, as the bulk of verification work is done in advance or through efficient comparison operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250117375A1Data verification in a distributed data processing system
Publication Date: 2025.04.10 NEDERLANDSE ORG VOOR TOEGEPAST NATUURWETENSCHAPPELIJK ONDERZOEK TNO
  • US20250117375A1 patent drawing
  • US20250117375A1 patent drawing
  • US20250117375A1 patent drawing

AI summary

A verification device operates to evaluate consistency of input values from a client device used by a server to execute a task. In an example the task may be installation of software into the client device, and the consistency evaluation of the input values may involve evaluating whether identifiers used to obtain attribute values of components of the client device for the installation apply to the same client device. To initiate execution of the task, the client device commands a plurality of data source servers to supply the attribute values. The data source servers return response messages defining the attribute values associated with the identifiers supplied by the client device. The client device supplies the response messages to the server for use in the execution of the task. Before executing the task, the server supplies information from the response messages to a verification device, the information defining a combination of the identifiers of the response messages, as well as the combination of data source servers that have defined attribute values associated with the identifiers. The verification device performing a consistency evaluation on said combination of identifiers, dependent on whether said combination of identifiers is consistent or inconsistent with previously stored combinations of identifiers for said combination of data source servers stored for previously executed tasks and/or whether values of a corresponding further attribute associated with the identifiers in the data source servers in the combination of data source servers are consistent. The server selecting between executing the task or not dependent on a result of the consistency evaluation.