Task execution method and device based on cloud edge collaboration

By obtaining and allocating task information in the cloud-edge collaborative system in real time and executing it in the cloud or edge-edge according to the task type, the delay and broadband pressure problems in the execution of cloud-edge collaborative tasks are solved, and the service quality and user experience are improved.

CN119065869APending Publication Date: 2024-12-03石化盈科信息技术有限责任公司 +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410960663.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-17
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

In the implementation of cloud-edge collaborative tasks, we face comprehensive problems such as task diversity, deployment management difficulties, security challenges, optimization goal conflicts, and resource heterogeneity, resulting in high data interaction delays, high broadband pressure, service quality and user experience Not good.

Method used

By obtaining collaborative task information in real time between the cloud and the edge, determining the task type, and reasonably allocating and executing it in the cloud or edge according to the task type, generating task execution results and syncing them to the corresponding end, achieving ultra-low latency of data interaction Automatic feedback on time and messages to alleviate the broadband pressure on the central cloud.

Benefits of technology

It realizes efficient execution of tasks and data collaborative processing, reduces data interaction delay, improves service quality and user experience, and alleviates the broadband pressure of the central cloud.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119065869A_ABST
    Figure CN119065869A_ABST
Patent Text Reader

Abstract

The invention provides a task execution method and device based on cloud edge collaboration. The method and device are applied to a collaboration system formed by a cloud end and a plurality of edge ends. The method comprises the steps that a source end obtains collaborative task information in real time; if the creation end of the collaborative task information is a cloud end, the side end is an opposite end, and if the creation end of the collaborative task information is the side end, the side end is the cloud end; the source end determines a corresponding collaborative task type according to the collaborative task information; the source end and the opposite end collaboratively complete corresponding task execution operation according to the collaborative task type, and a task execution result is generated; the task execution result is displayed in the opposite-end collaborative service and synchronized to the source-end collaborative service. According to different task characteristics and requirements, tasks are reasonably distributed to the cloud end or the side end for processing, ultra-low delay of data interaction and automatic message feedback are achieved, the broadband pressure of the central cloud is relieved, and the service quality and the user experience are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of cloud computing technology, and in particular to a method, device, electronic equipment and storage medium for simulating a secondary migration path of petroleum. Background Art

[0002] With the emergence of cloud-edge collaborative technology, problems such as the differences in cloud service demands among different industries, cloud-edge resource management and scheduling, and data consistency and security have been solved, achieving the goal of extending cloud computing and cloud analysis to the edge.

[0003] However, at the current stage, the realization of cloud-edge collaborative task execution faces comprehensive problems such as task diversity, deployment management difficulties, security challenges, optimization goal conflicts, and resource heterogeneity. Summary of the invention

[0004] The present invention provides a task execution method and device based on cloud-edge collaboration, which reasonably allocates tasks to the cloud or edge for processing according to different task characteristics and requirements.

[0005] In a first aspect, the present invention provides a task execution method based on cloud-edge collaboration, which is applied to a collaborative system consisting of a cloud and several edge terminals; the method comprises:

[0006] Step S1, the source end obtains the collaborative task information in real time; if the creation end of the collaborative task information is the cloud, the edge end is the peer end; if the creation end of the collaborative task information is the edge end, the edge end is the cloud;

[0007] Step S2, the source end determines a corresponding collaborative task type according to the collaborative task information;

[0008] In step S3, the source end and the peer end collaboratively complete the corresponding task execution operation according to the collaborative task type and generate a task execution result; the task execution result is displayed on the peer end collaborative service and synchronized to the source end collaborative service.

[0009] Optionally, the collaborative task type includes a single collaborative task and a mixed task; and step S3 includes:

[0010] Step S31, if the collaborative task type is the single collaborative task, after the source end determines the subtask type of the single collaborative task, the source end and the peer end collaboratively complete the task execution operation according to the subtask execution order corresponding to the subtask type, and generate the task execution result;

[0011] Step S32, if the collaborative task type is the mixed task, after the source end determines the subtask type contained in the mixed task, the source end and the counterpart end execute the subtask execution order corresponding to the subtask type in sequence according to the preset subtask type execution order, collaboratively complete the corresponding task execution operation, and generate the task execution result.

[0012] Optionally, the subtask type includes: product collaboration task; and step S31 includes:

[0013] Step S311a, the source end parses the product information in the product collaborative task;

[0014] In step S312a, the source end synchronizes the specified products in the product warehouse of the source end to the product warehouse of the opposite end through collaborative technology; the task execution result is generated after the product deployment is completed in the product warehouse of the opposite end.

[0015] Optionally, the subtask type includes: command execution task; the step S31 includes:

[0016] Step S311b, the source end coordinates the task data in the command execution task to the peer end;

[0017] Step S312b, the opposite end parses the target node and task content in the task data, and sends the task content to the target node; the task execution result is generated after the target node completes the execution of the task content.

[0018] Optionally, the subtask type includes: a message notification task; and step S31 includes:

[0019] Step S311c, the source end coordinates the message data in the message notification task to the peer end;

[0020] Step S312c, the opposite end parses the notification address and notification content of all notification tasks in the message data, and sends the notification content to the notification address; the task execution result is generated after the opposite end completes the execution of all the notification tasks.

[0021] Optionally, the step S32 includes:

[0022] S321, the source end determines whether the mixed task includes the product collaborative task, and if so, executes the steps S311a and S312a;

[0023] S322, the source end determines whether the mixed task includes the command execution task, and if so, executes the steps S311b and S312b;

[0024] S323, the source end determines whether the mixed task includes the message notification task, and if so, executes the steps S311c and S312c.

[0025] In a second aspect, the present invention provides a task execution device based on cloud-edge collaboration, which is applied to a collaborative system consisting of a cloud and several edge terminals; the device includes:

[0026] An acquisition module, used for acquiring collaborative task information in real time through a source end; if the creation end of the collaborative task information is a cloud end, the edge end is a peer end; if the creation end of the collaborative task information is the edge end, the edge end is the cloud end;

[0027] A collaborative task type determination module, used to determine the corresponding collaborative task type according to the collaborative task information through the source end;

[0028] The result generation module is used to collaboratively complete the corresponding task execution operation through the source end and the peer end according to the collaborative task type, and generate a task execution result; the task execution result is displayed on the peer end collaborative service and synchronized to the source end collaborative service.

[0029] Optionally, the collaborative task types include single collaborative tasks and mixed tasks; and the result generation module includes:

[0030] A first generating submodule is used for, when the collaborative task type is the single collaborative task, after the source end determines the subtask type of the single collaborative task, the source end and the peer end collaboratively complete the task execution operation according to the subtask execution order corresponding to the subtask type, and generate the task execution result;

[0031] The second generation submodule is used for, when the collaborative task type is the mixed task, after the source end determines the subtask type included in the mixed task, the source end and the opposite end execute the subtask execution order corresponding to the subtask type in sequence according to the preset subtask type execution order, collaboratively complete the corresponding task execution operation, and generate the task execution result.

[0032] In a third aspect, the present invention provides an electronic device, comprising a processor and a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps in the method provided in the first aspect are performed.

[0033] In a fourth aspect, the present invention provides a storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, runs the steps of the method provided in the first aspect.

[0034] It can be seen from the above technical solutions that the present invention has the following advantages:

[0035] The present invention provides a task execution method and device based on cloud-edge collaboration, which is applied to a collaborative system composed of a cloud and several edge terminals; the method includes: step S1, the source terminal obtains collaborative task information in real time; if the creation terminal of the collaborative task information is the cloud, the edge terminal is the opposite terminal, and if the creation terminal of the collaborative task information is the edge terminal, the edge terminal is the cloud; step S2, the source terminal determines the corresponding collaborative task type according to the collaborative task information; step S3, the source terminal and the opposite terminal, according to the collaborative task type, collaboratively complete the corresponding task execution operation and generate a task execution result; the task execution result is displayed on the opposite terminal collaborative service and synchronized to the source terminal collaborative service. According to different task characteristics and requirements, tasks are reasonably allocated to the cloud or edge terminal for processing, achieving ultra-low latency and automatic message feedback for data interaction, alleviating the broadband pressure of the central cloud, and improving service quality and user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0037] Figure 1 This is a process step diagram of a first embodiment of a task execution method based on cloud-edge collaboration of the present invention;

[0038] Figure 2 This is one of the execution schematic diagrams of Embodiment 1 of a task execution method based on cloud-edge collaboration of the present invention;

