Protocol account checking method and device, computer equipment and storage medium

Abstract

The invention relates to a protocol account checking method and device, computer equipment and a storage medium. The method comprises the following steps: determining a protocol to be generated based on service data, a service strategy and a protocol scene rule, determining an actually generated protocol according to a protocol snapshot, determining a protocol number reconciliation detail according to the protocol to be generated and the actually generated protocol, and determining a first protocol difference detail according to a protocol actual call record and the protocol number reconciliation detail; determining protocol actual generation parameters according to the protocol number reconciliation details and the protocol snapshots, determining protocol required generation parameters according to the protocol calling parameters, the protocol template rules and the protocol number reconciliation details, and determining second protocol difference details according to the protocol actual generation parameters and the protocol required generation parameters; analyzing the protocol file to obtain signature content, and checking the signature content with protocol seal configuration content in the protocol template to obtain third protocol difference details; and generating a protocol reconciliation result according to the protocol difference details. The protocol review efficiency can be improved, and the effectiveness of the protocol can be ensured.

Description

Technical Field

[0001] This application relates to the field of Internet finance technology, and particularly to a protocol reconciliation method, apparatus, computer device, and storage medium. Background Art

[0002] With the development of information technology, more and more business processes have been computerized and automated. In these processes, the protocol, as a formal document agreed upon between two or more parties, its correctness is crucial.

[0003] Most of the existing protocol review methods rely on manual review or are limited to simple matching of protocol texts, and cannot comprehensively cover potential problems in multiple links such as protocol generation and protocol execution. In addition, with the increasingly wide application of digital signature technology, how to verify the integrity and accuracy of signatures has also become a new challenge. Obviously, the traditional manual review method is not only time-consuming and laborious, but also error-prone. Especially in the credit industry with a large number of protocols, manual review is no longer practical. Therefore, there is an urgent need for an algorithm that can automatically detect the correctness of protocols to improve the efficiency of protocol review and ensure the effectiveness of protocols. Summary of the Invention

[0004] In view of the above deficiencies or drawbacks, this application provides a protocol reconciliation method, apparatus, computer device, and storage medium. The embodiments of this application can improve the efficiency of protocol review and ensure the effectiveness of protocols.

[0005] According to a first aspect of this application, a protocol reconciliation method is provided. In some embodiments, the method includes:

[0006] Determine the protocol that should be generated for the target business operation based on the business data, business strategy, and protocol scenario rules of the target business operation. Determine the actually generated protocol of the target business operation according to the protocol snapshot of the target business operation. Determine the protocol quantity reconciliation details based on the protocol that should be generated and the actually generated protocol. Determine the first protocol difference details based on the protocol actual call record and the protocol quantity reconciliation details of the target business operation;

[0007] Determine the protocol actually generated parameters based on the protocol quantity reconciliation details and the protocol snapshot. Determine the protocol parameters that should be generated based on the protocol call parameters, protocol template rules, and protocol quantity reconciliation details of the target business operation. Determine the second protocol difference details based on the protocol actually generated parameters and the protocol parameters that should be generated;

[0008] Parse the protocol file generated by the target business operation to obtain the signature content in the protocol file, and compare the signature content with the protocol signature configuration content in the protocol template to obtain the third protocol difference details;

[0009] Generate a protocol reconciliation result based on the first protocol difference details, the second protocol difference details, and the third protocol difference details.

[0010] In some embodiments, determining the protocol to be generated for a target business operation based on the business data, business strategy, and protocol scenario rules of the target business operation includes:

[0011] Associating the business data and business strategy of the target business operation to obtain a protocol call record;

[0012] Associating the protocol call record and the protocol scenario rules to obtain the protocol to be generated for the target business operation.

[0013] In some embodiments, determining the first protocol difference details based on the protocol actual call record and the protocol quantity reconciliation details of the target business operation includes:

[0014] Filtering out abnormal protocols in the protocol quantity reconciliation details to obtain protocol abnormality details;

[0015] Determining the protocol call difference based on the protocol actual call record and the protocol call record of the target business operation;

[0016] Determining the first protocol difference details based on the protocol call difference and the protocol abnormality details.

[0017] In some embodiments, determining the protocol actual generation parameters based on the protocol quantity reconciliation details and the protocol snapshot includes:

[0018] Filtering out non-missing protocols in the protocol quantity reconciliation details to obtain protocol non-missing details;

