Cross-domain data transmission method and cross-domain transmission system

By combining zero-trust architecture and quantum key distribution technology to generate and encrypt session keys, the communication security risks in cross-domain collaborative working modes are resolved, achieving higher security and reliability and adapting to quantum computing threats.

CN119094123AActive Publication Date: 2024-12-06ANHUI GUOKE QUANTUM NETWORK CO LTD

Patent Information

Application Number
CN202411258429.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-09
Publication Date
2024-12-06
Estimated Expiration
2044-09-09

AI Technical Summary

Technical Problem

Existing quantum key encryption algorithms cannot provide long-term security guarantees, resulting in continued security risks in communication during cross-domain collaborative work.

Method used

Employing a zero-trust architecture and quantum key distribution technology, the zero-trust control platform generates session keys and encrypts them using quantum keys, ensuring the security of session keys during cross-domain transmission. Furthermore, dynamic access control is implemented through trust tokens and real-time environmental awareness, enhancing the security of communication data.

Benefits of technology

It improves communication security in cross-domain collaborative working modes, enhances the security of session keys and the reliability of data transmission, prevents unauthorized access and internal threats, and adapts to the security challenges of future quantum computing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119094123A_ABST
    Figure CN119094123A_ABST
Patent Text Reader

Abstract

The invention relates to the field of communication security, and discloses a cross-domain data transmission method and a cross-domain transmission system, a first zero-trust domain node in a first network domain receives an application session request sent by a sending terminal in the first network domain; sending the application session request to a zero-trust control platform, generating a session key by the zero-trust control platform according to the application session request, performing quantum key encryption on the session key to obtain session encryption information, and sending the session encryption information to a first zero-trust domain node; the first zero-trust domain node forwards the session encryption information to a sending terminal, the sending terminal performs quantum key decryption on the session encryption information to obtain a session key, encrypts communication data through the session key to obtain encrypted communication data, and sends an encrypted data transmission request to the first zero-trust domain node; and the first zero-trust domain node sends the encrypted data transmission request to the receiving terminal in the second network domain through the second zero-trust domain node in the second network domain, so that the security of cross-domain communication is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication security, and in particular to a cross-domain data transmission method and a cross-domain transmission system. Background Art

[0002] With the rapid development of information technology and the Internet, collaborative work and data sharing between different organizations and network security domains have become increasingly frequent. This cross-domain collaborative work model has greatly improved work efficiency and resource utilization, but it also brings huge security challenges. Frequent cyber attacks and data leaks, especially advanced persistent threats and internal attacks, seriously threaten the security of cross-domain collaborative communications.

[0003] In the existing technology, quantum keys can be used to achieve communication security in a cross-domain collaborative working mode. Quantum key distribution technology uses the principles of quantum mechanics to provide an unconditionally secure key distribution mechanism. Quantum key distribution technology transmits keys through quantum states, and any eavesdropping behavior will change the quantum state and be detected, ensuring the security of the key distribution process. However, with the development of quantum computing technology, the encryption algorithm of quantum keys will face the risk of being cracked and cannot provide long-term security guarantees, resulting in security risks in communication security in a cross-domain collaborative working mode. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a cross-domain data transmission method and a cross-domain transmission system to improve the communication security in a cross-domain collaborative working mode.

[0005] To solve the above technical problems, an embodiment of the present application provides a cross-domain data transmission method, which is applied to a first zero-trust domain node in a first network domain, including:

[0006] Receiving a session application request sent by a sending terminal in the first network domain;

[0007] Sending the session application request to the zero trust control platform, so that the zero trust control platform generates a session key according to the session application request, performs quantum key encryption on the session key to obtain session encryption information, and sends the session encryption information to the first zero trust domain node;

[0008] Receiving the session encryption information sent by the zero trust control platform;

[0009] Sending the session encryption information to the sending terminal, so that the sending terminal performs quantum key decryption on the session encryption information to obtain the session key, encrypts the communication data by using the session key to obtain encrypted communication data, and sends an encrypted data transmission request carrying the encrypted communication data, the session identifier, and the receiving terminal identifier to the first zero-trust domain node;

[0010] receiving the encrypted data transmission request sent by the sending terminal;

[0011] The encrypted data transmission request is sent to the receiving terminal in the second network domain through the second zero trust domain node in the second network domain corresponding to the receiving terminal identifier.

[0012] The embodiment of the present application further provides a cross-domain data transmission method, before receiving the session application request sent by the sending terminal in the first network domain, further comprising:

[0013] Receiving a request for applying for access to a network domain trust token sent by the sending terminal;

[0014] Sending the request for applying for access to the network domain trust token to the zero trust control platform, so that the zero trust control platform determines the trust token of the sending terminal according to the request for applying for access to the network domain trust token, and sends the trust token to the first zero trust domain node;

[0015] Receiving a trust token of the sending terminal sent by the zero trust control platform;

[0016] sending the trust token to the sending terminal so that the sending terminal adds the trust token to the encrypted data transmission request;

[0017] The step of sending the encrypted data transmission request to a receiving terminal in the second network domain through a second zero trust domain node in the second network domain corresponding to the receiving terminal identifier includes:

[0018] Verifying access rights of the trust token of the sending terminal to the second network domain;

[0019] If the verification passes, the encrypted data transmission request is sent to the receiving terminal through the second zero trust domain node.

[0020] An embodiment of the present application further provides a cross-domain data transmission method, which, before verifying the access rights of the trust token of the sending terminal to the second network domain, further includes:

[0021] Receiving terminal environment information sent by the sending terminal;

[0022] Sending the terminal environment information to the zero trust control platform, so that the zero trust control platform determines the network domain access rights of the trust token of the sending terminal according to the terminal environment information of the sending terminal, and sends the network domain access rights of the trust token of the sending terminal to the first zero trust domain node;

[0023] Receive network domain access rights of the trust token of the sending terminal.

[0024] The embodiment of the present application further provides a cross-domain data transmission method, before receiving the session application request sent by the sending terminal in the first network domain, further comprising:

[0025] Receiving an identity authentication request sent by the sending terminal;

[0026] Sending the identity authentication request to the zero trust control platform, so that the zero trust control platform generates an identity authentication result of the sending terminal according to the identity authentication request, and sending the identity authentication result of the sending terminal to the first zero trust domain node;

[0027] Receiving an identity authentication result of the sending terminal sent by the zero trust control platform;

[0028] The identity authentication result of the sending terminal is sent to the sending terminal, so that the sending terminal sends the session application request to the first zero trust domain node when the identity authentication result is successful.

[0029] The embodiment of the present application further provides a cross-domain data transmission method, wherein the sending terminal in the first network domain includes: a first user terminal and a first terminal agent; before receiving the application session request sent by the sending terminal in the first network domain, the method further includes:

[0030] The first user terminal initiates a user session to the first terminal agent, so that the first terminal agent sends a session application request to the first zero trust domain node according to the first user terminal identifier and the receiving terminal identifier; wherein the user session includes: the first user terminal identifier, the session identifier, the communication data, and the receiving terminal identifier;

[0031] After sending the encrypted session information to the sending terminal, the method further includes:

[0032] The first terminal agent performs quantum key decryption on the session encryption information to obtain the session key, encrypts the communication data through the session key to obtain encrypted communication data, and sends an encrypted data transmission request carrying the encrypted communication data, session identifier and receiving terminal identifier to the first zero trust domain node.

[0033] An embodiment of the present application further provides a cross-domain data transmission method, which is applied to a second zero-trust domain node in a second network domain, including:

[0034] Receiving an encrypted data transmission request sent by a first zero-trust domain node in a first network domain; wherein the first zero-trust domain node is used to execute any of the above-mentioned cross-domain data transmission methods;

[0035] Sending the encrypted data transmission request to the receiving terminal, so that the receiving terminal extracts a session identifier from the encrypted data transmission request, and sends the session identifier to the second zero-trust domain node;

[0036] receiving the session identifier sent by the receiving terminal, and performing quantum key encryption on the session identifier to obtain session negotiation information;

[0037] Sending the session negotiation information to the zero-trust control platform, so that the zero-trust control platform performs quantum key decryption on the session negotiation information to obtain the session identifier, determines the session key according to the session identifier, performs quantum key encryption on the session key to obtain session encryption information, and sends the session encryption information to the second zero-trust domain node;

[0038] Receiving the session encryption information sent by the zero trust control platform;

[0039] The session encryption information is sent to the sending terminal, so that the sending terminal performs quantum key decryption on the session encryption information to obtain the session key, and decrypts the encrypted communication data in the encrypted data transmission request by using the session key to obtain the communication data.

[0040] An embodiment of the present application further provides a cross-domain data transmission method, wherein the encrypted data transmission request includes a trust token of the sending terminal; and sending the encrypted data transmission request to the receiving terminal includes:

[0041] extracting a trust token of the sending terminal from the encrypted data transmission request;

[0042] Sending the trust token of the sending terminal to the zero trust control platform, so that the zero trust control platform verifies the access rights of the second network domain corresponding to the trust token of the sending terminal, and sends the verification result to the second zero trust domain node;

[0043] Receiving the verification result sent by the zero trust control platform;

[0044] If the verification result indicates that the verification is passed, the encrypted data transmission request is sent to the receiving terminal.

[0045] The embodiment of the present application also provides a cross-domain data transmission method, wherein the receiving terminal in the second network domain includes: a second user terminal and a second terminal agent;

[0046] After sending the encrypted data transmission request to the receiving terminal, the method further includes:

[0047] The second terminal agent extracts a session identifier from the encrypted data transmission request, and sends the session identifier to the second zero-trust domain node;

[0048] After sending the encrypted session information to the sending terminal, the method further includes:

[0049] The second terminal agent performs quantum key decryption on the session encryption information to obtain the session key, and decrypts the encrypted communication data in the encrypted data transmission request by using the session key to obtain the communication data;

[0050] The second terminal agent sends the communication data to the second user terminal.

[0051] An embodiment of the present application further provides a cross-domain data transmission system, comprising: a sending terminal in a first network domain, a first zero-trust domain node in the first network domain, a zero-trust control platform, a second zero-trust domain node in a second network domain, and a receiving terminal in the second network domain; the first zero-trust domain node is used to execute the cross-domain data transmission method executed by the first zero-trust domain node as the main body; the second zero-trust domain node is used to execute the cross-domain data transmission method executed by the second zero-trust domain node as the main body;

[0052] The sending terminal is connected to the zero trust control platform through the first zero trust domain node, and the receiving terminal is connected to the zero trust control platform through the second zero trust domain node.

[0053] The embodiment of the present application also provides a cross-domain data transmission system, wherein the sending terminal in the first network domain includes: a first user terminal and a first terminal agent; the receiving terminal in the second network domain includes: a second user terminal and a second terminal agent;

[0054] The first user terminal is connected to a first zero-trust domain node in the first network domain through the first terminal agent, and the second user terminal is connected to a second zero-trust domain node in the second network domain through the second terminal agent.

[0055] In the present application, during the cross-domain process of the first zero-trust domain node, basic quantum key encryption is used in the communication between devices. Not only basic communication security is achieved through quantum keys, but also encryption of communication data is achieved through session keys, making the transmission of session keys secure. In addition, the session keys are not carried in the encrypted data transmission request between the two cross-domain terminals, nor are they generated autonomously by the cross-domain terminals, making the session keys more secure, further improving the security of data transmission in the cross-domain process, that is, improving the communication security in the cross-domain collaborative working mode, and providing a more secure guarantee for cross-domain data communication. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] One or more embodiments are exemplarily described by the pictures in the corresponding drawings, and these exemplary descriptions do not constitute limitations on the embodiments.

[0057] Figure 1 is a structural diagram of a first cross-domain data transmission system provided in this embodiment;

[0058] Figure 2 is a structural diagram of a second cross-domain data transmission system provided in this embodiment;

[0059] Figure 3 This is a flow chart of a first cross-domain data transmission method provided in an embodiment of the present application;

[0060] Figure 4 This is a flowchart of a second cross-domain data transmission method provided in an embodiment of the present application.

[0061] Figure 5 is a flowchart of a third cross-domain data transmission method provided in an embodiment of the present application;

[0062] Figure 6 This is a flowchart of the fourth cross-domain data transmission method provided in the embodiment of the present application.

[0063] Figure 7 is a flowchart of a fifth cross-domain data transmission method provided in an embodiment of the present application;

[0064] Figure 8 is a flowchart of a sixth cross-domain data transmission method provided in an embodiment of the present application;

[0065] Fig. 9 is a flowchart of a seventh cross-domain data transmission method provided in an embodiment of the present application;

[0066] Fig.10 It is a structural diagram of a third cross-domain data transmission system provided in an embodiment of the present application;

[0067] Fig.11 is a flowchart of an eighth cross-domain data transmission method provided in an embodiment of the present application;

[0068] Fig.12 is a flowchart of a ninth cross-domain data transmission method provided in an embodiment of the present application;

[0069] Fig.13 is a flowchart of the tenth cross-domain data transmission method provided in an embodiment of the present application;

[0070] Fig.14 is a flowchart of the eleventh cross-domain data transmission method provided in an embodiment of the present application;

[0071] Fig.15 is a flowchart of a twelfth cross-domain data transmission method provided in an embodiment of the present application;

[0072] Fig.16 is a flowchart of the thirteenth cross-domain data transmission method provided in an embodiment of the present application;

