Shared Repository for Duplicate Session Detection in Pub/Sub Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In publish and subscribe systems with a distributed broker, detecting and managing duplicate client sessions is challenging due to the decoupled nature of clients and servers, which can lead to false detection of duplicate sessions when servers fail or clients reconnect, causing potential disruptions and requiring efficient policies for resolution.
Innovation Solution
A system that includes a processor to receive connection requests with client identifiers and predefined policies for duplicate client sessions, querying a shared repository to execute actions based on detected duplicate sessions, using parameters like client properties, connection histories, and server statuses, allowing for dynamic and localized management of duplicate client sessions without centralized arbitration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a distributed broker architecture is used to improve system scalability and reduce centralized bottlenecks, then system capacity and fault tolerance are improved, but duplicate client session detection accuracy deteriorates due to the decoupled nature of clients and servers
Solution Approach 1:
The patent introduces a shared repository as an intermediary component that all servers in the distributed broker can query. This repository stores client session information and serves as a centralized data source that resolves the detection accuracy issue while maintaining the distributed architecture's scalability benefits.
Solution Approach 2:
The shared repository serves multiple functions: it stores client session data, enables duplicate detection across all servers, and provides a centralized truth source for session management. This multi-functional component addresses the detection accuracy problem without requiring a fully centralized broker architecture.
2Measurement precision
If centralized arbitration is used to manage duplicate client sessions, then duplicate detection accuracy is improved, but system complexity and centralized bottlenecks increase
Solution Approach 1:
The patent segments the arbitration function by allowing each server to independently query the shared repository and make local decisions about duplicate sessions. This eliminates the need for a centralized arbitration mechanism while maintaining accurate duplicate detection through the shared data source.
Solution Approach 2:
The patent extracts the session data management function from the server logic and places it in a separate shared repository. This separation allows servers to maintain simplicity while achieving accurate duplicate detection by querying the external repository, rather than implementing complex centralized arbitration.
3Measurement precision
If servers frequently communicate with each other to detect duplicate sessions, then duplicate detection accuracy is improved, but network overhead and server interaction complexity increase
Solution Approach 1:
The patent merges the session data from all servers into a single shared repository. This consolidation eliminates the need for servers to communicate with each other individually, as they can all query the same centralized data source, reducing network overhead while maintaining detection accuracy.
Data Source
AI summary
Examples of techniques for tracking client sessions in a publish and subscribe system using a shared repository are described herein. An example system includes a processor of a server to receive a connection request with a client identifier from a client a predefined policy for duplicate client sessions. The processor is to query a shared repository of the system using the client identifier. The processor is to also execute a set of actions based on the predefined policy, a query result including a detected duplicate client session from the shared repository, and a set of parameters.