Data reset and restoration method and terminal

Abstract

A data reset and restoration method and terminal monitor hijacking events of target data. If a hijacking event occurs, a preset reset strategy is obtained from the cloud; an independent memory area is generated according to the preset reset strategy, and the target data before the hijacking is stored in the independent memory area; and the call relationship of the target data is directed to the independent memory area. The present invention monitors hijacking events of target data to ensure that the recovery process can be automatically triggered when the data is tampered with or hijacked. If a hijacking event is detected, the system can obtain a preset reset strategy from the cloud, generate an independent memory area, and store the target data before the hijacking in the area, thereby ensuring the integrity and accuracy of data recovery.

Description

Technical Field

[0001] The present invention relates to the field of data processing, and in particular to a data resetting and restoring method and a terminal. Background Art

[0002] In modern computer systems, data integrity and security are important guarantees for the normal operation of the system. To this end, various data self-verification methods are widely used to ensure that data has not been illegally tampered with or lost during data storage, transmission or processing. Existing self-verification technologies generally include the following: Checksum: Checksum is a method of verifying whether data has changed by calculating the sum of data blocks and comparing it with the pre-stored or transmitted checksum. This method is often used to check the integrity of files or data packets, but it can only detect whether the data has undergone simple bit-level changes, and cannot detect complex tampering or hijacking.

[0003] Cyclic Redundancy Check (CRC): CRC is a method of verifying data integrity by generating a cyclic redundancy check code for a data block. Compared with checksums, CRC can detect data transmission errors more effectively and is often used in network communications. However, it also relies on static algorithms and local calculations, requiring recalculation and comparison of each piece of data, which may result in a waste of computing resources.

[0004] However, the above technologies have the following defects: For example, checksum and CRC rely on static data comparison and algorithm calculation, and need to continuously expand and compare the data in the memory. This not only takes up a lot of computing resources, but also makes it difficult to update and restore data in real time in a dynamic environment. Traditional verification methods usually require multi-threading to handle different verification tasks separately. This multi-threaded processing method will lead to excessive consumption of system resources, affect overall performance, and cause waste of resources. Summary of the invention

[0005] The technical problem to be solved by the present invention is to provide a data resetting and restoring method and terminal to solve the problem of resource waste in the data self-checking process.

[0006] In order to solve the above technical problems, the technical solution adopted by the present invention is: A data reset and restoration method comprises the steps of: S1. Monitor the hijacking event of the target data, and if the hijacking event occurs, obtain a preset reset strategy from the cloud; S2. Generate an independent memory area according to the preset reset strategy, and store the target data before being hijacked in the independent memory area; S3. Point the calling relationship of the target data to the independent memory area.

[0007] In order to solve the above technical problems, another technical solution adopted by the present invention is: A data reset and restoration terminal comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor completes the following steps when executing the computer program: S1. Monitor the hijacking event of the target data, and if the hijacking event occurs, obtain a preset reset strategy from the cloud; S2. Generate an independent memory area according to the preset reset strategy, and store the target data before being hijacked in the independent memory area; S3. Point the calling relationship of the target data to the independent memory area.

[0008] The beneficial effects of the present invention are: providing a data reset and restoration method and terminal, by monitoring the hijacking event of the target data, ensuring that the recovery process can be automatically triggered when the data is tampered with or hijacked. If a hijacking event is detected, the system can obtain a preset reset strategy from the cloud, generate an independent memory area, and store the target data before the hijacking in the area, thereby ensuring the integrity and accuracy of data recovery. Compared with traditional self-verification technologies such as checksums and CRC, this method no longer relies on static data and complex multi-threading technologies for memory expansion and comparison, but performs real-time recovery through dynamic cloud strategies. This not only simplifies the data protection process, but also avoids the waste of resources and inefficiency caused by static data verification. At the same time, the method does not need to constantly compare local and remote data, which greatly improves the efficiency of data recovery and reduces the possibility of false alarms and false positives. Ultimately, the user experience is optimized, computing resources are saved, and the data recovery process is more intelligent and automated. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 A flowchart of a data reset and restoration method according to an embodiment of the present invention; Figure 2 A schematic diagram of a data resetting and restoring terminal in an embodiment of the present invention; Description of labels: 1. A data reset and restoration terminal; 2. A memory; 3. A processor. DETAILED DESCRIPTION

