Workflow recommendation method and device and storage medium

CN118922843APending Publication Date: 2024-11-08SIEMENS AG
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280093874.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-29
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In requirements engineering, the mapping relationship between requirement entities and workflow entities results in low recommendation efficiency due to inconsistent labels and different granularities, making it difficult to achieve accurate matching.

Method used

By establishing a deterministic mapping relationship between requirement entities and workflow entities, using the mapping relationship between ‘use’ and ‘used’ to establish connections, candidate workflow entities are recommended.

Benefits of technology

It improves the accuracy and efficiency of workflow recommendations, realizes flexible matching of demand entities, and has high feasibility and scalability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118922843A_ABST
    Figure CN118922843A_ABST
Patent Text Reader

Abstract

The invention discloses a workflow recommendation method and device and a computer readable storage medium. The method comprises the following steps: receiving a current demand entity; based on a pre-established deterministic mapping relationship between each demand entity and each workflow entity, searching the deterministic mapping relationship by taking the current demand entity as a keyword to obtain at least one candidate workflow entity which establishes a deterministic mapping relationship with the current demand entity; in the deterministic mapping relationship, the demand entity and the corresponding workflow entity establish a connection through a mapping relationship of "use" and "used"; and recommending the candidate workflow entity. According to the method, accurate workflow recommendation can be realized.
Need to check novelty before this filing date? Find Prior Art

Description

Workflow recommendation method, device and storage medium Technical Field

[0001] The present application relates to the field of computers, and in particular to a workflow recommendation method, device, and computer-readable storage medium.

[0002] Background of the Invention

[0003] With the development of computers, requirements engineering has also gained widespread popularity. Requirements engineering is a discipline that applies proven techniques and methods to conduct requirements analysis, identify customer needs, help analysts understand the problem, and define all external characteristics of the target system. Requirements engineering uses appropriate tools and notations to systematically describe the system to be developed, its behavioral characteristics, and associated constraints, forming a requirements document that supports the evolving needs of users.

[0004] One of the goals of requirements engineering is to generate workflows by providing requirements such as use case descriptions and functional requirements. A key point in achieving this goal is to map requirement entities (such as tasks and use cases) to workflow entities (such as components, skills, and features). A typical approach is keyword mapping, in which requirement entities and workflow entities are tagged with the same label (i.e., keyword) to create a mapping relationship between them.

[0005] For example, Figure 1 shows an example keyword mapping. As shown in Figure 1, the requirement entity "Performance Improvement" is labeled with "Performance Monitoring" and "Availability Monitoring," and the skill entity "Performance Analysis" is labeled with "Performance Monitoring" and "OEE Monitoring." While the "Performance Monitoring" label can match the requirement and skill, the "Availability Monitoring" and "OEE Monitoring" labels cannot. However, common sense suggests that OEE (Overall Equipment Effectiveness) represents availability, making the two synonyms.

[0006] Since requirement entities and workflow entities are usually provided by different user groups, and different user groups may set different labels for the same meaning or set the same label for different meanings, natural language keywords such as synonyms and polysemy will reduce their feasibility in keyword mapping. In addition, the granularity of each entity may be different, and the entity categories may partially overlap or differ from each other. For example, different tasks may have the same skills, while the same task may have different skills; different use cases may have the same edge applications, while the same use case may have different edge applications. This makes it difficult to correctly label entities with a unified set of labels.

[0007] Therefore, those skilled in the art are still working on finding other workflow recommendation solutions.

[0008] Summary of the Invention

[0009] In view of this, embodiments of the present application provide, on the one hand, a workflow recommendation method, and on the other hand, a workflow recommendation device and a computer-readable storage medium, which can implement workflow recommendation in demand engineering and improve the flexibility and efficiency of workflow recommendation.

[0010] To solve the above technical problems, the technical solution of this application is implemented as follows:

[0011] A workflow recommendation method comprises: receiving a current demand entity; based on a pre-established deterministic mapping relationship between each demand entity and each workflow entity, searching the deterministic mapping relationship with the current demand entity as a keyword to obtain at least one candidate workflow entity having a deterministic mapping relationship with the current demand entity; in the deterministic mapping relationship, the demand entity and the corresponding workflow entity are connected through a mapping relationship of "using" and "being used"; and recommending the candidate workflow entity.

