Security Object Sync via Distribution Queues
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Synchronizing security objects in an active-active environment is challenging due to potential conflicts between updates from different locations, network bandwidth limitations, and latency.
Innovation Solution
A system and method for security object synchronization that utilizes a distribution structure with a source queue and target node-specific distribution queues, allowing for efficient tracking and transmission of sync requests, and incorporating features like acknowledgement-based queue closure, resend mechanisms, and encoding for security and authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If security object updates are propagated between multiple locations via network, then synchronization is achieved, but network bandwidth limitations and latency cause conflicts and delays
Solution Approach 1:
The patent segments security object updates into individual update packets that are tracked separately. Each update is assigned a unique identifier and processed independently through the distribution structure, allowing selective retransmission of only failed updates rather than resending entire synchronization data sets.
Solution Approach 2:
The patent implements feedback mechanisms where receiving nodes send acknowledgments back to source nodes confirming successful update reception. The distribution structure tracks these acknowledgments and triggers selective retransmission of updates that lack confirmation, ensuring reliable delivery while minimizing redundant network traffic.
2Productivity
If multiple locations can independently update security objects, then development productivity is improved, but conflicts arise between simultaneous updates from different nodes
Solution Approach 1:
The patent establishes a distribution structure in advance that defines source queues and distribution queues for each target node before updates occur. This pre-configured framework provides clear rules for update propagation and conflict resolution, allowing multiple nodes to independently update security objects without ad-hoc conflict management complexity.
Solution Approach 2:
The patent introduces a distribution structure as an intermediary layer between updating nodes and target nodes. This intermediary tracks update origins, manages propagation paths, and resolves conflicts by determining which updates should be applied at each target node, thereby simplifying the complexity of direct peer-to-peer update conflicts.
3Reliability
If security object sync requests are resent upon lack of acknowledgement, then transmission reliability is improved, but transmission overhead increases
Solution Approach 1:
The patent implements partial retransmission by sending only the specific update packets that failed to be acknowledged rather than resending complete synchronization data sets. This partial action approach maintains reliable delivery of critical updates while significantly reducing the time overhead compared to full retransmission strategies.
Data Source
AI summary
The present disclosure provides a method, system, and device for security object synchronization at multiple nodes of an active-active environment. To illustrate, a source node may generate a corresponding security object sync request for each of multiple target nodes. The source node may send the security object sync request to the target nodes via a source queue and, for each target node, a corresponding distribution queue. A distribution queue may be closed based on an acknowledgement received from a corresponding target node, after a time period, or after a number of transmission attempts. A synchronization log may be maintained to indicate which security object sync requests have been delivered to which target nodes. In some implementations, the source node and the target nodes are part of an active-active environment that may be synchronized in time so the nodes resolve conflicts between received security object updates initiated from two different nodes.