Workflow-based digital asset processing system, method, equipment and medium

Abstract

The invention provides a workflow-based digital asset processing system, method, equipment and medium, and the system comprises a trigger, a querier and an executor, the trigger is used as a starting node of a workflow, the querier is used as a query node of the workflow, and the executor is used as an execution node of the workflow; the trigger is configured to start a task workflow of the target digital assets when a trigger configuration event of the target digital assets is detected; the querier is configured to screen out a flow entity related to the task workflow of the target digital asset from the asset database based on a task triggering type corresponding to the task workflow of the target digital asset; and the executor is configured to execute corresponding function operation on the flow entity related to the task workflow of the target digital asset. Therefore, task workflows of different target digital assets are effectively processed, and the asset processing efficiency is improved.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to the field of asset processing technology, and in particular, to a workflow-based digital asset processing system, method, device, and medium. Background Art

[0002] A DAM (Digital Assent Management) system is a centralized repository where an organization's personnel can efficiently store, organize, manage, access, and distribute large amounts of digital assets, such as images, graphics, layouts, PDF files, documents, web pages, video clips, social media posts, and audio files.

[0003] DAM systems need to address the specific asset management needs of different enterprises and develop customized asset management links for different tenants. Therefore, DAM systems must support a flexible model to adapt to various differentiated scenarios. While ensuring the stability of the core backbone link, they must also provide efficient decoupling capabilities to flexibly add customized branch links. However, existing DAM systems are unable to customize asset management for different tenants, resulting in low asset processing efficiency. Summary of the Invention

[0004] The embodiments described herein provide a workflow-based digital asset processing system, method, device, and medium that overcome the aforementioned problems.

[0005] In a first aspect, according to the present disclosure, a workflow-based digital asset processing system is provided, comprising: a trigger, a queryer, and an executor, wherein the trigger serves as a start node of the workflow, the queryer serves as a query node of the workflow, and the executor serves as an execution node of the workflow;

[0006] The trigger is configured to start the task workflow of the target digital asset when a trigger configuration event of the target digital asset is detected;

[0007] The query unit is configured to filter out flow entities related to the task workflow of the target digital asset from the asset database based on the task trigger type corresponding to the task workflow of the target digital asset;

[0008] The executor is configured to perform corresponding functional operations on flow entities related to the task workflow of the target digital asset.

[0009] In a second aspect, according to the present disclosure, a workflow-based digital asset processing method is provided, comprising:

[0010] When a trigger configuration event of a target digital asset is detected, a task workflow of the target digital asset is started;

[0011] Based on the task trigger type corresponding to the task workflow of the target digital asset, filter out flow entities related to the task workflow of the target digital asset from the asset database;

[0012] Execute corresponding functional operations on flow entities related to the task workflow of the target digital asset.

[0013] In a third aspect, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the steps of the workflow-based digital asset processing method in any of the above embodiments are implemented.

[0014] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the workflow-based digital asset processing method in any of the above embodiments are implemented.

[0015] The workflow-based digital asset processing system provided by the embodiment of the present application includes: a trigger, a queryer, and an executor. The trigger serves as the starting node of the workflow, the queryer serves as the query node of the workflow, and the executor serves as the execution node of the workflow. The trigger is configured to start the task workflow of the target digital asset when a trigger configuration event of the target digital asset is detected. The queryer is configured to filter out flow entities related to the task workflow of the target digital asset from the asset database based on the task trigger type corresponding to the task workflow of the target digital asset. The executor is configured to perform corresponding functional operations on the flow entities related to the task workflow of the target digital asset. In this way, it is possible to filter out adapted flow entities according to the task trigger type corresponding to the task workflow of the target digital asset, facilitate corresponding functional operations, effectively process task workflows of different target digital assets, and improve asset processing efficiency.

[0016] The above description is only an overview of the technical solutions of the embodiments of the present application. In order to more clearly understand the technical means of the embodiments of the present application, they can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiments of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings of the embodiments will be briefly described below. It should be noted that the drawings described below only relate to some embodiments of the present disclosure and are not intended to limit the present disclosure.

