Mobile App Deployment via Offline Data Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for application deployment on mobile devices are limited by the need for operating system-specific development, large data loads, and require network connectivity for interaction, making it difficult to deploy and use applications on devices with alternate operating systems and during periods of limited or no network connectivity.
Innovation Solution
A client application on a mobile device receives and stores mobile applications, processes user input data, authenticates with an application server, and transmits data via an indirect communication channel, allowing for offline data storage and reduced data transmission by using a hierarchical data structure that mirrors the server's structure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If existing application deployment methods are used, then applications can be deployed on mobile devices, but the data load between enterprise system and mobile device is large because screen layouts are transferred together with transactional data
Solution Approach 1:
The patent segments the application data into two distinct components: screen layouts (user interface elements) and transactional data (operational data). By separating these components, the system can download only the essential transactional data to the mobile device while keeping screen layouts on the server, thereby reducing the data load transmitted to the mobile device while maintaining deployment functionality.
Solution Approach 2:
The patent extracts and removes screen layouts from the data transmission process. Instead of transferring complete application packages including UI elements, the system extracts only the necessary transactional data for offline operation, leaving the screen layout definitions on the server to be rendered dynamically when needed.
2Ease of operation
If existing application deployment methods are used, then applications can be deployed on mobile devices, but interaction with the application is only possible while there is network connectivity since screen layouts are unable to be downloaded to the mobile device
Solution Approach 1:
The patent implements preliminary action by downloading and storing transactional data on the mobile device before network connectivity is lost. This allows the application to continue functioning with cached data during offline periods, enabling users to interact with the application even when disconnected from the network.
Solution Approach 2:
The patent introduces an intermediary layer (local database/cache on mobile device) that mediates between the user and the remote server. This intermediary stores transactional data locally, allowing the application to respond to user interactions offline and synchronize with the server when connectivity is restored.
3Ease of manufacture
If operating system-specific development is used, then applications can be deployed on mobile devices, but modifications and different installation requirements are needed for mobile devices with alternate operating systems
Solution Approach 1:
The patent implements universality by creating a platform-agnostic application architecture where the core application logic and data structures are operating system independent. The application uses standardized data formats and communication protocols that can be rendered across different operating systems (iOS, Android, Windows) without requiring separate development versions, thereby achieving cross-platform compatibility while maintaining development simplicity.
Data Source
AI summary
Some embodiments relate to an application server. The application server may comprise: a communication port to communicate with a client application installed on a mobile communication device, the client application being configured to assist the application server to deploy one or more mobile applications on the mobile communication device; an application database to store multiple records of operational data; and a processor. The processor may be configured to: authenticate the client application with the application server; receive from the client application, via a communications network, operational data indicative of information input to the mobile communication device by a user; and store in the application database the operational data received from the client application. Other embodiments relate to methods carried out on or by the application server and to mobile communication devices configured to perform related methods.