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

Abstract

The invention discloses a plug-in type process management system, electronic equipment and a business process management method, and belongs to the field of computers. 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, and each business plug-in is configured to receive to-be-processed business data, store the to-be-processed business data in the corresponding storage space, copy the to-be-processed business data, and process the copied to-be-processed business data; the problem that a large amount of time needs to be consumed due to the fact that the whole business process needs to be executed again from the beginning when a certain plug-in goes wrong in an existing plug-in type process management system is solved.

Description

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

[0001] The present application relates to the field of computers, and specifically relates to a plug-in process management system, an electronic device, and a business process management method. Background Art

[0002] Plug-in process management systems are configurable and easy to create business projects. They are widely used in scenarios such as business approval processes and software development processes. These systems consist of a process management component and a series of parameterized business plug-ins. The process management component provides query access to all business plug-ins, organizes and configures business plug-ins, creates and configures business projects, and executes and schedules business plug-ins.

[0003] In current plug-in-based process management systems, when executing business processes, a higher-level plug-in processes the data it receives and then passes it to a lower-level plug-in. The lower-level plug-in then processes the data and passes it to the next level. If a plug-in fails, the entire business process must be re-executed from the beginning.

[0004] Summary of the Invention

[0005] In view of this, the purpose of this application is to provide a plug-in process management system, electronic device and business process management method to improve the existing plug-in process management system. When a plug-in fails, the entire business process needs to be re-executed from the beginning, resulting in a lot of time consumption.

[0006] The embodiment of the present application is implemented as follows:

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

[0008] In the embodiment of the present application, each business plug-in corresponds to an independent storage space, and each business plug-in can store the received business data to be processed in the corresponding storage space. In this way, when a business plug-in fails, the erroneous business plug-in can directly read the data in the storage space and re-execute it, rather than re-executing the entire process from the beginning, which greatly improves processing efficiency.

[0009] In combination with a possible implementation manner of the embodiment of the first aspect, each of the service plug-ins is further configured to respond to a re-execution instruction, reprocess the pre-stored service data to be processed, and send the reprocessed service data.

[0010] In an embodiment of the present application, each business plug-in can respond to a re-execution instruction, reprocess the pre-stored business data to be processed, and send the reprocessed business data. In this way, when a business plug-in fails, the erroneous business plug-in can directly read the data in the storage space for heavy execution, rather than re-executing the entire process from the beginning, which greatly improves processing efficiency.

[0011] In combination with a possible implementation method of the first aspect embodiment, the plug-in process management system also includes a process management component, which is connected to 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.

[0012] In an embodiment of the present application, a process management component is used to issue a re-execution instruction to a target business plug-in that needs to re-execute the business, thereby instructing the target business plug-in to reprocess the pre-stored business data to be processed, thereby eliminating the need to re-execute the entire process from the beginning, greatly improving processing efficiency.

[0013] In combination with a possible implementation manner of the embodiment of the first aspect, the plug-in process management system also includes a shared storage space; the shared storage space is configured to store business data shared by multiple business plug-ins; and the independent storage space of each business plug-in is configured to store business data unique to each business plug-in.

[0014] In the embodiment of the present application, a shared storage space is used to store business data shared by multiple business plug-ins, which can reduce the number of times the same data is sent, thereby improving execution efficiency.

[0015] In conjunction with a possible implementation manner of the embodiment 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 the power consumption in the working state.

[0016] In an embodiment of the present application, each service plug-in has a sleep state and a working state, so that the service plug-in can be configured to belong to different states. For example, each service plug-in can be placed in a "sleep state" after the entire process is executed, thereby saving power consumption.

[0017] In combination with a possible implementation of the embodiment of the first aspect, each service plug-in is further configured to respond to a deletion instruction and delete the to-be-processed service data stored in itself.

[0018] In the embodiment of the present application, in order to save the cost of data storage, after the entire process is successfully executed, a business process for cleaning up data can be automatically initiated to allow each business plug-in to delete its own stored data.

