Code-free security point management system development method and device

Abstract

The invention provides a code-free security point management system development method and device in the technical field of security management. The code-free security point management system development method comprises the following steps: S1, creating a security point management rule and analyzing to obtain a management node; s2, packaging the management nodes into technical components, and inputting the technical components into a component warehouse; s3, creating a data model and a business object through a data modeling tool of the code-free development platform; s4, creating a system interface through the page designer and the page component; s5, performing service definition and service interface declaration on the technical component, the data model and the business object through a service modeling tool; s6, binding the service with the page component through a page event definition device, and defining interaction logic; and S7, issuing through an issuing tool. The method has the advantages that the development convenience, efficiency and expansibility of the safety point management system are greatly improved, and the use safety of the safety point management system is greatly improved.

Description

Technical Field

[0001] This invention relates to the field of security management technology, and in particular to a no-code security points management system development method and apparatus. Background Technology

[0002] A safety points management system is a points-based safety management system designed to incentivize employees and workers to prioritize safety, comply with safety regulations, and actively participate in safety management activities. Safety points management systems are widely used in fields requiring a high level of safety awareness, such as construction sites and hazardous chemical management. The rules and procedures for safety points management systems vary depending on the industry, region, company size, work environment, and specific needs.

[0003] With the development of software engineering, especially the specialization of labor, complex systems can be broken down into multiple components. Each component is researched, developed and optimized in depth by professional companies and teams. This specialization enables each component to reach a higher level of technology and quality standards. For example, front-end components, back-end data computing and processing components, databases, facial recognition, maps and so on can all be developed by professional companies and personnel.

[0004] Traditionally, security points management systems are developed based on code and component-based technologies. Different components are developed by different component vendors, and these components need to be assembled, debugged, tested, and deployed. However, these component vendors only provide professional programming interfaces, so the subsequent work still needs to be done by programmers with computer science backgrounds. In order to cope with the differences in security points management rules and processes, multiple sets of code are often required, which has the problems of high technical threshold, low development efficiency, need for team collaboration, high cost, and poor system scalability. In addition, traditionally developed security points management systems only use account passwords for authentication, which is not secure enough and is at risk of being accessed without authorization.

[0005] Therefore, how to provide a no-code security points management system development method and device to improve the convenience, efficiency and scalability of security points management system development, and enhance the security of security points management system use, has become an urgent technical problem to be solved. Summary of the Invention

[0006] The technical problem to be solved by the present invention is to provide a no-code security points management system development method and apparatus, thereby improving the convenience, efficiency and scalability of security points management system development and enhancing the security of security points management system use.

[0007] In a first aspect, the present invention provides a no-code security points management system development method, comprising the following steps: Step S1: Create a security points management rule, and use a UML tool to parse the security points management rule to obtain a component diagram including several management nodes; Step S2: Encapsulate each management node into a corresponding technical component. After setting the configuration information of each technical component through XML, including at least component attributes, input parameters, output parameters, event descriptions and behavior descriptions, enter each technical component into the component repository of the no-code development platform. Step S3: Based on the security points management rules, create a data model and business objects for the security points management system using the data modeling tools of the no-code development platform; Step S4: Using the page designer of the no-code development platform, drag and drop page components from the component repository to create the system interface of the security points management system. Step S5: Using the service modeling tool of the no-code development platform, define services and declare service interfaces for the technical components, data models, and business objects; Step S6: Bind the service to the page components of the system interface through the page event definer of the no-code development platform, and define the interaction logic of each page component. Step S7: Using the deployment tool of the no-code development platform, package the system interface and services into a security points management system, set the security verification mechanism of the security points management system, and deploy the security points management system to the container orchestration system based on the input deployment command.

[0008] Furthermore, in step S3, the creation of the data model for the security points management system using the data modeling tool of the no-code development platform specifically involves: Define a data source, including database type and connection address information, using the data source definition tool of the no-code development platform; the connection address information includes at least IP address, port, and database name; Based on the aforementioned security points management rules, an ER diagram is output using a database design tool; Using the data modeling tools of a no-code development platform, the ER diagram is converted into a data model including a logical model and a physical model based on database normalization. The data model is then published to the data source, and the metadata of the data model is stored in a pre-created metadata table.

[0009] Furthermore, step S4 specifically includes: Using the page designer of the no-code development platform, page components in the component repository are dragged and dropped in a drag-and-drop interactive manner to lay out each page component, set the style of each page component, and store the display parameters including the layout and style in HTML and CSS formats to create a system interface of the security points management system including several sub-interfaces. A unique interface identifier is generated for each sub-interface to complete the creation of the system interface of the security points management system.

[0010] Furthermore, in step S5, the service definition includes at least the definitions of service data objects, service input parameters, service output parameters, and business logic.

[0011] Furthermore, step S6 specifically includes: By using the page event definer of the no-code development platform, the service is bound to the page components of the system interface, and the interaction logic of each page component is defined, including at least the triggering event and the associated behavior. In step S7, the container orchestration system is Kubernetes; The verification process of the security verification mechanism is as follows: The access request from the security points management system is parsed to obtain ciphertext data, signature data, timestamp, and MAC value. The calculation process for the ciphertext data is as follows: First-level encrypted data is obtained by encrypting the account password, device ID, and public key used to verify the signature data using the IDEA algorithm; second-level encrypted data is obtained by mapping each character of the first-level encrypted data using a preset first mapping rule; third-level encrypted data is obtained by encrypting the second-level encrypted data using the RSA algorithm; fourth-level encrypted data is obtained by mapping each character of the third-level encrypted data using a preset second mapping rule; fifth-level encrypted data is obtained by encrypting the fourth-level encrypted data using the ECDSA algorithm; sixth-level encrypted data is obtained by mapping each character of the fifth-level encrypted data using a preset third mapping rule; and finally, ciphertext data is obtained by encrypting the sixth-level encrypted data using the 3DES algorithm. The MAC value is calculated by performing MAC calculation on the ciphertext data, signature data, and timestamp. After verifying the integrity of the ciphertext data, signature data, and timestamp using the MAC value, and then verifying the validity of the data using the timestamp, the ciphertext data is decrypted to obtain the account password, device ID, and public key. The signature data is then verified using the public key. The device ID is then verified for validity using a preset device management table. Finally, the account password is verified for validity using a preset password management table. The decryption process for the encrypted data is as follows: The ciphertext data is decrypted using the 3DES algorithm to obtain level six encrypted data. Each character of the level six encrypted data is mapped using a preset third mapping rule to obtain level five encrypted data. The level five encrypted data is decrypted using the ECDSA algorithm to obtain level four encrypted data. Each character of the level four encrypted data is mapped using a preset second mapping rule to obtain level three encrypted data. The level three encrypted data is decrypted using the RSA algorithm to obtain level two encrypted data. Each character of the level two encrypted data is mapped using a preset first mapping rule to obtain level one encrypted data. The level one encrypted data is then decrypted using the IDEA algorithm to obtain the account password, device ID, and public key. Secondly, the present invention provides a no-code security points management system development device, comprising the following modules: The security points management rule parsing module is used to create a security points management rule and parse the security points management rule using a UML tool to obtain a component diagram including several management nodes. The technical component creation module is used to encapsulate each of the management nodes into a corresponding technical component. After setting the configuration information of each technical component through XML, including at least component attributes, input parameters, output parameters, event descriptions and behavior descriptions, the technical components are entered into the component repository of the no-code development platform. The data model and business object creation module is used to create the data model and business objects of the security points management system based on the security points management rules, using the data modeling tools of the no-code development platform. The system interface creation module is used to create the system interface of the security points management system by dragging and dropping page components from the component repository through the page designer of the no-code development platform. The service definition module is used to define services and declare service interfaces for the technical components, data models, and business objects through the service modeling tools of the no-code development platform. The interaction logic definition module is used to bind the service to the page components of the system interface through the page event definer of the no-code development platform, and to define the interaction logic of each page component. The publishing module is used to package the system interface and services into a security points management system using the publishing tools of the no-code development platform, set the security verification mechanism of the security points management system, and publish the security points management system to the container orchestration system based on the input publishing command.

[0012] Furthermore, in the data model and business object creation module, the creation of the data model for the security points management system using the data modeling tool of the no-code development platform specifically involves: Define a data source, including database type and connection address information, using the data source definition tool of the no-code development platform; the connection address information includes at least IP address, port, and database name; Based on the aforementioned security points management rules, an ER diagram is output using a database design tool; Using the data modeling tools of a no-code development platform, the ER diagram is converted into a data model including a logical model and a physical model based on database normalization. The data model is then published to the data source, and the metadata of the data model is stored in a pre-created metadata table.

[0013] Furthermore, the system interface creation module is specifically used for: Using the page designer of the no-code development platform, page components in the component repository are dragged and dropped in a drag-and-drop interactive manner to lay out each page component, set the style of each page component, and store the display parameters including the layout and style in HTML and CSS formats to create a system interface of the security points management system including several sub-interfaces. A unique interface identifier is generated for each sub-interface to complete the creation of the system interface of the security points management system.

[0014] Furthermore, in the service definition module, the service definition includes at least the definition of service data objects, service input parameters, service output parameters, and business logic.

[0015] Furthermore, the interaction logic definition module is specifically used for: By using the page event definer of the no-code development platform, the service is bound to the page components of the system interface, and the interaction logic of each page component is defined, including at least the triggering event and the associated behavior. In the deployment module, the container orchestration system is Kubernetes; The verification process of the security verification mechanism is as follows: The access request from the security points management system is parsed to obtain ciphertext data, signature data, timestamp, and MAC value. The calculation process for the ciphertext data is as follows: First-level encrypted data is obtained by encrypting the account password, device ID, and public key used to verify the signature data using the IDEA algorithm; second-level encrypted data is obtained by mapping each character of the first-level encrypted data using a preset first mapping rule; third-level encrypted data is obtained by encrypting the second-level encrypted data using the RSA algorithm; fourth-level encrypted data is obtained by mapping each character of the third-level encrypted data using a preset second mapping rule; fifth-level encrypted data is obtained by encrypting the fourth-level encrypted data using the ECDSA algorithm; sixth-level encrypted data is obtained by mapping each character of the fifth-level encrypted data using a preset third mapping rule; and finally, ciphertext data is obtained by encrypting the sixth-level encrypted data using the 3DES algorithm. The MAC value is calculated by performing MAC calculation on the ciphertext data, signature data, and timestamp. After verifying the integrity of the ciphertext data, signature data, and timestamp using the MAC value, and then verifying the validity of the data using the timestamp, the ciphertext data is decrypted to obtain the account password, device ID, and public key. The signature data is then verified using the public key. The device ID is then verified for validity using a preset device management table. Finally, the account password is verified for validity using a preset password management table. The decryption process for the encrypted data is as follows: The ciphertext data is decrypted using the 3DES algorithm to obtain level six encrypted data. Each character of the level six encrypted data is mapped using a preset third mapping rule to obtain level five encrypted data. The level five encrypted data is decrypted using the ECDSA algorithm to obtain level four encrypted data. Each character of the level four encrypted data is mapped using a preset second mapping rule to obtain level three encrypted data. The level three encrypted data is decrypted using the RSA algorithm to obtain level two encrypted data. Each character of the level two encrypted data is mapped using a preset first mapping rule to obtain level one encrypted data. The level one encrypted data is then decrypted using the IDEA algorithm to obtain the account password, device ID, and public key. The advantages of this invention are: 1. By creating security points management rules, and using UML tools to parse these rules to obtain a component diagram containing several management nodes, each management node is encapsulated as a corresponding technical component. After setting configuration information for each technical component, including at least component attributes, input parameters, output parameters, event descriptions, and behavior descriptions, each technical component is entered into the component repository of the no-code development platform. Next, based on the security points management rules, the data model and business objects of the security points management system are created using the data modeling tools of the no-code development platform. The page designer uses a drag-and-drop interaction to drag page components from the component repository to create the system interface of the security points management system. Service modeling tools are used to define services and declare service interfaces for the technical components, data model, and business objects. The page event definer binds services to the page components of the system interface and defines each page group. The interaction logic of the components is then packaged into a security points management system using a publishing tool. After setting the security verification mechanism of the security points management system, it is published to the container orchestration system based on the input publishing command. That is, technical components created based on security points management rules are entered into the component repository of the no-code development platform. The no-code development platform develops the security points management system based on the technical components in a WYSIWYG manner, without requiring programmers with computer science backgrounds. Furthermore, the technical components can be extended as needed. Before the security points management system is published, a security verification mechanism including integrity verification, timeliness verification, signature verification, first legality verification, and second legality verification is set to prevent unauthorized access to the security points management system, thereby greatly improving the convenience, efficiency, and scalability of the security points management system development, and greatly enhancing the security of the security points management system.

[0016] 2. By setting the access request to carry encrypted data, signature data, timestamp, and MAC value, the encrypted data is obtained by multi-level encryption of the account password, device ID, and public key used to verify the signature data. Subsequent verification can be performed based on the MAC value for integrity, the timestamp for timeliness, the public key for signature verification, the device ID for first-level legitimacy verification, and the account password for second-level legitimacy verification. The account password, device ID, and public key are encrypted using the IDEA algorithm to obtain first-level encrypted data. Each character of the first-level encrypted data is mapped using a preset first mapping rule to obtain second-level encrypted data. The second-level encrypted data is then encrypted using the RSA algorithm to obtain third-level encrypted data, which is then further encrypted using a preset second mapping rule. The system maps each character of the Level 3 encrypted data to obtain Level 4 encrypted data. Level 4 encrypted data is then encrypted using the ECDSA algorithm to obtain Level 5 encrypted data. Finally, Level 5 encrypted data is encrypted using a preset third mapping rule to obtain Level 6 encrypted data. The Level 6 encrypted data is then encrypted using the 3DES algorithm to obtain ciphertext data. Without knowing the corresponding encryption algorithm or mapping rule, the ciphertext data cannot be cracked. At least 12 security measures are implemented (IDEA algorithm, first mapping rule, RSA algorithm, second mapping rule, ECDSA algorithm, third mapping rule, 3DES algorithm, MAC value, timestamp, public key, device ID, and account password), thus greatly enhancing the security of the security points management system. Attached Figure Description

[0017] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0018] Figure 1 This is a flowchart of a no-code security points management system development method according to the present invention.

[0019] Figure 2 This is a schematic diagram of the structure of a no-code security points management system development device according to the present invention. Detailed Implementation

[0020] The overall concept of the technical solution in this application embodiment is as follows: Technical components based on security points management rules are created and entered into the component repository of a no-code development platform. The no-code development platform develops a WYSIWYG security points management system based on these technical components, eliminating the need for programmers with computer science backgrounds. Furthermore, the technical components can be expanded as needed. Before the security points management system is released, a security verification mechanism is set up, including integrity verification, timeliness verification, signature verification, first legality verification, and second legality verification, to prevent unauthorized access to the security points management system. This improves the convenience, efficiency, and scalability of the security points management system development, and enhances the security of its use. Please refer to Figures 1 to 2 As shown, a preferred embodiment of the no-code security points management system development method of the present invention includes the following steps: Step S1: Create a security points management rule, and use a UML (Unified Modeling Language) tool (such as Visio) to parse the security points management rule to obtain a component diagram including several management nodes; Step S2: Encapsulate each management node into a corresponding technical component. After setting the configuration information of each technical component using XML (Extensible Markup Language), including at least component attributes, input parameters, output parameters, event descriptions, and behavior descriptions, enter each technical component into the component repository of the no-code development platform. The component repository is equipped with components for data query, data update, data insertion, etc. Step S3: Based on the security points management rules, create a data model and business objects for the security points management system using the data modeling tools of the no-code development platform. The no-code development platform is a technology platform that allows software development without writing code. Through a graphical interface and pre-built modules, it enables non-professional programmers to quickly build applications, providing rich functions and tools, including online form design, report generation, data visualization, etc., aiming to lower the threshold for software development and improve development efficiency. A Business Object (BO) is an abstract representation of information related to people, events, things, and places. It is a mapping of actual business operations in the information world, a component for data retrieval and processing, and a software abstraction of the real world. Business objects typically reside in the middle layer or business logic layer and are an important component of the digitalization-digital architecture-business architecture-business object-data model-data asset chain. Business objects have the following characteristics: ① Data and behavior integration: Business objects not only contain data (such as attributes) but also behaviors (such as methods) that operate on this data; ② Reusability: Business objects can be reused by multiple systems or applications, improving development efficiency and interoperability between systems; ③ Business logic encapsulation: Business objects encapsulate business logic, allowing developers to focus more on the implementation of business logic rather than underlying data processing.

[0021] Step S4: Using the page designer of the no-code development platform, drag and drop page components from the component repository to create the system interface of the security points management system. Step S5: Using the service modeling tool of the no-code development platform, define services and declare service interfaces for the technical components, data models, and business objects; in specific implementation, the defined services can be re-arranged to form a new aggregated service. Step S6: Bind the service to the page components of the system interface through the page event definer of the no-code development platform, and define the interaction logic of each page component to form the page form used by the end user. Step S7: Using the deployment tool of the no-code development platform, package the system interface and services into a security points management system, set the security verification mechanism of the security points management system, and deploy the security points management system to the container orchestration system based on the input deployment command. The verification process of the security verification mechanism is as follows: The access request from the security points management system is parsed to obtain ciphertext data, signature data, timestamp, and MAC value. The calculation process for the ciphertext data is as follows: First-level encrypted data is obtained by encrypting the account password, device ID, and public key used to verify the signature data using the IDEA algorithm; second-level encrypted data is obtained by mapping each character of the first-level encrypted data using a preset first mapping rule; third-level encrypted data is obtained by encrypting the second-level encrypted data using the RSA algorithm; fourth-level encrypted data is obtained by mapping each character of the third-level encrypted data using a preset second mapping rule; fifth-level encrypted data is obtained by encrypting the fourth-level encrypted data using the ECDSA algorithm; sixth-level encrypted data is obtained by mapping each character of the fifth-level encrypted data using a preset third mapping rule; and finally, ciphertext data is obtained by encrypting the sixth-level encrypted data using the 3DES algorithm. The MAC value is calculated by performing MAC calculation on the ciphertext data, signature data, and timestamp. After verifying the integrity of the ciphertext data, signature data, and timestamp using the MAC value, and then verifying the validity of the data using the timestamp, the ciphertext data is decrypted to obtain the account password, device ID, and public key. The signature data is then verified using the public key. The device ID is then verified for validity using a preset device management table. Finally, the account password is verified for validity using a preset password management table.

[0022] The access request is configured to carry encrypted data, signature data, a timestamp, and a MAC value. The encrypted data is obtained by multi-level encryption of the account password, device ID, and the public key used to verify the signature data. Subsequent verification can be performed based on the MAC value for integrity, the timestamp for timeliness, the public key for signature verification, the device ID for first-level legitimacy verification, and the account password for second-level legitimacy verification. The IDEA algorithm is used to encrypt the account password, device ID, and public key to obtain first-level encrypted data. A preset first mapping rule is used to map each character of the first-level encrypted data to obtain second-level encrypted data. The RSA algorithm is used to encrypt the second-level encrypted data to obtain third-level encrypted data. A preset second mapping rule is then used to further encrypt the data. The characters of the three-level encrypted data are mapped to obtain the four-level encrypted data. The four-level encrypted data is then encrypted using the ECDSA algorithm to obtain the five-level encrypted data. The characters of the five-level encrypted data are then mapped using a preset third mapping rule to obtain the six-level encrypted data. Finally, the six-level encrypted data is encrypted using the 3DES algorithm to obtain the ciphertext data. If the corresponding encryption algorithm or mapping rule is unknown, the ciphertext data cannot be cracked. At least 12 security measures are taken (IDEA algorithm, first mapping rule, RSA algorithm, second mapping rule, ECDSA algorithm, third mapping rule, 3DES algorithm, MAC value, timestamp, public key, device ID, account password), thereby greatly improving the security of the security points management system.

[0023] In step S3, the creation of the data model for the security points management system using the data modeling tool of the no-code development platform specifically involves: Define a data source, including database type and connection address information, using the data source definition tool of a no-code development platform; the connection address information includes at least IP address, port, and database name; the database type is MySQL, SQL Server, or Oracle. Based on the aforementioned security points management rules, an ER diagram is output using a database design tool; Using the data modeling tools of a no-code development platform, the ER diagram (Entity-Relationship Diagram) is converted into a data model including a logical model and a physical model based on database paradigms (a set of rules and guidelines followed when using relational databases, aimed at reducing data redundancy and improving data consistency and integrity). The data model is then published to the data source, and the metadata of the data model is stored in a pre-created metadata table.

[0024] Step S4 specifically involves: Using the page designer of a no-code development platform, page components from the component repository are dragged and dropped in a drag-and-drop interactive manner to lay out and style each component. Display parameters, including the layout and style, are stored in HTML (a standard markup language for creating web pages) and CSS (for describing the rendering of HTML or XML documents) formats to create a system interface for the security points management system, comprising several sub-interfaces. A unique interface identifier (GUID) is generated for each sub-interface to complete the creation of the system interface for the security points management system. When a user initiates a page request through the security points management system, the unique interface identifier is included. The pre-written page parsing interface of the security points management system retrieves the corresponding page layout and style data from the database based on the unique interface identifier and returns it to the front-end browser.

