A method and system for synchronizing the status of a flow based on a cryptographic marking

Abstract

This invention is a divisional application of application number 202511705112.1. It discloses a method and system for synchronizing and integrating the flow state based on cryptographic tags, deployed within a controlled internal system. The method includes: receiving business requests from relevant business systems and obtaining corresponding original identification information; generating a cryptographic tag uniquely bound to the original identification information based on a pre-set cryptographic security key; receiving verification requests initiated on the cryptographic tag and performing validity verification during the flow of the controlled information carrier; capturing the verification action as a flow business event upon successful verification; determining the current flow state information based on the flow business event and the request source identifier; and synchronizing the flow state information to relevant business systems through a state synchronization function to trigger closed-loop business operations. This invention achieves logical decoupling through an asynchronous mechanism, combining message persistence and failure retry processes to ensure business continuity and eventual data consistency without relying on real-time responses.

Description

[0001] This invention is a divisional application of application number 202511705112.1, filed on November 20, 2025, entitled "An autonomous closed-loop method, system, medium and hardware for receiving information based on cryptographic tags". Technical Field

[0002] This invention belongs to the field of information security and data processing technology, specifically relating to a method and system for synchronizing and integrating the flow state based on cryptographic tags. Background Technology

[0003] With the deepening of information technology construction in modern institutions, when controlled information carriers in the real environment circulate within a group, they need to interact with relevant business systems to manage the circulation status.

[0004] In existing workflow management solutions, conventional static barcodes or QR codes are typically used as identifiers, which are scanned by operators using handheld terminals to directly initiate status update requests to the backend business system. However, this conventional system architecture and workflow mechanism has the following shortcomings in practical applications: The verification process is highly coupled with business logic, posing security risks and limiting scalability. In existing technologies, scanning terminals often need to directly connect to relevant backend business systems (such as directly calling the interfaces of inventory management systems or OA systems) to complete data interaction. This architecture forces business systems to expose interfaces to a large number of transfer terminals, increasing underlying system security risks. Furthermore, replacing related business systems or upgrading terminals often requires complex adjustments to the entire interaction chain, lacking an independent logical decoupling mechanism.

[0005] Conventional identifiers lack cryptographic verification and lifecycle management, making business status susceptible to interference. Most existing identifiers are generated in plaintext, making them easily copied or replayed. Due to the lack of dynamic constraints and lifecycle strategies based on cryptographic keys, the system struggles to objectively determine the validity of flow verification actions. This leads to the system easily receiving invalid flow status information, triggering erroneous business closed-loop operations (such as incorrect inventory quantity deductions or document archiving), and affecting data consistency between systems.

[0006] It is highly dependent on the network environment and struggles to adapt to continuous business processes in complex environments. In real-world workflow scenarios, verification nodes may be located in areas with weak network signals. Existing workflow systems typically cannot complete validity verification when the network is interrupted; and after the network is restored, it is difficult to guarantee the sequential synchronization of state events, resulting in gaps in state records within the business system and failing to guarantee the eventual consistency of the workflow state.

[0007] Cross-system interactions lack tamper-proof underlying evidence storage, making audit trails difficult. When the workflow status triggers related business systems to execute closed-loop operations, existing solutions mostly rely on the routine log records of each business system. This decentralized recording method makes it difficult to provide objective and tamper-proof underlying audit trail evidence when facing cross-departmental workflow reviews or compliance audits.

[0008] In summary, existing workflow integration technologies have shortcomings in terms of security, decoupling, and availability. There is an urgent need for a method and system that can securely and objectively capture verification actions and reliably drive related business systems to complete business closed-loop operations while achieving system logic decoupling. Summary of the Invention

[0009] To address the problems existing in the prior art, such as high coupling between verification actions and business logic, lack of cryptographic verification and lifecycle management, high dependence on network environment, and lack of tamper-proof underlying audit and evidence storage, this invention aims to provide a method and system for synchronous integration of flow status based on cryptographic tags. This method and system can securely and objectively capture flow verification actions and drive relevant business systems to complete closed-loop operations while achieving decoupling of system logic.

[0010] A first aspect of the present invention provides a method for synchronizing and integrating transition states based on cryptographic tokens, the method being deployed in a controlled internal system of a specific group, comprising the following steps: Information collection and tag generation steps: Receive business requests from relevant business systems, obtain the original identification information corresponding to the business requests; based on preset cryptographic security keys and preset interception strategies, generate a cryptographic tag uniquely bound to the original identification information, and output the cryptographic tag and carry it on a controlled information carrier; Flow verification and event capture steps: During the flow of the controlled information carrier carrying the cryptographic token, the receiving terminal initiates a verification request for the cryptographic token and performs validity verification; when the validity verification is successful, the verification action is captured as a flow business event; State deduction steps: Based on the flow business event and the request source identifier obtained by parsing the verification request, determine the current flow status information of the controlled information carrier; State synchronization and closed-loop triggering steps: Through the state synchronization function deployed in the controlled internal system, the flow state information is synchronized to the relevant business systems deployed within the specific group, so as to trigger the relevant business systems to execute the corresponding business closed-loop operation, thereby realizing the logical decoupling of cryptographic verification actions and relevant business systems.

