Joint computing state control method and device, electronic equipment and storage medium

Abstract

The application provides a state control method and device for joint calculation, electronic equipment and a storage medium. The method comprises the following steps: according to project information configured by a project initiator for a target project, sending project invitation information to each project participant, and updating the state of the target project to be confirmed. If the project feedback information fed back by each project participant all indicates participation in joint calculation of the target project, the state of the target project is updated to be confirmed. When the state of the target project is confirmed, according to a joint calculation task initiated by a task initiator, task invitation information is sent to each task participant. If the task feedback information fed back by each task participant all indicates participation in the joint calculation task, the state of the joint calculation task is updated to be confirmed. When the state of the joint calculation task is confirmed, the state of the joint calculation task is updated according to the execution progress of the task initiator and the task participant. The present scheme can improve the security of joint calculation.

Description

Technical Field

[0001] This application relates to the field of secure computing technology, and in particular to a state control method, apparatus, electronic device, and storage medium for joint computing. Background Technology

[0002] Joint computing refers to a method of computing and analyzing sensitive data distributed across different platforms without sharing the original data. This method allows different stakeholders to collaborate on data analysis without sharing the actual original data, thereby protecting data privacy and security.

[0003] Currently, to ensure the security of federated computing, a centralized institution or organization is usually responsible for managing and coordinating the computing process.

[0004] However, centralized collaborative computing typically relies on a centralized institution or organization to undertake the tasks of data aggregation, analysis, and computation. If the centralized node fails or is attacked, the data of all participants may be compromised, resulting in low security. Summary of the Invention

[0005] In view of this, embodiments of this application provide a state control method, apparatus, electronic device, and storage medium for joint computing, in order to at least solve some of the above-mentioned problems.

[0006] According to a first aspect of the embodiments of this application, a state control method for collaborative computing is provided. The method includes: sending project invitation information to at least one project participant based on project information configured by a project initiator for a target project, and updating the state of the target project to "pending confirmation," wherein the project invitation information is used to invite the project participants to participate in the collaborative computing of the target project. If the project feedback information provided by the at least one project participant all indicates participation in the collaborative computing of the target project, then the state of the target project is updated to "confirmed." When the state of the target project is confirmed, sending task invitation information to at least one task participant based on a collaborative computing task initiated by a task initiator, and updating the state of the collaborative computing task to "pending confirmation," wherein the task initiator includes any one of the at least one project participant or the project initiator, and the task participant includes any one of the at least one project participant or the project initiator. If the task feedback information provided by the at least one task participant all indicates participation in the collaborative computing task, then the state of the collaborative computing task is updated to "confirmed." When the status of the joint computing task is confirmed, the task initiator and the task participants execute the joint computing task, and update the status of the joint computing task according to the execution progress of the task initiator and the task participants.

[0007] According to a second aspect of the embodiments of this application, a state control device for collaborative computing is provided. The device includes: a project initiation module, configured to send project invitation information to at least one project participant based on project information configured by a project initiator for a target project, and update the state of the target project to "pending confirmation," wherein the project invitation information is used to invite the project participants to participate in the collaborative computing of the target project; a project update module, configured to update the state of the target project to "confirmed" when project feedback information from at least one project participant indicates participation in the collaborative computing of the target project; a task initiation module, configured to send task invitation information to at least one task participant based on a collaborative computing task initiated by a task initiator when the state of the target project is confirmed, and update the state of the collaborative computing task to "pending confirmation," wherein the task initiator includes any one of the at least one project participant or the project initiator, and the task participant includes any one of the at least one project participant or the project initiator; and a task confirmation module, configured to update the state of the collaborative computing task to "confirmed" when task feedback information from at least one task participant indicates participation in the collaborative computing task. The task update module is used to execute the joint computing task by the task initiator and the task participants when the status of the joint computing task is confirmed, and to update the status of the joint computing task according to the execution progress of the task initiator and the task participants.

[0008] According to a third aspect of the embodiments of this application, an electronic device is provided, including: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the memory, and the communication interface communicate with each other through the communication bus. The memory is used to store at least one executable instruction, which causes the processor to perform an operation corresponding to the joint computing state control method described in the first aspect above.

[0009] According to a fourth aspect of the embodiments of this application, a computer storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the state control method for joint computation as described in the first aspect above.

