Root key acquisition method of quantum security gateway

Abstract

The invention discloses a root key acquisition method of a quantum security gateway, which comprises the following steps: a security gateway initiates a registration request to a command and control center, and the command and control center generates and issues a network access code and sends identity category information including identity information or the network access code to a root key pool; the root key pool generates a source key file and a root key file based on the identity category information; the security gateway carries out initialization operation on the security gateway; the aggregation security gateway confirms whether the security gateway initiates a first access request or not and whether a data transmission link is established with the security gateway or not through monitoring; the security gateway initiates a root key downloading request to an aggregation security gateway based on the message for establishing the data transmission link; the aggregation security gateway obtains a root key file from a root key pool, generates a data transmission packet and sends the data transmission packet to the security gateway; and the security gateway obtains and temporarily stores the root key file, and performs consistency authentication on the temporarily stored root key file: if the authentication is passed, persistently stores the root key file.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of cryptography, in particular to a root key acquisition method of a quantum security gateway. BACKGROUND

[0002] In the existing quantum security network system, the normal work of the security gateway depends on the key file uniformly distributed and managed by the aggregation security gateway. Generally, after the initial deployment, the security gateway needs to wait for the aggregation security gateway to issue the required key file through the public Internet or other non-trusted network channels, so as to start and participate in secure communication. However, since the key file itself contains key parameters for guaranteeing the confidentiality and integrity of subsequent communication, the security of its transmission process is crucial. In the prior art, during the first access stage of the security gateway, the data communication channel based on quantum key encryption has not been established between the security gateway and the aggregation security gateway, which significantly increases the risk of the key file being transmitted in plaintext or non-quantum encryption manner in the Internet environment. Attackers may intercept, tamper with or forge the key file during this transmission process, thereby threatening the trust root of the entire quantum security network system.

[0003] Therefore, the prior art has obvious security defects: in the scenario where the initial trust relationship has not been established, there is a lack of a reliable and secure mechanism to guarantee the first delivery of the key file from the aggregation security gateway to the security gateway. How to design a method so that the security gateway can ensure that the root key file obtained from the aggregation security gateway is complete, authentic and not leaked when accessing the network for the first time has become a key technical problem to be solved in the field. SUMMARY

[0004] The present application provides a root key acquisition method of a quantum security gateway to solve the problems in the prior art.

[0005] Technical scheme: The present application provides a root key acquisition method of a quantum security gateway, the participants of the method include a control center, an aggregation security gateway, a root key pool and a security gateway; wherein the aggregation security gateway is connected with the control center and the root key pool through an intranet communication connection, the aggregation security gateway is connected with the security gateway through an Internet communication connection, and the number of the security gateways is at least one, the method comprises the following steps:

[0006] Step 1: the security gateway initiates a registration request to the control center using identity information DID, the control center generates and issues a network access code RID, and sends identity category information including the identity information DID or the network access code RID to the root key pool, and the root key pool generates a source key file doc0 and a root key file doc1 based on the identity category information;

[0007] Step 2: the security gateway initializes itself to confirm whether to build the first access request req1;

[0008] Step 3: the aggregation security gateway listens to confirm whether the security gateway initiates the first access request req1, and whether the data transmission link is established with the security gateway in response to the first access request req1;

[0009] Step 4: the security gateway initiates the root key download request req2 to the aggregation security gateway through the instruction transmission link based on the message of establishing the data transmission link; the aggregation security gateway obtains the root key file doc1 from the root key pool based on the root key download request req2, and stores it locally and persistently, and at the same time, the root key file doc1 is calculated and encrypted to generate a data transmission package mes which is sent to the security gateway through the data transmission link; the security gateway obtains the root key file doc1' by parsing and decrypting, and temporarily stores it;

[0010] Step 5: the security gateway performs consistency authentication on the temporarily stored root key file: if the authentication is passed, the root key file is persistently stored; otherwise, the root key acquisition process is re-executed.

[0011] As an improvement of the application, the specific process of step 1 is:

[0012] The security gateway uses its own identity information DID to initiate a registration request to the control center, and the registration request includes the identity information DID; the control center responds to the registration request to generate and issue a network code RID for the security gateway, records the identity category information as the identity information DID or the network code RID, and establishes the identity correspondence between the identity information DID and the network code RID; the control center locally stores the identity correspondence between the identity information DID and the network code RID, and sends the identity category information to the root key pool, and the root key pool locally generates a source key file doc0 and a root key file doc1 for the security gateway corresponding to the identity category information; the source key file doc0 is pre-stored in the aggregation security gateway and the security gateway in the form of offline download.

[0013] As an improvement of the application, in step 2, the specific process of the initialization operation includes: the security gateway checks whether the network code RID has been stored in the identity storage unit in the current device, or checks whether the root key file already exists in the local key storage pool, if yes, no operation is performed; if not, the first access request req1 is built; wherein the first access request req1 includes the identity information DID or the network code RID of the security gateway itself; wherein the access request req1 is transmitted through the instruction transmission link.

[0014] As an improvement of the present application, the specific process of step 3 is as follows:

[0015] Step 3-1: In response to the first access request req1 initiated by the security gateway to itself in response to the discovery of the security gateway by the aggregation security gateway through the external network port, the aggregation security gateway receives the first access request req1 and starts the internal network port monitoring, and performs an identity authentication operation on the security gateway, and obtains the feedback result of the identity authentication from the root key pool through the internal network port monitoring.

[0016] The specific process of performing the identity authentication operation is as follows:

[0017] The aggregation security gateway forwards the first access request req1 to the root key pool, the root key pool reads the identity category information of the security gateway in the first access request req1, and finds whether there is a corresponding root key file in the local according to the identity category information, if yes, it feeds back that the identity authentication is successful, otherwise, it feeds back that the identity authentication fails, returns to step 1, and re-executes the root key acquisition process; at the same time, the feedback information of the identity authentication success carries the identity category information corresponding to the root key file doc1 in the root key pool;

[0018] Step 3-2: The aggregation security gateway establishes a data transmission link with the security gateway in response to the first access request req1 based on the feedback result of the identity authentication success, and rejects the first access request req1 based on the feedback result of the identity authentication failure, and returns to step 1 to re-execute the root key acquisition process.

[0019] As an improvement of the present application, the specific process of finding whether there is a corresponding root key file in the local according to the identity category information is as follows:

[0020] If the first access request req1 carries the identity information DID, and the root key file doc1 is generated based on the identity information DID in the root key pool, then it is directly found in the locally stored root key list whether there is a root key file doc1 corresponding to the identity information DID;

[0021] If the first access request req1 carries the network access code RID, and the root key file doc1 is generated based on the network access code RID in the root key pool, then it is directly found in the locally stored root key list whether there is a root key file doc1 corresponding to the network access code RID;

[0022] If the identity information DID is carried in the first access request req1 and the root key pool generates the root key file doc1 based on the network access code RID, the root key pool first confirms whether there is an identity corresponding relationship corresponding to the identity information DID from the control center based on the identity information DID, if there is, confirms the network access code RID corresponding to the identity information DID based on the identity corresponding relationship, and then searches the locally stored root key list based on the corresponding network access code RID to find whether there is a root key file doc1 corresponding to the network access code RID; if not, it is determined that the identity authentication fails;

[0023] If the network access code RID is carried in the first access request req1 and the root key pool generates the root key file doc1 based on the identity information DID, the root key pool first obtains the identity corresponding relationship from the control center based on the network access code RID, confirms the identity information DID corresponding to the network access code RID based on the identity corresponding relationship, and then searches the locally stored root key list based on the corresponding identity information DID to find whether there is a root key file doc1 corresponding to the identity information DID.

[0024] As an improvement of the application, the specific process of step 4 is:

[0025] Step 4-1: Based on the data transmission link established between the aggregation security gateway and the security gateway, the security gateway initiates a root key download request req2 to the aggregation security gateway through the instruction transmission link; wherein the root key download request req2 carries the identity category information carried in step 3;

