Encryption method for low-code component library design general rule and related equipment

Abstract

The invention discloses a low-code component library design general rule encryption method and related equipment, and relates to the technical field of computer software, and the method comprises the following steps: classifying Schema low-code models according to attributes; performing primary verification, compression and encryption on the various classified Schema low-code models so as to extract other attributes of the various Schema low-code models except self attributes, and obtaining encrypted and decoupled data models; and performing secondary verification, compression and encryption on various data models to obtain a secondary encryption model. According to the method, the pollution of the Schema low-code model in the network request is blocked through secondary encryption, so that the page data is effectively read, and the data security and the processing efficiency of the website page are improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer software, and particularly relates to a low-code component library design general rule encryption method and related equipment. BACKGROUND

[0002] At present, in the browser rendering performance of the front-end project in the ToB field, the structure quantity of DOM greatly affects the efficiency of browser rendering. When rendering the huge DOM node, the page may be stuck or even dead, which seriously affects the user experience.

[0003] Moreover, in the browser security rendering of the front-end project in the low-code platform field, the huge Schema model data is transmitted in plaintext between various SDKs of the low-code platform, and the normal WEB platform of the Schema data model has serious and huge security risks. SUMMARY

[0004] The main purpose of the embodiment of the present application is to provide a low-code component library design general rule encryption method and related equipment to improve the processing efficiency and security of the Schema low-code model.

[0005] To achieve the above purpose, one aspect of the embodiment of the present application provides a low-code component library design general rule encryption method, which comprises the following steps: Classifying the Schema low-code model according to attributes; Primary verification, compression and encryption of the classified various Schema low-code models are performed to abstract other attributes of the various Schema low-code models except their own attributes, so as to obtain an encrypted and decoupled data model; Secondary verification, compression and encryption of the various data models are performed to obtain a secondary encryption model.

[0006] In some embodiments, the classifying the Schema low-code model according to attributes comprises the following steps: Classifying the Schema low-code model according to attributes to obtain a Schema basic model, a Schema combination model, a Schema condition model, a Schema service model and a Schema business page model.

[0007] In some embodiments, the step of performing primary encryption and compression on the classified various Schema low-code models comprises the following steps: Using Crypto.randomUUID() to input the classified various Schema low-code models, and then returning a primary encryption seed; According to the primary encryption seed, various Schema low-code models after classification are compressed by primary encryption using Crypto. getRandomValues().

[0008] In some embodiments, the secondary verification, compression and encryption of various data models to obtain a secondary encryption model include the following steps: Various data models are encoded using a key-value mapping relationship, and various data models are flattened using Array. flatMap according to the returned encoded value, and then the values of various data models are converted into binary stream encryption storage; Various data models after binary stream encryption storage are subjected to secondary verification, compression and encryption to obtain a secondary encryption model.

[0009] In some embodiments, the secondary verification, compression and encryption of various data models after binary stream encryption storage to obtain a secondary encryption model include the following steps: Various data models after binary stream encryption storage are input using Crypto. randomUUID(), and then a secondary encryption seed is returned; According to the secondary encryption seed, various data models after binary stream encryption storage are compressed by secondary encryption using Crypto. getRandomValues().

[0010] In some embodiments, the method further includes the following steps: The secondary encryption model is decrypted to obtain the Schema low-code model.

[0011] In some embodiments, the decryption of the secondary encryption model to obtain the Schema low-code model includes the following steps: The secondary encryption model is decrypted to obtain the Schema low-code model according to the secondary encryption seed using Crypto. getRandomValues().

[0012] To achieve the above object, another aspect of the embodiment of the application proposes an encryption device for designing general rules of a low-code component library, the device comprising: A model classification unit is configured to classify Schema low-code models according to attributes; A primary encryption unit is configured to perform primary verification, compression and encryption on various classified Schema low-code models to abstract other attributes of various Schema low-code models except their own attributes, and obtain encrypted and decoupled data models; A secondary encryption unit is configured to perform secondary verification, compression and encryption on the various data models to obtain a secondary encrypted model.

[0013] To achieve the above object, another aspect of the embodiments of the present application provides an electronic device, which comprises a memory and a processor, the memory stores a computer program, and the processor implements the above method when executing the computer program.

[0014] To achieve the above object, another aspect of the embodiments of the present application provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the above method.