[0010] In order to explain the technical content, achieved objectives and effects of the present invention in detail, the following is an explanation in combination with the implementation modes and the accompanying drawings.

[0011] Please refer to Figure 1 , a data reset and restoration method, comprising the steps of: S1. Monitor the hijacking event of the target data, and if the hijacking event occurs, obtain a preset reset strategy from the cloud; S2. Generate an independent memory area according to the preset reset strategy, and store the target data before being hijacked in the independent memory area; S3. Point the calling relationship of the target data to the independent memory area.

[0012] It is understandable that the above target data may refer to data that is critical to the normal operation of the system, such as functions in programs, API interfaces, data in DLL files, sensitive information of users, or key data blocks in memory. Once these data are tampered with or hijacked, they may cause serious consequences such as system crash, data leakage, and functional failure. The system sets the corresponding data as target data according to the needs.

[0013] As can be seen from the above description, the beneficial effect of the present invention is that by monitoring the hijacking event of the target data, it is ensured that the recovery process can be automatically triggered when the data is tampered or hijacked. If a hijacking event is detected, the system can obtain the preset reset strategy from the cloud, generate an independent memory area, and store the target data before the hijacking in the area, thereby ensuring the integrity and accuracy of data recovery. Compared with traditional self-verification technologies such as checksums and CRC, this method no longer relies on static data and complex multi-threading technologies for memory expansion and comparison, but performs real-time recovery through dynamic cloud strategies. This not only simplifies the data protection process, but also avoids the waste of resources and inefficiency caused by static data verification. At the same time, the method does not need to constantly compare local and remote data, which greatly improves the efficiency of data recovery and reduces the possibility of false alarms and false positives. Ultimately, the user experience is optimized, computing resources are saved, and the data recovery process is more intelligent and automated.

[0014] In an embodiment of the present invention, the step S3 further includes a step S4: Compare the data features of the target data with those of the target data in the independent memory area, and if there is a difference, control the cloud to overwrite the original target data with the target data stored in the independent memory area.

[0015] From the above description, it can be seen that the step of comparing the target data with the target data in the independent memory area has been added. This improvement significantly enhances the accuracy and reliability of data recovery. By comparing the data characteristics of the two, if differences are found, the system will control the cloud to overwrite the original target data with the data stored in the independent memory area, thereby ensuring that the recovered data is consistent with the original data. This process not only improves the accuracy of data reset, but also solves the problem of resource waste in traditional methods that rely on multiple technologies and perform data comparison step by step. Through dynamic comparison and automatic overwriting, the system can repair the target data according to actual conditions, thereby ensuring that there are no errors or incomplete recovery during the data recovery process. Compared with the traditional method that requires manual intervention and static comparison, this method achieves more efficient and accurate data recovery through automated cloud policy adjustment, reduces the complexity of operations, and improves user experience and data security.

[0016] In an embodiment of the present invention, the step S4 further includes a step S5: After the target data is restored, the calling status and integrity of the target data are continuously monitored. If a new hijacking event is detected, steps S1 to S3 are re-executed, and the preset reset strategy is adjusted according to the new hijacking event; If no hijacking event is detected, the target data is regularly checked for integrity to ensure that the target data has not been tampered with.

[0017] From the above description, it can be seen that by monitoring the call status and integrity of the target data, the system can detect in real time whether there are new hijacking events, which is crucial to improving the dynamic adaptability of the data recovery system. If a new hijacking event is detected, the system will re-execute steps S1 to S3 and re-obtain the updated reset strategy from the cloud to ensure that data recovery can adapt to new security threats and repair them in a timely manner. In the absence of new hijacking events, the system will regularly perform integrity checks on the target data to ensure that the data has not been tampered with. This step effectively enhances the long-term effectiveness of data protection, avoids secondary damage caused by potential threats after data recovery, and ensures that the target data is always in the safest and most up-to-date state. Compared with the periodic checks of traditional methods, this method can actively respond to changes in the external environment, avoid security vulnerabilities caused by the system ignoring dynamic changes, and provide a more comprehensive and intelligent data protection solution.