[0019] Extracting protocol parameters from the protocol snapshot;

[0020] Determining the protocol actual generation parameters based on the protocol non-missing details and the protocol parameters in the protocol snapshot.

[0021] In some embodiments, determining the protocol to be generated parameters based on the protocol call parameters, protocol template rules, and protocol quantity reconciliation details of the target business operation includes:

[0022] Obtaining the protocol non-missing details obtained based on the protocol quantity reconciliation details;

[0023] Determining the protocol to be generated parameters based on the protocol call parameters, protocol template rules, and protocol non-missing details of the target business operation.

[0024] In some embodiments, the method further includes:

[0025] Determining the protocol to be backfilled based on the backfill type in the protocol template;

[0026] Obtaining the actual backfill protocol of the target business operation;

[0027] Determine the fourth protocol difference details according to the agreed re-injection protocol and the actual re-injection protocol.

[0028] In some embodiments, generate a protocol reconciliation result according to the first protocol difference details, the second protocol difference details, and the third protocol difference details, including:

[0029] Generate a protocol reconciliation result according to the first protocol difference details, the second protocol difference details, the third protocol difference details, and the fourth protocol difference details.

[0030] According to a second aspect of the present application, a protocol reconciliation device is provided. In some embodiments, the device includes:

[0031] A first reconciliation module, configured to determine the protocol to be generated for the target business operation based on the business data, business policies, and protocol scenario rules of the target business operation, determine the actually generated protocol of the target business operation according to the protocol snapshot of the target business operation, determine the protocol quantity reconciliation details according to the protocol to be generated and the actually generated protocol, and determine the first protocol difference details according to the protocol actual call record and the protocol quantity reconciliation details of the target business operation;

[0032] A second reconciliation module, configured to determine the actually generated protocol parameters according to the protocol quantity reconciliation details and the protocol snapshot, determine the protocol parameters to be generated according to the protocol call parameters, protocol template rules, and protocol quantity reconciliation details of the target business operation, and determine the second protocol difference details according to the actually generated protocol parameters and the protocol parameters to be generated;

[0033] A third reconciliation module, configured to parse the protocol file generated by the target business operation to obtain the signature content in the protocol file, and compare the signature content with the protocol seal configuration content in the protocol template to obtain the third protocol difference details;

[0034] A reconciliation result generation module, configured to generate a protocol reconciliation result according to the first protocol difference details, the second protocol difference details, and the third protocol difference details.

[0035] According to a third aspect of the present application, a computer device is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the steps of the protocol reconciliation method provided in any of the above embodiments are implemented.

[0036] According to a fourth aspect of the present application, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the protocol reconciliation method provided in any of the above embodiments are implemented.

[0037] In the above embodiments of the present application, the protocol reconciliation system determines the protocol to be generated for the target business operation based on the business data, business policies, and protocol scenario rules of the target business operation, determines the actually generated protocol for the target business operation according to the protocol snapshot of the target business operation, determines the protocol quantity reconciliation details based on the protocol to be generated and the actually generated protocol, determines the first protocol difference details based on the protocol actual call record and the protocol quantity reconciliation details of the target business operation, determines the protocol actually generated parameters based on the protocol quantity reconciliation details and the protocol snapshot, determines the protocol parameters to be generated based on the protocol call parameters, protocol template rules, and protocol quantity reconciliation details of the target business operation, determines the second protocol difference details based on the protocol actually generated parameters and the protocol parameters to be generated, parses the protocol file generated by the target business operation to obtain the signature content in the protocol file, compares the signature content with the protocol seal configuration content in the protocol template to obtain the third protocol difference details, and finally generates the protocol reconciliation result based on the first protocol difference details, the second protocol difference details, and the third protocol difference details, thereby realizing full-link automated protocol reconciliation, improving the protocol review efficiency, and ensuring the validity of the protocol. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 It is a schematic flowchart of a protocol reconciliation method provided by the present application according to one or more embodiments;

[0039] Figure 2 It is a structural block diagram of a protocol reconciliation device provided by the present application according to one or more embodiments;

[0040] Figure 3 It is an internal structure diagram of a computer device provided by the present application according to one or more embodiments. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0041] To make the objectives, technical solutions, and advantages of the present application clearer, the following will further describe the embodiments of the present application in detail in conjunction with the accompanying drawings. It should be clear that the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of the present application.