[0012] A workflow recommendation device comprises: a human-computer interaction module and a workflow entity search module; wherein the human-computer interaction module is used to receive a current demand entity and provide the current demand entity to the workflow entity search module; and recommend candidate workflow entities from the workflow search module; the workflow entity search module is used to search for a deterministic mapping relationship between each demand entity and each workflow entity based on a pre-established deterministic mapping relationship between the current demand entity and the workflow entity, using the current demand entity as a keyword, to obtain at least one candidate workflow entity having a deterministic mapping relationship with the current demand entity, and provide the at least one candidate workflow entity to the human-computer interaction module; in the deterministic mapping relationship, the demand entity and the corresponding workflow entity are connected through a mapping relationship of "using" and "being used".

[0013] A workflow recommendation device includes at least one memory and at least one processor, wherein: the at least one memory is used to store a computer program; the at least one processor is used to call the computer program stored in the at least one memory to execute the workflow recommendation method described in any of the above embodiments.

[0014] A computer-readable storage medium stores a computer program thereon; the computer program can be executed by a processor and implements the workflow recommendation method described in any one of the above embodiments.

[0015] As can be seen from the above technical solutions, in this application, since a deterministic mapping relationship is established between the demand entity and the workflow entity, a definite and accurate workflow entity can be recommended for the current demand entity, and the efficiency and effectiveness of the workflow recommendation are improved.

[0016] In addition, since deterministic mapping between any number of requirement entities and workflow entities can be achieved and new mapping relationships can be extended, it has high feasibility and scalability.

[0017] Furthermore, since the deterministic mapping relationship paradigm between requirement entities and workflow entities can be applied to the establishment of mapping relationships between any requirement entities and workflow entities, it is universal.

[0018] BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to better understand the present application, the embodiments of the present application will be described in detail below with reference to the accompanying drawings so that those skilled in the art can better understand the above and other features and advantages of the present application. In the accompanying drawings:

[0020] FIG1 is an exemplary flowchart of a workflow recommendation method in an embodiment of the present application.

[0021] FIG. 2A and FIG. 2B are schematic diagrams of the basic mapping relationship between the requirement entity and the workflow entity in an example of the present application.

[0022] Figure 3A is a schematic diagram of a deterministic mapping relationship from use cases to edge applications based on the basic mapping relationship shown in Figure 2A in an example of this application.

[0023] FIG3B is a schematic diagram of searching for edge applications of the current use case based on the deterministic mapping relationship shown in FIG3A .

[0024] FIG3C is a schematic diagram of searching for edge applications of the current use case based on the deterministic mapping relationship shown in FIG3A .

[0025] FIG4A is a schematic diagram of a deterministic mapping relationship from use cases to functional blocks based on the basic mapping relationship shown in FIG2B in an example of the present application.

[0026] FIG. 4B is a schematic diagram of searching for a functional block of a current task of a current use case based on the deterministic mapping relationship shown in FIG. 4A .

[0027] FIG5 is an exemplary structural diagram of a workflow recommendation device in an embodiment of the present application.

[0028] FIG6 is an exemplary structural diagram of another workflow recommendation device in an embodiment of the present application.

[0029] The accompanying drawings are numerals as follows:

[0030] Meaning of labels 101-104 Steps EA1, EA2, EA3, EAN1 Edge applications SK1, SK2, SKN2 Skills UC1, UC2, UC3, UCN3, UCN8 Use cases T1, T2, TN4, TN7 Tasks

[0031] FB1, FB2, FB3, FBN5 functional blocks DV1, DV2, DVN6 device 51 human-computer interaction module 52 workflow entity search module 61 memory 62 processor 63 bus

[0032] Methods of implementing this application

[0033] In an embodiment of the present application, in order to avoid various problems caused by keyword mapping, it is considered to establish a deterministic mapping relationship between the demand entity and the workflow entity, and recommend a corresponding workflow entity for the current demand entity based on the deterministic mapping relationship.

[0034] In order to make the purpose, technical solutions and advantages of this application more clear, the technical solutions of this application are described in detail below with reference to the accompanying drawings and examples.

[0035] FIG1 is an exemplary flow chart of a workflow recommendation method in an embodiment of the present application. As shown in FIG1 , the method may include the following steps:

[0036] Step 101: Pre-establish a deterministic mapping relationship between each requirement entity and each workflow entity. In the deterministic mapping relationship, the requirement entity and the corresponding workflow entity are connected through a "use" and "used by" mapping relationship.

[0037] For example, FIG2A and FIG2B respectively show schematic diagrams of a basic mapping relationship between a requirement entity and a workflow entity in an example of the present application.

