A service continuity management method and system in a private network disconnection scenario

Abstract

The present application relates to the technical field of service management, in particular to a service continuity management method and system in a private network disconnection scenario, in the present application, by acquiring the service continuity constraint fingerprint corresponding to the target service object, when the private network connection state meets the disconnection condition, the original service operation object is judged and converted into a continuity operation unit based on the service continuity constraint fingerprint, and the corresponding disconnected load constraint and the disconnected continuity bridging chain recording the disconnected load constraint are generated; after the private network is restored, the constraint space matching of the candidate connection result is carried out based on the service continuity constraint fingerprint, and the connection consistency verification is carried out based on the disconnected continuity bridging chain, and then the service connection control result is generated and the connection management is carried out, which helps to form the constraint association between the load processing result during the disconnection of the private network and the service connection control process after the recovery of the private network, and improves the recovery connection consistency guarantee capability.

Description

Technical Field

[0001] This invention relates to the field of business management technology, specifically to a business continuity management method and system for scenarios where a private network is disconnected. Background Technology

[0002] In business systems carried by private networks, business terminals, business servers, and related management components typically rely on private network connections to complete processes such as submitting business requests, synchronizing business status, updating data versions, and verifying permissions. For business objects with continuous operation, phased workflow, or state maintenance requirements, the private network connection status affects the submission, confirmation, and subsequent continuation of business operations. In actual operation, private networks may experience disconnection due to link anomalies, session interruptions, channel unavailability, or changes in authentication status. Therefore, business continuity management in private network disconnection scenarios needs to consider both the handling of business operations during the disconnection period and the state continuation and data merging after the private network is restored.

[0003] Traditional methods typically employ offline caching, local queues, or offline execution rules to handle business operations generated during private network outages. For example, upon detecting private network unavailability, operation requests generated by business terminals are cached locally and submitted to the server in cached order after the private network is restored. Alternatively, on the terminal side, based on preset operation types, permission status, business stages, or data versions, some operations are locally approved, temporarily stored, or executed, generating corresponding offline operation records. Furthermore, a recovery synchronization mechanism can be set up on the server side to read offline operation records after the private network is restored, combining them with the server's current business status, data version, and business logs to generate synchronization or merging results, thereby updating the official business data.

[0004] However, in scenarios with high business continuity requirements, the above methods may still suffer from insufficient coordination between operational processing during network outages and post-network restoration control. Some solutions focus more on caching, replaying, or synchronizing offline operations, while failing to adequately express the correlation between operational admission criteria, execution boundaries, execution results formed during network outages, and post-recovery consolidation boundaries. This makes it difficult for the restoration results generated during the recovery phase to stably inherit the constraint information from the outage period. Furthermore, the lack of effective consistency verification between operational processing results during outages and post-recovery candidate restoration results can easily affect the reliability of business object state transitions, data writing, and version updates after recovery. Summary of the Invention

[0005] The purpose of this invention is to provide a service continuity management method and system for private network outage scenarios, in order to solve the problems mentioned in the background. Specifically, it addresses the problem that existing technologies lack sufficient constraint correlation between the service operation and processing results during private network outages and the service continuity control process after network recovery, resulting in a need to improve the consistency guarantee capability for recovery and continuity.

[0006] To achieve the above objectives, one objective of this invention is to provide a service continuity management method for private network disconnection scenarios, comprising the following steps: S1. Obtain the business continuity constraint fingerprint corresponding to the target business object; specifically including: Receive the object identifier of the target business object and write the object identifier into the runtime context; Read the business continuity constraint fingerprint from the business continuity constraint fingerprint storage area based on the object identifier; The business continuity constraint fingerprint includes the target business object identifier, business stage identifier, allowed disconnection operation type, operation parameter boundary, operation timing boundary, data version boundary, permission boundary, back-and-forth processing boundary, and verification identifier; Examine the existence status, field format, and binding relationships between fields in the business continuity constraint fingerprint; When the target business object identifier matches the object identifier, and all fields in the business continuity constraint fingerprint have been read, the business continuity constraint fingerprint is locked as the constraint baseline and written into the runtime context.

[0007] Step S1 obtains the business continuity constraint fingerprint corresponding to the target business object, and reads, checks and locks the target business object identifier, business stage identifier, allowed disconnection bearer operation type, operation parameter boundary, operation timing boundary, data version boundary, permission boundary, back-and-forth processing boundary and verification identifier. This enables subsequent disconnection bearer determination, disconnection bearer constraint generation, constraint space matching and connection control to be processed based on the same constraint benchmark, thereby helping to reduce the deviation between the business operation processing rules during the private network disconnection period and the business connection rules after the private network is restored.

[0008] S2. In response to the detection that the private network connection status corresponding to the target service object meets the disconnection condition, based on the service continuity constraint fingerprint, the original service operation objects generated during the private network disconnection period are subjected to disconnection bearer determination, and the original service operation objects that meet the disconnection bearer condition are converted into continuous operation units; specifically including: Collect the connection heartbeat status, business channel transmission and reception status, private network session status, and link authentication status corresponding to the target business object; When the connection heartbeat status, service channel transmit and receive status, private network session status and link authentication status are all written to the disconnection status, the service status of the target service object will be switched from the normal service status to the disconnection continuity management status. Under the continuity management state, the operation requests generated by the business terminal during the period of disconnection from the private network are encapsulated into the original business operation object; Based on business continuity constraint fingerprints, the disconnection bearing determination is performed on the operation object identifier, operation type, operation parameters, operation initiation time, operation initiating entity, data version before operation, and local operation sequence number of the original business operation object. When the original business operation object meets the disconnection bearer condition, a continuous operation unit is generated and written into the disconnection bearer queue. When the original business operation object does not meet the disconnection and load-bearing conditions, the original business operation object is marked as disconnection and load-bearing rejection.

[0009] Step S2 switches the target service object to the disconnection continuity management state when the connection heartbeat state, service channel transmission and reception state, private network session state, and link authentication state meet the disconnection conditions. Based on the service continuity constraint fingerprint, the operation object identifier, operation type, operation parameters, operation initiation time, operation initiating subject, data version before operation, and local operation sequence number of the original service operation object are used to determine the disconnection bearer. This allows operation requests generated during the private network disconnection period to be constrained and filtered before being converted into continuous operation units. This provides a structured object basis for incorporating the bearer processing results during the disconnection period into the recovery and reconnection process.

[0010] S3. Based on the business continuity constraint fingerprint, generate disconnection bearer constraints corresponding to the continuity operation unit. These disconnection bearer constraints define the execution boundaries of the continuity operation unit during the period of private network disconnection and the reconnection boundaries after the private network is restored. Specifically, they include: Read the continuity operation unit from the disconnected load queue and generate the disconnected load constraint identifier; Write the disconnection bearing constraint identifier and the continuous operation unit identifier into the same binding record; Execution boundaries are generated based on the operation parameter boundaries, operation timing boundaries, data version boundaries, and permission boundaries in the business continuity constraint fingerprint; The merge boundary is generated based on the merge processing boundary, data version boundary, operation timing boundary, and verification identifier in the business continuity constraint fingerprint; Execution admission checks are performed on continuous operation units based on execution boundaries, and a local execution result summary is generated when the execution admission check passes. Write the disconnection bearing constraint identifier, continuous operation unit identifier, execution boundary, merge boundary, and verification identifier into the disconnection bearing constraint.

[0011] Step S3 generates disconnection bearer constraints for continuous operation units based on service continuity constraint fingerprints, and writes the execution boundary and reconnection boundary into the disconnection bearer constraints simultaneously, so that the execution admission conditions of the continuous operation unit during the private network disconnection period correspond to the reconnection conditions after the private network is restored; at the same time, through the binding record between the disconnection bearer constraint identifier and the continuous operation unit identifier, the continuous operation unit formed during the disconnection period can carry the constraint basis that can be called later, thereby helping to enhance the constraint association between the disconnection bearer processing result and the service continuity control process.

[0012] S4. Based on the binding relationship between the continuity operation unit and the disconnection bearing constraint, generate a disconnection continuity bridge chain that records the disconnection bearing constraint; specifically including: Generate chained record nodes based on the bound records; The chained record node includes the chain head identifier, the previous node identifier, the current node identifier, the continuous operation unit identifier, the disconnection bearing constraint identifier, the target business object identifier, the local operation sequence number, the disconnection generation time, the execution status, the merge status, the local execution result summary, and the verification identifier; The node order of the chain record nodes is determined according to the local operation sequence number, and the chain record nodes are connected sequentially through the previous node identifier and the current node identifier to generate a broken continuity bridging chain. The execution status is updated based on the local execution status of the continuous operation unit and a local execution result summary is written. The merge status is kept as pending merge until the private network is restored.