[0010] The above technical solution first sends project invitation information to each project participant based on the project information configured by the project initiator for the target project, and updates the status of the target project to "pending confirmation." Then, when all project participants provide feedback indicating their participation in the joint computation of the target project, the status of the target project is updated to "confirmed," ensuring mutual trust and consistency between the project initiator and each project participant, and clarifying the scope of cooperation. Next, the task initiator of the target project initiates a joint computation task, sending task invitation information to each task participant. At this time, the status of the joint computation task is "pending confirmation." When all task participants provide feedback indicating their participation in the joint computation task, the status of the joint computation task is updated to "confirmed." The task feedback information ensures that the algorithms and data used in the joint computation task are within a controllable range. Then, the task initiator and task participants begin to execute the joint computation task, updating the status of the joint computation task according to their respective execution progress. Through the dual control mechanism of project status and task status, the security of joint computation is improved. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a flowchart of a joint computing state control method provided in one embodiment of this application;

[0013] Figure 2 This is a schematic diagram of a project status control method provided in one embodiment of this application;

[0014] Figure 3 This is a schematic diagram of a task state control method provided in another embodiment of this application;

[0015] Figure 4 This is a schematic diagram of a joint computing state control device provided in one embodiment of this application;

[0016] Figure 5 This is a schematic block diagram of an electronic device provided in one embodiment of this application. Detailed Implementation

[0017] To enable those skilled in the art to better understand the technical solutions in the embodiments of the present invention, the technical solutions in the embodiments of the present invention will be clearly and thoroughly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art should fall within the protection scope of the present invention.

[0018] Reference is made to the accompanying drawings, which form part of the detailed description and illustrate exemplary embodiments. Furthermore, it should be understood that other embodiments may be utilized, and structural and / or logical changes may be made without departing from the scope of the claimed subject matter. It should also be noted that orientations and references (e.g., up, down, top, bottom, etc.) may be used merely to facilitate the description of features in the drawings. Therefore, the following detailed description is not to be construed in a limiting sense, and the scope of the claimed subject matter is defined only by the appended claims and their equivalents.

[0019] Numerous details are set forth in the following description. However, it will be apparent to those skilled in the art that the embodiments described herein can be practiced without these specific details. In some instances, well-known methods and apparatus are shown in block diagram form rather than in detail to avoid obscuring the embodiments described herein. Throughout this specification, references to “embodiment,” “one embodiment,” or “some embodiments” mean that a particular feature, structure, function, or characteristic described in connection with that embodiment is included in at least one embodiment herein. Therefore, the phrases “in an embodiment,” “in one embodiment,” or “some embodiments” appearing throughout this specification do not necessarily refer to the same embodiment. Furthermore, in one or more embodiments, particular features, structures, functions, or characteristics can be combined in any suitable manner. For example, a first embodiment can be combined with a second embodiment in any way that does not mutually exclude particular features, structures, functions, or characteristics associated with two embodiments.

[0020] As used in the description and appended claims, the singular forms “a (a, an)” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0021] The terms “coupling” and “connection”, along with their derivatives, are used herein to describe functional or structural relationships between components. It should be understood that these terms are not intended to be synonyms for each other. Rather, in certain embodiments, “connection” can be used to indicate that two or more elements are in direct physical, optical, or electrical contact with each other. “Coupling” can be used to indicate that two or more elements are in direct or indirect physical or electrical contact with each other (with other intermediary elements between them), and / or that two or more elements cooperate or interact with each other (e.g., as in a causal relationship).

[0022] As used herein, the terms “above,” “below,” “between,” and “on” refer to the relative position of a component or material with respect to other components or materials, where such physical relationships are noteworthy. For example, in the context of materials, a material positioned above or below another material may be in direct contact with it, or may have one or more intermediate materials. Furthermore, a material positioned between two materials may be in direct contact with both layers, or may have one or more intermediate layers. In contrast, a first material or material “on” a second material or material is in direct contact with that second material / material. Similar distinctions are made in the context of component assembly.

[0023] As described throughout this document and in the claims, a list of items connected by the terms “at least one of” or “one or more of” may mean any combination of the listed items. For example, the phrase “at least one of A, B, or C” may mean A; B; C; A and B; A and C; B and C; or A, B, and C.

[0024] The terms “circuit” or “module” can refer to one or more passive and / or active components arranged to cooperate with each other to provide a desired function. The term “signal” can refer to at least one current signal, voltage signal, or magnetic signal. The terms “substantially,” “close to,” “approximately,” “near,” and “about” generally refer to within + / -10% of the target value.

[0025] The specific implementation of the embodiments of the present invention will be further described below with reference to the accompanying drawings.

