Workflow management system, method, and electronic device

Abstract

The application discloses a workflow management system, belongs to the technical field of computers, and helps to improve the efficiency of workflow execution. The workflow management system disclosed by the embodiment of the application comprises a workflow engine, a proxy server and a meta universe server. Message interaction between the workflow engine and the meta universe server is realized through the proxy server, so that the workflow engine can send workflow node execution information configured to be executed in the meta universe to the meta universe server in the form of a message, trigger the meta universe server to build an execution environment of the workflow node in the meta universe, and manage the execution of the workflow node in the meta universe. In this way, for the workflow node that needs personnel participation or multi-person interaction, the corresponding digital avatar can be executed in the meta universe, and the convenience and execution efficiency of the workflow execution are improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to workflow management systems, methods, electronic devices, and computer-readable storage media. Background Technology

[0002] A workflow is a computational model of a work process. It represents the logic and rules governing how tasks are organized sequentially within a workflow in a computer model and performs calculations accordingly. The main problem that workflows aim to solve is: to achieve a specific business objective, automatically transfer tasks among multiple participants using computers according to predetermined rules, thereby automating, intelligentizing, and integrating work process management. A workflow organizes a set of tasks to complete a business process: it defines the triggering order and conditions of the tasks. Each task can be completed by one or more software systems, by one or a group of people, or by one or more people collaborating with software systems. A workflow management system is a system used to model, execute, and monitor workflows.

[0003] In existing technologies, the execution efficiency of workflows that require human interaction is limited by the human interaction environment.

[0004] It is evident that existing workflow management systems still require improvement. Summary of the Invention

[0005] This application provides a workflow management system that helps improve workflow execution efficiency.

[0006] In a first aspect, embodiments of this application provide a workflow management system, including:

[0007] A workflow engine for building a model of a workflow and executing the workflow; wherein each workflow includes at least one node, the model is used to indicate at least the nodes included in each workflow and the execution order of the nodes;

[0008] A metaverse server is used to respond to a received workflow execution message by executing the workflow node indicated by the workflow execution message in the metaverse; wherein, the workflow execution message is sent by the workflow engine when it determines that the current node to be executed in the workflow is a node that needs to be executed in the metaverse during the execution of the workflow;

[0009] A proxy server is used to manage message interactions between the workflow engine and the metaverse server.

[0010] Secondly, embodiments of this application provide a workflow management method, including:

[0011] Obtain a model of a pre-established workflow, wherein each workflow includes at least one node, and the model is used to indicate at least the nodes included in each workflow, and the execution order of the nodes;

[0012] According to the execution order, obtain the current node to be executed in the current workflow;

[0013] In response to the fact that the current node to be executed is a node that needs to be executed in the metaverse, a metaverse execution message is generated for the current node to be executed based on the execution information of the current node to be executed;

[0014] The metaverse execution message is sent to a preset proxy server, which encapsulates the metaverse execution message into a workflow execution message and sends the workflow execution message to a preset metaverse server, triggering the metaverse server to execute the currently pending node in the metaverse.

[0015] Thirdly, embodiments of this application also disclose an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the workflow management method described in embodiments of this application.

[0016] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, performs the steps of the workflow management method disclosed in embodiments of this application.

[0017] The workflow management system disclosed in this application uses a proxy server to facilitate message interaction between the workflow engine and the metaverse server. This allows the workflow engine to send execution information of workflow nodes configured to be executed in the metaverse to the metaverse server in the form of messages. The metaverse server then constructs the execution environment for that workflow node within the metaverse and manages its execution. In this way, workflow nodes requiring human participation or multi-user interaction can be executed in the metaverse using corresponding digital avatars, improving the convenience and efficiency of workflow execution.

[0018] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0019] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0020] Figure 1 This is one of the schematic diagrams of the workflow management system structure in Embodiment 1 of this application;

[0021] Figure 2 This is the second schematic diagram of the workflow management system structure in Embodiment 1 of this application;

[0022] Figure 3 This is the third schematic diagram of the workflow management system structure in Embodiment 1 of this application;

[0023] Figure 4 This is the fourth schematic diagram of the workflow management system structure in Embodiment 1 of this application;

[0024] Figure 5 This is a flowchart of the workflow management method in Embodiment 2 of this application;

[0025] Figure 6 This is a schematic diagram of workflow execution data interaction in Embodiment 2 of this application;

[0026] Figure 7 A block diagram schematically illustrates an electronic device for performing the method according to this application; and

[0027] Figure 8 A storage unit for holding or carrying program code implementing the method according to this application is illustrated schematically. Detailed Implementation

[0028] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0029] Example 1

[0030] This application discloses a workflow management system, such as... Figure 1 As shown, the system includes: a workflow engine 110, a proxy server, and a metaverse server 130. The data processing schemes for each component are described below.

[0031] Workflow engine 110 is used to build a model of a workflow and to execute the workflow, each of the workflows including at least one node, the model being used at least to indicate the nodes included in each of the workflows and the execution order of the nodes.

[0032] The workflow engine has three main functions: verifying the current process state: given the current state, check whether the task can be executed effectively; determining user permissions: check whether the current user is allowed to execute the task; and executing the conditional script: after the first two steps, the workflow engine will execute the task. If the execution is successful, it will return success; otherwise, it will return an error and trigger and roll back the changes.

[0033] Workflow engines are a core technology in task assignment software (such as business process management), in which tasks are assigned to different executors while workflow participants exchange data.

[0034] In some embodiments of this application, the workflow engine 110 may include: a modeling module, an operation module, a monitoring module, and a service management module. The modeling module further includes: a process modeling submodule, an organizational relationship modeling submodule, and a rule management submodule, etc.; the operation module further includes: an execution engine, a process management submodule, and a task management submodule, etc.; the monitoring module further includes: a log management module, a business statistics module, etc.; and the service management module further includes: an authorization and authentication module, an organization adaptation module, and a business interface module, etc.