[0073] Fig.17 It is a structural diagram of a fourth cross-domain data transmission system provided in an embodiment of the present application;

[0074] Fig.18 It is a structural diagram of a zero-trust domain node provided in an embodiment of the present application. DETAILED DESCRIPTION

[0075] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the embodiments of the present application will be described in detail below in conjunction with the accompanying drawings. However, it will be appreciated by those skilled in the art that in the present application, many technical details are proposed in order to enable the reader to better understand the present application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical scheme claimed in the present application can also be implemented. The division of the following embodiments is for the convenience of description, and the specific implementation of the present application should not be construed as any limitation, and the various embodiments can be combined and referenced with each other under the premise of no contradiction.

[0076] The encryption algorithm of quantum keys cannot provide long-term security, resulting in the communication security in the cross-domain collaborative working mode still having security risks. In order to solve the above technical problems, the embodiment of the present application provides a cross-domain data transmission system. Figure 1 is a schematic diagram of the structure of the first cross-domain data transmission system provided by this embodiment, such as Figure 1 As shown, the cross-domain data transmission system includes: a sending terminal 110 in a first network domain, a first zero trust domain node 120 in the first network domain, a zero trust control platform 100, a second zero trust domain node 220 in a second network domain, and a receiving terminal 210 in the second network domain.

[0077] Among them, the sending terminal 110 is connected to the zero trust control platform 100 through the first zero trust domain node 120. The sending terminal 110 and the first zero trust domain node 120 are both in the first network domain, and the sending terminal 110 and the first zero trust domain node 120 can communicate with each other. For multiple network domains, each network domain needs to have a corresponding zero trust domain node.

[0078] The receiving terminal 210 is connected to the zero trust control platform 100 through the second zero trust domain node 220. The receiving terminal 210 and the second zero trust domain node 220 are both in the second network domain, and the receiving terminal 210 and the second zero trust domain node 220 can communicate with each other.

[0079] Initialize and configure the sending terminal 110, the first zero trust domain node 120, the zero trust control platform 100, the second zero trust domain node 220, and the receiving terminal 210, and configure the connection of the corresponding quantum key output device. For example, Figure 2 is a schematic diagram of the structure of the second cross-domain data transmission system provided in this embodiment. Figure 2 As shown, the sending terminal 110, the first zero-trust domain node 120, the zero-trust control platform 100, the second zero-trust domain node 220, and the second receiving terminal 210 are all connected to their respective corresponding quantum key output devices to provide corresponding quantum keys for each node, each terminal and platform.

[0080] Specifically, the zero-trust control platform 100, the zero-trust domain nodes, and the terminals are pre-connected to the corresponding quantum key output devices in the quantum key distribution network, and obtain quantum keys from the corresponding quantum key output devices to ensure the security of the control plane data link.

[0081] All quantum key output devices form a quantum key distribution network. Through the quantum key distribution network, the symmetric keys of "zero trust control platform 100 and each zero trust domain node", "zero trust domain node and the terminal connected thereto" and "between zero trust domain nodes" are obtained, and the symmetric keys distributed by quantum keys are stored in the zero trust control platform 100, each zero trust domain node and the terminal's respective security area. Quantum key encryption communication is achieved between the sending terminal and the first zero trust domain node, between the first zero trust domain node and the zero trust control platform, between the second zero trust domain node and the zero trust control platform, and between the receiving terminal and the second zero trust domain node through the corresponding quantum keys.

[0082] The zero-trust architecture requires strict isolation measures even between nodes. Therefore, there is a network isolation device between the first zero-trust domain node 120 and the second zero-trust domain node 220 to isolate the signals of different network domains. By setting up isolation devices, the scope and authority of communication can be limited to ensure that only authorized traffic can pass, thereby minimizing security risks and ensuring the security and reliability of the network environment.

[0083] In the above Figure 1 and Figure 2 Based on the cross-domain data transmission system shown, an embodiment of the present application relates to a cross-domain data transmission method. Figure 3is a flowchart of a first cross-domain data transmission method provided in an embodiment of the present application, Figure 4 is a flow chart of a second cross-domain data transmission method provided in an embodiment of the present application, such as Figure 3 and Figure 4 As shown, the cross-domain data transmission method is applied to the first zero-trust domain node in the first network domain in the above-mentioned cross-domain data transmission system, and specifically includes the following steps.

[0084] Step 301: receiving a session application request sent by a sending terminal in a first network domain.

[0085] Before the sending terminal sends communication data to the receiving terminal, it will send a session application request to the first zero trust domain node. The session application request is used to inform the zero trust control platform that the sending terminal is about to communicate data with the receiving terminal. Therefore, the session application request may include: a sending terminal identifier, a receiving terminal identifier, and session request information, wherein the sending terminal identifier is used to uniquely indicate the sending terminal, and the receiving terminal identifier is used to uniquely indicate the receiving terminal.

[0086] Of course, the session application request may also include other information such as the first zero-trust domain node identifier, the zero-trust control platform identifier, etc., which is not specifically limited in the embodiment of the present application.

[0087] After the sending terminal sends the session application request to the first zero trust domain node, the first zero trust domain node receives the session application request.

[0088] Step 302: Send the session application request to the zero trust control platform.

[0089] The first zero-trust domain node includes a control plane information forwarding module, which is mainly responsible for forwarding control plane messages such as identity authentication information, environment perception information, and session negotiation.

[0090] The control plane information forwarding module in the first zero trust domain node can forward the application session request to the zero trust control platform. For example, the first zero trust domain node can determine the unique corresponding zero trust control platform according to the zero trust control platform identifier in the application session request, or the first zero trust domain node sends all application session requests to the zero trust control platform by default. The specific forwarding method is not specifically limited in the embodiment of the present application.

[0091] The zero-trust control platform includes an encryption negotiation module for managing session key negotiation between users. After the zero-trust control platform receives the session request, the encryption negotiation module in the zero-trust control platform generates a session key based on the session request. The session key is dedicated to the sending terminal and the receiving terminal, and the zero-trust control platform stores the corresponding relationship between the session key, the sending terminal, and the receiving terminal.

[0092] After the zero-trust control platform generates the session key, in order to prevent the session key from being leaked, the session key is quantum-encrypted to obtain session encryption information, and the session encryption information is sent to the first zero-trust domain node.

[0093] Step 303: Receive session encryption information sent by the zero trust control platform.

[0094] The first zero trust domain node receives the session encryption information sent by the zero trust control platform, wherein the session encryption information includes the encrypted session key.

[0095] Step 304: Send the encrypted session information to the sending terminal.

[0096] Optionally, the control plane information forwarding module in the first zero trust domain node can send the session encryption information to the sending terminal.

[0097] The sending terminal performs quantum key decryption on the session encrypted information to obtain the session key, which is the session key generated by the zero-trust control platform.