[0015] The embodiments of the present application at least have the following beneficial effects: The present application can classify Schema low-code models according to attributes; perform primary verification, compression and encryption on the classified various Schema low-code models to abstract other attributes of the various Schema low-code models except their own attributes, and obtain encrypted and decoupled data models; perform secondary verification, compression and encryption on the various data models to obtain secondary encrypted models. The present application blocks the pollution of Schema low-code models in network requests through secondary encryption, thereby effectively reading page data and improving the data security and processing efficiency of website pages. BRIEF DESCRIPTION OF DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiment description. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor on the basis of these drawings.

[0017] Figure 1 A flowchart of an encryption method for designing general rules of a low-code component library provided by the embodiments of the present application; Figure 2 An example flowchart of an encryption method for designing general rules of a low-code component library provided by the embodiments of the present application; Figure 3 A structural schematic diagram of an encryption device for designing general rules of a low-code component library provided by the embodiments of the present application; Figure 4 A hardware structural schematic diagram of an electronic device provided by the embodiments of the present application. DETAILED DESCRIPTION

[0018] In order to make the purposes, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and not intended to limit the present application. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with embodiments of the present application. They are only examples of apparatuses and methods consistent with some aspects of the embodiments of the present application as detailed in the appended claims.

[0019] It can be understood that the terms "first", "second" and the like used in the present application can be used herein to describe various concepts, but unless specifically stated, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another. For example, without departing from the scope of the embodiments of the present application, the first information can also be referred to as the second information, and similarly, the second information can also be referred to as the first information. Depending on the context, the word "if" as used herein can be interpreted as "when" or "when" or "in response to determining".

[0020] The terms "at least one", "multiple", "each", "any" and the like used in the present application include one, two or more than two, multiple includes two or more than two, each refers to each of the corresponding multiple, and any refers to any one of the multiple.

[0021] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as understood by those skilled in the art to which the present application belongs. The terms used herein are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.

[0022] Before the embodiments of the present application are described in detail, first, some related technologies involved in the embodiments of the present application are described as follows: At present, in the front-end project based on the ToB field, the number of DOM structures greatly affects the efficiency of browser rendering. When rendering a large number of DOM nodes, the page may be stuck or even frozen, which seriously affects the user experience. Specifically, it includes: first screen loading, multi-table data display, article list display, comment list display, fast scrolling and other complex DOM operation scenarios. The present embodiment mainly provides an optimization method based on browser CSS for such a scene with too many DOMs.

[0023] Currently, in the field of low-code platform-based front-end projects, the schema data model of the normal WEB platform has serious and huge security risks in browser security rendering. The huge Schema model data is transmitted in plaintext between various SDKs of the low-code platform, including: client request reading service data leakage, low-code material base system source code built-in Schema data leakage, low-code palette area rendering Schema generated DOM node data leakage, and material collection Schema batch generated source code data leakage problems. The embodiment mainly provides an optimization method based on the built-in encryption function of the browser system for the above scenarios.

[0024] Therefore, the encryption method for low-code component library design general rules and related equipment are provided. The technical scheme of the present application includes: classifying the Schema low-code model according to the attributes; performing primary verification, compression and encryption on the classified various Schema low-code models to abstract other attributes of the various Schema low-code models except their own attributes, and obtain encrypted and decoupled data models; performing secondary verification, compression and encryption on the various data models to obtain secondary encrypted models. The present application blocks the pollution of the Schema low-code model in the network request through secondary encryption, thereby effectively reading the page data and improving the data security and processing efficiency of the website page.

[0025] The encryption method for low-code component library design general rules and related equipment provided by the embodiment of the present application are related to the technical field of computer software. The encryption method for low-code component library design general rules and related equipment provided by the embodiment of the present application can be applied in a terminal, can be applied in a server, and can also be software running in a terminal or a server. In some embodiments, the terminal can be a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, a vehicle-mounted terminal, and the like, but is not limited thereto; the server end can be configured as a standalone physical server, can be configured as a server cluster or a distributed system composed of multiple physical servers, can be configured as a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, and basic cloud computing services such as big data and artificial intelligence platforms, and the server can also be a node server in a blockchain network; the software can be an application that implements an encryption method for low-code component library design general rules, and the like, but is not limited to the above forms.

