Cross-system signature card state synchronization method and device, storage medium and processor

Abstract

The embodiment of the invention provides a cross-system signature card state synchronization method and device, a storage medium and a processor. The method comprises the following steps: receiving process update information for a signature card sent by a verification and seal system, the process update information being generated when a user who modifies permission verification changes the state of the signature card in the verification and seal system; determining a first operation process executed when the state of the signature card is changed in the verification system according to the process updating information; adjusting a first state flag corresponding to the first operation process into a first preset flag, and determining a process category to which the first operation process belongs; under the condition that the process category is a preset category, adjusting a second state flag and an execution date of a second operation process associated with the first operation process according to a preset NAND mechanism; and after the second state flag and the execution date of the second operation process are adjusted, updating the execution date of the first operation process so as to accurately synchronize the state of the seal card to the seal management system.

Description

Technical Field

[0001] This application relates to the field of electronic signature technology, specifically to a method, apparatus, storage medium, processor, and computer program product for synchronizing signature card status across systems. Background Technology

[0002] In existing technologies, the seal verification system, as an upstream business system, can synchronize the operation process of the seal card to the seal management system in real time. The seal management system can then uniformly manage the process information of each operation process of the seal card.

[0003] However, the various operation processes of the seal card have a strong sequential relationship, and the states of the seal cards are also interdependent. When the verification system sends the process information to the seal management system in sequence according to the operation process, the process information received by the seal management system as a downstream system may be out of order. When updating data across systems, it is difficult to ensure the accuracy of the data update, resulting in inaccurate synchronization of the seal card status across systems. Summary of the Invention

[0004] The purpose of this application is to provide a method, apparatus, storage medium, processor, and computer program product for synchronizing the status of signature cards across systems, in order to solve the problem that the synchronization of signature card status across systems is not accurate enough in the prior art.

[0005] To achieve the above objectives, the first aspect of this application provides a method for synchronizing signature card status across systems, applied to a signature management system, comprising:

[0006] Receive process update information for the signature card sent by the signature verification system. The process update information is generated when the user with modified permissions changes the status of the signature card in the signature verification system.

[0007] The first operation procedure to be performed when changing the status of the signature card in the signature verification system is determined based on the process update information.

[0008] Adjust the first status flag corresponding to the first operation process to the first preset flag, and determine the process category to which the first operation process belongs;

[0009] When the process category is a preset category, the second status flag and execution date of the second operation process associated with the first operation process are adjusted according to the preset NAND mechanism;

[0010] After adjusting the second status flag and execution date of the second operation process, update the execution date of the first operation process to synchronize the status of the seal card to the seal management system.

[0011] In this embodiment, the preset categories include a seal verification process category, an account cancellation process category, and an account opening cancellation process category. When the process category is a preset category, adjusting the second status flag and execution date of the second operation process associated with the first operation process according to a preset AND-NOT mechanism includes: when the process category is a seal verification process category, adjusting the second status flag and execution date of the second operation process according to a preset AND mechanism; when the process category is an account cancellation process category or an account opening cancellation process category, adjusting the second status flag and execution date of the second operation process according to a preset NOT mechanism.

[0012] In this embodiment of the application, when the process category is a seal verification process, adjusting the second status flag and execution date of the second operation process associated with the first operation process according to a preset AND mechanism includes: when the process category is a seal verification process, determining whether the first operation process is a seal verification collection process; when the first operation process is not a seal verification collection process, determining that the second operation process is another seal verification operation process that precedes the first operation process; when the status flag of the other seal verification operation process is negative, adjusting the status flag of the other seal verification operation process to the first preset flag according to the AND mechanism; and adjusting the execution date corresponding to the other seal verification operation processes to the date when the first operation process is executed in the seal verification system according to the AND mechanism.

[0013] In this embodiment of the application, when the process category is the account cancellation process category, adjusting the second status flag and execution date of the second operation process according to the preset non-mechanism includes: when the process category is the account cancellation process category, determining that the second operation process is other seal verification operation processes and audit processes that are ranked before the first operation process; and clearing the status flag and execution date of other seal verification operation processes and audit processes according to the non-mechanism.

[0014] In this embodiment of the application, when the process category is the account opening and cancellation process category, adjusting the second status flag and execution date of the second operation process according to the preset non-mechanism includes: when the process category is the account opening and cancellation process category, determining that the second operation process is another seal verification operation process that precedes the first operation process; adjusting the status flag of the other seal verification operation process to the second preset flag according to the non-mechanism, and clearing the execution date of the other seal verification operation process.

[0015] In this embodiment of the application, after adjusting the second status flag and execution date of the second operation process, updating the execution date of the first operation process to synchronize the status of the seal card to the seal management system includes: after adjusting the second status flag and execution date of the second operation process, determining whether there is an anomaly in the process update information; if there is an anomaly in the process update information, updating the execution date corresponding to the first operation process to the date on which the seal management system receives the process update information; if there is no anomaly in the process update information, updating the execution date corresponding to the first operation process to the date on which the user executes the first operation process in the seal verification system.

[0016] In this embodiment of the application, the method further includes: if the process category is not a preset category, determining that the first operation process is an audit operation process, and determining whether there is an associated card corresponding to the seal card; if there is a corresponding associated card, adjusting the status flag corresponding to the audit operation process of the associated card to the status corresponding to the execution result of the audit operation process; after adjusting the status flag corresponding to the audit operation process of the associated card, updating the execution date of the audit operation process to synchronize the status of the seal card to the seal management system.

[0017] A second aspect of this application provides a device for synchronizing the status of signature cards across systems, comprising:

[0018] The information receiving module is used to receive process update information for the seal card sent by the seal verification system. The process update information is generated when the user who modifies the permission verification changes the status of the seal card in the seal verification system.

[0019] The operation process determination module is used to determine the first operation process to be executed when the status of the seal card is changed in the seal verification system, based on the process update information.

[0020] The process category determination module is used to adjust the first status flag corresponding to the first operation process to the first preset flag, and determine the process category to which the first operation process belongs;

[0021] The information adjustment module is used to adjust the second status flag and execution date of the second operation process associated with the first operation process according to a preset NAND mechanism when the process category is a preset category.

[0022] The status synchronization module updates the execution date of the first operation process after adjusting the second status flag and execution date of the second operation process, so as to synchronize the status of the seal card to the seal management system.

[0023] A third aspect of this application provides a processor configured to perform the above-described method for synchronizing the state of a signature card across systems.