[0018] Figure 1 This is a structural diagram of a workflow-based digital asset processing system provided by the present disclosure.

[0019] Figure 2 This is a schematic diagram of an interface of a task workflow provided by the present disclosure.

[0020] Figure 3 This is a flowchart of a workflow-based digital asset processing method provided by the present disclosure.

[0021] Figure 4 It is a structural diagram of a computer device provided by the present disclosure.

[0022] It should be noted that the elements in the drawings are schematic and not drawn to scale. DETAILED DESCRIPTION

[0023] In order to make the purpose, technical solutions and advantages of the embodiments of the present disclosure more clear, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the described embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without creative work also fall within the scope of protection of the present disclosure.

[0024] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present disclosure belongs. It will be further understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the specification and the relevant art, and will not be interpreted in an idealized or overly formal manner unless otherwise explicitly defined herein. As used herein, a statement that two or more parts are "connected" or "coupled" together shall mean that the parts are joined together either directly or through one or more intermediate components.

[0025] References to "embodiments" herein mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase "embodiment" in various places in the specification does not necessarily refer to the same embodiment, nor does it necessarily refer to independent or alternative embodiments that are mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0026] The term "and / or" in this document simply describes an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists, A and B exist simultaneously, and B exists. Additionally, the character " / " in this document generally indicates that the related objects are in an "or" relationship. Terms such as "first" and "second" are used solely to distinguish one component (or portion of a component) from another component (or portion of a component).

[0027] In the description of this application, unless otherwise specified, "plurality" means more than two (including two), and similarly, "multiple groups" means more than two (including two).

[0028] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.

[0029] Figure 1 This is a structural diagram of a workflow-based digital asset processing system provided by an embodiment of the present disclosure. Figure 1 As shown, the workflow-based digital asset processing system specifically includes: a trigger 110, a query unit 120 and an executor 130.

[0030] Trigger 110, the workflow's initiation node, captures and responds to specific events in production. Querier 120, the workflow's query node, screens and filters entities involved in the workflow. Executor 130, the workflow's execution node, executes specific functional operations and is the workflow's core action point.

[0031] The trigger 110 is configured to start the task workflow of the target digital asset when a trigger configuration event of the target digital asset is detected.

[0032] Among them, the target digital assets may refer to other digital assets, such as posters, marketing content, enterprise storage content (videos, images and other materials), etc.

[0033] The trigger configuration events for the target digital asset may include: material storage, material editing, material grouping, timed triggering, etc. When the trigger configuration event for the target digital asset is material storage, it is triggered when new materials are uploaded to the DAM system; when the trigger configuration event for the target digital asset is material editing, it is triggered when the materials are modified; when the trigger configuration event for the target digital asset is material grouping, it is triggered when the materials are classified into a specified group; when the trigger configuration event for the target digital asset is timed triggering, it is triggered at a pre-set time point, such as regularly starting a workflow task at dawn every day.

[0034] The task workflow of the target digital asset can be used to describe the processing flow of the target digital asset, such as asset storage, asset group storage, asset content modification / editing, asset scheduled upload / deletion, etc.

[0035] In some embodiments, the trigger 110 is specifically configured to:

[0036] When a trigger configuration event of a target digital asset is detected, an event trigger type corresponding to the trigger configuration event is obtained; based on the event trigger type corresponding to the trigger configuration event, a task workflow of the target digital asset is generated; based on the task trigger type corresponding to the task workflow of the target digital asset, the task workflow of the target digital asset is started.

[0037] The event trigger types include scheduled triggers and non-scheduled triggers. The task trigger types corresponding to the task workflow of the target digital asset correspond to the event trigger types. The task trigger types corresponding to the task workflow of the target digital asset include scheduled tasks and non-scheduled tasks.