[0013] Step S4 generates a disconnection continuity bridge chain based on the binding relationship between the continuity operation unit and the disconnection bearer constraint. The chain record node records the continuity operation unit identifier, disconnection bearer constraint identifier, local operation sequence number, execution status, merging status, local execution result summary, and verification identifier, so that the operation sequence, execution status, and constraint reference relationship formed during the private network disconnection can be preserved in a chain. This disconnection continuity bridge chain serves as a bridge object for invocation after the private network is restored, which helps to pass the processing results formed in the disconnection bearer stage to the subsequent connection consistency verification and service continuity control process.

[0014] S5. Based on the business continuity constraint fingerprint, perform constraint space matching on the candidate connection results generated for the target business object after the private network is restored to obtain the target candidate connection results; specifically including: When the connection heartbeat status, service channel transmit and receive status, private network session status and link authentication status are all restored to the connection status, the target service object is confirmed to enter the private network recovery status. Based on the continuity bridging chain, read the details of the continuity operation unit, the continuity bearing constraint reference relationship, the local operation sequence number, the local execution result summary, and the verification identifier; Read the current data version and business stage status of the target business object from the server, and generate candidate operation sequence, candidate data version, candidate business stage identifier, candidate merge status, and candidate verification identifier; Based on the business continuity constraint fingerprint, constraint space matching is performed on the candidate succession results; When the constraint space matching is successful, the candidate continuation result is determined as the target candidate continuation result; When the constraint space matching fails, the candidate continuation result is marked as a constraint space mismatch state.

[0015] Step S5 reads the details of continuity operation units, disconnection bearer constraint references, local operation sequence numbers, local execution result summaries, and verification identifiers in the disconnection continuity bridging chain under the private network recovery state. Based on the service continuity constraint fingerprint, it performs constraint space matching on the candidate connection results. This allows the candidate operation sequences, candidate data versions, candidate service stage identifiers, candidate merging statuses, and candidate verification identifiers generated after the private network recovery to be matched with a unified constraint benchmark. This helps to filter out candidate connection results that are not compatible with the constraint benchmark during the disconnection period, providing target candidate connection results for subsequent connection consistency verification.

[0016] S6. Based on the continuity bridging chain, perform continuity consistency verification on the target candidate connection results to obtain consistent connection results; specifically including: Based on the local operation sequence number of the chain record node, extract the continuous operation unit, disconnection bearing constraint, execution status, merging status, local execution result summary and verification identifier from the disconnection continuity bridging chain; Read the candidate operation sequence, candidate data version, candidate merge status, and candidate verification identifier from the target candidate continuation results; Perform sequential consistency checks on candidate operation sequences, version consistency checks on candidate data versions, state admission checks on candidate merge states, and identifier consistency checks on candidate verification identifiers. If all the above checks pass, a consistent continuation result is generated; if any check fails, a consistent continuation result is not generated, and the target candidate continuation result is marked as inconsistent.

[0017] Step S6 verifies the continuity of the target candidate connection results by using the disconnection continuity bridging chain. It performs sequential consistency verification, version consistency verification, status admission verification, and identifier consistency verification on the candidate operation sequence, candidate data version, candidate merging status, and candidate verification identifier. This allows the target candidate connection results to be compared with the continuity operation units, disconnection bearer constraints, execution status, merging status, local execution result summary, and verification identifier formed during the private network disconnection period. This helps improve the ability to identify the consistency of operation sequence, data version, merging status, and verification identifier during the connection recovery process.

[0018] S7. Based on the disconnection bearer constraints recorded in the disconnection continuity bridging chain, generate service continuity control results for the consistent continuity results, specifically including: Based on the consistency continuation results, read the continuous operation unit reference relationship and the disconnection bearing constraint reference relationship; Locate the corresponding chain record node along the discontinuity bridging chain and read the discontinuity bearing constraint recorded in the chain record node; Extract the merge boundary from the disconnection bearing constraint, and compare it with the continuation operation sequence, continuation data version, continuation merge status, merge status in the chain record node, and the reference relationship of the disconnection bearing constraint; When all the above comparisons pass, the connection permission flag will be set to allowed, and a service connection control result will be generated. If any comparison fails, the connection allow flag will be changed to connection prohibition, and a connection blocking record will be generated.

[0019] Based on the business continuity control results, continuity management is performed on the target business object; specifically including: Read the connection permission flag from the service connection control result; When the connection permission flag is set to allow connection, data writing, status update, and version update are performed on the formal business data area of ​​the target business object according to the connection operation sequence to form formal connection data and update the data version of the target business object. According to the chain record node update instruction, the merge status of the corresponding chain record node is updated from pending merge to merge in progress, and then updated to merged after the actual data writing is completed; According to the target business object status update instruction, the business status of the target business object is switched from disconnection continuity management status to normal business status. When the connection permission flag is changed to connection prohibition, the business status of the target business object is kept in the disconnection continuity management state, the merging status of the corresponding chain record node in the disconnection continuity bridging chain is kept in the pending merging state, and the connection blocking record is retained.

[0020] Step S7 locates the corresponding chain record node along the continuity bridging chain, reads the disconnection bearer constraints recorded in the chain record node, and compares the continuation operation sequence, continuation data version, continuation continuation status, continuation status in the chain record node, and reference relationship of the disconnection bearer constraints based on the merging boundary in the disconnection bearer constraints. This ensures that the generation of the service continuation control result is consistent with the disconnection bearer constraints bound during the private network disconnection period. When the continuation permission flag is set to allow continuation, data writing is performed on the formal business data area of ​​the target business object according to the continuation operation sequence. The system updates the status and version, and synchronously updates the merge status of the chain record nodes and the business status of the target business object. When the connection allow flag is changed to connection prohibition, the system maintains the business status of the target business object in the disconnection continuity management state, maintains the merge status of the corresponding chain record node in the pending merge state, and retains the connection blocking record. This helps to controllably implement the results of the connection consistency verification into the connection management of the target business object, and alleviates the problem of insufficient constraint correlation between the business operation bearing processing results during the private network disconnection period and the business connection control process after the private network is restored.

[0021] The second objective of this invention is to provide a service continuity management system for private network disconnection scenarios, including a constraint fingerprint acquisition module, a disconnection bearer determination module, a bearer constraint generation module, a bridging link generation module, a connection succession matching module, a connection consistency verification module, and a connection management execution module, wherein: The constraint fingerprint acquisition module obtains the business continuity constraint fingerprint corresponding to the target business object; The disconnection bearer determination module responds to the detection that the private network connection status corresponding to the target service object meets the disconnection condition. Based on the service continuity constraint fingerprint, it performs disconnection bearer determination on the original service operation objects generated during the private network disconnection period and converts the original service operation objects that meet the disconnection bearer condition into continuous operation units. The bearer constraint generation module generates disconnection bearer constraints corresponding to the continuity operation unit based on the business continuity constraint fingerprint. The disconnection bearer constraints are used to limit the execution boundary of the continuity operation unit during the period of disconnection in the private network and the reconnection boundary after the private network is restored. The bridging chain generation module generates a broken continuity bridging chain that records the broken continuity constraint based on the binding relationship between the continuity operation unit and the broken continuity bearing constraint. The connection result matching module, based on the business continuity constraint fingerprint, performs constraint space matching on the candidate connection results generated for the target business object after the private network is restored, and obtains the target candidate connection result. The continuity verification module performs continuity verification on the target candidate connection results based on the disconnection continuity bridging chain to obtain a consistent connection result. The continuity management execution module generates business continuity control results based on the disconnection bearer constraints recorded in the continuity bridging chain, and performs continuity management on the target business object according to the business continuity control results.

