Data checking system, method, device, medium and product

Abstract

The application provides a data verification system, method, device, medium and product, the system comprises: a script management module for obtaining a script to be verified; an engine pool module for determining the script engine corresponding to the script to be verified; a secure sandbox module for isolating the access rights of the script to be verified according to a preset permission policy; a data binding module for binding the data to be verified to the script execution context of the script to be verified; and a verification execution module for executing verification on the script to be verified and the corresponding script execution context through the script engine to obtain the result of data verification. The script to be verified can be obtained at runtime, the verification logic is executed by selecting the script engine, the script access rights are isolated through the secure sandbox, and the data to be verified is bound to the script context for verification, thereby realizing unified management and efficient processing of different data types and verification rules, and significantly improving the flexibility, execution efficiency and security of the system.

Description

Technical Field

[0001] This invention relates to the field of computers, and more particularly to a data verification system, method, device, medium, and product. Background Technology

[0002] As enterprise information systems continue to expand, the types and structures of various business data become increasingly complex. In order to maintain the operation of the information system, it is necessary to verify the business data.

[0003] However, traditional data validation methods generally embed validation rules into the product's backend code. Every time the rules are modified, they need to be redeveloped, compiled, and released, resulting in high maintenance costs and poor flexibility. Such validation methods cannot adapt to frequently changing business strategies. Summary of the Invention

[0004] This invention addresses the problem that existing data verification methods cannot adapt to frequently changing business strategies, and proposes a data verification system, method, device, medium, and product.

[0005] In a first aspect, the present invention provides a data verification system, the system comprising: The script management module is used to obtain the scripts to be verified. The engine pool module is used to determine the script engine corresponding to the script to be verified. The security sandbox module is used to isolate the access permissions of the script to be verified in the system according to a preset permission policy. The data binding module is used to bind the data to be verified to the script execution context of the script to be verified; The verification execution module is used to perform verification on the script to be verified and the corresponding script execution context through the script engine, and obtain the data verification result.

[0006] Preferably, the script management module is also used to perform one or more of the following: updating, storing, syntax checking, and security analysis of the script to be verified.

[0007] Preferably, the engine pool module includes multiple script engines; The engine pool module is also used to determine a matching script engine from the plurality of script engines based on the performance parameters of the script to be verified, and use it as the script engine corresponding to the script to be verified. Preferably, the engine pool module is also used to schedule the script to be verified from the script engine corresponding to the script to be verified to the remaining script engines among the plurality of script engines through a hot switching mechanism. Preferably, the engine pool module is also used to reuse any one or more of the plurality of script engines.

[0008] Preferably, the permission policy includes one or more of Java class permissions, method permissions, and system resource permissions.

[0009] Preferably, the data to be verified includes any one or more of JSON, XML, and Java object formats; The data binding module is also used to map the data to be verified through a data mapping table, so that the data format of the data to be verified corresponds to the data format of the script execution context; Preferably, the data binding module is further configured to expand the data to be verified using an object graph.

[0010] Preferably, the verification execution module is further configured to perform verification on the script to be verified and the corresponding script execution context through a transaction mechanism; Preferably, the verification execution module is also used to record any exceptions that occur during the verification process; Preferably, the verification execution module is further configured to synchronously or asynchronously execute the verification of at least one set of the scripts to be verified and their corresponding script execution contexts.

[0011] Secondly, the present invention provides a data verification method, the method comprising: Obtain the script to be verified; Determine the script engine corresponding to the script to be verified; Access permissions to the script to be verified are isolated according to a preset permission policy; Bind the data to be verified to the script execution context of the script to be verified; The script engine performs verification on the script to be verified and its corresponding script execution context to obtain the data verification result.

[0012] Thirdly, the present invention provides an electronic device comprising a processor and a memory, wherein the memory stores at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by the processor to implement the data verification method as described in the second aspect.

[0013] Fourthly, the present invention provides a computer-readable storage medium storing at least one instruction or at least one program, wherein the at least one instruction or at least one program is loaded and executed by a processor to implement the data verification method as described in the second aspect.

[0014] Fifthly, the present invention provides a computer program product, including a computer program that, when executed by a processor, implements the data verification method as described in the second aspect.

[0015] The data verification system, method, device, medium, and product provided by this invention have the following technical effects: By combining a script management module, an engine pool module, a security sandbox module, a data binding module, and a verification execution module, a flexible and efficient data verification system is achieved. It can obtain the script to be verified at runtime, select and execute the verification logic with the script engine, isolate script access permissions through the security sandbox, and bind the data to be verified to the script context for verification. This enables unified management and efficient processing of different data types and verification rules, significantly improving the system's flexibility, execution efficiency, and security.

