PSaaS Pub-Sub Handover with Message ID Sync Between Data Functions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing publish-subscribe (pub-sub) architectures face challenges in seamlessly handing over sessions between data functions (DFs) while minimizing message loss and duplication, especially when using make-before-break or break-before-make connectivity modes, which can result in inefficiencies and data loss.
Innovation Solution
The publish-subscribe-as-a-service (PSaaS) architecture employs logical separation of control and data planes into control functions (CFs) and data functions (DFs), utilizing message identifiers (MIDs) to facilitate seamless handover between source and target DFs, supporting different client connectivity modes and quality-of-service levels, thereby reducing migration duration and minimizing message loss and duplication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If make-before-break or break-before-make connectivity modes are used for handover, then session continuity is maintained, but message loss and duplication occur
Solution Approach 1:
The patent applies preliminary action by having the target data function prepare message buffering and synchronization mechanisms in advance before the handover is complete. The target DF pre-positions itself to receive messages from the source DF and maintains message queues to prevent loss during the transition, ensuring messages are not lost while maintaining session continuity.
Solution Approach 2:
The patent uses message identifiers (MIDs) as an intermediary mechanism to track and manage message flow during handover. The MIDs serve as a mediator between source and target data functions, enabling precise tracking of message delivery status and coordination of message forwarding, thereby preventing both message loss and duplication while maintaining session continuity.
2Loss of information
If message identifiers are used to track handover progress, then message loss is minimized, but system complexity increases
Solution Approach 1:
The patent applies universality by designing message identifiers (MIDs) to serve multiple functions simultaneously: they uniquely identify messages, track delivery status, coordinate handover progress, and enable synchronization between source and target data functions. This multi-functionality minimizes message loss without requiring separate complex tracking systems, thereby reducing overall system complexity while maintaining effectiveness.
3Loss of information
If seamless handover is implemented with message tracking, then message loss is reduced, but handover duration increases
Solution Approach 1:
The patent applies self-service by enabling the target data function to autonomously track and manage message reception and forwarding using message identifiers. The target DF independently monitors message flow, buffers messages appropriately, and coordinates with the source DF without requiring extensive external control, thereby reducing handover duration while maintaining message loss prevention.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Various example embodiments for supporting seamless handover in a publish-subscribe (pub-sub) architecture are presented herein. Various example embodiments for supporting seamless handover in pub-sub architecture may be configured to support seamless handover of pub-sub sessions in a pub-sub architecture implemented as a publish-subscribe-as-a-service (PSaaS) architecture in which pub-sub brokers are implemented using logically separated control functions (CFs) and data functions (DFs). Various example embodiments for supporting seamless handover in a PSaaS architecture may be configured to support seamless handover of pub-sub sessions between DFs in a PSaaS architecture. Various example embodiments for supporting seamless handover of pub-sub sessions between DFs in a PSaaS architecture may be configured to support seamless handover of pub-sub sessions between DFs in the PSaaS architecture based on use of message identifiers (MIDs) of messages on the pub-sub sessions to control seamless handover of pub-sub sessions between source DFs (SDFs) and target DFs (TDFs) in the PSaaS architecture.