Mobile Service Component Upgrade via Dynamic Version Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile service upgrades on devices require all components to be upgraded simultaneously, leading to inefficiencies and inflexibility, including the need for device restarts, which can be inconvenient and time-consuming.
Innovation Solution
A method for independently upgrading each component of a mobile service, allowing for real-time upgrades without device restarts, by downloading and loading new versions of services based on invocation requests and managing dependencies through a class loader routing table and process prioritization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all components in mobile service are upgraded together, then system stability is maintained, but upgrade time increases and flexibility is reduced
Solution Approach 1:
The patent divides the mobile service into multiple independent components (e.g., location service, map service, advertising service), each with its own version management. This allows individual components to be upgraded independently without requiring upgrades of the entire service suite, thereby reducing upgrade time while maintaining system stability through selective updates.
Solution Approach 2:
The patent introduces dynamic version management where components can operate at different versions simultaneously. The system dynamically tracks which components need updating and applies updates on-demand based on invocation requests, transforming the static all-or-nothing upgrade model into a dynamic selective update mechanism.
2Device complexity
If all components are upgraded together, then dependency management is simplified, but adaptability to specific service needs is reduced
Solution Approach 1:
The patent segments the service dependency graph into independent components, each with its own version and dependency tracking. This allows the system to manage dependencies at the component level rather than requiring synchronization across the entire service suite, enabling flexible upgrades based on specific service needs while maintaining manageable dependency complexity through localized dependency graphs.
Solution Approach 2:
The patent implements a feedback mechanism where the version management system tracks invocation requests and service usage patterns. This feedback information is used to determine which components need updating and when, allowing the system to adapt upgrade strategies to actual service needs rather than following rigid schedules or requiring manual coordination.
3Reliability
If device restart is required after upgrade, then upgrade completeness is ensured, but user convenience is reduced
Solution Approach 1:
The patent segments the service components so that updates can be applied to individual components without requiring a complete system restart. Each component maintains its own execution context and can be updated independently, allowing the system to ensure upgrade completeness at the component level while avoiding the inconvenience of device-wide restarts.
Solution Approach 2:
The patent prepares updated components in advance and loads them into memory before they are actually invoked. This preliminary loading of updated components allows the system to switch to new versions seamlessly at invocation time without requiring a restart, ensuring upgrade completeness while maintaining user convenience during normal operation.
4Ease of operation
If silent background upgrade is used, then user experience is improved, but real-time upgrade capability is lost
Solution Approach 1:
The patent creates a dynamic upgrade system that can operate in multiple modes: silent background upgrades for non-critical components and real-time on-demand upgrades for critical services. The system dynamically determines the appropriate upgrade mode based on service type, user needs, and invocation requests, combining the benefits of both silent upgrades and real-time responsiveness.
Solution Approach 2:
The patent implements self-service upgrade capability where the version management system automatically identifies which components need updating and applies updates based on invocation requests without requiring manual user intervention. This self-service mechanism maintains user experience by handling upgrades transparently while enabling real-time upgrades when needed through automated response to service invocation demands.
Data Source
AI summary
This application provides example mobile service upgrade methods. In one example method, a target service invocation request sent by an application is received, where a target service is one of a plurality of services comprised in a mobile service, and the target service is an application which is installation-free in a terminal device. A new version of the target service is downloaded from a remote computer in response to determining, based on the service invocation request, that the target service needs to be upgraded, where the new version is a version that meets a requirement of the invocation request. The new version of the target service is then loaded and run.