Privacy computing system, method and device, electronic equipment and medium

Abstract

The invention provides a privacy computing system, method and device, electronic equipment and a medium, which are used for realizing interconnection and intercommunication between privacy algorithm products stored in different privacy computing equipment. In the embodiment of the invention, a second privacy computing device can send a privacy computing request to a first privacy computing device, and the privacy computing request carries a target permission voucher; the first privacy computing device may, upon receiving a privacy computing request, identify a first data plane in the first privacy computing device indicated by a target permission credential, perform a corresponding privacy computing based on a privacy algorithm product in the first data plane, and send a computing result to the second privacy computing device, based on which the privacy computing request is received, to the second privacy computing device. The purpose that privacy algorithm products stored in different privacy computing devices can be interconnected and intercommunicated can be achieved.

Description

Technical Field

[0001] The present application relates to the field of network security technology, and in particular to a privacy computing system, method, device, electronic device and medium. Background Art

[0002] Privacy computing (Privacy compute or Privacy computing) refers to a collection of technologies that implement data analysis and computing while protecting the data itself from external leakage, so as to achieve the goal of "available but invisible" data, and realize the transformation and release of data value while fully protecting data and privacy security.

[0003] With the increasing awareness of data protection in the industry and the tightening of privacy regulatory policies, privacy computing has attracted widespread attention in the industry due to its "available, invisible" characteristics. Many technology vendors have launched privacy computing products with industry characteristics. While enriching market choices, numerous privacy computing products have also brought new challenges. For example, privacy computing products launched by different technology vendors are usually designed and implemented based on different system platforms. When privacy computing products of different system platforms are stored in different privacy computing devices, privacy computing products of different system platforms usually cannot complete information interaction, turning "data islands" into "computing islands". In addition, even if the same privacy computing product is launched by the same technology vendor, when the same privacy computing product is stored in different privacy computing devices, the same privacy computing product usually cannot complete information interaction, which also turns "data islands" into "computing islands".

[0004] Therefore, the interoperability problem between privacy algorithm products stored in different privacy computing devices has become an absolute pain point in the industry. How to achieve interoperability between privacy algorithm products stored in different privacy computing devices is a technical problem that needs to be solved urgently. Summary of the invention

[0005] The present application provides a privacy computing system, method, apparatus, electronic device, and medium for realizing interconnection between privacy algorithm products stored in different privacy computing devices.

[0006] In a first aspect, the present application provides a privacy-preserving computing system, the system comprising: a first privacy-preserving computing device and at least one second privacy-preserving computing device; wherein:

[0007] Any second privacy-preserving computing device, used to send a privacy-preserving computing request to the first privacy-preserving computing device, wherein the privacy-preserving computing request carries a target permission credential;

[0008] The first privacy computing device is used to receive the privacy computing request, identify the first data plane in the first privacy computing device indicated by the target license credential, perform corresponding privacy computing based on the privacy algorithm product in the first data plane, and send the calculation result to the second privacy computing device.

[0009] In a possible implementation, the first privacy computing device is further used to:

[0010] creating a session corresponding to the target license credential;

[0011] Based on the session, the calculation result and the correspondence between the session and the target permission credential are sent to the second privacy computing device, so that the second privacy computing device identifies the second data plane in the second privacy computing device indicated by the target permission credential and sends the calculation result to the second data plane.

[0012] In a possible implementation, the first privacy computing device is further used to:

[0013] Sending an authorization request to a second privacy computing device that performs management-plane intercommunication and collaborative privacy computing tasks with the first privacy computing device, wherein the authorization request carries the privacy computing resource entity information of the target data plane involved by the first privacy computing device;

[0014] The second privacy-preserving computing device is configured to receive the authorization request, generate a permission credential between the privacy-preserving computing resource entity information of any data plane in the second privacy-preserving computing device and the privacy-preserving computing resource entity information of the target data plane in the first privacy-preserving computing device, and send the permission credential to the first privacy-preserving computing device;

[0015] The first privacy computing device is used to receive and save the permission credential.

[0016] In a possible implementation, the first privacy computing device is specifically used to:

[0017] The management layer in the management plane of the first privacy computing device receives the privacy computing request;

[0018] The management layer sends a privacy computing task for the privacy computing request to the scheduling layer in the first data plane. When receiving the privacy computing task, the scheduling layer determines the scenario algorithm layer and security algorithm layer where the privacy algorithm product involved in the privacy computing task is located, and calls the scenario algorithm layer and security algorithm layer to perform corresponding privacy computing based on the privacy algorithm product.

[0019] In a possible implementation, the first privacy computing device is specifically used to:

[0020] The transport layer in the first data plane sends the calculation result and the correspondence between the session and the target permission credential to the second privacy computing device based on the session.

[0021] In a possible implementation, the first privacy computing device is further used to:

[0022] Based on the service grid layer in the first privacy computing device, the same exclusive identifier is configured for each target data processing flow generated by the privacy computing request between the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transport layer, and the exclusive identifier is used to characterize the privacy computing request.

[0023] In a possible implementation, the first privacy computing device is further used to:

[0024] If a data processing flow tracking link query request is received for the privacy computing request, the target data processing flow identified as the exclusive identifier is filtered out from each data processing flow according to the identifier corresponding to each data processing flow, and a data processing flow tracking link constructed by at least one of the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transmission layer related to each target data processing flow is generated and displayed.

[0025] In a second aspect, the present application provides a privacy-preserving computing method, which is applied to a first privacy-preserving computing device, and includes:

[0026] Receiving a privacy computing request sent by any second privacy computing device, wherein the privacy computing request carries a target permission credential;

[0027] Identify a first data plane in a first privacy computing device indicated by the target license credential, perform corresponding privacy computing based on a privacy algorithm product in the first data plane, and send the computing result to the second privacy computing device.

[0028] In a possible implementation, after receiving the privacy computing request sent by any second privacy computing device and before sending the computing result to the second privacy computing device, the method further includes:

[0029] creating a session corresponding to the target license credential;

[0030] The sending the calculation result to the second privacy computing device comprises:

[0031] Based on the session, the calculation result and the correspondence between the session and the target permission credential are sent to the second privacy computing device.

[0032] In a possible implementation, before receiving the privacy computing request sent by any second privacy computing device, the method further includes:

[0033] Sending an authorization request to a second privacy computing device that performs management-plane intercommunication and collaborative privacy computing tasks with the first privacy computing device, wherein the authorization request carries the privacy computing resource entity information of the target data plane involved by the first privacy computing device; allowing the second privacy computing device to receive the authorization request and generate a permission credential between the privacy computing resource entity information of any data plane in the second privacy computing device and the privacy computing resource entity information of the target data plane in the first privacy computing device, and allowing the second privacy computing device to send the permission credential to the first privacy computing device;

[0034] The permission credential is received and stored.

[0035] In a possible implementation, receiving a privacy-preserving computing request sent by any second privacy-preserving computing device includes:

[0036] The management layer in the management plane of the first privacy computing device receives the privacy computing request;

[0037] The performing corresponding privacy calculation based on the privacy algorithm product in the first data plane includes:

[0038] The management layer sends a privacy computing task for the privacy computing request to the scheduling layer in the first data plane. When receiving the privacy computing task, the scheduling layer determines the scenario algorithm layer and security algorithm layer where the privacy algorithm product involved in the privacy computing task is located, and calls the scenario algorithm layer and security algorithm layer to perform corresponding privacy computing based on the privacy algorithm product.

[0039] In a possible implementation, sending the calculation result to the second data plane in the second privacy computing device based on the session includes:

[0040] The transport layer in the first data plane sends the calculation result and the correspondence between the session and the target permission credential to the second privacy computing device based on the session.

[0041] In a possible implementation, the method further includes:

[0042] Based on the service grid layer in the first privacy computing device, the same exclusive identifier is configured for each target data processing flow generated by the privacy computing request between the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transport layer, and the exclusive identifier is used to characterize the privacy computing request.

[0043] In a possible implementation, the method further includes:

