Function management method, platform, equipment, medium and product

Abstract

The invention provides a function management method, platform and equipment, a medium and a product, and relates to the technical field of block chains. The method is applied to a certificate management platform, and comprises the following steps: receiving a first request sent by a certificate initiating end, and storing the first request in a block chain and a database; receiving a second request sent by the certificate initiating end; sending the second request to the certificate providing end according to the certificate providing end identification information; receiving a third request sent by the function providing end, and storing the third request in the block chain and the database; and receiving a fourth request sent by the letter providing end, and sending the fourth request to the letter initiating end according to the letter initiating end identification information. According to the method provided by the invention, the database is used in an auxiliary manner, and the certificate request information and the electronic feedback file are stored in the block chain and the database at the same time, so that the whole certificate process can still be smoothly carried out when the block chain network fails, and the stability and reliability of the certificate management platform are improved.

Description

Technical Field

[0001] The present application relates to the field of blockchain technology, and in particular to a letter of credit management method, platform, equipment, medium and product. Background Art

[0002] During the audit process, confirmation refers to a method in which the auditing unit (i.e., the confirmation initiator) sends a confirmation letter directly to a third-party financial institution (i.e., the confirmation provider) after obtaining authorization from the audited unit, and audits the audited unit through the electronic reply document from the confirmation provider.

[0003] In existing technologies, electronic confirmations are usually managed based on blockchain technology. By utilizing the distributed ledger characteristics of blockchain, the generation, transmission and confirmation processes of electronic confirmations can be accurately recorded, and these records can be accessed and verified in real time by all relevant parties.

[0004] However, this blockchain-based confirmation management method relies on blockchain technology to securely store, transmit, and verify data. If the blockchain network fails, the entire confirmation process will be interrupted, affecting the normal progress of audit work. Summary of the Invention

[0005] The present application provides a confirmation management method, platform, device, medium and product, which are used to store confirmation request information and electronic reply documents in the blockchain and the database at the same time through the auxiliary use of the database, ensuring that the entire confirmation process can still proceed smoothly when the blockchain network fails, thereby improving the stability and reliability of the confirmation management platform.

[0006] In a first aspect, the present application provides a confirmation management method, which is applied to a confirmation management platform and includes:

[0007] Receive a first request sent by the confirmation initiator, and store the first request in the blockchain and the database, where the first request includes the confirmation initiator's identification information, the transaction number information, and a first hash value generated by the confirmation initiator based on the request parameters entered by the user;

[0008] receiving a second request sent by the confirmation initiator, the second request including the confirmation initiator identification information, the transaction number information, the encrypted request parameters, and the confirmation provider identification information;

[0009] Sending the second request to the confirmation provider according to the confirmation provider identification information, so that the confirmation provider generates an electronic reply file according to the second request;

[0010] Receive a third request from the confirmation provider, and store the third request in the blockchain and the database. The third request includes the confirmation provider identification information, the transaction number information, the confirmation initiator identification information, and a second hash value generated by the confirmation provider based on the electronic reply document.

[0011] Receive the fourth request sent by the confirmation provider, and send the fourth request to the confirmation initiator according to the confirmation initiator's identification information. The fourth request includes the confirmation provider's identification information, transaction number information, the encrypted electronic reply file and the confirmation initiator's identification information.

[0012] In a second aspect, the present application provides a letter confirmation management platform, including: an accounting module, a request sending module, and a reply sending module;

[0013] The accounting module is configured to receive a first request sent by a confirmation initiator and store the first request in the blockchain and the database, wherein the first request includes identification information of the confirmation initiator, transaction number information, and a first hash value generated by the confirmation initiator based on request parameters input by the user;

[0014] a request sending module, configured to receive a second request sent by the confirmation initiator, the second request including the confirmation initiator identification information, the transaction number information, the encrypted request parameters, and the confirmation provider identification information;

[0015] The request sending module is further configured to send the second request to the confirmation providing end according to the identification information of the confirmation providing end, so that the confirmation providing end generates an electronic reply file according to the second request;

[0016] The accounting module is further configured to receive a third request sent by the confirmation provider and store the third request in the blockchain and the database, wherein the third request includes the confirmation provider identification information, the transaction number information, the confirmation initiator identification information, and a second hash value generated by the confirmation provider based on the electronic reply document;

[0017] The reply letter sending module is used to receive the fourth request sent by the confirmation provider and send the fourth request to the confirmation initiator according to the confirmation initiator's identification information. The fourth request includes the confirmation provider's identification information, transaction number information, encrypted electronic reply letter file and confirmation initiator's identification information.

[0018] In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;

[0019] Memory stores computer-executable instructions;

[0020] The processor executes the computer execution instructions stored in the memory to implement a letter of credit management method according to the first aspect of the invention.

[0021] In a fourth aspect, the present application provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are executed by a processor, they are used to implement a letter of credit management method according to the invention content of the first aspect.

[0022] In a fifth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, is used to implement a letter of credit management method according to the invention content of the first aspect.