[0019] In conjunction with a possible implementation manner of the embodiment of the first aspect, each of the service plug-ins is a single plug-in or a combined plug-in, and the combined plug-in includes multiple single plug-ins.

[0020] In the embodiment of the present application, multiple single plug-ins can be combined into a combined plug-in for use, so that a series of complex processes can be combined into a combined plug-in, which can simplify the system structure and the difficulty of business process maintenance and use.

[0021] In the second aspect, an embodiment of the present application also provides a plug-in process management system, comprising: N business plug-ins and a process management component, each of the business plug-ins being configured to store the received business data to be processed in a corresponding storage space, and to copy the business data to be processed, and to process the copied business data to be processed, where N is an integer greater than or equal to 2; the process management component is connected to each business plug-in, and the process management component is configured to determine the target business plug-in that needs to re-execute the business data when the business data needs to be re-executed in the lower-level business plug-in, and to issue a re-execution instruction to the target business plug-in; the target business plug-in is configured to respond to the re-execution instruction, reprocess the pre-stored business data to be processed, and send the reprocessed business data.

[0022] In a third aspect, an embodiment of the present application further provides an electronic device, comprising: a process management system provided in the above-mentioned first aspect embodiment and / or any possible implementation method in combination with the first aspect embodiment, or a process management system provided in the above-mentioned second aspect embodiment.

[0023] In the fourth aspect, an embodiment of the present application also provides a business process management method, including: when business data needs to be re-executed in a lower-level business plug-in, the process management component determines the 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 responds to the re-execution instruction, reprocesses the input business data backed up in advance, and sends the reprocessed business data; all business plug-ins after the target business plug-in, when receiving the pending business data sent by the upper-level business plug-in, store the pending business data in the corresponding storage space, copy the pending business data, and process the copied pending business data.

[0024] In combination with a possible implementation manner of the fourth aspect, the method also includes: the process management component obtains the position of the target business plug-in in the entire business process; the process management component obtains all business plug-ins located after the target business plug-in; the process management component sends a save instruction to all business plug-ins after the target business plug-in, and the save instruction is used to instruct the business plug-in to store the received business data to be processed in the corresponding storage space.

[0025] Other features and advantages of the present application will be described in the following description. The purpose and other advantages of the present application can be realized and obtained through the structures specifically pointed out in the written description and the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without inventive work. The above and other purposes, features and advantages of the present application will be more clearly shown through the drawings.

[0027] FIG1 shows a schematic diagram showing the principle of a plug-in process management system provided in an embodiment of the present application.

[0028] FIG2 shows a schematic structural diagram of a combined plug-in provided in an embodiment of the present application.

[0029] FIG3 is an equivalent schematic diagram of FIG1 .

[0030] FIG4 shows a schematic diagram showing the principle of another plug-in process management system provided in an embodiment of the present application.

[0031] FIG5 shows a flow chart of a business process management method provided in an embodiment of the present application.

[0032] FIG6 is a schematic structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The following embodiments can be used as examples to more clearly illustrate the technical solutions of the present application, and are not intended to limit the scope of protection of the present application. It will be understood by those skilled in the art that, in the absence of conflict, the features in the following embodiments and embodiments can be combined with each other.

[0034] The terms "comprises," "comprising," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0035] Furthermore, the term "and / or" in this application is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0036] In current plug-in-based process management systems, when a business plug-in fails, the entire business process needs to be re-executed from the beginning, which consumes a lot of time. To save time, business plug-ins can be re-executed. This allows you to correct errors in a business plug-in and continue execution in the current business plug-in, rather than starting from the beginning.

[0037] In view of this, an embodiment of the present application provides a plug-in process management system that supports parallel execution of business flows. At the same time, each business plug-in can save its own input data. Therefore, when an error occurs in a business plug-in, the error can be corrected in the current business plug-in and execution can continue, rather than re-executing the entire process from the beginning.

