Certified Intermediary Server for Secure RIA Delivery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for delivering Rich Internet Applications (RIAs) to mobile devices face challenges such as security, access control, computing power, bandwidth, and platform compatibility, making it difficult to develop and deploy applications that provide a rich user experience across various devices.
Innovation Solution
A system and method that utilizes a certified player on remote computing devices to invoke server-side web services through a single, secure, certified server intermediary, providing a secure and access-controlled channel for RIAs, enabling platform independence and offline functionality while abbreviating the certification process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If RIAs are delivered directly to mobile devices using traditional desktop methodologies, then the application functionality is maintained, but security is compromised due to device mobility and susceptibility to theft/loss
Solution Approach 1:
The patent introduces a server as an intermediary between the mobile device and the RIA application. The server hosts the application and manages secure access, while the mobile device only contains a lightweight client that communicates with the server. This intermediary architecture allows the application to maintain its functionality while the server enforces security policies, controls access based on device location and user authentication, and protects sensitive data from being exposed on the mobile device itself.
2Adaptability or versatility
If applications are developed for multiple mobile platforms and operating systems, then platform compatibility is improved, but development complexity and certification time increase significantly
Solution Approach 1:
The patent creates a universal server-based platform that can serve multiple mobile devices regardless of their specific platform or operating system. The server hosts the application in a platform-independent manner, while the mobile client is designed to work across different devices. This universal architecture eliminates the need to develop and certify separate applications for each mobile platform, as the server handles platform-specific concerns and provides a consistent application interface to all clients.
3Ease of operation
If application processing is transferred to the web client to provide rich user interface experience, then user experience is improved, but the mobile device's limited processing capacity and storage are overwhelmed
Solution Approach 1:
The patent segments the application processing into two parts: the user interface rendering and interaction logic are handled by the mobile client to provide a rich user experience, while the heavy processing, data management, and business logic are offloaded to the server. This segmentation allows the mobile device to display and interact with the application without being burdened by complex processing requirements, as the server handles the computationally intensive tasks and returns processed results to the client.
Data Source
AI summary
A system and a method of playing rich internet applications on remote computing devices by using a certifying player to invoke server-side web services through a single, secure, certifying intermediary server. The application player resides in the remote computing device and is configured to be executed by the remote computing device. The intermediary server is configured to communicate with the remote computing device via a network connection and to receive message requests from the application player and to send message responses to the application player. The intermediary server provides access of the RIA to the remote computing device by accessing an application server, where the RIA resides, via a single, secure and access-controlled network connection. The application player requests functionality of the RIA from the intermediary server via message requests and interprets the message responses received from the intermediary server. The message requests and responses may be Extensible Mark-up Language (XML) messages.