[0016] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the invention. Attached Figure Description

[0017] The accompanying drawings, which form part of this specification, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an undue limitation of the invention. In the drawings: Figure 1 A structural diagram of a data verification system provided as an exemplary embodiment of the present invention; Figure 2 A flowchart of a data verification method provided as an exemplary embodiment of the present invention; Figure 3 This is a structural diagram of an electronic device provided as an exemplary embodiment of the present invention.

[0018] Figure labeling: Script management module 11, Engine pool module 12, Security sandbox module 13, Data binding module 14, Verification execution module 15, Electronic device 300, Central processing unit 310, Storage medium 320, Memory 330, Application program 323, Data 322, Operating system 321, Input / output interface 340, Wireless network interface 350, Power supply 360. Detailed Implementation

[0019] The present invention will now be described in detail with reference to the accompanying drawings and embodiments. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0020] The following detailed description is exemplary and intended to provide further detailed explanation of the invention. Unless otherwise specified, all technical terms used in this invention have the same meaning as commonly understood by one of ordinary skill in the art. The terminology used in this invention is for describing particular embodiments only and is not intended to limit the scope of exemplary embodiments according to the invention.

[0021] Currently, the following methods are mainly used for data verification during application: First, annotation-based validation: using the JSR-303 Bean Validation specification (a standardized data validation specification in the Java domain), validation rules are defined through annotations.

[0022] Second, third-party validation: Use third-party libraries such as Apache Commons Validator (an early general-purpose validation library), Hibernate Validator (an official reference implementation of JSR-303 / JSR-380), and Spring (a wrapper and extension based on Bean Validation) for validation.

[0023] Third, hard-coded validation: Developers write a large amount of validation logic directly in the business code based on known business rules, and then compile and release it with the product.

[0024] Fourth, configuration file validation: Configure validation rules through XML (Extensible Markup Language) or properties (key-value pair configuration file format) files.

[0025] However, these data verification methods have the following problems: First, it lacks flexibility: the validation rules need to be predefined, and users cannot dynamically modify or add custom rules according to real-time needs. This results in poor system scalability.

[0026] Second, development efficiency is low: any minor change to business rules requires modifying the source code, recompiling, testing, and deploying the entire system, making it impossible to achieve dynamic updates at runtime, which increases development and maintenance costs.

[0027] Third, high maintenance costs: As business rules become more complex and diverse, the code will be filled with a large amount of validation code that is difficult to maintain and understand, violating the open / closed principle.

[0028] Fourth, functional limitations: Existing validation libraries struggle to support complex logic (such as cross-field dependencies and dynamic data source validation) and cannot leverage the rich ecosystem of JavaScript.

[0029] Fifth, security risks: Directly executing user scripts may introduce security vulnerabilities, such as code injection or malicious attacks, and existing technologies lack effective security control mechanisms.

[0030] Based on this, an exemplary embodiment of the present invention provides a data verification system. The data verification system provided in this embodiment of the present invention is preferably applied to the JAVA framework, but is not limited thereto, and the specific application may be selected according to the actual situation.

[0031] See Figure 1 The system includes the following modules, which sequentially compile and verify the script to be verified. Specifically: Script management module 11 is used to obtain the script to be verified.

[0032] The script to be verified is generated by the administrator according to the verification requirements, and can be obtained from multiple channels such as script repository, configuration center or user interface.

[0033] In one embodiment, the script management module 11 is further configured to perform one or more of the following: updating, storing, syntax checking, and security analysis of the script to be verified. Specifically: Updating the script to be verified includes: for existing scripts to be verified, when the administrator releases a new version of the script to be verified, incremental modifications or version replacements are made to the existing scripts to be verified according to the new version.

[0034] Storing the scripts to be verified includes storing them in the corresponding database. To facilitate updates, the scripts can be indexed by version number. Older versions of the scripts can be saved or deleted from the database, depending on the administrator's configuration.

[0035] Syntax checks on the script to be validated include: performing syntax validity checks on the obtained script using a script syntax parser to avoid runtime errors.

[0036] Security analysis of the script to be verified includes analyzing the script content to check for sensitive calls, unauthorized access, or potentially risky operations.

[0037] Engine pool module 12 is used to determine the script engine corresponding to the script to be verified.