[0035] To help readers understand this solution, the functions and data processing flow of each component of the workflow engine 110 are briefly described below.

[0036] The process modeling submodule is used to define at least one node included in at least one workflow during the workflow design process, and to define the flow order of the at least one node. Here, a node is a workflow node, which is a step or stage in the process. The process modeling submodule can connect one or more nodes to form a workflow; it can also define whether a specified node needs to be executed in the metaverse. In some embodiments of this application, the node that needs to be executed in the metaverse is a node involving human interaction. For example, when designing a workflow for awarding a degree, the workflow node corresponding to the thesis defense stage can be designated as a node that needs to be executed in the metaverse. As another example, when designing a product development workflow, the workflow node corresponding to the brainstorming stage of product development can be designated as a node that needs to be executed in the metaverse.

[0037] The organizational relationship modeling submodule is used to model organizational relationships such as institutions, positions, roles, and authorization relationships. In some embodiments of this application, the organizational relationship modeling submodule is used to set the correspondence between the user identifier in the real world and the digital avatar of the user participating in human interaction in the workflow. In some embodiments of this application, the identity correspondence can be input through the human-computer interaction interface of the workflow engine or imported through a third-party platform or application. In the embodiments of this application, the method of generating the identity correspondence is not limited.

[0038] The rule management submodule is used to set the interaction data rules followed by messages and other data exchanged between the workflow engine and the metaverse server. In some embodiments of this application, the interaction data rules can be edited through the human-computer interaction interface of the workflow engine, or they can be imported through a third-party platform or application. In the embodiments of this application, the method of generating interaction data rules is not limited.

[0039] The execution engine is used to verify the current process status, determine user permissions, and execute the workflow if the conditions are met, that is, to execute the conditional script corresponding to the workflow.

[0040] In the embodiments of this application, during the execution of the workflow, the execution engine determines whether the current node to be executed is a node that needs to be executed in the metaverse. When it is determined that the current node to be executed in the workflow is a node that needs to be executed in the metaverse, the proxy server 120 interacts with the metaverse server 130 to send the execution information of the node that needs to be executed in the metaverse to the metaverse server 130. Then, the metaverse server 130 manages the execution process of the node.

[0041] The physical architecture of the workflow engine 110 can be found in the prior art, and will not be described again in the embodiments of this application.

[0042] Proxy server 120 is used to manage message interaction between the workflow engine and the metaverse server. Proxy server 120 receives and sends messages bidirectionally. For example, after receiving a message from metaverse server 130, proxy server 120 repackages the message according to preset rules and sends it to workflow engine 110; or, after receiving a message from workflow engine 110, proxy server 120 repackages the message according to preset rules and sends it to metaverse server 130.

[0043] In some embodiments of this application, such as Figure 2 As shown, the system also includes a storage module 140, which has a signal connection with the workflow engine 110 and the proxy server 120.

[0044] The storage module 140 is used to store the interaction data rules between the workflow engine and the metaverse server. For example, after setting the interaction data rules, the rule management submodule (not shown in the figure) of the workflow engine 110 can store the interaction data rules in the storage module 140 for access by the proxy server 120. In some embodiments of this application, the interaction data rules can be used to indicate, for example, message format, field meaning, message or instruction meaning, message naming rules, etc.

[0045] The storage module 140 is also used to store the identity correspondence between real-world users and their digital avatars in the metaverse. For example, after the organizational relationship modeling submodule (not shown in the figure) of the workflow engine 110 sets the identity correspondence, it can store the identity correspondence in the storage module 140 for access by the proxy server 120.

[0046] In some embodiments of this application, managing the message interaction between the workflow engine and the metaverse server includes: the proxy server parsing and encapsulating the messages between the workflow engine and the metaverse server according to the interaction data rules, and, during the parsing and encapsulation, performing user identity conversion according to the identity correspondence.

