Dynamic workflow collaboration method and related equipment

Abstract

The invention discloses a dynamic workflow collaboration method and related equipment, and relates to the technical field of system architecture.The method comprises the steps that operation change data of terminal equipment is obtained; extracting structured incremental data of the operation change data through an incremental capture mechanism; determining a data transmission link of the structured incremental data based on the real-time network monitoring result; synchronizing the structured incremental data to a cloud server through a data transmission link; performing conflict resolution algorithm processing operation on the current data version stored in the cloud server and the structured incremental data to generate a target data version; sending the target data version to associated terminal equipment based on a real-time push protocol; in response to an electronic signature request triggered by the associated terminal device, controlling the cloud server to perform signature decryption operation and return encrypted signature data; and updating the workflow state of the business object according to the encrypted signature data.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of system architecture, and in particular to a dynamic workflow collaboration method and related equipment. BACKGROUND

[0002] Current business collaboration systems generally use full data synchronization mechanism, and complete business object copies need to be transmitted in the data update process. This mechanism leads to a large amount of network bandwidth resources being occupied by redundant data, especially in multi-terminal collaboration scenarios, frequent full synchronization operations result in high average synchronization delay. High delay not only reduces collaboration efficiency, but also causes data synchronization failure when the network fluctuates, affecting the continuity of business processes.

[0003] Another defect of the existing scheme is the lack of real-time state tracking capability. When multiple terminals concurrently operate the same business object, the traditional architecture cannot quickly identify and solve data conflicts, resulting in frequent version inconsistency problems. Therefore, there is an urgent need for a dynamic workflow collaboration method to solve the above-mentioned technical problems. SUMMARY

[0004] A series of simplified concepts are introduced in the summary section, which will be further described in detail in the specific embodiments section. The summary section of the present application does not mean to attempt to limit the key features and necessary technical features of the claimed technical solutions, nor to attempt to determine the protection scope of the claimed technical solutions.

[0005] In a first aspect, the present application provides a dynamic workflow collaboration method, comprising:

[0006] Obtaining operation change data of a terminal device;

[0007] Extracting structured incremental data of the operation change data through an incremental capture mechanism;

[0008] Based on real-time network monitoring results, determining a data transmission link of the structured incremental data;

[0009] Synchronizing the structured incremental data to a cloud server through the data transmission link;

[0010] Performing conflict resolution algorithm processing operation on the current data version stored in the cloud server and the structured incremental data to generate a target data version;

[0011] Based on a real-time push protocol, sending the target data version to an associated terminal device;

[0012] In response to an electronic signature request triggered by the associated terminal device, controlling the cloud server to perform signature decryption operation and return encrypted signature data;

[0013] According to the encrypted signature data, the workflow state of the business object is updated.

[0014] In some embodiments, the structured incremental data of the operation change data is extracted through an incremental capture mechanism, including:

[0015] Based on the operation log capture mechanism, the change data sequence generated by the user operation is determined;

[0016] The change data sequence is structured and parsed to generate structured change records containing field identification and change content;

[0017] Based on the differential extraction algorithm, the incremental data is separated from the structured change record to generate structured incremental data.

[0018] In some embodiments, based on the real-time network monitoring result, the data transmission link of the structured incremental data is determined, including:

[0019] Based on the preset monitoring frequency, the network round-trip time sequence is obtained in real time;

[0020] Based on the network round-trip time sequence, the average value of the time delay of the preset number of continuous monitoring is calculated;

[0021] Based on the average value of the time delay and the first preset time delay threshold, the main transmission link state is determined;

[0022] Based on the main transmission link state, the data transmission link is determined;

[0023] When the average value of the time delay is less than or equal to the first preset time delay threshold, the main transmission link state is determined to be in an available state, and the data transmission link is determined to be the main transmission link based on the available state; When the average value of the time delay is greater than the first preset time delay threshold, the main transmission link state is determined to be in an unavailable state, and the data transmission link is determined to be a backup transmission channel based on the unavailable state.

[0024] In some embodiments, the structured incremental data is synchronized to the cloud server through the data transmission link, including:

[0025] Based on the type identification of the data transmission link, the data transmission mode is determined;

[0026] When the type identification is the main transmission link, the default network interface is controlled to perform the encrypted transmission operation of the structured incremental data; or,

[0027] When the type identification is the backup transmission channel, the standby network interface is activated and a secure tunnel is established;

[0028] Based on the secure tunnel, the encrypted transmission operation of the structured incremental data is performed;

[0029] The completion state of the encrypted transmission operation is monitored;

[0030] When the completion status is success, a synchronization completion identifier of the cloud server is generated.

[0031] In some embodiments, the current data version stored in the cloud server and the structured incremental data are processed by a conflict resolution algorithm to generate a target data version, including:

[0032] A first version identifier of the current data version and a corresponding first cloud timestamp are obtained;

[0033] A second version identifier contained in the structured incremental data and a corresponding second terminal timestamp are obtained;

[0034] Based on a preset time tolerance threshold and the second terminal timestamp, a conflict determination critical time value is calculated;

[0035] Based on the first cloud timestamp and the conflict determination critical time value, a data merging strategy is determined;

[0036] Based on the data merging strategy, the current data version and the structured incremental data are merged to generate a target data version.

[0037] In some embodiments, based on a real-time push protocol, the target data version is sent to an associated terminal device, including:

[0038] Based on the target data version and a preset WebSocket long connection channel, a push server is controlled to perform a notification message packaging operation to generate a notification message packaging operation result;

[0039] Based on the notification message packaging operation result, a lightweight notification message is generated, wherein the lightweight notification message contains a version change field and a merge identifier;

[0040] Based on an event triggering mechanism of the WebSocket long connection channel, the lightweight notification message is sent to a specified callback interface of the associated terminal device;

[0041] Based on a message reception confirmation signal returned by the associated terminal device, a push completion status of the target data version is determined.

[0042] In some embodiments, in response to an electronic signature request triggered by the associated terminal device, the cloud server is controlled to perform signature decryption operation and return encrypted signature data, including:

[0043] Based on the electronic signature request, a request parameter set is parsed, wherein the request parameter set contains a user identifier and a business object identifier;

[0044] Based on the user identifier, a biological feature verification interface is called to obtain real-time biological feature data;

[0045] determine an identity authentication state based on the real-time biometric data and the pre-stored biometric template;

[0046] extract a signature ciphertext from a cloud signature library based on the business object identifier when the identity authentication state is verified;

[0047] perform a decryption operation on the signature ciphertext based on an AES-GCM algorithm to generate plaintext signature data;

[0048] perform real-time encryption on the plaintext signature data based on a pre-set encryption key to generate encrypted signature data;