[0026] Joint computing state control method

[0027] This application provides a state control method for joint computing. The following describes the state control method for joint computing in detail through multiple embodiments.

[0028] Joint computing refers to a method of computing and analyzing sensitive data distributed across different platforms without sharing the original data. This method allows different stakeholders to collaborate on data analysis without sharing the actual original data, thereby protecting data privacy and security.

[0029] To improve the security of federated computing, this application provides a state control method for federated computing.

[0030] Figure 1 This is a flowchart of a joint computation state control method according to an embodiment of this application. Figure 1 As shown, the joint computation state control method includes the following steps:

[0031] Step S102: Based on the project information configured by the project initiator for the target project, send project invitation information to each project participant and update the status of the target project to pending confirmation. The project invitation information is used to invite project participants to participate in the joint calculation of the target project.

[0032] The target project is created by the project initiator and configured with corresponding project information, which may include project name, project description, data description, cooperation agreement, etc., though this embodiment does not limit this. After the target project is configured, project invitation information is sent to each project participant, inviting them to participate in the joint calculation of the target project. Then, the status of the target project is updated to pending confirmation. The project participants can be one or more parties.

[0033] It should be noted that after configuring the project information, the project initiator can also cancel the target project and update the target project status to "project ended".

[0034] Step S104: If the project feedback information from each project participant indicates participation in the joint calculation of the target project, then update the status of the target project to confirmed.

[0035] After receiving the project invitation, project participants will decide whether to participate in the target project. If all project participants indicate that they will participate in the joint calculation of the target project, it means that the project initiator and all project participants have reached a mutual trust and consensus and clarified the scope of cooperation. Then, the status of the target project will be updated to confirmed.

[0036] Step S106: When the status of the target project is confirmed, send task invitation information to each task participant according to the joint computing task initiated by the task initiator, and update the status of the joint computing task to pending confirmation.

[0037] The task initiator can be any one of the project participants or the project initiator. The task participants can be any one of the project participants or the project initiator. For example, if the project initiator is A and the project participants are B, C, and D, the task initiator can be B and the task participants can be A and C, or the task initiator can be A and the task participants can be B, C, and D.

[0038] When the target project's status is "Confirmed," it means that a joint computing task can be initiated for the target project. The task initiator initiates the joint computing task, identifies the other parties involved in this joint computing task as task participants. Task participants can be one or more parties. Then, the task initiator sends task invitation messages to all task participants, inviting them to participate in the joint computing task.

[0039] Step S108: If the task feedback information from each task participant indicates participation in the joint computing task, then update the status of the joint computing task to confirmed.

[0040] After receiving the task invitation, the task participants will provide feedback to the task initiator. When all the task participants provide feedback indicating that they are participating in the joint computing task, it means that the algorithm, data and other information used in the joint computing task are within a controllable range, and the joint computing task can continue. The status of the joint computing task will then be updated to confirmed.

[0041] Step S110: When the status of the joint computing task is confirmed, the task initiator and the task participants execute the joint computing task, and update the status of the joint computing task according to the execution progress of the task initiator and the task participants.

[0042] When the status of a joint computing task is confirmed, it means that the task can start execution. The joint computing task is executed by the task initiator and the task participants. During the execution process, the status of the joint computing task is updated according to the execution progress of the task initiator and the task participants.

[0043] In this embodiment, firstly, based on the project information configured by the project initiator for the target project, project invitation information is sent to each project participant, and the status of the target project is updated to pending confirmation. Then, when the project feedback information from all project participants indicates participation in the joint computation of the target project, the status of the target project is updated to confirmed, ensuring mutual trust and consistency between the project initiator and each project participant and clarifying the scope of cooperation. Next, a joint computation task is initiated for the target project task initiator, and task invitation information is sent to each task participant. At this time, the status of the joint computation task is pending confirmation. When the task feedback information from all task participants indicates participation in the joint computation task, the status of the joint computation task is updated to confirmed. The task feedback information ensures that the algorithm and data used in the joint computation task are within a controllable range. Then, the task initiator and task participants begin to execute the joint computation task and update the status of the joint computation task according to their respective execution progress. Through the dual control mechanism of project status and task status, the security of joint computation is improved.

[0044] In one possible implementation, once the project information is configured, if the project information is saved to the database and no project invitation information has been sent to each project participant, then the status of the target project is updated to "not submitted", project invitation information is sent to each project participant, and the status of the target project is updated from "not submitted" to "pending confirmation".

