Group Communication Protocol Version Negotiation via View Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In view-oriented group communication systems, managing multiple protocol versions among communication entities is complex due to incompatible state transitions and the need for simultaneous support of old and new versions during dynamic membership changes, which existing solutions fail to address effectively.
Innovation Solution
A method is introduced where a communication entity disconnects from the group, configures itself with a new protocol version, and then rejoins, ensuring that only compatible versions are used, allowing for seamless transition and concurrent operation without system shutdown.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the system supports multiple protocol versions concurrently, then adaptability is improved, but device complexity increases due to managing incompatible state transitions and coordination between versions
Solution Approach 1:
The system segments communication entities into different views, where each view operates with a specific protocol version. This allows the system to support multiple protocol versions concurrently by isolating them in separate views, thereby improving adaptability while managing complexity through structured segmentation.
Solution Approach 2:
The system enables dynamic switching between protocol versions by allowing communication entities to transition between different views. Each view is associated with a specific protocol version, and entities can dynamically join or leave views based on protocol requirements, providing flexibility without permanent complexity.
2Productivity
If protocol version changes are implemented dynamically, then productivity is improved by avoiding system shutdown, but reliability may worsen due to potential communication errors during transition
Solution Approach 1:
Before a communication entity switches protocol versions, it performs preliminary actions by joining a new view associated with the target protocol version while maintaining membership in the current view. This allows the entity to prepare for the transition in advance, ensuring both views are properly configured before the switch, thereby maintaining reliability during dynamic changes.
Solution Approach 2:
The view mechanism acts as an intermediary during protocol version transitions. When a communication entity needs to switch versions, it uses the view structure as a mediator to manage the transition smoothly, ensuring that protocol messages are properly routed and that state transitions are coordinated, thus maintaining communication stability during dynamic changes.
3Adaptability or versatility
If communication entities switch protocol versions independently, then adaptability is improved, but device complexity increases due to coordination overhead and state synchronization
Solution Approach 1:
The view structure serves multiple functions simultaneously: it groups communication entities, manages protocol version associations, handles membership transitions, and coordinates state synchronization. This multi-functionality reduces the need for separate mechanisms for each task, thereby improving adaptability while managing coordination complexity through a unified universal structure.
Data Source
AI summary
Methods and systems are provided in a group communication system for dynamically changing a version of a group communication protocol from a first version to a second version transparently to external sources and destinations. The system accommodates newly joining members that can only support versions of the protocol other than the version currently in use without interruption in service. Similarly, the system can upgrade its operating version of the group communication protocol to improve performance when a member having relatively low capabilities exits the group.