A heterogeneous platform node interaction method, system and storage medium

Abstract

The present application provides a heterogeneous platform node interaction method, system and storage medium, the method comprising: an alliance management server receives an access request initiated by a platform node; the alliance management server verifies the authentication certificate provided by the platform node, and if the authentication certificate is qualified, returns a response message to the platform node allowing entry into the alliance; the alliance management server receives a publishing request sent by the platform node, and the publishing request carries the platform node information of the platform node; the alliance management server adds the platform node to the alliance platform node list, and adds publicly available information in the platform node information to the alliance platform node list, so that the platform nodes can interact with each other through the alliance platform node list. The alliance manages the standardized platform node interconnection process to enable heterogeneous platform nodes to interact and work together; and by setting an authentication mechanism, the security and reliability of platform node interaction in the alliance is guaranteed.

Description

Technical Field

[0001] The present application relates to the field of platform interaction, and more specifically, to a heterogeneous platform node interaction method, system and storage medium. Background Art

[0002] With the acceleration of enterprise digital transformation and deepening of industry integration, the demand for cross-domain data security integration is becoming increasingly strong. Privacy computing platforms are based on privacy computing technology and provide complete and rigorous technical products for implementing privacy computing tasks. With the continuous expansion of the privacy computing market and the entry of many manufacturers in various fields, various manufacturers have launched different privacy computing platforms. However, it is difficult to achieve communication between multiple different privacy computing platforms. Summary of the invention

[0003] The purpose of the embodiments of the present invention is to provide a heterogeneous platform node interaction method, system and storage medium, which can achieve identification, connection and communication between platform nodes with the same definition through unified management of heterogeneous platform nodes; enable interaction and collaborative work between heterogeneous platform nodes through standardized platform node interconnection and intercommunication processes; and ensure the security and reliability of platform node interaction in the alliance through the authentication mechanism set by the alliance management server.

[0004] In a first aspect, an embodiment of the present application provides a heterogeneous platform node interaction method, including: an alliance management server receives an access request initiated by a platform node; the alliance management server verifies the authentication certificate provided by the platform node, and if the authentication certificate is qualified, returns a response message to the platform node allowing entry into the alliance; the alliance management server receives a publishing request sent by the platform node, and the publishing request carries the platform node information of the platform node; the alliance management server adds the platform node to the alliance platform node list, and adds publicly available information in the platform node information to the alliance platform node list, so that platform nodes can interact with each other through the alliance platform node list.

[0005] In the above implementation process, the platform nodes enter the alliance through the authentication mechanism set by the alliance to ensure the security and reliability of the interaction of platform nodes in the alliance, and the node release mechanism makes the platform nodes joining the alliance visible to each other, facilitating collaboration between platform nodes.

[0006] Optionally, in an embodiment of the present application, the platform node receives an authentication request sent by another platform node in the alliance platform node list; if the platform node agrees to the authentication, the other platform node is added to its own cooperation platform node list, wherein the platform node in the cooperation platform node list has the authority to apply to join the platform node's collaborative computing project.

[0007] In the above implementation process, the platform nodes establish a connection relationship through authentication, and the platform nodes that establish the connection relationship write their own cooperation platform node list to facilitate the selection of partners from the cooperation platform node list at a later time.

[0008] Optionally, in the embodiment of the present application, if the platform node agrees to the authentication, the other platform node also adds the platform node to its cooperative platform node list. In this solution, two-way authentication between platform nodes can be completed by requesting authentication once, thereby improving the authentication efficiency.

[0009] Optionally, in an embodiment of the present application, the platform node receives a cooperation request to join a collaborative computing project initiated by a cooperative platform node in its own cooperative platform node list; if the platform node agrees to the cooperation request, it authorizes its own computing resources for the collaborative computing project to the cooperative platform node. In the above implementation process, the platform node receives a cooperation request to join a collaborative computing project initiated by itself from a cooperative platform node in its own cooperative platform node list, agrees to the request and authorizes it, and can join the collaborative computing project together with the cooperative platform node, authorizing the other party to use computing resources for the collaborative computing project, thereby achieving platform node connectivity, resource sharing, and task collaboration between platform nodes.

