WO2023050410A1

WO2023050410A1 - Workflow operation method and apparatus

Info

Publication number: WO2023050410A1
Application number: PCT/CN2021/122423
Authority: WO
Inventors: 高永峰; 高亮
Original assignee: 西门子股份公司; 西门子（中国）有限公司
Priority date: 2021-09-30
Filing date: 2021-09-30
Publication date: 2023-04-06
Also published as: CN117940904A

Abstract

Embodiments of the present application provide a workflow operation method and apparatus, capable of effectively improving the work efficiency on the basis of reducing manpower. The method comprises: a first device obtains a workflow, the workflow being used for indicating at least one function invoked by an event and an execution sequence of the at least one function; after receiving a first event, the first device determines, according to the workflow, a first function to be invoked by the first event, the event comprising the first event, and the at least one function comprising the first function; if the first device is a device where the first function is located, the first device invokes the first function; and if a second device is a device where the first function is located, the first device routes the first event to the second device.

Description

Method and apparatus for workflow operation

technical field

The present application relates to the field of computer technology, and more specifically, to a workflow operation method and device.

Background technique

At present, when engineers need to deploy or operate and maintain applications, it generally takes a lot of time to deploy solutions for different devices on site by directly connecting them to devices through data cables. If the application is modified, the application needs to be redeployed, causing engineers to repeat the previous complicated and tedious process.

Furthermore, if tasks need to be run across multiple edge devices to complete a series of business processes, the multiple edge devices may come from different vendors. Therefore, in addition to the need to develop and integrate heterogeneous systems of different devices, the above-mentioned problems will also be encountered during deployment, which not only wastes manpower but also reduces efficiency.

Contents of the invention

The present application provides a workflow operation method and device, which can effectively improve work efficiency on the basis of reducing manpower.

According to the first aspect, there is provided a workflow operation method, which is characterized by comprising: the first device obtains the workflow, and the workflow is used to indicate at least one function function called by an event and the execution sequence of the at least one function function ; After the first device receives the first event, according to the workflow, determine the first function to be called by the first event, the event includes the first event, and the at least one function Including the first functional function; if the first device is the device where the first functional function is located, then the first device calls the first functional function; if the second device is the first functional function device, the first device routes the first event to the second device.

In the above technical solution, by deploying functional functions on the device, the entire workflow can be completed on the device, that is, the application can be processed through remote deployment without going to the site, which greatly reduces manpower. In addition, the device completes the entire workflow according to the workflow used to indicate the at least one functional function invoked by the event and the execution sequence of the at least one functional function, which can effectively improve work efficiency.

Furthermore, because the device can obtain the workflow, no matter which device the function is deployed on, the device can determine the function called by the event according to the workflow, even if the device is not the device where the function is located, the event can also be routed to the device where the function is located to call the function, so that the flexibility of the entire system can be improved.

In some possible implementation manners, the functional functions deployed on the first device are determined according to the resources of the first device, and the functional functions deployed on the second device are determined according to the resources of the second device If the resources of the first device are greater than the resources of the second device, more functional functions are deployed on the first device than on the second device.

In the above technical solution, the functional functions are deployed on the device according to the resources of the device. More functional functions are deployed on the device with more resources, and relatively fewer functional functions are deployed on the device with few resources, so that the rational allocation of resources and the allocation of resources can be realized. use efficiently. Further, deploying functional functions on devices according to device resources avoids the problem that a certain functional function must be deployed to a certain device, and improves the flexibility of deploying functional functions.

In some possible implementation manners, if the second device is the device where the first functional function is located, the method further includes: the first device receives feedback information sent by the second device, and the feedback information uses Feedback of an execution result of the first functional function executed by the second device.

In the above technical solution, when the device receiving the event is not the device where the function called by the event is located, the device where the function called by the event is located will feed back the result of executing the function to the device receiving the event after executing the function , so that the device receiving the event can continue to execute the next step, avoiding the invalid waiting time of the device receiving the event, and greatly reducing the time for executing the entire workflow.

In some possible implementation manners, the method further includes: the first device determines the device where the first functional function is located according to record information, and the record information is used to record each of the at least one functional function The device on which the function function resides.

In the above technical solution, the device receiving the event can accurately route the event to the device where the function called by the event is located by recording the recorded information of the device where each functional function is located.

