Plug-in type process management system, electronic device and business process management method

Abstract

The application discloses a plug-in type process management system, an electronic device and a business process management method, and belongs to the computer field.The plug-in type process management system comprises N storage spaces and N business plug-ins, wherein N is an integer greater than or equal to 2; each business plug-in corresponds to an independent storage space; each business plug-in is configured to receive to-be-processed business data, store the to-be-processed business data into the corresponding storage space, copy the to-be-processed business data, and process the copied to-be-processed business data, thereby improving the problem that, when an error occurs in a plug-in, the entire business process needs to be re-executed from the beginning, and a large amount of time needs to be consumed.

Description

TECHNICAL FIELD

[0001] The present application belongs to the field of computer, and particularly relates to a plug-in type process management system, an electronic device and a business process management method. BACKGROUND

[0002] The plug-in type process management system has the advantages of being configurable and easy to establish a business item, and is widely applied to scenes such as business approval process and software development process. The plug-in type process management system comprises a process management component and a series of parameterized business plug-ins. The process management component provides query of all business plug-ins, establishes and configures a business item by organizing and configuring the business plug-ins, and performs and schedules the business plug-ins.

[0003] When the current plug-in type process management system executes a business, a superior plug-in provides data received to an inferior plug-in after processing, and the inferior plug-in submits the data received to its next level after processing. When an error occurs in a certain plug-in, the entire business process needs to be re-executed from the beginning. SUMMARY

[0004] In view of this, the purpose of the present application is to provide a plug-in type process management system, an electronic device and a business process management method, so as to improve the existing plug-in type process management system, and solve the problem that when an error occurs in a certain plug-in, the entire business process needs to be re-executed from the beginning, resulting in a large amount of time being consumed.

[0005] Embodiments of the present application are implemented as follows:

[0006] In a first aspect, the embodiments of the present application provide a plug-in type process management system, comprising: N storage spaces and N business plug-ins, N being an integer greater than or equal to 2; each business plug-in corresponds to an independent storage space, each business plug-in is configured to receive to-be-processed business data, store the to-be-processed business data into the corresponding storage space, and copy the to-be-processed business data and process the copied to-be-processed business data.

[0007] In the embodiments of the present application, each business plug-in corresponds to an independent storage space, and each business plug-in can store the received to-be-processed business data into the corresponding storage space, so that when an error occurs in a certain business plug-in, the error business plug-in can directly read the data of the storage space to re-execute, instead of re-executing the entire process from the beginning, which greatly improves the processing efficiency.

[0008] In combination with a possible implementation manner of the first aspect, each business plug-in is further configured to re-process the to-be-processed business data stored in advance in response to a re-execution instruction, and send the re-processed business data.

[0009] In the embodiments of the present application, each service plug-in can respond to the re-execution instruction, re-process the previously stored to-be-processed service data, and send the re-processed service data. In this way, when a certain service plug-in is faulty, the faulty service plug-in can directly read the data in the storage space to perform re-processing, instead of re-executing the entire flow from the beginning, thereby greatly improving the processing efficiency.

[0010] With reference to a possible implementation of the first aspect, the plug-in type flow management system further comprises a flow management component, which is connected with each service plug-in; the flow management component is configured to determine a target service plug-in that needs to re-process the service when the service data needs to be re-processed in the lower-level service plug-in, and issue a re-execution instruction to the target service plug-in.

[0011] In the embodiments of the present application, the flow management component is used to issue a re-execution instruction to the target service plug-in that needs to re-process the service, to instruct the target service plug-in to re-process the previously stored to-be-processed service data, thereby greatly improving the processing efficiency without re-executing the entire flow from the beginning.

[0012] With reference to a possible implementation of the first aspect, the plug-in type flow management system further comprises a shared storage space; the shared storage space is configured to store service data shared by multiple service plug-ins; and the storage space of each service plug-in is configured to store service data unique to each service plug-in.