[0038] In Figure 2A, the case where the demand entity includes a use case UC and a task T, and the workflow entity includes an edge application EA and a skill SK is taken as an example. As shown in Figure 2A, in the basic mapping relationship shown in Figure 2A, a mapping relationship of "include" and "included" is set between the use case UC representing the demand entity and the task T included in the use case UC, a mapping relationship of "provide" and "be provided" is set between the edge application EA representing the workflow entity and the skill SK provided by the edge application EA, and a mapping relationship of "use" and "be used" is set between the task T and the skill SK. In Figure 2A, P means provide, C means include, and U means use. Among them, the mapping relationship of "include" and "be included", the mapping relationship of "provide" and "be provided", and the mapping relationship of "use" and "be used" are all deterministic mapping relationships.

[0039] In Figure 2B, the case where the requirement entity includes a use case UC and a task T, and the workflow entity includes a function block FB and a device DV is taken as an example. As shown in Figure 2B, in the basic mapping relationship shown in Figure 2B, a mapping relationship of "include" and "included" is set between the use case UC representing the requirement entity and the task T included in the use case UC, a mapping relationship of "support" and "supported" is set between the function block FB representing the workflow entity and the device DV supported by the function block FB, and a mapping relationship of "use" and "be used" is set between the task T and the device DV. In Figure 2B, S represents support, C represents inclusion, and U represents use. Among them, the mapping relationship of "include" and "be included", the mapping relationship of "support" and "be supported", and the mapping relationship of "use" and "be used" are all deterministic mapping relationships.

[0040] Figure 3A illustrates a deterministic mapping relationship from use cases to edge applications based on the basic mapping relationship shown in Figure 2A. As shown in Figure 3A, on the workflow entity side, the first edge application EA1 provides the first skill SK1; the second edge application EA2 provides the first skill SK1 and the second skill SK2; the third edge application EA3 provides the second skill SK2; ...; the N1th edge application EAN1 provides the first skill SK1 and the N2nd skill SKN2. On the requirement entity side, the first use case UC1 includes the second task T2 and the Nth task TN; the second use case UC2 includes the first task T1; the third use case UC2 includes the second task T2 and the N3rd task TN3; ...; the N4th use case UCN4 includes the N3rd task TN3. Between the workflow entity and the requirement entity, the first task T1 uses the N2nd skill SKN2; the second task T2 uses the first skill SK1 and the second skill SK2; and the N3rd task TN3 uses the first skill SK1. In Figure 3A, P stands for Provide, C stands for Include, and U stands for Use. It can be seen that through this deterministic mapping relationship, different edge applications with various skills and different use cases with various tasks can be connected.

[0041] Figure 4A shows a schematic diagram of an example deterministic mapping relationship from use cases to function blocks based on the basic mapping relationship shown in Figure 2B. As shown in Figure 4A, on the workflow entity side, the first function block FB1 supports the first device DV1, the second device DV2, and the (N6)th device DVN6; the second function block FB2 supports the first device DV1 and the second device DV2; the third function block FB3 supports the second device DV2 and the (N6)th device DVN6; ...; the (N5)th function block FBN5 supports the first device DV1 and the (N6)th device DVN6. On the requirement entity side, the first use case UC1 includes the first task T1 and the (N7)th task TN7; the second use case UC2 includes the (N7)th task TN7; the third use case UC2 includes the first task T1 and the second task T2; ...; the (N8)th use case UCN8 includes the second task T2. Between the workflow entity and the requirement entity, the first task T1 uses the second device DV2 and the N6th device DVN6; the second task T2 uses the first device DV1 and the second device DV2; and the N7th task TN7 uses the second device DV1. In Figure 4A, S stands for support, C stands for inclusion, and U stands for use. This deterministic mapping relationship allows for connecting different functional blocks supporting various devices and different use cases with various tasks.

[0042] In specific implementations, the deterministic mapping relationship between each requirement entity and each workflow entity can be created by the workflow provider based on the various application requirements and requirement entities provided by the requirement provider and the various workflow entities provided by itself. Alternatively, the requirement provider can create the mapping relationship based on the various workflow entities provided by the workflow provider and the various application requirements and requirement entities provided by itself. Alternatively, the mapping relationship can be created by a third party based on the various application entities provided by the requirement provider and the various workflow entities provided by the workflow provider. This is not limited here.

[0043] Step 102: Receive the current demand entity.

[0044] In this embodiment, the current demand entity may be provided by any user, for example, a demand provider in an actual application, or other users of the test system.