In some possible implementation manners, the acquiring the workflow by the first device includes: receiving, by the first device, workflow scheduling information sent by a system, where the workflow scheduling information identifies the workflow.

In some possible implementation manners, the first device receiving the workflow scheduling information sent by the system includes: before the first device leaves the factory, the first device receives the workflow scheduling information sent by the system .

In the above technical solution, the workflow can be obtained before the device receiving the event leaves the factory. In this way, even if the device is disconnected from the central cluster, the workflow can still be executed, which greatly ensures the normal operation of the workflow.

In some possible implementation manners, the first event includes first information, and the first information is an input of the first functional function.

In some possible implementation manners, the first device and the second device are edge devices.

In a second aspect, an apparatus for workflow operation is provided, including units for executing the method in the above first aspect or various implementations thereof.

In a third aspect, a device for workflow operation is provided, including: a memory for storing programs; a processor for executing the programs stored in the memory, and when the programs stored in the memory are executed, the processing The device is configured to execute the method in the above first aspect or its various implementation manners.

In a fourth aspect, a computer-readable storage medium is provided, storing program code for execution by a device, where the program code includes instructions for executing the steps in the method in the above-mentioned first aspect or each implementation manner thereof.

Description of drawings

Fig. 1 is a schematic diagram of a workflow operation method according to an embodiment of the present application.

Fig. 2 is a schematic diagram of a service mesh according to an embodiment of the present application.

Fig. 3 is a schematic diagram of step 1 in the flow of an event-triggered workflow according to an embodiment of the present application.

Fig. 4 is a schematic diagram of step 2 in the flow of an event-triggered workflow according to an embodiment of the present application.

Fig. 5 is a schematic diagram of step 3 in the flow of an event-triggered workflow according to an embodiment of the present application.

Fig. 6 is a schematic block diagram of an apparatus for workflow operation according to an embodiment of the present application.

Fig. 7 is a schematic block diagram of an apparatus for workflow operation according to an embodiment of the present application.

List of reference signs:

100. The workflow operation method of the embodiment of the present application

110. The first device acquires a workflow;

120. After the first device receives the first event, determine the first function to be called by the first event according to the workflow;

130. If the first device is the device where the first function is located, the first device calls the first function;

140. If the second device is the device where the first function resides, the first device routes the first event to the second device;

CP, control panel (control plane);

F1, function function 1;

F2, function function 2;

F3, function function 3;

S, start;

S1-S3, steps 1-3;

E, end;

e1, event 1;

e2, event 2;

D1, device 1;

D2, device 2;

C, container (container);

SC, sidecar (sidecar);

600. A device for workflow operation;

610. Acquire a unit;

620. Determine the unit;

630, call the unit;

640, a routing unit;

700. A device for workflow operation;

701, memory;

702, a processor;

703, communication interface;

704, bus.

Detailed ways

The technical solutions in the embodiments of the present application are described below with reference to the accompanying drawings. It should be understood that the specific examples in this specification are only to help those skilled in the art better understand the embodiments of the present application, rather than limiting the scope of the embodiments of the present application.

It should be understood that in various embodiments of the present application, the serial numbers of the processes do not mean the order of execution, and the execution order of the processes should be determined by their functional functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation.

It should also be understood that the various implementation manners described in this specification can be implemented alone or in combination, which is not limited in this embodiment of the present application.

Unless otherwise specified, all technical and scientific terms used in the embodiments of the present application have the same meaning as commonly understood by those skilled in the technical field of the present application. The terms used in the present application are only for the purpose of describing specific embodiments, and are not intended to limit the scope of the present application.

Furthermore, if tasks need to be run across multiple edge devices to complete a series of business processes, the multiple edge devices may come from different vendors. Therefore, in addition to requiring a lot of energy to deal with the development, communication, debugging, and integration of heterogeneous systems, the above-mentioned problems will also be encountered during deployment, which not only wastes manpower but also reduces efficiency.

In view of this, the embodiment of the present application proposes a method for invoking a function, which can effectively improve work efficiency on the basis of reducing manpower.

FIG. 1 shows a schematic flowchart of a workflow operation method 100 according to an embodiment of the present application. The method 100 may be executed by a first device. As shown in FIG. 1 , the method 100 may include at least part of the following contents.