[0010] Optionally, in an embodiment of the present application, if the platform node cancels the authorization to the cooperative platform node, the cooperative platform node's permission to obtain computing resources is canceled. In the above implementation process, the platform node is authorized to enter the collaborative computing project, and the authorization status is not permanent. The platform node cancels the authorization to the cooperative platform node and cancels the cooperative platform node's permission to obtain computing resources, thereby realizing flexible control of collaborative computing permissions according to actual needs.

[0011] Optionally, in an embodiment of the present application, if the platform node information of the platform node changes, the changed platform node information is synchronized to the alliance management server and the cooperative platform node. In the above implementation process, the platform node information includes the attribute information of the platform node, the platform node authentication, connection establishment and authorization status information, etc. If the platform node information changes, the changed platform node information is synchronized to the alliance management server and the cooperative platform node, so that the alliance management server and other platform nodes can obtain the latest platform node information, which is convenient for managing the platform nodes within the alliance and for platform nodes to interact based on the platform node information.

[0012] Optionally, in an embodiment of the present application, the interactive behavior of the platform node within the alliance is recorded and stored. In the above implementation process, the data and behavior of the platform node during the interaction process within the alliance are recorded to meet the needs of internal and external regulatory audits and task responsibility attribution tracing.

[0013] Optionally, in an embodiment of the present application, the platform node information includes a canonical field. In the above implementation process, the canonical field can be a standardized attribute field, and the attribute field defines various types of information of the platform node. Through the platform nodes with the same definition, identification, connection and communication between platform nodes are achieved.

[0014] In a second aspect, the embodiment of the present application further provides a heterogeneous platform node interaction system, including:

[0015] A platform node interaction management module is used to receive an access request initiated by a platform node, verify the authentication certificate provided by the platform node, and return a response message to the platform node to allow entry into the alliance if the authentication certificate is qualified; and to receive a publishing request sent by the platform node, the publishing request carrying the platform node information of the platform node; add the platform node to the alliance platform node list, and add publicly available information in the platform node information to the alliance platform node list, so that platform nodes can interact with each other through the alliance platform node list;

[0016] A platform node information management module, used to manage the platform node information of the platform nodes in the alliance platform node list;

[0017] A platform node authority management module, used to set resource access rights, resource control rights, action rights, and operation rights of platform nodes in the alliance;

[0018] The platform node role management module is used to manage the project role of the platform node in the collaborative computing project.

[0019] Optionally, in an embodiment of the present application, the platform node interaction management module is also used to assist platform nodes in establishing connections through mutual authentication, and to assist connected platform nodes in authorizing each other to carry out the same collaborative computing project.

[0020] In a third aspect, an embodiment of the present application further provides an electronic device, comprising: a processor and a memory, wherein the memory stores machine-readable instructions executable by the processor, and when the machine-readable instructions are executed by the processor, the method described above is performed.

[0021] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the method described above is executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0023] Figure 1 A model of a platform node provided in an embodiment of the present application;

[0024] Figure 2 A schematic diagram of a heterogeneous platform node interaction system provided in an embodiment of the present application;

[0025] Figure 3 A schematic diagram of a flow chart of a heterogeneous platform node interaction method provided in an embodiment of the present application;

[0026] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] The following embodiments of the technical solution of the present application are described in detail in conjunction with the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present application, and are therefore only used as examples, and cannot be used to limit the scope of protection of the present application.

[0028] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by technicians in the technical field to which this application belongs; the terms used herein are only for the purpose of describing specific embodiments and are not intended to limit this application.

[0029] In the description of the embodiments of the present application, the technical terms "first", "second", etc. are only used to distinguish different objects, and cannot be understood as indicating or implying relative importance or implicitly indicating the number, specific order or primary and secondary relationship of the indicated technical features. In the description of the embodiments of the present application, the meaning of "multiple" is more than two, unless otherwise clearly and specifically defined.

[0030] Before describing the heterogeneous platform node interaction method, system and storage medium provided by the present application, a brief description of the platform node is first given. Figure 1 A model of a platform node provided by an embodiment of the present application is shown.