[0023] The present application provides a letter confirmation management method, platform, device, medium and product, including: first, receiving a first request sent by a letter confirmation initiator, and storing the first request in a blockchain and a database, wherein the first request includes the letter confirmation initiator's identification information, transaction number information, and a first hash value generated by the letter confirmation initiator based on the request parameters input by the user; then, receiving a second request sent by the letter confirmation initiator, wherein the second request includes the letter confirmation initiator's identification information, transaction number information, encrypted request parameters and the letter confirmation provider's identification information; and sending the second request to the letter confirmation provider based on the letter confirmation provider's identification information. The confirmation provider generates an electronic reply document based on the second request. Then, the confirmation provider receives a third request and stores it in the blockchain and database. The third request includes the confirmation provider's identification information, transaction number information, confirmation initiator's identification information, and a second hash value generated by the confirmation provider based on the electronic reply document. Finally, the confirmation provider receives a fourth request and sends it to the confirmation initiator based on the confirmation initiator's identification information. The fourth request includes the confirmation provider's identification information, transaction number information, the encrypted electronic reply document, and confirmation initiator's identification information. This achieves the following technical effect: By using both blockchain and database to store information simultaneously, it ensures that the normal operation of the confirmation process is not affected when blockchain issues arise. When the blockchain service is operating normally, the confirmation management platform uses the blockchain to ensure data immutability and multi-party consensus. However, in the event of a network anomaly or service interruption on the blockchain, the database temporarily takes over the storage and transfer of key data, ensuring the continued and stable operation of the entire confirmation process, thereby improving the stability and reliability of the confirmation management platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0025] Figure 1 A flowchart of a letter of credit management method provided in an embodiment of the present application.

[0026] Figure 2 A schematic diagram of a method for storing cached data provided in an embodiment of the present application.

[0027] Figure 3 A schematic diagram of an interactive method for a confirmation management method provided in an embodiment of the present application.

[0028] Figure 4 A schematic diagram of an interactive scenario of a confirmation management method provided in an embodiment of the present application.

[0029] Figure 5 A schematic diagram of the structure of a confirmation management platform provided in an embodiment of the present application.

[0030] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0031] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0032] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0033] In the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit differences. It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described in this application as "exemplary" or "for example" should not be interpreted as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way. In the embodiments of the present application, "at least one" refers to one or more, and "more than one" refers to two or more.

[0034] It should be noted that the "at..." in the embodiments of the present application can mean the instant a certain situation occurs, or it can mean a period of time after a certain situation occurs, and the embodiments of the present application do not specifically limit this. In addition, the letter of credit management method provided in the embodiments of the present application is only an example, and a letter of credit management method can also include more or less content.

[0035] It should be noted that the letter of confirmation management method, platform, equipment, medium and products provided in this application can be used in the field of blockchain technology, and can also be used in any field other than the field of blockchain technology. The application field of the letter of confirmation management method, platform, equipment, medium and products in this application is not limited.

[0036] Confirmation is a method in which the auditing unit (as the confirmation initiator) sends a confirmation letter to a third-party financial institution (as the confirmation provider) on the premise of obtaining authorization from the audited unit, and conducts audit work on the audited unit based on the electronic reply document provided by the confirmation provider.

[0037] Currently, electronic confirmations are widely managed on blockchain. Leveraging blockchain's distributed ledger capabilities, every step of the electronic confirmation process, from generation to transmission to confirmation, can be accurately recorded. These records are accessible and verifiable in real time by all relevant parties, effectively ensuring the authenticity and traceability of the confirmation data.

[0038] However, blockchain-based confirmation management methods have certain limitations. Because they rely heavily on blockchain technology for secure data storage, transmission, and verification, any blockchain network failure, such as a network outage or node anomaly, will directly disrupt and stagnate the entire confirmation process, hindering the normal progress of audit work and reducing its continuity and efficiency.

[0039] Based on this, the embodiments of this application propose a confirmation management method, platform, device, medium, and product for use in the blockchain technology field, aiming to address the aforementioned technical issues of the prior art. While retaining the advantages of existing blockchain technology, this method introduces a database as a secondary storage mechanism. When processing a confirmation request, the confirmation request information and the electronic reply document are simultaneously recorded in the blockchain and the database. Therefore, in the event of a network anomaly or service interruption on the blockchain, the database can temporarily take over the storage and transfer of critical data, ensuring the continued and stable operation of the confirmation process.

[0040] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0041] Figure 1 This is a flow chart of a letter of credit management method provided in the embodiment of this application. Figure 1 As shown, the method includes:

[0042] S101. Receive a first request sent by a confirmation initiator, and store the first request in a blockchain and a database.

[0043] In an embodiment of the present application, a confirmation management method is implemented by a confirmation management platform. This platform can be implemented as a server cluster or distributed system consisting of multiple physical servers. It is used to receive, process, and forward confirmation requests, and manage reply information. Furthermore, the confirmation management platform integrates a blockchain system and a database system.