[0049] package the encrypted signature data into a structured response data packet, wherein the structured response data packet includes a message digest header and an encrypted payload;

[0050] return the structured response data packet based on the network address of the associated terminal device.

[0051] In some embodiments, updating the workflow state of the business object according to the encrypted signature data includes:

[0052] verify the integrity of the encrypted signature data based on the message digest header in the encrypted signature data;

[0053] when the integrity is valid, generate plaintext signature based on the encrypted payload of the encrypted signature data and a pre-set decryption key;

[0054] determine the signature embedding position of the target business document based on the plaintext signature and the business object identifier;

[0055] render the plaintext signature to the document object model of the target business document based on the signature embedding position;

[0056] update the current node identifier of the workflow state based on the rendered document object model;

[0057] broadcast the workflow state change event to all associated terminal devices based on the updated current node identifier and a real-time push protocol.

[0058] In a second aspect, the application provides a dynamic workflow collaboration device, comprising:

[0059] a change capture unit for obtaining operation change data of a terminal device;

[0060] an incremental extraction unit for extracting structured incremental data of the operation change data through an incremental capture mechanism;

[0061] a link decision unit for determining a data transmission link of the structured incremental data based on real-time network monitoring results;

[0062] a cloud synchronization unit configured to synchronize the structured incremental data to a cloud server via a data transmission link;

[0063] a conflict resolution unit configured to perform a conflict resolution algorithm on the current data version stored in the cloud server and the structured incremental data to generate a target data version;

[0064] a data pushing unit configured to send the target data version to the associated terminal device based on a real-time pushing protocol;

[0065] a signature processing unit configured to, in response to an electronic signature request triggered by the associated terminal device, control the cloud server to perform a signature decryption operation and return encrypted signature data;

[0066] a state updating unit configured to update a workflow state of the business object according to the encrypted signature data.

[0067] In a third aspect, an electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor is configured to implement the steps of the dynamic workflow collaboration method of any one of the first aspect when executing the computer program stored in the memory.

[0068] In a fourth aspect, the present application provides a computer readable storage medium storing a computer program, and the computer program is executable by a processor to implement the steps of the dynamic workflow collaboration method of any one of the first aspect.

[0069] In summary, the present application extracts the structured incremental data of the operation change, synchronizes only the field-level change content, reduces the data transmission amount, dynamically selects the optimal transmission link in combination with real-time network monitoring to avoid transmission interruption caused by network fluctuations, uses a time window constrained conflict resolution algorithm in the cloud server to ensure the consistency of the data version in the case of multi-terminal concurrent operation, implements second-level state pushing based on a lightweight notification message and a long connection channel to enable the associated terminal to perceive the workflow change in real time, and in particular, the cloud server centrally processes the electronic signature decryption operation to improve the security verification response speed, and the encrypted signature data drives the automatic updating of the workflow state to ensure that the key business operation can still be continuously executed in a deteriorated network environment.

[0070] The dynamic workflow collaboration method of the present application, other advantages, objects and features of the present application will be embodied in part through the following description, and will be understood by those skilled in the art through research and practice of the present application. BRIEF DESCRIPTION OF DRAWINGS

[0071] 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 embodiment. The accompanying drawings are included to provide a description of preferred embodiments, and are not intended to limit the present description to the illustrated embodiments. Moreover, the same reference numerals in different figures indicate same or similar components. In the drawings:

[0072] Figure 1 A dynamic workflow collaboration method flow diagram provided for an embodiment of the present application;

[0073] Figure 2 A dynamic workflow collaboration device structure diagram provided for an embodiment of the present application;

[0074] Figure 3 A dynamic workflow collaboration electronic device structure diagram provided for an embodiment of the present application. DETAILED DESCRIPTION

[0075] The terms "first", "second", "third", "fourth" and the like in the description and in the claims of the present application, if any, are used for distinguishing between similar objects and not necessarily for describing a specific sequential or chronological order. It is to be understood that the use of these terms are interchangeable under appropriate circumstances such that the embodiments of the present application described herein are, for example, capable of orderly or chronological logical rearrangement. Furthermore, the terms "comprise", "comprising", "include", "including", and the like, are specifically intended to be open-ended. That is, references to individual steps and / or units do not sunder the inclusion of additional steps or units, whether or not, however, additional steps or units are specifically recited in the claims of the present application. The following detailed description of the embodiments of the present application will be made with reference to the accompanying drawings, in which:

[0076] Reference will now be made to Figure 1 A dynamic workflow collaboration method flow diagram provided for an embodiment of the present application, specifically can include:

[0077] S110, obtaining operation change data of a terminal device;

[0078] Exemplarily, in a dynamic workflow collaboration scenario, the terminal device generates operation change data by capturing user operation events in real time. Specifically, when the user performs an active operation such as editing, configuring, or state adjustment on a business object, the terminal device captures the original change record generated by the operation behavior in time sequence in real time through the built-in operation log recording module. These change data are temporarily stored in the terminal local cache area in the form of structured logs, and the content covers core fields such as operation type identifier, operation timestamp, target object identifier, and change content description. This process is independent of specific business scenarios and can be adapted to various collaboration modes such as document collaboration, design review, and task assignment, ensuring that data collection is completed within milliseconds after the user triggers the operation, and providing low-latency raw input for subsequent incremental synchronization.

[0079] S120, extracting structured incremental data of operation change data through an incremental capture mechanism;

[0080] Exemplarily, in a business collaboration scenario, the terminal device continuously monitors user operation events based on an operation log capture mechanism, and generates a change data sequence containing operation type identifier and timestamp when detecting editing or configuration changes on a business object. The sequence is processed by a structured parsing engine to separate field identifiers and corresponding change content segments, forming machine-readable structured change records. Then, a differential extraction algorithm is used to incrementally compare adjacent operation records, and only the newly added or modified field data is retained, finally generating a lightweight structured incremental data packet. This process ensures that the transmission content only contains necessary change information, which is smaller than the size of the full business object data, laying a foundation for low-latency synchronization.

[0081] S130, determining a data transmission link of the structured incremental data based on real-time network monitoring results;

[0082] Exemplarily, during the operation of the business collaboration system, the terminal device continuously performs network state monitoring operations, and acquires a continuous measurement value sequence of network round-trip delay at a preset frequency. Based on the delay sequence, the average delay value in the sliding window is calculated in real time, and the calculation result is dynamically compared with a preset delay threshold. When the average delay value is in an acceptable range, the communication channel of the main transmission link is maintained as the data synchronization path; when it is detected that the average delay value continuously exceeds the tolerance range, a backup network interface is activated and an encrypted tunnel is established, and the backup transmission channel is switched to the current data transmission link. This link decision mechanism based on real-time network quality evaluation avoids the interference of network fluctuations on the transmission of business data packets, and ensures that the structured incremental data can select the optimal transmission path to complete cloud synchronization under any network condition.