[0038] The script engine parses the syntax of the script to be validated and executes it line by line during runtime. During execution, the script engine performs logical judgments based on the data to be validated and the script execution context to validate the data. Script engines typically support multiple scripting languages ​​such as JavaScript, Groovy, and Python, and the appropriate runtime environment can be selected based on performance or compatibility requirements. The script engines provided in this embodiment include, but are not limited to, the Nashorn engine, the GraalVM JavaScript engine, and other compliant script engines; the specific engine can be selected based on actual needs. Different engines have different performance characteristics, memory models, and execution speeds.

[0039] In one embodiment, the engine pool module 12 includes multiple script engines.

[0040] In an optional implementation, the engine pool module 12 is further configured to determine a matching script engine from multiple script engines based on the performance parameters of the script to be verified, and use it as the script engine corresponding to the script to be verified.

[0041] The performance parameters include, but are not limited to, execution time, complexity, and resource consumption. The engine pool module 12 can determine the matching script engine based on the performance parameters of the script to be verified. For example, GraalVM JavaScript is selected for scripts with higher complexity, which has higher performance; while Nashorn engine is selected for scripts with lower complexity, which has faster startup speed.

[0042] In an optional implementation, the engine pool module 12 is further configured to schedule the script to be verified from the script engine corresponding to the script to be verified to the remaining script engines among multiple script engines through a hot-switching mechanism.

[0043] The hot-switching mechanism refers to switching between multiple script engines without stopping the system. For example, when the script engine corresponding to the script to be verified is overloaded, the script is scheduled to be executed on one of the remaining script engines.

[0044] In an alternative implementation, the engine pool module 12 is also used to reuse any one or more of the multiple script engines.

[0045] The reused engine needs to meet the following conditions: maintaining a no-business state internally, isolating data through a new script context each time it is executed, and returning the engine to the engine pool module 12 after execution. Through engine pools and reuse technology, the creation overhead of engines can be significantly reduced, improving the system's concurrency performance.

[0046] The security sandbox module 13 is used to isolate the access permissions of the script to be verified according to the preset permission policy.

[0047] The permission policy is used to isolate the access scope of scripts in the system. The security sandbox module 13 can use a custom class loader, permission manager and static analyzer to isolate the execution environment of the script to be verified from other resources of the system, so as to ensure that the execution of the script does not pose a security threat to the system.

[0048] In one embodiment, the security sandbox module 13 provides fine-grained access control and supports method-level access restrictions.

[0049] In one embodiment, the permission policy includes one or more of Java class permissions, method permissions, and system resource permissions. Specifically: Java class permissions: Only allow the script to be verified to access classes in the whitelist.

[0050] Method permissions: The script to be verified can only call whitelisted methods, such as methods in utility classes.

[0051] System resource permissions only allow the script to be verified to perform specific file read / write, specific network access, or specific thread operations.

[0052] The data binding module 14 is used to bind the data to be verified to the script execution context of the script to be verified.

[0053] The script execution context refers to the runtime environment accessible to the script being verified during execution, including a set of variables, method interfaces, system resources, and environment parameters related to the current verification task. The script execution context provides the script with necessary input information, enabling it to perform logical judgments, data processing, or verification operations based on the attributes within the context. The data to be verified is the data that needs to be validated by the script's logic, including but not limited to JSON data, XML data, and Java objects. This data can be provided by external systems, by the administrator, or generated internally by the system.

[0054] In one embodiment, the data binding module 14 is further configured to map the data to be verified through a data mapping table, so that the data format of the data to be verified corresponds to the data format of the script execution context.

[0055] Specifically, the data to be verified varies in format depending on its source, including but not limited to JSON, XML, and Java objects. The data mapping table includes mappings between different data formats and the data formats of the script execution context, converting the data to be verified into a format accessible to the script being verified.

[0056] In one embodiment, the data binding module 14 is also used to expand the data to be verified through an object graph.

[0057] Among them, object graph expansion refers to fully expanding the hierarchical and referential relationships of the data to be verified into a processable form, including expanding complex data structures such as nested objects and collection objects, so that the script to be verified can directly access the deep attributes of the data to be verified.

[0058] In one embodiment, the code for the data binding module 14 can be seen in the following example: Bindings bindings = engine.createBindings(); bindings.put("data", validateData); bindings.put("result",new ValidationResult()).

[0059] The verification execution module 15 is used to perform verification on the script to be verified and the corresponding script execution context through the script engine, and obtain the data verification result.

[0060] In one embodiment, the verification execution module 15 is further configured to perform verification on the script to be verified and the corresponding script execution context through a transaction mechanism.

[0061] The transaction mechanism involves creating a transaction boundary before the verification script is executed. If the script encounters an error, a rollback is performed to ensure the atomicity and consistency of data verification. For example, when batch-verifying multiple data sets, the transaction boundary is set to the state before verification. If the verification fails midway, the process can be rolled back to the state before verification, preventing inconsistencies caused by partial successful verification. Modified states can be automatically reverted if an error occurs during verification or script execution.