[0026] Step 4-2: The aggregation security gateway forwards the root key download request req2 to the root key pool, and the root key pool extracts the root key file doc1 corresponding to the identity category information from the local according to the identity category information, sends the root key file doc1 to the aggregation security gateway through the intranet, and the aggregation security gateway persistently stores the root key file doc1 locally, and performs hash calculation and encryption operation on the persistently stored root key file doc1, generates a data transmission package mes, and sends it to the security gateway through the data transmission link;

[0027] Step 4-3: The security gateway receives the data transmission package mes, performs hash calculation and compares the hash values, and after the comparison is passed, performs decryption operation to obtain the root key file doc1' in plaintext state, and temporarily stores it.

[0028] As an improvement of the application, in step 4-2, the specific process of generating the data transmission package mes is:

[0029] The aggregation security gateway obtains two random numbers p1 and s1 with a length of 128 bits from a preset stored source key file doc0, records the key index idx-s1 of the random number s1 in the source key file doc0, generates an irreducible polynomial p1(x) by using the random number p1, records a string str-1 composed of coefficients of each term in the irreducible polynomial p1(x) except the highest term, generates a hash function h p1,s1 by using the irreducible polynomial p1(x) and the input random number s1, inputs the root key file doc1 into the hash function h p1,s1 , and obtains a hash value H(doc1)= h p1,s1 (doc1).

[0030] The aggregation security gateway obtains an encryption key key1 from the preset stored source key file doc0, records the key index idx-key1 of the encryption key key1 in the source key file doc0, performs an encryption operation on the root key file doc1 by using the encryption key key1, and obtains a root key file ciphertext enc(doc1)=doc1⊕key1. The root key file ciphertext enc(doc1), the key index idx-key1, the key index idx-s1, the string str-1 and the hash value H(doc1) are spliced together to obtain a data transmission package mes.

[0031] As an improvement of the present application, the specific process of the step 4-3 is that the security gateway receives the data transmission package mes, obtains the root key file ciphertext enc(doc1)', the key index idx-key1', the key index idx-s1', the string str-1' and the hash value H(doc1)', obtains a decryption key key1' from the locally stored source key file doc0 according to the received key index idx-key1', and uses the decryption key key1' to decrypt the received root key ciphertext enc(doc1)' to obtain the plaintext state root key file doc1' which is temporarily stored.

[0032] As an improvement of the present application, the specific process of the step 5 is that:

[0033] The security gateway performs consistency authentication on the temporarily stored root key file and the persistently stored root key file in the aggregation security gateway.

[0034] The security gateway obtains a random number s1' from the locally stored source key file doc0 according to the received key index idx-s1', constructs a hash function h p1’,s1’ by using the random number s1' and the string str-1', and inputs the decrypted root key file doc1' into the hash function h p1’,s1’, get the hash value H(doc1') = h p1’,s1’ (doc1'); compare the calculated hash value H(doc1') with the received hash value H(doc1), if the comparison result is consistent, the consistency authentication is passed, the security gateway converts the root key file doc1' from temporary storage to persistent storage, and deletes the preset source key file doc0 locally; otherwise, go back to step 1, and re-execute the root key acquisition process.

[0035] Advantages:

[0036] 1. By pre-configuring a unified source key file in the aggregation security gateway and the security gateway, an initial encryption basis is provided for identity authentication and data communication between the aggregation security gateway and the security gateway, which solves the difficulty that the communication parties cannot perform encrypted transmission due to lack of corresponding keys before the root key file is officially issued, and blocks security vulnerabilities from the source;

[0037] 2. In the root key acquisition process, the preset source key file is used to perform quantum hash calculation on the root key file requested to be downloaded, so as to verify the legitimacy of the identity of the communication parties, and the root key file is encrypted and then issued, which effectively prevents the core sensitive data of the root key from being stolen, tampered with or forged when transmitted through an untrusted channel such as the public Internet, and ensures the security and integrity of the issued root key file;