[0038] For a better understanding, the plug-in process management system provided in an embodiment of the present application will be described below in conjunction with FIG1 . The plug-in process management system includes N storage spaces and N business plug-ins, where N is an integer greater than or equal to 2. The number N depends on the complexity of the business project. 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 when used for a business approval process is different from the structure of the plug-in process management system when used for a development process.

[0039] If a plug-in process management system is used as an application (e.g., a business approval app or a software development app), business plug-ins can be considered the functional modules that make up the entire app. As the app's design features increase, the number of corresponding business plug-ins also increases. When a new business function is needed, a new business plug-in can be added and its coordination with the existing business plug-in can be configured to implement the new function. The N storage spaces can be from the same memory, which can be divided into N parts, with each business plug-in corresponding to an independent storage space.

[0040] These N service plug-ins work together to complete a specific service project. These N service plug-ins can be configured in series or in parallel, depending on the needs of the service project, to process the specified service project. For example, in Figure 1, service plug-in 1, service plug-in 2, service plug-in 3, service plug-in 4, and service plug-in 5 are all service plug-ins. Service plug-in 1, service plug-in 4, and service plug-in 5 are connected in series, service plug-in 1, service plug-in 2, service plug-in 3, and service plug-in 5 are connected in series, and service plug-in 4 is connected in parallel with service plug-in 2 and service plug-in 3.

[0041] In traditional processes, business plug-ins 2, 3, and 4 cannot be executed simultaneously. If parallel processing is required, two separate tasks are usually created. However, in a parallel business process, these plug-ins can be executed concurrently as separate business plug-ins within the same task, saving time.

[0042] Business plug-ins can transfer data and schedule execution in sequence with other business plug-ins in parallel or series. In the series execution scenario, the upper-level plug-in stores the data in its own corresponding storage space, and at the same time, copies the data, processes the copied data, and provides the processed data to the lower-level. After receiving the data sent by the upper-level plug-in, the lower-level plug-in stores it in its own storage space, and at the same time, copies the data, processes the copied data, and then transmits the processed new data downward.

[0043] It is understandable that the structure of the plug-in process management system is not limited to that shown in Figure 1. The corresponding structure varies according to the different business processes. That is, the connection method of the N business plug-ins and the number of N can be changed according to the processing objects and usage scenarios.

[0044] Each business plug-in can be a single plug-in or a composite plug-in. A composite plug-in can include multiple single plug-ins. For example, in one embodiment, business plug-in 2, business plug-in 3, and business plug-in 4 in Figure 1 can be combined into a new composite plug-in. This composite plug-in is called a template plug-in, and its schematic diagram is shown in Figure 2. The business project configuration of the plug-in-based process management system supports template plug-ins. Such a plug-in is not a specific business plug-in, but rather a new plug-in created by combining other business plug-ins. Business projects can use such template plug-ins directly as a business plug-in. This allows a series of complex processes to be combined into a single template plug-in, simplifying the maintenance and use of business processes.

[0045] In an alternative embodiment, the plug-in-based process management system shown in Figure 1 can be simplified to the plug-in-based process management system shown in Figure 3 , where the combined plug-in 2 in Figure 3 includes the business plug-in 2, business plug-in 3, and business plug-in 4 in Figure 1 . Regardless of 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 in Figure 3 corresponds to storage space 2 '.

[0046] Each business plug-in is classified as either a parent plug-in or a subordinate plug-in based on its position in the business project's workflow. A subordinate plug-in is responsible for processing the business data (i.e., pending business data) sent by its connected parent plug-in. Multiple subordinate plug-ins can be connected in series under a given business plug-in. These subordinate plug-ins can be in parallel, processing their own business data independently. Parallel businesses can also connect sub-businesses in series, and then reunite in a business plug-in that supports multiple inputs.