[0025] In step S5, the service definition includes at least the definitions of service data objects, service input parameters, service output parameters, and business logic. The service input parameters and service output parameters can be business objects or multiple independent formal parameters.

[0026] Step S6 specifically involves: By using the page event definer of the no-code development platform, the service is bound to the page components of the system interface, and the interaction logic of each page component is defined, including at least the triggering event and the associated behavior. In step S7, the container orchestration system is Kubernetes, which is used for the automated deployment, scaling, and management of containerized applications. The decryption process for the encrypted data is as follows: The ciphertext data is decrypted using the 3DES algorithm to obtain level six encrypted data. Each character of the level six encrypted data is mapped using a preset third mapping rule to obtain level five encrypted data. The level five encrypted data is decrypted using the ECDSA algorithm to obtain level four encrypted data. Each character of the level four encrypted data is mapped using a preset second mapping rule to obtain level three encrypted data. The level three encrypted data is decrypted using the RSA algorithm to obtain level two encrypted data. Each character of the level two encrypted data is mapped using a preset first mapping rule to obtain level one encrypted data. The level one encrypted data is then decrypted using the IDEA algorithm to obtain the account password, device ID, and public key. A preferred embodiment of the no-code security points management system development device of the present invention includes the following modules: The security points management rule parsing module is used to create a security points management rule and parse the security points management rule using a UML (Unified Modeling Language) tool (such as Visio) to obtain a component diagram including several management nodes; The technical component creation module is used to encapsulate each of the management nodes into a corresponding technical component. After setting the configuration information of each technical component through XML (Extensible Markup Language), including at least component attributes, input parameters, output parameters, event descriptions, and behavior descriptions, the technical components are entered into the component repository of the no-code development platform. The component repository is equipped with components for data query, data update, data insertion, etc. The data model and business object creation module is used to create the data model and business objects of the security points management system based on the security points management rules, using the data modeling tools of the no-code development platform. The no-code development platform is a technology platform that allows software development without writing code. Through a graphical interface and pre-built modules, it enables non-professional programmers to quickly build applications, providing rich functions and tools, including online form design, report generation, data visualization, etc., aiming to lower the threshold for software development and improve development efficiency. A Business Object (BO) is an abstract representation of information related to people, events, things, and places. It is a mapping of actual business operations in the information world, a component for data retrieval and processing, and a software abstraction of the real world. Business objects typically reside in the middle layer or business logic layer and are an important component of the digitalization-digital architecture-business architecture-business object-data model-data asset chain. Business objects have the following characteristics: ① Data and behavior integration: Business objects not only contain data (such as attributes) but also behaviors (such as methods) that operate on this data; ② Reusability: Business objects can be reused by multiple systems or applications, improving development efficiency and interoperability between systems; ③ Business logic encapsulation: Business objects encapsulate business logic, allowing developers to focus more on the implementation of business logic rather than underlying data processing.

[0027] The system interface creation module is used to create the system interface of the security points management system by dragging and dropping page components from the component repository through the page designer of the no-code development platform. The service definition module is used to define services and declare service interfaces for the technical components, data models, and business objects through the service modeling tools of the no-code development platform. In specific implementation, the defined services can be re-arranged to form a new aggregated service. The interaction logic definition module is used to bind the service to the page components of the system interface through the page event definer of the no-code development platform, and define the interaction logic of each page component to form the page form used by the end user. The publishing module is used to package the system interface and services into a security points management system using the publishing tools of the no-code development platform, set the security verification mechanism of the security points management system, and publish the security points management system to the container orchestration system based on the input publishing command. The verification process of the security verification mechanism is as follows: The access request from the security points management system is parsed to obtain ciphertext data, signature data, timestamp, and MAC value. The calculation process for the ciphertext data is as follows: First-level encrypted data is obtained by encrypting the account password, device ID, and public key used to verify the signature data using the IDEA algorithm; second-level encrypted data is obtained by mapping each character of the first-level encrypted data using a preset first mapping rule; third-level encrypted data is obtained by encrypting the second-level encrypted data using the RSA algorithm; fourth-level encrypted data is obtained by mapping each character of the third-level encrypted data using a preset second mapping rule; fifth-level encrypted data is obtained by encrypting the fourth-level encrypted data using the ECDSA algorithm; sixth-level encrypted data is obtained by mapping each character of the fifth-level encrypted data using a preset third mapping rule; and finally, ciphertext data is obtained by encrypting the sixth-level encrypted data using the 3DES algorithm. The MAC value is calculated by performing MAC calculation on the ciphertext data, signature data, and timestamp. After verifying the integrity of the ciphertext data, signature data, and timestamp using the MAC value, and then verifying the validity of the data using the timestamp, the ciphertext data is decrypted to obtain the account password, device ID, and public key. The signature data is then verified using the public key. The device ID is then verified for validity using a preset device management table. Finally, the account password is verified for validity using a preset password management table.