[0039] Figure 3 This is a second execution diagram of Embodiment 1 of a task execution method based on cloud-edge collaboration of the present invention;

[0040] Figure 4 This is a structural block diagram of an embodiment of a task execution device based on cloud-edge collaboration of the present invention. DETAILED DESCRIPTION

[0041] The embodiments of the present invention provide a task execution method and device based on cloud-edge collaboration, which reasonably allocates tasks to the cloud or edge for processing according to different task characteristics and requirements.

[0042] In order to make the purpose, features and advantages of the present invention more obvious and easy to understand, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described below are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0043] Embodiment 1

[0044] See also Figure 1 , Figure 1 This is a flow chart of a first embodiment of a task execution method based on cloud-edge collaboration of the present invention, which is applied to a collaborative system consisting of a cloud and several edge terminals; the method includes:

[0045] Step S1, the source end obtains the collaborative task information in real time; if the creation end of the collaborative task information is the cloud, the edge end is the peer end; if the creation end of the collaborative task information is the edge end, the edge end is the cloud;

[0046] It should be noted that cloud-edge collaboration refers to the collaborative work between the cloud and the edge, leveraging the advantages of cloud and edge resources to achieve efficient task execution and collaborative processing of data.

[0047] The cloud usually refers to a cloud computing center with a large amount of computing and storage resources for processing large-scale data and complex computing tasks.

[0048] The edge refers to terminal devices close to data sources or users, such as sensors, smartphones, IoT devices, etc., which usually have limited computing and storage capabilities.

[0049] Step S2, the source end determines a corresponding collaborative task type according to the collaborative task information;

[0050] In step S3, the source end and the peer end collaboratively complete the corresponding task execution operation according to the collaborative task type and generate a task execution result; the task execution result is displayed on the peer end collaborative service and synchronized to the source end collaborative service.

[0051] Specifically, the collaborative task types include single collaborative tasks and mixed collaborative tasks; step S3 includes:

[0052] Step S31, if the collaborative task type is the single collaborative task, after the source end determines the subtask type of the single collaborative task, the source end and the peer end collaboratively complete the task execution operation according to the subtask execution order corresponding to the subtask type, and generate the task execution result;

[0053] In the embodiment of the present invention, the subtask types include: product collaboration tasks, command execution types and message notification tasks.

[0054] When the subtask type is a product collaboration task, step S31 includes:

[0055] The source end parses the product information in the product collaborative task;

[0056] The source end synchronizes the formulated products in the product warehouse of the source end to the product warehouse of the opposite end through collaborative technology; the task execution result is generated after the product deployment is completed in the product warehouse of the opposite end.

[0057] See also Figure 2 , Figure 2 This is one of the execution diagrams of the first embodiment of a task execution method based on cloud-edge collaboration of the present invention, wherein 1 is the cloud, 2 is the edge, 3 is the cloud product warehouse, and 4 is the edge product warehouse. The embodiment of the present invention uses the cloud 1 as the source end to obtain collaborative task information in real time. The collaborative service of the cloud 1 parses the product information in the product collaborative task and specifies the product in the cloud product warehouse 3. Then, through the collaborative technology, the edge 2 synchronizes the specified product of the cloud product warehouse 3 to the edge product warehouse 4. After the product warehouse 4 on the other end completes the product deployment, the task execution result is automatically generated and fed back to the collaborative service of the cloud 1 by the collaborative service of the edge 2. After the collaborative service of the cloud 1 receives the task execution result, it notifies the collaborative service of the edge 2 of the task execution result to complete the execution of the product collaborative task.

[0058] When the subtask type is a command execution type, step S31 includes:

[0059] The source end coordinates the task data in the command execution task to the peer end;

[0060] The opposite end parses the target node and the task content in the task data, and sends the task content to the target node; the task execution result is generated after the target node completes the execution of the task content.

[0061] See also Figure 3 , Figure 3This is the second execution diagram of the first embodiment of a task execution method based on cloud-edge collaboration of the present invention, wherein 5 is an edge node. In the embodiment of the present invention, the cloud 1 is the source end, and the collaborative service of the edge 2 parses the task content in the command execution task, and executes the task content in one or more edge nodes 5 specified as target nodes in the command execution task. After the target node completes the execution of the task content, the collaborative service of the edge 2 displays the automatically generated task execution results, and synchronizes the task execution results to the collaborative service of the cloud 1, so as to complete the execution of the command execution task.