[0018] In an embodiment of the present invention, step S3 further includes the steps of: Modify the calling relationship of the target data to a private call to ensure that the target data is only called by the current program to prevent hijacking or tampering by other programs.

[0019] From the above description, it can be seen that the step of modifying the calling relationship of the target data to a private call is added. This measure effectively enhances the isolation and security of the data. Private calls ensure that the target data can only be called by the current program, and other programs cannot hijack or tamper with the target data, thereby preventing malicious programs or external software from hijacking data by modifying the calling path. This measure can significantly improve the anti-tampering ability of the target data, so that the data can continue to maintain independence after recovery without being interfered by external factors. Compared with traditional methods that rely on external protection mechanisms or static protection measures, the implementation of private calls further enhances the security of data after recovery. Through this isolation mechanism, not only the integrity and stability of the data after recovery are improved, but also mutual interference between programs can be prevented, reducing the risks that may occur when the system is running in a high-security environment, and ultimately improving the user's security and operating experience.

[0020] In an embodiment of the present invention, the preset reset strategy is used to detect the type of the target data, and select to reset, partially reset or stop resetting the target data according to the type.

[0021] From the above description, it can be seen that by adding the detection of the target data type to the data reset and restoration method, and selecting different reset strategies (such as full reset, partial reset or stop reset) according to the type, the flexibility and adaptability of the data recovery process are effectively improved. The preset reset strategy can select the most appropriate recovery method according to the specific type of target data (such as sensitive data, ordinary data, etc.), thereby avoiding a comprehensive reset of unnecessary data, saving computing resources and improving processing efficiency. In addition, for specific types of data, a partial reset method can be adopted to only restore part of the data that needs to be repaired, thereby further optimizing the data recovery process. Compared with the traditional unified reset method, the present invention can be flexibly adjusted according to different situations, reducing unnecessary operations and resource waste. This intelligent strategy selection not only improves the performance of the system, but also enhances the user's control over the data recovery process, and ultimately achieves more efficient and accurate dynamic data protection.

[0022] Please refer to Figure 2 A data reset and restoration terminal 1 includes a memory 2, a processor 3, and a computer program stored in the memory 2 and executable on the processor 3. When the processor 3 executes the computer program, the steps in the data recharge and restoration method are completed. That is, a carrier for executing the above method is provided, and data reset and restoration are performed when the above method is executed.

[0023] The present invention provides a data resetting and restoring method and terminal, which are mainly used to simplify the process of data self-checking, and are specifically described below in conjunction with embodiments.

[0024] Please refer to Figure 1 , Embodiment 1 of the present invention is: A data reset and restoration method comprises the steps of: S1. Monitor the hijacking of target data. If a hijacking occurs, obtain a preset reset strategy from the cloud. S2. Generate an independent memory area according to a preset reset strategy, and store the target data before hijacking in the independent memory area; S3. Point the calling relationship of the target data to an independent memory area.

[0025] The target data is the function in the program, API interface, data in DLL file, sensitive information of the user, or key data block in memory, and the system is set according to individual needs. The hijacking environment is a port with processing capability such as client or mobile terminal.

[0026] The preset reset strategy is used to detect the type of target data and select to reset, partially reset or stop resetting the target data according to the type.

[0027] That is, in this embodiment, by monitoring the hijacking of the target data, it is ensured that the recovery process can be automatically triggered when the data is tampered or hijacked. If a hijacking event is detected, the system can obtain a preset reset strategy from the cloud, generate an independent memory area, and store the target data before the hijacking in the area, thereby ensuring the integrity and accuracy of data recovery.