[0045] Once the project initiator has configured the project information, they can save the project information to the database instead of sending project invitations to project participants. Then, the target project's status will be updated to "Unsubmitted," and at this point, the target project will only be visible to the project initiator. Then, project invitations can be sent to all project participants, at which point all project participants will also be able to see the project information, and the target project's status will be updated to "Pending Confirmation."

[0046] In this embodiment, after the project information is configured, the project initiator saves the project information to the database before sending the project invitation information and updates the status of the target project to "not submitted". At this time, the project information is only visible to the project initiator. Then, when the status of the target project is "not submitted", the project invitation information is sent to each project participant and the status of the target project is updated to "pending confirmation". By setting the "not submitted" status, the granularity of the project status control is refined and the security of the collaborative computing project is improved.

[0047] In one possible implementation, when the target project is in an unsubmitted state, the project information is edited and saved according to the editing instructions from the project initiator.

[0048] When the target project is in the "Unsubmitted" state, it is only visible to the project initiator. The project initiator can edit the project information according to the project requirements, save the edited project information, and then send project invitation information to the project participants based on the edited project information, and then update the target project status to "Pending Confirmation".

[0049] In this embodiment of the application, when the target project is in an unsubmitted state, the project information is edited and saved according to the editing instructions of the project initiator. By supporting the editing of project information, the flexible configuration of the target project is ensured, providing a greater possibility for establishing mutual trust and consensus between the project initiator and the project participants.

[0050] In one possible implementation, if the project feedback information from each project participant indicates a refusal to participate in the joint calculation of the target project, or if the project initiator terminates the target project, then the status of the target project will be updated from pending confirmation to terminated, and the terminated status of the target project will be synchronized to each project participant.

[0051] After receiving the project invitation information, project participants can confirm their participation or refuse to participate in the target project. When at least one project participant provides feedback indicating that they refuse to participate in the joint calculation of the target project, the status of the target project will be updated from pending confirmation to terminated.

[0052] The project initiator has the right to terminate the target project at any time. For example, if the project initiator discovers that the target project for joint computing has security risks or other problems, the project initiator can terminate the target project immediately and update the status of the target project from pending confirmation to terminated.

[0053] When the target project is in the terminated state, the target project's status needs to be synchronized with all project participants.

[0054] In this embodiment of the application, if the project feedback information from each project participant indicates a refusal to participate in the joint computation of the target project, or if the project initiator terminates the target project, the status of the target project will be updated from pending confirmation to terminated. Whether the target project is terminated is jointly decided by the project participants and the project initiator to ensure the security of the joint computation. Then, the terminated status of the target project will be synchronized to each project participant. If any party causes the target project to terminate, other partners will be notified, so that the status of the project is within a controllable range.

[0055] In one possible implementation, if the task feedback information from each task participant indicates a refusal to participate in the joint computing task, the status of the joint computing task is updated to "rejected".

[0056] After receiving the task invitation information from the task initiator, the task participants can decide whether to participate in the joint computing task based on various factors such as the algorithm, data usage, and cooperation agreement. When at least one task participant provides feedback indicating that they refuse to participate in the joint computing task, it means that the joint computing task cannot continue, and the status of the joint computing task will be updated to "rejected".

[0057] In this embodiment of the application, if the task feedback information provided by each task participant indicates that they refuse to participate in the joint computing task, it means that the joint computing task cannot continue. In this case, the status of the joint computing task is updated to "rejected". By setting the "rejected" status for the joint computing task, the granularity of task status management is refined, and the security of joint computing is improved.

[0058] In one possible implementation, when updating the status of the joint computing task based on the execution progress of the task initiator and the task participants, the following steps are taken: the task initiator and the task participants update the status of the sub-computing tasks based on the progress of the sub-computing tasks included in the joint computing task. The task initiator and each task participant execute different sub-computing tasks, and the status of the sub-computing tasks includes suspended, in progress, completed, failed, or terminated. The status of the joint computing task is determined based on the status of each sub-computing task.

[0059] Once the status of the joint computing task is confirmed, execution can begin. Both the task initiator and participants have their own sub-computation tasks to execute. These sub-computation tasks differ, and they form the joint computing task. Therefore, the status of the joint computing task can be determined based on the status of all sub-computation tasks. The status of a sub-computation task includes: suspended, in progress, completed, failed, or terminated. For example, if all sub-computation tasks are completed, the status of the joint computing task can be determined as completed. If at least one sub-computation task fails, the status of the joint computing task is determined as failed.

