Fault repairing method and device for solid state disk, medium and equipment

CN121725867APending Publication Date: 2026-03-24LEIZHISHU SYST TECH (XIAN) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-12-22
Publication Date
2026-03-24

AI Technical Summary

Technical Problem

In existing technologies, solid-state drives require manual inspection and repair when they fail, which affects the stability and availability of the device. Furthermore, fault alarms are not timely and lack an automatic and efficient self-repair mechanism.

Method used

By monitoring abnormal situations, the system notifies users of faults and confirms repairs, erases physical blocks in the data area, updates the bad block table, initializes the mapping table, and automatically allocates available physical blocks in the event of a fault, establishing a mapping relationship between logical addresses and physical addresses.

Benefits of technology

It enables rapid self-repair in the event of a solid-state drive failure, improving the overall availability and stability of the device and reducing maintenance costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121725867A_ABST
    Figure CN121725867A_ABST
Patent Text Reader

Abstract

The invention discloses a fault repairing method and device for a solid state disk, a medium and equipment, and relates to the technical field of computer storage. The running process of the solid state disk is monitored in real time, and whether the solid state disk is in the fault state needing to be repaired or not is judged in real time through the preset threshold value, so that when the solid state disk breaks down, feedback is given to a user in time, the user is prompted to conduct repair confirmation, and after the repair confirmation instruction is received, repair is conducted. According to the method, firstly, all physical blocks, corresponding to a data area of a user, in the solid state disk are erased, physical blocks which fail to be erased serve as bad blocks to be added into a bad block table in the erasing process, a mapping table is initialized after erasing, and when a data write-in instruction for the solid state disk is received subsequently, the data write-in instruction for the solid state disk is written into the bad block table. And allocating available physical blocks to the bad blocks according to the bad block table and establishing a corresponding mapping relationship. When the solid state disk breaks down, timely feedback and self-repairing can be achieved, and the overall usability and stability of the solid state disk are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of computer storage technology, and in particular to a method, apparatus, medium, and device for repairing faults in a solid-state drive (SSD). Background Technology

[0002] Currently, with the rapid development of computer technology, solid-state drives (SSDs) are widely used in personal computers, servers, mobile terminals and other devices due to their advantages such as high-speed read and write, low power consumption and shock resistance.

[0003] In existing technologies, the core storage medium of solid-state drives (SSDs) is FLASH memory chips. During long-term use, FLASH memory chips are prone to problems such as bad blocks and UECC (Uncorrectable Error Correction Code). When an SSD malfunctions, it is typically inspected, repaired, or replaced manually by professional technicians.

[0004] However, if a fault occurs, manual repair is often required, which often necessitates removing the solid-state drive (SSD) from the corresponding computer device. This inevitably affects the continuous processing of data on the original computer device, meaning that the overall availability and stability of the SSD are relatively poor. Summary of the Invention

[0005] Therefore, it is necessary to provide a method, apparatus, medium, and device for repairing solid-state drives (SSDs) to address the aforementioned technical problems.

[0006] The present invention adopts the following technical solution: This invention provides a method for repairing solid-state drives (SSDs). First, it monitors for abnormal conditions during SSD operation. When the abnormal condition exceeds a preset threshold, it displays an information interface to the user indicating an SSD failure and confirming the repair. Then, upon receiving a repair confirmation command in response to a user operation, it erases all physical blocks in the SSD corresponding to the user's data area. Physical blocks that fail to be erased are added as bad blocks to a bad block table, and the SSD's mapping table is initialized. Finally, when a data write command to the SSD is received, it allocates available physical blocks outside the bad block table for the data write command and establishes a mapping relationship between the logical addresses and physical addresses of the allocated physical blocks based on the mapping table.