[0062] When the subtask type is a message notification task, step S31 includes:

[0063] The source end coordinates the message data in the message notification task to the peer end;

[0064] The peer end parses the notification address and notification content of all notification tasks in the message data, and sends the notification content to the notification address; the task execution result is generated after the peer end completes the execution of all the notification tasks.

[0065] See also Figure 3 , Figure 3 This is the second execution diagram of the first embodiment of a task execution method based on cloud-edge collaboration of the present invention. In the embodiment of the present invention, the cloud end 1 is used as the source end, and the collaborative service of the edge end 2 parses the notification content in the message notification task and the edge node 5 as the notification address, and sends the notification content to the corresponding notification address in accordance with the format requirements. After the edge end 2 completes the execution of all notification tasks, the collaborative service of the edge end 2 will display the automatically generated task execution results, and synchronize the task execution results to the collaborative service of the cloud end 1, so as to complete the execution of the command execution task.

[0066] Step S32, if the collaborative task type is the mixed task, after the source end determines the subtask type contained in the mixed task, the source end and the counterpart end execute the subtask execution order corresponding to the subtask type in sequence according to the preset subtask type execution order, collaboratively complete the corresponding task execution operation, and generate the task execution result.

[0067] Specifically, the step S32 includes:

[0068] S321, the source end determines whether the mixed task includes the product collaborative task. If so, the source end parses the product information in the product collaborative task; the source end synchronizes the formulated products in the source product warehouse to the peer product warehouse through collaborative technology; the task execution result is generated after the peer product warehouse completes the product deployment.

[0069] S322, the source end determines whether the mixed task includes the command execution task. If so, the source end coordinates the task data in the command execution task to the opposite end; the opposite end parses the target node and task content in the task data, and sends the task content to the target node; the task execution result is generated after the target node completes the execution of the task content.

[0070] S323, the source end determines whether the mixed task includes the message notification task. If so, the source end coordinates the message data in the message notification task to the opposite end; the opposite end parses the notification address and notification content of all notification tasks in the message data, and sends the notification content to the notification address; the task execution result is generated after the opposite end completes the execution of all the notification tasks.

[0071] In an embodiment of the present invention, when a mixed type task is actually executed, the subtask types included in the mixed type task are executed in the order of first processing the product collaboration task, then processing the command execution task, and finally processing the message notification task, and the execution details are also carried out in accordance with the execution process of the corresponding subtask type in the embodiment.

[0072] A task execution method based on cloud-edge collaboration provided by an embodiment of the present invention is applied to a collaborative system composed of a cloud and several edge terminals; the method includes: step S1, the source terminal obtains collaborative task information in real time; if the creation terminal of the collaborative task information is the cloud, the edge terminal is the opposite terminal, and if the creation terminal of the collaborative task information is the edge terminal, the edge terminal is the cloud; step S2, the source terminal determines the corresponding collaborative task type according to the collaborative task information; step S3, the source terminal and the opposite terminal, according to the collaborative task type, collaboratively complete the corresponding task execution operation and generate a task execution result; the task execution result is displayed on the opposite terminal collaborative service and synchronized to the source terminal collaborative service. According to different task characteristics and requirements, tasks are reasonably allocated to the cloud or edge terminal for processing, achieving ultra-low latency and automatic message feedback for data interaction, alleviating the broadband pressure of the central cloud, and improving service quality and user experience.

[0073] Embodiment 2

[0074] See also Figure 3 , Figure 3 This is a structural block diagram of an embodiment of a task execution device based on cloud-edge collaboration of the present invention, which is applied to a collaborative system consisting of a cloud and several edge terminals; the device includes:

[0075] The acquisition module 201 is used to acquire the collaborative task information in real time through the source end; if the creation end of the collaborative task information is the cloud end, the edge end is the peer end; if the creation end of the collaborative task information is the edge end, the edge end is the cloud end;

[0076] A collaborative task type determination module 202, configured to determine a corresponding collaborative task type according to the collaborative task information through the source end;

[0077] The result generation module 203 is used to collaboratively complete the corresponding task execution operation through the source end and the peer end according to the collaborative task type and generate a task execution result; the task execution result is displayed on the peer end collaborative service and synchronized to the source end collaborative service.