[0011] Furthermore, in the state deduction step, determining the current flow state information of the controlled information carrier specifically includes: Obtain the identity of the source terminal represented by the request source identifier, and determine the corresponding permission policy; By combining the preset correspondence, the source terminal identity, the permission policy and the circulation business event are associated and matched to determine the corresponding circulation status information of being prepared, being delivered, being delivered or being received.

[0012] Furthermore, in the state synchronization and closed-loop triggering steps, the state synchronization function, as an independent data bus service, performs the following operations: The flow status information is synchronized to the relevant business systems via a message queue; When a timeout or failure to write back the status is detected in the relevant business system, a message persistence and retry mechanism is triggered to ensure eventual data consistency between the controlled internal system and the relevant business system.

[0013] Furthermore, the triggering of the relevant business system to execute the corresponding business closed-loop operation specifically includes: When the synchronized flow status information indicates a received status, the inventory management system in the relevant business system is triggered to complete the corresponding material inventory quantity deduction operation; and / or This triggers the OA system or official document circulation platform in the relevant business system to update the status of the relevant entity document to "archived".

[0014] Optionally, the method further includes an exception handling step: When the validity verification fails, the controlled internal system triggers a preset exception handling process and captures the failed verification action as an exception flow event. The abnormal flow event is synchronized to the relevant business system through the state synchronization function, so as to trigger the relevant business system to terminate the current delivery operation or update to the abnormal flow status.

[0015] Optionally, the method further includes an audit evidence preservation step: Generate hash records for the execution results of the aforementioned business events and the status synchronization function; The hash records are synchronized to a tamper-proof audit log library or consortium blockchain to form an immutable audit trail.

[0016] Optionally, the method further includes offline verification and log synchronization steps: When the network connection is interrupted, the terminal can perform local verification using pre-cached key parameters and verification policies and cache the operation log locally on the terminal. After the network connection is restored, the operation log automatically synchronized by the terminal is received, and it is captured as the flow service event and synchronized to the relevant business system to ensure the final consistency of the flow status.

[0017] Optionally, the method further includes a lifecycle management step: The cryptographic tokens are subject to a predefined lifecycle policy. When the synchronized flow status information is characterized as received or archived, the lifecycle policy is triggered to automatically invalidate the binding relationship between the corresponding cryptographic token and the original identification information.

[0018] Optionally, the method further includes an internal status notification step: After the flow status information is synchronized to the relevant business system, the relevant business system is triggered to send a business status change notification to the preset receiving terminal through a group-autonomous and controllable internal notification channel. The notification channels include: the organization's self-built messaging system, in-application push notifications, or notification interfaces of enterprise-level instant messaging tools based on the organization's internal architecture.

[0019] A second aspect of the present invention provides a cryptographically-based flow state synchronization integration system, the system being deployed within a controlled internal system of a specific group, comprising: The information collection and tag generation module is configured to: receive business requests from relevant business systems, obtain original identification information corresponding to the business requests; generate a cryptographic tag uniquely bound to the original identification information based on a preset cryptographic security key and a preset interception strategy, and output the cryptographic tag and carry it on a controlled information carrier; The flow verification and event capture module is configured to: receive a verification request initiated by the terminal for the cryptographic token during the flow of the controlled information carrier carrying the cryptographic token, and perform validity verification; when the validity verification is successful, capture the verification action as a flow business event; The status deduction module is configured to: determine the current flow status information of the controlled information carrier based on the flow business event and the request source identifier obtained by parsing the verification request; The state synchronization and closed-loop triggering module is configured to: synchronize the flow state information to the relevant business systems deployed within a specific group through the state synchronization function deployed in the controlled internal system, so as to trigger the relevant business systems to execute the corresponding business closed-loop operation, thereby realizing the logical decoupling of cryptographic verification actions and relevant business systems.

[0020] Furthermore, the state deduction module is further configured as follows: Obtain the request source identifier of the verification request and determine the permission policy to which the verification node belongs; By combining preset rules, the request source identifier, the permission policy, and the circulation business event are associated and matched to determine the corresponding circulation status information of being prepared, being delivered, being delivered, or being received.

[0021] Furthermore, in the state synchronization and closed-loop triggering module, the state synchronization module serves as an independent data bus service and performs the following operations: The flow status information is synchronized to the relevant business systems via a message queue; When a timeout or failure to write back the status is detected in the relevant business system, a message persistence and retry mechanism is triggered to ensure eventual data consistency between the controlled internal system and the relevant business system.

[0022] Furthermore, when the state synchronization and closed-loop triggering module triggers the relevant business system to execute the corresponding business closed-loop operation, it is specifically configured as follows: When the synchronized flow status information indicates a received status, the inventory management system in the relevant business system is triggered to complete the corresponding material inventory quantity deduction operation; and / or This triggers the OA system or official document circulation platform in the relevant business system to update the status of the relevant entity document to "archived".