[0007] This invention provides a device for repairing faults in a solid-state drive, comprising: The monitoring unit is used to monitor abnormal conditions during the operation of the solid-state drive. When the abnormal condition exceeds a preset threshold, it displays an information interface to the user to indicate solid-state drive failure and confirm repair. The control unit is used to erase all physical blocks in the solid-state drive corresponding to the user's data area after receiving a repair confirmation command in response to user operation; add physical blocks that fail to be erased as bad blocks to the bad block table, and initialize the mapping table of the solid-state drive; when a data write command to the solid-state drive is received, allocate available physical blocks in the solid-state drive other than the bad block table for the data write command, and establish a mapping relationship between the logical address and physical address of the allocated physical block based on the mapping table.

[0008] The present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the above-described solid-state drive fault repair method.

[0009] The present invention provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the above-mentioned solid-state drive fault repair method.

[0010] The above-mentioned at least one technical solution adopted in this invention can achieve the following beneficial effects: Bad blocks on solid-state drives (SSDs) typically occupy only a small portion of the total storage space. This invention monitors the SSD's operation in real time and uses preset thresholds to determine if the SSD has entered a fault state requiring repair. This allows for timely feedback to the user when an SSD malfunctions, prompting them to confirm repair. Upon receiving a confirmation command, the invention first erases all physical blocks in the SSD corresponding to the user's data area, clearing all data and potential error markers. During the erasure process, failed erase blocks are added to a bad block table. After erasure, the mapping table is initialized, clearing any unusable mappings. When subsequent data write commands are received to the SSD, usable physical blocks are allocated based on the bad block table, and corresponding mappings are established. This invention provides rapid feedback when an SSD malfunctions and automatically repairs the fault. After automatic and rapid repair, the system can resume data processing on the original computer based on usable physical blocks, improving the overall availability and stability of the SSD. Attached Figure Description

[0011] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this invention, illustrate exemplary embodiments of the invention and are used to explain the invention, but do not constitute an undue limitation of the invention. In the drawings:

[0012] Figure 1 A schematic diagram of a fault repair method for a solid-state drive provided by the present invention; Figure 2A schematic diagram of a solid-state drive fault repair device provided by the present invention; Figure 3 A schematic diagram of a fault repair process on the host device side provided by the present invention; Figure 4 A schematic diagram of a fault repair process on the solid-state drive side provided by the present invention; Figure 5 This is a schematic diagram of a self-repair method in a solid-state drive device provided by the present invention; Figure 6 This is a schematic diagram of a solid-state drive fault repair device provided by the present invention. Detailed Implementation

[0013] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this invention, and not all of them. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.

[0014] Currently, when a solid-state drive (SSD) malfunctions during operation, existing technologies typically have the following shortcomings: 1. The fault alarms for solid-state drives (SSDs) are not timely or clear, and the host cannot quickly know the fault status of the SSD, resulting in the user not being able to take timely countermeasures.

[0015] 2. The repair process for solid-state drives (SSDs) relies on manual intervention, requiring professional technicians to inspect, repair, or replace them. This not only results in low repair efficiency but also increases maintenance costs and may lead to data loss or prolonged device malfunction. The lack of an automatic and efficient self-repair mechanism prevents SSDs from autonomously recovering after failure, impacting the overall availability and stability of the device.

[0016] Therefore, there is an urgent need for a technical solution that can provide timely alarms for solid-state drive failures and enable automatic and efficient self-repair, in order to solve the aforementioned problems in existing technologies.

[0017] The technical solutions provided by the various embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0018] Figure 1 This is a schematic diagram of a solid-state drive (SSD) fault repair method according to the present invention, which specifically includes the following steps: S101: Monitors abnormal conditions during the operation of the solid-state drive (SSD). When the abnormal condition exceeds a preset threshold, it displays an information interface to the user to indicate SSD failure and confirm repair.

[0019] S102: Upon receiving a repair confirmation command in response to a user operation, erase all physical blocks in the solid-state drive corresponding to the user's data area.

[0020] S103: Add the physical blocks that failed to be erased as bad blocks to the bad block table and initialize the mapping table of the solid-state drive.