[0013] In the embodiments of the present application, the shared storage space is used to store service data shared by multiple service plug-ins, which can reduce the number of times of issuing the same data, thereby improving the execution efficiency.

[0014] With reference to a possible implementation of the first aspect, each service plug-in has a sleep state and a working state, and the power consumption in the sleep state is less than that in the working state.

[0015] In the embodiments of the present application, each service plug-in has a sleep state and a working state, which can configure the service plug-in to belong to different states. For example, each service plug-in can be in a "sleep" state after the execution of the entire flow, thereby saving power consumption.

[0016] With reference to a possible implementation of the first aspect, each service plug-in is further configured to delete the to-be-processed service data stored by itself in response to a deletion instruction.

[0017] In the embodiments of the present application, in order to save the cost of data storage, a data cleaning business process can be automatically initiated after the whole process is successfully executed, so that each business plug-in deletes the respective stored data.

[0018] In combination with a possible implementation manner of the first aspect, each of the business plug-ins is a single plug-in or a combined plug-in, and the combined plug-in includes a plurality of single plug-ins.

[0019] In the embodiments of the present application, a plurality of single plug-ins can be combined into a combined plug-in, so that a series of complex processes can be combined into a combined plug-in, and the system structure and the difficulty of business process maintenance and use can be simplified.

[0020] In the second aspect, the embodiments of the present application further provide a plug-in type process management system, including: N business plug-ins and a process management component, each of the business plug-ins is configured to store received to-be-processed business data into a corresponding storage space, and to copy the to-be-processed business data and process the copied to-be-processed business data, and N is an integer greater than or equal to 2; the process management component is connected with each of the business plug-ins, and the process management component is configured to determine a target business plug-in that needs to re-execute business data when the business data needs to be re-executed in a lower-level business plug-in, and to issue a re-execution instruction to the target business plug-in; and the target business plug-in is configured to re-process the previously stored to-be-processed business data in response to the re-execution instruction, and to send the re-processed business data.

[0021] In the third aspect, the embodiments of the present application further provide an electronic device, including: the process management system provided in the first aspect and / or any possible implementation manner in combination with the first aspect, or the process management system provided in the second aspect.

[0022] In the fourth aspect, the embodiments of the present application further provide a business process management method, including: when business data needs to be re-executed in a lower-level business plug-in, a process management component determines a target business plug-in that needs to re-execute the business data, and issues a re-execution instruction to the target business plug-in; the target business plug-in re-processes the previously backed up input business data in response to the re-execution instruction, and sends the re-processed business data; and all business plug-ins after the target business plug-in store to-be-processed business data received from a previous business plug-in into a corresponding storage space, copy the to-be-processed business data, and process the copied to-be-processed business data.

[0023] With reference to a possible implementation of the fourth aspect, the method further comprises: the flow management component obtaining the position of the target business plug-in in the entire business flow; the flow management component obtaining all business plug-ins located after the target business plug-in; and the flow management component sending a save instruction to all business plug-ins located after the target business plug-in, the save instruction being used to instruct the business plug-ins to store the received to-be-processed business data into the corresponding storage space.

[0024] Other features and advantages of the present application will be set forth in the following description, in part in terms of the descriptions of the drawings. The features and advantages of the present application will become apparent with reference to the drawings in which like reference numerals designate identical or corresponding parts throughout the figures. BRIEF DESCRIPTION OF DRAWINGS

[0025] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed to be used in the embodiments will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained from these drawings without creative labor. Through the drawings, the above and other purposes, features and advantages of the present application will be more apparent.

[0026] Figure 1 A principle schematic diagram of a plug-in type flow management system provided by an embodiment of the present application is shown.

[0027] Figure 2 A structural schematic diagram of a combined plug-in provided by an embodiment of the present application is shown.

[0028] Figure 3 For Figure 1 An equivalent schematic diagram is shown.

[0029] Figure 4 A principle schematic diagram of another plug-in type flow management system provided by an embodiment of the present application is shown.