[0047] For example, the proxy server 120 obtains the interaction data rules and the identity correspondence from the storage module 140. Then, it parses the message sent by the workflow engine 110 (hereinafter referred to as the "first message") according to the interaction data rules to obtain the information carried in the first message. The first message includes a workflow execution message. In some embodiments of this application, the workflow execution message carries information about the currently pending node, wherein the information includes: the node identifier of the currently pending node, the execution scenario information matched by the currently pending node (such as the meeting room number), the user identifier of the real-world user executing the currently pending node (such as the participant's number in the workflow system), and the execution event matched by the currently pending node (such as a meeting). After parsing the first message, the proxy server 120 can obtain information such as the node identifier, execution event, the real-world user identifier of the participant, and the execution scenario. Next, the proxy server 120 further determines the digital identity in the metaverse corresponding to each user identifier carried in the first message based on the identity correspondence, and encapsulates the node identifier, execution scenario, execution event and digital identity information into a second message according to the interaction data rules, and sends the second message to the metaverse server 130.

[0048] For example, proxy server 120 obtains the interaction data rules and the identity correspondence from storage module 140. Then, it parses the message sent by metaverse server 130 (hereinafter referred to as the "third message") according to the interaction data rules to obtain the information carried in the third message. The third message includes an execution result feedback message. In some embodiments of this application, the execution result feedback message carries the execution result of the node, wherein the execution result includes at least: node identifier, information of the digital avatar in the metaverse executing the node (such as an account number in the metaverse), and node execution result. After parsing the third message, proxy server 120 can obtain the node identifier, digital avatar information, and execution result. Next, proxy server 120 further determines the user identifier of the user in the real world corresponding to the digital avatar in the third message according to the identity correspondence, and encapsulates the node identifier, user identifier, execution result, and other information into a fourth message according to the interaction data rules, and sends the fourth message to workflow engine 110.

[0049] In some embodiments of this application, the metaverse server 130 includes a user module, an object module, a message module, and a region module, with each module responsible for implementing different functions. For example, the user module manages digital avatars; the object module manages objects (such as furniture, tools, etc.) and the digital avatars' assets; the message module processes messages in the metaverse; and the region module manages various regions in the metaverse, such as a square area of ​​A×A, with one or more regions constituting the execution environment of a node. The various modules work together to enable the metaverse to function.

[0050] In some embodiments of this application, the functions of the metaverse server 130 can be distributed across multiple physical devices or implemented on a single physical device. That is, the metaverse server 130 can be a standalone machine or a server cluster. In the embodiments of this application, the physical form of the metaverse server 130 is not limited.

[0051] For specific implementation methods of the metaverse server 130 described in this application embodiment, please refer to the prior art, which will not be repeated here.

[0052] The improvement of the metaverse server 130 described in this application embodiment over the metaverse server in the prior art is that it adds message interaction with the proxy server, and, in view of the characteristics of the workflow, in the process of managing execution events, for workflow nodes with time window attributes, it adds a process of managing the execution events corresponding to the nodes in the time dimension, so as to ensure the smooth execution of workflows with execution time requirements.

[0053] In some embodiments of this application, the metaverse server 130 is configured to execute the workflow node indicated by the workflow execution message in the metaverse in response to receiving the workflow execution message; wherein, the workflow execution message is sent by the workflow engine when it determines that the current node to be executed in the workflow is a node that needs to be executed in the metaverse during the execution of the workflow. For example, during the operation of the metaverse, the metaverse server 130 receives messages sent by the proxy server 120 in real time or periodically, and after receiving the workflow execution message sent by the proxy server 120, executes the workflow node matching the node information in the metaverse according to the node information carried in the workflow execution message.

[0054] In some embodiments of this application, the workflow execution message carries information about the currently pending node, wherein the information includes: execution scenario information matched by the currently pending node, digital avatar information of the real-world user executing the currently pending node in the metaverse, and execution event matched by the currently pending node; the step of executing the workflow node indicated by the workflow execution message in the metaverse in response to receiving the workflow execution message includes: the metaverse server, in response to receiving the workflow execution message, renders the execution scenario of the currently pending node in the metaverse according to the execution scenario information, and notifies the real-world user matched by the digital avatar information to execute the execution event in the metaverse through the digital avatar. For example, after receiving the workflow execution message sent by the proxy server 120, the metaverse server 130 renders the execution scenario (e.g., meeting room) in the metaverse according to the execution event (e.g., meeting), execution scenario, and participating digital avatars (e.g., the digital avatars of the meeting participants) carried in the workflow execution message, and notifies the meeting participants to operate their digital avatars through the metaverse to attend the meeting in the meeting room.

[0055] In some embodiments of this application, the metaverse server 130 can send a notification message to the client of the metaverse that logs into the metaverse account through the metaverse account matched by the digital avatar. The notification message is used to notify the real-world user corresponding to the digital avatar to perform the execution event through the digital avatar in the metaverse.

[0056] In some embodiments of this application, the metaverse server 130 is further configured to, after the execution event is completed, generate an execution result feedback message for the previous node to be executed based on the execution result of the execution event, and send the execution result feedback message to the proxy server. Taking a meeting as an example, when a user in the real world completes a meeting event in the metaverse through a digital avatar, they can trigger a meeting end event through the metaverse client. After receiving the meeting end event, the metaverse server 130 generates a meeting execution result feedback message and then sends the generated execution result feedback message to the proxy server 120. In some embodiments of this application, the execution result feedback message may include: node identifier, execution result, digital avatar information, etc.

[0057] In some embodiments of this application, the workflow execution message carries information about the currently pending node, wherein the information includes: execution scenario information and time window information matched by the currently pending node, digital identity information of the real-world user executing the currently pending node in the metaverse, and execution event matched by the currently pending node; the step of executing the workflow node indicated by the workflow execution message in the metaverse in response to receiving the workflow execution message includes: the metaverse server, in response to receiving the workflow execution message, rendering the execution scenario of the currently pending node in the metaverse according to the execution scenario information, and notifying the real-world user matched by the digital identity information to execute the execution event in the metaverse through the digital identity within the time limit indicated by the time window information.

[0058] Accordingly, the metaverse server is further configured to, when the execution event is not completed within the timeframe indicated by the time window information, generate an execution result feedback message for the previously pending node based on the execution result of the execution event, and send the execution result feedback message to the proxy server. In this case, the execution result of the execution event indicates that the execution event is not completed.

[0059] Correspondingly, the proxy server 120 is also configured to respond to the execution result feedback message by parsing and encapsulating the execution result feedback message, and send the message generated by parsing and encapsulation to the workflow engine. For example, after receiving the execution result feedback message sent by the metaverse server 130, the proxy server 120 parses the execution result feedback message (referred to as "the fifth message") according to the interaction data rules, and obtains the node identifier, digital identity information, and execution result carried in the execution result feedback message (i.e., the fifth message); further, the proxy server 120 obtains the user identifier in the real world corresponding to the digital identity information according to the identity correspondence, and re-encapsulates the node identifier, user identifier, and execution result into a sixth message according to the interaction data rules, and then the proxy server 120 sends the sixth message to the workflow engine 110.

[0060] This completes the process of executing one node of the workflow in the metaverse.

[0061] Furthermore, since the workflow system and the metaverse environment are two independent systems, they need to communicate via a proxy for interface or message conversion to enable mutual access. Therefore, a proxy server 120 is set up between the workflow engine 110 and the metaverse server 130. The proxy server 120 enables mutual access between the workflow engine 110 and the proxy server by performing data encapsulation operations such as interface conversion and message conversion.

[0062] The following section, using the specific structure of the proxy server 120 as an example, elaborates on the message interaction process between the workflow engine 110 and the metaverse server 130.

[0063] In some embodiments of this application, such as Figure 3 As shown, the proxy server 120 may include a communication module 310 and a message conversion module 320. The communication module 310 is used to receive messages sent by the workflow engine 110 and / or the metaverse server 130. The message conversion module 320 is used to parse and encapsulate the messages received by the communication module 310 according to the interaction data rules, and, during the parsing and encapsulation, to convert user identity information according to the identity correspondence. The communication module 310 is also used to send the messages generated by the parsing and encapsulation to the workflow engine 110 and / or the metaverse server 130.

[0064] The communication module 310 is a bidirectional message sending and receiving module, used to receive messages sent by the workflow engine 110 and the metaverse server 130, and to send messages to the metaverse server 130 based on triggers from the workflow engine 110, and vice versa. Further, after receiving messages from the workflow engine 110 and the metaverse server 130, the communication module 310 transmits the received messages to the message conversion module 320. The message conversion module 320 determines whether the recipient of the message is the workflow engine 110 or the metaverse server 130, then parses and encapsulates the message to obtain a message recognizable by the recipient, and sends the encapsulated message to the recipient.

[0065] In some embodiments of this application, the acquired message is parsed and encapsulated according to the interaction data rules, and during the parsing and encapsulation, user identity conversion is performed according to the identity correspondence, including: determining the target recipient of the message; in response to the target recipient being a metaverse server, parsing and encapsulating the acquired message according to the interaction data rules, and during the parsing and encapsulation, converting the user identifier carried in the message into the digital identity information of the real-world user to which the user identifier belongs in the metaverse according to the identity correspondence; in response to the target recipient being a workflow engine, parsing and encapsulating the acquired message according to the interaction data rules, and during the parsing and encapsulation, converting the digital identity information carried in the message into the user identifier of the real-world user to which the digital identity information belongs according to the identity correspondence.

[0066] Taking the message conversion module 320 processing a message received by the metaverse server 130 as an example, firstly, the message conversion module 320 parses the message transmitted by the communication module 310 according to the aforementioned interaction data rules, obtaining information such as the workflow node identifier, the real-world user identifier of the user executing the current workflow node, the execution scenario information, and the execution event carried in the message; then, the message conversion module 320 obtains the digital identity information corresponding to the user identifier according to the aforementioned identity correspondence, and repackages the obtained digital identity information, the parsed node identifier, the execution event, the execution scenario, and other information into a message to be sent to the metaverse server 130 according to the aforementioned interaction data rules; finally, the repackaged message is sent to the metaverse server 130 through the communication module 310.

[0067] Taking the message conversion module 320 processing a message received by the workflow engine 110 as an example, firstly, the message conversion module 320 parses the message transmitted by the communication module 310 according to the aforementioned interaction data rules, obtaining the workflow node identifier, the digital identity information of the user executing the current workflow node in the metaverse, the execution result, etc., carried in the message; then, the message conversion module 320 obtains the user identifier in the real world corresponding to the digital identity information according to the aforementioned identity correspondence, and repackages the obtained user identifier, parsed node identifier, execution result, etc., into a message to be sent to the workflow engine 110 according to the aforementioned interaction data rules; finally, the repackaged message is sent to the workflow engine 110 through the communication module 310.

[0068] In some embodiments of this application, in order to improve the message processing efficiency of the proxy server 120, such as Figure 4 As shown, the proxy server 120 further includes: a communication module 410, a message preprocessing module 420, and a message conversion module 430. The communication module 410 is used to receive messages sent by the workflow engine 110 and / or the metaverse server 130. The message preprocessing module 420 is used to store the messages received by the communication module 410 into a pre-created message queue. The message conversion module 430 is used to retrieve messages from the message queue, parse and encapsulate the retrieved messages according to the interaction data rules, and, during parsing and encapsulation, perform user identity conversion according to the identity correspondence. The communication module 410 is also used to send the messages generated by the parsing and encapsulation to the workflow engine 110 and / or the metaverse server 130.

[0069] The communication module 410 is a bidirectional message sending and receiving module, used to receive messages sent by the workflow engine 110 and the metaverse server 130, and to send messages to the metaverse server 130 and vice versa, triggered by the workflow engine 110 and the metaverse server 130, respectively. Further, after receiving messages from the workflow engine 110 and the metaverse server 130, the communication module 410 transmits the received messages to the message preprocessing module 420, which stores the messages in a pre-created message queue. The message conversion module 430 sequentially retrieves messages from the message queue, determines whether the recipient is the workflow engine 110 or the metaverse server 130, parses and encapsulates the message to obtain a message recognizable by the recipient, and then sends the encapsulated message to the recipient.

[0070] In some embodiments of this application, the message conversion module 430 can retrieve messages from the message queue according to a first-in-first-out strategy, or it can retrieve messages from the queue position pointed to by the current pointer using a message queue pointer.

[0071] The specific method by which the message conversion module 430 parses and encapsulates messages is described above and will not be repeated here.

[0072] In some embodiments of this application, the pre-created message queues may include multiple queues, for example, one or more: a metaverse message queue for storing messages sent by the workflow engine to the metaverse server; and one or more workflow message queues for storing messages sent by the metaverse server to the workflow engine; the message preprocessing module 420 is further configured to store messages whose target recipient is the metaverse server 130 in the metaverse message queue, and to store messages whose target recipient is the workflow engine 110 in the workflow message queue. In some embodiments of this application, the target recipient of a message can be determined based on message attributes such as message name.

[0073] Correspondingly, the message conversion module 430 is used to obtain messages from the workflow message queue and the metaverse message queue, and to parse and encapsulate the obtained messages according to the interaction data rules, and to perform user identity conversion according to the identity correspondence during the parsing and encapsulation.

[0074] To further improve message processing efficiency and enhance the stability of the proxy server 120, multiple message conversion sub-modules can be set in the message conversion module 430, with each message conversion sub-module processing messages in a message queue.

[0075] In some embodiments of this application, the message conversion module 430 further includes: a first message conversion submodule and a second message conversion submodule (not shown in the figure). The first message conversion submodule is used to obtain messages from the metaverse message queue, parse and encapsulate the obtained messages according to the interaction data rules, and, during parsing and encapsulation, convert the user identifier carried in the message into the digital identity information of the real-world user to which the user identifier belongs in the metaverse according to the identity correspondence relationship. The second message conversion submodule is used to obtain messages from the workflow message queue, parse and encapsulate the obtained messages according to the interaction data rules, and, during parsing and encapsulation, convert the digital identity information carried in the message into the user identifier of the real-world user to which the digital identity information belongs according to the identity correspondence relationship. In the embodiments of this application, the user identifier refers to the user identifier of a real-world user in the workflow system.

[0076] For details on how the message conversion submodule parses and encapsulates messages, please refer to the relevant descriptions above, which will not be repeated here.

[0077] In some embodiments of this application, the message received by the communication module 410 carries event type and / or time window information. The message preprocessing module 420 is further configured to determine the processing priority of the message based on the event type and / or time window information carried in the message. The message preprocessing module 420 is further configured to insert messages whose target recipient is the metaverse server 130 into the metaverse message queue and store them in the queue position that matches the processing priority, and to insert messages whose target recipient is the workflow engine 110 into the workflow message queue and store them in the queue position that matches the processing priority.

[0078] For example, after receiving a message, the communication module 410 transmits the received message to the message preprocessing module 420. When the message preprocessing module 420 determines that the message is a message sent by the workflow engine 110 to the metaverse server 130, it determines that the message needs to be stored in the metaverse message queue. Further, the message preprocessing module 420 determines the processing priority of the message based on the event type and / or time window information carried in the message, and stores the message in the metaverse message queue at the queue position matching the determined processing priority. Taking the storage of messages in the message queue in descending order of priority as an example, the message can be inserted into the appropriate position in the metaverse message queue by comparing the processing priority of the message with the processing priorities of messages already stored in the metaverse message queue.

[0079] Referring to the above description, the message preprocessing module 420 can insert the message sent by the metaverse server 130 to the workflow engine 110 into the appropriate position in the workflow message queue, so that the message is processed by the message conversion module 430 at the appropriate time.

[0080] For a specific example, taking the messages in the metaverse message queue arranged from highest to lowest processing priority as an example, when the message preprocessing module 420 receives message M1 sent by the workflow engine 110 to the metaverse server 130, which carries the event type "signature" and the time window information "2 PM today", the message preprocessing module 420 sets the processing priority of message M1 to P1 and stores message M1 in the Nth queue position in the metaverse message queue; when the message preprocessing module 420 receives message M2 sent by the workflow engine 110 to the metaverse server 130, which carries the event type "signature" and the time window information "1 PM today", the message preprocessing module 420 determines the processing priority of message M2 to P2, and P2 is higher than P1, and stores message M2 in a position before the Nth queue position in the metaverse message queue. In this way, messages with higher processing priority will be parsed and encapsulated by the message conversion module 430 first, and then sent to the target receiver. Correspondingly, workflow nodes corresponding to messages with higher processing priority will be sent to the metaverse server 130 first, thereby avoiding delays in the execution of workflow nodes that need to be executed as soon as possible due to message backlog in the message queue, and ensuring smooth execution of the workflow.

[0081] In some embodiments of this application, the processing priority of a message can be set according to one or more message parameters, such as the urgency of message processing time and the event type. For example, the processing priority of a message with a larger time window can be set lower than that of a message with a smaller time window; for another example, the processing priority of an important event can be set higher than that of an ordinary event; and for yet another example, for messages with the same time window, the processing priority of the message can be further set according to the event type.

[0082] The workflow management system disclosed in this application includes: a workflow engine, a proxy server, and a metaverse server. The workflow engine is used to establish workflow models and execute the workflows. Each workflow includes at least one node. The model is used to indicate at least the nodes included in each workflow and the execution order of the nodes. The metaverse server is used to execute the workflow node indicated by the workflow execution message in the metaverse in response to receiving a workflow execution message. The workflow execution message is sent by the workflow engine when it determines that the currently pending node of the workflow needs to be executed in the metaverse during workflow execution. The proxy server manages the message interaction between the workflow engine and the metaverse server. The workflow management system implements message interaction between the workflow engine and the metaverse server through the proxy server, thereby enabling the workflow engine to send the execution information of workflow nodes configured to be executed in the metaverse to the metaverse server in the form of messages, triggering the metaverse server to construct the execution environment of the workflow node in the metaverse and manage the execution of the workflow node in the metaverse. In this way, workflow nodes that require human participation or multi-person interaction can be executed through corresponding digital avatars in the metaverse, improving the convenience and efficiency of workflow execution.

[0083] Example 2

[0084] This application discloses a workflow management method, which is applied to, for example, Figure 1 The workflow management system shown. Figure 5 As shown, the workflow management method includes steps 510 to 540.

[0085] For the composition of the workflow management system and the functions and specific implementation schemes of each component, please refer to Example 1, which will not be repeated in this example.

[0086] Step 510: Obtain a pre-established workflow model, wherein each workflow includes at least one node, and the model is used to indicate at least the nodes included in each workflow and the execution order of the nodes.

[0087] In some embodiments of this application, a workflow engine pre-establishes models of one or more workflows. Each workflow may include one or more nodes, and the model not only sets the nodes included in each workflow, but also sets the execution order of the nodes included in each workflow.

[0088] In some embodiments of this application, for nodes that require multi-person interaction or human participation, the workflow engine can be configured to execute in the metaverse.

[0089] The structure and functions of the workflow engine, as well as the specific implementation methods for establishing workflows, are described in Example 1 and will not be repeated here.

[0090] Step 520: Obtain the current node to be executed in the current workflow according to the execution order.

[0091] During the execution of the current workflow, the workflow engine retrieves each node of the current workflow in the order of node execution and uses the retrieved node as the current node to be executed.

[0092] Step 530: In response to the fact that the current node to be executed is a node that needs to be executed in the metaverse, generate a metaverse execution message for the current node to be executed based on the execution information of the current node to be executed.

[0093] In some embodiments of this application, before executing the current node to be executed, the workflow engine first determines whether the current node to be executed needs to be executed in the metaverse. If so, it generates a metaverse execution message based on the node identifier, participants, execution scenario, execution event, time window and other configuration information of the current node to be executed.

[0094] Step 540: The metaverse execution message is sent to a preset proxy server, which encapsulates the metaverse execution message into a workflow execution message and sends the workflow execution message to a preset metaverse server, triggering the metaverse server to execute the currently pending node in the metaverse.

[0095] Afterwards, the workflow engine sends the generated metaverse execution messages to a pre-defined proxy server (such as...). Figure 1 The proxy server 120 in the middle parses the metaverse execution message, and according to the parsing result, encapsulates the information required by the metaverse to execute the current node to be executed according to the preset data interaction rules, and generates a workflow execution message.

[0096] For details on how the proxy server parses and encapsulates the messages sent by the workflow engine, please refer to the relevant description in Embodiment 1, which will not be repeated here.

[0097] Subsequently, the proxy server sends the encapsulated and generated workflow execution message to a preset metaverse server (such as...). Figure 1 Metaverse Server 130 (in the middle).

[0098] After receiving the workflow execution message, the metaverse server executes the currently pending node in the metaverse.

[0099] The workflow execution message carries information about the currently pending node, including: execution scenario information matched by the currently pending node, digital identity information of the real-world user executing the currently pending node in the metaverse, and execution event matched by the currently pending node; the metaverse server executes the currently pending node in the metaverse, including: in response to receiving the workflow execution message, the metaverse server renders the execution scenario of the currently pending node in the metaverse according to the execution scenario information, and notifies the real-world user matched by the digital identity information to execute the execution event in the metaverse through the digital identity.

[0100] In some embodiments of this application, after sending the metaverse execution message to a preset proxy server, the method further includes: receiving the execution result for the current node to be executed from the metaverse server.

[0101] In some embodiments of this application, the metaverse server is further configured to generate an execution result feedback message for the previous node to be executed based on the execution result of the execution event after the execution event is completed, and send the execution result feedback message to the proxy server;

[0102] The proxy server is also configured to respond to the execution result feedback message by parsing and encapsulating the execution result feedback message, and send the message generated by parsing and encapsulation to the workflow engine.

[0103] For details on how the proxy server parses and encapsulates the messages sent by the metaverse server, please refer to the relevant description in Embodiment 1, which will not be repeated here.

[0104] In some embodiments of this application, the workflow management system further includes:

[0105] The storage module is used to store the interaction data rules between the workflow engine and the metaverse server;

[0106] The storage module is also used to store the identity correspondence between real-world users and their digital avatars in the metaverse;

[0107] The proxy server is also used to parse and encapsulate messages between the workflow engine and the metaverse server according to the interaction data rules, and to perform user identity conversion according to the identity correspondence during the parsing and encapsulation process.

[0108] In some embodiments of this application, the proxy server further includes: a communication module, a message preprocessing module, and a message conversion module, wherein...

[0109] The communication module is used to receive messages sent by the workflow engine and / or the metaverse server;

[0110] The message preprocessing module is used to store the messages received by the communication module into a pre-created message queue;

[0111] The message conversion module is used to obtain messages from the message queue, parse and encapsulate the obtained messages according to the interaction data rules, and, during the parsing and encapsulation, convert user identities according to the identity correspondence.

[0112] The communication module is also used to send the parsed and encapsulated messages to the workflow engine and / or the metaverse server.

[0113] In some embodiments of this application, the pre-created message queue includes:

[0114] The metaverse message queue is used to store messages sent by the workflow engine to the metaverse server;

[0115] A workflow message queue is used to store messages sent by the metaverse server to the workflow engine;

[0116] The message preprocessing module is further configured to store messages whose target recipient is the metaverse server into the metaverse message queue, and to store messages whose target recipient is the workflow engine into the workflow message queue.

[0117] The message conversion module is used to obtain messages from the workflow message queue and the metaverse message queue, and to parse and encapsulate the obtained messages according to the interaction data rules. In addition, during the parsing and encapsulation, user identity conversion is performed according to the identity correspondence.

[0118] In some embodiments of this application, the message conversion module further includes: a first message conversion submodule and a second message conversion submodule, wherein,

[0119] The first message conversion submodule is used to obtain messages from the metaverse message queue, and to parse and encapsulate the obtained messages according to the interaction data rules. In addition, during the parsing and encapsulation, the user identifier carried in the message is converted into the digital identity information of the real-world user to which the user identifier belongs in the metaverse according to the identity correspondence.

[0120] The second message conversion submodule is used to obtain messages from the workflow message queue, parse and encapsulate the obtained messages according to the interaction data rules, and, during the parsing and encapsulation, convert the digital identity information in the metaverse carried in the message into the user identifier of the real-world user to which the digital identity information belongs, according to the identity correspondence.

[0121] In some embodiments of this application, the message received by the communication module carries event type and / or time window information; correspondingly,

[0122] The message preprocessing module is further configured to determine the processing priority of the message based on the event type and / or the time window information carried in the message;

[0123] The message preprocessing module is further configured to insert messages whose target recipient is the metaverse server into the metaverse message queue at a queue position that matches the processing priority for storage, and to insert messages whose target recipient is the workflow engine into the workflow message queue at a queue position that matches the processing priority for storage.

[0124] The following is combined Figure 6 The data interaction diagram shown further illustrates the implementation of the workflow management method disclosed in this application.

[0125] like Figure 6 As shown, first, the workflow engine executes step 610.

[0126] Step 610: Establish the workflow model.

[0127] Step 620: The workflow engine selects the current workflow.

[0128] Next, the workflow engine retrieves a pre-built workflow model and selects the current workflow.

[0129] Step 630: The workflow engine obtains the current node to be executed in the current workflow.

[0130] Next, the workflow engine retrieves the current node to be executed in the current workflow according to the execution order of each node in the current workflow.

[0131] Step 640: The workflow engine determines whether the current node to be executed needs to be executed in the metaverse. If yes, proceed to step 650; otherwise, proceed to step 6110.

[0132] Step 650: The workflow engine generates a metaverse execution message for the current node to be executed based on the execution information of the current node to be executed, and sends the metaverse execution message to the proxy server.

[0133] Step 660: The proxy server encapsulates the metaverse execution message into a workflow execution message and sends the workflow execution message to the preset metaverse server.

[0134] Step 670: In response to the workflow execution message, the metaverse server executes the currently pending node in the metaverse.

[0135] Step 680: The metaverse server generates an execution result feedback message for the previous node to be executed and sends the execution result feedback message to the proxy server.

[0136] Step 690: In response to the execution result feedback message, the proxy server parses and encapsulates the execution result feedback message, and sends the message generated by parsing and encapsulation to the workflow engine.

[0137] Step 6100: The workflow engine receives the execution result of the currently pending node.

[0138] This completes the interaction process of one node executing a workflow in the metaverse.

[0139] Then, the workflow engine determines whether to continue executing subsequent nodes of the current workflow based on the execution result of the current node to be executed.

[0140] Step 6110: The workflow engine executes the currently pending node.

[0141] If the currently pending node does not need to be executed in the metaverse, then the workflow engine executes the currently pending node. Afterwards, the workflow engine determines whether to continue executing subsequent nodes of the current workflow based on the local execution result of the currently pending node.

[0142] The workflow management method disclosed in this application improves the convenience and efficiency of workflow execution by obtaining a pre-established workflow model, wherein each workflow includes at least one node, the model is used to indicate at least the nodes included in each workflow, and the execution order of the nodes; according to the execution order, the current node to be executed in the current workflow is obtained; in response to the current node to be executed being a node that needs to be executed in the metaverse, a metaverse execution message is generated for the current node to be executed based on the execution information of the current node to be executed; the metaverse execution message is sent to a preset proxy server, so that the proxy server encapsulates the metaverse execution message into a workflow execution message and sends the workflow execution message to a preset metaverse server, triggering the metaverse server to execute the current node to be executed in the metaverse, thereby improving the convenience and efficiency of workflow execution.

[0143] The workflow management method disclosed in this application configures workflow nodes requiring human participation or multi-user interaction as workflow nodes to be executed in a metaverse, and sends the execution information of such workflow nodes to a metaverse server. This triggers the metaverse server to construct the execution environment for the workflow node in the metaverse and manage the execution of the workflow node in the metaverse. In this way, workflow nodes requiring human participation can be executed in the metaverse through the digital avatars of the corresponding personnel, improving the convenience and efficiency of workflow execution.

[0144] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the method embodiments, since they are based on system implementation, the specific implementation methods of each step are basically similar to the implementation methods of the corresponding modules or sub-modules in the system, so the descriptions are relatively simple; relevant parts can be referred to the descriptions in the system embodiments.

[0145] The workflow management system and method provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method of this application and its core idea. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the idea of ​​this application. Therefore, the content of this specification should not be construed as a limitation of this application.

[0146] The system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0147] The various component embodiments of this application can be implemented in hardware, or as software modules running on one or more processors, or a combination thereof. Those skilled in the art will understand that microprocessors or digital signal processors (DSPs) can be used in practice to implement some or all of the functions of some or all of the components in the electronic device according to the embodiments of this application. This application can also be implemented as a device or system program (e.g., a computer program and computer program product) for performing part or all of the methods described herein. Such an implementation of this application can be stored on a computer-readable medium, or can be in the form of one or more signals. Such signals can be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

