Model encryption method and device, equipment and storage medium
By generating an encrypted model library in the modeling software and flexibly selecting the loading method, the convenience and compatibility of the model data protection method are solved, and efficient and secure protection of model data is achieved.
Patent Information
- Application Number
- CN202510409296.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-02
- Publication Date
- 2025-07-18
AI Technical Summary
The existing model data protection methods have limitations in terms of operational ease, compatibility and encryption strength, and are difficult to meet the high security needs of modern engineering design and scientific research.
After building a model in the modeling software, save it to the model library and generate an encrypted model library through a symmetric encryption algorithm. When importing, flexibly choose decryption loading or non-decryption loading to ensure the security and convenience of model data.
It realizes all-round protection of model data during storage and use, improves operational convenience, avoids the complexity and compatibility issues of traditional encryption tools, and ensures the confidentiality of model data.
Smart Images

Figure CN120337252A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of information security technology, and in particular, to a model encryption method, apparatus, device, and storage medium. Background Art
[0002] In today's digital age, modeling software has become an indispensable tool in engineering design, scientific research, industrial manufacturing, and many high-tech fields. Through modeling software, engineers and scientific researchers can efficiently build complex 3D models, conduct virtual simulation analysis, and generate relevant code, thereby optimizing design schemes, shortening the R & D cycle, reducing production costs, and improving the overall quality and reliability of projects.
[0003] However, with the wide application of modeling technology, the security issue of model data has gradually become the focus of industry attention. Model data usually contains an enterprise's core intellectual property rights, business secrets, and key technical details. Once leaked, it may cause huge economic losses and reputational damage to the enterprise. For example, in the aerospace field, the 3D model data of aircraft may involve advanced aerodynamic design and material technology; in the automotive manufacturing industry, automotive model data may contain unique powertrain design and appearance patents. The confidentiality of this data is of utmost importance.
[0004] Currently, traditional model data protection methods mainly include external encryption tools, file permission management, etc. Although external encryption tools can provide data protection to a certain extent, they often require users to manually encrypt and decrypt operations, and the process is relatively cumbersome, and it is easy to cause data loss or inability to use properly due to improper operations. In addition, the compatibility of these tools with modeling software is relatively poor, which may cause the software to run unstably or have compatibility errors. File permission management mainly relies on the permission settings of the operating system, and its encryption strength is relatively low, easy to be cracked, and cannot effectively prevent illegal access or data leakage by internal personnel.
[0005] In summary, the existing model data protection methods have many limitations in terms of operation convenience, compatibility, and encryption strength, and it is difficult to meet the high requirements for model data security protection in modern engineering design and scientific research. Therefore, there is an urgent need for a more efficient, convenient, and secure model encryption method that can achieve comprehensive protection of the constructed model and its automatically generated code, thereby effectively ensuring the security and confidentiality of model data. Summary of the Invention
[0006] In view of the above problems, this application provides a model encryption method, including the following content:
[0007] In a first aspect, this application provides a model encryption method, which includes:
[0008] Save the model built in the modeling software to the model library;
[0009] Export and encrypt the models in the model library to generate an encrypted model library;
[0010] When importing the models in the encrypted model library into the application, decrypt and load or not decrypt and load the imported encrypted models.
[0011] Optionally, the encrypting the models in the model library includes:
[0012] Encrypt the model library using a symmetric encryption algorithm.
[0013] Optionally, when decrypting and loading the imported encrypted models, the method further includes:
[0014] Decrypt the encrypted model library to restore and generate an unencrypted model library;
[0015] Based on the models in the unencrypted model library, view, modify, save, and reuse the internal structure of the models and the code corresponding to the generated models.
[0016] Optionally, when not decrypting and loading the imported encrypted models, the method further includes:
[0017] Instantiate and apply the models in the encrypted model library, and the internal implementation logic of the models cannot be viewed; for the code of the models in the encrypted model library, subsystem functions are allowed to be viewed, but the implementation logic cannot be viewed.
[0018] Optionally, when the model built in the modeling software is generated, the corresponding code is generated simultaneously.
[0019] In a second aspect, the present application provides a model encryption device, which includes:
[0020] A model construction module for constructing a model and saving the model built in the modeling software to the model library;
[0021] A model encryption configuration module for exporting and encrypting the models in the model library to generate an encrypted model library;
[0022] A model library management module for decrypting and loading or not decrypting and loading the imported encrypted model library;
[0023] A user interface providing interfaces for model export and password setting, as well as interfaces for model import, decryption selection, and password input.
[0024] Optionally, the model encryption configuration module is specifically used for:
[0025] Encrypt the model library using a symmetric encryption algorithm.
[0026] Optionally, the device further includes:
[0027] A code generation module, configured to generate corresponding code while the model built in the modeling software is being generated.
[0028] Optionally, the device further includes: a model decryption and loading module, configured to decrypt the encrypted model library and restore it to generate an unencrypted model library when decrypting and loading the imported encrypted model;
[0029] The model library management module is specifically configured to view, modify, save, and reuse the internal structure of the model and generate the code corresponding to the model based on the models in the unencrypted model library.
[0030] Optionally, when the model library management module does not decrypt and load the imported encrypted model, it instantiates and applies the models in the encrypted model library, and the internal implementation logic of the models cannot be viewed; for the code of the models in the encrypted model library, the subsystem functions are allowed to be viewed, but the implementation logic cannot be viewed.
[0031] In a third aspect, the present application provides a device, which includes a memory and a processor. The memory is used to store instructions or code, and the processor is used to execute the instructions or code so that the device executes the model encryption method described in any implementation manner of the foregoing first aspect.
[0032] In a fourth aspect, the present application provides a computer-readable storage medium, in which code is stored. When the code is run, the device running the code implements the model encryption method described in any implementation manner of the foregoing first aspect.
[0033] The present application provides a model encryption method. When executing the method, first save the model built in the modeling software to the model library, then export and encrypt the models in the model library to generate an encrypted model library, and finally, when importing and applying the models in the encrypted model library, decrypt and load or not decrypt and load the imported encrypted model. In this way, by saving the model to the model library and encrypting it to generate an encrypted model library, the risk of model data leakage during storage and use can be effectively prevented. Both the model itself and the code automatically generated based on the model are comprehensively encrypted to ensure the confidentiality of the model data. Description of the Drawings
[0034] To more clearly illustrate the technical solutions in this embodiment or the prior art, the following will briefly introduce the accompanying drawings required for the description of the embodiment or the prior art. Obviously, the accompanying drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.
[0035] Figure 1 It is a flowchart of a model encryption method provided by an embodiment of the present application;
[0036] Figure 2 It is a display schematic diagram of an unencrypted model provided by an embodiment of the present application;
[0037] Figure 3 It is a display schematic diagram of an encrypted model provided by an embodiment of the present application;
[0038] Figure 4 It is a structural schematic diagram of a model encryption device provided by an embodiment of the present application. Detailed implementation manners
[0039] As described in the background art of the present application, currently, traditional model data protection methods mainly include external encryption tools, file permission management, etc. Although external encryption tools can provide data protection to a certain extent, they often require users to manually perform encryption and decryption operations, with a relatively cumbersome process and are prone to data loss or abnormal use due to improper operations. In addition, the compatibility of these tools with modeling software is relatively poor, which may lead to unstable software operation or compatibility errors. File permission management mainly relies on the permission settings of the operating system, with relatively low encryption strength, being easily cracked, and unable to effectively prevent illegal access or data leakage by internal personnel.
[0040] To solve the above technical problems, an embodiment of the present application provides a model encryption method, which includes: saving the model constructed in the modeling software to the model library; exporting and encrypting the model in the model library to generate an encrypted model library; when importing the model in the encrypted model library into the application, decrypting and loading or not decrypting and loading the imported encrypted model.
[0041] In this way, by saving the model constructed in the modeling software to the model library and performing encryption processing to generate an encrypted model library, and at the same time flexibly selecting the method of decrypting and loading or not decrypting and loading when importing into the application, comprehensive protection of model data is achieved. This method not only effectively prevents the leakage risk of model data during storage and use, ensures the confidentiality and security of the data, but also greatly improves the convenience of operation, avoiding the problems of complex operation and poor compatibility of traditional encryption tools.
[0042] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the following will clearly and completely describe the technical solutions in the embodiments of this application with reference to the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are only a part rather than all of the embodiments of this application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in this application without creative efforts shall fall within the scope of protection of this application.
[0043] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data that have been authorized by the user or fully authorized by all parties. Moreover, the collection, use, and processing of relevant data need to comply with the relevant laws, regulations, and standards of the relevant countries and regions.
[0044] Figure 1 This is a flowchart of a model encryption method provided by an embodiment of this application. In combination with Figure 1 as shown, the model encryption method provided by the embodiments of this application may include:
[0045] S101. Save the model constructed in the modeling software to the model library.
[0046] First, the user uses the modeling software to create a model. This process is the stage where the user designs and constructs the model according to requirements, such as designing a mechanical part, a building structure, or an electronic circuit. During the model construction process, the modeling software will automatically generate code related to the model. These codes may be codes used to describe the geometric shape, attributes, logical relationships, etc. of the model. For example, in some software, the codes can define the dimensions, material properties, connection relationships, etc. of the model.
[0047] Since the encryption method mentioned in this application is implemented inside the modeling software. That is to say, the encryption process is embedded in the functions of the modeling software, rather than being completed by external tools or software. This encryption method can ensure that during the model construction process, the encryption operation can be seamlessly integrated with the modeling process. The encrypted model can prevent unauthorized access, copying, or modification, ensuring the security of the model data.
[0048] The constructed model and the automatically generated code are saved together. The model is saved in the model library in the form of a "subsystem model". A subsystem model means that the model is decomposed into smaller, manageable parts or modules. This saving method has the following advantages: Facilitating management: Subsystem models can be conveniently classified, retrieved, and updated; Enhancing security: By decomposing the model into subsystems, different parts can be encrypted and access-controlled more flexibly; Facilitating reuse: Subsystem models can be reused in other projects, improving design efficiency.
[0049] The above-mentioned implementation of encryption within the modeling software ensures the security of the model during the construction process. At the same time, saving the model in the form of subsystems in the model library facilitates management and reuse, and also improves the security and maintainability of the model.
[0050] S102. Export the model in the model library and perform encryption processing to generate an encrypted model library.
[0051] When the constructed model is saved in the model library, it is saved in an unencrypted form. That is to say, the model in the model library can be directly accessed and used in an unencrypted state. The advantage of this saving method is that it is convenient for internal development and use, but the disadvantage is that the security is relatively low, and it is easy to be accessed or tampered with by unauthorized personnel.
[0052] To improve the security of the model, it is necessary to export and encrypt the model in the model library to obtain an encrypted model library. The models in the encrypted model library are all encrypted. In one implementation manner of the embodiments of the present application, the process of encrypting the model uses a symmetric encryption algorithm to encrypt the model library. The characteristic of the symmetric encryption algorithm is that the same key is used for encryption and decryption. The advantage of this algorithm is that the encryption and decryption speeds are fast, and it is suitable for processing a large amount of data. Common symmetric encryption algorithms include AES (Advanced Encryption Standard), DES (Data Encryption Standard), etc. The encryption and decryption processes of the symmetric encryption algorithm are relatively simple, and the calculation efficiency is high, which is suitable for encrypting a large amount of data.
[0053] The above steps generate an encrypted model library by exporting and encrypting the models in the model library. By using a symmetric encryption algorithm to encrypt the model, the security of the model can be improved, and the security of the model during storage and sharing can be ensured. This encryption method is particularly suitable for scenarios that require high security and efficient processing, such as the model management involving high-value designs, trade secrets, and technical secrets.
[0054] S103. When importing the models in the encrypted model library into the application, decrypt and load or not decrypt and load the imported encrypted models.
[0055] The models in the encrypted model library are all models that have undergone encryption processing. When importing the models in the encrypted model library into an application, there are two processing methods: decrypt and load, that is, decrypt the imported encrypted model to restore it to an unencrypted state for further operations; do not decrypt and load, that is, directly use the encrypted model without decrypting. This method is usually used for instantiation applications during runtime without involving viewing or modifying the internal structure of the model.
[0056] When decrypting the model, the same key or the corresponding decryption algorithm used during encryption is required to decrypt the encrypted model library to restore and generate an unencrypted model library. The decrypted unencrypted model library can be used to view, modify, save, and reuse the model. The schematic diagram of the model structure after decryption is as Figure 2 shown, Figure 2 is the display schematic diagram of the unencrypted model provided by the embodiment of the present application. According to Figure 2 it can be known that after the model is decrypted, the internal logic and structure of the model can be viewed. In the unencrypted model library, users can perform the following operations:
[0057] View the detailed internal structure of the model, including geometric shapes, parameters, logical relationships, etc.; view the code related to the model, which may be used to describe the construction logic, attributes, etc. of the model; modify the model, such as adjusting dimensions, changing parameters, optimizing the design, etc.; save the modified model back to the model library for subsequent use; reuse some parts or the entire model in other projects to improve the design efficiency.
[0058] Without decrypting, the model in the encrypted model library can be directly instantiated and applied, but the internal implementation logic of the model cannot be viewed, which helps to protect the design details of the model. In addition, users can view the interfaces and function descriptions of the subsystem functions defined in the model, but cannot view the specific implementation logic of these functions. This limitation ensures that users can use the functions of the model normally but cannot obtain the core technical details of the model. As Figure 3 shown, Figure 3 is the display schematic diagram of the encrypted model provided by the embodiment of the present application. Without decrypting, the internal structure of the model is hidden and viewing the internal details of the model is not supported.
[0059] In the above steps, by decrypting and restoring to an unencrypted model library, users can view, modify, and reuse the model; while directly performing instantiation applications without decrypting can protect the internal implementation logic of the model and ensure the security of the model. This flexible processing method not only meets the needs of development and debugging but also ensures the security of the model during use.
[0060] The above are some specific implementations of a model encryption method provided in the embodiment of the present application. Based on this, the present application also provides a corresponding device. The device provided in the embodiment of the present application will be introduced from the perspective of functional modularization.
[0061] Figure 4 A schematic diagram of the structure of a model encryption device provided in an embodiment of the present application. Figure 4 As shown, the model encryption device 400 provided in the embodiment of the present application includes:
[0062] The model building module 410 is used to build a model and save the completed model in the modeling software to the model library.
[0063] This module is the original basic module of the modeling software, which supports the model construction. The model construction process is the same as the introduction in the above embodiment and will not be repeated here.
[0064] The model encryption configuration module 420 is used to export and encrypt the models in the model library to generate an encrypted model library.
[0065] The model encryption configuration module mainly includes the model encryption specific implementation module developed and integrated into the modeling software, and the model encryption configuration controls and windows of the software operation interface.
[0066] The specific implementation modules of model encryption include encryption module and key management module. The encryption module adopts symmetric encryption algorithm and is responsible for implementing specific encryption and decryption operations; the key management module is responsible for key generation and storage. The model encryption configuration controls and windows are integrated in the model library management interface. After completing the construction of the model library and the subsystem models in the library, users can directly export the encrypted model library and configure the password in the model library management interface to implement model encryption configuration.
[0067] The model library management module 430 is used to load the imported encrypted model library with or without decryption.
[0068] This module is based on the original model library management function module of the modeling software, and adds management functions for the encryption library, including exporting the encryption library interface, importing and loading the encryption library interface, and viewing and reusing the encryption library.
[0069] Export encryption library interface: The model library management interface of the modeling software adds an interface for exporting encryption libraries. After the model is built and saved to the model library, you can choose to export it into an encryption library, and a pop-up window will be provided for users to set the encryption library password. The underlying software uses a symmetric encryption algorithm to encrypt the selected model library, generate a model description file, and manage the encryption library.
[0070] Interface for importing and loading the encrypted library: On the model library import interface of the modeling software, add an interface for importing the encrypted library. When selecting to import the encrypted library, in the form of a pop-up window, etc., the user can choose to import the model after decryption or import without decryption. If the user selects to import after decryption, they need to enter a password. After the password is entered correctly, the software decrypts the encrypted library at the underlying layer and then loads it. What is loaded and imported is all the information of the original model library, and the user can view, modify, save, reuse, etc. all the models in this model library. If the user selects to import without decryption, the encrypted model library is directly loaded, and the user can instantiate and apply all the models in the encrypted model library. The interfaces and internal functions of the models are not affected, but the internal logic of the models and the code generated based on the models are all hidden.
[0071] Viewing and reusing the encrypted library: After the encrypted library is loaded and imported, all the models in the model library can be seen in the model management decryption. Dragging the subsystem model to the canvas can instantiate and apply the subsystem model in the encrypted library, which is no different from the operation of instantiating and applying the ordinary library model. However, the internal details of the subsystem model in the encrypted library are not supported to be viewed. When viewing the corresponding generated code in the code preview interface, only the subsystem functions can be displayed, and the internal implementation logic is all hidden.
[0072] The user interface 440 provides interfaces for model export and password setting, as well as interfaces for model import, whether to decrypt selection, and password input.
[0073] In an implementation manner of the embodiment of the present application, the device further includes:
[0074] The code generation module is used to generate corresponding code while the model constructed in the modeling software is being generated. The code generation module is the original basic module of the modeling software, which supports the realization of code generation based on the model.
[0075] In an implementation manner of the embodiment of the present application, the model library management module is specifically used to instantiate and apply the models in the encrypted model library when the imported encrypted model is loaded without decryption, and the internal implementation logic of the models cannot be viewed; for the code of the models in the encrypted model library, the subsystem functions are allowed to be viewed, and the implementation logic cannot be viewed.
[0076] In an implementation manner of the embodiment of the present application, the device further includes: a model decryption and loading module, which is used to decrypt the encrypted model library when the imported encrypted model is decrypted and loaded, and restore and generate an unencrypted model library; the model library management module is specifically used to realize viewing, modifying, saving, and reusing the internal structure of the model and generating the code corresponding to the model based on the models in the unencrypted model library.
[0077] The model decryption and loading module mainly includes the specific implementation module for model decryption and loading developed and integrated within the modeling software, as well as the controls and windows for model import and loading mode selection on the software operation interface.
[0078] The specific implementation module for model decryption and loading includes an encrypted model library import and loading module, a model decryption and non-secret library generation module, and a decrypted model library import and loading module. The encrypted model library import and loading module directly calls the model interfaces and function description files exported and generated by the model encryption module to load the encrypted model library, realizing the black-box loading and calling of each model within the model library. The model decryption and non-secret library generation module calls the password carrier file of the encrypted model, reads the decryption password input on the operation interface, and after comparison, calls the reverse algorithm of the encryption algorithm in the encryption module to decrypt the encrypted library and restore and generate a non-encrypted library containing all the information of the model. The decrypted model library import and loading module loads the above-mentioned decrypted and restored non-encrypted library to realize the white-box loading and calling of the model.
[0079] The controls and windows for model import and loading mode selection are integrated in the model library import interface. When the user imports the encrypted library, they can choose whether to decrypt. If they choose not to decrypt, the encrypted model library import and loading module is executed to directly import the encrypted model library. The encrypted model library and the models it contains will be displayed in the model library management column on the software interface. In this mode, both the model library and the models are protected and modification is not supported. The models can be instantiated for application, but the internal parts of the models cannot be viewed. If they choose to decrypt, a password input window will pop up. After the user enters the correct password, the encrypted library is decrypted to restore and generate a non-secret model containing all the information of the model, and then this non-secret model is automatically loaded. The non-secret model library and the models it contains will be displayed in the model library management column on the software interface. In this mode, both the model library and the models are in an open state and can be viewed, modified, saved, and reused.
[0080] The embodiments of the present application also provide corresponding devices and computer storage media for implementing the solutions provided by the embodiments of the present application.
[0081] Among them, the device includes a memory and a processor. The memory is used to store instructions or codes, and the processor is used to execute the instructions or codes so that the device executes the method described in any embodiment of the present application.
[0082] The computer storage medium stores codes. When the codes are run, the device running the codes implements the method described in any embodiment of the present application.
[0083] As can be seen from the description of the above embodiments, those skilled in the art can clearly understand that all or part of the steps in the above method embodiments can be implemented by means of software plus a general hardware platform. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product, which can be stored in a storage medium, such as a read-only memory (ROM) / RAM, magnetic disk, optical disk, etc., and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network communication device such as a router) to execute the methods described in various embodiments or some parts of the embodiments of the present application.
[0084] It can be understood that in the specific implementation of the present application, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved need to obtain user permission or consent when the above embodiments of the present application are applied to specific products or technologies, and the collection, use, and processing of relevant data need to comply with relevant laws, regulations, and standards of relevant countries and regions.
[0085] It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the phrase "comprising a..." does not exclude the presence of additional identical elements in the process, method, article or device comprising the element.
[0086] It should also be noted that the embodiments in this specification are all described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other, and the key point of each embodiment is to illustrate the differences from other embodiments. In particular, for the embodiments of the device and apparatus, since they are basically similar to the method embodiments, the description is relatively simple, and reference can be made to the relevant parts of the method embodiments for the relevant content. The device and apparatus embodiments described above are only illustrative. The units described as separate components may or may not be physically separated, and the components referred to as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art can understand and implement it without creative efforts.
[0087] As described above, it is only a specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any changes or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed in this application should be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.
Claims
1. A model encryption method, characterized in that, The method includes: Saving the model constructed in the modeling software to the model library; Exporting and encrypting the models in the model library to generate an encrypted model library; When importing the models in the encrypted model library into an application, decrypting and loading the imported encrypted models or loading them without decryption.
2. The model encryption method according to claim 1, wherein The encrypting the models in the model library includes: Encrypting the model library using a symmetric encryption algorithm.
3. The method according to claim 1, characterized in that, When decrypting and loading the imported encrypted models, the method further includes: Decrypting the encrypted model library to restore and generate an unencrypted model library; Based on the models in the unencrypted model library, realizing viewing, modifying, saving, and reusing the internal structure of the models and the code corresponding to the generated models.
4. The model encryption method according to claim 1, wherein When loading the imported encrypted models without decryption, the method further includes: Instantiating and applying the models in the encrypted model library, where the internal implementation logic of the models cannot be viewed; for the code of the models in the encrypted model library, the subsystem functions are allowed to be viewed, but the implementation logic cannot be viewed.
5. The method according to claim 1, wherein During the generation of the models constructed in the modeling software, corresponding code is generated simultaneously.
6. A model encryption device, characterized in that, The modeling device includes: A model construction module, configured to construct a model and save the model constructed in the modeling software to the model library; A model encryption configuration module, configured to export and encrypt the models in the model library to generate an encrypted model library; A model library management module, configured to decrypt and load or load without decryption the imported encrypted model library; A user interface, providing interfaces for model export and password setting, as well as interfaces for model import, selection of whether to decrypt, and password input.
7. The device according to claim 6, characterized in that, The model encryption configuration module is specifically configured to: Encrypt the model library using a symmetric encryption algorithm.
8. The device according to claim 6, characterized in that, The device further includes: A code generation module, configured to generate corresponding code simultaneously during the generation of the models constructed in the modeling software.
9. A computing device, characterized in that, The computing device includes: a memory, a processor; The memory is used to store a computer program; The processor is configured to implement the method according to any one of claims 1 to 5 when executing the computer program.
10. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium, and when the computer program is executed by the processor, the method according to any one of claims 1 to 5 is implemented.