Firmware Recovery Logging Across Controller Software States
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In information processing systems, when firmware of a functional device like a facsimile card is falsified, the recovery processing execution result cannot be recorded in the log due to the controller software not being activated during the recovery process.
Innovation Solution
The system activates controller software to record execution history data when firmware falsification is detected, then activates installer software to perform recovery processing, and reactivates the controller software after completion to log the success or failure of the recovery processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If installer software is activated to perform recovery processing, then firmware can be reinstalled, but controller software is not activated so recovery execution result cannot be recorded in log
Solution Approach 1:
The controller software performs preliminary actions before the recovery process: it detects firmware falsification, records execution history data indicating recovery is needed, and stores this information in the storage unit. This preliminary recording ensures that when the controller software is reactivated after recovery, it can retrieve the recorded information and log the recovery execution result, thus preventing loss of information about the recovery process.
2Loss of information
If controller software is activated during recovery processing, then recovery result can be recorded in log, but installer software cannot perform recovery processing
Solution Approach 1:
The system segments the recovery process into distinct phases with different software components active: (1) Detection and recording phase where controller software detects firmware falsification and records execution history data; (2) Recovery execution phase where installer software performs the actual firmware reinstallation; (3) Verification and logging phase where controller software reactivates to verify recovery success and log the result. This segmentation allows each software component to perform its specific function without interference.
Solution Approach 2:
The storage unit serves as an intermediary between the controller software and installer software. It stores execution history data recorded by the controller software during the detection phase, making this information available to the controller software during the verification phase after recovery. This intermediary mechanism enables information transfer without requiring the controller software to remain active throughout the entire recovery process.
3Device complexity
If controller software remains inactive during recovery, then system complexity is reduced, but log recording capability is lost
Solution Approach 1:
The controller software performs all necessary log recording actions before deactivating during recovery processing. It records execution history data indicating that recovery is needed and stores this in the storage unit. This preliminary action ensures that when the controller software reactivates after recovery, it can immediately retrieve the recorded information and log the recovery execution result, eliminating the need for continuous activation.
Data Source
AI summary
An information processing system includes a processor, in which the processor: records information in a storage unit via controller software for controlling a functional device and recording a log related to the functional device when a falsification of firmware installed in the functional device is detected in a state where the controller software has been activated, the information indicating that recovery processing for reinstalling the firmware in the functional device is to be executed; activates installer software for performing the recovery processing in a state where the controller software is not activated and executes the recovery processing via the installer software; and activates the controller software after executing the recovery processing, and when the firmware of the functional device is normal and the information indicating that the recovery processing is to be executed has been recorded in the storage unit, records, in a log, via the controller software, that the recovery processing has been executed and that the recovery processing has succeeded.