Selective Identity Data Synchronization in Distributed Manufacturing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Synchronizing identity data across remote distributed database servers with a central database server is challenging due to issues like data replication over unstable Wireless Area Networks, network unreliability, strict security requirements, and the need for selective data distribution, especially in manufacturing environments where human interaction-based solutions are inefficient.
Innovation Solution
A system that uses a Factory Synchronizer and Loader (FSL) to assign and synchronize identity data types to factories based on device manufacturing needs, leveraging local area networks for stable data synchronization, and includes mechanisms for correcting errors and handling failures with minimal human intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data replication is performed over WAN to remote distributed database servers, then identity data can be synchronized across all servers, but network instability and poor reliability make the process non-viable
Solution Approach 1:
The patent introduces a centralized database server as an intermediary that receives identity data from the configuration manager and distributes it to remote database servers. This intermediary approach allows the system to bypass direct WAN connections between remote servers and the configuration manager, using instead stable LAN connections between the centralized server and remote servers, thereby resolving the network reliability issue.
Solution Approach 2:
The patent segments the data distribution architecture into two distinct parts: a centralized database server that handles all identity data reception and distribution logic, and remote database servers that only handle local data storage and retrieval. This segmentation allows each component to operate independently with optimized connection strategies, using stable LAN connections for remote servers while centralizing the complex synchronization logic.
2Reliability
If all identity data is loaded to all remote distributed database servers, then complete data synchronization is achieved, but strict security requirements necessitate selective data distribution to applicable servers only
Solution Approach 1:
The patent implements local quality by having each remote database server receive and store only the identity data applicable to its specific location or organization. The centralized database server filters and selects only the relevant data subsets for each remote server based on predefined criteria, ensuring that each server maintains locally relevant data without requiring all servers to process or store the complete data set.
Solution Approach 2:
The patent applies partial action by distributing only the necessary subset of identity data to each remote database server rather than copying the entire data set. This selective distribution approach reduces the data processing burden on each server while maintaining complete synchronization for the applicable data portions, effectively resolving the complexity issue.
3Adaptability or versatility
If identity data is modified in the central database server, then updated data can be synchronized to all applicable remote servers, but the modification and synchronization process becomes complex without a robust solution
Solution Approach 1:
The patent implements feedback mechanisms where the centralized database server receives updates from the configuration manager, processes these updates, and automatically propagates them to all applicable remote database servers. The system includes feedback loops that monitor synchronization status and can retransmit data if needed, ensuring that modifications are reliably communicated across the distributed architecture without requiring complex manual intervention.
Solution Approach 2:
The patent applies preliminary action by having the centralized database server pre-process and prepare data updates before distributing them to remote servers. The system anticipates synchronization needs and proactively pushes updates to remote servers, ensuring that all applicable servers have the latest data without requiring complex real-time coordination or manual triggering of synchronization processes.
4Ease of operation
If human interaction-based synchronization methods are used, then data can be downloaded and uploaded to databases, but the process is inefficient for automated manufacturing environments
Solution Approach 1:
The patent implements self-service by enabling the centralized database server to automatically receive identity data from the configuration manager and autonomously distribute it to all applicable remote database servers without requiring human intervention. The system includes automated mechanisms for data reception, processing, filtering, and transmission, allowing the synchronization process to occur continuously and efficiently in automated manufacturing environments.
Solution Approach 2:
The patent ensures continuity of useful action by establishing continuous automated data flow between the configuration manager, centralized database server, and remote database servers. The system operates continuously to monitor for data updates and maintain synchronization, eliminating the discontinuous nature of manual download-upload processes and ensuring that identity data is always current across all servers without interruption.
Data Source
AI summary
A method for resolving the synchronization of identity data from a central database server to distributed database servers is provided. The method involves synchronizing identity data to central and distributed database servers based on identity data types associated with a factory. The method first includes assigning by a configuration manager identity data types to factories which manufacture devices that will need identity data. Next an Identity Data (ID) Loader receives a file containing the identity data, and the ID Loader loads the identity data to a central database server and creates a file history record indicating a record of the file loaded. Next, a Factory Synchronizer Loader (FSL) is triggered to create and execute jobs to load identity data, configuration data or other data. Finally, the identity data is synchronized between the central data base with the remote database servers in a location of the factory. In some embodiments, the FSL corrects identity data and resynchronizes, or determines when synchronization fails and repeats synchronization processes when the failure occurs.