[0047] Each service plug-in corresponds to an independent storage space, allowing each service plug-in to save its own input data. Each service plug-in is configured to receive service data to be processed, store the processed service data in the corresponding storage space, copy the received service data to be processed, process the copied service data, and then send the processed data.

[0048] It is understandable that different business plug-ins process the received business data in different ways, and the corresponding processing methods are also different in different application scenarios. For example, the processing methods include but are not limited to data calculation, data forwarding, format conversion, data filtering, etc.

[0049] Since each business plug-in has its own corresponding storage space, it can support the processing of multiple data streams. Even if the data streams cannot be processed at the same time, they can be stored in the storage space first. When they can be processed, the business data can be copied from the storage space for processing.

[0050] The plug-in-based process management system provided by the present application embodiment has its own corresponding storage space, so when processing data streams, the business data to be processed can be stored in the corresponding storage space, which supports parallel processing. At the same time, each business plug-in can save its own input data. Therefore, if a business plug-in fails, the error can be corrected in the current business plug-in and execution can be continued, rather than re-executing the entire process from the beginning, greatly improving processing efficiency.

[0051] Each business plug-in will copy the business data of its parent and process it on the copied business data, leaving the original parent data unchanged. In this way, if the business process needs to be re-executed, there is no need to start from the beginning. You only need to modify the configuration on the problematic business plug-in to resume execution here.

[0052] In one optional implementation, each service plug-in is further configured to respond to a re-execution instruction, reprocess previously stored pending service data, and send the re-processed service data. This allows errors in a service plug-in to be corrected and execution to continue in the current service plug-in, rather than starting over.

[0053] In one optional embodiment, the plug-in process management system further includes a process management component connected to each business plug-in. When business data needs to be re-executed in a lower-level business plug-in, the process management component is configured to identify a target business plug-in for re-execution and issue a re-execution instruction to the target business plug-in. The target business plug-in responds to the re-execution instruction, reprocesses pre-stored business data to be processed, and sends the re-processed business data.

[0054] Among them, the subordinate business plug-ins are distinguished according to their positions in the plug-in process management system. All business plug-ins that are not at the head end (or top end) can be called subordinate business plug-ins. For example, in Figure 1, business plug-in 2, business plug-in 3, business plug-in 4, and business plug-in 5 are all subordinate business plug-ins relative to business plug-in 1. If any of the above business plug-ins fails to run, it can be used as a business plug-in to re-execute business data.

[0055] The process management component organizes and configures business plug-ins to establish and configure business projects, execute and schedule business plug-ins, and can issue configuration instructions to each business plug-in to instruct each business plug-in to complete the business project together.

[0056] In an optional implementation, each service plug-in can be configured to save input data. If a service plug-in does not save input data, its subordinate plug-ins will not be able to obtain the same input data again, and thus cannot be used as the starting plug-in for re-execution. When the service needs to be re-executed, it can only be executed from the previous service plug-in. Whether each service plug-in saves input data can be configured by issuing a command from the process management component.

[0057] In one optional implementation, to save data storage costs, after the entire process successfully executes, a data cleanup process can be automatically initiated, instructing each service plug-in to delete its stored data. In this implementation, each service plug-in is also configured to respond to a delete instruction and delete its stored pending service data. The delete instruction can be sent by the process management component. After the entire process successfully executes, the process management component issues the delete instruction to each service plug-in. Each service plug-in responds to the delete instruction and deletes its stored pending service data.

[0058] In one optional implementation, each service plug-in has its own inherent properties, such as a dormant state and an active state, where the power consumption in the dormant state is lower than in the active state. A service plug-in with this property can enter a "dormant" state after the entire process completes. After preparing new configuration data, the user can re-trigger the service to resume execution from the dormant state. The process management component can issue commands to configure the service plug-in to different states.