[0028] Embodiment 2 of the present invention is: Based on the first embodiment, step S3 further includes step S4: Compare the data features of the target data and the target data in the independent memory area. If there is a difference, the cloud will be controlled to overwrite the original target data with the target data stored in the independent memory area. By comparing the data features of the two, if a difference is found, the system will control the cloud to overwrite the original target data with the data stored in the independent memory area, thereby ensuring that the restored data is consistent with the original data. This process not only improves the accuracy of data reset, but also solves the problem of resource waste in traditional methods that rely on multiple technologies and conduct data comparison step by step.

[0029] Step S4 is followed by step S5: S5. After the target data is restored, the call status and integrity of the target data are continuously monitored. If a new hijacking event is detected, steps S1 to S3 are re-executed, and the preset reset strategy is adjusted according to the new hijacking event. If no hijacking event is detected, the target data is regularly checked for integrity to ensure that the target data has not been tampered with. By monitoring the call status and integrity of the target data, the system can detect in real time whether there are new hijacking events, which is crucial to improving the dynamic adaptability of the data recovery system. If a new hijacking event is detected, the system will re-execute steps S1 to S3 and re-obtain an updated reset strategy from the cloud to ensure that data recovery can adapt to new security threats and repair them in a timely manner. In the absence of new hijacking events, the system will regularly check the integrity of the target data to ensure that the data has not been tampered with.

[0030] Embodiment 3 of the present invention is: Based on the first embodiment, step S3 further includes the following steps: Modify the calling relationship of the target data to a private call to ensure that the target data is only called by the current program to prevent other programs from hijacking or tampering with it. Private calls ensure that the target data can only be called by the current program, and other programs cannot hijack or tamper with the target data, thereby preventing malicious programs or external software from hijacking data by modifying the calling path.

[0031] Embodiment 4 of the present invention is: A data reset and restoration method, specifically applied as follows: 1. Monitor the state of the target function or data Check the current status of each key function or data in the system to ensure that they have not been tampered with or hijacked. The system will check the integrity of the target data (such as API functions in DLL) or data (such as certain important variables) regularly or in real time. At this time, the system will compare the current state of the function or data with the original version, usually through hash verification, signature verification or version number comparison to determine whether they have changed. For example, there is an API function CALLTEST, whose original version is known. The system will verify the current state of this function through the hash value to see if it has been tampered with.

[0032] 2. Determine whether a reset is required Determine whether the target data or function needs to be reset based on the monitoring results. If the current version of the target function or data is found to be different from the preset original version, it means that the function or data may have been tampered with or hijacked. The system decides whether to start the reset process based on these differences. If no tampering is detected, no changes are required and the system will continue to operate normally. For example, if the hash value of CALLTEST does not match, the system will determine that it may have been tampered with and therefore needs to be reset.

[0033] 3. Get the reset policy from the cloud Get the appropriate reset strategy through the cloud. The cloud will generate a reset strategy based on the current system version, status, and security requirements. This strategy will determine how to restore the target function or data, whether it needs to be fully reset, partially reset, or whether only certain specific data parts need to be replaced. The reset strategy can be dynamically adjusted according to different environments or security requirements. For example, based on the system version and configuration of the CALLTEST function and the security rules of the cloud, it is determined whether the entire function needs to be completely replaced or only the tampered part needs to be repaired.

[0034] 4. Allocate a new memory area for reset Assign a new, isolated memory area to the target data or data to avoid conflicts with the original memory area and protect the target data from external interference. According to the reset strategy of the cloud, the system creates a new memory area for the target data or data. This new memory area is independent and does not overlap with the memory areas of other programs. The new memory area will store the reset data or function, ensuring that the original memory area will not be interfered with and will not affect the normal operation of other programs. For example, the system assigns a new memory address to CALLTEST, and the new memory stores the reset, normal version of the CALLTEST function.

[0035] 5. Point to the new memory area Point the target data or data calls to the newly allocated memory area to ensure that the function resumes normal operation without external interference. Once the new memory area is allocated and contains the reset data or function, the system will update the call path pointing to the target data or data so that all calls to the function point to the new memory area. This process ensures that even if the original memory area is tampered with, the caller can still use the reset data or function normally. For example, in the program, all calls to CALLTEST will be redirected to the new memory area, and even if other programs (such as security software or malware) may still access the original memory location through hijacking, the normal function of CALLTEST will not be affected.