[0026] The application is operable in a variety of general purpose or special purpose computer systems environments or configurations. Examples of well-known computing systems, environments, and / or configurations that can be suitable for use with the application include personal computers, server computers, handheld or laptop devices, tablet devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. The application can be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, and the like, that perform particular tasks or implement particular abstract data types. The application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in local and remote computer storage media including memory storage devices.

[0027] Referring to Figure 1 The embodiment of the application provides a low-code component library design universal rule encryption method, which can include but is not limited to S100 to S120, and specifically as follows: S100: classifying Schema low-code models according to attributes; S110: performing primary verification, compression and encryption on the classified various Schema low-code models, to abstract other attributes of the various Schema low-code models except for self attributes, and obtain encrypted and decoupled data models; S120: performing secondary verification, compression and encryption on the various data models, to obtain secondary encryption models.

[0028] Optionally, the classifying Schema low-code models according to attributes includes the following steps: Classifying Schema low-code models according to attributes to obtain Schema basic models, Schema combination models, Schema condition models, Schema service models and Schema business page models.

[0029] Optionally, the step of performing primary encryption and compression on the classified various Schema low-code models includes the following steps: Using Crypto.randomUUID() to input the classified various Schema low-code models, and then returning to obtain a primary encryption seed; According to the primary encryption seed, using Crypto.getRandomValues() to perform primary encryption and compression on the classified various Schema low-code models.

[0030] Optionally, the secondary verification, compression and encryption of various data models to obtain a secondary encryption model comprises the following steps: The various data models are encoded using a key-value mapping relationship, and the various data models are flattened using Array.flatMap according to the returned encoded value, and then the values of the various data models are converted into a binary stream for encrypted storage. The various data models after binary stream encrypted storage are subjected to secondary verification, compression and encryption to obtain a secondary encryption model.

[0031] Optionally, the secondary verification, compression and encryption of the various data models after binary stream encrypted storage to obtain a secondary encryption model comprises the following steps: The various data models after binary stream encrypted storage are input using Crypto.randomUUID(), and then a secondary encryption seed is returned. The various data models after binary stream encrypted storage are subjected to secondary encryption compression using Crypto.getRandomValues() according to the secondary encryption seed.

[0032] Optionally, the method further comprises the following steps: The secondary encryption model is decrypted to obtain the Schema low-code model.

[0033] Optionally, the decryption of the secondary encryption model to obtain the Schema low-code model comprises the following steps: The secondary encryption model is decrypted using Crypto.getRandomValues() according to the secondary encryption seed to obtain the Schema low-code model.

[0034] Next, the scheme of the embodiments of the present application will be described in detail with reference to specific application examples.

[0035] The present embodiment provides an encryption algorithm for the general rules of low-code Schema models, aiming to solve the problem of data security in the use, rendering and upgrading of Schema models in the low-code platform page, which may cause the platform security system to be attacked. The specific encryption details are as follows: The present embodiment provides a new DOM optimization method, aiming to solve the problem of poor user experience caused by the performance lag of DOM rendering in the Web platform page. The main purpose is to selectively generate corresponding DOM code for the business UI model structure, and the step flow chart is as follows: Figure 2 .

[0036] The flow node of the embodiment scheme is described as follows: Flow node 1: attribute classification according to Schema low code model data.

[0037] The Schema low code model integrates all functions in a page: business interaction, request, script, style, font picture, video and other resource attribute definitions. Through separation and classification according to the definition, rules and actual use of attributes, the five basic attribute sets can be divided into: basic attributes, combined attributes, conditional attributes, service attributes and business attributes. According to the five separated attributes, five data models are generated in turn: Schema basic model, Schema combined model, Schema conditional model, Schema service model and Schema container model.

[0038] Flow node 2: initial encryption Crypto.

[0039] After analyzing the data model obtained in flow node 1, the model data is transmitted into the model data using Crypto.randomUUID(), and the initial encryption seed is returned. Then, according to the seed, Crypto.getRandomValues() is used for encryption compression. It is ensured that the initial data of each data model cannot be normally read, and the possibility of stealing and using the data model is blocked.

[0040] Flow node 3: model integration coding.

[0041] After the data model obtained in flow node 2 is encrypted, there is still a possibility of reverse decryption. Therefore, key-value mapping relationship coding is used for each data model, and the returned coding value is used to flatten the data using the browser's built-in API: Array.flatMap. Flow node 4: re-encryption Crypto.