[0044] Specifically, the confirmation management platform serves as an intermediary between the confirmation initiator and the confirmation provider. It receives requests from these two parties, stores data, and transmits requests and information between them. The confirmation initiator, which can be an auditing firm, initiates confirmation requests based on user-entered request parameters. The confirmation provider, which can be a third-party financial institution, responds to the confirmation and provides an electronic reply document. The blockchain and database are used to store and record the confirmation management platform's operation logs, hash values, and requests from the confirmation initiator and the confirmation provider. The database can be a traditional database, such as a relational database.

[0045] The first request includes the confirmation initiator's identification information, transaction number information, and a first hash value generated by the confirmation initiator based on the request parameters entered by the user. Specifically, after the user enters the request parameters through the confirmation initiator, the confirmation initiator can calculate the first hash value of the user-entered request parameters through a hash function and generate the first request based on the confirmation initiator's identification information, transaction number information, and the first hash value. The confirmation initiator can then send this first request to the confirmation management platform. The confirmation management platform can store this first request simultaneously on the blockchain and in a database to ensure data security and availability. By using both the blockchain and the database to store information simultaneously, problems with the blockchain can be prevented from impacting the normal operation of the confirmation process.

[0046] That is to say, when the blockchain service is operating normally, the confirmation management platform can use the blockchain to ensure the immutability of data and multi-party consensus; when the blockchain encounters network anomalies or service interruptions, the database can temporarily take over the storage and circulation functions of key data to ensure that the entire confirmation process can continue to operate stably, thereby improving the stability and reliability of the confirmation management platform.

[0047] S102. Receive the second request sent by the confirmation initiator.

[0048] In an embodiment of the present application, the second request includes the confirmation initiator identification information, transaction number information, encrypted request parameters and confirmation provider identification information.

[0049] Specifically, after the user enters the request parameters through the confirmation initiator, the confirmation initiator can encrypt the request parameters entered by the user. Optionally, the encryption process can utilize asymmetric encryption technology, encrypting the request parameters entered by the user using the public key of the confirmation provider. After encryption is complete, the confirmation initiator can generate a second request based on the confirmation initiator's identification information, the transaction number, the encrypted request parameters, and the confirmation provider's identification information, and send the second request to the confirmation management platform.

[0050] S103. Send the second request to the confirmation provider according to the identification information of the confirmation provider, so that the confirmation provider generates an electronic reply file according to the second request.

[0051] Specifically, the second request includes the confirmation provider's identification information (i.e., the destination address of the confirmation request). Upon receiving the second request, the confirmation management platform can verify the confirmation initiator's identification information and transaction number information in the second request against the first request stored in the blockchain or database. Once verification is successful, the second request is sent to the confirmation provider based on the confirmation provider's identification information. This ensures that the confirmation request (second request) is accurately delivered to the confirmation provider. The confirmation provider then decrypts the encrypted request parameters in the second request using its private key and generates an electronic reply file based on the request parameters. The method and process for generating the electronic reply file are consistent with existing methods and can be directly adapted, so this will not be further elaborated here.

[0052] S104. Receive the third request sent by the confirmation provider, and store the third request in the blockchain and the database.

[0053] In an embodiment of the present application, the third request includes the identification information of the confirmation provider, the transaction number information, the identification information of the confirmation initiator, and the second hash value generated by the confirmation provider based on the electronic reply file.

[0054] Specifically, after the confirmation provider generates the electronic reply document, it can also use a hash function to calculate a second hash value for the electronic reply document. It then generates a third request based on the confirmation provider's identification information, the transaction number, the confirmation initiator's identification information, and the second hash value. The confirmation provider can then send this third request to the confirmation management platform. The confirmation management platform can also store this third request simultaneously on the blockchain and in the database. By supplementing the database with data storage, this ensures data security and availability in the event of a blockchain network failure.

[0055] S105. Receive the fourth request sent by the confirmation provider, and send the fourth request to the confirmation initiator according to the confirmation initiator identification information.

[0056] In an embodiment of the present application, the fourth request includes the identification information of the confirmation provider, transaction number information, the encrypted electronic reply file and the identification information of the confirmation initiator.

[0057] Specifically, after the confirmation provider generates the electronic reply document, it can also encrypt it to ensure data transmission security. The encryption process for the electronic reply document is similar to the encryption of the confirmation request parameters by the confirmation initiator, and will not be repeated here.

[0058] After encrypting the electronic reply document, the confirmation provider can generate a fourth request based on the provider's identification information, the transaction number, the encrypted electronic reply document, and the confirmation initiator's identification information, and send it to the confirmation management platform. Upon receiving the fourth request, the confirmation management platform can verify the provider's identification information and transaction number in the fourth request against the third request stored in the blockchain or database. Once verification is successful, the platform will send the fourth request to the confirmation initiator based on the confirmation initiator's identification information. This ensures that the reply information (fourth request) is accurately returned to the confirmation initiator.