[0022] Compared with the prior art, the beneficial effects of the present invention are: 1. Based on further analysis and research of existing technical problems, this invention recognizes that business continuity management in the scenario of private network disconnection not only requires temporary storage or processing of the original business operation objects generated during the private network disconnection, but also requires that the processing results be continuously referenced and verified in the business continuity control process after the private network is restored. Otherwise, it is easy to have insufficient constraint association between the processing results of business operations during the private network disconnection and the business continuity control process after the private network is restored. To this end, this invention revolves around business continuity constraint fingerprints. First, based on the business continuity constraint fingerprints, the original business operation objects generated during the private network outage are judged for disconnection and bearer status. The original business operation objects that meet the disconnection and bearer status conditions are converted into continuous operation units. Furthermore, disconnection and bearer constraints are generated to limit the execution boundary of the continuous operation units during the private network outage and the merging boundary after the private network is restored. Then, based on the binding relationship between the continuous operation units and the disconnection and bearer constraints, a disconnection and continuity bridging chain recording the disconnection and bearer constraints is generated, so that the operation objects, constraint relationships, execution status and merging status formed in the disconnection and bearer stage form a bridging object for subsequent invocation. Subsequently, after the private network is restored, the candidate connection results are matched for constraint space based on the business continuity constraint fingerprints, and the target candidate connection results are verified for continuity consistency based on the disconnection and continuity bridging chain. Finally, the business connection control results are generated based on the disconnection and bearer constraints recorded in the disconnection and continuity bridging chain, and connection management is executed. Therefore, this invention forms a sequential dependency processing chain: the disconnection bearing processing of the original business operation object is driven by the business continuity constraint fingerprint; the processing results during the disconnection period are taken over by the disconnection bearing constraint and the disconnection continuity bridging chain; and the subsequent connection processing after the private network is restored is jointly constrained by the business continuity constraint fingerprint and the disconnection continuity bridging chain. This allows the execution boundary during the private network disconnection period and the consolidation boundary after the private network is restored to be associated, expressed, and continuously invoked in the same business continuity management process. This helps to improve the consistency assurance capability of restoration and connection and alleviates the problem of insufficient constraint association between the business operation bearing processing results during the private network disconnection period and the business connection control process after the private network is restored.

[0023] 2. This invention writes the disconnection bearer constraint identifier and the continuity operation unit identifier into the same binding record, generates chained record nodes based on the binding record, and determines the node order of the chained record nodes according to the local operation sequence number. The chained record nodes are then connected sequentially using the preceding node identifier and the current node identifier to generate a disconnection continuity bridging chain. This ensures that the continuity operation unit identifier, disconnection bearer constraint identifier, target business object identifier, local operation sequence number, execution status, merge status, local execution result summary, and verification identifier are recorded in the chained structure. Therefore, when performing continuity consistency verification and service continuity control after the private network is restored, the continuity operation unit, disconnection bearer constraint, execution status, merge status, local execution result summary, and verification identifier can be extracted along the disconnection continuity bridging chain. Based on this, candidate operation sequences, candidate data versions, candidate merge statuses, and candidate verification identifiers can be compared, further enhancing the traceability and verifiability of operation sequence, execution results, and constraint reference relationships during the private network disconnection period during the restoration phase. Attached Figure Description

[0024] Figure 1 This is a schematic diagram of the core process of the overall method steps of the present invention; Figure 2 This is a schematic diagram of the core process of step S1 of the present invention; Figure 3 This is a schematic diagram of the core process of step S2 of the present invention; Figure 4 This is a schematic diagram of the core process of step S3 of the present invention; Figure 5 This is a schematic diagram of the core process of step S4 of the present invention; Figure 6 This is a schematic diagram of the core process of step S5 of the present invention; Figure 7 This is a schematic diagram of the core process of step S6 of the present invention; Figure 8 This is a schematic diagram of the core process of step S7 of the present invention; Figure 9 This is a schematic diagram of the core process of the overall module of the present invention.

[0025] In the diagram: 100, Constraint Fingerprint Acquisition Module; 200, Disconnection Bearer Judgment Module; 300, Bearer Constraint Generation Module; 400, Bridging Chain Generation Module; 500, Connection Result Matching Module; 600, Connection Consistency Verification Module; 700, Connection Management Execution Module. Detailed Implementation

[0026] The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0027] Next, please refer to Figure 1 One objective of this embodiment is to provide a service continuity management method for a dedicated network (DMN) disconnection scenario. This method is used to disconnect service operations generated during the DMN disconnection period when the DMN connection corresponding to a target service object is lost, and to perform consistent continuation management on the operation results generated during the DMN disconnection period after the DMN is restored. This method uses a service continuity constraint fingerprint as a unified constraint basis and a disconnection continuity bridging chain as a bridging data object between the DMN disconnection phase and the DMN recovery phase, making disconnection bearer determination, disconnection bearer constraint generation, candidate continuation result screening, consistent continuation verification, and service continuation control form a sequentially dependent processing chain. This service continuity management method for a DMN disconnection scenario includes steps S1 to S7; wherein: Step S1 is used to obtain the service continuity constraint fingerprint corresponding to the target service object; Step S2 is used to generate a continuity operation unit based on the private network connection status and the service continuity constraint fingerprint; Step S3 is used to generate a disconnection bearer constraint based on the service continuity constraint fingerprint; Step S4 is used to generate a disconnection continuity bridging chain based on the binding relationship between the continuity operation unit and the disconnection bearer constraint; Step S5 is used to generate a target candidate connection result based on the service continuity constraint fingerprint; Step S6 is used to generate a consistent connection result based on the disconnection continuity bridging chain; Step S7 is used to determine the service connection control result and perform connection management based on the disconnection bearer constraint recorded in the disconnection continuity bridging chain.

[0028] Please see Figure 2 S1. Obtain the business continuity constraint fingerprint corresponding to the target business object, specifically including: Receive the object identifier of the target business object and write the object identifier into the runtime context of this business continuity management process; Access the business continuity constraint fingerprint storage area based on the object identifier in the runtime context, and read the business continuity constraint fingerprint that matches the object identifier; The business continuity constraint fingerprint includes the target business object identifier, business stage identifier, allowed disconnection operation type, operation parameter boundary, operation timing boundary, data version boundary, permission boundary, back-and-forth processing boundary, and verification identifier; The system includes the following components: Target Business Object Identifier (DDI) indicates the business object bound to the business continuity constraint fingerprint; Business Stage Identifier indicates the current business processing stage of the target business object; Allowed Disconnection Operation Type records the operation categories that can be converted to continuous operation units during a network outage; Operation Parameter Boundaries are stored in the form of field name, field type, allowed values, numerical range, and state transition relationship; Operation Timing Boundaries record the time window for allowed disconnection and the local operation sequence number rules for allowed execution; Data Version Boundaries record the allowed data version before the operation, the server-side data version accepted during merge, and the data version after the connection; Permission Boundaries record the identity, role scope, and permission level of the entity that can initiate business operations during a network outage; Merge Processing Boundaries record the state conditions, operation sequence conditions, and version acceptance conditions for allowing the execution of continuation processing after the network is restored; and Verification Identifiers are generated from the Target Business Object Identifier, Business Stage Identifier, Data Version Boundaries, Operation Timing Boundaries, and Merge Processing Boundaries using preset identifier generation rules. The verification identifier is used to confirm the consistency of the constraint source among continuous operation units, disconnection bearing constraints, disconnection continuity bridging chains, candidate connection results, and consistent connection results; Examine the existence status, field format, and binding relationships between fields in the business continuity constraint fingerprint; When the target business object identifier in the business continuity constraint fingerprint is consistent with the object identifier in the runtime context, and all fields in the business continuity constraint fingerprint have been read, the business continuity constraint fingerprint is locked as the constraint benchmark for this business continuity management process and written into the runtime context.

[0029] Step S1 completes the reading, verification, and locking of the business continuity constraint fingerprint, obtaining the constraint benchmark for this business continuity management process, and providing input for the disconnection bearer determination in step S2, the disconnection bearer constraint generation in step S3, and the constraint space matching in step S5.

[0030] The preset identifier generation rules in step S1 specifically include: The target business object identifier, business stage identifier, data version boundary, operation timing boundary, and back-merge processing boundary are read sequentially according to the preset field order. The existence status and format of each read field are confirmed. When both the existence status and format meet the requirements, the fields are combined in the same field order to generate constraint source data. A verification identifier is generated based on the constraint source data. When it is necessary to confirm the consistency of the constraint source for continuous operation units, disconnection bearing constraints, disconnection continuity bridging chains, candidate continuation results, or consistent continuation results, the recorded verification identifier is read and compared with the verification identifier in the business continuity constraint fingerprint. When the verification identifiers match, the constraint source is confirmed to be consistent; when the verification identifiers do not match, the constraint source is confirmed to be inconsistent.

[0031] Please see Figure 3 S2. Generate a continuity operation unit based on the private network connection status and service continuity constraint fingerprint, specifically including the disconnection status identification process, the original service operation object encapsulation process, the disconnection bearer determination process, and the continuity operation unit generation process.

[0032] The process of identifying disconnection status specifically includes: Continuously collect the private network connection status corresponding to the target business object. The private network connection status includes connection heartbeat status, business channel transmission and reception status, private network session status, and link authentication status. Among them, the connection heartbeat status is used to characterize the heartbeat detection result between the target service object and the private network; the service channel transmit and receive status is used to characterize the data transmit and receive result of the service channel corresponding to the target service object; the private network session status is used to characterize whether the private network session corresponding to the target service object is valid; and the link authentication status is used to characterize the authentication result of the private network link corresponding to the target service object. Confirm the connection heartbeat status, service channel transmission and reception status, private network session status, and link authentication status in the preset detection order. When the connection heartbeat status, service channel transmit and receive status, private network session status, and link authentication status are all written to the disconnected status, it is confirmed that the private network connection status corresponding to the target service object meets the disconnection condition, and the service status of the target service object is switched from normal service status to disconnection continuity management status.

