Event-Message Authentication State Synchronization Across Data Centers

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems face challenges in maintaining consistent and secure user authentication states across multiple data centers, leading to potential security vulnerabilities and disruptions due to the inefficiencies of copying large data structures and waiting for confirmation, which consumes resources and causes latency issues.

Innovation Solution

The use of event messages to synchronize authentication states across data centers by generating and transmitting smaller event messages that reflect changes in user authentication states, allowing for faster and more reliable synchronization without the need for full data structure copying.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full data structure copying is used to synchronize authentication states, then consistency across data centers is improved, but latency and resource consumption increase

Engineering Contradiction:

Improveauthentication state consistencyVSAvoidsynchronization latency

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the authentication state data structure into individual authentication events. Instead of copying the entire data structure, only specific event messages are transmitted between data centers. This segmentation allows for selective synchronization of only the necessary changes, reducing latency while maintaining consistency.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent extracts only the essential authentication events from the complete authentication state data structure. By taking out only the relevant event messages that represent state changes, the system avoids transmitting redundant data, thereby reducing synchronization time and resource consumption while preserving the necessary consistency information.

Inventive Principle:

Principle #2Taking out (Extraction)

2Reliability

If full data structure copying is used to synchronize authentication states, then consistency across data centers is improved, but resource consumption increases

Engineering Contradiction:

Improveauthentication state consistencyVSAvoidbandwidth and computing resources

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by transmitting only the necessary event messages rather than complete data structures. This partial synchronization approach uses fewer resources while achieving the required level of consistency, avoiding the excessive resource consumption of full data copying.

Inventive Principle:

Principle #16Partial or excessive action

3Reliability

If verification processes are implemented for data structure copying, then security is improved, but synchronization speed decreases

Engineering Contradiction:

Improveauthentication state consistencyVSAvoidsynchronization speed

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by establishing trust relationships between data centers in advance. Verification of data center identities and permissions is performed beforehand, allowing event messages to be synchronized rapidly without repeated verification delays. This preliminary verification maintains security while enabling faster synchronization.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where data centers verify and acknowledge received event messages. This feedback loop ensures security and consistency by confirming that synchronization operations are legitimate and successful, while the streamlined feedback process does not significantly impact synchronization speed.

Inventive Principle:

Principle #23Feedback

4Productivity

If event messages are used instead of full data copying, then synchronization speed is improved, but data completeness may be compromised

Engineering Contradiction:

Improvesynchronization speedVSAvoidauthentication state information

Core Design Contradiction:

ProductivityVSLoss of information

Solution Approach 1:

The patent segments the authentication state into discrete event messages that capture all necessary state changes. Each event message contains sufficient information to reconstruct the authentication state accurately, ensuring no information is lost while enabling fast synchronization through selective transmission of only changed events.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS12368719B2Synchronizing a user's authentication state across multiple data centers using event messages

Publication Date: 2025.07.22 RED HAT LLC

AI summary

Techniques for synchronizing the authentication state of a user across data centers using event messages are provided herein. In one example, a system can determine a first change in the authentication state, update a first data structure representing the authentication state in a first data center based on the change, and store a first event message indicating the first change in a message queue. The system can then transmit the first event message to a second data center. Based on the event message, the second data center can update a second data structure also representing the authentication state of the user. In some examples, the second data center can also transmit a second event message to the first data center indicating a second change to the authentication state of the user. The first data center can update first data structure based on the second event message.