[0024] A fourth aspect of this application provides a machine-readable storage medium storing instructions that, when executed by a processor, cause the processor to be configured to perform the aforementioned method for synchronizing the state of a cross-system signature card.

[0025] The fifth aspect of this application provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method for synchronizing the status of a signature card across systems.

[0026] The above technical solution receives process update information for the seal card sent by the seal verification system; determines the first operation process to be executed when the status of the seal card is changed in the seal verification system based on the process update information; adjusts the first status flag corresponding to the first operation process to a first preset flag, and determines the process category to which the first operation process belongs; if the process category is a preset category, adjusts the second status flag and execution date of the second operation process associated with the first operation process according to a preset NAND mechanism; after adjusting the second status flag and execution date of the second operation process, updates the execution date of the first operation process to accurately synchronize the status of the seal card to the seal management system.

[0027] Other features and advantages of the embodiments of this application will be described in detail in the following detailed description section. Attached Figure Description

[0028] The accompanying drawings are provided to further illustrate the embodiments of this application and form part of the specification. They are used together with the following detailed description to explain the embodiments of this application, but do not constitute a limitation on the embodiments of this application. In the drawings:

[0029] Figure 1 The illustration shows a flowchart of a method for synchronizing signature card status across systems according to an embodiment of this application;

[0030] Figure 2 This schematic diagram illustrates a structural block diagram of an apparatus for synchronizing the status of signature cards across systems according to an embodiment of this application;

[0031] Figure 3 The diagram illustrates the internal structure of a computer device according to an embodiment of this application. Detailed Implementation

[0032] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only for illustration and explanation of the embodiments of this application and are not intended to limit the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0033] It should be noted that if the embodiments of this application involve directional indicators (such as up, down, left, right, front, back, etc.), the directional indicators are only used to explain the relative positional relationship and movement of the components in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indicators will also change accordingly.

[0034] Furthermore, if the embodiments of this application involve descriptions such as "first" or "second," these descriptions are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, features defined with "first" or "second" may explicitly or implicitly include at least one of those features. Additionally, the technical solutions of various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. If the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed in this application.

[0035] The acquisition, transmission, storage, use, and processing of data in this application comply with relevant national laws and regulations. Furthermore, it should be noted that existing industry solutions such as software, components, and models may be mentioned in the embodiments of this application. These should be considered exemplary, intended only to illustrate the feasibility of implementing the technical solution of this application, and do not imply that the applicant has already used or necessarily used such solutions.

[0036] Figure 1 A schematic flowchart illustrating a method for synchronizing signature card status across systems according to an embodiment of this application is shown. Figure 1 As shown in one embodiment of this application, a method for synchronizing signature card status across systems is provided, applied to a signature management system, including the following steps:

[0037] Step 102: Receive process update information for the signature card sent by the signature verification system. The process update information is generated when the user with modified permissions changes the status of the signature card in the signature verification system.

[0038] In the signature verification system, users can perform operations such as data collection, modeling, verification, auditing, account closure, and account opening cancellation on signature cards. After a user performs any of the above operations to modify the status of a signature card in the signature verification system, the system can obtain the user's credentials based on the modification request. These credentials include, but are not limited to, the user's employee number and facial image from the company where the signature verification system is located. The system can then use these credentials to determine the user's identity and verify their modification permissions.

[0039] When verifying a user's modification permissions, the system can traverse the employee information database of the company hosting the verification system based on the user's identity information to determine if the user exists in the database. If the user exists, their user permissions can be retrieved from the database. Then, based on these permissions, it can be determined whether the user has the authority to modify the signature card in the verification system. For example, the user's permission level can be determined. If the user's permission level is greater than or equal to a preset permission level, then the user has the authority to modify the signature card in the verification system; if the user's permission level is less than the preset permission level, then the user does not have the authority to modify the signature card in the verification system. The preset permission level can be set according to actual needs. For example, if stricter controls are required for signature card status changes in the verification system, the preset permission level can be set higher; if more lenient controls are required, the preset permission level can be set lower.

[0040] If the user has permission to modify the signature card in the signature verification system, then the user has passed the modification permission verification. In this case, the user's modifications to the signature card's status in the signature verification system are valid, and the signature verification system can send the corresponding process update information to the signature management system. If the user does not have permission to modify the signature card in the signature verification system, then the user has failed the modification permission verification. In this case, the user's modifications to the signature card's status in the signature verification system are invalid, and the signature verification system will not send the corresponding process update information to the signature management system.

[0041] In this way, the seal verification system can send the process update information generated when a user with modified permissions changes the status of the seal card in the seal verification system to the seal management system, ensuring the security of cross-system synchronization of seal card status and improving the reliability and accuracy of cross-system synchronization of seal card status.

[0042] The seal management system is used to uniformly manage the status information of seal cards. When synchronizing seal card status across systems, the seal verification system can send process update information for the seal cards to the seal management system. The seal management system can receive process update information for the seal cards sent by the seal verification system. This process update information is generated when a user with modified permissions changes the seal card status in the seal verification system. The process update information may include data collection process information, modeling process information, review process information, audit failure or success information, account closure information, and account opening cancellation information.

[0043] Step 104: Determine the first operation procedure to be performed when changing the status of the signature card in the signature verification system based on the process update information.

[0044] The seal management system can determine the first operation procedure to be executed when the status of a seal card is changed in the seal verification system based on process update information. For example, if the process update information is collection process information, the first operation procedure is collection operation. Collection operation involves collecting information from the front and back of the seal card. If the process update information is modeling process information, the first operation procedure is modeling operation. Modeling operation involves creating the OCR image information of the seal card. If the process update information is verification process information, the first operation procedure is verification operation. Verification operation refers to verifying the physical seal card uploaded by the branch and the collected information. If the process update information is audit failure or audit success information, the first operation procedure is audit operation. Audit operation refers to verifying whether the physical seal card matches the one used during modeling. If the process update information is account cancellation information, the first operation procedure is account cancellation operation. Account cancellation operation refers to canceling the seal card. If the process update information is account opening cancellation information, the first operation procedure is account opening cancellation operation. The account opening cancellation operation refers to canceling the account opened after the signature card has been opened.

[0045] Step 106: Adjust the first status flag corresponding to the first operation process to the first preset flag, and determine the process category to which the first operation process belongs.

[0046] The seal management system can adjust the first status flag corresponding to the first operation process to a first preset flag, indicating that the seal card has undergone the first operation process in the verification system. For example, the first preset flag can be represented by "Yes" or "1". The seal management system can determine the process category to which the first operation process belongs. The process can include preset categories and non-preset categories.