[0062] In one embodiment, the verification execution module 15 is also used to record any exceptions that occur during the verification process.

[0063] The recorded content includes, but is not limited to, exception type, exception stack trace, and exception execution context information, and is stored as a log for administrators to review.

[0064] In one embodiment, the verification execution module 15 is further configured to synchronously or asynchronously execute the verification of at least one set of scripts to be verified and their corresponding script execution contexts.

[0065] Synchronous execution executes the script sequentially using a single thread, while asynchronous execution executes it in batches using multiple threads, thus improving throughput.

[0066] The data verification system provided in this embodiment has the following technical effects: First, through the script management module 11, users can dynamically add, modify, or delete verification rules at runtime without modifying the underlying code, thereby supporting real-time verification needs for multiple scenarios and strategies, and significantly improving the system's scalability and adaptability.

[0067] Secondly, the system supports real-time script loading, syntax checking, and security analysis. Validation rules can be applied without recompiling and deploying the entire application, greatly shortening the development cycle for business rule changes and reducing development and testing costs.

[0068] Third, the verification logic is centrally managed in the script to be verified and executed uniformly through the data binding module 14 and the script execution module, avoiding a large amount of verification logic embedded in business code, so that the system follows the open / closed principle and is easy to understand, maintain and iterate.

[0069] Fourth, through engine pool module 12 and script context binding, the system can handle complex validation logic, including cross-field dependencies and dynamic data source validation, thereby expanding the functional scope that traditional validation libraries cannot cover.

[0070] Fifth, the security sandbox module 13 and fine-grained access control can restrict the access scope of the script to be verified, preventing code injection and malicious operations. Combined with class loader isolation and permission whitelist mechanisms, it ensures that script execution occurs in a controlled environment, significantly reducing security risks.

[0071] An exemplary embodiment of the present invention provides a data verification method, see below. Figure 2 The methods include: S201. Obtain the script to be verified.

[0072] S202. Determine the script engine corresponding to the script to be verified; S203. Isolate the access permissions of the script to be verified according to the preset permission policy.

[0073] S204. Bind the data to be verified to the script execution context of the script to be verified; S205. The script engine performs verification on the script to be verified and the corresponding script execution context to obtain the data verification result.

[0074] In one embodiment, step S201 is followed by: Update, store, perform syntax checks, and perform security analysis on the script to be verified.

[0075] In one embodiment, the engine pool module includes multiple script engines.

[0076] Step S202 further includes: determining a matching script engine from multiple script engines based on the performance parameters of the script to be verified, and using it as the script engine corresponding to the script to be verified.

[0077] In one embodiment, step S202 further includes: scheduling the script to be verified from the script engine corresponding to the script to be verified to the remaining script engine among multiple script engines through a hot-switching mechanism.

[0078] In one embodiment, step S202 further includes reusing any one or more of the multiple script engines.

[0079] In one embodiment, the permission policy includes one or more of Java class permissions, method permissions, and system resource permissions.

[0080] In one embodiment, the data to be verified includes any one or more of JSON, XML, and Java object formats.

[0081] Step S204 further includes: mapping the data to be verified through a data mapping table so that the data format of the data to be verified corresponds to the data format of the script execution context.

[0082] In one embodiment, step S204 further includes: expanding the data to be verified using an object graph.

[0083] In one embodiment, step S205 further includes: performing verification on the script to be verified and the corresponding script execution context through a transaction mechanism.

[0084] In one embodiment, step S205 further includes: recording any exceptions that occur during the verification process.

[0085] In one embodiment, step S205 further includes: synchronously or asynchronously executing the verification of at least one set of scripts to be verified and their corresponding script execution contexts.