[0044] If a data processing flow tracking link query request is received for the privacy computing request, the target data processing flow identified as the exclusive identifier is filtered out from each data processing flow according to the identifier corresponding to each data processing flow, and a data processing flow tracking link constructed by at least one of the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transmission layer related to each target data processing flow is generated and displayed.

[0045] In a third aspect, the present application provides a privacy-preserving computing method, which is applied to a second privacy-preserving computing device, and includes:

[0046] A privacy computing request is sent to a first privacy computing device, wherein the privacy computing request carries a target permission credential; the first privacy computing device identifies a first data plane in the first privacy computing device indicated by the target permission credential, and the first privacy computing device performs corresponding privacy computing based on a privacy algorithm product in the first data plane and sends the calculation result to the second privacy computing device.

[0047] In a possible implementation, the method further includes:

[0048] If the calculation result sent by the first privacy computing device and the correspondence between the session and the target permission credential are received, the second data plane in the second privacy computing device indicated by the target permission credential is identified, and the calculation result is sent to the second data plane.

[0049] In a possible implementation, the method further includes:

[0050] Receiving an authorization request sent by the first privacy computing device that performs a management plane intercommunication and collaborative privacy computing task with the second privacy computing device, wherein the authorization request carries privacy computing resource entity information of a target data plane involved by the first privacy computing device;

[0051] Generate a permission credential between the privacy computing resource entity information of any data plane in the second privacy computing device and the privacy computing resource entity information of the target data plane in the first privacy computing device, and send the permission credential to the first privacy computing device.

[0052] In a fourth aspect, the present application provides a privacy computing device, comprising a unit or module for executing any method as described in the second aspect, or comprising a unit or module for executing any method as described in the third aspect.

[0053] When the privacy computing device executes any one of the methods in the second aspect, the privacy computing device includes:

[0054] A receiving module, configured to receive a privacy computing request sent by any second privacy computing device, wherein the privacy computing request carries a target permission credential;

[0055] an identification module, configured to identify a first data plane in a first privacy computing device indicated by the target permission credential;

[0056] A computing module is used to perform corresponding privacy computing based on the privacy algorithm product in the first data plane, and send the computing result to the second privacy computing device.

[0057] In a possible implementation, the device further includes:

[0058] A creation module, configured to create a session corresponding to the target license credential;

[0059] The first sending module is used to send the calculation result and the corresponding relationship between the session and the target permission credential to the second privacy computing device based on the session.

[0060] In a possible implementation, the first sending module is further configured to send an authorization request to a second privacy computing device that performs management-plane intercommunication and collaborative privacy computing tasks with the first privacy computing device, wherein the authorization request carries the privacy computing resource entity information of the target data plane involved by the first privacy computing device; so that the second privacy computing device receives the authorization request and generates a permission credential between the privacy computing resource entity information of any data plane in the second privacy computing device and the privacy computing resource entity information of the target data plane in the first privacy computing device, and the second privacy computing device sends the permission credential to the first privacy computing device;

[0061] The receiving module is further configured to receive and save the license certificate.

[0062] In a possible implementation, the receiving module is specifically configured to receive the privacy computing request based on a management layer in a management plane of the first privacy computing device;

[0063] The computing module is specifically used to send a privacy computing task for the privacy computing request to the scheduling layer in the first data plane based on the management layer, and determine the scenario algorithm layer and security algorithm layer where the privacy algorithm product involved in the privacy computing task is located when the scheduling layer receives the privacy computing task, and perform corresponding privacy computing based on the privacy algorithm product by calling the scenario algorithm layer and security algorithm layer.

[0064] In a possible implementation, the first sending module is specifically configured to send the calculation result and the correspondence between the session and the target license credential to the second privacy computing device based on the transport layer in the first data plane and based on the session.

[0065] In a possible implementation, the device further includes:

[0066] A tracking module is used to configure the same exclusive identifier for each target data processing flow generated by the privacy computing request between the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transport layer based on the service grid layer in the first privacy computing device, and the exclusive identifier is used to characterize the privacy computing request.

[0067] In one possible implementation, the tracking module is also used to, if a data processing flow tracking link query request is received for the privacy computing request, filter out the target data processing flow identified as the exclusive identifier from each data processing flow according to the identifier corresponding to each data processing flow, and generate and display a data processing flow tracking link constructed by at least one of the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transport layer related to each target data processing flow.

[0068] Wherein, when the privacy computing device executes any one of the methods in the third aspect, the privacy computing device includes:

[0069] The second sending module is used to send a privacy computing request to the first privacy computing device, wherein the privacy computing request carries a target permission credential; so that the first privacy computing device identifies the first data plane in the first privacy computing device indicated by the target permission credential, and enables the first privacy computing device to perform corresponding privacy computing based on the privacy algorithm product in the first data plane and send the calculation result to the second privacy computing device.

[0070] In a possible implementation, the second sending module is further configured to, upon receiving the calculation result sent by the first privacy computing device and the correspondence between the session and the target license credential, identify the second data plane in the second privacy computing device indicated by the target license credential and send the calculation result to the second data plane.

[0071] In a possible implementation, the device further includes:

[0072] A licensing module is used to receive an authorization request sent by the first privacy computing device that performs management-plane intercommunication and collaborative privacy computing tasks with the second privacy computing device, wherein the authorization request carries the privacy computing resource entity information of the target data plane involved by the first privacy computing device; generate a licensing certificate between the privacy computing resource entity information of any data plane in the second privacy computing device and the privacy computing resource entity information of the target data plane in the first privacy computing device, and send the licensing certificate to the first privacy computing device.

[0073] In a fifth aspect, the present application provides an electronic device comprising a processor and a memory, wherein the memory stores a program code, and when the program code is executed by the processor, the processor executes the steps of the method as described in any one of the second aspect, or executes the steps of the method as described in any one of the third aspect.

[0074] In a sixth aspect, the present application provides a computer-readable storage medium comprising a program code. When the storage medium is run on an electronic device, the program code is used to cause the electronic device to execute the steps of the method as described in any one of the second aspect, or to execute the steps of the method as described in any one of the third aspect.

[0075] In a seventh aspect, the present application provides a computer program product, which, when called by a computer, enables the computer to execute the method as described in any one of the second aspect, or execute the method as described in any one of the third aspect.

[0076] In the embodiment of the present application, the second privacy computing device can send a privacy computing request to the first privacy computing device, and the privacy computing request carries a target permission credential. When receiving the privacy computing request, the first privacy computing device can identify the first data plane in the first privacy computing device indicated by the target permission credential, perform corresponding privacy computing based on the privacy algorithm product in the first data plane, and send the calculation result to the second privacy computing device. Based on this, the purpose of interconnection and intercommunication between privacy algorithm products stored in different privacy computing devices can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] In order to more clearly illustrate the implementation methods in the embodiments of the present application or the related technologies, the following is a brief introduction to the drawings required for use in the embodiments or the related technology descriptions. Obviously, the drawings described below are some embodiments of the present application, and a person skilled in the art can also obtain other drawings based on these drawings.

[0078] Figure 1 A schematic diagram of the structure of a privacy computing system provided by some embodiments is shown;

[0079] Figure 2 A schematic diagram of a privacy algorithm interconnection process provided by some embodiments is shown;

[0080] Figure 3A A schematic diagram of a data processing flow tracking link provided by some embodiments is shown;

[0081] Figure 3B Another data processing flow tracking link schematic diagram provided by some embodiments is shown;

[0082] Figure 4 A schematic diagram of the relationship between Envoy and Jaeger provided in some embodiments is shown;

[0083] Figure 5 A schematic diagram of a traffic forwarding relationship between a service component and Envoy provided in some embodiments is shown;

[0084] Figure 6 A schematic diagram of a privacy computing process provided by some embodiments is shown;

[0085] Figure 7 Another privacy computing process schematic diagram provided by some embodiments is shown;

[0086] Figure 8 A schematic diagram of another privacy computing process provided by some embodiments is shown;

[0087] Fig. 9 A schematic diagram of a privacy computing device provided by some embodiments is shown;