[0083] S140, synchronizing the structured incremental data to a cloud server through the data transmission link;

[0084] Exemplarily, after determining the data transmission link of the structured incremental data, the terminal device performs a differential transmission control process according to the link type identification. When the link type is a main transmission link, the terminal device directly calls a default network communication interface to perform an encryption and packaging operation on the structured incremental data, and transmits the data packet to the cloud server through an established regular network channel; when the link type is a backup transmission channel, the terminal device first activates a backup network hardware interface and negotiates encryption protocol parameters, and then performs an encryption transmission operation of the structured incremental data after establishing an end-to-end encryption tunnel. The transmission process continuously monitors the data packet sending state and the cloud response signal, and when a complete receiving confirmation instruction returned by the cloud server is received, a synchronization completion state identifier with a time stamp is generated locally in the terminal.

[0085] S150, performing a conflict resolution algorithm processing operation on the current data version stored in the cloud server and the structured incremental data to generate a target data version;

[0086] Exemplarily, in a business collaboration scenario, after the cloud server obtains the structured incremental data, it immediately performs a conflict resolution algorithm processing operation to generate a target data version. This operation first extracts the first version identifier of the current cloud data version and its corresponding cloud timestamp, and simultaneously parses the second version identifier and the terminal timestamp embedded in the structured incremental data packet. Based on a preset time tolerance threshold, a conflict determination critical time value is dynamically calculated, and the data merging strategy is determined by comparing the numerical relationship between the cloud timestamp and the critical time value: when the cloud timestamp exceeds the critical value, the cloud data version is directly used; otherwise, the current data version and the incremental data are subjected to field-level semantic merging operation, and finally a target data version containing a merging identifier is generated.

[0087] S160, based on a real-time push protocol, sending the target data version to the associated terminal device;

[0088] Exemplarily, after the target data version is generated, the cloud server pushes the update information to all associated terminal devices through a pre-established WebSocket long connection channel. The push server first encapsulates the changed fields and the merging identifier in the target data version into a lightweight notification message, which is compressed in binary format to reduce transmission load. Based on the event triggering mechanism, the encapsulated notification message is instantaneously sent to the preset callback interface of each terminal, ensuring that the terminal can receive the update without active query. During the push process, the message receiving confirmation signals returned by the associated terminal are continuously monitored, and when all target terminals return valid confirmation, the push completion state is recorded; if it is detected that part of the terminals do not respond in time, a limited number of supplementary pushes are performed according to the preset retransmission strategy. This real-time push mechanism based on long connection ensures that the workflow state change information covers all collaborative terminals within milliseconds, so that the version state of the business object remains synchronized.

[0089] S170, in response to the electronic signature request triggered by the associated terminal device, controlling the cloud server to perform signature decryption operation and return encrypted signature data;

[0090] Exemplarily, in the business collaboration scenario, when the associated terminal device triggers the electronic signature request, the cloud server immediately starts the centralized security processing flow. The flow first parses the user identity and target business object identifier in the request, calls the biometric verification interface based on the identity to complete real-time identity verification. After verification, the cloud server extracts the encrypted signature data corresponding to the target business object from the secure storage area, and performs decryption operation using the AES-GCM algorithm to generate plaintext signature content. To ensure transmission security, the system performs dynamic encryption processing on the plaintext signature and encapsulates it as a structured response data packet, which contains a message digest header for integrity verification and a payload body storing encrypted content. Finally, the response data packet is returned to the terminal device that initiates the request through an encrypted link.

[0091] S180, updating the workflow state of the business object according to the encrypted signature data.

[0092] Exemplarily, in the business collaboration system, after the associated terminal device receives the encrypted signature data from the cloud server, it performs integrity verification and decryption operation to generate plaintext signature content, then locates the signature embedding position of the target document according to the business object identifier, dynamically implants the signature data into the specified area of the document through the document object model rendering engine, triggers the workflow state machine update mechanism after implantation, pushes the current node identifier to the next collaboration stage, and finally broadcasts the state change event to all associated parties through the real-time push channel, forming the update flow from signature completion to state synchronization of the business object.

[0093] In summary, the embodiment of the present application optimizes the utilization of network bandwidth resources by extracting the structured incremental change data and synchronizing only the field-level change content instead of transmitting the full data; dynamically selects the optimal transmission link based on real-time network quality monitoring, quickly completes the primary and backup link switching in network fluctuations, effectively avoids synchronization interruption and maintains the collaboration continuity between the terminal device and the cloud server; uses the time window constrained conflict resolution algorithm in the cloud to dynamically decide the merging strategy based on the terminal timestamp and the preset tolerance threshold, ensuring the consistency of data versions in multi-terminal concurrent operation; implements instantaneous state pushing based on lightweight notification messages and long connection channels, making the change content synchronized across terminals in a very short time; and particularly, by integrating biometric authentication, ciphertext decryption and dynamic encryption into atomic operations through the centralized signature processing mechanism in the cloud, the electronic signature response time is compressed, and the document object model rendering and workflow state automatic update are driven by encrypted signature data, which improves the end-to-end collaboration timeliness and system robustness in a deteriorating network environment.

[0094] In some examples, the structured incremental data of the operation change data is extracted by an incremental capture mechanism, including: determining a sequence of change data generated by a user operation based on an operation log capture mechanism;

[0095] The sequence of change data is structured parsed to generate structured change records containing field identifiers and change contents;

[0096] The incremental data is separated from the structured change records based on a differential extraction algorithm to generate structured incremental data.

[0097] For example, in a business collaboration system, a terminal device continuously monitors a user interface operation event stream through an operation log capture mechanism. When an editing, configuration or state adjustment operation on a business object is detected, the system generates a sequence of change data containing an operation type identifier, a timestamp sequence and a target object identifier with millisecond-level time accuracy. The sequence is temporarily stored in a ring buffer form in the local storage area of the terminal to ensure that the original data collection is completed within a very short time after the user operation is triggered, providing a low-latency input source for incremental extraction.

[0098] After obtaining the sequence of change data, a structured parsing engine performs field-level semantic analysis on the original log entries. First, the key metadata in the operation record is identified, and the field identifier (such as document paragraph number, form control ID, etc.) and the corresponding change content fragment are separated; then, according to the preset template mapping rule, the unstructured content fragment is converted into a machine-readable key-value pair format, generating a triple structured change record containing field identifier, change type marker and content value.