[0042] After the data model obtained in flow node 2 is encrypted, there is still a possibility of reverse decryption. Therefore, key-value mapping relationship coding is used for each data model, and the returned coding value is used to flatten the data using the browser's built-in API: Array.flatMap. This step directly blocks the possibility that the data model cannot be decrypted in the local and network bandwidth.

[0043] The beneficial effects of the embodiment include: The encryption process design for the low code Schema data model has the following advantages: 1. From the fundamental sense, the data model is blocked in the network request, the page data is effectively read, and the data security of the website page is ensured; 2. Optimized data loss and pollution problems of data model in the transmission process, fundamentally eliminated the data overlap cycle problem; 3. Reduced vulnerability of using external third-party encryption library, reduced page rendering time and bandwidth cost by using the built-in API feature of the browser; 4. The performance loss of high-frequency read-write operation encryption always maintains a very low level; 5. Make full use of the encryption Workder function of the client, reduce the single-threaded browser caused by the web page card node.

[0044] Reference Figure 3 The embodiment of the application also provides an encryption device for low-code component library design general rules, which can implement the low-code component library design general rule encryption method. The device comprises: A model classification unit for classifying Schema low-code models according to attributes; A primary encryption unit for performing primary verification, compression and encryption on the classified Schema low-code models, to abstract other attributes of the Schema low-code models except their own attributes, and obtain encrypted and decoupled data models; A secondary encryption unit for performing secondary verification, compression and encryption on the data models to obtain secondary encryption models.

[0045] It can be understood that the contents in the above method embodiments are applicable to the device embodiments, the device embodiments specifically implement the same functions as the above method embodiments, and achieve the same beneficial effects as the above method embodiments.

[0046] The embodiment of the application also provides an electronic device, which comprises a memory and a processor. The memory stores a computer program, and the processor implements the method of the embodiment of the application when executing the computer program. The electronic device can be any intelligent terminal, such as a tablet computer or a vehicle-mounted computer.

[0047] It can be understood that the contents in the above method embodiments are applicable to the device embodiments, the device embodiments specifically implement the same functions as the above method embodiments, and achieve the same beneficial effects as the above method embodiments.

[0048] Please refer to Figure 4 , Figure 4 The hardware structure of the electronic device of another embodiment is illustrated, which comprises: The processor 401 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits, and is configured to execute related programs to implement the technical solutions provided by the embodiments of the present application. The memory 402 can be implemented by a ROM (Read Only Memory), a static storage device, a dynamic storage device, or a RAM (Random Access Memory), and the like. The memory 402 can store an operating system and other application programs, and when the technical solutions provided by the embodiments of the present application are implemented by software or firmware, the related program codes are stored in the memory 402 and are called and executed by the processor 401 to implement the method of the embodiments of the present application. The input / output interface 403 is configured to implement information input and output. The communication interface 404 is configured to implement the communication interaction between the device and other devices, and can realize the communication through a wired manner (for example, a USB, a network cable, or the like) or a wireless manner (for example, a mobile network, WIFI, Bluetooth, or the like). The bus 405 is configured to transmit information between various components (for example, the processor 401, the memory 402, the input / output interface 403, and the communication interface 404) of the device. The processor 401, the memory 402, the input / output interface 403, and the communication interface 404 are connected to each other through the bus 405 to realize the communication connection between the device.

[0049] The embodiments of the present application further provide a computer readable storage medium, which stores a computer program. The computer program is executed by a processor to implement the method of the present application.

[0050] It can be understood that the content in the above method embodiments is applicable to the storage medium embodiments, the storage medium embodiments specifically implement the functions of the above method embodiments, and achieve the same beneficial effects as the above method embodiments.

[0051] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. In addition, the memory can include a high-speed random access memory and can also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state memory device. In some embodiments, the memory can optionally include a memory disposed remotely from the processor, which can be connected to the processor through a network. Examples of the above network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0052] The embodiments described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the evolution of technology and the appearance of new application scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0053] Those skilled in the art can understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and can include more or fewer steps than shown in the figures, or combine certain steps, or different steps.

[0054] The device embodiments described above are only schematic, and the units described as separate components can or can not be physically separate, i.e., can be located in one place, or can be distributed on multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the embodiments of the present application.

[0055] Those skilled in the art can understand that all or some of the steps in the above disclosed method, the functional modules / units in the system and the device can be implemented as software, firmware, hardware and their appropriate combinations.