[0021] S104: When a data write command to the solid-state drive is received, an available physical block other than the bad block table in the solid-state drive is allocated for the data write command, and a mapping relationship between the logical address and physical address of the allocated physical block is established based on the mapping table.

[0022] Generally, solid-state drives (SSDs) are typically used in conjunction with a host computer. Therefore, this invention uses a host computer as the main entity that directly interacts with the SSD. The host computer referred to in this invention can be a server set up on a business platform, or a device such as a desktop computer, laptop computer, or embedded board that can execute the solution of this invention.

[0023] Figure 2 This is a schematic diagram of a solid-state drive fault repair device according to the present invention. Subsequent descriptions will refer to it as such. Figure 2 The device will be used as an example for explanation. It is understandable that... Figure 2 This is merely an exemplary device.

[0024] The solid-state drive (SSD) device is a SATA or PCIe interface SSD based on NAND flash storage media. It integrates a control unit and is equipped with two GPIO interfaces. GPIO0 can be used to send SSD fault alarm information and self-repair completion information to the host; GPIO1 can be used to monitor and receive control information from the host in real time. The host device can be a computer device with SATA or PCIe protocols. The host motherboard is equipped with GPIO detection and control circuitry for level signal interaction with the SSD's GPIO0 and GPIO1 interfaces. The host's power management module supports independent power-on and power-off control for the SATA or PCIe interface SSD device.

[0025] Figure 3 This is a schematic diagram of a fault repair process on the host device side in this invention. Figure 4 This is a schematic diagram of a fault repair process on the solid-state drive side in this invention. The following is based on... Figure 3 and Figure 4 Please provide a detailed explanation.

[0026] Typically, the host can monitor the operation of the solid-state drive (SSD). When a major anomaly occurs during the operation of the SSD, it may enter a fault state (such as write-protected state), and the control unit inside the SSD will trigger a fault alarm process.

[0027] In specific cases, according to one or more embodiments of the present invention, when the number of bad blocks on the solid-state drive (SSD) exceeds a first threshold and / or the read / write error rate exceeds a second threshold, the SSD is considered to have experienced a significant anomaly. In this case, an information interface can be displayed to the user to indicate the SSD malfunction and confirm repair. The number of bad blocks and the read / write error rate allow for a relatively accurate assessment of the SSD's condition.

[0028] Specifically, in the interaction between the host and the solid-state drive (SSD), the SSD's control unit can control its general-purpose input / output interface (GPIO1) to output an alarm level signal, for example, output a 3.3V high-level signal. This high-level signal is transmitted to the host's GPIO2 interface through a dedicated level signal transmission line.

[0029] It should be noted that this alarm level signal can be high, low, or other alternating high and low level signals. This signal is transmitted to the host via a hardware connection to notify the host that the solid-state drive is currently in a fault state. This fault state can be a protective state indicating that the solid-state drive is no longer responding to read and write operations.

[0030] The host monitors the level signal output by GPIO1 of the solid-state drive in real time through its internal alarm signal detection module (integrated in the GPIO control circuit of the motherboard). When an alarm level signal is detected, the host can display fault alarm information to the user through pop-up windows on the display interface, sound prompts, etc.

[0031] For example, the host computer can display a pop-up window on its screen saying "The solid-state drive has entered a fault state. Please trigger the repair process" through its internal alarm module. It can also emit a "beep" sound through the host computer's speaker. After seeing the pop-up window and hearing the prompt, the user can click the "Trigger solid-state drive repair" button in the "Disk Management" tool of the host computer's operating system to confirm the repair.

[0032] After the user confirms the alarm information and confirms the repair, the host control module can receive the user's repair trigger command. It can control the host's GPIO3 interface to output a repair notification level signal through the host's control command (such as the repair trigger command issued by the operating system), for example, outputting a 0V low level signal. This low level signal is transmitted to the GPIO1 interface of the solid-state drive.

[0033] It should be noted that this repair notification signal can be a high level, a low level, or other alternating high and low level signals. This signal is transmitted to the solid-state drive (SSD) to notify it to initiate a self-repair process.