[0059] The present embodiment provides a letter confirmation management method, which is applied to a letter confirmation management platform, including: first, receiving a first request sent by a letter confirmation initiator, and storing the first request in a blockchain and a database, wherein the first request includes identification information of the letter confirmation initiator, transaction number information, and a first hash value generated by the letter confirmation initiator according to request parameters input by the user; then, receiving a second request sent by the letter confirmation initiator, wherein the second request includes identification information of the letter confirmation initiator, transaction number information, encrypted request parameters, and identification information of the letter confirmation provider; and sending the second request to the letter confirmation provider according to the identification information of the letter confirmation provider, so as to obtain the encrypted request parameters of the letter confirmation provider. The confirmation provider generates an electronic reply file according to the second request; then, a third request sent by the confirmation provider is received, and the third request is stored in the blockchain and the database. The third request includes the confirmation provider's identification information, transaction number information, the confirmation initiator's identification information, and a second hash value generated by the confirmation provider according to the electronic reply file; finally, a fourth request is received from the confirmation provider, and the fourth request is sent to the confirmation initiator according to the confirmation initiator's identification information. The fourth request includes the confirmation provider's identification information, transaction number information, the encrypted electronic reply file, and the confirmation initiator's identification information.

[0060] The following technical effects have been achieved: By using both blockchain and databases to store information simultaneously, the normal operation of the confirmation process is ensured even when blockchain issues arise. When the blockchain service is operating normally, the confirmation management platform uses the blockchain to ensure data immutability and multi-party consensus. However, in the event of network anomalies or service interruptions on the blockchain, the database temporarily takes over the storage and flow of critical data, ensuring the continued stable operation of the entire confirmation process, thereby improving the stability and reliability of the confirmation management platform.

[0061] In one possible implementation, in step S101, storing the first request in the blockchain and the database includes:

[0062] S201. When an abnormality occurs in the storage function of the blockchain or database, the first request is stored in the cache.

[0063] Specifically, to ensure high availability and data integrity, the platform will switch to cache storage if it detects a blockchain or database storage failure. This means the platform is unable to provide storage services due to an anomaly in the blockchain or database storage function. The platform will store the first request in the cache and record the timestamp and error message of the storage failure. Furthermore, it can send a warning of the storage anomaly to technical personnel.

[0064] S202: When the storage function of the blockchain or database returns to normal, store the first request in the cache in the blockchain or database.

[0065] Specifically, when the confirmation management platform detects that the storage function of the blockchain or database has been restored, it can extract the first request to be stored from the cache and retry to write to the blockchain or database. If the write is successful, the corresponding record in the cache will be deleted; if the write fails, it will remain in the cache, record the error log and wait for the next retry.

[0066] Optionally, the cache can use a high-performance distributed cache system to ensure high availability of the cache itself.

[0067] A confirmation management method provided in an embodiment of the present application effectively avoids data loss or audit process interruption caused by blockchain or database storage failure by using a cache to temporarily store the first request when an abnormality occurs in the storage function of the blockchain or database. It ensures that the audit process can continue to run even when part of the storage system of the confirmation management platform is temporarily unavailable, while ensuring that data will not be lost, and automatically completes data synchronization after the storage system function is restored, thereby improving the stability and reliability of the confirmation management platform.

[0068] In one possible implementation, in the above step S201, when an abnormality occurs in the storage function of the blockchain or the database, the first request is stored in the cache, including: when an abnormality is detected in the network connection of the blockchain or the storage function of the database, stopping the operation of directly storing the first request in the blockchain or directly storing it in the database, and storing the first request in the cache in the order of the time when the request was initiated.

[0069] Specifically, when the confirmation management platform detects that the blockchain node is disconnected, such as the Ethereum node is offline or the database service is down or the response timeout, it can stop writing the first request directly to the blockchain or database, and cache the first request in the order of initiation time, so that after the blockchain or database becomes available again, the first request can be retrieved from the cache and resubmitted to the blockchain or database in order.

[0070] In order to increase data access speed, in this embodiment, a cache may be used to temporarily store the first request.

[0071] In the above step S202, when the storage function of the blockchain or database returns to normal, the first request in the cache is stored in the blockchain or database, including: when the storage function of the blockchain or database returns to normal, triggering the retry submission mechanism of the first request saved in the cache, and storing it in the blockchain or database in the order of the time when the requests were initiated.

[0072] Specifically, to ensure that the first request in the cache can be correctly and orderly stored in the blockchain or database after the abnormal recovery, the confirmation management platform can start the cache retry process when the blockchain node is successfully reconnected or the database service health check passes (such as the heartbeat test returns to normal). The first request is retrieved from the cache in the order in which the request was initiated and attempted to be submitted to the blockchain or database. After successful submission, the first request is removed from the cache; after submission fails, the platform continues to retry a preset number of times (for example, 5 times), records the error log, and sends a storage abnormality warning message to the technical staff.

[0073] Specifically, the cache in the embodiment of the present application can store data according to different storage service identifiers. Figure 2 Schematic diagram of a method for storing cache data provided in an embodiment of the present application. Figure 2 As shown, compensating storage refers to storing data through cache.