[0148] For example, Figure 7 An electronic device is shown that can implement the methods according to this application. The electronic device may be a PC, mobile terminal, personal digital assistant, tablet computer, etc. The electronic device conventionally includes a processor 710 and a memory 720, and program code 730 stored in the memory 720 and executable on the processor 710. When the processor 710 executes the program code 730, it implements the methods described in the above embodiments. The memory 720 may be a computer program product or a computer-readable medium. The memory 720 may be an electronic memory such as flash memory, EEPROM (Electrically Erasable Programmable Read-Only Memory), EPROM, hard disk, or ROM. The memory 720 has a storage space 7201 for the program code 730 of a computer program for performing any of the method steps described above. For example, the storage space 7201 for the program code 730 may include various computer programs for implementing the various steps in the above methods. The program code 730 is computer-readable code. These computer programs can be read from or written to one or more computer program products. These computer program products include program code carriers such as hard disks, CDs, memory cards, or floppy disks. The computer program includes computer-readable code that, when executed on an electronic device, causes the electronic device to perform the method according to the above embodiments.

[0149] This application also discloses a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the workflow management method as described in Embodiment 1 of this application.

[0150] Such a computer program product can be a computer-readable storage medium, which can have the same characteristics as... Figure 7 The memory 720 in the illustrated electronic device is similarly arranged with storage segments, storage spaces, etc. Program code can be stored, for example, in a compressed form on the computer-readable storage medium. The computer-readable storage medium is typically as shown in the reference... Figure 8 The portable or fixed storage unit is described above. Typically, the storage unit includes computer-readable code 730', which is code read by a processor and, when executed by the processor, implements the various steps of the method described above.