[0060] In this embodiment, the task initiator and task participants update the status of the sub-computing tasks based on their progress in executing the joint computing task. The status of the sub-computing tasks includes aborted, in progress, completed, failed, or terminated. The task initiator and task participants independently control the status of the sub-computing tasks. By controlling the status of the sub-computing tasks, the scheduling of resources and data becomes more reasonable and convenient. Then, based on the status of each sub-computing task, the status of the joint computing task is determined. After the task starts, the task status is controlled through multiple statuses such as aborted, in progress, completed, failed, or terminated. This refines the granularity of task status control and further improves the security of joint computing.

[0061] In one possible implementation, when the target project is in an unsubmitted or terminated state, the project information of the target project is deleted in response to a first deletion instruction sent by the project initiator; and / or, when the joint computation task is in any one of an unsubmitted, rejected, completed, failed, or terminated state, the sub-computation task executed by the task initiator or task participant is deleted in response to a second deletion instruction sent by the task initiator or task participant.

[0062] During the project status management phase, the project initiator has the right to delete the project information of the target project. When the status of the target project is "not submitted", the project initiator can delete the project information if he / she wants to cancel the project. When the status of the target project is "terminated", it means that the target project can no longer continue, and the project information of the target project can be deleted.

[0063] During the task status management phase, if the status of the joint computing task is any of the following: not submitted, rejected, completed, failed, or terminated, it means that the joint computing task cannot continue, and the task initiator or task participant can delete their respective sub-computing tasks.

[0064] In this embodiment, when the target project is in the state of not submitted or terminated, the project information of the target project is deleted in response to the first deletion instruction sent by the project initiator; and / or, when the state of the joint computing task is any one of not submitted, rejected, completed, failed, and terminated, the sub-computing task executed by the task initiator or task participant is deleted in response to the second deletion instruction sent by the task initiator or task participant. Based on the state of the target project and / or the joint computing task, it is determined whether to delete the corresponding project information or sub-computing task, which refines the granularity of the state control of the project and / or task and improves the security of joint computing.

[0065] Figure 2 This is a schematic diagram of the state control of a project according to an embodiment of this application, such as... Figure 2As shown, the project initiator creates a new target project and configures the project information. After configuration, the initiator can initiate three operations: first, cancel to end the project; second, send project invitations to project participants, at which point the target project status is updated to "Pending Confirmation"; third, save the project information to the database, updating the target project status to "Unsubmitted." In the "Unsubmitted" state, the project information can be edited, and then project invitations can be sent to project participants, updating the target project status to "Pending Confirmation" again. When a project participant receives a project invitation, they save the project information to the database and set it to "Pending Confirmation." If the participant chooses to confirm participation in the joint calculation of the target project, the locally saved project status is set to "Confirmed." If the participant chooses to refuse participation, the locally saved project status is set to "Terminated." After making a choice, the participant needs to provide feedback to the project initiator. After receiving feedback from all participants, the initiator determines whether all participants have confirmed their participation. If so, the target project status is updated to "Confirmed"; otherwise, the target project status is updated to "Terminated." Once the project initiator updates the target project's status to "Confirmed," they can choose to terminate the project, at which point the project's status will be updated to "Terminated." After updating the target project's status to "Terminated," the project initiator will synchronize the terminated status to every project participant. When a project participant confirms their participation, they can also choose to terminate the target project, updating their locally saved project status to "Terminated" and synchronizing the terminated status to the project initiator. When the target project is in an "Unsubmitted" or "Terminated" status, the project initiator can delete the project information. It should be noted that project participants can be one or more parties.