[0033] The disconnection status identification process completes the collection of private network connection status and the judgment of disconnection conditions, and obtains the target business object whose business status is disconnection continuity management status, providing a trigger basis for the original business operation object encapsulation process.

[0034] The encapsulation process of the original business operation object specifically includes: When the business status of the target business object is in the disconnection continuity management state, receive the operation request generated by the business terminal during the period of disconnection on the private network; The operation request is encapsulated into a raw business operation object, which includes the operation object identifier, operation type, operation parameters, operation initiation time, operation initiating body, data version before operation, and local operation sequence number. Among them, the operation object identifier is used to indicate the business object corresponding to the operation request; the operation type is used to indicate the business operation category corresponding to the operation request; the operation parameters are used to record the business fields and values ​​carried in the operation request; the operation initiation time is used to record the time when the operation request was generated; the operation initiating subject is used to record the user, role or terminal identity that initiated the operation request; the data version before operation is used to record the data version corresponding to the target business object before the operation request was executed; and the local operation sequence number is used to record the local sorting position of the operation request during the period of private network disconnection. The local operation sequence number is used to determine the execution order and subsequent chain connection order during the private network disconnection period, and the operation initiation time is used to verify whether the operation request occurred within the time window that allows disconnection of the bearer.

[0035] The encapsulation process of the original business operation object completes the data objectification of the operation request, resulting in the original business operation object, which provides input for the disconnection bearer determination process.

[0036] The process for determining the disconnection of load capacity specifically includes: Based on the business continuity constraint fingerprint obtained in step S1, the original business operation object is subjected to disconnection bearing determination. Perform a consistency comparison between the operation object identifier and the target business object identifier; Match the operation type with the operation type that allows disconnection of the bearer; The operation parameters are read according to the field name, and field type validation, allowed value validation, numerical range validation, and state transition relationship validation are performed according to the boundaries of the operation parameters. Compare the operation initiation time with the time window in the operation timing boundary; Compare the local operation sequence number with the local operation sequence number rules in the operation timing boundary; Compare the data version before the operation with the allowed data versions before the operation that are referenced within the data version boundary; The entity initiating the operation is compared with the entity's identity, role scope, and permission level within the permission boundary. When all the above comparisons pass, the original business operation object will be marked as meeting the disconnection and bearer conditions. If any comparison fails, the original business operation object is marked as disconnected and rejected, and the original business operation object is prevented from entering the continuous operation unit generation process.

[0037] The disconnection and bearer determination process completes multi-field matching between the original business operation object and the business continuity constraint fingerprint, and obtains the original business operation object that meets the disconnection and bearer conditions and the original business operation object in the disconnection and bearer rejection state, providing admission results for the continuity operation unit generation process.

[0038] The process of generating continuous operation units specifically includes: For original service operation objects that meet the disconnection conditions, generate continuous operation unit identifiers; Retain the operation type, operation parameters, operation initiator, data version before operation, and local operation sequence number from the original business operation object; Write the target business object identifier, the disconnection generation time, and the verification identifier corresponding to the business continuity constraint fingerprint; Based on the continuous operation unit identifier, target business object identifier, operation type, operation parameters, operation initiator, data version before operation, local operation sequence number, disconnection generation time and verification identifier, a continuous operation unit is generated and written to the disconnection bearer queue.

[0039] The continuous operation unit generation process completes the conversion of the original business operation object into a continuous operation unit, resulting in a continuous operation unit with a continuous operation unit identifier, local operation sequence number, pre-operation data version, and verification identifier, providing input for the generation of disconnection bearing constraints in step S3.

[0040] The state transition relationship verification process in step S2 specifically includes: The system reads the state to be migrated corresponding to the original business operation object from the state field in the operation parameters, and reads the business stage identifier based on the current business processing stage of the target business object. The system compares the state to be migrated with the state migration relationship recorded in the operation parameter boundary. If the state to be migrated is within the allowed state migration range of the state migration relationship, and the business stage identifier is consistent with the business processing stage bound to the state migration relationship, the state migration relationship verification is confirmed to be successful. If the state to be migrated is not within the allowed state migration range of the state migration relationship, or the business stage identifier is inconsistent with the business processing stage bound to the state migration relationship, the state migration relationship verification is confirmed to be unsuccessful.

[0041] Please see Figure 4 S3. Generate disconnection constraints corresponding to the continuity operation unit based on the business continuity constraint fingerprint, specifically including: Based on the continuous operation unit generated in step S2, read the continuous operation unit from the disconnection bearer queue; Based on the business continuity constraint fingerprint obtained in step S1, a disconnection bearer constraint identifier is generated for the continuity operation unit, and the disconnection bearer constraint identifier and the continuity operation unit identifier are written into the same binding record. Execution boundaries are generated based on the operation parameter boundaries, operation timing boundaries, data version boundaries, and permission boundaries in the business continuity constraint fingerprint; The execution boundary record continuity operation unit can perform the operation types, operation parameters, initiating entity, local operation sequence number, and allowed reference to the previous data version during the private network disconnection period; Before executing continuous operation units locally, read the execution boundary and perform execution admission verification; When the admission verification passes, the continuous operation unit is executed in the local disconnected environment, and a local execution result summary is generated. The local execution result summary is used to record the execution results of the continuous operation unit in the local disconnection environment, and is written into the disconnection continuity bridge chain in step S4. When the admission verification fails, the continuous operation unit is marked as disconnected and cannot be executed, and the continuous operation unit is prevented from entering the local execution process. The merge boundary is generated based on the merge processing boundary, data version boundary, operation timing boundary, and verification identifier in the business continuity constraint fingerprint; The merge boundary record includes the allowed continuation status, allowed operation order, server-side data version when merge is allowed, data version after continuation, and verification identifier. Among them, the following are allowed: the continuation status can come from the status conditions in the merge processing boundary; the operation order can come from the operation order conditions in the merge processing boundary and the local operation sequence number rules in the operation timing boundary; the server-side data version accepted during merge and the data version after continuation can come from the data version boundary; the verification identifier is used to confirm that the merge boundary is consistent with the source of the business continuity constraint fingerprint. Write the disconnection bearing constraint identifier, continuous operation unit identifier, execution boundary, merge boundary, and verification identifier into the disconnection bearing constraint.

[0042] Step S3 completes the constraint derivation process between the continuity operation unit and the business continuity constraint fingerprint, and obtains the disconnection bearing constraint, local execution result summary, and disconnection non-executable status flag that are bound one-to-one with the continuity operation unit. This provides the binding relationship, execution status, and constraint boundary data for the generation of the disconnection continuity bridging chain in step S4.

[0043] The process of generating the execution boundary in step S3 specifically includes: Write the operation type that allows disconnection from the business continuity constraint fingerprint into the operation type in the execution boundary; write the field name, field type, allowed values, numerical range, and state transition relationship from the operation parameter boundary into the operation parameters in the execution boundary; write the subject identity, role scope, and permission level from the permission boundary into the initiating subject in the execution boundary; write the local operation sequence number rule from the operation sequence boundary into the local operation sequence number in the execution boundary; write the allowed referenced previous data version from the data version boundary into the allowed referenced previous data version in the execution boundary; thus forming the execution boundary corresponding to the continuous operation unit.

[0044] The process of forming the local execution result summary in step S3 specifically includes: Read the continuity operation unit identifier, disconnection bearer constraint identifier, operation type, operation parameters, data version before operation, local operation sequence number, and execution status; after completing the execution of the continuity operation unit in the local disconnection environment, record the local execution result corresponding to the continuity operation unit, the local status after execution, and the business fields and values ​​corresponding to the operation parameters; write the local execution result, the local status after execution, the business fields and values, the continuity operation unit identifier, the disconnection bearer constraint identifier, the local operation sequence number, and the verification identifier into the local execution result summary; the local execution result summary is used to confirm the execution result of the continuity operation unit in the local disconnection environment in the disconnection continuity bridge chain.

[0045] The process of generating the merge boundary in step S3 specifically includes: Write the state conditions in the merge processing boundary into the allowed continuation state in the merge boundary; write the operation sequence conditions in the merge processing boundary and the local operation sequence number rules in the operation timing boundary into the allowed operation sequence in the merge boundary; write the server-side data version allowed for merge in the data version boundary into the allowed server-side data version allowed for merge in the merge boundary; write the continuation data version in the data version boundary into the continuation data version in the merge boundary; write the verification identifier in the business continuity constraint fingerprint into the verification identifier in the merge boundary; thus forming the merge boundary corresponding to the disconnection bearing constraint.