[0099] Based on the differential extraction algorithm, the continuous structured change records are incrementally compared. The algorithm first establishes the field identifier mapping relationship between adjacent records, identifies the newly added field identifier set and the modified field content fragment through hash value comparison; then filters the unchanged field data, only retains the difference part and encapsulates it as a lightweight structured incremental data packet. This process uses a sliding window mechanism to maintain the last two valid records, and the window size is dynamically adjusted by a preset operation continuity threshold, ensuring that the incremental data packet always reflects the latest change content. The size of the final output structured incremental data packet is smaller than that of the full business object.

[0100] In summary, the embodiments of the present application separate the field-level change content through real-time capture and structured parsing of operation logs, greatly reducing the amount of data to be synchronized compared to traditional full transmission; combined with the differential extraction algorithm controlled by the sliding window, the incremental data packet only contains the necessary change information, avoiding the occupation of network bandwidth by redundant data transmission; the triple format design of the structured change record enhances system compatibility, which can adapt to various business object types such as documents, forms, process configurations, etc., improving the response speed and resource utilization of the workflow collaboration system.

[0101] In some examples, based on the real-time network monitoring result, the data transmission link of the structured incremental data is determined, comprising:

[0102] Based on the preset monitoring frequency, the network round-trip time sequence is obtained in real time;

[0103] Based on the network round-trip time sequence, the average value of the time delay monitored for a preset number of times is calculated;

[0104] Based on the average value of the time delay and the first preset time delay threshold, the main transmission link state is determined;

[0105] Based on the main transmission link state, the data transmission link is determined;

[0106] Wherein, when the average value of the time delay is less than or equal to the first preset time delay threshold, the main transmission link state is determined to be in an available state, and the data transmission link is determined to be the main transmission link based on the available state; when the average value of the time delay is greater than the first preset time delay threshold, the main transmission link state is determined to be in an unavailable state, and the data transmission link is determined to be a backup transmission channel based on the unavailable state.

[0107] For example, the terminal device performs a network state acquisition operation based on a preset monitoring frequency, and obtains a continuous measurement value sequence of the network round-trip time in real time by periodically sending probe data packets and receiving responses. The sequence is stored in the terminal cache area in chronological order, forming a complete observation record of the network round-trip time sequence. Wherein, the preset monitoring frequency is dynamically configured according to the real-time requirement of the business cooperation scene, to ensure the timeliness of network state evaluation and the balance of system resource occupation.

[0108] Based on the network round-trip time sequence, the terminal device performs a sliding window calculation operation. Specifically, the latest continuous preset number of time delay measurement values are selected as calculation samples, and an arithmetic average operation is performed on the sample set to generate a time delay average value index. This calculation process uses a dynamic window mechanism, and the window size is positively correlated with the transmission sensitivity of business data, to ensure that the network quality evaluation result accurately reflects the current transmission environment state.

[0109] The terminal device compares the average value of the time delay with the first preset time delay threshold in real time, and performs a main transmission link state determination operation. When the average value of the time delay is less than or equal to the first preset time delay threshold, it is determined that the main transmission link is in an available state; when the average value of the time delay is continuously greater than the first preset time delay threshold, it is determined that the main transmission link enters an unavailable state. The first preset time delay threshold is jointly calibrated according to historical network quality data and business tolerance delay.

[0110] Based on the determination result of the main transmission link state, the terminal device performs a data transmission link decision operation. When the state is available, the main transmission link composed of the default network interface is selected as the data transmission channel; when the state is unavailable, the standby network interface is immediately activated and an end-to-end encryption tunnel is established, and the backup transmission channel is switched to the current data transmission link. Transmission handshake verification and link stability test are performed during the switching process to ensure that the new link meets the synchronization requirements of structured incremental data.

[0111] In summary, the embodiments of the present application use real-time network monitoring and dynamic link decision mechanism. When the network quality fluctuates, the system automatically switches to the backup transmission channel, effectively avoiding data synchronization interruption caused by main link degradation. The average delay calculation based on the sliding window reflects the network state change trend, making the link switching decision forward-looking. Seamless switching of the main and backup links ensures the continuity of business collaboration processes, especially in high-delay network environments, improving the synchronization success rate of terminal devices to cloud servers, and providing communication support for real-time workflow state synchronization.

[0112] In some examples, the structured incremental data is synchronized to the cloud server through the data transmission link, including:

[0113] Based on the type identification of the data transmission link, the data transmission mode is determined;

[0114] When the type identification is the main transmission link, the default network interface is controlled to perform the encryption transmission operation of the structured incremental data; or when the type identification is the backup transmission channel, the standby network interface is activated and a secure tunnel is established;

[0115] Based on the secure tunnel, the encryption transmission operation of the structured incremental data is performed;

[0116] The completion status of the encryption transmission operation is monitored;

[0117] When the completion status is successful, a synchronization completion identifier of the cloud server is generated.

[0118] For example, the terminal device performs differential transmission control based on the type identification of the data transmission link. When the type identification points to the main transmission link, the terminal device calls the default network communication interface, performs standardized encryption and packaging operation on the structured incremental data, and transmits the encrypted data packet to the cloud server through the preset main network channel. This process uses a continuous session mechanism to maintain connection stability. When the type identification points to the backup transmission channel, the terminal device activates the physical layer or virtualized standby network interface, establishes an end-to-end encryption tunnel through a security protocol negotiation module, and performs the transmission operation of the structured incremental data in the encryption tunnel. The tunnel uses a two-way authentication mechanism to ensure channel security.

[0119] In the data transmission process, the terminal device starts the transmission state monitoring module to collect the data packet sending state code and the cloud response signal in real time. The monitoring module dynamically determines the completion state of the encrypted transmission operation by analyzing the protocol layer feedback information, including data packet complete arrival, partial loss or timeout failure, etc. When the monitoring module detects the complete receiving confirmation instruction returned by the cloud server, the instruction contains the data packet verification digest and the receiving timestamp, and the terminal device generates a synchronous completion identifier with an accurate time marker and stores it in the local log system.

[0120] If an abnormal transmission state is detected, such as data packet verification failure or response timeout, the terminal device automatically triggers the incremental data retransmission mechanism. The retransmission mechanism selects a differentiated strategy according to the abnormal type: for data packets with verification failure, perform local retransmission, keeping the original transmission link unchanged; for response timeout, re-evaluate the network state and trigger the link switching process if necessary. The number of retransmissions is limited by a preset upper limit to avoid invalid transmission occupying system resources.

[0121] The generation of the synchronous completion identifier marks the consistency of the terminal device and the cloud server data, and the identifier contains three elements: data packet unique hash value, cloud receiving timestamp and transmission link type code. The terminal device synchronizes the identifier to the state management service to drive the subsequent conflict resolution process to start. At the same time, the identifier information is written into the persistent storage system to provide traceable records for transmission audit.