[0038] When generating a task workflow for a target digital asset based on the event trigger type corresponding to a trigger configuration event, if the event trigger type corresponding to the trigger configuration event is a non-scheduled trigger type, the generated task workflow for the target digital asset can be asset storage into a warehouse, asset group storage, or asset content modification / editing; if the event trigger type corresponding to the trigger configuration event is a scheduled trigger type, the generated task workflow for the target digital asset can be scheduled asset upload / deletion.

[0039] Therefore, the task workflow of the target digital asset can be generated by triggering the event trigger type corresponding to the configuration event, and the task workflow corresponding to the target digital asset can be started according to the task trigger type corresponding to the task workflow of the target digital asset.

[0040] The query unit 120 is configured to filter out flow entities related to the task workflow of the target digital asset from the asset database based on the task trigger type corresponding to the task workflow of the target digital asset.

[0041] Among them, the asset database stores multiple materials that can represent digital assets. The flow entity related to the task workflow of the target digital asset can be one or more materials, such as images, or it can be a material entity that can represent one or more materials, such as animals and plants in an image.

[0042] In some embodiments, the query unit 120 is specifically configured to:

[0043] If the task trigger type corresponding to the task workflow of the target digital asset corresponds to a non-scheduled task class, then obtain the event message body corresponding to the trigger configuration event; based on the event message body corresponding to the trigger configuration event, match the flow entity related to the task workflow of the target digital asset from the asset database.

[0044] The event message body corresponding to the configuration triggering event includes additional asset information when the configuration triggering event is added. Specifically, the additional asset information can be additional information added during the approval and storage, such as image color, image size, etc.

[0045] Therefore, the operation object can be accurately located according to the context conditions of the target digital asset, so as to dynamically filter out the flow entities related to the task workflow of the target digital asset from the asset database.

[0046] In some other embodiments, the query unit 120 is specifically configured to:

[0047] If the task trigger type corresponding to the task workflow of the target digital asset corresponds to a timed task class, all entities included in the asset database are obtained; based on the workflow identifiers corresponding to the all entities included in the asset data, candidate entities are filtered out from the asset database; based on the entity quantity rule corresponding to the task workflow of the target digital asset, flow entities related to the task workflow of the target digital asset are filtered out from the candidate entities.

[0048] Among them, the full set of entities included in the asset database is all the materials stored in the asset database that can represent digital assets.

[0049] The workflow ID corresponding to an entity can be used to describe the entity's historical screening information. For example, a workflow ID of 1 indicates that the entity's screening count is too high (exceeding a certain threshold T1), while a workflow ID of 2 indicates that the entity's screening count is too low (below a certain threshold T1). Specifically, when screening candidate entities from the asset database, the entity with a workflow ID of 1 can be selected as the candidate entity.

[0050] The entity quantity rule corresponding to the task workflow of the target digital asset can be used to reflect the entity quantity limit of the task workflow of the target digital asset. If the entity quantity is less than T2, T2 entities are selected from the candidate entities as the flow entities related to the task workflow of the target digital asset.

[0051] Therefore, when the task trigger type corresponding to the task workflow of the target digital asset corresponds to the scheduled task class, entity screening is performed through multiple rules to facilitate the selection of flow entities that are more adaptable and can be related to the task workflow of the target digital asset.

[0052] The executor 130 is configured to execute corresponding functional operations on flow entities related to the task workflow of the target digital asset.

[0053] Among them, functional operations may include: material tagging, material renaming, material grouping, permission setting, content modification / editing, and material scheduled upload / deletion. The interface diagram corresponding to the task workflow is as follows Figure 2 shown.

[0054] In some embodiments, the actuator 130 is specifically configured to:

[0055] Obtain the entity execution policy of the flow entity related to the task workflow of the target digital asset; if the entity execution policy of the flow entity related to the task workflow of the target digital asset corresponds to the triggered execution policy, then based on the preset trigger time of the triggered execution policy, perform corresponding functional operations on the flow entity related to the task workflow of the target digital asset; if the entity execution policy of the flow entity related to the task workflow of the target digital asset corresponds to the non-triggered execution policy, obtain the preset execution rules of the non-triggered execution policy, and based on the preset execution rules of the non-triggered execution policy, perform corresponding functional operations on the flow entity related to the task workflow of the target digital asset.