[0045] Taking the basic mapping relationship shown in Figures 2A and 2B as an example, the current use case or the current task of the current use case representing the current demand entity can be received in this step. For example, for the deterministic mapping relationship shown in Figure 3A, the current demand entity can be the third use case UC3 (i.e., the current use case), or it can be the first task T1 of the second use case UC2 (i.e., the current task of the current use case), etc. For another example, for the deterministic mapping relationship shown in Figure 4A, the current demand entity can be the second use case UC2 (i.e., the current use case), or it can be the N7th task TN7 of the second use case UC2 (i.e., the current task of the current use case).

[0046] Step 103: Based on the deterministic mapping relationships between each requirement entity and each workflow entity, the current requirement entity is used as a keyword to search for the deterministic mapping relationships to obtain candidate workflow entities that have a deterministic mapping relationship with the current requirement entity. Typically, at least one candidate workflow entity is obtained.

[0047] Taking the deterministic mapping relationship shown in Figures 2A and 3A as an example, in this step, the deterministic mapping relationship can be searched using the current use case or the current task of the current use case as a keyword to obtain candidate edge applications that provide the skills used by the current use case or the current task of the current use case.

[0048] The specific query process can be:

[0049] Find [Edge Apps], Condition with {; Find [Edge Apps] that meet the following conditions:

[0050] 1. [Edge Apps] provide [Skills]; [Edge Apps] provide [Skills], and

[0051] 2. [Skills] are used by [Tasks]&&; [Skills] are used by [Tasks], and

[0052] 3.[Tasks]are contained in[Use Cases]; [Tasks] are contained in [Use Cases].

[0053] }

[0054] If the current demand entity is the third use case UC3, the following query process can be used:

[0055] Find [Edge Apps], Condition with {; Find [Edge Apps] that meet the following conditions:

[0056] 1. [Edge Apps] provide [Skills]; [Edge Apps] provide [Skills], and

[0057] 2. [Skills] are used by [Tasks]&&; [Skills] are used by [Tasks], and

[0058] 3.[Tasks]are contained in <uc3>; [Task] is included in [Third Use Case].

[0059] }

[0060] Accordingly, as shown by the solid line portion in FIG3B , a first edge application EA1 , a second edge application EA2 , a third edge application EA3 and an N1 th edge application EAN1 are obtained.

[0061] For the case where the current demand entity is the first task T1 of the second use case UC2, the following query process can be used:

[0062] Find [Edge Apps], Condition with {; Find [Edge Apps] that meet the following conditions:

[0063] 1. [Edge Apps] provide [Skills]; [Edge Apps] provide [Skills], and

[0064] 2. [Skills] are used by [T1]; [Skills] are used by [First Task], and

[0065] 3.[T1]are contained in <uc2>; [First Task] is included in [Second Use Case].

[0066] }

[0067] Accordingly, as shown by the solid line in FIG3C , an N1th edge application EAN1 is obtained.

[0068] Taking the deterministic mapping relationship shown in Figures 2B and 4A as an example, in this step, the deterministic mapping relationship can be searched using the current use case or the current task of the current use case as a keyword to obtain candidate functional blocks of the equipment used to support the current use case or the current task of the current use case.

[0069] The specific query process can be:

[0070] Find [Function Blocks], Condition with {; Search [Function Blocks] that meet the following conditions:

[0071] 1. [Function Blocks] support [Devices] &&; [Function Blocks] support [Devices], and

[0072] 2. [Devices] are used by [Tasks]&&; [Device] is used by [Task], and

[0073] 3.[Tasks]are contained in[Use Cases]; [Tasks] are contained in [Use Cases].

[0074] }

[0075] If the current demand entity is the second use case UC2, the following query process can be used:

[0076] Find [Function Blocks], Condition with {; Search [Function Blocks] that meet the following conditions:

[0077] 1. [Function Blocks] support [Devices] &&; [Function Blocks] support [Devices], and

[0078] 2. [Devices] are used by [Tasks]&&; [Device] is used by [Task], and

[0079] 3.[Tasks]are contained in <uc2>; [Task] is included in [Second Use Case].

[0080] }

[0081] Accordingly, as shown by the solid line portion in FIG. 4B , a first function block FB1 , a second function block FB2 and a third function block FB3 are obtained.

[0082] For the case where the current demand entity is the N7th task TN7 of the second use case UC2, the following query process can be used:

[0083] Find [Function Blocks], Condition with {; Search [Function Blocks] that meet the following conditions:

[0084] 1. [Function Blocks] support [Devices] &&; [Function Blocks] support [Devices], and

[0085] 2. [Devices] are used by [TN7]; [Devices] are used by [Task N7], and

[0086] 3.[TN7]are contained in <uc2>; [Task N7] is included in the [Second Use Case].

[0087] }