[0042] When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0043] In the description of this application, it should be understood that the terms "first", "second", "third", etc. are only used to distinguish similar objects, and do not necessarily describe a specific order or sequence, nor can they be understood as indicating or implying relative importance. For those of ordinary skill in the art, the specific meanings of the above terms in this application can be understood according to specific circumstances. In addition, in the description of this application, unless otherwise specified, "a plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after.

[0044] In view of the deficiencies or defects of the related art, this application provides a protocol reconciliation method, which can achieve full-link automated protocol reconciliation, thereby improving the efficiency of protocol review and ensuring the validity of the protocol.

[0045] In some embodiments, the protocol reconciliation method includes the steps as Figure 1 shown below. Taking the application of this method to the protocol reconciliation system of an Internet financial platform as an example for illustration.

[0046] S110: Determine the protocol to be generated for the target business operation based on the business data, business strategy, and protocol scenario rules of the target business operation. Determine the actually generated protocol for the target business operation according to the protocol snapshot of the target business operation. Determine the protocol quantity reconciliation details based on the protocol to be generated and the actually generated protocol. Determine the first protocol difference details based on the protocol actual call record and the protocol quantity reconciliation details of the target business operation.

[0047] The Internet financial platform includes a business system, a protocol system, and a protocol reconciliation system. Among them, there are usually multiple business systems corresponding to different businesses, while there is usually only one protocol system and one protocol reconciliation system. The above-mentioned systems can be separate independent servers, and communication connections can be established between the systems based on business needs and interactions can be carried out through these connections.