[0074] Furthermore, the confirmation management platform can also ensure data integrity by regularly comparing the first hash value in the cache with the first request in the blockchain or database.

[0075] A confirmation management method provided in an embodiment of the present application triggers a retry submission mechanism for the first request saved in the cache when the blockchain or database storage function returns to normal, and submits the requests in the order in which they were initiated. This not only improves the fault tolerance of the confirmation management platform, but also ensures the continuity of the entire confirmation process and the integrity of the data.

[0076] In one possible implementation, after the above-mentioned step S104, receiving the third request sent by the confirmation provider, the method further includes: sending the first hash value in the blockchain or database to the confirmation provider according to the third request, so that the confirmation provider verifies the consistency of the third hash value with the first hash value after decrypting the encrypted request parameters in the second request and generating the third hash value.

[0077] In an embodiment of the present application, after receiving the second request, the confirmation provider can verify whether the request parameters in the second request have been tampered with by sending a third request to the confirmation management platform.

[0078] Specifically, the confirmation management platform can search and extract the corresponding first hash value from the blockchain or database based on the third request sent by the confirmation provider, and then send it to the confirmation provider based on the confirmation provider's identification information. The confirmation provider can use its private key to decrypt the encrypted request parameters in the second request and calculate the third hash value of the decrypted request parameters using the same hash function as the confirmation initiator. The confirmation provider can then determine whether the request parameters in the second request have been tampered with by comparing the third hash value with the first hash value. If they are consistent, it indicates that the request parameters in the second request have not been tampered with, and the confirmation provider can generate a fourth request in response.

[0079] An embodiment of the present application provides a confirmation management method, which receives a third request sent by a confirmation provider and sends a first hash value in a blockchain or database to the confirmation provider based on the third request, so that the confirmation provider verifies whether the request parameters in the second request have been tampered with, thereby ensuring that the confirmation management platform can safely and reliably complete the hash value verification process, thereby ensuring the integrity and authenticity of the data during transmission and processing.

[0080] In one possible implementation, in the above steps, sending the first hash value in the blockchain or database to the confirmation provider according to the third request includes: extracting the confirmation initiator identification information and transaction number information from the third request; extracting the first hash value corresponding to the transaction number information from the blockchain or database according to the confirmation initiator identification information and transaction number information; and sending the extracted first hash value to the confirmation provider.

[0081] Specifically, after receiving the third request from the confirmation provider, the confirmation management platform can first parse it to extract the confirmation initiator's identification information and transaction number information. The confirmation initiator's identification information includes the confirmation initiator's identity, such as a number, user identification (ID), and institution code. The transaction number uniquely identifies a confirmation request, facilitating the confirmation management platform's location of the first hash value corresponding to the transaction number in the blockchain or database. The confirmation management platform can then use the confirmation initiator's identification information and transaction number information as query criteria to search for the corresponding data record in the blockchain or database and extract the first hash value. Finally, the confirmation management platform can encapsulate the retrieved first hash value into a response message and return it to the confirmation provider via a secure channel, such as HyperText Transfer Protocol Secure (HTTPS) or Transport Layer Security (TLS).

[0082] An embodiment of the present application provides a confirmation management method, which extracts the confirmation initiator identification information and transaction number information in the third request, and extracts the first hash value corresponding to the transaction number information from the blockchain or database. The confirmation management platform can efficiently and securely complete the extraction and transmission of the first hash value, thereby ensuring the integrity and authenticity of the data.

[0083] In one possible implementation, the letter confirmation management platform also includes a service gateway; accordingly, receiving a first request sent by the letter confirmation initiator includes: receiving the first request sent by the letter confirmation initiator through the service gateway; receiving a second request sent by the letter confirmation initiator includes: receiving the second request sent by the letter confirmation initiator through the service gateway; sending the second request to the letter confirmation provider includes: sending the second request to the letter confirmation provider through the service gateway; receiving a third request sent by the letter confirmation provider includes: receiving the third request sent by the letter confirmation provider through the service gateway; receiving a fourth request sent by the letter confirmation provider, and sending the fourth request to the letter confirmation initiator according to the identification information of the letter confirmation initiator, includes: receiving the fourth request sent by the letter confirmation provider through the service gateway, and sending the fourth request to the letter confirmation initiator according to the identification information of the letter confirmation initiator.

[0084] Specifically, within the confirmation management platform, the service gateway serves as both the entry and exit points for requests, implementing routing, load balancing, and security verification. For example, request routing forwards requests to the correct backend service based on the request type or path; permission control authenticates and authorizes different roles (e.g., confirmation initiator and confirmation provider); protocol conversion enables conversion between multiple transmission protocols; logging uniformly records all request / response information for easy detection and auditing; and security protection prevents external attacks, injection attacks, and other security threats.

[0085] Specifically, the service gateway serves as the entry and exit point for all external requests. It can receive the first request and the second request from the confirmation initiator; forward the second request to the confirmation provider; and receive the third request and the fourth request from the confirmation provider; and return the fourth request to the confirmation initiator.