[0047] Step 108: If the process category is a preset category, adjust the second status flag and execution date of the second operation process associated with the first operation process according to the preset NAND mechanism.

[0048] When the process category is a preset category, the seal management system can adjust the second status flag and execution date of the second operation process associated with the first operation process according to the preset AND / NOT mechanism. The preset categories include seal verification process category, account cancellation process category, and account opening cancellation process category.

[0049] In this embodiment, the preset categories include a seal verification process category, an account cancellation process category, and an account opening cancellation process category. When the process category is a preset category, adjusting the second status flag and execution date of the second operation process associated with the first operation process according to a preset AND-NOT mechanism includes: when the process category is a seal verification process category, adjusting the second status flag and execution date of the second operation process according to a preset AND mechanism; when the process category is an account cancellation process category or an account opening cancellation process category, adjusting the second status flag and execution date of the second operation process according to a preset NOT mechanism.

[0050] The preset categories include seal verification process category, account cancellation process category, and account opening cancellation process category. The operation process of the seal verification process category can include seal collection process, seal verification process, and seal modeling process. When the process category is seal verification process, the seal management system can adjust the second status flag and execution date of the second operation process according to the preset mechanism.

[0051] In this embodiment of the application, when the process category is a seal verification process, adjusting the second status flag and execution date of the second operation process associated with the first operation process according to a preset AND mechanism includes: when the process category is a seal verification process, determining whether the first operation process is a seal verification collection process; when the first operation process is not a seal verification collection process, determining that the second operation process is another seal verification operation process that precedes the first operation process; when the status flag of the other seal verification operation process is negative, adjusting the status flag of the other seal verification operation process to the first preset flag according to the AND mechanism; and adjusting the execution date corresponding to the other seal verification operation processes to the date when the first operation process is executed in the seal verification system according to the AND mechanism.

[0052] When the process category is a seal verification process, the seal management system can determine whether the first operation process is a seal verification and data collection process. If the first operation process is not a seal verification and data collection process, the seal management system can determine that the second operation process is another seal verification operation process that precedes the first operation process.

[0053] If the status flags of other verification procedures are negative, it indicates that the update information corresponding to the first verification procedure has been received first, but the update information corresponding to other verification procedures preceding the first procedure has not yet been received. In this case, the seal management system can adjust the status flags of other verification procedures to the first preset flag according to the established mechanism. This indicates that the seal card has already undergone other verification procedures preceding the first procedure in the verification system before proceeding with the first procedure. The seal management system can also adjust the execution date corresponding to other verification procedures to the date of executing the first procedure in the verification system according to the established mechanism.

[0054] For example, when the seal management system receives the modeling process information, it can determine that the first operation process is the modeling operation process and adjust the flag of the modeling operation process to "yes". It can also determine that the process category to which the first operation process belongs is the seal verification process category, and that the first operation process is not the seal verification collection process. At this time, if the flag of the seal card collection operation process is "no", the "AND" operation can be used to adjust the flag of the collection operation process to "yes", and the "AND" operation can be used to change the date of the collection operation process to the date of executing the modeling operation process in the seal verification system.

[0055] For example, when the seal management system receives the verification process information, it can determine that the first operation process is a verification operation process and adjust the flag of the verification operation process to "yes". It can also determine that the process category to which the first operation process belongs is the seal verification process category, and that the first operation process is not the seal verification collection process. At this time, if the flag of the seal card collection or modeling operation process is "no", the "AND" operation can be used to adjust the flag of the collection or modeling operation process to "yes", and the "AND" operation can be used to change the date of the collection or modeling operation process to the date of the verification operation process executed in the seal verification system.

[0056] In one embodiment, if the first operation process is a seal verification and acquisition process, the seal management system can adjust the execution date of the first operation process to the date when the first operation process is executed in the seal verification system.

[0057] For example, when the seal management system receives the collection process information, it can determine that the first operation process is a collection operation process, adjust the collection operation process flag to "yes", and determine that the process category to which the first operation process belongs is the seal verification process category, and that the first operation process is a seal verification collection process. At this time, the execution date of the first operation process can be adjusted to the date when the collection operation process is executed in the seal verification system.

[0058] The above technical solution, when the process category to which the first operation process belongs is the seal verification process category, adjusts the second status flag and execution date of the second operation process associated with the first operation process based on the process category of the first operation process and whether the first operation process is a seal verification and acquisition process. This enables the information of each seal verification operation process to be received in sequence, improving the accuracy of cross-system synchronization of seal card status.

[0059] When the process category is the account cancellation process category, the seal management system can adjust the second status flag and execution date of the second operation process according to a preset non-mechanism. In this embodiment of the application, when the process category is the account cancellation process category, adjusting the second status flag and execution date of the second operation process according to the preset non-mechanism includes: when the process category is the account cancellation process category, determining that the second operation process is one of the other seal verification operation processes and audit processes that precede the first operation process; and clearing the status flag and execution date of the other seal verification operation processes and audit processes according to the non-mechanism.

[0060] When the process category is account cancellation, the seal management system can determine that the second operation process is one of the other seal verification and audit processes that precede the first operation process. At this time, it may not have received the corresponding process update information for the other seal verification and audit processes that preceded the account cancellation operation, or it may have received the corresponding process update information. The seal management system can clear the status flags and execution dates of the other seal verification and audit processes according to a non-mechanical method, indicating that the seal card has been cancelled in the seal verification system, and the flags and dates corresponding to the seal verification and audit processes in the seal management system are invalidated.

[0061] The above technical solution, when the process category to which the first operation process belongs is the account cancellation process category, adjusts the second status flag and execution date of the second operation process according to the preset non-mechanism. It can quickly update the signature card status when receiving information from the account cancellation operation process, and can also ensure the accuracy of the signature card status when receiving update information from other processes in the future, thereby improving the accuracy of cross-system synchronization of signature card status.

[0062] When the process category is an account opening / revocation process, the seal management system can adjust the second status flag and execution date of the second operation process according to a preset non-mechanism. Specifically, in this embodiment, when the process category is an account opening / revocation process, adjusting the second status flag and execution date of the second operation process according to a preset non-mechanism includes: determining that the second operation process is one of the other seal verification operation processes preceding the first operation process; adjusting the status flag of the other seal verification operation processes to the second preset flag according to the non-mechanism, and clearing the execution date of the other seal verification operation processes.