[0048] Users can send business requests, such as borrowing requests and credit requests, to the business system through user devices (usually users' mobile intelligent devices, such as smartphones and tablets). In response to receiving the business requests from the user devices, the business system will execute the business processes corresponding to the business requests. For example, if the business request is a borrowing request, the corresponding credit borrowing process will be executed; if the business request is a credit request, the corresponding credit process will be executed. The business process usually includes one or more links (or called scenarios). In some links, the business system needs to call the protocol system to generate a protocol corresponding to the current link. For example, after the user submits a borrowing request to the business system, in the relevant business process, the business system needs to call the protocol system to generate a credit inquiry authorization letter. Another example is that after the user submits a card binding request to the business system, in the relevant business process, the business system needs to call the protocol system to generate a deduction authorization letter. After the protocol system generates the protocol, it will call the relevant signature authority to stamp the protocol, and then feedback the stamped protocol to the business system to promote the flow of the business process. The protocol in this embodiment is a contract, and there are various types of protocols. It can be understood that the protocols that need to be generated in different links are usually of different types, and the specific type of the protocol is related to the actual business. For example, the protocols related to credit business include, but are not limited to, various protocols such as user credit authorization letters, borrowing contracts, and guarantee contracts. This embodiment does not make specific limitations on the types of protocols that need to be generated. The protocol reconciliation system will automatically review the protocols generated by the protocol system to efficiently confirm the correctness of the protocols.

[0049] Specifically, business strategies are pre-configured in the business system. The business strategies are used to specify which links in the business process need to call the protocol system to generate protocols, as well as the business parameters that need to be transmitted when calling the protocol system in each link. Among them, the business system can call the protocol system through the protocol interface of the protocol system. The protocol system is a system used to generate protocols. Business personnel will pre-configure protocol templates and protocol scenario rules (used to determine the protocols that need to be generated in each scenario) in the protocol system. When the business system calls the protocol system to generate a protocol, the protocol system will determine the protocol template to be used from the pre-configured protocol templates according to the business parameters (such as borrower, loan amount, scenario identifier, etc.) transmitted by the business system and the protocol scenario rules, and then extract the parameters required by the protocol template from the business parameters and fill them into the corresponding positions of the protocol template to generate a protocol snapshot. Then, it will call the signature authority of the capital provider (which can be abbreviated as the funder) to sign the protocol snapshot, thus completing the protocol signing. Among them, the protocol template is a contract template pre-agreed by the Internet financial platform, the capital provider, and the guarantor. By filling in real parameters and completing the stamping in the protocol template, a protocol can be obtained. Different protocol templates require different protocol parameters to be filled. Usually, the protocol needs to be jointly signed by the user and the capital provider, and the protocols for some specific businesses need to be jointly signed by the user, the capital provider, and the guarantor. Among them, when generating a protocol, the protocol system can call the relevant interfaces (such as the signature interface) of the capital provider and the guarantor to complete the signing.

[0050] In some embodiments, determining the operation of generating a protocol for the target business operation based on the business data, business strategy, and protocol scenario rules of the target business operation may be to first associate the business data of the target business operation with the business strategy, thereby obtaining a protocol call record, and then associate the protocol call record with the protocol scenario rules, so as to obtain the protocol to be generated for the target business operation.

[0051] Among them, the target business operation refers to the business operation corresponding to the generation of the protocol this time, including the operation of the business system calling the protocol system and the operation of the protocol system generating the protocol. The protocol call record is the relevant information theoretically generated when the business system calls the protocol system to generate a protocol during the execution of the target business operation, including but not limited to the scenario identifier (indicating the scenario corresponding to when the business system should call the protocol system), the call time (indicating the time when it should be called), and the business parameters (indicating the business parameters that the business system should transmit to the protocol system through the protocol interface).

[0052] After obtaining the protocol call record, associate the protocol call record with the protocol scenario rules to obtain the protocol to be generated for the target business operation. The protocol scenario rules are used to specify the protocol templates required for each scenario. The protocol reconciliation system performs data cleaning based on the scenario identifier in the protocol call record and the protocol scenario rules, and can obtain the protocol template corresponding to the scenario identifier, that is, the protocol to be generated.

[0053] The protocol snapshot is the protocol to be sealed after filling the protocol parameters in the protocol template. After the protocol system generates the protocol snapshot, it will be stored in the protocol snapshot table. The protocol reconciliation system can obtain the protocol snapshot related to the target business operation from it, and then determine the actually generated protocol based on the protocol snapshot.

[0054] The operation of determining the actually generated protocol for the target business operation based on the protocol snapshot of the target business operation can be that the protocol reconciliation system cleans various protocol statuses in the protocol snapshot to obtain the actually generated protocol. The various protocol statuses in the protocol snapshot include the protocol enabled status (initialized, effective, or invalidated), the signature status (no signature required, signature pending, or signed), and the backflow status (no backflow required, backflow pending, or backflow completed). It should be noted that in the credit business, there will be a capital provider and a guarantor involved. Some protocols need to be generated and signed by the capital provider and then the signed protocol is passed to the guarantor, which is called protocol backflow for the guarantor.

[0055] After obtaining the protocol to be generated and the actually generated protocol, the protocol quantity reconciliation details can be determined based on the protocol to be generated and the actually generated protocol. Specifically, the protocol reconciliation system compares whether the quantities of the protocol to be generated and the actually generated protocol related to the target business operation are the same, and generates the protocol quantity reconciliation details. The protocol quantity reconciliation details include information indicating whether the quantities of the protocol to be generated and the actually generated protocol are the same, and the quantity difference between the protocol to be generated and the actually generated protocol.

[0056] After the protocol reconciliation system determines the protocol quantity reconciliation details, it determines the first protocol difference details based on the protocol actual call record and the protocol quantity reconciliation details of the target business operation. In some embodiments, the operation of determining the first protocol difference details based on the protocol actual call record and the protocol quantity reconciliation details of the target business operation can be to filter out the abnormal protocols in the protocol quantity reconciliation details to obtain the protocol abnormality details, then determine the protocol call difference based on the protocol actual call record and the protocol call record of the target business operation, and finally determine the first protocol difference details based on the protocol call difference and the protocol abnormality details.

[0057] Each time the business system calls the protocol system, corresponding protocol actual call records will be generated, including but not limited to the scenario identifier (indicating the scenario corresponding to the actual call of the business system to the protocol system), the call time (indicating the actual call time), and the business parameters (indicating the business parameters actually passed by the business system to the protocol system through the protocol interface). These records are stored and maintained by the business system. The protocol reconciliation system can obtain the protocol actual call records related to the target business operation from the business system. Then, it compares the field information of the protocol actual call records related to the target business operation with the corresponding field information of the protocol expected call records (such as comparing whether there are differences in the scenario identifier, call time, and business parameters between the two call records) to determine the differences between the two, that is, the protocol call differences.

[0058] S120: Determine the protocol actual generation parameters based on the protocol quantity reconciliation details and the protocol snapshot, determine the protocol expected generation parameters based on the protocol call parameters, protocol template rules, and protocol quantity reconciliation details of the target business operation, and determine the second protocol difference details based on the protocol actual generation parameters and the protocol expected generation parameters.

[0059] This step is used to check whether the protocol parameters in the expected generated protocol and the actual generated protocol related to the target business operation are the same.

[0060] In some embodiments, the operation of determining the protocol actual generation parameters based on the protocol quantity reconciliation details and the protocol snapshot can be to first filter the non-missing protocols in the protocol quantity reconciliation details to obtain the protocol non-missing details, then extract the protocol parameters in the protocol snapshot, and finally determine the protocol actual generation parameters based on the protocol non-missing details and the protocol parameters in the protocol snapshot. Among them, data cleaning can be performed based on the protocol non-missing details and the protocol parameters in the protocol snapshot to obtain the protocol actual generation parameters, that is, the protocol parameters actually filled in the protocol template.

[0061] In some embodiments, the operation of determining the protocol expected generation parameters based on the protocol call parameters, protocol template rules, and protocol quantity reconciliation details of the target business operation can be to obtain the protocol non-missing details obtained previously based on the protocol quantity reconciliation details, and then determine the protocol expected generation parameters based on the protocol call parameters, protocol template rules, and the protocol non-missing details of the target business operation.

[0062] S130: Analyze the protocol file generated by the target business operation to obtain the signature content in the protocol file, and compare the signature content with the protocol seal configuration content in the protocol template to obtain the third protocol difference details.

[0063] The protocol document can be a file in PDF (Portable Document Format) format. The protocol reconciliation system parses the protocol document in PDF format, extracts the signature content from it, and then compares it with the protocol seal configuration content on the protocol template to ensure that the signature content on the protocol is correct and complete. The third protocol difference details include information indicating whether the signature content is complete and information indicating whether the signature content is correct.

[0064] S140: Generate a protocol reconciliation result based on the first protocol difference details, the second protocol difference details, and the third protocol difference details.

[0065] After the protocol reconciliation system completes the reconciliation operations for the protocol quantity, protocol value, and protocol signature, it can integrate various protocol difference details based on actual business requirements and output a protocol reconciliation result.

[0066] In some embodiments, the method further includes: determining the protocol to be backfilled based on the backfill type in the protocol template; obtaining the actual backfilled protocol of the target business operation; and determining the fourth protocol difference details based on the protocol to be backfilled and the actual backfilled protocol. Accordingly, generating a protocol reconciliation result based on the first protocol difference details, the second protocol difference details, and the third protocol difference details includes: generating a protocol reconciliation result based on the first protocol difference details, the second protocol difference details, the third protocol difference details, and the fourth protocol difference details.

[0067] The generation process of some protocols also includes a backfill link to achieve automated reconciliation of all links. The protocol reconciliation system also implements the backfilled protocol reconciliation operation through this step. Among them, there is an identifier on the protocol template indicating whether backfilling is required. Accordingly, the protocol reconciliation system can obtain the protocol to be backfilled based on the protocol to be generated and the identifier indicating whether backfilling is required on the protocol template, and then check whether the quantities of the actual backfilled protocol and the protocol to be backfilled are the same, generate the fourth protocol difference details based on the check result, and finally perform difference integration by combining the protocol difference details generated by other reconciliation operations to generate a protocol reconciliation result.

[0068] It should be noted that for each step included in the protocol reconciliation method provided in any of the above embodiments, unless there is a clear description in this article, the execution of these steps does not have a strict order limit, and these steps can be executed in other orders. Moreover, at least some of these steps can include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed 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 alternately or in turn with at least a part of other steps or sub-steps or stages of other steps.

[0069] Based on the same inventive concept, the present application also provides a protocol reconciliation device. In some embodiments, as Figure 2 shown, the protocol reconciliation device includes the following modules:

[0070] The first reconciliation module 110 is configured to determine the protocol that should be generated for the target business operation based on the business data, business strategy, and protocol scenario rules of the target business operation, determine the actually generated protocol of the target business operation according to the protocol snapshot of the target business operation, determine the protocol quantity reconciliation details according to the protocol that should be generated and the actually generated protocol, and determine the first protocol difference details according to the protocol actual call record and the protocol quantity reconciliation details of the target business operation;

[0071] The second reconciliation module 120 is configured to determine the actually generated protocol parameters according to the protocol quantity reconciliation details and the protocol snapshot, determine the protocol parameters that should be generated according to the protocol call parameters, protocol template rules, and protocol quantity reconciliation details of the target business operation, and determine the second protocol difference details according to the actually generated protocol parameters and the protocol parameters that should be generated;

[0072] The third reconciliation module 130 is configured to parse the protocol file generated by the target business operation to obtain the signature content in the protocol file, and compare the signature content with the protocol seal configuration content in the protocol template to obtain the third protocol difference details;

[0073] The reconciliation result generation module 140 is configured to generate a protocol reconciliation result according to the first protocol difference details, the second protocol difference details, and the third protocol difference details.

[0074] In some embodiments, the first reconciliation module 110 includes:

[0075] The should-call record determination sub-module is configured to associate the business data and business strategy of the target business operation to obtain the protocol should-call record;

[0076] The should-generate protocol determination sub-module is configured to associate the protocol should-call record with the protocol scenario rules to obtain the protocol that should be generated for the target business operation.

[0077] In some embodiments, the first reconciliation module 110 further includes:

[0078] The exception details determination sub-module is configured to filter out the abnormal protocols in the protocol quantity reconciliation details to obtain the protocol exception details;

[0079] The call difference determination sub-module is configured to determine the protocol call difference according to the protocol actual call record and the protocol should-call record of the target business operation;

[0080] The first difference determination sub-module is configured to determine the first protocol difference details according to the protocol call difference and the protocol exception details.

[0081] In some embodiments, the second reconciliation module 120 includes:

[0082] The non - missing details determination sub - module is used to filter out the non - missing protocols in the protocol quantity reconciliation details to obtain the protocol non - missing details;

[0083] The protocol parameter extraction sub - module is used to extract the protocol parameters in the protocol snapshot;

[0084] The actual generation parameter determination sub - module is used to determine the actual generation parameters of the protocol according to the protocol non - missing details and the protocol parameters in the protocol snapshot.

[0085] In some embodiments, the second reconciliation module 120 further includes:

[0086] The non - missing details acquisition sub - module is used to acquire the protocol non - missing details obtained based on the protocol quantity reconciliation details;

[0087] The should - generate parameter determination sub - module is used to determine the should - generate parameters of the protocol according to the protocol call parameters of the target business operation, the protocol template rules, and the protocol non - missing details.

[0088] In some embodiments, the device further includes a fourth reconciliation module. The fourth reconciliation module includes:

[0089] The should - backfill protocol determination sub - module is used to determine the should - backfill protocol based on the backfill type in the protocol template;

[0090] The actual backfill protocol determination sub - module is used to acquire the actual backfill protocol of the target business operation;

[0091] The fourth difference determination sub - module is used to determine the fourth protocol difference details according to the should - backfill protocol and the actual backfill protocol.

[0092] In some embodiments, the reconciliation result generation module 140 is further used to generate a protocol reconciliation result according to the first protocol difference details, the second protocol difference details, the third protocol difference details, and the fourth protocol difference details.

[0093] For the specific limitations of the protocol reconciliation device, reference can be made to the limitations on the protocol reconciliation method in the above text, which will not be elaborated here. Each module in the above - mentioned protocol reconciliation device can be implemented in whole or in part through software, hardware, and their combination. The above - mentioned modules can be embedded in the processor of the computer device in hardware form or be independent of it, or can be stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to the above - mentioned modules.

[0094] The present application also provides a computer device. In some embodiments, the computer device includes a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the steps of the protocol reconciliation method provided in any of the above embodiments can be implemented.

[0095] Further, in some embodiments, the internal structure diagram of the computer device may be as Figure 3 shown. The computer device includes a processor, a memory, a network interface, and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data such as protocol difference details, and the specific stored data can also refer to the limitations in the above method embodiments. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a protocol reconciliation method is implemented.

[0096] Those skilled in the art can understand that Figure 3 the structure shown in

[0097] is only a block diagram of some structures related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different component layout.

[0098] In the above embodiments of the present application, the descriptions of the various embodiments have their own emphases. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0099] Those of ordinary skill in the art can understand that all or part of the processes in the above method embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the above method embodiments. Among them, any reference to a memory, storage, database, or other medium used in the embodiments provided in the present application can include non-volatile and / or volatile memories. Non-volatile memories can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memories can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink), DRAM (SLDRAM), memory bus (Rambus), direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0100] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope described in this specification.