[0151] The terms "an embodiment," "embodiment," or "one or more embodiments" as used herein mean that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment of this application. Furthermore, please note that the examples of the phrase "in one embodiment" do not necessarily all refer to the same embodiment.

[0152] Numerous specific details are set forth in the specification provided herein. However, it will be understood that embodiments of this application may be practiced without these specific details. In some instances, well-known methods, structures, and techniques have not been shown in detail so as not to obscure the understanding of this specification.

[0153] In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. This application can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims enumerating several systems, several of these systems may be embodied by the same item of hardware. The use of the words first, second, and third, etc., does not indicate any order. These words can be interpreted as names.

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

Claims

1. A workflow management system, characterized in that, include: A workflow engine for building a model of a workflow and executing the workflow; wherein each workflow includes at least one node, the model is used to indicate at least the nodes included in each workflow and the execution order of the nodes; A metaverse server is used to respond to a received workflow execution message by executing the workflow node indicated by the workflow execution message in the metaverse; wherein, the workflow execution message is sent by the workflow engine when it determines that the current node to be executed in the workflow is a node that needs to be executed in the metaverse during the execution of the workflow; A proxy server is used to manage message interactions between the workflow engine and the metaverse server; The workflow execution message carries information about the currently pending node, wherein the information includes: execution scenario information matching the currently pending node, the digital identity information of the real-world user executing the currently pending node in the metaverse, and the execution event matching the currently pending node; the step of executing the workflow node indicated by the workflow execution message in the metaverse in response to receiving the workflow execution message includes: In response to receiving the workflow execution message, the metaverse server renders the execution scene of the current node to be executed in the metaverse according to the execution scene information, and notifies the real-world user whose digital identity information matches to execute the execution event in the metaverse through the digital identity. The storage module is used to store the interaction data rules between the workflow engine and the metaverse server; The storage module is also used to store the identity correspondence between real-world users and their digital avatars in the metaverse; Managing message interactions between the workflow engine and the metaverse server includes: The proxy server parses and encapsulates the messages between the workflow engine and the metaverse server according to the interaction data rules, and performs user identity conversion according to the identity correspondence during the parsing and encapsulation process.