[0023] Optionally, the system further includes an exception handling module: When the validity verification fails, the controlled internal system triggers a preset exception handling process and captures the failed verification action as an exception flow event. The abnormal flow event is synchronized to the relevant business system through the state synchronization function, so as to trigger the relevant business system to terminate the current delivery operation or update to the abnormal flow status.

[0024] Optionally, the system further includes an audit and evidence storage module: Generate hash records for the execution results of the aforementioned business events and the status synchronization function; The hash records are synchronized to a tamper-proof audit log library or consortium blockchain to form an immutable audit trail.

[0025] Optionally, the system further includes an offline verification and log synchronization module, configured as follows: When the network connection is interrupted, the terminal can perform local verification using pre-cached key parameters and verification policies and cache the operation log locally on the terminal. After the network connection is restored, the operation log automatically synchronized by the terminal is received, and it is captured as the flow service event and synchronized to the relevant business system to ensure the final consistency of the flow status.

[0026] Optionally, the system further includes a lifecycle management module, configured to: The cryptographic tags are constrained based on a predefined lifecycle strategy; When the synchronized flow status information is characterized as received or archived, the lifecycle policy is triggered to automatically invalidate the binding relationship between the corresponding cryptographic token and the original identification information.

[0027] Optionally, the system further includes an internal status notification module: After the flow status information is synchronized to the relevant business system, the relevant business system is triggered to send a business status change notification to the preset receiving terminal through a group-autonomous and controllable internal notification channel. The notification channels include: the organization's self-built messaging system, in-application push notifications, or notification interfaces of enterprise-level instant messaging tools based on the organization's internal architecture.

[0028] A third aspect of the present invention provides an electronic device including a processor, a memory, and a communication interface; wherein the memory stores one or more computer programs configured to be executed by the processor to enable the electronic device to implement the cryptographically-based flow state synchronization integration method as described in the first aspect of the present invention or any optional embodiment of the first aspect.

[0029] A fourth aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the cryptographically-based flow state synchronization integration method as described in the first aspect of the present invention or any optional embodiment of the first aspect.

[0030] The fifth aspect of the present invention provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the cryptographically-based flow state synchronization integration method as described in the first aspect of the present invention or any optional embodiment of the first aspect.

[0031] Compared with the prior art, the present invention has the following beneficial effects: This invention achieves logical decoupling between verification actions and business systems, enhancing business continuity: By introducing independent state synchronization functionality into the controlled internal system, an integrated architecture based on asynchronous event-driven mechanisms is constructed. This architecture deeply decouples the underlying cryptographic verification actions from the upper-layer business logic execution, ensuring that the verification of controlled information carriers no longer synchronously depends on the real-time interface responses of related business systems. This design effectively avoids the paralysis of frontline verification operations due to single points of failure, performance bottlenecks, or network communication interruptions in related business systems. In extreme cases, the terminal can still perform legitimacy determinations and capture business events based on the controlled internal system. After the business system recovers, the asynchronous mechanism ensures eventual data consistency, significantly improving the business resilience of the entire collaborative network.

[0032] To ensure synchronization between physical flow and digital status and drive business closure: This invention derives the current flow status information of the controlled information carrier based on the request source identifier and permission policy obtained from parsing and verifying the request, and synchronizes it to relevant business systems through a monitoring mechanism. When the flow status information indicates that the document has been received or archived, the relevant business system is triggered to perform an inventory quantity deduction operation for the corresponding material, or to update the status of the relevant entity document to archived. This mechanism uses a cryptographically marked successful verification event as the baseline trigger event, reducing the risk of discrepancies between accounts and actual inventory and time delays caused by manual data entry. Simultaneously, in conjunction with message persistence, failure retries, and manual compensation processes, it ensures eventual data consistency between the controlled internal system and relevant business systems.

[0033] Strengthening access control to meet compliance audit and traceability requirements: This invention generates cryptographic tokens for the original identifier information of proxies, and combines them with preset rules for association matching and differentiated controlled output, achieving secure cross-node transfer without exposing the original identifier information. This invention uses the execution results of transfer business events and state synchronization functions as key operations to generate tamper-proof audit log records or synchronize them to the consortium blockchain. This constructs an audit trail covering the entire lifecycle of token generation, verification, state synchronization, and automatic invalidation of binding relationships for specific groups, meeting the compliance and traceability requirements of controlled groups for the transfer of materials and information. Attached Figure Description

[0034] Figure 1 This is a system architecture diagram of the flow status synchronization integration system according to an embodiment of the present invention; Figure 2 This is a flowchart of the flow state synchronization integration method according to an embodiment of the present invention; Figure 3 This is a flowchart illustrating the business closed-loop implementation process in a typical application scenario of this invention. Figure 4 This is a module architecture diagram of the flow status synchronization integration system according to an embodiment of the present invention. Detailed Implementation

