CN113467919B - Block chain-based flow management method, system and storage medium - Google Patents
Block chain-based flow management method, system and storage medium Download PDFInfo
- Publication number
- CN113467919B CN113467919B CN202110812783.3A CN202110812783A CN113467919B CN 113467919 B CN113467919 B CN 113467919B CN 202110812783 A CN202110812783 A CN 202110812783A CN 113467919 B CN113467919 B CN 113467919B
- Authority
- CN
- China
- Prior art keywords
- flow
- node
- instance
- json file
- operation information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 29
- 230000002159 abnormal effect Effects 0.000 claims abstract description 45
- 238000000034 method Methods 0.000 claims description 116
- 230000008569 process Effects 0.000 claims description 90
- 238000012544 monitoring process Methods 0.000 claims description 71
- 238000011084 recovery Methods 0.000 claims description 4
- 238000012806 monitoring device Methods 0.000 claims description 2
- 230000005856 abnormality Effects 0.000 abstract description 8
- 230000009471 action Effects 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000000903 blocking effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000017074 necrotic cell death Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 239000000725 suspension Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Abstract
The invention discloses a block chain-based flow management method, a block chain-based flow management system and a block chain-based flow management storage medium, wherein the operation result of each flow node can be monitored through a flow engine, when the operation result of a certain flow node is abnormal in flow, the flow engine can control a super node to delete operation information of the corresponding flow node with the abnormal flow, so that a JSON file of the super node is restored to a previous JSON file version, and the flow engine can return a flow instance to a flow state before the operation of the flow node with the abnormal flow according to the previous JSON file version. The invention can backup the operation information of the flow node through the super node, and timely rollback the flow instance to the flow state before the flow abnormality occurs according to the operation information of the flow node when the flow abnormality occurs, thereby avoiding the flow instance from being kept in the abnormal state for a long time and improving the safety and the reliability of the system.
Description
Technical Field
The present invention relates to the field of blockchain, and in particular, to a blockchain-based flow management method, system, and storage medium.
Background
The use of a flow engine may provide the user with functionality for management of the flow node, such as flow node access management and operation management. However, in the process of managing the flow nodes by using the flow engine, there are still problems that flow stagnation or flow interruption occurs in the flow instance in the flow engine due to various reasons.
Currently, there is temporarily no solution to the above-mentioned problems for the flow instance.
Disclosure of Invention
In view of the above, the present invention provides a blockchain-based flow management method, system, and storage medium that overcomes or at least partially solves the above-described problems.
In a first aspect, a blockchain-based flow management method includes:
a first super node on a first alliance chain obtains first operation information of a first flow node on the first alliance chain for a first flow instance;
the first supernode stores the first operation information into an old version JSON file so as to obtain a new version JSON file, wherein at least other operation information of other flow nodes except the first flow node for the first flow instance is stored in the old version JSON file, and the other flow nodes are flow nodes which operate the first flow instance before the first flow node;
a flow engine determines a current node monitoring result, wherein the flow engine is a flow engine for managing the first flow instance, the current node monitoring result is an operation result of the first flow node on the first flow instance, and the current node monitoring result includes: abnormal flow or normal flow;
if the current node monitoring result is abnormal in flow, the flow engine controls the first super node to delete the first operation information in the new version of JSON file, so that the new version of JSON file is restored to the old version of JSON file;
and the flow engine controls the first flow instance to recover to a flow state before the first flow node operates according to the old version JSON file.
With reference to the first aspect, in certain optional embodiments, the method further comprises:
if the current node monitoring result is abnormal flow, the flow engine records the identification of the first flow instance and the identification of the first flow node.
In combination with the above embodiment, in certain alternative embodiments, the method further comprises:
if the current node monitoring result is abnormal flow, the flow engine backs up first operation information of the first flow node corresponding to the abnormal flow to an abnormal flow operation information table;
the process engine controls the first process instance to recover to a process state before the first process node operates according to the old version JSON file, and the process engine comprises the following steps:
and the flow engine controls the first super node to roll back the first flow instance to a flow state before the first flow node operates according to the old version JSON file.
In combination with the second embodiment, in some optional embodiments, the process engine controlling the first supernode to delete the first operation information in the new version JSON file includes:
the process engine analyzes the new version of JSON file to obtain the operation information of each process node in the new version of JSON file;
and the flow engine controls the first super node to delete the first operation information of the first flow node in the new version JSON file according to the recorded identification of the first flow instance and the recorded identification of the first flow node.
With reference to the first aspect, in some optional embodiments, the process of determining, by the flow engine, a current node monitoring result includes:
obtaining the operation time of the first process node to the first process instance in the process engine;
and the flow engine determines the monitoring result of the current node according to the operation time.
In combination with the above embodiments, in some optional embodiments, the determining, by the flow engine, the current node monitoring result according to the operation time includes:
and if the operation time does not exceed the preset time threshold, the flow engine determines that the current node monitoring result is normal in flow, otherwise, determines that the current node monitoring result is abnormal in flow.
With reference to the first aspect, in some optional embodiments, after the flow engine controls the first flow instance to restore to a flow state before the first flow node operates according to the old version JSON file, the method further includes:
and the first super node sends the flow state before the first flow instance is restored to the first flow node for operation to other flow nodes on the first alliance chain as a node updating result through the first alliance chain.
With reference to the first aspect, in some optional embodiments, before the first supernode on the first federation chain obtains the first operation information of the first flow node on the first federation chain for the first flow instance, the method further includes:
operating the first flow instance by a first flow node on the first federation chain, and recording first operation information of the first flow instance by the first flow node;
the first flow node uploads the first operation information to the first federation chain, so that a first super node on the first federation chain obtains the first operation information through the first federation chain.
In a second aspect, a blockchain-based flow management system includes: the flow engine and the first super node;
the first super node comprises: a first operation information obtaining unit and a first operation information storage unit;
the flow engine comprises: the monitoring device comprises a monitoring result determining unit, a control information deleting unit and a control flow recovery unit;
the first operation information obtaining unit is configured to obtain first operation information of a first flow node on the first alliance chain for a first flow instance;
the first operation information storage unit is configured to store the first operation information into an old version JSON file so as to obtain a new version JSON file, wherein at least other operation information of other flow nodes except the first flow node on the first flow instance is stored in the old version JSON file, and the other flow nodes are flow nodes which operate the first flow instance before the first flow node;
the monitoring result determining unit is configured to determine a current node monitoring result, where the flow engine is a flow engine that manages the first flow instance, the current node monitoring result is an operation result of the first flow node on the first flow instance, and the current node monitoring result includes: abnormal flow or normal flow;
the control information deleting unit is configured to execute, if the current node monitoring result is that the flow is abnormal, control the first super node to delete the first operation information in the new version JSON file, so that the new version JSON file is restored to the old version JSON file;
the control flow restoration unit is configured to control the first flow instance to restore to a flow state before the first flow node operates according to the old version JSON file. In a third aspect, a storage medium has stored thereon a program that when executed by a processor implements the blockchain-based flow management method of any of the above.
In a third aspect, a storage medium has stored thereon a program that when executed by a processor implements the blockchain-based flow management method of any of the above.
By means of the technical scheme, the block chain-based flow management method, the block chain-based flow management system and the storage medium can obtain first operation information of a first flow node on a first alliance chain for a first flow instance through the first super node on the first alliance chain; the first supernode stores the first operation information into an old version JSON file so as to obtain a new version JSON file, wherein at least other operation information of other flow nodes except the first flow node for the first flow instance is stored in the old version JSON file, and the other flow nodes are flow nodes which operate the first flow instance before the first flow node; a flow engine determines a current node monitoring result, wherein the flow engine is a flow engine for managing the first flow instance, the current node monitoring result is an operation result of the first flow node on the first flow instance, and the current node monitoring result includes: abnormal flow or normal flow; if the current node monitoring result is abnormal in flow, the flow engine controls the first super node to delete the first operation information in the new version of JSON file, so that the new version of JSON file is restored to the old version of JSON file; and the flow engine controls the first flow instance to recover to a flow state before the first flow node operates according to the old version JSON file. Therefore, the flow engine can monitor the operation result of each flow node, when the operation result of a certain flow node is abnormal in flow, the flow engine can control the super node to delete the operation information of the corresponding flow node with abnormal flow, so that the JSON file of the super node is restored to the previous JSON file version, and the flow engine can return the flow instance to the flow state before the operation of the flow node with abnormal flow according to the previous JSON file version. The invention can backup the operation information of the flow node through the super node, and timely rollback the flow instance to the flow state before the flow abnormality occurs according to the operation information of the flow node when the flow abnormality occurs, thereby avoiding the flow instance from being kept in the abnormal state for a long time and improving the safety and the reliability of the system.
The foregoing description is only an overview of the present invention, and is intended to be implemented in accordance with the teachings of the present invention in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present invention more readily apparent.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to designate like parts throughout the figures. In the drawings:
FIG. 1 illustrates a flow chart of a blockchain-based flow management method provided by the present invention;
FIG. 2 is a schematic diagram illustrating a block chain based flow management system according to the present invention;
fig. 3 shows a schematic structural diagram of an electronic device provided by the invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
As shown in fig. 1, the present invention provides a block chain-based flow management method, which includes:
s100, a first super node on a first alliance chain obtains first operation information of a first flow node on the first alliance chain for a first flow instance;
optionally, the first federation chain may be one of the block chain fields, where the first supernode and the first process node are both located on the first federation chain, and an authentication consensus is established between each supernode and the process node on the first federation chain, which is not limited in this aspect of the present invention.
Alternatively, the first supernode described herein may refer to the definition and interpretation of supernodes in the blockchain domain, which is not described in too much of the present invention.
Alternatively, the first federation chain may have any other number of super nodes in addition to the first super node, and may have any other number of flow nodes in addition to the first flow node, which the present invention is not limited to.
Alternatively, the first process instance described herein may refer to the definition and explanation of the process instance in the process engine field, which is not described herein too much.
Alternatively, the flow definition may be converted to a flow instance after execution. A process instance refers to an independent actual running process of a business process. Each process instance represents a thread with internal state capable of independently controlling execution, and each process instance has own independence from the inside to the outside.
Optionally, the first process node is used as a node link for operating the first process instance, and a processor or a processing role, a judging condition, an approval result (influencing the trend of the next gateway branch), an associated form number (i.e. an interface of the custom process node), an automatic approval timeout time and the like of the first process node can be configured, which are not limited in the invention.
Optionally, when the first flow node joins the first federation chain, authentication consensus may be achieved with the first supernode, that is, the first supernode records operation information of each flow node of the first flow instance, and the recorded information may be broadcast on the first federation chain. The super node may also control each operation action of the first process node, which is not limited by the present invention.
S200, the first super node stores the first operation information into an old version JSON file so as to obtain a new version JSON file, wherein the old version JSON file at least stores other operation information of other flow nodes except the first flow node on the first flow instance, and the other flow nodes are flow nodes which operate the first flow instance before the first flow node;
optionally, there may be a JSON file in the first supernode, which correspondingly stores the operation information of all the flow nodes connected to the JSON file, including the operation information of the first flow node, which is not limited in the present invention. Of course, a process node may correspond to a JSON file, which is not limited in the present invention.
Optionally, the JSON file may store operation information of the first flow node for performing various operations on the first flow instance, including operation information of operations on the first flow instance before the first flow node, which is not limited in the present invention.
Alternatively, the new version of JSON file may be understood as a JSON file added with new operation information, and the old version of JSON file may be understood as a JSON file before adding new operation information, which is not limited in the present invention.
S300, determining a current node monitoring result by a flow engine, wherein the flow engine is used for managing the first flow instance, the current node monitoring result is an operation result of the first flow node on the first flow instance, and the current node monitoring result comprises: abnormal flow or normal flow;
alternatively, the process engine may provide important functions of process node management, flow direction management, process sample management, etc. of the process instance, which is not limited by the present invention.
Optionally, a monitoring module may be embedded in the flow engine described herein, where the monitoring module may monitor the operation process and the operation result of each flow node on the flow instance, including the operation process and the operation result of the first flow node on the first flow instance, which is not limited in this invention.
Optionally, if after the first process node operates on the first process instance, the first process instance has the conditions of flow stagnation, flow suspension, or tampered configuration information, etc., the current node monitoring result is that the flow is abnormal, otherwise, the current node monitoring result is that the flow is normal, which is not limited in the invention.
S400, if the current node monitoring result is abnormal in flow, the flow engine controls the first super node to delete the first operation information in the new version JSON file, so that the new version JSON file is restored to the old version JSON file;
optionally, if the current node monitoring result is that the flow is abnormal, it is indicated that the operation of the first flow node on the first flow instance is problematic, and the correspondingly generated first operation information is also abnormal information, so that the deletion of the first operation information can be deleted, so that the new version JSON file is restored to the old version JSON file, which is not limited in the invention.
For example, if the current node monitoring result is abnormal flow, it indicates that the operation of the first flow node is inaccurate, or does not meet the requirement, or causes flow necrosis, etc. In this case, the first supernode may reject the operation of the first flow node and other flow nodes on the first flow instance, and restore the first flow instance to the modification before the modification according to the JSON file, which is not limited in the present invention.
S500, the flow engine controls the first flow instance to recover to a flow state before the first flow node operates according to the old version JSON file.
In connection with the embodiment shown in fig. 1, in certain alternative embodiments, the method further comprises:
if the current node monitoring result is abnormal flow, the flow engine records the identification of the first flow instance and the identification of the first flow node.
Optionally, the identification of the first flow instance causing the flow abnormality and the identification of the first flow node causing the flow abnormality of the first flow instance are recorded, so that the corresponding JSON file and the corresponding operation information can be found in time when needed, which is not limited in the invention.
In combination with the above embodiment, in certain alternative embodiments, the method further comprises: step 101;
step 101, if the current node monitoring result is that the flow is abnormal, the flow engine backs up the first operation information of the first flow node corresponding to the flow abnormality to an abnormal flow operation information table;
the S500 includes: step 102;
step 102, the flow engine controls the first supernode to roll back the first flow instance to the flow state before the first flow node operates according to the old version JSON file.
Optionally, if the current node monitoring result is that the flow is abnormal, the operation information of the corresponding node in the JSON file is deleted, and then the deleted operation information in the JSON file can be backed up in an abnormal flow operation information table, so that trace can be traced when needed, which is not limited in the invention.
Optionally, the monitoring component in the flow engine notifies the first supernode to roll back, and the roll back is performed according to the old version JSON file and the recorded operation information. The operation information in the JSON file of each flow instance records the current flow node, and rollback is to change the current flow node into the last flow node, which is not limited by the invention.
In combination with the second embodiment, in some optional embodiments, the controlling, by the flow engine in S400, the first supernode to delete the first operation information in the new version JSON file includes: step 201 and step 202;
step 201, the process engine analyzes the new version JSON file to obtain the operation information of each process node in the new version JSON file;
optionally, the process engine analyzes the new JSON file to obtain the operation information of each process node, where the operation information includes the first operation information of the first process node, which is not limited in the present invention.
Step 202, the process engine controls the first supernode to delete the first operation information of the first process node in the new version JSON file according to the recorded identification of the first process instance and the recorded identification of the first process node.
Optionally, in the foregoing embodiment, the identifier of the first process instance and the identifier of the first process node have been already recorded, so that a corresponding new version JSON file may be quickly found according to the identifier of the first process instance, and the first operation information of the first process node stored in the new version JSON file may be quickly located according to the identifier of the first process node.
In connection with the embodiment shown in fig. 1, in some alternative embodiments, the process of determining the current node monitoring result by the flow engine includes: step 301 and step 302;
step 301, the process engine obtains the operation time of the first process node on the first process instance;
alternatively, the operation time may be a start time or an end time of the operation of the first process instance by the first process node, or may be a duration of the operation of the first process instance by the first process node, which is not limited in the present invention.
Step 302, the flow engine determines the monitoring result of the current node according to the operation time.
Optionally, the operation time of the flow node on the flow instance is changed in a small range or almost unchanged, and if the operation time is changed greatly, it is indicated that the operation of the corresponding flow node on the flow instance causes flow abnormality, which is not limited in the present invention.
For example, in combination with the previous embodiment, in certain alternative embodiments, the step 302 includes:
and if the operation time does not exceed the preset time threshold, the flow engine determines that the current node monitoring result is normal in flow, otherwise, determines that the current node monitoring result is abnormal in flow.
With reference to the first aspect, in certain optional embodiments, after S500, the method further includes:
and the first super node sends the flow state before the first flow instance is restored to the first flow node for operation to other flow nodes on the first alliance chain as a node updating result through the first alliance chain.
Optionally, the process instance may roll back to the previous process node, so that the process instance may continue to run on the previous dead node, avoiding process blocking, which is not limited by the present invention.
With reference to the first aspect, in certain optional embodiments, before S100, the method further includes: step 401 and step 402;
step 401, a first process node on the first federation chain operates the first process instance, and the first process node records first operation information of the first process instance;
step 402, the first flow node uploads the first operation information to the first federation chain, so that a first super node on the first federation chain obtains the first operation information through the first federation chain.
As shown in FIG. 2, the present invention provides a blockchain-based flow management system, comprising: a flow engine 100 and a first supernode 200;
the flow engine 100 includes: a monitoring result determining unit 110, a control information deleting unit 120, and a control flow restoring unit 130;
the first super node 200 includes: a first operation information obtaining unit 210 and a first operation information storage unit 220;
the first operation information obtaining unit 210 is configured to obtain first operation information of a first flow node on the first federation chain for a first flow instance;
the first operation information storage unit 220 is configured to store the first operation information into an old version JSON file, so as to obtain a new version JSON file, where the old version JSON file stores at least other operation information of other flow nodes except the first flow node on the first flow instance, where the other flow nodes are flow nodes that operate on the first flow instance before the first flow node;
the monitoring result determining unit 110 is configured to determine a current node monitoring result, where the flow engine 100 is the flow engine 100 that manages the first flow instance, the current node monitoring result is an operation result of the first flow node on the first flow instance, and the current node monitoring result includes: abnormal flow or normal flow;
the control information deleting unit 120 is configured to execute, if the current node monitoring result is that the flow is abnormal, control the first supernode 200 to delete the first operation information in the new version JSON file, so that the new version JSON file is restored to the old version JSON file;
the control flow restoration unit 130 is configured to control the first flow instance to restore to a flow state before the first flow node operates according to the old version JSON file.
In connection with the embodiment shown in fig. 2, in some alternative embodiments, the process engine 100 further includes: a recording subunit;
the recording subunit is configured to record the identifier of the first flow instance and the identifier of the first flow node if the current node monitoring result is that the flow is abnormal.
In connection with the embodiment shown in fig. 2, in some alternative embodiments, the process engine 100 further includes: a backup subunit;
the backup subunit is configured to execute the backup of the first operation information of the first flow node corresponding to the flow exception to an abnormal flow operation information table if the current node monitoring result is the flow exception;
the control flow recovery unit 130 includes: a control flow recovery subunit;
the control flow restoration subunit is configured to execute a flow state before controlling the first supernode 200 to roll back the first flow instance to the first flow node for operation according to the old version JSON file.
In combination with the embodiment shown in fig. 2, in some optional embodiments, when the control information deleting unit 120 performs control to delete the first operation information in the new version JSON file by using the first supernode 200, the method specifically includes: a parsing subunit and a deleting subunit;
the analysis subunit is configured to perform analysis on the new version of JSON file to obtain operation information of each flow node in the new version of JSON file;
the deleting subunit is configured to perform control, according to the recorded identifier of the first flow instance and the identifier of the first flow node, the first supernode 200 to delete the first operation information of the first flow node in the new version JSON file.
In combination with the embodiment shown in fig. 2, in some optional embodiments, when the monitoring result determining unit 110 determines the current node monitoring result, the method specifically includes: a monitoring subunit and a determining subunit;
the monitoring subunit is configured to obtain the operation time of the first process node on the first process instance;
the determining subunit is configured to determine the current node monitoring result according to the operation time.
In combination with the above embodiment, in some optional embodiments, the determining subunit includes: a first determination subunit and a second determination subunit;
the first determining subunit is configured to execute the process engine 100 to determine that the current node monitoring result is that the process is normal if the operation time does not exceed a preset time threshold;
and the second determining subunit is configured to execute the step of determining that the current node monitoring result is abnormal in flow if the operation time exceeds a preset time threshold.
In connection with the embodiment shown in fig. 2, in some alternative embodiments, the first super node 200 further includes: a result transmitting subunit;
the result sending subunit is configured to perform, after the flow engine 100 controls the first flow instance to recover to the flow state before the first flow node performs the operation according to the old version JSON file, sending, through the first federation chain, the flow state before the first flow instance recovers to the first flow node performs the operation as a node update result to other flow nodes on the first federation chain.
In combination with the embodiment shown in fig. 2, in some alternative embodiments, the flow management system further includes: a first flow node;
the first process node comprises: an operation subunit and an uploading subunit;
the operation subunit is configured to perform an operation on a first flow instance before the first super node 200 on the first federation chain obtains first operation information of the first flow node on the first federation chain for the first flow instance, and record the first operation information of the first flow instance;
the uploading subunit is configured to perform uploading the first operation information to the first federation chain, so that the first super node 200 on the first federation chain obtains the first operation information through the first federation chain.
The present invention provides a storage medium having stored thereon a program which, when executed by a processor, implements any of the blockchain-based flow management methods described above.
As shown in fig. 3, the present invention provides an electronic device 70, said electronic device 70 comprising at least one processor 701, and at least one memory 702, bus 703 connected to said 701 processor; wherein, the processor 701 and the memory 702 complete communication with each other through the bus 703; the processor 701 is configured to invoke program instructions in the memory 702 to perform any of the blockchain-based flow management methods described above.
In this application, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In this specification, each embodiment is described in a related manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
The foregoing description is only of the preferred embodiments of the present invention and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.
Claims (10)
1. A blockchain-based process management method, comprising:
a first super node on a first alliance chain obtains first operation information of a first flow node on the first alliance chain for a first flow instance;
the first supernode stores the first operation information into an old version JSON file so as to obtain a new version JSON file, wherein at least other operation information of other flow nodes except the first flow node for the first flow instance is stored in the old version JSON file, and the other flow nodes are flow nodes which operate the first flow instance before the first flow node;
a flow engine determines a current node monitoring result, wherein the flow engine is a flow engine for managing the first flow instance, the current node monitoring result is an operation result of the first flow node on the first flow instance, and the current node monitoring result includes: abnormal flow or normal flow;
if the current node monitoring result is abnormal in flow, the flow engine controls the first super node to delete the first operation information in the new version of JSON file, so that the new version of JSON file is restored to the old version of JSON file;
and the flow engine controls the first flow instance to recover to a flow state before the first flow node operates according to the old version JSON file.
2. The method according to claim 1, wherein the method further comprises:
if the current node monitoring result is abnormal flow, the flow engine records the identification of the first flow instance and the identification of the first flow node.
3. The method according to claim 2, wherein the method further comprises:
if the current node monitoring result is abnormal flow, the flow engine backs up first operation information of the first flow node corresponding to the abnormal flow to an abnormal flow operation information table;
the process engine controls the first process instance to recover to a process state before the first process node operates according to the old version JSON file, and the process engine comprises the following steps:
and the flow engine controls the first super node to roll back the first flow instance to a flow state before the first flow node operates according to the old version JSON file.
4. The method of claim 2, wherein the flow engine controlling the first supernode to delete the first operational information in the new version of JSON file comprises:
the process engine analyzes the new version of JSON file to obtain the operation information of each process node in the new version of JSON file;
and the flow engine controls the first super node to delete the first operation information of the first flow node in the new version JSON file according to the recorded identification of the first flow instance and the recorded identification of the first flow node.
5. The method of claim 1, wherein the process of the flow engine determining the current node monitoring result comprises:
the process engine obtains the operation time of the first process node on the first process instance;
and the flow engine determines the monitoring result of the current node according to the operation time.
6. The method of claim 5, wherein the flow engine determining the current node monitoring result based on the operation time comprises:
and if the operation time does not exceed the preset time threshold, the flow engine determines that the current node monitoring result is normal in flow, otherwise, determines that the current node monitoring result is abnormal in flow.
7. The method of claim 1, wherein after the flow engine controls the first flow instance to revert to a flow state prior to operation by the first flow node in accordance with the legacy JSON file, the method further comprises:
and the first super node sends the flow state before the first flow instance is restored to the first flow node for operation to other flow nodes on the first alliance chain as a node updating result through the first alliance chain.
8. The method of claim 1, wherein before a first supernode on the first federation chain obtains first operational information for a first flow instance for a first flow node on the first federation chain, the method further comprises:
operating the first flow instance by a first flow node on the first federation chain, and recording first operation information of the first flow instance by the first flow node;
the first flow node uploads the first operation information to the first federation chain, so that a first super node on the first federation chain obtains the first operation information through the first federation chain.
9. A blockchain-based flow management system, comprising: the flow engine and the first super node;
the first super node comprises: a first operation information obtaining unit and a first operation information storage unit;
the flow engine comprises: the monitoring device comprises a monitoring result determining unit, a control information deleting unit and a control flow recovery unit;
the first operation information obtaining unit is configured to obtain first operation information of a first flow node on a first alliance chain for a first flow instance;
the first operation information storage unit is configured to store the first operation information into an old version JSON file so as to obtain a new version JSON file, wherein at least other operation information of other flow nodes except the first flow node on the first flow instance is stored in the old version JSON file, and the other flow nodes are flow nodes which operate the first flow instance before the first flow node;
the monitoring result determining unit is configured to determine a current node monitoring result, where the flow engine is a flow engine that manages the first flow instance, the current node monitoring result is an operation result of the first flow node on the first flow instance, and the current node monitoring result includes: abnormal flow or normal flow;
the control information deleting unit is configured to execute, if the current node monitoring result is that the flow is abnormal, control the first super node to delete the first operation information in the new version JSON file, so that the new version JSON file is restored to the old version JSON file;
the control flow restoration unit is configured to control the first flow instance to restore to a flow state before the first flow node operates according to the old version JSON file.
10. A storage medium having a program stored thereon, wherein the program when executed by a processor implements the blockchain-based flow management method of any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110812783.3A CN113467919B (en) | 2021-07-19 | 2021-07-19 | Block chain-based flow management method, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110812783.3A CN113467919B (en) | 2021-07-19 | 2021-07-19 | Block chain-based flow management method, system and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113467919A CN113467919A (en) | 2021-10-01 |
| CN113467919B true CN113467919B (en) | 2024-02-02 |
Family
ID=77880974
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110812783.3A Active CN113467919B (en) | 2021-07-19 | 2021-07-19 | Block chain-based flow management method, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113467919B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117075942A (en) * | 2023-08-28 | 2023-11-17 | 中电云计算技术有限公司 | Node Pod management method and system based on DaemonSet controller |
| CN117667362B (en) * | 2024-01-31 | 2024-04-30 | 上海朋熙半导体有限公司 | Method, system, equipment and readable medium for scheduling process engine |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108615153A (en) * | 2018-04-28 | 2018-10-02 | 百度在线网络技术（北京）有限公司 | Processing method, device, system, equipment and the storage medium of block chain data |
| CN110968445A (en) * | 2019-11-13 | 2020-04-07 | 泰康保险集团股份有限公司 | Node skipping method and device based on process engine and electronic equipment |
| WO2021017278A1 (en) * | 2019-07-30 | 2021-02-04 | 平安科技（深圳）有限公司 | Task execution program detection method and apparatus, and computer device and storage medium |
| CN112328433A (en) * | 2020-11-11 | 2021-02-05 | 杭州趣链科技有限公司 | Processing method and device for restoring archived data, electronic device and storage medium |
| CN112714177A (en) * | 2020-12-24 | 2021-04-27 | 天津科技大学 | PBFT improved algorithm with linear message complexity |
-
2021
- 2021-07-19 CN CN202110812783.3A patent/CN113467919B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108615153A (en) * | 2018-04-28 | 2018-10-02 | 百度在线网络技术（北京）有限公司 | Processing method, device, system, equipment and the storage medium of block chain data |
| WO2021017278A1 (en) * | 2019-07-30 | 2021-02-04 | 平安科技（深圳）有限公司 | Task execution program detection method and apparatus, and computer device and storage medium |
| CN110968445A (en) * | 2019-11-13 | 2020-04-07 | 泰康保险集团股份有限公司 | Node skipping method and device based on process engine and electronic equipment |
| CN112328433A (en) * | 2020-11-11 | 2021-02-05 | 杭州趣链科技有限公司 | Processing method and device for restoring archived data, electronic device and storage medium |
| CN112714177A (en) * | 2020-12-24 | 2021-04-27 | 天津科技大学 | PBFT improved algorithm with linear message complexity |
Non-Patent Citations (1)
| Title |
|---|
| 国内外供应链金融研究热点及发展趋势分析;叶珵珵;CNKI优秀硕士学位论文全文库;1-72 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113467919A (en) | 2021-10-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113467919B (en) | Block chain-based flow management method, system and storage medium | |
| JP4321705B2 (en) | Apparatus and storage system for controlling acquisition of snapshot | |
| JP5021929B2 (en) | Computer system, storage system, management computer, and backup management method | |
| US6330570B1 (en) | Data backup system | |
| JP4704893B2 (en) | Computer system, management computer, storage system, and backup management method | |
| US7571349B2 (en) | Configuration replication for system recovery and migration | |
| JP3140906B2 (en) | How to update and restore system files | |
| TWI575362B (en) | Backup method, pre-testing method for enviornment updating and system thereof | |
| JP5444178B2 (en) | Backup / restore processing device, backup / restore processing method and program | |
| US20110197279A1 (en) | Management methods of storage system and file system | |
| US8321860B2 (en) | Local collector | |
| US20090013012A1 (en) | Journal management method in cdp remote configuration | |
| TW201220050A (en) | Automated and self-adjusting data protection driven by business and data activity events | |
| JP2008171387A (en) | Backup system with continuous data protection | |
| JP2009288836A (en) | System failure recovery method of virtual server, and its system | |
| US20080086518A1 (en) | Session sensitive data backups and restores | |
| JP2015050560A (en) | Communication device, communication method and communication program | |
| CN111949449A (en) | Firmware recovery method, device, system, computer equipment and storage medium | |
| CN105760283A (en) | Log output method and device | |
| Cisco | Maintaining Your CSPM System | |
| CN111338847A (en) | Server management method and system capable of automatically recovering and related equipment | |
| KR102221593B1 (en) | System for maintaining the installation envoronment of computer terminals | |
| JP2007257156A (en) | Restore system and restore method | |
| US20030200309A1 (en) | Transmission network system | |
| JP2001142788A (en) | Method and device for preserving data by data updating monitor and storage medium with data preservation program stored therein |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |