Aircraft manufacturing data management method and system

Abstract

The invention provides an aircraft manufacturing data management method and system. The method comprises the following steps: creating a dynamic aircraft manufacturing data model and a data model field template corresponding to the dynamic aircraft manufacturing data model; after a request for modifying the type of the aircraft manufacturing data through the data model field template is initiated, the request node initiates a request for modifying the type of the aircraft manufacturing data to the interstellar file system; and the hyperledger randomly generates a key for the request node and encrypts the key, and the encrypted data is stored in an interstellar file system. According to the method, the dynamic aircraft manufacturing data model and the corresponding data model field template are created, so that the dynamic management requirement of the aircraft manufacturing data can be met, the AES encryption mode based on the block chain is used when the storage of the aircraft manufacturing data is modified, it is guaranteed that the data is not prone to being lost, and the credibility and safety of the data are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of aircraft manufacturing, and in particular to an aircraft manufacturing data management method; in addition, the present invention also relates to an aircraft manufacturing data management system. Background Art

[0002] In the aircraft manufacturing industry chain, aircraft manufacturing data plays an important role in the supervision of aircraft quality and aviation safety. Each aircraft is composed of multiple parts, with a wide variety of parts, and the parts are designed and manufactured globally, with a complex multi-stage supply chain. In particular, aircraft manufacturers involve many professional processes in the production and manufacturing of product parts. These professional processes involve process data and knowledge such as process terminology, process methods, process parameters, material parameters, and assembly processes. Each database table often has a different field structure depending on the process data and knowledge stored, and its field structure may also change as the process data and knowledge change.

[0003] However, in some currently developed aircraft manufacturing data management systems, it is impossible to dynamically manage and modify the corresponding data field structure for changes in process data and knowledge, thus failing to meet data management needs. Furthermore, in the process of managing aircraft manufacturing data, it is impossible to ensure that data is easily lost and the credibility of data is not guaranteed. These are the problems that urgently need to be solved in the current management of aircraft data. Summary of the invention

[0004] In order to solve the problems existing in the prior art, at least one embodiment of the present invention provides an aircraft manufacturing data management method, which largely meets the needs of aircraft manufacturing data management, ensures that data is not easily lost, and improves data credibility and security. To this end, at least one embodiment of the present invention also provides an aircraft manufacturing data management system.

[0005] In a first aspect, an embodiment of the present invention provides an aircraft manufacturing data management method, comprising:

[0006] Creating a dynamic aircraft manufacturing data model and a data model field template corresponding to the dynamic aircraft manufacturing data model;

[0007] After initiating a request to modify the aircraft manufacturing data type through the data model field template, the requesting node initiates a request to modify the aircraft manufacturing data type to the Interplanetary File System;

[0008] Hyperledger randomly generates a key for the requesting node and encrypts it, and stores the encrypted data in the InterPlanetary File System.

[0009] In some embodiments, in the aircraft manufacturing data management method provided by the present invention, the dynamic aircraft manufacturing data model stores dynamic data via JSON.

[0010] In some embodiments, in the aircraft manufacturing data management method provided by the present invention, the hyperledger randomly generates a key for the requesting node and encrypts the key, including:

[0011] The modified data of the requesting node is encrypted using the AES encryption algorithm.

[0012] In some embodiments, the aircraft manufacturing data management method provided by the present invention stores encrypted data in an interplanetary file system, including:

[0013] According to the encrypted data size, the data is stored in blocks respectively, and empty blocks are created. The empty blocks are linked to all blocks, and all blocks and the index structures corresponding to each block are stored in the interstellar file system.

[0014] In some embodiments, the aircraft manufacturing data management method provided by the present invention includes creating a Tab page, wherein the Tab page is provided with a three-dimensional model tag and an attribute tag, and the data in the attribute tag is associated with the three-dimensional model.

[0015] In a second aspect, an embodiment of the present invention further provides an aircraft manufacturing data management system, including:

[0016] A data model creation module, used for creating a dynamic aircraft manufacturing data model and a data model field template corresponding to the dynamic aircraft manufacturing data model;

[0017] A modification request module, used for initiating a request to modify the aircraft manufacturing data type through a data model field template, and the request node initiates a request to modify the aircraft manufacturing data type to the interplanetary file system;

[0018] The encryption module is used by the Hyperledger to randomly generate and encrypt a key for the requesting node;

[0019] The storage module is used to store the encrypted data in the Interstellar File System.

[0020] In some embodiments, the present invention provides an aircraft manufacturing data management system, the system comprising:

[0021] The Tab page module is used to create a Tab page. The Tab page has a 3D model label and an attribute label. The data in the attribute label is associated with the 3D model.

[0022] In a third aspect, an embodiment of the present invention further provides an aircraft manufacturing data management device, comprising at least one processor; a memory coupled to the at least one processor, the memory storing executable instructions, which when executed by the at least one processor implement the steps of any one of the methods of the first aspect above.

[0023] In a fourth aspect, an embodiment of the present invention further provides a chip for executing the steps of the method in the first aspect. Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip is used to execute the steps of the method in the first aspect.

[0024] In a fifth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of any one of the methods in the first aspect above are implemented.

[0025] It can be seen that an aircraft manufacturing data management method and system in an embodiment of the present invention can meet the needs of dynamic management of aircraft manufacturing data by creating a dynamic aircraft manufacturing data model and a corresponding data model field template, and use a blockchain-based AES encryption method when modifying the aircraft manufacturing data storage, thereby ensuring that data is not easily lost and improving data credibility and security. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0027] Figure 1 Shown is a flow chart of an aircraft manufacturing data management method according to an embodiment of the present invention;

[0028] Figure 2 Shown is a schematic diagram of the framework of an aircraft manufacturing data management system in an embodiment of the present invention. Specific implementation plan

[0029] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0030] 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. In this article, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0031] [Example 1]

[0032] The inventor of this solution has found that in the prior art, some currently developed aircraft manufacturing data management systems cannot dynamically manage and modify the corresponding data field structure for changes in process data and knowledge, thereby failing to meet data management needs. Furthermore, in the process of managing aircraft manufacturing data, it is impossible to ensure that data is easily lost and the credibility of data is not guaranteed. Embodiment 1 of the present invention provides the following solution:

[0033] like Figure 1 As shown, this embodiment provides an aircraft manufacturing data management method, including:

[0034] Step 101: Create a dynamic aircraft manufacturing data model and a data model field template corresponding to the dynamic aircraft manufacturing data model.

[0035] It should be noted that aircraft manufacturing data includes manufacturing process terminology data, metal processing process data, plastic forming process data, and material data, etc. The data model field template has various fields, which usually include some field attributes, such as ID, serial number, name, weight field, data type, link address, edit display, view display, description information, etc.

[0036] In some embodiments, the dynamic aircraft manufacturing data model stores dynamic data via JSON. It is understandable that the editing of dynamic fields of aircraft manufacturing data is achieved by modifying the properties of JSON, and the properties of JSON are modified via the data model field template on the front-end page.

[0037] Step 102, after initiating a request to modify the aircraft manufacturing data type through the data model field template, the requesting node initiates a request to modify the aircraft manufacturing data type to the InterPlanetary File System.

[0038] It can be understood that when initiating the above-mentioned modification request, the aircraft manufacturing data type is modified through the data model field template and the corresponding data of the modified field is also supplemented. Accordingly, the request node initiates a request to modify the aircraft manufacturing data type and the corresponding data to the interstellar file system.

[0039] Step 103: Hyperledger randomly generates a key for the requesting node and encrypts it, and stores the encrypted data in the InterPlanetary File System.