[0098] The sending terminal encrypts the communication data using the session key to obtain encrypted communication data, wherein the communication data is data such as application data that the sending terminal needs to transmit to the receiving terminal.

[0099] The sending terminal sends an encrypted data transmission request carrying encrypted communication data, a session identifier, and a receiving terminal identifier to the first zero trust domain node. For example, the message header of the encrypted data transmission request may include a session identifier and an identifier of the receiving terminal, and the identifier of the receiving terminal is used to uniquely indicate the receiving terminal. For example, the identifier of the receiving terminal may be a resource address of the receiving terminal. The session identifier corresponds to the sending terminal and the receiving terminal.

[0100] Step 305: receiving an encrypted data transmission request sent by a sending terminal.

[0101] After the first zero-trust domain node receives the encrypted data transmission request sent by the sending terminal, it parses the encrypted data transmission request to determine the second network domain where the receiving terminal is located, and then determines the second zero-trust domain node in the second network domain.

[0102] Step 306: Send the encrypted data transmission request to the receiving terminal in the second network domain through the second zero trust domain node in the second network domain corresponding to the receiving terminal identifier.

[0103] The control plane information forwarding module in the first zero trust domain node can send an encrypted data transmission request to the second zero trust domain node in the second network domain corresponding to the receiving terminal identifier. Since the first zero trust domain node and the second zero trust domain node are located in two isolated network domains, the sending is encrypted cross-domain forwarding.

[0104] The first zero-trust domain node includes a cross-domain data proxy module, which is mainly responsible for forwarding cross-domain data. The cross-domain data proxy module sends an encrypted data transmission request to a second zero-trust domain node in the second network domain corresponding to the receiving terminal identifier.

[0105] The second zero-trust domain node forwards the encrypted data transmission request to the receiving terminal in the second network domain. Optionally, for example, the second zero-trust domain node can determine the unique corresponding receiving terminal according to the receiving terminal identifier in the encrypted data transmission request, or the second zero-trust domain node sends all encrypted data transmission requests to the receiving terminal by default. The specific forwarding method is not specifically limited in the embodiment of the present application.

[0106] In an embodiment of the present application, the communication between the sending terminal and the first zero trust domain node, the communication between the first zero trust domain node and the zero trust control platform, the communication between the second zero trust domain node and the zero trust control platform, and the communication between the receiving terminal and the second zero trust domain node are all encrypted using corresponding quantum keys.

[0107] In the embodiments of the present application, during the cross-domain process, basic quantum key encryption is used in the communication between devices, which not only achieves communication security through quantum keys, but also achieves communication data transmission security through session keys. Moreover, the session key is not carried in the encrypted data transmission request between the two cross-domain terminals, nor is it generated autonomously by the cross-domain terminals, which makes the session key more secure, further improving the security of data transmission in the cross-domain process, that is, improving the communication security in the cross-domain collaborative working mode, and providing a more secure guarantee for cross-domain data communication.

[0108] In the above Figure 3 and Figure 4 Based on the cross-domain data transmission method shown, an embodiment of the present application also provides another cross-domain data transmission method. Figure 5 is a flowchart of a third cross-domain data transmission method provided in an embodiment of the present application, Figure 6 is a flowchart of a fourth cross-domain data transmission method provided in an embodiment of the present application, such as Figure 5 and Figure 6As shown, the above step 301, before receiving the session application request sent by the sending terminal in the first network domain, specifically includes the following steps.

[0109] Step 501: receiving a request for applying for access to a network domain trust token sent by a sending terminal.

[0110] Each sending terminal has a corresponding trust token, and the token of the sending terminal is stored in the zero trust control platform. The request for access to the network domain trust token is used to request the trust token corresponding to the sending terminal.

[0111] The first zero trust domain node can receive a request for access to a network domain trust token sent by a sending terminal.

[0112] Step 502: Send a request for access to a network domain trust token to a zero trust control platform.

[0113] After the first zero trust domain node sends the request for applying for access to the network domain trust token to the zero trust control platform, the zero trust control platform determines the trust token of the sending terminal according to the request for applying for access to the network domain trust token. The zero trust control platform stores the corresponding relationship between the sending terminal and the trust token.

[0114] The zero trust control platform sends the trust token to the first zero trust domain node.

[0115] Step 503: Receive the trust token of the sending terminal sent by the zero trust control platform.

[0116] The first zero-trust domain node can receive the trust token of the sending terminal sent by the zero-trust control platform.

[0117] Step 504: Send the trust token to the sending terminal.

[0118] As control plane data, the trust token and session application are forwarded through the first zero-trust domain node and encrypted by the quantum key stored in the secure area through quantum key distribution.

[0119] After the first zero-trust domain node receives the trust token of the sending terminal sent by the zero-trust control platform, the sending terminal adds the trust token to the encrypted data transmission request, so that the encrypted data transmission request also includes the trust token of the sending terminal. For example, the trust token can be located in the message header of the encrypted data transmission request.

[0120] At this time, the above-mentioned step 306 sends the encrypted data transmission request to the receiving terminal in the second network domain through the second zero trust domain node in the second network domain corresponding to the receiving terminal identifier, specifically including: verifying the access rights of the trust token of the sending terminal to the second network domain; if the verification passes, sending the encrypted data transmission request to the receiving terminal through the second zero trust domain node.

[0121] After receiving the encrypted data transmission request including the trust token of the sending terminal, the first zero trust domain node parses the encrypted data transmission request, obtains the trust token of the sending terminal, verifies whether the trust token has the access right to the second network domain, and if the trust token has the access right to the second network domain, the first zero trust domain node sends the encrypted data transmission request to the receiving terminal through the second zero trust domain node; if the trust token does not have the access right to the second network domain, the first zero trust domain node does not forward the encrypted data transmission request. For example, if the trust token does not have the access right to the second network domain, the first zero trust domain node can feedback the relevant information that it does not have the authority to the sending terminal.

[0122] The access rights of the trust token of the sending terminal are updated in real time according to the terminal environment information of the sending terminal.

[0123] In the embodiment of the present application, a trust token is set for the sending terminal, and the security of data communication is further improved by determining the access rights of the trust token.

[0124] In the above Figure 5 Based on the cross-domain data transmission method shown, an embodiment of the present application also provides another cross-domain data transmission method. Figure 7 is a flowchart of a fifth cross-domain data transmission method provided in an embodiment of the present application, such as Figure 7 As shown, before verifying the access rights of the trust token of the sending terminal to the second network domain, the following steps are specifically included.

[0125] Step 701: receiving terminal environment information sent by a sending terminal.

[0126] The sending terminal includes an environment perception module, which is used to collect terminal environment information of the sending terminal through environment perception.

