A centralized quantum key relay management method and system, and a relay node
By eliminating the key pool of relay nodes and directly uploading the quantum key XOR data to the key relay management system, the problems of complex process, insufficient reliability and poor real-time performance in centralized quantum key relay schemes are solved, and a more efficient key relay process is achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- QUANTUMCTEK CO LTD
- Filing Date
- 2021-12-28
- Publication Date
- 2026-07-10
AI Technical Summary
Existing centralized quantum key relay schemes suffer from problems such as complex key relay processes, insufficient reliability, and poor real-time performance.
The relay node eliminates the key pool, and the quantum key XOR data is directly uploaded to the key relay management system for storage. The relay node no longer stores the key XOR data, and the key relay management system directly performs key XOR data retrieval and calculation locally, simplifying the process and improving real-time performance and reliability.
It simplifies the key relay process, improves the real-time performance and reliability of key relay, and reduces the equipment security burden and data interaction risks of relay nodes.
Smart Images
Figure CN116366237B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of quantum secure communication technology, and in particular to a centralized quantum key relay management method, system and relay node. Background Technology
[0002] Quantum secure communication, with its unconditional security and high efficiency, has brought about a revolutionary development in information security and is currently the main research direction for secure data transmission.
[0003] To achieve wide-area networking capabilities for quantum secure communication networks, distributed hop-by-hop key relay technology is generally used. This involves redistributing quantum keys using distributed hop-by-hop key relay to form a shared key over a wide area. However, distributed hop-by-hop key relay schemes suffer from complex key relay processes and poor reliability and real-time performance.
[0004] Based on this, some people have proposed a centralized key relay scheme. However, in this scheme, the key is still stored in the relay node. The only difference is that the XOR calculation of the key for each hop is changed to be aggregated and calculated on the same node. Although this centralized scheme simplifies the process of hop-by-hop key relay, it is still similar to the distributed hop-by-hop key relay, with problems of insufficient reliability and poor real-time performance. Summary of the Invention
[0005] To address the aforementioned technical problems, this application provides a centralized quantum key relay management method, system, and relay node to simplify the key relay process and improve its reliability and real-time performance. The technical solution is as follows:
[0006] A centralized quantum key relay management method is applied to a key relay management system. The key relay management system stores key XOR data of relay nodes. The key XOR data is obtained by XORing a second quantum key determined by the relay node with a first quantum key shared by the nodes connected to it. The relay nodes do not store the first quantum key, the second quantum key, or the key XOR data. The method includes:
[0007] In response to a key relay request, terminal node information is parsed from the key relay request, and target key XOR data associated with the terminal node information is retrieved from the stored key XOR data.
[0008] Perform an XOR operation on the target key XOR data to obtain the XOR operation result;
[0009] The result of the XOR operation is sent to the terminal node corresponding to the terminal node information.
[0010] Furthermore, the key relay management system also stores a key topology containing the key XOR data of the relay nodes, the key topology being generated in the following manner:
[0011] Based on the identifier of the quantum key upon which the key XOR data of the relay node is based, the association relationship between the node that generates the quantum key and the node that generates the quantum key is constructed, and the node is associated with the key XOR data obtained by XORing the quantum key of the node to obtain the key topology.
[0012] The step of retrieving the target key XOR data associated with the terminal node information from the stored key XOR data includes:
[0013] In the key topology, query the topology path of the node containing the terminal node information, and obtain the key XOR data associated with each node in the topology path as the target key XOR data.
[0014] Furthermore, the method also includes:
[0015] The key quantity requirement information is parsed from the key relay request;
[0016] The step of obtaining the key XOR data associated with each node in the topology path as the target key XOR data includes:
[0017] If there are multiple topology paths, select a target topology path from the multiple topology paths whose key quantity of each sub-topology path meets the key quantity requirement information;
[0018] Obtain the key XOR data associated with each node in the target topology path, excluding the starting node and the destination node, and use it as the target key XOR data.
[0019] A centralized quantum key relay management method, applied to relay nodes, includes:
[0020] Generate a first quantum key that is the same as the quantum key of the node connected to the relay node;
[0021] For each of the first quantum keys, a second quantum key is determined, and the second quantum key is XORed with the first quantum key to obtain the key XOR data;
[0022] The XOR data of the key, the identifier of the first quantum key, and the identifier of the second quantum key are uploaded to the key relay management system so that the key relay management system stores the XOR data of the key, the identifier of the first quantum key, and the identifier of the second quantum key.
[0023] The relay node does not store the key XOR data, the second quantum key, and the first quantum key.
[0024] Furthermore, for each of the first quantum keys, a second quantum key is determined, including:
[0025] When there are two nodes connected to the relay node, a second quantum key different from each of the first quantum keys is generated;
[0026] If the number of nodes connected to the relay node is greater than 2, for each first quantum key, another first quantum key is selected from the first quantum keys that are the same as the quantum keys of the nodes connected to the relay node, and used as the second quantum key.
[0027] A key relay management system, wherein the key relay management system stores key XOR data of relay nodes, the key XOR data being the data obtained by XORing a second quantum key determined by the relay node with a first quantum key shared by the nodes connected to it, wherein the relay node does not store the first quantum key, the second quantum key, and the key XOR data, the system comprising:
[0028] The retrieval module is used to respond to a key relay request, parse terminal node information from the key relay request, and retrieve target key XOR data associated with the terminal node information from the stored key XOR data.
[0029] The XOR operation module is used to perform an XOR operation on the target key XOR data to obtain the XOR operation result.
[0030] The sending module is used to send the XOR operation result to the terminal node corresponding to the terminal node information.
[0031] Furthermore, the key relay management system also stores a key topology containing the key XOR data of the relay nodes, the key topology being generated in the following manner:
[0032] Based on the identifier of the quantum key upon which the key XOR data of the relay node is based, the association relationship between the node that generates the quantum key and the node that generates the quantum key is constructed, and the node is associated with the key XOR data obtained by XORing the quantum key of the node to obtain the key topology.
[0033] The retrieval module is specifically used for:
[0034] In the key topology, query the topology path of the node containing the terminal node information, and obtain the key XOR data associated with each node in the topology path as the target key XOR data.
[0035] Furthermore, the retrieval module is specifically used for:
[0036] In response to a key relay request, terminal node information and key quantity requirement information are parsed from the key relay request;
[0037] In the key topology, query the topology path of the node containing the terminal node information;
[0038] If there are multiple topology paths, select a target topology path from the multiple topology paths whose key quantity of each sub-topology path meets the key quantity requirement information;
[0039] Obtain the key XOR data associated with each node in the target topology path, excluding the starting node and the destination node, and use it as the target key XOR data.
[0040] A relay node includes:
[0041] A generation module is used to generate a first quantum key that is the same as the quantum key of the node connected to the relay node;
[0042] The determining module is used to determine a second quantum key for each first quantum key, and to XOR the second quantum key with the first quantum key to obtain key XOR data;
[0043] An upload module is used to upload the key XOR data, the identifier of the first quantum key, and the identifier of the second quantum key to the key relay management system, so that the key relay management system stores the key XOR data, the identifier of the first quantum key, and the identifier of the second quantum key;
[0044] The relay node does not store the key XOR data, the second quantum key, and the first quantum key.
[0045] Furthermore, the determining module is specifically used for:
[0046] When there are two nodes connected to the relay node, a second quantum key different from each of the first quantum keys is generated;
[0047] If the number of nodes connected to the relay node is greater than 2, for each first quantum key, another first quantum key is selected from the first quantum keys that are the same as the quantum keys of the nodes connected to the relay node, and used as the second quantum key.
[0048] Compared with the prior art, the beneficial effects of this application are as follows:
[0049] In this application, the relay node obtains the key XOR data, and the key relay management system stores the key XOR data of the relay node. The relay node no longer stores the key XOR data, and the key relay management system responds to the key relay request by parsing the terminal node information from the key relay request, retrieving the target key XOR data associated with the terminal node information from the stored key XOR data, performing an XOR operation on the target key XOR data to obtain the XOR operation result, and sending the XOR operation result to the terminal node corresponding to the terminal node information. This ensures that the key relay management system executes the key relay process without interacting with other relay nodes, simplifying the key relay process and improving its real-time performance and reliability. Attached Figure Description
[0050] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0051] Figure 1 This is a schematic diagram of a centralized key relay scheme in the prior art;
[0052] Figure 2 This is a schematic diagram of the centralized quantum key relay system architecture provided in this application;
[0053] Figure 3 This is a schematic diagram of the structure of a key relay control system provided in this application;
[0054] Figure 4 This is a flowchart illustrating a centralized quantum key relay management method provided in Embodiment 1 of this application;
[0055] Figure 5 This is a schematic diagram of a key topology provided in this application;
[0056] Figure 6 This is a flowchart illustrating a centralized quantum key relay management method provided in Embodiment 2 of this application;
[0057] Figure 7 This is a flowchart illustrating a centralized quantum key relay management method provided in Embodiment 3 of this application;
[0058] Figure 8This is a flowchart illustrating a centralized quantum key relay management method provided in Embodiment 4 of this application;
[0059] Figure 9 This is a schematic diagram illustrating a scenario where a relay node uploads XOR data of a key, as provided in this application.
[0060] Figure 10 This is a schematic diagram of the structure of a key relay control system provided in this application;
[0061] Figure 11 This is a schematic diagram of the structure of a relay node provided in this application. Detailed Implementation
[0062] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0063] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.
[0064] For current centralized key relay schemes, such as Figure 1 As shown, when the key relay control system receives a key relay request, it sends a key request to the relay nodes along the key relay path. The relay nodes return XORed key data based on the key request. For example, if relay node 1 returns... Data returned by relay node 2 The key relay control system performs XOR processing on the collected XOR key data to calculate... Then it is sent to node A or B to calculate the shared key. For example, if it is sent to node B, the shared key is calculated. Obtain the shared key K between node B and node A. A1 The inventors summarized the following functions of the key relay control system:
[0065] (1) The key relay routing table module calculates the available key relay routing table based on the quantum key distribution (QKD) network topology and the key quantity and device status reported by each node, which will be used in the key relay process.
[0066] (2) The key relay control system receives key relay requests, and the key relay management module processes the key relay process.
[0067] (3) The key relay management module queries the key relay path between the starting node and the destination node from the key relay routing table template and sends the key request to the relay node.
[0068] (4) After receiving the key request issued by the key relay management system, the relay node will XOR the quantum key shared with the previous node and the next node respectively, and upload the key XOR data to the key relay management system.
[0069] (5) The identifier of the key selected by each relay node needs to be synchronized with the adjacent nodes on the key relay path to ensure the consistency of key selection between the two nodes. The key identifier can be synchronized directly between the two nodes or through the key relay management system;
[0070] (6) After the key relay control system’s key XOR data calculation module collects all key XOR data on the key relay path, it performs XOR processing on all the data and sends the result to the starting node or the destination node.
[0071] (7) After receiving the key XOR data sent by the key relay management system, the starting node or the destination node calculates and restores the key, and uses it as the shared key between the starting node and the destination node.
[0072] By summarizing the above functions, the inventors found that current centralized key relay schemes are basically variations of hop-by-hop relay, with little change in the basic process logic. The main difference is that the hop-by-hop key XOR calculation has been changed to be performed at a single node. Other functions are largely retained, including: collecting device information to generate a key relay routing table, triggering the key relay process with a key relay request, performing key XOR calculations at each node, synchronizing key identifiers during key XOR calculations at each node, and calculating a shared key at the starting or destination node. This approach does not fully leverage the benefits of centralized key relay, for example, the following functions:
[0073] (1) The key relay management system collects device status information and key information to calculate the routing table:
[0074] Device status information and key information need to be synchronized between the relay node and the key relay management system. The synchronization process has time intervals, so the status of the two cannot be synchronized in real time. Inconsistency will cause the routing table to become unusable.
[0075] (2) Key identifiers must be synchronized when XORing keys at each node:
[0076] Synchronizing key identifiers between nodes increases additional data interaction between nodes, increases interaction processes and security risks, and can also cause key relay processes to fail due to synchronization errors.
[0077] (3) The key relay control system needs to obtain key XOR data from the relay node:
[0078] The key relay management system needs to obtain key XOR data from all relay nodes. The operations of multiple nodes need to be processed synchronously, and the failure of any node will cause the entire process to fail.
[0079] (4) Relay nodes need to cache quantum keys:
[0080] In the current scheme, after the quantum key is generated, it still needs to be stored in the key pool of the node, which increases the security burden of key protection for the device.
[0081] The inventors have identified that existing centralized key relay schemes suffer from problems such as complex quantum key relay processes, insufficient reliability of key relay processes, and poor real-time performance.
[0082] To address the aforementioned issues, the inventors proposed a novel centralized quantum key relay system architecture and a centralized quantum key relay management method.
[0083] The centralized quantum key relay system architecture in this application can be found in [reference needed]. Figure 2 ,like Figure 2 As shown, relay nodes eliminate key pools and directly XOR the quantum keys generated by the uplink and downlink with the key relay management system for storage. The key identifier synchronization process between relay nodes is eliminated; only consistency of the identifier for the same key is required. The key relay management system adds storage for key XOR data. The key relay management system eliminates the calculation of the key routing table, instead directly retrieving the required key XOR data based on the stored key XOR data. After receiving a key relay request, the key relay management system can directly perform key XOR data retrieval and calculation locally to provide the result, without needing to interact with other relay nodes. Finally, since relay nodes only upload key XOR data, one-way communication between relay nodes and the key relay management system can be achieved, which is highly beneficial for the security protection of the communication interface for relay node devices.
[0084] In this application, the key relay management system can employ distributed computing and microservice technologies, such as... Figure 3 As shown, some functional modules can be distributed and deployed across multiple nodes to form a key relay management system to provide services.
[0085] Reference Figure 4 This is a flowchart illustrating a centralized quantum key relay management method provided in Embodiment 1 of this application. This method is applied to applications such as... Figure 2The centralized quantum key relay system architecture shown includes a key relay management system. This key relay management system stores the key XOR data of the relay nodes. This key XOR data is obtained by XORing the second quantum key determined by the relay node with a first quantum key shared by the nodes connected to it. The relay nodes do not store the first quantum key, the second quantum key, and the key XOR data. Figure 4 As shown, the method may include, but is not limited to, the following steps:
[0086] Step S11: In response to the key relay request, parse the terminal node information from the key relay request, and retrieve the target key XOR data associated with the terminal node information from the stored key XOR data.
[0087] In this embodiment, the terminal node information may include: information about the starting node and information about the destination node.
[0088] For example, relay node 1 is connected to terminal node A1, and relay node 1 uploads key XOR data. In the key relay management system, relay node 2 connects to terminal node B2, and relay node 2 uploads the key XOR data. The key relay control system stores the key XOR data. XOR data with key Upon receiving a key relay request, the key relay control system responds by parsing the information of terminal node A1 and terminal node B2 from the request, and then retrieves the key XOR data from the stored key XOR data. XOR data with key
[0089] Step S12: Perform an XOR operation on the target key XOR data to obtain the XOR operation result.
[0090] For example, when the key XOR data is retrieved XOR data with key After that, proceed get
[0091] Step S13: Send the XOR operation result to the terminal node corresponding to the terminal node information.
[0092] For example, Send to terminal node A1 or B2.
[0093] In this embodiment, the relay node obtains the key XOR data, and the key relay management system stores the key XOR data of the relay node. The relay node no longer stores the key XOR data, and the key relay management system responds to the key relay request by parsing the terminal node information from the key relay request, retrieving the target key XOR data associated with the terminal node information from the stored key XOR data, performing an XOR operation on the target key XOR data to obtain the XOR operation result, and sending the XOR operation result to the terminal node corresponding to the terminal node information. This ensures that the key relay management system executes the key relay process without interacting with other relay nodes, simplifying the key relay process and improving its real-time performance and reliability.
[0094] In another embodiment 2 of this application, the functionality of the key relay management system is extended. Based on embodiment 1, the key relay management system can also store a key topology containing the key XOR data of the relay nodes.
[0095] In this embodiment, the key topology can be generated in the following way:
[0096] Based on the identifier of the quantum key upon which the key XOR data of the relay node is based, an association relationship is constructed between the node that generates the quantum key and the node that generates the quantum key. The node is then associated with the key XOR data obtained by XORing the quantum key of the node to obtain the key topology.
[0097] It is understood that the node that generates the quantum key can be a relay node or a terminal node.
[0098] For example, if the key XOR data stored in the key relay control system includes: based on The quantum key K on which it is based AC and K AB The logo, The quantum key K on which it is based AB and K BC The logo, The quantum key K on which it is based AB and K BD The logo, The quantum key K on which it is based BC and K CD The logo, The quantum key K on which it is based AC and K CE The logo, The quantum key K on which it is based BD and K DE The logo, The quantum key K on which it is based CD and K DE logo and The quantum key K on which it is based CE and K DE The identifiers are used to construct and generate the nodes A, B, C, D, and E, as well as the association relationships between nodes A, B, C, D, and E. Furthermore, the XOR data obtained by XORing the quantum key with node A, B, C, D, or E is associated to obtain the following: Figure 5 The key topology shown.
[0099] Each topological path in the key topology can also be associated with a key quantity, such as... Figure 5 As shown, The corresponding key quantity is 1. The corresponding key size is 2. The corresponding key quantity is 2. The corresponding key quantity is 3. The corresponding key quantity is 1. The corresponding key quantity is 3. The corresponding key quantity is 0. The corresponding key quantity is 1.
[0100] Based on the aforementioned key relay management system, this embodiment provides a refined scheme for the centralized quantum key relay management method described in Embodiment 1 above, such as... Figure 6 As shown, the method may include, but is not limited to, the following steps:
[0101] Step S21: In response to the key relay request, parse the terminal node information from the key relay request, query the topology path containing the node corresponding to the terminal node information in the key topology, and obtain the key XOR data associated with each node in the topology path as the target key XOR data.
[0102] For example, if parsed from a key relay request, such as Figure 5 The information about nodes A and E indicates that a key relay is to be performed from node A to node E. This can be achieved through methods such as... Figure 5 Directly retrieved from the key topology shown As the target key XOR data, it can also be selected Used as XOR data for the target key.
[0103] Step S21 is a specific implementation of step S11 in Example 1.
[0104] Step S22: Perform an XOR operation on the target key XOR data to obtain the XOR operation result.
[0105] Step S23: Send the XOR operation result to the terminal node corresponding to the terminal node information.
[0106] In this embodiment, by generating a key topology and responding to a key relay request, the terminal node information is parsed from the key relay request. The topology path containing the node corresponding to the terminal node information is queried in the key topology, and the key XOR data associated with each node in the topology path is obtained as the target key XOR data. This can improve the efficiency of obtaining the target key XOR data and improve the efficiency of key relay.
[0107] As another optional embodiment of this application, refer to Figure 7 This is a flowchart of a centralized quantum key relay management method provided in Embodiment 3 of this application. This embodiment is mainly an extension of the method described in Embodiment 2 above, such as... Figure 7 As shown, the method may include, but is not limited to, the following steps:
[0108] Step S31: In response to the key relay request, parse the terminal node information and key quantity requirement information from the key relay request, and query the topology path of the node containing the terminal node information in the key topology.
[0109] Step S32: If there are multiple topological paths, select a target topological path from the multiple topological paths whose key quantity of each sub-topological path meets the key quantity requirement information.
[0110] Step S33: Obtain the key XOR data associated with each node in the target topology path, excluding the starting node and the destination node, as the target key XOR data.
[0111] For example, if the terminal node information includes information about node A and node E, and the key requirement information is that the key quantity for the topology path is not less than 2, then it can be obtained from... Figure 5 From the key topology shown, sub-topology paths ABD (key size 2) and BDE (key size 3) are selected. Then, node B in the target topology path ABDE, which contains sub-topology paths ABD and BDE, is... and node D Used as XOR data for the target key.
[0112] Step S34: Perform an XOR operation on the target key XOR data to obtain the XOR operation result.
[0113] Step S35: Send the XOR operation result to the terminal node corresponding to the terminal node information.
[0114] In this embodiment, in response to a key relay request, terminal node information and key quantity requirement information are parsed from the key relay request. The topology path containing the node corresponding to the terminal node information is queried in the key topology. If there are multiple topology paths, a target topology path is selected from the multiple topology paths, and the key quantity of each sub-topology path meets the key quantity requirement information. The key XOR data associated with each node in the target topology path, except for the starting node and the destination node, is obtained as the target key XOR data. This enables the acquisition of target key XOR data based on more information, meets different needs, and improves user experience.
[0115] As another optional embodiment of this application, refer to Figure 8 This is a flowchart of a centralized quantum key relay management method provided in Embodiment 4 of this application. This method is applied to relay nodes, such as... Figure 8 As shown, the method may include, but is not limited to, the following steps:
[0116] Step S41: Generate a first quantum key that is the same as the quantum key of the node connected to the relay node.
[0117] Step S42: For each first quantum key, determine a second quantum key, and XOR the second quantum key with the first quantum key to obtain key XOR data.
[0118] In this embodiment, determining a second quantum key for each first quantum key may include:
[0119] When there are two nodes connected to the relay node, a second quantum key, different from each of the first quantum keys, is generated. For example, if nodes B and C are connected to relay node A, the first quantum key, which is the same as the quantum key of node B, is K. B1 The first quantum key that is the same as the quantum key of node C is K. C1 Then the relay node can generate the quantum key K. A1 Relay node A can obtain the key XOR data. and
[0120] If the number of nodes connected to the relay node is greater than 2, for each first quantum key, another first quantum key is selected from the first quantum keys that are the same as the quantum keys of the nodes connected to the relay node, and used as the second quantum key.
[0121] For example, if relay node 1 has links connecting it to nodes A, B, and C, and node A's quantum key is K... A1 The quantum key of node B is K. B1The quantum key of node C is K. C1 Then relay node 1 generates the first quantum key K. A1 K B1 and K C1 And for the first quantum key K A1 From K B1 and K C1 Select K B1 As the second quantum key; for the first quantum key K B1 From K A1 and K C1 Select K C1 As the second quantum key; for the first quantum key K C1 From the first quantum key K A1 and K B1 Select K A1 As a second quantum key. Figure 9 As shown, relay node 1 uploads key XOR data. Stored in the key relay control system for key relay between A and B, A and C, and B and C.
[0122] Step S43: Upload the key XOR data, the identifier of the first quantum key, and the identifier of the second quantum key to the key relay management system, so that the key relay management system stores the key XOR data, the identifier of the first quantum key, and the identifier of the second quantum key.
[0123] The relay node does not store the key XOR data, the second quantum key, and the first quantum key.
[0124] The key relay management system and relay nodes provided in this application will be introduced below. The key relay management system and relay nodes described below can be referred to in correspondence with the centralized quantum key relay management method described above.
[0125] Please see Figure 10 The key relay management system stores key XOR data of relay nodes. The key XOR data is the data obtained by XORing the second quantum key determined by the relay node with the first quantum key shared by the nodes connected to it. The relay node does not store the first quantum key, the second quantum key and the key XOR data. The key relay management system includes: a retrieval module 100, an XOR operation module 200 and a sending module 300.
[0126] The retrieval module 100 is configured to, in response to a key relay request, parse terminal node information from the key relay request and retrieve target key XOR data associated with the terminal node information from the stored key XOR data;
[0127] The XOR operation module 200 is used to perform an XOR operation on the target key XOR data to obtain the XOR operation result.
[0128] The sending module 300 is used to send the XOR operation result to the terminal node corresponding to the terminal node information.
[0129] In this embodiment, the key relay management system also stores a key topology containing the key XOR data of the relay nodes, and the key topology is generated in the following way:
[0130] Based on the identifier of the quantum key upon which the key XOR data of the relay node is based, the association relationship between the node that generates the quantum key and the node that generates the quantum key is constructed, and the node is associated with the key XOR data obtained by XORing the quantum key of the node to obtain the key topology.
[0131] The retrieval module 100 can be specifically used for:
[0132] In the key topology, query the topology path of the node containing the terminal node information, and obtain the key XOR data associated with each node in the topology path as the target key XOR data.
[0133] In this embodiment, the retrieval module 100 can be specifically used for:
[0134] In response to a key relay request, terminal node information and key quantity requirement information are parsed from the key relay request;
[0135] In the key topology, query the topology path of the node containing the terminal node information;
[0136] If there are multiple topology paths, select a target topology path from the multiple topology paths whose key quantity of each sub-topology path meets the key quantity requirement information;
[0137] Obtain the key XOR data associated with each node in the target topology path, excluding the starting node and the destination node, and use it as the target key XOR data.
[0138] Please see Figure 11 The relay nodes include: generation module 400, determination module 500, and upload module 600.
[0139] The generation module 400 is used to generate a first quantum key that is the same as the quantum key of the node connected to the relay node;
[0140] The determining module 500 is used to determine a second quantum key for each first quantum key, and to XOR the second quantum key with the first quantum key to obtain key XOR data;
[0141] The upload module 600 is used to upload the key XOR data, the identifier of the first quantum key, and the identifier of the second quantum key to the key relay management system, so that the key relay management system stores the key XOR data, the identifier of the first quantum key, and the identifier of the second quantum key.
[0142] The relay node does not store the key XOR data, the second quantum key, and the first quantum key.
[0143] In this embodiment, the determining module 500 can be specifically used for:
[0144] When there are two nodes connected to the relay node, a second quantum key different from each of the first quantum keys is generated;
[0145] If the number of nodes connected to the relay node is greater than 2, for each first quantum key, another first quantum key is selected from the first quantum keys that are the same as the quantum keys of the nodes connected to the relay node, and used as the second quantum key.
[0146] It should be noted that each embodiment focuses on describing the differences from other embodiments, and the same or similar parts between the embodiments can be referred to accordingly. For the device embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiments.
[0147] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0148] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.
[0149] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or some parts of the embodiments of this application.
[0150] The above provides a detailed description of a centralized quantum key relay management method, system, and relay node provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.
Claims
1. A centralized quantum key relay management method, characterized in that, An application to a key relay management system, wherein the key relay management system stores key XOR data of relay nodes, the key XOR data being the data obtained by XORing a second quantum key determined by the relay node with a first quantum key shared by the nodes connected to it, wherein the relay node does not store the first quantum key, the second quantum key, and the key XOR data, the method comprising: In response to a key relay request, terminal node information is parsed from the key relay request, and target key XOR data associated with the terminal node information is retrieved from the stored key XOR data. Perform an XOR operation on the target key XOR data to obtain the XOR operation result; The result of the XOR operation is sent to the terminal node corresponding to the terminal node information.
2. The method according to claim 1, characterized in that, The key relay management system also stores a key topology containing the key XOR data of the relay nodes, and the key topology is generated in the following way: Based on the identifier of the quantum key upon which the key XOR data of the relay node is based, the association relationship between the node that generates the quantum key and the node that generates the quantum key is constructed, and the node is associated with the key XOR data obtained by XORing the quantum key of the node to obtain the key topology. The step of retrieving the target key XOR data associated with the terminal node information from the stored key XOR data includes: In the key topology, query the topology path of the node containing the terminal node information, and obtain the key XOR data associated with each node in the topology path as the target key XOR data.
3. The method according to claim 2, characterized in that, The method further includes: The key quantity requirement information is parsed from the key relay request; The step of obtaining the key XOR data associated with each node in the topology path as the target key XOR data includes: If there are multiple topology paths, select a target topology path from the multiple topology paths whose key quantity of each sub-topology path meets the key quantity requirement information; Obtain the key XOR data associated with each node in the target topology path, excluding the starting node and the destination node, and use it as the target key XOR data.
4. A centralized quantum key relay management method, characterized in that, Applied to relay nodes, the method includes: Generate a first quantum key that is the same as the quantum key of the node connected to the relay node; For each of the first quantum keys, a second quantum key is determined, and the second quantum key is XORed with the first quantum key to obtain the key XOR data; The XOR data of the key, the identifier of the first quantum key, and the identifier of the second quantum key are uploaded to the key relay management system so that the key relay management system stores the XOR data of the key, the identifier of the first quantum key, and the identifier of the second quantum key. The relay node does not store the key XOR data, the second quantum key, and the first quantum key.
5. The method according to claim 4, characterized in that, For each of the first quantum keys, a second quantum key is determined, including: When there are two nodes connected to the relay node, a second quantum key different from each of the first quantum keys is generated; If the number of nodes connected to the relay node is greater than 2, for each first quantum key, another first quantum key is selected from the first quantum keys that are the same as the quantum keys of the nodes connected to the relay node, and used as the second quantum key.
6. A key relay control system, characterized in that, The key relay management system stores key XOR data of relay nodes. This key XOR data is obtained by XORing a second quantum key determined by the relay node with a first quantum key shared by the nodes connected to it. The relay nodes do not store the first quantum key, the second quantum key, or the key XOR data. The system includes: The retrieval module is used to respond to a key relay request, parse terminal node information from the key relay request, and retrieve target key XOR data associated with the terminal node information from the stored key XOR data. The XOR operation module is used to perform an XOR operation on the target key XOR data to obtain the XOR operation result. The sending module is used to send the XOR operation result to the terminal node corresponding to the terminal node information.
7. The system according to claim 6, characterized in that, The key relay management system also stores a key topology containing the key XOR data of the relay nodes, and the key topology is generated in the following way: Based on the identifier of the quantum key upon which the key XOR data of the relay node is based, the association relationship between the node that generates the quantum key and the node that generates the quantum key is constructed, and the node is associated with the key XOR data obtained by XORing the quantum key of the node to obtain the key topology. The retrieval module is specifically used for: In the key topology, query the topology path of the node containing the terminal node information, and obtain the key XOR data associated with each node in the topology path as the target key XOR data.
8. The system according to claim 7, characterized in that, The retrieval module is specifically used for: In response to a key relay request, terminal node information and key quantity requirement information are parsed from the key relay request; In the key topology, query the topology path of the node containing the terminal node information; If there are multiple topology paths, select a target topology path from the multiple topology paths whose key quantity of each sub-topology path meets the key quantity requirement information; Obtain the key XOR data associated with each node in the target topology path, excluding the starting node and the destination node, and use it as the target key XOR data.
9. A relay node, characterized in that, include: A generation module is used to generate a first quantum key that is the same as the quantum key of the node connected to the relay node; The determining module is used to determine a second quantum key for each first quantum key, and to XOR the second quantum key with the first quantum key to obtain key XOR data; An upload module is used to upload the key XOR data, the identifier of the first quantum key, and the identifier of the second quantum key to the key relay management system, so that the key relay management system stores the key XOR data, the identifier of the first quantum key, and the identifier of the second quantum key; The relay node does not store the key XOR data, the second quantum key, and the first quantum key.
10. The relay node according to claim 9, characterized in that, The determining module is specifically used for: When there are two nodes connected to the relay node, a second quantum key different from each of the first quantum keys is generated; If the number of nodes connected to the relay node is greater than 2, for each first quantum key, another first quantum key is selected from the first quantum keys that are the same as the quantum keys of the nodes connected to the relay node, and used as the second quantum key.