[0040] In some embodiments, after receiving the modification request, the hyperledger uses the AES encryption algorithm to encrypt the modification data of the requesting node. AES (Advanced Encryption Standarf) is a symmetric encryption algorithm that uses the same key for encryption and decryption, thereby making the encryption speed fast and the data operation efficiency high. The S-box transformation is a nonlinear mapping in the AES encryption algorithm, and its calculation is shown in the following formula 1:

[0041] S(x)=(f 1 (x), f 2 (x), ..., f m (x)): F n →F m ; Formula 1 Where x is the input byte element, n and m are the n-bit column vector and m-bit row vector of the table matrix.

[0042] It should be noted that the S-box is obtained by nonlinearly mapping the input a-bit data and outputting b-bit data. When an algorithm is attacked by a third party, the model constructed by combining the S-box and diffusion component characteristics of the algorithm can effectively resist these attacks.

[0043] Specifically, the S-box construction method includes random construction and mathematical function construction. For the input byte element, on the finite field GF28, the multiplication inverse operation of the following formula 2 is solved:

[0044] m(x)=x 8 +x 4 +x 3 +x+1; Formula 2

[0045] The specific operation is shown in the following formula 3:

[0046]

[0047] In Formula 3, in the finite field GF28, affine transformation operations are performed on u and v to perform affine transformation on each byte. Using quantum affine transformation as the main encryption method, combined with logistic mapping and Huffman coding, can resist information entropy attacks. It should be noted that the affine transformation is achieved by performing linear transformation and constant XOR operations on each byte of each data block. Specifically, the affine transformation includes a linear transformation and a constant addition. This step helps with confusion and diffusion during the encryption process, enhancing the security of the algorithm and its ability to resist cryptanalysis. The expression of the affine transformation is shown in Formula 4 below:

[0048] y=Ax -1 +B; Formula 4

[0049] Among them, A is an 8×8 reversible matrix in the finite field GF28, and B is an 8-bit column vector in the finite field GF28. The reversible matrix of the finite field is realized by mathematical operations on the finite field, and is used to confuse and diffuse data blocks. The reversible matrix is ​​a linear transformation used in the encryption round to ensure that the algorithm encryption effect is good, thereby effectively increasing the difficulty of cracking. Through mathematical operations on the finite field, these reversible matrices help to confuse and diffuse data blocks, thereby enhancing the encryption effect. A and B are specifically shown in the following formula 5:

[0050]

[0051] According to formula 5, we can get the following formula 6:

[0052] y=ux+v; Formula 6

[0053] The corresponding matrix expression of Formula 6 is shown in Formula 7 below:

[0054]

[0055] In Formula 7, the affine transformation pair selected in the AES algorithm is shown in Formula 8 below:

[0056]

[0057] It should be noted that Formula 4 is a nonlinear expression of the S-box. -1 Substitute it into equation 7 to get the inverse operation, thereby reconstructing the new S-box permutation table. The decryption process is the opposite of the encryption process, using the inverse operation, with the same key and the same operation. The inverse operation includes inverse permutation, inverse substitution and inverse confusion.

[0058] In some embodiments, data is stored in blocks according to the size of the encrypted data, empty blocks are created, the empty blocks are linked to all blocks, and all blocks and index structures corresponding to each block are stored in the interplanetary file system.

[0059] For example, if the data file size is less than 128KB, the file is directly stored in a block; if the data file size is larger than 128KB, the file is split into multiple 128KB files and placed in blocks. The Interstellar File System creates an empty block, which will link all sub-blocks of the file. Finally, all blocks and the index structures corresponding to each block are stored in the Interstellar File System.

[0060] In some embodiments, a Tab page is created, and the Tab page is provided with a three-dimensional model tag and an attribute tag. The data in the attribute tag is associated with the three-dimensional model, so that the aircraft manufacturing data can be managed more intuitively through the three-dimensional model on the page.

[0061] [Example 2]