[0035] Before describing the specific embodiments of the present invention in detail, the key specific terms involved in the entire specification and claims are defined as follows to enable those skilled in the art to accurately understand the technical solutions of the present invention: Controlled internal system: In this invention, it refers to a server-side system belonging to a specific group, responsible for performing cryptographic verification independent of related business systems, and acting as the main body for state synchronization processing. Furthermore, the deployment form of the controlled internal system (or internal server) should not constitute a limitation on the scope of protection of this invention. It can be physically deployed in the local data center of the specific group, or logically deployed in a private cloud space rented exclusively by the specific group or in a controlled virtual private cloud (VPC), as long as its data access permissions are controlled by that specific group.

[0036] Related business systems: In this invention, these refer to software platforms or business modules deployed within a specific group to receive flow status information and execute final business closed-loop operations. This includes, but is not limited to, third-party collaboration platforms integrated via APIs or dedicated links.

[0037] Original identification information: In this invention, it refers to the data to be protected that can uniquely determine the identity, attributes or location of an object, which serves as the core basis for triggering and completing the status update of the relevant business system.

[0038] Cryptographic token: In this invention, it refers to a data structure generated by the controlled internal system that acts as a proxy for the original identification information. The validity verification of this token serves as a baseline trigger event to drive the synchronization of the execution state of the relevant business systems.

[0039] Controlled information carrier: In this invention, it refers to a physical medium or digital data packet used to carry the cryptographic token.

[0040] Request source identifier: In this invention, it refers to a data field or logical identifier used to characterize the identity of the node that initiates the verification request and to serve as an associated parameter for deriving the flow status information.

[0041] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0042] Example 1: Overall Architecture of a Cryptographically Tag-Based Flow State Synchronization Integration System This embodiment discloses the overall architecture of a flow state synchronization integration system based on cryptographic tags.

[0043] like Figure 1As shown, the system is deployed in a controlled network environment of a specific group, and its core consists of a controlled internal system (101). This controlled internal system (101) is logically independent of the group's related business systems (105), realizing the logical decoupling of the underlying cryptographic verification actions and the upper-level business logic.

[0044] The controlled internal system (101) operates in a controlled network environment with exclusive control. It integrates tag generation, verification and parsing functions, and a state synchronization function (104) as an independent data bus service. The state synchronization function (104) is configured to capture in real time the flow of business events generated by the verification action initiated by the terminal (109), and synchronize the flow status information to the relevant business system (105) based on preset rules.

[0045] The relevant business systems (105) include, but are not limited to, the Hospital Information System (HIS) (106), the Inventory Management System (107), or the OA System (108). These systems interact with the controlled internal system (101) through standardized API interfaces. The core feature of this architecture is that the controlled internal system (101) does not directly rely on the real-time response of the relevant business system (105) to complete the verification logic.

[0046] When the terminal (109) scans the cryptographic markers on the controlled information carrier, a verification request is sent to the controlled internal system (101). The controlled internal system (101) independently performs validity verification and captures the successful verification action as a flow business event. Subsequently, the state synchronization function (104) writes the corresponding flow status information back to the relevant business system (105) by listening to the message queue, database transaction log, or specific events published by the system. This asynchronous synchronization mechanism ensures that even if the relevant business system (105) experiences a network connection interruption or failure, the front-line verification and delivery operations can continue through the offline verification mode of the controlled internal system (101) or the terminal (109), and the state synchronization function (104) ensures eventual data consistency after the network connection is restored.

[0047] In the specific business integration scenario of this invention, the relevant business systems include, but are not limited to, hospital information systems (HIS), enterprise resource planning systems (ERP), inventory management systems, or government approval and processing platforms.

[0048] Furthermore, the controlled information carrier can be medical consumables, physical documents, or digital communication messages. Meanwhile, the circulation status information can specifically represent various business node statuses such as ready for shipment, in transit, delivered, received, or archived.

[0049] In addition, the state synchronization function can be used as an independent data bus service to synchronize the state with the relevant business systems by (but not limited to) listening to message queues, database transaction logs or specific events published by the system.

[0050] Example 2: A method for synchronizing and integrating transition states based on cryptographic tags This embodiment discloses the underlying technical logic and method steps of the present invention.

[0051] like Figure 2 As shown, the method is deployed in a controlled internal system of a specific group and includes the following steps to achieve logical decoupling and eventual data consistency.

[0052] Information collection and tag generation steps (201) The controlled internal system receives business requests from relevant business systems and obtains the original identification information corresponding to the business request. Subsequently, based on a preset cryptographic security key and a preset interception strategy, a cryptographic token uniquely bound to the original identification information is generated. This cryptographic token is converted into a machine-readable format and attached to the controlled information carrier to proxy the original identification information into physical or digital circulation processes.

[0053] Flow verification and event capture steps (202) During the circulation of the controlled information carrier carrying the cryptographic token, the controlled internal system receives the verification request (203) initiated by the terminal for the cryptographic token and performs validity verification (204).

[0054] At this point, there are two verification branches: If the validity verification fails, the exception handling step (205) is executed: the controlled internal system triggers the preset exception handling process, captures the action that failed the verification as an exception flow event, and synchronizes it to the relevant business system through the status synchronization function to trigger it to terminate the current delivery operation or update to the exception flow status.