[0030] Figure 5 A flow schematic diagram of a business flow management method provided by an embodiment of the present application is shown.

[0031] Figure 6 A structural schematic diagram of an electronic device provided by an embodiment of the present application is shown. DETAILED DESCRIPTION

[0032] With reference to the drawings, the technical solutions in the embodiments of the present application will be described below. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments of the present application. The following embodiments are used as examples to more clearly illustrate the technical solutions of the present application, and should not be used to limit the protection scope of the present application. Those skilled in the art can understand that the following embodiments and the features in the embodiments can be combined with each other without conflict.

[0033] The terms "comprising", "containing", or any other variant thereof are intended to cover a non-exclusive inclusion, so that a process, method, article, or apparatus that comprises a list of elements not only includes those elements, but also includes other elements that are not expressly listed, or other elements inherent in such process, method, article, or apparatus. Without more limitations, the element defined by the phrase "comprising a" does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0034] Furthermore, the term "and / or" in the present application is only a description of the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent the three cases of A alone, A and B together, and B alone.

[0035] In view of the current plug-in process management system, when a business plug-in runs an error, the entire business process needs to be re-executed from the beginning, resulting in a large amount of time being consumed. In order to save the time consumed by the process, each business plug-in can be repeatedly executed, so that when an error occurs in a certain business plug-in, the error can be corrected and the current business plug-in can continue to execute, rather than starting from the beginning.

[0036] In view of this, the plug-in process management system provided in the embodiments of the present application supports parallel execution of business flows, and each business plug-in can save its own input data, so that when an error occurs in a certain business plug-in, the error can be corrected and the current business plug-in can continue to execute, rather than re-executing the entire process from the beginning.

[0037] For better understanding, the following will be combined with Figure 1 The plug-in process management system provided in the embodiments of the present application is described, which includes N storage spaces and N business plug-ins, and N is an integer greater than or equal to 2. The number of N depends on the complexity of the business project, and the more complex the business project to be processed, the more business plug-ins are required. For example, the structure of the plug-in process management system used in the business approval process is different from the structure of the plug-in process management system used in the development process.

[0038] If the plug-in type process management system is an application APP (such as a business approval APP, a software development APP), the business plug-in can be regarded as a functional module constituting the entire APP. As the design function of the APP increases, the corresponding business plug-in also increases. When a certain business function needs to be added, a business plug-in can be added, and the mutual cooperation relationship between the added business plug-in and the original business plug-in can be set to achieve the purpose of adding the function. The N storage spaces can come from the same memory, and the memory can be divided into N parts, and each business plug-in corresponds to an independent storage space.

[0039] The N business plug-ins cooperate with each other to complete the specified business project. The N business plug-ins can be configured in series or in series-parallel according to the needs of the business project to achieve the processing of the specified business project. For example, Figure 1 The business plug-in 1, the business plug-in 2, the business plug-in 3, the business plug-in 4, and the business plug-in 5 in the figure are business plug-ins. The business plug-in 1, the business plug-in 4, and the business plug-in 5 are connected in series, the business plug-in 1, the business plug-in 2, the business plug-in 3, and the business plug-in 5 are connected in series, and the business plug-in 4 is connected in parallel with the business plug-in 2 and the business plug-in 3.

[0040] In the traditional process, the business plug-in 2, the business plug-in 3, and the business plug-in 4 cannot be executed at the same time. If parallel processing is required, two different tasks usually need to be created. In the parallel business process, they can be executed concurrently as different business plug-ins of the same task, saving process time.

[0041] The business plug-in can pass data and sequentially schedule execution with other business plug-ins in parallel or in series. In the series execution scenario, the upper plug-in stores data in the storage space corresponding to itself, simultaneously, copies the data, processes the copied data, and provides the processed data to the lower level. After receiving the data issued by the upper plug-in, the lower plug-in stores the data in its own storage space, simultaneously, copies the data, processes the copied data, and then transmits the new data obtained by processing to the next level.

