Asynchronous Push Application Gateway for Wireless Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developing software applications for wireless devices is challenging due to the variety of devices, restricted resources, and the complexity of delivering data, especially with browser-based applications that require significant bandwidth and are not efficiently executed across different platforms.
Innovation Solution
A communication system enabling asynchronous push-based applications using a notification protocol, such as WS-Eventing, that allows wireless devices to subscribe to topics and receive updates dynamically, with an application gateway mediating between devices and backend services for efficient message transformation and delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If browser-based applications are used to provide cross-platform compatibility, then adaptability across different devices is improved, but resource consumption and network bandwidth requirements increase significantly
Solution Approach 1:
The patent introduces a runtime environment as an intermediary layer between the application and the device hardware. This runtime environment executes the application logic once and translates it for different device types, eliminating the need for multiple platform-specific implementations while reducing resource consumption by avoiding repeated interpretation across different browsers.
Solution Approach 2:
The patent creates a virtualized copy of the execution environment through the runtime environment. Instead of running applications natively on each diverse device, the system copies the application logic into a standardized runtime environment that can be efficiently executed across different device types, reducing overall system resource consumption.
2Adaptability or versatility
If browser-based applications are used to ensure platform independence, then versatility across devices is improved, but network transfer bandwidth requirements increase
Solution Approach 1:
The patent performs preliminary compilation and packaging of applications into a standardized format that can be executed by the runtime environment. This preliminary action eliminates the need for continuous downloading and rendering of HTML pages in browsers, significantly reducing ongoing network bandwidth requirements while maintaining platform independence.
3Reliability
If proprietary push application implementations are used, then notification functionality is achieved, but ease of deployment and standardization deteriorates
Solution Approach 1:
The patent creates a universal runtime environment that can execute multiple types of applications including push notifications, email, and messaging through a single standardized platform. This multi-functional approach eliminates the need for separate proprietary implementations for each application type, greatly easing deployment while maintaining reliable notification functionality.
4Adaptability or versatility
If applications are rendered at runtime in browsers, then adaptability to different devices is improved, but execution efficiency and responsiveness deteriorate
Solution Approach 1:
The patent replaces the browser-based rendering mechanism with a dedicated runtime environment that executes applications more efficiently. This substitution eliminates the overhead of HTML parsing, CSS rendering, and JavaScript interpretation that plagues browser-based applications, significantly improving execution efficiency and responsiveness while maintaining device adaptability through the standardized runtime interface.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
There is provided a system and method of enabling asynchronous push-based applications on a wireless device in a system having an application gateway server including an application repository and a server proxy including an event sink for communicating between the system and the device. The method comprises reading a Web service interface, generating a Web service interface therefrom conforming to a notification protocol, creating a notification-based application bundle for the Web service, publishing the notification-based application bundle, creating an event source. The system comprises an application gateway server, an application repository and an application registry. The application gateway includes an event sink for communicating between the system and the device. The application gateway server is configured for communication with a backend server including an event source.