[0088] Correspondingly, since the second use case only contains one task, namely the N7th task TN7, when the deterministic mapping relationship shown in Figure 4A is searched using the second use case or the N7th task of the second use case as the keyword, the same search result will be obtained, namely, as shown in the solid line part in Figure 4B, the first function block FB1, the second function block FB2 and the third function block FB3 are obtained.

[0089] Step 104: recommend the candidate workflow entity.

[0090] With respect to the deterministic mapping relationships shown in FIG. 2A and FIG. 3A , in this embodiment, the candidate edge application may be recommended as a workflow corresponding to the current demand entity.

[0091] With respect to the deterministic mapping relationships shown in FIG. 2B and FIG. 4A , in this embodiment, the candidate functional blocks may be recommended as the workflow corresponding to the current demand entity.

[0092] In this embodiment, in order to maintain the continuous mapping relationship expansion and update of the deterministic relationship, if the current required entity is used as a keyword to search the deterministic mapping relationship, and it is determined that the current required entity is not in the deterministic mapping relationship, the current required entity can be provided to the deterministic mapping relationship builder, and the deterministic mapping relationship builder maps the current required entity to an existing workflow entity or a new workflow entity, and forms a new mapping record, and updates the new mapping record to the deterministic mapping relationship. For example, for the deterministic mapping relationship shown in Figures 2A and 3A, if the current use case or the current task of the current use case is used as a keyword to search the deterministic mapping relationship, and it is determined that the current use case or the current task of the current use case is not in the deterministic mapping relationship, the current use case or the current task of the current use case is provided to the deterministic mapping relationship builder, and the deterministic mapping relationship builder maps the current use case or the current task of the current use case to an existing skill or new skill of an existing edge application or to a skill provided by a new edge application, and forms a new mapping record, and updates the new mapping record to the deterministic mapping relationship. For another example, for the deterministic mapping relationship shown in Figures 2B and 4A, if the deterministic mapping relationship is searched using the current use case or the current task of the current use case as a keyword, and it is determined that the current use case or the current task of the current use case is not in the deterministic mapping relationship, the current use case or the current task of the current use case is provided to the deterministic mapping relationship builder, and the deterministic mapping relationship builder maps the current use case or the current task of the current use case to an existing device or new device supported by an existing functional block or to a device supported by a new functional block, and forms a new mapping record, and updates the new mapping record to the deterministic mapping relationship.

[0093] Of course, the demand provider can also continuously propose new demand entities, and the deterministic mapping relationship builder will map the new demand entity to an existing workflow entity or a new workflow entity, and form a new mapping record, and update the new mapping record to the deterministic mapping relationship.

[0094] Furthermore, to enable the deterministic relationship to learn and maintain continuous mapping relationship ranking updates, embodiments of the present invention may receive a user's selection result from the candidate workflow entities and, based on the selection result, increase the weight of the mapping relationship between the user-selected candidate workflow entity and the current required entity. Furthermore, based on the selection result, the weight of the mapping relationship between the user-unselected candidate workflow entity and the current required entity may be decreased.

[0095] Specifically, for the deterministic mapping relationships shown in Figures 2A and 3A, a selection result of a user selecting from the candidate edge applications may be received; based on the selection result, a weight may be added to the mapping relationship between the candidate edge application selected by the user and the current demand entity. Furthermore, based on the selection result, the weight may be reduced for the mapping relationship between the candidate edge application not selected by the user and the current demand entity. For the deterministic mapping relationships shown in Figures 2B and 4A, a selection result of a user selecting from the candidate function blocks may be received; based on the selection result, a weight may be added to the mapping relationship between the candidate function block selected by the user and the current demand entity. Furthermore, based on the selection result, the weight may be reduced for the mapping relationship between the candidate function block not selected by the user and the current demand entity.

[0096] For example, an initial weight, such as 100%, can be set for each newly established deterministic mapping relationship between a requirement entity and a workflow entity. When a user receives recommended candidate workflow entities, he or she can select or deselect one or more recommended workflow entities. If a workflow entity is selected, a reward can be fed back to the mapping relationship between the selected workflow entity and the input requirement entity. A simple reward equation is shown in the following equation (1):

[0097] R updated =R current +Award n %≤100% (1)

[0098] The 100% on the right side of formula (1) is used to limit the maximum value of the weight to only 100%.

[0099] Furthermore, if a workflow entity is not selected, a penalty can be fed back to the mapping relationship between the selected workflow entity and the input requirement entity. A simple penalty equation is shown in the following equation (2):