[0042] It can be understood that the structure of the plug-in type process management system is not limited to Figure 1 As shown in the figure. The corresponding structure is different according to the processing business, that is, the connection mode of the N business plug-ins and the number N can be changed according to the processing object and the use scenario.

[0043] Each business plug-in can be a single plug-in or a combined plug-in. The combined plug-in includes multiple single plug-ins. For example, in an embodiment, the Figure 1The business plug-in 2, the business plug-in 3 and the business plug-in 4 in the business project 1 are combined into a new combined plug-in, which can be called a template plug-in, and the schematic diagram thereof is shown in FIG. 2. Figure 2 The business item configuration of the plug-in type process management system supports the template plug-in, and such a plug-in is not a specific business plug-in, but a new plug-in combined by other business plug-ins. The business item can directly use such a template plug-in as a business plug-in. In this way, a series of complex processes can be combined into a template plug-in, thereby simplifying the difficulty of business process maintenance and use.

[0044] In an optional embodiment, the plug-in type process management system shown in FIG. 1 can be simplified into the plug-in type process management system shown in FIG. 3, wherein the combined plug-in 2 in the business project 1 includes the business plug-in 2, the business plug-in 3 and the business plug-in 4 in the business project 1. Figure 1 Figure 3 In an optional embodiment, the plug-in type process management system shown in FIG. 1 can be simplified into the plug-in type process management system shown in FIG. 3, wherein the combined plug-in 2 in the business project 1 includes the business plug-in 2, the business plug-in 3 and the business plug-in 4 in the business project 1. Figure 3 Figure 1 The combined plug-in 2 includes the business plug-in 2, the business plug-in 3 and the business plug-in 4 in the business project 1. In the business project, no matter whether the business plug-in is a single plug-in or a combined plug-in, each business plug-in corresponds to a storage space, for example, the combined plug-in corresponds to the storage space 2' in the business project 1. Figure 3

[0045] Each business plug-in is divided into an upper plug-in or a lower plug-in according to its position in the process of the business item. The lower plug-in is responsible for processing the business data (i.e., the to-be-processed business data) issued by the upper plug-in connected thereto. Multiple lower plug-ins can be connected in series at the lower level of a certain business plug-in. These lower plug-ins can belong to a parallel relationship and process respective business data. Each parallel business can further be connected in series with a sub-business and be recombined at a business plug-in supporting multiple inputs.

[0046] Each business plug-in corresponds to an independent storage space, so that each business plug-in can save its own input data. Each business plug-in is configured to receive to-be-processed business data, store the to-be-processed business data into the corresponding storage space, copy the received to-be-processed business data, process the copied to-be-processed business data, and then send out the processed data.

[0047] It can be understood that different business plug-ins process received business data in different ways, and the corresponding processing methods are different in different application scenarios, for example, the processing methods include but are not limited to data operation, data forwarding, format conversion, data filtering, etc.

[0048] Since each business plug-in has its own corresponding storage space, it can support processing of multiple data streams. Even if it cannot process the data streams at the same time, it can first store the data streams in the storage space and then copy the business data from the storage space for processing when it can process the data streams. ​​​

[0049] The plug-in type process management system provided by the embodiments of the present application has a corresponding storage space for each business plug-in, so that when processing data flow, the business data to be processed can be stored in the corresponding storage space, and parallel processing can be supported. Meanwhile, each business plug-in can save its own input data, so that when an error occurs in a certain business plug-in, the current business plug-in can be corrected and continued to be executed, instead of re-executing the entire process from the beginning, which greatly improves the processing efficiency.

[0050] Each business plug-in copies the upper-level business data and processes the copied business data, and the original upper-level data remains unchanged, so that when the business process needs to be re-executed, it is not necessary to start from the beginning, but only to modify the configuration of the faulty business plug-in to resume the execution.