[0055] If the validity verification is successful, the verification action is captured as a flow business event (206). This mechanism transforms the physical scan action into a baseline trigger event that the system can recognize, thereby achieving logical decoupling between the verification action and the related business system.

[0056] State derivation steps (207) Based on the aforementioned circulation business events, the controlled internal system further parses the request source identifier obtained from the verification request to obtain the source terminal identity represented by the request source identifier and determines the corresponding permission policy. Combining a preset correspondence, the source terminal identity, the permission policy, and the circulation business events are associated and matched to deduce the current circulation status information (208) of the controlled information carrier. The circulation status information includes "prepared," "in delivery," "delivered," or "received."

[0057] State synchronization and closed-loop triggering steps (209) The state synchronization function deployed in the controlled internal system acts as an independent data bus service. By listening to message queues, database transaction logs, or specific events published by the system, it synchronizes the derived flow state information to the relevant business systems deployed within the specific group.

[0058] During this synchronization process, the system performs a status synchronization verification (210): If the relevant business system is detected to have a timeout response or a failure to write back the status synchronization, the message persistence and failure retry mechanism (211) is triggered to ensure the eventual consistency of data between the controlled internal system and the relevant business system.

[0059] If synchronization is successful, the relevant business system is triggered to execute the corresponding business closed-loop operation (212). Specifically, when the synchronized flow status information indicates that it has been received, the inventory management system in the relevant business system is triggered to complete the inventory quantity deduction operation of the corresponding material, or the OA system is triggered to execute the operation of updating the status of the relevant entity document to archived.

[0060] Additional functional logic steps (213) In addition to the core principles mentioned above, this method also includes the following mechanisms: Offline verification and log synchronization mechanism: When the network connection is interrupted, the terminal can use the pre-cached key parameters and verification strategy to perform local basic verification and record operation logs; after the network connection is restored, the operation logs are automatically synchronized to the controlled internal system to capture them as business events.

[0061] Audit evidence storage mechanism: The execution results of the business events and the status synchronization function are generated into hash records, and the hash records are synchronized to the tamper-proof audit log library or consortium blockchain to form an immutable audit trace.

[0062] Lifecycle management mechanism: When the synchronized flow status information is characterized as received or archived, a predefined lifecycle strategy is triggered, causing the binding relationship between the corresponding cryptographic token and the original identification information to automatically become invalid.

[0063] Internal status notification mechanism: After the flow status information is synchronized to the relevant business system, the relevant business system is triggered to send a business status change notification to the preset receiving terminal through an internal notification channel that is autonomously controlled by the group (including: the organization's self-built messaging system, in-application push, or notification interface of an enterprise-level instant messaging tool based on the organization's internal architecture), so as to realize a closed-loop reminder for business collaboration.

[0064] Example 3: Implementation of Business Closed Loop in Typical Application Scenarios like Figure 3 As shown, this embodiment applies the aforementioned cryptographically-based flow state synchronization integration method to specific business scenarios. This embodiment includes medical supply delivery scenarios and official document flow scenarios.

[0065] Medical supply delivery scenario In this scenario, the relevant business systems are the Hospital Information System (HIS) and the Inventory Management System, and the controlled internal systems are deployed in the hospital's controlled network environment.

[0066] Clinical departments initiate material requisitions through the Hospital Information System (HIS). The controlled internal system obtains the original identification information and generates a cryptographic token (301). This cryptographic token is converted into a machine-readable format and attached to the material packaging, i.e., the controlled information carrier.

[0067] The distribution center prepares the goods according to the requisition form. After the goods are prepared, the status synchronization function in the controlled internal system will synchronize the circulation status information to "prepared" (302).

[0068] When a delivery person picks up supplies, they use a terminal to scan a cryptographic token to initiate a verification request. After the controlled internal system verifies the request, it captures the verification action as a workflow event, combines it with the request source identifier to deduce the workflow status information during delivery, and asynchronously synchronizes it to the hospital information system (HIS) (303) through the status synchronization function.

[0069] When the delivery person delivers the supplies to the designated node in the target department, they scan the cryptographic token again using the terminal and initiate a verification request. The controlled internal system captures this transaction event, derives the delivery status information, and synchronizes it to the hospital information system (HIS) (304).

[0070] The nurses in the target department perform final verification and receipt of the supplies, scanning the cryptographic tokens using their terminals. After successful verification and capture of the transfer event by the controlled internal system, the received transfer status information is derived. The status synchronization function updates the status in the Hospital Information System (HIS) accordingly and triggers the inventory management system to deduct the corresponding supply's inventory quantity (305). At this point, the binding relationship between the cryptographic token and the original identification information automatically becomes invalid. This process achieves logical decoupling between the physical scanning verification action and the status update of the relevant business system.

[0071] Scenario of official document circulation in government agencies In another optional scenario for the circulation of official documents, the relevant business system is the OA system, and the controlled information carrier is the physical document.

[0072] When physical documents are transferred to the archiving node, the archiving manager uses a terminal to scan the cryptographic markers on the physical documents (306).

[0073] After successful verification by the controlled internal system, the workflow event is captured, and the archived workflow status information (307) is derived by combining the permission policies of the file management personnel.