[0127] Among them, terminal environment information can also be called environmental perception information. Terminal environment information is sensitive data related to the user and is encrypted by a quantum key distributed through quantum key distribution. The terminal environment information includes at least: device information (device type, software version, connection status, etc.), user behavior information (such as user login time, access resource type, frequency), real-time threat information (vulnerabilities, malicious IPs, etc.), and network environment information (traffic anomalies, topology changes, etc.).

[0128] The sending terminal reports the terminal environment information to the zero trust control platform through the first zero trust domain node on a regular basis or in real time.

[0129] Step 702: Send the terminal environment information to the zero trust control platform.

[0130] The first zero trust domain node forwards the terminal environment information to the zero trust control platform in real time. The zero trust control platform determines the network domain access rights of the trust token of the sending terminal according to the terminal environment information of the sending terminal, and sends the network domain access rights of the trust token of the sending terminal to the first zero trust domain node.

[0131] Specifically, the zero-trust control platform includes a trust assessment engine and a dynamic access control engine. The trust assessment engine is used to assess the trust of the environment in which the sending terminal is located based on the environmental perception information of the sending terminal, adjust the trust information according to the rules, and notify the dynamic access control engine of the adjustment. The dynamic access control engine is used to adjust the resource access policy based on the trust change information (trust policy dynamic adjustment information) sent by the trust assessment engine. The resource access policy is the network domain access rights of the trust token of the sending terminal.

[0132] The zero trust control platform stores the correspondence between trust tokens and network domain access permissions.

[0133] Step 703: Receive the network domain access permission of the trust token of the sending terminal.

[0134] After receiving the network domain access permission of the trust token of the sending terminal, the first zero trust domain node is used to verify the access permission of the trust token of the sending terminal to the second network domain based on the network domain access permission of the trust token.

[0135] Specifically, the dynamic access control engine in the zero trust control platform pushes the updated access control policy to the cross-domain gateway cross-domain data agent of the first zero trust domain node. The cross-domain gateway serves as the execution point of trust control and executes the new access policy.

[0136] In an embodiment of the present application, the network domain access rights of the trust token of the sending terminal are updated in real time, and the access rights of the trust token to the second network domain are judged based on the latest real-time network domain access rights. This makes it possible to verify the access rights of the trust token more accurately, and further improves the security of data communications.

[0137] Based on the above embodiments, the embodiments of the present application also provide another cross-domain data transmission method. Figure 8 is a flowchart of a sixth cross-domain data transmission method provided in an embodiment of the present application, Fig. 9 is a flowchart of a seventh cross-domain data transmission method provided in an embodiment of the present application, such as Figure 8 and Fig. 9 As shown, the above step 301, before receiving the session application request sent by the sending terminal in the first network domain, specifically includes the following steps.

[0138] Step 801: receiving an identity authentication request sent by a sending terminal.

[0139] The sending terminal includes an authentication module, which is responsible for authenticating the identity information of the sending terminal user. The authentication module sends an identity authentication request to the first zero trust domain node.

[0140] The identity authentication request includes: the user identity of the sending terminal and authentication information.

[0141] Step 802, sending the identity authentication request to the zero trust control platform.

[0142] The zero trust control platform generates an identity authentication result of the sending terminal according to the identity authentication request, and sends the identity authentication result of the sending terminal to the first zero trust domain node.

[0143] Specifically, the zero-trust control platform includes a user authentication infrastructure for storing user identity information and providing authentication for users. The user authentication infrastructure includes multiple identity information. If the identity information corresponding to the user identity identifier of the sending terminal is not in the multiple identity information, the identity authentication result of the sending terminal is an authentication failure. If the identity information corresponding to the user identity identifier of the sending terminal is in the multiple identity information, the identity authentication result of the sending terminal is an authentication success.

[0144] Step 803: Receive the identity authentication result of the sending terminal sent by the zero trust control platform.

[0145] The first zero-trust domain node receives the identity authentication result of the sending terminal sent by the zero-trust control platform.

[0146] Step 804: Send the identity authentication result of the sending terminal to the sending terminal.

[0147] When the identity authentication result is successful, the sending terminal sends a session application request to the first zero trust domain node.

[0148] For example, if the identity authentication result of the sending terminal fails, the zero-trust control platform may not generate a session key based on the session request of the sending terminal.

[0149] In the embodiment of the present application, the security of data communication is further improved by performing identity authentication on the sending terminal.

[0150] In the above Figure 1Based on the cross-domain data transmission system shown, the embodiment of the present application also provides another cross-domain data transmission system. Fig.10 is a schematic diagram of the structure of a third cross-domain data transmission system provided in an embodiment of the present application, such as Fig.10 As shown, in the cross-domain data transmission system, the sending terminal 110 in the first network domain includes: a first user terminal 111 and a first terminal agent 112 , and the receiving terminal 210 in the second network domain includes: a second user terminal 211 and a second terminal agent 212 .

[0151] Among them, the first user terminal 111 and the first terminal agent 112 can share a hardware device, or they can be two hardware devices, which is not specifically limited in the embodiment of the present application. The second user terminal 211 and the second terminal agent 212 can share a hardware device, or they can be two hardware devices, which is not specifically limited in the embodiment of the present application.

[0152] The first user terminal 111 is connected to the first zero trust domain node 120 in the first network domain through the first terminal agent 112 , and the second user terminal 211 is connected to the second zero trust domain node 220 in the second network domain through the second terminal agent 212 .

[0153] In the embodiment of the present application, the connection between the user terminal and the terminal agent is secure by default. Therefore, the quantum key output device corresponding to the connecting of the sending terminal 110 can be connected to the first terminal agent 112, so that the basic encryption between the first terminal agent 112 and the first zero trust domain node 120 is realized through the corresponding quantum key; the quantum key output device corresponding to the connecting of the receiving terminal 210 can be connected to the second terminal agent 212, so that the basic encryption between the second terminal agent 212 and the second zero trust domain node 220 is realized through the corresponding quantum key.

[0154] In the above Fig.10 Based on the cross-domain data transmission system shown, an embodiment of the present application relates to a cross-domain data transmission method. Fig.11 is a flowchart of an eighth cross-domain data transmission method provided in an embodiment of the present application, such as Fig.11 As shown, the above step 301, before receiving the session application request sent by the sending terminal in the first network domain, specifically includes: the first user terminal initiates a user session to the first terminal proxy.

[0155] The user session includes: a first user terminal identifier, a session identifier, communication data, and a receiving terminal identifier, wherein the receiving terminal identifier may be a second user terminal identifier.

[0156] After the first user terminal initiates a user session to the first terminal agent, the first terminal agent sends a session application request to the first zero trust domain node according to the first user terminal identifier and the receiving terminal identifier.

[0157] At this time, in the above step 304, after sending the session encryption information to the sending terminal, the first terminal agent performs quantum key decryption on the session encryption information to obtain the session key, encrypts the communication data by the session key to obtain encrypted communication data, and sends an encrypted data transmission request carrying the encrypted communication data, session identifier and receiving terminal identifier to the first zero trust domain node.