[0088] Fig.10 A schematic diagram of another privacy computing device provided by some embodiments is shown;

[0089] Fig.11 A schematic diagram of the structure of an electronic device provided by some embodiments is shown. DETAILED DESCRIPTION

[0090] In order to achieve interconnection between privacy computing products stored in different privacy computing devices, the present application provides a privacy computing system, method, apparatus, device and medium.

[0091] In order to make the purpose and implementation method of the present application clearer, the exemplary implementation method of the present application will be clearly and completely described below in conjunction with the drawings in the exemplary embodiments of the present application. Obviously, the described exemplary embodiments are only part of the embodiments of the present application, rather than all the embodiments.

[0092] The terms "first", "second", "third", etc. in the specification and claims of this application and the above drawings are used to distinguish similar or similar objects or entities, and do not necessarily mean to limit a specific order or sequence, unless otherwise noted. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances.

[0093] The terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover but not exclude inclusion, for example, a product or device comprising a list of components is not necessarily limited to all the components expressly listed but may include other components not expressly listed or inherent to such product or device.

[0094] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

[0095] Embodiment 1:

[0096] Figure 1 A schematic diagram of the structure of a privacy computing system provided by some embodiments is shown, the system comprising: a first privacy computing device 11 and at least one second privacy computing device 12;

[0097] Any second privacy-preserving computing device, used to send a privacy-preserving computing request to the first privacy-preserving computing device, wherein the privacy-preserving computing request carries a target permission credential;

[0098] The first privacy computing device is used to receive the privacy computing request, identify the first data plane in the first privacy computing device indicated by the target license credential, perform corresponding privacy computing based on the privacy algorithm product in the first data plane, and send the calculation result to the second privacy computing device.

[0099] In a possible implementation, the first privacy computing device 11 and the second privacy computing device 12 may be devices such as PCs, mobile terminals, or devices such as servers, which are not specifically limited in this application. The first privacy computing device 11 and the second privacy computing device 12 may be two different devices.

[0100] In a possible implementation, the number of second privacy computing devices 12 can be one or more. The present application does not specifically limit the number of second privacy computing devices 12, and can be flexibly set according to needs. Regardless of whether the number of second privacy computing devices 12 is one or more, for each second privacy computing device 12, the privacy computing process when the first privacy computing device 11 and the privacy algorithm product stored in the second privacy computing device 12 are interconnected can adopt the privacy computing process provided in the embodiment of the present application, which will not be repeated here.

[0101] In one possible implementation, see Figure 2 , Figure 2 A schematic diagram of a privacy algorithm interconnection process provided by some embodiments is shown, such as Figure 2 As shown, each privacy computing device may include a management plane and a data plane, each privacy computing device may include several data planes, and each data plane may store corresponding privacy algorithm products. The first privacy computing device and the second privacy computing device may collaborate on privacy computing tasks (synchronize collaborative information) through intercommunication between management planes, and may execute privacy computing tasks based on intercommunication between data planes, so that the privacy algorithm product stored in a data plane (such as the first data plane) of the first privacy computing device and the privacy algorithm product stored in a data plane (such as the second data plane) of the second privacy computing device can be interconnected and interoperated for joint computing. Optionally, the management plane intercommunication and data plane intercommunication between privacy computing devices may be independent of each other.

[0102] Please refer again Figure 2In a possible implementation, when the first privacy computing device and any second privacy computing device communicate with each other on the management plane, some coarse-grained contract operations for device nodes and network relationship operations can be performed first. Exemplarily, the privacy algorithm developer can send the Internet Protocol (IP) address, unique code (ID) and other identification information of the first privacy computing device 11 offline in advance (for the convenience of description, the identification information of the first privacy computing device 11 will be referred to as the first identification information in the following) to the second privacy computing device 12, and the second privacy computing device 12 can regard the first privacy computing device 11 corresponding to the first identification information as a safe and compliant device, and save the first identification information in the identification information of its own compliant device. At the same time, the privacy algorithm developer can also send the IP address, ID and other identification information of the second privacy computing device 12 offline in advance (for the convenience of description, the identification information of the second privacy computing device 12 will be referred to as the second identification information in the following) to the first privacy computing device 11, and the first privacy computing device 11 can regard the second privacy computing device 12 corresponding to the second identification information as a safe and compliant device, and save the second identification information in the identification information of its own compliant device. That is to say, the first privacy computing device 11 and the second privacy computing device 12 can exchange identification information such as node IP, node ID, etc.

[0103] In a possible implementation, when the first privacy computing device and the second privacy computing device communicate with each other on the management plane to collaborate on the privacy computing task, a fine-grained authorization and permission process for the data plane in the privacy computing device can be performed. Specifically, when performing the authorization and permission process, the first privacy computing device can send an authorization request to the second privacy computing device, and the authorization request can carry the privacy computing resource entity information of several target data planes involved in the first privacy computing device. Among them, the privacy computing resource entity information of the data plane carried in the authorization request may include node information (such as node ID, node service address, etc.), data set information, project information, process information of joint privacy computing, privacy computing task information and other privacy computing resource entity information, which is not specifically limited in this application. In a possible implementation, the authorization request may also carry the first identification information of the first privacy computing device. Among them, the target data plane can be all data planes in the first privacy computing device, or it can be part of the data plane in the first privacy computing device, which is not specifically limited in this application.

[0104] After receiving the authorization request, the second privacy computing device can first determine whether the first privacy computing device 11 corresponding to the first identification information is a safe and compliant device. For example, it can determine whether the first identification information is included in the identification information of the compliant device it saves. If so, the first privacy computing device can be considered to be a safe and compliant device. In one possible implementation, for any target data plane, the second privacy computing device can generate a permission certificate between the privacy computing resource entity information of any target data plane (such as the first data plane) in the first privacy computing device and the privacy computing resource entity information of any data plane (such as the second data plane) in the second privacy computing device, and can send the generated permission certificate to the first privacy computing device. After receiving the above-mentioned permission certificate, the first privacy computing device can save the permission certificate.

[0105] Among them, the "first" and "second" in the above-mentioned first privacy computing device and the second privacy computing device are only used to distinguish different privacy computing devices, and the privacy computing devices themselves are not specifically limited. The process of the first privacy computing device sending an authorization request to the second privacy computing device in the above embodiment is only an exemplary description. For example, the first privacy computing device can send the above authorization request to the second privacy computing device, or the second privacy computing device can send the above authorization request to the first privacy computing device. When the second privacy computing device sends the above authorization request to the first privacy computing device, the authorization request can carry information of the set target data plane (such as the second data plane) of the second privacy computing device; after receiving the authorization request, the first privacy computing device can generate a permission certificate between the set target data plane (such as the second data plane) of the second privacy computing device and any data plane (such as the first data plane) in the first privacy computing device, and send the permission certificate to the second privacy computing device, which will not be repeated here.

[0106] In a possible implementation, after the above-mentioned data plane-level authorization and permission process is performed between the first privacy computing device and the second privacy computing device, a joint computing process based on the privacy algorithm product stored in the data plane can be performed. Exemplarily, the second privacy computing device can send a privacy computing request to the first privacy computing device, and the privacy computing request can carry a target permission credential, wherein the target permission credential can be a permission credential between the privacy computing resource entity information of a data plane (such as the first data plane) in the first privacy computing device and the privacy computing resource entity information of a data plane (such as the second data plane) in the second privacy computing device.

[0107] In one possible implementation, please refer again to Figure 2, the first privacy computing device can receive the privacy computing request sent by the second privacy computing device based on the management layer in its own management plane. After receiving the privacy computing request, the management layer can identify the target license credential carried in the privacy computing request and authenticate the target license credential. For example, the management layer of the first privacy computing device can compare the target license credential with the license credential saved by itself. If the license credential saved by itself contains the above-mentioned target license credential and the target license credential is within the validity period, it can be considered that the target license credential is compliant, and the first data plane in the first privacy computing device indicated by the target license credential can be identified. Afterwards, the management layer can send the privacy computing task for this privacy computing request to the scheduling layer in the first data plane to perform the corresponding privacy computing based on the privacy algorithm product in the first data plane. For example, when the scheduling layer in the first data plane receives the privacy computing task, it can determine the scene algorithm layer and security algorithm layer where the privacy algorithm product involved in the privacy computing task is located, and perform the corresponding privacy computing based on the privacy algorithm product by calling the scene algorithm layer and security algorithm layer where the privacy algorithm product is located. Afterwards, the calculation result can be sent to the second privacy computing device. The specific process of privacy computing will not be repeated here.