In step 110, the first device obtains the workflow.

In step 120, after the first device receives the first event, according to the workflow, determine the first function to be called by the first event.

In step 130, if the first device is the device where the first function resides, the first device calls the first function.

In step 140, if the second device is the device where the first function resides, the first device routes the first event to the second device.

Wherein, the first device is different from the second device, and the first device and/or the second device may be an edge device. An edge device can be a device that provides an entry point into an enterprise or service provider core network. For example, edge devices may include edge routers, routing switches, firewalls, multiplexers, and other wide area network (wide area network, WAN) devices. With the development of artificial intelligence and Internet of things (IoT) technology, edge devices generally have built-in processors with onboard analysis or artificial intelligence capabilities. These devices may include sensors, drivers, and IoT gateways.

Certainly, the first device and the second device may also be other devices except the edge device, which is not specifically limited in this embodiment of the present application.

It should be noted that the term "and/or" in this article is only an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B can mean: A exists alone, and A exists at the same time and B, there are three cases of B alone.

Optionally, the above functional functions may be, but not limited to, message queuing telemetry transport (message queuing telemetry transport, MQTT) protocol analysis functional functions, data processing functional functions, and the like.

A workflow (workflow) may be used to indicate at least one functional function invoked by an event (event) of the workflow and an execution sequence of the at least one functional function. It can be seen that workflow can be used to orchestrate functional functions into coordinated microservice applications, that is, to combine functional functions and events into a coherent unit, and to describe the execution of functional functions and the information delivered in a prescribed manner.

As an example, FIG. 2 shows a schematic diagram of a possible network in the embodiment of the present application. In FIG. 2 , the workflow is: event 1 calls function 1, and after function 1 is executed, function 2 is called. After function function 2 is executed, event 2 calls function function 3.

It should be understood that FIG. 2 is only intended to help those skilled in the art better understand the embodiment of the present application, rather than limit the scope of the embodiment of the present application. For example, event 1 may also call function function 3, and after function function 3 is executed, event 2 may also call function function 1 and function function 2.

Optionally, events and workflows can be defined by referring to the specification CloudEvents. CloudEvents is a specification for describing event data in a common format to provide interoperability across services, platforms, and systems. Of course, the definition of events and workflow can also refer to the cloud native computing foundation (cloud native computing foundation, CNCF) serverless workflow (serverless workflow).

Each function in the workflow can be driven by events from different sources, that is, the workflow in this embodiment of the present application is triggered by events. Optionally, an event can call one or more function functions. As shown in FIG. 2 , event 1 calls function function 1 and function function 2 , and event 2 calls function function 3 .

Alternatively, multiple events can call a single function.

Optionally, workflows can be developer-created and pre-configured on the built system. The system here may be, but not limited to, a function as a service (function as a service, FaaS) system. For the convenience of description, the following description takes the system as an example of a FaaS system.

Continuing to refer to FIG. 2 , the FaaS system may include two parts, one of which is a function management module. The functional function management module can be used to be responsible for the full life cycle management of functional functions, such as creation, release, update, destruction, etc. Exemplarily, the functional function management module can refer to the following actions to control the life cycle of the functional function:

(a) Create: Create new functional functions, including their specifications and codes;

(b) release: create a new version that can be deployed on the cluster;

(c) update alias/label (version): update version alias;

(d) Acquisition: return function metadata and specifications;

(e) Update: modify the latest version of the function;

(f) Deletion: To delete a function, you can delete a specific version or all versions of the function;

(g) list: display a list of functional functions and their metadata;

(h) Obtain statistical information: return statistical information about the usage of the function when it is running;

(i) Get log: return the log generated by the function function.

The other part is the workflow management module, as shown in Figure 2, the workflow management module includes workflow.

Before the developer creates the workflow, the developer may first join the first device and/or the second device to the network. Wherein, the network may be a service mesh (service mesh).

Continuing to take Figure 2 as an example for illustration, the service mesh may include a control plane (control plane) and equipment. Among them, besides including the FaaS system, the control panel can also perform other actions, such as routing control management, function registration, function discovery, monitoring and traffic tracking.

Optionally, developers can create functional functions according to business requirements, and configure the created functional functions on the functional function management module in the FaaS system. Afterwards, the functional function management module can hot-deploy these functional functions to the device. For example, the functional function management module can hot-deploy these functional functions into containers (containers) on the device.