[0028] The access request is configured to carry encrypted data, signature data, a timestamp, and a MAC value. The encrypted data is obtained by multi-level encryption of the account password, device ID, and the public key used to verify the signature data. Subsequent verification can be performed based on the MAC value for integrity, the timestamp for timeliness, the public key for signature verification, the device ID for first-level legitimacy verification, and the account password for second-level legitimacy verification. The IDEA algorithm is used to encrypt the account password, device ID, and public key to obtain first-level encrypted data. A preset first mapping rule is used to map each character of the first-level encrypted data to obtain second-level encrypted data. The RSA algorithm is used to encrypt the second-level encrypted data to obtain third-level encrypted data. A preset second mapping rule is then used to further encrypt the data. The characters of the three-level encrypted data are mapped to obtain the four-level encrypted data. The four-level encrypted data is then encrypted using the ECDSA algorithm to obtain the five-level encrypted data. The characters of the five-level encrypted data are then mapped using a preset third mapping rule to obtain the six-level encrypted data. Finally, the six-level encrypted data is encrypted using the 3DES algorithm to obtain the ciphertext data. If the corresponding encryption algorithm or mapping rule is unknown, the ciphertext data cannot be cracked. At least 12 security measures are taken (IDEA algorithm, first mapping rule, RSA algorithm, second mapping rule, ECDSA algorithm, third mapping rule, 3DES algorithm, MAC value, timestamp, public key, device ID, account password), thereby greatly improving the security of the security points management system.

[0029] In the data model and business object creation module, the creation of the data model for the security points management system using the data modeling tool of the no-code development platform specifically involves: Define a data source, including database type and connection address information, using the data source definition tool of a no-code development platform; the connection address information includes at least IP address, port, and database name; the database type is MySQL, SQL Server, or Oracle. Based on the aforementioned security points management rules, an ER diagram is output using a database design tool; Using the data modeling tools of a no-code development platform, the ER diagram (Entity-Relationship Diagram) is converted into a data model including a logical model and a physical model based on database paradigms (a set of rules and guidelines followed when using relational databases, aimed at reducing data redundancy and improving data consistency and integrity). The data model is then published to the data source, and the metadata of the data model is stored in a pre-created metadata table.

[0030] The system interface creation module is specifically used for: Using the page designer of a no-code development platform, page components from the component repository are dragged and dropped in a drag-and-drop interactive manner to lay out and style each component. Display parameters, including the layout and style, are stored in HTML (a standard markup language for creating web pages) and CSS (for describing the rendering of HTML or XML documents) formats to create a system interface for the security points management system, comprising several sub-interfaces. A unique interface identifier (GUID) is generated for each sub-interface to complete the creation of the system interface for the security points management system. When a user initiates a page request through the security points management system, the unique interface identifier is included. The pre-written page parsing interface of the security points management system retrieves the corresponding page layout and style data from the database based on the unique interface identifier and returns it to the front-end browser.

[0031] In the service definition module, the service definition includes at least the definitions of service data objects, service input parameters, service output parameters, and business logic. The service input parameters and service output parameters can be business objects or multiple independent formal parameters.

[0032] The interaction logic definition module is specifically used for: By using the page event definer of the no-code development platform, the service is bound to the page components of the system interface, and the interaction logic of each page component is defined, including at least the triggering event and the associated behavior. In the deployment module, the container orchestration system is Kubernetes, which is used for the automated deployment, scaling, and management of containerized applications. The decryption process for the encrypted data is as follows: The ciphertext data is decrypted using the 3DES algorithm to obtain level six encrypted data. Each character of the level six encrypted data is mapped using a preset third mapping rule to obtain level five encrypted data. The level five encrypted data is decrypted using the ECDSA algorithm to obtain level four encrypted data. Each character of the level four encrypted data is mapped using a preset second mapping rule to obtain level three encrypted data. The level three encrypted data is decrypted using the RSA algorithm to obtain level two encrypted data. Each character of the level two encrypted data is mapped using a preset first mapping rule to obtain level one encrypted data. The level one encrypted data is then decrypted using the IDEA algorithm to obtain the account password, device ID, and public key. In summary, the advantages of this invention are as follows: 1. By creating security points management rules, and using UML tools to parse these rules to obtain a component diagram containing several management nodes, each management node is encapsulated as a corresponding technical component. After setting configuration information for each technical component, including at least component attributes, input parameters, output parameters, event descriptions, and behavior descriptions, each technical component is entered into the component repository of the no-code development platform. Next, based on the security points management rules, the data model and business objects of the security points management system are created using the data modeling tools of the no-code development platform. The page designer uses a drag-and-drop interaction to drag page components from the component repository to create the system interface of the security points management system. Service modeling tools are used to define services and declare service interfaces for the technical components, data model, and business objects. The page event definer binds services to the page components of the system interface and defines each page group. The interaction logic of the components is then packaged into a security points management system using a publishing tool. After setting the security verification mechanism of the security points management system, it is published to the container orchestration system based on the input publishing command. That is, technical components created based on security points management rules are entered into the component repository of the no-code development platform. The no-code development platform develops the security points management system based on the technical components in a WYSIWYG manner, without requiring programmers with computer science backgrounds. Furthermore, the technical components can be extended as needed. Before the security points management system is published, a security verification mechanism including integrity verification, timeliness verification, signature verification, first legality verification, and second legality verification is set to prevent unauthorized access to the security points management system, thereby greatly improving the convenience, efficiency, and scalability of the security points management system development, and greatly enhancing the security of the security points management system.