[0063] When the process category is "account opening and cancellation process," the seal management system can determine that the second operation process is one of the other seal verification operation processes that precedes the first operation process. At this time, it is possible that the process update information corresponding to the other seal verification operation processes that precede the account opening and cancellation operation has not yet been received, or it is possible that the process update information corresponding to the other seal verification operation processes that precede the account opening and cancellation operation has already been received.

[0064] At this point, the seal management system can adjust the status flags of other seal verification processes to the second preset flag based on the non-mechanical mechanism, and clear the execution dates of other seal verification processes. Adjusting the status flags of other seal verification processes to the second preset flag indicates that the seal card has not undergone other seal verification processes in the system. For example, the second preset flag can be represented by "No" or "0".

[0065] The above technical solution, when the process category to which the first operation process belongs is the account opening cancellation process category, adjusts the second status flag and execution date of the second operation process according to the preset non-mechanism. It can quickly update the signature card status when receiving information from the account opening cancellation operation process, and can also ensure the accuracy of the signature card status when receiving update information from other processes in the future, thereby improving the accuracy of cross-system synchronization of signature card status.

[0066] Step 110: After adjusting the second status flag and execution date of the second operation process, update the execution date of the first operation process to synchronize the status of the seal card to the seal management system.

[0067] After adjusting the second status flag and execution date of the second operation process, the seal management system can update the execution date of the first operation process to synchronize the seal card status to the seal management system. Specifically, it can determine whether there are any anomalies in the process change information, and then update the execution date of the first operation process based on the determination result of whether there are any anomalies in the process change information.

[0068] Specifically, in this embodiment, after adjusting the second status flag and execution date of the second operation process, updating the execution date of the first operation process to synchronize the status of the seal card to the seal management system includes: after adjusting the second status flag and execution date of the second operation process, determining whether there is an anomaly in the process update information; if there is an anomaly in the process update information, updating the execution date corresponding to the first operation process to the date on which the seal management system receives the process update information; if there is no anomaly in the process update information, updating the execution date corresponding to the first operation process to the date on which the user executes the first operation process in the seal verification system.

[0069] After adjusting the second status flag and execution date of the second operation process, it is determined whether there are any anomalies in the process update information. Specifically, it is checked whether the process update information has a value and whether the format of the process update information is correct. If the process update information has no value or the format is incorrect, it can be determined that there is an anomaly in the process update information.

[0070] If there are any anomalies in the process update information, the seal management system can update the execution date corresponding to the first operation process to the date the seal management system received the process update information, i.e., the current date. If there are no anomalies in the process update information, the seal management system can update the execution date corresponding to the first operation process to the date the user executed the first operation process in the seal verification system, i.e., the maintenance date.

[0071] The above technical solution, after adjusting the second status flag and execution date of the second operation process, updates the execution date of the first operation process, which helps to track the time of the synchronized signature card status, facilitates the update management of signature card status, and improves the accuracy of cross-system synchronized signature card status.

[0072] In this embodiment of the application, the method further includes: if the process category is not a preset category, determining that the first operation process is an audit operation process, and determining whether there is an associated card corresponding to the seal card; if there is a corresponding associated card, adjusting the status flag corresponding to the audit operation process of the associated card to the status corresponding to the execution result of the audit operation process; after adjusting the status flag corresponding to the audit operation process of the associated card, updating the execution date of the audit operation process to synchronize the status of the seal card to the seal management system.

[0073] If the process category is not a preset category, the seal management system can determine that the first operation process is an audit operation process and check whether there is an associated card corresponding to the seal card. An associated card can also refer to a sub-card. If a corresponding associated card exists, the seal management system can adjust the status flag of the audit operation process corresponding to the associated card to the status corresponding to the execution result of the audit operation process. That is, the result obtained after executing the audit operation process on the seal card, for example, if the execution result of the audit operation process includes failure and success, is synchronously updated to the audit operation process of the associated card.

[0074] After adjusting the status flags corresponding to the audit operation process of the associated card, the seal management system can update the execution date of the audit operation process to synchronize the status of the seal card to the seal management system. Specifically, it can determine whether there are any anomalies in the process change information. If there are anomalies, the execution date corresponding to the audit operation process can be updated to the date the seal management system receives the process update information. If there are no anomalies, the execution date corresponding to the audit operation process can be updated to the date the user executes the audit operation process in the seal verification system.

[0075] For example, if the audit operation process for a signature card in the signature verification system is successful, and there is an associated card corresponding to the signature card, the status of the audit operation process for the associated card can also be changed to "audit passed." If there is no associated card corresponding to the signature card, i.e., only the signature card exists, the status of the signature card's audit operation process is adjusted to "successful." If the audit process update information has no value or is in an incorrect format, the date corresponding to the audit operation process can be modified to the current date, i.e., the date the audit process update information was received; otherwise, the date corresponding to the audit operation process can be modified to the date the user executed the audit operation process in the signature verification system.

[0076] For example, if the audit operation on the signature card in the signature verification system fails, and there is an associated card corresponding to the signature card, the audit operation status of the associated card can be simultaneously changed to "audit passed." If there is no associated card corresponding to the signature card, i.e., only the signature card exists, the audit operation status of the signature card is changed to "failed." If the audit process update information has no value or is in an incorrect format, the date corresponding to the audit operation can be modified to the current date, i.e., the date the audit process update information was received; otherwise, the date corresponding to the audit operation can be modified to the date the user executed the audit operation in the signature verification system.

[0077] The above technical solution receives process update information for the seal card sent by the seal verification system; determines the first operation process to be executed when the status of the seal card is changed in the seal verification system based on the process update information; adjusts the first status flag corresponding to the first operation process to a first preset flag, and determines the process category to which the first operation process belongs; if the process category is a preset category, adjusts the second status flag and execution date of the second operation process associated with the first operation process according to a preset NAND mechanism; after adjusting the second status flag and execution date of the second operation process, updates the execution date of the first operation process to accurately synchronize the status of the seal card to the seal management system.

[0078] Figure 1 This is a flowchart illustrating a method for synchronizing signature card status across systems in one embodiment. It should be understood that, although... Figure 1 The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figure 1At least some of the steps in the process may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.

[0079] In one embodiment, such as Figure 2 As shown, a device 200 for synchronizing signature card status across systems is provided, including an information receiving module 202, an operation flow determination module 204, a flow category determination module 206, an information adjustment module 208, and a status synchronization module 210, wherein:

[0080] The information receiving module 202 is used to receive process update information for the seal card sent by the seal verification system. The process update information is generated when the user with modified permission verification changes the status of the seal card in the seal verification system.

[0081] The operation process determination module 204 is used to determine the first operation process to be executed when the status of the seal card is changed in the seal verification system based on the process update information.

