Display Apparatus Page Loading via URL Parameter Injection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current display apparatuses face inefficiencies in managing and loading applications, particularly due to the need for instant-launching and instant-loading mechanisms that result in slow loading times and a lack of unified management, leading to poor user experience and low management efficiency.
Innovation Solution
The display apparatus obtains a code package for an application, which includes an application description file, to generate a loading page with rich content by reading and writing loading parameters into the URL of the loading page, allowing for the presentation of display content during the loading process, and loading the application display page in the background to improve user experience and efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If instant-launching and instant-loading mechanisms are used to enable quick application launch, then application launch speed is improved, but loading time increases and user experience deteriorates
Solution Approach 1:
The patent applies preliminary action by pre-fetching and caching application resources (images, scripts, stylesheets) in the background before the application actually needs to load. When an application is launched, the controller checks if resources are already cached and serves them immediately, avoiding the need to download everything during the loading phase. This resolves the contradiction by preparing data in advance so that the actual loading time is minimized while maintaining quick launch capability.
2Device complexity
If cloud-hosted applications are used to reduce device complexity, then device complexity is reduced, but loading performance and user experience worsen
Solution Approach 1:
The patent introduces a local caching mechanism as an intermediary between the cloud-hosted application and the display apparatus. Instead of directly fetching all resources from the cloud every time an application is launched, the system first checks the local cache for previously downloaded resources. This intermediary caching layer reduces the dependency on cloud latency while maintaining the cloud-hosted architecture, thereby improving loading performance without increasing device complexity.
3Reliability
If traditional application loading methods are used to ensure reliability, then system stability is improved, but loading speed decreases and productivity worsens
Solution Approach 1:
The patent implements preliminary action by pre-loading and caching application resources during idle periods or in the background before the user actually needs to access the application. The controller maintains a caching mechanism that stores images, scripts, and stylesheets locally, and checks this cache before attempting to load resources from the cloud. This approach maintains system reliability by having a fallback mechanism while significantly improving loading speed through reduced network dependency.
4Productivity
If comprehensive application resources are cached to improve loading speed, then loading performance is improved, but device memory consumption increases
Solution Approach 1:
The patent applies local quality by implementing a selective caching strategy where different types of application resources are cached with different priorities and retention policies. Critical resources that are frequently accessed (such as core application scripts and essential images) are cached locally with higher priority, while less critical resources are either not cached or cached with lower priority. This differentiated approach improves loading performance for essential functions while limiting overall memory consumption by not uniformly caching all possible resources.
Data Source
AI summary
The present application discloses a page loading method and a display apparatus. While launching an application, a URL of the application, a code package, and a URL of a loading page are obtained; when the URL of the application is a target protocol URL, a loading parameter is read from the code package; the loading parameter is written into the URL of the loading page to generate a new URL of the loading page; and based on the new URL of the loading page, a loading page including display content corresponding to the loading parameter is presented on a display.