Persistent Push Session Authentication for Mobile Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for server-initiated communications with mobile devices are inefficient, requiring repeated authentication and validation of mobile devices and applications each time a connection is established, leading to strain on network resources, especially with the increasing use of push notifications and concurrent applications.
Innovation Solution
A push communication server system that authenticates mobile devices and registers applications requesting push services, establishing a persistent connection session that maintains authentication and application registration, allowing re-establishment of connections without repeating authentication and validation if the link is lost or terminated.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If a pull communication framework is used where mobile devices initiate all data communications, then the mobile device can maintain control and security, but the server cannot send notifications or data communications to the mobile device in a timely manner
Solution Approach 1:
The patent merges the pull communication framework with push notification capabilities by introducing a notification service that maintains persistent connections with mobile devices. This allows the server to initiate communications (push capability) while the mobile device still controls the connection establishment (pull framework), resolving the contradiction between timely notification delivery and mobile device control.
2Speed
If SMS messages are used to enable server-initiated communications, then the server can send notifications to mobile devices, but additional carrier equipment and capabilities are required, increasing system complexity and cost
Solution Approach 1:
The patent extracts the notification delivery function from the SMS/carrier gateway infrastructure and implements it directly within the mobile device through a local notification service. This eliminates the need for additional carrier equipment and SMS capabilities, reducing system complexity while maintaining timely notification delivery.
3Reliability
If authentication and validation are performed each time a connection is established, then security is maintained, but network resources are strained, especially with increasing push notifications and concurrent applications
Solution Approach 1:
The patent performs authentication and validation in advance when the mobile device first connects to the notification service, establishing a persistent authenticated connection. This preliminary authentication action eliminates the need for repeated authentication with each notification or connection, maintaining security while significantly improving network resource efficiency for subsequent communications.
4Productivity
If a persistent connection session is established with pre-authentication and application registration, then repeated authentication is avoided, but the initial connection establishment process becomes more complex
Solution Approach 1:
The patent merges the authentication process with the application registration process into a single integrated flow. When an application requests push notification capability, the system authenticates the mobile device and registers the application simultaneously in one connection establishment sequence, rather than as separate steps. This reduces the perceived complexity while establishing the persistent authenticated connection.
Data Source
AI summary
A server system and a mobile device establish a push data framework for communication. The mobile device includes a push client, and runs one or more applications requiring push data communications. The push client transmits a device authentication and application validation request to a push server. Upon the push server successfully authenticating and validating the device and application, the push client receives a session identifier for establishing a persistent communication connection with the push server. Once established, an application server can push data to the mobile device via the persistent communication session. The session identifier remains valid for an extended period of time, and allows the push client to maintain and re-establish push connections with the push server for the duration of the extended period of time.