[0062] like Figure 2 As shown, this embodiment provides an aircraft manufacturing data management system, including:

[0063] The data model creation module 201 is used to create a dynamic aircraft manufacturing data model and a data model field template corresponding to the dynamic aircraft manufacturing data model.

[0064] It should be noted that aircraft manufacturing data includes manufacturing process terminology data, metal processing process data, plastic forming process data, and material data, etc. The data model field template has various fields, which usually include some field attributes, such as ID, serial number, name, weight field, data type, link address, edit display, view display, description information, etc.

[0065] In some embodiments, the dynamic aircraft manufacturing data model stores dynamic data via JSON. It is understandable that the editing of dynamic fields of aircraft manufacturing data is achieved by modifying the properties of JSON, and the properties of JSON are modified via the data model field template on the front-end page.

[0066] The modification request module 202 is used for initiating a request to modify the aircraft manufacturing data type through the data model field template, and the request node initiates a request to modify the aircraft manufacturing data type to the interplanetary file system.

[0067] It can be understood that when initiating the above-mentioned modification request, the aircraft manufacturing data type is modified through the data model field template and the corresponding data of the modified field is also supplemented. Accordingly, the request node initiates a request to modify the aircraft manufacturing data type and the corresponding data to the interstellar file system.

[0068] The encryption module 203 is used for the hyperledger to randomly generate a key for the requesting node and encrypt it.

[0069] In some embodiments, after receiving the modification request, the hyperledger uses the AES encryption algorithm to encrypt the modification data of the requesting node. AES (Advanced Encryption Standarf) is a symmetric encryption algorithm that uses the same key for encryption and decryption, thereby making the encryption speed fast and the data operation efficiency high. S-box transformation is a nonlinear mapping in the AES encryption algorithm, and its calculation is shown in the following formula 1:

[0070] S(x)=(f 1 (x), f 2 (x), ..., f m (x)): F n →F m ; Formula 1 Where x is the input byte element, n and m are the n-bit column vector and m-bit row vector of the table matrix.

[0071] It should be noted that the S-box is obtained by nonlinearly mapping the input a-bit data and outputting b-bit data. When an algorithm is attacked by a third party, the model constructed by combining the S-box and diffusion component characteristics of the algorithm can effectively resist these attacks.

[0072] Specifically, the S-box construction method includes random construction and mathematical function construction. For the input byte element, on the finite field GF28, the multiplication inverse operation of the following formula 2 is solved:

[0073] m(x)=x 8 +x 4 +x 3 +x+1; Formula 2

[0074] The specific operation is shown in the following formula 3:

[0075]

[0076] In Formula 3, in the finite field GF28, affine transformation operations are performed on u and v to perform affine transformation on each byte. Using quantum affine transformation as the main encryption method, combined with logistic mapping and Huffman coding, can resist information entropy attacks. It should be noted that the affine transformation is achieved by performing linear transformation and constant XOR operations on each byte of each data block. Specifically, the affine transformation includes a linear transformation and a constant addition. This step helps with confusion and diffusion during the encryption process, enhancing the security of the algorithm and its ability to resist cryptanalysis. The expression of the affine transformation is shown in Formula 4 below:

[0077] y=Ax -1 +B; Formula 4

[0078] Among them, A is an 8×8 reversible matrix in the finite field GF28, and B is an 8-bit column vector in the finite field GF28. The reversible matrix of the finite field is realized by mathematical operations on the finite field, and is used to confuse and diffuse data blocks. The reversible matrix is ​​a linear transformation used in the encryption round to ensure that the algorithm encryption effect is good, thereby effectively increasing the difficulty of cracking. Through mathematical operations on the finite field, these reversible matrices help to confuse and diffuse data blocks, thereby enhancing the encryption effect. A and B are specifically shown in the following formula 5:

[0079]

[0080] According to formula 5, we can get the following formula 6:

[0081] y=ux+v; Formula 6