[0066] Figure 3 This is a schematic diagram of the state control of a task according to an embodiment of this application, as shown below. Figure 3As shown, the task initiator creates a joint computation task. After creation, the initiator can initiate two operations: First, it can directly send task invitation information to the task participants, at which point the joint computation task status is updated to "Pending Confirmation." Second, it can save the joint computation task information to the database, update the joint computation task status to "Unsubmitted," and send task invitation information to the task participants in the "Unsubmitted" state, updating the joint computation task status to "Pending Confirmation." In the "Unsubmitted" state, the task initiator can also choose to delete the joint computation task. When a task participant receives a task invitation, it saves the joint computation task information to the database and sets it to "Pending Confirmation." If a task participant chooses to confirm participation, the locally saved joint computation task status is set to "Confirmed." If a task participant chooses to refuse participation, the locally saved joint computation task status is set to "Rejected." After making a choice, the task participant needs to send task feedback information back to the task initiator. After receiving the task feedback information from each task participant, the task initiator determines whether all participants have confirmed participation. If so, the joint computation task status is updated to "Confirmed"; otherwise, the joint computation task status is updated to "Rejected." When the status of the joint computing task is confirmed, both the task initiator and the task participants can begin executing their respective sub-computation tasks and update the status of the sub-computation tasks according to their respective execution progress. The status of a sub-computation task includes suspended, in progress, completed, failed, or terminated. The task initiator and the task participants independently control the status of the joint computing task. When the status of a sub-computation task is completed, failed, or terminated, the corresponding task initiator or task participant can delete the sub-computation task. It should be noted that the task initiator and task participants can be any one of the project initiator and all project participants; there can be one or more task participants.

[0067] Jointly computed state control device

[0068] Figure 4 This is a schematic diagram of a joint computing state control device provided in one embodiment of this application, as shown below. Figure 4 As shown, the joint computing state control device 400 may include: a project initiation module 402, a project update module 404, a task initiation module 406, a task confirmation module 408, and a task update module 410.

[0069] The project initiation module 402 is used to send project invitation information to each project participant based on the project information configured by the project initiator for the target project, and update the status of the target project to pending confirmation. The project invitation information is used to invite project participants to participate in the joint calculation of the target project.

[0070] The target project is created by the project initiator through the project initiation module 402, and the corresponding project information is configured. The project information may include the project name, project description, data description, cooperation agreement, etc., which are not limited in this embodiment. After the target project is configured, the project invitation information is sent to each project participant through the project initiation module 402, inviting the project participants to participate in the joint calculation of the target project. Then, the status of the target project is updated to pending confirmation. The project participants can be one or more parties.

[0071] It should be noted that after the project initiator has configured the project information, they can also cancel the target project, and the target project status will be updated to "project ended".

[0072] Project update module 404 is used to update the status of the target project to "confirmed" when the project feedback information from all project participants indicates participation in the joint calculation of the target project.

[0073] After receiving the project invitation, project participants will decide whether to participate in the target project. If all project participants indicate that they will participate in the joint calculation of the target project, it means that the project initiator and all project participants have reached a mutual trust and consensus and clarified the scope of cooperation. Then, the status of the target project will be updated to confirmed through the project update module 404.

[0074] The task initiation module 406 is used to send task invitation information to each task participant based on the joint computing task initiated by the task initiator when the status of the target project is confirmed, and to update the status of the joint computing task to pending confirmation.

[0075] The task initiator can be any one of the project participants or the project initiator. The task participants can be any one of the project participants or the project initiator. For example, if the project initiator is A and the project participants are B, C, and D, the task initiator can be B and the task participants can be A and C, or the task initiator can be A and the task participants can be B, C, and D.

[0076] When the target project's status is "Confirmed," it means that a joint computing task can be initiated for the target project. The task initiator initiates the joint computing task through the task initiation module 406, identifying other parties involved in this joint computing task as task participants. Task participants can be one or more parties. Then, the task initiator sends task invitation information to all task participants, inviting them to participate in the joint computing task.

[0077] The task confirmation module 408 is used to update the status of the joint computing task to "confirmed" when the task feedback information from all task participants indicates participation in the joint computing task.

[0078] After receiving the task invitation information, the task participants will provide feedback to the task initiator. When all the task feedback information from the task participants indicates participation in the joint computing task, it means that the algorithm, data and other information used in the joint computing task are within the controllable range, and the joint computing task can continue. The task confirmation module 408 updates the status of the joint computing task to confirmed.

[0079] The task update module 410 is used to execute the joint computing task by the task initiator and the task participants when the status of the joint computing task is confirmed, and to update the status of the joint computing task according to the execution progress of the task initiator and the task participants.

[0080] When the status of the joint computing task is confirmed, it means that the task can start execution. The joint computing task is executed by the task initiator and the task participants. During the execution, the status of the joint computing task is updated through the task update module 410 according to the execution progress of the task initiator and the task participants.