[0122] In summary, the embodiment of the present application realizes seamless switching between primary and backup links through a differentiated transmission control mechanism driven by link type, ensures that structured incremental data can still be reliably synchronized to the cloud in a network fluctuation environment; the dual protection of encrypted tunnel and protocol layer monitoring effectively prevents the risk of eavesdropping and tampering during data transmission; the intelligent retransmission strategy based on state code improves the transmission success rate and avoids the resource waste of traditional fixed retry mechanism; the three-element design of the synchronous completion identifier provides accurate version tracing basis for cloud conflict resolution, forming a key link between the terminal device and the cloud server. Finally, a high-robustness and auditable data transmission is built to provide bottom communication support for workflow collaboration.

[0123] In some examples, the current data version stored in the cloud server and the structured incremental data are processed by a conflict resolution algorithm to generate a target data version, including:

[0124] Obtain the first version identifier of the current data version and the corresponding first cloud timestamp;

[0125] Obtain the second version identifier contained in the structured incremental data and the corresponding second terminal timestamp;

[0126] Based on the preset time tolerance threshold and the second terminal timestamp, calculate the conflict judgment critical time value;

[0127] determining a data merging strategy based on the first cloud timestamp and the conflict determination threshold time value;

[0128] merging the current data version and the structured incremental data based on the data merging strategy to generate a target data version.

[0129] For example, after receiving the structured incremental data, the cloud server first obtains the first version identifier of the current data version and the corresponding first cloud timestamp. The timestamp records the last update time of the data version using the UTC millisecond time system. The second version identifier and the associated second terminal timestamp embedded in the structured incremental data packet are synchronously parsed. The timestamp is marked by the terminal device when generating the incremental data. By extracting the time reference information of the above-mentioned double versions, a time sequence comparison basis is established for subsequent conflict determination.

[0130] Based on the preset time tolerance threshold and the second terminal timestamp, the cloud server performs dynamic calculation of the conflict determination threshold time value. The calculation process performs an arithmetic addition operation on the second terminal timestamp and the preset time tolerance threshold to generate the conflict determination threshold time value. The preset time tolerance threshold is pre-configured according to the real-time requirement of the business scenario, and is used to define the maximum time tolerance interval of the validity of the terminal local version. This step ensures that the conflict determination standard considers the timeliness of terminal operation and the newness of cloud data.

[0131] The cloud server compares the first cloud timestamp with the conflict determination threshold time value to determine the data merging strategy. When the first cloud timestamp is greater than the conflict determination threshold time value, it is determined that the cloud data version is higher than the terminal local version, and therefore the direct overwrite strategy is adopted, and the current cloud data version is determined as the valid target version. When the first cloud timestamp is less than or equal to the conflict determination threshold time value, it is determined that the terminal local version still has timeliness validity, and the field-level semantic merging operation process is triggered.

[0132] In the field-level semantic merging operation, the system compares the differences between the current cloud data version and the structured incremental data field by field. For text type fields, paragraph-level difference merging based on semantic units is performed to retain valid modified content of both versions. For numerical type fields, a preset weight factor is used for weighted calculation to generate a merged value. For enumeration type fields, the latest operation priority strategy is implemented according to the operation timestamp. The merging process strictly follows the data mode constraint to ensure the business logic integrity of the merging result.

[0133] After the data merging process is completed, the system generates a target data version containing a merging identifier. This version marks the operation result type processed by the conflict resolution algorithm, while inheriting the timestamp metadata of the double version. The target data version is stored persistently in the cloud database and the global version index is updated by the version management service, providing a complete link for subsequent data tracing.

[0134] In summary, the embodiments of the present application dynamically select the optimal merging strategy through the time window constrained double version timing comparison mechanism, effectively avoiding the data version splitting problem caused by multi-terminal concurrent operation; based on the differential merging operation of field-level semantics, the effective operation of the terminal is retained while the cloud data update is compatible, ensuring that the merging result meets the business rules; the inheritance design of the merging identifier and the timestamp metadata provides version tracing basis for workflow state synchronization, reduces conflict resolution delay and improves data consistency guarantee strength.

[0135] In some embodiments, based on the real-time push protocol, the target data version is sent to the associated terminal device, including:

[0136] Based on the target data version and the preset WebSocket long connection channel, the push server is controlled to perform a notification message packaging operation to generate a notification message packaging operation result.

[0137] Based on the notification message packaging operation result, a lightweight notification message is generated, wherein the lightweight notification message contains a version change field and a merging identifier.

[0138] Based on the event triggering mechanism of the WebSocket long connection channel, the lightweight notification message is sent to the specified callback interface of the associated terminal device.

[0139] Based on the message reception confirmation signal returned by the associated terminal device, the push completion state of the target data version is determined.

[0140] For example, the cloud server performs a notification message packaging operation based on the generated target data version and the pre-established WebSocket long connection channel. This operation first extracts the version change field in the target data version and the merging identifier generated by the conflict resolution process, and encodes it into a lightweight data structure; then it calls a binary compression algorithm to package the data structure, generating a notification message packaging operation result. This process ensures that the notification message only contains necessary state change information, avoiding bandwidth waste caused by full data transmission, while retaining key metadata of data version evolution.

[0141] The cloud server generates a lightweight notification message based on the encapsulation operation result of the notification message. The message adopts a double-layer structure of a header identification area and a payload area: the header identification area stores a message type identifier and a protocol version number; and the payload area carries a set of version change fields processed by compression and a merge identifier. The generation of the lightweight notification message strictly follows a preset message length threshold constraint. When the number of change fields exceeds the threshold, a fragmentation encapsulation mechanism is automatically enabled to ensure that the single transmission load meets the low delay requirement.

[0142] The cloud server sends the lightweight notification message to the designated callback interface of the associated terminal device through the event triggering mechanism of the WebSocket long connection channel. When the target data version generation event is triggered, the cloud server immediately broadcasts the message to all terminal callback interfaces that subscribe to the business object change event. The sending process adopts an asynchronous non-blocking transmission mode to avoid blocking the cloud main thread while maintaining the long connection session.

[0143] The cloud server continuously monitors the message reception confirmation signals returned by the associated terminal devices and determines the push completion status of the target data version based on the same. The monitoring process sets a preset waiting time window, collects the confirmation signals returned by each terminal within the window; when all associated terminals return valid confirmation, the push status is marked as successfully completed; if it is detected that part of the terminals do not respond, limited retransmission is initiated according to the exponential backoff strategy until the maximum retry threshold is reached or all terminal confirmations are completed.

