Push Notification Framework for OTT Application IMS Registration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile device operating systems often suspend Over-the-Top (OTT) applications, leading to missed calls and messages due to loss of network connection and registration with the IMS core network, which existing solutions like frequent 'keep-alive' messages or non-battery optimized mode fail to adequately address, resulting in inefficient communication.
Innovation Solution
Implementing a push notification framework, where an access gateway sends notifications to the OTT application to wake it up and re-register with the IMS core network, using a single point of configuration for notifications, thereby maintaining active registration and reducing communication delays.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If the OTT application is suspended by the operating system to save battery power, then energy consumption is reduced, but the application loses network connection and registration with the IMS core network, resulting in missed calls and messages
Solution Approach 1:
The system performs preliminary actions by establishing a background service that maintains network registration and connection status before the application is actually suspended. This background service proactively monitors network state and prepares to restore connections, ensuring that when the application wakes from suspension, it can quickly re-establish communication without missing calls or messages.
Solution Approach 2:
A background service acts as an intermediary between the suspended OTT application and the network infrastructure. This intermediary maintains the network connection and registration status on behalf of the application, translating between the suspended application's needs and the network's requirements, thereby preserving communication reliability without requiring the application to remain active.
2Reliability
If frequent 'keep-alive' messages are sent to maintain application wakefulness, then communication reliability is improved, but battery power consumption increases
Solution Approach 1:
Instead of continuous or frequent keep-alive messages, the system implements periodic actions through a background service that maintains network registration at appropriate intervals. This periodic maintenance of connection status achieves communication reliability while significantly reducing the frequency of wake-up events and associated energy consumption compared to frequent keep-alive messaging.
Solution Approach 2:
The background service provides self-service functionality by autonomously maintaining network registration and connection status without requiring the main application to be active. This self-service approach handles network maintenance independently, allowing the application to remain suspended and conserve battery power while communication reliability is preserved through the background service's periodic network maintenance.
3Reliability
If the application remains continuously active to maintain network registration, then communication reliability is improved, but battery power consumption and network resource usage increase
Solution Approach 1:
The system segments the application's functionality into two distinct components: the main application that can be suspended to save battery, and a background service that remains active to maintain network registration. This segmentation allows the critical network maintenance function to operate independently with lower resource requirements, while the power-intensive application processing can be suspended when not needed.
Solution Approach 2:
The system implements dynamic behavior by allowing the application's operational state to change between active and suspended based on user interaction patterns. The background service dynamically adjusts its activity level, maintaining full network registration when the application is suspended but using optimized procedures that consume fewer resources than continuous full application operation, thus adapting resource usage to actual communication needs.
Data Source
AI summary
Systems and methods are provided for facilitating communications with an operating system suspended OTT application on a user device. The methods include sending, from a P-CSCF or a WebRTC Gateway, to a push notification framework, a notification configured to cause the push notification framework to send a push notification to the suspended OTT application (IMS OTT application or WebRTC OTT application). The push notification may wake up the OTT application and cause a notification initiated REGISTRATION request to be sent by the OTT application. This can be initiated just before the IMS core network de-registers the OTT application based on a timer, or based on receipt of a SIP request (e.g. phone call received) when the OTT application is suspended. In addition, the push notification provides a lightweight authentication at the P-CSCF instead of a full blown authentication at the usual place S-CSCF.