Single-User Database Replication for DDIL Email Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise directory services face challenges in providing access to electronic identities and email accounts in environments with limited or no internet connectivity, as conventional multi-master database replication schemes are difficult to use in denied, degraded, intermittent, or latent (DDIL) network conditions, leading to issues with synchronization and email functionality.
Innovation Solution
Implementing a system with a single-user database that replicates user-specific electronic identities and email accounts across cloud and on-premises servers, allowing access and communication within a DDIL environment and synchronizing with the main database when connectivity is restored, using a multi-master replication scheme.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional multi-master database replication schemes are used for enterprise directory services, then email functionality and user identity access are provided in normal network conditions, but access to electronic identities and email accounts becomes impossible in environments with limited or no internet connectivity
Solution Approach 1:
The patent segments the large enterprise directory database into individual single-user databases. Each user's electronic identity and email account are stored in separate, self-contained databases that can be independently replicated and cached on local devices. This segmentation enables users to access their own data offline without requiring connection to the central server, while still maintaining the ability to synchronize when connectivity is restored.
2Loss of information
If large enterprise databases are replicated across cloud servers, then comprehensive user data is available centrally, but synchronization becomes difficult and time-consuming in DDIL network conditions
Solution Approach 1:
The patent extracts individual user data from the large centralized database and places it into separate single-user databases that can be cached locally on user devices. This extraction eliminates the need to synchronize entire large databases in DDIL environments, as only small individual user database files need to be transferred and synchronized when connectivity is available, dramatically reducing synchronization time and complexity.
3Ease of operation
If single-user databases are replicated to DDIL servers, then continuous access to email and identities is enabled in disconnected environments, but device and system complexity increases
Solution Approach 1:
The patent creates simplified copies of user data in single-user databases that can be independently stored and accessed on local devices or DDIL servers. These copies contain all necessary information for offline email and identity verification, enabling users to operate fully offline. The copying approach balances the need for offline access with manageable complexity, as individual user database files are small and can be efficiently managed compared to full database replication.
Data Source
AI summary
The present invention generally relates to systems and methods for providing an enterprise user with an electronic identity and an electronic mailbox when the user has denied, degraded, intermittent, or latent network connectivity. In aspects, a database limited to a single user containing the user's electronic identity and electronic mailbox is provided. The single user database is replicated using a multi-master replication scheme across the cloud and on-premises servers. When a user is entering an environment with denied, degraded, intermittent, or latent network connectivity (“DDIL”), the single user database is replicated to a DDIL server. The user is provided access to their electronic identity and electronic mailbox in the single-user database via the DDIL server during periods of denied, degraded, intermittent, or latent network connectivity. The single user database can be replicated across the cloud/on-premises servers during periods when network connectivity is established and adequate for replication.