[0056] The terms "first", "second", "third", "fourth" and the like used in the specification of the present application and the above-described drawings, if any, are used to distinguish similar objects, and do not necessarily have to describe a particular order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device including a series of steps or units does not have to be limited to only those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0057] It should be understood that, in the application, "at least one" refers to one or more, and "multiple" refers to two or more. "And / or" is used to describe the association relationship of the associated objects, which means that there can be three relationships, for example, "A and / or B" can represent three cases of only A, only B, and A and B existing at the same time, wherein A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects before and after it. "At least one of the following" or similar expressions means any combination of these items, including any combination of single or multiple items. For example, at least one of a, b or c can represent a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, and c can be single or multiple.

[0058] In several embodiments provided in the application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the above units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed mutual units can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0059] The units described above as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on multiple network units. According to actual needs, part or all of the units can be selected to achieve the purpose of the embodiment scheme.

[0060] In addition, the functional units in each embodiment of the application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0061] The integrated unit, if implemented in the form of a software function unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application, essentially or in other words, the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes multiple instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program storage media.

[0062] The preferred embodiments of the embodiments of the present application are described above with reference to the accompanying drawings, and are not limited to the scope of the embodiments of the present application. Any modifications, equivalent replacements and improvements made by those skilled in the art without departing from the scope and essence of the embodiments of the present application shall be within the scope of the embodiments of the present application.

Claims

1. A method for encrypting general rules for designing a low-code component library, characterized in that: The method comprises the following steps: Classify Schema low-code models based on attributes; Initially verify, compress, and encrypt the various Schema low-code models after classification to extract other attributes of the various Schema low-code models except their own attributes to obtain encrypted and decoupled data models; The various data models are subjected to secondary verification, compression and encryption to obtain a secondary encrypted model.

2. The encryption method for designing general rules for a low-code component library according to claim 1 is characterized in that: The classification of the Schema low-code model according to attributes includes the following steps: The Schema low-code model is classified according to attributes to obtain the Schema basic model, Schema combination model, Schema conditional model, Schema service model and Schema business page model.

3. The encryption method for designing general rules for a low-code component library according to claim 1 is characterized in that: The steps of initially encrypting and compressing the various Schema low-code models after classification include the following steps: Use Crypto.randomUUID() to pass in the various Schema low-code models after classification, and then return the initial encryption seed; According to the initial encryption seed, Crypto.getRandomValues() is used to perform initial encryption compression on the various classified Schema low-code models.

4. The encryption method for designing general rules for a low-code component library according to claim 1 is characterized in that: The secondary verification, compression and encryption of the various data models to obtain a secondary encrypted model includes the following steps: Encode the various data models using a key-value mapping relationship and flatten the various data models using Array.flatMap according to the returned encoded values, and then convert the values ​​of the various data models into binary stream encrypted storage; The various data models stored in binary stream encryption are subjected to secondary verification, compression and encryption to obtain secondary encrypted models.

5. The encryption method for designing general rules for a low-code component library according to claim 4 is characterized in that: The method of performing secondary verification, compression, and encryption on the various data models stored after binary stream encryption to obtain a secondary encrypted model includes the following steps: Use Crypto.randomUUID() to pass in the various data models stored after binary stream encryption, and then return the secondary encryption seed; The various data models stored after binary stream encryption are compressed twice using Crypto.getRandomValues() according to the secondary encryption seed.

6. A method for encrypting general rules for designing a low-code component library according to any one of claims 1 to 5, characterized in that: The method further comprises the following steps: The secondary encrypted model is decrypted to obtain the Schema low-code model.

7. The encryption method for designing general rules for a low-code component library according to claim 6 is characterized in that: Decrypting the secondary encrypted model to obtain the Schema low-code model includes the following steps: Use Crypto.getRandomValues() according to the secondary encryption seed to decrypt the secondary encrypted model to obtain the Schema low-code model.

8. An encryption device for designing general rules for a low-code component library, characterized in that: The device comprises: Model classification unit, used to classify Schema low-code models according to attributes; The initial encryption unit is used to perform initial verification, compression and encryption on the various Schema low-code models after classification, so as to extract other attributes of the various Schema low-code models except their own attributes and obtain an encrypted and decoupled data model; The secondary encryption unit is used to perform secondary verification, compression and encryption on the various data models to obtain secondary encrypted models.

9. An electronic device, characterized in that: The electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images