[0046] Please see Figure 5 S4. Generate a disconnected continuity bridging chain based on the binding relationship between the continuity operation unit and the disconnection bearing constraint, specifically including: Based on the binding records obtained in step S3, generate a chain record node for each group of binding records; The chained record node includes the chain head identifier, the previous node identifier, the current node identifier, the continuous operation unit identifier, the disconnection bearing constraint identifier, the target business object identifier, the local operation sequence number, the disconnection generation time, the execution status, the merge status, the local execution result summary, and the verification identifier; Among them, the chain head identifier is used to indicate the starting node of the disconnected continuity bridging chain; the preceding node identifier is used to indicate the previous chain record node of the current node; the current node identifier is used to uniquely identify the current chain record node; the execution status is used to record the execution status of the continuous operation unit in the local disconnected environment; and the reconnection status is used to record the reconnection processing progress of the continuous operation unit after the private network is restored. For the first linked record node, write the chain head identifier into the current node identifier, and write the previous node identifier to a null value; For subsequent chain record nodes, the node order is determined according to the local operation sequence number, and the current node identifier of the previous chain record node is written into the previous node identifier of the next chain record node. Connect the chained record nodes sequentially to generate a broken continuity bridge chain; When the continuous operation unit completes local execution, it updates the execution status of the corresponding chain record node to "executed" and writes the local execution result summary formed in step S3. When a continuous operation unit has not completed its local execution, the execution status of the corresponding chain record node is kept as pending execution. Before the private network is restored, the merge status of the chain record nodes will be kept as pending merge.

[0047] Step S4 establishes a chain association between the continuity operation unit, disconnection bearing constraint, execution status, merging status, and verification identifier, resulting in a disconnection continuity bridging chain. This chain provides bridging data objects for the continuity operation unit detail reporting in step S5, the continuity consistency verification in step S6, and the determination of the service continuity control results in step S7.

[0048] Please see Figure 6 S5. Generate target candidate connection results based on business continuity constraint fingerprints, specifically including private network recovery identification process, candidate connection result generation process and constraint space matching process.

[0049] The private network recovery and identification process specifically includes: Collect the connection heartbeat status, business channel transmission and reception status, private network session status, and link authentication status corresponding to the target business object; When the connection heartbeat status, service channel transmit / receive status, private network session status, and link authentication status are all restored to the connection status, the target service object is confirmed to have entered the private network recovery status.

[0050] The private network recovery identification process completes the private network recovery status judgment, obtains the target business object in the private network recovery status, and provides the trigger basis for the candidate connection result generation process.

[0051] The process of generating candidate succession results specifically includes: Based on the disconnected continuity bridging chain generated in step S4, read the disconnected continuity bridging chain identifier, continuity operation unit details, disconnected bearing constraint reference relationship, local operation sequence number, local execution result summary and verification identifier. The continuity bridging chain identifier indicates the source of the bridging chain corresponding to the candidate connection result; the continuity operation unit details include operation type, operation parameters, local operation sequence number, data version before operation, operation initiating entity, and disconnection generation time; the disconnection bearer constraint reference relationship indicates the disconnection bearer constraint referenced by the candidate connection result; the local execution result summary confirms the execution result of the continuity operation unit in the local disconnection environment; and the verification identifier confirms that the candidate connection result is consistent with the source of the business continuity constraint fingerprint. Read the current data version and business stage status of the target business object from the server. Candidate operation sequences are generated based on the operation type, operation parameters, local operation sequence number, and pre-operation data version in the continuous operation unit details. Use the current data version on the server as a candidate data version to be accepted. Based on the candidate data version to be accepted and the data version before operation in the details of the continuous operation unit, generate the candidate data version after succession. Generate candidate data versions based on candidate data versions and candidate data versions following the succession; Among them, the candidate data version is used to record the data version of the continuous operation unit accepted by the server when the private network is restored, and the candidate data version after connection is used to record the data version after the candidate operation sequence is executed. Generate candidate business stage identifiers based on the business stage status; Write the candidate merge status as mergeable and write the verification flag as the candidate verification flag; Based on the candidate object identifier, candidate business stage identifier, candidate data version, candidate operation sequence, candidate merge status, and candidate verification identifier, candidate continuation results are generated.

[0052] The candidate continuation result generation process completes the continuation combination of the details of the continuous operation unit and the server data version in the disconnected continuity bridging chain to obtain candidate continuation results, providing objects to be screened for the constraint space matching process.

[0053] The constraint space matching process specifically includes: Based on the business continuity constraint fingerprint obtained in step S1, constraint space matching is performed on the candidate continuation results. Perform a consistency comparison between the candidate object identifier and the target business object identifier; Compare the candidate business stage identifier with the business stage identifier; Compare the candidate accepting data versions in the candidate data versions with the server accepting data versions that are allowed to merge at the data version boundary; Compare the candidate successor data versions in the candidate data versions with the successor data versions in the data version boundary; Compare the candidate operation sequence with the local operation sequence number rules in the operation timing boundary; Compare the candidate merge states with the state conditions in the merge processing boundary; Compare the candidate verification identifier with the verification identifier; When all the above comparisons pass, the candidate succession result is determined as the target candidate succession result and written into the target candidate succession result identifier; If any alignment fails, the candidate continuation result is marked as a constraint space mismatch.

[0054] The constraint space matching process completes the matching of objects, stages, versions, sequences, states, and identifiers between candidate succession results and business continuity constraint fingerprints, obtaining the target candidate succession results and constraint space mismatch states, providing input for succession consistency verification in step S6.

[0055] The process of generating the candidate operation sequence in step S5 specifically includes: The continuous operation unit details are sorted according to their local operation sequence numbers. The operation type, operation parameters, pre-operation data version, operation initiator, and disconnection generation time are read sequentially from the sorted continuous operation unit details. Each continuous operation unit detail is treated as a candidate operation item in the candidate operation sequence. When the local operation sequence numbers between candidate operation items satisfy the local operation sequence number rules in the operation timing boundary, and the pre-operation data version in the candidate operation item belongs to a pre-operation data version that is allowed to be referenced by the data version boundary, a candidate operation sequence is formed according to the sorting result. When any candidate operation item does not satisfy the local operation sequence number rules or does not satisfy the allowed pre-operation data version, the generation of the candidate operation sequence is stopped, and the corresponding candidate continuation result is marked as a constraint space mismatch state.

[0056] The process of generating candidate continuation data versions in step S5 specifically includes: Read the candidate data version, candidate operation sequence, pre-operation data version in the details of continuous operation units, and version acceptance conditions in the merge processing boundary; according to the order of the candidate operation sequence, use the candidate data version as the starting acceptance version for the continuation processing; compare the pre-operation data version in the candidate operation item with the allowed pre-operation data version in the data version boundary, and compare the acceptance relationship in the continuation processing with the version acceptance conditions; when all candidate operation items in the candidate operation sequence meet the version acceptance conditions, form the candidate continuation data version based on the data version after the execution of the candidate operation sequence; when any candidate operation item does not meet the version acceptance conditions, do not generate a candidate continuation data version, and mark the corresponding candidate continuation result as a constraint space mismatch state.

[0057] Please see Figure 7 S6. Generate consistent continuation results based on the disconnected continuity bridging chain, specifically including: Based on the disconnected continuity bridging chain generated in step S4, extract the continuity operation unit, disconnection bearing constraint, execution status, merging status, local execution result summary and verification identifier in sequence according to the local operation sequence number of the chain record node. Based on the target candidate continuation result obtained in step S5, read the candidate operation sequence, candidate data version, candidate merge status and candidate verification identifier; Perform sequential consistency checks between the candidate operation sequence and the continuous operation units recorded in the disconnected continuity bridging chain; Perform version consistency verification between the candidate acceptance data version in the candidate data version and the server acceptance data version allowed for re-merging in the re-merging boundary of the disconnection bearing constraint; Perform version consistency verification between the candidate continuation data version in the candidate data version and the continuation data version in the merge boundary of the disconnection bearing constraint. Perform state admission verification between the candidate merged states and the allowed continuation states in the merged boundary of the disconnected bearing constraint; Perform a consistency check between the execution status and the executed status in the chained record nodes; Perform consistency verification between the merge state and the state to be merged in the chained record nodes; Perform an identifier consistency check between the candidate check identifier and the check identifier in the disconnected continuity bridging chain. When all the above checks pass, a consistent continuation result is generated; Consistent connection results include the target business object identifier, connection operation sequence, connection data version, connection merge status, continuous operation unit reference relationship, and disconnection bearer constraint reference relationship; Among them, the continuation operation sequence comes from the candidate operation sequence; the continuation data version includes the continuation acceptance data version and the continuation data version, the continuation acceptance data version comes from the candidate acceptance data version, and the continuation data version comes from the candidate continuation data version; the continuation merge status comes from the candidate merge status; the continuous operation unit reference relationship comes from the continuous operation unit identifier; the disconnection bearing constraint reference relationship comes from the disconnection bearing constraint identifier. If any verification fails, no consistent continuation result is generated, and the target candidate continuation result is marked as inconsistent.