[0031] Platform nodes refer to the deployment instances of various computing technology platforms. They are the basic components of the alliance and provide external interactive interfaces. A platform node can have multiple collaborative computing projects, and each collaborative computing project has computing resources for that collaborative computing project. Platform nodes can create collaborative computing projects and join collaborative computing projects of other platform nodes. Each platform node has its own computing resources and can also access the computing resources of other platform nodes through authorization. Computing resources can include data resources, model resources, and algorithm component resources.

[0032] In each collaborative computing project of the platform node, multiple collaborative computing algorithm processes can be created. Each collaborative computing algorithm process is formed by the component resources being deployed locally, becoming executable trusted components, and then being organized and arranged in the order of input and output. The types of input and output of each component include data resources and model resources.

[0033] It should be understood that the alliance in this application may be a privacy computing alliance or a computing alliance in other scenarios.

[0034] Privacy computing refers to a collection of technologies that implement data analysis and computing while protecting the data itself from external leakage, thereby achieving the goal of making data "available but invisible"; while fully protecting data and privacy security, it realizes the transformation and release of data value.

[0035] The Privacy Computing Alliance has unified the conceptual model of heterogeneous platform nodes, designed standard functional modules and standard interconnection processes for platform nodes, and solved the problem of incompatibility and inability to communicate between privacy computing platforms due to differences in manufacturers, developers, versions, and audit iterations in architecture, algorithms, and communications. This allows heterogeneous privacy computing platforms to be interconnected, share resources, and collaborate to complete privacy computing tasks.

[0036] The following describes a heterogeneous platform node interaction system provided in an embodiment of the present application. The interaction system is used to manage platform nodes within an alliance and provide support for interaction between platform nodes. Figure 2 , the heterogeneous platform node interaction system 100 includes:

[0037] The platform node interaction management module 110 is responsible for the admission of platform nodes and adding node information of the entered platform nodes to the alliance platform node list, so that the platform nodes can interact with each other through the alliance platform node list.

[0038] A platform node information management module 120, used to manage the platform node information of the platform nodes in the alliance platform node list;

[0039] The platform node authority management module 130 is used to set the resource access authority, resource control authority, action authority and operation authority of the platform node in the alliance;

[0040] The platform node role management module 140 is used to manage the project role of the platform node in the collaborative computing project.

[0041] Among them, the platform node interaction management module 110 can be specifically used to: receive an access request initiated by a platform node, verify the authentication certificate provided by the platform node, and if the authentication certificate is qualified, return a response message to the platform node allowing entry into the alliance; and receive a publishing request sent by the platform node, the publishing request carrying the platform node information of the platform node; add the platform node to the alliance platform node list, and add the publicly available information in the platform node information to the alliance platform node list.

[0042] The platform node information management module 120 is specifically used to manage the addition, deletion, modification, and query of platform node information of platform nodes in the alliance platform node list, and the platform node information management module is also used to register, deregister, change, and configure platform nodes in the management alliance management server.

[0043] The platform node permission management module 130 is specifically used to manage the platform node's permissions to open, read, modify and copy local or external resources; control permissions to use, disable, view and block local resources; action permissions for visible objects in the system window; and operation permissions for platform nodes that join the collaborative computing project when processing the collaborative computing project.

[0044] The platform node role management module 140 is specifically used for role management of platform nodes in collaborative computing projects. Role management includes: adding role groups, adding roles, editing role groups, editing roles, deleting role groups, deleting roles, and role authorization.

[0045] In some optional embodiments, the platform node interaction management module 110 is also used to assist platform nodes in establishing connections through mutual authentication, and to assist connected platform nodes in authorizing each other to carry out the same collaborative computing project.

[0046] The following describes the specific interaction process between platform nodes. Figure 3 ,Heterogeneous platform node interaction methods include:

[0047] Step S210: the alliance management server receives an access request initiated by the platform node.

[0048] The implementation method of the above step S210 includes: before the platform node enters the platform node alliance, it performs alliance-approved platform node authentication and initiates an access request to the alliance management server. Specifically, the platform node authentication can use a certificate issued by a third-party CA organization to authenticate the platform node. After receiving the access request initiated by the platform node, the alliance management server performs subsequent verification operations.