[0078] In an optional embodiment, the collaborative task types include single collaborative tasks and mixed tasks; the result generation module 203 includes:

[0079] A first generating submodule is used for, when the collaborative task type is the single collaborative task, after the source end determines the subtask type of the single collaborative task, the source end and the peer end collaboratively complete the task execution operation according to the subtask execution order corresponding to the subtask type, and generate the task execution result;

[0080] The second generation submodule is used for, when the collaborative task type is the mixed task, after the source end determines the subtask type included in the mixed task, the source end and the opposite end execute the subtask execution order corresponding to the subtask type in sequence according to the preset subtask type execution order, collaboratively complete the corresponding task execution operation, and generate the task execution result.

[0081] In an optional embodiment, the subtask type includes: product collaboration task; the first generation submodule includes:

[0082] A parsing unit, configured to parse the artifact information in the artifact collaborative task through the source end;

[0083] The synchronization unit is used to synchronize the specified products of the product warehouse of the source end to the product warehouse of the opposite end through the collaborative technology of the source end; the task execution result is generated after the product deployment is completed in the product warehouse of the opposite end.

[0084] In an optional embodiment, the subtask type includes: a command execution task; the first generation submodule includes:

[0085] A first coordination unit, configured to coordinate task data in the command execution task to the peer end through the source end;

[0086] The first sending unit is used to parse the target node and task content in the task data through the opposite end, and send the task content to the target node; the task execution result is generated after the target node completes the execution of the task content.

[0087] In an optional embodiment, the subtask type includes: a message notification task; the first generation submodule includes:

[0088] A second coordination unit, configured for the source end to coordinate the message data in the message notification task to the peer end;

[0089] The second sending unit is used for the opposite end to parse the notification address and notification content of all notification tasks in the message data, and send the notification content to the notification address; the task execution result is generated after the opposite end completes the execution of all the notification tasks.

[0090] In an optional embodiment, the second generation submodule includes:

[0091] A first judgment unit, configured to judge whether the mixed task includes the product collaborative task through the source end, and if so, execute the parsing unit and the synchronization unit;

[0092] A second determining unit, configured to determine, through the source end, whether the mixed task includes the command execution task, and if so, execute the first coordination unit and the first sending unit;

[0093] The third judgment unit is used to judge whether the mixed task includes the message notification task through the source end, and if so, execute the second collaboration unit and the second sending unit.

[0094] Embodiment 3

[0095] An embodiment of the present invention further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of a task execution method based on cloud-edge collaboration in any embodiment, which is applied to a collaborative system composed of a cloud and several edge terminals; the method includes:

[0096] Step S1, the source end obtains the collaborative task information in real time; if the creation end of the collaborative task information is the cloud, the edge end is the peer end; if the creation end of the collaborative task information is the edge end, the edge end is the cloud;

[0097] Step S2, the source end determines a corresponding collaborative task type according to the collaborative task information;

[0098] In step S3, the source end and the peer end collaboratively complete the corresponding task execution operation according to the collaborative task type and generate a task execution result; the task execution result is displayed on the peer end collaborative service and synchronized to the source end collaborative service.

[0099] In an optional embodiment, the collaborative task types include single collaborative tasks and mixed tasks; and step S3 includes:

[0100] Step S31, if the collaborative task type is the single collaborative task, after the source end determines the subtask type of the single collaborative task, the source end and the peer end collaboratively complete the task execution operation according to the subtask execution order corresponding to the subtask type, and generate the task execution result;

[0101] Step S32, if the collaborative task type is the mixed task, after the source end determines the subtask type contained in the mixed task, the source end and the counterpart end execute the subtask execution order corresponding to the subtask type in sequence according to the preset subtask type execution order, collaboratively complete the corresponding task execution operation, and generate the task execution result.

[0102] In an optional embodiment, the subtask type includes: product collaboration task; the step S31 includes:

[0103] Step S311a, the source end parses the product information in the product collaborative task;

[0104] In step S312a, the source end synchronizes the specified products in the product warehouse of the source end to the product warehouse of the opposite end through collaborative technology; the task execution result is generated after the product deployment is completed in the product warehouse of the opposite end.

[0105] In an optional embodiment, the subtask type includes: command execution task; the step S31 includes:

[0106] Step S311b, the source end coordinates the task data in the command execution task to the peer end;