[0082] The process category determination module 206 is used to adjust the first status flag corresponding to the first operation process to the first preset flag, and determine the process category to which the first operation process belongs.

[0083] The information adjustment module 208 is used to adjust the second status flag and execution date of the second operation process associated with the first operation process according to a preset NAND mechanism when the process category is a preset category.

[0084] The status synchronization module 210 is used to update the execution date of the first operation process after adjusting the second status flag and execution date of the second operation process, so as to synchronize the status of the seal card to the seal management system.

[0085] In the signature verification system, users can perform operations such as data collection, modeling, verification, auditing, account closure, and account opening cancellation on signature cards. After a user performs any of the above operations to modify the status of a signature card in the signature verification system, the system can obtain the user's credentials based on the modification request. These credentials include, but are not limited to, the user's employee number and facial image from the company where the signature verification system is located. The system can then use these credentials to determine the user's identity and verify their modification permissions.

[0086] When verifying a user's modification permissions, the system can traverse the employee information database of the company hosting the verification system based on the user's identity information to determine if the user exists in the database. If the user exists, their user permissions can be retrieved from the database. Then, based on these permissions, it can be determined whether the user has the authority to modify the signature card in the verification system. For example, the user's permission level can be determined. If the user's permission level is greater than or equal to a preset permission level, then the user has the authority to modify the signature card in the verification system; if the user's permission level is less than the preset permission level, then the user does not have the authority to modify the signature card in the verification system. The preset permission level can be set according to actual needs. For example, if stricter controls are required for signature card status changes in the verification system, the preset permission level can be set higher; if more lenient controls are required, the preset permission level can be set lower.

[0087] If the user has permission to modify the signature card in the signature verification system, then the user has passed the modification permission verification. In this case, the user's modifications to the signature card's status in the signature verification system are valid, and the signature verification system can send the corresponding process update information to the signature management system. If the user does not have permission to modify the signature card in the signature verification system, then the user has failed the modification permission verification. In this case, the user's modifications to the signature card's status in the signature verification system are invalid, and the signature verification system will not send the corresponding process update information to the signature management system.

[0088] In this way, the seal verification system can send the process update information generated when a user who has been verified by modifying permissions changes the status of the seal card in the seal verification system to the information receiving module 202, ensuring the security of cross-system synchronization of seal card status and improving the reliability and accuracy of cross-system synchronization of seal card status.

[0089] The information receiving module 202 is used for unified management of the signature card status information. When synchronizing signature card status across systems, the signature verification system can send process update information for the signature card to the information receiving module 202. The information receiving module 202 can receive the process update information for the signature card sent by the signature verification system. This process update information is generated when a user with modified permissions changes the signature card status in the signature verification system. The process update information may include data collection process information, modeling process information, review process information, audit failure or success information, account closure information, and account opening cancellation information.

[0090] The operation process determination module 204 can determine the first operation process to be executed when the status of the seal card is changed in the seal verification system based on the process update information. For example, if the process update information is collection process information, the first operation process is a collection operation. This collection operation involves collecting information from the front and back of the seal card. If the process update information is modeling process information, the first operation process is a modeling operation. This modeling operation involves creating the OCR image information of the seal card. If the process update information is a verification process information, the first operation process is a verification operation. This verification operation refers to verifying the physical seal card uploaded by the branch and the collected information. If the process update information is an audit failure or audit success information, the first operation process is an audit operation. This audit operation involves verifying whether the physical seal card matches the one used during modeling. If the process update information is an account cancellation information, the first operation process is an account cancellation operation. This account cancellation operation involves cancelling the seal card. If the process update information is an account opening cancellation information, the first operation process is an account opening cancellation operation. The account opening cancellation operation refers to canceling the account opened after the signature card has been opened.

[0091] The process category determination module 206 can adjust the first status flag corresponding to the first operation process to a first preset flag, indicating that the seal card has undergone the first operation process in the seal verification system. For example, the first preset flag can be represented by "yes" or "1". The process category determination module 206 can determine the process category to which the first operation process belongs. The process can include preset categories and non-preset categories.

[0092] When the process category is a preset category, the information adjustment module 208 can adjust the second status flag and execution date of the second operation process associated with the first operation process according to a preset NAND mechanism. The preset categories include the seal verification process category, the account cancellation process category, and the account opening cancellation process category.

[0093] In this embodiment, the preset categories include a seal verification process category, an account cancellation process category, and an account opening cancellation process category. The information adjustment module is used to adjust the second status flag and execution date of the second operation process associated with the first operation process according to a preset AND-NOT mechanism when the process category is a preset category. This includes: adjusting the second status flag and execution date of the second operation process according to a preset AND mechanism when the process category is a seal verification process category; and adjusting the second status flag and execution date of the second operation process according to a preset NOT mechanism when the process category is an account cancellation process category or an account opening cancellation process category.

[0094] The preset categories include seal verification process category, account cancellation process category, and account opening cancellation process category. The operation process of the seal verification process category may include seal collection process, seal verification process, and seal modeling process. When the process category is seal verification process category, the information adjustment module 208 can adjust the second status flag and execution date of the second operation process according to the preset mechanism.

[0095] In this embodiment, the information adjustment module is used to adjust the second status flag and execution date of the second operation process associated with the first operation process according to a preset AND mechanism when the process category is a seal verification process category. This includes: determining whether the first operation process is a seal verification collection process when the process category is a seal verification process category; determining that the second operation process is another seal verification operation process that precedes the first operation process when the first operation process is not a seal verification collection process; adjusting the status flag of the other seal verification operation process to the first preset flag according to the AND mechanism when the status flag of the other seal verification operation process is negative; and adjusting the execution date corresponding to the other seal verification operation process to the date when the first operation process is executed in the seal verification system according to the AND mechanism.

[0096] If the process category is a seal verification process, the information adjustment module 208 can determine whether the first operation process is a seal verification and collection process. If the first operation process is not a seal verification and collection process, the information adjustment module 208 can determine that the second operation process is another seal verification operation process that precedes the first operation process.

[0097] If the status flags of other verification procedures are negative, it indicates that the update information corresponding to the first verification procedure has been received first, but the update information corresponding to other verification procedures preceding the first procedure has not yet been received. In this case, the information adjustment module 208 can adjust the status flags of other verification procedures to the first preset flag according to the AND mechanism, indicating that the seal card has already undergone other verification procedures preceding the first procedure in the verification system before proceeding with the first procedure. The information adjustment module 208 can also adjust the execution date corresponding to other verification procedures to the date of execution of the first procedure in the verification system according to the AND mechanism.