[0056] Triggered execution strategies can be used to describe triggered, point-by-point execution, while non-triggered execution strategies can be used to describe conditional execution based on preset rules. Preset execution rules can be applied to multiple assets, for example, when multiple assets are executing a function simultaneously.

[0057] Therefore, corresponding functional operations can be executed according to different entity execution strategies of flow entities related to the task workflow of the target digital asset, so as to meet the specific needs of different tenants.

[0058] The workflow-based digital asset processing system provided in this embodiment includes: a trigger, a queryer, and an executor. The trigger serves as the workflow's initiation node, the queryer serves as the workflow's query node, and the executor serves as the workflow's execution node. The trigger is configured to initiate the target digital asset's task workflow upon detecting a trigger configuration event for the target digital asset. The queryer is configured to filter out flow entities related to the target digital asset's task workflow from an asset database based on the task trigger type corresponding to the target digital asset's task workflow. The executor is configured to perform corresponding functional operations on the flow entities related to the target digital asset's task workflow. In this way, the system can filter out suitable flow entities based on the task trigger type corresponding to the target digital asset's task workflow, facilitate corresponding functional operations, effectively process task workflows for different target digital assets, and improve asset processing efficiency.

[0059] Some embodiments further include: a responder.

[0060] The responder is configured to, upon detecting that a corresponding functional operation is completed on a flow entity related to a task workflow of a target digital asset, count the execution time of the operation corresponding to the functional operation; if the execution time of the operation corresponding to the functional operation meets a preset time threshold, generate a first execution response; if the execution time of the operation corresponding to the functional operation does not meet the preset time threshold, generate a second execution response.

[0061] The first execution response is used to indicate that the execution result of the functional operation meets expectations, and the second execution response is used to indicate that the execution result of the functional operation does not meet expectations.

[0062] Therefore, after detecting that the corresponding functional operation on the flow entity related to the task workflow of the target digital asset is completed, the execution result of each functional operation can be effectively identified by counting the execution time of the operation corresponding to the functional operation.

[0063] In some embodiments, the executor 130 is further configured to determine the operation execution component that performs the corresponding functional operation when the second execution response is detected; obtain component performance parameters of the operation execution component, and determine the component optimization strategy of the operation execution component based on the component performance parameters of the operation execution component.

[0064] Among them, the loss of the component performance parameters of the operation execution component can be evaluated. If the loss evaluation result of the component performance parameters of the operation execution component shows that the loss is serious, the component of the operation execution component is optimized; if the loss evaluation result of the component performance parameters of the operation execution component shows that the loss is relatively light, the component of the operation execution component is monitored, and the loss evaluation is performed after the operation execution component completes the corresponding function each time, and the component optimization strategy is re-formulated to effectively ensure the optimization of the parameters of each operation execution component.

[0065] In summary, the workflow of this embodiment can seamlessly execute multi-step operations and reduce manual intervention, which not only significantly improves work efficiency but also ensures the accuracy and consistency of operations. Through automation and standardization, the complexity and error rate of manual operations are reduced. The event-driven design greatly simplifies business logic and reduces system complexity. At the same time, the stability and reliability of system responses are ensured through unified event standards. The modular design improves the maintainability and reusability of the system; tenants can flexibly configure workflows according to actual needs, and use different triggers, query engines or executors to quickly adapt to changing business scenarios, continuously improving the system's scalability. The flexible configuration capability enables enterprises to quickly respond to personalized needs and enhance user experience.

[0066] Figure 3 A flowchart of a workflow-based digital asset processing method provided in this embodiment is shown in FIG. Figure 3 As shown, the specific process of the workflow-based digital asset processing method includes:

[0067] S310: When a trigger configuration event of a target digital asset is detected, the task workflow of the target digital asset is started.

[0068] Among them, the target digital assets may refer to other digital assets, such as posters, marketing content, enterprise storage content (videos, images and other materials), etc.

[0069] The trigger configuration events for the target digital asset may include: material storage, material editing, material grouping, timed triggering, etc. When the trigger configuration event for the target digital asset is material storage, it is triggered when new materials are uploaded to the DAM system; when the trigger configuration event for the target digital asset is material editing, it is triggered when the materials are modified; when the trigger configuration event for the target digital asset is material grouping, it is triggered when the materials are classified into a specified group; when the trigger configuration event for the target digital asset is timed triggering, it is triggered at a pre-set time point, such as regularly starting a workflow task at dawn every day.

[0070] The task workflow of the target digital asset can be used to describe the processing flow of the target digital asset, such as asset storage, asset group storage, asset content modification / editing, asset scheduled upload / deletion, etc.

[0071] In some embodiments, upon detecting a trigger configuration event for a target digital asset, initiating a task workflow for the target digital asset includes:

[0072] When a trigger configuration event of a target digital asset is detected, an event trigger type corresponding to the trigger configuration event is obtained, and the event trigger types include: scheduled trigger type and non-scheduled trigger type; based on the event trigger type corresponding to the trigger configuration event, a task workflow of the target digital asset is generated, and the task trigger type corresponding to the task workflow of the target digital asset corresponds to the event trigger type, and the task trigger types corresponding to the task workflow of the target digital asset include: scheduled task type and non-scheduled task type; based on the task trigger type corresponding to the task workflow of the target digital asset, the task workflow of the target digital asset is started.

[0073] Among them, when generating the task workflow of the target digital asset based on the event trigger type corresponding to the trigger configuration event, if the event trigger type corresponding to the trigger configuration event is a non-scheduled trigger type, the generated task workflow of the target digital asset can be asset storage in the warehouse, asset group storage, and asset content modification / editing; if the event trigger type corresponding to the trigger configuration event is a scheduled trigger type, the generated task workflow of the target digital asset can be asset scheduled upload / deletion.

[0074] Therefore, the task workflow of the target digital asset can be generated by triggering the event trigger type corresponding to the configuration event, and the task workflow corresponding to the target digital asset can be started according to the task trigger type corresponding to the task workflow of the target digital asset.

[0075] S320: Based on the task trigger type corresponding to the task workflow of the target digital asset, filter out flow entities related to the task workflow of the target digital asset from the asset database.

[0076] Among them, the asset database stores multiple materials that can represent digital assets. The flow entity related to the task workflow of the target digital asset can be one or more materials, such as images, or it can be a material entity that can represent one or more materials, such as animals and plants in an image.

[0077] In some embodiments, based on the task trigger type corresponding to the task workflow of the target digital asset, filtering out flow entities related to the task workflow of the target digital asset from the asset database includes:

[0078] If the task trigger type corresponding to the task workflow of the target digital asset corresponds to a non-scheduled task class, then the event message body corresponding to the trigger configuration event is obtained, and the event message body corresponding to the trigger configuration event includes additional asset information when the trigger configuration event is added; based on the event message body corresponding to the trigger configuration event, the flow entity related to the task workflow of the target digital asset is matched from the asset database.

[0079] The event message body corresponding to the configuration triggering event includes additional asset information when the configuration triggering event is added. Specifically, the additional asset information can be additional information added during the approval and storage, such as image color, image size, etc.

[0080] Therefore, the operation object can be accurately located according to the context conditions of the target digital asset, so as to dynamically filter out the flow entities related to the task workflow of the target digital asset from the asset database.

[0081] In some other embodiments, based on the task trigger type corresponding to the task workflow of the target digital asset, the flow entities related to the task workflow of the target digital asset are screened from the asset database, including:

[0082] If the task trigger type corresponding to the task workflow of the target digital asset corresponds to a timed task class, all entities included in the asset database are obtained; based on the workflow identifiers corresponding to the all entities included in the asset data, candidate entities are filtered out from the asset database; based on the entity quantity rule corresponding to the task workflow of the target digital asset, flow entities related to the task workflow of the target digital asset are filtered out from the candidate entities.

[0083] Among them, the full set of entities included in the asset database is all the materials stored in the asset database that can represent digital assets.

[0084] The workflow ID corresponding to an entity can be used to describe the entity's historical screening information. For example, a workflow ID of 1 indicates that the entity's screening count is too high (exceeding a certain threshold T1), while a workflow ID of 2 indicates that the entity's screening count is too low (below a certain threshold T1). Specifically, when screening candidate entities from the asset database, the entity with a workflow ID of 1 can be selected as the candidate entity.

[0085] The entity quantity rule corresponding to the task workflow of the target digital asset can be used to reflect the entity quantity limit of the task workflow of the target digital asset. If the entity quantity is less than T2, T2 entities are selected from the candidate entities as the flow entities related to the task workflow of the target digital asset.

[0086] Therefore, when the task trigger type corresponding to the task workflow of the target digital asset corresponds to the scheduled task class, entity screening is performed through multiple rules to facilitate the selection of flow entities that are more adaptable and can be related to the task workflow of the target digital asset.

[0087] S330: Execute corresponding functional operations on flow entities related to the task workflow of the target digital asset.

[0088] Among them, functional operations may include: material labeling, material renaming, material grouping, permission setting, content modification / editing, and scheduled material uploading / deletion.

[0089] Therefore, it is possible to filter the adapted flow entity according to the task trigger type corresponding to the task workflow of the target digital asset, facilitate the corresponding functional operations, effectively process the task workflows of different target digital assets, and improve asset processing efficiency.

[0090] In some embodiments, performing corresponding functional operations on flow entities related to the task workflow of the target digital asset includes:

[0091] Obtain the entity execution policy of the flow entity related to the task workflow of the target digital asset; if the entity execution policy of the flow entity related to the task workflow of the target digital asset corresponds to the triggered execution policy, then based on the preset trigger time of the triggered execution policy, perform corresponding functional operations on the flow entity related to the task workflow of the target digital asset; if the entity execution policy of the flow entity related to the task workflow of the target digital asset corresponds to the non-triggered execution policy, obtain the preset execution rules of the non-triggered execution policy, and based on the preset execution rules of the non-triggered execution policy, perform corresponding functional operations on the flow entity related to the task workflow of the target digital asset.

[0092] Triggered execution strategies can be used to describe triggered, point-by-point execution, while non-triggered execution strategies can be used to describe conditional execution based on preset rules. Preset execution rules can be applied to multiple assets, for example, when multiple assets are executing a function simultaneously.

[0093] Therefore, corresponding functional operations can be executed according to different entity execution strategies of flow entities related to the task workflow of the target digital asset, so as to meet the specific needs of different tenants.

[0094] In some embodiments, the present invention further comprises:

[0095] If it is detected that the corresponding functional operation on the flow entity related to the task workflow of the target digital asset is completed, the operation execution time corresponding to the functional operation is counted; if the operation execution time corresponding to the functional operation meets the preset time threshold, a first execution response is generated; if the operation execution time corresponding to the functional operation does not meet the preset time threshold, a second execution response is generated.

[0096] The first execution response is used to indicate that the execution result of the functional operation meets expectations, and the second execution response is used to indicate that the execution result of the functional operation does not meet expectations.

[0097] Therefore, after detecting that the corresponding functional operation on the flow entity related to the task workflow of the target digital asset is completed, the execution result of each functional operation can be effectively identified by counting the execution time of the operation corresponding to the functional operation.

[0098] In some embodiments, the present invention further comprises:

[0099] When the second execution response is detected, an operation execution component that executes the corresponding functional operation is determined; component performance parameters of the operation execution component are obtained, and a component optimization strategy of the operation execution component is determined based on the component performance parameters of the operation execution component.