[0059] In an optional implementation, the plug-in process management system may further include a shared storage space (not shown in the figure); configured to store business data shared by multiple business plug-ins; and each business plug-in's independent storage space is configured to store business data unique to each business plug-in. Business data can be divided into global data types and business plug-in-specific data types. When establishing a business, if the required configuration name is required by more than one plug-in, the data type is used as a global data type, otherwise as a plug-in-specific data type. By storing the global data type in the shared storage space shared by each business plug-in, the business initiator does not need to repeatedly enter redundant data when initiating a business, and can directly store the global data in the shared storage space.

[0060] Based on the same inventive concept, an embodiment of the present application also provides a plug-in process management system including: N business plug-ins and process management components, where N is an integer greater than or equal to 2, as shown in FIG4 .

[0061] N business plug-ins cooperate with each other to complete a specified business project. Each business plug-in is configured to store the received business data to be processed into a corresponding storage space, copy the business data to be processed, and process the copied business data to be processed.

[0062] The process management component is connected to each business plug-in. When business data needs to be re-executed in a lower-level business plug-in, the process management component is configured to determine the target business plug-in that needs to re-execute the business data and issue a re-execution instruction to the target business plug-in; the target business plug-in is configured to respond to the re-execution instruction, reprocess the pre-stored business data to be processed, and send the re-processed business data.

[0063] It can be understood that the implementation principle and technical effects of the above-mentioned plug-in process management system (Figure 4) are the same as those of the plug-in process management system embodiment shown in Figure 1. For the sake of brief description, for matters not mentioned in this embodiment, please refer to the corresponding content in the aforementioned plug-in process management system embodiment.

[0064] Based on the same inventive concept, the embodiment of the present application further provides a business process management method, which will be described below in conjunction with Figure 5. The business process management method shown in Figure 5 can be applied to the above-mentioned plug-in process management system.

[0065] S1: When business data needs to be re-executed in a lower-level business plug-in, the 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.

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

[0067] S2: The target service plug-in responds to the re-execution instruction, reprocesses the previously backed-up input service data, and sends the reprocessed service data.

[0068] It is understandable that each business plug-in can be configured to store the input business data in a corresponding storage space, so that when a re-execution instruction is subsequently received, the previously backed-up input business data can be reprocessed and the reprocessed business data can be sent.

[0069] S3: When receiving the to-be-processed business data sent by the upper-level business plug-in, all the business plug-ins after the target business plug-in store the to-be-processed business data in corresponding storage spaces, copy the to-be-processed business data, and process the copied to-be-processed business data.

[0070] Since each business plug-in can be configured to receive the business data to be processed, store the business data to be processed in the corresponding storage space, copy the business data to be processed, and process the copied business data to be processed, in this way, when the target business plug-in in the lower-level business plug-in re-executes the business data, all business plug-ins located after the target business plug-in will store the business data to be processed in the corresponding storage space, copy the business data to be processed, and process the copied business data to be processed when they receive the business data to be processed sent by the upper-level business plug-in.

[0071] Optionally, the method further includes: the process management component obtaining the location of the target business plug-in within the entire business process; the process management component obtaining all business plug-ins located after the target business plug-in; and the process management component sending a save instruction to all business plug-ins after the target business plug-in, the save instruction being used to instruct the business plug-in to store the received pending business data in a corresponding storage space. In this embodiment, whether each business plug-in saves received input data is configurable, and the configuration method is relatively simple, requiring only the issuance of corresponding configuration instructions. For example, issuing a save instruction can instruct the business plug-in to save the received input data.

[0072] Optionally, the method further includes: after the entire process is successfully executed, the process management component sends a deletion instruction to each business plug-in, and each business plug-in responds to the deletion instruction and deletes the to-be-processed business data stored in itself.

[0073] The business process management method provided in the embodiment of the present application has the same implementation principle and technical effects as those of the aforementioned plug-in process management system embodiment. For the sake of brief description, for matters not mentioned in the method embodiment, please refer to the corresponding content in the aforementioned plug-in process management system embodiment.

