Subscription Service Host Server Suspend Logic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In packet data communication systems, terminated subscriptions continue to retry re-subscription, leading to server resource waste, battery life consumption, and potential system congestion due to repeated requests, which are not efficiently managed by existing Presence Servers.
Innovation Solution
A method and Subscription Service Host Server that monitor system conditions to suspend subscriptions without explicit user requests, allowing for subsequent reactivation or termination, thereby managing resource utilization and reducing congestion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the Presence Server continues to reject re-subscription requests from terminated subscriptions, then server resources are protected from overload, but repeated retry attempts still consume user terminal battery life and may congest the system
Solution Approach 1:
The Presence Server sends a preliminary notification to the Watcher indicating that the subscription has been terminated or is about to expire. This allows the user terminal to stop retrying re-subscription before actually attempting, thereby conserving battery life while the server maintains its rejection policy for resource protection
Solution Approach 2:
The system implements a feedback mechanism where the Presence Server informs the Watcher about the subscription status (terminated or expiring). This feedback loop allows the user terminal to adjust its behavior (stop retrying) based on server status, preventing unnecessary energy consumption from repeated retry attempts
2Productivity
If the Presence Server rejects all re-subscription requests from terminated subscriptions, then system congestion is prevented, but server processing overhead increases due to handling repeated rejection requests
Solution Approach 1:
The notification function is extracted from the re-subscription handling process. Instead of processing full re-subscription requests and then rejecting them, the server extracts and sends only a notification about termination status, allowing the client to stop retrying without the server needing to process subsequent rejection requests
Solution Approach 2:
The server performs a preliminary notification action before the client can attempt re-subscription. This preliminary action informs the client of the termination status, preventing the client from initiating further re-subscription requests that would require server processing and rejection
3Quantity of substance
If the Presence Server allows subscriptions to expire without intervention, then server resources are freed for active subscriptions, but Watchers continue to retry re-subscription causing battery consumption and potential congestion
Solution Approach 1:
The Presence Server implements a feedback mechanism that notifies Watchers when subscriptions are terminated or about to expire. This feedback allows Watchers to stop retrying re-subscription, eliminating the harmful effect of repeated requests while the server maintains control over active subscription quantities
Solution Approach 2:
The server sends a preliminary notification about subscription termination or impending expiration before the Watcher can attempt re-subscription. This preliminary action prevents the generation of harmful retry requests while allowing the server to manage the quantity of active subscriptions effectively
Data Source
AI summary
A method and Subscription Service Host Server that support a presence service receives multiple subscription requests associated with multiple of subscribers, wherein each subscription request of the multiple subscription requests comprises a request to subscribe to presence information of a status publication source. In response to receiving the multiple subscription requests, a subscription is created for each subscriber of the multiple subscribers. A system condition is monitored and, based on the monitored system condition, a determination is made to suspend a subscription of a subscriber of the multiple subscribers. The subscription of the subscriber is placed into a suspended state to produce a suspended subscription, wherein the Server suspends the subscription without receiving, from the subscriber, a request to suspend the subscription. Subsequent to placing the subscription into a suspended state, a determination is made to one of reactivate and terminate the suspended subscription.