[0058] Step S6 completes the verification of the order, version, execution status, merging status and identifier between the target candidate connection result and the disconnection continuity bridging chain, and obtains a consistent connection result or a connection inconsistency status. This provides the connection operation sequence, connection data version, continuity operation unit reference relationship and disconnection bearer constraint reference relationship for determining the service connection control result in step S7.

[0059] Please see Figure 8 S7. Determine the service continuity control result and execute continuity management based on the disconnection bearing constraints recorded in the disconnection continuity bridging chain. Specifically, this includes the process of determining the service continuity control result and the process of executing continuity management.

[0060] The process for determining the results of business continuity control specifically includes: Based on the consistent connection result obtained in step S6, read the continuous operation unit reference relationship and the disconnection bearing constraint reference relationship; Based on the continuous operation unit reference relationship and the disconnection bearing constraint reference relationship, locate the corresponding chain record node along the disconnection continuity bridging chain generated in step S4; Read the disconnection bearing constraints recorded in the chain record nodes, and extract the back-merge boundary from the disconnection bearing constraints; Perform a consistency comparison between the sequence of subsequent operations and the allowed order of operations in the merge boundary; Perform a consistency comparison between the successor data version in the successor data version and the server-side successor data version allowed for merging in the merge boundary; Perform a consistency comparison between the continuation data version in the continuation data version and the continuation data version in the merge boundary; Compare the continuation merge state with the allowed continuation states in the merge boundary for admission; Perform a consistency comparison between the merge state in the chained record node and the state to be merged; Compare the consistency between the disconnection load constraint reference relationship and the disconnection load constraint identifier in the disconnection continuity bridging chain; When all the above comparisons pass, the connection permission flag will be set to allowed, and a service connection control result will be generated. The results of business continuity control include continuity permission flag, continuity operation sequence, continuity data version, concurrency execution status, chain record node update instructions, and target business object status update instructions; Among them, the continuity permission flag is used to indicate whether it is allowed to write the consistent continuity result to the formal business data area; the merge execution status is used to record the execution result of the continuity operation sequence; the chain record node update instruction is used to update the merge status in the chain record node; and the target business object status update instruction is used to update the business status of the target business object. When any comparison fails, the connection allow flag is changed to connection prohibited, and a connection blocking record is generated. The connection blocking record includes the target business object identifier, the disconnection continuity bridging chain identifier, the failed comparison item, and the blocking time.

[0061] The process of determining the service continuity control result completes the control verification between the consistent continuity result and the back-to-boundary boundary in the disconnection bearing constraint, and obtains the service continuity control result or continuity blocking record, providing continuity permission identifier, continuity operation sequence, continuity data version and chain record node update instructions for the continuity management execution process.

[0062] The follow-up management execution process specifically includes: Read the connection permission flag from the service connection control result; When the connection permission flag is set to allow connection, data writing, status update and version update are performed on the formal business data area of ​​the target business object in accordance with the connection operation sequence; After execution, formal continuation data is generated, and the data version of the target business object is updated according to the continuation data version. According to the chain record node update instruction, locate the corresponding chain record node along the disconnected continuity bridging chain, and update the merge status of the corresponding chain record node from pending merge to merge in progress. After the formal continuation of data writing is completed, the merge status of the corresponding chain record node is updated from merged to merged, and the merge execution status is written. According to the target business object status update instruction, the business status of the target business object is switched from disconnection continuity management status to normal business status. When the connection permission flag is changed to connection prohibition, the business status of the target business object is kept in the disconnection continuity management state, the merging status of the corresponding chain record node in the disconnection continuity bridging chain is kept in the pending merging state, and the connection blocking record is retained.

[0063] The continuation management execution process completes the writing of formal business data area, the data version update of target business object, the update of the merge status of chain record nodes, and the switching of business status of target business object, to obtain formal continuation data, the disconnected continuity bridging chain node in the merged state, and the target business object in the normal business state; under the continuation prohibited branch, the continuation blocking record is obtained and kept in the waiting merge state, providing reserved data for subsequent reconnection processing.

[0064] The writing process of the formal business data area in step S7 specifically includes: Following the order of each successive operation item in the successive operation sequence, the operation type, operation parameters, operation initiating entity, and pre-operation data version in each successive operation item are read sequentially. The successive data version in the successive data version is used as the basis for the succession of the formal business data area. The business fields and values ​​corresponding to the target business object in the formal business data area are written according to the operation type and operation parameters. The status is updated according to the business processing result corresponding to the successive operation item. After all successive operation sequences are written, the version is updated according to the successive data version in the successive data version, and the formal successive data is formed.

[0065] In this embodiment, the consistency verification process is described in detail as follows: After locking the business continuity constraint fingerprint as the constraint benchmark for this business continuity management process in step S1, subsequent steps will use the target business object identifier, business stage identifier, operation parameter boundary, operation timing boundary, data version boundary, permission boundary, merge processing boundary and verification identifier in the business continuity constraint fingerprint as the basis for consistency verification. In step S2, when determining the disconnection of the original business operation object, the consistency of the operation object identifier and the target business object identifier is compared, the operation type is matched with the operation type that is allowed to be disconnected, the operation parameters are compared with the operation parameter boundaries, the operation initiation time and the local operation sequence number are compared with the operation time sequence boundary, the data version before the operation is compared with the data version boundary, and the operation initiating subject is compared with the permission boundary to confirm whether the original business operation object meets the disconnection conditions. In steps S3 and S4, the verification identifier in the business continuity constraint fingerprint is written into the continuity operation unit, the disconnection bearer constraint, and the disconnection continuity bridging chain. The reference relationship between the continuity operation unit, the disconnection bearer constraint, and the disconnection continuity bridging chain is confirmed to be consistent through the binding relationship between the disconnection bearer constraint identifier and the continuity operation unit identifier, and the chain connection relationship between the previous node identifier and the current node identifier in the chain record node. In step S5, after generating candidate succession results, the candidate object identifier is compared with the target business object identifier for consistency, the candidate business stage identifier is compared with the business stage identifier, the candidate data version is compared with the data version boundary, the candidate operation sequence is compared with the local operation sequence number rule in the operation time sequence boundary, the candidate merge status is compared with the status condition in the merge processing boundary, and the candidate verification identifier is compared with the verification identifier to filter and obtain the target candidate succession results; In step S6, the continuous operation unit, disconnection bearing constraint, execution state, merge state, local execution result summary, and verification identifier are extracted sequentially according to the local operation sequence number of the chain record node. The candidate operation sequence is checked for sequential consistency with the continuous operation unit recorded in the disconnection continuity bridging chain. The candidate data version is checked for version consistency with the merge boundary of the disconnection bearing constraint. The candidate merge state is checked for state admission with the allowed continuation state. The execution state is checked for consistency with the executed state. The merge state is checked for consistency with the state to be merged. The candidate verification identifier is checked for identifier consistency with the verification identifier in the disconnection continuity bridging chain. When all the above checks pass, a consistent continuation result is generated. When any check fails, a consistent continuation result is not generated, and the target candidate continuation result is marked as a continuation inconsistency state. In step S7, the continuation operation sequence, continuation data version, continuation merge status, continuity operation unit reference relationship, and disconnection bearer constraint reference relationship in the consistency continuation result are read. The corresponding chain record node is located along the disconnection continuity bridging chain. The continuation operation sequence is compared with the allowed operation sequence in the merge boundary for consistency. The continuation data version is compared with the server-side data version and the data version after continuation in the allowed merge boundary for consistency. The continuation merge status is compared with the allowed continuation status for admission. The merge status in the chain record node is compared with the pending merge status for consistency. The disconnection bearer constraint reference relationship is compared with the disconnection bearer constraint identifier in the disconnection continuity bridging chain for consistency. When all the above comparisons pass, the continuation allow identifier is written as allowed continuation, and data writing, status update, and version update are performed on the formal business data area of ​​the target business object according to the continuation operation sequence. When any comparison fails, the continuation allow identifier is written as prohibited continuation, and a continuation blocking record is generated.