[0086] A letter of confirmation management method provided in an embodiment of the present application introduces a service gateway component into a letter of confirmation management platform, and all requests (first request, second request, third request, fourth request) are uniformly processed by the service gateway. The letter of confirmation management platform can efficiently and securely process requests from different clients, thereby effectively improving the security, maintainability and scalability of the letter of confirmation management platform.

[0087] Figure 3 This is a schematic diagram of an interactive method for a letter of credit management method provided in an embodiment of the present application. Figure 3 As shown, the method includes:

[0088] S301. The confirmation initiator generates a first hash value according to the request parameters input by the user.

[0089] S302. The confirmation initiator generates a first request according to the confirmation initiator identification information, the transaction number information and the first hash value.

[0090] S303. The confirmation initiator sends the first request to the confirmation management platform.

[0091] S304. The confirmation management platform stores the first request in both the blockchain and the database.

[0092] S305. The confirmation initiator encrypts the request parameters input by the user using the public key of the confirmation provider.

[0093] S306. The confirmation initiator generates a second request based on the confirmation initiator identification information, transaction number information, encrypted request parameters and confirmation provider identification information.

[0094] S307. The confirmation initiator sends the second request to the confirmation management platform.

[0095] S308. The confirmation management platform sends the second request to the confirmation provider according to the identification information of the confirmation provider.

[0096] S309. The confirmation provider uses the private key to decrypt the encrypted request parameters in the second request.

[0097] S310. The confirmation provider generates an electronic reply file according to the request parameters.

[0098] S311. The confirmation provider calculates the second hash value of the electronic reply file through a hash function.

[0099] S312. The confirmation provider generates a third request based on the confirmation provider identification information, transaction number information, confirmation initiator identification information and the second hash value.

[0100] S313. The confirmation provider sends the third request to the confirmation management platform.

[0101] S314. The confirmation management platform stores the third request in both the blockchain and the database.

[0102] S315. The confirmation management platform searches and extracts the corresponding first hash value from the blockchain or database based on the third request sent by the confirmation provider.

[0103] S316. The confirmation management platform sends the first hash value to the confirmation provider according to the identification information of the confirmation provider.

[0104] S317. The confirmation provider uses the same hash function as the confirmation initiator to calculate the third hash value of the decrypted request parameter.

[0105] S318. The confirmation provider verifies the consistency of the third hash value and the first hash value.

[0106] S319. The confirmation provider generates a fourth request based on the confirmation provider identification information, transaction number information, encrypted electronic reply file and confirmation initiator identification information.

[0107] S320. The confirmation provider sends the fourth request to the confirmation management platform.

[0108] S321. The confirmation management platform sends the fourth request to the confirmation initiator according to the identification information of the confirmation initiator.

[0109] Furthermore, the confirmation initiator can verify whether the electronic reply file in the received fourth request has been tampered with through the second hash value stored in the confirmation management platform. The verification method is similar to the method used by the confirmation provider to verify the consistency of the third hash value and the first hash value, and will not be repeated here.

[0110] Figure 4This is a schematic diagram of an interactive scenario of a letter of credit management method provided in an embodiment of the present application. Figure 4 As shown, confirmation initiator 110 and confirmation provider 130 transmit requests and information via confirmation management platform 120. Confirmation management platform 120 communicates with confirmation initiator 110 and confirmation provider 130 via service gateway 123, implementing accounting service 121 and confirmation service 122. The accounting service stores the first, second, third, and fourth requests, while confirmation service 122 processes the first, second, third, and fourth requests, or forwards the second and fourth requests, ensuring a smooth flow of the confirmation process.

[0111] Figure 5 This is a structural diagram of a letter of credit management platform provided in the embodiment of this application. Figure 5 As shown, the confirmation management platform includes: an accounting module 510, a request sending module 520 and a reply sending module 530.

[0112] The accounting module 510 is configured to receive a first request sent by the confirmation initiator and store the first request in the blockchain and the database. The first request includes the confirmation initiator's identification information, the transaction number information, and a first hash value generated by the confirmation initiator based on the request parameters input by the user.

[0113] Request sending module 520, configured to receive a second request sent by the confirmation initiator, the second request including the confirmation initiator identification information, transaction number information, encrypted request parameters, and confirmation provider identification information;

[0114] The request sending module 520 is further configured to send the second request to the confirmation provider according to the confirmation provider identification information, so that the confirmation provider generates an electronic reply file according to the second request;

[0115] The accounting module 510 is further configured to receive a third request sent by the confirmation provider and store the third request in the blockchain and the database. The third request includes the confirmation provider identification information, the transaction number information, the confirmation initiator identification information, and a second hash value generated by the confirmation provider based on the electronic reply document.

[0116] The reply sending module 530 is used to receive the fourth request sent by the confirmation provider and send the fourth request to the confirmation initiator according to the confirmation initiator's identification information. The fourth request includes the confirmation provider's identification information, transaction number information, the encrypted electronic reply file and the confirmation initiator's identification information.