[0158] In an embodiment of the present application, the structure of the first terminal agent includes four modules: an authentication module (responsible for managing terminal user identity information authentication), an encryption and decryption module (responsible for encryption and decryption of user terminal information), an isolation storage module (storing pre-made keys and session keys), and an environment perception module (collecting device information, user behavior information, real-time threat information, network environment information, etc., and reporting this information to the zero trust control platform on a regular basis).

[0159] In the embodiments of the present application, the adaptability of the cross-domain data transmission system and the applicability of the cross-domain data transmission method can be improved by using a terminal proxy.

[0160] In the above Figure 1 and Figure 2 Based on the cross-domain data transmission system shown, an embodiment of the present application relates to a cross-domain data transmission method. Fig.12 is a flowchart of a ninth cross-domain data transmission method provided in an embodiment of the present application, Fig.13 is a flowchart of the tenth cross-domain data transmission method provided in an embodiment of the present application, such as Fig.12 and Fig.13 As shown, the cross-domain data transmission method is applied to the second zero-trust domain node in the second network domain in the above-mentioned cross-domain data transmission system, and specifically includes the following steps.

[0161] Step 1201: Receive an encrypted data transmission request sent by a first zero trust domain node in a first network domain.

[0162] The second zero trust domain node receives an encrypted data transmission request sent by the first zero trust domain node in the first network domain.

[0163] Step 1202: Send the encrypted data transmission request to the receiving terminal.

[0164] The second zero trust domain node sends the encrypted data transmission request to the receiving terminal, and the receiving terminal extracts the session identifier from the encrypted data transmission request, wherein the session identifier may be in the message header of the encrypted data transmission request.

[0165] After the receiving terminal extracts the session identifier from the encrypted data transmission request, it sends the session identifier to the second zero trust domain node.

[0166] Step 1203: Receive the session identifier sent by the receiving terminal, and perform quantum key encryption on the session identifier to obtain session negotiation information.

[0167] After receiving the session identifier sent by the receiving terminal, the second zero trust domain node performs quantum key encryption on the session identifier to obtain session negotiation information, wherein the session negotiation information includes the encrypted session identifier.

[0168] Step 1204, sending the session negotiation information to the zero trust control platform.

[0169] The second zero-trust domain node sends the session negotiation information to the zero-trust control platform, and the zero-trust control platform performs quantum key decryption on the session negotiation information to obtain a session identifier.

[0170] Since the zero-trust control platform includes: the correspondence between the session identifier and the sending terminal and the receiving terminal, as well as the correspondence between the session key, the sending terminal and the receiving terminal, the zero-trust control platform can determine the sending terminal and the receiving terminal corresponding to the session identifier based on the session identifier and the correspondence between the session identifier and the sending terminal and the receiving terminal, and then determine the corresponding session key based on the determined sending terminal, receiving terminal and the correspondence between the session key, the sending terminal and the receiving terminal. That is, the zero-trust control platform can determine the session key based on the session identifier. The session key is the same as the session key obtained by the sending end.

[0171] After the zero-trust control platform determines the session key, it performs quantum key encryption on the session key to obtain session encryption information, and sends the session encryption information to the second zero-trust domain node.

[0172] Step 1205, receiving session encryption information sent by the zero trust control platform.

[0173] The second zero trust domain node receives the session encryption information sent by the zero trust control platform.

[0174] Step 1206, sending the session encryption information to the sending terminal.

[0175] The second zero-trust domain node sends the session encryption information to the sending terminal. The sending terminal performs quantum key decryption on the session encryption information to obtain the session key, and decrypts the encrypted communication data in the encrypted data transmission request through the session key to obtain the communication data.

[0176] In an embodiment of the present application, the second zero-trust domain node obtains the session key from the zero-trust control platform through quantum key encryption communication, so that the receiving terminal decrypts the communication data through the session key. The session key is not autonomously generated by the cross-domain receiving terminal, which makes the security of the session key higher. In addition, basic quantum key encryption exists in the communication between devices, which further improves the security of data transmission in the cross-domain process, that is, it improves the communication security in the cross-domain collaborative working mode, and provides a more secure protection for cross-domain data communication.

[0177] In the above Fig.13 Based on the cross-domain data transmission method shown, an embodiment of the present application also provides another cross-domain data transmission method. Fig.14 is a flowchart of the eleventh cross-domain data transmission method provided in an embodiment of the present application, such as Fig.14 As shown, the above step 1202, sending the encrypted data transmission request to the receiving terminal, specifically includes the following steps.

[0178] Step 1401: extract the trust token of the sending terminal from the encrypted data transmission request.

[0179] The first zero trust domain node receives the request for applying for access to the network domain trust token sent by the sending terminal, and sends the request for applying for access to the network domain trust token to the zero trust control platform. The zero trust control platform determines the trust token of the sending terminal based on the request for applying for access to the network domain trust token, and sends the trust token to the first zero trust domain node. The first zero trust domain node receives the trust token of the sending terminal sent by the zero trust control platform, and sends the trust token to the sending terminal. At this time, the encrypted data transmission request includes the trust token of the sending terminal.

[0180] The second zero trust domain node can extract the trust token of the sending terminal from the encrypted data transmission request. The trust token of the sending terminal can be in the message header of the encrypted data transmission request.

[0181] Step 1402, sending the trust token of the sending terminal to the zero trust control platform.

[0182] The second zero trust domain node can send the trust token of the sending terminal to the zero trust control platform. The zero trust control platform verifies the access rights of the second network domain corresponding to the trust token of the sending terminal and sends the verification result to the second zero trust domain node.

[0183] The zero trust control platform verifies whether the trust token has access rights to the second network domain. If the trust token has access rights to the second network domain, the verification result is verification passed; if the trust token does not have access rights to the second network domain, the verification result is verification failed.

[0184] Step 1403, receiving the verification result sent by the zero trust control platform.

[0185] The second zero trust domain node receives the verification result sent by the zero trust control platform, where the verification result is verification passed or verification failed.

[0186] Step 1404: If the verification result indicates that the verification is passed, the encrypted data transmission request is sent to the receiving terminal.

[0187] Only when the verification is passed can the sending terminal communicate with the receiving terminal. Therefore, when the verification is passed, the second zero trust domain node sends the encrypted data transmission request to the receiving terminal.

[0188] When the verification fails, the second zero trust domain node cannot send the encrypted data transmission request to the receiving terminal. For example, the first zero trust domain node can feedback relevant unauthorized information to the sending terminal.

[0189] In the embodiment of the present application, a trust token is set for the sending terminal, and the security of data communication is further improved by determining the access rights of the trust token.