[0066] In this embodiment, the thresholds involved include the time window for allowing disconnection and the local operation sequence number rules allowed to be executed in the operation timing boundary, the allowed values ​​and numerical ranges in the operation parameter boundary, the allowed data version before the operation in the data version boundary, the server-side data version accepted during the merge and the data version after the connection are allowed, the permission level in the permission boundary, and the status conditions, operation order conditions and version acceptance conditions in the merge processing boundary. The range of the above threshold values ​​is limited to the range within which disconnection and reconnection processing are allowed in the current business processing stage of the target business object. That is, it shall not exceed the constraint space jointly defined by the business stage identifier, the type of operation that allows disconnection, the operation parameter boundary, the operation timing boundary, the data version boundary, the permission boundary, and the back-and-forth processing boundary. The determination is based on the business processing stage of the target business object, the types of business operations allowed to be executed during the period of private network disconnection, the data version inheritance relationship of the target business object, the identity, role scope and permission level of the entity initiating the business operation, and the status conditions, operation sequence conditions and version inheritance conditions that allow the execution of continuation processing after the private network is restored. In step S1, it is read, verified and locked as a business continuity constraint fingerprint. Subsequent steps S2 to S7 all use the threshold-type constraints in the business continuity constraint fingerprint as the basis for disconnection bearer determination, disconnection bearer constraint generation, candidate continuation result screening, consistency continuation verification and business continuation control.

[0067] To further illustrate the working process of this embodiment, a specific operation process is given below: First, the object identifier of the target business object is received through step S1, and the business continuity constraint fingerprint corresponding to the target business object is read according to the object identifier. The business continuity constraint fingerprint is then locked as the constraint benchmark for this business continuity management process. When the private network connection status corresponding to the target business object meets the disconnection condition, the business status of the target business object is switched from normal business status to disconnection continuity management status through step S2. The operation request generated by the business terminal during the private network disconnection period is received, the operation request is encapsulated into the original business operation object, and the disconnection bearing is determined for the original business operation object according to the business continuity constraint fingerprint. A continuous operation unit is generated for the original business operation object that meets the disconnection bearing condition. Then, in step S3, disconnection bearing constraints corresponding to the continuity operation unit are generated based on the business continuity constraint fingerprint. After the admission verification is passed, the continuity operation unit is executed in the local disconnection environment to form a local execution result summary. Then, in step S4, a disconnected continuity bridge chain is generated based on the binding relationship between the continuity operation unit and the disconnection bearing constraint, and the chain record nodes are connected according to the local operation sequence number to record the execution status, merging status, local execution result summary and verification identifier. When the target business object enters the private network recovery state, the continuity operation unit details, disconnection bearer constraint reference relationship, local execution result summary and verification identifier in the disconnection continuity bridging chain are read through step S5. Candidate connection results are generated by combining the current data version of the server, and the target candidate connection result is determined by constraint space matching. Then, step S6 performs sequential consistency verification, version consistency verification, state admission verification, and identifier consistency verification based on the disconnection continuity bridging chain and the target candidate connection result. After the verification is passed, a consistent connection result is generated. Finally, in step S7, the service continuity control result is determined based on the disconnection bearer constraints recorded in the disconnection continuity bridging chain. When the continuity allow flag is set to allow continuity, data writing, status update, and version update are performed on the formal business data area of ​​the target business object according to the continuity operation sequence. The merge status of the chain record node is updated from pending merge to merge in progress, and then from merge in progress to merged. At the same time, the business status of the target business object is switched from the disconnection continuity management status to the normal business status.

[0068] As can be seen from the above description, the service continuity management method for a private network disconnection scenario provided in this embodiment has the following technical effects: Using business continuity constraint fingerprints as a unified constraint basis, when the private network connection status corresponding to the target business object meets the disconnection condition, the original business operation objects generated during the private network disconnection period are judged for disconnection bearing based on the business continuity constraint fingerprint. The original business operation objects that meet the disconnection bearing condition are converted into continuous operation units, and disconnection bearing constraints corresponding to the continuous operation units are generated according to the business continuity constraint fingerprint, so that the execution boundary of the continuous operation unit during the private network disconnection period and the return boundary after the private network is restored can be clearly defined. Furthermore, a disconnection continuity bridging chain is generated by binding the continuity operation unit with the disconnection bearing constraint. The continuity operation unit, disconnection bearing constraint, execution status, merging status, local execution result summary and verification identifier are linked in a chain, so that the operation objects, constraint relationships and local execution results formed during the disconnection of the private network can be continuously referenced as bridging data objects after the private network is restored. After the private network is restored, target candidate connection results are generated based on the business continuity constraint fingerprint. The order, version, execution status, merging status and identifier of the target candidate connection results are verified according to the disconnection continuity bridging chain to generate consistent connection results. Then, the business connection control results are determined according to the disconnection bearer constraints recorded in the disconnection continuity bridging chain and connection management is executed. Therefore, this embodiment forms a sequential processing chain whereby the business continuity constraint fingerprint drives the determination of disconnected bearer and the generation of disconnected bearer constraints; the disconnected continuity bridging chain takes over the processing results during the private network disconnection period; and the business continuity constraint fingerprint and the disconnected continuity bridging chain jointly constrain the subsequent processing after the private network is restored. This allows the execution boundary during the private network disconnection period and the consolidation boundary after the private network is restored to be associated, continuously invoked, and consistently verified within the same business continuity management process. This helps to improve the continuity consistency guarantee capability after the private network is restored, enhances the traceability and verifiability of the operation sequence, execution results, and constraint reference relationships during the private network disconnection period in the restoration and continuation phase, and alleviates the problem of insufficient constraint association between the business operation bearer processing results during the private network disconnection period and the business continuation control process after the private network is restored.

[0069] Please see Figure 9 The second objective of this embodiment is to provide a service continuity management system for private network disconnection scenarios, including a constraint fingerprint acquisition module 100, a disconnection bearer determination module 200, a bearer constraint generation module 300, a bridging link generation module 400, a connection result matching module 500, a connection consistency verification module 600, and a connection management execution module 700, wherein: The constraint fingerprint acquisition module 100 acquires the business continuity constraint fingerprint corresponding to the target business object; In response to detecting that the private network connection status corresponding to the target service object meets the disconnection condition, the disconnection bearer determination module 200 performs disconnection bearer determination on the original service operation object generated during the private network disconnection period based on the service continuity constraint fingerprint, and converts the original service operation object that meets the disconnection bearer condition into a continuous operation unit. The bearer constraint generation module 300 generates disconnection bearer constraints corresponding to the continuous operation unit based on the business continuity constraint fingerprint. The disconnection bearer constraints are used to limit the execution boundary of the continuous operation unit during the period of disconnection in the private network and the reconnection boundary after the private network is restored. The bridging chain generation module 400 generates a disconnected continuity bridging chain that records the disconnected load constraints based on the binding relationship between the continuity operation unit and the disconnection load constraints. The connection result matching module 500, based on the business continuity constraint fingerprint, performs constraint space matching on the candidate connection results generated for the target business object after the private network is restored, and obtains the target candidate connection result. The continuity verification module 600 performs continuity verification on the target candidate connection results based on the disconnection continuity bridging chain to obtain a consistent connection result. The continuity management execution module 700 generates service continuity control results based on the disconnection bearer constraints recorded in the disconnection continuity bridging chain, and performs continuity management on the target service object according to the service continuity control results.

[0070] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely preferred examples and are not intended to limit the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of the present invention is defined by the appended claims and their equivalents.

Claims