In a possible implementation manner, the functional function management module can hot-deploy these functional functions to different devices according to the resources of each device. That is, the functional functions deployed on the first device may be determined according to the resources of the first device, and similarly, the functional functions deployed on the second device may also be determined according to the resources of the second device.

The resources of the first device and the resources of the second device may be central processing unit (central processing unit, CPU) resources, gateway resources, etc. of the first device. The resource of the first device may be the total resource of the first device, or may be a resource not used by the first device at the current moment. Correspondingly, the resources of the second device may also be the total resources of the second device or the resources not used by the second device at the current moment.

Specifically, the service mesh can monitor the resource status of the first device and the second device. After the service mesh monitors the resource status of the first device and the resource status of the second device, it can control the function management module to deploy the function to the first device and the second device. Among them, the function deployed on the device with more resources Functions can be more than functional functions deployed on devices with few resources. Continuing to refer to Figure 2, if the resource of device 1 is more than that of device 2, then the functional functions deployed on device 1 are more than those deployed on device 2, that is, functional function 1 and functional function 2 are deployed on device 1, Function 2 is deployed on device 2. Of course, function 2 and function 3 may also be deployed on device 1, and function 1 may be deployed on device 2.

It should be understood that the embodiment of the present application does not specifically limit which device the function function is deployed on, as long as the number of function functions deployed on the device with more resources is greater than the number of function functions deployed on the device with fewer resources.

Optionally, when determining the function function called by the event, the developer may determine it according to the input of the function function. Specifically, the event may include information, which is an input of a function called by the event. For example, a first event calls a first function, the first event includes first information, and the first information is an input of the first function.

Optionally, step 110 may specifically include: the first device receives workflow scheduling information sent by the FaaS system, where the workflow scheduling information identifies a workflow.

As an example, the FaaS system may send workflow scheduling information to the first device every preset time period. Exemplarily, the preset time period may be 5s. In this way, the probability that the first device obtains the workflow can be improved.

As another example, before the first device leaves the factory, the first device may receive workflow scheduling information sent to it by the FaaS system. In this technical solution, the workflow can be obtained before the first device leaves the factory, so that even if the first device is disconnected from the central cluster, the workflow can still be executed, which greatly ensures the normal execution of the workflow.

Further, the method 100 may further include: the first device determines the device where the first functional function is located according to the record information, where the record information is used to record the device where each functional function of the at least one functional function is located.

Optionally, after the functional function management module deploys at least one functional function to different devices, the functional function management module sends record information to each device, so as to notify the device of the device where each functional function in the at least one functional function is located .

As an example, each device may include a sidecar, and the function management module may send record information to the sidecar, so that the sidecar of each device may record the functions deployed on each device. Continuing to take FIG. 2 as an example for illustration, the sidecar of device 1 may record function 1 and function 3 on device 1, and function 2 on device 2.

After the first device receives the first event, if the first device determines that it is the device where the first function resides according to the recorded information, the first device may directly call the first function.

If the first device determines, according to the record information, that it is not the device where the first function resides, but the second device is the device where the first function resides, then the first device may route the first event to the second device.

As shown in Figure 3, device 2 receives event 1, determines that event 1 invokes function 1 according to the workflow, and determines that function 1 is on device 1, therefore, device 2 routes event 1 to device 1, so that event 1 The functional function 1 is called, and the device 1 executes the functional function 1.

It can be seen from Figure 3 that device 2 receives event 1 and device 2 routes event 1 to device 1, both of which are executed by the sidecar of the device. That is, the sidecar of device 2 receives event 1 and routes event 1 to the sidecar of device 1.

Of course, device 2 receiving event 1 and device 2 routing event 1 to device 1 may also be executed by other modules of the device, which is not specifically limited in this embodiment of the present application.

Optionally, the second device may also send feedback information to the first device, where the feedback information is used to feed back an execution result of the second device executing the first function.

For example, the second device may send feedback information to the first device during the process of executing the first function, such as sending a negative acknowledgment (negative acknowledgment, NACK), so that the first device knows that the second device is executing the first function. .

Alternatively, the second device may send feedback information to the first device after executing the first function, such as sending an acknowledgment (acknowledgment, ACK), so that the first device knows that the second device has completed the execution of the first function. .