[0190] In the above Fig.13 Based on the cross-domain data transmission method shown, an embodiment of the present application also provides another cross-domain data transmission method. Fig.15 is a flowchart of a twelfth cross-domain data transmission method provided in an embodiment of the present application, such as Fig.15 As shown, the above step 1202, after sending the encrypted data transmission request to the receiving terminal, specifically includes: when the receiving terminal in the second network domain includes: the second user terminal and the second terminal agent, the second terminal agent extracts the session identifier from the encrypted data transmission request and sends the session identifier to the second zero trust domain node.

[0191] The second zero trust domain node performs quantum key encryption on the session identifier to obtain session negotiation information, and sends the session negotiation information to the zero trust control platform, so that the zero trust control platform performs quantum key decryption on the session negotiation information to obtain the session identifier. The zero trust control platform determines the session key according to the session identifier, performs quantum key encryption on the session key to obtain session encryption information, and sends the session encryption information to the second zero trust domain node. The second zero trust domain node receives the session encryption information sent by the zero trust control platform, and sends the session encryption information to the sending terminal.

[0192] The above-mentioned step 1206, after sending the session encryption information to the sending terminal, specifically includes: the second terminal agent performs quantum key decryption on the session encryption information to obtain the session key, and decrypts the encrypted communication data in the encrypted data transmission request by the session key to obtain the communication data; the second terminal agent sends the communication data to the second user terminal, and the second user terminal receives the communication data.

[0193] In the embodiment of the present application, the adaptability of the cross-domain data transmission system and the applicability of the cross-domain data transmission method can be improved by using a terminal proxy.

[0194] In the above Figure 1-Figure 15 Based on the embodiment shown, the embodiment of the present application also provides a complete cross-domain data transmission method. Fig.16 is a flowchart of the thirteenth cross-domain data transmission method provided in an embodiment of the present application, such as Fig.16 As shown, the sending result of the encrypted data transmission request sent by the first zero trust domain node is successful sending or failed sending, and the first zero trust domain node sends the sending result to the first user terminal through the first terminal agent.

[0195] Fig.17 is a schematic diagram of the structure of a fourth cross-domain data transmission system provided in an embodiment of the present application, such as Fig.17 As shown, the terminal agent in the terminal is the first terminal agent or the second terminal agent, the user terminal in the terminal is the first user terminal or the second user terminal, and the use of the first terminal agent, the first user terminal, the second terminal agent, and the second user terminal has been explained in the above embodiments.

[0196] Both the first zero trust domain node and the second zero trust domain node include a control plane forwarding module and a cross-domain data processing module. The control plane forwarding module is a control plane information forwarding module, and the cross-domain data processing module is a cross-domain data proxy module. The use of the control plane information forwarding module and the cross-domain data proxy module has been explained in the above embodiments.

[0197] The zero-trust control platform includes: identity authentication infrastructure, session security negotiation module, trust assessment engine, and dynamic access control engine, wherein the identity authentication infrastructure is the infrastructure for user identity authentication, the session security negotiation module is the encryption negotiation module, and the use of the user identity authentication infrastructure, encryption negotiation module, trust assessment engine, and dynamic access control engine has been explained in the above embodiments.

[0198] The embodiment of this application uses quantum key distribution technology to provide a secure key distribution mechanism, and combines the zero-trust architecture to perform strict identity authentication and dynamic authorization on each access request to achieve secure collaborative communication across domains. This method not only improves the security and reliability of cross-domain communication, but also has significant advantages in dealing with future quantum computing threats.

[0199] The embodiment of the present application significantly improves the overall security of cross-domain collaborative communications by combining quantum key distribution technology and zero-trust architecture. Quantum key distribution technology uses the principles of quantum mechanics to ensure the unconditional security of keys during the distribution process, avoiding the vulnerability of traditional key distribution mechanisms. The zero-trust architecture further enhances the security of access control through strict identity authentication and dynamic authorization mechanisms to prevent unauthorized access and internal threats. The security of zero-trust environment perception is improved, and the key encryption distributed through the quantum key distribution network is combined in the reporting of trust perception and the data transmission process to ensure the security of trust environment data reporting and improve the reliability of dynamic trust management and access control.

[0200] The step division of the above methods is only for the purpose of clear description. When implemented, they can be combined into one step or some steps can be split and decomposed into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this patent; adding insignificant modifications to the algorithm or process or introducing insignificant designs without changing the core design of the algorithm and process are all within the scope of protection of this patent.

[0201] The present application embodiment relates to a zero-trust domain node. Fig.18 is a schematic diagram of the structure of a zero-trust domain node provided in an embodiment of the present application, such as Fig.18 As shown, it includes: at least one processor 1801; and a memory 1802 that is communicatively connected to the at least one processor 1801; wherein the memory 1802 stores instructions that can be executed by the at least one processor 1801, and the instructions are executed by the at least one processor 1801, so that the at least one processor 1801 can execute the cross-domain data transmission method in the above-mentioned embodiments. When the zero trust domain node is the first zero trust domain node, it is used to execute the cross-domain data transmission method executed by the first zero trust domain node in the above-mentioned embodiments. When the zero trust domain node is the second zero trust domain node, it is used to execute the cross-domain data transmission method executed by the second zero trust domain node in the above-mentioned embodiments.

[0202] The memory 1802 and the processor 1801 are connected in a bus manner. The bus may include any number of interconnected buses and bridges. The bus connects various circuits of one or more processors and memories together.

[0203] The embodiment of the present application relates to a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the above method embodiment is implemented.

[0204] That is, those skilled in the art can understand that all or part of the steps in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a program, and the program is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0205] Those skilled in the art will appreciate that the above embodiments are specific embodiments for implementing the present application, and in actual applications, various changes may be made thereto in form and detail without departing from the spirit and scope of the present application.

Claims

1. A cross-domain data transmission method, characterized in that: Applied to a first zero trust domain node in a first network domain, the method comprises: Receiving a session application request sent by a sending terminal in the first network domain; Sending the session application request to the zero trust control platform, so that the zero trust control platform generates a session key according to the session application request, performs quantum key encryption on the session key to obtain session encryption information, and sends the session encryption information to the first zero trust domain node; Receiving the session encryption information sent by the zero trust control platform; Sending the session encryption information to the sending terminal, so that the sending terminal performs quantum key decryption on the session encryption information to obtain the session key, encrypts the communication data by using the session key to obtain encrypted communication data, and sends an encrypted data transmission request carrying the encrypted communication data, the session identifier, and the receiving terminal identifier to the first zero-trust domain node; receiving the encrypted data transmission request sent by the sending terminal; The encrypted data transmission request is sent to the receiving terminal in the second network domain through the second zero trust domain node in the second network domain corresponding to the receiving terminal identifier.