1. A service continuity management method for a private network disconnection scenario, characterized in that, The methods and steps include the following: S1. Obtain the business continuity constraint fingerprint corresponding to the target business object; specifically including: Receive the object identifier of the target business object and write the object identifier into the runtime context; Read the business continuity constraint fingerprint from the business continuity constraint fingerprint storage area based on the object identifier in the runtime context; The business continuity constraint fingerprint includes the target business object identifier, business stage identifier, allowed disconnection operation type, operation parameter boundary, operation timing boundary, data version boundary, permission boundary, back-and-forth processing boundary, and verification identifier. When the target business object identifier in the business continuity constraint fingerprint is consistent with the object identifier in the runtime context, and all fields in the business continuity constraint fingerprint have been read, the business continuity constraint fingerprint is locked as the constraint baseline and written into the runtime context. S2. In response to detecting that the private network connection status corresponding to the target service object meets the disconnection condition, based on the service continuity constraint fingerprint, the original service operation object generated during the private network disconnection period is subjected to disconnection bearing determination, and the original service operation object that meets the disconnection bearing condition is converted into a continuous operation unit and written into the disconnection bearing queue. S3. Based on the service continuity constraint fingerprint, generate a disconnection bearer constraint corresponding to the continuity operation unit. The disconnection bearer constraint is used to limit the execution boundary of the continuity operation unit during the period of private network disconnection and the reconnection boundary after the private network is restored. The generation process of the disconnection bearer constraint specifically includes: Read the continuity operation unit from the disconnected bearer queue and generate a disconnected bearer constraint identifier; Write the disconnection bearing constraint identifier and the continuous operation unit identifier into the same binding record; Execution boundaries are generated based on the operation parameter boundaries, operation timing boundaries, data version boundaries, and permission boundaries in the business continuity constraint fingerprint. The merge boundary is generated based on the merge processing boundary, data version boundary, operation timing boundary, and verification identifier in the business continuity constraint fingerprint. The continuous operation unit is subjected to execution admission verification based on the execution boundary, and a local execution result summary is formed when the execution admission verification passes. Write the disconnection bearing constraint identifier, continuous operation unit identifier, execution boundary, merge boundary, and verification identifier into the disconnection bearing constraint; S4. Based on the binding relationship between the continuity operation unit and the disconnection bearing constraint, generate a disconnection continuity bridge chain that records the disconnection bearing constraint; specifically including: Generate a chain of record nodes based on the bound records; The chained record node includes a chain head identifier, a previous node identifier, a current node identifier, a continuous operation unit identifier, a disconnection bearing constraint identifier, a target business object identifier, a local operation sequence number, a disconnection generation time, an execution status, a merge status, a local execution result summary, and a verification identifier. The node order of the chain record nodes is determined according to the local operation sequence number, and the chain record nodes are connected sequentially through the previous node identifier and the current node identifier to generate a broken continuity bridging chain. The execution status is updated according to the local execution status of the continuous operation unit and a local execution result summary is written. The merge status is kept as pending merge until the private network is restored. S5. Based on the service continuity constraint fingerprint, perform constraint space matching on the candidate connection results generated for the target service object after the private network is restored to obtain the target candidate connection results; wherein: Based on the disconnected continuity bridging chain, read the details of the continuous operation unit, the disconnected bearing constraint reference relationship, the local operation sequence number, the local execution result summary, and the verification identifier. Read the current data version and business stage status of the target business object on the server side, and generate candidate operation sequence, candidate data version, candidate business stage identifier, candidate merge status and candidate verification identifier; S6. Based on the disconnected continuity bridging chain, perform a continuity consistency check on the target candidate connection results to obtain a consistent connection result; specifically including: According to the local operation sequence number of the chain record node, extract the continuous operation unit, disconnection bearing constraint, execution status, merging status, local execution result summary and verification identifier from the disconnection continuity bridging chain; Read the candidate operation sequence, candidate data version, candidate merge status, and candidate verification identifier from the target candidate continuation result; Perform sequential consistency verification on the candidate operation sequence, version consistency verification on the candidate data version, state admission verification on the candidate merge state, and identifier consistency verification on the candidate verification identifier. When all the above checks pass, a consistent continuation result is generated; Consistent connection results include the target business object identifier, connection operation sequence, connection data version, connection merge status, continuous operation unit reference relationship, and disconnection bearer constraint reference relationship; Among them, the continuation operation sequence comes from the candidate operation sequence; the continuation data version includes the continuation acceptance data version and the continuation data version, the continuation acceptance data version comes from the candidate acceptance data version, and the continuation data version comes from the candidate continuation data version; the continuation merge status comes from the candidate merge status; the continuous operation unit reference relationship comes from the continuous operation unit identifier; the disconnection bearing constraint reference relationship comes from the disconnection bearing constraint identifier. If any verification fails, no consistent continuation result is generated, and the target candidate continuation result is marked as inconsistent. S7. Based on the disconnection bearer constraints recorded in the disconnection continuity bridging chain, generate a service continuity control result for the consistent continuity result, and perform continuity management on the target service object according to the service continuity control result; the process of determining the service continuity control result specifically includes: Based on the consistency continuation results, read the continuous operation unit reference relationship and the disconnection bearing constraint reference relationship; Locate the corresponding chain record node along the discontinuity bridging chain and read the discontinuity bearing constraint recorded in the chain record node; Extract the back-merge boundary from the disconnection bearing constraint, and compare it with the continuation operation sequence, continuation data version, continuation back-merge status, back-merge status in the chain record node, and the reference relationship of the disconnection bearing constraint; When all the above comparisons pass, the connection permission flag will be set to allowed, and a service connection control result will be generated. If any comparison fails, the connection allow flag will be changed to connection prohibition, and a connection blocking record will be generated.

2. The service continuity management method for private network disconnection scenarios according to claim 1, characterized in that, The generation process of the continuous operation unit specifically includes: Collect the connection heartbeat status, service channel transmission and reception status, private network session status, and link authentication status corresponding to the target service object; When the connection heartbeat status, service channel transmit and receive status, private network session status and link authentication status are all written to the disconnection status, the service status of the target service object will be switched from the normal service status to the disconnection continuity management status. Under the disconnection continuity management state, the operation requests generated by the service terminal during the period of disconnection from the private network are encapsulated into the original service operation object; Based on the business continuity constraint fingerprint, the disconnection bearing determination is performed on the operation object identifier, operation type, operation parameters, operation initiation time, operation initiating subject, data version before operation, and local operation sequence number of the original business operation object. When the original business operation object meets the disconnection bearer condition, a continuous operation unit is generated; When the original service operation object does not meet the disconnection and load-bearing conditions, the original service operation object is marked as disconnection and load rejection state.

3. The service continuity management method for private network disconnection scenarios according to claim 2, characterized in that, The process of generating the target candidate continuation result specifically includes: When the connection heartbeat status, service channel transmit / receive status, private network session status, and link authentication status are all restored to the connection status, the target service object is confirmed to have entered the private network recovery status. Based on the aforementioned business continuity constraint fingerprint, constraint space matching is performed on the candidate connection results; When the constraint space matching is successful, the candidate continuation result is determined as the target candidate continuation result. When the constraint space matching fails, the candidate continuation result is marked as a constraint space mismatch state.

4. The service continuity management method for private network disconnection scenarios according to claim 1, characterized in that, The execution process of the continuity management specifically includes: Read the connection permission identifier from the service connection control result; When the connection permission flag is set to allow connection, data writing, status update, and version update are performed on the formal business data area of ​​the target business object according to the connection operation sequence to form formal connection data, and the data version of the target business object is updated. According to the chain record node update instruction, the merge status of the corresponding chain record node is updated from pending merge to merge in progress, and then updated to merged after the formal continuation data is written. According to the target business object status update instruction, the business status of the target business object is switched from disconnection continuity management status to normal business status. When the connection permission flag is set to connection prohibition, the business status of the target service object is kept in the disconnection continuity management state, the merging status of the corresponding chain record node in the disconnection continuity bridging chain is kept in the pending merging state, and the connection blocking record is retained.

5. A service continuity management system for a private network disconnection scenario, used to implement the service continuity management method for a private network disconnection scenario as described in any one of claims 1-4, characterized in that, It includes a constraint fingerprint acquisition module, a disconnection bearer determination module, a bearer constraint generation module, a bridging chain generation module, a connection result matching module, a connection consistency verification module, and a connection management execution module, wherein: The constraint fingerprint acquisition module acquires the business continuity constraint fingerprint corresponding to the target business object; The disconnection bearer determination module responds to the detection that the private network connection status corresponding to the target service object meets the disconnection condition, and performs disconnection bearer determination on the original service operation object generated during the private network disconnection based on the service continuity constraint fingerprint, and converts the original service operation object that meets the disconnection bearer condition into a continuous operation unit. The bearer constraint generation module generates disconnection bearer constraints corresponding to the continuity operation unit based on the service continuity constraint fingerprint. The disconnection bearer constraints are used to limit the execution boundary of the continuity operation unit during the period of disconnection in the private network and the reconnection boundary after the private network is restored. The bridging chain generation module generates a disconnected continuity bridging chain that records the disconnected bearing constraint based on the binding relationship between the continuity operation unit and the disconnection bearing constraint. The connection result matching module performs constraint space matching on the candidate connection results generated for the target service object after the private network is restored, based on the service continuity constraint fingerprint, to obtain the target candidate connection result. The continuity verification module performs continuity verification on the target candidate connection result based on the disconnection continuity bridging chain to obtain a consistent connection result. The continuity management execution module generates a service continuity control result based on the disconnection bearer constraints recorded in the disconnection continuity bridging chain, and performs continuity management on the target service object according to the service continuity control result.

Images