[0049] After step S210, step S220 is executed: the alliance management server verifies the authentication certificate provided by the platform node, and if the authentication certificate is qualified, a response message of allowing entry into the alliance is returned to the platform node.

[0050] The implementation method of the above step S220 includes: the alliance management server verifies the authentication certificate provided by the platform node, and determines the identity validity and legality of the platform node through the certificate. If the authentication certificate is qualified, a response message allowing entry into the alliance is returned to the platform node, that is, the platform node authentication is successful, and the platform node enters the alliance.

[0051] After step S220, step S230 is executed: the alliance management server receives a publishing request sent by the platform node, and the publishing request carries the platform node information of the platform node.

[0052] The implementation method of the above step S230 includes: the platform node entering the alliance sends a publishing request to the alliance management server, the publishing request carries the platform node information of the platform node, and the alliance management server receives the publishing request sent by the platform node and obtains the platform node information of the platform node.

[0053] After step S230, step S240 is executed: the alliance management server adds the platform node to the alliance platform node list, and adds publicly available information in the platform node information to the alliance platform node list, so that the platform nodes can interact with each other through the alliance platform node list.

[0054] The implementation method of the above step S240 includes: after the alliance management server receives the publishing request sent by the platform node, it adds the platform node to the alliance platform node list, and adds the publicly available information in the platform node information to the alliance platform node list. The platform node entering the alliance can query and retrieve the publicly available information of other platform nodes through the alliance platform node list. It should be noted that the platform node information of the platform node for which the alliance management server has not received the publishing request will not be added to the alliance platform node list, and the platform node information of the platform node will not be discovered by other platform nodes in the alliance.

[0055] In the above implementation process, the alliance management server receives the access request initiated by the platform node, allows the platform node to enter the alliance according to the authentication certificate of the platform node, and adds the platform node to the alliance platform node list according to the release request received from the platform node in the alliance, and adds the publicly available information of the platform node to the alliance platform node list, so that the platform node can obtain the information of other platform nodes for interaction. The platform node enters the alliance through the authentication mechanism set by the alliance, ensuring the security and reliability of the interaction of heterogeneous platform nodes in the alliance.

[0056] Optionally, in an embodiment of the present application, the platform node receives an authentication request sent by another platform node in the alliance platform node list; if the platform node agrees to the authentication, the other platform node is added to its own cooperation platform node list, wherein the platform node in the cooperation platform node list has the authority to apply to join the platform node's collaborative computing project.

[0057] The implementation method of the above steps is, for example: the platform node receives an authentication request sent by another platform node in the alliance platform node list, and the information in the alliance platform node list checks the platform node information of the platform node that sent the authentication request. If there is a willingness to cooperate, the platform node agrees to the authentication and adds the platform node that sent the authentication request to its own cooperative platform node list. The platform nodes in the cooperative platform node list have the right to apply to join the collaborative computing project of the platform node, that is, the platform node agrees to authenticate other platform nodes that have joined its own cooperative platform node list, and has the right to apply to join the collaborative computing project of the platform node for collaborative cooperation.

[0058] In the above implementation process, the platform node can choose to initiate an authentication request through the platform node information in the alliance platform node list; the platform node platform receives the authentication requests sent by the alliance platform node list and other platform nodes, and adds them to its own cooperative platform node list after agreeing to the authentication. The connection relationship is established between the platform nodes through authentication, and the platform nodes that have established the connection relationship are written into their own cooperative platform node list.

[0059] Optionally, in the embodiment of the present application, if the platform node agrees to the authentication, the other platform node also adds the platform node to its cooperative platform node list. The implementation method of the above steps is, for example: the platform nodes are in a two-way authentication process. If the platform nodes pass the two-way authentication, it means that a connection relationship is established, and the other platform node is written into its own cooperative platform node list.

[0060] Optionally, in an embodiment of the present application, the platform node receives a cooperation request to join a collaborative computing project initiated by a cooperative platform node in its own cooperative platform node list; if the platform node agrees to the cooperation request, it authorizes its own computing resources for the collaborative computing project to the cooperative platform node.