[0098] For example, when the information adjustment module 208 receives the modeling process information, it can determine that the first operation process is a modeling operation process and adjust the flag of the modeling operation process to "yes". It can also determine that the process category to which the first operation process belongs is the seal verification process category and that the first operation process is not the seal verification collection process. At this time, if the flag of the seal card collection operation process is "no", the "AND" operation can be used to adjust the flag of the collection operation process to "yes" and the "AND" operation can be used to change the date of the collection operation process to the date of executing the modeling operation process in the seal verification system.

[0099] For example, when the information adjustment module 208 receives the review process information, it can determine that the first operation process is a review operation process and adjust the flag of the review operation process to "yes". It can also determine that the process category to which the first operation process belongs is the seal verification process category and that the first operation process is not the seal verification collection process. At this time, if the flag of the seal card collection or modeling operation process is "no", the "AND" operation can be used to adjust the flag of the collection or modeling operation process to "yes" and the "AND" operation can be used to change the date of the collection or modeling operation process to the date of the review operation process executed in the seal verification system.

[0100] In one embodiment, when the first operation process is a seal verification and acquisition process, the information adjustment module 208 can adjust the execution date of the first operation process to the date when the first operation process is executed in the seal verification system.

[0101] For example, when the information adjustment module 208 receives the collection process information, it can determine that the first operation process is a collection operation process, adjust the flag of the collection operation process to "yes", and determine that the process category to which the first operation process belongs is the seal verification process category, and that the first operation process is a seal verification collection process. At this time, the execution date of the first operation process can be adjusted to the date when the collection operation process is executed in the seal verification system.

[0102] The above technical solution, when the process category to which the first operation process belongs is the seal verification process category, adjusts the second status flag and execution date of the second operation process associated with the first operation process based on the process category of the first operation process and whether the first operation process is a seal verification and acquisition process. This enables the information of each seal verification operation process to be received in sequence, improving the accuracy of cross-system synchronization of seal card status.

[0103] When the process category is the account cancellation process category, the information adjustment module 208 can adjust the second status flag and execution date of the second operation process according to a preset non-mechanism. In this embodiment, the information adjustment module is used to adjust the second status flag and execution date of the second operation process according to a preset non-mechanism when the process category is the account cancellation process category, including: determining that the second operation process is one of the other verification operation processes and audit processes that precede the first operation process; and clearing the status flag and execution date of the other verification operation processes and audit processes according to a non-mechanism.

[0104] When the process category is account cancellation, the information adjustment module 208 can determine that the second operation process is one of the other seal verification operation processes and audit processes that precede the first operation process. At this time, the process update information corresponding to the other seal verification operation processes and audit processes that precede the account cancellation operation may not have been received yet, or it may have been received. The information adjustment module 208 can clear the status flags and execution dates of the other seal verification operation processes and audit processes according to a non-mechanism, indicating that the seal card has been cancelled in the seal verification system, and the flags and dates corresponding to the seal verification operation processes and audit processes in the information adjustment module 208 are invalidated.

[0105] The above technical solution, when the process category to which the first operation process belongs is the account cancellation process category, adjusts the second status flag and execution date of the second operation process according to the preset non-mechanism. It can quickly update the signature card status when receiving information from the account cancellation operation process, and can also ensure the accuracy of the signature card status when receiving update information from other processes in the future, thereby improving the accuracy of cross-system synchronization of signature card status.

[0106] When the process category is an account opening / cancellation process, the information adjustment module 208 can adjust the second status flag and execution date of the second operation process according to a preset non-mechanism. Specifically, in this embodiment, the information adjustment module is used to adjust the second status flag and execution date of the second operation process according to a preset non-mechanism when the process category is an account opening / cancellation process. This includes: determining that the second operation process is another verification operation process that precedes the first operation process; adjusting the status flag of the other verification operation process to the second preset flag according to the non-mechanism, and clearing the execution date of the other verification operation process.

[0107] When the process category is account opening cancellation process, the information adjustment module 208 can determine that the second operation process is another seal verification operation process that precedes the first operation process. At this time, it is possible that the process update information corresponding to the other seal verification operation process that precedes the account opening cancellation operation has not yet been received, or it is possible that the process update information corresponding to the other seal verification operation process that precedes the account opening cancellation operation has already been received.

[0108] At this time, the information adjustment module 208 can adjust the status flags of other verification operation processes to the second preset flag according to the non-mechanism, and clear the execution dates of other verification operation processes. Adjusting the status flags of other verification operation processes to the second preset flag indicates that the seal card has not undergone other verification operation processes in the verification system. For example, the second preset flag can be represented by "No" or "0".

[0109] The above technical solution, when the process category to which the first operation process belongs is the account opening cancellation process category, adjusts the second status flag and execution date of the second operation process according to the preset non-mechanism. It can quickly update the signature card status when receiving information from the account opening cancellation operation process, and can also ensure the accuracy of the signature card status when receiving update information from other processes in the future, thereby improving the accuracy of cross-system synchronization of signature card status.

[0110] After adjusting the second status flag and execution date of the second operation process, the status synchronization module 210 can update the execution date of the first operation process to synchronize the status of the seal card to the seal management system. Specifically, it can determine whether there is any abnormality in the process change information, and then update the execution date of the first operation process based on the determination result of whether there is any abnormality in the process change information.

[0111] Specifically, in this embodiment, the status synchronization module is used to update the execution date of the first operation process after adjusting the second status flag and execution date of the second operation process, so as to synchronize the status of the seal card to the seal management system. This includes: after adjusting the second status flag and execution date of the second operation process, determining whether there is an anomaly in the process update information; if there is an anomaly in the process update information, updating the execution date corresponding to the first operation process to the date on which the seal management system receives the process update information; if there is no anomaly in the process update information, updating the execution date corresponding to the first operation process to the date on which the user executes the first operation process in the seal verification system.

[0112] After adjusting the second status flag and execution date of the second operation process, it is determined whether there are any anomalies in the process update information. Specifically, it is checked whether the process update information has a value and whether the format of the process update information is correct. If the process update information has no value or the format is incorrect, it can be determined that there is an anomaly in the process update information.

[0113] If there is an anomaly in the process update information, the status synchronization module 210 can update the execution date corresponding to the first operation process to the date the seal management system received the process update information, i.e., the current date. If there is no anomaly in the process update information, the status synchronization module 210 can update the execution date corresponding to the first operation process to the date the user executed the first operation process in the seal verification system, i.e., the maintenance date.