[0117] In one possible design, the accounting module 510 includes: a cache module and a compensation record module.

[0118] A cache module, configured to store the first request in a cache when an abnormality occurs in the storage function of the blockchain or database;

[0119] The compensation recording module is used to store the first request in the cache in the blockchain or database when the storage function of the blockchain or database returns to normal.

[0120] In one possible design, the cache module is further configured to stop directly storing the first request in the blockchain or in the database when detecting an abnormality in the blockchain network connection or an abnormality in the storage function of the database, and store the first request in the cache in the order of the time when the request was initiated.

[0121] The compensation record module is also used to trigger the retry submission mechanism of the first request saved in the cache when the storage function of the blockchain or database returns to normal, and store it in the blockchain or database in the order of the time when the request was initiated.

[0122] In one possible design, the platform also includes a hash value sending module.

[0123] The hash value sending module is used to send the first hash value in the blockchain or database to the confirmation provider according to the third request, so that the confirmation provider can verify the consistency of the third hash value with the first hash value after decrypting the request parameters encrypted in the second request and generating the third hash value.

[0124] In one possible design, the hash value sending module includes: an information extraction module, a hash value extraction module and a hash value sending module.

[0125] The information extraction module is used to extract the confirmation initiator identification information and transaction number information from the third request.

[0126] The hash value extraction module is used to extract the first hash value corresponding to the transaction number information from the blockchain or database based on the confirmation initiator identification information and the transaction number information.

[0127] The hash value sending module is used to send the extracted first hash value to the confirmation providing end.

[0128] In one possible design, the letter of credit management platform also includes a service gateway.

[0129] Correspondingly, the accounting module 510 is also used to receive the first request sent by the confirmation initiator through the service gateway.

[0130] The request sending module 520 is further configured to receive a second request sent by the confirmation initiator through the service gateway.

[0131] The request sending module 520 is further configured to send the second request to the confirmation provider through the service gateway;

[0132] The accounting module 510 is further configured to receive a third request sent by the confirmation provider through the service gateway.

[0133] The reply sending module 530 is further configured to receive the fourth request sent by the confirmation provider through the service gateway, and send the fourth request to the confirmation initiator according to the identification information of the confirmation initiator.

[0134] This embodiment provides a confirmation management platform that can execute a confirmation management method of the above embodiment. Its implementation principle and technical effects are similar and will not be described in detail in this embodiment.

[0135] In a specific implementation of the aforementioned letter of credit management platform, each module and unit can be implemented as a processor, and the processor can execute computer-executable instructions stored in the memory, so that the processor executes the aforementioned letter of credit management method.

[0136] Figure 6 This is a schematic diagram of the structure of the electronic device provided in the embodiment of the present application. Figure 6 As shown, the electronic device includes: at least one processor 610 and a memory 620. The electronic device also includes a communication component 630. The processor 610, the memory 620 and the communication component 630 are connected via a bus 640.

[0137] During the specific implementation process, at least one processor 610 executes the computer execution instructions stored in the memory 620, so that at least one processor 610 executes a confirmation management method as executed on the electronic device side as described above.

[0138] The specific implementation process of the processor 610 can be found in the above method embodiment. Its implementation principle and technical effects are similar and will not be repeated here in this embodiment.

[0139] In the above embodiments, it should be understood that the processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASICs), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the present invention may be directly executed by a hardware processor or by a combination of hardware and software modules within the processor.

[0140] The memory may include a high-speed RAM memory, and may also include a non-volatile storage NVM, such as at least one disk storage.

[0141] A bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. Buses can be categorized as address buses, data buses, and control buses. For ease of illustration, the buses in the drawings of this application are not limited to just one bus or just one type of bus.

[0142] The above-mentioned functions implemented by the electronic device and the main control device have introduced the solutions provided by the embodiments of the present invention. It can be understood that in order to implement the above-mentioned functions, the electronic device or the main control device includes hardware structures and / or software modules corresponding to the execution of each function. In combination with the units and algorithm steps of the various examples described in the embodiments disclosed in the embodiments of the present invention, the embodiments of the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solution of the embodiments of the present invention.

[0143] The present application also provides a computer-readable storage medium, which stores computer-executable instructions. When a processor executes the computer-executable instructions, it is used to implement the above-mentioned letter of credit management method.

[0144] The readable storage medium may be implemented by any type of volatile or non-volatile memory device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0145] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be an integral part of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the readable storage medium can also exist as discrete components in an electronic device or a main control device.

[0146] The present application also provides a computer program product, which includes a computer program. The computer program is stored in a readable storage medium. At least one processor of an electronic device can read the computer program from the readable storage medium. At least one processor executes the computer program so that the electronic device executes the solution provided by the above embodiment.