[0100] R updated =R current -Award m %>0% (2)

[0101] The 0% on the right side of formula (2) is used to limit the minimum value of the weight to not be lower than 0%.

[0102] Among them, R current is the current weight, R updated is the updated weight, Award is a reward and punishment coefficient greater than 1, n is the number of times the user has selected, and m is the number of times the user has not selected.

[0103] Having described the workflow recommendation method in the embodiments of the present invention in detail above, the workflow recommendation apparatus in the embodiments of the present invention will now be described in detail. The workflow recommendation apparatus in the embodiments of the present invention can be used to implement the workflow recommendation method in the embodiments of the present invention. For details not disclosed in the embodiments of the apparatus, please refer to the corresponding description in the embodiments of the method.

[0104] FIG5 is an exemplary structural diagram of a workflow recommendation device according to an embodiment of the present invention. As shown in FIG5 , the device may include: a human-computer interaction module 51 and a workflow entity search module 52 .

[0105] The human-computer interaction module is configured to receive a current demand entity, provide the current demand entity to the workflow entity search module 52, and recommend candidate workflow entities from the workflow search module 52. The workflow entity search module 52 is configured to search a pre-established deterministic mapping relationship between each demand entity and each workflow entity, using the current demand entity as a keyword, to obtain at least one candidate workflow entity that has a deterministic mapping relationship with the current demand entity, and provide the at least one candidate workflow entity to the human-computer interaction module 51. In the deterministic mapping relationship, a demand entity and a corresponding workflow entity are connected through a "use" and "used by" mapping relationship.

[0106] Among them, in the deterministic mapping relationship shown in Figures 2A and 3A, a mapping relationship of "include" and "is included" is set between the use case representing the demand entity and the task included in the use case, a mapping relationship of "provide" and "is provided" is set between the edge application representing the workflow entity and the skills provided by the edge application, and a mapping relationship of "use" and "is used" is set between the task and the skill.

[0107] In the deterministic mapping relationships shown in Figures 2B and 4A, a mapping relationship of "include" and "is included" is set between the use case representing the requirement entity and the task included in the use case, a mapping relationship of "support" and "is supported" is set between the function block representing the workflow entity and the device supported by the function block, and a mapping relationship of "use" and "is used" is set between the task and the device.

[0108] In one embodiment, when the human-computer interaction module 51 receives a search failure indication from the workflow entity search module 52 (including failure to receive a candidate edge application from the workflow entity search module 52 within a set time), the human-computer interaction module 51 may provide the current demand entity to a deterministic mapping relationship builder, and the deterministic mapping relationship builder maps the current demand entity to an existing workflow entity or a new workflow entity, and forms a new mapping record, and provides the new mapping record to the workflow entity search module 52, and the workflow entity search module 52 updates the new mapping record to the deterministic mapping relationship.

[0109] In one embodiment, the human-computer interaction module 51 further receives a selection result from the user, selecting from the candidate workflow entities, and provides the selection result to the workflow entity search module 52. The workflow entity search module 52 is further configured to increase the weight of the mapping relationship between the candidate workflow entity selected by the user and the currently required entity based on the selection result. Furthermore, the workflow entity search module 52 may also decrease the weight of the mapping relationship between the candidate workflow entity not selected by the user and the currently required entity based on the selection result.

[0110] In fact, the workflow recommendation device provided by this embodiment of the present application can be implemented in various ways. For example, the workflow recommendation device can be compiled into a plug-in installed in a smart terminal by using an application programming interface that complies with specific rules, or it can be packaged into an application for users to download and use.

[0111] When compiled as a plug-in, the workflow recommendation device can be implemented in various plug-in formats, such as ocx, dll, and cab. The workflow recommendation device provided by this implementation of the present application can also be implemented using specific technologies, such as Flash plug-in technology, RealPlayer plug-in technology, MMS plug-in technology, MIDI plug-in technology, or ActiveX plug-in technology.

[0112] The workflow recommendation method provided by this implementation of the present application can be stored in various storage media in an instruction storage manner or an instruction set storage manner. These storage media include, but are not limited to, floppy disks, optical disks, DVDs, hard disks, flash memory, USB flash memory, CF cards, SD cards, MMC cards, SM cards, memory sticks, and xD cards.

[0113] In addition, the workflow recommendation method provided by this embodiment of the present application can also be applied to flash memory (Nand-flash) based storage media, such as USB flash drives, CF cards, SD cards, SDHC cards, MMC cards, SM cards, memory sticks and xD cards.

