Multi-system hierarchical management and system based on RSA encryption algorithm

Abstract

The application discloses a multi-system hierarchical management method and system based on RSA encryption algorithm. The method is used for information protection in a satellite system. The system comprises a front end, a superior node, an inferior node, a node tree and a database. The method comprises the following steps: establishing a middle station service module for serving the system, wherein the middle station service module is responsible for identity verification and filtering of all requests accessing the system; introducing a hierarchical management module in the middle station service module, wherein the hierarchical management module is responsible for providing node information of the system, registering between the system nodes and providing information support for other modules of the system. The hierarchical management module in the application supports the middle station service module. The node tree is encrypted by the RS256 algorithm, so that each parent node has a strong trusted relationship with its child nodes. In the entire node tree, any access is secure.

Description

Technical Field

[0001] This invention belongs to the field of encrypted communication information technology, specifically relating to a hierarchical management method and system for multiple systems based on the RSA encryption algorithm. Background Technology

[0002] With the development of the times, satellite communication technology has become increasingly mature, and its application scope has become wider and wider, performing increasingly well in disaster relief and communication in areas without signal. Currently, satellite systems support both FDMA and TDMA. In terms of satellite resource management, the trustworthiness of users and resources across multiple systems is particularly important for the security of the entire system tree. Existing management systems have not considered security issues, and even in intranet environments, problems such as information leakage can occur.

[0003] In existing products, the registration information between multi-level systems is completely open and transparent. By simply capturing packets and forging information to gain access, it is possible to directly obtain node information and user data. Such network intrusion is very easy to accomplish. Due to the complexity of satellite management of multi-level systems, there is no highly reliable hierarchical management implementation method. Summary of the Invention

[0004] Purpose of the invention: To overcome the shortcomings of existing technologies, this invention provides a hierarchical management method and system for multiple systems based on the RSA encryption algorithm. Under the encryption of the RS256 algorithm, each parent node has a strong trust relationship with its child nodes. Any access within the entire node tree is secure, and any external request will not be decrypted by RS256, thus protecting data from accidental or malicious damage, alteration, or leakage.

[0005] Technical Solution: To solve the above-mentioned technical problems, this invention provides a multi-system hierarchical management system based on the RSA encryption algorithm for the protection of information in satellite systems. The system includes at least: The middleware service module verifies the information of external users; At least one root node is connected to the middleware service module; At least one subordinate node is connected to the middleware service module; several root nodes and subordinate nodes are connected to form the node tree of the system; The hierarchical management module includes at least a first management module and a second management module, wherein the first management module is connected to the lower-level nodes and the second management module is connected to the root node. The hierarchical management module embeds an encryption algorithm to encrypt the information flowing between the root node and the lower-level nodes.

[0006] Furthermore, the hierarchical management module includes at least: Non-root nodes register with their superior units to send registration requests to the root node; The root node is the node allocation and management unit, used to add or delete subordinate nodes; A real-time system node liveness verification unit is used to monitor the status of the node tree.

[0007] Furthermore, the middleware service module includes at least: The backend interface information integration unit is used to filter information; The configuration management unit for system nodes is used to configure node attributes; The message event aggregation and distribution unit, used to collect and organize logs; The access information source verification unit is used to verify the access information.

[0008] A hierarchical management method for inter-system systems based on the RSA encryption algorithm, implemented using any of the above-mentioned hierarchical management systems based on the RSA encryption algorithm, includes the following steps: S1. The system starts up and verifies the node information within the system. The hierarchical management module then enables the hierarchical management function. S2. When a user logs into the system, the middleware service module verifies and obtains the configuration information of the user's subordinate nodes and encrypts the configuration information. The hierarchical management module uses the private key to decrypt and check the configuration information, enabling the subordinate nodes to initiate registration with the root node. The root node can add subordinate nodes and complete the registration. S3. Based on S2, information of subordinate nodes can be deleted from the root node; S4. In S2, when the decrypted configuration information is not related to the user, the hierarchical management module uses the public key to encrypt it and sends it to the front end.

[0009] Furthermore, the steps for a lower-level node to initiate registration with the root node in S2 include: S21. External users log in to the system after authentication. The middleware service module obtains the configuration information of the user's subordinate nodes and sends it to the first hierarchical management module. S22. The first hierarchical management module obtains the root node information, and the lower-level nodes initiate a registration application to the root node; S23. After the application is confirmed by the middleware service module, the second hierarchical management module stores the user's configuration information; the configuration information includes at least node ID, node name, node IP, node port, and node public key.