[0036] 6. Ensure private calls do not affect other programs By setting the reset function or data as a private call, it is ensured that it is not affected by other programs and avoids being hijacked. The system sets the new memory area as private memory and only allows the current program to access it. In this way, although other programs (such as security software or malware) can still try to hijack the original public function, they cannot modify or interfere with the reset version of the function in the new memory. The current program can safely call the reset function without worrying about external interference. For example, the new memory area of ​​CALLTEST is set as private memory, and only the current program can access and call it. Even if other programs hijack CALLTEST in the original memory area, they cannot affect the current program's call to CALLTEST in the new memory.

[0037] Please refer to Figure 2 , Embodiment 5 of the present invention is: A data reset and restoration terminal 1 includes a memory 2, a processor 3, and a computer program stored in the memory 2 and executable on the processor 3. When the processor 3 executes the computer program, the steps in any one of the data reset and restoration methods in embodiments 1 to 4 are completed.

[0038] The above descriptions are merely embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent transformations made using the contents of the present invention's specification and drawings, or directly or indirectly applied in related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A data reset and restoration method, characterized in that: Includes steps: S1. Monitor the hijacking event of the target data, and if the hijacking event occurs, obtain a preset reset strategy from the cloud; S2. Generate an independent memory area according to the preset reset strategy, and store the target data before being hijacked in the independent memory area; S3. Point the calling relationship of the target data to the independent memory area.

2. A data reset and restoration method according to claim 1, characterized in that: The step S3 further includes a step S4: Compare the data features of the target data with those of the target data in the independent memory area, and if there is a difference, control the cloud to overwrite the original target data with the target data stored in the independent memory area.

3. A data reset and restoration method according to claim 2, characterized in that: The step S4 further includes a step S5: After the target data is restored, the calling status and integrity of the target data are continuously monitored. If a new hijacking event is detected, steps S1 to S3 are re-executed, and the preset reset strategy is adjusted according to the new hijacking event; If no hijacking event is detected, the target data is regularly checked for integrity to ensure that the target data has not been tampered with.

4. A data reset and restoration method according to claim 1, characterized in that: The step S3 further comprises the steps of: Modify the calling relationship of the target data to a private call to ensure that the target data is only called by the current program to prevent hijacking or tampering by other programs.

5. A data reset and restoration method according to claim 1, characterized in that: The preset reset strategy is used to detect the type of the target data, and select to reset, partially reset or stop resetting the target data according to the type.

6. A data reset and restoration terminal, characterized in that: The invention comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the following steps are performed: S1. Monitor the hijacking event of the target data, and if the hijacking event occurs, obtain a preset reset strategy from the cloud; S2. Generate an independent memory area according to the preset reset strategy, and store the target data before being hijacked in the independent memory area; S3. Point the calling relationship of the target data to the independent memory area.

7. A data reset and restoration terminal according to claim 6, characterized in that: The step S3 further includes a step S4: Compare the data features of the target data with those of the target data in the independent memory area, and if there is a difference, control the cloud to overwrite the original target data with the target data stored in the independent memory area.

8. The data reset and restoration terminal according to claim 7, characterized in that: The step S4 further includes a step S5: After the target data is restored, the calling status and integrity of the target data are continuously monitored. If a new hijacking event is detected, steps S1 to S3 are re-executed, and the preset reset strategy is adjusted according to the new hijacking event; If no hijacking event is detected, the target data is regularly checked for integrity to ensure that the target data has not been tampered with.

9. The data reset and restoration terminal according to claim 6, characterized in that: The step S3 further comprises the steps of: Modify the calling relationship of the target data to a private call to ensure that the target data is only called by the current program to prevent hijacking or tampering by other programs.

10. The data reset and restoration terminal according to claim 6, characterized in that: The preset reset strategy is used to detect the type of the target data, and select to reset, partially reset or stop resetting the target data according to the type.

Images