[0082] The corresponding matrix expression of Formula 6 is shown in Formula 7 below:

[0083]

[0084] In Formula 7, the affine transformation pair selected in the AES algorithm is shown in Formula 8 below:

[0085]

[0086] It should be noted that Formula 4 is a nonlinear expression of the S-box. -1 Substitute it into equation 7 to get the inverse operation, thereby reconstructing the new S-box permutation table. The decryption process is the opposite of the encryption process, using the inverse operation, with the same key and the same operation. The inverse operation includes inverse permutation, inverse substitution and inverse confusion.

[0087] The storage module 204 is used to store the encrypted data in the interplanetary file system.

[0088] In some embodiments, data is stored in blocks according to the size of the encrypted data, empty blocks are created, the empty blocks are linked to all blocks, and all blocks and index structures corresponding to each block are stored in the interplanetary file system.

[0089] For example, if the data file size is less than 128KB, the file is directly stored in a block; if the data file size is larger than 128KB, the file is split into multiple 128KB files and placed in blocks. The Interstellar File System creates an empty block, which will link all sub-blocks of the file. Finally, all blocks and the index structures corresponding to each block are stored in the Interstellar File System.

[0090] In some embodiments, the system also includes a Tab page module 205 for creating a Tab page. The Tab page is provided with a three-dimensional model tag and an attribute tag. The data in the attribute tag is associated with the three-dimensional model, so that the aircraft manufacturing data can be managed more intuitively through the three-dimensional model on the page.

[0091] [Example 3]

[0092] This embodiment provides an aircraft manufacturing data management device, including:

[0093] At least one processor; a memory coupled to the at least one processor, the memory storing executable instructions, wherein the executable instructions, when executed by the at least one processor, implement the method steps of embodiment 1 of the present invention.

[0094] In an aircraft manufacturing data management device provided by an embodiment of the present invention, a processor and a memory may be provided separately or integrated together.

[0095] For example, the memory may include a random access memory, a flash memory, a read-only memory, a programmable read-only memory, a non-volatile memory or a register, etc. The processor may be a central processing unit (CPU), etc. or a graphic processing unit (GPU). The memory may store executable instructions. The processor may execute the executable instructions stored in the memory to implement the various processes described herein.

[0096] It can be understood that the memory in this embodiment can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a ROM (Read-Only Memory), a PROM (Programmable ROM), an EPROM (Erasable PROM), an EEPROM (Electrically EPROM), or a flash memory. The volatile memory can be a RAM (Random Access Memory), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as SRAM (Static RAM), DRAM (Dynamic RAM), SDRAM (Synchronous DRAM), DDR SDRAM (Double Data Rate SDRAM), ESDRAM (Enhanced SDRAM), SLDRAM (Synchlink DRAM), and DRRAM (Direct Rambus RAM). The memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0097] In some embodiments, the memory stores the following elements, upgrade packages, executable units or data structures, or a subset thereof, or an extended set thereof: an operating system and an application program.

[0098] The operating system includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., which are used to implement various basic services and process hardware-based tasks. The application program includes various application programs, which are used to implement various application services. The program for implementing the method of the embodiment of the present invention can be included in the application program.

[0099] In the embodiment of the present invention, the processor calls a program or instruction stored in the memory, specifically, a program or instruction stored in an application program, and the processor is used to execute the method steps of the embodiment 1 of the present invention.

[0100] [Example 4]

[0101] This embodiment provides a chip for executing the method of the above-mentioned embodiment 1 of the present invention. Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip is used to execute the method of the embodiment 1 of the present invention.

[0102] [Example 5]

[0103] This embodiment provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method of Embodiment 1 of the present invention are implemented.

[0104] For example, machine-readable storage media may include, but are not limited to, various known and unknown types of non-volatile memory.