[0010] Furthermore, the process of adding subordinate nodes to the root node includes the following steps: S24. The root node selects the corresponding part of the configuration information in S23, and writes the node ID into the node tree through the second hierarchical management module; S25. The second hierarchical management module encrypts the root node information using the public key of the lower-level node, calls the deletion callback method of the lower-level node, and decrypts and verifies it through the middle platform service module. S26. Update the registration success information to the network control of the lower-level node. After the update is completed, change the status of the lower-level node to registration success in the root node.

[0011] Furthermore, after the lower-level node is successfully registered as described in S26, the process of the root node deleting the lower-level node includes the following steps: S27. The second hierarchical management module deletes the lower-level node from the node tree; S28. The second hierarchical management module encrypts the root node information using the public key of the lower-level node, calls the deletion callback method of the lower-level node, and the lower-level node decrypts and verifies the information through the middleware service module. S29. Delete all root node information in the network control of the lower-level node; and delete the lower-level node information in the root node.

[0012] Furthermore, when the subordinate node has the attribute of a root node, the root node has the right to refuse the registration of the subordinate node.

[0013] Furthermore, it also includes the lower-level node obtaining node tree information, specifically through the following steps: S261. When a lower-level node has the attribute of a root node, the lower-level node obtains the node tree information. S262. When a lower-level node does not have the attribute of a root node, the node tree information is obtained through the middle platform service module and forwarded to the first hierarchical management module of the lower-level node to obtain the node tree information.

[0014] Beneficial effects: Compared with the prior art, the present invention has the following advantages: The hierarchical management module in the present invention supports the middleware service module. Under the encryption of the node tree by the RS256 algorithm, each parent node has a strong trust relationship with its child nodes. In the entire node tree, any access is secure, and any external request will not be decrypted by RS256, thus protecting the data from being damaged, altered, or leaked due to accidental or malicious reasons. Attached Figure Description

[0015] Figure 1 This is a flowchart of the workflow in this invention.

[0016] Figure 2 This is a flowchart of the application process for lower-level nodes in this invention.

[0017] Figure 3 This is a flowchart of adding a subordinate node to the root node in this invention.

[0018] Figure 4 This is a flowchart illustrating the process of deleting a lower-level node from a root node in this invention. Detailed Implementation

[0019] The invention will now be further described with reference to the accompanying drawings.

[0020] Example 1 like Figure 1 As shown, this embodiment is a hierarchical management method for multiple systems based on the RSA encryption algorithm. This method is used to protect information in a satellite system. The system includes at least a middleware service module, at least one root node, at least one subordinate node, a node tree, and a database. The root node and subordinate nodes are connected to form the node tree of the system. In this embodiment, the middleware service includes a front-end and a back-end.

[0021] Establish a middleware service module on the system to serve the system. The middleware service module is responsible for verifying the identity and filtering all requests that access the system. A hierarchical management module is introduced into the middleware service module. The hierarchical management module is responsible for providing node information of the system, the registration function between system nodes, and the information support provided by other modules to the system.

[0022] This invention consists of two parts: a middleware service module and a hierarchical management module. Both provide services to the system. The middleware service module is responsible for verifying and filtering the identity of all requests accessing the system, while the hierarchical management module is responsible for providing system node information, facilitating registration between system nodes, and providing inter-system information support for other modules.

[0023] The middleware service module includes at least: a backend interface information integration unit, a system node configuration management unit, a message event aggregation and distribution unit, and an access information source verification unit.

[0024] The hierarchical management module is responsible for providing system node information and the registration function between system nodes. It provides information support between systems for other modules and mainly has the following functions: non-root nodes registering to the upper level, root nodes' node allocation and management functions, and real-time system node verification mechanism.

[0025] In this embodiment, backend interface information aggregation: In satellite systems with a large amount of data, the filtering of interface information is particularly important. Much of the data required by various system modules is not what users need to see. In order to allow users to see the most critical data, the middleware service module needs to filter a large amount of information before pushing it to the frontend for display.

[0026] System node configuration management: When the system starts up, it will determine whether the node is a root node and whether hierarchical management is enabled based on the configuration in the configuration management. When the hierarchical management module is enabled, it is allowed to distinguish whether it is a root node. When the hierarchical management module is disabled, the system node is used as a subsystem in this invention. When a subsystem is enabled for hierarchical management and is the root node, it will not be allowed to register upwards or poll in reverse, and the root node management functions will be enabled for it. Conversely, when a subsystem is not the root node, the root node-related management functions will be disabled, upward registration will be enabled, and reverse polling will be allowed.

