Edge Node Master Dataset for Network Data Consistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Digital networks face resource constraints and data inconsistencies due to the accumulation of large amounts of data across multiple nodes, leading to inefficiencies in resource utilization and vulnerability to duplicates and inconsistencies.
Innovation Solution
Implementing a bottom-up hierarchical data administration system where edge nodes compile and store transactional data as a master dataset, comparing it to central server data to ensure consistency, and updating the central server data accordingly, while also storing copies on edge nodes using a distributed ledger like blockchain for consensus-based authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is accumulated from multiple nodes in the network, then the network can maintain comprehensive data records, but resource utilization deteriorates due to increased memory, processing power, and bandwidth requirements
Solution Approach 1:
The patent divides the network into hierarchical segments with central servers and edge nodes. Each edge node maintains a local dataset while the central server maintains a master dataset. This segmentation allows data to be distributed across multiple locations for reliability while limiting the data volume each individual node must process, thereby reducing overall network resource utilization.
Solution Approach 2:
The patent introduces a hierarchical dimension to the data storage architecture, creating multiple levels (edge nodes and central server) rather than a single flat layer. This dimensional change enables the system to maintain comprehensive data across the hierarchy while each node only handles a subset of the total data, optimizing resource usage at each level.
2Adaptability or versatility
If data is accumulated from disparate elements in the network, then the network can capture diverse information, but data consistency deteriorates due to duplicates and inconsistencies
Solution Approach 1:
The patent implements a feedback mechanism where the central server compares the master dataset against datasets from multiple edge nodes. When inconsistencies or duplicates are detected, the system uses feedback loops to identify and resolve conflicts, ensuring data consistency is maintained across the distributed network while preserving diverse data sources.
Solution Approach 2:
The patent merges data from multiple disparate edge nodes into a unified master dataset at the central server. This combining process consolidates diverse information while applying validation and conflict resolution rules to eliminate duplicates and inconsistencies, thereby maintaining both data diversity and consistency.
3Device complexity
If centralized data processing is used, then data management is simplified, but latency increases due to data transmission distances
Solution Approach 1:
The patent segments data processing functions between edge nodes and the central server. Edge nodes perform local data validation, filtering, and preliminary processing, which reduces the amount of data that needs to be transmitted to the central server. This segmentation maintains simplified centralized management for critical operations while reducing latency through distributed preprocessing.
Solution Approach 2:
The patent applies preliminary action by having edge nodes perform data validation, filtering, and formatting before transmitting data to the central server. This preprocessing reduces the workload on the central server and minimizes transmission time, thereby reducing latency while maintaining centralized oversight and simplifying the overall data management process.
Data Source
AI summary
A bottom-up hierarchical computer network architecture is provided. The architecture may include a central server. The architecture may also include a plurality of edge nodes that may be coupled to the central server. At least a first one of the edge nodes may be configured to process a transaction, compile data associated with the transaction, and store the data as a master dataset in the first edge node. The architecture may also include a data administration module. The data administration module may be configured to compare the master dataset in the first edge node to transactional data in the central server. When the transactional data in the central server is inconsistent with the master dataset in the first edge node, the data administration module may be configured to update the transactional data in the central server to be consistent with the master dataset in the first edge node.