[0144] In summary, through the event triggering mechanism of the WebSocket long connection channel and the lightweight message design, the embodiments of the present application realize instantaneous push of workflow state change information, eliminate the query delay caused by the traditional polling mechanism; the fixed header and the differential encoded payload body structure reduce the amount of transmission data, so that the network resources are concentrated on the transmission of key business data; the directional delivery mechanism based on the callback interface ensures that the change notification reaches the target terminal, avoiding the broadcast storm problem; the status monitoring and intelligent retransmission strategy driven by the confirmation signal minimizes the redundant transmission while ensuring the reliability of the push, forming a low-delay and high-reliable state synchronization, which provides real-time guarantee for multi-terminal business collaboration.

[0145] In some examples, in response to an electronic signature request triggered by an associated terminal device, the control cloud server performs signature decryption operation and returns encrypted signature data, including:

[0146] Based on the electronic signature request, a set of request parameters is parsed, wherein the set of request parameters includes a user identifier and a business object identifier;

[0147] Based on the user identifier, a biological feature verification interface is called to obtain real-time biological feature data;

[0148] Determine an identity authentication state based on real-time biometric data and a pre-stored biometric template;

[0149] When the identity authentication state is verified, extract the signature ciphertext from the cloud signature library based on the business object identifier;

[0150] Based on the AES-GCM algorithm, the signature ciphertext is decrypted and operated to generate plaintext signature data;

[0151] Based on the preset encryption key, the plaintext signature data is encrypted in real time to generate encrypted signature data;

[0152] Encapsulate the encrypted signature data into a structured response data packet, wherein the structured response data packet includes a message digest header and an encrypted payload;

[0153] Based on the network address of the associated terminal device, return the structured response data packet.

[0154] For example, when the associated terminal device triggers an electronic signature request, the cloud server immediately starts the request parsing operation. This operation parses the original request message based on the transmission layer protocol, extracts the user identifier and business object identifier in the request parameter set. The user identifier is used to uniquely associate the identity certificate of the request initiator, and the business object identifier is used to locate the specific business document of the target operation. The parsing process strictly follows the preset message structure specification to ensure the integrity and accuracy of parameter extraction.

[0155] The cloud server calls the biometric verification interface based on the user identifier and initiates a biometric collection instruction to the terminal device. The terminal device collects the user's biometric raw data in real time through hardware sensors, including fingerprint images or facial feature point coordinates, etc., and transmits the encrypted real-time biometric data to the cloud server through a secure channel. This process uses a two-way certificate authentication mechanism to ensure the non-repudiation of the data transmission link.

[0156] The cloud server performs an identity authentication state determination operation. This operation performs similarity calculation on the real-time biometric data and the biometric template pre-stored in the secure storage area, and determines the consistency of the two through a preset matching threshold. If the similarity calculation result exceeds the matching threshold, an identity authentication state of verification is generated; otherwise, it is marked as verification failed and the subsequent process is terminated. The matching threshold is dynamically configured based on the business security level to ensure the strictness of the authentication.

[0157] When the identity authentication state is verified, the cloud server performs a signature ciphertext extraction operation based on the business object identifier to access the cloud signature library. The cloud signature library uses a sharded storage architecture, locates the target shard according to the hash value of the business object identifier, and retrieves the signature ciphertext data bound to the business object from the encrypted storage area. The ciphertext data is stored in a secure envelope format, including a key identifier and a ciphertext payload.

[0158] The cloud server uses the AES-GCM algorithm to perform decryption operation on the signature ciphertext. The operation first obtains the corresponding decryption key from the key management service based on the key identifier, and then calls the cryptographic hardware acceleration module to perform authentication decryption calculation. The decryption process synchronously generates a data integrity verification tag, and outputs the plaintext signature data when the tag passes the verification; if the verification fails, the key rotation mechanism is triggered and the decryption is reattempted.

[0159] The cloud server performs real-time encryption operation on the plaintext signature data based on a preset encryption key. The preset encryption key is generated by the terminal device during the session establishment stage, and forms a temporary key pair with the decryption key stored locally by the terminal. The encryption process uses a streaming encryption mode to encrypt the plaintext signature data block by block, generating encrypted signature data in the form of a ciphertext data stream.

[0160] The cloud server encapsulates the encrypted signature data into a structured response data packet. The encapsulation operation first calculates the message digest value of the encrypted signature data and writes it into the message digest header, which is used for integrity verification by the receiver; then the encrypted signature data is combined with the message digest header as a layered data structure. The length of the structured response data packet is constrained by a preset packet size threshold, and when the threshold is exceeded, the fragmentation encapsulation strategy is automatically enabled.

[0161] The cloud server returns the structured response data packet based on the network address of the associated terminal device. The operation transmits the data packet through the established end-to-end encryption link, and the transport layer protocol preferentially selects a low-latency path. The return process continuously monitors the receiving confirmation signal of the terminal device, and if no confirmation is received within a preset timeout window, it initiates a limited number of retransmissions according to the exponential backoff algorithm, until the transmission is successful or the maximum number of retries is reached.

[0162] In summary, the embodiments of the present application integrate biometric verification, signature decryption and dynamic encryption into an atomic operation chain through a centralized cloud processing architecture, eliminating the security computing load of the terminal device; the on-demand decryption mechanism based on key identifiers avoids the risk of long-term exposure of the key, and the AES-GCM algorithm ensures the integrity and confidentiality of the ciphertext processing; the layered design of the structured response data packet is compatible with the size of the signature data in different business scenarios, and the message digest header provides tamper-proofing capability during transmission; the encryption link directional transmission and intelligent retransmission strategy ensure that the response data packet reliably reaches the terminal device in a degraded network environment, providing a verifiable and anti-repudiation business operation environment for workflow collaboration.

[0163] In some examples, the workflow state of the business object is updated according to the encrypted signature data, including:

[0164] Based on the message digest header in the encrypted signature data, the integrity of the encrypted signature data is verified.

[0165] When the integrity is valid, the encrypted payload based on the encrypted signature data and the preset decryption key is generated into plaintext signature;

[0166] Based on the plaintext signature and the business object identifier, the signature embedding position of the target business document is determined;

[0167] Based on the signature embedding position, the plaintext signature is rendered to the document object model of the target business document;

[0168] Based on the rendered document object model, the current node identifier of the workflow state is updated;

[0169] Based on the updated current node identifier and the real-time push protocol, the workflow state change event is broadcasted to all associated terminal devices.

[0170] Illustratively, after the terminal device receives the structured response data packet returned by the cloud, first, the integrity verification operation is performed based on the message digest header in the data packet. The operation compares the hash value of the encrypted payload with the preset hash reference value stored in the message digest header: when they are completely consistent, it is determined that the encrypted signature data is complete and valid; if there is a difference, the data packet is discarded and an error handling process is triggered.