[0027] Message event aggregation and distribution function: During the process of users using the system, the system will generate a large number of logs, reminders, resource warnings, etc. The number of logs will increase with the increase of users. In order to accurately remind users which ones they need to pay attention to, the middle platform service module will collect all logs and organize them. Then, it can push relevant information based on the currently logged-in user and user permissions.

[0028] Access source verification: In an interactive network environment, various data packets are transmitted. To prevent malicious access and acquisition of critical system data, all access is verified using RSA at the middleware service module layer. When the system starts, an RS256 asymmetric public and private key is generated, which is unique throughout the system's lifecycle. The public keys of all parent and child nodes can be shared in the node tree. Access to the system node is made through the public key of a certain node. The system node can use its own private key to decrypt the data. Only when decryption is successful and the system node information of the decrypted data packet exists in the node tree will the request continue to be executed. If any link fails, the request will be rejected.

[0029] Example 2 The hierarchical management module in this embodiment includes at least: a non-root node registration unit, a root node allocation and management unit, and a real-time system node activation unit. Through the above functions, the hierarchical management module can realize its work content.

[0030] Among them, the non-root node registration function to the upper level: when the subsystem has enabled the hierarchical management module and is a non-root node, the subsystem will be allowed to send requests to the node tree. It only needs to configure the reachable root node network address and port, and then register to transmit the node information and public key of this level to the node tree.

[0031] Root node allocation and management functions: When the subsystem has the hierarchical management module enabled and is the root node, the subsystem will enable node management functions. In the same group of node trees, there will only be one root node. The root node mainly has the following functions: 1. Assigning registered nodes: After a non-root node initiates registration, the root node has the right to assign the node to any position in the node tree based on the node information in the registration list, and to make all information available in the node tree; 2. Reject registration of subordinate nodes: After a non-root node initiates registration, the root node has the right to reject the registration request of that node, and there will be no communication with that node in the node tree; 3. Delete a node: When a node is working in the node tree, the root node has the right to remove it from the node tree and reclaim all issued resources, regardless of the circumstances. 4. Obtain node data: The root node has the right to view the association of all nodes in the current node tree, as well as the health status of all nodes.

[0032] Real-time system node liveness verification mechanism: During the lifecycle of a subsystem, various changes will occur. In order to monitor the liveness status of the subsystem in the face of these changes, the root node and its subordinate nodes have different mechanisms to check the status of the node tree at any time.

[0033] Root node: It checks the status of each node by polling all its subordinate nodes and sending requests to all subordinate nodes, and finally modifies the node status based on all the node status codes.

[0034] Non-root nodes: Sometimes, due to network fluctuations, when a node is added or deleted by a higher-level node, the state is not correctly synchronized to the lower-level nodes. This causes the lower-level nodes to be unsure of their own state in the node tree. In this case, the reverse polling function in the hierarchical management module will send the non-root node to request the node tree list from the root node with encrypted node information. When the root node receives the request and decrypts it, it will determine whether the non-root node's node information is in the node tree. The non-root node will then synchronize and update its own state based on this result.

[0035] Example 3 Based on Examples 1 and 2, such as Figures 2 to 3 As shown, the workflow for the hierarchical management module to apply for registration at lower-level nodes includes the following steps: First is user login. After the user enters their username and password on the front end, the front end accesses the login interface of the middle platform service module. The middle platform performs identity verification and returns a token containing user information to the front end after successful verification. At this point, the user has successfully logged in. Then, the user configures the node. After the user enters the node information on the front end, the front end pushes the node information to the middle platform service module, and the middle platform service module stores the node information in the database. User registration is performed, where lower-level nodes can initiate registration with the root node. Based on node information, the lower-level node forwards the user-configured registration information to the first-level management module of the lower-level node through the middleware service module. After obtaining the root node information, the first-level management module then requests the middleware service module of the root node. After the middleware of the root node confirms the request information, it forwards it to the second-level management module of the root node, which stores the information of the lower-level node to be registered in the lower-level request list. The fields include node ID, node name, node IP, node port, and node public key.