2. The system according to claim 1, characterized in that, The metaverse server is further configured to, after the execution event is completed, generate an execution result feedback message for the previous node to be executed based on the execution result of the execution event, and send the execution result feedback message to the proxy server; The proxy server is also configured to respond to the execution result feedback message by parsing and encapsulating the execution result feedback message, and send the message generated by parsing and encapsulation to the workflow engine.

3. The system according to claim 1, characterized in that, The proxy server further includes: a communication module, a message preprocessing module, and a message conversion module, wherein... The communication module is used to receive messages sent by the workflow engine and / or the metaverse server; The message preprocessing module is used to store the messages received by the communication module into a pre-created message queue; The message conversion module is used to obtain messages from the message queue, parse and encapsulate the obtained messages according to the interaction data rules, and, during the parsing and encapsulation, convert user identities according to the identity correspondence. The communication module is also used to send the parsed and encapsulated messages to the workflow engine and / or the metaverse server.

4. The system according to claim 3, characterized in that, The pre-created message queue includes: The metaverse message queue is used to store messages sent by the workflow engine to the metaverse server; A workflow message queue is used to store messages sent by the metaverse server to the workflow engine; The message preprocessing module is further configured to store messages whose target recipient is the metaverse server into the metaverse message queue, and to store messages whose target recipient is the workflow engine into the workflow message queue. The message conversion module is used to obtain messages from the workflow message queue and the metaverse message queue, and to parse and encapsulate the obtained messages according to the interaction data rules. In addition, during the parsing and encapsulation, user identity conversion is performed according to the identity correspondence.