[0147] Those skilled in the art will appreciate that all or part of the steps in the above-described method embodiments can be implemented using hardware associated with program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0148] So far, the technical solution of the present application has been described in conjunction with the preferred embodiments shown in the accompanying drawings. However, it is easy for those skilled in the art to understand that the scope of protection of the present application is obviously not limited to these specific embodiments. The above embodiments are only used to illustrate the technical solution of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, ordinary technicians in this field should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solution to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A confirmation management method, characterized in that: The method is applied to a confirmation management platform and includes: Receive a first request sent by a confirmation initiator, and store the first request in a blockchain and a database, wherein the first request includes identification information of the confirmation initiator, transaction number information, and a first hash value generated by the confirmation initiator based on request parameters input by the user; receiving a second request sent by the confirmation initiator, the second request including the confirmation initiator identification information, the transaction number information, the encrypted request parameters, and the confirmation provider identification information; sending the second request to the confirmation provider according to the confirmation provider identification information, so that the confirmation provider generates an electronic reply file according to the second request; receiving a third request sent by the confirmation provider, and storing the third request in the blockchain and the database, the third request including the confirmation provider identification information, the transaction number information, the confirmation initiator identification information, and a second hash value generated by the confirmation provider based on the electronic reply document; Receive the fourth request sent by the confirmation provider, and send the fourth request to the confirmation initiator according to the confirmation initiator identification information, the fourth request including the confirmation provider identification information, the transaction number information, the encrypted electronic reply file and the confirmation initiator identification information.

2. The method according to claim 1, characterized in that Storing the first request in the blockchain and the database includes: When a storage function of the blockchain or the database is abnormal, storing the first request in a cache; When the storage function of the blockchain or the database returns to normal, the first request in the cache is stored in the blockchain or the database.

3. The method according to claim 2, characterized in that When an abnormality occurs in the storage function of the blockchain or the database, storing the first request in a cache includes: When detecting an abnormality in the network connection of the blockchain or an abnormality in the storage function of the database, stopping the operation of directly storing the first request in the blockchain or directly storing it in the database, and storing the first request in the cache in the order of the time when the request was initiated; When the storage function of the blockchain or the database returns to normal, storing the first request in the cache in the blockchain or the database includes: When the storage function of the blockchain or the database returns to normal, a retry submission mechanism of the first request saved in the cache is triggered, and the first request is stored in the blockchain or the database in the order of the time when the request was initiated.

4. The method according to claim 1, wherein After receiving the third request sent by the confirmation provider, the method further includes: The first hash value in the blockchain or the database is sent to the confirmation provider according to the third request, so that the confirmation provider verifies the consistency of the third hash value with the first hash value after decrypting the request parameters encrypted in the second request and generating the third hash value.

5. The method according to claim 4, characterized in that The sending the first hash value in the blockchain or the database to the confirmation providing end according to the third request includes: Extracting the confirmation originator identification information and the transaction number information from the third request; Extracting a first hash value corresponding to the transaction number information from the blockchain or the database based on the confirmation initiator identification information and the transaction number information; The extracted first hash value is sent to the confirmation provider.

6. The method according to any one of claims 1 to 5, characterized in that The letter of credit management platform also includes a service gateway; Accordingly, the receiving of the first request sent by the confirmation initiator includes: Receiving, through the service gateway, a first request sent by a confirmation initiator; The receiving the second request sent by the confirmation initiator includes: Receiving, through the service gateway, a second request sent by the confirmation initiator; The sending of the second request to the confirmation provider includes: Sending the second request to the letter confirmation provider through the service gateway; The receiving the third request sent by the confirmation provider includes: Receiving, through the service gateway, a third request sent by the confirmation provider; The receiving the fourth request sent by the confirmation providing end, and sending the fourth request to the confirmation initiating end according to the confirmation initiating end identification information, includes: The fourth request sent by the confirmation provider is received through the service gateway, and the fourth request is sent to the confirmation initiator according to the identification information of the confirmation initiator.

7. A letter of credit management platform, characterized in that: include: Accounting module, request sending module and reply sending module; The accounting module is configured to receive a first request sent by a confirmation initiator and store the first request in the blockchain and the database, wherein the first request includes identification information of the confirmation initiator, transaction number information, and a first hash value generated by the confirmation initiator based on request parameters input by the user; The request sending module is configured to receive a second request sent by the confirmation initiator, wherein the second request includes the confirmation initiator identification information, the transaction number information, the encrypted request parameters, and the confirmation provider identification information; The request sending module is further configured to send the second request to the confirmation provider according to the confirmation provider identification information, so that the confirmation provider generates an electronic reply file according to the second request; The accounting module is further configured to receive a third request sent by the confirmation provider, and store the third request in the blockchain and the database, wherein the third request includes identification information of the confirmation provider, transaction number information, identification information of the confirmation initiator, and a second hash value generated by the confirmation provider based on the electronic reply document; The reply letter sending module is used to receive the fourth request sent by the confirmation provider and send the fourth request to the confirmation initiator according to the confirmation initiator identification information. The fourth request includes the confirmation provider identification information, the transaction number information, the encrypted electronic reply letter file and the confirmation initiator identification information.

8. An electronic device, characterized in that: include: a processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 6 when executed by a processor.

10. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 6 when the computer program is executed by a processor.

Images