[0034] When the SSD's control unit detects a 0V low-level signal received from the host's GPIO3 interface on its GPIO1 interface, it can transmit this signal to the SSD's control unit, causing the control unit to initiate a self-repair process. Figure 5 This is a schematic diagram of a self-repair method in a solid-state drive device according to the present invention, which may specifically include: Full erasure of FLASH storage media: The control unit sends an erase command to the FLASH storage media of the solid-state drive to erase all physical blocks of the FLASH storage media where the user's data area is located, in order to clear all data and potential error marks in the FLASH storage media.

[0035] Added bad block detection and bad block table update: During the FLASH storage media erasure process, the solid-state drive's control unit can detect and identify physical blocks that failed to be erased; these physical blocks are unusable bad blocks. As mentioned above, solid-state drives also perform bad block monitoring during normal operation, but usually not all bad blocks are detected during normal operation. Therefore, new bad blocks can be identified during the erasure process. In one or more embodiments of this invention, it can be determined whether the physical blocks that failed to be erased have been recorded in the bad block table; if not, the physical blocks that failed to be erased are added to the bad block table as bad blocks.

[0036] The SSD's control unit can thus detect and identify newly added, unusable bad blocks after erasure. The physical address information of these new bad blocks is added to and saved in the SSD's internal bad block table. Subsequent data read / write operations on the SSD can be configured to automatically skip bad blocks recorded in the bad block table, avoiding the use of faulty storage areas.

[0037] Mapping table reinitialization: The solid-state drive (SSD) control unit reinitializes the logical address to physical address mapping table (L2P mapping table) of the SSD, clears the original mapping relationship, and establishes a new initial mapping state to ensure that the mapping between logical address and physical address is accurate during subsequent data read and write processes.

[0038] After the SSD self-repair process is complete, the control unit again controls its GPIO1 interface to output a restart notification signal, such as a 0V low-level signal. This signal is transmitted to the host's GPIO2 interface to notify the host that the self-repair is complete. It should be noted that this restart notification signal can be a high level, a low level, or other alternating high and low level signals. This restart notification signal is transmitted to the host to notify the host that the SSD self-repair is complete and a power-on / power-off operation is required.

[0039] Furthermore, after the host detects the restart notification level signal output by the SSD's GPIO2 via the restart notification detection module, it can send a restart notification detection signal to the host control module. Upon receiving this restart notification detection signal, the host control module can control the SSD's power supply line through its power management module, first powering down the SSD for a preset time (e.g., 3-5 seconds), and then powering it back on. After the SSD is powered back on, its control unit can load the updated bad block table and the re-initialized L2P mapping table in the DRAM, clearing all fault states and restoring it to normal operating condition, allowing for normal data read and write operations.

[0040] At this point, the host's "Disk Management" tool can recognize the solid-state drive (SSD) normally, and the user can partition and format it. After that, the SSD can read and write data normally and return to normal operation.

[0041] based on Figure 1 The solid-state drive (SSD) fault repair method described herein addresses the issue that bad blocks on an SSD typically constitute only a small portion of the total storage space. This invention monitors the SSD's operation in real-time and uses preset thresholds to determine if the SSD has entered a fault state requiring repair. This allows for timely feedback to the user upon SSD failure, prompting confirmation for repair. Upon receiving confirmation, the invention first erases all physical blocks in the SSD corresponding to the user's data area, clearing all data and potential error markers. During erasure, failed erase blocks are added to a bad block table. After erasure, the mapping table is initialized, clearing any unusable mappings. When subsequent data write commands are received, usable physical blocks are allocated based on the bad block table, and corresponding mappings are established. This invention enables rapid feedback when an SSD malfunctions and automatically completes logical fault repair. After automatic and rapid repair, data processing on the original computer equipment can resume based on usable physical blocks, improving the overall availability and stability of the SSD.