[0074] Subsequently, the status synchronization function triggers the OA system to perform the operation of updating the status of the relevant entity documents to archived (308), thereby realizing the business loop in this scenario.

[0075] Example 4: Functional Module of a Synchronization Integration System for Transitional State Based on Cryptographic Symbols like Figure 4 As shown, this embodiment discloses the configuration of functional modules and their internal data flow relationships in a controlled internal system (400) deployed to a specific group. The system achieves logical decoupling between verification actions and related business systems (406) through the independent configuration and data interaction of each module.

[0076] Information collection and tag generation module (401) It is configured to: receive business requests and original identification information issued from relevant business systems (406); generate a cryptographic tag uniquely bound to the original identification information based on a preset cryptographic security key and a preset interception strategy, and output the cryptographic tag and carry it on a controlled information carrier (412).

[0077] Flow verification and event capture module (402) It is configured to: during the flow of the controlled information carrier (412) carrying the cryptographic token, receive the terminal (411) to initiate a verification request for the cryptographic token and perform a validity verification; when the validity verification is successful, capture the verification action as a flow business event.

[0078] State derivation module (403) It is configured to: based on the flow service event and the request source identifier obtained by parsing the verification request, obtain the identity of the source terminal (receiving terminal (411)) represented by the request source identifier, and determine the corresponding permission policy; combine the preset correspondence relationship to associate and match the source terminal identity, the permission policy and the flow service event, thereby deriving the current flow status information of the controlled information carrier (412).

[0079] State synchronization and closed-loop triggering module (404) It is configured to: synchronize the derived flow status information to the relevant business system (406) deployed within a specific group through a message queue by using the status synchronization function deployed in the controlled internal system (400) as an independent data bus service; when the synchronization is successful, the relevant business system (406) is triggered to execute the corresponding business closed-loop operation; when the response timeout of the relevant business system (406) or the status synchronization write-back failure is detected, the message persistence and failure retry mechanism is triggered to ensure the eventual consistency of data between the controlled internal system (400) and the relevant business system (406).

[0080] Optionally, the system further includes an exception handling module (405). It is configured to: when the validity verification fails, trigger a preset exception handling process and capture the failure of the verification as an abnormal flow event; through the state synchronization and closed-loop triggering module (404), synchronize the abnormal flow event to the relevant business system (406) to trigger it to terminate the current delivery operation or update to the abnormal flow state.

[0081] Optionally, the system further includes an audit evidence storage module (407), configured to: generate a hash record from the execution result of the flow business event and the status synchronization and closed-loop triggering module (404); and synchronize the hash record to an anti-tampering audit log library or consortium chain (413) to form an untamperable audit trace.

[0082] Optionally, the system further includes an offline verification and log synchronization module (408), configured to: when the network connection is interrupted, support the receiving terminal (411) to perform local verification using pre-cached key parameters and verification strategies and cache the operation log locally on the terminal; after the network connection is restored, the receiving terminal (411) automatically synchronizes the operation log to capture it as the flow service event, and synchronizes it to the relevant business system (406) via the state synchronization and closed-loop triggering module (404) to ensure the final consistency of the flow state.

[0083] Optionally, the system further includes a lifecycle management module (409), configured to: constrain the cryptographic token based on a preset lifecycle policy; when the synchronized flow status information is characterized as received or archived, trigger the lifecycle policy to invalidate the binding relationship between the corresponding cryptographic token and the original identification information, so that the controlled internal system (400) rejects subsequent verification requests for the cryptographic token.

[0084] Optionally, the system further includes an internal status notification module (410), configured to: after the flow status information is synchronized to the relevant business system (406), trigger the relevant business system (406) to send a business status change notification to a preset receiving terminal through a group-controlled internal notification channel (414); wherein, the group internal notification channel (414) includes: a message system built by the organization, in-application push, or a notification interface of an enterprise-level instant messaging tool based on the organization's internal architecture.

[0085] Through the configuration of the above functional modules, the flow verification and event capture module (402) executes cryptographic logic and event generation, and the state update is executed by the state synchronization and closed-loop triggering module (404). The controlled internal system (400) realizes the logical decoupling of the verification action and the related business system (406) through asynchronous data flow relationship.

[0086] Example 5: Electronic Device Example This application also provides an electronic device that logically corresponds to the foregoing method embodiments. Specifically, the electronic device includes a processor and a memory; wherein the memory is used to store a computer program, and the processor implements the steps of the cryptographically-tagged flow state synchronization integration method as described in any one of claims 1 to 9 by calling and executing the computer program stored in the memory.

[0087] It should be understood that the electronic device, as the hardware carrier for executing the aforementioned method, has internal hardware connections and operational logic that are logically consistent with the steps of the aforementioned method.

[0088] Example 6: Example of a computer-readable storage medium This invention also provides a computer-readable storage medium storing a computer program thereon. When executed by a processor, the computer program implements the steps of the cryptographically-tagged flow state synchronization integration method as described in any one of claims 1 to 9. The computer-readable storage medium may be non-transitory, including but not limited to disks, optical disks, flash memory, or any form of electronic storage device.