[0081] In this embodiment, firstly, based on the project information configured by the project initiator for the target project, the project initiation module 402 sends project invitation information to each project participant and updates the status of the target project to pending confirmation. Then, when all project participants provide feedback indicating participation in the joint computation of the target project, the project update module 404 updates the status of the target project to confirmed, ensuring mutual trust and consistency between the project initiator and each project participant and clarifying the scope of cooperation. Next, the task initiator for the target project initiates a joint computation task through the task initiation module 406 and sends task invitation information to each task participant. At this time, the status of the joint computation task is pending confirmation. When all task participants provide feedback indicating participation in the joint computation task, the task confirmation module 408 updates the status of the joint computation task to confirmed. The task feedback information ensures that the algorithms and data used in the joint computation task are within a controllable range. Then, the task initiator and task participants begin to execute the joint computation task and update the status of the joint computation task through the task update module 410 according to their respective execution progress. Through the dual control mechanism of project status and task status, the security of joint computation is improved.

[0082] electronic devices

[0083] Figure 5 This is a schematic block diagram of an electronic device provided in an embodiment of this application. Specific embodiments of this application do not limit the specific implementation of the electronic device. Figure 5As shown, the electronic device 500 may include: a processor 502, a communications interface 504, a memory 506, and a communications bus 508. Wherein:

[0084] The processor 502, communication interface 504, and memory 506 communicate with each other via communication bus 508.

[0085] Communication interface 504 is used to communicate with other electronic devices or servers.

[0086] The processor 502 is used to execute program 510, which can specifically execute the relevant steps in any of the aforementioned joint calculation state control method embodiments.

[0087] Specifically, program 510 may include program code that includes computer operation instructions.

[0088] The processor 502 may be a CPU, an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application. The smart device may include one or more processors of the same type, such as one or more CPUs; or it may include processors of different types, such as one or more CPUs and one or more ASICs.

[0089] Memory 506 is used to store program 510. Memory 506 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0090] Specifically, program 510 can be used to cause processor 502 to execute the state control method of joint computation in any of the foregoing embodiments.

[0091] The specific implementation of each step in program 510 can be found in the corresponding steps and units described in any of the aforementioned joint calculation state control method embodiments, and will not be repeated here. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the devices and modules described above can be referred to the corresponding process descriptions in the aforementioned method embodiments, and will not be repeated here.

[0092] The electronic device in this embodiment first sends project invitation information to each project participant based on the project information configured by the project initiator for the target project, and updates the status of the target project to "pending confirmation". Then, when the project feedback information from all project participants indicates participation in the joint computation of the target project, the status of the target project is updated to "confirmed" to ensure mutual trust and consistency between the project initiator and each project participant and to clarify the scope of cooperation. Next, the task initiator of the target project initiates a joint computation task and sends task invitation information to each task participant. At this time, the status of the joint computation task is "pending confirmation". When the task feedback information from all task participants indicates participation in the joint computation task, the status of the joint computation task is updated to "confirmed". The task feedback information ensures that the algorithm and data used in the joint computation task are within a controllable range. Then, the task initiator and task participants begin to execute the joint computation task and update the status of the joint computation task according to their respective execution progress. Through the dual control mechanism of project status and task status, the security of joint computation is improved.

[0093] storage media

[0094] In this embodiment, a computer-readable storage medium is provided to store instructions for causing a machine to perform a state control method for joint computing as described herein. Specifically, a system or apparatus equipped with a storage medium storing software program code that implements the functions of any of the embodiments described above, and enabling the computer (or CPU or MPU) of the system or apparatus to read and execute the program code stored in the storage medium.

[0095] In this case, the program code read from the storage medium can itself implement the function of any of the above embodiments, and therefore the program code and the storage medium storing the program code constitute part of this application.

[0096] Examples of storage media used to provide program code include floppy disks, hard disks, magneto-optical disks, optical disks (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD+RW), magnetic tapes, non-volatile memory cards, and ROMs. Alternatively, program code can be downloaded from a server computer via a communication network.

[0097] It should be noted that the above-mentioned joint computing state control method embodiment is based on the aforementioned joint computing state control method embodiment. For details and beneficial effects, please refer to the description in the aforementioned joint computing state control method embodiment, which will not be repeated here.

[0098] In the description of this application, the terms "first" and "second" are used only for convenience in describing different components or names, and should not be construed as indicating or implying a sequential relationship, relative importance, or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature.

[0099] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.

[0100] It should be noted that although specific embodiments of this application have been described in detail with reference to the accompanying drawings, this should not be construed as limiting the scope of protection of this application. Various modifications and variations that can be made by those skilled in the art without inventive effort within the scope described in the claims still fall within the scope of protection of this application.

