Primary And Visited MCX Servers for Localized Low-Latency Service
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mission critical communication systems face challenges in achieving ultra-reliable low latency communication (URLLC) due to centralized server deployment, especially in scenarios where clients and servers are geographically distant, leading to complex user profile management and increased latency in decentralized environments like railway systems.
Innovation Solution
Implementing a decentralized MCX server deployment with a primary server maintaining user profiles and dynamically mirroring data to local servers, allowing for localized communication management and reducing the need for long-distance data connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If centralized server deployment is used, then user profile management is simplified, but communication latency increases due to long-distance data transmission
Solution Approach 1:
The system divides the centralized server functionality into two parts: a primary MCX server that maintains user profiles and a visited MCX server that handles local communication. This segmentation allows user profile management to remain centralized while communication operations are localized, resolving the contradiction between simplified management and reduced latency.
Solution Approach 2:
The primary MCX server acts as an intermediary that stores user profiles and provides them to visited MCX servers. This mediator approach allows the visited server to handle communications locally without directly connecting to remote users, reducing latency while maintaining centralized profile management through the primary server.
2Loss of time
If decentralized server deployment is used, then communication latency is reduced through localized management, but user profile management becomes complex
Solution Approach 1:
The system segments functionality by designating specific roles: the primary MCX server handles profile management while visited MCX servers handle communication operations. This clear division of responsibilities simplifies the overall system architecture despite the decentralized deployment, as each server has a well-defined function.
Solution Approach 2:
The primary MCX server serves multiple functions: it acts as a profile repository, a communication server for its own users, and a support server for visited MCX servers. This multi-functionality consolidates complexity into a single server while allowing visited servers to remain simple communication endpoints.
3Reliability
If data is stored locally at visited servers, then communication reliability improves, but data consistency and synchronization become complex
Solution Approach 1:
The system creates a copy of the relevant user profile data from the primary MCX server to the visited MCX server. This copying approach allows the visited server to have local access to necessary data for reliable communication while the primary server maintains the master copy. The synchronization complexity is managed by only copying necessary profile data rather than all data.
Solution Approach 2:
The system performs preliminary data synchronization by providing user profile information to the visited MCX server before communication begins. This preliminary action ensures that the visited server has the necessary data stored locally for reliable communication, eliminating the need for complex real-time synchronization during active communications.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An apparatus comprise means for: causing a primary mission critical service server to store in a user profile of a user client stored in the primary mission critical service server information about a visited mission critical service server serving the user client.