[0086] An exemplary embodiment of the present invention also provides an electronic device, see below. Figure 3The electronic device 300 can vary significantly due to differences in configuration or performance. It may include one or more central processing units (CPUs) 310 (CPUs 310 may include, but are not limited to, microprocessors (MCUs) or programmable logic devices (FPGAs), a memory 330 for storing data, and one or more storage media 320 (e.g., one or more mass storage devices) for storing application programs 323 or data 322. The memory 330 and storage media 320 may be temporary or persistent storage. The storage media 320 stores at least one instruction, at least one program, code set, or instruction set, which is loaded and executed by the processor to implement the aforementioned data verification method.

[0087] Furthermore, the central processing unit 310 can be configured to communicate with the storage medium 320 and execute a series of instructions stored in the storage medium 320 on the electronic device 300. The electronic device 300 may also include one or more power supplies 360, one or more wired or wireless network interfaces 350, one or more input / output interfaces 340, and / or one or more operating systems 321, such as Windows Server™, MacOSX™, Unix™, Linux™, FreeBSD™, etc.

[0088] The input / output interface 340 can be used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the electronic device 300. In one example, the input / output interface 340 includes a network interface controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the input / output interface 340 may be a radio frequency (RF) module used for wireless communication with the Internet.

[0089] Those skilled in the art will understand that Figure 3 The structure shown is for illustrative purposes only and does not limit the structure of the electronic device described above. For example, the electronic device 300 may also include... Figure 3 The more or fewer components shown, or having the same Figure 3 The different configurations shown.

[0090] Embodiments of the present invention also provide a computer-readable storage medium, which can be disposed in a server to store at least one instruction, at least one program, code set, or instruction set related to implementing a data verification method in the embodiments of the data verification method. The at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the above-described data verification method.

[0091] Optionally, in this embodiment, the storage medium may be located at at least one of the multiple network servers in a computer network. Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0092] Embodiments of the present invention also provide a computer program product, including a computer program that, when executed by a processor, implements the above-described data verification method.

[0093] The program code for executing the computer program product disclosed herein can be written in any combination of one or more programming languages. The program code can be executed entirely on a user device, partially on a user device, as a stand-alone software package, partially on a user device and partially on a remote device, or entirely on a remote device.

[0094] As is known from common technical knowledge, this invention can be implemented through other embodiments that do not depart from its spirit or essential characteristics. Therefore, the disclosed embodiments described above are merely illustrative in all respects and are not the only ones. All modifications within the scope of this invention or its equivalents are included in this invention.

[0095] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0096] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0097] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0098] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0099] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that modifications or equivalent substitutions can still be made to the specific implementation of the present invention. Any modifications or equivalent substitutions that do not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A data verification system, characterized in that, The system includes: The script management module is used to obtain the scripts to be verified. The engine pool module is used to determine the script engine corresponding to the script to be verified. The security sandbox module is used to isolate the access permissions of the script to be verified in the system according to a preset permission policy; The data binding module is used to bind the data to be verified to the script execution context of the script to be verified; The verification execution module is used to perform verification on the script to be verified and the corresponding script execution context through the script engine, and obtain the data verification result.

2. The data verification system as described in claim 1, characterized in that, The script management module is also used to perform one or more of the following: updating, storing, syntax checking, and security analysis of the script to be verified.

3. The data verification system as described in claim 1, characterized in that, The engine pool module includes multiple script engines; The engine pool module is also used to determine a matching script engine from the plurality of script engines based on the performance parameters of the script to be verified, and use it as the script engine corresponding to the script to be verified. And / or, the engine pool module is also used to schedule the script to be verified from the script engine corresponding to the script to be verified to the remaining script engine among the plurality of script engines through a hot switching mechanism; And / or, the engine pool module is also used to reuse any one or more of the plurality of script engines.

4. The data verification system as described in claim 1, characterized in that, The permission policy includes one or more of the following: Java class permissions, method permissions, and system resource permissions.

5. The data verification system as described in claim 1, characterized in that, The data to be verified includes any one or more of the following formats: JSON, XML, and Java object. The data binding module is also used to map the data to be verified through a data mapping table, so that the data format of the data to be verified corresponds to the data format of the script execution context; And / or, the data binding module is further configured to expand the data to be verified through an object graph.

6. The data verification system as described in claim 1, characterized in that, The verification execution module is also used to perform verification on the script to be verified and the corresponding script execution context through a transaction mechanism; And / or, the verification execution module is also used to record any exceptions that occur during the verification process; And / or, the verification execution module is further configured to synchronously or asynchronously execute the verification of at least one set of the scripts to be verified and their corresponding script execution contexts.

7. A data verification method, characterized in that, The method includes: Obtain the script to be verified; Determine the script engine corresponding to the script to be verified; Access permissions to the script to be verified are isolated according to a preset permission policy; Bind the data to be verified to the script execution context of the script to be verified; The script engine performs verification on the script to be verified and its corresponding script execution context to obtain the data verification result.

8. An electronic device, characterized in that, The electronic device includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, code set, or instruction set, and the at least one instruction, at least one program, code set, or instruction set is loaded and executed by the processor to implement the data verification method as described in claim 7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one instruction or at least one program, which is loaded and executed by a processor to implement the data verification method as described in claim 7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the data verification method as described in claim 7.

Images