[0061] An example of an implementation method of the above steps is as follows: the platform nodes in the cooperative platform node list have the authority to apply to join the collaborative computing project of the platform nodes. The platform nodes receive the cooperation request initiated by the cooperative platform nodes to join the collaborative computing project, and choose whether to agree to the cooperation request based on the collaborative computing project in the cooperation request. If the platform node agrees to the cooperation request, it is authorized to join the collaborative computing project and authorizes the cooperative platform nodes to use their own computing resources for the collaborative computing project.

[0062] Specifically, the platform nodes that are authorized to join the collaborative computing project participate in the same computing process, and authorize computing resources such as data, models, and algorithm components to participate in the computing process. Multiple authorized platform nodes collaborate to complete collaborative computing tasks by mutually negotiating basic information about algorithms and models, data input and output specification definitions, algorithm arrangement order, and other computing-related content.

[0063] In the above implementation process, the platform node receives the cooperative platform nodes in its own cooperative platform node list, and after agreeing to and authorizing the cooperation request to join the collaborative computing project initiated by itself, it can join the collaborative computing project together with the cooperative platform nodes and authorize the other party to use the computing resources for the collaborative computing project, thereby realizing platform node connectivity, resource sharing and task collaboration between platform nodes.

[0064] Optionally, in an embodiment of the present application, if the platform node cancels the authorization to the cooperation platform node, the permission of the cooperation platform node to obtain computing resources is canceled.

[0065] An example of an implementation method of the above steps is: the platform node is authorized to enter the collaborative computing project. The authorization status is not permanent. The platform node can cancel the authorization to the cooperative platform node according to actual needs, and then cancel the cooperative platform node's authority to obtain computing resources, thereby realizing flexible control of collaborative computing permissions according to actual needs.

[0066] Optionally, in an embodiment of the present application, if the platform node information of the platform node changes, the changed platform node information is synchronized to the alliance management server and the cooperation platform node.

[0067] An example of an implementation method of the above steps is as follows: the platform node information includes the attribute information of the platform node, the platform node authentication, connection establishment and authorization status information, etc. If the platform node information changes, the changed platform node information will be synchronized to the alliance management server and the cooperative platform node. Specifically, after the platform node information or platform node status changes, the cooperative platform node will be notified in real time, the cooperative platform node list will be updated, and the platform node alliance list of the alliance management server will be synchronously updated.

[0068] In the above implementation process, the changed platform node information is synchronized to the alliance management server and the cooperative platform node, so that the alliance management server and other platform nodes can obtain the latest platform node information, which is convenient for managing the platform nodes within the alliance and facilitating the interaction between platform nodes based on the platform node information.

[0069] Optionally, in an embodiment of the present application, the interactive behaviors of the platform nodes within the alliance are recorded and stored.

[0070] The implementation methods of the above steps are, for example: recording the data and behaviors of the platform nodes during the interaction process within the alliance to meet the needs of internal and external regulatory audits and task responsibility traceability. Among them, the recording process can be executed by the alliance management server to record and store information such as data and behaviors of multiple platform nodes during the interaction process in the alliance; it can also be implemented through blockchain technology, that is, each platform node records the data and behaviors during the interaction process to form a distributed shared ledger and database; it can also be recorded by the trusted execution environment TEE within each platform node, and the TEE environment ensures that the data is not tampered with. The content of the evidence should be tamper-proof and support customization based on the specific needs of the regulator and the business. The content of the evidence should be destroyed within the period agreed upon by the participants, and the agreed storage period should comply with the requirements of laws and regulations.

[0071] Optionally, in an embodiment of the present application, the platform node information includes a canonical field.

