Remote Application Distribution System Activation Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing distribution systems for application software and firmware lack the ability to uniformly control the activation states of applications across multiple devices during remote updates, as devices have varying execution states due to user-specific settings and license limitations, making it challenging for manufacturers to manage and maintain devices efficiently.
Innovation Solution
A distribution system that includes an obtaining unit for identifying firmware and application information, a display unit for switching between settings screens based on obtained information, and a transmission unit for designating the operating state of applications after update, allowing for appropriate control of activation states across multiple devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If applications are distributed remotely to multiple devices, then collective maintenance can be performed, but the activation states of applications differ across devices due to user-specific settings and license limitations
Solution Approach 1:
The system allows different activation state designations for applications on different devices based on their individual states. The distribution server determines the appropriate activation state (active or stopped) for each device individually, considering factors such as whether the application is currently running, licensed, or stopped on that specific device. This enables uniform management policy while accommodating local device conditions.
2Ease of operation
If the activation state is not designated after update, then simple distribution can be performed, but appropriate control of activation states cannot be achieved
Solution Approach 1:
The distribution server determines and designates the activation state for the updated application before the actual distribution process. Based on the current state of the application on each device (whether active, stopped, licensed, or unlicensed), the server pre-determines the appropriate post-update activation state and transmits this designation to the device. This ensures reliable activation control is established in advance of the update operation.
3Use of energy by moving object
If applications are kept in stop state during update, then resource consumption is reduced, but version upgrades cannot be synchronized across multiple applications
Solution Approach 1:
The system dynamically adjusts the activation state of applications during the update process based on their current status and the update requirements. For applications that are currently stopped or unlicensed, the system can proceed with updates without requiring the application to be active first. The distribution server determines appropriate activation states post-update based on whether the application should be activated, stopped, or maintained in its current state, enabling flexible version synchronization across different application types and device conditions.
Data Source
AI summary
When applications in multiple devices are collectively, remotely updated, the applications cannot be uniformly determined to be activated and stopped because the execution states are different between devices and between applications. A distribution system obtains identification information and version information on each of firmware and an application that are installed in a network device, switches between a first screen for distribution setting pertaining to the firmware and a second screen for distribution setting pertaining to the application, based on the information obtained, and displays the screen, and transmits, to the network device, any of the distribution setting pertaining to the firmware designated through the first screen and the distribution setting pertaining to the application designated through the second screen. The distribution setting of the application transmitted includes designation of the operating state of the application after distribution.