[0089] It should be noted that the electronic device provided in the embodiments of the present invention includes a processor for executing instructions stored in a memory to implement the above-described method. The processor should be understood as a logic device with computational processing capabilities, and its specific form should not constitute a limitation on the scope of protection of the present invention.

[0090] Furthermore, in these embodiments of the invention, the aforementioned method steps can all be implemented by a computer program product. This computer program product includes a computer program / instruction that, when executed by a processor, implements the steps of any of the above method embodiments. This computer program product can be written in any combination of one or more programming languages ​​and can be distributed and deployed via network download, or stored in memory, registers, or any form of storage medium.

[0091] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art can make various improvements and modifications without departing from the spirit and principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for synchronizing and integrating transition states based on cryptographic tokens, characterized in that, The method, deployed in a controlled internal system of a specific group, includes the following steps: Information collection and tag generation steps: Receive business requests from relevant business systems, obtain the original identification information corresponding to the business requests; based on preset cryptographic security keys and preset interception strategies, generate a cryptographic tag uniquely bound to the original identification information, and output the cryptographic tag and carry it on a controlled information carrier; Flow verification and event capture steps: During the flow of the controlled information carrier carrying the cryptographic token, a verification request initiated by the verification node for the cryptographic token is received, and validity verification is performed; when the validity verification is successful, the verification action is captured as a flow business event; State deduction steps: Based on the flow business event and the request source identifier obtained by parsing the verification request, determine the current flow status information of the controlled information carrier; State synchronization and closed-loop triggering steps: Through the state synchronization function deployed in the controlled internal system, the flow state information is synchronized to the relevant business systems deployed within the specific group, so as to trigger the relevant business systems to execute the corresponding business closed-loop operation, thereby realizing the logical decoupling of cryptographic verification actions and relevant business systems.

2. The method for synchronizing and integrating flow states based on cryptographic tags according to claim 1, characterized in that, The state derivation step, which determines the current circulation state information of the controlled information carrier, specifically includes: Obtain the source terminal identity represented by the request source identifier and determine the corresponding permission policy; combine the preset correspondence relationship to associate and match the source terminal identity, the permission policy and the circulation business event to determine the corresponding circulation status information of being prepared, being delivered, being delivered or being received.

3. The method for synchronizing and integrating transition states based on cryptographic tags according to claim 1, characterized in that, In the state synchronization and closed-loop triggering steps, the state synchronization function, as an independent data bus service, performs the following operations: The flow status information is synchronized to the relevant business systems via a message queue; When a timeout or failure to write back the status is detected in the relevant business system, a message persistence and retry mechanism is triggered to ensure eventual data consistency between the controlled internal system and the relevant business system.

4. The method for synchronizing and integrating transition states based on cryptographic tags according to claim 1, characterized in that, The triggering of relevant business systems to execute corresponding business closed-loop operations specifically includes: When the synchronized flow status information indicates a received status, the inventory management system in the relevant business system is triggered to automatically perform a deduction operation on the corresponding material's inventory quantity; and / or This triggers the OA system or official document circulation platform in the relevant business system to perform the archiving operation of the relevant entity documents or business documents.

5. The method for synchronizing and integrating transition states based on cryptographic tags according to claim 1, characterized in that, The method also includes an exception handling step: When the validity verification fails, the controlled internal system triggers a preset exception handling process and captures the failed verification action as an exception flow event. The abnormal flow event is synchronized to the relevant business system through the state synchronization function, so as to trigger the relevant business system to terminate the current delivery operation or update to the abnormal flow status.

6. The method for synchronizing and integrating transition states based on cryptographic tags according to claim 1, characterized in that, The method also includes an audit evidence preservation step: Generate hash records for the execution results of the aforementioned business events and the status synchronization function; The hash records are synchronized to a tamper-proof audit log library or consortium blockchain to form an immutable audit trail.

7. The method for synchronizing and integrating transition states based on cryptographic tags according to claim 1, characterized in that, The method also includes offline verification and log synchronization steps: When the network connection is interrupted, the terminal can perform local verification using pre-cached key parameters and verification policies and cache the operation log locally on the terminal. After the network connection is restored, the operation log automatically synchronized by the terminal is received, and it is captured as the flow service event and synchronized to the relevant business system to ensure the final consistency of the flow status.

8. The method for synchronizing and integrating transition states based on cryptographic tags according to claim 1, characterized in that, The method also includes lifecycle management steps: The cryptographic tokens are subject to a preset lifecycle policy; When the synchronized flow status information indicates that it has been received or archived, the lifecycle policy is triggered to invalidate the binding relationship between the corresponding cryptographic token and the original identification information, so that the controlled internal system rejects subsequent verification requests for the cryptographic token.

9. The method for synchronizing and integrating transition states based on cryptographic tags according to claim 1, characterized in that, The method also includes an internal status notification step: After the flow status information is synchronized to the relevant business system, the relevant business system is triggered to send a business status change notification to the preset receiving terminal through a group-autonomous and controllable internal notification channel. The notification channels include: the organization's self-built messaging system, in-application push notifications, or notification interfaces of enterprise-level instant messaging tools based on the organization's internal architecture.