[0072] The implementation method of the above steps is as follows: the canonical field can be a standardized attribute field, and the attribute field defines various information of the platform node. Specifically, for example, the platform node information includes the platform node identification, platform node name, affiliated organization, external management service address, external privacy computing service address, internal management and operation service address, internal component service address, platform node public key, platform node status and platform node description. Among them, the platform node identifier is the platform node identity number that is unique and cannot be tampered with in the global alliance. The reference format can be: "N" + 10-digit timestamp + 6-digit random number to ensure uniqueness in the entire network; the organization to which it belongs is the organization name; the external management service address is the management service address of the platform node, which provides query and management service interfaces. The formal production environment must provide services through https with a digital certificate; the external privacy computing service address is the platform node privacy computing service address, which is only used for the execution of privacy computing tasks. The formal production environment must provide services through https with a digital certificate; the internal management and operation service address and the internal component service address are the service addresses and component service addresses for the internal operations of the platform node, and are not disclosed to the public; the public key is for the platform node to encrypt session keys, verify digital signatures, or encrypt data that can be decrypted with the corresponding private key; the platform node status is the description information of the platform node, including platform node introduction, platform node functions, resource overview, technology selection statement and other information.

[0073] It should be noted that the platform node status is the current status of the platform node, and the platform node status may include ready status, online status, offline status, abnormal status, and destroyed status.

[0074] Among them, the ready state: the platform node starts and completes the preparation of related computing resources; the online state: the platform node enters the collaborative computing project after passing the authentication, and can cooperate with other platform nodes online to complete the collaborative computing tasks; the online state is subdivided with the execution process of the collaborative computing tasks: when the platform node joins the network but does not join any collaborative computing tasks, it is in the online waiting state; when the platform node receives a collaborative computing task, it is in the online working state; when the platform node suspends the collaborative computing task, it is in the online suspended state. Offline state: the platform node enters the collaborative computing project after passing the authentication, and cannot complete the collaborative computing tasks with other platform nodes offline; abnormal state: the platform node encounters an abnormal situation, automatically restarts or requires the corresponding maintenance personnel to analyze the problem and restart. Destroyed state: the platform node exits the alliance network and logs out.

[0075] In the above implementation process, through the platform nodes with the same definition, platform nodes from different manufacturers, developers or versions can recognize, connect, communicate and perform collaborative computing with each other.

[0076] In a preferred embodiment, before a platform node enters the alliance network, it should be authenticated using a certificate issued by a third-party CA organization. The alliance composed of multiple platform nodes uses certificates to determine the validity and legitimacy of each other's identities. Only after the platform node is authenticated will the platform node be allowed to join the alliance and perform other operations. After the platform node is successfully authenticated, a platform node release request is submitted to the alliance, and then the platform node's publicly available information appears on the alliance platform node list, which can be retrieved and queried by other platform nodes. Platform nodes that have not been published cannot be discovered by other platform nodes in the alliance network.

[0077] The platform node retrieves and views the platform node information published by other platform nodes. If there is a willingness to cooperate, it can initiate a collaborative computing project request later. The platform nodes pass two-way authentication with each other. After successful authentication, a connection relationship is established and the nodes enter the other party's list of cooperative platform nodes. The connected platform nodes are authorized to join the same collaborative computing project, participate in the same collaborative computing process, and authorize computing resources such as data, models, and algorithm components to participate in the computing process. Only authorized platform nodes can send collaborative computing project requests to each other. The authorization status is non-permanent. After authorization, both platform nodes can cancel the authorization at any time. Multiple authorized platform nodes jointly complete collaborative computing tasks by negotiating basic information of algorithms and models, data input and output specification definitions, algorithm arrangement order and other computing-related content.

[0078] During the interaction of platform nodes, if the platform node information of the platform node changes, the changed platform node information will be synchronously updated to the alliance platform node list and the cooperation platform node list. The interaction behavior of the platform node within the alliance will be recorded and preserved.

[0079] See also Figure 4 The electronic device 300 provided in the embodiment of the present application includes: a processor 310 and a memory 320, wherein the memory 320 stores machine-readable instructions executable by the processor 310, and when the machine-readable instructions are executed by the processor 310, the above method is executed.

[0080] An embodiment of the present application further provides a storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the above method is executed.

[0081] Among them, the storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable red-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, disk or optical disk.