[0101] The above-described embodiments merely represent several implementation manners of the present application. Their descriptions are relatively specific and detailed, but they should not be construed as limiting the scope of the invention patent. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application should be subject to the appended claims.

Claims

1. A protocol reconciliation method, characterized in that, The method includes: Determining the protocol to be generated for the target business operation based on the business data, business strategy, and protocol scenario rules of the target business operation, determining the actually generated protocol of the target business operation according to the protocol snapshot of the target business operation, determining the protocol quantity reconciliation details based on the protocol to be generated and the actually generated protocol, and determining the first protocol difference details based on the protocol actual call record of the target business operation and the protocol quantity reconciliation details; Determining the actually generated protocol parameters based on the protocol quantity reconciliation details and the protocol snapshot, determining the protocol parameters to be generated based on the protocol call parameters, protocol template rules, and the protocol quantity reconciliation details of the target business operation, and determining the second protocol difference details based on the actually generated protocol parameters and the protocol parameters to be generated; Parsing the protocol file generated by the target business operation to obtain the signature content in the protocol file, and comparing the signature content with the protocol seal configuration content in the protocol template to obtain the third protocol difference details; Generating a protocol reconciliation result based on the first protocol difference details, the second protocol difference details, and the third protocol difference details.

2. The method according to claim 1, wherein Determining the protocol to be generated for the target business operation based on the business data, business strategy, and protocol scenario rules of the target business operation includes: Associating the business data and business strategy of the target business operation to obtain a protocol call record to be made; Associating the protocol call record to be made with the protocol scenario rules to obtain the protocol to be generated for the target business operation.

