Mobile Client Recovery via Push Notification Exponential Back-off

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems for recovering application server registration after network outages or service disruptions are time-consuming and user-interaction dependent, leading to decreased user experience and potential network overload due to increased traffic volume.

Innovation Solution

A system utilizing exponential back-off via push notifications, involving a core access node, notification server, and push notification service, allows the application to automatically attempt registration with the application server without user intervention, switching between active and inactive states based on timed push notifications, thereby managing traffic and conserving power.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If the application sends frequent registration requests to recover access after network outage, then the application can quickly re-establish connection with the server, but the network becomes overloaded due to increased traffic volume

Engineering Contradiction:

Improvere-registration speedVSAvoidnetwork overload

Core Design Contradiction:

SpeedVSObject-generated harmful factors

Solution Approach 1:

The system implements periodic registration attempts with exponentially increasing intervals (1 minute, 2 minutes, 4 minutes, 8 minutes, etc.) between requests. This periodic action with growing delays allows the application to systematically recover connection after network outage while progressively reducing network traffic volume, preventing overload during the re-registration process

Inventive Principle:

Principle #19Periodic action

Solution Approach 2:

The application proactively implements exponential back-off timing before sending registration requests, cushioning the network against traffic spikes by delaying subsequent requests when failures occur. This beforehand cushioning prevents the harmful effect of network overload by anticipating potential connection failures and spacing out re-attempts appropriately

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

2Ease of operation

If the application requires user interaction for re-authentication, then the user can consciously control the re-login process, but the user experience deteriorates due to time-consuming manual steps

Engineering Contradiction:

Improveuser controlVSAvoidre-authentication time

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The application implements self-service by automatically performing registration requests and handling re-authentication in the background without requiring user intervention. The system autonomously manages the entire re-registration process, including sending requests, handling failures, and implementing exponential back-off timing, thereby eliminating manual user steps while maintaining operational control through automated mechanisms

Inventive Principle:

Principle #25Self-service

3Use of energy by moving object

If the application remains in inactive state to conserve power, then energy consumption is reduced, but the application cannot automatically attempt re-registration without user activation

Engineering Contradiction:

Improvepower consumptionVSAvoidautomatic re-registration

Core Design Contradiction:

Use of energy by moving objectVSExtent of automation

Solution Approach 1:

The application performs preliminary registration attempts while in the inactive state by leveraging background execution capabilities and push notification triggers. The system prepares and sends registration requests without requiring the application to be fully active, enabling automatic re-registration functionality while maintaining the power-saving inactive state for extended periods

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system uses push notifications as an intermediary mechanism to trigger registration attempts. When a push notification is received while the application is inactive, it serves as a mediator that activates the registration process without requiring full application foregrounding, thus enabling automatic re-registration with minimal power consumption by only briefly activating the necessary components

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS11558468B2Mobile client recovery using push notifications to execute exponential back-off procedure

Publication Date: 2023.01.17 T MOBILE US INC

AI summary

A system and method for recovering application authentication with an application server by using an exponential back-off procedure via push notifications is discussed herein. The system allows for authentication of a user account after network outages or service disruptions without traffic overload during recovery. A user equipment (UE) receives a failed registration notification after a failed registration attempt of the user account with an application server associated with the application. A push notification includes an instruction that causes the application to switch from an inactive state to a temporary active state. The push notification is sent from a push notification service in response to a push request from a notification server based on a recovery request from the UE due to the failed registration notification. While the application is in the temporary active state, the instruction further causes the application to request registration with the application server.