[0100] Among them, the loss of the component performance parameters of the operation execution component can be evaluated. If the loss evaluation result of the component performance parameters of the operation execution component shows that the loss is serious, the component of the operation execution component is optimized; if the loss evaluation result of the component performance parameters of the operation execution component shows that the loss is relatively light, the component of the operation execution component is monitored, and the loss evaluation is performed after the operation execution component completes the corresponding function each time, and the component optimization strategy is re-formulated to effectively ensure the optimization of the parameters of each operation execution component.

[0101] The present application also provides a computer device. Figure 4 , Figure 4 This is a basic structural block diagram of the computer device in this embodiment.

[0102] The computer device includes a memory 410 and a processor 420 that are interconnected and communicate with each other via a system bus. It should be noted that the figure only shows a computer device with a memory 410 and a processor 420, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to a microprocessor, an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a digital signal processor (DSP), an embedded device, etc.

[0103] Computer devices can be desktop computers, laptops, PDAs, cloud servers, etc. Computer devices can interact with users through keyboards, mice, remote controls, touchpads, or voice-activated devices.

[0104] The memory 410 includes at least one type of readable storage medium, including non-volatile memory or volatile memory, such as flash memory, hard disk, multimedia card, card-type memory (such as SD or DX memory), random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic storage, magnetic disk, optical disk, etc. The RAM may include static RAM or dynamic RAM. In some embodiments, the memory 410 may be an internal storage unit of a computer device, such as a hard disk or memory of the computer device. In other embodiments, the memory 410 may also be an external storage device of the computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, or a Flash Card equipped on the computer device. Of course, the memory 410 may also include both the internal storage unit of the computer device and its external storage device. In this embodiment, the memory 410 is generally used to store the operating system and various application software installed on the computer device, such as the program code of the above-mentioned method. In addition, the memory 410 may also be used to temporarily store various types of data that have been output or are about to be output.

[0105] The processor 420 is generally used to perform the overall operation of the computer device. In this embodiment, the memory 410 is used to store program code or instructions, which include computer operating instructions. The processor 420 is used to execute the program code or instructions stored in the memory 410 or process data, such as the program code for running the above method.

[0106] In this document, a bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. This bus system can be divided into address buses, data buses, and control buses. For ease of illustration, the figure uses only one thick line, but this does not mean that there is only one bus or only one type of bus.

[0107] Another embodiment of the present application further provides a computer-readable medium, which may be a computer-readable signal medium or a computer-readable medium. A processor in a computer reads the computer-readable program code stored in the computer-readable medium, enabling the processor to execute the functional actions specified in each step or combination of steps in the above method, and to generate a device that implements the functional actions specified in each block or combination of blocks in the block diagram.

[0108] Computer-readable media include but are not limited to electronic, magnetic, optical, electromagnetic, infrared memory or semiconductor systems, devices or apparatuses, or any appropriate combination of the foregoing, the memory is used to store program codes or instructions, the program codes include computer operating instructions, and the processor is used to execute the program codes or instructions of the above-mentioned methods stored in the memory.

[0109] For the definitions of memory and processor, please refer to the description of the aforementioned computer device embodiment and will not be repeated here.

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

[0111] Each functional unit or module in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The above-mentioned integrated units may be implemented in the form of hardware or software functional units.

[0112] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program code.

[0113] In the claims, any reference signs placed between brackets shall not be construed as limiting the claims. The word "comprising" described in the present application 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. The present application can be implemented with the aid of hardware comprising several different elements and with the aid of a suitably programmed computer. In a unit claim that lists several means, several units of these means may be embodied by the same hardware item. The use of first, second, and third etc. does not indicate any order and these words may be interpreted as names. The steps in the above embodiments should not be understood as limiting the order of execution unless otherwise specified.