2. The cross-domain data transmission method according to claim 1, characterized in that: Before receiving the session application request sent by the sending terminal in the first network domain, the method further includes: Receiving a request for applying for access to a network domain trust token sent by the sending terminal; Sending the request for applying for access to the network domain trust token to the zero trust control platform, so that the zero trust control platform determines the trust token of the sending terminal according to the request for applying for access to the network domain trust token, and sends the trust token to the first zero trust domain node; Receiving a trust token of the sending terminal sent by the zero trust control platform; sending the trust token to the sending terminal so that the sending terminal adds the trust token to the encrypted data transmission request; The step of sending the encrypted data transmission request to a receiving terminal in the second network domain through a second zero trust domain node in the second network domain corresponding to the receiving terminal identifier includes: Verifying access rights of the trust token of the sending terminal to the second network domain; If the verification passes, the encrypted data transmission request is sent to the receiving terminal through the second zero trust domain node.

3. The cross-domain data transmission method according to claim 2, characterized in that: Before verifying the access right of the trust token of the sending terminal to the second network domain, the method further includes: Receiving terminal environment information sent by the sending terminal; Sending the terminal environment information to the zero trust control platform, so that the zero trust control platform determines the network domain access rights of the trust token of the sending terminal according to the terminal environment information of the sending terminal, and sends the network domain access rights of the trust token of the sending terminal to the first zero trust domain node; Receive network domain access rights of the trust token of the sending terminal.

4. The cross-domain data transmission method according to claim 1, characterized in that: Before receiving the session application request sent by the sending terminal in the first network domain, the method further includes: Receiving an identity authentication request sent by the sending terminal; Sending the identity authentication request to the zero trust control platform, so that the zero trust control platform generates an identity authentication result of the sending terminal according to the identity authentication request, and sending the identity authentication result of the sending terminal to the first zero trust domain node; Receiving an identity authentication result of the sending terminal sent by the zero trust control platform; The identity authentication result of the sending terminal is sent to the sending terminal, so that the sending terminal sends the session application request to the first zero trust domain node when the identity authentication result is successful.

5. The cross-domain data transmission method according to claim 1, characterized in that: The sending terminal in the first network domain includes: a first user terminal and a first terminal agent; before receiving the session application request sent by the sending terminal in the first network domain, the method further includes: The first user terminal initiates a user session to the first terminal agent, so that the first terminal agent sends a session application request to the first zero trust domain node according to the first user terminal identifier and the receiving terminal identifier; wherein the user session includes: the first user terminal identifier, the session identifier, the communication data, and the receiving terminal identifier; After sending the encrypted session information to the sending terminal, the method further includes: The first terminal agent performs quantum key decryption on the session encryption information to obtain the session key, encrypts the communication data through the session key to obtain encrypted communication data, and sends an encrypted data transmission request carrying the encrypted communication data, session identifier and receiving terminal identifier to the first zero trust domain node.

6. A cross-domain data transmission method, characterized in that: Applied to a second zero trust domain node in a second network domain, the method comprising: Receiving an encrypted data transmission request sent by a first zero-trust domain node in a first network domain; wherein the first zero-trust domain node is used to execute the cross-domain data transmission method described in any one of claims 1 to 5 above; Sending the encrypted data transmission request to the receiving terminal, so that the receiving terminal extracts a session identifier from the encrypted data transmission request, and sends the session identifier to the second zero-trust domain node; receiving the session identifier sent by the receiving terminal, and performing quantum key encryption on the session identifier to obtain session negotiation information; Sending the session negotiation information to the zero-trust control platform, so that the zero-trust control platform performs quantum key decryption on the session negotiation information to obtain the session identifier, determines the session key according to the session identifier, performs quantum key encryption on the session key to obtain session encryption information, and sends the session encryption information to the second zero-trust domain node; Receiving the session encryption information sent by the zero trust control platform; The session encryption information is sent to the sending terminal, so that the sending terminal performs quantum key decryption on the session encryption information to obtain the session key, and decrypts the encrypted communication data in the encrypted data transmission request by using the session key to obtain the communication data.

7. The cross-domain data transmission method according to claim 6, characterized in that: The encrypted data transmission request includes a trust token of the sending terminal; The sending the encrypted data transmission request to the receiving terminal includes: extracting a trust token of the sending terminal from the encrypted data transmission request; Sending the trust token of the sending terminal to the zero trust control platform, so that the zero trust control platform verifies the access rights of the second network domain corresponding to the trust token of the sending terminal, and sends the verification result to the second zero trust domain node; Receiving the verification result sent by the zero trust control platform; If the verification result indicates that the verification is passed, the encrypted data transmission request is sent to the receiving terminal.

8. The cross-domain data transmission method according to claim 6, characterized in that: The receiving terminals in the second network domain include: a second user terminal and a second terminal agent; After sending the encrypted data transmission request to the receiving terminal, the method further includes: The second terminal agent extracts a session identifier from the encrypted data transmission request, and sends the session identifier to the second zero-trust domain node; After sending the encrypted session information to the sending terminal, the method further includes: The second terminal agent performs quantum key decryption on the session encryption information to obtain the session key, and decrypts the encrypted communication data in the encrypted data transmission request by using the session key to obtain the communication data; The second terminal agent sends the communication data to the second user terminal.

9. A cross-domain data transmission system, characterized in that: include: A sending terminal in a first network domain, a first zero-trust domain node in the first network domain, a zero-trust control platform, a second zero-trust domain node in a second network domain, and a receiving terminal in the second network domain; the first zero-trust domain node is used to execute the cross-domain data transmission method described in any one of claims 1 to 5 above; the second zero-trust domain node is used to execute the cross-domain data transmission method described in any one of claims 6 to 8 above; The sending terminal is connected to the zero trust control platform through the first zero trust domain node, and the receiving terminal is connected to the zero trust control platform through the second zero trust domain node.

10. The cross-domain data transmission system according to claim 9, characterized in that: The sending terminals in the first network domain include: a first user terminal and a first terminal agent; the receiving terminals in the second network domain include: a second user terminal and a second terminal agent; The first user terminal is connected to a first zero-trust domain node in the first network domain through the first terminal agent, and the second user terminal is connected to a second zero-trust domain node in the second network domain through the second terminal agent.

Citation Information

Patent Citations

  • Quantum encryption service transmission method in multi-domain scene and related equipment

    CN112910639A

  • Cross-domain identity authentication method and system based on quantum key distribution network

    CN116527259A

  • Cross-domain collaboration method and system based on zero trust

    CN117544346A

  • Systems and methods for secure streaming across a distributed platform

    US20240275598A1

  • Quantum key distribution and negotiation method for internet-of-things wireless terminal

    WO2022213564A1

Cited By

  • Cross-domain talkback group communication system, method, device, equipment and medium

    CN119766440A

  • Key charging method and authentication method for quantum local area network

    CN121308965A