In order to understand the embodiment of the present application more clearly, on the basis of FIG. 2 , the specific flow of the event-triggered workflow of the embodiment of the present application will be further illustrated below in conjunction with FIGS. 3-5 .

step 1

In the initial state, Device 1 and Device 2 wait for an event to trigger. When the sidecar in device 2 receives event 1, it is determined that event 1 invokes function 1 according to the workflow. Since function 1 is deployed on device 1, the sidecar routes event 1 to device 1 to invoke function 1.

step 2

After executing function 1, device 1 sends feedback information to the sidecar of device 2 through the sidecar, so that device 2 determines that device 1 has executed function 1.

Next, the device 2 again determines to call the functional function 2 according to the workflow, and the functional function 2 is deployed on the device 2. Therefore, the device 2 directly calls the functional function 2.

According to the workflow, it can be known that after the functional function 2 is executed, the event 2 may trigger the workflow to call the functional function 3 . Therefore, after executing function 2, the system waits for event 2 to be triggered.

step 3

After receiving event 2, the sidecar in device 2 determines that event 2 calls function 3 according to the workflow. Since function 3 is deployed on device 1, the sidecar routes event 2 to device 1 to invoke function 3.

After executing function 3, the container in device 1 can send feedback information to the sidecar of device 1. At this point, the workflow execution is complete.

In the embodiment of the present application, by deploying functional functions on the device, the entire workflow can be completed on the device, that is, the application can be processed through remote deployment without going to the site, which greatly reduces manpower. In addition, the device completes the entire workflow according to the workflow used to indicate the at least one functional function invoked by the event and the execution sequence of the at least one functional function, which can effectively improve work efficiency.

The method embodiments of the embodiments of the present application are described in detail above, and the device embodiments of the embodiments of the present application are described below. The device embodiments correspond to the method embodiments. Therefore, for the parts that are not described in detail, please refer to the previous method embodiments and device embodiments. Any possible implementation manner in the above methods can be implemented.

FIG. 6 shows a schematic block diagram of an apparatus 600 for workflow operation according to an embodiment of the present application. The workflow operation apparatus 600 may execute the workflow operation method 100 in the embodiment of the present application, and the workflow operation apparatus 600 may be the first device in the aforementioned method.

As shown in FIG. 6, the device 600 for the workflow operation includes:

An acquiring unit 610, configured to acquire workflow scheduling information, where the workflow scheduling information is used to indicate at least one functional function called by an event of the workflow and an execution order of the at least one functional function;

The determining unit 620 is configured to determine a first function to be called by the first event according to the workflow scheduling information after the first device receives the first event, the event of the workflow includes the a first event, said at least one functional function comprising said first functional function;

a calling unit 630, configured to call the first functional function if the first device is the device where the first functional function is located;

The routing unit 640 is configured to route the first event to the second device if the second device is the device where the first function resides.

Optionally, in an embodiment of the present application, the functional functions deployed on the first device are determined according to the resources of the first device, and the functional functions deployed on the second device are determined according to the second The resources of the device are determined.

If the resources of the first device are greater than the resources of the second device, more functional functions are deployed on the first device than on the second device.

Optionally, in one embodiment of the present application, if the second device is the device where the first functional function resides, the apparatus 600 may further include: a communication unit configured to receive feedback information sent by the second device, so The feedback information is used to feed back an execution result of the second device executing the first function.

Optionally, in one embodiment of the present application, the determining unit 620 may be further configured to: determine the device where the first functional function is located according to the record information, where the record information is used to record each of the at least one functional function The device where the function is located.

Optionally, in an embodiment of the present application, the apparatus 600 may further include: a communication unit, configured to receive the workflow scheduling information sent by the system.

Optionally, in an embodiment of the present application, the communication unit is specifically configured to: receive the workflow scheduling information sent by the system before the first device leaves the factory.

Optionally, in an embodiment of the present application, the first event includes first information, and the first information is an input of the first functional function.

Optionally, in an embodiment of the present application, the first device and the second device are edge devices.

FIG. 7 is a schematic diagram of a hardware structure of an apparatus for workflow operation according to an embodiment of the present application. The workflow operation apparatus 700 shown in FIG. 7 may be a first device, and the workflow operation apparatus 700 includes a memory 701 , a processor 702 , a communication interface 703 and a bus 704 . Wherein, the memory 701 , the processor 702 , and the communication interface 703 are connected to each other through a bus 704 .