[0038] 3. A reliable and secure non-single-level key distribution mechanism is established, through which the aggregation security gateway can safely distribute the root key to the next level security gateway, and the next level gateway can safely serve more terminals or lower level networks based on the root key file after obtaining the root key file, thereby laying a scalable and solid trust transmission foundation for constructing a large-scale and hierarchical quantum security network. BRIEF DESCRIPTION OF DRAWINGS

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

[0040] Figure 1 Connection diagram of the method participants of the present application;

[0041] Figure 2 Flowchart of the method of the present application. DETAILED DESCRIPTION

[0042] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail 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 in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0043] This invention provides a method for obtaining the root key of a quantum-safe gateway. For example... Figure 1 As shown, the participants in the method include: a command and control center, an aggregated security gateway, a root key pool, and a security gateway; wherein, the aggregated security gateway is connected to the command and control center and the root key pool via intranet communication, and the aggregated security gateway is connected to the security gateway via the Internet, and the number of security gateways is at least one. The quantum security gateway includes the aggregated security gateway and multiple peer-to-peer security gateways, wherein the aggregated security gateway is used to monitor all security gateways and authenticate the legitimacy of their initial access requests; the security gateways are used to aggregate traffic and encrypt and decrypt data, and send initial access requests and root key download requests to the aggregated security gateway for the keys required for the data encryption and decryption process.

[0044] like Figure 2 As shown, the quantum-secure root key acquisition method includes the following steps:

[0045] Step 1: The security gateway initiates a registration request to the command and control center using its own identity information DID. The command and control center generates and issues the network access code RID, and sends the identity category information, including the identity information DID or the network access code RID, to the root key pool. The root key pool generates a source key file doc0 and a root key file doc1 based on the identity category information.

[0046] Specifically, the process of step 1 is as follows:

[0047] The security gateway initiates a registration request to the accusation center using its own identity information DID, the registration request including the identity information DID; the accusation center generates and issues a network code RID for the security gateway in response to the registration request, records identity category information (identity information DID or network code RID), and establishes an identity correspondence between the identity information DID and the network code RID; the accusation center locally stores the identity correspondence between the identity information DID and the network code RID, and sends the identity category information (identity information DID or network code RID) to the root key pool, which generates a source key file doc0 and a root key file doc1 for the security gateway corresponding to the identity category information (identity information DID or network code RID) locally. The source key file doc0 is pre-stored in the aggregated security gateway and the security gateway in the form of offline download. It should be noted that the root key file doc1 is not stored in the aggregated security gateway at this time to reduce the storage space occupation.

[0048] Step 2: The security gateway performs an initialization operation on itself to confirm whether to build a first access request req1.

[0049] The specific process of the initialization operation includes: the security gateway checks whether the identity-related information such as the network code RID has been stored in the identity storage unit in the current device, or checks whether the root key file already exists in the local key storage pool. If yes, it means non-first access, and no operation is performed; if not, a first access request req1 is built; wherein the first access request req1 includes the identity information DID or the network code RID of the security gateway itself; wherein the access request req1 is transmitted through the instruction transmission link.

[0050] At this time, there is only an instruction transmission link between the security gateway and the aggregated security gateway, and there is no data transmission link.

[0051] As described above, the security gateway and the aggregated security gateway can store a unified source key file to encrypt the transmission content, which includes instruction information such as access requests, download requests, etc., and also includes data information such as the root key file in subsequent step 4; after the root key acquisition process is completed, the source key file is deleted and no longer used. It should be noted that the source key file pre-stored in the security gateway and the aggregated security gateway does not need to be very large and can be expanded according to the size of the transmission content.

[0052] Step 3: The aggregated security gateway confirms whether the security gateway initiates a first access request req1 and whether it establishes a data transmission link with the security gateway in response to the first access request req1 by listening.

[0053] Specifically, step 3 includes:

[0054] Step 3-1: In response to the aggregation security gateway initiating a first access request req1 to itself in response to the discovery of the security gateway by the aggregation security gateway through the external network port, the aggregation security gateway receives the first access request req1 and starts listening to the internal network port, and performs an identity authentication operation on the security gateway, and obtains a feedback result of the identity authentication of the security gateway from the root key pool through the listening of the internal network port;

