Cross-domain data transmission method and device, electronic device, and computer-readable medium
By creating intermediate nodes in the cloud platform for data decryption and security verification, the problem of low security in cross-domain data transmission within the same cloud platform is solved, thus improving the security of data transmission.
Patent Information
- Application Number
- CN202211009658.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-08-22
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2042-08-22
AI Technical Summary
In existing technologies, cross-domain data transmission within the same cloud platform is difficult to isolate using physical devices such as network gateways due to the blurred network boundaries, resulting in low security for cross-domain data transmission.
By creating intermediate nodes in the cloud platform, encrypted data is received, decrypted, and its security is verified, ensuring proper control over data transmission and improving security.
This enhances the security of cross-domain data transmission within the same cloud platform, preventing data tampering and theft during transmission and strengthening data transmission security.
Smart Images

Figure CN115361143B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a cross-domain data transmission method, a cross-domain data transmission device, an electronic device, and a computer-readable medium. Background Art
[0002] At present, with the widespread application of cloud computing, important businesses have been migrated to cloud platforms. Cloud computing has developed into an important support for ensuring the smooth operation of the national economy, but cloud platforms have become a hard-hit area for cyber attacks.
[0003] Among them, cross-network and cross-domain data transmission between different cloud platforms usually involves communication between the intranet and the extranet. In order to ensure the security of cross-domain data transmission, it can be isolated through physical devices such as network gates. However, for cross-domain data transmission within the same cloud platform, due to the fuzzy network boundaries, it is difficult to isolate it through physical devices such as network gates, resulting in lower security for cross-domain data transmission.
[0004] Therefore, how to reasonably control cross-domain data transmission to improve the security of cross-domain data transmission is an urgent problem to be solved. Summary of the invention
[0005] The embodiments of the present application provide a cross-domain data transmission method and device, an electronic device, and a computer-readable medium, thereby achieving reasonable control of cross-domain data transmission at least to a certain extent and improving the security of cross-domain data transmission.
[0006] In the first aspect, an embodiment of the present application provides a cross-domain data transmission method, which is applied to a cloud platform, wherein the cloud platform includes a first node and a second node located in different domains, and the method is executed by an intermediate node created by the cloud platform, and the method includes: receiving encrypted data sent by the first node; decrypting the encrypted data to obtain decrypted data; performing a security check on the encrypted data based on the decrypted data to obtain a check result; if the check result indicates that the check is passed, sending the encrypted data to the second node.
[0007] In one embodiment of the present application, based on the aforementioned scheme, the decrypted data includes decrypted source data and decrypted hash data to be verified, and the hash data to be verified is obtained by performing a hash operation on the source data; the security verification of the encrypted data according to the decrypted data to obtain a verification result includes: performing a hash operation on the decrypted source data to obtain target hash data; if the target hash data matches the hash data to be verified, a verification result is obtained to characterize that the security verification of the encrypted data has passed; if the target hash data does not match the hash data to be verified, a verification result is obtained to characterize that the transmission security verification of the encrypted data has failed.
[0008] In one embodiment of the present application, based on the aforementioned scheme, the encrypted data includes encrypted source data and encrypted hash data to be verified, and the hash data to be verified is obtained by performing a hash operation on the source data; decrypting the encrypted data to obtain decrypted data includes: decrypting the encrypted hash data to be verified to obtain decrypted hash data to be verified, and decrypting the encrypted source data to obtain decrypted source data.
[0009] In one embodiment of the present application, based on the aforementioned scheme, the encrypted data also includes an encrypted key, the encrypted source data is encrypted using the key, and the encrypted key and the encrypted hash data to be verified are encrypted using a public key; the decrypting of the encrypted hash data to be verified to obtain the decrypted hash data to be verified includes: decrypting the encrypted hash data to be verified using a private key to obtain the decrypted hash data to be verified; wherein the private key matches the public key; the decrypting of the encrypted hash data to be verified to obtain the decrypted hash data to be verified includes: decrypting the encrypted key using the private key to obtain the decrypted key; decrypting the encrypted source data using the decrypted key to obtain the decrypted source data.
[0010] In one embodiment of the present application, based on the aforementioned scheme, sending the encrypted data to the second node includes: disconnecting the first transmission link established with the first node; wherein the first transmission link is used to transmit the encrypted data; establishing a second transmission link with the second node; wherein the second transmission link is used to transmit the encrypted data; and sending the encrypted data to the second node via the second transmission link.
[0011] In one embodiment of the present application, based on the aforementioned scheme, before receiving the encrypted data sent by the first node, the method also includes: receiving an intermediate node creation request sent by the first node through the cloud platform, and creating the intermediate node based on the creation request; wherein, the intermediate node creation request is sent by the first node after receiving the cross-domain data request sent by the second node and performing identity verification on the second node.
[0012] In one embodiment of the present application, based on the aforementioned scheme, after sending the encrypted data to the second node, the method also includes: receiving, through the cloud platform, transmission completion information for the encrypted data sent by the second node, and destroying the intermediate node based on the transmission completion information; wherein, the transmission completion information is sent by the second node after receiving the encrypted data sent by the intermediate node, decrypting the encrypted data, obtaining the decrypted data, and passing the security verification of the encrypted data based on the decrypted data.
[0013] In the second aspect, an embodiment of the present application provides a cross-domain data transmission device, which is applied to a cloud platform, wherein the cloud platform includes a first node and a second node located in different domains, and the device is configured in an intermediate node created by the cloud platform, and the device includes: a receiving module, configured to receive encrypted data sent by the first node; a decryption module, configured to decrypt the encrypted data to obtain decrypted data; a verification module, configured to perform a security verification on the encrypted data based on the decrypted data to obtain a verification result; and a sending module, configured to send the encrypted data to the second node if the verification result indicates that the verification is passed.
[0014] In a third aspect, an embodiment of the present application provides an electronic device, comprising one or more processors; and a memory for storing one or more programs, so that when the one or more programs are executed by the one or more processors, the electronic device implements the cross-domain data transmission method as described above.
[0015] In a fourth aspect, an embodiment of the present application provides a computer-readable medium having a computer program stored thereon, and when the computer program is executed by a processor, the cross-domain data transmission method as described above is implemented.
[0016] In a fifth aspect, an embodiment of the present application provides a computer program product, including computer instructions, which, when executed by a processor, implement the cross-domain data transmission method as described above.
[0017] In the technical solution provided in the embodiments of the present application:
[0018] The intermediate node created through the cloud platform receives the encrypted data sent by the first node, then decrypts the encrypted data to obtain the decrypted data, and then performs a security check on the encrypted data based on the decrypted data to obtain a check result. If the check result indicates that the check is passed, the encrypted data is sent to the second node; wherein the first node and the second node are nodes located in different domains in the cloud platform.
[0019] On the one hand, since the first node and the second node are nodes located in different domains in the cloud platform, the intermediate node is used as a transit point for data transmission between nodes in different domains, thereby realizing cross-domain data transmission within the same cloud platform (which belongs to indirect data transmission), avoiding the phenomenon of a node attacking another node due to direct data transmission between nodes in different domains, and improving the security of cross-domain data transmission within the same cloud platform.
[0020] On the other hand, since the intermediate nodes will decrypt and verify the encrypted data, the security of the encrypted data during transmission is verified, which avoids the encrypted data from being tampered with or stolen during transmission, and further improves the security of cross-domain data transmission within the same cloud platform.
[0021] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] Figure 1 is a schematic diagram of an exemplary implementation environment to which the technical solution of the embodiments of the present application can be applied;
[0023] Figure 2 is a flowchart of a cross-domain data transmission method shown in an exemplary embodiment of the present application;
[0024] Figure 3 is a flowchart of a cross-domain data transmission method shown in another exemplary embodiment of the present application;
[0025] Figure 4 is a flowchart of a cross-domain data transmission method shown in another exemplary embodiment of the present application;
[0026] Figure 5 is a flowchart of a cross-domain data transmission method shown in another exemplary embodiment of the present application;
[0027] Figure 6 is a flowchart of a cross-domain data transmission method shown in another exemplary embodiment of the present application;
[0028] Figure 7is a flowchart of a cross-domain data transmission method shown in another exemplary embodiment of the present application;
[0029] Figure 8 is a flowchart of a cross-domain data transmission method shown in another exemplary embodiment of the present application;
[0030] Fig. 9 is a flowchart of a cross-domain data transmission method shown in an exemplary embodiment of the present application;
[0031] Fig.10 is a flowchart of a cross-domain data transmission method shown in an exemplary embodiment of the present application;
[0032] Fig.11 is a flowchart of a cross-domain data transmission method shown in an exemplary embodiment of the present application;
[0033] Fig.12 is a block diagram of a cross-domain data transmission device according to an embodiment of the present application;
[0034] Fig.13 is a block diagram of a cross-domain data transmission device according to an embodiment of the present application;
[0035] Fig.14 is a block diagram of a cross-domain data transmission device according to an embodiment of the present application;
[0036] Fig.15 It is a structural diagram of a computer system suitable for implementing an electronic device of an embodiment of the present application. DETAILED DESCRIPTION
[0037] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments that are the same as the present application. Instead, they are only examples of devices and methods that are the same as some aspects of the present application as detailed in the attached claims.
[0038] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.
[0039] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.
[0040] It should be noted that the "multiple" mentioned in this application refers to two or more than two. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship.
[0041] Cloud computing refers to the delivery and use model of IT infrastructure, which means obtaining required resources through the network in an on-demand and easily scalable manner; in a broad sense, cloud computing refers to the delivery and use model of services, which means obtaining required services through the network in an on-demand and easily scalable manner. This service can be IT and software, Internet-related, or other services. Cloud computing is the product of the development and integration of traditional computer and network technologies such as grid computing, distributed computing, parallel computing, utility computing, network storage, virtualization, and load balancing.
[0042] With the development of the Internet, real-time data streams, and the diversification of connected devices, as well as the demand for search services, social networks, mobile commerce, and open collaboration, cloud computing has developed rapidly. Different from the previous parallel distributed computing, the emergence of cloud computing will promote revolutionary changes in the entire Internet model and enterprise management model from a conceptual perspective.
[0043] At present, with the widespread application of cloud computing, important businesses have been migrated to cloud platforms. Cloud computing has developed into an important support for the smooth operation of the national economy, but cloud platforms have become the hardest hit by cyber attacks. Among them, cross-network and cross-domain data transmission between different cloud platforms usually involves communication between the intranet and the extranet. In order to ensure the security of cross-domain data transmission, it can be isolated through a physical device such as a network gate. However, for cross-domain data transmission within the same cloud platform, due to the fuzzy network boundaries, it is difficult to isolate it through a physical device such as a network gate, resulting in low security of cross-domain data transmission.
[0044] See also Figure 1 , Figure 1 1 is a schematic diagram of an implementation environment involved in the present application. The implementation environment mainly includes a cloud platform 101 , a first node 1011 , a second node 1012 , and an intermediate node 102 .
[0045] The cloud platform 101 is a system / platform constructed by cloud computing.
[0046] Exemplarily, the cloud platform may include multiple nodes located in the same domain; for example, the cloud platform includes five nodes 1-5, wherein nodes 1-5 are located in domain A.
[0047] Exemplarily, the cloud platform may include multiple nodes located in different domains; for example, the cloud platform includes five nodes 1-5, where node 1 is located in domain A, node 2 is located in domain B, node 3 is located in domain C, node 4 is located in domain D, and node 5 is located in domain E.
[0048] Exemplarily, the cloud platform may include multiple nodes located in the same domain and different domains; for example, the cloud platform includes five nodes 1-5, wherein nodes 1-2 are located in domain A, node 3 is located in domain B, and nodes 4-5 are located in domain C.
[0049] It is understandable that the number of nodes included in the cloud platform can be flexibly adjusted according to the specific application scenario. For ease of understanding, the embodiment of the present application is illustrated by taking the cloud platform as including two first nodes 1011 (shown in domain A) and second nodes 1012 (shown in domain B) located in different domains.
[0050] The first node 1011 and the second node 1012 may be cloud servers or terminal devices based on cloud computing.
[0051] Exemplarily, a cloud server may be one that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms.
[0052] Exemplarily, the terminal device includes but is not limited to smart phones, tablets, laptops, computers, intelligent voice interaction devices, smart home appliances, vehicle-mounted terminals, aircraft, etc.
[0053] Among them, the intermediate node 102 can be a cloud platform constructed according to lightweight virtualization technology such as containers, which is used to realize data transmission between nodes located in different domains in the cloud platform, so as to isolate direct data transmission between nodes located in different domains in the cloud platform; that is, the intermediate node serves as a data transmission transitor between nodes located in different domains in the cloud platform, and realizes the indirect transmission of data between nodes located in different domains in the cloud platform, thereby avoiding the phenomenon of a node attacking another node due to direct data transmission between nodes located in different domains in the cloud platform, thereby improving the security of cross-domain data transmission.
[0054] It should be noted that Figure 1The number of cloud platforms 101, first nodes 1011, second nodes 1012, and intermediate nodes 102 is merely illustrative, and any number of cloud platforms 101, first nodes 1011, second nodes 1012, and intermediate nodes 102 may be provided according to actual needs.
[0055] In one embodiment of the present application, the cross-domain data transmission method may be executed by the first node 1011, and the first node 1011 at this time serves as a data providing node.
[0056] Exemplarily, the first node 1011 encrypts the data to be transmitted to obtain the encrypted data, and then sends the encrypted data to the intermediate node.
[0057] In one embodiment of the present application, the cross-domain data transmission method may be executed by the intermediate node 102 , and the intermediate node 102 at this time serves as a data transfer node.
[0058] Exemplarily, the first node 1011 receives the encrypted data sent by the first node 1011, then decrypts the encrypted data to obtain decrypted data, and then performs a security check on the encrypted data based on the decrypted data to obtain a check result, wherein if the check result indicates that the check is passed, the encrypted data is sent to the second node.
[0059] In one embodiment of the present application, the cross-domain data transmission method may be executed by the second node 1012, and the second node 1012 at this time serves as a data requesting / receiving node.
[0060] Exemplarily, the second node 1012 receives the encrypted data sent by the intermediate node 102, and then decrypts the encrypted data to obtain decrypted data.
[0061] Figure 1 The technical solution of the illustrated embodiment can be applied to various scenarios for cross-domain data transmission, including but not limited to smart transportation, assisted driving, cloud technology, artificial intelligence, etc.; in actual applications, it can be flexibly adjusted according to specific application scenarios.
[0062] The following is a detailed description of various implementation details of the technical solution of the embodiment of the present application:
[0063] See also Figure 2 , Figure 2 FIG. 1 is a flow chart of a cross-domain data transmission method according to an embodiment of the present application. The cross-domain data transmission method may be executed by the intermediate node 102. Figure 2 As shown, the cross-domain data transmission method at least includes S201 to S204, which are described in detail as follows:
[0064] S201, receiving encrypted data sent by the first node.
[0065] In the embodiment of the present application, the first node sends encrypted data to the intermediate node. Correspondingly, the intermediate node receives the encrypted data sent by the first node.
[0066] S202, decrypt the encrypted data to obtain decrypted data.
[0067] In the embodiment of the present application, the intermediate node receives the encrypted data sent by the first node, and then can decrypt the encrypted data to obtain the decrypted data.
[0068] S203, performing security verification on the encrypted data according to the decrypted data to obtain a verification result.
[0069] In the embodiment of the present application, the intermediate node decrypts the encrypted data to obtain the decrypted data, and then can perform a security check on the encrypted data based on the decrypted data to obtain a check result.
[0070] In the embodiment of the present application, the intermediate node performs security verification on the encrypted data according to the decrypted data, and the verification results obtained have at least the following two situations:
[0071] In case 1, if the intermediate node performs security verification on the encrypted data according to the decrypted data and the verification result is passed, a verification result indicating that the security verification on the encrypted data has passed is obtained.
[0072] In case 2, if the intermediate node performs a security check on the encrypted data based on the decrypted data and the check fails, a check result indicating that the security check on the encrypted data fails is obtained.
[0073] S204: If the verification result indicates that the verification is passed, the encrypted data is sent to the second node.
[0074] In the embodiment of the present application, the intermediate node performs a security check on the encrypted data based on the decrypted data to obtain a check result, and then determines whether to send the encrypted data to the second node based on the check result.
[0075] In the embodiment of the present application, the intermediate node determines whether to send the encrypted data to the second node according to the verification result in at least the following two situations:
[0076] In case 1, if the intermediate node obtains a verification result indicating that the security verification of the encrypted data has passed, the encrypted data may be sent to the second node.
[0077] In the second case, if the intermediate node obtains a verification result indicating that the security verification of the encrypted data has failed, no processing may be performed, that is, the encrypted data may not be sent to the second node; or the first node may be marked as an abnormal node and corresponding abnormal information may be generated and sent to the cloud platform, so that the cloud platform can determine that the first node is an abnormal node based on the abnormal information, and thus take corresponding control measures on it.
[0078] In the embodiment of the present application, the intermediate node is used as a transitor for data transmission between nodes in different domains, thereby realizing cross-domain data transmission within the same cloud platform (which belongs to indirect data transmission), avoiding the phenomenon of one node attacking another node caused by direct data transmission between nodes in different domains, and improving the security of cross-domain data transmission within the same cloud platform; at the same time, the intermediate node will decrypt and verify the encrypted data, realizing security verification of the encrypted data during transmission, avoiding the phenomenon of the encrypted data being tampered with or stolen during transmission, and further improving the security of cross-domain data transmission within the same cloud platform.
[0079] In one embodiment of the present application, another cross-domain data transmission method is provided, which can be performed by the intermediate node 102. Figure 3 As shown, the cross-domain data transmission method may include S301, S201, S203 to S204.
[0080] Among them, the encrypted data in the embodiment of the present application includes encrypted source data and encrypted hash data to be verified, and the hash data to be verified is obtained by performing a hash operation on the source data.
[0081] For example, m represents the source data, h represents the hash data to be verified, and Encrypt represents the encryption process. The encrypted data includes Encrypt(m)+Encrypt(h), where h=hash(m), that is, h is obtained by performing a hash operation on m.
[0082] S301 is described in detail as follows:
[0083] S301, decrypting the encrypted hash data to be verified to obtain decrypted hash data to be verified, and decrypting the encrypted source data to obtain decrypted source data.
[0084] Since the encrypted data in the embodiment of the present application includes the encrypted source data and the encrypted hash data to be verified; therefore, the process in which the intermediate node in the embodiment of the present application decrypts the encrypted data to obtain the decrypted data can specifically be decrypting the encrypted hash data to be verified, thereby obtaining the decrypted hash data to be verified, and decrypting the encrypted source data, thereby obtaining the decrypted source data.
[0085] For example, following the above example, Decrypt is used to represent the decryption process. The encrypted hash data to be verified is decrypted as Decrypt(Encrypt(h)=h, and the encrypted source data is decrypted to obtain the decrypted source data as Decrypt(Encrypt(m))=m.
[0086] It should be noted that Figure 3 For detailed description of S201, S203 to S204, please refer to Figure 2 S201, S203 to S204 shown are not described in detail here.
[0087] In the embodiment of the present application, the encrypted data includes not only the source data but also the hash data to be verified, and the decrypted data includes not only the source data but also the hash data to be verified. This provides strong support for the later intermediate nodes to generate target hash data using the decrypted source data, and perform security verification based on the matching of the target hash data and the hash data to be verified.
[0088] In one embodiment of the present application, another cross-domain data transmission method is provided, which can be performed by the intermediate node 102. Figure 4 As shown, the cross-domain data transmission method may include S401 to S403, S201, and S203 to S204.
[0089] Among them, in the embodiment of the present application, the encrypted data also includes an encrypted key, the encrypted source data is encrypted using the key, and the encrypted key and the encrypted hash data to be verified are encrypted using the public key.
[0090] For example, if m represents the source data, h represents the hash data to be verified, Encrypt represents the encryption process, key represents the key, and pub-key represents the public key, then the encrypted data includes Encrypt key (m)+Encrypt pub-key (h, key), where h = hash(m), that is, h is obtained by performing a hash operation on m. It can be understood that Encrypt pub-key (h, key) can also be split into Encryptpub-key (h)+Encrypt pub-key (key).
[0091] S401 to S403 are described in detail as follows:
[0092] S401, using a private key to decrypt the encrypted hash data to be verified to obtain decrypted hash data to be verified; wherein the private key matches the public key.
[0093] Since the encrypted data in the embodiment of the present application includes encrypted hash data to be verified, and the encrypted hash data to be verified is obtained by encryption using a public key; therefore, in the embodiment of the present application, the intermediate node decrypts the encrypted hash data to be verified to obtain the decrypted hash data to be verified. Specifically, the encrypted hash data to be verified can be decrypted using a private key that matches the public key to obtain the decrypted hash data to be verified.
[0094] For example, following the above example, Decrypt is used to represent the decryption process, and priv-key is used to represent the private key. Then, the encrypted hash data to be verified is decrypted using the private key. priv-key (Encrypt pub-key (h))=h.
[0095] S402, using the private key to decrypt the encrypted key to obtain a decrypted key.
[0096] Since the encrypted data in the embodiment of the present application includes the encrypted source data and the encrypted key, and the encrypted source data is encrypted using the key; therefore, in the embodiment of the present application, the intermediate node decrypts the encrypted source data to obtain the decrypted source data. Specifically, it can be to first use the private key to decrypt the encrypted key to obtain the decrypted key, and then use the decrypted key to decrypt the encrypted source data to obtain the decrypted source data.
[0097] S403, decrypt the encrypted source data using the decrypted key to obtain the decrypted source data.
[0098] As mentioned above, for example, continuing the previous example, using the private key to decrypt the encrypted key is Decrypt priv-key (Encrypt pub-key (key)) = key, and then use the decrypted key to decrypt the encrypted source data to Decrypt key (Encrypt key (m))=m.
[0099] It is understandable that S401 and S402 can be executed in parallel. For example, following the above example, the encrypted hash data to be verified and the encrypted key are decrypted at the same time using the private key. priv-key (Encrypt pub-key (h, key)) = h, key.
[0100] It should be noted that Figure 4 For detailed description of S201, S203 to S204, please refer to Figure 2 S201, S203 to S204 shown are not described in detail here.
[0101] In the embodiment of the present application, the encrypted data includes not only the source data but also the hash data to be verified and the key, and the source data is encrypted by the key, and the hash data to be verified and the key are encrypted by the public key; the decrypted data includes not only the source data but also the hash data to be verified and the key, and the intermediate node uses the private key to decrypt the encrypted hash data to be verified and the key, and uses the decrypted key to decrypt the encrypted source data. For the source data, it includes two layers of decryption process, which avoids the phenomenon that the source data is tampered with or stolen during the data transmission process, and improves the security of source data transmission within the same cloud platform.
[0102] In one embodiment of the present application, another cross-domain data transmission method is provided, which can be performed by the intermediate node 102. Figure 5 As shown, the cross-domain data transmission method may include S501 to S503, S201 to S202, and S204.
[0103] Among them, the decrypted data in the embodiment of the present application may include decrypted source data and decrypted hash data to be verified.
[0104] Optionally, in an embodiment of the present application, the decrypted data may include decrypted source data, decrypted hash data to be verified, and a decrypted key.
[0105] S501 to S503 are described in detail as follows:
[0106] S501, performing a hash operation on the decrypted source data to obtain target hash data.
[0107] In the embodiment of the present application, the intermediate node can perform a hash operation on the decrypted source data to obtain target hash data.
[0108] For example, h' is used to represent the target hash data, where h'=hash(m), that is, h' is obtained by performing a hash operation on the decrypted m.
[0109] S502: If the target hash data matches the hash data to be verified, a verification result is obtained, which is used to indicate that the security verification of the encrypted data has passed.
[0110] In the embodiment of the present application, the intermediate node performs a hash operation on the decrypted source data to obtain target hash data, and then can match the target hash data with the hash data to be verified, and then can determine the verification result for the encrypted data based on the matching result.
[0111] In the embodiment of the present application, the intermediate node determines the verification result for the encrypted data according to the matching result. There are at least two situations:
[0112] In case one, if the target hash data matches the hash data to be verified, it is determined that the encrypted data has not been tampered with, and the security of its transmission process is relatively high; therefore, in the embodiment of the present application, it can be determined that the security check on the encrypted data has passed at this time, and accordingly, a verification result is obtained to characterize that the security check on the encrypted data has passed.
[0113] Case two: if the target hash data does not match the hash data to be verified, it is determined that the encrypted data may be tampered with or has been tampered with, and the security of its transmission process is low; therefore, in the embodiment of the present application, it can be determined that the security check on the encrypted data has failed at this time, and accordingly, a verification result is obtained to characterize that the transmission security check on the encrypted data has failed.
[0114] S503: If the target hash data does not match the hash data to be verified, a verification result is obtained, indicating that the transmission security verification of the encrypted data has failed.
[0115] As mentioned above, for example, following the previous example, assume that h'=hash(m) and h=hash(m); if h'=h, that is, it indicates that the target hash data matches the hash data to be verified, and a verification result is obtained to indicate that the security verification of the encrypted data has passed; if h'≠h, that is, it indicates that the target hash data does not match the hash data to be verified, and a verification result is obtained to indicate that the transmission security verification of the encrypted data has failed.
[0116] It should be noted that Figure 5 For detailed description of S201 to S202 and S204, please refer to Figure 2 S201 to S202 and S204 shown are not described in detail here.
[0117] In the embodiment of the present application, the intermediate node uses the decrypted source data to generate target hash data, and based on the matching of the target hash data and the hash data to be verified, quickly and accurately implements the security verification of the encrypted data, which is suitable for many application scenarios.
[0118] In one embodiment of the present application, another cross-domain data transmission method is provided, which can be performed by the intermediate node 102. Figure 6 As shown, the cross-domain data transmission method may include S601 to S603 and S201 to S203.
[0119] S601 to S603 are described in detail as follows:
[0120] S601, disconnecting a first transmission link established with a first node; wherein the first transmission link is used to transmit encrypted data.
[0121] It can be understood that in the embodiment of the present application, when the first node needs to send encrypted data to the intermediate node, it can first send a link establishment request to the intermediate node. In this way, after the intermediate node receives the link establishment request sent by the first node, it can establish a first transmission link with the first node, so that the first node can send the encrypted data to the intermediate node through the first transmission link.
[0122] Among them, after the intermediate node passes the security check on the encrypted data based on the decrypted data, the first transmission link is no longer needed; therefore, in the embodiment of the present application, the intermediate node can disconnect the first transmission link, thereby reducing the resource consumption caused by maintaining the first transmission link.
[0123] Optionally, after the intermediate node performs a security check on the encrypted data based on the decrypted data and passes it, the intermediate node may not disconnect the first transmission link, so that the first node can use the first transmission link to transmit data when data transmission is required without re-creating the transmission link.
[0124] Among them, when the intermediate node fails the security check on the encrypted data based on the decrypted data, the first transmission link may still be needed so that the first node can use the first transmission link to retransmit the new encrypted data; therefore, in the embodiment of the present application, the intermediate node can maintain the first transmission link, thereby reducing the low data transmission efficiency caused by re-creating the transmission link.
[0125] Optionally, when the intermediate node performs a security check on the encrypted data based on the decrypted data and the check fails, the intermediate node may also disconnect the first transmission link, thereby maximally ensuring the security of data transmission.
[0126] S602, establishing a second transmission link with a second node; wherein the second transmission link is used to transmit encrypted data.
[0127] In an embodiment of the present application, the intermediate node can send a link establishment request to the second node, so that after the second node receives the link establishment request sent by the intermediate node, it can establish a second transmission link with the intermediate node, so that the intermediate node can send encrypted data to the second node through the second transmission link.
[0128] S603: Send the encrypted data to the second node through the second transmission link.
[0129] It is understandable that S601 and S602 can be executed in parallel, or one can be executed first and the other can be executed later. In actual applications, they can be flexibly adjusted according to specific application scenarios.
[0130] It should be noted that Figure 6 For detailed description of S201 to S203, please refer to Figure 2 S201 to S203 shown are not described in detail here.
[0131] In the embodiment of the present application, after the intermediate node performs a security check on the encrypted data sent by the first node, the intermediate node disconnects the first transmission link established between it and the first node, thereby saving and reducing the resource consumption caused by maintaining the first transmission link; at the same time, the intermediate node establishes a second transmission link between itself and the second node, and sends the encrypted data to the second node through the second transmission link, thereby ensuring the normal transmission of the encrypted data.
[0132] In one embodiment of the present application, another cross-domain data transmission method is provided, which can be performed by the intermediate node 102. Figure 7 As shown, the cross-domain data transmission method may further include S701 before S201.
[0133] S701 is described in detail as follows:
[0134] S701, receiving an intermediate node creation request sent by a first node through a cloud platform, and creating an intermediate node based on the creation request; wherein, the intermediate node creation request is sent by the first node after receiving a cross-domain data request sent by a second node and performing identity verification on the second node.
[0135] As mentioned above, the intermediate node is created by the cloud platform; therefore, the process of creating the intermediate node in the embodiment of the present application can specifically be receiving the intermediate node creation request sent by the first node through the cloud platform, and creating the intermediate node based on the creation request; wherein the intermediate node creation request is sent by the first node after receiving the cross-domain data request sent by the second node and passing the identity verification of the second node.
[0136] That is, in the embodiment of the present application, the second node sends a cross-domain data request to the first node. Accordingly, the first node receives the cross-domain data request sent by the second node, and then performs identity verification on the second node. If the first node passes the identity verification of the second node, an intermediate node creation request is generated and sent to the cloud platform. Accordingly, the cloud platform receives the intermediate node creation request sent by the first node, and determines that the first node has a need to send data to the second node through the intermediate node at this time; therefore, the cloud platform creates an intermediate node.
[0137] Optionally, in the embodiment of the present application, the process of the first node verifying the identity of the second node may specifically verify the unique identifier of the second node, such as a serial number (which may be pre-assigned by the cloud platform), a name, etc., to verify the identity of the second node. In practical applications, it can be flexibly adjusted according to specific application scenarios.
[0138] Optionally, the process of the cloud platform creating an intermediate node in the embodiment of the present application can be specifically that after the cloud platform receives the request to establish the intermediate node, it pulls the intermediate node image file from the container image library to create the intermediate node (such as dockernode); wherein the dockernode has built-in kafka service, encryption and decryption service, and scanning service, etc. It can be understood that the process of receiving the encrypted data sent by the first node in S201 introduced in the aforementioned embodiment can be implemented by the kafka service, the process of decrypting the encrypted data in S202 to obtain the decrypted data can be implemented by the encryption and decryption service, and the process of performing security verification on the encrypted data according to the decrypted data in S203 to obtain the verification result can be implemented by the scanning service, etc.
[0139] It should be noted that Figure 7 For detailed description of S201 to S204, please refer to Figure 2 S201 to S204 shown are not described in detail here.
[0140] In the embodiment of the present application, an intermediate node is created after the cloud platform receives an intermediate node creation request sent by the first node, providing strong support for the later intermediate node to act as a transit point for data transmission between different domain nodes (i.e., the first node and the second node).
[0141] In one embodiment of the present application, another cross-domain data transmission method is provided, which can be performed by the intermediate node 102. Figure 8 As shown, the cross-domain data transmission method may further include S801 after S204.
[0142] S801 is described in detail as follows:
[0143] S801, receiving transmission completion information for encrypted data sent by the second node through the cloud platform, and destroying the intermediate node based on the transmission completion information; wherein, the transmission completion information is sent by the second node after receiving the encrypted data sent by the intermediate node, decrypting the encrypted data, obtaining the decrypted data, and verifying the security of the encrypted data based on the decrypted data.
[0144] In the embodiment of the present application, after the intermediate node sends the encrypted data to the second node, it can also receive the transmission completion information for the encrypted data sent by the second node through the cloud platform, and destroy the intermediate node based on the transmission completion information; wherein the transmission completion information is sent by the second node after receiving the encrypted data sent by the intermediate node, decrypting the encrypted data, obtaining the decrypted data, and passing the security verification of the encrypted data based on the decrypted data.
[0145] That is, in the embodiment of the present application, the second node receives the encrypted data sent by the intermediate node, then decrypts the encrypted data to obtain the decrypted data, and verifies the security of the encrypted data based on the decrypted data to obtain the verification result. If the verification result indicates that the verification is passed (where the decryption and verification process of the second node is similar to the decryption and verification process of the intermediate node), a transmission completion message for the encrypted data is generated and sent to the cloud platform. Accordingly, the cloud platform receives the transmission completion message sent by the second node, and determines that the transmission of the encrypted data has been completed / ended at this time, and the intermediate node is no longer needed as a data transmission transferor; therefore, the cloud platform destroys the intermediate node.
[0146] It should be noted that Figure 8 For detailed description of S201 to S204, please refer to Figure 2 S201 to S204 shown are not described in detail here.
[0147] In the embodiment of the present application, the intermediate node is destroyed after the cloud platform receives the transmission completion information for the encrypted data sent by the second node, thereby reducing the time that the intermediate node is exposed to the network, thereby avoiding the phenomenon of abnormal nodes attacking the intermediate node, further improving the security of cross-domain data transmission within the same cloud platform, and also reducing the resource consumption caused by the cloud platform maintaining the intermediate nodes.
[0148] It should be noted that Figures 2 to 8 The illustrated embodiment is described from the perspective of the intermediate node 102. Fig. 9 The implementation details of the technical solution of the embodiment of the present application are described in detail from the perspective of the first node 1011:
[0149] See also Fig. 9 , Fig. 9 FIG. 1 is a flow chart of a cross-domain data transmission method shown in an embodiment of the present application. The cross-domain data transmission method may be executed by the first node 1011. Fig. 9 As shown, the cross-domain data transmission method at least includes S901 to S902, which are described in detail as follows:
[0150] S901, encrypt the data to be transmitted to obtain encrypted data.
[0151] As described in the foregoing embodiment, when there is a demand for data acquisition, the second node can generate a cross-domain data request and send the cross-domain data request to the first node. Accordingly, the first node receives the cross-domain data request sent by the second node, and encrypts the data to be transmitted to obtain the encrypted data. The data to be transmitted includes the data required to be obtained by the second node (i.e., the source data mentioned in the foregoing embodiment) and the hash data to be verified, and the hash data to be verified is obtained by performing a hash operation on the source data. Optionally, the data to be transmitted may also include a key, which is used to encrypt the source data.
[0152] Optionally, in an embodiment of the present application, the first node receives a cross-domain data request sent by the second node, and then can perform an identity verification on the second node, and generate an intermediate node creation request after the identity verification of the second node is passed, and send the intermediate node creation request to the cloud platform, so that the cloud platform can create an intermediate node based on the creation request.
[0153] S902, sending the encrypted data to the intermediate node so that the intermediate node decrypts the encrypted data to obtain the decrypted data, and after performing a security check on the encrypted data based on the decrypted data and passing the security check, the encrypted data is sent to the second node; wherein the intermediate node is created by the cloud platform.
[0154] In the embodiment of the present application, the first node encrypts the data to be transmitted to obtain the encrypted data, and then sends the encrypted data to the intermediate node, so that the intermediate node decrypts the encrypted data to obtain the decrypted data, and performs a security check on the encrypted data according to the decrypted data, and then sends the encrypted data to the second node. Please refer to the above embodiment for details, which will not be repeated here.
[0155] Optionally, the process of sending the encrypted data to the intermediate node in the embodiment of the present application may specifically be sending a link establishment request to the intermediate node, so that after the intermediate node receives the link establishment request sent by the first node, it can establish a first transmission link with the first node, so that the first node can send the encrypted data to the intermediate node through the first transmission link.
[0156] In the embodiment of the present application, the first node uses the intermediate node as the transitor of data transmission between it and the second node, thereby realizing indirect transmission of data within the same cloud platform and improving the security of cross-domain data transmission within the same cloud platform; at the same time, the intermediate node will decrypt and verify the encrypted data, realizing security verification of the encrypted data during the transmission process, and further improving the security of cross-domain data transmission within the same cloud platform.
[0157] It should be noted that Fig. 9 The embodiment shown is described from the perspective of the first node 1011. Fig.10 The implementation details of the technical solution of the embodiment of the present application are described in detail from the perspective of the second node 1012:
[0158] See also Fig.10 , Fig.10 1 is a flow chart of a cross-domain data transmission method shown in an embodiment of the present application, and the cross-domain data transmission method can be executed by the second node 1012. Fig.10 As shown, the cross-domain data transmission method at least includes S1001 to S1002, which are described in detail as follows:
[0159] S1001, receiving encrypted data sent by an intermediate node; wherein the intermediate node is created by a cloud platform, and the encrypted data is obtained by the intermediate node decrypting the encrypted data sent by the first node, and then performing a security check on the encrypted data based on the decrypted data before sending it.
[0160] As described in the above embodiment, when the second node has a data acquisition demand, it can generate a cross-domain data request and send the cross-domain data request to the first node. Accordingly, the first node receives the cross-domain data request sent by the second node, encrypts the data to be transmitted, obtains the encrypted data, and sends the encrypted data to the intermediate node. Accordingly, the intermediate node receives the encrypted data sent by the first node, then decrypts the encrypted data to obtain the decrypted data, and then performs a security check on the encrypted data based on the decrypted data to obtain a check result. If the check result indicates that the check is passed, the encrypted data is sent to the second node. Accordingly, the second node receives the encrypted data sent by the intermediate node. Please refer to the above embodiment for details, which will not be repeated here.
[0161] S1002, decrypt the encrypted data to obtain decrypted data.
[0162] In the embodiment of the present application, the second node receives the encrypted data sent by the intermediate node, and then decrypts the encrypted data to obtain the decrypted data. The decryption process of the second node is similar to that of the intermediate node, and will not be repeated here.
[0163] Optionally, in the embodiment of the present application, the second node decrypts the encrypted data to obtain the decrypted data, and then performs a security check on the encrypted data based on the decrypted data to obtain a check result. The check process of the second node is similar to that of the intermediate node, and will not be repeated here.
[0164] Among them, after the second node passes the security check on the encrypted data based on the decrypted data, the second transmission link is no longer needed; therefore, in the embodiment of the present application, the second node can disconnect the second transmission link, thereby reducing the resource consumption caused by maintaining the second transmission link.
[0165] Optionally, after the second node performs a security check on the encrypted data based on the decrypted data and passes it, the second transmission link may be maintained so that the intermediate node can use the second transmission link to transmit data when data transmission is required without re-creating the transmission link.
[0166] Among them, when the second node fails the security check on the encrypted data based on the decrypted data, the second transmission link may still be needed so that the intermediate node can use the second transmission link to retransmit the new encrypted data; therefore, in the embodiment of the present application, the second node can maintain the second transmission link, thereby reducing the low data transmission efficiency caused by re-creating the transmission link.
[0167] Optionally, when the second node performs a security check on the encrypted data based on the decrypted data and the check fails, the second node may also disconnect the second transmission link, thereby maximally ensuring the security of data transmission.
[0168] Optionally, after the second node performs a security check on the encrypted data based on the decrypted data and passes it, it can generate transmission completion information for the encrypted data and send the transmission completion information to the cloud platform, so that the cloud platform can destroy the intermediate node based on the transmission completion information.
[0169] In the embodiment of the present application, the second node uses the intermediate node as the transitor of data transmission between it and the first node, thereby realizing indirect transmission of data within the same cloud platform and improving the security of cross-domain data transmission within the same cloud platform; at the same time, the intermediate node will decrypt and verify the encrypted data, realizing security verification of the encrypted data during the transmission process, and further improving the security of cross-domain data transmission within the same cloud platform.
[0170] The following is a detailed description of a specific scenario of an embodiment of the present application:
[0171] Also based on Figure 1 The implementation environment shown is shown in Fig.11 , Fig.11 FIG. 1 is a flow chart of a cross-domain data transmission method according to an embodiment of the present application. Fig.11 As shown, the cross-domain data transmission method at least includes S1101 to S1113, which are described in detail as follows:
[0172] S1101, the second node sends a cross-domain data request to the first node.
[0173] S1102: The first node receives a cross-domain data request sent by the second node, and verifies the identity of the second node based on the cross-domain data request.
[0174] S1103, the first node passes the identity verification of the second node, generates an intermediate node creation request, and sends the intermediate node creation request to the cloud platform.
[0175] S1104, the cloud platform receives the intermediate node creation request sent by the first node, and creates an intermediate node based on the intermediate node creation request.
[0176] S1105, the first node encrypts the data to be transmitted to obtain encrypted data.
[0177] Optionally, the data to be transmitted includes source data, hash data to be verified, and a key, wherein the hash data to be verified is obtained by performing a hash operation on the source data, and the key is used to encrypt the source data.
[0178] Optionally, the encrypted data includes Encrypt key (m)+Encrypt pub-key (h, key), where h = hash(m). For specific parameters, please refer to the introduction of the above embodiment, which will not be repeated here.
[0179] S1106: The first node establishes a first transmission link with the intermediate node, and sends the encrypted data to the intermediate node through the first transmission link.
[0180] S1107, the intermediate node receives the encrypted data sent by the first node, decrypts the encrypted data to obtain decrypted data, and performs security verification on the encrypted data according to the decrypted data to obtain a verification result.
[0181] Optionally, the decrypted data includes Decrypt key (Encrypt key (m))=m+Decrypt priv-key (Encrypt pub-key (h, key)) = h, key. For specific parameters, please refer to the introduction of the above embodiment, which will not be repeated here.
[0182] Optionally, the intermediate node performs a security check on the encrypted data based on the decrypted data to obtain a verification result, which may specifically include performing a hash operation on the decrypted source data to obtain target hash data (i.e., h' in the aforementioned embodiment). If the target hash data matches the hash data to be verified (i.e., h'=h), a verification result is obtained that indicates that the security check on the encrypted data has passed. If the target hash data does not match the hash data to be verified (i.e., h'≠h), a verification result is obtained that indicates that the transmission security check on the encrypted data has failed.
[0183] S1108: If the verification result indicates that the verification is passed, the intermediate node disconnects the first transmission link established between the intermediate node and the first node.
[0184] S1109: The intermediate node establishes a second transmission link with the second node, and sends the encrypted data to the second node through the second transmission link.
[0185] Optionally, the encrypted data includes Encrypt key (m)+Encrypt pub-key (h, key), where h = hash(m). For specific parameters, please refer to the introduction of the above embodiment, which will not be repeated here.
[0186] S1110, the second node receives the encrypted data sent by the intermediate node, decrypts the encrypted data to obtain the decrypted data, and performs security verification on the encrypted data according to the decrypted data to obtain a verification result.
[0187] Optionally, the decrypted data includes Decrypt key (Encrypt key (m))=m+Decrypt priv-key (Encrypt pub-key (h, key)) = h, key. For specific parameters, please refer to the introduction of the above embodiment, which will not be repeated here.
[0188] Optionally, the second node performs a security check on the encrypted data based on the decrypted data to obtain a verification result, which may specifically include performing a hash operation on the decrypted source data to obtain target hash data (i.e., h' in the aforementioned embodiment). If the target hash data matches the hash data to be verified (i.e., h'=h), a verification result is obtained that indicates that the security check on the encrypted data has passed. If the target hash data does not match the hash data to be verified (i.e., h'≠h), a verification result is obtained that indicates that the transmission security check on the encrypted data has failed.
[0189] S1111: If the verification result indicates that the verification is passed, the second node disconnects the second transmission link established between the second node and the intermediate node.
[0190] S1112, the second node generates transmission completion information for the encrypted data, and sends the transmission completion information to the cloud platform.
[0191] S1113, the cloud platform receives the transmission completion information sent by the second node, and destroys the intermediate node based on the transmission completion information.
[0192] It should be noted that Fig.11 For detailed description of S1101 to S1113 shown, please refer to the aforementioned embodiment, which will not be repeated here.
[0193] In the present application embodiment:
[0194] On the one hand, by creating an intermediate node, the direct network interaction between the two parties of data transmission is cut off, and the security of the data to be transmitted is checked at the intermediate node, avoiding the phenomenon of the attacker initiating a malicious network connection to carry out a network attack, thereby improving the security of cross-domain data transmission.
[0195] On the other hand, the cloud platform uses containers to create intermediate nodes, which can quickly and easily create a secure and reliable intermediate node, reduce the waiting time required to create the intermediate node, and destroy the intermediate node in time after the transmission is completed, which also saves cloud platform computing resources, reduces the time that the intermediate node is exposed to the network, and reduces the risk of the intermediate node being attacked, thereby further improving the security of cross-domain data transmission.
[0196] Fig.12 FIG. 1 is a block diagram of a cross-domain data transmission device according to an embodiment of the present application. Fig.12 As shown, the cross-domain data transmission device is configured in the intermediate node created by the cloud platform, and the cross-domain data transmission device includes:
[0197] The receiving module 1201 is configured to receive the encrypted data sent by the first node;
[0198] The decryption module 1202 is configured to decrypt the encrypted data to obtain decrypted data;
[0199] Verification module 1203, configured to perform security verification on the encrypted data according to the decrypted data to obtain a verification result;
[0200] The sending module 1204 is configured to send the encrypted data to the second node if the verification result indicates that the verification is passed.
[0201] In one embodiment of the present application, the decrypted data includes the decrypted source data and the decrypted hash data to be verified, and the hash data to be verified is obtained by performing a hash operation on the source data; the verification module 1203 is specifically configured as follows:
[0202] Perform hash operation on the decrypted source data to obtain target hash data;
[0203] If the target hash data matches the hash data to be verified, a verification result is obtained, which is used to indicate that the security verification of the encrypted data has passed;
[0204] If the target hash data does not match the hash data to be verified, a verification result is obtained, which is used to indicate that the transmission security verification of the encrypted data has failed.
[0205] In one embodiment of the present application, the encrypted data includes the encrypted source data and the encrypted hash data to be verified, and the hash data to be verified is obtained by performing a hash operation on the source data; the decryption module 1202 is specifically configured as follows:
[0206] The encrypted hash data to be verified is decrypted to obtain the decrypted hash data to be verified, and the encrypted source data is decrypted to obtain the decrypted source data.
[0207] In one embodiment of the present application, the encrypted data also includes an encrypted key, the encrypted source data is encrypted using the key, and the encrypted key and the encrypted hash data to be verified are encrypted using the public key; the decryption module 1202 is further specifically configured as follows:
[0208] Decrypt the encrypted hash data to be verified using the private key to obtain the decrypted hash data to be verified; wherein the private key matches the public key;
[0209] Decrypt the encrypted key using the private key to obtain the decrypted key;
[0210] The encrypted source data is decrypted using the decrypted key to obtain the decrypted source data.
[0211] In one embodiment of the present application, the sending module 1204 is specifically configured as follows:
[0212] Disconnecting a first transmission link established with the first node; wherein the first transmission link is used to transmit encrypted data;
[0213] Establishing a second transmission link with the second node; wherein the second transmission link is used to transmit the encrypted data;
[0214] The encrypted data is sent to the second node via the second transmission link.
[0215] In one embodiment of the present application, the cross-domain data transmission device further includes:
[0216] A creation module is configured to receive an intermediate node creation request sent by a first node through a cloud platform, and to create an intermediate node based on the creation request; wherein, the intermediate node creation request is sent by the first node after receiving a cross-domain data request sent by a second node and performing identity verification on the second node.
[0217] In one embodiment of the present application, the cross-domain data transmission device further includes:
[0218] A destruction module is configured to receive transmission completion information for encrypted data sent by the second node through the cloud platform, and to destroy the intermediate node based on the transmission completion information; wherein the transmission completion information is sent by the second node after receiving the encrypted data sent by the intermediate node, decrypting the encrypted data, obtaining the decrypted data, and verifying the security of the encrypted data based on the decrypted data.
[0219] Fig.13 FIG. 1 is a block diagram of a cross-domain data transmission device according to an embodiment of the present application. Fig.13As shown, the cross-domain data transmission device is configured in the first node included in the cloud platform, and the cross-domain data transmission device includes:
[0220] The encryption module 1301 is configured to encrypt the data to be transmitted to obtain encrypted data;
[0221] The sending module 1302 is configured to send the encrypted data to the intermediate node so that the intermediate node decrypts the encrypted data to obtain the decrypted data, and after performing a security check on the encrypted data based on the decrypted data, sends the encrypted data to the second node; wherein the intermediate node is created by the cloud platform.
[0222] Fig.14 FIG. 1 is a block diagram of a cross-domain data transmission device according to an embodiment of the present application. Fig.14 As shown, the cross-domain data transmission device is configured in the second node included in the cloud platform, and the cross-domain data transmission device includes:
[0223] The receiving module 1401 is configured to receive encrypted data sent by the intermediate node; wherein the intermediate node is created by the cloud platform, and the encrypted data is obtained by the intermediate node decrypting the encrypted data sent by the first node, and performing security verification on the encrypted data according to the decrypted data before sending the encrypted data;
[0224] The decryption module 1402 is configured to decrypt the encrypted data to obtain decrypted data.
[0225] It should be noted that the apparatus provided in the aforementioned embodiment and the method provided in the aforementioned embodiment belong to the same concept, wherein the specific manner in which each module and unit performs the operation has been described in detail in the method embodiment.
[0226] An embodiment of the present application also provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the electronic device implements the cross-domain data transmission method as described above.
[0227] Fig.15 It is a structural diagram of a computer system suitable for implementing an electronic device of an embodiment of the present application.
[0228] It should be noted that Fig.15 The computer system 1500 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0229] like Fig.15As shown, the computer system 1500 includes a central processing unit (CPU) 1501, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1502 or the program loaded from the storage part 1508 to the random access memory (RAM) 1503, such as executing the method in the above embodiment. In RAM 1503, various programs and data required for system operation are also stored. CPU 1501, ROM 1502 and RAM 1503 are connected to each other through bus 1504. Input / output (I / O) interface 1505 is also connected to bus 1504.
[0230] The following components are connected to the I / O interface 1505: an input section 1506 including a keyboard, a mouse, etc.; an output section 1507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1508 including a hard disk, etc.; and a communication section 1509 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 1509 performs communication processing via a network such as the Internet. A drive 1510 is also connected to the I / O interface 1505 as needed. A removable medium 1511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1510 as needed so that a computer program read therefrom is installed into the storage section 1508 as needed.
[0231] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 1509, and / or installed from a removable medium 1511. When the computer program is executed by a central processing unit (CPU) 1501, various functions defined in the system of the present application are executed.
[0232] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. Computer-readable media may be, for example, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples of computer-readable media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable medium may be any tangible medium containing or storing a program, which may be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable computer program is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. A computer program contained on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.
[0233] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0234] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.
[0235] Another aspect of the present application also provides a computer-readable medium having a computer program stored thereon, which implements the cross-domain data transmission method as described above when the computer program is executed by a processor. The computer-readable medium may be included in the electronic device described in the above embodiment, or may exist independently without being assembled into the electronic device.
[0236] Another aspect of the present application also provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable medium. A processor of a computer device reads the computer instruction from the computer-readable medium, and the processor executes the computer instruction, so that the computer device executes the cross-domain data transmission method provided in each of the above embodiments.
[0237] The above content is only a preferred exemplary embodiment of the present application and is not intended to limit the implementation scheme of the present application. A person skilled in the art can easily make corresponding changes or modifications based on the main concept and spirit of the present application. Therefore, the scope of protection of the present application shall be based on the scope of protection required by the claims.
Claims
1. A cross-domain data transmission method, characterized in that: Applied to a cloud platform, the cloud platform includes a first node and a second node located in different domains, the method is performed by an intermediate node created by the cloud platform, the intermediate node is created after receiving an intermediate node creation request sent by the first node, and the method includes: receiving the encrypted data sent by the first node; Decrypting the encrypted data to obtain decrypted data; Performing a security check on the encrypted data according to the decrypted data to obtain a check result; If the verification result indicates that the verification is passed, sending the encrypted data to the second node; The intermediate node is destroyed after receiving transmission completion information for the encrypted data sent by the second node, and the transmission completion information means that the second node receives the encrypted data sent by the intermediate node.
2. The method according to claim 1, characterized in that The decrypted data includes the decrypted source data and the decrypted hash data to be verified, and the hash data to be verified is obtained by performing a hash operation on the source data; The performing security verification on the encrypted data according to the decrypted data to obtain a verification result includes: Performing a hash operation on the decrypted source data to obtain target hash data; If the target hash data matches the hash data to be verified, a verification result is obtained, which indicates that the security verification of the encrypted data has passed; If the target hash data does not match the hash data to be verified, a verification result is obtained, which is used to indicate that the transmission security verification of the encrypted data has failed.
3. The method according to claim 1, characterized in that The encrypted data includes the encrypted source data and the encrypted hash data to be verified, and the hash data to be verified is obtained by performing a hash operation on the source data; The decrypting the encrypted data to obtain the decrypted data comprises: The encrypted hash data to be verified is decrypted to obtain the decrypted hash data to be verified, and the encrypted source data is decrypted to obtain the decrypted source data.
4. The method according to claim 3, characterized in that The encrypted data also includes an encrypted key, the encrypted source data is encrypted using the key, and the encrypted key and the encrypted hash data to be verified are encrypted using a public key; The step of decrypting the encrypted hash data to be verified to obtain the decrypted hash data to be verified includes: Decrypting the encrypted hash data to be verified using a private key to obtain decrypted hash data to be verified; wherein the private key matches the public key; The decrypting the encrypted source data to obtain the decrypted source data comprises: Decrypting the encrypted key using the private key to obtain a decrypted key; The encrypted source data is decrypted using the decrypted key to obtain the decrypted source data.
5. The method according to any one of claims 1 to 4, characterized in that The step of sending the encrypted data to the second node comprises: Disconnecting a first transmission link established with the first node; wherein the first transmission link is used to transmit the encrypted data; Establishing a second transmission link with the second node; wherein the second transmission link is used to transmit the encrypted data; The encrypted data is sent to the second node through the second transmission link.
6. The method according to any one of claims 1 to 4, characterized in that Before receiving the encrypted data sent by the first node, the method further includes: An intermediate node creation request sent by the first node is received through the cloud platform, and the intermediate node is created based on the creation request; wherein the intermediate node creation request is sent by the first node after receiving the cross-domain data request sent by the second node and performing identity verification on the second node.
7. The method according to any one of claims 1 to 4, characterized in that After sending the encrypted data to the second node, the method further includes: Receive transmission completion information for the encrypted data sent by the second node through the cloud platform, and destroy the intermediate node based on the transmission completion information; wherein the transmission completion information is sent by the second node after receiving the encrypted data sent by the intermediate node, decrypting the encrypted data, obtaining the decrypted data, and passing the security verification of the encrypted data based on the decrypted data.
8. A cross-domain data transmission device, characterized in that: Applied to a cloud platform, the cloud platform includes a first node and a second node located in different domains, the device is configured in an intermediate node created by the cloud platform, the intermediate node is created after receiving an intermediate node creation request sent by the first node, and the device includes: A receiving module, configured to receive the encrypted data sent by the first node; A decryption module, configured to decrypt the encrypted data to obtain decrypted data; A verification module, configured to perform a security verification on the encrypted data according to the decrypted data to obtain a verification result; a sending module, configured to send the encrypted data to the second node if the verification result indicates that the verification is passed; The intermediate node is destroyed after receiving transmission completion information for the encrypted data sent by the second node, and the transmission completion information means that the second node receives the encrypted data sent by the intermediate node.
9. An electronic device, characterized in that: include: one or more processors; A memory for storing one or more programs, which, when executed by the electronic device, enables the electronic device to implement the cross-domain data transmission method as described in any one of claims 1 to 7.
10. A computer readable medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the cross-domain data transmission method according to any one of claims 1 to 7 is implemented.