[0036] Example 4 Based on the registration request from the lower-level node to the root node in Embodiment 3, the process of the root node adding the lower-level node after the lower-level node initiates registration with the root node in this embodiment includes: The root node displays a list of all registered subordinate nodes. The root node selects the subordinate node ID and the parent node ID to be registered, requests the root node's middleware service module, and then the root node's second-level management module writes the subordinate node ID into the node tree. The root node information is then encrypted using the subordinate node's public key. The subordinate node's registration callback method is then called. The subordinate node's middleware service module decrypts and verifies the information, updating the registration success message to the subordinate node's network controller. Once the update is complete, the root node changes the subordinate node's status to "registered successfully."

[0037] Example 5 Based on Example 4, when a child node is added to the root node, and when the root node needs to delete a child node, such as... Figure 4 As shown, the following process is performed: The second-level management module of the root node deletes the lower-level node from the node tree, encrypts the root node information using the lower-level node's public key, and then calls the lower-level node's deletion callback method. After the lower-level node's middleware decrypts and verifies the information, it enters the lower-level node's subsystem to delete all root node information. After deletion, it returns to the root node to delete the lower-level node's information. Notably, the root node can delete any registered lower-level node.

[0038] Example 6 Building upon Example 5, the hierarchical management module further includes acquiring node tree information and processing it in different ways based on the attributes of lower-level nodes: When a lower-level node has the root node attribute, the node tree is returned directly to obtain the node tree information. When a lower-level node does not have the root node attribute, it is a single lower-level node attribute. The front end calls the node tree information in the middle platform service module and then forwards it to the first hierarchical management module of the lower-level node. The first hierarchical management module encrypts the node at this level using the root node's public key and then requests the root node's interface to obtain node tree information. The middle platform service module of the root node verifies the encrypted information in the request. After confirming the node information, it uses the root node's interface to obtain node tree information to return the node tree information to the lower-level node.

[0039] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely illustrative descriptions of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.

[0040] The above are merely preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A multi-system hierarchical management system based on RSA encryption algorithm for information protection in satellite systems, characterized in that... The system includes at least: The middleware service module verifies the information of external users; At least one root node is connected to the middleware service module; At least one subordinate node is connected to the middleware service module; several root nodes and subordinate nodes are connected to form the node tree of the system; A hierarchical management module, comprising at least a first management module and a second management module, wherein the first management module is connected to lower-level nodes and the second management module is connected to the root node, and the hierarchical management module embeds an encryption algorithm to encrypt information flowing between the root node and lower-level nodes. Throughout the lifecycle of a subsystem, in order to monitor the subsystem's survival status in the face of changes, both the root node and its subordinate nodes have different mechanisms to check the status of the node tree at any time. Root node: It checks the status of each node by polling all its subordinate nodes and sending requests to all subordinate nodes, and finally modifies the node status based on all the node status codes; Non-root nodes: Sometimes, due to network fluctuations, when a node is added or deleted by a higher-level node, the state is not correctly synchronized to the lower-level node. This causes the lower-level node to be uncertain about its own state in the node tree. In this case, the reverse polling function in the hierarchical management module will send the non-root node to request the node tree list of the root node with encrypted node information. When the root node receives the request and decrypts it, it will determine whether the non-root node's node information is in the node tree. The non-root node will then synchronize and update its own state based on this result. All accesses undergo RSA verification at the middleware service module layer. When the system starts, it generates RS256 asymmetric public and private keys, which are unique throughout the system's lifecycle. The public keys of all parent and child nodes can be shared in the node tree. Access to the system node is made through the public key of a certain node. The system node can use its own private key to decrypt the data. Only when decryption is successful and the system node information of the decrypted data packet exists in the node tree will the request continue to be executed. If any link fails, the request will be rejected.

2. The multi-system hierarchical management system based on RSA encryption algorithm as described in claim 1, characterized in that, The hierarchical management module includes at least: Non-root nodes register with their superior units to send registration requests to the root node; The root node is the node allocation and management unit, used to add or delete subordinate nodes; A real-time system node liveness verification unit is used to monitor the status of the node tree.

3. The multi-system hierarchical management system based on RSA encryption algorithm as described in claim 1, characterized in that, The middleware service module includes at least: The backend interface information integration unit is used to filter information; The configuration management unit for system nodes is used to configure node attributes; The message event aggregation and distribution unit, used to collect and organize logs; The access information source verification unit is used to verify the access information.