[0033] 2. By setting the access request to carry encrypted data, signature data, timestamp, and MAC value, the encrypted data is obtained by multi-level encryption of the account password, device ID, and public key used to verify the signature data. Subsequent verification can be performed based on the MAC value for integrity, the timestamp for timeliness, the public key for signature verification, the device ID for first-level legitimacy verification, and the account password for second-level legitimacy verification. The account password, device ID, and public key are encrypted using the IDEA algorithm to obtain first-level encrypted data. Each character of the first-level encrypted data is mapped using a preset first mapping rule to obtain second-level encrypted data. The second-level encrypted data is then encrypted using the RSA algorithm to obtain third-level encrypted data, which is then further encrypted using a preset second mapping rule. The system maps each character of the Level 3 encrypted data to obtain Level 4 encrypted data. Level 4 encrypted data is then encrypted using the ECDSA algorithm to obtain Level 5 encrypted data. Finally, Level 5 encrypted data is encrypted using a preset third mapping rule to obtain Level 6 encrypted data. The Level 6 encrypted data is then encrypted using the 3DES algorithm to obtain ciphertext data. Without knowing the corresponding encryption algorithm or mapping rule, the ciphertext data cannot be cracked. At least 12 security measures are implemented (IDEA algorithm, first mapping rule, RSA algorithm, second mapping rule, ECDSA algorithm, third mapping rule, 3DES algorithm, MAC value, timestamp, public key, device ID, and account password), thus greatly enhancing the security of the security points management system.

[0034] While specific embodiments of the present invention have been described above, those skilled in the art should understand that the specific embodiments described are merely illustrative and not intended to limit the scope of the present invention. Equivalent modifications and variations made by those skilled in the art in accordance with the spirit of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A code-free safety points management system development method, characterized by: The steps include: Step S1, creating a safety point management rule, and parsing the safety point management rule by using a UML tool to obtain a component diagram including a plurality of management nodes; Step S2: Encapsulate each of the management nodes into a corresponding technical component, set the configuration information of each of the technical components including at least component attributes, input parameters, output parameters, event descriptions, and behavior descriptions through XML, and then enter each of the technical components into the component warehouse of the codeless development platform; Step S3: Based on the security points management rules, create a data model and business objects of the security points management system through a data modeling tool of the codeless development platform; Step S4: dragging the page components in the component warehouse in an interactive drag-and-drop manner through the page designer of the codeless development platform to create a system interface of the security points management system; Step S5: Using the service modeling tool of the codeless development platform, perform service definition and service interface declaration for the technical components, data models, and business objects; Step S6: Bind the service to the page components of the system interface through the page event definer of the codeless development platform, and define the interaction logic of each of the page components; Step S7: Package the system interface and services into a security points management system through the publishing tool of the codeless development platform, set the security verification mechanism of the security points management system, and then publish the security points management system to the container orchestration system based on the input publishing instructions.

2. A code-free security points management system development method as claimed in claim 1, characterized in that: In step S3, the data model of the security points management system created by the data modeling tool of the codeless development platform is specifically: Defining a data source including a database type and connection address information through a data source definition tool of a codeless development platform; the connection address information includes at least an IP address, a port, and a database name; Based on the safety score management rules, outputting the ER diagram through a database design tool; Through the data modeling tool of the codeless development platform, the ER diagram is converted into a data model including a logical model and a physical model based on the database paradigm, the data model is published to the data source, and the metadata of the data model is stored in a pre-created metadata table.

3. A code-free security points management system development method as claimed in claim 1, characterized in that: The step S4 is specifically as follows: Through the page designer of the codeless development platform, the page components in the component repository are dragged in an interactive manner to layout each of the page components, set the style of each of the page components, and store the display parameters including the layout and style in HTML format and CSS format to create a system interface of the security points management system including several sub-interfaces, and generate a unique interface identifier for each of the sub-interfaces to complete the creation of the system interface of the security points management system.

4. A code-free security points management system development method as claimed in claim 1, characterized in that: In step S5, the service definition at least includes the definition of service data objects, service input parameters, service output parameters and business logic.

5. A code-free security points management system development method as claimed in claim 1, characterized in that: The step S6 is specifically as follows: By using the page event definer of the codeless development platform, the service is bound to the page components of the system interface, and the interaction logic of each of the page components is defined, including at least a triggering event and associated behaviors; In step S7, the container orchestration system is kubernetes; The verification process of the security verification mechanism is specifically as follows: Parse the access request of the security points management system to obtain ciphertext data, signature data, timestamp and MAC value; the calculation process of the ciphertext data is: encrypt the account password, device ID, and the public key used to verify the signature data by the IDEA algorithm to obtain the first-level encrypted data, map each character of the first-level encrypted data by the preset first mapping rule to obtain the second-level encrypted data, encrypt the second-level encrypted data by the RSA algorithm to obtain the third-level encrypted data, map each character of the third-level encrypted data by the preset second mapping rule to obtain the fourth-level encrypted data, encrypt the fourth-level encrypted data by the ECDSA algorithm to obtain the fifth-level encrypted data, map each character of the fifth-level encrypted data by the preset third mapping rule to obtain the sixth-level encrypted data, and encrypt the sixth-level encrypted data by the 3DES algorithm to obtain the ciphertext data; the MAC value is obtained by performing MAC calculation on the ciphertext data, signature data and timestamp; After the integrity of the ciphertext data, signature data and timestamp is checked by the MAC value, the timeliness is checked by the timestamp, and then the ciphertext data is decrypted to obtain the account password, device ID and public key, and then the signature data is verified by the public key, and the first legitimacy check is performed on the device ID through the preset device management table, and finally the second legitimacy check is performed on the account password through the preset password management table; The decryption process of the ciphertext data is: The ciphertext data is decrypted by the 3DES algorithm to obtain level 6 encrypted data, each character of the level 6 encrypted data is mapped by the preset third mapping rule to obtain level 5 encrypted data, the level 5 encrypted data is decrypted by the ECDSA algorithm to obtain level 4 encrypted data, each character of the level 4 encrypted data is mapped by the preset second mapping rule to obtain level 3 encrypted data, the level 3 encrypted data is decrypted by the RSA algorithm to obtain level 2 encrypted data, each character of the level 2 encrypted data is mapped by the preset first mapping rule to obtain level 1 encrypted data, and the level 1 encrypted data is decrypted by the IDEA algorithm to obtain the account password, device ID and public key.