[0042] This invention provides a self-repair method for solid-state drives (SSDs), enabling the SSD to promptly send a fault alarm signal to the host when a fault occurs, and to perform autonomous repair under host triggering, ultimately restoring normal use, thereby improving the availability and stability of the SSD and reducing maintenance costs.

[0043] When applying the solid-state drive fault repair method provided by this invention, it is not necessary to... Figure 1 The steps shown are executed in sequence. The specific execution order of each step can be determined as needed, and this invention does not impose any restrictions on it.

[0044] The above describes a method for repairing solid-state drives (SSDs) based on one or more embodiments of the present invention. Based on the same concept, the present invention also provides a corresponding SSD repair device, such as... Figure 2 As shown.

[0045] Figure 2 A schematic diagram of a solid-state drive (SSD) fault repair device provided by the present invention includes: The monitoring unit 201 is used to monitor abnormal conditions during the operation of the solid-state drive. When the abnormal condition exceeds a preset threshold, it displays an information interface to the user to indicate solid-state drive failure and confirm repair. The control unit 201 is used to perform an erase operation on all physical blocks in the solid-state drive corresponding to the user's data area after receiving a repair confirmation command in response to a user operation; add physical blocks that fail to be erased as bad blocks to the bad block table, and initialize the mapping table of the solid-state drive; when a data write command to the solid-state drive is received, allocate available physical blocks in the solid-state drive other than the bad block table for the data write command, and establish a mapping relationship between the logical address and physical address of the allocated physical block based on the mapping table.

[0046] Specifically, regarding the interaction between the host and the solid-state drive (SSD), the device can be further divided into SSD-side devices and host-side devices, which may include: Solid-state drive side device: The alarm signal output module includes a GPIO interface for the solid-state drive, which is connected to the control unit. Under the control of the control unit, it outputs an alarm level signal to the host device to realize fault alarm; after self-repair is completed, it outputs a restart notification level signal to the host device.

[0047] The repair trigger receiving module includes a GPIO interface for the solid-state drive, which is connected to the control unit. It is used to receive the repair notification level signal sent by the host device and transmit the repair notification level signal to the control unit to trigger the self-repair process.

[0048] The self-repair module, part of the control unit, performs self-repair operations under the control of the control unit. These operations include a FLASH erase submodule that controls the complete erasure of the FLASH storage medium, a bad block detection and update submodule that detects new bad blocks and updates the bad block table, and a mapping table initialization submodule that re-initializes the mapping table.

[0049] The control unit connects to the host device via SATA or PCIe signals and is used to receive commands and data for data storage and retrieval. It also receives fault detection signals from the fault detection module, controls the alarm signal output module to output corresponding level signals, receives repair trigger signals from the repair trigger receiving module and controls the self-repair module to perform self-repair operations, and controls the alarm signal output module to output a restart notification signal after self-repair is complete.

[0050] The flash memory module, consisting of multiple FLASH chips, is connected to the control unit of the solid-state drive (SSD) and is used to store data and accept erase operations from the FLASH erase submodule.

[0051] Main unit side device: The alarm signal detection module includes a GPIO interface on the host computer, which is used to detect the alarm level signal output by the solid-state drive device in real time. When an alarm level signal is detected, an alarm detection signal is sent to the host control module.

[0052] The alarm notification module is connected to the host control module. Under the control of the host control module, it displays fault alarm information to the user through pop-up windows, sound prompts, and other means.

[0053] The repair trigger signal output module includes the host's GPIO interface, which is connected to the host control module. Under the control of the host control module, it outputs a repair notification level signal to the solid-state drive side device.

[0054] The restart notification detection module includes the host's GPIO interface, which is used to detect the level signal output by the solid-state drive device in real time. When a restart notification level signal is detected, a restart notification detection signal is sent to the host control module.

[0055] The power management module is connected to the host control module and, under the control of the host control module, performs power-on and power-off operations on the solid-state drive.

