SIP Subscription Mechanism for Permanent and Time-Policy Notifications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Session Initiation Protocol (SIP) SUBSCRIBE/NOTIFY mechanism lacks functionality for permanent and time-policy-based subscriptions, requiring users to stay online for permanent subscriptions and facing challenges in setting subscription durations for temporary subscriptions, and lacks flexibility in initiating subscriptions based on specific time policies.
Innovation Solution
The introduction of permanent and temporary subscription identifiers within SIP messages, using extended or new header fields such as 'Expires', 'Subscription-State', and 'Event', allows for continuous notification without user intervention for permanent subscriptions and flexible time-based subscription policies by specifying start times and notification intervals.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Duration of action of stationary object
If users want permanent subscriptions, then continuous notification is achieved, but users must stay online requiring constant user intervention
Solution Approach 1:
The system performs preliminary action by automatically renewing subscriptions before they expire. The server monitors subscription validity periods and proactively extends them, eliminating the need for users to manually intervene or stay online to maintain permanent subscriptions.
Solution Approach 2:
The subscription system serves itself through automated renewal mechanisms. The server autonomously manages subscription extensions without requiring user action, making the system self-sufficient in maintaining permanent subscriptions while users remain offline.
2Manufacturing precision
If users set specific subscription durations for temporary subscriptions, then accurate time management is achieved, but flexibility in time-policy-based subscriptions is reduced
Solution Approach 1:
The system introduces dynamic time policies that allow subscription parameters to be adjusted based on various conditions. Instead of fixed durations, subscriptions can adapt their timing and validity periods according to event types, user preferences, and system conditions, achieving both precision and flexibility.
Solution Approach 2:
The patent enables parameter changes in subscription configurations by allowing multiple time-related parameters (start time, expiration time, renewal intervals) to be modified based on different policies. This permits accurate timing control while maintaining adaptability to various subscription scenarios.
3Device complexity
If the SIP protocol uses existing header fields for subscription management, then protocol simplicity is maintained, but functionality for permanent and time-policy-based subscriptions is limited
Solution Approach 1:
Existing SIP header fields are made multi-functional to support both traditional and advanced subscription features. The same header fields serve multiple purposes: managing temporary subscriptions, permanent subscriptions, and time-policy-based subscriptions, thereby maintaining protocol simplicity while expanding functionality.
Solution Approach 2:
The patent introduces intermediary elements (such as additional parameters within existing headers or intermediate processing layers) that enable enhanced subscription functionality without fundamentally altering the SIP protocol structure. These intermediaries bridge the gap between simple protocol design and complex subscription requirements.
Data Source
AI summary
A subscription method and device based upon the session initiation protocol are disclosed, such that a function of permanent subscription and temporary subscription is achieved, and a time at which a notification is sent can be customized. In the present invention, a mechanism of permanent subscription and temporary subscription is introduced. Upon reception of a SUBSCRIBE message, a notifier sets a temporary subscription flag or a permanent subscription flag for a subscriber according to an identifier carried in the message or service characteristic corresponding to a subscribed event. In the case of the permanent subscription flag, a NOTIFY message from the notifier is continuously sent until the subscriber or the system revokes subscription, and in the case of the temporary subscription flag, the notifier no longer sends a NOTIFY message upon finishing of a subscribed service. The subscriber may also carry a parameter indicative of a start time at which subscription gets validated and/or a parameter indicative of a time at which a notification is sent in the SUBSCRIBE message sent to the notifier. The notifier parses the message and sends the NOTIFY message to the subscriber when the start time at which subscription gets validated is reached and/or according to the time at which a notification is sent.