[0114] It should be clear that the operating system operating in the computer can implement the functions of any of the above embodiments not only by executing the program code read by the computer from the storage medium, but also by using instructions based on the program code to implement part or all of the actual operations.

[0115] For example, Figure 6 is an exemplary structural diagram of another workflow recommendation device in an embodiment of the present application. This device can be used to perform the method shown in Figure 1 or to implement the device shown in Figure 5. As shown in Figure 6, the device may include at least one memory 61 and at least one processor 62. In addition, it may also include other components, such as communication ports, input / output controllers, network communication interfaces, etc. These components communicate via a bus 63, etc.

[0116] At least one memory 61 is used to store computer programs. In one example, the computer program can be understood to include the various modules of the apparatus shown in FIG5 . Furthermore, at least one memory 61 can store an operating system, etc. Operating systems include, but are not limited to, Android operating system, Symbian operating system, Windows operating system, Linux operating system, etc.

[0117] At least one processor 62 is configured to invoke a computer program stored in at least one memory 61 to execute the workflow recommendation method described in the examples of this application. The processor 62 may be a CPU, a processing unit / module, an ASIC, a logic module, or a programmable gate array, and may receive and send data via a communication port.

[0118] The input / output controller has a display and an input device, and is used to input, output and display relevant data as a human-computer interaction module.

[0119] It should be understood that "and / or" used herein is intended to include any and all possible combinations of one or more of the associated listed items.

[0120] The number of the embodiments of the present application is only used for description and does not represent the advantages of the embodiments.

[0121] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A workflow recommendation method, characterized in that: include: Receive current demand entity (102); Based on a pre-established deterministic mapping relationship between each demand entity and each workflow entity, the deterministic mapping relationship is searched using the current demand entity as a keyword to obtain at least one candidate workflow entity (103) having a deterministic mapping relationship with the current demand entity; in the deterministic mapping relationship, the demand entity and the corresponding workflow entity are connected through a "use" and "used by" mapping relationship; The candidate workflow entity is recommended (104).

2. The workflow recommendation method according to claim 1, characterized in that: Each demand entity includes a use case and a task, and each workflow entity includes an edge application and a skill; the current demand entity includes: a current use case or a current task of the current use case; In the deterministic mapping relationship, a "include" and "is included" mapping relationship is set between the use case representing the requirement entity and the task included in the use case, a "provide" and "is provided" mapping relationship is set between the edge application representing the workflow entity and the skill provided by the edge application, and a "use" and "is used" mapping relationship is set between the task and the skill; The step of searching for the deterministic mapping relationship using the current demand entity as a keyword to obtain a workflow entity having a deterministic mapping relationship with the current demand entity includes: searching for the deterministic mapping relationship using the current use case or the current task of the current use case as a keyword to obtain at least one candidate edge application that provides the skills used by the current use case or the current task of the current use case.

3. The workflow recommendation method according to claim 2, characterized in that: The searching for the deterministic mapping relationship using the current use case as a keyword includes: Search for [Edge Application] that meets the following conditions: [Edge applications] provide [skills], and [Skill] is used by [Task], and The task is included in the current use case. The searching for the deterministic mapping relationship using the current task of the current use case as a keyword includes: Search for [Edge Application] that meets the following conditions: [Edge applications] provide [skills], and [Skill] is used by [Current Task], and The [Current Task] is included in the [Current Use Case].

4. The workflow recommendation method according to claim 1, wherein: Each requirement entity includes a use case and a task, and each workflow entity includes a function block and a device; the current requirement entity includes: a current use case or a current task of the current use case; In the deterministic mapping relationship, a "include" and "is included" mapping relationship is set between the use case representing the requirement entity and the task included in the use case, a "support" and "is supported" mapping relationship is set between the function block representing the workflow entity and the device supported by the function block, and a "use" and "is used" mapping relationship is set between the task and the device; The step of searching for the deterministic mapping relationship using the current demand entity as a keyword to obtain a workflow entity having a deterministic mapping relationship with the current demand entity includes: searching for the deterministic mapping relationship using the current use case or the current task of the current use case as a keyword to obtain at least one candidate functional block of a device used to support the current use case or the current task of the current use case.

5. The workflow recommendation method according to claim 4, characterized in that: The searching for the deterministic mapping relationship using the current use case as a keyword includes: Search for [Function Block] that meets the following conditions: [Function Block] supports [Device], and [Device] is used by [Task], and The task is included in the current use case. The searching for the deterministic mapping relationship using the current task of the current use case as a keyword includes: Search for [Function Block] that meets the following conditions: [Function Block] supports [Device], and [Device] is used by [Current Task], and The [Current Task] is included in the [Current Use Case].

