Settlement Terminal Program Update via Volatile Memory Intermediary
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing settlement terminals face challenges in updating programs securely due to limited volatile memory capacity and security concerns when updating firmware or OS, as direct rewriting of nonvolatile memory is difficult and volatile memory is insufficient for storing large program updates.
Innovation Solution
A download method that determines specific touch screen operations at power-on to execute encrypted program updates, using a memory data rewriting program to decode and rewrite nonvolatile memory, with divided program updates and secure erasure of volatile memory data to enhance security and maintainability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a program update is performed by directly rewriting nonvolatile memory, then update functionality is achieved, but security is compromised and module board detachment prevents direct writing
Solution Approach 1:
The patent introduces a volatile memory (RAM) as an intermediary between the program server and nonvolatile memory. The update process involves downloading the program to volatile memory first, then executing a rewriting program from volatile memory to update the nonvolatile memory. This intermediary approach enables secure updates while preventing direct modification of nonvolatile memory, thereby maintaining security integrity.
Solution Approach 2:
The patent performs preliminary actions by first downloading the program to volatile memory and verifying it before executing the rewriting operation. The rewriting program is prepared in advance in volatile memory, and the system checks whether the program needs updating before initiating the rewrite process. This preliminary verification ensures that only authenticated and verified programs are installed, enhancing security.
2Device complexity
If the entire program is stored in volatile memory for updating, then update process is simplified, but the limited volatile memory capacity prevents storing large programs
Solution Approach 1:
The patent segments the program update process into multiple stages: downloading the program to volatile memory, executing the rewriting program, and then erasing the volatile memory. The rewriting program itself is segmented into functional components (download control, rewrite control, erasure control). This segmentation allows the system to handle large programs by processing them in manageable portions through the rewriting operation rather than requiring the entire program to reside in volatile memory simultaneously.
3Ease of operation
If the rewriting program is always present in volatile memory, then program updating is convenient, but security is reduced due to potential illegal analysis and rewriting
Solution Approach 1:
The patent employs a disposable volatile memory approach where the rewriting program is downloaded, executed, and then immediately erased from volatile memory. The volatile memory serves its purpose during the update process and is then discarded (erased) to eliminate any risk of illegal analysis or reuse. This disposable approach ensures that the rewriting program cannot be persistently stored or analyzed, thereby maintaining security while enabling convenient updates.
Solution Approach 2:
The patent implements a time-limited execution model where the rewriting program is executed rapidly and then immediately erased from volatile memory before any potential illegal analysis can occur. The system rushes through the execution phase and transitions to the erasure phase without allowing prolonged presence of the rewriting program in volatile memory. This rushing through mechanism ensures that the program is available for updating when needed but cannot be persistently analyzed or misused.
4Adaptability or versatility
If the module board is made detachable for program updating, then program replacement becomes flexible, but security is compromised and direct memory writing is enabled
Solution Approach 1:
The patent uses volatile memory as an intermediary that enables program updates without requiring module board detachment. The rewriting program is loaded into volatile memory and executed there, which then facilitates safe rewriting of the nonvolatile memory. This intermediary approach provides the flexibility of program replacement while maintaining the security benefits of a fixed, non-detachable module board architecture.
Data Source
AI summary
A download method of a program to a settlement terminal which includes a processor operated based on the program, a nonvolatile memory, a volatile memory and a touch screen and executes an on-line settlement. The download method includes a determination operation determining whether a specific operation to the touch screen is executed or not when power of the settlement terminal is turned on, a download operation in which, when the specific operation has been executed, a memory data rewriting program is downloaded from a program server to the volatile memory, and an update operation in which the processor executes the memory data rewriting program and thereby, a program to be updated is downloaded from the program server and is stored to the volatile memory and then, a program in the nonvolatile memory is rewritten by the program to be updated which is stored in the volatile memory.