The memory 701 may be a read-only memory (read-only memory, ROM), a static storage device and a random access memory (random access memory, RAM). The memory 701 can store a program. When the program stored in the memory 701 is executed by the processor 702, the processor 702 and the communication interface 703 are used to execute each step of the workflow operation method of the embodiment of the present application.

The processor 702 may adopt a general-purpose CPU, a microprocessor, an application specific integrated circuit (ASIC), a graphics processing unit (GPU), or one or more integrated circuits for executing related programs, In order to realize the functional functions to be executed by the units in the device of the embodiment of the present application, or execute the workflow operation method of the embodiment of the present application.

The processor 702 may also be an integrated circuit chip, which has a signal processing capability. In the implementation process, each step of the workflow operation method in the embodiment of the present application may be completed by an integrated logic circuit of hardware in the processor 702 or instructions in the form of software.

Above-mentioned processor 702 can also be general-purpose processor, digital signal processor (digital signal processing, DSP), ASIC, off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic device, discrete gate or transistor logic devices, discrete hardware components. Various methods, steps, and logic block diagrams disclosed in the embodiments of the present application may be implemented or executed. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like. The steps of the methods disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register. The storage medium is located in the memory 701, and the processor 702 reads the information in the memory 701, and combines its hardware to complete the functions required by the units included in the device of the embodiment of the present application, or execute the workflow operation of the embodiment of the present application method.

The communication interface 703 implements communication between the workflow operation apparatus 700 and other devices or communication networks by using a transceiver device such as but not limited to a transceiver. For example, the apparatus 700 may receive the feedback information sent by the second device through the communication interface 703 .

The bus 704 may include pathways for transferring information between various components of the apparatus 700 (eg, memory 701 , processor 702 , communication interface 703 ) for workflow operations.

It should be noted that although the above-mentioned workflow operation device 700 only shows a memory, a processor, and a communication interface, in the specific implementation process, those skilled in the art should understand that the workflow operation device 700 may also include other necessary devices. Meanwhile, according to specific requirements, those skilled in the art should understand that the workflow operation apparatus 700 may also include hardware devices for implementing other additional functions. In addition, those skilled in the art should understand that the apparatus 700 for workflow operation may only include components necessary to realize the embodiment of the present application, and does not necessarily include all the components shown in FIG. 7 .

The embodiment of the present application also provides a computer-readable storage medium, which stores program code for execution by a device, and the program code includes instructions for executing the steps in the above-mentioned workflow operation method.

The embodiment of the present application also provides a computer program product, the computer program product includes a computer program stored on a computer-readable storage medium, the computer program includes program instructions, and when the program instructions are executed by the computer, the The computer executes the above-mentioned workflow operation method.

The above-mentioned computer-readable storage medium may be a transitory computer-readable storage medium, or a non-transitory computer-readable storage medium.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the device described above can refer to the corresponding process in the foregoing method embodiment, and details are not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined Or it can be integrated into another system, or some features can be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The terms used in the present application are used to describe the embodiments only and are not used to limit the claims. As used in the examples and description of the claims, the singular forms "a" and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. Similarly, the term "and/or" as used in this application is meant to include any and all possible combinations of one or more of the associated listed ones. Additionally, when used in this application, the term "comprising" refers to the presence of stated features, integers, steps, operations, elements, and/or components, but does not exclude one or more other features, integers, steps, operations, The presence or addition of elements, components and/or groupings of these.

The aspects, implementations, implementations or features of the described embodiments can be used alone or in any combination. Aspects of the described embodiments can be implemented by software, hardware or a combination of hardware and software. The described embodiments may also be embodied by a computer-readable medium storing computer-readable code comprising instructions executable by at least one computing device. The computer readable medium can be associated with any data storage device that can store data that can be read by a computer system. Exemplary computer readable media may include read-only memory, random access memory, compact disc read-only memory (CD-ROM), hard disk drive (HDD), digital Video disc (digital video disc, DVD), magnetic tape, and optical data storage device, etc. The computer readable medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