[0051] In an optional embodiment, each business plug-in is further configured to re-process the previously stored business data to be processed in response to the re-execution instruction, and send the re-processed business data. In this way, when an error occurs in a certain business plug-in, the error can be corrected and the current business plug-in can be continued to be executed, instead of starting from the beginning.

[0052] In an optional embodiment, the plug-in type process management system further includes a process management component connected with each business plug-in; the process management component is configured to determine the target business plug-in that needs to re-execute the business when the business data needs to be re-executed in the lower-level business plug-in, and issue a re-execution instruction to the target business plug-in. The target business plug-in re-processes the previously stored business data to be processed in response to the re-execution instruction, and sends the re-processed business data.

[0053] The lower-level business plug-in is distinguished according to the position of the business plug-in in the plug-in type process management system. All business plugs that are not at the first end (or top end) can be referred to as lower-level business plugs. For example, for the plug-in type process management system shown in FIG. 1, the business plug-in 2, the business plug-in 3, the business plug-in 4, and the business plug-in 5 are all lower-level business plugs relative to the business plug-in 1, and any of the business plugs can be used as the business plug-in for re-executing the business data if an error occurs. Figure 1

[0054] The process management component establishes and configures a business project by organizing and configuring the business plugs, executes and schedules the business plugs, and the like. The process management component can issue respective configuration instructions to the business plugs to instruct the business plugs to jointly complete the business project.

[0055] ​In an alternative embodiment, whether each service plug-in saves input data is configurable. If a service plug-in does not save input data, the service plug-in cannot be used as a starting point for re-execution, because the service plug-in cannot obtain the same input data again. When the service needs to be re-executed, the service can only be executed from a service plug-in in front of the service plug-in. Whether each service plug-in saves input data can be configured by a command issued by the flow management component.

[0056] In an alternative embodiment, to save the cost of data storage, a data cleaning service flow can be automatically initiated after the entire flow is successfully executed, so that each service plug-in deletes the stored data. In this embodiment, each service plug-in is further configured to delete the stored to-be-processed service data in response to a deletion instruction. The deletion instruction can be sent by the flow management component. After the entire flow is successfully executed, the flow management component issues the deletion instruction to each service plug-in, and each service plug-in deletes the stored to-be-processed service data in response to the deletion instruction.

[0057] In an alternative embodiment, each service plug-in has its own inherent attributes, such as a sleep state and a working state, where the power consumption in the sleep state is less than the power consumption in the working state. A service plug-in with such attributes can be in a "sleep" state after the entire flow is executed. The user can trigger the service again when new configuration data is ready, so that the service can be restored from the sleep state and continue to be executed. The service plug-in can be configured to belong to different states by a command issued by the flow management component.

[0058] In an alternative embodiment, the plug-in type flow management system can further include a shared storage space (not shown in the figure) configured to store service data shared by the plurality of service plug-ins, and a storage space independent of each service plug-in configured to store service data unique to each service plug-in. The service data can be divided into global data type and service plug-in specific data type. When establishing a service, if more than one plug-in needs the configuration name, the data type is used as global data type, otherwise, the data type is used as plug-in specific data type. By storing the global data type in the shared storage space shared by the plurality of service plug-ins, the service initiator can directly store the global data in the shared storage space when initiating a service, without repeatedly inputting redundant data.

[0059] Based on the same inventive concept, the embodiments of the present application further provide a plug-in type flow management system including N service plug-ins and a flow management component, where N is an integer greater than or equal to 2, as shown in Figure 4

[0060] ​N service plug-ins cooperate to complete the designated service project, each service plug-in is configured to store the received to-be-processed service data to a corresponding storage space, and to copy the to-be-processed service data and process the copied to-be-processed service data.

[0061] The process management component is connected with each service plug-in, the process management component is configured to determine a target service plug-in that needs to re-execute service data when the service data needs to be re-executed in a lower-level service plug-in, and issue a re-execution instruction to the target service plug-in; the target service plug-in is configured to re-process the previously stored to-be-processed service data in response to the re-execution instruction, and send the re-processed service data.