[0108] Among them, in order to increase the flexibility and accuracy of privacy computing, the privacy algorithm product can be decoupled into two algorithms including scenario algorithms and security algorithms. Among them, if the privacy algorithm product does not contain a security algorithm, but only contains a scenario algorithm, it can be considered that the processed data is calculated in plain text without secure encryption protection; if the privacy algorithm product contains a scenario algorithm and a security algorithm, it can be considered that the processed data is privacy-oriented under the protection of secure encryption. The scenario algorithm and security algorithm contained in the privacy algorithm product can be flexibly selected according to needs. For example, the scenario algorithm can be a privacy intersection algorithm or a longitudinal logistic regression algorithm, etc. The security algorithm can be a secure multi-party computing protocol or a cryptographic algorithm such as homomorphic encryption and secret sharing protocol. The security algorithm can be used to perform primitive operations or calculations on data in a confidential state. This application does not make specific restrictions on this. In one possible implementation, the scenario algorithm can be saved in the scenario algorithm layer (also called the application algorithm layer), and the security algorithm can be saved in the security operator layer.

[0109] In one possible implementation, after the first privacy computing device receives a privacy computing request sent by the second privacy computing device and identifies the first data plane in the first privacy computing device indicated in the target license credential, the first data plane in the first privacy computing device can, for example, create a session corresponding to the target license credential and a session identifier (Session Id).

[0110] When receiving a privacy computing task, the scheduling layer in the first data plane can determine the scenario algorithm layer and security algorithm layer where the privacy algorithm product involved in the privacy computing task is located, and send the session identifier (Session Id) to the scenario algorithm layer and security algorithm layer where the privacy algorithm product is located. After the scenario algorithm layer and the security algorithm layer perform corresponding privacy computing based on the privacy algorithm product, the calculation results and the session identifier (Session Id) can be sent to the transport layer (also referred to as a transmission module or transmission component) in the target data plane. The transport layer can generate a routing table based on the session corresponding to the session identifier (Session Id), and send the calculation results and the corresponding relationship between the session (Session Id) and the target license credential to the second privacy computing device.

[0111] In a possible implementation, after receiving the calculation result and the correspondence between the session and the target license credential, the management layer (gateway) in the second privacy computing device can identify the second data plane in the second privacy computing device indicated by the target license credential and send the calculation result to the second data plane. Figure 2 The transport layer (referred to as the transport module in the figure) in the first data plane of the first privacy computing device sends the calculation results to the second privacy computing device, and the management layer in the second privacy computing device sends the calculation results to the second data plane in the second privacy computing device. This process can be called message communication.

[0112] In the embodiment of the present application, the second privacy computing device can send a privacy computing request to the first privacy computing device, and the privacy computing request carries a target permission credential. When receiving the privacy computing request, the first privacy computing device can identify the first data plane in the first privacy computing device indicated by the target permission credential, perform corresponding privacy computing based on the privacy algorithm product in the first data plane, and send the calculation result to the second privacy computing device. Based on this, the purpose of interconnection and intercommunication between privacy algorithm products stored in different privacy computing devices can be achieved.

[0113] If the privacy computing device is regarded as a device (a node) belonging to a company, and a privacy computing device corresponds to a management plane, then the different data planes in the privacy computing device can be regarded as data planes belonging to different departments in the company. Compared with the architecture of one management plane corresponding to one data plane, if multiple different departments in a company want to cooperate with the same external company under this architecture, it is necessary to configure a node (node ​​ID, node-id) and a management plane for each department. In view of the fact that multiple departments need to repeat the device node-level signing operations, open up network relationships and other operations, resulting in many repeated operations, in the embodiment of the present application, multiple different departments of the same company can share a device node architecture (also referred to as an architecture of one management plane corresponding to multiple different data planes or a multi-engine architecture of one set of management planes corresponding to multiple sets of data planes). Multiple different departments only need to perform device node-level operations once, which can avoid repeated operations and improve efficiency. At the same time, the privacy computing products of different departments are configured on different data planes, and authorization and permission operations at the data plane level are performed separately, which can also meet the data isolation and privacy protection needs between different departments.

[0114] In addition, compared to aggregating the data processing flows (traffic) generated by each data plane to the management plane in the privacy computing device, and having the management plane uniformly forward the traffic, which causes a large amount of traffic pressure on the management plane, in the embodiment of the present application, the calculation results can be sent to the second privacy computing device based on the transport layer in the target data plane, etc., which can reduce the traffic pressure caused by the unified traffic forwarding by the management plane.

[0115] Embodiment 2:

[0116] Considering that when privacy algorithm products are interconnected, data processing flows for resource application approval of various categories of resources such as node information, data set information, project information, process information, etc., as well as data processing flows for interaction between management planes, data processing flows for algorithm scheduling interaction between privacy computing products in the data plane, etc., are involved, the interaction is frequent and the links of the data processing flows are relatively complex. In order to track and monitor the data processing flows, ensure the security of the interconnected and interoperable joint privacy computing process, and facilitate the subsequent rapid investigation of the causes of errors when errors and exceptions occur, on the basis of the above embodiments, in the embodiments of the present application, the first privacy computing device is also used to:

[0117] Based on the service mesh layer in the first privacy computing device, the same exclusive identifier is configured for each target data processing flow generated by the privacy computing request between the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transport layer, and the exclusive identifier is used to characterize the privacy computing request.

[0118] Among them, the service mesh layer is an infrastructure layer, and the service mesh layer can include a proxy module, namely a sidecar module. The sidecar module can be used to handle communication between services. Based on the sidecar module, the same exclusive identifier (traceId) that can characterize the privacy computing request can be configured for each target data processing flow generated by the same privacy computing request between the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transport layer in the privacy computing device, so as to facilitate tracking and monitoring of the data processing flow generated by the above privacy computing request.

[0119] Exemplarily, when the management layer (WEB management end) sends a request to create a privacy computing task corresponding to a privacy computing request to the scheduling layer, the sidecar module in the scheduling layer container can inject (configure) a set of standard request header (http request header) information (header) for the data processing flow (traffic). The standard request header information contains a unique identifier configured for the corresponding data processing flow (the unique identifier can also be called a link tracking identifier, x-trace-id). After the data processing flow flowing into the data plane is configured with a unique identifier, each other data processing flow generated based on the data processing flow in the data plane will also be configured with the same standard request header (http request header) information. These data processing flows can be uniformly managed by the service mesh layer. In the interconnection architecture, the data processing flow (traffic) can be tracked using the unique identifier x-trace-id in the standard request header.

[0120] In a possible implementation, the standard request header may carry the information shown in Table 1. For example, in addition to the above-mentioned exclusive identifier (link tracking identifier, x-trace-id), the standard request header may also carry a signature value (x-auth-sign) for security verification, cross-site request forgery protection (x-csrf-protection) for avoiding cross-site request forgery attacks, the requester node id (x-source-node-id), the destination node id (x-target-node-id), an anti-replay random string (x-nonce) for generating a signature value, a timestamp (x-timestamp), and a permission credential set (x-mprac-token-set).

[0121] Table 1

[0122]