[0171] When the integrity verification passes, the terminal device calls the local security module to perform decryption operation. Based on the decryption key pre-negotiated in the session establishment stage, the encrypted payload is decrypted to restore the plaintext signature data. The decryption process uses a symmetric cryptography scheme as the encryption algorithm in the cloud to ensure the reversibility of data conversion. If decryption fails (such as key mismatch or data corruption), the terminal automatically initiates a re-issuance request to the cloud to maintain business continuity.

[0172] After obtaining the plaintext signature data, the terminal device locates the target business document in combination with the business object identifier. By querying the preset document structure mapping table, the signature embedding position rule set corresponding to the business object type is determined. According to the coordinate positioning algorithm (such as absolute coordinates based on document page number or anchor point coordinates relative to content block) in the rule set, the accurate embedding position coordinates of the signature in the target document are calculated. This process adapts to different formats of business documents to ensure that the positioning result meets the visual rendering requirements.

[0173] The terminal device starts the document object model rendering engine to dynamically implant the plaintext signature data into the document according to the calculated embedding position coordinates. The rendering engine analyzes the pixel matrix and transparency parameters of the signature data to generate a signature graphic object on the specified layer of the document object model, while preserving the editability of the original document content. The rendering process performs a collision detection algorithm, which automatically adjusts the signature size or transparency when detecting that the signature area overlaps with existing content to ensure document readability.

[0174] After the signature rendering is completed, the terminal device triggers a workflow state machine update operation. Based on a mapping relationship between a "signature completion" event and a state node in a preset workflow rule library, a current node identifier is pushed to a next collaboration stage. The state machine simultaneously records a timestamp and an executor identifier of the signature operation, and generates a state update instruction including a new node identifier, the timestamp, and the operator.

[0175] The terminal device broadcasts a workflow state change event to all associated terminal devices through a real-time push protocol. An event data packet encapsulates an updated node identifier, a change timestamp, and an associated business object identifier, and is pushed instantaneously via a preset WebSocket long connection channel. The broadcast adopts a publish or subscribe mode, and only terminal devices that have subscribed to the change event of the business object receive the data packet. After the push is completed, the confirmation responses of the terminal devices are listened to. If an unresponsive terminal device is detected, limited retransmission is started until all associated terminal devices confirm that the state is successfully received, thereby achieving state synchronization of the full collaboration network.

[0176] To sum up, the embodiments of the present application guarantee trusted execution of business operations through double verification of signature data integrity and decryption results; accurate rendering of a document object model is achieved based on rule-based signature positioning and intelligent collision processing; a rule-driven update mechanism of a workflow state machine ensures that state advancement complies with business logic constraints; and finally, multi-terminal state synchronization is formed relying on a real-time broadcast channel. The above-mentioned scheme eliminates the need for manual state maintenance, improves the reliability of signature operations, and reduces the delay of workflow state changes to within seconds, thereby ensuring the strong consistency and timeliness of business collaboration, especially in high-concurrency scenarios.

[0177] Please refer to Figure 2 A dynamic workflow collaboration device structure schematic diagram is provided for the embodiments of the present application, which includes:

[0178] A change capture unit 21 is configured to acquire operation change data of a terminal device.

[0179] An incremental extraction unit 22 is configured to extract structured incremental data of the operation change data through an incremental capture mechanism.

[0180] A link decision unit 23 is configured to determine a data transmission link of the structured incremental data based on real-time network monitoring results.

[0181] A cloud synchronization unit 24 is configured to synchronize the structured incremental data to a cloud server through the data transmission link.

[0182] A conflict resolution unit 25 is configured to perform a conflict resolution algorithm processing operation on a current data version stored in the cloud server and the structured incremental data, and generate a target data version.

[0183] The data pushing unit 26 is configured to send the target data version to the associated terminal device based on a real-time pushing protocol.

[0184] The signature processing unit 27 is configured to, in response to an electronic signature request triggered by the associated terminal device, control the cloud server to perform signature decryption operation and return encrypted signature data.

[0185] The state updating unit 28 is configured to update the workflow state of the business object according to the encrypted signature data.

[0186] Please refer to Figure 3 The electronic device 300 according to the embodiment of the present application comprises a memory 310, a processor 320 and a computer program 311 stored in the memory 310 and executable on the processor 320. The processor 320 implements the steps of the dynamic workflow collaboration method when executing the computer program 311.

[0187] Since the electronic device according to the embodiment of the present application is the device used to implement the dynamic workflow collaboration method according to the embodiment of the present application, the specific implementation of the electronic device according to the embodiment of the present application and various changes thereof can be understood by those skilled in the art based on the method according to the embodiment of the present application. Therefore, how the electronic device implements the method according to the embodiment of the present application will not be described in detail, and the device used to implement the method according to the embodiment of the present application belongs to the scope of protection of the present application.

[0188] In the implementation process, the computer program 311 can implement any of the embodiments of the first aspect when executed by the processor.

[0189] It should be noted that in the above embodiments, the description of each embodiment has its own emphasis, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments.

[0190] Those skilled in the art should understand that the embodiments of the present application can provide a method, a system or a computer program product. Therefore, the present application can adopt a completely hardware embodiment, a completely software embodiment or an embodiment combining software and hardware aspects. Moreover, the present application can adopt a computer program product in the form of one or more computer readable storage media containing computer readable program code.

[0191] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flow or blocks. Figure 1 one or more flow or blocks.

[0192] These computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart block or blocks. Figure 1 one or more flow or blocks. Figure 1 one or more flow or blocks.

[0193] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flow or blocks. Figure 1 one or more flow or blocks.

[0194] The embodiments of the present application also provide a computer program product, which comprises computer software instructions, when the computer software instructions are executed on a processing device, causing the processing device to perform the flow of a dynamic workflow collaboration method in the corresponding embodiments. Figure 1 The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

[0195] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through a wired or wireless manner. The computer-readable storage medium can be any available medium that can be stored by the computer or a data storage device such as a server, data center, etc. integrated with one or more available media. The available media can be a magnetic medium, an optical medium or a semiconductor medium, etc.

[0196] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0197] In several embodiments provided in the present application, it should be understood that the disclosed devices, apparatuses and methods can be implemented in other ways. For example, the apparatus embodiments described above are only schematic. The division of units is only a logical function division. Actual implementation can have another division manner. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other form.

[0198] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or they can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiments.

[0199] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be in the form of hardware and / or software functional units.

[0200] The integrated unit, if implemented in the form of a software function unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application essentially or the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes a plurality of instructions for causing a computer device to execute all or part of the steps of the embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk, and various program code storage media.