[0062] It can be understood that the implementation principle and the technical effects of the above-described plug-in type process management system Figure 4 are the same as those of the plug-in type process management system embodiment shown in Figure 1 for brevity of description, the unmentioned parts in this embodiment can be referred to the corresponding content in the foregoing plug-in type process management system embodiments.

[0063] Based on the same inventive concept, the embodiments of the present application also provide a service process management method, which will be described below. Figure 5 The service process management method can be applied to the above-described plug-in type process management system. Figure 5

[0064] S1: When service data needs to be re-executed in a lower-level service plug-in, the process management component determines a target service plug-in that needs to re-execute the service data, and issues a re-execution instruction to the target service plug-in.

[0065] When a certain service plug-in runs an error, so that the service data needs to be re-executed in a lower-level service plug-in, the process management component determines a target service plug-in that needs to re-execute the service data, and issues a re-execution instruction to the target service plug-in.

[0066] S2: The target service plug-in re-processes the previously backed up input service data in response to the re-execution instruction, and sends the re-processed service data.

[0067] It can be understood that each service plug-in can be configured to store the input service data to a corresponding storage space, so as to facilitate subsequent re-processing of the previously backed up input service data when the re-execution instruction is received, and sending the re-processed service data.

[0068] ​S3: All the service plugins behind the target service plugin store the to-be-processed service data into corresponding storage spaces and replicate the to-be-processed service data and process the replicated to-be-processed service data when receiving the to-be-processed service data sent by the upper-level service plugin.

[0069] Since each service plugin can be configured to receive to-be-processed service data, store the to-be-processed service data into corresponding storage spaces, replicate the to-be-processed service data, and process the replicated to-be-processed service data, when the target service plugin at the lower level re-executes the service data, all the service plugins behind the target service plugin will store the to-be-processed service data into corresponding storage spaces, replicate the to-be-processed service data, and process the replicated to-be-processed service data when receiving the to-be-processed service data sent by the upper-level service plugin.

[0070] Optionally, the method further includes: the process management component obtaining the position of the target service plugin in the entire service process; the process management component obtaining all the service plugins behind the target service plugin; and the process management component sending a save instruction to all the service plugins behind the target service plugin, the save instruction being used to instruct the service plugins to store the received to-be-processed service data into corresponding storage spaces. In this implementation, whether each service plugin saves the received input data is configurable, and the configuration is relatively simple, which only needs to issue corresponding configuration instructions, for example, issuing a save instruction to instruct the service plugins to save the received input data.

[0071] Optionally, the method further includes: the process management component issuing a delete instruction to each service plugin after the entire process is successfully executed, and each service plugin deletes the stored to-be-processed service data in response to the delete instruction.

[0072] The service process management method provided in the embodiments of the present application has the same implementation principle, technical effects, and the like as the aforementioned plug-in type process management system, and for brevity, the part not mentioned in the method embodiments can refer to the corresponding content in the aforementioned plug-in type process management system.

[0073] The embodiments of the present application further provide an electronic device including the aforementioned plug-in type process management system. Optionally, as shown in Figure 6 The electronic device 200 includes a transceiver 210, a memory 220, a communication bus 230, and a processor 240. The various plugins in the aforementioned plug-in type process management system can be deployed in the processor 240. The storage spaces in the plug-in type process management system can come from the memory 220. The memory 220 can be divided into N storage spaces corresponding to N service plugins one by one.

[0074] The transceiver 210, the memory 220, the processor 240 are electrically connected with each other directly or indirectly to realize the transmission or interaction of data. For example, these elements can be electrically connected with each other through one or more communication buses 230 or signal lines. The transceiver 210 is configured to transceive data. The memory 220 is configured to store a computer program, such as a computer program required to execute the above-mentioned business process management method. The computer program includes at least one software function module in the form of software or firmware, which is stored in the memory 220 or solidified in the operating system (OS) of the electronic device 200. The processor 240 is configured to execute the executable module stored in the memory 220 to execute the above-mentioned business process management method.