6. The workflow recommendation method according to any one of claims 1 to 5, characterized in that: Further including: After searching the deterministic mapping relationship with the current demand entity as the keyword, when it is determined that the current demand entity is not in the deterministic mapping relationship, the current demand entity is provided to the deterministic mapping relationship builder, and the deterministic mapping relationship builder maps the current demand entity to an existing workflow entity or a new workflow entity, and forms a new mapping record, and updates the new mapping record to the deterministic mapping relationship.

7. The workflow recommendation method according to any one of claims 1 to 5, characterized in that: Further including: receiving a selection result of a user selecting from the candidate workflow entities; According to the selection result, a weight is added to the mapping relationship between the candidate workflow entity selected by the user and the current demand entity.

8. The workflow recommendation method according to claim 7, characterized in that: Further including: According to the selection result, the weight of the mapping relationship between the candidate workflow entity not selected by the user and the current demand entity is reduced.

9. A workflow recommendation device, characterized in that: include: Human-computer interaction module (51) and workflow entity search module (52); wherein, The human-computer interaction module (51) is used to receive a current demand entity, provide the current demand entity to the workflow entity search module (52), and recommend candidate workflow entities from the workflow search module (52); The workflow entity search module (52) is used to search for a deterministic mapping relationship between each demand entity and each workflow entity based on a pre-established deterministic mapping relationship between each demand entity and each workflow entity, using the current demand entity as a keyword, to obtain at least one candidate workflow entity that has a deterministic mapping relationship with the current demand entity, and provide the at least one candidate workflow entity to the human-computer interaction module (51); in the deterministic mapping relationship, the demand entity and the corresponding workflow entity are connected through a mapping relationship of "using" and "being used".

10. The workflow recommendation device according to claim 9, characterized in that: Each demand entity includes a use case and a task, and each workflow entity includes an edge application and a skill; the current demand entity includes: a current use case or a current task of the current use case; In the deterministic mapping relationship, a "include" and "is included" mapping relationship is set between the use case representing the requirement entity and the task included in the use case, a "provide" and "is provided" mapping relationship is set between the edge application representing the workflow entity and the skill provided by the edge application, and a "use" and "is used" mapping relationship is set between the task and the skill; The workflow entity search module (52) searches for the deterministic mapping relationship using the current use case or the current task of the current use case as a keyword to obtain at least one candidate edge application that provides the skills used by the current use case or the current task of the current use case.

11. The workflow recommendation device according to claim 9, characterized in that: Each requirement entity includes a use case and a task, and each workflow entity includes a function block and a device; the current requirement entity includes: a current use case or a current task of the current use case; In the deterministic mapping relationship, a "include" and "is included" mapping relationship is set between the use case representing the requirement entity and the task included in the use case, a "support" and "is supported" mapping relationship is set between the function block representing the workflow entity and the device supported by the function block, and a "use" and "is used" mapping relationship is set between the task and the device; The workflow entity search module (52) searches for the deterministic mapping relationship using the current use case or the current task of the current use case as a keyword to obtain at least one candidate function block of a device used to support the current use case or the current task of the current use case.

12. The workflow recommendation device according to any one of claims 9 to 11, characterized in that: When the human-computer interaction module (51) receives a search failure indication from the workflow entity search module, it provides the current demand entity to the deterministic mapping relationship builder, and the deterministic mapping relationship builder maps the current demand entity to an existing workflow entity or a new workflow entity, and forms a new mapping record, and provides the new mapping record to the workflow entity search module (52), so that the workflow entity search module (52) updates the new mapping record to the deterministic mapping relationship.

13. The workflow recommendation device according to any one of claims 9 to 11, characterized in that: The human-computer interaction module (51) further receives a selection result of a user selecting from the candidate workflow entities, and provides the selection result to the workflow entity search module; The workflow entity search module (52) further increases the weight of the mapping relationship between the candidate workflow entity selected by the user and the current required entity according to the selection result, and reduces the weight of the mapping relationship between the candidate workflow entity not selected by the user and the current required entity.

14. A workflow recommendation device, characterized in that: The invention comprises at least one memory (61) and at least one processor (62), wherein: The at least one memory (61) is used to store a computer program; The at least one processor (62) is configured to call a computer program stored in the at least one memory (61) to execute the workflow recommendation method according to any one of claims 1 to 8.

15. A computer-readable storage medium having a computer program stored thereon; characterized in that: The computer program can be executed by a processor and implements the workflow recommendation method according to any one of claims 1 to 8.