[0201] The above embodiments are only used to illustrate the technical solutions of the present application, but not limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacements for part of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

[0202] Although the preferred embodiments of the present specification have been described, those skilled in the art can make additional changes and modifications to the embodiments once they know the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present specification.

[0203] Obviously, those skilled in the art can make various modifications to the present specification without departing from the spirit and scope of the present specification. Thus, if these modifications of the present specification fall within the scope of the claims of the present specification and their equivalents, the present specification also intends to include these modifications.

Claims

1. A dynamic workflow collaboration method, characterized in that, include: Obtain operational change data from terminal devices; The structured incremental data of the operation change data is extracted through an incremental capture mechanism; Based on real-time network monitoring results, the data transmission link of the structured incremental data is determined; The structured incremental data is synchronized to the cloud server via the data transmission link. A conflict resolution algorithm is applied to the current data version stored on the cloud server and the structured incremental data to generate a target data version; Based on the real-time push protocol, the target data version is sent to the associated terminal devices; In response to an electronic signature request triggered by the associated terminal device, the cloud server is controlled to perform signature decryption operations and return encrypted signature data; Update the workflow status of the business object based on the encrypted signature data.

2. The method according to claim 1, characterized in that, The structured incremental data extracted through the incremental capture mechanism for the operation change data includes: Based on the operation log capture mechanism, the sequence of changed data generated by user operations is determined; The changed data sequence is parsed in a structured manner to generate a structured change record containing field identifiers and change content; Incremental data is separated from the structured change record based on the differential extraction algorithm to generate the structured incremental data.

3. The method according to claim 1, characterized in that, The process of determining the data transmission link of the structured incremental data based on real-time network monitoring results includes: Based on a preset monitoring frequency, the network round-trip delay sequence is acquired in real time. Based on the network round-trip delay sequence, calculate the average delay value after a preset number of continuous monitoring cycles; The status of the main transmission link is determined based on the average delay value and the first preset delay threshold. The data transmission link is determined based on the status of the primary transmission link; Specifically, when the average delay is less than or equal to the first preset delay threshold, the main transmission link is determined to be in an available state, and the data transmission link is determined to be the main transmission link based on the available state; when the average delay is greater than the first preset delay threshold, the main transmission link is determined to be in an unavailable state, and the data transmission link is determined to be a backup transmission channel based on the unavailable state.

4. The method according to claim 3, characterized in that, The process of synchronizing the structured incremental data to the cloud server via the data transmission link includes: Based on the type identifier of the data transmission link, the data transmission mode is determined; When the type is identified as the primary transmission link, the default network interface is controlled to perform encrypted transmission of the structured incremental data; or... When the type is identified as a backup transmission channel, the backup network interface is activated and a secure tunnel is established; Based on the secure tunnel, the structured incremental data is transmitted in encrypted form. Monitor the completion status of the encrypted transmission operation; When the completion status is successful, a synchronization completion identifier is generated for the cloud server.

5. The method according to claim 1, characterized in that, The step of performing a conflict resolution algorithm on the current data version stored on the cloud server and the structured incremental data to generate a target data version includes: Obtain the first version identifier and the corresponding first cloud timestamp of the current data version; Obtain the second version identifier and the corresponding second terminal timestamp contained in the structured incremental data; Based on the preset time tolerance threshold and the second terminal timestamp, calculate the critical time value for conflict determination; Based on the first cloud timestamp and the conflict determination critical time value, a data merging strategy is determined; Based on the data merging strategy, the current data version and the structured incremental data are merged to generate the target data version.

6. The method according to claim 1, characterized in that, The step of sending the target data version to associated terminal devices based on a real-time push protocol includes: Based on the target data version and the preset WebSocket long connection channel, the push server is controlled to perform a notification message encapsulation operation and generate a notification message encapsulation operation result. Based on the result of the notification message encapsulation operation, a lightweight notification message is generated, wherein the lightweight notification message includes a version change field and a merge identifier; Based on the event triggering mechanism of the WebSocket long connection channel, the lightweight notification message is sent to the specified callback interface of the associated terminal device; Based on the message reception confirmation signal returned by the associated terminal device, the push completion status of the target data version is determined.

7. The method according to claim 1, characterized in that, The step of responding to an electronic signature request triggered by the associated terminal device, controlling the cloud server to perform signature decryption operations and return encrypted signature data, includes: Based on the electronic signature request, the request parameter set is parsed, wherein the request parameter set includes a user identifier and a business object identifier; Based on the user identifier, call the biometric verification interface to obtain real-time biometric data; Based on the real-time biometric data and the pre-stored biometric template, the identity authentication status is determined; When the identity authentication status is verified, the encrypted signature is extracted from the cloud signature library based on the business object identifier; The encrypted signature is decrypted using the AES-GCM algorithm to generate plaintext signature data. The plaintext signature data is encrypted in real time based on a preset encryption key to generate encrypted signature data. The encrypted signature data is encapsulated into a structured response data packet, wherein the structured response data packet includes a message digest header and an encrypted payload body; The structured response data packet is returned based on the network address of the associated terminal device.

8. The method according to claim 1, characterized in that, The step of updating the workflow status of the business object based on the encrypted signature data includes: The integrity of the encrypted signature data is verified based on the message digest header in the encrypted signature data. When the integrity is valid, a plaintext signature is generated based on the encrypted payload of the encrypted signature data and the preset decryption key; Based on the plaintext signature and business object identifier, determine the signature embedding position of the target business document; Based on the signature embedding location, the plaintext signature is rendered onto the document object model of the target business document; Based on the rendered document object model, update the current node identifier of the workflow state; Based on the updated current node identifier and the real-time push protocol, the workflow status change event is broadcast to all associated terminal devices.

9. A dynamic workflow collaboration device, characterized in that, include: The change capture unit is used to acquire operation change data of the terminal device; An incremental extraction unit is used to extract structured incremental data of the operation change data through an incremental capture mechanism; The link decision unit is used to determine the data transmission link of the structured incremental data based on real-time network monitoring results. A cloud synchronization unit is used to synchronize the structured incremental data to a cloud server via the data transmission link; The conflict resolution unit is used to perform conflict resolution algorithm processing operations on the current data version stored on the cloud server and the structured incremental data to generate a target data version. A data push unit is used to send the target data version to associated terminal devices based on a real-time push protocol; The signature processing unit is used to respond to the electronic signature request triggered by the associated terminal device, control the cloud server to perform signature decryption calculation and return encrypted signature data; The status update unit is used to update the workflow status of the business object based on the encrypted signature data.

10. An electronic device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that the processor, when executing the computer program stored in the memory, implements the steps of the dynamic workflow collaboration method as described in any one of claims 1 to 8.

Images