4. A multi-system hierarchical management method based on RSA encryption algorithm, implemented based on the multi-system hierarchical management system based on RSA encryption algorithm as described in any one of claims 1-3, characterized in that, Includes the following steps: S1. The system starts up and verifies the node information within the system. The hierarchical management module then enables the hierarchical management function. S2. When a user logs into the system, the middleware service module verifies and obtains the configuration information of the user's subordinate nodes and encrypts the configuration information to prevent external access to the configuration information. The hierarchical management module uses a private key to decrypt the encrypted configuration information. After a security check, it initiates registration with the root node. The root node can add subordinate nodes and complete the registration. S3. Receive node deletion information and delete information of subordinate nodes from the root node; S4. When the decrypted configuration information is not related to the user, the hierarchical management module uses the public key to encrypt it and sends it to the front end. Throughout the lifecycle of a subsystem, in order to monitor the subsystem's survival status in the face of changes, both the root node and its subordinate nodes have different mechanisms to check the status of the node tree at any time. Root node: It checks the status of each node by polling all its subordinate nodes and sending requests to all subordinate nodes, and finally modifies the node status based on all the node status codes; Non-root nodes: Sometimes, due to network fluctuations, when a node is added or deleted by a higher-level node, the state is not correctly synchronized to the lower-level node. This causes the lower-level node to be uncertain about its own state in the node tree. In this case, the reverse polling function in the hierarchical management module will send the non-root node to request the node tree list of the root node with encrypted node information. When the root node receives the request and decrypts it, it will determine whether the non-root node's node information is in the node tree. The non-root node will then synchronize and update its own state based on this result. All accesses undergo RSA verification at the middleware service module layer. When the system starts, it generates RS256 asymmetric public and private keys, which are unique throughout the system's lifecycle. The public keys of all parent and child nodes can be shared in the node tree. Access to the system node is made through the public key of a certain node. The system node can use its own private key to decrypt the data. Only when decryption is successful and the system node information of the decrypted data packet exists in the node tree will the request continue to be executed. If any link fails, the request will be rejected.

5. The method for a multi-system hierarchical management system based on the RSA encryption algorithm as described in claim 4, characterized in that, In S2, the steps for a lower-level node to initiate registration with the root node include: S21. External users log in to the system after authentication. The middleware service module obtains the configuration information of the user's subordinate nodes and sends it to the first hierarchical management module. S22. The first hierarchical management module obtains the root node information, and the lower-level nodes initiate a registration application to the root node; S23. After the application is confirmed by the middleware service module, the second hierarchical management module stores the user's configuration information; the configuration information includes at least node ID, node name, node IP, node port, and node public key.

6. The method for a multi-system hierarchical management system based on the RSA encryption algorithm as described in claim 5, characterized in that, The process of adding a child node to the root node includes the following steps: S24. The root node selects the corresponding part of the configuration information in S23, and writes the node ID into the node tree through the second hierarchical management module; S25. The second hierarchical management module encrypts the root node information using the public key of the lower-level node, calls the deletion callback method of the lower-level node, and decrypts and verifies it through the middle platform service module. S26. Update the registration success information to the network control of the lower-level node. After the update is completed, change the status of the lower-level node to registration success in the root node.

7. The method for a multi-system hierarchical management system based on the RSA encryption algorithm as described in claim 6, characterized in that, After the lower-level node is successfully registered as described in S26, the process of the root node deleting the lower-level node includes the following steps: S27. The second hierarchical management module deletes the lower-level node from the node tree; S28. The second hierarchical management module encrypts the root node information using the public key of the lower-level node, calls the deletion callback method of the lower-level node, and the lower-level node decrypts and verifies the information through the middleware service module. S29. Delete all root node information in the network control of the lower-level node; and delete the lower-level node information in the root node.

8. The method for a multi-system hierarchical management system based on the RSA encryption algorithm as described in claim 7, characterized in that, When a subordinate node has the attribute of a root node, the root node has the right to refuse the registration of the subordinate node.

9. The method for a multi-system hierarchical management system based on the RSA encryption algorithm as described in claim 8, characterized in that, It also includes the lower-level nodes obtaining node tree information, specifically through the following steps: S261. When a lower-level node has the attribute of a root node, the lower-level node obtains the node tree information. S262. When a lower-level node does not have the attribute of a root node, the node tree information is obtained through the middle platform service module and forwarded to the first hierarchical management module of the lower-level node to obtain the node tree information.

Images