[0114] The above technical solution, after adjusting the second status flag and execution date of the second operation process, updates the execution date of the first operation process, which helps to track the time of the synchronized signature card status, facilitates the update management of signature card status, and improves the accuracy of cross-system synchronized signature card status.

[0115] In this embodiment of the application, the information adjustment module 208 is further configured to: determine that the first operation process is an audit operation process when the process category is not a preset category, and determine whether there is an associated card corresponding to the seal card; if there is a corresponding associated card, adjust the status flag corresponding to the audit operation process of the associated card to the status corresponding to the execution result of the audit operation process; after adjusting the status flag corresponding to the audit operation process of the associated card, update the execution date of the audit operation process to synchronize the status of the seal card to the seal management system.

[0116] If the process category is not a preset category, the status synchronization module 210 can determine that the first operation process is an audit operation process and determine whether there is an associated card corresponding to the signature card. The associated card can also refer to a sub-card. If a corresponding associated card exists, the status synchronization module 210 can adjust the status flag corresponding to the audit operation process of the associated card to the status corresponding to the execution result of the audit operation process. That is, the result obtained after executing the audit operation process on the signature card, for example, if the execution result of the audit operation process includes failure and success, is synchronously updated to the audit operation process of the associated card.

[0117] After adjusting the status flags corresponding to the audit operation process of the associated card, the status synchronization module 210 can update the execution date of the audit operation process to synchronize the status of the seal card to the seal management system. Specifically, it can determine whether there are any anomalies in the process change information. If there are anomalies, the execution date corresponding to the audit operation process can be updated to the date on which the seal management system receives the process update information. If there are no anomalies, the execution date corresponding to the audit operation process can be updated to the date on which the user executes the audit operation process in the seal verification system.

[0118] For example, if the audit operation process for a signature card in the signature verification system is successful, and there is an associated card corresponding to the signature card, the status of the audit operation process for the associated card can also be changed to "audit passed." If there is no associated card corresponding to the signature card, i.e., only the signature card exists, the status of the signature card's audit operation process is adjusted to "successful." If the audit process update information has no value or is in an incorrect format, the date corresponding to the audit operation process can be modified to the current date, i.e., the date the audit process update information was received; otherwise, the date corresponding to the audit operation process can be modified to the date the user executed the audit operation process in the signature verification system.

[0119] For example, if the audit operation on the signature card in the signature verification system fails, and there is an associated card corresponding to the signature card, the audit operation status of the associated card can be simultaneously changed to "audit passed." If there is no associated card corresponding to the signature card, i.e., only the signature card exists, the audit operation status of the signature card is changed to "failed." If the audit process update information has no value or is in an incorrect format, the date corresponding to the audit operation can be modified to the current date, i.e., the date the audit process update information was received; otherwise, the date corresponding to the audit operation can be modified to the date the user executed the audit operation in the signature verification system.

[0120] The device 200 for synchronizing the status of signature cards across systems includes a processor and a memory. The aforementioned information receiving module 202, operation process determination module 204, process category determination module 206, information adjustment module 208, and status synchronization module 210 are all stored in the memory as program units. The processor executes the aforementioned program modules stored in the memory to implement the corresponding functions.

[0121] The processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured, and methods for synchronizing the status of signature cards across systems can be implemented by adjusting kernel parameters.

[0122] The memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0123] This application provides a storage medium storing a program that, when executed by a processor, implements the method for synchronizing the state of a signature card across systems.

[0124] This application provides a processor for running a program, wherein the program executes the method described above for synchronizing the status of a signature card across systems.

[0125] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 3As shown. The computer device includes a processor A01, a network interface A02, memory (not shown), and a database (not shown) connected via a system bus. The processor A01 provides computing and control capabilities. The memory includes internal memory A03 and a non-volatile storage medium A04. The non-volatile storage medium A04 stores an operating system B01, a computer program B02, and a database (not shown). The internal memory A03 provides an environment for the operation of the operating system B01 and the computer program B02 stored in the non-volatile storage medium A04. The database stores data such as the status of the signature card. The network interface A02 communicates with external terminals via a network connection. When the computer program B02 is executed by the processor A01, it implements a method for synchronizing the signature card status across systems.

[0126] Those skilled in the art will understand that Figure 3 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0127] This application provides a device including a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, it performs the following steps: receiving process update information for a signature card sent by a signature verification system, wherein the process update information is generated when a user with modified permissions changes the status of the signature card in the signature verification system; determining a first operation process executed when the signature card status is changed in the signature verification system based on the process update information; adjusting a first status flag corresponding to the first operation process to a first preset flag, and determining the process category to which the first operation process belongs; if the process category is a preset category, adjusting a second status flag and execution date of a second operation process associated with the first operation process according to a preset NAND mechanism; and after adjusting the second status flag and execution date of the second operation process, updating the execution date of the first operation process to synchronize the signature card status to the signature management system.

[0128] In one embodiment, the preset categories include a signature verification process category, an account cancellation process category, and an account opening cancellation process category. When the process category is a preset category, adjusting the second status flag and execution date of the second operation process associated with the first operation process according to a preset AND-NOT mechanism includes: when the process category is a signature verification process category, adjusting the second status flag and execution date of the second operation process according to a preset AND mechanism; when the process category is an account cancellation process category or an account opening cancellation process category, adjusting the second status flag and execution date of the second operation process according to a preset NOT mechanism.

[0129] In one embodiment, when the process category is a seal verification process, adjusting the second status flag and execution date of the second operation process associated with the first operation process according to a preset AND mechanism includes: when the process category is a seal verification process, determining whether the first operation process is a seal verification collection process; if the first operation process is not a seal verification collection process, determining that the second operation process is another seal verification operation process preceding the first operation process; if the status flag of the other seal verification operation process is negative, adjusting the status flag of the other seal verification operation process to the first preset flag according to the AND mechanism; and adjusting the execution date corresponding to the other seal verification operation processes to the date of executing the first operation process in the seal verification system according to the AND mechanism.

[0130] In one embodiment, when the process category is the account cancellation process category, adjusting the second status flag and execution date of the second operation process according to a preset non-mechanism includes: when the process category is the account cancellation process category, determining that the second operation process is one of the other seal verification operation processes and audit processes that precede the first operation process; and clearing the status flag and execution date of the other seal verification operation processes and audit processes according to a non-mechanism.