[0055] The specific process of performing the identity authentication operation is as follows: the aggregation security gateway forwards the first access request req1 to the root key pool, the root key pool reads the identity category information (identity information DID or network access code RID) of the security gateway in the first access request req1, and finds whether there is a corresponding root key file locally according to the identity category information, if yes, it feeds back that the identity authentication is successful; otherwise, it feeds back that the identity authentication fails, returns to step 1, and re-executes the root key acquisition process; at the same time, the feedback information of the identity authentication success carries the identity category information corresponding to the root key file doc1 in the root key pool;

[0056] The specific process of finding whether there is a corresponding root key file locally according to the identity category information is as follows:

[0057] If the first access request req1 carries the identity information DID, and the root key pool generates the root key file doc1 based on the identity information DID, then it is directly found whether there is a root key file doc1 corresponding to the identity information DID in the locally stored root key list;

[0058] If the first access request req1 carries the network access code RID, and the root key pool generates the root key file doc1 based on the network access code RID, then it is directly found whether there is a root key file doc1 corresponding to the network access code RID in the locally stored root key list;

[0059] If the first access request req1 carries the identity information DID, and the root key pool generates the root key file doc1 based on the network access code RID, then the root key pool first confirms whether there is an identity corresponding relationship corresponding to the identity information DID from the control center based on the identity information DID, if yes, it confirms the network access code RID corresponding to the identity information DID based on the identity corresponding relationship, and then finds whether there is a root key file doc1 corresponding to the network access code RID in the locally stored root key list based on the corresponding network access code RID; if not, it directly determines that the identity authentication fails;

[0060] If the onboarding code RID is carried in the first access request req1, and the root key pool is based on the identity information DID to generate the root key file doc1, the root key pool first obtains the identity correspondence from the control center based on the onboarding code RID, confirms the identity information DID corresponding to the onboarding code RID based on the identity correspondence, and then finds whether there is a root key file doc1 corresponding to the identity information DID in the locally stored root key list based on the corresponding identity information DID;

[0061] In the above four finding situations, if the finding result is yes, identity authentication success is fed back, and at the same time, the identity authentication success feedback information carries the identity category information corresponding to the root key in the root key pool, for example, whether the root key file is generated based on the identity information DID or the onboarding code RID, so that the correct identity identifier can be carried in the root key download request req2 generated next, and the judgment process of the identity correspondence in the above four relationships is reduced; if the finding result is no, identity authentication failure is fed back.

[0062] Step 3-2: The aggregation security gateway establishes a data transmission link with the security gateway in response to the first access request req1 based on the feedback result of identity authentication success, and rejects the first access request req1 based on the feedback result of identity authentication failure, and returns to step 1 to re-execute the root key acquisition process.

[0063] Step 4: The security gateway initiates a root key download request req2 to the aggregation security gateway through the instruction transmission link based on the message of establishing a data transmission link, the aggregation security gateway obtains the root key file doc1 from the root key pool based on the root key download request req2, and stores it in the local persistent storage, and at the same time, the root key file doc1 is subjected to hash calculation and encryption operation to generate a data transmission package mes which is sent to the security gateway through the data transmission link; the security gateway obtains the root key file doc1' by parsing and decrypting, and temporarily stores it.

[0064] Specifically, step 4 includes:

[0065] Step 4-1: The aggregation security gateway and the root key pool are connected through the intranet, and can directly communicate through the intranet, based on the data transmission link established between the aggregation security gateway and the security gateway, the security gateway initiates a root key download request req2 to the aggregation security gateway through the instruction transmission link, and the root key download request req2 carries the identity category information (identity information DID or onboarding code RID) carried in step 3;

[0066] Step 4-2: The aggregation security gateway forwards the root key downloading request req2 to the root key pool, the root key pool extracts the root key file doc1 corresponding to the identity category information from the local according to the identity category information, sends the root key file doc1 to the aggregation security gateway through the intranet plaintext, the aggregation security gateway stores the root key file doc1 persistently in the local, and performs hash calculation on the persistently stored root key file doc1 to obtain the hash value H(doc1), and the specific process is as follows:

[0067] The aggregation security gateway obtains two random numbers p1 and s1 with a length of 128 bits from the preset stored source key file doc0, records the key index idx-s1 of the random number s1 in the source key file doc0; generates an irreducible polynomial p1(x) using the random number p1, and records the string composed of the coefficient of each term of the irreducible polynomial p1(x) except the highest term as str-1; generates a hash function h p1,s1 using the irreducible polynomial p1(x) and the input random number s1; inputs the root key file doc1 into the hash function h p1,s1 , and obtains the hash value H(doc1)= h p1,s1 (doc1).

[0068] The aggregation security gateway obtains the encryption key key1 from the preset stored source key file doc0, records the key index idx-key1 of the encryption key key1 in the source key file doc0; performs encryption operation on the root key file doc1 using the encryption key key1 to obtain the root key file ciphertext enc(doc1)=doc1⊕key1; splices the root key file ciphertext enc(doc1), the key index idx-key1, the key index idx-s1, the string str-1, and the hash value H(doc1) to obtain a data transmission package mes, and sends the data transmission package mes to the security gateway via the data transmission link. It should be noted that the encryption key used for encryption is obtained from the source key file doc0 preset stored by the security gateway and the aggregation security gateway, and the source key file doc0 is obtained by the security gateway and the aggregation security gateway in the form of offline downloading (for example, in the form of a U disk), and has not passed through the transmission link between the two, so there is no risk of interception or tampering. In the embodiment of the application, because the intranet is secure, the aggregation security gateway can directly persistently store the root key file doc1 plaintext from the root key pool.

[0069] Step 4-3: The security gateway receives the data transmission package mes, obtains the root key file ciphertext enc(doc1)', the key index idx-key1', the key index idx-s1', the string str-1' and the hash value H(doc1)' ; obtains the decryption key key1' from the locally stored source key file doc0 according to the received key index idx-key1', decrypts the received root key ciphertext enc(doc1)' using the decryption key key1', obtains the plaintext state root key file doc1', and temporarily stores it. Since the connection between the security gateway and the aggregation security gateway is the Internet, which is not necessarily secure and has the possibility of being tampered with, the security gateway temporarily stores the root key file doc1' first.

[0070] At this point, the security gateway and the aggregation security gateway have both received the root key file.

[0071] Step 5: The security gateway performs consistency authentication on the temporarily stored root key file: if the authentication is passed, the root key file is stored persistently; otherwise, the root key acquisition process is re-executed.

[0072] Specifically, the process of step 5 is:

[0073] The security gateway performs consistency authentication on the temporarily stored root key file and the persistently stored root key file in the aggregation security gateway:

[0074] The security gateway obtains the random number s1' from the locally stored source key file doc0 according to the received key index idx-s1', constructs a hash function h p1’,s1’ (doc1') using the random number s1' and the string str-1', inputs the decrypted root key file doc1' into the hash function h p1’,s1’ , obtains the hash value H(doc1') = h p1’,s1’ (doc1'), compares the calculated hash value H(doc1') with the received hash value H(doc1)', and if the comparison result is consistent, the consistency authentication is passed, the security gateway converts the root key file doc1' from temporary storage to persistent storage, and deletes the pre-stored source key file doc0 locally. Otherwise, go back to step 1 and re-execute the root key acquisition process.

Claims

1. A method for root key acquisition of a quantum secure gateway, participants of the method comprising: The method comprises the following steps: Step 1: the security gateway initiates a registration request to the control center using identity information DID, the control center generates and issues a network access code RID, sends identity category information including the identity information DID or the network access code RID to the root key pool, and the root key pool generates a source key file doc0 and a root key file doc1 based on the identity category information; Step 2: the security gateway performs an initialization operation on itself to confirm whether to build a first access request req1; Step 3: the aggregation security gateway listens to confirm whether the security gateway initiates the first access request req1 and whether the first access request req1 is responded to to establish a data transmission link with the security gateway; Step 4: the security gateway initiates a root key download request req2 to the aggregation security gateway through an instruction transmission link based on the message of establishing the data transmission link; the aggregation security gateway obtains the root key file doc1 from the root key pool based on the root key download request req2, and locally persists the root key file doc1, simultaneously performs hash calculation and encryption operation on the root key file doc1, generates a data transmission package mes, and sends the data transmission package mes to the security gateway through the data transmission link; the security gateway obtains the root key file doc1' through analysis and decryption, and temporarily stores the root key file doc1'; Step 5: the security gateway performs consistency authentication on the temporarily stored root key file: if the authentication is passed, the root key file is persisted; otherwise, the root key acquisition process is re-executed.

2. The root key acquisition method of a quantum security gateway according to claim 1, characterized by, The specific process of step 1 is as follows: The security gateway initiates a registration request to the control center using its own identity information DID, and the registration request includes the identity information DID; the control center generates and issues a network access code RID for the security gateway in response to the registration request, records identity category information as the identity information DID or the network access code RID, and establishes an identity correspondence relationship between the identity information DID and the network access code RID; the control center locally stores the identity correspondence relationship between the identity information DID and the network access code RID, simultaneously sends the identity category information to the root key pool, and the root key pool generates a source key file doc0 and a root key file doc1 for the security gateway corresponding to the identity category information; the source key file doc0 is pre-stored in the aggregation security gateway and the security gateway in the form of offline download.

3. The root key acquisition method of a quantum security gateway according to claim 1, characterized by, In step 2, the specific process of the initialization operation includes: the security gateway checking whether the identity storage unit in the current device has already stored the network access code RID or whether the local key storage pool already has the root key file, if yes, no operation is performed; if not, a first access request req1 is constructed; wherein the first access request req1 includes the identity information DID of the security gateway itself or the network access code RID; wherein the access request req1 is transmitted through the instruction transmission link.

4. The root key acquisition method of a quantum security gateway according to claim 3, characterized by, The specific process of step 3 is as follows: Step 3-1: in response to the fact that the aggregation security gateway discovers that the security gateway initiates the first access request req1 to itself through the external network port monitoring, the aggregation security gateway receives the first access request req1 and starts the internal network port monitoring, and performs the identity authentication operation on the security gateway, and obtains the feedback result of the identity authentication from the root key pool through the internal network port monitoring; The specific process of performing the identity authentication operation is as follows: The aggregation security gateway forwards the first access request req1 to the root key pool, the root key pool reads the identity category information of the security gateway in the first access request req1, and finds whether there is a corresponding root key file in the local according to the identity category information, if yes, the identity authentication is fed back as successful; otherwise, the identity authentication is fed back as failed, and the root key acquisition process is re-executed in step 1; at the same time, the feedback information of the identity authentication success carries the identity category information corresponding to the root key file doc1 in the root key pool; Step 3-2: the aggregation security gateway responds to the first access request req1 based on the feedback result of the identity authentication success, and establishes a data transmission link with the security gateway; based on the feedback result of the identity authentication failure, the first access request req1 is rejected, and the root key acquisition process is re-executed in step 1.

5. The root key acquisition method of a quantum security gateway according to claim 4, characterized by, The specific process of finding whether there is a corresponding root key file in the local according to the identity category information is as follows: If the first access request req1 carries the identity information DID, and the root key pool generates the root key file doc1 based on the identity information DID, then whether there is a root key file doc1 corresponding to the identity information DID in the locally stored root key list is directly found; If the first access request req1 carries the network access code RID, and the root key pool generates the root key file doc1 based on the network access code RID, then whether there is a root key file doc1 corresponding to the network access code RID in the locally stored root key list is directly found; If the first access request req1 carries the identity information DID, and the root key pool generates the root key file doc1 based on the network access code RID, then the root key pool first confirms whether there is an identity corresponding relationship corresponding to the identity information DID from the control center based on the identity information DID, if yes, the network access code RID corresponding to the identity information DID is confirmed based on the identity corresponding relationship, and then whether there is a root key file doc1 corresponding to the network access code RID in the locally stored root key list is found based on the corresponding network access code RID; if not, it is determined that the identity authentication fails; If the onboarding code RID is carried in the first access request req1, and the root key pool generates the root key file doc1 based on the identity information DID, the root key pool first obtains the identity correspondence from the control center based on the onboarding code RID, confirms the identity information DID corresponding to the onboarding code RID based on the identity correspondence, and then searches the locally stored root key list for the root key file doc1 corresponding to the identity information DID.

6. The root key acquisition method of a quantum security gateway according to claim 4, characterized by, The specific process of step 4 is as follows: Step 4-1: Based on the data transmission link established between the aggregation security gateway and the security gateway, the security gateway initiates a root key download request req2 to the aggregation security gateway through the instruction transmission link; wherein the root key download request req2 carries the identity category information carried in step 3; Step 4-2: The aggregation security gateway forwards the root key download request req2 to the root key pool, and the root key pool extracts the root key file doc1 corresponding to the identity category information from the local according to the identity category information, sends the root key file doc1 to the aggregation security gateway through the intranet, and the aggregation security gateway locally stores the root key file doc1, and performs hash calculation and encryption operation on the stored root key file doc1, generates a data transmission package mes, and sends it to the security gateway through the data transmission link; Step 4-3: The security gateway receives the data transmission package mes, performs hash calculation and hash value comparison, and after the comparison is passed, performs decryption operation to obtain the root key file doc1' in plaintext state, and temporarily stores it.

7. The root key acquisition method of a quantum security gateway according to claim 6, characterized by, In step 4-2, the specific process of generating the data transmission package mes is as follows: The aggregation security gateway obtains two random numbers p1 and s1 with a length of 128 bits from the pre-stored source key file doc0, records the key index idx-s1 of the random number s1 in the source key file doc0; generates an irreducible polynomial p1(x) using the random number p1, and the string composed of the coefficient of each term in the irreducible polynomial p1(x) except the highest term is str-1; An irreducible polynomial p1(x) and an input random number s1 are used to generate a hash function h p1,s1 ; a root key file doc1 is input into the hash function h p1,s1 , and a hash value H(doc1) = h p1,s1 (doc1) is obtained. The aggregation security gateway obtains the encryption key key1 from the pre-stored source key file doc0, records the key index idx-key1 of the encryption key key1 in the source key file doc0; uses the encryption key key1 to perform encryption operation on the root key file doc1, and obtains the root key file ciphertext enc(doc1)=doc1⊕key1; concatenates the root key file ciphertext enc(doc1), the key index idx-key1, the key index idx-s1, the string str-1 and the hash value H(doc1) to obtain the data transmission package mes.

8. The root key acquisition method of a quantum security gateway according to claim 7, characterized by, The specific process of step 4-3 is that the security gateway receives the data transmission package mes, obtains the root key file ciphertext enc(doc1)', the key index idx-key1', the key index idx-s1', the character string str-1' and the hash value H(doc1)', obtains the decryption key key1' in the locally stored source key file doc0 according to the received key index idx-key1', uses the decryption key key1' to decrypt the received root key ciphertext enc(doc1)', obtains the plaintext state root key file doc1', and temporarily stores it.

9. The root key acquisition method of a quantum security gateway according to claim 8, characterized by, The specific process of step 5 is that: The security gateway performs consistency authentication on the temporarily stored root key file and the root key file persistently stored in the aggregation security gateway: The security gateway obtains the random number s1' from the locally stored source key file doc0 according to the received key index idx-s1', constructs a hash function h using the random number s1' and the string str-1' p1’,s1’ ; inputs the decrypted root key file doc1' into the hash function h p1’,s1’ , to obtain a hash value H(doc1')=h p1’,s1’ (doc1'); compares the calculated hash value H(doc1') with the received hash value H(doc1)', and if the comparison result is consistent, the consistency authentication passes, the security gateway converts the root key file doc1' from temporary storage to persistent storage, and deletes the preset source key file doc0 locally; otherwise, returns to step 1 and re-executes the root key acquisition process.

Images