[0074] An embodiment of the present application further provides an electronic device comprising the aforementioned plug-in process management system. Optionally, as shown in FIG6 , the electronic device 200 comprises: a transceiver 210, a memory 220, a communication bus 230, and a processor 240. The various plug-ins in the aforementioned plug-in process management system can be deployed in the processor 240. The storage space in the plug-in process management system can come from the memory 220. The memory 220 can be divided into N storage spaces corresponding to the N business plug-ins.

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

[0076] The memory 220 may 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.

[0077] The processor 240 may be an integrated circuit chip with signal processing capabilities. The above-mentioned processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), a microprocessor, etc.; it may also 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. The various methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. Alternatively, the processor 240 may also be any conventional processor, etc.

[0078] The electronic device 200 mentioned above includes but is not limited to a tablet, a computer, a vehicle-mounted device, etc.

[0079] It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same and similar parts between the various embodiments can be referenced to each other.

[0080] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architectures, functions and operations of the devices, methods and computer program products according to the multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and the module, program segment or a part of the code contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or can be implemented using a combination of dedicated hardware and computer instructions.

[0081] In addition, the functional modules in each embodiment 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.

[0082] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A plug-in process management system, characterized in that: include: N storage spaces, where N is an integer greater than or equal to 2; N business plug-ins, each of which corresponds to an independent storage space, and each of which is configured to receive business data to be processed, store the business data to be processed in the corresponding storage space, copy the business data to be processed, and process the copied business data to be processed.

2. The plug-in process management system according to claim 1, characterized in that: Each of the service plug-ins is further configured to respond to the re-execution instruction, re-process the pre-stored service data to be processed, and send the re-processed service data.

3. The plug-in process management system according to claim 2, characterized in that: The plug-in process management system further includes a process management component, and the process management component is connected to each business plug-in; The process management component is configured to determine a target business plug-in that needs to re-execute the business when business data needs to be re-executed in a lower-level business plug-in, and issue a re-execution instruction to the target business plug-in.

4. The plug-in process management system according to claim 1, characterized in that: The plug-in process management system further comprises a shared storage space; the shared storage space is configured to store business data shared by a plurality of business plug-ins; The independent storage space of each service plug-in is configured to store service data unique to each service plug-in.

5. The plug-in process management system according to claim 1, characterized in that: Each service plug-in has a dormant state and a working state, and the power consumption in the dormant state is less than the power consumption in the working state.

6. The plug-in process management system according to claim 1, characterized in that: Each service plug-in is also configured to respond to a deletion instruction and delete the service data to be processed stored in itself.

7. The plug-in process management system according to any one of claims 1 to 6, characterized in that: Each of the service plug-ins is a single plug-in or a combined plug-in, and the combined plug-in includes multiple single plug-ins.

8. A plug-in process management system, characterized in that: include: N service plug-ins, each of which is configured to store the received service data to be processed in a corresponding storage space, copy the service data to be processed, and process the copied service data to be processed, where N is an integer greater than or equal to 2; A process management component connected to each business plug-in, wherein the process management component is configured to determine a target business plug-in that needs to re-execute the business data when the business data needs to be re-executed by the lower-level business plug-in, and issue a re-execution instruction to the target business plug-in; The target service plug-in is configured to respond to the re-execution instruction, reprocess the pre-stored service data to be processed, and send the re-processed service data.

9. An electronic device, characterized in that: include: A process management system as claimed in any one of claims 1 to 7, or a process management system as claimed in claim 8.

10. A business process management method, characterized in that: include: When the business data needs to be re-executed in the lower-level business plug-in, the process management component determines the 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 service plug-in responds to the re-execution instruction, reprocesses the previously backed-up input service data, and sends the reprocessed service data; When receiving the to-be-processed business data sent by the upper-level business plug-in, all the business plug-ins after the target business plug-in store the to-be-processed business data in the corresponding storage space, copy the to-be-processed business data, and process the copied to-be-processed business data.

Images