Business Web App Lifecycle Management with Multi-Tasking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Data processing applications face performance limitations due to slow network speeds, significant power consumption, and computing resource usage, particularly when transmitting large data sets, leading to user frustration, device freezing, and inefficiencies in data transmission.
Innovation Solution
Implementing techniques to reuse previously transmitted data stored in local temporary storage, such as RAM chips, to avoid frequent re-transmissions, thereby reducing computing resource and network bandwidth consumption, and enhancing data access speed and power efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is transmitted frequently from remote server to device, then data freshness is improved, but network bandwidth consumption increases and response time deteriorates
Solution Approach 1:
The patent pre-loads data from the remote server to local temporary storage (RAM) before it is actually needed. When a user navigates to a page, the required data is already cached locally, eliminating the need for real-time network requests and significantly reducing response time while maintaining data availability.
Solution Approach 2:
The patent creates local copies of data from the remote server and stores them in temporary storage (RAM) on the device. These copies are used for subsequent page loads and data transmissions, reducing the need for repeated network transmissions and improving response time while consuming less network bandwidth.
2Reliability
If data is transmitted frequently from remote server to device, then data availability is improved, but network bandwidth consumption increases
Solution Approach 1:
The patent creates local copies of data from the remote server and stores them in temporary storage (RAM) on the device. These copies are used for subsequent page loads and data transmissions, reducing the need for repeated network transmissions and improving response time while consuming less network bandwidth.
Solution Approach 2:
The system serves itself by using previously cached data from local temporary storage for subsequent page loads and data transmissions. This self-service approach reduces dependency on continuous network connectivity and minimizes network bandwidth consumption while maintaining data availability.
3Speed
If data is transmitted frequently from remote server to device, then data access is improved, but device power consumption increases
Solution Approach 1:
The patent pre-loads data from the remote server to local temporary storage (RAM) before it is actually needed. When a user navigates to a page, the required data is already cached locally, eliminating the need for real-time network requests and significantly reducing response time while maintaining data availability.
Solution Approach 2:
The patent creates local copies of data from the remote server and stores them in temporary storage (RAM) on the device. These copies are used for subsequent page loads and data transmissions, reducing the need for repeated network transmissions and improving response time while consuming less network bandwidth.
4Productivity
If computing resources are used for frequent data transmissions, then data processing capability is improved, but device responsiveness deteriorates
Solution Approach 1:
The system serves itself by using previously cached data from local temporary storage for subsequent page loads and data transmissions. This self-service approach reduces dependency on continuous network connectivity and minimizes network bandwidth consumption while maintaining data availability.
Data Source
AI summary
Technical solutions for managing business application life cycle with multi-tasking ability are provided. In some implementations, a method includes: at an enterprise data processing application: (A) activating a first application page, which includes: loading a first data set from a first data source, and causing the first data set to be displayed on the first application page; (B) switching from the first application page to a second application page, by: deactivating, without closing, the first application page, including: causing the first data set to be stored in a temporary storage; and activating a second application page; and (C) switching from the second application page back to the first application page, by: deactivating, without closing, the second application page; and re-activating the first application page, including: loading the first data set from the temporary storage, and causing the first data set to be displayed on the first application page.