[0123] The information included in the permission voucher set (x-mprac-token-set) is introduced below. For example, when the first privacy computing device sends an authorization request to the second privacy computing device, the authorization request may carry privacy computing resource entity information (for the convenience of description, referred to as entity information) such as node information, data set information, project information, process information of joint privacy computing, and privacy computing task information for a certain data plane in the first privacy computing device. For the data plane, the second privacy computing device may review each entity information such as node information, data set information, project information, process information of joint privacy computing, and privacy computing task information of the data plane in turn. After each entity information is reviewed and approved, a sub-permission voucher for the entity information may be generated. The sub-permission voucher may include privacy computing resource entity information of a certain data plane (such as the first data plane) of the first privacy computing device and privacy computing resource entity information of a certain data plane (such as the second data plane) of the second privacy computing device. These sub-permission vouchers may constitute a permission voucher set. The target permission voucher introduced in the above embodiment may also be considered as a permission voucher set composed of multiple sub-permission vouchers. In a possible implementation, the license credential set may be uniformly maintained and managed by the service grid layer. The above-described process of authenticating and verifying the target license credential may be considered as the authentication and verification process for each sub-license credential. If each sub-license credential is compliant, the target license credential may be considered compliant, and no further details will be given here.

[0124] For ease of understanding, the privacy computing process provided by this application is explained below through a specific embodiment. Figure 2 , the process includes the following steps:

[0125] The management layer in the privacy computing device, as the management surface of the interconnection architecture, can provide a visual configuration page for various algorithms (privacy algorithm products), and can configure the above-mentioned entity information of various algorithms based on the visual configuration page. The management layer, scheduling layer, scenario algorithm layer, security algorithm layer, transport layer and other components in the interconnection architecture can be deployed in a containerized manner. At the same time, these components can provide standard application programming interfaces (Application Programming Interface, API) to the outside world. The inflow and outflow of traffic of each component (business component) can be uniformly managed by the service grid layer. For example, the sidecar module in the service grid layer can configure (mark) a unique exclusive identifier (traceId) for the inflow and outflow of traffic on each container component, and forward the inflow and outflow traffic to facilitate subsequent tracking and monitoring of the traffic.

[0126] In a possible implementation, the privacy computing interconnection architecture may include management plane resource approval traffic, scheduling layer algorithm call state synchronization traffic, algorithm layer privacy computing traffic, etc. Among them, the data processing flow (traffic) generated when the above management layer processes privacy computing requests, etc. can be called management plane resource approval traffic, the data processing flow (traffic) generated when the above scheduling layer processes privacy computing requests, etc. can be called scheduling layer algorithm call state synchronization traffic, and the data processing flow (traffic) generated when the above algorithm layer processes privacy computing requests can be called algorithm layer privacy computing traffic.

[0127] Among them, the management plane resource approval traffic is mainly the application and approval confirmation of resources (entity information). The application information corresponding to the management plane resource approval traffic can carry the permission certificate (token_id) and signature (auth_id) of resource approval. The management plane Envoy can automatically add signature information, permission certificate (token_id), exclusive identification and other information to the standard request header information of the corresponding traffic, and uniformly manage the token_id of different resources.

[0128] For the state synchronization traffic initiated by the scheduling layer algorithm, the scheduling layer Envoy can perform routing forwarding based on the permission credential set in the standard request header information based on its reverse proxy function. For example, for the traffic for starting a task, the request header information of the corresponding traffic can carry the sub-permission credential of each entity resource (entity information) required to start the task, such as the node information sub-permission credential (node ​​token_id), the dataset information sub-permission credential (dataset token_id), the project information sub-permission credential (project token_id), the algorithm component sub-permission credential (algorithm component token_id), the process information sub-permission credential of the joint privacy computing (process token_id), etc. The scheduling layer Envoy performs reverse proxy based on the permission credential set and can authenticate the permission credential set of the traffic. The scheduling layers in the data plane of different privacy computing devices can perform operations such as process coordination of joint privacy computing based on the information in the standard request header.

[0129] For algorithm layer privacy computing traffic, in order to adapt to different forms of communication components between heterogeneous privacy computing platforms, the algorithm layer Envoy can act as a gateway to adapt to different forms of algorithm layer privacy computing traffic. For example, the algorithm layer Envoy can convert algorithm layer privacy computing traffic in the form of grpc and algorithm layer privacy computing traffic in the form of http.

[0130] In the embodiments of the present application, the privacy computing traffic at the algorithm layer can adapt to the protocols of different privacy computing platforms, and can enhance the interoperability (connectivity) between heterogeneous privacy computing platforms. Among them, the application algorithm layers in the data planes of different privacy computing devices can communicate with each other based on the information in the standard request header to realize joint privacy computing, and the security operator layers in the data planes of different privacy computing devices can communicate with each other based on the information in the standard request header to realize joint privacy computing, which will not be repeated here. In one possible implementation, the algorithms in the algorithm layer (application algorithm layer and security operator layer) can be run based on the algorithm container loading module, which will not be repeated here.

[0131] The embodiments of the present application can decouple the processes of configuring exclusive identification for data processing flows (traffic) and forwarding authentication from privacy computing services through the service grid layer, thereby improving the service governance capabilities of the interconnected privacy computing architecture, improving the agility of traffic scheduling and the flexibility of business components, and reducing the difficulty of troubleshooting abnormal problems in business components.

[0132] Also, please refer again to Figure 2 In the embodiment of the present application, authentication and verification of license credentials can be integrated as a separate capability into the framework base of the interconnected privacy computing platform, thereby improving the security of the privacy computing platform. In addition, the framework base of the privacy computing platform can also integrate computing engines, storage engines, log modules, distributed link tracking system modules, etc.

[0133] Embodiment 3:

[0134] In order to facilitate the tracking and monitoring of traffic, based on the above embodiments, in the embodiment of the present application, the first privacy computing device is further used to:

[0135] If a data processing flow tracking link query request is received for the privacy computing request, the target data processing flow identified as the exclusive identifier is filtered out from each data processing flow according to the identifier corresponding to each data processing flow, and a data processing flow tracking link constructed by the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transmission layer related to each target data processing flow is generated and displayed.

[0136] In one possible implementation, see Figure 3A and Figure 3B , Figure 3A A schematic diagram of a data processing flow tracking link provided by some embodiments is shown. Figure 3B Another data processing flow tracking link diagram provided by some embodiments is shown. When processing a privacy computing request, it may pass through various service component elements (spans) such as the management layer, scheduling layer, algorithm layer, and transport layer. For example, Figure 3Aand Figure 3B In the example, after the management layer in privacy computing device A (referred to as node A management layer in the figure) receives the privacy computing request, it can call the algorithm layer (scenario algorithm layer, security algorithm layer) where the corresponding privacy computing product is located by calling the scheduling layer in privacy computing device A (referred to as node A scheduling layer in the figure) and the scheduling layer in privacy computing device B (referred to as node B scheduling layer in the figure). For example, the scheduling layer in privacy computing device A can call the algorithm layer in privacy computing device A (referred to as node A algorithm layer in the figure) and the algorithm layer in privacy computing device B (referred to as node B algorithm layer in the figure), etc. Based on the link call query function of each container component provided by open source service mesh (Istio), the path (Trace) of the call link between each service component element (span) when processing the privacy computing request can be connected in chronological order to form a network such as Figure 3A or Figure 3B The complete data processing flow tracking link (also called call chain) is shown. Specifically, when a data processing flow tracking link query request for a privacy computing request is received, the target data processing flow identified as a unique identifier representing the privacy computing request can be filtered out from each data processing flow based on Istio, thereby identifying each target data processing flow generated by processing the privacy computing request, and generating and displaying a data processing flow tracking link constructed by the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transport layer related to each target data processing flow according to the time sequence of each target data processing flow. Please refer to Figure 3B , the order of the service component elements from left to right on the horizontal axis (left and right in the figure) in the figure can be the service component elements that are called in a chronological order from first to last. The order of the service component elements from top to bottom on the vertical axis (up and down in the figure) in the figure can be the service component elements that are called in a chronological order from first to last, which will not be repeated here.