[0082] In several embodiments provided by the embodiments of the present application, it should be understood that the disclosed system and method can also be implemented in other ways. The system embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the systems, methods and computer program products according to the multiple embodiments of the embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and a part of the module, program segment or code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0083] In addition, the functional modules in each embodiment of the present application can be integrated together to form an independent part, or each module can exist separately, or two or more modules can be integrated to form an independent part.

[0084] The above description is only an optional implementation manner of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the embodiments of the present application, which should be covered within the protection scope of the embodiments of the present application.

Claims

1. A heterogeneous platform node interaction method, characterized in that: Applied to a privacy-preserving computing network, the privacy-preserving computing network includes a federation management server and a platform node, the privacy-preserving computing network is used to perform privacy-preserving computing, and the heterogeneous platform node interaction method includes: The alliance management server receives the access request initiated by the platform node; The alliance management server verifies the authentication certificate provided by the platform node, and returns a response message to the platform node to allow entry into the alliance if the authentication certificate is qualified; The alliance management server receives a publishing request sent by the platform node, wherein the publishing request carries the platform node information of the platform node, wherein the platform node information includes a platform node identifier, a platform node name, an organization to which it belongs, an external management service address, an external privacy computing service address, an internal management and operation service address, an internal component service address, a platform node public key, a platform node status, and a platform node description; wherein the external management service address is the management service address of the platform node, which provides a query and management service interface, and is publicly available information; the external privacy computing service address is the privacy computing service address of the platform node, and is used for the execution of privacy computing tasks; the internal management and operation service address and the internal component service address are the service address and component service address of the internal operation of the platform node, and are non-public information; The alliance management server adds the platform node to the alliance platform node list, and adds publicly available information in the platform node information to the alliance platform node list, so that the platform nodes can interact with each other through the alliance platform node list; The platform node receives an authentication request sent by another platform node in the alliance platform node list; If the platform node agrees to the authentication, the other platform node is added to its own cooperative platform node list, wherein the platform nodes in the cooperative platform node list have the authority to apply to join the collaborative computing project of the platform node.

2. The method according to claim 1, characterized in that If the platform node agrees to the authentication, the other platform node will also add the platform node to its cooperative platform node list.

3. The method according to claim 2, characterized in that The method further comprises: The platform node receives a cooperation request for joining a collaborative computing project initiated by a cooperation platform node in the cooperation platform node list; If the platform node agrees to the cooperation request, the platform node authorizes its own computing resources for the collaborative computing project to the cooperation platform node.

4. The method according to claim 3, characterized in that The method further comprises: If the platform node cancels the authorization to the cooperation platform node, the permission of the cooperation platform node to obtain the computing resource is canceled.

5. The method according to any one of claims 2 to 4, characterized in that: The method further comprises: If the platform node information of the platform node changes, the changed platform node information is synchronized to the alliance management server and the cooperation platform node.

6. The method according to claim 1, characterized in that The method further comprises: The interactive behaviors of the platform nodes within the alliance are recorded and stored.

7. A heterogeneous platform node interaction system, characterized in that: Applied to a privacy computing network, the privacy computing network includes a federation management server and a platform node, and the privacy computing network is used to perform privacy computing; the heterogeneous platform node interaction system is used to perform the method according to any one of claims 1 to 6, and the heterogeneous platform node interaction system includes: A platform node interaction management module is used to receive an access request initiated by a platform node, verify the authentication certificate provided by the platform node, and return a response message to the platform node to allow entry into the alliance if the authentication certificate is qualified; and to receive a publishing request sent by the platform node, the publishing request carrying the platform node information of the platform node; add the platform node to the alliance platform node list, and add publicly available information in the platform node information to the alliance platform node list, so that platform nodes can interact with each other through the alliance platform node list; A platform node information management module, used to manage the platform node information of the platform nodes in the alliance platform node list; A platform node authority management module, used to set resource access rights, resource control rights, action rights, and operation rights of platform nodes in the alliance; The platform node role management module is used to manage the project role of the platform node in the collaborative computing project.

8. The heterogeneous platform node interaction system according to claim 7, characterized in that: The platform node interaction management module is also used to assist platform nodes in establishing connections through mutual authentication, and to assist connected platform nodes in authorizing each other to carry out the same collaborative computing project.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is executed.

Images