[0107] Step S312b, the opposite end parses the target node and task content in the task data, and sends the task content to the target node; the task execution result is generated after the target node completes the execution of the task content.

[0108] In an optional embodiment, the subtask type includes: a message notification task; and step S31 includes:

[0109] Step S311c, the source end coordinates the message data in the message notification task to the peer end;

[0110] Step S312c, the opposite end parses the notification address and notification content of all notification tasks in the message data, and sends the notification content to the notification address; the task execution result is generated after the opposite end completes the execution of all the notification tasks.

[0111] In an optional embodiment, the step S32 includes:

[0112] S321, the source end determines whether the mixed task includes the product collaborative task, and if so, executes the steps S311a and S312a;

[0113] S322, the source end determines whether the mixed task includes the command execution task, and if so, executes the steps S311b and S312b;

[0114] S323, the source end determines whether the mixed task includes the message notification task, and if so, executes the steps S311c and S312c.

[0115] Embodiment 4

[0116] An embodiment of the present invention further provides a computer storage medium having a computer program stored thereon. When the computer program is executed by the processor, the steps of a task execution method based on cloud-edge collaboration in any embodiment are implemented, and the method is applied to a collaborative system consisting of a cloud and several edge terminals. The method includes:

[0117] Step S1, the source end obtains the collaborative task information in real time; if the creation end of the collaborative task information is the cloud, the edge end is the peer end; if the creation end of the collaborative task information is the edge end, the edge end is the cloud;

[0118] Step S2, the source end determines a corresponding collaborative task type according to the collaborative task information;

[0119] In step S3, the source end and the peer end collaboratively complete the corresponding task execution operation according to the collaborative task type and generate a task execution result; the task execution result is displayed on the peer end collaborative service and synchronized to the source end collaborative service.

[0120] In an optional embodiment, the collaborative task types include single collaborative tasks and mixed tasks; and step S3 includes:

[0121] Step S31, if the collaborative task type is the single collaborative task, after the source end determines the subtask type of the single collaborative task, the source end and the peer end collaboratively complete the task execution operation according to the subtask execution order corresponding to the subtask type, and generate the task execution result;

[0122] Step S32, if the collaborative task type is the mixed task, after the source end determines the subtask type contained in the mixed task, the source end and the counterpart end execute the subtask execution order corresponding to the subtask type in sequence according to the preset subtask type execution order, collaboratively complete the corresponding task execution operation, and generate the task execution result.

[0123] In an optional embodiment, the subtask type includes: product collaboration task; the step S31 includes:

[0124] Step S311a, the source end parses the product information in the product collaborative task;

[0125] In step S312a, the source end synchronizes the specified products in the product warehouse of the source end to the product warehouse of the opposite end through collaborative technology; the task execution result is generated after the product deployment is completed in the product warehouse of the opposite end.

[0126] In an optional embodiment, the subtask type includes: command execution task; the step S31 includes:

[0127] Step S311b, the source end coordinates the task data in the command execution task to the peer end;

[0128] Step S312b, the opposite end parses the target node and task content in the task data, and sends the task content to the target node; the task execution result is generated after the target node completes the execution of the task content.

[0129] In an optional embodiment, the subtask type includes: a message notification task; and step S31 includes:

[0130] Step S311c, the source end coordinates the message data in the message notification task to the peer end;

[0131] Step S312c, the opposite end parses the notification address and notification content of all notification tasks in the message data, and sends the notification content to the notification address; the task execution result is generated after the opposite end completes the execution of all the notification tasks.

[0132] In an optional embodiment, the step S32 includes:

[0133] S321, the source end determines whether the mixed task includes the product collaborative task, and if so, executes the steps S311a and S312a;

[0134] S322, the source end determines whether the mixed task includes the command execution task, and if so, executes the steps S311b and S312b;

[0135] S323, the source end determines whether the mixed task includes the message notification task, and if so, executes the steps S311c and S312c.