[0137] In a possible implementation, when generating a data processing flow tracking link based on Istio, etc., the corresponding data processing flow tracking link can be generated based on the Envoy architecture and Jaeger architecture in Istio. Among them, Envoy is a high-performance proxy server, i.e., a sidecar server, which can be used for communication between component services. Jaeger is a distributed tracing system that can help analyze and monitor the traffic tracked by Envoy. When a request is intercepted by Envoy (Sidecar), Envoy can automatically inject standard request header (HTTP Headers) information into the data processing flow corresponding to the request, and add a header information (Headers) starting with x-b3 and the like and a unique identifier (x-request-id) to the HTTP Headers information. The standard request header information can be transmitted in different service components (service component elements) along with the business processing logic. After the downstream Envoy (Sidecar) receives the traffic corresponding to the request, it can report the information of the relevant service component element span to Jaeger. Finally, the complete call link can be parsed by Jaeger.

[0138] See also Figure 4 , Figure 4 A schematic diagram of the relationship between Envoy and Jaeger provided by some embodiments is shown. For example, the Envoy (Front Envoy) located in the management layer in the first privacy computing device can be the first Envoy (Sidecar) in the first privacy computing device to receive the privacy computing request. It can be responsible for creating a root span (rootspan) and appending a unique identifier to the request header information. When the data processing flow that processes the request reaches different service components (service component elements), such as the scheduling layer in the privacy computing device A (referred to as the node A scheduling layer in the figure), the scheduling layer in the privacy computing device B (referred to as the node B scheduling layer in the figure), and the algorithm layer in the privacy computing device A (referred to as the node A algorithm layer in the figure), the corresponding Envoy (Sidecar) of each service component element can report the information of the corresponding data processing flow to Jaeger.

[0139] See also Figure 5 , Figure 5A schematic diagram of the traffic forwarding relationship between a service component and Envoy provided by some embodiments is shown. The service component (service component element) can run in a container under a kubernetes (K8s) Pod. Taking the scheduling layer as an example, the Envoy of the scheduling layer can forward the traffic flowing into the scheduling layer and the traffic flowing out of the scheduling layer. In the figure, I1 and I2 represent the traffic flowing into the scheduling layer, and O1 and O2 in the figure represent the traffic flowing out of the scheduling layer. The traffic flowing out of the scheduling layer can be forwarded to other service component elements downstream of the scheduling layer through Envoy. Each flow flowing into and out of the scheduling layer can contain the same header information. For example, the header information can contain the same exclusive identifier (traceId), etc. When the scheduling layer calls up the downstream algorithm layer and the algorithm layer of the cooperative node, the corresponding traffic can be configured with corresponding exclusive identifiers and other information. Each flow can also carry information such as the identifier (SpanId) of the service component element that processes the traffic. In a possible implementation, the process of generating a data processing flow tracking link based on Istio, etc. can realize the restoration of distributed requests into call links, and centrally display the service component call status for a request. In a possible implementation, the generated data processing flow tracking link can also display the processing time of each service component element span, whether each service component element span is callable or not, and other status information, such as the server that processes the request, etc., which will not be repeated here.

[0140] In one possible implementation, please refer again to Figure 2 In addition to the computing engine for privacy computing, the storage engine for storing information, the log module related to operation logs, etc., the framework base of the privacy computing platform can also be configured with a distributed link tracking system module. The process of building a data processing flow tracking link and the like described in the above embodiment can be implemented based on the distributed link tracking system module, which will not be repeated here.

[0141] In a possible implementation, in addition to performing traffic forwarding based on the sidecar module in the service mesh layer, the operations performed by the sidecar module can also be performed based on engine X (NGINX), F5, etc. in the service mesh layer. For ease of understanding, the privacy computing process provided by this application is introduced through a specific embodiment. Figure 6 , Figure 6 A schematic diagram of a privacy computing process provided by some embodiments is shown, and the process includes the following steps:

[0142] The management plane (management layer) in the first privacy computing device receives a privacy computing request (also referred to as external traffic in the figure) sent by the second privacy computing device based on its proxy application programming interface (API). Assuming that there are two data planes in the first privacy computing device, data plane 1 and data plane 2, the target permission credential carried in this privacy computing request is a permission credential indicating joint privacy computing based on the privacy computing resource entity information in data plane 1 (first data plane) in the first privacy computing device and the privacy computing resource entity information in the second data plane in the second privacy computing device. The management layer in the first privacy computing device can send a privacy computing task for this privacy computing request to the scheduling layer in the first data plane (data plane 1). When receiving the privacy computing task, the scheduling layer can determine the scene algorithm layer and security algorithm layer where the privacy algorithm product involved in the privacy computing task is located, and perform corresponding privacy computing based on the corresponding privacy algorithm product by calling the scene algorithm layer and the security algorithm layer. Afterwards, the transport layer in the first data plane can send the privacy computing result to the second data plane (not shown) in the second privacy computing device based on the corresponding session. Among them, the management layer and the scheduling layer can all perform operations such as traffic forwarding based on engine X (NGINX), etc., which will not be repeated here. The corresponding information for the management plane can be stored in a relational database (UPSQL) or a DBPM database, for example. The corresponding information for the scheduling layer can be stored in a Mysql database, for example. The corresponding information for the algorithm layer can be stored in an S3 database, for example. Information on different data planes can be saved in a harbor database, etc. In one possible implementation, the management plane may include components such as Federated AI Technology Enabler (fate), fate-site, fate-site-adapter, etc., which can implement secure computing protocols for homomorphic encryption and multi-party computing (MPC), etc., which will not be repeated here. The scheduling layer may include components such as fate-sdk and scheduler (schedulerlayer), which will not be repeated here.The algorithm layer may include privacy algorithms such as Elliptic Curve Diffie-Hellman Private Set Intersection (ECDH-PSI), Logistic Regression (LR), Public Key Cryptography with Private Set Intersection (RSA-PSI), and Extreme Gradient Boosting (XGB), which will not be described here.

[0143] Embodiment 3:

[0144] Based on the same technical concept, the present application provides a privacy computing method, which is applied to a first privacy computing device, see Figure 7 , Figure 7 Another privacy computing process schematic diagram provided by some embodiments is shown, the method comprising:

[0145] S701: Receive a privacy computing request sent by any second privacy computing device, where the privacy computing request carries a target permission credential.

[0146] S702: Identify the first data plane in the first privacy computing device indicated by the target license credential, perform corresponding privacy computing based on the privacy algorithm product in the first data plane, and send the calculation result to the second privacy computing device.

[0147] In a possible implementation, after receiving the privacy computing request sent by any second privacy computing device and before sending the computing result to the second privacy computing device, the method further includes:

[0148] creating a session corresponding to the target license credential;

[0149] The sending the calculation result to the second privacy computing device comprises:

[0150] Based on the session, the calculation result and the correspondence between the session and the target permission credential are sent to the second privacy computing device.

[0151] In a possible implementation, before receiving the privacy computing request sent by any second privacy computing device, the method further includes:

[0152] Sending an authorization request to a second privacy computing device that performs management-plane intercommunication and collaborative privacy computing tasks with the first privacy computing device, wherein the authorization request carries the privacy computing resource entity information of the target data plane involved by the first privacy computing device; allowing the second privacy computing device to receive the authorization request and generate a permission credential between the privacy computing resource entity information of any data plane in the second privacy computing device and the privacy computing resource entity information of the target data plane in the first privacy computing device, and allowing the second privacy computing device to send the permission credential to the first privacy computing device;

[0153] The permission credential is received and stored.

[0154] In a possible implementation, receiving a privacy-preserving computing request sent by any second privacy-preserving computing device includes:

[0155] The management layer in the management plane of the first privacy computing device receives the privacy computing request;

[0156] The performing corresponding privacy calculation based on the privacy algorithm product in the first data plane includes:

[0157] The management layer sends a privacy computing task for the privacy computing request to the scheduling layer in the first data plane. When receiving the privacy computing task, the scheduling layer determines the scenario algorithm layer and security algorithm layer where the privacy algorithm product involved in the privacy computing task is located, and calls the scenario algorithm layer and security algorithm layer to perform corresponding privacy computing based on the privacy algorithm product.

[0158] In a possible implementation, sending the calculation result to the second data plane in the second privacy computing device based on the session includes:

[0159] The transport layer in the first data plane sends the calculation result and the correspondence between the session and the target permission credential to the second privacy computing device based on the session.

[0160] In a possible implementation, the method further includes:

[0161] Based on the service grid layer in the first privacy computing device, the same exclusive identifier is configured for each target data processing flow generated by the privacy computing request between the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transport layer, and the exclusive identifier is used to characterize the privacy computing request.

[0162] In a possible implementation, the method further includes:

[0163] If a data processing flow tracking link query request is received for the privacy computing request, the target data processing flow identified as the exclusive identifier is filtered out from each data processing flow according to the identifier corresponding to each data processing flow, and a data processing flow tracking link constructed by at least one of the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transmission layer related to each target data processing flow is generated and displayed.

[0164] Embodiment 4:

[0165] Based on the same technical concept, the present application provides a privacy computing method, which is applied to a second privacy computing device, see Figure 8 , Figure 8 A schematic diagram of another privacy computing process provided by some embodiments is shown, the method comprising:

[0166] S801: Receive an authorization request sent by the first privacy computing device that performs management-plane intercommunication and collaborative privacy computing tasks with the second privacy computing device, wherein the authorization request carries the privacy computing resource entity information of the target data plane involved by the first privacy computing device; generate a permission credential between the privacy computing resource entity information of any data plane in the second privacy computing device and the privacy computing resource entity information of the target data plane in the first privacy computing device, and send the permission credential to the first privacy computing device.

[0167] S802: Send a privacy computing request to a first privacy computing device, wherein the privacy computing request carries a target permission credential; enable the first privacy computing device to identify a first data plane in the first privacy computing device indicated by the target permission credential, and enable the first privacy computing device to perform corresponding privacy computing based on a privacy algorithm product in the first data plane and send the calculation result to the second privacy computing device.

[0168] In a possible implementation, the method further includes:

[0169] If the calculation result sent by the first privacy computing device and the correspondence between the session and the target permission credential are received, the second data plane in the second privacy computing device indicated by the target permission credential is identified, and the calculation result is sent to the second data plane.

[0170] Embodiment 5:

[0171] Based on the same technical concept, this application provides a privacy computing device, see Fig. 9 , Fig. 9 A schematic diagram of a privacy-preserving computing device provided by some embodiments is shown, and the privacy-preserving computing device includes:

[0172] The receiving module 901 is used to receive a privacy computing request sent by any second privacy computing device, wherein the privacy computing request carries a target permission credential;

[0173] An identification module 902, configured to identify a first data plane in a first privacy computing device indicated by the target permission credential;

[0174] The calculation module 903 is used to perform corresponding privacy calculation based on the privacy algorithm product in the first data plane, and send the calculation result to the second privacy computing device.

[0175] In a possible implementation, the device further includes:

[0176] A creation module 904, configured to create a session corresponding to the target license credential;

[0177] The first sending module 905 is used to send the calculation result and the corresponding relationship between the session and the target permission credential to the second privacy computing device based on the session.

[0178] In a possible implementation, the first sending module 905 is further configured to send an authorization request to a second privacy computing device that performs management-plane intercommunication and collaborative privacy computing tasks with the first privacy computing device, wherein the authorization request carries the privacy computing resource entity information of the target data plane involved by the first privacy computing device; so that the second privacy computing device receives the authorization request and generates a permission credential between the privacy computing resource entity information of any data plane in the second privacy computing device and the privacy computing resource entity information of the target data plane in the first privacy computing device, and the second privacy computing device sends the permission credential to the first privacy computing device;

[0179] The receiving module 906 is further configured to receive and save the permission certificate.

[0180] In a possible implementation, the receiving module 906 is specifically configured to receive the privacy computing request based on a management layer in a management plane of the first privacy computing device;

[0181] The computing module 903 is specifically used to send a privacy computing task for the privacy computing request to the scheduling layer in the first data plane based on the management layer, and determine the scenario algorithm layer and security algorithm layer where the privacy algorithm product involved in the privacy computing task is located when the scheduling layer receives the privacy computing task, and perform corresponding privacy computing based on the privacy algorithm product by calling the scenario algorithm layer and the security algorithm layer.

[0182] In a possible implementation, the first sending module 905 is specifically configured to send the calculation result and the correspondence between the session and the target license credential to the second privacy computing device based on the transport layer in the first data plane and based on the session.

[0183] In a possible implementation, the device further includes:

[0184] The tracking module 907 is used to configure the same exclusive identifier for each target data processing flow generated by the privacy computing request between the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transport layer based on the service grid layer in the first privacy computing device, and the exclusive identifier is used to characterize the privacy computing request.

[0185] In one possible implementation, the tracking module 907 is also used to, if a data processing flow tracking link query request is received for the privacy computing request, filter out the target data processing flow identified as the exclusive identifier from each data processing flow according to the identifier corresponding to each data processing flow, and generate and display a data processing flow tracking link constructed by at least one of the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transport layer related to each target data processing flow.

[0186] Embodiment 6:

[0187] Based on the same technical concept, this application provides a privacy computing device, see Fig.10 , Fig.10 A schematic diagram of another privacy-preserving computing device provided by some embodiments is shown, and the privacy-preserving computing device includes:

[0188] The second sending module 1001 is used to send a privacy computing request to the first privacy computing device, wherein the privacy computing request carries a target permission credential; so that the first privacy computing device identifies the first data plane in the first privacy computing device indicated by the target permission credential, and enables the first privacy computing device to perform corresponding privacy computing based on the privacy algorithm product in the first data plane and send the calculation result to the second privacy computing device.

[0189] In a possible implementation, the second sending module 1001 is further configured to, upon receiving the calculation result sent by the first privacy computing device and the correspondence between the session and the target license credential, identify the second data plane in the second privacy computing device indicated by the target license credential, and send the calculation result to the second data plane.

[0190] In a possible implementation, the device further includes:

[0191] The licensing module 1002 is used to receive an authorization request sent by the first privacy computing device that performs management-plane intercommunication and collaborative privacy computing tasks with the second privacy computing device, wherein the authorization request carries the privacy computing resource entity information of the target data plane involved by the first privacy computing device; generate a licensing certificate between the privacy computing resource entity information of any data plane in the second privacy computing device and the privacy computing resource entity information of the target data plane in the first privacy computing device, and send the licensing certificate to the first privacy computing device.

[0192] Embodiment 7:

[0193] Based on the same technical concept, the present application also provides an electronic device, Fig.11 A schematic diagram of the structure of an electronic device provided by some embodiments is shown. Fig.11 As shown, it includes: a processor 1101, a communication interface 1102, a memory 1103 and a communication bus 1104, wherein the processor 1101, the communication interface 1102, and the memory 1103 communicate with each other through the communication bus 1104;

[0194] The memory 1103 stores a computer program. When the program is executed by the processor 1101, the processor 1101 executes the steps of the method in any of the above embodiments, and the repeated parts are not repeated here.

[0195] The communication bus mentioned in the above communication device (electronic device) can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0196] The communication interface 1102 is used for communication between the above communication device (electronic device) and other devices.

[0197] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0198] The above-mentioned processor can be a general-purpose processor, including a central processing unit, a network processor (Network Processor, NP), etc.; it can also be a digital signal processing processor (Digital Signal Processing, DSP), an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc.

[0199] Based on the same inventive concept, the embodiment of the present application provides a computer-readable storage medium, and the computer program product includes: computer program code, when the computer program code is run on a computer, the computer executes any of the methods discussed above. Since the principle of solving the problem by the above-mentioned computer-readable storage medium is similar to that of the privacy computing method, the implementation of the above-mentioned computer-readable storage medium can refer to the implementation of the method, and the repeated parts will not be repeated.

[0200] The above-mentioned computer-readable storage medium can be any available medium or data storage device that can be accessed by the processor in the electronic device, including but not limited to magnetic storage such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc., optical storage such as CD, DVD, BD, HVD, etc., and semiconductor storage such as ROM, EPROM, EEPROM, non-volatile memory (NANDFLASH), solid-state drive (SSD), etc.