6. A code-free safety points management system development device, characterized in that: Includes the following modules: A safety point management rule parsing module is used to create a safety point management rule and parse the safety point management rule through a UML tool to obtain a component diagram including several management nodes; A technical component creation module, used to encapsulate each of the management nodes into a corresponding technical component, and after setting the configuration information of each of the technical components including at least component attributes, input parameters, output parameters, event descriptions, and behavior descriptions through XML, enter each of the technical components into the component warehouse of the codeless development platform; A data model and business object creation module, which is used to create a data model and business objects of the security points management system through a data modeling tool of a codeless development platform based on the security points management rules; A system interface creation module, used to drag page components in the component warehouse in a drag-and-drop interactive manner through a page designer of a codeless development platform to create a system interface of a security points management system; A service definition module, used to perform service definition and service interface declaration for the technical components, data models, and business objects through a service modeling tool of a codeless development platform; An interactive logic definition module, used to bind the service to the page components of the system interface through the page event definer of the codeless development platform, and define the interactive logic of each of the page components; The publishing module is used to package the system interface and services into a security points management system through the publishing tool of the codeless development platform, set the security verification mechanism of the security points management system, and then publish the security points management system to the container orchestration system based on the input publishing instructions.

7. A code-free security points management system development device as claimed in claim 6, characterized in that: In the data model and business object creation module, the data model of the security points management system created by the data modeling tool of the codeless development platform is specifically: Defining a data source including a database type and connection address information through a data source definition tool of a codeless development platform; the connection address information includes at least an IP address, a port, and a database name; Based on the safety score management rules, outputting the ER diagram through a database design tool; Through the data modeling tool of the codeless development platform, the ER diagram is converted into a data model including a logical model and a physical model based on the database paradigm, the data model is published to the data source, and the metadata of the data model is stored in a pre-created metadata table.

8. A code-free security points management system development device as claimed in claim 6, characterized in that: The system interface creation module is specifically used for: Through the page designer of the codeless development platform, the page components in the component repository are dragged in an interactive manner to layout each of the page components, set the style of each of the page components, and store the display parameters including the layout and style in HTML format and CSS format to create a system interface of the security points management system including several sub-interfaces, and generate a unique interface identifier for each of the sub-interfaces to complete the creation of the system interface of the security points management system.

9. A code-free security points management system development device as claimed in claim 6, characterized in that: In the service definition module, the service definition at least includes definitions of service data objects, service input parameters, service output parameters and business logic.

10. A code-free security points management system development device as claimed in claim 6, characterized in that: The interaction logic definition module is specifically used for: By using the page event definer of the codeless development platform, the service is bound to the page components of the system interface, and the interaction logic of each of the page components is defined, including at least a triggering event and associated behaviors; In the publishing module, the container orchestration system is kubernetes; The verification process of the security verification mechanism is specifically as follows: Parse the access request of the security points management system to obtain ciphertext data, signature data, timestamp and MAC value; the calculation process of the ciphertext data is: encrypt the account password, device ID, and the public key used to verify the signature data by the IDEA algorithm to obtain the first-level encrypted data, map each character of the first-level encrypted data by the preset first mapping rule to obtain the second-level encrypted data, encrypt the second-level encrypted data by the RSA algorithm to obtain the third-level encrypted data, map each character of the third-level encrypted data by the preset second mapping rule to obtain the fourth-level encrypted data, encrypt the fourth-level encrypted data by the ECDSA algorithm to obtain the fifth-level encrypted data, map each character of the fifth-level encrypted data by the preset third mapping rule to obtain the sixth-level encrypted data, and encrypt the sixth-level encrypted data by the 3DES algorithm to obtain the ciphertext data; the MAC value is obtained by performing MAC calculation on the ciphertext data, signature data and timestamp; After the integrity of the ciphertext data, signature data and timestamp is checked by the MAC value, the timeliness is checked by the timestamp, and then the ciphertext data is decrypted to obtain the account password, device ID and public key, and then the signature data is verified by the public key, and the first legitimacy check is performed on the device ID through the preset device management table, and finally the second legitimacy check is performed on the account password through the preset password management table; The decryption process of the ciphertext data is: The ciphertext data is decrypted by the 3DES algorithm to obtain level 6 encrypted data, each character of the level 6 encrypted data is mapped by the preset third mapping rule to obtain level 5 encrypted data, the level 5 encrypted data is decrypted by the ECDSA algorithm to obtain level 4 encrypted data, each character of the level 4 encrypted data is mapped by the preset second mapping rule to obtain level 3 encrypted data, the level 3 encrypted data is decrypted by the RSA algorithm to obtain level 2 encrypted data, each character of the level 2 encrypted data is mapped by the preset first mapping rule to obtain level 1 encrypted data, and the level 1 encrypted data is decrypted by the IDEA algorithm to obtain the account password, device ID and public key.

Images