Inter-Domain Event Service Subscription Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional inter-domain event services face inefficiencies due to continuous passing of presence information, leading to significant system overhead and redundancy in subscriptions and notifications.
Innovation Solution
The system optimizes inter-domain event services by aggregating multiple subscriptions into a lesser number, reducing messaging overhead and eliminating redundancy through shared subscriptions and notifications, while maintaining expressivity for authorization and filtering.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple subscriptions are maintained for presence information, then individual subscription requirements are met, but system overhead and messaging load increase significantly
Solution Approach 1:
The patent merges multiple redundant subscriptions into a single shared subscription when the same presence information is requested by multiple users. The system identifies that multiple subscribers are requesting identical or overlapping presence data and consolidates these into one subscription relationship, thereby reducing the number of notification messages that need to be generated and transmitted while still delivering the required information to all subscribers.
Solution Approach 2:
The patent creates a universal shared subscription mechanism that can serve multiple subscribers simultaneously. Instead of creating separate subscription instances for each user requesting presence information, the system establishes a single multi-functional subscription that delivers notifications to multiple endpoints, making the subscription system more efficient and scalable.
2Speed
If continuous presence information notifications are sent to all subscribers, then real-time presence updates are provided, but messaging overhead between servers increases
Solution Approach 1:
The patent combines multiple notification delivery paths into a single optimized path by identifying redundant subscriptions. When multiple users subscribe to the same presence information, the system generates one notification message and delivers it to all subscribers through the shared subscription mechanism, rather than generating and transmitting separate notification messages for each subscriber.
Solution Approach 2:
The patent uses a publish-subscribe model where a single notification message is published once and then copied/distributed to multiple subscribers. The presence information update is generated a single time and then efficiently replicated and delivered to all interested parties, reducing the original messaging volume while maintaining real-time delivery to all subscribers.
3Productivity
If redundant subscriptions are eliminated through aggregation, then system overhead is reduced, but individual subscription expressivity must be maintained
Solution Approach 1:
The patent merges subscriptions at the notification delivery level while preserving individual subscription characteristics. The system aggregates the delivery mechanism for redundant subscriptions but maintains separate subscription records that capture each subscriber's specific requirements, filters, and preferences. This allows the system to optimize messaging while still honoring individual subscription expressivity.
Solution Approach 2:
The patent segments the subscription management into two distinct layers: the aggregation layer that optimizes notification delivery by combining redundant subscriptions, and the individual subscription layer that maintains each subscriber's specific requirements and expressivity. This segmentation allows both efficiency and flexibility to coexist.
Data Source
AI summary
Event services provided between domains include receiving a first subscription request to receive an event state of an event source. A view associated with the first subscription request is determined. A notify message is sent that reflects a first defined view into the event state of the event source that corresponds to the first subscription request. A second subscription request is received to receive the event state of the event source. A view associated with the second subscription request is determined. It is determined if the first defined view corresponds to the second subscription request.