The above technical description may refer to the accompanying drawings, which form a part hereof, and in which are shown by way of description implementations in accordance with the described embodiments. While these embodiments are described in sufficient detail to enable those skilled in the art to practice the embodiments, these embodiments are not limiting; as such, other embodiments can be used and without departing from the scope of the described embodiments Circumstances can also be changed. For example, the order of operations described in the flow diagrams is non-limiting, and thus the order of two or more operations illustrated in and described with respect to the flow diagrams may be changed according to several embodiments. As another example, in several embodiments, one or more operations illustrated in and described with respect to the flowcharts are optional, or may be deleted. Additionally, certain steps or functions may be added to the disclosed embodiments, or the order of two or more steps permuted. All such variations are considered to be encompassed by the disclosed embodiments as well as the claims.

Additionally, terminology was used in the above technical description to provide a thorough understanding of the described embodiments. However, undue detail is not required to implement the described embodiments. Thus, the foregoing description of the embodiments has been presented for purposes of illustration and description. The embodiments presented in the foregoing description, and examples disclosed according to these embodiments, are provided individually to add context and to facilitate understanding of the described embodiments. The above description is not intended to be exhaustive or to limit the described embodiments to the precise form of the application. Several modifications, alternatives, and variations are possible in light of the above teachings. In some instances, well known process steps have not been described in detail in order not to unnecessarily obscure the described embodiments.

The above is only the specific implementation of the embodiment of the present application, but the scope of protection of the embodiment of the present application is not limited thereto. Anyone familiar with the technical field can easily Any changes or substitutions that come to mind should be covered within the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application should be based on the protection scope of the claims.

Claims

A workflow operation method, characterized by comprising:

The first device acquires (110) a workflow, where the workflow is used to indicate at least one functional function called by the event and an execution sequence of the at least one functional function;

After the first device receives the first event, according to the workflow, determine (120) the first function to be called by the first event, the event includes the first event, and the at least one the functional functions include said first functional function;

If the first device is the device where the first functional function is located, the first device calls (130) the first functional function;

If the second device is the device where the first functional function resides, the first device routes (140) the first event to the second device.
The method according to claim 1, wherein the functional functions deployed on the first device are determined according to the resources of the first device, and the functional functions deployed on the second device are determined according to the resources of the first device. 2. The resources of the equipment are determined;

If the resources of the first device are greater than the resources of the second device, more functional functions are deployed on the first device than on the second device.
The method according to claim 1 or 2, wherein if the second device is the device where the first functional function is located, the method further comprises:

The first device receives feedback information sent by the second device, where the feedback information is used to feed back an execution result of the first function executed by the second device.
The method according to any one of claims 1 to 3, wherein the method further comprises:

The first device determines the device where the first functional function is located according to the record information, where the record information is used to record the device where each functional function of the at least one functional function is located.
The method according to any one of claims 1 to 4, wherein the acquiring (110) workflow by the first device includes:

The first device receives workflow scheduling information sent by the system, where the workflow scheduling information identifies the workflow.
The method according to claim 5, wherein the workflow scheduling information sent by the first device receiving system includes:

Before the first device leaves the factory, the first device receives the workflow scheduling information sent by the system.
The method according to any one of claims 1 to 6, wherein the first event includes first information, and the first information is an input of the first functional function.
The method according to any one of claims 1 to 7, wherein the first device and the second device are edge devices.
A workflow operation device (600), characterized in that the device is a first device, comprising:

An acquisition unit (610), configured to acquire a workflow, where the workflow is used to indicate at least one functional function invoked by an event and an execution sequence of the at least one functional function;

A determining unit (620), configured to determine, according to the workflow, a first function to be called by the first event after the first device receives the first event, the event includes the first event , the at least one functional function includes the first functional function;

A calling unit (630), configured to call the first functional function if the first device is the device where the first functional function is located;

A routing unit (640), configured to route the first event to the second device if the second device is the device where the first function resides.
A device for workflow operation, characterized by comprising:

memory (701), for storing programs;

A processor (702), configured to execute the program stored in the memory (701), when the program stored in the memory (701) is executed, the processor (702) is configured to execute the program according to claims 1 to 8. A method of workflow operation as described in any one.
A computer-readable storage medium, characterized in that the computer-readable medium stores program code for execution by a device, and the program code includes a program code for executing the workflow according to any one of claims 1 to 8 An instruction for a step in an action's method.