[0056] The host control module is connected to the alarm signal detection module, alarm prompt module, repair trigger signal output module, restart notification detection module, and power management module, respectively. It is used to receive alarm detection signals from the alarm signal detection module and control the alarm prompt module to work, receive user repair trigger commands and control the repair trigger signal output module to output repair notification level signals, and receive restart notification detection signals from the restart notification detection module and control the power management module to perform power-on and power-off operations on the solid-state drive.

[0057] Specific limitations regarding the solid-state drive (SSD) fault repair device can be found in the above description of SSD fault repair methods, and will not be repeated here. Each module in the aforementioned SSD fault repair device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device, or stored in the computer device's memory as software, so that the processor can call and execute the corresponding operations of each module.

[0058] The present invention also provides a computer-readable storage medium storing a computer program that can be used to execute the above-described... Figure 1 The provided troubleshooting methods for solid-state drives (SSDs).

[0059] This invention also provides a computer device. At the hardware level, the computer device includes a processor, an internal bus, a network interface, memory, and non-volatile memory, and may also include other hardware required for various operations. The processor reads the corresponding computer program from the non-volatile memory into memory and then executes it to achieve the above-mentioned functions. Figure 1 The provided troubleshooting methods for solid-state drives (SSDs).

[0060] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. Any references to memory, storage, databases, or other media used in the embodiments provided by this invention can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0061] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this invention.

Claims

1. A method for repairing faults in a solid-state drive, characterized in that, include: Monitor abnormal conditions during the operation of the solid-state drive (SSD). When the abnormal condition exceeds a preset threshold, display an information interface to the user to indicate SSD failure and confirm repair. When a repair confirmation command is received in response to a user operation, all physical blocks in the solid-state drive corresponding to the user's data area are erased. Physical blocks that failed to be erased are added as bad blocks to the bad block table, and the mapping table of the solid-state drive is initialized. When a data write command to the solid-state drive is received, an available physical block outside the bad block table in the solid-state drive is allocated for the data write command, and a mapping relationship between the logical address and physical address of the allocated physical block is established based on the mapping table.

2. The solid-state drive fault repair method as described in claim 1, characterized in that, When the abnormal condition exceeds a preset threshold, an information interface is displayed to the user to indicate a solid-state drive failure and confirm repair, specifically including: When the number of bad blocks on the solid-state drive (SSD) exceeds the first threshold and / or the read / write error rate of the SSD exceeds the second threshold, an information interface is displayed to the user to indicate SSD failure and confirm repair.

3. The solid-state drive fault repair method as described in claim 1, characterized in that, The step of adding physical blocks that failed to be erased as bad blocks to the bad block table specifically includes: Determine whether the physical blocks that failed to be erased have been recorded in the bad block table; If not, the physical blocks that failed to be erased are added to the bad block table as bad blocks.

4. The solid-state drive fault repair method as described in claim 1, characterized in that, The method further includes: When the abnormal condition exceeds a preset threshold, the solid-state drive is marked as faulty, and the faulty condition indicates that the solid-state drive no longer responds to read and write operations. After initializing the mapping table of the solid-state drive (SSD), the SSD is powered off and held for a preset time. Then, the SSD is powered on and loaded with the updated bad block table and the initialized mapping table. Finally, the fault status flag of the SSD is removed.

5. A fault repair device for a solid-state drive, characterized in that, include: The monitoring unit is used to monitor abnormal conditions during the operation of the solid-state drive. When the abnormal condition exceeds a preset threshold, it displays an information interface to the user to indicate solid-state drive failure and confirm repair. The control unit is used to erase all physical blocks in the solid-state drive corresponding to the user's data area after receiving a repair confirmation command in response to user operation; add physical blocks that fail to be erased as bad blocks to the bad block table, and initialize the mapping table of the solid-state drive; when a data write command to the solid-state drive is received, allocate available physical blocks in the solid-state drive other than the bad block table for the data write command, and establish a mapping relationship between the logical address and physical address of the allocated physical block based on the mapping table.

6. A computer-readable storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, implements the method as described in any one of claims 1 to 4.

7. A computer device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method as described in any one of claims 1 to 4.