3. The method according to claim 2, characterized in that, Determining the first protocol difference details based on the protocol actual call record of the target business operation and the protocol quantity reconciliation details includes: Filtering out the abnormal protocols in the protocol quantity reconciliation details to obtain protocol abnormality details; Determining the protocol call difference based on the protocol actual call record and the protocol call record to be made of the target business operation; Determining the first protocol difference details based on the protocol call difference and the protocol abnormality details.

4. The method according to claim 1, wherein Determining the actually generated protocol parameters based on the protocol quantity reconciliation details and the protocol snapshot includes: Filtering out the non-missing protocols in the protocol quantity reconciliation details to obtain protocol non-missing details; Extracting the protocol parameters from the protocol snapshot; Determining the actually generated protocol parameters based on the protocol non-missing details and the protocol parameters in the protocol snapshot.

5. The method according to claim 4, wherein Determining the protocol parameters to be generated based on the protocol call parameters, protocol template rules, and the protocol quantity reconciliation details of the target business operation includes: Obtaining the protocol non-missing details obtained based on the protocol quantity reconciliation details; Determining the protocol parameters to be generated based on the protocol call parameters, protocol template rules, and the protocol non-missing details of the target business operation.

6. The method according to claim 1, wherein The method further includes: Determining the protocol to be backfilled based on the backfill type in the protocol template; Obtaining the actually backfilled protocol of the target business operation; Determining the fourth protocol difference details based on the protocol to be backfilled and the actually backfilled protocol.