[0201] Based on the same inventive concept, the embodiment of the present application also provides a computer program product, which includes: computer program code, when the computer program code is run on a computer, the computer executes any of the methods discussed above. Since the principle of solving the problem by the above computer program product is similar to that of the privacy computing method, the implementation of the above computer program product can refer to the implementation of the method, and the repeated parts will not be repeated.

[0202] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0203] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0204] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0205] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0206] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A privacy computing system, characterized in that: The system includes: a first privacy computing device and at least one second privacy computing device; Any second privacy-preserving computing device, used to send a privacy-preserving computing request to the first privacy-preserving computing device, wherein the privacy-preserving computing request carries a target permission credential; The first privacy computing device is used to receive the privacy computing request, identify the first data plane in the first privacy computing device indicated by the target license credential, perform corresponding privacy computing based on the privacy algorithm product in the first data plane, and send the calculation result to the second privacy computing device.

2. The system according to claim 1, characterized in that The first privacy computing device is further used for: creating a session corresponding to the target license credential; Based on the session, the calculation result and the correspondence between the session and the target permission credential are sent to the second privacy computing device, so that the second privacy computing device identifies the second data plane in the second privacy computing device indicated by the target permission credential and sends the calculation result to the second data plane.

3. The system according to claim 2, characterized in that The first privacy computing device is further used for: Sending an authorization request to a second privacy computing device that performs management-plane intercommunication and collaborative privacy computing tasks with the first privacy computing device, wherein the authorization request carries the privacy computing resource entity information of the target data plane involved by the first privacy computing device; The second privacy-preserving computing device is configured to receive the authorization request, generate a permission credential between the privacy-preserving computing resource entity information of any data plane in the second privacy-preserving computing device and the privacy-preserving computing resource entity information of the target data plane in the first privacy-preserving computing device, and send the permission credential to the first privacy-preserving computing device; The first privacy computing device is used to receive and save the permission credential.

4. The system according to claim 2, characterized in that The first privacy computing device is specifically used for: The management layer in the management plane of the first privacy computing device receives the privacy computing request; The management layer sends a privacy computing task for the privacy computing request to the scheduling layer in the first data plane. When receiving the privacy computing task, the scheduling layer determines the scenario algorithm layer and security algorithm layer where the privacy algorithm product involved in the privacy computing task is located, and calls the scenario algorithm layer and security algorithm layer to perform corresponding privacy computing based on the privacy algorithm product.

5. The system according to claim 4, characterized in that The first privacy computing device is specifically used for: The transport layer in the first data plane sends the calculation result and the correspondence between the session and the target permission credential to the second privacy computing device based on the session.

6. The system according to claim 5, characterized in that The first privacy computing device is further used for: Based on the service grid layer in the first privacy computing device, the same exclusive identifier is configured for each target data processing flow generated by the privacy computing request between the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transport layer, and the exclusive identifier is used to characterize the privacy computing request.

7. The system according to claim 6, characterized in that The first privacy computing device is further used for: If a data processing flow tracking link query request is received for the privacy computing request, the target data processing flow identified as the exclusive identifier is filtered out from each data processing flow according to the identifier corresponding to each data processing flow, and a data processing flow tracking link constructed by at least one of the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transmission layer related to each target data processing flow is generated and displayed.

8. A privacy computing method, characterized in that: The method is applied to a first privacy computing device, and the method includes: Receiving a privacy computing request sent by any second privacy computing device, wherein the privacy computing request carries a target permission credential; Identify a first data plane in a first privacy computing device indicated by the target license credential, perform corresponding privacy computing based on a privacy algorithm product in the first data plane, and send the computing result to the second privacy computing device.

9. The method according to claim 8, characterized in that After receiving the privacy computing request sent by any second privacy computing device and before sending the computing result to the second privacy computing device, the method further includes: creating a session corresponding to the target license credential; The sending the calculation result to the second privacy computing device comprises: Based on the session, the calculation result and the correspondence between the session and the target permission credential are sent to the second privacy computing device.

10. The method according to claim 9, characterized in that Before receiving the privacy computing request sent by any second privacy computing device, the method further includes: Sending an authorization request to a second privacy computing device that performs management-plane intercommunication and collaborative privacy computing tasks with the first privacy computing device, wherein the authorization request carries the privacy computing resource entity information of the target data plane involved by the first privacy computing device; allowing the second privacy computing device to receive the authorization request and generate a permission credential between the privacy computing resource entity information of any data plane in the second privacy computing device and the privacy computing resource entity information of the target data plane in the first privacy computing device, and allowing the second privacy computing device to send the permission credential to the first privacy computing device; The permission credential is received and stored.

11. The method according to claim 9, characterized in that The receiving a privacy computing request sent by any second privacy computing device includes: The management layer in the management plane of the first privacy computing device receives the privacy computing request; The performing corresponding privacy calculation based on the privacy algorithm product in the first data plane includes: The management layer sends a privacy computing task for the privacy computing request to the scheduling layer in the first data plane. When receiving the privacy computing task, the scheduling layer determines the scenario algorithm layer and security algorithm layer where the privacy algorithm product involved in the privacy computing task is located, and calls the scenario algorithm layer and security algorithm layer to perform corresponding privacy computing based on the privacy algorithm product.

12. The method according to claim 11, characterized in that The sending the calculation result to the second data plane in the second privacy computing device based on the session includes: The transport layer in the first data plane sends the calculation result and the correspondence between the session and the target permission credential to the second privacy computing device based on the session.

13. The method according to claim 12, characterized in that The method further comprises: Based on the service grid layer in the first privacy computing device, the same exclusive identifier is configured for each target data processing flow generated by the privacy computing request between the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transport layer, and the exclusive identifier is used to characterize the privacy computing request.

14. The method according to claim 13, characterized in that The method further comprises: If a data processing flow tracking link query request is received for the privacy computing request, the target data processing flow identified as the exclusive identifier is filtered out from each data processing flow according to the identifier corresponding to each data processing flow, and a data processing flow tracking link constructed by at least one of the management layer, scheduling layer, scenario algorithm layer, security algorithm layer and transmission layer related to each target data processing flow is generated and displayed.

15. A privacy computing method, characterized in that: The method is applied to a second privacy computing device, and the method includes: A privacy computing request is sent to a first privacy computing device, wherein the privacy computing request carries a target permission credential; the first privacy computing device identifies a first data plane in the first privacy computing device indicated by the target permission credential, and the first privacy computing device performs corresponding privacy computing based on a privacy algorithm product in the first data plane and sends the calculation result to the second privacy computing device.

16. The method according to claim 15, characterized in that The method further comprises: If the calculation result sent by the first privacy computing device and the correspondence between the session and the target permission credential are received, the second data plane in the second privacy computing device indicated by the target permission credential is identified, and the calculation result is sent to the second data plane.

17. The method according to claim 15 or 16, characterized in that The method further comprises: Receiving an authorization request sent by the first privacy computing device that performs a management plane intercommunication and collaborative privacy computing task with the second privacy computing device, wherein the authorization request carries privacy computing resource entity information of a target data plane involved by the first privacy computing device; Generate a permission credential between the privacy computing resource entity information of any data plane in the second privacy computing device and the privacy computing resource entity information of the target data plane in the first privacy computing device, and send the permission credential to the first privacy computing device.

18. A privacy computing device, characterized in that: The method comprises a unit or a module for executing the method according to any one of claims 8 to 14, or comprises a unit or a module for executing the method according to any one of claims 15 to 17.

19. An electronic device, characterized in that: It includes a processor and a memory, wherein the memory stores program code, and when the program code is executed by the processor, the processor executes the steps of the method as described in any one of claims 8 to 14, or executes the steps of the method as described in any one of claims 15 to 17.

20. A computer-readable storage medium, characterized in that: It includes program code. When the storage medium runs on an electronic device, the program code is used to enable the electronic device to execute the steps of the method as described in any one of claims 8 to 14, or to execute the steps of the method as described in any one of claims 15 to 17.

Images