[0136] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0137] In the several embodiments provided in the present application, it should be understood that the methods, devices, electronic devices and storage media disclosed in the present invention can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0138] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed on multiple grid units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0139] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0140] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a readable storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a grid device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned readable storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0141] As described above, the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features thereof may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A task execution method based on cloud-edge collaboration, characterized in that: Applied to a collaborative system consisting of a cloud and several edge terminals; the method includes: Step S1, the source end obtains the collaborative task information in real time; if the creation end of the collaborative task information is the cloud, the edge end is the peer end; if the creation end of the collaborative task information is the edge end, the edge end is the cloud; Step S2, the source end determines a corresponding collaborative task type according to the collaborative task information; In step S3, the source end and the peer end collaboratively complete the corresponding task execution operation according to the collaborative task type and generate a task execution result; the task execution result is displayed on the peer end collaborative service and synchronized to the source end collaborative service.

2. The task execution method based on cloud-edge collaboration according to claim 1 is characterized in that: The collaborative task types include single collaborative tasks and mixed tasks; step S3 includes: Step S31, if the collaborative task type is the single collaborative task, after the source end determines the subtask type of the single collaborative task, the source end and the peer end collaboratively complete the task execution operation according to the subtask execution order corresponding to the subtask type, and generate the task execution result; Step S32, if the collaborative task type is the mixed task, after the source end determines the subtask type contained in the mixed task, the source end and the counterpart end execute the subtask execution order corresponding to the subtask type in sequence according to the preset subtask type execution order, collaboratively complete the corresponding task execution operation, and generate the task execution result.

3. The task execution method based on cloud-edge collaboration according to claim 2 is characterized in that: The subtask types include: product collaboration tasks; the step S31 includes: Step S311a, the source end parses the product information in the product collaborative task; In step S312a, the source end synchronizes the specified products in the product warehouse of the source end to the product warehouse of the opposite end through collaborative technology; the task execution result is generated after the product deployment is completed in the product warehouse of the opposite end.

4. The task execution method based on cloud-edge collaboration according to claim 3 is characterized in that: The subtask types include: command execution tasks; the step S31 includes: Step S311b, the source end coordinates the task data in the command execution task to the peer end; Step S312b, the opposite end parses the target node and task content in the task data, and sends the task content to the target node; the task execution result is generated after the target node completes the execution of the task content.

5. The task execution method based on cloud-edge collaboration according to claim 4 is characterized in that: The subtask types include: message notification tasks; the step S31 includes: Step S311c, the source end coordinates the message data in the message notification task to the peer end; Step S312c, the opposite end parses the notification address and notification content of all notification tasks in the message data, and sends the notification content to the notification address; the task execution result is generated after the opposite end completes the execution of all the notification tasks.

6. The task execution method based on cloud-edge collaboration according to claim 5 is characterized in that: The step S32 comprises: S321, the source end determines whether the mixed task includes the product collaborative task, and if so, executes the steps S311a and S312a; S322, the source end determines whether the mixed task includes the command execution task, and if so, executes the steps S311b and S312b; S323, the source end determines whether the mixed task includes the message notification task, and if so, executes the steps S311c and S312c.

7. A task execution device based on cloud-edge collaboration, characterized in that: Applied to the collaborative system consisting of the cloud and several edge terminals; the device includes: An acquisition module, used for acquiring collaborative task information in real time through a source end; if the creation end of the collaborative task information is a cloud end, the edge end is a peer end; if the creation end of the collaborative task information is the edge end, the edge end is the cloud end; A collaborative task type determination module, used to determine the corresponding collaborative task type according to the collaborative task information through the source end; The result generation module is used to collaboratively complete the corresponding task execution operation through the source end and the peer end according to the collaborative task type, and generate a task execution result; the task execution result is displayed on the peer end collaborative service and synchronized to the source end collaborative service.

8. The task execution device based on cloud-edge collaboration according to claim 7 is characterized in that: The collaborative task types include single collaborative tasks and mixed tasks; the result generation module includes: A first generating submodule is used for, when the collaborative task type is the single collaborative task, after the source end determines the subtask type of the single collaborative task, the source end and the peer end collaboratively complete the task execution operation according to the subtask execution order corresponding to the subtask type, and generate the task execution result; The second generation submodule is used for, when the collaborative task type is the mixed task, after the source end determines the subtask type included in the mixed task, the source end and the opposite end execute the subtask execution order corresponding to the subtask type in sequence according to the preset subtask type execution order, collaboratively complete the corresponding task execution operation, and generate the task execution result.

9. An electronic device, characterized in that: The method comprises a processor and a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the method according to any one of claims 1 to 6 is executed.

10. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 6 is executed.