Universal Application Delivery System for Wireless Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprises face high costs in designing dedicated systems to provide software applications to wireless devices, making it impractical for non-critical applications, and there is a need for an efficient method to deliver applications over wireless networks.
Innovation Solution
A system and method that involves receiving selection data from front-end and back-end systems, transmitting service modules associated with applications to front-end systems, and processing output data, allowing for the provision of applications across multiple user devices while maintaining data security and billing capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a dedicated system is designed and built to provide software applications to wireless devices, then the application delivery capability is improved, but the system cost increases significantly
Solution Approach 1:
The patent implements a universal application delivery system that serves multiple enterprises and wireless devices through a shared infrastructure. The system provides application delivery, management, and distribution capabilities to multiple customers simultaneously, eliminating the need for each enterprise to build separate dedicated systems. This multi-functional approach maintains reliable application delivery while significantly reducing per-enterprise system costs.
Solution Approach 2:
The system uses virtualization and software-based replication to provide application delivery services. Instead of requiring physical dedicated hardware for each enterprise, the system creates virtual copies of application delivery environments that can be deployed across shared infrastructure, reducing hardware costs while maintaining service reliability.
2Productivity
If a dedicated system is built for application delivery, then application provision capability is improved, but the cost becomes unjustified for non-critical applications
Solution Approach 1:
The patent combines application delivery, management, and distribution functions into an integrated platform that serves multiple enterprises. By merging these functions and sharing resources across customers, the system achieves high application provision capability while reducing costs through economies of scale, making it economically viable even for non-critical applications.
Solution Approach 2:
The universal system provides multiple functions (application delivery, management, distribution) to multiple enterprises through a single platform, improving productivity while reducing the cost burden on individual enterprises, particularly for non-critical applications.
3Adaptability or versatility
If different versions of service modules are transmitted to different front-end systems, then customization capability is improved, but the system complexity increases
Solution Approach 1:
The patent segments the application delivery system into modular service modules that can be independently configured and transmitted to different front-end systems. This segmentation allows each module to be customized for specific enterprise requirements while maintaining overall system manageability through standardized interfaces and centralized control.
Solution Approach 2:
The system manages different service module versions by controlling configuration parameters rather than creating entirely separate systems. By changing parameters such as module versions, configuration settings, and deployment targets, the system achieves high customization capability while maintaining relatively simple system architecture through parameterized control.
Data Source
AI summary
Systems and methods are disclosed for providing an application. The systems and methods may include receiving a first selection data from a first front-end system or a first back-end system and receiving a second selection data from a second front-end system and a second back-end system. The systems and methods may next include transmitting a first version of a first service module to the first front-end system and transmitting a second version of the first service module to the second front-end system. In addition, the systems and methods may include receiving a first output data and a second output data from the first front-end system and from the second front-end system respectively, the first output data being produced by the first version of the first service module executed on the first front-end system and the second output data being produced by the second version of the first service module executed on the second front-end system.