[0105] In summary, embodiments 1-5 of the present invention provide an aircraft manufacturing data management method and system, which can meet the needs of dynamic management of aircraft manufacturing data by creating a dynamic aircraft manufacturing data model and a corresponding data model field template. When modifying the storage of aircraft manufacturing data, a blockchain-based AES encryption method is used to ensure that data is not easily lost and improve data credibility and security.

[0106] It will be appreciated by those skilled in the art that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0107] In the embodiments of the present application, the disclosed systems, devices and methods can be implemented in other ways. For example, the division of units is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system. In addition, the coupling between the various units can be direct coupling or indirect coupling. In addition, the various functional units in the embodiments of the present application can be integrated into a processing unit, or can be separate physical existences, etc.

[0108] It should be understood that in the various embodiments of the present application, the size of the serial number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0109] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a machine-readable storage medium. Therefore, the technical solution of the present application can be embodied in the form of a software product, which can be stored in a machine-readable storage medium, which can include several instructions to enable an electronic device to perform all or part of the technical solution described in the embodiments of the present application. The above-mentioned storage medium may include various media that can store program codes, such as ROM, RAM, removable disk, hard disk, magnetic disk or optical disk.

[0110] The above contents are only specific implementation methods of the present application, and the protection scope of the present application is not limited thereto. Those skilled in the art may make changes or substitutions within the technical scope disclosed in the present application, and these changes or substitutions shall be within the protection scope of the present application.

Claims

1. A method for managing aircraft manufacturing data, characterized in that: include: Creating a dynamic aircraft manufacturing data model and a data model field template corresponding to the dynamic aircraft manufacturing data model; After initiating a request to modify the aircraft manufacturing data type through the data model field template, the requesting node initiates a request to modify the aircraft manufacturing data type to the InterPlanetary File System; The hyperledger randomly generates a key for the requesting node and encrypts it, and stores the encrypted data in the interplanetary file system.

2. The aircraft manufacturing data management method according to claim 1, characterized in that: The dynamic aircraft manufacturing data model stores dynamic data via JSON.

3. The aircraft manufacturing data management method according to claim 1, characterized in that: The hyperledger randomly generates a key for the requesting node and encrypts it, including: The modified data of the requesting node is encrypted using the AES encryption algorithm.

4. The aircraft manufacturing data management method according to claim 1, characterized in that: The storing the encrypted data in the interplanetary file system comprises: According to the encrypted data size, the data are stored in blocks respectively, and empty blocks are created. The empty blocks are linked to all blocks, and all blocks and the index structures corresponding to each block are stored in the interplanetary file system.

5. The aircraft manufacturing data management method according to claim 1, characterized in that: The method comprises creating a Tab page, wherein the Tab page is provided with a three-dimensional model label and an attribute label, and the data in the attribute label is associated with the three-dimensional model.

6. An aircraft manufacturing data management system, characterized in that: include: A data model creation module, used to create a dynamic aircraft manufacturing data model and a data model field template corresponding to the dynamic aircraft manufacturing data model; A modification request module, configured to, after initiating a request to modify the aircraft manufacturing data type through the data model field template, the request node initiates a request to modify the aircraft manufacturing data type to the Interplanetary File System; The encryption module is used by the Hyperledger to randomly generate and encrypt a key for the requesting node; The storage module is used to store the encrypted data in the interplanetary file system.

7. The aircraft manufacturing data management system according to claim 6, characterized in that: The system comprises: The Tab page module is used to create a Tab page, wherein the Tab page is provided with a three-dimensional model tag and an attribute tag, and the data in the attribute tag is associated with the three-dimensional model.

8. An aircraft manufacturing data management device, comprising at least one processor; a memory coupled to the at least one processor, the memory storing executable instructions, characterized in that: The executable instructions, when executed by the at least one processor, enable the steps of the method according to any one of claims 1 to 5 to be implemented.

9. A chip, characterized in that: It comprises a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the steps of the method as claimed in any one of claims 1 to 5.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are implemented.

Images