5. The system according to claim 4, characterized in that, The message conversion module further includes: a first message conversion submodule and a second message conversion submodule, wherein, The first message conversion submodule is used to obtain messages from the metaverse message queue, and to parse and encapsulate the obtained messages according to the interaction data rules. In addition, when parsing and encapsulating, the user identifier carried in the message is converted into the digital identity information of the real-world user to which the user identifier belongs in the metaverse according to the identity correspondence. The second message conversion submodule is used to obtain messages from the workflow message queue, parse and encapsulate the obtained messages according to the interaction data rules, and, during the parsing and encapsulation, convert the digital identity information in the metaverse carried in the message into the user identifier of the real-world user to which the digital identity information belongs, according to the identity correspondence.

6. The system according to claim 4, characterized in that, The message received by the communication module carries event type and / or time window information. The message preprocessing module is further configured to determine the processing priority of the message based on the event type and / or the time window information carried in the message; The message preprocessing module is further configured to insert messages whose target recipient is the metaverse server into the metaverse message queue at a queue position that matches the processing priority for storage, and to insert messages whose target recipient is the workflow engine into the workflow message queue at a queue position that matches the processing priority for storage.

7. A workflow management method, characterized in that, include: Obtain a model of a pre-established workflow, wherein each workflow includes at least one node, and the model is used to indicate at least the nodes included in each workflow, and the execution order of the nodes; According to the execution order, obtain the current node to be executed in the current workflow; In response to the fact that the current node to be executed is a node that needs to be executed in the metaverse, a metaverse execution message is generated for the current node to be executed based on the execution information of the current node to be executed; The metaverse execution message is sent to a preset proxy server, which encapsulates the metaverse execution message into a workflow execution message and sends the workflow execution message to a preset metaverse server, triggering the metaverse server to execute the currently pending node in the metaverse; The workflow execution message carries information about the currently pending node, including: execution scenario information matching the currently pending node, the digital identity information of the real-world user executing the currently pending node in the metaverse, and the execution event matching the currently pending node; sending the workflow execution message to a preset metaverse server to trigger the metaverse server to execute the currently pending node in the metaverse includes: The workflow execution message is sent to a preset metaverse server, which triggers the metaverse server to render the execution scene of the current node to be executed in the metaverse according to the execution scene information, and notifies the real-world user whose digital identity information matches to execute the execution event in the metaverse through the digital identity.

8. An electronic device, comprising a memory, a processor, and program code stored in the memory and executable on the processor, characterized in that, When the processor executes the program code, it implements the workflow management method of claim 7.

9. A computer-readable storage medium having program code stored thereon, characterized in that, When the program code is executed by the processor, it implements the steps of the workflow management method of claim 7.

Images