[0101] The examples of the embodiments in this application are intended to concisely illustrate the technical features of the embodiments in this application, so that those skilled in the art can intuitively understand the technical features of the embodiments in this application, and are not intended to be improper limitations on the embodiments in this application.

[0102] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A joint computational state control method, characterized in that, The method includes: Based on the project information configured by the project initiator for the target project, a project invitation message is sent to at least one project participant, and the status of the target project is updated to pending confirmation. The project invitation message is used to invite the project participant to participate in the joint computation of the target project. If the project feedback information from at least one project participant indicates participation in the joint calculation of the target project, then the status of the target project will be updated to confirmed. When the status of the target project is confirmed, according to the joint computing task initiated by the task initiator, a task invitation message is sent to at least one task participant, and the status of the joint computing task is updated to pending confirmation. The task initiator includes any one of the at least one project participant or the project initiator. The task participant includes any one of the at least one project participant or the project initiator. If the task feedback information from at least one task participant indicates participation in the joint computing task, then the status of the joint computing task is updated to confirmed. When the status of the joint computing task is confirmed, the task initiator and the task participants execute the joint computing task, and update the status of the joint computing task according to the execution progress of the task initiator and the task participants.

2. The method according to claim 1, characterized in that, The method further includes: Once the project information is configured, if the project information is saved to the database and the project invitation information has not been sent to at least one project participant, then the status of the target project will be updated to "not submitted". Sending project invitation information to at least one project participant and updating the status of the target project to pending confirmation includes: Send the project invitation information to at least one project participant and update the status of the target project from unsubmitted to pending confirmation.

3. The method according to claim 2, characterized in that, The method further includes: When the target project is in an unsubmitted state, the project information is edited and saved according to the editing instructions of the project initiator.

4. The method according to claim 3, characterized in that, The method further includes: If the project feedback information from at least one of the project participants indicates a refusal to participate in the joint computation of the target project, or if the project initiator terminates the target project, then the status of the target project will be updated from pending confirmation to terminated, and the terminated status of the target project will be synchronized to the at least one project participant.

5. The method according to claim 4, characterized in that, The method further includes: If at least one of the task participants provides task feedback information indicating a refusal to participate in the joint computing task, the status of the joint computing task is updated to "rejected".

6. The method according to claim 5, characterized in that, The step of updating the status of the joint computing task based on the execution progress of the task initiator and the task participants includes: The task initiator and the task participants update the status of the sub-computing tasks based on the progress of the execution of the sub-computing tasks included in the joint computing task. The task initiator and the at least one task participant execute different sub-computing tasks, and the status of the sub-computing tasks includes suspended, in progress, completed, failed, or terminated. The state of the joint computing task is determined based on the state of each of the sub-computing tasks.

7. The method according to claim 6, characterized in that, The method further includes: When the status of the target project is unsubmitted or terminated, in response to the first deletion instruction sent by the project initiator, the project information of the target project is deleted. And / or, When the status of the joint computing task is any one of unsubmitted, rejected, completed, failed, or terminated, the sub-computing task executed by the task initiator or the task participant is deleted in response to a second deletion instruction sent by the task initiator or the task participant.

8. A state control device for joint computation, characterized in that, The device includes: The project initiation module is used to send project invitation information to at least one project participant based on the project information configured by the project initiator for the target project, and update the status of the target project to pending confirmation. The project invitation information is used to invite the project participant to participate in the joint calculation of the target project. The project update module is used to update the status of the target project to "confirmed" when the project feedback information provided by at least one project participant indicates participation in the joint calculation of the target project. The task initiation module is used to send task invitation information to at least one task participant according to the joint computing task initiated by the task initiator when the status of the target project is confirmed, and update the status of the joint computing task to pending confirmation. The task initiator includes any one of the at least one project participant or the project initiator. The task participant includes any one of the at least one project participant or the project initiator. The task confirmation module is used to update the status of the joint computing task to "confirmed" when the task feedback information from at least one task participant indicates participation in the joint computing task. The task update module is used to execute the joint computing task by the task initiator and the task participants when the status of the joint computing task is confirmed, and to update the status of the joint computing task according to the execution progress of the task initiator and the task participants.

9. An electronic device, characterized in that, include: The processor, communication interface, memory, and communication bus communicate with each other through the communication bus. The memory is used to store at least one executable instruction that causes the processor to perform the operation corresponding to the state control method of the joint computation as described in any one of claims 1-7.

10. A computer storage medium having a computer program stored thereon, which, when executed by a processor, implements the state control method for joint computation as described in any one of claims 1-7.

Images