HTTP Push Server Logic for Mobile Device Session Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Short Message Service (SMS) has limitations in supporting non-telephone devices and incurs additional costs due to dependency on SMS for communication sessions, with challenges in guaranteeing delivery and managing devices behind firewalls or with unknown IP addresses.
Innovation Solution
Implementing a HyperText Transfer Protocol (HTTP) push operation to simulate server-initiated sessions, using a push server logic that sends a GET command with a timeout parameter to manage mobile devices and eliminate SMS dependency, enabling support for non-telephone devices and reducing operational costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If SMS is used for server-initiated communication sessions, then mobile phones can be accessed, but additional SMS charges are incurred and non-telephone devices cannot be supported
Solution Approach 1:
The patent implements a universal communication protocol (HTTP) that works across multiple device types including mobile phones, PDAs, and other non-telephone devices. The push server uses standard HTTP GET commands with timeout parameters that can be processed by any device with HTTP capability, eliminating the need for device-specific SMS clients and enabling broad device compatibility without incurring SMS charges.
2Ease of operation
If TCP or UDP protocols are used with known IP addresses, then server can initiate communication, but heavy-type clients must monitor protocols and communication fails behind firewalls or with NAT routers
Solution Approach 1:
The patent implements a self-service mechanism where the client device automatically monitors for incoming push messages without requiring heavy-type client software to continuously monitor protocols. The push server sends HTTP GET commands with timeout parameters, and the lightweight client simply waits for and processes these commands, eliminating complex protocol monitoring requirements while enabling server-initiated communication even behind firewalls and NAT routers.
3Reliability
If SMS-type functionality is used, then communication can be established, but communication fails if the device is behind a firewall or with network address translation
Solution Approach 1:
The patent introduces an HTTP push server as an intermediary that mediates communication between the server and client devices. The push server receives HTTP GET commands with timeout parameters and forwards them to client devices, acting as a mediator that works around firewall and NAT router restrictions. This intermediary approach enables reliable communication in diverse network environments by using standard HTTP protocols that can traverse firewalls and NAT infrastructure.
Data Source
AI summary
A mobile device apparatus uses an HyperText Transfer protocol (HTTP) push operation to simulate server-initiated sessions. The illustrative mobile device apparatus comprises a push server logic operable in a push server that sends a message to a mobile device over a network. The push server logic is configured to receive a GET command from a mobile device. The GET command includes a mobile device identifier parameter and a timeout parameter designating a maximum time interval for the push server to reply with a message. The push server logic holds a GET command session until expiration of a timeout designated by the timeout parameter in a condition that no message is targeted to the mobile device. The push server logic terminates the GET command session by sending a message immediately in a condition that the message is targeted to the mobile device.