7. The method according to claim 6, wherein Generating a protocol reconciliation result based on the first protocol difference details, the second protocol difference details, and the third protocol difference details includes: Generate a protocol reconciliation result based on the first protocol difference details, the second protocol difference details, the third protocol difference details, and the fourth protocol difference details.

8. A protocol reconciliation device, characterized in that The device includes: A first reconciliation module, configured to determine a protocol to be generated for a target business operation based on business data, business policies, and protocol scenario rules of the target business operation, determine the actually generated protocol of the target business operation according to the protocol snapshot of the target business operation, determine protocol quantity reconciliation details according to the protocol to be generated and the actually generated protocol, and determine first protocol difference details according to the protocol actual call record of the target business operation and the protocol quantity reconciliation details; A second reconciliation module, configured to determine actually generated protocol parameters according to the protocol quantity reconciliation details and the protocol snapshot, determine protocol parameters to be generated according to the protocol call parameters, protocol template rules, and the protocol quantity reconciliation details of the target business operation, and determine second protocol difference details according to the actually generated protocol parameters and the protocol parameters to be generated; A third reconciliation module, configured to parse the protocol file generated by the target business operation to obtain the signature content in the protocol file, and compare the signature content with the protocol seal configuration content in the protocol template to obtain third protocol difference details; A reconciliation result generation module, configured to generate a protocol reconciliation result according to the first protocol difference details, the second protocol difference details, and the third protocol difference details.

9. A computer device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images