[0114] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A digital asset processing system based on workflow, characterized in that: include: A trigger, a queryer, and an executor, wherein the trigger serves as a start node of the workflow, the queryer serves as a query node of the workflow, and the executor serves as an execution node of the workflow; The trigger is configured to start the task workflow of the target digital asset when a trigger configuration event of the target digital asset is detected; The query unit is configured to filter out flow entities related to the task workflow of the target digital asset from the asset database based on the task trigger type corresponding to the task workflow of the target digital asset; The executor is configured to perform corresponding functional operations on flow entities related to the task workflow of the target digital asset.

2. The system according to claim 1, wherein: The trigger is specifically configured as follows: When a trigger configuration event of a target digital asset is detected, an event trigger type corresponding to the trigger configuration event is obtained, where the event trigger type includes: a timed trigger type and a non-timed trigger type; Generate a task workflow for the target digital asset based on the event trigger type corresponding to the trigger configuration event, wherein the task trigger type corresponding to the task workflow for the target digital asset corresponds to the event trigger type, and the task trigger types corresponding to the task workflow for the target digital asset include scheduled tasks and non-scheduled tasks; Based on the task trigger type corresponding to the task workflow of the target digital asset, the task workflow of the target digital asset is started.

3. The system according to claim 2, characterized in that The query device is specifically configured to: If the task trigger type corresponding to the task workflow of the target digital asset corresponds to the non-scheduled task class, obtaining an event message body corresponding to the trigger configuration event, wherein the event message body corresponding to the trigger configuration event includes additional asset information when the trigger configuration event is added; Based on the event message body corresponding to the trigger configuration event, a flow entity related to the task workflow of the target digital asset is matched from an asset database.

4. The system according to claim 2, wherein: The query device is specifically configured to: If the task trigger type corresponding to the task workflow of the target digital asset corresponds to the scheduled task class, obtaining all entities included in the asset database; Filtering candidate entities from the asset database based on workflow identifiers corresponding to all entities included in the asset data; Based on the entity quantity rule corresponding to the task workflow of the target digital asset, flow entities related to the task workflow of the target digital asset are screened out from the candidate entities.

5. The system according to claim 1, wherein: The actuator is specifically configured as follows: Obtaining an entity execution policy of a flow entity related to a task workflow of the target digital asset; If the entity execution policy of the flow entity related to the task workflow of the target digital asset corresponds to the trigger execution policy, then based on the preset trigger time of the trigger execution policy, performing a corresponding functional operation on the flow entity related to the task workflow of the target digital asset; If the entity execution policy of the flow entity related to the task workflow of the target digital asset corresponds to a non-trigger execution policy, then the preset execution rules of the non-trigger execution policy are obtained, and based on the preset execution rules of the non-trigger execution policy, corresponding functional operations are performed on the flow entity related to the task workflow of the target digital asset.

6. The system according to claim 1, wherein: Also includes: Responder; The responder is configured to, upon detecting that a corresponding functional operation is completed on a flow entity related to the task workflow of the target digital asset, count the execution time of the operation corresponding to the functional operation; and generate a first execution response if the execution time of the operation corresponding to the functional operation meets a preset time threshold; If the execution time of the operation corresponding to the functional operation does not meet the preset time threshold, a second execution response is generated.

7. The system according to claim 6, characterized in that The executor is further configured to determine the operation execution component that performs the corresponding functional operation when the second execution response is detected; obtain the component performance parameters of the operation execution component, and determine the component optimization strategy of the operation execution component based on the component performance parameters of the operation execution component.

8. A workflow-based digital asset processing method, characterized in that: include: When a trigger configuration event of a target digital asset is detected, a task workflow of the target digital asset is started; Based on the task trigger type corresponding to the task workflow of the target digital asset, filter out flow entities related to the task workflow of the target digital asset from the asset database; Execute corresponding functional operations on flow entities related to the task workflow of the target digital asset.

9. A computer device, characterized in that: The method comprises a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the workflow-based digital asset processing method as claimed in claim 8 is implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the workflow-based digital asset processing method according to claim 8 is implemented.

Images