[0075] The memory 220 can be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), etc.

[0076] The processor 240 can be an integrated circuit chip with a signal processing capability. The processor mentioned above can be a general processor, including a central processing unit (CPU), a network processor (NP), a microprocessor, etc.; also can be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can realize or execute the disclosed methods, steps and logic block diagrams in the embodiments of the present application. Or the processor 240 can also be any conventional processor or the like.

[0077] The electronic device 200 includes, but is not limited to, a tablet, a computer, a vehicle-mounted device, and the like.

[0078] It should be noted that each of the embodiments in the present specification is described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the embodiments can be mutually referred to.

[0079] In several embodiments provided in the present application, it should be understood that the disclosed apparatus and method can also be implemented by other manners. The apparatus embodiments described above are only schematic, for example, the flow charts and block diagrams in the drawings show the possible implementation architectures, functions and operations of the apparatus, method and computer program product according to the embodiments of the present application. In this regard, each block in the flow charts or block diagrams can represent a module, a program segment or a part of code, which contains one or more executable instructions for implementing the specified logical functions. It should also be noted that, in some alternative implementations, the functions noted in the blocks can occur in different orders from those noted in the drawings. For example, two consecutive blocks can actually be executed substantially in parallel, and sometimes they can be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flow charts, and the combination of blocks in the block diagrams and / or flow charts, can be implemented by a dedicated hardware-based system for implementing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0080] In addition, each functional module in each of the embodiments of the present application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0081] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be limited by the protection scope of the claims.

Claims

1. A plug-in process management system, characterized by, The application relates to a plug-in type process management system. The plug-in type process management system comprises: N storage spaces, N being an integer greater than or equal to 2; N service plug-ins, each of which corresponds to an independent storage space, each of which is configured to receive to-be-processed service data, store the to-be-processed service data into the corresponding storage space, and copy and process the copied to-be-processed service data; wherein each of the service plug-ins is further configured to reprocess the previously stored to-be-processed service data in response to a re-execution instruction and send the reprocessed service data; and wherein the plug-in type process management system further comprises a shared storage space, and the shared storage space is configured to store service data shared by multiple service plug-ins.

2. The plug-in process management system of claim 1, wherein, Each of the independent storage spaces of the service plug-ins is configured to store service data unique to each service plug-in. The plug-in type process management system further comprises a process management component connected with each of the service plug-ins.

3. The plug-in process management system of claim 1, wherein, The process management component is configured to determine a target service plug-in that needs to reprocess service data when the service data needs to be reprocessed in a lower-level service plug-in and issue a re-execution instruction to the target service plug-in.

4. The plug-in process management system of claim 1, wherein, Each of the service plug-ins has a sleep state and a working state, and the power consumption in the sleep state is less than that in the working state.

5. The plug-in process management system according to any one of claims 1 to 4, characterized by, Each of the service plug-ins is further configured to delete the to-be-processed service data stored by itself in response to a deletion instruction.

6. An electronic device, comprising: Each of the service plug-ins is a single plug-in or a combined plug-in, and the combined plug-in comprises multiple single plug-ins. The application relates to a plug-in type process management system.

7. A business process management method characterized by, The plug-in type process management system comprises: When service data needs to be reprocessed in a lower-level service plug-in, the process management component determines a target service plug-in that needs to reprocess the service data and issues a re-execution instruction to the target service plug-in; The shared storage space is configured to store service data shared by multiple service plug-ins; Each of the independent storage spaces of the service plug-ins is configured to store service data unique to each service plug-in; The target service plug-in reprocesses the previously backed-up input service data in response to the re-execution instruction and sends the reprocessed service data; All the service plug-ins after the target service plug-in store to-be-processed service data into corresponding storage spaces, copy and process the copied to-be-processed service data when receiving the to-be-processed service data sent by a previous service plug-in.

Images