[0131] In one embodiment, when the process category is the account opening and cancellation process category, adjusting the second status flag and execution date of the second operation process according to the preset non-mechanism includes: when the process category is the account opening and cancellation process category, determining that the second operation process is another seal verification operation process that precedes the first operation process; adjusting the status flag of the other seal verification operation process to the second preset flag according to the non-mechanism, and clearing the execution date of the other seal verification operation process.

[0132] In one embodiment, updating the execution date of the first operation process after adjusting the second status flag and execution date of the second operation process to synchronize the status of the seal card to the seal management system includes: after adjusting the second status flag and execution date of the second operation process, determining whether there is an anomaly in the process update information; if there is an anomaly in the process update information, updating the execution date corresponding to the first operation process to the date on which the seal management system receives the process update information; if there is no anomaly in the process update information, updating the execution date corresponding to the first operation process to the date on which the user executes the first operation process in the seal verification system.

[0133] In one embodiment, the method further includes: if the process category is not a preset category, determining that the first operation process is an audit operation process, and determining whether there is an associated card corresponding to the seal card; if there is a corresponding associated card, adjusting the status flag corresponding to the audit operation process of the associated card to the status corresponding to the execution result of the audit operation process; after adjusting the status flag corresponding to the audit operation process of the associated card, updating the execution date of the audit operation process to synchronize the status of the seal card to the seal management system.

[0134] This application also provides a computer program product that, when executed on a data processing device, is adapted to perform method steps for initializing the state of a cross-system synchronized signature card.

[0135] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0136] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0137] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0138] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0139] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0140] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0141] Computer-readable media include both permanent and non-permanent, removable and non-removable media, which can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0142] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0143] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for synchronizing signature card status across systems, characterized in that, Applied to a seal management system, the method includes: Receive process update information for the signature card sent by the signature verification system, wherein the process update information is generated when the user with modified permissions changes the status of the signature card in the signature verification system; Based on the process update information, determine the first operation process to be executed when the status of the signature card is changed in the signature verification system; The first status flag corresponding to the first operation process is adjusted to the first preset flag, and the process category to which the first operation process belongs is determined. When the process category is a preset category, the second status flag and execution date of the second operation process associated with the first operation process are adjusted according to a preset NAND mechanism; After adjusting the second status flag and execution date of the second operation process, the execution date of the first operation process is updated to synchronize the status of the seal card to the seal management system.

2. The method for synchronizing signature card status across systems according to claim 1, characterized in that, The preset categories include seal verification process category, account cancellation process category, and account opening cancellation process category. When the process category is a preset category, adjusting the second status flag and execution date of the second operation process associated with the first operation process according to a preset NAND mechanism includes: When the process category is the seal verification process category, the second status flag and execution date of the second operation process are adjusted according to a preset mechanism; When the process category is the account cancellation process category or the account opening cancellation process category, the second status flag and execution date of the second operation process are adjusted according to a preset non-mechanism.

3. The method for synchronizing signature card status across systems according to claim 2, characterized in that, When the process category is the seal verification process category, adjusting the second status flag and execution date of the second operation process associated with the first operation process according to a preset mechanism includes: If the process category is the seal verification process category, determine whether the first operation process is a seal verification and acquisition process. If the first operation process is not the signature verification and collection process, the second operation process is determined to be another signature verification operation process that precedes the first operation process. If the status flag of the other verification operation process is negative, the status flag of the other verification operation process is adjusted to the first preset flag according to the AND mechanism. According to the aforementioned mechanism, the execution date corresponding to the other verification operation process is adjusted to the date on which the first operation process is executed in the verification system.

4. The method for synchronizing signature card status across systems according to claim 2, characterized in that, When the process category is the account cancellation process category, adjusting the second status flag and execution date of the second operation process according to a preset non-mechanism includes: If the process category is the account cancellation process category, the second operation process is determined to be other seal verification operation processes and audit processes that precede the first operation process; The status flags and execution dates of the other verification and audit procedures are cleared according to the non-mechanism.

5. The method for synchronizing signature card status across systems according to claim 2, characterized in that, When the process category is the account opening cancellation process category, adjusting the second status flag and execution date of the second operation process according to a preset non-mechanism includes: If the process category is the account opening cancellation process category, the second operation process is determined to be another seal verification operation process that precedes the first operation process. According to the non-mechanism, the status flag of the other seal verification operation process is adjusted to the second preset flag, and the execution date of the other seal verification operation process is cleared.

6. The method for synchronizing signature card status across systems according to claim 1, characterized in that, The step of updating the execution date of the first operation process after adjusting the second status flag and execution date of the second operation process to synchronize the status of the signature card to the signature management system includes: After adjusting the second status flag and execution date of the second operation process, determine whether there is any abnormality in the process update information; If there is an anomaly in the process update information, the execution date corresponding to the first operation process will be updated to the date on which the seal management system receives the process update information; If there are no abnormalities in the process update information, the execution date corresponding to the first operation process will be updated to the date on which the user performed the first operation process in the seal verification system.

7. The method for synchronizing signature card status across systems according to claim 1, characterized in that, The method further includes: If the process category is not the preset category, the first operation process is determined to be an audit operation process, and it is determined whether there is an associated card corresponding to the seal card. If a corresponding associated card exists, the status flag corresponding to the audit operation process of the associated card will be adjusted to the status corresponding to the execution result of the audit operation process. After adjusting the status flag corresponding to the audit operation process of the associated card, the execution date of the audit operation process is updated to synchronize the status of the seal card to the seal management system.

8. A device for synchronizing the status of signature cards across systems, characterized in that, The device includes: The information receiving module is used to receive process update information for the seal card sent by the seal verification system. The process update information is generated when the user with modified permissions changes the status of the seal card in the seal verification system. The operation process determination module is used to determine the first operation process to be executed when the status of the seal card is changed in the seal verification system, based on the process update information. The process category determination module is used to adjust the first status flag corresponding to the first operation process to a first preset flag, and determine the process category to which the first operation process belongs. The information adjustment module is used to adjust the second status flag and execution date of the second operation process associated with the first operation process according to a preset NAND mechanism when the process category is a preset category. The status synchronization module, after adjusting the second status flag and execution date of the second operation process, updates the execution date of the first operation process to synchronize the status of the seal card to the seal management system.

9. A processor, characterized in that, Configured to perform a method for synchronizing signature card status across systems as described in any one of claims 1 to 7.

10. A machine-readable storage medium storing instructions thereon, characterized in that, When executed by a processor, this instruction causes the processor to be configured to perform a method for synchronizing the status of signature cards across systems according to any one of claims 1 to 7.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method for synchronizing the status of signature cards across systems according to any one of claims 1 to 7.

Images