10. A flow state synchronization integration system based on cryptographic tokens, characterized in that, The system is deployed within a controlled internal system of a specific group, including: The information collection and tag generation module is configured to: receive business requests from relevant business systems, obtain original identification information corresponding to the business requests; generate a cryptographic tag uniquely bound to the original identification information based on a preset cryptographic security key and a preset interception strategy, and output the cryptographic tag and carry it on a controlled information carrier; The flow verification and event capture module is configured to: receive a verification request initiated by a verification node for the cryptographic token during the flow of the controlled information carrier carrying the cryptographic token, and perform validity verification; when the validity verification is successful, capture the verification action as a flow business event; The status deduction module is configured to: determine the current flow status information of the controlled information carrier based on the flow business event and the request source identifier obtained by parsing the verification request; The state synchronization and closed-loop triggering module is configured to: synchronize the flow state information to the relevant business systems deployed within a specific group through the state synchronization function deployed in the controlled internal system, so as to trigger the relevant business systems to execute the corresponding business closed-loop operation, thereby realizing the logical decoupling of cryptographic verification actions and relevant business systems.

11. A cryptographically-based flow state synchronization integration system according to claim 10, characterized in that, The state deduction module is further configured to: obtain the source terminal identity represented by the request source identifier and determine the corresponding permission policy; combine the preset correspondence relationship to associate and match the source terminal identity, the permission policy and the circulation business event to determine the corresponding circulation status information of being prepared, being delivered, being delivered or being received.

12. The cryptographically-based flow state synchronization integration system according to claim 10, characterized in that, The state synchronization and closed-loop triggering module is further configured to: act as an independent data bus service, synchronize the flow status information to the relevant business system through a message queue; and trigger the message persistence and failure retry mechanism when the relevant business system's response times out or the state synchronization write-back fails, so as to ensure the eventual consistency of data between the controlled internal system and the relevant business system.

13. The cryptographically-based flow state synchronization integration system according to claim 10, characterized in that, The state synchronization and closed-loop triggering module is further configured to: when the synchronized circulation status information indicates a received status, trigger the inventory management system in the relevant business system to automatically perform the corresponding material inventory quantity deduction operation; and / or trigger the OA system or official document circulation platform in the relevant business system to perform the archiving operation of relevant entity documents or business documents.

14. The cryptographically-based flow state synchronization integration system according to claim 10, characterized in that, The system also includes an exception handling module, configured to: trigger a preset exception handling process when the validity verification fails, and capture the failure of the verification as an exception flow event; The abnormal flow event is synchronized to the relevant business system through the state synchronization and closed-loop triggering module, so as to trigger the relevant business system to terminate the current delivery operation or update to the abnormal flow state.

15. A cryptographically-based flow state synchronization integration system according to claim 10, characterized in that, The system also includes an audit evidence storage module, configured to: generate hash records by synchronizing the flow business events and the status with the execution results of the closed-loop triggering module; and synchronize the hash records to an anti-tampering audit log library or consortium blockchain to form an immutable audit trace.

16. A cryptographically-based flow state synchronization integration system according to claim 10, characterized in that, The system also includes an offline verification and log synchronization module, configured as follows: When the network connection is interrupted, the terminal can perform local verification using pre-cached key parameters and verification policies and cache the operation log locally on the terminal. After the network connection is restored, the operation log automatically synchronized by the terminal is received, and it is captured as the flow service event and synchronized to the relevant business system to ensure the final consistency of the flow status.

17. A cryptographically-based flow state synchronization integration system according to claim 10, characterized in that, The system also includes a lifecycle management module, configured as follows: The cryptographic tokens are constrained based on a preset lifecycle strategy; When the synchronized flow status information indicates that it has been received or archived, the lifecycle policy is triggered to invalidate the binding relationship between the corresponding cryptographic token and the original identification information, so that the controlled internal system rejects subsequent verification requests for the cryptographic token.

18. A cryptographically-based flow state synchronization integration system according to claim 10, characterized in that, The system also includes an internal status notification module, configured as follows: After the flow status information is synchronized to the relevant business system, the relevant business system is triggered to send a business status change notification to the preset receiving terminal through a group-autonomous and controllable internal notification channel. The notification channels include: the organization's self-built messaging system, in-application push notifications, or notification interfaces of enterprise-level instant messaging tools based on the organization's internal architecture.

19. An electronic device, characterized in that, Includes processor, memory, and communication interface; The memory stores one or more computer programs configured to be executed by the processor to enable the electronic device to implement the cryptographically-based flow state synchronization integration method as described in any one of claims 1 to 9.

20. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the cryptographically marked flow state synchronization integration method as described in any one of claims 1 to 9.

21. A computer program product, comprising a computer program / instructions, characterized in that, When the computer program / instruction is executed by the processor, it implements the steps of the cryptographically marked flow state synchronization integration method as described in any one of claims 1 to 9.

Images